Repository: NUWCDIVNPT/stig-manager
Branch: main
Commit: b21da06cca79
Files: 613
Total size: 25.8 MB
Directory structure:
gitextract_d5fz8a2i/
├── .dockerignore
├── .github/
│ ├── ISSUE_TEMPLATE/
│ │ ├── bug-report-form.yml
│ │ └── feature_request.md
│ └── workflows/
│ ├── api-audit-test-coverage-response.yml
│ ├── api-binary-tests.yml
│ ├── api-container-tests.yml
│ ├── api-spec-validation.yml
│ ├── api-state-tests.yml
│ ├── build-binary-artifacts.yml
│ ├── build-client.yml
│ ├── build-docs.yml
│ ├── client-sonarcloud.yml
│ ├── pub-docker.yml
│ └── unit-tests.yml
├── .readthedocs.yml
├── CONTRIBUTING.md
├── CONTRIBUTORS.md
├── Dockerfile
├── INTENT.md
├── LICENSE.md
├── README.md
├── SECURITY.md
├── api/
│ ├── README.md
│ ├── bin/
│ │ └── .gitignore
│ ├── build.sh
│ ├── dist/
│ │ └── .gitignore
│ ├── launchers/
│ │ ├── gen-launchers.py
│ │ ├── stig-manager.bat
│ │ └── stig-manager.sh
│ ├── nuwcdivnpt-bot.gpg.asc
│ ├── pkg.config.json
│ └── source/
│ ├── README.md
│ ├── bootstrap/
│ │ ├── bootstrapUtils.js
│ │ ├── client.js
│ │ ├── dependencies.js
│ │ ├── docs.js
│ │ ├── errorHandlers.js
│ │ ├── extensionCheck.js
│ │ ├── middlewares.js
│ │ ├── server.js
│ │ └── signals.js
│ ├── controllers/
│ │ ├── Asset.js
│ │ ├── Collection.js
│ │ ├── Job.js
│ │ ├── Metrics.js
│ │ ├── Operation.js
│ │ ├── Review.js
│ │ ├── STIG.js
│ │ └── User.js
│ ├── healthcheck.js
│ ├── index.js
│ ├── package.json
│ ├── service/
│ │ ├── AssetService.js
│ │ ├── CollectionService.js
│ │ ├── JobService.js
│ │ ├── MetricsService.js
│ │ ├── OperationService.js
│ │ ├── ReviewService.js
│ │ ├── STIGService.js
│ │ ├── UserService.js
│ │ ├── migrations/
│ │ │ ├── 0000.js
│ │ │ ├── 0001.js
│ │ │ ├── 0002.js
│ │ │ ├── 0003.js
│ │ │ ├── 0004.js
│ │ │ ├── 0005.js
│ │ │ ├── 0006.js
│ │ │ ├── 0007.js
│ │ │ ├── 0008.js
│ │ │ ├── 0009.js
│ │ │ ├── 0010.js
│ │ │ ├── 0011.js
│ │ │ ├── 0012.js
│ │ │ ├── 0013.js
│ │ │ ├── 0014.js
│ │ │ ├── 0015.js
│ │ │ ├── 0016.js
│ │ │ ├── 0017.js
│ │ │ ├── 0018.js
│ │ │ ├── 0019.js
│ │ │ ├── 0020.js
│ │ │ ├── 0021.js
│ │ │ ├── 0022.js
│ │ │ ├── 0023.js
│ │ │ ├── 0024.js
│ │ │ ├── 0025.js
│ │ │ ├── 0026.js
│ │ │ ├── 0027.js
│ │ │ ├── 0028.js
│ │ │ ├── 0029.js
│ │ │ ├── 0032.js
│ │ │ ├── 0033.js
│ │ │ ├── 0034.js
│ │ │ ├── 0035.js
│ │ │ ├── 0036.js
│ │ │ ├── 0037.js
│ │ │ ├── 0038.js
│ │ │ ├── 0039.js
│ │ │ ├── 0040.js
│ │ │ ├── 0041.js
│ │ │ ├── 0042.js
│ │ │ ├── 0043.js
│ │ │ ├── 0044.js
│ │ │ ├── 0045.js
│ │ │ ├── 0046.js
│ │ │ ├── lib/
│ │ │ │ ├── MigrationHandler.js
│ │ │ │ ├── mysql-import.js
│ │ │ │ └── umzug-mysql-storage.js
│ │ │ └── sql/
│ │ │ ├── 0000/
│ │ │ │ └── up/
│ │ │ │ ├── 10-stigman-schema.sql
│ │ │ │ ├── 31-stigman-static.sql
│ │ │ │ └── 32-cci-data.sql
│ │ │ ├── 0001/
│ │ │ │ ├── down/
│ │ │ │ │ └── 10-collection-created.sql
│ │ │ │ └── up/
│ │ │ │ └── 10-collection-created.sql
│ │ │ ├── 0002/
│ │ │ │ ├── down/
│ │ │ │ │ └── 10-collection-description.sql
│ │ │ │ └── up/
│ │ │ │ └── 10-collection-description.sql
│ │ │ ├── 0003/
│ │ │ │ └── up/
│ │ │ │ └── 10-asset-mac-fqdn.sql
│ │ │ ├── 0004/
│ │ │ │ └── up/
│ │ │ │ └── 10-user-data.sql
│ │ │ ├── 0005/
│ │ │ │ ├── down/
│ │ │ │ │ └── 10-v-current-rev.sql
│ │ │ │ └── up/
│ │ │ │ └── 10-v-current-rev.sql
│ │ │ ├── 0006/
│ │ │ │ └── up/
│ │ │ │ └── 10-v-current-rev.sql
│ │ │ ├── current/
│ │ │ │ ├── 10-stigman-tables.sql
│ │ │ │ ├── 20-stigman-static.sql
│ │ │ │ └── 31-rev5-cci-data.sql
│ │ │ └── generateSchema.sh
│ │ └── utils.js
│ ├── specification/
│ │ ├── log-socket.yaml
│ │ └── stig-manager.yaml
│ ├── tls/
│ │ └── README.md
│ └── utils/
│ ├── PoolMonitor.js
│ ├── asyncApiValidator.js
│ ├── auth.js
│ ├── buffer-json.js
│ ├── config.js
│ ├── error.js
│ ├── escape.js
│ ├── jwksCache.js
│ ├── klona.js
│ ├── log-schema.json
│ ├── logSocket.js
│ ├── logger.js
│ ├── parsers.js
│ ├── poam-template-mccast.xlsx
│ ├── poam-template.xlsx
│ ├── roles.js
│ ├── serializeError.js
│ ├── serializers.js
│ ├── state.js
│ ├── writer.js
│ └── xlsx-template-js-zip-upgrade/
│ ├── LICENSE
│ ├── README.md
│ ├── lib/
│ │ ├── index.d.ts
│ │ └── index.js
│ └── package.json
├── client/
│ ├── README.md
│ ├── build.sh
│ ├── dist/
│ │ └── .gitignore
│ └── src/
│ ├── css/
│ │ ├── ColumnHeaderGroup.css
│ │ ├── RowEditor.css
│ │ ├── dark-mode.css
│ │ ├── init.css
│ │ ├── jsonview.bundle.css
│ │ └── stigman.css
│ ├── ext/
│ │ ├── INCLUDE_ORDER.txt
│ │ ├── adapter/
│ │ │ └── ext/
│ │ │ ├── ext-base-debug.js
│ │ │ └── ext-base.js
│ │ ├── ext-all-debug-w-comments.js
│ │ ├── ext-all-debug.js
│ │ ├── ext-all.js
│ │ ├── ext.jsb2
│ │ ├── gpl-3.0.txt
│ │ ├── index.html
│ │ ├── license.txt
│ │ ├── release-notes.html
│ │ ├── resources/
│ │ │ ├── charts.swf
│ │ │ ├── css/
│ │ │ │ ├── debug.css
│ │ │ │ ├── ext-all-notheme.css
│ │ │ │ ├── ext-all.css
│ │ │ │ ├── reset-min.css
│ │ │ │ ├── structure/
│ │ │ │ │ ├── borders.css
│ │ │ │ │ ├── box.css
│ │ │ │ │ ├── button.css
│ │ │ │ │ ├── combo.css
│ │ │ │ │ ├── core.css
│ │ │ │ │ ├── date-picker.css
│ │ │ │ │ ├── dd.css
│ │ │ │ │ ├── debug.css
│ │ │ │ │ ├── dialog.css
│ │ │ │ │ ├── editor.css
│ │ │ │ │ ├── form.css
│ │ │ │ │ ├── grid.css
│ │ │ │ │ ├── layout.css
│ │ │ │ │ ├── list-view.css
│ │ │ │ │ ├── menu.css
│ │ │ │ │ ├── panel-reset.css
│ │ │ │ │ ├── panel.css
│ │ │ │ │ ├── pivotgrid.css
│ │ │ │ │ ├── progress.css
│ │ │ │ │ ├── qtips.css
│ │ │ │ │ ├── reset.css
│ │ │ │ │ ├── resizable.css
│ │ │ │ │ ├── slider.css
│ │ │ │ │ ├── tabs.css
│ │ │ │ │ ├── toolbar.css
│ │ │ │ │ ├── tree.css
│ │ │ │ │ └── window.css
│ │ │ │ ├── theme-access/
│ │ │ │ │ ├── borders.css
│ │ │ │ │ ├── box.css
│ │ │ │ │ ├── button.css
│ │ │ │ │ ├── combo.css
│ │ │ │ │ ├── core.css
│ │ │ │ │ ├── date-picker.css
│ │ │ │ │ ├── dd.css
│ │ │ │ │ ├── debug.css
│ │ │ │ │ ├── dialog.css
│ │ │ │ │ ├── editor.css
│ │ │ │ │ ├── form.css
│ │ │ │ │ ├── grid.css
│ │ │ │ │ ├── layout.css
│ │ │ │ │ ├── list-view.css
│ │ │ │ │ ├── menu.css
│ │ │ │ │ ├── panel.css
│ │ │ │ │ ├── progress.css
│ │ │ │ │ ├── qtips.css
│ │ │ │ │ ├── resizable.css
│ │ │ │ │ ├── slider.css
│ │ │ │ │ ├── tabs.css
│ │ │ │ │ ├── toolbar.css
│ │ │ │ │ ├── tree.css
│ │ │ │ │ └── window.css
│ │ │ │ ├── theme-gray/
│ │ │ │ │ ├── borders.css
│ │ │ │ │ ├── box.css
│ │ │ │ │ ├── button.css
│ │ │ │ │ ├── combo.css
│ │ │ │ │ ├── core.css
│ │ │ │ │ ├── date-picker.css
│ │ │ │ │ ├── dd.css
│ │ │ │ │ ├── debug.css
│ │ │ │ │ ├── dialog.css
│ │ │ │ │ ├── editor.css
│ │ │ │ │ ├── form.css
│ │ │ │ │ ├── grid.css
│ │ │ │ │ ├── layout.css
│ │ │ │ │ ├── list-view.css
│ │ │ │ │ ├── menu.css
│ │ │ │ │ ├── panel.css
│ │ │ │ │ ├── pivotgrid.css
│ │ │ │ │ ├── progress.css
│ │ │ │ │ ├── qtips.css
│ │ │ │ │ ├── resizable.css
│ │ │ │ │ ├── slider.css
│ │ │ │ │ ├── tabs.css
│ │ │ │ │ ├── toolbar.css
│ │ │ │ │ ├── tree.css
│ │ │ │ │ └── window.css
│ │ │ │ ├── visual/
│ │ │ │ │ ├── borders.css
│ │ │ │ │ ├── box.css
│ │ │ │ │ ├── button.css
│ │ │ │ │ ├── combo.css
│ │ │ │ │ ├── core.css
│ │ │ │ │ ├── date-picker.css
│ │ │ │ │ ├── dd.css
│ │ │ │ │ ├── debug.css
│ │ │ │ │ ├── dialog.css
│ │ │ │ │ ├── editor.css
│ │ │ │ │ ├── form.css
│ │ │ │ │ ├── grid.css
│ │ │ │ │ ├── layout.css
│ │ │ │ │ ├── list-view.css
│ │ │ │ │ ├── menu.css
│ │ │ │ │ ├── panel.css
│ │ │ │ │ ├── pivotgrid.css
│ │ │ │ │ ├── progress.css
│ │ │ │ │ ├── qtips.css
│ │ │ │ │ ├── resizable.css
│ │ │ │ │ ├── slider.css
│ │ │ │ │ ├── tabs.css
│ │ │ │ │ ├── toolbar.css
│ │ │ │ │ ├── tree.css
│ │ │ │ │ └── window.css
│ │ │ │ ├── xtheme-access.css
│ │ │ │ ├── xtheme-blue.css
│ │ │ │ ├── xtheme-gray.css
│ │ │ │ └── yourtheme.css
│ │ │ ├── expressinstall.swf
│ │ │ └── images/
│ │ │ ├── access/
│ │ │ │ └── form/
│ │ │ │ ├── clear-trigger.psd
│ │ │ │ ├── date-trigger.psd
│ │ │ │ ├── search-trigger.psd
│ │ │ │ └── trigger.psd
│ │ │ ├── default/
│ │ │ │ ├── form/
│ │ │ │ │ ├── clear-trigger.psd
│ │ │ │ │ ├── date-trigger.psd
│ │ │ │ │ ├── search-trigger.psd
│ │ │ │ │ ├── trigger-square.psd
│ │ │ │ │ └── trigger.psd
│ │ │ │ └── window/
│ │ │ │ ├── left-corners.psd
│ │ │ │ ├── left-right.psd
│ │ │ │ ├── right-corners.psd
│ │ │ │ └── top-bottom.psd
│ │ │ └── yourtheme/
│ │ │ ├── README.txt
│ │ │ ├── form/
│ │ │ │ ├── clear-trigger.psd
│ │ │ │ ├── date-trigger.psd
│ │ │ │ ├── search-trigger.psd
│ │ │ │ ├── trigger-square.psd
│ │ │ │ └── trigger.psd
│ │ │ └── window/
│ │ │ ├── left-corners.psd
│ │ │ ├── left-right.psd
│ │ │ ├── right-corners.psd
│ │ │ └── top-bottom.psd
│ │ └── ux/
│ │ ├── BufferView.js
│ │ ├── CenterLayout.js
│ │ ├── CheckColumn.js
│ │ ├── ColumnHeaderGroup.js
│ │ ├── ColumnNodeUI.js
│ │ ├── DataView-more.js
│ │ ├── DataViewTransition.js
│ │ ├── FieldLabeler.js
│ │ ├── FieldReplicator.js
│ │ ├── Focus.js
│ │ ├── GMapPanel.js
│ │ ├── GroupSummary.js
│ │ ├── GroupTab.js
│ │ ├── GroupTabPanel.js
│ │ ├── ItemSelector.js
│ │ ├── LockingGridView.js
│ │ ├── MultiSelect.js
│ │ ├── PagingMemoryProxy.js
│ │ ├── PanelResizer.js
│ │ ├── Portal.js
│ │ ├── PortalColumn.js
│ │ ├── Portlet.js
│ │ ├── ProgressBarPager.js
│ │ ├── Reorderer.js
│ │ ├── RowEditor.js
│ │ ├── RowExpander.js
│ │ ├── RowLayout.js
│ │ ├── SearchField.js
│ │ ├── SelectBox.js
│ │ ├── SlidingPager.js
│ │ ├── Spinner.js
│ │ ├── SpinnerField.js
│ │ ├── Spotlight.js
│ │ ├── TabCloseMenu.js
│ │ ├── TabScrollerMenu.js
│ │ ├── TableGrid.js
│ │ ├── ToolbarDroppable.js
│ │ ├── ToolbarReorderer.js
│ │ ├── XmlTreeLoader.js
│ │ ├── css/
│ │ │ ├── CenterLayout.css
│ │ │ ├── ColumnHeaderGroup.css
│ │ │ ├── ColumnNodeUI.css
│ │ │ ├── GroupSummary.css
│ │ │ ├── GroupTab.css
│ │ │ ├── LockingGridView.css
│ │ │ ├── MultiSelect.css
│ │ │ ├── PanelResizer.css
│ │ │ ├── Portal.css
│ │ │ ├── RowEditor.css
│ │ │ ├── Spinner.css
│ │ │ └── ux-all.css
│ │ ├── fileuploadfield/
│ │ │ ├── FileUploadField.js
│ │ │ └── css/
│ │ │ └── fileuploadfield.css
│ │ ├── gridfilters/
│ │ │ ├── GridFilters.js
│ │ │ ├── css/
│ │ │ │ ├── GridFilters.css
│ │ │ │ └── RangeMenu.css
│ │ │ ├── filter/
│ │ │ │ ├── BooleanFilter.js
│ │ │ │ ├── DateFilter.js
│ │ │ │ ├── Filter.js
│ │ │ │ ├── ListFilter.js
│ │ │ │ ├── NumericFilter.js
│ │ │ │ └── StringFilter.js
│ │ │ └── menu/
│ │ │ ├── ListMenu.js
│ │ │ └── RangeMenu.js
│ │ ├── statusbar/
│ │ │ ├── StatusBar.js
│ │ │ ├── ValidationStatus.js
│ │ │ └── css/
│ │ │ └── statusbar.css
│ │ ├── treegrid/
│ │ │ ├── TreeGrid.js
│ │ │ ├── TreeGridColumnResizer.js
│ │ │ ├── TreeGridColumns.js
│ │ │ ├── TreeGridLoader.js
│ │ │ ├── TreeGridNodeUI.js
│ │ │ ├── TreeGridSorter.js
│ │ │ └── treegrid.css
│ │ ├── ux-all-debug.js
│ │ └── ux-all.js
│ ├── index.html
│ ├── js/
│ │ ├── BufferView.js
│ │ ├── ColumnHeaderGroup.js
│ │ ├── Env.js.example
│ │ ├── ExportButton.js
│ │ ├── FileSaver.js
│ │ ├── FileUploadField.js
│ │ ├── LockingGridView.js
│ │ ├── MessageBox.js
│ │ ├── RowEditor.js
│ │ ├── RowExpander.js
│ │ ├── SM/
│ │ │ ├── Acl.js
│ │ │ ├── ActivityHandler.js
│ │ │ ├── Ajax.js
│ │ │ ├── ApiState.js
│ │ │ ├── AppData.js
│ │ │ ├── AppInfo.js
│ │ │ ├── AssetSelection.js
│ │ │ ├── Attachments.js
│ │ │ ├── BatchReview.js
│ │ │ ├── Cache.js
│ │ │ ├── Checklist.js
│ │ │ ├── Classification.js
│ │ │ ├── CollectionClone.js
│ │ │ ├── CollectionPanel.js
│ │ │ ├── ColumnFilters.js
│ │ │ ├── Error.js
│ │ │ ├── EventDispatcher.js
│ │ │ ├── Exports.js
│ │ │ ├── FindingsPanel.js
│ │ │ ├── FlexboxLayout.js
│ │ │ ├── Global.js
│ │ │ ├── Grant.js
│ │ │ ├── Inventory.js
│ │ │ ├── Job.js
│ │ │ ├── Library.js
│ │ │ ├── LogStream.js
│ │ │ ├── MainPanel.js
│ │ │ ├── Manage.js
│ │ │ ├── MetaPanel.js
│ │ │ ├── NavTree.js
│ │ │ ├── Review.js
│ │ │ ├── ReviewsImport.js
│ │ │ ├── RowEditorToolbar.js
│ │ │ ├── SelectingGridToolbar.js
│ │ │ ├── ServiceWorker.js
│ │ │ ├── StackTrace.js
│ │ │ ├── State.js
│ │ │ ├── StigRevision.js
│ │ │ ├── TipContent.js
│ │ │ ├── TransferAssets.js
│ │ │ ├── User.js
│ │ │ ├── UserGroup.js
│ │ │ └── WhatsNew.js
│ │ ├── collectionAdmin.js
│ │ ├── collectionManager.js
│ │ ├── collectionReview.js
│ │ ├── completionStatus.js
│ │ ├── diff.js
│ │ ├── findingsSummary.js
│ │ ├── init.js
│ │ ├── jsonview.bundle.js
│ │ ├── library.js
│ │ ├── modules/
│ │ │ ├── package.json
│ │ │ └── source-map/
│ │ │ ├── mappings.wasm
│ │ │ └── source-map.js
│ │ ├── overrides.js
│ │ ├── resources-dist.js
│ │ ├── resources.js
│ │ ├── review.js
│ │ ├── stigAdmin.js
│ │ ├── stigman.js
│ │ ├── stigmanUtils.js
│ │ └── workers/
│ │ ├── oidc-worker.js
│ │ ├── service-worker.js
│ │ └── state-worker.js
│ └── reauth.html
├── data/
│ ├── appdata/
│ │ └── README.md
│ └── schemas/
│ ├── Stigman-Model.mwb
│ └── _manifest.json
├── docker-build.sh
├── docs/
│ ├── .nojekyll
│ ├── Dockerfile
│ ├── Makefile
│ ├── STIG-Manager-OSS.ckl
│ ├── _build/
│ │ ├── .gitignore
│ │ └── html/
│ │ └── .gitignore
│ ├── _static/
│ │ └── css/
│ │ ├── custom-pydata-theme.css
│ │ └── custom.css
│ ├── admin-guide/
│ │ ├── admin-guide.rst
│ │ ├── admin-quickstart.rst
│ │ └── index.rst
│ ├── build.sh
│ ├── conf.py
│ ├── features/
│ │ ├── common-tasks.rst
│ │ └── index.rst
│ ├── index.html
│ ├── index.rst
│ ├── installation-and-setup/
│ │ ├── authentication.rst
│ │ ├── data-and-permissions.rst
│ │ ├── db.rst
│ │ ├── environment-variables.rst
│ │ ├── envvars-node.csv
│ │ ├── envvars.csv
│ │ ├── index.rst
│ │ ├── installation-and-setup.rst
│ │ ├── logging.rst
│ │ ├── reverse-proxy.rst
│ │ ├── securing.rst
│ │ └── stigman-asd-full.csv
│ ├── make.bat
│ ├── reference/
│ │ └── index.rst
│ ├── requirements.txt
│ ├── the-project/
│ │ ├── DockerHub_Readme.md
│ │ ├── clients.rst
│ │ ├── contributing.rst
│ │ ├── documentation.rst
│ │ ├── examples.rst
│ │ ├── index.rst
│ │ ├── project-description.rst
│ │ ├── related-repos.rst
│ │ ├── requirements-and-dependencies.rst
│ │ └── testing.rst
│ └── user-guide/
│ ├── Stig-Manager-Asset-Batch-Import.csv
│ ├── index.rst
│ ├── republished-rules.csv
│ ├── review-handling.rst
│ ├── roles-and-access.rst
│ ├── rule-exceptions.rst
│ ├── user-guide.rst
│ └── user-quickstart.rst
├── release-notes.rst
├── root.json
└── test/
├── api/
│ ├── README.md
│ ├── appdata/
│ │ ├── appdata-meta-metrics-with-pin.jsonl
│ │ ├── appdata.jsonl
│ │ ├── batch-test-data.jsonl
│ │ ├── user-status-get-post.jsonl
│ │ └── user-status-patch-put.jsonl
│ ├── dark.css
│ ├── form-data-files/
│ │ ├── U_MS_Windows_10_STIG_V1R23_Manual-xccdf.xml
│ │ ├── U_RHEL_7_STIG_V3R0-3_Manual-xccdf.xml
│ │ ├── U_VPN_SRG-OTHER_V1R1_Manual-xccdf.xml
│ │ ├── U_VPN_SRG-OTHER_V1R1_twoRules-matchingFingerprints.xml
│ │ ├── U_VPN_SRG_V1R0_Manual-xccdf.xml
│ │ ├── U_VPN_SRG_V1R1_Manual-xccdf-replace.xml
│ │ ├── U_VPN_SRG_V1R1_Manual-xccdf.xml
│ │ └── U_VPN_SRG_V2R3_Manual-xccdf-reviewKeyChange.xml
│ ├── mocha/
│ │ ├── cross-boundary/
│ │ │ └── lvl1.test.js
│ │ ├── data/
│ │ │ ├── acl/
│ │ │ │ ├── directAcl.test.js
│ │ │ │ ├── directIterations.js
│ │ │ │ ├── groupAcl.test.js
│ │ │ │ ├── groupIterations.js
│ │ │ │ └── referenceData.js
│ │ │ ├── asset/
│ │ │ │ ├── assetDelete.test.js
│ │ │ │ ├── assetGet.test.js
│ │ │ │ ├── assetPatch.test.js
│ │ │ │ ├── assetPost.test.js
│ │ │ │ ├── assetPut.test.js
│ │ │ │ ├── expectations.js
│ │ │ │ └── requestBodies.js
│ │ │ ├── collection/
│ │ │ │ ├── collectionDelete.test.js
│ │ │ │ ├── collectionGet.test.js
│ │ │ │ ├── collectionPatch.test.js
│ │ │ │ ├── collectionPost.test.js
│ │ │ │ ├── collectionPut.test.js
│ │ │ │ ├── expectations.js
│ │ │ │ └── requestBodies.js
│ │ │ ├── metrics/
│ │ │ │ ├── expectations.js
│ │ │ │ ├── metaMetricsGet.json
│ │ │ │ ├── metaMetricsGet.test.js
│ │ │ │ ├── metricsGet.json
│ │ │ │ └── metricsGet.test.js
│ │ │ ├── operation/
│ │ │ │ └── op.test.js
│ │ │ ├── review/
│ │ │ │ ├── expectations.js
│ │ │ │ ├── requestBodies.js
│ │ │ │ ├── reviewDelete.test.js
│ │ │ │ ├── reviewGet.test.js
│ │ │ │ ├── reviewPatch.test.js
│ │ │ │ ├── reviewPost.test.js
│ │ │ │ └── reviewPut.test.js
│ │ │ ├── stig/
│ │ │ │ ├── expectations.js
│ │ │ │ └── stigs.test.js
│ │ │ ├── user/
│ │ │ │ ├── expectations.js
│ │ │ │ ├── requestBodies.js
│ │ │ │ └── user.test.js
│ │ │ └── user-group/
│ │ │ ├── requestBodies.js
│ │ │ └── user-group.test.js
│ │ ├── integration/
│ │ │ ├── access.test.js
│ │ │ ├── aclResolution.test.js
│ │ │ ├── asset.test.js
│ │ │ ├── collection.test.js
│ │ │ ├── deleteHandling.test.js
│ │ │ ├── expectations.js
│ │ │ ├── grantChange.test.js
│ │ │ ├── job.test.js
│ │ │ ├── logStream.test.js
│ │ │ ├── metrics.test.js
│ │ │ ├── resultEngine.test.js
│ │ │ ├── review.test.js
│ │ │ ├── revisionPinning.test.js
│ │ │ ├── roleResolution.test.js
│ │ │ ├── stig.test.js
│ │ │ └── userStatus.test.js
│ │ ├── iterations.js
│ │ ├── referenceData.js
│ │ ├── security/
│ │ │ └── reviewCrossCollectionWrite.test.js
│ │ ├── testConfig.js
│ │ └── utils/
│ │ └── testUtils.js
│ ├── mock-keycloak/
│ │ └── auth/
│ │ └── realms/
│ │ └── stigman/
│ │ ├── .well-known/
│ │ │ └── openid-configuration
│ │ └── protocol/
│ │ └── openid-connect/
│ │ └── certs
│ ├── mock-keycloak-test-cases/
│ │ ├── no-jwks/
│ │ │ └── auth/
│ │ │ └── realms/
│ │ │ └── stigman/
│ │ │ ├── .well-known/
│ │ │ │ └── openid-configuration
│ │ │ └── protocol/
│ │ │ └── openid-connect/
│ │ │ └── certs
│ │ └── secure-kid/
│ │ └── auth/
│ │ └── realms/
│ │ └── stigman/
│ │ ├── .well-known/
│ │ │ └── openid-configuration
│ │ └── protocol/
│ │ └── openid-connect/
│ │ └── certs
│ ├── package.json
│ └── runMocha.sh
├── state/
│ ├── drop-db.sh
│ ├── mocha/
│ │ ├── bootstrap.test.js
│ │ ├── db.test.js
│ │ ├── jwks.test.js
│ │ ├── lib.js
│ │ ├── oidc.test.js
│ │ └── tokenValidation.test.js
│ └── package.json
├── unit/
│ ├── mocha/
│ │ └── asyncApiValidator.test.js
│ └── package.json
└── utils/
├── appdata-update.js
├── mockOidc.js
└── package.json
================================================
FILE CONTENTS
================================================
================================================
FILE: .dockerignore
================================================
**/node_modules
**/state.json
**/README.md
**/.git
**/.gitignore
**/data
**/test
**/uploads
**/docker
!client/**/node_modules
================================================
FILE: .github/ISSUE_TEMPLATE/bug-report-form.yml
================================================
name: 🐞 Bug Report
description: File a bug/issue
title: "***The title of your Issue here***"
labels: [Bug, Needs Triage]
body:
- type: checkboxes
attributes:
label: Is there an existing issue for this?
description: Please search to see if an issue already exists for the bug you encountered.
options:
- label: I have searched the existing issues
required: true
- type: checkboxes
attributes:
label: Are you using the latest version of STIG Manager?
description: The latest release is . You can see the version you are using in the app on the Home tab, in the badge next to the STIG Manager name and logo. The STIGMan project is in development using an agile process that releases new features and bugfixes frequently.
options:
- label: I am using the latest [Release](https://github.com/NUWCDIVNPT/stig-manager/releases).
- label: I am NOT using the latest [Release](https://github.com/NUWCDIVNPT/stig-manager/releases). I am aware that the first thing I will be asked to do is update the application so that I have the latest bugfixes.
- type: checkboxes
id: issue-location
attributes:
label: Where are you experiencing the issue?
description: Select one or more.
options:
- label: API
- label: UI or other client
- label: Deployment
- label: Elsewhere
- type: textarea
attributes:
label: Current Behavior
description: A description of what you're experiencing.
validations:
required: true
- type: textarea
attributes:
label: Expected Behavior
description: A description of what you expected to happen.
validations:
required: false
- type: textarea
attributes:
label: Steps To Reproduce
description: Steps to reproduce the behavior.
placeholder: |
1. In this environment...
2. With this config...
3. Run '...'
4. See error...
validations:
required: false
- type: textarea
attributes:
label: Can you provide screenshots, logs, or other useful artifacts?
description: |
Links? References? Anything that will give us more context about the issue you are encountering!
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
validations:
required: false
- type: textarea
attributes:
label: Describe your Environment
description: |
examples:
- **Hosting**: Are you hosting your own deployment of STIGMan or being provided with an instance?
- **Browser**: Chrome
- **OS**: Ubuntu 20.04
- **Node**: 13.14.0
- **npm**: 7.6.3
value: |
- Hosting:
- Browser:
- OS:
- Node:
- npm:
render: markdown
validations:
required: false
================================================
FILE: .github/ISSUE_TEMPLATE/feature_request.md
================================================
---
name: Feature request
about: Suggest an idea for this project
title: 'FEATURE REQUEST: '
labels: enhancement
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
================================================
FILE: .github/workflows/api-audit-test-coverage-response.yml
================================================
name: API source
on:
workflow_dispatch:
pull_request:
branches:
- main
- test-coverage
paths:
- "api/source/**"
- "test/api/**"
- ".github/workflows/api-audit-test-coverage-response.yml"
push:
branches:
- main
- test-coverage
paths:
- "api/source/**"
- "test/api/**"
- ".github/workflows/api-audit-test-coverage-response.yml"
env:
STIGMAN_API_PORT: 64001
STIGMAN_DB_HOST: localhost
STIGMAN_DB_PORT: 3306
STIGMAN_DB_PASSWORD: stigman
STIGMAN_API_AUTHORITY: http://127.0.0.1:8080/auth/realms/stigman
STIGMAN_SWAGGER_ENABLED: true
STIGMAN_SWAGGER_SERVER: http://localhost:64001/api
STIGMAN_SWAGGER_REDIRECT: http://localhost:64001/api-docs/oauth2-redirect.html
STIGMAN_DEV_RESPONSE_VALIDATION: logOnly
STIGMAN_EXPERIMENTAL_APPDATA: 'true'
STIGMAN_DEV_ALLOW_INSECURE_TOKENS: 'true'
NODE_V8_COVERAGE: /home/runner/work/stig-manager/stig-manager/api/source/coverage/tmp/
permissions:
pull-requests: read # allows SonarCloud to decorate PRs with analysis results
jobs:
npm_audit:
name: npm audit
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: install dependencies
run: npm ci
working-directory: ./api/source/
- name: Audit Dependencies and Create PR Comment if needed
uses: oke-py/npm-audit-action@2c6b2da234031fbf72af81a04c76b3a152bb2222 # pin@v2
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
create_issues: false
create_pr_comments: true
working_directory: ./api/source/
test_api:
name: Run tests with coverage
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: lts/*
- name: coverage directory
run: printenv NODE_V8_COVERAGE
- name: Install app dependencies
working-directory: ./api/source
run: npm ci
- name: Install test dependencies
run: npm ci
working-directory: ./test/api/
- name: Install utils test dependencies
run: npm ci
working-directory: ./test/utils/
- name: Run mock Keycloak
id: idp-run
working-directory: ./test/api/mock-keycloak
run: |
python3 -m http.server 8080 &
- name: Run MySQL container
id: mysql-run
run: |
docker run -d --name stig-manager-db \
-p 3306:3306 \
-e MYSQL_ROOT_PASSWORD=rootpw \
-e MYSQL_DATABASE=stigman \
-e MYSQL_USER=stigman \
-e MYSQL_PASSWORD=stigman \
mysql:8.0.24
- name: Install c8 coverage reporter
run: |
sudo npm install -g c8
- name: Run app and echo pid
working-directory: ./api/source
run: sh -c 'echo $$ > /tmp/test.pid ; exec c8 -r html node index.js > api-log.json 2>&1' &
- name: pid file check
working-directory: ./api/source
run: cat /tmp/test.pid
- name: Wait for bootstrap
run: for i in {1..10}; do [ $i -gt 1 ] && sleep 5; curl --output /dev/null --silent --fail http://localhost:64001/api/op/configuration && s=0 && break || s=$?; printf '.'; done; (exit $s)
- name: Run tests with coverage
working-directory: ./test/api/
run: npm test
- name: Upload mocha test report
id: artifact-upload-mocha
uses: actions/upload-artifact@v4
if: ${{ always() }}
with:
name: mocha-report
path: ./test/api/mochawesome-report
- name: Kill child pid
working-directory: ./api/source
run: kill -SIGINT $(ps -ef --ppid `cat /tmp/test.pid` -o pid= )
- name: Wait until c8 process ends, or 60 seconds, whichever is shorter.
run: timeout 60 tail --pid=`cat /tmp/test.pid` -f /dev/null
- name: run c8 text/lcov report
working-directory: ./api/source
run: c8 report -r lcov -r text -r html
- name: Upload coverage artifact
id: artifact-upload-coverage
uses: actions/upload-artifact@v4
if: ${{ always() }}
with:
name: coverage-report
path: ./api/source/coverage
- name: Upload API logs
id: artifact-upload-api-logs
uses: actions/upload-artifact@v4
if: ${{ always() }}
with:
name: api-log
path: ./api/source/api-log.json
response_validation:
name: Response validation
needs:
- test_api
runs-on: ubuntu-latest
steps:
- name: Download API log artifact
uses: actions/download-artifact@v4
with:
name: api-log
path: ./logs
- name: Test for response validation messages
working-directory: ./logs
run: |
jq -s 'map(select(.type=="responseValidation")|{method:.data.request.method,url:.data.request.url,errors:.data.error.errors,body:.data.body})' api-log.json > response-validation.json
exit $(jq '. | length' response-validation.json)
- name: Upload response validation artifact
if: ${{ failure() }}
uses: actions/upload-artifact@v4
with:
name: response-validation
path: ./logs/response-validation.json
SonarCloudAnalysis-API:
name: SonarCloud Analysis
needs: test_api
runs-on: ubuntu-latest
steps:
- name: Check if PR is from a fork
id: check_fork
run: |
if [ "${{ github.event.pull_request.head.repo.fork }}" == "true" ]; then
echo "This is a PR from a fork, skipping sonarcloud analysis."
echo "SKIP_STEP=true" >> $GITHUB_ENV
fi
- name: Checkout repository
if: env.SKIP_STEP != 'true'
uses: actions/checkout@v4
with:
fetch-depth: 0 # Important to fetch all history for accurate blame information
- name: Download lcov artifact
if: env.SKIP_STEP != 'true'
uses: actions/download-artifact@v4
with:
name: coverage-report
- name: Move lcov.info to api/source
if: env.SKIP_STEP != 'true'
run: mv lcov.info ./api/source/
- name: Analyze API with SonarCloud
if: env.SKIP_STEP != 'true'
uses: SonarSource/sonarqube-scan-action@v6.0.0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN_API }} # Needed to push to SonarCloud
with:
# Additional arguments for the sonarcloud scanner
projectBaseDir: ./api/source
args: -Dsonar.projectKey=nuwcdivnpt_stig-manager-api
-Dsonar.projectName=nuwcdivnpt_stig-manager-api
-Dsonar.organization=nuwcdivnpt
-Dsonar.inclusions=**/*.js
-Dsonar.exclusions=**/node_modules/**,**/coverage-report/**
-Dsonar.javascript.lcov.reportPaths=./lcov.info
# This will fail the action if Quality Gate fails (leaving out for now )
# - name: Check Quality Gate
# uses: sonarsource/sonarqube-quality-gate-action@master
# env:
# SONAR_TOKEN:
================================================
FILE: .github/workflows/api-binary-tests.yml
================================================
name: Build and Test Linux Binary
on:
workflow_dispatch:
pull_request:
branches:
- main
paths:
- "api/source/**"
- "test/api/**"
- ".github/workflows/api-binary-tests.yml"
- "api/build.sh"
- "client/build.sh"
- "docs/build.sh"
push:
branches:
- main
paths:
- "api/source/**"
- "test/api/**"
- ".github/workflows/api-binary-tests.yml"
- "api/build.sh"
- "client/build.sh"
- "docs/build.sh"
env:
STIGMAN_API_PORT: 64001
STIGMAN_DB_HOST: localhost
STIGMAN_DB_PORT: 3306
STIGMAN_DB_PASSWORD: stigman
STIGMAN_API_AUTHORITY: http://127.0.0.1:8080/auth/realms/stigman
STIGMAN_SWAGGER_ENABLED: true
STIGMAN_SWAGGER_SERVER: http://127.0.0.1:64001/api
STIGMAN_SWAGGER_REDIRECT: http://127.0.0.1:64001/api-docs/oauth2-redirect.html
STIGMAN_DEV_RESPONSE_VALIDATION: logOnly
STIGMAN_EXPERIMENTAL_APPDATA: 'true'
STIGMAN_OIDC_PROVIDER: http://127.0.0.1:8080/auth/realms/stigman
STIGMAN_DEV_ALLOW_INSECURE_TOKENS: 'true'
jobs:
build-artifacts:
name: Build binary artifacts
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: lts/*
- name: Get repository metadata
id: repo
uses: actions/github-script@v7
with:
script: |
const repo = await github.rest.repos.get(context.repo)
return repo.data
- name: install uglify
run: |
sudo npm install -g uglify-js
- name: run build script
id: run-the-build-script
working-directory: ./api
run: ./build.sh
- name: Upload builds
if: always()
uses: actions/upload-artifact@v4
with:
name: binary-artifacts
path: ./api/bin/
if-no-files-found: error
- name: Upload archives
if: always()
uses: actions/upload-artifact@v4
with:
name: binary-archives
path: ./api/dist/
if-no-files-found: error
run-test-linux-binary-artifact:
name: Run and test linux artifact
needs: build-artifacts
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: lts/*
- name: Run mock Keycloak
id: idp-run
working-directory: test/api/mock-keycloak
run: |
python3 -m http.server 8080 &
- name: Run MySQL container
id: mysql-run
run: |
docker run -d --name stig-manager-db \
-p 3306:3306 \
-e MYSQL_ROOT_PASSWORD=rootpw \
-e MYSQL_DATABASE=stigman \
-e MYSQL_USER=stigman \
-e MYSQL_PASSWORD=stigman \
mysql:8.0.24
- name: wait 10 seconds
run: sleep 10
- name: Download builds
uses: actions/download-artifact@v4
with:
name: binary-artifacts
path: ./binary-artifacts
- name: Set execute permissions on binary
run: chmod +x ./binary-artifacts/stig-manager-linuxstatic
- name: Run linux binary and log output
working-directory: ./
run: |
mkdir -p ./binary-artifacts/logs
echo "Running tests on binary artifacts"
./binary-artifacts/stig-manager-linuxstatic > ./binary-artifacts/logs/output.log 2>&1 &
echo $! > binary-artifacts/stig-manager.pid
- name: Wait for bootstrap
run: for i in {1..10}; do [ $i -gt 1 ] && sleep 5; curl --output /dev/null --silent --fail http://localhost:64001/api/op/configuration && s=0 && break || s=$?; printf '.'; done; (exit $s)
- name: Install test dependencies
run: npm ci
working-directory: ./test/api/
- name: Install utils test dependencies
run: npm ci
working-directory: ./test/utils/
- name: Run tests with coverage and log output
working-directory: ./test/api/
run: |
set -o pipefail
npm test 2>&1 | tee ../../binary-artifacts/logs/test-output.log
- name: Stop linux binary
if: always()
run: |
if [ -f binary-artifacts/stig-manager.pid ]; then
kill $(cat binary-artifacts/stig-manager.pid) || true
fi
- name: Upload logs
if: always()
uses: actions/upload-artifact@v4
with:
name: test-logs
path: ./binary-artifacts/logs/
================================================
FILE: .github/workflows/api-container-tests.yml
================================================
name: API containers
on:
workflow_dispatch:
pull_request:
branches:
- main
paths:
- "api/source/**"
- "test/api/**"
- "Dockerfile"
- ".github/workflows/api-container-tests.yml"
jobs:
fetch-mysql-versions:
runs-on: ubuntu-latest
outputs:
MYSQL_VERSIONS: ${{ steps.fetch-versions.outputs.version_array }}
steps:
- name: Fetch MySQL Versions
id: fetch-versions
run: |
# Fetch latest 3 MySQL 8.0.x versions plus 8.0.24
MYSQL_8_0=$(curl -s "https://registry.hub.docker.com/v2/repositories/library/mysql/tags/?page_size=100" | jq -r '.results[].name | select(test("^8\\.0\\.\\d+$"))' | sort -V | tail -n2 | cat <(echo "8.0.24") - | sort -V | uniq)
# Fetch latest 2 MySQL 8.4.x versions
MYSQL_8_4=$(curl -s "https://registry.hub.docker.com/v2/repositories/library/mysql/tags/?page_size=100" | jq -r '.results[].name | select(test("^8\\.4\\.\\d+$"))' | sort -V | tail -n2)
# Combine both version lists into JSON array
VERSIONS=$(echo "$MYSQL_8_0" "$MYSQL_8_4" | tr ' ' '\n' | jq -Rnc '[inputs]')
echo "version_array=$VERSIONS" >> $GITHUB_OUTPUT
test_api:
needs: fetch-mysql-versions
name: ${{ matrix.container.name }} and MySQL ${{ matrix.mysql_version }}
runs-on: ubuntu-latest
strategy:
matrix:
container:
- name: "stig-manager-alpine"
build_arg: "node:lts-alpine"
mysql_version: ${{fromJson(needs.fetch-mysql-versions.outputs.MYSQL_VERSIONS)}}
steps:
- name: Check out the repo
uses: actions/checkout@v4
- name: Build image for ${{ matrix.container.name }}
id: image-build
run: |
docker build -t ${{ matrix.container.name }} --build-arg BASE_IMAGE=${{ matrix.container.build_arg }} .
- name: Run mock Keycloak
id: id-run
working-directory: ./test/api/mock-keycloak
run: |
python3 -m http.server 8080 &
- name: Run MySQL container version ${{ matrix.mysql_version }}
id: mysql-run
run: |
docker run -d --name stig-manager-db \
-p 3306:3306 \
-e MYSQL_ROOT_PASSWORD=rootpw \
-e MYSQL_DATABASE=stigman \
-e MYSQL_USER=stigman \
-e MYSQL_PASSWORD=stigman \
mysql:${{ matrix.mysql_version }}
- name: Run STIG Manager container ${{ matrix.container.name }}
id: api-run
run: |
docker run -d --name stig-manager-api \
--net=host \
-e STIGMAN_API_PORT=64001 \
-e STIGMAN_DB_HOST=localhost \
-e STIGMAN_DB_PORT=3306 \
-e STIGMAN_DB_PASSWORD=stigman \
-e STIGMAN_API_AUTHORITY=http://127.0.0.1:8080/auth/realms/stigman \
-e STIGMAN_DEV_RESPONSE_VALIDATION=logOnly \
-e STIGMAN_EXPERIMENTAL_APPDATA=true \
-e STIGMAN_DEV_ALLOW_INSECURE_TOKENS=true \
${{ matrix.container.name }}
- name: Install test dependencies
run: npm ci
working-directory: ./test/api/
- name: Install utils test dependencies
run: npm ci
working-directory: ./test/utils/
- name: Wait for bootstrap
run: for i in {1..10}; do [ $i -gt 1 ] && sleep 5; curl --output /dev/null --silent --fail http://localhost:64001/api/op/configuration && s=0 && break || s=$?; printf '.'; done; (exit $s)
- name: Run tests with coverage
working-directory: ./test/api/
run: npm test
- name: Upload mocha test report
id: artifact-upload-mocha
uses: actions/upload-artifact@v4
if: ${{ always() }}
with:
name: mocha-report-${{ matrix.container.name }}-${{ matrix.mysql_version }}
path: ./test/api/mochawesome-report
- name: Extract API container log
id: api-log-extract
if: ${{ always() }}
working-directory: ./test/api
run: |
docker logs stig-manager-api > api-log-${{ matrix.container.name }}-${{ matrix.mysql_version }}-${{ github.run_id }}.json
- name: Upload API log artifact
uses: actions/upload-artifact@v4
id: api-log-upload
if: ${{ always() }}
with:
name: api-log-${{ matrix.container.name }}-${{ matrix.mysql_version }}-${{ github.run_id }}
path: ./test/api/api-log-${{ matrix.container.name }}-${{ matrix.mysql_version }}-${{ github.run_id }}.json
- name: Collect all container logs on failure
if: ${{ cancelled() || failure() }}
uses: jwalton/gh-docker-logs@54a2a89cd6a2c929525f26ca67a7a4857a5dc1d9 # pin@v1
with:
dest: "./logs-${{ matrix.container.name }}-${{ matrix.mysql_version }}"
- name: Tar container logs
if: ${{ cancelled() || failure() }}
run: tar cvzf ./logs-${{ matrix.container.name }}-${{ matrix.mysql_version }}.tgz ./logs-${{ matrix.container.name }}-${{ matrix.mysql_version }}
- name: Upload container logs artifact
if: ${{ cancelled() || failure() }}
uses: actions/upload-artifact@v4
with:
name: logs-${{ matrix.container.name }}-${{ matrix.mysql_version }}.tgz
path: ./logs-${{ matrix.container.name }}-${{ matrix.mysql_version }}.tgz
================================================
FILE: .github/workflows/api-spec-validation.yml
================================================
name: API spec validation
on:
workflow_dispatch:
pull_request:
branches:
- main
paths:
- "api/source/specification/**"
- ".github/workflows/api-spec-validation.yml"
push:
branches:
- main
paths:
- "api/source/specification/**"
- ".github/workflows/api-spec-validation.yml"
jobs:
validate_asyncapi:
name: Validate AsyncAPI specs
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: lts/*
- name: Validate log-socket.yaml
run: npx --yes @asyncapi/cli@2 validate api/source/specification/log-socket.yaml
================================================
FILE: .github/workflows/api-state-tests.yml
================================================
name: API state tests
on:
workflow_dispatch:
pull_request:
branches:
- main
paths:
- "api/source/**"
- "test/state/**"
- ".github/workflows/api-state-tests.yml"
jobs:
api-state-tests:
name: state tests
runs-on: ubuntu-latest
strategy:
matrix:
component: ["bootstrap", "db", "jwks", "oidc", "tokenValidation"]
steps:
- name: Check out the repo
uses: actions/checkout@v4
- name: Install api libraries
working-directory: ./api/source
run: npm ci
- name: Install Test dependencies
working-directory: ./test/state
run: npm ci
- name: Install Test utils dependencies
working-directory: ./test/utils
run: npm ci
- name: Run tests
working-directory: ./test/state
run: npx mocha --reporter mochawesome --showFailed --exit './mocha/${{ matrix.component}}.test.js'
- name: Upload mocha test report
uses: actions/upload-artifact@v4
if: ${{ always() }}
with:
name: mocha-report-${{ matrix.component}}
path: ./test/state/mochawesome-report
================================================
FILE: .github/workflows/build-binary-artifacts.yml
================================================
name: Build Binary Artifacts and Sign
on:
workflow_dispatch:
push:
branches:
- main
paths:
- 'api/source/**'
- 'client/src/**'
- 'client/build.sh'
- 'docs/**'
- '.github/workflows/build-client.yml'
- '.github/workflows/build-docs.yml'
- '.github/workflows/build-binary-artifacts.yml'
tags:
- 1.**
jobs:
build-binary-artifacts-and-sign:
name: Build binary artifacts, sign, export
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
with:
ref: main
fetch-depth: 0
- name: Get repository metadata
id: repo
uses: actions/github-script@v7
with:
script: |
const repo = await github.rest.repos.get(context.repo)
return repo.data
- name: install uglify
run: |
sudo npm install -g uglify-js
- name: run build script
id: run-the-build-script
working-directory: ./api
run: ./build.sh
- name: Import GPG Key
id: import_gpg
run: |
if ! echo "${{ secrets.STIGMAN_PRIVATE_KEY }}" | gpg --import; then
echo "::warning ::Private key GPG Import failed"
exit 1
fi
- name: Get latest tag
id: get_tag
run: |
DESCRIBE=$(git describe --tags | sed 's/\(.*\)-.*/\1/')
echo "tag=$DESCRIBE" >> $GITHUB_ENV
- name: Sign Dist Artifacts
id: sign_artifacts
working-directory: ./api/dist
run: |
if ! gpg --default-key nuwcdivnpt-bot@users.noreply.github.com --armor --detach-sig ./stig-manager-linux-${{ env.tag }}.tar.xz; then
echo "::warning ::Linux Signing failed"
exit 1
fi
if ! gpg --default-key nuwcdivnpt-bot@users.noreply.github.com --armor --detach-sig ./stig-manager-win-${{ env.tag }}.zip; then
echo "::warning ::Windows Signing failed"
exit 1
fi
- name: Verify Signatures
id: verify_signatures
working-directory: ./api/dist
run: |
if ! gpg --verify stig-manager-linux-${{ env.tag }}.tar.xz.asc stig-manager-linux-${{ env.tag }}.tar.xz; then
echo "::warning ::Signature verification for Linux failed"
exit 1
fi
if ! gpg --verify stig-manager-win-${{ env.tag }}.zip.asc stig-manager-win-${{ env.tag }}.zip; then
echo "::warning ::Signature verification for Windows failed"
exit 1
fi
- name: Upload builds
if: always()
uses: actions/upload-artifact@v4
with:
name: binary-artifacts
path: ./api/bin/
if-no-files-found: error
- name: Upload archives
if: always()
uses: actions/upload-artifact@v4
with:
name: binary-archives
path: ./api/dist/
if-no-files-found: error
================================================
FILE: .github/workflows/build-client.yml
================================================
name: Build client
on:
workflow_dispatch:
workflow_call:
jobs:
builder:
name: builder
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
with:
ref: ${{ github.ref }}
- name: Install uglify-js
run: npm install -g uglify-js
- name: Create distribution
working-directory: ./client
run: ./build.sh
- name: Upload distribution
uses: actions/upload-artifact@v4
with:
name: client-dist
path: ./client/dist
================================================
FILE: .github/workflows/build-docs.yml
================================================
name: Build docs
on:
workflow_dispatch:
workflow_call:
jobs:
builder:
name: builder
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
with:
ref: ${{ github.ref }}
- name: run image, generating docs
working-directory: ./docs
run: ./build.sh
- name: Upload docs
uses: actions/upload-artifact@v4
with:
name: docs-build
path: ./docs/_build/html
================================================
FILE: .github/workflows/client-sonarcloud.yml
================================================
name: Client SonarCloud
on:
workflow_dispatch:
pull_request:
branches:
- main
paths:
- "client/src/js/**"
- "client/src/css/**"
- "client/src/serviceWorker.js"
- ".github/workflows/client-sonarcloud.yml"
push:
branches:
- main
paths:
- "client/src/js/**"
- "client/src/css/**"
- "client/src/serviceWorker.js"
- ".github/workflows/client-sonarcloud.yml"
permissions:
pull-requests: read # allows SonarCloud to decorate PRs with analysis results
jobs:
SonarCloudAnalysis-Client:
name: SonarCloud Analysis client
runs-on: ubuntu-latest
steps:
- name: Check if PR is from a fork
id: check_fork
run: |
if [ "${{ github.event.pull_request.head.repo.fork }}" == "true" ]; then
echo "This is a PR from a fork, skipping sonarcloud analysis."
echo "SKIP_STEP=true" >> $GITHUB_ENV
fi
#checkout the repo
- name: Checkout repository
if: env.SKIP_STEP != 'true'
uses: actions/checkout@v4
with:
fetch-depth: 0 # Important to fetch all history for accurate blame information
- name: Analyze client with SonarCloud
if: env.SKIP_STEP != 'true'
uses: SonarSource/sonarqube-scan-action@v6.0.0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN_CLIENT }} # Needed to push to SonarCloud
with:
projectBaseDir: ./client/src
# Additional arguments for the sonarcloud scanner
args: -Dsonar.projectKey=nuwcdivnpt_stig-manager-client
-Dsonar.projectName=nuwcdivnpt_stig-manager-client
-Dsonar.organization=nuwcdivnpt
-Dsonar.inclusions=**/*.js,**/*.html,**/*.css
-Dsonar.exclusions=**/node_modules/**
# This will fail the action if Quality Gate fails (leaving out for now )
# - name: Check Quality Gate
# uses: sonarsource/sonarqube-quality-gate-action@master
# env:
# SONAR_TOKEN:
================================================
FILE: .github/workflows/pub-docker.yml
================================================
name: Publish Docker images
env:
DOCKERHUB_REPOSITORY: nuwcdivnpt/stig-manager
on:
workflow_dispatch:
push:
branches:
- main
paths:
- 'api/source/**'
- 'client/src/**'
- 'client/build.sh'
- 'docs/**'
- 'Dockerfile'
- '.github/workflows/build-client.yml'
- '.github/workflows/build-docs.yml'
- '.github/workflows/pub-docker.yml'
tags:
- 1.**
jobs:
build-client:
uses: nuwcdivnpt/stig-manager/.github/workflows/build-client.yml@main
build-docs:
uses: nuwcdivnpt/stig-manager/.github/workflows/build-docs.yml@main
build-push-alpine:
name: Build and push from Alpine base
needs:
- build-client
- build-docs
runs-on: ubuntu-latest
steps:
- name: Check out the repo
uses: actions/checkout@v4
with:
ref: main
fetch-depth: 0
- name: Download client distribution
uses: actions/download-artifact@v4
with:
name: client-dist
path: ./client/dist
- name: Download documentation
uses: actions/download-artifact@v4
with:
name: docs-build
path: ./docs/_build/html
- name: Get repository metadata
id: repo
uses: actions/github-script@v7
with:
script: |
const repo = await github.rest.repos.get(context.repo)
return repo.data
- name: Prepare variables
id: prep
run: |
DOCKER_IMAGE=${{ env.DOCKERHUB_REPOSITORY }}
BRANCH=$(git symbolic-ref --short HEAD)
SHA=$(git rev-parse --short=10 HEAD)
DESCRIBE=$(git describe --tags)
TAG=$(git describe --tags --abbrev=0)
TAGS=${DOCKER_IMAGE}:latest
[[ ${{ github.ref_type }} == "tag" ]] && TAGS="$TAGS,${DOCKER_IMAGE}:${{ github.ref_name }}"
[[ ${{ github.event_name }} == "workflow_dispatch" && ${{ github.ref_name }} != "main" ]] && TAGS="${DOCKER_IMAGE}:${{ github.ref_name }}"
echo "version=${TAG}" >> $GITHUB_OUTPUT
echo "sha=${SHA}" >> $GITHUB_OUTPUT
echo "tag=${TAG}" >> $GITHUB_OUTPUT
echo "branch=${BRANCH}" >> $GITHUB_OUTPUT
echo "tags=${TAGS}" >> $GITHUB_OUTPUT
echo "describe=${DESCRIBE}" >> $GITHUB_OUTPUT
echo "created=$(date -u +'%Y-%m-%dT%H:%M:%SZ')" >> $GITHUB_OUTPUT
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@4b4e9c3e2d4531116a6f8ba8e71fc6e2cb6e6c8c # pin@v2
- name: Login to DockerHub
uses: docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a # pin@v2
with:
username: ${{ secrets.DOCKERHUB_ORG_OWNER_USERNAME }}
password: ${{ secrets.DOCKERHUB_ORG_OWNER_PW }}
- name: Build and push
id: docker_build
uses: docker/build-push-action@1104d471370f9806843c095c1db02b5a90c5f8b6 # pin@v3
with:
context: .
platforms: linux/amd64,linux/arm64
file: ./Dockerfile
push: true
build-args: |
COMMIT_BRANCH=${{ steps.prep.outputs.branch }}
COMMIT_SHA=${{ steps.prep.outputs.sha }}
COMMIT_TAG=${{ steps.prep.outputs.tag }}
COMMIT_DESCRIBE=${{ steps.prep.outputs.describe }}
tags: ${{ steps.prep.outputs.tags }}
labels: |
org.opencontainers.image.title=${{ fromJson(steps.repo.outputs.result).name }}
org.opencontainers.image.description=${{ fromJson(steps.repo.outputs.result).description }}
org.opencontainers.image.url=${{ fromJson(steps.repo.outputs.result).html_url }}
org.opencontainers.image.source=${{ fromJson(steps.repo.outputs.result).clone_url }}
org.opencontainers.image.version=${{ steps.prep.outputs.version }}
org.opencontainers.image.created=${{ steps.prep.outputs.created }}
org.opencontainers.image.revision=${{ steps.prep.outputs.describe }}
org.opencontainers.image.licenses=${{ fromJson(steps.repo.outputs.result).license.spdx_id }}
- name: Image digest
run: echo ${{ steps.docker_build.outputs.digest }}
- name: Update Docker Hub Description
if: github.event_name != 'workflow_dispatch'
uses: peter-evans/dockerhub-description@202973a37c8a723405c0c5f0a71b6d99db470dae # pin@v3
with:
username: ${{ secrets.DOCKERHUB_ORG_OWNER_USERNAME }}
password: ${{ secrets.DOCKERHUB_ORG_OWNER_PW }}
repository: ${{ env.DOCKERHUB_REPOSITORY }}
short-description: An API and Web client for managing STIG assessments.
readme-filepath: ./docs/the-project/DockerHub_Readme.md
================================================
FILE: .github/workflows/unit-tests.yml
================================================
name: Unit tests
on:
workflow_dispatch:
pull_request:
branches:
- main
paths:
- "api/source/**"
- "test/unit/**"
- ".github/workflows/unit-tests.yml"
push:
branches:
- main
paths:
- "api/source/**"
- "test/unit/**"
- ".github/workflows/unit-tests.yml"
jobs:
unit-tests:
name: Run unit tests
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: lts/*
- name: Install API dependencies
run: npm ci
working-directory: ./api/source/
- name: Install test dependencies
run: npm ci
working-directory: ./test/unit/
- name: Run unit tests
working-directory: ./test/unit/
run: npm test
================================================
FILE: .readthedocs.yml
================================================
# .readthedocs.yml
# Read the Docs configuration file
# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
# Required
version: 2
# Set the OS, Python version and other tools you might need
build:
os: ubuntu-22.04
tools:
python: "3.12"
# Build documentation in the docs/ directory with Sphinx
sphinx:
configuration: docs/conf.py
# Optionally build your docs in additional formats such as PDF
# formats:
# - pdf
# Optionally set the version of Python and requirements required to build your docs
python:
install:
- requirements: docs/requirements.txt
================================================
FILE: CONTRIBUTING.md
================================================
# Contributing to STIG Manager
**NOTE: This CONTRIBUTING.md describes our software contribution policy. You do not need to follow the Developer's Certificate of Origin (DCO) process for commenting on the STIG Manager repository documentation, such as CONTRIBUTING.md, INTENT.md, etc. or for submitting issues. For more information about developing and contributing to the project, please see the [STIG Manager Contribution Guide](https://stig-manager.readthedocs.io/en/latest/the-project/contributing.html) that is part of our [overall documentation](https://stig-manager.readthedocs.io/en/latest/index.html)**
## Policy
### 1. Introduction
The project maintainer for this Project will only accept contributions using the Developer's Certificate of Origin 1.1 located at [developercertificate.org](https://developercertificate.org) ("DCO"). The DCO is a legally binding statement asserting that you are the creator of your contribution, or that you otherwise have the authority to distribute the contribution, and that you are intentionally making the contribution available under the license associated with the Project ("License").
### 2. Developer Certificate of Origin Process
Before submitting contributing code to this repository for the first time, you'll need to sign a Developer Certificate of Origin (DCO) (see below). To agree to the DCO, add your name and email address to the [CONTRIBUTORS.md](CONTRIBUTORS.md) file. At a high level, adding your information to this file tells us that you have the right to submit the work you're contributing and indicates that you consent to our treating the contribution in a way consistent with the license associated with this software (as described in [LICENSE.md](LICENSE.md)) and its documentation ("Project").
### 3. Important Points
Pseudonymous or anonymous contributions are permissible, but you must be reachable at the email address provided in the Signed-off-by line.
If your contribution is significant, you are also welcome to add your name and copyright date to the source file header.
U.S. Federal law prevents the government from accepting gratuitous services unless certain conditions are met. By submitting a pull request, you acknowledge that your services are offered without expectation of payment and that you expressly waive any future pay claims against the U.S. Federal government related to your contribution.
If you are a U.S. Federal government employee and use a `*.mil` or `*.gov` email address, we interpret your Signed-off-by to mean that the contribution was created in whole or in part by you and that your contribution is not subject to copyright protections.
### 4. DCO Text
The full text of the DCO is included below and is available online at [developercertificate.org](https://developercertificate.org):
```txt
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
```
================================================
FILE: CONTRIBUTORS.md
================================================
# Contributors
**By adding your name, email address, and copyright date below, you understand and agree to the terms of the [Developer's Certificate of Origin](https://developercertificate.org/) (DCO) version 1.1, and you are submitting all contributions you make to this Project pursuant to the terms described in [LICENSE.md](LICENSE.md).**
## Signed-off-by
- Copyright 2020-2026 U.S. Federal Government (in countries where recognized)
- Copyright 2020-2026 Carl Smigielski, carl.a.smigielski@saic.com
- Copyright 2020-2026 Christopher Daley, cdaley@rite-solutions.com
- Copyright 2023-2026 Mathew Ferreira, mferreira@rite-solutions.com
- Copyright 2021 Russell Johnson, russell.d.johnson@saic.com
- Copyright 2024 Rajesh Shrestha, rshrestha@rite-solutions.com
- Copyright 2024 David Whalen, david.whalen@usmc.mil
- Copyright 2025 Christian Rodriguez, christian.a.rodriguez@mantech.com
- _Add the copyright date, your name, and email address here. (PLEASE KEEP THIS LINE)_
## Note for U.S. Federal Employees
If you're a U.S. Federal Government employee and use a `*.mil` or `*.gov` email address to agree to the DCO, we interpret your signed DCO to mean that the contribution was created in whole or in part by you as part of your job with the U.S. Federal Government and that your contribution is not subject to copyright protections.
================================================
FILE: Dockerfile
================================================
# STIG Manager OSS
#
# COPY commands assume the following lines in .dockerignore
# **/node_modules
# **/state.json
# **/README.md
# **/.git
# **/.gitignore
# **/data
# **/docs
# **/test
# **/uploads
# **/docker
ARG BASE_IMAGE="node:lts-alpine"
FROM ${BASE_IMAGE}
LABEL maintainer="carl.a.smigielski@saic.com"
ARG COMMIT_BRANCH=""
ARG COMMIT_SHA=""
ARG COMMIT_TAG=""
ARG COMMIT_DESCRIBE=""
LABEL commit-branch=${COMMIT_BRANCH}
LABEL commit-sha=${COMMIT_SHA}
LABEL commit-tag=${COMMIT_TAG}
LABEL commit-describe=${COMMIT_DESCRIBE}
WORKDIR /home/node
USER node
# Install app dependencies
COPY --chown=node:node ./api/source .
RUN npm ci
RUN mkdir client
# Requires the client build files. Alternatively, copy ./client/src
COPY --chown=node:node ./client/dist ./client
RUN mkdir docs
COPY --chown=node:node ./docs/_build/html ./docs
# Ensure sticky bit is set on all world-writable directories (fixes tenable 1000749)
USER root
RUN df -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -type d -perm -0002 2>/dev/null | xargs chmod a+t 2>/dev/null | echo 'tenable 1000749'
USER node
# Set environment
ENV COMMIT_SHA=${COMMIT_SHA} \
COMMIT_BRANCH=${COMMIT_BRANCH} \
COMMIT_TAG=${COMMIT_TAG} \
COMMIT_DESCRIBE=${COMMIT_DESCRIBE} \
STIGMAN_CLIENT_DIRECTORY=./client \
STIGMAN_DOCS_DIRECTORY=./docs
EXPOSE 54000
CMD [ "node", "index.js" ]
================================================
FILE: INTENT.md
================================================
# Licensing Intent
The intent is that this software and documentation ("Project") should be treated as if it is licensed under the license associated with the Project ("License") in the LICENSE.md file. However, because we are part of the United States (U.S.) Federal Government, it is not that simple.
The portions of this Project written by United States (U.S.) Federal government employees within the scope of their federal employment are ineligible for copyright protection in the U.S.; this is generally understood to mean that these portions of the Project are placed in the public domain.
In countries where copyright protection is available (which does not include the U.S.), contributions made by U.S. Federal government employees are released under the License. Merged contributions from private contributors are released under the License.
================================================
FILE: LICENSE.md
================================================
---
*For all code except the STIG Manager client*
---
## MIT License
```
Copyright (c) 2020-2026 U.S. Federal Government (in countries where recognized)
Copyright (c) 2020-2026 Science Applications International Corporation
Copyright (c) 2020-2026 Rite-Solutions, An Arcfield Company
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
```
---
*For the STIG Manager client, which uses the ExtJS 3.4 JavaScript framework licensed under the GNU General Public License*
---
## GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 [Free Software Foundation, Inc.](http://fsf.org/)
Everyone is permitted to copy and distribute verbatim copies of this license
document, but changing it is not allowed.
## Preamble
The GNU General Public License is a free, copyleft license for software and
other kinds of works.
The licenses for most software and other practical works are designed to take
away your freedom to share and change the works. By contrast, the GNU General
Public License is intended to guarantee your freedom to share and change all
versions of a program--to make sure it remains free software for all its users.
We, the Free Software Foundation, use the GNU General Public License for most
of our software; it applies also to any other work released this way by its
authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our
General Public Licenses are designed to make sure that you have the freedom to
distribute copies of free software (and charge for them if you wish), that you
receive source code or can get it if you want it, that you can change the
software or use pieces of it in new free programs, and that you know you can do
these things.
To protect your rights, we need to prevent others from denying you these rights
or asking you to surrender the rights. Therefore, you have certain
responsibilities if you distribute copies of the software, or if you modify it:
responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for
a fee, you must pass on to the recipients the same freedoms that you received.
You must make sure that they, too, receive or can get the source code. And you
must show them these terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps:
1. assert copyright on the software, and
2. offer you this License giving you legal permission to copy, distribute
and/or modify it.
For the developers' and authors' protection, the GPL clearly explains that
there is no warranty for this free software. For both users' and authors' sake,
the GPL requires that modified versions be marked as changed, so that their
problems will not be attributed erroneously to authors of previous versions.
Some devices are designed to deny users access to install or run modified
versions of the software inside them, although the manufacturer can do so. This
is fundamentally incompatible with the aim of protecting users' freedom to
change the software. The systematic pattern of such abuse occurs in the area of
products for individuals to use, which is precisely where it is most
unacceptable. Therefore, we have designed this version of the GPL to prohibit
the practice for those products. If such problems arise substantially in other
domains, we stand ready to extend this provision to those domains in future
versions of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents. States
should not allow patents to restrict development and use of software on
general-purpose computers, but in those that do, we wish to avoid the special
danger that patents applied to a free program could make it effectively
proprietary. To prevent this, the GPL assures that patents cannot be used to
render the program non-free.
The precise terms and conditions for copying, distribution and modification
follow.
## TERMS AND CONDITIONS
### 0. Definitions.
*This License* refers to version 3 of the GNU General Public License.
*Copyright* also means copyright-like laws that apply to other kinds of works,
such as semiconductor masks.
*The Program* refers to any copyrightable work licensed under this License.
Each licensee is addressed as *you*. *Licensees* and *recipients* may be
individuals or organizations.
To *modify* a work means to copy from or adapt all or part of the work in a
fashion requiring copyright permission, other than the making of an exact copy.
The resulting work is called a *modified version* of the earlier work or a work
*based on* the earlier work.
A *covered work* means either the unmodified Program or a work based on the
Program.
To *propagate* a work means to do anything with it that, without permission,
would make you directly or secondarily liable for infringement under applicable
copyright law, except executing it on a computer or modifying a private copy.
Propagation includes copying, distribution (with or without modification),
making available to the public, and in some countries other activities as well.
To *convey* a work means any kind of propagation that enables other parties to
make or receive copies. Mere interaction with a user through a computer
network, with no transfer of a copy, is not conveying.
An interactive user interface displays *Appropriate Legal Notices* to the
extent that it includes a convenient and prominently visible feature that
1. displays an appropriate copyright notice, and
2. tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the work
under this License, and how to view a copy of this License.
If the interface presents a list of user commands or options, such as a menu, a
prominent item in the list meets this criterion.
### 1. Source Code.
The *source code* for a work means the preferred form of the work for making
modifications to it. *Object code* means any non-source form of a work.
A *Standard Interface* means an interface that either is an official standard
defined by a recognized standards body, or, in the case of interfaces specified
for a particular programming language, one that is widely used among developers
working in that language.
The *System Libraries* of an executable work include anything, other than the
work as a whole, that (a) is included in the normal form of packaging a Major
Component, but which is not part of that Major Component, and (b) serves only
to enable use of the work with that Major Component, or to implement a Standard
Interface for which an implementation is available to the public in source code
form. A *Major Component*, in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system (if any) on
which the executable work runs, or a compiler used to produce the work, or an
object code interpreter used to run it.
The *Corresponding Source* for a work in object code form means all the source
code needed to generate, install, and (for an executable work) run the object
code and to modify the work, including scripts to control those activities.
However, it does not include the work's System Libraries, or general-purpose
tools or generally available free programs which are used unmodified in
performing those activities but which are not part of the work. For example,
Corresponding Source includes interface definition files associated with source
files for the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require, such as
by intimate data communication or control flow between those subprograms and
other parts of the work.
The Corresponding Source need not include anything that users can regenerate
automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
### 2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on
the Program, and are irrevocable provided the stated conditions are met. This
License explicitly affirms your unlimited permission to run the unmodified
Program. The output from running a covered work is covered by this License only
if the output, given its content, constitutes a covered work. This License
acknowledges your rights of fair use or other equivalent, as provided by
copyright law.
You may make, run and propagate covered works that you do not convey, without
conditions so long as your license otherwise remains in force. You may convey
covered works to others for the sole purpose of having them make modifications
exclusively for you, or provide you with facilities for running those works,
provided that you comply with the terms of this License in conveying all
material for which you do not control copyright. Those thus making or running
the covered works for you must do so exclusively on your behalf, under your
direction and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the
conditions stated below. Sublicensing is not allowed; section 10 makes it
unnecessary.
### 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure
under any applicable law fulfilling obligations under article 11 of the WIPO
copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention is
effected by exercising rights under this License with respect to the covered
work, and you disclaim any intention to limit operation or modification of the
work as a means of enforcing, against the work's users, your or third parties'
legal rights to forbid circumvention of technological measures.
### 4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it,
in any medium, provided that you conspicuously and appropriately publish on
each copy an appropriate copyright notice; keep intact all notices stating that
this License and any non-permissive terms added in accord with section 7 apply
to the code; keep intact all notices of the absence of any warranty; and give
all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may
offer support or warranty protection for a fee.
### 5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it
from the Program, in the form of source code under the terms of section 4,
provided that you also meet all of these conditions:
- a) The work must carry prominent notices stating that you modified it, and
giving a relevant date.
- b) The work must carry prominent notices stating that it is released under
this License and any conditions added under section 7. This requirement
modifies the requirement in section 4 to *keep intact all notices*.
- c) You must license the entire work, as a whole, under this License to
anyone who comes into possession of a copy. This License will therefore
apply, along with any applicable section 7 additional terms, to the whole
of the work, and all its parts, regardless of how they are packaged. This
License gives no permission to license the work in any other way, but it
does not invalidate such permission if you have separately received it.
- d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your work need
not make them do so.
A compilation of a covered work with other separate and independent works,
which are not by their nature extensions of the covered work, and which are not
combined with it such as to form a larger program, in or on a volume of a
storage or distribution medium, is called an *aggregate* if the compilation and
its resulting copyright are not used to limit the access or legal rights of the
compilation's users beyond what the individual works permit. Inclusion of a
covered work in an aggregate does not cause this License to apply to the other
parts of the aggregate.
### 6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4
and 5, provided that you also convey the machine-readable Corresponding Source
under the terms of this License, in one of these ways:
- a) Convey the object code in, or embodied in, a physical product (including
a physical distribution medium), accompanied by the Corresponding Source
fixed on a durable physical medium customarily used for software
interchange.
- b) Convey the object code in, or embodied in, a physical product (including
a physical distribution medium), accompanied by a written offer, valid for
at least three years and valid for as long as you offer spare parts or
customer support for that product model, to give anyone who possesses the
object code either
1. a copy of the Corresponding Source for all the software in the product
that is covered by this License, on a durable physical medium
customarily used for software interchange, for a price no more than your
reasonable cost of physically performing this conveying of source, or
2. access to copy the Corresponding Source from a network server at no
charge.
- c) Convey individual copies of the object code with a copy of the written
offer to provide the Corresponding Source. This alternative is allowed only
occasionally and noncommercially, and only if you received the object code
with such an offer, in accord with subsection 6b.
- d) Convey the object code by offering access from a designated place
(gratis or for a charge), and offer equivalent access to the Corresponding
Source in the same way through the same place at no further charge. You
need not require recipients to copy the Corresponding Source along with the
object code. If the place to copy the object code is a network server, the
Corresponding Source may be on a different server operated by you or a
third party) that supports equivalent copying facilities, provided you
maintain clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the Corresponding
Source, you remain obligated to ensure that it is available for as long as
needed to satisfy these requirements.
- e) Convey the object code using peer-to-peer transmission, provided you
inform other peers where the object code and Corresponding Source of the
work are being offered to the general public at no charge under subsection
6d.
A separable portion of the object code, whose source code is excluded from the
Corresponding Source as a System Library, need not be included in conveying the
object code work.
A *User Product* is either
1. a *consumer product*, which means any tangible personal property which is
normally used for personal, family, or household purposes, or
2. anything designed or sold for incorporation into a dwelling.
In determining whether a product is a consumer product, doubtful cases shall be
resolved in favor of coverage. For a particular product received by a
particular user, *normally used* refers to a typical or common use of that
class of product, regardless of the status of the particular user or of the way
in which the particular user actually uses, or expects or is expected to use,
the product. A product is a consumer product regardless of whether the product
has substantial commercial, industrial or non-consumer uses, unless such uses
represent the only significant mode of use of the product.
*Installation Information* for a User Product means any methods, procedures,
authorization keys, or other information required to install and execute
modified versions of a covered work in that User Product from a modified
version of its Corresponding Source. The information must suffice to ensure
that the continued functioning of the modified object code is in no case
prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as part of a
transaction in which the right of possession and use of the User Product is
transferred to the recipient in perpetuity or for a fixed term (regardless of
how the transaction is characterized), the Corresponding Source conveyed under
this section must be accompanied by the Installation Information. But this
requirement does not apply if neither you nor any third party retains the
ability to install modified object code on the User Product (for example, the
work has been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates for a
work that has been modified or installed by the recipient, or for the User
Product in which it has been modified or installed. Access to a network may be
denied when the modification itself materially and adversely affects the
operation of the network or violates the rules and protocols for communication
across the network.
Corresponding Source conveyed, and Installation Information provided, in accord
with this section must be in a format that is publicly documented (and with an
implementation available to the public in source code form), and must require
no special password or key for unpacking, reading or copying.
### 7. Additional Terms.
*Additional permissions* are terms that supplement the terms of this License by
making exceptions from one or more of its conditions. Additional permissions
that are applicable to the entire Program shall be treated as though they were
included in this License, to the extent that they are valid under applicable
law. If additional permissions apply only to part of the Program, that part may
be used separately under those permissions, but the entire Program remains
governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any
additional permissions from that copy, or from any part of it. (Additional
permissions may be written to require their own removal in certain cases when
you modify the work.) You may place additional permissions on material, added
by you to a covered work, for which you have or can give appropriate copyright
permission.
Notwithstanding any other provision of this License, for material you add to a
covered work, you may (if authorized by the copyright holders of that material)
supplement the terms of this License with terms:
- a) Disclaiming warranty or limiting liability differently from the terms of
sections 15 and 16 of this License; or
- b) Requiring preservation of specified reasonable legal notices or author
attributions in that material or in the Appropriate Legal Notices displayed
by works containing it; or
- c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in reasonable
ways as different from the original version; or
- d) Limiting the use for publicity purposes of names of licensors or authors
of the material; or
- e) Declining to grant rights under trademark law for use of some trade
names, trademarks, or service marks; or
- f) Requiring indemnification of licensors and authors of that material by
anyone who conveys the material (or modified versions of it) with
contractual assumptions of liability to the recipient, for any liability
that these contractual assumptions directly impose on those licensors and
authors.
All other non-permissive additional terms are considered *further restrictions*
within the meaning of section 10. If the Program as you received it, or any
part of it, contains a notice stating that it is governed by this License along
with a term that is a further restriction, you may remove that term. If a
license document contains a further restriction but permits relicensing or
conveying under this License, you may add to a covered work material governed
by the terms of that license document, provided that the further restriction
does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place,
in the relevant source files, a statement of the additional terms that apply to
those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a
separately written license, or stated as exceptions; the above requirements
apply either way.
### 8. Termination.
You may not propagate or modify a covered work except as expressly provided
under this License. Any attempt otherwise to propagate or modify it is void,
and will automatically terminate your rights under this License (including any
patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a
particular copyright holder is reinstated
- a) provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and
- b) permanently, if the copyright holder fails to notify you of the
violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated
permanently if the copyright holder notifies you of the violation by some
reasonable means, this is the first time you have received notice of violation
of this License (for any work) from that copyright holder, and you cure the
violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses
of parties who have received copies or rights from you under this License. If
your rights have been terminated and not permanently reinstated, you do not
qualify to receive new licenses for the same material under section 10.
### 9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy
of the Program. Ancillary propagation of a covered work occurring solely as a
consequence of using peer-to-peer transmission to receive a copy likewise does
not require acceptance. However, nothing other than this License grants you
permission to propagate or modify any covered work. These actions infringe
copyright if you do not accept this License. Therefore, by modifying or
propagating a covered work, you indicate your acceptance of this License to do
so.
### 10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a
license from the original licensors, to run, modify and propagate that work,
subject to this License. You are not responsible for enforcing compliance by
third parties with this License.
An *entity transaction* is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered work
results from an entity transaction, each party to that transaction who receives
a copy of the work also receives whatever licenses to the work the party's
predecessor in interest had or could give under the previous paragraph, plus a
right to possession of the Corresponding Source of the work from the
predecessor in interest, if the predecessor has it or can get it with
reasonable efforts.
You may not impose any further restrictions on the exercise of the rights
granted or affirmed under this License. For example, you may not impose a
license fee, royalty, or other charge for exercise of rights granted under this
License, and you may not initiate litigation (including a cross-claim or
counterclaim in a lawsuit) alleging that any patent claim is infringed by
making, using, selling, offering for sale, or importing the Program or any
portion of it.
### 11. Patents.
A *contributor* is a copyright holder who authorizes use under this License of
the Program or a work on which the Program is based. The work thus licensed is
called the contributor's *contributor version*.
A contributor's *essential patent claims* are all patent claims owned or
controlled by the contributor, whether already acquired or hereafter acquired,
that would be infringed by some manner, permitted by this License, of making,
using, or selling its contributor version, but do not include claims that would
be infringed only as a consequence of further modification of the contributor
version. For purposes of this definition, *control* includes the right to grant
patent sublicenses in a manner consistent with the requirements of this
License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent
license under the contributor's essential patent claims, to make, use, sell,
offer for sale, import and otherwise run, modify and propagate the contents of
its contributor version.
In the following three paragraphs, a *patent license* is any express agreement
or commitment, however denominated, not to enforce a patent (such as an express
permission to practice a patent or covenant not to sue for patent
infringement). To *grant* such a patent license to a party means to make such
an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the
Corresponding Source of the work is not available for anyone to copy, free of
charge and under the terms of this License, through a publicly available
network server or other readily accessible means, then you must either
1. cause the Corresponding Source to be so available, or
2. arrange to deprive yourself of the benefit of the patent license for this
particular work, or
3. arrange, in a manner consistent with the requirements of this License, to
extend the patent license to downstream recipients.
*Knowingly relying* means you have actual knowledge that, but for the patent
license, your conveying the covered work in a country, or your recipient's use
of the covered work in a country, would infringe one or more identifiable
patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you
convey, or propagate by procuring conveyance of, a covered work, and grant a
patent license to some of the parties receiving the covered work authorizing
them to use, propagate, modify or convey a specific copy of the covered work,
then the patent license you grant is automatically extended to all recipients
of the covered work and works based on it.
A patent license is *discriminatory* if it does not include within the scope of
its coverage, prohibits the exercise of, or is conditioned on the non-exercise
of one or more of the rights that are specifically granted under this License.
You may not convey a covered work if you are a party to an arrangement with a
third party that is in the business of distributing software, under which you
make payment to the third party based on the extent of your activity of
conveying the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory patent
license
- a) in connection with copies of the covered work conveyed by you (or copies
made from those copies), or
- b) primarily for and in connection with specific products or compilations
that contain the covered work, unless you entered into that arrangement, or
that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied
license or other defenses to infringement that may otherwise be available to
you under applicable patent law.
### 12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not excuse
you from the conditions of this License. If you cannot convey a covered work so
as to satisfy simultaneously your obligations under this License and any other
pertinent obligations, then as a consequence you may not convey it at all. For
example, if you agree to terms that obligate you to collect a royalty for
further conveying from those to whom you convey the Program, the only way you
could satisfy both those terms and this License would be to refrain entirely
from conveying the Program.
### 13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have permission to
link or combine any covered work with a work licensed under version 3 of the
GNU Affero General Public License into a single combined work, and to convey
the resulting work. The terms of this License will continue to apply to the
part which is the covered work, but the special requirements of the GNU Affero
General Public License, section 13, concerning interaction through a network
will apply to the combination as such.
### 14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU
General Public License from time to time. Such new versions will be similar in
spirit to the present version, but may differ in detail to address new problems
or concerns.
Each version is given a distinguishing version number. If the Program specifies
that a certain numbered version of the GNU General Public License *or any later
version* applies to it, you have the option of following the terms and
conditions either of that numbered version or of any later version published by
the Free Software Foundation. If the Program does not specify a version number
of the GNU General Public License, you may choose any version ever published by
the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the
GNU General Public License can be used, that proxy's public statement of
acceptance of a version permanently authorizes you to choose that version for
the Program.
Later license versions may give you additional or different permissions.
However, no additional obligations are imposed on any author or copyright
holder as a result of your choosing to follow a later version.
### 15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
PARTIES PROVIDE THE PROGRAM *AS IS* WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.
### 16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
### 17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot
be given local legal effect according to their terms, reviewing courts shall
apply local law that most closely approximates an absolute waiver of all civil
liability in connection with the Program, unless a warranty or assumption of
liability accompanies a copy of the Program in return for a fee.
## END OF TERMS AND CONDITIONS ###
### How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible
use to the public, the best way to achieve this is to make it free software
which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach
them to the start of each source file to most effectively state the exclusion
of warranty; and each file should have at least the *copyright* line and a
pointer to where the full notice is found.
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like
this when it starts in an interactive mode:
Copyright (C)
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w` and `show c` should show the appropriate
parts of the General Public License. Of course, your program's commands might
be different; for a GUI interface, you would use an *about box*.
You should also get your employer (if you work as a programmer) or school, if
any, to sign a *copyright disclaimer* for the program, if necessary. For more
information on this, and how to apply and follow the GNU GPL, see
[http://www.gnu.org/licenses/](http://www.gnu.org/licenses/).
The GNU General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may consider
it more useful to permit linking proprietary applications with the library. If
this is what you want to do, use the GNU Lesser General Public License instead
of this License. But first, please read
[http://www.gnu.org/philosophy/why-not-lgpl.html](http://www.gnu.org/philosophy/why-not-lgpl.html).
---
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
================================================
FILE: README.md
================================================
# STIG Manager
STIG Manager is an API and web client for managing STIG assessments of Information Systems, sponsored by the [NAVSEA Warfare Centers](https://www.navsea.navy.mil/Home/Warfare-Centers/). The application presents a unified view of STIG compliance drawn from manual reviews in the web app, file imports (.ckl/.cklb/XCCDF), or automated integrations via the API. STIG Manager supports DISA [Security Technical Implementation Guides (STIGs)](https://public.cyber.mil/stigs/) and Security Requirements Guides (SRGs).
## Who It's For
If you need to track STIG evaluation status across multiple assets, STIGs, or systems, this tool addresses the challenges of managing assessment data that would otherwise be scattered across individual checklist files or spreadsheets.
System administrators can record compliance status in real-time as they harden systems, and scan results from external tools can flow in automatically via the API, providing ISSOs and security managers with live visibility into assessment progress. Working from a shared data set ensures all users maintain a consistent view of compliance status.
## Key Capabilities
- **Collection-Based Organization**: Group Assets, STIGs, and Reviews into Collections that align with your RMF packages or organizational structure; use customizable Labels to categorize Assets and filter views.
- **Progress Tracking and Metrics**: Real-time dashboards showing assessment completion rates, findings by severity, CORA risk scoring, and status tracking.
- **Multi-Source Review Integration**: Combine manual evaluations with imported scan results (XCCDF) and checklists (CKL) in a unified data management interface.
- **Intelligent STIG Revision Management**: When DISA releases new STIG versions, only Rules with changed check content require re-evaluation. Existing reviews are automatically matched to updated Rules where appropriate.
- **Bulk Operations**: Evaluate the same Rule across multiple Assets simultaneously in the Collection Review workspace, apply batch updates, and import/export entire Collections.
- **Collaborative Workflows**: Role-based access controls, Accept/Reject review validation, and configurable review requirements per Collection.
- **API-First Architecture**: Complete REST API (OpenAPI 3.0.1) enables integration with automated scanning tools and custom workflows. The API-first architecture allows custom or third-party clients to interact with assessment data.
## Screenshots
### Collection Dashboard
*Real-time metrics showing assessment completion, findings by severity, and CORA risk scoring*
### Asset Review Workspace
*Assessment interface with Rule details, CCI/Control mappings, and reference to previous assessments on similar Assets*
### Collection Review Workspace
*Evaluate the same STIG Rule across all Assets in a Collection, with color-coded status and the ability to apply bulk updates*
### Meta-Collection Dashboard
*Aggregate metrics across all Collections you have access to, providing organization-wide visibility into assessment status*
## Role in RMF Workflows
STIG Manager primarily supports **RMF Steps 3 (Implement Security Controls)** and **4 (Assess Security Controls)** by serving as the authoritative reference for current STIG assessment status. During **Step 6 (Monitor Security Controls)**, it tracks review ages, maintains assessment history, and identifies what requires re-evaluation when STIGs update or systems change.
The tool fits within existing processes that typically involve eMASS (or similar RMF platforms), SCAP compliance scanners, and other security tools. STIG Manager does not replace these systems—it specializes in STIG assessment tracking and can import results from scanning tools, export checklists for package submission, and support custom automation via its API.
## Getting Started
- [User Walkthrough](https://stig-manager.readthedocs.io/en/latest/user-guide/user-quickstart.html) - Learn the core workflows for security analysts
- [Admin Walkthrough](https://stig-manager.readthedocs.io/en/latest/admin-guide/admin-quickstart.html) - Setup and Collection management for Application Managers
- [Installation Guide](https://stig-manager.readthedocs.io/en/latest/installation-and-setup/installation-and-setup.html) - Deployment instructions and configuration
- [Environment Variables Reference](https://stig-manager.readthedocs.io/en/latest/installation-and-setup/environment-variables.html)
## Deployment Options
**Containerized (Recommended):**
- Official [Docker images](https://hub.docker.com/r/nuwcdivnpt/stig-manager) available on Docker Hub and DoD Iron Bank
- Quick-start Docker Compose orchestration includes all dependencies (Keycloak, MySQL)
- [Reference orchestration with CAC/PKI authentication](https://github.com/NUWCDIVNPT/stigman-orchestration) demonstrates nginx reverse proxy integration
- Supports Kubernetes, OpenShift, or any OCI-compliant container runtime
**Direct Deployment:**
- Run from source using Node.js LTS
- Pre-compiled binaries for Windows/Linux/macOS (no Node.js required)
**Infrastructure Requirements:**
- OpenID Connect (OIDC) provider for authentication (Keycloak, Okta, Azure Entra ID, and F5 tested)
- MySQL 8.4+ database
- Optional reverse proxy for CAC/PKI authentication
The application is stateless and can scale horizontally. Configuration is managed entirely through environment variables.
## Documentation and Resources
The [STIG Manager documentation](https://stig-manager.readthedocs.io/en/latest/index.html) includes User and Setup Guides, video tutorials, terminology references, and deployment scenarios.
- [YouTube Channel](https://www.youtube.com/@stig-manager) - Video tutorials and feature demonstrations
- [Release Notes](https://github.com/NUWCDIVNPT/stig-manager/releases) - Version history
- [Contribution Guide](CONTRIBUTING.md) - DCO requirements and development setup
## Related Resources
**[STIGMan Watcher](https://github.com/NUWCDIVNPT/stigman-watcher)** - A command-line utility that monitors filesystem directories and automatically imports .ckl/.cklb checklists and XCCDF scan results into STIG Manager. Useful for automated workflows and continuous integration with scanning tools.
**[Reference orchestration with CAC/PKI authentication](https://github.com/NUWCDIVNPT/stigman-orchestration)** - A sample Docker Compose setup that includes nginx configured for CAC/PKI authentication in front of STIG Manager and Keycloak.
**[C-PAT](https://github.com/NSWC-Crane/C-PAT)** - The Crane POA&M Automation Tool, developed by NSWC Crane, integrates with STIG Manager's API to automate vulnerability documentation and POA&M tracking throughout the RMF process.
## Sponsor
STIG Manager is sponsored by the [NAVSEA Warfare Centers](https://www.navsea.navy.mil/Home/Warfare-Centers/). While its primary goal is to support NAVSEA compliance processes, the tool is designed to be flexible and adaptable to other workflows. This project follows [Code.mil](https://code.mil) [guidance](https://github.com/Code-dot-mil/code.mil) for open source software released by the U.S. Department of Defense.
For inquiries, contact the RMF Tools team at RMF_Tools@us.navy.mil.
================================================
FILE: SECURITY.md
================================================
# Security Policy
## Supported Versions
The STIG Manager Team makes every effort to produce secure software. The project addresses vulnerabilities in the application with new mainline releases. Old versions will not be patched. All users are expected to stay up to date with security and feature updates by running only the latest release available.
| Version | Supported |
| ------- | ------------------ |
| Current | :white_check_mark: |
| All previous | :x: |
## Reporting a Vulnerability
Vulnerability scans are run regularly against project components and any issues identified are addressed. Nevertheless, we are grateful to anyone reporting a vulnerability and helping us to make STIG Manager better and more secure. Additionally, we encourage everyone to disclose bugs in a responsible way, allowing us and other STIGMan users to react accordingly and in a timely manner. That means:
- If you want to report a critical security bug or vulnerability please send a bug report to RMF_Tools@us.navy.mil before publishing it. We will acknowledge your email within a week (7 days), and will send a more detailed response up to 48 hours after that indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and an announcement. We may ask for additional information or guidance. When disclosing vulnerabilities please include the following:
- The word "SECURITY" in the subject line.
- Your name and affiliation (if any).
- Scope of vulnerability. Let us know who could use this exploit.
- Documented steps to identify the vulnerability. It is important that we can reproduce your findings.
- If you want to report a non-critical bug, please open an issue on the GitHub project. If you are using a scanning tool to identify a vulnerability, please attempt to determine whether or not the issue is a false positive before reporting, and if it is not, include the specific scanner, settings, and config you used to identify it.
- Report security bugs in third-party modules to the person or team maintaining the module.
- This is an open source project. If you discover a bug and fix it, you are very welcome to submit a PR. Your fix will be reviewed, and if accepted, you will become a valued addition to our CONTRIBUTORS.md file!
- Known vulnerabilities will be published on the [Security Advisories page of the project's GitHub site.](https://github.com/NUWCDIVNPT/stig-manager/security/advisories)
## Securing STIG Manager
STIG Manager is one component of a system that must be deployed according to your individual or organizational security requirements.
Please see the [project Documentation for more information on this topic.](https://stig-manager.readthedocs.io/en/latest/installation-and-setup/securing.html)
================================================
FILE: api/README.md
================================================
# STIG Manager API for Node.js
## Required Node version
The API requires Node 14.0.0 or greater
## Building binaries
- Read the comments in `build.sh` regarding build requirements
- Run `./build.sh` or `build.sh --sign`
- Binaries are written to `./bin`
- Archives with launcher scripts are written to `./dist`
## Configuring and running the API
The API is configured through [environment variables](../docs/Environment_Variables.md). The entry point is `index.js`
================================================
FILE: api/bin/.gitignore
================================================
## Directory for the STIG Manager API binaries
# Content can be written here by executing:
# $ ../build.sh
#
# This file hopes to prevent commits to this directory
# Ignore everything in this directory
*
# Except this file
!.gitignore
================================================
FILE: api/build.sh
================================================
#!/bin/bash
# This file is used to build API binaries on the team workstations. It is not tested elsewhere, yet.
# Requires:
# - Node.js and module "@yao-pkg/pkg" (npm install -g @yao-pkg/pkg@6.10)
# - zip
# - tar
check_exit_status() {
if [[ $? -eq 0 ]]; then
echo "[BUILD_TASK] $1 succeeded"
else
echo "[BUILD_TASK] $1 failed"
exit $2
fi
}
LAUNCHERDIR=launchers
BINDIR=bin
DISTDIR=dist
# Change to this script directory
cd "$(dirname "$(realpath "$0")")"
# Prepare
[ ! -d "$BINDIR" ] && mkdir -p "$BINDIR"
[ ! -d "$DISTDIR" ] && mkdir -p "$DISTDIR"
rm -rf $BINDIR/*
rm -rf $DISTDIR/*
echo "Fetching node_modules"
rm -rf ./source/node_modules
cd ./source
npm ci
npm install -g @yao-pkg/pkg@6.10
cd ..
../client/build.sh
../docs/build.sh
DESCRIBE=$(git describe --tags | sed 's/\(.*\)-.*/\1/')
check_exit_status "Getting latest tag" 4
echo $DESCRIBE
# Make binaries
echo "Building binaries"
pkg ./source/index.js -C gzip --public --public-packages=* --no-bytecode -c pkg.config.json
check_exit_status "Building binaries" 1
echo "Creating archives with launchers"
# Windows archive
zip --junk-paths $DISTDIR/stig-manager-win-$DESCRIBE.zip $LAUNCHERDIR/stig-manager.bat $BINDIR/stig-manager-win.exe
check_exit_status "Zipping Windows Archive" 3
# Linux archive
tar -cJvf $DISTDIR/stig-manager-linux-$DESCRIBE.tar.xz --xform='s|^|stig-manager/|S' -C $LAUNCHERDIR stig-manager.sh -C ../$BINDIR stig-manager-linuxstatic
check_exit_status "Zipping Linux Archive" 4
echo "Build artifacts are in $DISTDIR"
================================================
FILE: api/dist/.gitignore
================================================
## Directory for the STIG Manager API distribution archives
# Content can be written here by executing:
# $ ../build.sh
#
# This file hopes to prevent commits to this directory
# Ignore everything in this directory
*
# Except this file
!.gitignore
================================================
FILE: api/launchers/gen-launchers.py
================================================
#!/usr/bin/python3
import sys
import os
import io
import csv
import textwrap
if len(sys.argv) > 1 and sys.argv[1] == 'win':
system = 'win'
comment = '::'
command = 'set'
launch = 'stig-manager-win.exe'
filename = 'stig-manager.bat'
newline = '\r\n'
else:
system = 'linux'
comment = '#'
command = 'export'
launch = './stig-manager-linuxstatic'
filename = 'stig-manager.sh'
newline = '\n'
with open('../../docs/installation-and-setup/envvars.csv', 'r') as csvfile:
reader = csv.DictReader(csvfile)
with io.open(filename, 'w', newline=newline) as f:
for row in reader:
row['Description'] = row['Description'].replace('**Default**', 'Default:')
row['Description'] = row['Description'].replace('**No default**', 'No default.')
row['Description'] = row['Description'].replace('``', '"')
row['Description'] = '\n'.join(textwrap.wrap(row['Description'], width=80, initial_indent=comment + ' ', subsequent_indent=comment + ' '))
f.write('{0}==============================================================================\n'.format(comment))
content = '{0} {1}\n{0}\n{2}\n{0}\n{0} Affects: {3}\n'.format(comment, row['Variable'], row['Description'], row['Affects'])
f.write(content)
f.write('{0}==============================================================================\n'.format(comment))
f.write('{0} {1} {2}=\n'.format(comment, command, row['Variable']))
f.write('\n')
f.write(launch + '\n')
if system == 'linux':
os.chmod(filename, 0o755)
================================================
FILE: api/launchers/stig-manager.bat
================================================
::==============================================================================
:: STIGMAN_API_ADDRESS
::
:: | Default: "0.0.0.0" | The IP address on which the the API server will
:: listen
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_ADDRESS=
::==============================================================================
:: STIGMAN_API_MAX_JSON_BODY
::
:: | Default: "5242880" | The maximum size in bytes of the request body when
:: Content-Type is application/json
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_MAX_JSON_BODY=
::==============================================================================
:: STIGMAN_API_MAX_UPLOAD
::
:: | Default: "1073741824" | The maximum size in bytes of the file uploaded
:: with Content-Type multipart/form-data
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_MAX_UPLOAD=
::==============================================================================
:: STIGMAN_API_PORT
::
:: | Default: "54000" | The TCP port on which the server will listen
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_PORT=
::==============================================================================
:: STIGMAN_API_TLS_CERT_FILE
::
:: | No default. | A absolute path to the file that contains the PEM encoded
:: Server certificate used for TLS. Additionally requires setting
:: "STIGMAN_API_TLS_KEY_FILE" to enable TLS.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_TLS_CERT_FILE=
::==============================================================================
:: STIGMAN_API_TLS_KEY_FILE
::
:: | No default. | A absolute path to the file that contains the PEM encoded
:: Server private key used for TLS. Additionally requires setting
:: "STIGMAN_API_TLS_CERT_FILE" to enable TLS.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_TLS_KEY_FILE=
::==============================================================================
:: STIGMAN_API_TLS_KEY_PASSPHRASE
::
:: | No default. | If necessary, the passphrase that decrypts the PEM encoded
:: Server private key used for TLS. Additionally requires setting
:: "STIGMAN_API_TLS_CERT_FILE" to enable TLS.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_API_TLS_KEY_PASSPHRASE=
::==============================================================================
:: STIGMAN_CLASSIFICATION
::
:: | Default: "U" | Sets the classification banner, if any. Available values:
:: "NONE" "U" "CUI" "C" "S" "TS" "SCI"
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_CLASSIFICATION=
::==============================================================================
:: STIGMAN_CLIENT_ADMIN_TIMEOUT
::
:: | Default: "0" | The maximum time (in minutes) a user with admin privileges
:: can be inactive in the web client before discarding their access token and
:: requiring reauthorization. Activity is defined as mouse click, keypress, or
:: scrolling in any tab or window of a same-origin browsing context group. Set
:: to zero to disable idle detection.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_ADMIN_TIMEOUT=
::==============================================================================
:: STIGMAN_CLIENT_API_BASE
::
:: | Default: "api" | The base URL for Client requests to the API relative to
:: "window.location"
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_API_BASE=
::==============================================================================
:: STIGMAN_CLIENT_CONSOLE_MODE
::
:: | Default: "production" | The console mode of the web client, setting to
:: "development" enables console logging which is otherwise disabled
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_CONSOLE_MODE=
::==============================================================================
:: STIGMAN_CLIENT_DIRECTORY
::
:: | Default: "./clients" | The location of the web client files, relative to
:: the API source directory. Note that if running source from a clone of the
:: GitHub repository, the client is located at `../../clients` relative to the
:: API directory.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_CLIENT_DIRECTORY=
::==============================================================================
:: STIGMAN_CLIENT_DISABLED
::
:: | Default: "false" | Whether to *not* serve the reference web client
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_DISABLED=
::==============================================================================
:: STIGMAN_CLIENT_DISPLAY_APPMANAGERS
::
:: | Default: "true" | Whether to display application managers the home page of
:: web client
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_DISPLAY_APPMANAGERS=
::==============================================================================
:: STIGMAN_CLIENT_EXTRA_SCOPES
::
:: | No default. | A space separated list of OAuth2 scopes to request in
:: addition to "stig-manager:stig" "stig-manager:stig:read" "stig-
:: manager:collection" "stig-manager:user" "stig-manager:user:read" "stig-
:: manager:op". Some OIDC providers (Okta) generate a refresh token only if the
:: scope "offline_access" is requested
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_EXTRA_SCOPES=
::==============================================================================
:: STIGMAN_CLIENT_ID
::
:: | Default: "stig-manager" | The OIDC clientId of the web client
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_ID=
::==============================================================================
:: STIGMAN_CLIENT_OIDC_PROVIDER
::
:: | Default: Value of "STIGMAN_OIDC_PROVIDER" | Client override of the base
:: URL of the OIDC provider issuing signed JWTs for the API. The string
:: "/.well-known/openid-configuration" will be appended by the client when
:: fetching metadata.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_OIDC_PROVIDER=
::==============================================================================
:: STIGMAN_CLIENT_REAUTH_ACTION
::
:: | Default: "popup" | How to prompt for re-authentication when user
:: credentials expire. Available values: "popup", "iframe", "tab", or "reload".
:: See :ref:`stigman_client_reauth_action` in the Authentication document for
:: details.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_REAUTH_ACTION=
::==============================================================================
:: STIGMAN_CLIENT_RESPONSE_MODE
::
:: | Default: "fragment" | The response_mode the web client should specify when
:: requesting an authorization code from the OIDC provider. Available values:
:: "fragment", "query"
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_RESPONSE_MODE=
::==============================================================================
:: STIGMAN_CLIENT_SCOPE_PREFIX
::
:: | No default. | String used as a prefix for each scope when authenticating
:: to the OIDC Provider. Some providers (Azure AD) expect scope requests in the
:: format "api:///", where "api:///" is
:: the required prefix.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_SCOPE_PREFIX=
::==============================================================================
:: STIGMAN_CLIENT_STATE_EVENTS
::
:: | Default: "true" | Whether the web client listens for server sent events
:: (SSE) about the API state. Should only be disabled temporarily while
:: resolving buffering issues on a reverse proxy.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_STATE_EVENTS=
::==============================================================================
:: STIGMAN_CLIENT_STRICT_PKCE
::
:: | Default: "true" | Whether the web client verifies the OIDC provider is
:: advertising PKCE/S256 support in compliance with RFC 8414. A non-compliant
:: provider supports PKCE/S256 without advertising it. Independent of this
:: value, the web client always exclusively uses PKCE/S256 in the Authorization
:: Code Flow.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_STRICT_PKCE=
::==============================================================================
:: STIGMAN_CLIENT_USER_TIMEOUT
::
:: | Default: "0" | The maximum time (in minutes) a regular user can be
:: inactive in the web client before discarding their access token and
:: requiring reauthorization. Activity is defined as mouse click, keypress, or
:: scrolling in any tab or window of a same-origin browsing context group. Set
:: to zero to disable idle detection.
::
:: Affects: Client
::==============================================================================
:: set STIGMAN_CLIENT_USER_TIMEOUT=
::==============================================================================
:: STIGMAN_CLIENT_WELCOME_IMAGE
::
:: | No default. | The URL of an image hosted elsewhere that will be rendered
:: in the Home tab Welcome widget. The STIGMan app does not serve the image
:: itself, only the reference to it. The URL should be in relation to and
:: accessible from the client's browser. The image will be scaled to a max
:: width or height of 125 pixels - If no alternate image is specified, the seal
:: of the Department of the Navy (the project sponsor) will be displayed.
::
:: Affects: Client Appearance
::==============================================================================
:: set STIGMAN_CLIENT_WELCOME_IMAGE =
::==============================================================================
:: STIGMAN_CLIENT_WELCOME_LINK
::
:: | No default. | Value of an optional link that will follow the Welcome
:: message in the Home tab Welcome widget.
::
:: Affects: Client Appearance
::==============================================================================
:: set STIGMAN_CLIENT_WELCOME_LINK=
::==============================================================================
:: STIGMAN_CLIENT_WELCOME_MESSAGE
::
:: | No default. | Text that will be displayed in the Home tab Welcome widget.
::
:: Affects: Client Appearance
::==============================================================================
:: set STIGMAN_CLIENT_WELCOME_MESSAGE =
::==============================================================================
:: STIGMAN_CLIENT_WELCOME_TITLE
::
:: | Default: "Support" | The tile that will be displayed for the custom Home
:: tab Welcome message.
::
:: Affects: Client Appearance
::==============================================================================
:: set STIGMAN_CLIENT_WELCOME_TITLE =
::==============================================================================
:: STIGMAN_DB_HOST
::
:: | Default: "localhost" | The database hostname or IP from to the API server
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_HOST=
::==============================================================================
:: STIGMAN_DB_MAX_CONNECTIONS
::
:: | Default: "25" | The maximum size of the database connection pool
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_MAX_CONNECTIONS=
::==============================================================================
:: STIGMAN_DB_PASSWORD
::
:: | No default. | The password used to login to the database
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_PASSWORD=
::==============================================================================
:: STIGMAN_DB_PORT
::
:: | Default: "3306" | The database TCP port relative to the API server
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_PORT=
::==============================================================================
:: STIGMAN_DB_SCHEMA
::
:: | Default: "stigman" | The schema where the STIG Manager object are found
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_SCHEMA=
::==============================================================================
:: STIGMAN_DB_TLS_CA_FILE
::
:: | No default. | An absolute path or a path relative to the API /tls
:: directory that contains the PEM encoded CA certificate used to sign the
:: database TLS certificate. Setting this variable enables TLS connections to
:: the database.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_TLS_CA_FILE=
::==============================================================================
:: STIGMAN_DB_TLS_CERT_FILE
::
:: | No default. | An absolute path or a path relative to the API /tls
:: directory that contains the PEM encoded Client certificate used when
:: authenticating the database client. Additionally requires setting values for
:: "STIGMAN_DB_TLS_CA_FILE" and "STIGMAN_DB_TLS_KEY_FILE".
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_TLS_CERT_FILE=
::==============================================================================
:: STIGMAN_DB_TLS_KEY_FILE
::
:: | No default. | An absolute path or a path relative to the API /tls
:: directory that contains the PEM encoded Client private key used when
:: authenticating the database client. Additionally requires setting values for
:: "STIGMAN_DB_TLS_CA_FILE" and "STIGMAN_DB_TLS_CERT_FILE".
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_TLS_KEY_FILE=
::==============================================================================
:: STIGMAN_DB_USER
::
:: | Default: "stigman" | The user account used to login to the database
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DB_USER=
::==============================================================================
:: STIGMAN_DEPENDENCY_RETRIES
::
:: | Default: "24" | During startup, the number of attempts made to establish
:: connections to the database and OIDC Provider. Retries are made every 5
:: seconds and the API process exits if unsuccessful.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DEPENDENCY_RETRIES=
::==============================================================================
:: STIGMAN_DEV_ALLOW_INSECURE_TOKENS
::
:: | Default: "false" | Controls whether known insecure JWT signing keys are
:: allowed. Only for development/testing purposes. Setting to 'true' is NOT
:: recommended for production environments.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DEV_ALLOW_INSECURE_TOKENS=
::==============================================================================
:: STIGMAN_DEV_LOG_OPT_STATS
::
:: | Default: "true" | Controls whether the API will track API operation
:: statistics used for populating "Requests" portion of "/op/appinfo" response
:: body. Setting to 'false' is NOT recommended for production environments, as
:: this info can be useful for troubleshooting.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DEV_LOG_OPT_STATS=
::==============================================================================
:: STIGMAN_DEV_RESPONSE_VALIDATION
::
:: | Default: "none" | Controls whether the API will perform response
:: validation on API responses. If set to 'logOnly' the API will output log
:: entries indicating deviations from the OAS specification. Intended for
:: development/testing purposes. Available values: "none", "logOnly"
::
:: Affects: API
::==============================================================================
:: set STIGMAN_DEV_RESPONSE_VALIDATION=
::==============================================================================
:: STIGMAN_DOCS_DIRECTORY
::
:: | Default: "./docs" | The location of the documentation files, relative to
:: the API source directory. Note that if running source from a clone of the
:: GitHub repository, the docs are located at `../../docs/_build/html` relative
:: to the API directory.
::
:: Affects: API, Documentation
::==============================================================================
:: set STIGMAN_DOCS_DIRECTORY=
::==============================================================================
:: STIGMAN_DOCS_DISABLED
::
:: | Default: "false" | Whether to *not* serve the project Documentation.
:: NOTE: If you choose to serve the Client from the API container but not the
:: Documentation, the links do the Docs on the home page will not work.
::
:: Affects: Documentation
::==============================================================================
:: set STIGMAN_DOCS_DISABLED=
::==============================================================================
:: STIGMAN_EXPERIMENTAL_APPDATA
::
:: | Default: "false" | Set to "true" to enable the experimental AppData
:: import/export API endpoints and User Interface.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_EXPERIMENTAL_APPDATA=
::==============================================================================
:: STIGMAN_EXPERIMENTAL_LOGSTREAM
::
:: | Default: "true" | Set to "false" to disable the experimental WebSocket
:: for streaming API logs and the corresponding User Interface.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_EXPERIMENTAL_LOGSTREAM=
::==============================================================================
:: STIGMAN_LOG_LEVEL
::
:: | Default: "3" | Controls the granularity of the generated log output, from
:: 1 to 4. Each level is inclusive of the ones before it. Level 1 will log only
:: errors, level 2 includes warnings, level 3 includes status and transaction
:: logs, and level 4 includes debug-level logs
::
:: Affects: API
::==============================================================================
:: set STIGMAN_LOG_LEVEL=
::==============================================================================
:: STIGMAN_LOG_MODE
::
:: | Default: "combined" | Controls whether the logs will create one “combined”
:: log entry for http requests that includes both the request and response
:: information; or two separate log entries, one for the request and one for
:: the response, that can be correlated via a generated Request GUID in each
:: entry
::
:: Affects: API
::==============================================================================
:: set STIGMAN_LOG_MODE=
::==============================================================================
:: STIGMAN_JWKS_CACHE_MAX_AGE
::
:: | Default: "10" | The time in minutes after which the API's cache of JWT
:: signing keys is deemed stale and the API becomes unavailable. Cache
:: refreshes are scheduled at intervals of half this value and also occur when
:: an unknown signing key is presented. Scheduled refresh failures are retried
:: every 10 seconds.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_JWKS_CACHE_MAX_AGE=
::==============================================================================
:: STIGMAN_JWT_ASSERTION_CLAIM
::
:: | Default: "jti" | The access token claim whose value is the OIDC provider's
:: Assertion ID. Updates to this value trigger the API to update a User's
:: "lastClaims" property. The claim MUST NOT be nested and MUST be a valid
:: ECMAScript identifier. See :ref:`jwt_requirements` for token value format
:: requirements.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_JWT_ASSERTION_CLAIM=
::==============================================================================
:: STIGMAN_JWT_AUD_VALUE
::
:: | No default. | If present, a string which must be included in the access
:: token "aud" claim for requests to endpoints requiring authorization. See
:: :ref:`jwt_requirements` for token value format requirements.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_JWT_AUD_VALUE=
::==============================================================================
:: STIGMAN_JWT_EMAIL_CLAIM
::
:: | Default: "email" | The access token claim whose value is the user's email
:: address. The claim MUST NOT be nested and MUST be a valid ECMAScript
:: identifier. See :ref:`jwt_requirements` for token value format requirements.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_JWT_EMAIL_CLAIM=
::==============================================================================
:: STIGMAN_JWT_NAME_CLAIM
::
:: | Default: "name" | The access token claim whose value is the user's full
:: name. The claim MUST NOT be nested and MUST be a valid ECMAScript
:: identifier. See :ref:`jwt_requirements` for token value format requirements.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_JWT_NAME_CLAIM=
::==============================================================================
:: STIGMAN_JWT_PRIVILEGES_CLAIM
::
:: | Default: "realm_access.roles" | The access token claim whose value is the
:: user's privileges. The claim MAY be nested but SHOULD avoid invalid
:: ECMAScript identifiers. See :ref:`jwt_requirements` for token value format
:: requirements.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_JWT_PRIVILEGES_CLAIM=
::==============================================================================
:: STIGMAN_JWT_SCOPE_CLAIM
::
:: | Default: "scope" | The access token claim whose value is the user's
:: scopes. Some OIDC Providers (Okta, Azure AD) use the claim "scp" to
:: enumerate scopes. The claim MUST NOT be nested and MUST be a valid
:: ECMAScript identifier. See :ref:`jwt_requirements` for token value format
:: requirements.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_JWT_SCOPE_CLAIM=
::==============================================================================
:: STIGMAN_JWT_SERVICENAME_CLAIM
::
:: | Default: "clientId" | The access token claim whose value is the service
:: account's client. The claim MUST NOT be nested and MUST be a valid
:: ECMAScript identifier. See :ref:`jwt_requirements` for token value format
:: requirements.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_JWT_SERVICENAME_CLAIM=
::==============================================================================
:: STIGMAN_JWT_USERNAME_CLAIM
::
:: | Default: "preferred_username" | The access token claim whose value is the
:: user's username. The claim MUST NOT be nested and MUST be a valid ECMAScript
:: identifier. See :ref:`jwt_requirements` for token value format requirements.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_JWT_USERNAME_CLAIM=
::==============================================================================
:: STIGMAN_OIDC_CA_CERTS
::
:: | No default. | The full path to a file with one or more PEM-encoded CA
:: certificates for validating TLS connections to the OIDC Provider.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_OIDC_CA_CERTS=
::==============================================================================
:: STIGMAN_OIDC_PROVIDER
::
:: | Default: "http://localhost:8080/auth/realms/stigman" | The base URL of the
:: OIDC provider issuing signed JWTs for the API. The string "/.well-
:: known/openid-configuration" will be appended when fetching metadata.
::
:: Affects: API, Client
::==============================================================================
:: set STIGMAN_OIDC_PROVIDER=
::==============================================================================
:: STIGMAN_SWAGGER_ENABLED
::
:: | Default: "false" | Whether to enable the SwaggerUI SPA at /api-docs
::
:: Affects: API
::==============================================================================
:: set STIGMAN_SWAGGER_ENABLED=
::==============================================================================
:: STIGMAN_SWAGGER_OIDC_PROVIDER
::
:: | Default: Value of "STIGMAN_OIDC_PROVIDER" | SwaggerUI override of the base
:: URL of the OIDC provider issuing signed JWTs for the API. The string
:: "/.well-known/openid-configuration" will be appended by the SwaggerUI when
:: fetching metadata.
::
:: Affects: API
::==============================================================================
:: set STIGMAN_SWAGGER_OIDC_PROVIDER=
::==============================================================================
:: STIGMAN_SWAGGER_REDIRECT
::
:: | Default: "http://localhost:54000/api-docs/oauth2-redirect.html" | The
:: redirect URL sent by SwaggerUI to the OIDC provider when authorizing
::
:: Affects: API
::==============================================================================
:: set STIGMAN_SWAGGER_REDIRECT=
::==============================================================================
:: STIGMAN_SWAGGER_SERVER
::
:: | Default: "http://localhost:54000/api" | The API server URL relative to the
:: SwaggerUI
::
:: Affects: API
::==============================================================================
:: set STIGMAN_SWAGGER_SERVER=
stig-manager-win.exe
================================================
FILE: api/launchers/stig-manager.sh
================================================
#==============================================================================
# STIGMAN_API_ADDRESS
#
# | Default: "0.0.0.0" | The IP address on which the the API server will listen
#
# Affects: API
#==============================================================================
# export STIGMAN_API_ADDRESS=
#==============================================================================
# STIGMAN_API_MAX_JSON_BODY
#
# | Default: "5242880" | The maximum size in bytes of the request body when
# Content-Type is application/json
#
# Affects: API
#==============================================================================
# export STIGMAN_API_MAX_JSON_BODY=
#==============================================================================
# STIGMAN_API_MAX_UPLOAD
#
# | Default: "1073741824" | The maximum size in bytes of the file uploaded with
# Content-Type multipart/form-data
#
# Affects: API
#==============================================================================
# export STIGMAN_API_MAX_UPLOAD=
#==============================================================================
# STIGMAN_API_PORT
#
# | Default: "54000" | The TCP port on which the server will listen
#
# Affects: API
#==============================================================================
# export STIGMAN_API_PORT=
#==============================================================================
# STIGMAN_API_TLS_CERT_FILE
#
# | No default. | A absolute path to the file that contains the PEM encoded
# Server certificate used for TLS. Additionally requires setting
# "STIGMAN_API_TLS_KEY_FILE" to enable TLS.
#
# Affects: API
#==============================================================================
# export STIGMAN_API_TLS_CERT_FILE=
#==============================================================================
# STIGMAN_API_TLS_KEY_FILE
#
# | No default. | A absolute path to the file that contains the PEM encoded
# Server private key used for TLS. Additionally requires setting
# "STIGMAN_API_TLS_CERT_FILE" to enable TLS.
#
# Affects: API
#==============================================================================
# export STIGMAN_API_TLS_KEY_FILE=
#==============================================================================
# STIGMAN_API_TLS_KEY_PASSPHRASE
#
# | No default. | If necessary, the passphrase that decrypts the PEM encoded
# Server private key used for TLS. Additionally requires setting
# "STIGMAN_API_TLS_CERT_FILE" to enable TLS.
#
# Affects: API
#==============================================================================
# export STIGMAN_API_TLS_KEY_PASSPHRASE=
#==============================================================================
# STIGMAN_CLASSIFICATION
#
# | Default: "U" | Sets the classification banner, if any. Available values:
# "NONE" "U" "CUI" "C" "S" "TS" "SCI"
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_CLASSIFICATION=
#==============================================================================
# STIGMAN_CLIENT_ADMIN_TIMEOUT
#
# | Default: "0" | The maximum time (in minutes) a user with admin privileges
# can be inactive in the web client before discarding their access token and
# requiring reauthorization. Activity is defined as mouse click, keypress, or
# scrolling in any tab or window of a same-origin browsing context group. Set
# to zero to disable idle detection.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_ADMIN_TIMEOUT=
#==============================================================================
# STIGMAN_CLIENT_API_BASE
#
# | Default: "api" | The base URL for Client requests to the API relative to
# "window.location"
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_API_BASE=
#==============================================================================
# STIGMAN_CLIENT_CONSOLE_MODE
#
# | Default: "production" | The console mode of the web client, setting to
# "development" enables console logging which is otherwise disabled
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_CONSOLE_MODE=
#==============================================================================
# STIGMAN_CLIENT_DIRECTORY
#
# | Default: "./clients" | The location of the web client files, relative to
# the API source directory. Note that if running source from a clone of the
# GitHub repository, the client is located at `../../clients` relative to the
# API directory.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_CLIENT_DIRECTORY=
#==============================================================================
# STIGMAN_CLIENT_DISABLED
#
# | Default: "false" | Whether to *not* serve the reference web client
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_DISABLED=
#==============================================================================
# STIGMAN_CLIENT_DISPLAY_APPMANAGERS
#
# | Default: "true" | Whether to display application managers the home page of
# web client
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_DISPLAY_APPMANAGERS=
#==============================================================================
# STIGMAN_CLIENT_EXTRA_SCOPES
#
# | No default. | A space separated list of OAuth2 scopes to request in
# addition to "stig-manager:stig" "stig-manager:stig:read" "stig-
# manager:collection" "stig-manager:user" "stig-manager:user:read" "stig-
# manager:op". Some OIDC providers (Okta) generate a refresh token only if the
# scope "offline_access" is requested
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_EXTRA_SCOPES=
#==============================================================================
# STIGMAN_CLIENT_ID
#
# | Default: "stig-manager" | The OIDC clientId of the web client
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_ID=
#==============================================================================
# STIGMAN_CLIENT_OIDC_PROVIDER
#
# | Default: Value of "STIGMAN_OIDC_PROVIDER" | Client override of the base URL
# of the OIDC provider issuing signed JWTs for the API. The string "/.well-
# known/openid-configuration" will be appended by the client when fetching
# metadata.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_OIDC_PROVIDER=
#==============================================================================
# STIGMAN_CLIENT_REAUTH_ACTION
#
# | Default: "popup" | How to prompt for re-authentication when user
# credentials expire. Available values: "popup", "iframe", "tab", or "reload".
# See :ref:`stigman_client_reauth_action` in the Authentication document for
# details.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_REAUTH_ACTION=
#==============================================================================
# STIGMAN_CLIENT_RESPONSE_MODE
#
# | Default: "fragment" | The response_mode the web client should specify when
# requesting an authorization code from the OIDC provider. Available values:
# "fragment", "query"
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_RESPONSE_MODE=
#==============================================================================
# STIGMAN_CLIENT_SCOPE_PREFIX
#
# | No default. | String used as a prefix for each scope when authenticating to
# the OIDC Provider. Some providers (Azure AD) expect scope requests in the
# format "api:///", where "api:///" is
# the required prefix.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_SCOPE_PREFIX=
#==============================================================================
# STIGMAN_CLIENT_STATE_EVENTS
#
# | Default: "true" | Whether the web client listens for server sent events
# (SSE) about the API state. Should only be disabled temporarily while
# resolving buffering issues on a reverse proxy.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_STATE_EVENTS=
#==============================================================================
# STIGMAN_CLIENT_STRICT_PKCE
#
# | Default: "true" | Whether the web client verifies the OIDC provider is
# advertising PKCE/S256 support in compliance with RFC 8414. A non-compliant
# provider supports PKCE/S256 without advertising it. Independent of this
# value, the web client always exclusively uses PKCE/S256 in the Authorization
# Code Flow.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_STRICT_PKCE=
#==============================================================================
# STIGMAN_CLIENT_USER_TIMEOUT
#
# | Default: "0" | The maximum time (in minutes) a regular user can be inactive
# in the web client before discarding their access token and requiring
# reauthorization. Activity is defined as mouse click, keypress, or scrolling
# in any tab or window of a same-origin browsing context group. Set to zero to
# disable idle detection.
#
# Affects: Client
#==============================================================================
# export STIGMAN_CLIENT_USER_TIMEOUT=
#==============================================================================
# STIGMAN_CLIENT_WELCOME_IMAGE
#
# | No default. | The URL of an image hosted elsewhere that will be rendered in
# the Home tab Welcome widget. The STIGMan app does not serve the image itself,
# only the reference to it. The URL should be in relation to and accessible
# from the client's browser. The image will be scaled to a max width or height
# of 125 pixels - If no alternate image is specified, the seal of the
# Department of the Navy (the project sponsor) will be displayed.
#
# Affects: Client Appearance
#==============================================================================
# export STIGMAN_CLIENT_WELCOME_IMAGE =
#==============================================================================
# STIGMAN_CLIENT_WELCOME_LINK
#
# | No default. | Value of an optional link that will follow the Welcome
# message in the Home tab Welcome widget.
#
# Affects: Client Appearance
#==============================================================================
# export STIGMAN_CLIENT_WELCOME_LINK=
#==============================================================================
# STIGMAN_CLIENT_WELCOME_MESSAGE
#
# | No default. | Text that will be displayed in the Home tab Welcome widget.
#
# Affects: Client Appearance
#==============================================================================
# export STIGMAN_CLIENT_WELCOME_MESSAGE =
#==============================================================================
# STIGMAN_CLIENT_WELCOME_TITLE
#
# | Default: "Support" | The tile that will be displayed for the custom Home
# tab Welcome message.
#
# Affects: Client Appearance
#==============================================================================
# export STIGMAN_CLIENT_WELCOME_TITLE =
#==============================================================================
# STIGMAN_DB_HOST
#
# | Default: "localhost" | The database hostname or IP from to the API server
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_HOST=
#==============================================================================
# STIGMAN_DB_MAX_CONNECTIONS
#
# | Default: "25" | The maximum size of the database connection pool
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_MAX_CONNECTIONS=
#==============================================================================
# STIGMAN_DB_PASSWORD
#
# | No default. | The password used to login to the database
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_PASSWORD=
#==============================================================================
# STIGMAN_DB_PORT
#
# | Default: "3306" | The database TCP port relative to the API server
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_PORT=
#==============================================================================
# STIGMAN_DB_SCHEMA
#
# | Default: "stigman" | The schema where the STIG Manager object are found
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_SCHEMA=
#==============================================================================
# STIGMAN_DB_TLS_CA_FILE
#
# | No default. | An absolute path or a path relative to the API /tls directory
# that contains the PEM encoded CA certificate used to sign the database TLS
# certificate. Setting this variable enables TLS connections to the database.
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_TLS_CA_FILE=
#==============================================================================
# STIGMAN_DB_TLS_CERT_FILE
#
# | No default. | An absolute path or a path relative to the API /tls directory
# that contains the PEM encoded Client certificate used when authenticating the
# database client. Additionally requires setting values for
# "STIGMAN_DB_TLS_CA_FILE" and "STIGMAN_DB_TLS_KEY_FILE".
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_TLS_CERT_FILE=
#==============================================================================
# STIGMAN_DB_TLS_KEY_FILE
#
# | No default. | An absolute path or a path relative to the API /tls directory
# that contains the PEM encoded Client private key used when authenticating the
# database client. Additionally requires setting values for
# "STIGMAN_DB_TLS_CA_FILE" and "STIGMAN_DB_TLS_CERT_FILE".
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_TLS_KEY_FILE=
#==============================================================================
# STIGMAN_DB_USER
#
# | Default: "stigman" | The user account used to login to the database
#
# Affects: API
#==============================================================================
# export STIGMAN_DB_USER=
#==============================================================================
# STIGMAN_DEPENDENCY_RETRIES
#
# | Default: "24" | During startup, the number of attempts made to establish
# connections to the database and OIDC Provider. Retries are made every 5
# seconds and the API process exits if unsuccessful.
#
# Affects: API
#==============================================================================
# export STIGMAN_DEPENDENCY_RETRIES=
#==============================================================================
# STIGMAN_DEV_ALLOW_INSECURE_TOKENS
#
# | Default: "false" | Controls whether known insecure JWT signing keys are
# allowed. Only for development/testing purposes. Setting to 'true' is NOT
# recommended for production environments.
#
# Affects: API
#==============================================================================
# export STIGMAN_DEV_ALLOW_INSECURE_TOKENS=
#==============================================================================
# STIGMAN_DEV_LOG_OPT_STATS
#
# | Default: "true" | Controls whether the API will track API operation
# statistics used for populating "Requests" portion of "/op/appinfo" response
# body. Setting to 'false' is NOT recommended for production environments, as
# this info can be useful for troubleshooting.
#
# Affects: API
#==============================================================================
# export STIGMAN_DEV_LOG_OPT_STATS=
#==============================================================================
# STIGMAN_DEV_RESPONSE_VALIDATION
#
# | Default: "none" | Controls whether the API will perform response validation
# on API responses. If set to 'logOnly' the API will output log entries
# indicating deviations from the OAS specification. Intended for
# development/testing purposes. Available values: "none", "logOnly"
#
# Affects: API
#==============================================================================
# export STIGMAN_DEV_RESPONSE_VALIDATION=
#==============================================================================
# STIGMAN_DOCS_DIRECTORY
#
# | Default: "./docs" | The location of the documentation files, relative to
# the API source directory. Note that if running source from a clone of the
# GitHub repository, the docs are located at `../../docs/_build/html` relative
# to the API directory.
#
# Affects: API, Documentation
#==============================================================================
# export STIGMAN_DOCS_DIRECTORY=
#==============================================================================
# STIGMAN_DOCS_DISABLED
#
# | Default: "false" | Whether to *not* serve the project Documentation. NOTE:
# If you choose to serve the Client from the API container but not the
# Documentation, the links do the Docs on the home page will not work.
#
# Affects: Documentation
#==============================================================================
# export STIGMAN_DOCS_DISABLED=
#==============================================================================
# STIGMAN_EXPERIMENTAL_APPDATA
#
# | Default: "false" | Set to "true" to enable the experimental AppData
# import/export API endpoints and User Interface.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_EXPERIMENTAL_APPDATA=
#==============================================================================
# STIGMAN_EXPERIMENTAL_LOGSTREAM
#
# | Default: "true" | Set to "false" to disable the experimental WebSocket for
# streaming API logs and the corresponding User Interface.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_EXPERIMENTAL_LOGSTREAM=
#==============================================================================
# STIGMAN_LOG_LEVEL
#
# | Default: "3" | Controls the granularity of the generated log output, from 1
# to 4. Each level is inclusive of the ones before it. Level 1 will log only
# errors, level 2 includes warnings, level 3 includes status and transaction
# logs, and level 4 includes debug-level logs
#
# Affects: API
#==============================================================================
# export STIGMAN_LOG_LEVEL=
#==============================================================================
# STIGMAN_LOG_MODE
#
# | Default: "combined" | Controls whether the logs will create one “combined”
# log entry for http requests that includes both the request and response
# information; or two separate log entries, one for the request and one for the
# response, that can be correlated via a generated Request GUID in each entry
#
# Affects: API
#==============================================================================
# export STIGMAN_LOG_MODE=
#==============================================================================
# STIGMAN_JWKS_CACHE_MAX_AGE
#
# | Default: "10" | The time in minutes after which the API's cache of JWT
# signing keys is deemed stale and the API becomes unavailable. Cache refreshes
# are scheduled at intervals of half this value and also occur when an unknown
# signing key is presented. Scheduled refresh failures are retried every 10
# seconds.
#
# Affects: API
#==============================================================================
# export STIGMAN_JWKS_CACHE_MAX_AGE=
#==============================================================================
# STIGMAN_JWT_ASSERTION_CLAIM
#
# | Default: "jti" | The access token claim whose value is the OIDC provider's
# Assertion ID. Updates to this value trigger the API to update a User's
# "lastClaims" property. The claim MUST NOT be nested and MUST be a valid
# ECMAScript identifier. See :ref:`jwt_requirements` for token value format
# requirements.
#
# Affects: API
#==============================================================================
# export STIGMAN_JWT_ASSERTION_CLAIM=
#==============================================================================
# STIGMAN_JWT_AUD_VALUE
#
# | No default. | If present, a string which must be included in the access
# token "aud" claim for requests to endpoints requiring authorization. See
# :ref:`jwt_requirements` for token value format requirements.
#
# Affects: API
#==============================================================================
# export STIGMAN_JWT_AUD_VALUE=
#==============================================================================
# STIGMAN_JWT_EMAIL_CLAIM
#
# | Default: "email" | The access token claim whose value is the user's email
# address. The claim MUST NOT be nested and MUST be a valid ECMAScript
# identifier. See :ref:`jwt_requirements` for token value format requirements.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_JWT_EMAIL_CLAIM=
#==============================================================================
# STIGMAN_JWT_NAME_CLAIM
#
# | Default: "name" | The access token claim whose value is the user's full
# name. The claim MUST NOT be nested and MUST be a valid ECMAScript identifier.
# See :ref:`jwt_requirements` for token value format requirements.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_JWT_NAME_CLAIM=
#==============================================================================
# STIGMAN_JWT_PRIVILEGES_CLAIM
#
# | Default: "realm_access.roles" | The access token claim whose value is the
# user's privileges. The claim MAY be nested but SHOULD avoid invalid
# ECMAScript identifiers. See :ref:`jwt_requirements` for token value format
# requirements.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_JWT_PRIVILEGES_CLAIM=
#==============================================================================
# STIGMAN_JWT_SCOPE_CLAIM
#
# | Default: "scope" | The access token claim whose value is the user's scopes.
# Some OIDC Providers (Okta, Azure AD) use the claim "scp" to enumerate scopes.
# The claim MUST NOT be nested and MUST be a valid ECMAScript identifier. See
# :ref:`jwt_requirements` for token value format requirements.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_JWT_SCOPE_CLAIM=
#==============================================================================
# STIGMAN_JWT_SERVICENAME_CLAIM
#
# | Default: "clientId" | The access token claim whose value is the service
# account's client. The claim MUST NOT be nested and MUST be a valid ECMAScript
# identifier. See :ref:`jwt_requirements` for token value format requirements.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_JWT_SERVICENAME_CLAIM=
#==============================================================================
# STIGMAN_JWT_USERNAME_CLAIM
#
# | Default: "preferred_username" | The access token claim whose value is the
# user's username. The claim MUST NOT be nested and MUST be a valid ECMAScript
# identifier. See :ref:`jwt_requirements` for token value format requirements.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_JWT_USERNAME_CLAIM=
#==============================================================================
# STIGMAN_OIDC_CA_CERTS
#
# | No default. | The full path to a file with one or more PEM-encoded CA
# certificates for validating TLS connections to the OIDC Provider.
#
# Affects: API
#==============================================================================
# export STIGMAN_OIDC_CA_CERTS=
#==============================================================================
# STIGMAN_OIDC_PROVIDER
#
# | Default: "http://localhost:8080/auth/realms/stigman" | The base URL of the
# OIDC provider issuing signed JWTs for the API. The string "/.well-
# known/openid-configuration" will be appended when fetching metadata.
#
# Affects: API, Client
#==============================================================================
# export STIGMAN_OIDC_PROVIDER=
#==============================================================================
# STIGMAN_SWAGGER_ENABLED
#
# | Default: "false" | Whether to enable the SwaggerUI SPA at /api-docs
#
# Affects: API
#==============================================================================
# export STIGMAN_SWAGGER_ENABLED=
#==============================================================================
# STIGMAN_SWAGGER_OIDC_PROVIDER
#
# | Default: Value of "STIGMAN_OIDC_PROVIDER" | SwaggerUI override of the base
# URL of the OIDC provider issuing signed JWTs for the API. The string
# "/.well-known/openid-configuration" will be appended by the SwaggerUI when
# fetching metadata.
#
# Affects: API
#==============================================================================
# export STIGMAN_SWAGGER_OIDC_PROVIDER=
#==============================================================================
# STIGMAN_SWAGGER_REDIRECT
#
# | Default: "http://localhost:54000/api-docs/oauth2-redirect.html" | The
# redirect URL sent by SwaggerUI to the OIDC provider when authorizing
#
# Affects: API
#==============================================================================
# export STIGMAN_SWAGGER_REDIRECT=
#==============================================================================
# STIGMAN_SWAGGER_SERVER
#
# | Default: "http://localhost:54000/api" | The API server URL relative to the
# SwaggerUI
#
# Affects: API
#==============================================================================
# export STIGMAN_SWAGGER_SERVER=
./stig-manager-linuxstatic
================================================
FILE: api/nuwcdivnpt-bot.gpg.asc
================================================
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQENBGXcsB0BCADIpexQoymA+0AGb9ojtisErQ5cp+xWv3SlPd5kOhuCpbhRhTnB
yQMBr50jqpPZeDtV80V9zyrGg+yLy4MdWM0sBIaW9ixDYeOShRei/GKHVrKxvJI7
YQLZhkng4LqQLgI1AimEzBm5roqfrDQoEnvsj8PbD3iXj7kPrPoUeqZ/3DIVIvKw
DtwfiWb7ycWJjjWe9g9F6T4YLbAidNVwo8QAnGrr7YFKtqhKYpjkK8ZHIDArpzVU
kqTeFJpkC9MchTLmYMLdgjfJAV/NcA7NA+8pUC+jIoT7oLkMgw47iH6ifjarw2+w
HUGuOrhpBF9WCW9OUlJmknjUQEeJeUYn5bXjABEBAAG0Xm51d2NkaXZucHQtYm90
QHVzZXJzLm5vcmVwbHkuZ2l0aHViLmNvbSAoU3RpZ21hbktleSkgPG51d2NkaXZu
cHQtYm90QHVzZXJzLm5vcmVwbHkuZ2l0aHViLmNvbT6JAVQEEwEKAD4WIQRR1CQf
lX8LfXypLo8UO6ovUu6kagUCZdywHQIbLwUJEswDAAULCQgHAgYVCgkICwIEFgID
AQIeAQIXgAAKCRAUO6ovUu6kagZXB/oDogvKYf5vDc8Cu2mrvtGbKO2VXDeLHQJ4
N1X/ZK/Lr4RTZFYDqHJPiqJYlhg58sR+EDsy2HWI3Qxpk7C65SrEF0CwEfNbcHtH
71g7KwHrgDEJw46yCmrt61pjAXVCeokVDPpUozYFoZoCRUHPpWDKEhcR2sizhOeh
0HCOcV2yq308IZKzemAaJU9sAKcjHNB7RQkNbLl50/awINQY0F2kFCUItI8GQ9JA
1+belDh0x5r2dQWCT4O2IIJjUhnKdoMovtp2TlU/ynpKKt781CKF7L548r35eaSM
KRvO2kdsvFuvYe3372kkpkT8edEtxduJnqzZMWyINV43mtCk1GV/uQENBGXcsB0B
CADJtfxgwXWBt3XY0s5iBKPFZFkYEgBKrFJF5YHJV2o8P6+AWIg03KynoJg0yf0h
006tTegUYi53NJpUACUtkRRaDAy4g3xV4bLfK+aN50GWGqIdlIeFeaq93RYLgwL3
GTB/msHoA6CTlQSrSIpjxeqifBPKcklq540AVR4aenntqEjHjpxEjkfzeB0nM1kA
u/4H9N8/B8FM4PqOzF5YlTaTK/UtCJU6TqMTTAg0VMlZjRRItjUUt3Oq+4bOakeX
F+JUiOaYaaYO2OJGiLm9HMuaRSiZGaothkZ/C5LgtkDqIGVcCMgYH0L4l+14IaVJ
iu60rX9Yhca0OOa9gqbR4VQLABEBAAGJAnIEGAEKACYWIQRR1CQflX8LfXypLo8U
O6ovUu6kagUCZdywHQIbLgUJEswDAAFACRAUO6ovUu6kasB0IAQZAQoAHRYhBHS9
Eu1c1I822bsN1VTlnNMfBHn8BQJl3LAdAAoJEFTlnNMfBHn8fAgH/RBVKMde+uEt
18c9gYXLInBu1qvzFIbYpH2hUHXSZcvdaj5AH7i6OF2Ix0jQiaFrnY14FawQkofp
Kd2uYjgyqbdKqn+wTwQhFGgyy5PQBuoLyKmlLXJgIHdsjsmMckDG6R6cA7du4IZx
AUCYsJEoAcnQXuP/XRXDiu8ODpOkMtqnmUn74gDtTALQ5j9mMwVrm7TfT0lFsjj5
W8I2SqZS4YQWKIfdbtUmqHWrzWwVYbzBBkK34YkaFdHd7YpLFSpGUJRgkQfPCu2U
cuO1Tn25VaYaw8xTstk5ul/3sPyuGvbaJnvFBtt+xQgQo6H0+aAbhDDxzxrhtUTg
0MPOw657viZijwf/Vgj1WfpXCxY6v3B4Qghg3dOgsQDAinrWM9xaYueT9bkBWjnD
fZ4Z3iNfUipLFDwJ2XeRBz5MQGwK3d5N11xDMXnYO6IH5m0+0vSLmh12hWQYdGAa
pedI3qbKsZ4/UQfG8ZfKyeBUunZDWNTbR61rFKi+ZNb4W4vF5pVX4kLIIzcJpqa7
8+cUWuD5jUKJt9fZ0cEUlLmZqJ7jsseHE81L2sULIo74p2xgGX1kGpNw5/oyyHRf
/Rf7n9Wqs21lvHK4cqIpmTTUxkEOVomoB7LWlrqhUNMEPmnJes5oWkfN/t1euy8o
OJ/jXthJZVWrxBzZtOmsDMQmJNhTXhgTxlEzvQ==
=b4ti
-----END PGP PUBLIC KEY BLOCK-----
================================================
FILE: api/pkg.config.json
================================================
{
"name": "stig-manager",
"pkg": {
"scripts": ["./source/controllers/**/*.js", "./source/service/**/*.js"],
"assets": [
"../client/dist/**/*",
"../docs/_build/html",
"./source/service/**/*.sql",
"./source/node_modules/csv-stringify/**/*",
"./source/node_modules/swagger-ui-dist/**/*",
"./source/node_modules/axios/**/*",
"./source/utils/*.xlsx"
],
"targets": ["node24-win", "node24-linuxstatic"],
"outputPath": "./bin"
}
}
================================================
FILE: api/source/README.md
================================================
================================================
FILE: api/source/bootstrap/bootstrapUtils.js
================================================
const path = require('node:path')
const logger = require('../utils/logger')
const extensionCheck = require('./extensionCheck')
function modulePathResolver( handlersPath, route, apiDoc ) {
const pathKey = route.openApiRoute.substring(route.basePath.length)
const schema = apiDoc.paths[pathKey][route.method.toLowerCase()]
const controller = schema.tags[0]
const operationId = schema['operationId']
const modulePath = path.join(handlersPath, controller)
const handler = require(modulePath)
if (handler[operationId] === undefined) {
throw new Error(
`Could not find a [${operationId}] function in ${modulePath} when trying to route [${route.method} ${route.expressRoute}].`,
)
}
return extensionCheck.bind(handler[operationId])
}
function buildResponseValidationConfig(willValidateResponse) {
if (willValidateResponse){
return {
onError: (error, body, req) => {
logger.writeError('rest', 'responseValidation', {
error,
request: logger.serializeRequest(req),
body
})
}
}
}
else {
return false
}
}
function logAppConfig(config) {
logger.writeInfo('bootstrapUtils', 'starting bootstrap', {
version: config.version,
env: logger.serializeEnvironment(),
dirname: __dirname,
cwd: process.cwd()
})
logger.writeInfo('bootstrapUtils', 'configuration', config)
}
module.exports = {
modulePathResolver,
buildResponseValidationConfig,
logAppConfig
}
================================================
FILE: api/source/bootstrap/client.js
================================================
const express = require('express')
const path = require('path')
const writer = require('../utils/writer')
const logger = require('../utils/logger')
const config = require('../utils/config')
function serveClient(app) {
if (config.client.disabled) {
logger.writeDebug('serveClient', 'client', {message: 'client disabled'})
return
}
try {
serveClientEnv(app)
serveStaticFiles(app)
logger.writeDebug('serveClient', 'client', { message: 'succeeded setting up client' })
}
catch (err) {
logger.writeError('serveClient', 'client', {message: err.message, stack: err.stack})
}
}
function getClientEnv(){
const envJS =
`const STIGMAN = {
Env: {
version: "${config.version}",
consoleMode: "${config.client.consoleMode}",
apiBase: "${config.client.apiBase}",
displayAppManagers: ${config.client.displayAppManagers},
stateEvents: ${config.client.stateEvents},
welcome: {
image: "${config.client.welcome.image}",
title: "${config.client.welcome.title.replace(/"/g, '\\"')}",
message: "${config.client.welcome.message.replace(/"/g, '\\"')}",
link: "${config.client.welcome.link}"
},
commit: {
branch: "${config.commit.branch}",
sha: "${config.commit.sha}",
tag: "${config.commit.tag}",
describe: "${config.commit.describe}"
},
oauth: {
authority: "${config.client.authority}",
clientId: "${config.client.clientId}",
extraScopes: "${config.client.extraScopes ?? ''}",
scopePrefix: "${config.client.scopePrefix ?? ''}",
responseMode: "${config.client.responseMode}",
reauthAction: "${config.client.reauthAction}",
strictPkce: ${config.client.strictPkce},
audienceValue: "${config.oauth.audienceValue ?? ''}",
claims: ${JSON.stringify(config.oauth.claims)},
idleTimeoutUser: ${config.client.idleTimeoutUser},
idleTimeoutAdmin: ${config.client.idleTimeoutAdmin},
},
experimental: {
appData: "${config.experimental.appData}",
logStream: "${config.experimental.logStream}"
}
}
}`
return envJS
}
function serveClientEnv(app){
const envJS = getClientEnv()
app.get('/js/Env.js', function (req, res) {
req.component = 'static'
writer.writeWithContentType(res, { payload: envJS, contentType: "application/javascript" })
})
}
function serveStaticFiles(app){
const staticPath = path.join(__dirname, "../", config.client.directory)
logger.writeDebug('serveStaticFiles', 'client', {client_static: staticPath})
const expressStatic = express.static(staticPath)
app.use('/', (req, res, next) => {
req.component = 'static'
expressStatic(req, res, next)
})
}
module.exports = {
serveClient,
}
================================================
FILE: api/source/bootstrap/dependencies.js
================================================
const logger = require('../utils/logger')
const auth = require('../utils/auth')
const db = require('../service/utils')
const { serializeError } = require('../utils/serializeError')
const state = require('../utils/state')
async function initializeDependencies() {
try {
await Promise.all([
auth.initializeAuth(),
db.initializeDatabase()
])
}
catch (e) {
logger.writeError('dependencies', 'fail', {message:'Unable to setup dependencies'})
state.setState('fail')
}
}
module.exports = {
initializeDependencies
}
================================================
FILE: api/source/bootstrap/docs.js
================================================
const express = require('express')
const path = require('path')
const fs = require('fs')
const logger = require('../utils/logger')
const config = require('../utils/config')
const swaggerUi = require('swagger-ui-express')
const jsyaml = require('js-yaml')
function serveDocs(app) {
if (config.docs.disabled) {
logger.writeDebug('serveDocs', 'client', {message: 'documentation disabled'})
return
}
try {
app.use('/docs', express.static(path.join(__dirname, "../", config.docs.docsDirectory)))
logger.writeDebug('serveDocs', 'client', {message: 'succeeded setting up documentation'})
}
catch (err) {
logger.writeError('serveDocs', 'client', {message: err.message, stack: err.stack})
}
}
function serveApiDocs(app) {
const oasDoc = getOAS()
if (config.swaggerUi.enabled) {
configureSwaggerUI(app, oasDoc)
}
else
{
logger.writeDebug('serveApiDocs', 'SwaggerUI', { message: 'Swagger UI is disabled in configuration' })
}
}
function getOAS(){
// Read and modify OpenAPI specification
const apiSpecPath = path.join(__dirname, '../specification/stig-manager.yaml')
let spec = fs.readFileSync(apiSpecPath, 'utf8')
let oasDoc = jsyaml.load(spec)
// Replace with config values
oasDoc.info.version = config.version
oasDoc.servers[0].url = config.swaggerUi.server
oasDoc.components.securitySchemes.oauth.openIdConnectUrl = `${config.client.authority}/.well-known/openid-configuration`
config.definition = oasDoc
return oasDoc
}
function configureSwaggerUI(app, oasDoc){
app.use('/api-docs', swaggerUi.serve, swaggerUi.setup(oasDoc, null, {
oauth2RedirectUrl: config.swaggerUi.oauth2RedirectUrl,
oauth: {
usePkceWithAuthorizationCodeGrant: true
}
}))
app.get(['/swagger.json','/openapi.json'], function(req, res) {
res.json(oasDoc)
})
logger.writeDebug('configureSwaggerUI', 'client', {message: 'succeeded setting up swagger-ui'})
}
module.exports = { serveDocs, serveApiDocs }
================================================
FILE: api/source/bootstrap/errorHandlers.js
================================================
const logger = require('../utils/logger')
const smErrors = require('../utils/error')
const { serializeError } = require('../utils/serializeError')
const path = require('path')
function configureErrorHandlers(app) {
// express-openapi-validator does not expose top-level HttpError in their index.js.
// We can get it from framework.types.js
// CAUTION: We break here if express-openapi-validator changes this
const eovPath = path.dirname(require.resolve('express-openapi-validator'))
const eovErrors = require(path.join(eovPath, 'framework', 'types.js'))
app.use((err, req, res, next) => {
if (!(err instanceof smErrors.SmError) && !(err instanceof eovErrors.HttpError)) {
logger.writeError('rest', 'error', {
request: logger.serializeRequest(req),
error: serializeError(err)
})
}
res.errorBody = { error: err.message, code: err.code, detail: err.detail}
if (err.status === 500 || !(err.status)) res.errorBody.stack = err.stack
if (!res._headerSent) {
res.status(err.status || 500).header(err.headers).json(res.errorBody)
}
else {
res.write(JSON.stringify(res.errorBody) + '\n')
res.end()
}
})
}
module.exports = configureErrorHandlers
================================================
FILE: api/source/bootstrap/extensionCheck.js
================================================
const SmError = require('../utils/error')
function extensionCheck(req, res, next) {
if (req.openapi?.schema['x-elevation-required'] && !req.query.elevate) {
next(new SmError.ElevationError())
return
}
this(req, res, next)
}
module.exports = extensionCheck
================================================
FILE: api/source/bootstrap/middlewares.js
================================================
const path = require('node:path')
const multer = require('multer')
const express = require('express')
const cors = require('cors')
const { middleware: openApiMiddleware } = require('express-openapi-validator')
const config = require('../utils/config')
const { modulePathResolver, buildResponseValidationConfig } = require('./bootstrapUtils')
const auth = require('../utils/auth')
const configureErrorHandlers = require('./errorHandlers')
const { requestLogger } = require('../utils/logger')
const state = require('../utils/state')
const logger = require('../utils/logger')
function configureMiddleware(app) {
// Must run before any app.use() call: Express's lazyrouter binds the query
// parser at the moment the first middleware is registered and ignores
// later changes.
app.set('query parser', 'simple')
const middlewareConfigFunctions = [
configureMulter,
configureExpress,
configureCors,
configureLogging,
configureServiceCheck,
configureAuth,
configureOpenApi,
configureErrorHandlers,
]
logger.writeInfo('middleware', 'bootstrap', { message: 'configuring middleware' })
for (const middlewareConfigFunction of middlewareConfigFunctions) {
middlewareConfigFunction(app)
}
logger.writeInfo('middleware', 'bootstrap', { message: 'middleware configured' })
}
function configureMulter(app) {
let storage = multer.memoryStorage()
const upload = multer({
storage,
limits: {
fileSize: parseInt(config.http.maxUpload)
}
})
app.use(upload.single('importFile'))
}
function configureCors(app) {
app.use(cors())
}
function configureLogging(app) {
app.use(requestLogger)
}
function configureServiceCheck(app) {
app.use((req, res, next) => {
try {
if (
state.currentState !== 'available' && req.url.startsWith('/api') && !req.url.startsWith('/api/op/state')) {
res.status(503).json(state.apiState)
}
else {
next()
}
}
catch (e) {
next(e)
}
})
}
function configureAuth(app) {
app.use('/api', auth.validateToken)
app.use('/api', auth.setupUser)
}
function configureExpress(app) {
app.use(express.urlencoded( {extended: true}))
app.use(express.json({
strict: false, // allow root to be any JSON value, per https://datatracker.ietf.org/doc/html/rfc7159#section-2
limit: parseInt(config.http.maxJsonBody)
})) //Handle JSON request body
}
function configureOpenApi(app) {
const apiSpecPath = path.join(__dirname, '../specification/stig-manager.yaml')
app.use( "/api", openApiMiddleware ({
apiSpec: apiSpecPath,
validateRequests: {
coerceTypes: false,
allowUnknownQueryParameters: false,
},
validateResponses: buildResponseValidationConfig(config.settings.responseValidation === "logOnly"),
validateApiSpec: true,
$refParser: {
mode: 'dereference',
},
operationHandlers: {
basePath: path.join(__dirname, '../controllers'),
resolver: modulePathResolver,
},
validateSecurity: {
handlers:{
oauth: auth.validateOauthSecurity
}
},
fileUploader: false
}))
}
module.exports = configureMiddleware
================================================
FILE: api/source/bootstrap/server.js
================================================
const logger = require('../utils/logger')
const path = require('node:path')
const logSocket = require('../utils/logSocket')
const state = require('../utils/state')
const OperationSvc = require(`../service/OperationService`)
const { serializeError } = require('../utils/serializeError')
const config = require('../utils/config')
const { initializeDependencies } = require('./dependencies')
function setupTls() {
if (config.http.tls?.key_file && config.http.tls?.cert_file) {
const fs = require('node:fs')
let key, cert
try {
key = fs.readFileSync(config.http.tls.key_file)
} catch (e) {
logger.writeError('server', 'tls_key_read_error', {message: `Failed reading TLS key file: ${config.http.tls.key_file}`, error: serializeError(e)})
throw e
}
try {
cert = fs.readFileSync(config.http.tls.cert_file)
} catch (e) {
logger.writeError('server', 'tls_cert_read_error', {message: `Failed reading TLS certificate file: ${config.http.tls.cert_file}`, error: serializeError(e)})
throw e
}
const tlsOptions = {
key: key,
cert: cert
}
if (config.http.tls.key_passphrase) {
tlsOptions.passphrase = config.http.tls.key_passphrase
}
return tlsOptions
} else {
return null
}
}
async function startServer(app, startTime) {
let server
if (config.http.tls?.key_file && config.http.tls?.cert_file) {
const https = require('node:https')
const tlsOptions = setupTls()
logger.writeInfo('server', 'tls_enabled', {message: 'Creating server with TLS/HTTPS'})
server = https.createServer(tlsOptions, app)
} else {
const http = require('node:http')
server = http.createServer(app)
}
server.on('upgrade', (request) => {
logger.writeInfo('server', 'upgrade-request', {
url: request.url,
headers: request.headers,
remoteAddress: request.socket.remoteAddress
})
})
const onListenError = (e) => {
logger.writeError('server', 'shutdown', { message: `Server failed establishing or while listening on port ${config.http.port}`, error: serializeError(e) })
state.setState('fail')
}
server.on('error', onListenError)
await logSocket.setupLogSocket(server, path.join(__dirname, '../specification/log-socket.yaml'))
server.listen(config.http.port, async function () {
server.removeListener('error', onListenError)
logger.writeInfo('server', 'listening', {
port: config.http.port,
api: '/api',
client: config.client.disabled ? undefined : '/',
documentation: config.docs.disabled ? undefined : '/docs',
swagger: config.swaggerUi.enabled ? '/api-docs' : undefined
})
await initializeDependencies()
// Set/change classification if indicated
await applyConfigurationSettings()
logStartupDuration(startTime)
})
}
async function applyConfigurationSettings() {
if (config.settings.setClassification) {
await OperationSvc.setConfigurationItem('classification', config.settings.setClassification)
}
}
function logStartupDuration(startTime) {
const endTime = process.hrtime.bigint()
logger.writeInfo('server', 'started', {
durationS: Number(endTime - startTime) / 1e9
})
}
module.exports = startServer
================================================
FILE: api/source/bootstrap/signals.js
================================================
const state = require('../utils/state')
const logger = require('../utils/logger')
// This function sets up signal handlers for the process
// and listens for SIGINT, SIGTERM, and SIGHUP signals
module.exports.setupSignalHandlers = () => {
const signals = ['SIGINT', 'SIGTERM', 'SIGHUP'];
const signalHandler = (signal) => {
logger.writeInfo('signals','signal', {signal})
state.setState('stop')
}
for (const signal of signals) {
process.on(signal, signalHandler)
}
}
================================================
FILE: api/source/controllers/Asset.js
================================================
'use strict';
const writer = require('../utils/writer')
const config = require('../utils/config')
const escape = require('../utils/escape')
const AssetService = require(`../service/AssetService`)
const CollectionService = require(`../service/CollectionService`)
const Collection = require('./Collection')
const Security = require('../utils/roles')
const dbUtils = require(`../service/utils`)
const {XMLBuilder} = require("fast-xml-parser")
const SmError = require('../utils/error')
const {escapeForXml} = require('../utils/escape')
module.exports.createAsset = async function createAsset (req, res, next) {
try {
let projections = req.query.projection
let assets = req.body
const collectionId = req.body.collectionId
const grant = req.userObject.grants[collectionId]
if (!grant || grant.roleId < 3) throw new SmError.PrivilegeError()
assets.noncomputing = assets.hasOwnProperty("noncomputing") ? (assets.noncomputing ? 1 : 0) : 0
assets = [assets]
const failures = await dbUtils.createAssetValidation({assets, collectionId})
if (failures.length > 0) {
throw new SmError.UnprocessableError(failures)
}
let assetId
assetId = await AssetService.createAssets({assets, collectionId, svcStatus: res.svcStatus})
const response = await AssetService.getAsset({
assetId,
projections,
grant,
})
res.status(201).json(response)
}
catch (err) {
next(err)
}
}
module.exports.createAssets = async function createAssets (req, res, next) {
try {
let projections = req.query.projection
const collectionId = req.params.collectionId
let assets = req.body
let dryRun = req.query.dryRun
const grant = req.userObject.grants[collectionId]
if (!grant || grant.roleId < 3) throw new SmError.PrivilegeError()
// if batch normalize assets (put collection Id into the asset object) and make non-computing a 'boolean int'
assets = assets.map(asset => ({
...asset,
collectionId,
noncomputing: asset.hasOwnProperty("noncomputing") ? (asset.noncomputing ? 1 : 0) : 0
}))
const failures = await dbUtils.createAssetValidation({assets, collectionId})
if (failures.length > 0) {
res.status(200).json({
error: 'Validation Error',
detail: failures
})
return
}
if(dryRun) {
res.status(204).send()
return
}
let assetIds
assetIds = await AssetService.createAssets( {assets, collectionId, svcStatus: res.svcStatus})
const response = await AssetService.getAssets({
filter: {
collectionId: collectionId,
assetIds,
},
projections,
grant,
})
res.status(201).json(response)
}
catch (err) {
next(err)
}
}
module.exports.deleteAsset = async function deleteAsset (req, res, next) {
try {
let projections = req.query.projection
const { assetId, grant } = await getAssetInfoAndVerifyAccess(req)
const response = await AssetService.getAsset({assetId, projections, grant})
await AssetService.deleteAsset(assetId, req.userObject.userId, res.svcStatus)
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.removeStigFromAsset = async function (req, res, next) {
try {
let benchmarkId = req.params.benchmarkId
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req)
await AssetService.removeStigFromAsset({assetId, benchmarkId, grant, svcStatus: res.svcStatus})
const response = await AssetService.getStigsByAsset({assetId, grant})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.removeStigsFromAsset = async function removeStigsFromAsset (req, res, next) {
try {
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req)
await AssetService.removeStigsFromAsset(assetId, grant, res.svcStatus)
const response = await AssetService.getStigsByAsset({assetId, grant})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.exportAssets = async function exportAssets (projections, elevate, userObject) {
// let assets = await AssetService.getAssets({projections})
// return assets
}
module.exports.getAsset = async function (req, res, next) {
try {
const assetId = req.params.assetId
const projections = req.query.projection
const grant = await dbUtils.getGrantByAssetId(assetId, req.userObject.grants)
if (!grant) throw new SmError.PrivilegeError()
const response = await AssetService.getAsset({assetId, projections, grant})
if (!response) throw new SmError.PrivilegeError()
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getAssets = async function (req, res, next) {
try {
const collectionId = req.query.collectionId
const name = req.query.name
const nameMatch = req.query['name-match']
const benchmarkId = req.query.benchmarkId
const metadata = req.query.metadata
const labelIds = req.query.labelId
const labelNames = req.query.labelName
const labelMatch = req.query.labelMatch
const projections = req.query.projection
const grant = req.userObject.grants[collectionId]
if (!grant) throw new SmError.PrivilegeError('No Grant in Collection')
const response = await AssetService.getAssets({
filter: {
collectionId,
labels: {labelIds, labelNames, labelMatch},
name,
nameMatch,
benchmarkId,
metadata
},
projections,
grant
})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getStigsByAsset = async function (req, res, next) {
try {
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Restricted)
const response = await AssetService.getStigsByAsset({assetId, grant} )
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getChecklistByAssetStig = async function getChecklistByAssetStig (req, res, next) {
try {
const assetId = req.params.assetId
const benchmarkId = req.params.benchmarkId
const revisionStr = req.params.revisionStr
const format = req.query.format || 'json'
const projections = req.query.projection
const access = await dbUtils.getUserAssetStigAccess({assetId, benchmarkId, grants: req.userObject.grants})
if (access === 'none') throw new SmError.PrivilegeError()
const checklist = await AssetService.getChecklistByAssetStig(assetId, benchmarkId, revisionStr, format, projections, req.userObject )
if (format.startsWith('json')) {
res.json(format === 'json-access' ? {access, checklist} : checklist)
return
}
const dateString = escape.filenameComponentFromDate()
const fileBasename = `${checklist.marking}_${checklist.assetName}-${benchmarkId}-${checklist.revisionStrResolved}`
if (format === 'cklb') {
checklist.cklb.title = fileBasename
writer.writeInlineFile(res, JSON.stringify(checklist.cklb), `${fileBasename}_${dateString}.cklb`, 'application/json') // revisionStrResolved provides specific rev string, if "latest" was asked for.
}
else if (format === 'ckl') {
const builder = new XMLBuilder({
attributeNamePrefix : "@_",
textNodeName : "#text",
ignoreAttributes : true,
format: true,
indentBy: " ",
supressEmptyNode: false,
processEntities: false,
tagValueProcessor: escapeForXml,
attrValueProcessor: escapeForXml
})
let xml = `\n\n\n`
xml += builder.build(checklist.xmlJs)
writer.writeInlineFile(res, xml, `${fileBasename}_${dateString}.ckl`, 'application/xml') // revisionStrResolved provides specific rev string, if "latest" was asked for.
}
else if (format === 'xccdf') {
const builder = new XMLBuilder({
attributeNamePrefix : "@_",
textNodeName : "#text",
ignoreAttributes : false,
cdataTagName: "__cdata",
cdataPositionChar: "\\c",
format: true,
indentBy: " ",
supressEmptyNode: true,
processEntities: false,
tagValueProcessor: escapeForXml,
attrValueProcessor: escapeForXml
})
let xml = `\n\n\n`
xml += builder.build(checklist.xmlJs)
writer.writeInlineFile(res, xml, `${fileBasename}-xccdf_${dateString}.xml`, 'application/xml') // revisionStrResolved provides specific rev string, if "latest" was asked for.
}
}
catch (err) {
next(err)
}
}
module.exports.getChecklistByAsset = async function (req, res, next) {
try {
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Restricted)
const format = req.query.format //default of .ckl provided by EOV
const assetResponse = await AssetService.getAsset({assetId, projections: ['stigs'], grant} )
const availableBenchmarkIds = assetResponse.stigs.map( r => r.benchmarkId )
if (availableBenchmarkIds.length === 0) {
res.status(204).end()
return
}
const requestedBenchmarkIds = req.query.benchmarkId ?? availableBenchmarkIds
if (!requestedBenchmarkIds.every( requestedBenchmarkId => availableBenchmarkIds.includes(requestedBenchmarkId))) {
throw new SmError.ClientError('Asset is not mapped to all requested benchmarkIds')
}
const stigs = requestedBenchmarkIds.map( benchmarkId => ({benchmarkId, revisionStr: 'latest'}) )
const response = await AssetService.getChecklistByAsset(assetId, stigs, format)
const dateString = escape.filenameComponentFromDate()
if (format === 'cklb') {
writer.writeInlineFile(res, JSON.stringify(response.cklb), `${response.assetName}_${dateString}.cklb`, 'application/json')
}
else if (format === 'ckl') {
const builder = new XMLBuilder({
attributeNamePrefix : "@_",
textNodeName : "#text",
ignoreAttributes : true,
format: true,
indentBy: " ",
supressEmptyNode: false,
processEntities: false,
tagValueProcessor: escapeForXml,
attrValueProcessor: escapeForXml
})
let xml = `\n\n\n`
xml += builder.build(response.xmlJs)
writer.writeInlineFile(res, xml, `${response.marking}_${response.assetName}_${dateString}.ckl`, 'application/xml')
}
}
catch (err) {
next(err)
}
}
module.exports.getAssetsByStig = async function getAssetsByStig (req, res, next) {
try {
const benchmarkId = req.params.benchmarkId
const labelIds = req.query.labelId
const labelNames = req.query.labelName
const labelMatch = req.query.labelMatch
const projections = req.query.projection
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const response = await AssetService.getAssetsByStig({
collectionId,
benchmarkId,
labels: {labelIds, labelNames, labelMatch},
projections,
grant
})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.replaceAsset = async function replaceAsset (req, res, next) {
try {
const projections = req.query.projection
const body = req.body
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req)
const currentAsset = await AssetService.getAsset({assetId, projections, grant})
// Check if the asset is being transferred
const transferring = body.collectionId && currentAsset.collection.collectionId !== body.collectionId ?
{oldCollectionId: currentAsset.collection.collectionId, newCollectionId: body.collectionId} : null
if (transferring) {
// If so, Check if the user has an appropriate grant to the asset's updated collection
const updatedCollectionGrant = req.userObject.grants[body.collectionId]
if ( !updatedCollectionGrant || updatedCollectionGrant.roleId < 3 ) {
throw new SmError.PrivilegeError(`insufficient privilege in destination collection to transfer this asset.`)
}
}
await AssetService.updateAsset({
assetId,
body,
transferring,
svcStatus: res.svcStatus
})
const asset = await AssetService.getAsset({assetId, projections, grant})
res.json(asset)
}
catch (err) {
next(err)
}
}
module.exports.attachAssetsToStig = async function attachAssetsToStig (req, res, next) {
try {
let benchmarkId = req.params.benchmarkId
let assetIds = req.body
let projections = req.query.projection
const { collectionId, grant } = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
let collection = await CollectionService.getCollection( collectionId, ['assets'], false, req.userObject)
let collectionAssets = collection.assets.map( a => a.assetId)
if (assetIds.every( a => collectionAssets.includes(a))) {
await AssetService.attachAssetsToStig( collectionId, benchmarkId, assetIds )
let response = await AssetService.getAssetsByStig({collectionId, benchmarkId, projections, grant})
res.json(response)
}
else {
throw new SmError.PrivilegeError('One or more assetId is not a Collection member.')
}
}
catch (err) {
next(err)
}
}
module.exports.attachStigToAsset = async function attachStigToAsset (req, res, next) {
try {
let benchmarkId = req.params.benchmarkId
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Manage)
await AssetService.attachStigToAsset({
assetId,
benchmarkId,
grant,
svcStatus: res.svcStatus
})
const response = await AssetService.getStigsByAsset({assetId, grant})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.updateAsset = async function updateAsset (req, res, next) {
try {
const projections = req.query.projection
const body = req.body
const {assetId, grant} = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Manage)
// If this user has no grants permitting access to the asset, the response will be undefined
const currentAsset = await AssetService.getAsset({assetId, projections, grant} )
// if (!currentAsset) {
// throw new SmError.PrivilegeError('User has insufficient privilege to modify this asset.')
// }
// // Check if the user has an appropriate grant to the asset's collection
// const currentCollectionGrant = req.userObject.grants[currentAsset.collection.collectionId]
// if ( !currentCollectionGrant || currentCollectionGrant.roleId < 3 ) {
// throw new SmError.PrivilegeError(`User has insufficient privilege in collectionId ${currentAsset.collection.collectionId} to modify this asset.`)
// }
// Check if the asset's collectionId is being changed
const transferring = body.collectionId && currentAsset.collection.collectionId !== body.collectionId ?
{oldCollectionId: currentAsset.collection.collectionId, newCollectionId: body.collectionId} : null
if (transferring) {
// If so, Check if the user has an appropriate grant to the asset's updated collection
const updatedCollectionGrant = req.userObject.grants[body.collectionId]
if ( !updatedCollectionGrant || updatedCollectionGrant.roleId < 3 ) {
throw new SmError.PrivilegeError(`User has insufficient privilege in destination collection to transfer this asset.`)
}
}
await AssetService.updateAsset({
assetId,
body,
projections,
transferring,
currentCollectionId: currentAsset.collection.collectionId,
userObject: req.userObject,
svcStatus: res.svcStatus
})
const response = await AssetService.getAsset({assetId, projections, grant})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getAssetMetadata = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Restricted)
let result = await AssetService.getAssetMetadata(assetId, req.userObject)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.patchAssetMetadata = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req)
let metadata = req.body
await AssetService.patchAssetMetadata(assetId, metadata)
let result = await AssetService.getAssetMetadata(assetId)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.putAssetMetadata = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req)
let body = req.body
await AssetService.putAssetMetadata(assetId, body)
let result = await AssetService.getAssetMetadata(assetId)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getAssetMetadataKeys = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Restricted)
let result = await AssetService.getAssetMetadataKeys(assetId, req.userObject)
if (!result) {
throw new SmError.NotFoundError('metadata keys not found')
}
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getAssetMetadataValue = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req, Security.ROLES.Restricted)
let key = req.params.key
let result = await AssetService.getAssetMetadataValue(assetId, key, req.userObject)
if (!result) {
throw new SmError.NotFoundError('metadata key not found')
}
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.putAssetMetadataValue = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req)
let key = req.params.key
let value = req.body
await AssetService.putAssetMetadataValue(assetId, key, value)
res.status(204).send()
}
catch (err) {
next(err)
}
}
module.exports.deleteAssetMetadataKey = async function (req, res, next) {
try {
let { assetId } = await getAssetInfoAndVerifyAccess(req)
let key = req.params.key
await AssetService.deleteAssetMetadataKey(assetId, key, req.userObject)
res.status(204).send()
}
catch (err) {
next(err)
}
}
module.exports.patchAssets = async function (req, res, next) {
try {
// feature supports delete only
const collectionId = getCollectionIdAndVerifyAccess(req, Security.ROLES.Manage)
const patchRequest = req.body
// optimization: replace below with targeted sql query, select from asset where assetId in ? and collectionId != ?
const collection = await CollectionService.getCollection( collectionId, ['assets'], false, req.userObject)
const collectionAssets = collection.assets.map( a => a.assetId)
if (!patchRequest.assetIds.every( a => collectionAssets.includes(a))) {
throw new SmError.PrivilegeError('One or more assetId is not a Collection member.')
}
await AssetService.deleteAssets(patchRequest.assetIds, req.userObject.userId, res.svcStatus)
res.json({
operation: 'deleted',
assetIds: patchRequest.assetIds
})
}
catch (err) {
next(err)
}
}
function getCollectionIdAndVerifyAccess(request, minimumRole = Security.ROLES.Manage) {
let collectionId = request.query.collectionId
const grant = request.userObject.grants[collectionId]
if (grant?.roleId < minimumRole || !grant) {
throw new SmError.PrivilegeError()
}
return collectionId
}
/**
* Retrieves asset information and verifies user access to the asset which the operation is effecting.
* Also, ensures that the user has sufficient access level to perform the operation.
* @param {Object} request - The request object.
* @returns {Promise} - A promise that resolves to an object containing the assetId and a grant.
* @throws {SmError.PrivilegeError} - user does not have sufficient access level or the asset does not exist.
*/
async function getAssetInfoAndVerifyAccess(request, roleId = Security.ROLES.Manage) {
const assetId = request.params.assetId
const row = await dbUtils.selectCollectionByAssetId(assetId)
const grant = request.userObject.grants[row?.collectionId]
// check if user has sufficient access level
if (!grant || grant.roleId < roleId) {
throw new SmError.PrivilegeError("Insufficient access to this asset's collection.")
}
return {assetId, grant}
}
================================================
FILE: api/source/controllers/Collection.js
================================================
'use strict';
const writer = require('../utils/writer')
const config = require('../utils/config')
const escape = require('../utils/escape')
const CollectionService = require(`../service/CollectionService`)
const AssetService = require(`../service/AssetService`)
const STIGService = require(`../service/STIGService`)
const UserService = require(`../service/UserService`)
const Serialize = require(`../utils/serializers`)
const Security = require('../utils/roles')
const SmError = require('../utils/error')
const Archiver = require('archiver')
const {XMLBuilder} = require("fast-xml-parser")
const {escapeForXml} = require('../utils/escape')
const dbUtils = require('../service/utils')
module.exports.defaultSettings = {
fields: {
detail: {
enabled: 'always',
required: 'always'
},
comment: {
enabled: 'findings',
required: 'findings'
}
},
status: {
canAccept: true,
resetCriteria: 'result',
minAcceptGrant: 3
},
history: {
maxReviews: 5
},
importOptions:{
autoStatus: {
fail: 'saved',
notapplicable: 'saved',
pass: 'saved'
},
unreviewed: 'commented',
unreviewedCommented: 'informational',
emptyDetail: 'replace',
emptyComment: 'ignore',
allowCustom: true
}
}
module.exports.createCollection = async function createCollection (req, res, next) {
try {
const projection = req.query.projection
const elevate = req.query.elevate
const body = req.body
if ( elevate || req.userObject.privileges.create_collection ) {
if (elevate && (body.settings !== undefined || body.labels !== undefined || body.metadata !== undefined)) {
throw new SmError.PrivilegeError('Elevated requests cannot set collection settings, labels, or metadata.')
}
if (!hasUniqueGrants(body.grants)) {
throw new SmError.UnprocessableError('Duplicate user or user group in grant array')
}
const userIds = body.grants.map(g => g.userId).filter(Boolean)
const invalidUserIds = await dbUtils.selectInvalidUserIds(userIds)
if (invalidUserIds.length > 0) {
throw new SmError.UserInconsistentError()
}
try {
const response = await CollectionService.createCollection( body, projection, req.userObject, res.svcStatus)
res.status(201).json(response)
}
catch (err) {
// This is MySQL specific, should abstract
if (err.code === 'ER_DUP_ENTRY') {
throw new SmError.UnprocessableError('Duplicate name exists.')
}
else {
throw err
}
}
}
else {
throw new SmError.PrivilegeError()
}
}
catch (err) {
next(err)
}
}
module.exports.deleteCollection = async function deleteCollection (req, res, next) {
try {
const elevate = req.query.elevate
const projections = req.query.projection
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Owner, true)
const response = await CollectionService.getCollection(collectionId, projections, elevate, req.userObject)
await CollectionService.deleteCollection(collectionId, req.userObject.userId)
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.exportCollections = async function exportCollections (projection, elevate, userObject) {
try {
return await CollectionService.queryCollections({projection, elevate})
}
catch (err) {
next(err)
}
}
module.exports.getChecklistByCollectionStig = async function getChecklistByCollectionStig (req, res, next) {
try {
const benchmarkId = req.params.benchmarkId
const revisionStr = req.params.revisionStr
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const response = await CollectionService.getChecklistByCollectionStig(collectionId, benchmarkId, revisionStr, req.userObject )
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getCollection = async function getCollection (req, res, next) {
try {
const projection = req.query.projection
const elevate = req.query.elevate
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted, true)
const response = await CollectionService.getCollection(collectionId, projection, elevate, req.userObject )
res.status(typeof response === 'undefined' ? 204 : 200).json(response)
}
catch (err) {
next(err)
}
}
module.exports.getCollections = async function getCollections (req, res, next) {
try {
const projections = req.query.projection
const elevate = req.query.elevate
const name = req.query.name
const nameMatch = req.query['name-match']
const metadata = req.query.metadata
const response = await CollectionService.queryCollections({
filter: {name, nameMatch, metadata},
projections,
elevate,
grants: req.userObject.grants,
userId: req.userObject.userId
})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getFindingsByCollection = async function getFindingsByCollection (req, res, next) {
try {
const aggregator = req.query.aggregator
const benchmarkId = req.query.benchmarkId
const assetId = req.query.assetId
const acceptedOnly = req.query.acceptedOnly
const projections = req.query.projection
const {collectionId, grant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const response = await CollectionService.getFindingsByCollection({collectionId, aggregator, benchmarkId, assetId, acceptedOnly, projections, grant})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getPoamByCollection = async function getPoamByCollection (req, res, next) {
try {
const {
aggregator,
benchmarkId,
assetId,
acceptedOnly,
date,
office,
status,
mccastPackageId,
mccastAuthName,
format
} = req.query
const defaults = {
date,
office,
status,
mccastPackageId,
mccastAuthName
}
const {collectionId, grant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const findings = await CollectionService.getFindingsByCollection({
collectionId, aggregator, benchmarkId, assetId, acceptedOnly,
projections: [
'rulesWithDiscussion',
'groups',
'assets',
'stigs',
'ccis'
],
grant})
const poFns = {
EMASS: Serialize.poamObjectFromFindings,
MCCAST: Serialize.mccastPoamObjectFromFindings
}
const xlsx = await Serialize.xlsxFromPoamObject(poFns[format](findings, defaults), format)
writer.writeInlineFile( res, xlsx, `POAM-${format}-${grant.name}_${escape.filenameComponentFromDate()}.xlsx`, 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet')
}
catch (err) {
next(err)
}
}
// module.exports.getStigAssetsByCollectionUser = async function getStigAssetsByCollectionUser (req, res, next) {
// try {
// const userId = req.params.userId
// const { collectionId } = await getCollectionInfoAndCheckPermission(req)
// const response = await CollectionService.getStigAssetsByCollectionUser(collectionId, userId, req.userObject )
// res.json(response)
// }
// catch (err) {
// next(err)
// }
// }
module.exports.getStigsByCollection = async function getStigsByCollection (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const labelIds = req.query.labelId
const labelNames = req.query.labelName
const labelMatch = req.query.labelMatch
const projections = req.query.projection
const response = await CollectionService.getStigsByCollection({collectionId, labelIds, labelNames, labelMatch, projections, grant})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getStigByCollection = async function getStigByCollection (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const benchmarkId = req.params.benchmarkId
const projections = req.query.projection
const response = await CollectionService.getStigsByCollection({collectionId, projections, grant, benchmarkId})
if (!response[0]) {
res.status(204)
}
res.json(response[0])
}
catch (err) {
next(err)
}
}
module.exports.replaceCollection = async function replaceCollection (req, res, next) {
try {
const elevate = req.query.elevate
const {collectionId, grant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const projection = req.query.projection
const body = req.body
if (elevate && (body.settings !== undefined || body.labels !== undefined || body.metadata !== undefined)) {
throw new SmError.PrivilegeError('Elevated requests cannot set collection settings, labels, or metadata.')
}
if (!hasUniqueGrants(body.grants)) {
throw new SmError.UnprocessableError('Duplicate user in grant array')
}
const userIds = body.grants.map(g => g.userId).filter(Boolean)
const invalidUserIds = await dbUtils.selectInvalidUserIds(userIds)
if (invalidUserIds.length > 0) {
throw new SmError.UserInconsistentError()
}
const existingGrants = (await CollectionService.getCollection(collectionId, ['grants'], false, req.userObject))
?.grants
.map(g => {
const flattenedGrant = {roleId: g.roleId}
if (g.user) {
flattenedGrant.userId = g.user.userId
}
else {
flattenedGrant.userGroupId = g.userGroup.userGroupId
}
return flattenedGrant
})
if (!elevate && (grant.roleId !== Security.ROLES.Owner && !requestedOwnerGrantsMatchExisting(body.grants, existingGrants))) {
throw new SmError.PrivilegeError('Cannot create or modify owner grants.')
}
let response = await CollectionService.replaceCollection(collectionId, body, projection, req.userObject, res.svcStatus)
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.updateCollection = async function updateCollection (req, res, next) {
try {
const elevate = req.query.elevate
const {collectionId, grant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const projection = req.query.projection
const body = req.body
if (elevate && (body.settings !== undefined || body.labels !== undefined || body.metadata !== undefined)) {
throw new SmError.PrivilegeError('Elevated requests cannot set collection settings, labels, or metadata.')
}
if (body.grants) {
if (!hasUniqueGrants(body.grants)) {
throw new SmError.UnprocessableError('Duplicate user in grant array')
}
const userIds = body.grants.map(g => g.userId).filter(Boolean)
const invalidUserIds = await dbUtils.selectInvalidUserIds(userIds)
if (invalidUserIds.length > 0) {
throw new SmError.UserInconsistentError()
}
const existingGrants = (await CollectionService.getCollection(collectionId, ['grants'], false, req.userObject ))
?.grants
.map(g => {
const flattenedGrant = {roleId: g.roleId}
if (g.user) {
flattenedGrant.userId = g.user.userId
}
else {
flattenedGrant.userGroupId = g.userGroup.userGroupId
}
return flattenedGrant
})
if (!elevate && (grant.roleId !== Security.ROLES.Owner && !requestedOwnerGrantsMatchExisting(body.grants, existingGrants))) {
throw new SmError.PrivilegeError('Cannot create or modify owner grants.')
}
}
let response = await CollectionService.updateCollection(collectionId, body, projection, req.userObject, res.svcStatus)
res.json(response)
}
catch (err) {
next(err)
}
}
function hasUniqueGrants(requestedGrants) {
const userItems = {}
const userGroupItems = {}
for (const grant of requestedGrants) {
if (userItems[grant.userId]) return false
if (userGroupItems[grant.userGroupId]) return false
const itemsObject = grant.userId ? userItems : userGroupItems
itemsObject[grant.userId ?? grant.userGroupId] = true
}
return true
}
function requestedOwnerGrantsMatchExisting(requestedGrants, existingGrants) {
const accumulateOwners = (accumulator, currentValue) => {
if (currentValue.roleId === Security.ROLES.Owner)
accumulator.push(currentValue.userId ? `U${currentValue.userId}` : `UG${currentValue.userGroupId}`)
return accumulator
}
const haveSameSet = (a, b) => {
return a.every(item => b.includes(item)) && b.every(item => a.includes(item))
}
const existingOwners = existingGrants.reduce(accumulateOwners, [])
const requestedOwners = requestedGrants.reduce(accumulateOwners, [])
return !(existingOwners.length !== requestedOwners.length || !haveSameSet(existingOwners, requestedOwners))
}
/**
* Retrieves collectionId and collection grant and checks user's access grant level or elevate.
* Also allows for elevate
* @param {Object} request - The request object.
* @param {number} minimumRole - The minimum rokle required. Defaults to Security.ROLES.Manage.
* @param {boolean} allowElevate - Whether to allow elevation of access level. Defaults to false.
* @returns {Promise} - An object containing the collectionId and grant.
* @throws {SmError.PrivilegeError} - If the user does not have sufficient privileges.
*/
async function getCollectionInfoAndCheckPermission(request, minimumRole = Security.ROLES.Manage, supportsElevation = false) {
let collectionId = request.params.collectionId
const elevate = request.query.elevate
const grant = request.userObject.grants[collectionId]
// if elevating, check that collection exists
if(supportsElevation && elevate) {
const exists = await CollectionService.doesCollectionExist(collectionId)
if (!exists) {
throw new SmError.NotFoundError("Collection not found")
}
}
// If elevate is not set and supported, and the user does not have a grant, or the grant level is below the minimum required, throw an error.
if (!( (supportsElevation && elevate) || (grant?.roleId >= minimumRole) )) {
throw new SmError.PrivilegeError()
}
return {collectionId, grant}
}
module.exports.getCollectionInfoAndCheckPermission = getCollectionInfoAndCheckPermission
module.exports.getCollectionMetadata = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let result = await CollectionService.getCollectionMetadata(collectionId, req.userObject)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.patchCollectionMetadata = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let metadata = req.body
await CollectionService.patchCollectionMetadata(collectionId, metadata)
let result = await CollectionService.getCollectionMetadata(collectionId)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.putCollectionMetadata = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let body = req.body
await CollectionService.putCollectionMetadata( collectionId, body)
let result = await CollectionService.getCollectionMetadata(collectionId)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getCollectionMetadataKeys = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let result = await CollectionService.getCollectionMetadataKeys(collectionId, req.userObject)
if (!result) {
throw new SmError.NotFoundError('metadata keys not found')
}
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getCollectionMetadataValue = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let key = req.params.key
let result = await CollectionService.getCollectionMetadataValue(collectionId, key, req.userObject)
if (!result) {
throw new SmError.NotFoundError('metadata key not found')
}
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.putCollectionMetadataValue = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let key = req.params.key
let value = req.body
await CollectionService.putCollectionMetadataValue(collectionId, key, value)
res.status(204).send()
}
catch (err) {
next(err)
}
}
module.exports.deleteCollectionMetadataKey = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req)
let key = req.params.key
await CollectionService.deleteCollectionMetadataKey(collectionId, key, req.userObject)
res.status(204).send()
}
catch (err) {
next(err)
}
}
module.exports.deleteReviewHistoryByCollection = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const retentionDate = req.query.retentionDate
const assetId = req.query.assetId
let result = await CollectionService.deleteReviewHistoryByCollection(collectionId, retentionDate, assetId)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getReviewHistoryByCollection = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Full)
const startDate = req.query.startDate
const endDate = req.query.endDate
const assetId = req.query.assetId
const ruleId = req.query.ruleId
const status = req.query.status
let result = await CollectionService.getReviewHistoryByCollection(collectionId, startDate, endDate, assetId, ruleId, status)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getReviewHistoryStatsByCollection = async function (req, res, next) {
try {
let { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Full)
const startDate = req.query.startDate
const endDate = req.query.endDate
const assetId = req.query.assetId
const ruleId = req.query.ruleId
const status = req.query.status
const projection = req.query.projection
let result = await CollectionService.getReviewHistoryStatsByCollection(collectionId, startDate, endDate, assetId, ruleId, status, projection)
res.json(result)
}
catch (err) {
next(err)
}
}
module.exports.getCollectionLabels = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const response = await CollectionService.getCollectionLabels( collectionId, grant )
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.createCollectionLabel = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const labelId = await CollectionService.createCollectionLabel( collectionId, req.body )
const response = await CollectionService.getCollectionLabelById( collectionId, labelId, grant )
res.status(201).json(response)
}
catch (err) {
next(err)
}
}
module.exports.createCollectionLabels = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const createdLabelNames = await CollectionService.createCollectionLabels(collectionId, req.body)
const createdLabels = await CollectionService.getCollectionLabelsByName(collectionId, createdLabelNames, grant)
res.status(201).json(createdLabels)
} catch (err) {
next(err)
}
}
module.exports.getCollectionLabelById = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const response = await CollectionService.getCollectionLabelById( collectionId, req.params.labelId, grant )
if (!response) {
throw new SmError.NotFoundError()
}
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.patchCollectionLabelById = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const affectedRows = await CollectionService.patchCollectionLabelById( collectionId, req.params.labelId, req.body )
if (affectedRows === 0) {
throw new SmError.NotFoundError()
}
const response = await CollectionService.getCollectionLabelById( collectionId, req.params.labelId, grant )
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.deleteCollectionLabelById = async function (req, res, next) {
try {
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const affectedRows = await CollectionService.deleteCollectionLabelById(collectionId, req.params.labelId)
if (affectedRows === 0) {
throw new SmError.NotFoundError()
}
res.status(204).end()
}
catch (err) {
next(err)
}
}
module.exports.getAssetsByCollectionLabelId = async function (req, res, next) {
try {
const {collectionId, grant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const response = await CollectionService.getAssetsByCollectionLabelId( collectionId, req.params.labelId, grant )
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.putAssetsByCollectionLabelId = async function (req, res, next) {
try {
const { collectionId } = await getCollectionInfoAndCheckPermission(req)
const labelId = req.params.labelId
const assetIds = req.body
let collection = await CollectionService.getCollection( collectionId, ['assets','labels'], false, req.userObject)
if (!collection.labels.find( l => l.labelId === labelId)) {
throw new SmError.PrivilegeError('The labelId is not associated with this Collection.')
}
let collectionAssets = collection.assets.map( a => a.assetId)
if (assetIds.every( a => collectionAssets.includes(a))) {
await CollectionService.putAssetsByCollectionLabelId( collectionId, labelId, assetIds, res.svcStatus )
const response = await CollectionService.getAssetsByCollectionLabelId( collectionId, req.params.labelId, req.userObject )
res.json(response)
}
else {
throw new SmError.PrivilegeError('One or more assetId is not a Collection member.')
}
}
catch (err) {
next(err)
}
}
module.exports.postCklArchiveByCollection = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const mode = req.query.mode || 'mono'
const parsedRequest = await processAssetStigRequests (req.body, collectionId, mode, grant)
await postArchiveByCollection({
format: `ckl-${mode}`,
req,
res,
parsedRequest
})
}
catch (err) {
next(err)
}
}
module.exports.postCklbArchiveByCollection = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const mode = req.query.mode || 'mono'
const parsedRequest = await processAssetStigRequests (req.body, collectionId, mode, grant)
await postArchiveByCollection({
format: `cklb-${mode}`,
req,
res,
parsedRequest
})
}
catch (err) {
next(err)
}
}
module.exports.postXccdfArchiveByCollection = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const parsedRequest = await processAssetStigRequests (req.body, collectionId, 'mono', grant)
await postArchiveByCollection({
format: 'xccdf',
req,
res,
parsedRequest
})
}
catch (err) {
next(err)
}
}
async function postArchiveByCollection ({format = 'ckl-mono', req, res, parsedRequest}) {
const builder = new XMLBuilder({
attributeNamePrefix : "@_",
textNodeName : "#text",
ignoreAttributes: format.startsWith('ckl-'),
cdataTagName: "__cdata",
cdataPositionChar: "\\c",
format: true,
indentBy: " ",
supressEmptyNode: format === 'xccdf',
processEntities: false,
tagValueProcessor: escapeForXml,
attrValueProcessor: escapeForXml
})
const zip = Archiver('zip', {zlib: {level: 9}})
const started = new Date()
const dateString = escape.filenameComponentFromDate(started)
// Query for highest classification marking of STIG revisions
let classificationPrefix = config.settings.setClassification === 'NONE' ? 'U' : config.settings.setClassification
if (classificationPrefix === 'U' || classificationPrefix === 'CUI') {
const uniqueRevisions = Array.from(parsedRequest.assetStigArguments.reduce((map, arg) => {
arg.stigs.forEach(stig => map.set(`${stig.benchmarkId}:${stig.revisionStr}`, stig))
return map
}, new Map()).values())
const highestMarking = await STIGService.getHighestMarkingByRevisions(uniqueRevisions)
classificationPrefix = highestMarking === 'CUI' || highestMarking === 'FOUO' ? 'CUI' : 'U'
}
const attachmentName = escape.escapeFilename(`${classificationPrefix}_${parsedRequest.collection.name}-${format.startsWith('ckl-') ?
'CKL' : format.startsWith('cklb-') ? 'CKLB' : 'XCCDF'}_${dateString}.zip`)
res.attachment(attachmentName)
zip.pipe(res)
const manifest = {
started: started.toISOString(),
finished: '',
errorCount: 0,
errors: [],
memberCount: 0,
members: [],
requestParams: {
collection: parsedRequest.collection,
assetStigs: req.body
}
}
zip.on('error', function (e) {
manifest.errors.push({message: e.message, stack: e.stack})
manifest.errorCount += 1
})
for (const arg of parsedRequest.assetStigArguments) {
try {
let response
switch (format) {
case 'ckl-mono':
case 'ckl-multi':
response = await AssetService.cklFromAssetStigs(arg.assetId, arg.stigs)
break
case 'cklb-mono':
case 'cklb-multi':
response = await AssetService.cklbFromAssetStigs(arg.assetId, arg.stigs)
break
case 'xccdf':
response = await AssetService.xccdfFromAssetStig(arg.assetId, arg.stigs[0].benchmarkId, arg.stigs[0].revisionStr)
}
let data
if (response.xmlJs) {
data = `\n\n\n`
data += builder.build(response.xmlJs)
}
else {
data = JSON.stringify(response.cklb)
}
let filename = `${response.marking ? response.marking + '_' : ''}${arg.assetName}`
if (format === 'ckl-mono' || format === 'cklb-mono' || format === 'xccdf') {
filename += `-${arg.stigs[0].benchmarkId}-${response.revisionStrResolved}`
}
filename += `${format === 'xccdf' ? '-xccdf.xml' : format.startsWith('ckl-') ? '.ckl' : '.cklb'}`
filename = escape.escapeFilename(filename)
zip.append(data, {name: filename})
manifest.members.push(filename)
manifest.memberCount += 1
}
catch (e) {
arg.error = {message: e.message, stack: e.stack}
manifest.errors.push(arg)
manifest.errorCount += 1
}
}
manifest.finished = new Date().toISOString()
manifest.members.sort((a,b) => a.localeCompare(b))
zip.append(JSON.stringify(manifest, null, 2), {name: '_manifest.json'})
await zip.finalize()
}
module.exports.getUnreviewedAssetsByCollection = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const benchmarkId = req.query.benchmarkId
const assetId = req.query.assetId
const severities = req.query.severity || []
const labelIds = req.query.labelId || []
const labelNames = req.query.labelName || []
const projections = req.query.projection || []
const response = await CollectionService.getUnreviewedAssetsByCollection( {
collectionId,
benchmarkId,
assetId,
labelIds,
labelNames,
severities,
projections,
grant,
userObject: req.userObject
})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getUnreviewedRulesByCollection = async function (req, res, next) {
try {
const {collectionId, grant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const benchmarkId = req.query.benchmarkId
const ruleId = req.query.ruleId
const severities = req.query.severity || []
const labelIds = req.query.labelId || []
const labelNames = req.query.labelName || []
const projections = req.query.projection || []
const response = await CollectionService.getUnreviewedRulesByCollection( {
collectionId,
benchmarkId,
ruleId,
severities,
labelIds,
labelNames,
projections,
grant,
userObject: req.userObject
})
res.json(response)
}
catch (err) {
next(err)
}
}
// for the archive streaming endpoints
async function processAssetStigRequests (assetStigRequests, collectionId, mode = 'mono', grant) {
const assetStigArguments = []
let collectionName
// Pre-fetch the available revisions of STIGs that were accompanied by a requested revision
// Build a Set of the requested STIGs that were accomapnied by a requested revision
const requestedStigRevisionsSet = assetStigRequests.reduce((acc, value) => {
if (value.stigs) {
for (const item of value.stigs) {
if (typeof item !== 'string') {
acc.add(item.benchmarkId)
}
}
}
return acc
}, new Set())
const requestedStigRevisionsArray = [...requestedStigRevisionsSet]
// Create an object that can have benchmarkId properties and values of revisionStr arrays
let availableRevisions = {}
if (requestedStigRevisionsArray.length) {
availableRevisions = await STIGService.getRevisionStrsByBenchmarkIds(requestedStigRevisionsArray)
}
// iterate through the request
for (const requested of assetStigRequests) {
const assetId = requested.assetId
// Try to fetch asset as this user.
const assetResponse = await AssetService.getAsset({assetId, projections: ['stigs'], grant} )
// Does user have a grant permitting access to the asset?
if (!assetResponse) {
throw new SmError.PrivilegeError()
}
// Is asset a member of collectionId?
if (assetResponse.collection.collectionId !== collectionId) {
throw new SmError.UnprocessableError(`Asset id ${assetId} is not a member of Collection id ${collectionId}.`)
}
if (!collectionName) { collectionName = assetResponse.collection.name } // will be identical for other assets
// Does the asset have STIG assignments?
if (assetResponse.stigs.length === 0) {
throw new SmError.UnprocessableError(`Asset id ${assetId} has no STIG assignments.`)
}
// create Set with keys being the asset's benchmarkId assignments
const assignedStigsSet = new Set(assetResponse.stigs.map( stig => stig.benchmarkId))
// create Map with keys being the requested benchmarkIds for the asset and values being an array of requested revisionStrs for that benchmarkId
const requestedRevisionsMap = new Map()
if (!requested.stigs) {
// request doesn't specify STIGs, so create keys for each assigned benchmarkId and set each value to an array containing the default revision string
for (const stig of assetResponse.stigs) {
requestedRevisionsMap.set(stig.benchmarkId, [stig.revisionStr])
}
}
else {
// request includes specific STIGs
for (const stig of requested.stigs) {
if (typeof stig === 'string' && assignedStigsSet.has(stig)) {
// value is a benchmarkId string that matches an available STIG mapping
// get already requested revisions for this STIG or any empty array
const revisions = requestedRevisionsMap.get(stig) ?? []
// add the default revision string to the requested revisions
revisions.push(assetResponse.stigs.find( assetStig => assetStig.benchmarkId === stig).revisionStr)
// update the Map
requestedRevisionsMap.set(stig, revisions)
}
else if ((stig.revisionStr === 'latest' && assignedStigsSet.has(stig.benchmarkId)) ||
(assignedStigsSet.has(stig.benchmarkId) && availableRevisions[stig.benchmarkId].includes(stig.revisionStr))) {
// value is an object that matches an available STIG/Revision mapping
// get already requested revisions for this STIG or any empty array
const revisions = requestedRevisionsMap.get(stig.benchmarkId) ?? []
// add this requested revision string to the requested revisions
revisions.push(stig.revisionStr)
// update the Map
requestedRevisionsMap.set(stig.benchmarkId, revisions)
}
else {
throw new SmError.UnprocessableError(`Asset id ${assetId} is not mapped to ${JSON.stringify(stig)}.`)
}
}
}
// For generating individual filenames
const assetName = assetResponse.name
if (mode === 'mono') {
// XCCDF and mono CKLs
for (const entry of requestedRevisionsMap) {
for (const revisionStr of entry[1]) {
assetStigArguments.push({
assetId,
assetName,
stigs: [{benchmarkId: entry[0], revisionStr}]
})
}
}
}
else {
// multi-STIG CKLs
const stigsParam = []
for (const entry of requestedRevisionsMap) {
for (const revisionStr of entry[1]) {
stigsParam.push({benchmarkId: entry[0], revisionStr})
}
}
assetStigArguments.push({
assetId,
assetName,
stigs: stigsParam
})
}
}
return {
collection: {
collectionId,
name: collectionName,
},
assetStigArguments
}
}
module.exports.writeStigPropsByCollectionStig = async function (req, res, next) {
try {
const { collectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const benchmarkId = req.params.benchmarkId
const assetIds = req.body.assetIds
const defaultRevisionStr = req.body.defaultRevisionStr
const existingRevisions = await STIGService.getRevisionsByBenchmarkId({benchmarkId, grants: req.userObject.grants})
//if defaultRevisionStr is present, check that specified revision is valid for the benchmark
if (defaultRevisionStr && defaultRevisionStr !== "latest" && existingRevisions.find(benchmark => benchmark.revisionStr === defaultRevisionStr) === undefined) {
throw new SmError.UnprocessableError("The revisionStr is is not valid for the specified benchmarkId")
}
// The OAS layer mandated if assetIds is absent then defaultRevisionStr must be present
// we do not permit setting the default revision of an unassigned STIG
if (!assetIds && !await CollectionService.doesCollectionIncludeStig({collectionId, benchmarkId})) {
throw new SmError.UnprocessableError('Cannot set the default revision of a benchmarkId that has no mapped Assets')
}
if (assetIds && assetIds.length === 0 && defaultRevisionStr) {
throw new SmError.UnprocessableError('Cannot set the default revision of a benchmarkId and also remove all mapped Assets')
}
if (assetIds?.length) {
const collectionHasAssets = await CollectionService.doesCollectionIncludeAssets({
collectionId,
assetIds
})
if (!collectionHasAssets) {
throw new SmError.PrivilegeError('One or more assetId is not a Collection member.')
}
}
await CollectionService.writeStigPropsByCollectionStig( {
collectionId,
benchmarkId,
assetIds,
defaultRevisionStr,
svcStatus: res.svcStatus
})
const response = await CollectionService.getStigsByCollection({collectionId, grant, benchmarkId})
if (response[0]) {
res.json(response[0])
}
else {
res.status(204).send()
}
}
catch (err) {
next(err)
}
}
module.exports.cloneCollection = async function (req, res, next) {
try {
function progressCb(json) {
res.write(JSON.stringify(json) + '\n')
}
if ( req.userObject.privileges.create_collection ) {
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const options = {
grants: true,
labels: true,
assets: true,
stigMappings: 'withReviews',
pinRevisions: 'matchSource',
...req.body.options
}
res.setHeader('Content-Type', 'application/x-ndjson; charset=utf-8');
res.setHeader('X-Accel-Buffering', 'no'); // Disable buffering for nginx
const cloned = await CollectionService.cloneCollection({
collectionId,
userObject: req.userObject,
name: req.body.name,
description: req.body.description,
options,
svcStatus: res.svcStatus,
progressCb
})
if (cloned) {
// // hack the existing userObject
req.userObject.grants[cloned.destCollectionId] = {
collectionId: cloned.destCollectionId,
name: req.body.name,
roleId: 4,
grantIds: []
}
const collection = await CollectionService.getCollection(cloned.destCollectionId, req.query.projection, false, req.userObject )
res.write(JSON.stringify({stage: 'result', collection}) + '\n')
}
res.end()
}
else {
throw new SmError.PrivilegeError('User has not been granted createCollection privilege')
}
}
catch (err) {
next(err)
}
}
module.exports.exportToCollection = async function (req, res, next) {
try {
function progressCb(json) {
res.write(JSON.stringify(json) + '\n')
}
const { collectionId: srcCollectionId, grant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
req.params.collectionId = req.params.dstCollectionId
const { collectionId: dstCollectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
req.params.collectionId = srcCollectionId
const parsedRequest = await processAssetStigRequests (req.body, srcCollectionId, 'multi', grant)
res.setHeader('Content-Type', 'application/x-ndjson; charset=utf-8');
res.setHeader('X-Accel-Buffering', 'no'); // Disable buffering for nginx
await CollectionService.exportToCollection({
srcCollectionId,
dstCollectionId,
assetStigArguments: parsedRequest.assetStigArguments,
userObject: req.userObject,
progressCb,
svcStatus: res.svcStatus
})
res.end()
}
catch (err) {
next(err)
}
}
module.exports.getEffectiveAclByCollectionUser = async function (req, res, next) {
try{
const {collectionId} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage)
const userId = req.params.userId
if (!await CollectionService._hasCollectionGrant({collectionId, userId})) throw new SmError.UnprocessableError('user has no direct or group grant in collection')
const response = await CollectionService.getEffectiveAclByCollectionUser({collectionId, userId})
res.json(response)
}
catch(err){
next(err)
}
}
module.exports.putGrantByCollectionGrant = async function (req, res, next) {
try {
const grantId = req.params.grantId
const elevate = req.query.elevate
const grant = req.body
if (grant.userId) {
const invalidUserIds = await dbUtils.selectInvalidUserIds([grant.userId])
if (invalidUserIds.length) {
throw new SmError.UserInconsistentError()
}
}
const {collectionId, grant: requesterGrant} = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const currentGrant = (await CollectionService._getCollectionGrant({collectionId, grantId}))[0]
if (!currentGrant) {
throw new SmError.NotFoundError('no such grant in collection')
}
if (!elevate && currentGrant.roleId === 4 && requesterGrant.roleId !== 4) {
throw new SmError.PrivilegeError('cannot modify owner grants')
}
if (!elevate && grant.roleId === 4 && requesterGrant.roleId !== 4) {
throw new SmError.PrivilegeError('cannot create owner grants')
}
await CollectionService.putGrantById({grantId, grant, isRoleChange: currentGrant.roleId !== grant.roleId, svcStatus: res.svcStatus})
const updatedGrant = (await CollectionService._getCollectionGrant({collectionId, grantId}))[0]
res.json(updatedGrant)
}
catch (err) {
if (err.code === 'ER_NO_REFERENCED_ROW_2') {
err = new SmError.UnprocessableError('no such grantee')
}
else if (err.code === 'ER_DUP_ENTRY') {
err = new SmError.UnprocessableError('grantee has a conflicting grant')
}
next(err)
}
}
module.exports.getGrantByCollectionGrant = async function (req, res, next) {
try {
const grantId = req.params.grantId
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const grant = (await CollectionService._getCollectionGrant({collectionId, grantId}))[0]
if (!grant) throw new SmError.NotFoundError('no such grant in collection')
res.json(grant)
}
catch (err) {
next(err)
}
}
module.exports.getGrantsByCollection = async function (req, res, next) {
try {
const { collectionId } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const grants = await CollectionService._getCollectionGrant({collectionId})
res.json(grants)
}
catch (err) {
next(err)
}
}
module.exports.postGrantsByCollection = async function (req, res, next) {
try {
const { collectionId, grant: requesterGrant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const grants = req.body
const elevate = req.query.elevate
const userIds = grants.map(g => g.userId).filter(Boolean)
const invalidUserIds = await dbUtils.selectInvalidUserIds(userIds)
if (invalidUserIds.length > 0) {
throw new SmError.UserInconsistentError()
}
const roles = grants.map( g => g.roleId)
if (!elevate && roles.includes(4) && requesterGrant.roleId !== 4) {
throw new SmError.PrivilegeError('cannot create owner grants')
}
const grantIds = await CollectionService.postGrantsByCollection(collectionId, grants)
const newGrants = await CollectionService._getCollectionGrant({collectionId, grantIds})
res.status(201).json(newGrants)
}
catch (err) {
if (err.code === 'ER_NO_REFERENCED_ROW_2') {
err = new SmError.UnprocessableError('no such grantee')
}
else if (err.code === 'ER_DUP_ENTRY') {
err = new SmError.UnprocessableError('grantee has a conflicting grant')
}
next(err)
}
}
module.exports.deleteGrantByCollectionGrant = async function (req, res, next) {
try {
const grantId = req.params.grantId
const elevate = req.query.elevate
const { collectionId, grant: requesterGrant } = await getCollectionInfoAndCheckPermission(req, Security.ROLES.Manage, true)
const currentGrant = (await CollectionService._getCollectionGrant({collectionId, grantId}))[0]
if (!currentGrant) {
throw new SmError.NotFoundError('no such grant in collection')
}
if (!elevate && currentGrant.roleId === 4 && requesterGrant.roleId !== 4) {
throw new SmError.PrivilegeError('cannot remove owner grants')
}
await CollectionService.deleteGrantById(grantId)
res.json(currentGrant)
}
catch (err) {
next(err)
}
}
module.exports.getAclRulesByCollectionGrant = async function (req, res, next) {
try {
const grantId = req.params.grantId
const { collectionId } = await getCollectionInfoAndCheckPermission(req)
const grant = (await CollectionService._getCollectionGrant({collectionId, grantId}))[0]
if (!grant) throw new SmError.NotFoundError('no such grant in collection')
const response = await CollectionService.queryReviewAcl({grantId})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.putAclRulesByCollectionGrant = async function (req, res, next) {
try {
const grantId = req.params.grantId
const { collectionId } = await getCollectionInfoAndCheckPermission(req)
const grant = (await CollectionService._getCollectionGrant({collectionId, grantId}))[0]
if (!grant) throw new SmError.NotFoundError('no such grant in collection')
const acl = req.body
const validated = await CollectionService._reviewAclValidate({grantId, acl})
if (validated.fail.length > 0) {
throw new SmError.UnprocessableError(validated.fail)
}
await CollectionService.setValidatedAcl({
validatedAcl: validated.pass,
grantId,
attributionUserId: req.userObject.userId,
svcStatus: res.svcStatus
})
const response = await CollectionService.queryReviewAcl({grantId})
res.json(response)
}
catch (err) {
next(err)
}
}
================================================
FILE: api/source/controllers/Job.js
================================================
const SmError = require('../utils/error');
const JobService = require(`../service/JobService`)
const userJobIdBase = 100
exports.getJobs = async (req, res, next) => {
try {
const projections = req.query.projection
const jobs = await JobService.getJobs({projections})
res.json(jobs)
} catch (error) {
next(error)
}
}
exports.postJob = async (req, res, next) => {
try {
const jobId = await JobService.createJob({
jobData: req.body,
userId: req.userObject.userId,
svcStatus: res.svcStatus
})
const newJob = await JobService.getJob(jobId)
res.status(201).json(newJob)
} catch (error) {
if (error.code === 'ER_DUP_ENTRY') {
error = new SmError.UnprocessableError('Job name already exists')
} else if (error.code === 'ER_NO_REFERENCED_ROW_2') {
error = new SmError.UnprocessableError('Unknown taskId in list')
}
next(error)
}
}
exports.getJob = async (req, res, next) => {
try {
const projections = req.query.projection
const jobId = req.params.jobId
const job = await JobService.getJob(jobId, {projections})
if (!job) {
throw new SmError.NotFoundError(`Job with ID [${jobId}] not found.`)
}
res.json(job)
} catch (error) {
next(error)
}
}
exports.deleteJob = async (req, res, next) => {
try {
const jobId = req.params.jobId
if (parseInt(jobId) < userJobIdBase) {
throw new SmError.UnprocessableError(`Job is a system job and cannot be deleted.`)
}
// has desired side-effect of removing events named with the jobId, even if job does not exist
const wasDeleted = await JobService.deleteJob(jobId)
if (!wasDeleted) {
throw new SmError.NotFoundError(`Job with ID [${jobId}] not found.`)
}
res.status(204).end()
} catch (error) {
next(error)
}
}
exports.patchJob = async (req, res, next) => {
try {
const jobId = req.params.jobId
if (parseInt(jobId) < userJobIdBase) {
const bodyKeys = Object.keys(req.body)
if (!bodyKeys.every(key => key === 'event')) {
throw new SmError.UnprocessableError(`System jobs can only be modified with event properties.`)
}
}
const existingJob = await JobService.getJob(jobId)
if (!existingJob) {
throw new SmError.NotFoundError(`Job with ID [${jobId}] not found.`)
}
await JobService.patchJob({
jobId,
jobData: req.body,
userId: req.userObject.userId,
svcStatus: res.svcStatus
})
const patchedJob = await JobService.getJob(jobId)
res.status(200).json(patchedJob)
} catch (error) {
if (error.code === 'ER_DUP_ENTRY') {
error = new SmError.UnprocessableError('Job name already exists')
} else if (error.code === 'ER_NO_REFERENCED_ROW_2') {
error = new SmError.UnprocessableError('Unknown taskId in list')
}
next(error)
}
}
exports.getRunsByJob = async (req, res, next) => {
try {
const jobId = req.params.jobId
const job = await JobService.getJob(jobId)
if (!job) {
throw new SmError.NotFoundError(`Job with ID [${jobId}] not found.`)
}
const runs = await JobService.getRunsByJob(jobId)
res.json(runs)
} catch (error) {
next(error)
}
}
exports.runImmediateJob = async (req, res, next) => {
try {
const jobId = req.params.jobId
const job = await JobService.getJob(jobId)
if (!job) {
throw new SmError.NotFoundError(`Job with ID [${jobId}] not found.`)
}
const runId = await JobService.runImmediateJob(jobId)
res.json({runId})
} catch (error) {
next(error)
}
}
exports.getRunById = async (req, res, next) => {
try {
const runId = req.params.runId
const run = await JobService.getRunById(runId)
if (!run) {
throw new SmError.NotFoundError(`Run with ID [${runId}] not found.`)
}
res.json(run)
} catch (error) {
next(error)
}
}
exports.deleteRunById = async (req, res, next) => {
try {
const runId = req.params.runId
const wasDeleted = await JobService.deleteRunById(runId)
if (!wasDeleted) {
throw new SmError.NotFoundError(`Run with ID [${runId}] not found.`)
}
res.status(204).end()
} catch (error) {
next(error)
}
}
exports.getOutputByRun = async (req, res, next) => {
try {
const runId = req.params.runId
const afterSeq = req.query['after-seq']
const output = await JobService.getOutputByRun(runId, { filters: { afterSeq } })
res.json(output)
} catch (error) {
next(error)
}
}
exports.getAllTasks = async (req, res, next) => {
try {
const tasks = await JobService.getAllTasks()
res.json(tasks)
} catch (error) {
next(error)
}
}
================================================
FILE: api/source/controllers/Metrics.js
================================================
const config = require('../utils/config')
const MetricsService = require(`../service/MetricsService`)
const Collection = require('./Collection')
const Security = require('../utils/roles')
const SmError = require('../utils/error')
const {stringify: csvStringify} = require('csv-stringify/sync')
async function getCollectionMetrics (req, res, next, {style, aggregation, firstRowOnly = false}) {
try {
const { collectionId, grant } = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const returnType = req.query.format || 'json'
const filter = {
labelNames: req.query.labelName,
labelMatch: req.query.labelMatch,
labelIds: req.query.labelId,
assetIds: req.query.assetId,
benchmarkIds: req.query.benchmarkId,
}
const rows = await MetricsService.queryMetrics({
collectionId,
filter,
grant,
style,
aggregation,
returnType
})
if (returnType === 'csv') {
res.type('text/csv')
res.send(csvStringify(rows, {header: true}))
}
else {
res.json(firstRowOnly ? rows[0] : rows)
}
}
catch (e) {
next(e)
}
}
async function getMetaMetrics (req, res, next, {style, aggregation, firstRowOnly = false}) {
try {
const returnType = req.query.format || 'json'
const filter = {
collectionIds: req.query.collectionId,
benchmarkIds: req.query.benchmarkId,
revisionIds: req.query.revisionId
}
const rows = await MetricsService.queryMetaMetrics({
filter,
grants: req.userObject.grants,
style,
aggregation,
returnType
})
if (returnType === 'csv') {
res.type('text/csv')
res.send(csvStringify(rows, {header: true}))
}
else {
res.json(firstRowOnly ? rows[0] : rows)
}
}
catch (e) {
next(e)
}
}
module.exports.getMetricsDetailByCollection = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'detail', aggregation: 'unagg'})
}
module.exports.getMetricsDetailByCollectionAggAsset = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'detail', aggregation: 'asset'})
}
module.exports.getMetricsDetailByCollectionAgg = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'detail', aggregation: 'collection', firstRowOnly: true})
}
module.exports.getMetricsDetailByCollectionAggLabel = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'detail', aggregation: 'label'})
}
module.exports.getMetricsDetailByCollectionAggStig = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'detail', aggregation: 'stig'})
}
module.exports.getMetricsSummaryByCollection = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'summary', aggregation: 'unagg'})
}
module.exports.getMetricsSummaryByCollectionAggAsset = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'summary', aggregation: 'asset'})
}
module.exports.getMetricsSummaryByCollectionAgg = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'summary', aggregation: 'collection', firstRowOnly: true})
}
module.exports.getMetricsSummaryByCollectionAggLabel = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'summary', aggregation: 'label'})
}
module.exports.getMetricsSummaryByCollectionAggStig = async function (req, res, next) {
return getCollectionMetrics(req, res, next, {style: 'summary', aggregation: 'stig'})
}
module.exports.getMetricsDetailByMeta = async function (req, res, next) {
return getMetaMetrics(req, res, next, {style: 'detail', aggregation: 'meta', firstRowOnly: true})
}
module.exports.getMetricsDetailByMetaAggCollection = async function (req, res, next) {
return getMetaMetrics(req, res, next, {style: 'detail', aggregation: 'collection'})
}
module.exports.getMetricsDetailByMetaAggStig = async function (req, res, next) {
return getMetaMetrics(req, res, next, {style: 'detail', aggregation: 'metaStig'})
}
module.exports.getMetricsSummaryByMeta = async function (req, res, next) {
return getMetaMetrics(req, res, next, {style: 'summary', aggregation: 'meta', firstRowOnly: true})
}
module.exports.getMetricsSummaryByMetaAggCollection = async function (req, res, next) {
return getMetaMetrics(req, res, next, {style: 'summary', aggregation: 'collection'})
}
module.exports.getMetricsSummaryByMetaAggStig = async function (req, res, next) {
return getMetaMetrics(req, res, next, {style: 'summary', aggregation: 'metaStig'})
}
================================================
FILE: api/source/controllers/Operation.js
================================================
const config = require('../utils/config')
const OperationService = require(`../service/OperationService`)
const escape = require('../utils/escape')
const {JSONPath} = require('jsonpath-plus')
const SmError = require('../utils/error.js')
const state = require('../utils/state')
module.exports.getConfiguration = async function getConfiguration (req, res, next) {
try {
const dbConfigs = await OperationService.getConfiguration()
const {version, commit, lastMigration} = config
res.json({ version, commit, lastMigration, ...dbConfigs })
}
catch(err) {
next(err)
}
}
module.exports.setConfigurationItem = async function setConfigurationItem (req, res, next) {
try {
//TODO: Implement
}
catch(err) {
next(err)
}
}
module.exports.getAppData = async function getAppData (req, res, next) {
try {
if (!config.experimental.appData) throw new SmError.NotFoundError('endpoint disabled, to enable set STIGMAN_EXPERIMENTAL_APPDATA=true')
if (!req.query.elevate) throw new SmError.PrivilegeError()
const format = req.query.format || 'gzip'
res.attachment(`appdata-v${config.lastMigration}_${escape.filenameComponentFromDate()}.jsonl${format==='gzip'?'.gz':''}`)
if (format === 'jsonl') res.type('application/jsonl')
// the service method will stream the appdata file to the response object
OperationService.getAppData(res, format)
// the service ends the response by closing the gzip stream
}
catch (err) {
next(err)
}
}
module.exports.getAppDataTables = async function (req, res, next) {
try {
if (!req.query.elevate) throw new SmError.PrivilegeError()
const response = await OperationService.getAppDataTables()
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.replaceAppData = async function replaceAppData (req, res, next) {
// write JSONL to the response; called from the service method
function progressCb(json) {
res.write(JSON.stringify(json) + '\n')
}
try {
if (!config.experimental.appData) throw new SmError.NotFoundError('endpoint disabled, to enable set STIGMAN_EXPERIMENTAL_APPDATA=true')
if (!req.query.elevate) throw new SmError.PrivilegeError()
let chunks = []
for await (const chunk of req) {
chunks.push(chunk)
}
const buffer = Buffer.concat(chunks)
res.setHeader('Content-Type', 'application/jsonl; charset=utf-8')
res.setHeader('X-Accel-Buffering', 'no'); // Disable buffering for nginx
res.setHeader('Transfer-Encoding', 'chunked')
await OperationService.replaceAppData(buffer, req.headers['content-type'], progressCb )
res.end()
}
catch (err) {
next(err)
}
}
module.exports.getDefinition = async function getDefinition (req, res, next) {
try {
let jsonpath = req.query.jsonpath
if (jsonpath) {
res.json(JSONPath(jsonpath, config.definition))
}
else {
res.json(config.definition)
}
}
catch (err) {
next(err)
}
}
module.exports.getAppInfo = async function getAppInfo (req, res, next) {
try {
let elevate = req.query.elevate
if ( elevate ) {
const options = {
includeRowCounts: req.query.includeRowCounts
}
const response = await OperationService.getAppInfo(options)
res.json(response)
}
else {
throw new SmError.PrivilegeError()
}
}
catch (err) {
next(err)
}
}
module.exports.getState = function (req, res, next) {
try {
res.json(state.apiState)
}
catch (err) {
next(err)
}
}
module.exports.getDetails = module.exports.getAppInfo
module.exports.streamStateSse = function (req, res, next) {
try {
res.setHeader('Content-Type', 'text/event-stream');
res.setHeader('Cache-Control', 'no-cache');
res.setHeader('Connection', 'keep-alive');
res.setHeader('X-Accel-Buffering', 'no'); // Disable buffering for nginx
// Helper to send SSE events
function sendEvent(eventName, data) {
if (eventName) res.write(`event: ${eventName}\n`);
res.write(`data: ${typeof data === 'string' ? data : JSON.stringify(data)}\n\n`);
}
// Send initial state
sendEvent('state-report', state.apiState);
// Event listeners
const stateChangedListener = () => sendEvent('state-changed', state.apiState);
const dependencyChangedListener = () => sendEvent('dependency-changed', state.apiState);
state.on('state-changed', stateChangedListener);
state.on('dependency-changed', dependencyChangedListener);
// Keep-alive ping every 30 seconds
const keepAlive = setInterval(() => {
sendEvent('state-report', state.apiState);
}, 30000);
// Cleanup on client disconnect
req.on('close', () => {
clearInterval(keepAlive);
state.off('state-changed', stateChangedListener);
state.off('dependency-changed', dependencyChangedListener);
res.end();
});
} catch (err) {
next(err);
}
}
================================================
FILE: api/source/controllers/Review.js
================================================
'use strict';
const config = require('../utils/config')
const ReviewService = require(`../service/ReviewService`)
const CollectionService = require(`../service/CollectionService`)
const Collection = require(`./Collection`)
const SmError = require('../utils/error')
const Security = require('../utils/roles')
const dbUtils = require('../service/utils')
const _this = this
const AssetService = require('../service/AssetService')
module.exports.postReviewsByAsset = async function postReviewsByAsset (req, res, next) {
try {
const { collectionId } = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const assetId = req.params.assetId
const reviews = req.body
// check assetId exists, is enabled, and belongs to the collection in the URL path
const assetRow = await dbUtils.selectCollectionByAssetId(assetId)
if (!assetRow || assetRow.collectionId.toString() !== collectionId) {
throw new SmError.PrivilegeError()
}
const result = await ReviewService.putReviewsByAsset({
assetId,
reviews,
collectionId,
userId: req.userObject.userId,
grant: req.userObject.grants[collectionId],
svcStatus: res.svcStatus
})
res.json(result)
}
catch(err) {
next(err)
}
}
module.exports.deleteReviewByAssetRule = async function deleteReviewByAssetRule (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let projections = req.query.projection
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant, checkWritable: true})
if (userHasRule) {
let response = await ReviewService.deleteReviewByAssetRule({assetId, ruleId, projections, grant, svcStatus: res.svcStatus})
res.status(response ? 200 : 204).json(response)
}
else {
throw new SmError.PrivilegeError()
}
}
catch(err) {
next(err)
}
}
module.exports.exportReviews = async function exportReviews (includeHistory) {
return await ReviewService.exportReviews(includeHistory)
}
module.exports.getReviewByAssetRule = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let projections = req.query.projection
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const assetExists = await AssetService.doesAssetExist(assetId)
if (!assetExists) {
throw new SmError.PrivilegeError()
}
let response = await ReviewService.getReviews({
projections,
filter: {
collectionId,
assetId: assetId,
ruleId: ruleId
},
grant,
userObject: req.userObject
})
// res.json(response[0])
// res.status(typeof response === 'undefined' ? 204 : 200).json(response[0])
res.status(response.length == 0 ? 204 : 200).json(response[0])
}
catch(err) {
next(err)
}
}
module.exports.getReviewsByCollection = async function getReviewsByCollection (req, res, next) {
try {
let projections = req.query.projection
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
let response = await ReviewService.getReviews({
projections,
filter: {
collectionId,
result: req.query.result,
status: req.query.status,
rules: req.query.rules || 'default-mapped',
ruleId: req.query.ruleId,
groupId: req.query.groupId,
cci: req.query.cci,
userId: req.query.userId,
assetId: req.query.assetId,
benchmarkId: req.query.benchmarkId,
metadata: req.query.metadata
},
grant,
userObject: req.userObject
})
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getReviewsByAsset = async function (req, res, next) {
try {
let assetId = req.params.assetId
let projections = req.query.projection
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const assetExists = await AssetService.doesAssetExist(assetId)
if (!assetExists) {
throw new SmError.PrivilegeError()
}
let response = await ReviewService.getReviews({
projections,
filter: {
collectionId,
assetId: assetId,
rules: req.query.rules || 'default-mapped',
result: req.query.result,
status: req.query.status,
benchmarkId: req.query.benchmarkId,
metadata: req.query.metadata
},
grant,
userObject: req.userObject
})
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.putReviewByAssetRule = async function (req, res, next) {
try {
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const {assetId, ruleId} = {...req.params}
const review = {...req.body, ruleId}
const projections = req.query.projection
// check assetId exists, is enabled, and belongs to the collection in the URL path
const assetRow = await dbUtils.selectCollectionByAssetId(assetId)
if (!assetRow || assetRow.collectionId.toString() !== collectionId) {
throw new SmError.PrivilegeError()
}
const result = await ReviewService.putReviewsByAsset({
assetId,
reviews: [review],
collectionId,
userId: req.userObject.userId,
grant: req.userObject.grants[collectionId],
svcStatus: res.svcStatus
})
if (result.rejected.length) {
throw new SmError.PrivilegeError(result.rejected[0].reason)
}
const rows = await ReviewService.getReviews({
projections,
filter: {collectionId, assetId, ruleId},
grant,
userObject: req.userObject
})
res.status(result.affected.inserted > 0 ? 201 : 200).json(rows[0])
}
catch (err) {
next(err)
}
}
module.exports.patchReviewByAssetRule = async function (req, res, next) {
try {
if (Object.hasOwn(req.body, 'resultEngine') && !Object.hasOwn(req.body, 'result')) {
throw new SmError.UnprocessableError('Request body with resultEngine must include a result')
}
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const {assetId, ruleId} = {...req.params}
// check assetId exists, is enabled, and belongs to the collection in the URL path —
// must run before the pre-write existence read so a foreign-collection asset
// cannot satisfy the "review must exist" gate and reveal review state via 404 vs 403
const assetRow = await dbUtils.selectCollectionByAssetId(assetId)
if (!assetRow || assetRow.collectionId.toString() !== collectionId) {
throw new SmError.PrivilegeError()
}
const currentReviews = await ReviewService.getReviews({
filter: {collectionId, assetId, ruleId},
grant,
userObject: req.userObject
})
if (currentReviews.length === 0) {
throw new SmError.NotFoundError('Review must exist to be patched')
}
const review = {...req.body, ruleId}
const projections = req.query.projection
const result = await ReviewService.putReviewsByAsset({
assetId,
reviews: [review],
collectionId,
userId: req.userObject.userId,
grant: req.userObject.grants[collectionId],
svcStatus: res.svcStatus
})
if (result.rejected.length) {
throw new SmError.PrivilegeError(result.rejected[0].reason)
}
const rows = await ReviewService.getReviews({
projections,
filter: {collectionId, assetId, ruleId},
grant,
userObject: req.userObject
})
res.json(rows[0])
}
catch (err) {
next(err)
}
}
module.exports.getReviewMetadata = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant})
if (userHasRule) {
let response = await ReviewService.getReviewMetadata( assetId, ruleId, req.userObject)
res.json(response)
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to get the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.patchReviewMetadata = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let metadata = req.body
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant, checkWritable: true})
if (userHasRule) {
await ReviewService.patchReviewMetadata( assetId, ruleId, metadata)
let response = await ReviewService.getReviewMetadata( assetId, ruleId)
res.json(response)
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to patch the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.putReviewMetadata = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let body = req.body
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant, checkWritable: true})
if (userHasRule) {
await ReviewService.putReviewMetadata( assetId, ruleId, body)
let response = await ReviewService.getReviewMetadata( assetId, ruleId)
res.json(response)
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to put the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.getReviewMetadataKeys = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant})
if (userHasRule) {
let response = await ReviewService.getReviewMetadataKeys( assetId, ruleId, req.userObject)
if (!response) {
throw new SmError.NotFoundError('metadata keys not found')
}
res.json(response)
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to get the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.getReviewMetadataValue = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let key = req.params.key
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant})
if (userHasRule) {
let response = await ReviewService.getReviewMetadataValue( assetId, ruleId, key, req.userObject)
if (!response) {
throw new SmError.NotFoundError('metadata key not found')
}
res.json(response)
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to get the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.putReviewMetadataValue = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let key = req.params.key
let value = req.body
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant, checkWritable: true})
if (userHasRule) {
await ReviewService.putReviewMetadataValue( assetId, ruleId, key, value)
res.status(204).send()
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to put the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.deleteReviewMetadataKey = async function (req, res, next) {
try {
let assetId = req.params.assetId
let ruleId = req.params.ruleId
let key = req.params.key
const {collectionId, grant} = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const userHasRule = await ReviewService.checkRuleByAssetUser({ruleId, assetId, collectionId, grant, checkWritable: true})
if (userHasRule) {
await ReviewService.deleteReviewMetadataKey( assetId, ruleId, key, req.userObject)
res.status(204).send()
}
else {
throw new SmError.PrivilegeError('User has insufficient privilege to delete the review of this rule.')
}
}
catch (err) {
next(err)
}
}
module.exports.postReviewBatch = async function (req, res, next) {
try {
const { collectionId, grant } = await Collection.getCollectionInfoAndCheckPermission(req, Security.ROLES.Restricted)
const collectionSettings = await CollectionService.getCollectionSettings(collectionId)
const historySettings = collectionSettings.history
const statusSettings = collectionSettings.status
const userId = req.userObject.userId
let {source, assets, rules, action, updateFilters, dryRun = false} = req.body
// normalize status property
if (typeof source.review.status === 'string') {
source.review.status = {
label: source.review.status,
text: null
}
}
// reject unpermitted accept/reject
if (source.review.status?.label === 'accepted' || source.review.status?.label === 'rejected') {
if (!statusSettings.canAccept) {
throw new SmError.PrivilegeError('Reviews cannot be accepted/rejected in this Collection')
}
if (grant.roleId < statusSettings.minAcceptGrant) {
throw new SmError.PrivilegeError('User cannot accept/reject Reviews in this Collection')
}
}
// validate action
if (!source.review.result && (action === 'insert' || action === 'merge')) {
throw new SmError.UnprocessableError('Cannot insert a NULL result')
}
// default action if missing
if (!action) {
action = source.review.result ? 'merge' : 'update'
}
// are grant checks required
let skipGrantCheck = false
if (assets.benchmarkIds && rules.benchmarkIds && assets.benchmarkIds.length === rules.benchmarkIds.length) {
skipGrantCheck = assets.benchmarkIds.every( i => rules.benchmarkIds.includes(i)) &&
rules.benchmarkIds.every( i => assets.benchmarkIds.includes(i))
}
const result = await ReviewService.postReviewBatch({
source,
assets,
rules,
action,
updateFilters,
dryRun,
collectionId,
userId,
grant,
svcStatus: res.svcStatus,
historyMaxReviews: historySettings.maxReviews,
skipGrantCheck
})
res.json(result)
}
catch (err) {
next(err)
}
}
================================================
FILE: api/source/controllers/STIG.js
================================================
'use strict';
const config = require('../utils/config');
const SmError = require('../utils/error');
const parsers = require('../utils/parsers.js')
const STIGService = require(`../service/STIGService`)
module.exports.importBenchmark = async function importManualBenchmark (req, res, next) {
try {
if (!req.query.elevate) throw new SmError.PrivilegeError()
const extension = req.file.originalname.substring(req.file.originalname.lastIndexOf(".")+1)
const clobber = req.query.clobber ?? false
if (extension.toLowerCase() != 'xml') {
throw new SmError.ClientError(`File extension .${extension} not supported`)
}
let benchmark
try {
benchmark = parsers.benchmarkFromXccdf(req.file.buffer)
}
catch(err){
throw new SmError.ClientError(err.message)
}
if (benchmark.scap) {
throw new SmError.UnprocessableError('SCAP Benchmarks are not imported.')
}
const markingMatch = req.file.originalname.match(/^(CUI|U|FOUO)_/)
benchmark.revision.marking = markingMatch?.[1] ?? null
const revision = await STIGService.insertManualBenchmark(benchmark, clobber, res.svcStatus)
res.json(revision)
}
catch(err) {
next(err)
}
}
module.exports.deleteRevisionByString = async function deleteRevisionByString (req, res, next) {
try {
if (!req.query.elevate) throw new SmError.PrivilegeError()
const benchmarkId = req.params.benchmarkId
const revisionStr = req.params.revisionStr
const force = req.query.force
const response = await STIGService.getRevisionByString({
benchmarkId,
revisionStr,
grants: req.userObject.grants,
elevate: req.query.elevate
})
if(response === undefined) {
throw new SmError.NotFoundError('No matching revisionStr found.')
}
const existingRevisions = await STIGService.getRevisionsByBenchmarkId({benchmarkId, grants: req.userObject.grants})
const stigAssigned = await STIGService.getStigById(benchmarkId, req.userObject, true)
if (stigAssigned.collectionIds.length && existingRevisions.length == 1 && !force) {
throw new SmError.UnprocessableError("The revisionStr is the last remaining revision for this benchmark, which is assigned to one or more Collections. Set force=true to force the delete")
}
if (response.collectionIds.length && !force) {
throw new SmError.UnprocessableError("The revisionStr is pinned to one or more Collections. Set force=true to force the delete")
}
else {
await STIGService.deleteRevisionByString(benchmarkId, revisionStr, res.svcStatus)
res.json(response)
}
}
catch(err) {
next(err)
}
}
module.exports.deleteStigById = async function deleteStigById (req, res, next) {
if ( req.query.elevate ) {
try {
const benchmarkId = req.params.benchmarkId
const force = req.query.force
const response = await STIGService.getStigById(benchmarkId, req.userObject, true)
if(response === undefined) {
throw new SmError.NotFoundError('No matching benchmarkId found.')
}
if (response.collectionIds.length && !force) {
throw new SmError.UnprocessableError("The benchmarkId is assigned to one or more Collections. Set force=true to force the delete")
}
await STIGService.deleteStigById(benchmarkId, res.svcStatus)
res.json(response)
}
catch (err) {
next(err)
}
}
else {
next(new SmError.PrivilegeError())
}
}
module.exports.getCci = async function getCci (req, res, next) {
let cci = req.params.cci
let projection = req.query.projection
try {
let response = await STIGService.getCci(cci, projection, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getCcisByRevision = async function getCcisByRevision (req, res, next) {
let benchmarkId = req.params.benchmarkId
let revisionStr = req.params.revisionStr
try {
let response = await STIGService.getCcisByRevision(benchmarkId, revisionStr, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getGroupByRevision = async function getGroupByRevision (req, res, next) {
let projection = req.query.projection
let benchmarkId = req.params.benchmarkId
let revisionStr = req.params.revisionStr
let groupId = req.params.groupId
try {
let response = await STIGService.getGroupByRevision(benchmarkId, revisionStr, groupId, projection, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getGroupsByRevision = async function getGroupsByRevision (req, res, next) {
let projection = req.query.projection
let benchmarkId = req.params.benchmarkId
let revisionStr = req.params.revisionStr
try {
let response = await STIGService.getGroupsByRevision(benchmarkId, revisionStr, projection, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getRevisionByString = async function getRevisionByString (req, res, next) {
try {
const benchmarkId = req.params.benchmarkId
const revisionStr = req.params.revisionStr
const elevate = req.query.elevate
const response = await STIGService.getRevisionByString({
benchmarkId,
revisionStr,
grants: req.userObject.grants,
elevate
})
res.status(response ? 200 : 404).json(response)
}
catch(err) {
next(err)
}
}
module.exports.getRevisionsByBenchmarkId = async function getRevisionsByBenchmarkId (req, res, next) {
const benchmarkId = req.params.benchmarkId
const elevate = req.query.elevate
try {
const response = await STIGService.getRevisionsByBenchmarkId({benchmarkId, grants: req.userObject.grants, elevate})
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getRuleByRuleId = async function getRuleByRuleId (req, res, next) {
let projection = req.query.projection
let ruleId = req.params.ruleId
try {
let response = await STIGService.getRuleByRuleId(ruleId, projection, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getRuleByRevision = async function getRulesByRevision (req, res, next) {
let projection = req.query.projection
let benchmarkId = req.params.benchmarkId
let revisionStr = req.params.revisionStr
let ruleId = req.params.ruleId
try {
let response = await STIGService.getRuleByRevision(benchmarkId, revisionStr, ruleId, projection, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getRulesByRevision = async function getRulesByRevision (req, res, next) {
let projection = req.query.projection
let benchmarkId = req.params.benchmarkId
let revisionStr = req.params.revisionStr
try {
let response = await STIGService.getRulesByRevision(benchmarkId, revisionStr, projection, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getSTIGs = async function getSTIGs (req, res, next) {
const title = req.query.title
const elevate = req.query.elevate
const projection = req.query.projection || []
try {
let response = await STIGService.getSTIGs(title, projection, req.userObject, elevate)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getStigById = async function getStigById (req, res, next) {
let benchmarkId = req.params.benchmarkId
const elevate = req.query.elevate
try {
let response = await STIGService.getStigById(benchmarkId, req.userObject, elevate)
if(!response) {
throw new SmError.NotFoundError()
}
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getScapMap = async function getStigById (req, res, next) {
res.json([
{
scapBenchmarkId: 'CAN_Ubuntu_18-04_STIG',
benchmarkId: 'U_CAN_Ubuntu_18-04_STIG'
},
{
scapBenchmarkId: 'Mozilla_Firefox_RHEL',
benchmarkId: 'Mozilla_Firefox'
},
{
scapBenchmarkId: 'Mozilla_Firefox_Windows',
benchmarkId: 'Mozilla_Firefox'
},
{
scapBenchmarkId: 'MOZ_Firefox_Linux',
benchmarkId: 'MOZ_Firefox_STIG'
},
{
scapBenchmarkId: 'MOZ_Firefox_Windows',
benchmarkId: 'MOZ_Firefox_STIG'
},
{
scapBenchmarkId: 'Solaris_10_X86_STIG',
benchmarkId: 'Solaris_10_X86'
}
])
}
================================================
FILE: api/source/controllers/User.js
================================================
'use strict';
const config = require('../utils/config')
const UserService = require(`../service/UserService`)
const AssetService = require(`../service/AssetService`)
const CollectionService = require(`../service/CollectionService`)
const SmError = require('../utils/error')
const dbUtils = require('../service/utils')
async function validateCollectionGrants(collectionGrants, {elevate}) {
if (collectionGrants?.length) {
// Verify each grant for a valid collectionId
let requestedIds = collectionGrants.map( g => g.collectionId )
let availableCollections = await CollectionService.queryCollections({elevate})
let availableIds = availableCollections.map( c => c.collectionId)
if (! requestedIds.every( id => availableIds.includes(id) ) ) {
throw new SmError.UnprocessableError('One or more collectionIds are invalid.')
}
}
}
/* */
module.exports.createUser = async function createUser (req, res, next) {
try {
const elevate = req.query.elevate
if (!elevate) throw new SmError.PrivilegeError()
let body = req.body
let projection = req.query.projection
if (body.hasOwnProperty('collectionGrants') ) {
await validateCollectionGrants(body.collectionGrants, {elevate})
}
body.status = 'available'
try {
let response = await UserService.createUser(body, projection, elevate, req.userObject, res.svcStatus)
res.status(201).json(response)
}
catch (err) {
// This is MySQL specific, should abstract
if (err.code === 'ER_DUP_ENTRY') {
throw new SmError.UnprocessableError('Duplicate name exists.')
}
else {
throw err
}
}
}
catch(err) {
next(err)
}
}
module.exports.deleteUser = async function deleteUser (req, res, next) {
try {
let elevate = req.query.elevate
if (elevate) {
let userId = req.params.userId
let projection = req.query.projection
let userData = await UserService.getUserByUserId(userId, [], elevate, req.userObject)
if (userData?.lastAccess) {
// User has accessed the system, so we need to reject the request
throw new SmError.UnprocessableError('User has accessed the system. Use PATCH to remove collection grants or configure Authentication provider to reject user entirely.')
}
let response = await UserService.deleteUser(userId, projection, elevate, req.userObject)
res.json(response)
}
else {
throw new SmError.PrivilegeError()
}
}
catch(err) {
next(err)
}
}
module.exports.exportUsers = async function exportUsers (projection, elevate, userObject) {
if (elevate) {
return await UserService.getUsers(null, null, projection, elevate, userObject )
}
else {
throw new SmError.PrivilegeError()
}
}
module.exports.exportUserGroups = async function exportUserGroups (projections, elevate) {
if (elevate) {
return await UserService.queryUserGroups({projections})
}
else {
throw new SmError.PrivilegeError()
}
}
module.exports.getUser = async function getUser (req, res, next) {
try {
const projection = ['collectionGrants', 'statistics', 'userGroups']
if (req.query.projection) {
projection.push(req.query.projection)
}
let response = await UserService.getUserByUserId(req.userObject.userId, projection)
response.privileges = req.userObject.privileges
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.getUserByUserId = async function getUserByUserId (req, res, next) {
try {
let elevate = req.query.elevate
if ( elevate ) {
let userId = req.params.userId
let projection = req.query.projection
let response = await UserService.getUserByUserId(userId, projection, elevate, req.userObject)
if(!response) {
throw new SmError.NotFoundError()
}
res.json(response)
}
else {
throw new SmError.PrivilegeError()
}
}
catch(err) {
next(err)
}
}
module.exports.getUsers = async function getUsers (req, res, next) {
try {
let elevate = req.query.elevate
let username = req.query.username
let usernameMatch = req.query['username-match']
let privilege = req.query['privilege']
let status = req.query.status
let projection = req.query.projection
if ( !elevate && projection?.length > 0) {
throw new SmError.PrivilegeError()
}
let response = await UserService.getUsers( username, usernameMatch, privilege, status, projection, elevate, req.userObject)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.replaceUser = async function replaceUser (req, res, next) {
try {
let elevate = req.query.elevate
let userId = req.params.userId
if (!elevate) throw new SmError.PrivilegeError()
let body = req.body
let projection = req.query.projection
let userData = await UserService.getUserByUserId(userId)
if (!userData) {
throw new SmError.NotFoundError("UserId not found.")
}
const intendedStatus = body.status || userData.status
if (intendedStatus === 'unavailable') {
if (body.collectionGrants?.length || body.userGroups?.length) {
throw new SmError.UserInconsistentError()
}
}
if (body.status) {
body.statusUser = req.userObject.userId
body.statusDate = new Date()
}
if (body.collectionGrants?.length) {
await validateCollectionGrants(body.collectionGrants, {elevate})
}
let response = await UserService.replaceUser(userId, body, projection, elevate, req.userObject, res.svcStatus)
res.json(response)
}
catch(err) {
next(err)
}
}
module.exports.updateUser = async function updateUser (req, res, next) {
try {
let elevate = req.query.elevate
if (!elevate) throw new SmError.PrivilegeError()
let userId = req.params.userId
let body = req.body
let projection = req.query.projection
let userData = await UserService.getUserByUserId(userId)
if (!userData) {
throw new SmError.NotFoundError("UserId not found.")
}
// Determine intended status: body.status or current status
const intendedStatus = body.status || userData.status
if (intendedStatus === 'unavailable') {
if (body.collectionGrants?.length || body.userGroups?.length) {
throw new SmError.UserInconsistentError()
}
body.collectionGrants = []
body.userGroups = []
}
if (body.status) {
body.statusUser = req.userObject.userId
body.statusDate = new Date()
}
if (body.collectionGrants?.length) {
await validateCollectionGrants(body.collectionGrants, {elevate})
}
let response = await UserService.replaceUser(userId, body, projection, elevate, req.userObject, res.svcStatus)
res.json(response)
}
catch(err) {
next(err)
}
}
/* c8 ignore start */
module.exports.setUserData = async function setUserData (username, fields) {
try {
await UserService.setUserData(username, fields)
return await UserService.getUserByUsername(username)
}
catch (e) {
next(err)
}
}
/* c8 ignore end */
module.exports.createUserGroup = async (req, res, next) => {
try {
if (!req.query.elevate) throw new SmError.PrivilegeError()
const {userIds, collectionGrants, ...userGroupFields} = req.body
const invalidUserIds = await dbUtils.selectInvalidUserIds(userIds)
if (invalidUserIds.length) {
throw new SmError.UserInconsistentError()
}
await validateCollectionGrants(collectionGrants, {elevate: req.query.elevate})
let userGroupId
try{
userGroupId = await UserService.addOrUpdateUserGroup({
userGroupFields,
userIds,
collectionGrants,
createdUserId: req.userObject.userId,
modifiedUserId: req.userObject.userId
})
}
catch (err) {
throw err.code === 'ER_DUP_ENTRY' ? new SmError.UnprocessableError('Group name is already in use.') : err
}
const response = await UserService.queryUserGroups({
projections: req.query.projection,
filters: {userGroupId}
})
res.status(201).json(response[0])
}
catch (err) {
next(err)
}
}
module.exports.getUserGroups = async (req, res, next) => {
try {
if (req.query.projection?.includes('collections') && !req.query.elevate) {
throw new SmError.PrivilegeError('collections projection requires elevation')
}
const response = await UserService.queryUserGroups({
projections: req.query.projection
})
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.getUserGroup = async (req, res, next) => {
try {
if (req.query.projection?.includes('collections') && !req.query.elevate) {
throw new SmError.PrivilegeError('collections projection requires elevation')
}
const response = await UserService.queryUserGroups({
projections: req.query.projection,
filters: {userGroupId: req.params.userGroupId}
})
if (!response[0]) throw new SmError.NotFoundError()
res.json(response[0])
}
catch (err) {
next(err)
}
}
async function putOrPatchUserGroup (req, res, next) {
try {
if (!req.query.elevate) throw new SmError.PrivilegeError()
const {userIds, collectionGrants, ...userGroupFields} = req.body
const invalidUserIds = await dbUtils.selectInvalidUserIds(userIds)
if (invalidUserIds.length) {
throw new SmError.UserInconsistentError()
}
await validateCollectionGrants(collectionGrants, {elevate: req.query.elevate})
const userGroup = await UserService.queryUserGroups({
projections: [],
filters: {userGroupId: req.params.userGroupId}
})
if (!userGroup.length) throw new SmError.NotFoundError("UserGroup not found.")
const userGroupId = await UserService.addOrUpdateUserGroup({
userGroupId: req.params.userGroupId,
userGroupFields,
userIds,
collectionGrants,
modifiedUserId: req.userObject.userId
})
const response = await UserService.queryUserGroups({
projections: req.query.projection,
filters: {userGroupId}
})
res.json(response[0])
}
catch (err) {
next(err)
}
}
module.exports.patchUserGroup = putOrPatchUserGroup
module.exports.putUserGroup = putOrPatchUserGroup
module.exports.deleteUserGroup = async (req, res, next) => {
try{
if (!req.query.elevate) throw new SmError.PrivilegeError()
const response = await UserService.queryUserGroups({
projections: req.query.projection,
filters: {userGroupId: req.params.userGroupId}
})
await UserService.deleteUserGroup({
userGroupId: req.params.userGroupId,
})
res.json(response[0])
}
catch (err) {
next(err)
}
}
module.exports.getUserWebPreferences = async (req, res, next) => {
try {
const response = await UserService.getUserWebPreferences(req.userObject.userId)
res.json(response)
}
catch (err) {
next(err)
}
}
module.exports.patchUserWebPreferences = async (req, res, next) => {
try {
const body = req.body
await UserService.patchUserWebPreferences(req.userObject.userId, body)
const response = await UserService.getUserWebPreferences(req.userObject.userId)
res.json(response)
}
catch (err) {
next(err)
}
}
================================================
FILE: api/source/healthcheck.js
================================================
const http = require("http")
const options = {
host : "localhost",
port: process.env.STIGMAN_API_PORT || 54000,
path: "/api/op/definition?jsonpath=%24.info.version",
timeout : 2000
}
const request = http.request(options, (res) => {
console.log(`STATUS: ${res.statusCode}`)
if (res.statusCode == 200) {
process.exit(0)
}
else {
process.exit(1)
}
})
request.on('error', function(err) {
console.log('ERROR')
process.exit(1)
})
request.end()
================================================
FILE: api/source/index.js
================================================
'use strict'
const startTime = process.hrtime.bigint()
const express = require('express')
const logger = require('./utils/logger')
const state = require('./utils/state')
const signals = require('./bootstrap/signals')
const config = require('./utils/config')
const { serializeError } = require('./utils/serializeError')
const configureMiddleware = require('./bootstrap/middlewares.js')
const bootstrapUtils = require('./bootstrap/bootstrapUtils.js')
const client = require('./bootstrap/client.js')
const docs = require('./bootstrap/docs.js')
const startServer = require('./bootstrap/server')
signals.setupSignalHandlers()
bootstrapUtils.logAppConfig(config)
//Catch unhandled errors.
process.on('uncaughtException', (err, origin) => {
logger.writeError('app','uncaught', serializeError(err))
})
process.on('unhandledRejection', (reason, promise) => {
logger.writeError('app','unhandled', {reason, promise})
})
const app = express()
configureMiddleware(app, config)
run()
async function run() {
try {
client.serveClient(app)
docs.serveDocs(app)
docs.serveApiDocs(app)
await startServer(app, startTime)
}
catch (err) {
logger.writeError(err.message)
state.setState('fail')
}
}
================================================
FILE: api/source/package.json
================================================
{
"name": "stig-management-api",
"version": "1.6.9",
"description": "An API for managing evaluations of Security Technical Implementation Guide (STIG) assessments.",
"main": "index.js",
"scripts": {
"prestart": "npm install",
"start": "node index.js"
},
"keywords": [
"swagger"
],
"license": "MIT",
"private": true,
"dependencies": {
"ajv": "^8.17.1",
"ajv-formats": "^3.0.1",
"archiver": "^7.0.1",
"async-retry": "^1.3.3",
"compression": "^1.8.1",
"cors": "^2.8.5",
"csv-stringify": "^6.5.1",
"express": "^4.21.2",
"express-openapi-validator": "^5.6.2",
"fast-xml-parser": "^5.5.8",
"he": "^1.2.0",
"js-yaml": "^4.1.0",
"jsonpath-plus": "^10.3.0",
"jsonwebtoken": "^9.0.2",
"jszip": "^3.10.1",
"jwks-rsa": "^3.1.0",
"multer": "^2.1.1",
"mysql2": "^3.11.2",
"net-keepalive": "^4.0.17",
"on-finished": "^2.4.1",
"on-headers": "^1.1.0",
"semver": "^7.6.3",
"swagger-ui-express": "^4.1.6",
"umzug": "^2.3.0",
"undici": "^6.24.0",
"ws": "^8.18.3",
"xlsx-template": "file:utils/xlsx-template-js-zip-upgrade"
}
}
================================================
FILE: api/source/service/AssetService.js
================================================
'use strict';
const { randomUUID } = require('node:crypto')
const dbUtils = require('./utils')
const config = require('../utils/config')
let _this = this
/**
Generalized queries for asset(s).
**/
exports.queryAssets = async function ({projections = [], filter = {}, grant = {}}) {
const ctes = []
const columns = [
'CAST(a.assetId as char) as assetId',
'a.name',
'a.fqdn',
`json_object (
'collectionId', CAST(c.collectionId as char),
'name', c.name
) as "collection"`,
'a.description',
'a.ip',
`coalesce(
(select
json_arrayagg(BIN_TO_UUID(cl.uuid,1))
from
collection_label_asset_map cla
left join collection_label cl on cla.clId = cl.clId
where
cla.assetId = a.assetId),
json_array()
) as labelIds`,
`coalesce(
(select
json_arrayagg(json_object(
'labelId', BIN_TO_UUID(cl.uuid,1),
'name', cl.name,
'color', cl.color
))
from
collection_label_asset_map cla
left join collection_label cl on cla.clId = cl.clId
where
cla.assetId = a.assetId),
json_array()
) as labels`,
'a.mac',
'a.noncomputing',
'a.metadata'
]
const joins = [
'enabled_asset a',
'left join enabled_collection c on a.collectionId = c.collectionId',
'left join stig_asset_map sa on a.assetId = sa.assetId'
]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
// PROJECTIONS
if (projections.includes('statusStats')) {
columns.push(`(select json_object(
'stigCount', COUNT(saStatusStats.benchmarkId),
'ruleCount', SUM(rStatusStats.ruleCount),
'acceptedCount', SUM(saStatusStats.accepted),
'rejectedCount', SUM(saStatusStats.rejected),
'submittedCount', SUM(saStatusStats.submitted),
'savedCount', SUM(saStatusStats.saved),
'minTs', DATE_FORMAT(LEAST(MIN(saStatusStats.minTs), MIN(saStatusStats.maxTs)),'%Y-%m-%dT%H:%i:%sZ'),
'maxTs', DATE_FORMAT(GREATEST(MAX(saStatusStats.minTs), MAX(saStatusStats.maxTs)),'%Y-%m-%dT%H:%i:%sZ')
)
from
stig_asset_map saStatusStats
left join enabled_asset aStatusStats using (assetId)
left join default_rev drStatusStats on (saStatusStats.benchmarkId = drStatusStats.benchmarkId and aStatusStats.collectionId = drStatusStats.collectionId)
left join revision rStatusStats on drStatusStats.revId = rStatusStats.revId
where
FIND_IN_SET(saStatusStats.saId, GROUP_CONCAT(sa.saId))
) as "statusStats"`)
}
if (projections.includes('stigs')) {
//iterate: If benchmarkId is a predicate in main query, this incorrectly only shows that STIG
joins.push('left join default_rev dr on (sa.benchmarkId=dr.benchmarkId and a.collectionId = dr.collectionId)')
joins.push('left join revision on dr.revId = revision.revId')
columns.push(`cast(
concat('[',
coalesce (
group_concat(distinct
case when sa.benchmarkId is not null then
json_object(
'benchmarkId', sa.benchmarkId,
'revisionStr', revision.revisionStr,
'benchmarkDate', date_format(revision.benchmarkDateSql,'%Y-%m-%d'),
'revisionPinned', CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END,
'ruleCount', revision.ruleCount)
else null end
order by sa.benchmarkId),
''),
']')
as json) as "stigs"`)
}
// PREDICATES
const predicates = {
statements: [],
binds: []
}
if (filter.assetId) {
predicates.statements.push('a.assetId = ?')
predicates.binds.push(filter.assetId)
}
if (filter.assetIds && filter.assetIds.length > 0) {
predicates.statements.push(`a.assetId IN ?`)
predicates.binds.push([filter.assetIds])
}
if (filter.labels?.labelNames || filter.labels?.labelIds || filter.labels?.labelMatch) {
joins.push(
'left join collection_label_asset_map cla2 on a.assetId = cla2.assetId',
'left join collection_label cl2 on cla2.clId = cl2.clId'
)
const labelPredicates = []
if (filter.labels.labelIds) {
labelPredicates.push('cl2.uuid IN ?')
const uuidBinds = filter.labels.labelIds.map( uuid => dbUtils.uuidToSqlString(uuid))
predicates.binds.push([uuidBinds])
}
if (filter.labels.labelNames) {
labelPredicates.push('cl2.name IN ?')
predicates.binds.push([filter.labels.labelNames])
}
if (filter.labels.labelMatch === 'null') {
labelPredicates.push('cl2.uuid IS NULL')
}
const labelPredicatesClause = `(${labelPredicates.join(' OR ')})`
predicates.statements.push(labelPredicatesClause)
}
if ( filter.name ) {
let matchStr = '= ?'
if ( filter.nameMatch && filter.nameMatch !== 'exact') {
matchStr = 'LIKE ?'
switch (filter.nameMatch) {
case 'startsWith':
filter.name = `${filter.name}%`
break
case 'endsWith':
filter.name = `%${filter.name}`
break
case 'contains':
filter.name = `%${filter.name}%`
break
}
}
predicates.statements.push(`a.name ${matchStr}`)
predicates.binds.push(filter.name)
}
if (filter.collectionId) {
predicates.statements.push('a.collectionId = ?')
predicates.binds.push(filter.collectionId)
}
if (filter.benchmarkId) {
predicates.statements.push('sa.benchmarkId = ?')
predicates.binds.push(filter.benchmarkId)
}
if (filter.metadata ) {
for (const pair of filter.metadata) {
const [key, value] = pair.split(/:(.*)/s)
predicates.statements.push('JSON_CONTAINS(a.metadata, ?, ?)')
predicates.binds.push( JSON.stringify(value), `$.${key}`)
}
}
const groupBy = [
'a.assetId'
]
const orderBy = []
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.queryChecklist = async function (inPredicates, projections = []) {
let connection
try {
const columns = [
'CAST(:assetId as char) as "assetId"',
'rgr.ruleId',
'rgr.title as "ruleTitle"',
'rgr.version',
'rgr.groupId',
'rgr.groupTitle',
'rgr.severity',
`result.api as "result"`,
`CASE WHEN review.resultEngine = 0 THEN NULL ELSE review.resultEngine END as resultEngine`,
`review.autoResult`,
`status.api as "status"`,
`review.statusTs`,
`review.ts`,
`review.touchTs`
]
if (projections.includes('rule')) {
columns.push(`json_object(
'ruleId', rgr.ruleId,
'severity', rgr.severity,
'title', rgr.title,
'version', rgr.version,
'groupId', rgr.groupId,
'groupTitle', rgr.groupTitle,
'detail', json_object(
'weight', rgr.weight,
'vulnDiscussion', rgr.vulnDiscussion,
'falsePositives', rgr.falsePositives,
'falseNegatives', rgr.falseNegatives,
'documentable', rgr.documentable,
'mitigations', rgr.mitigations,
'severityOverrideGuidance', rgr.severityOverrideGuidance,
'potentialImpacts', rgr.potentialImpacts,
'thirdPartyTools', rgr.thirdPartyTools,
'mitigationControl', rgr.mitigationControl,
'responsibility', rgr.responsibility
),
'ccis', coalesce(
(
select json_arrayagg(json_object(
'cci', rgrcc.cci,
'apAcronym', cci.apAcronym,
'definition', cci.definition,
'control', crm.parentControl
))
from rev_group_rule_cci_map rgrcc
inner join cci using (cci)
left join cci_reference_map crm using (cci)
where rgrcc.rgrId = rgr.rgrId
),
json_array()
),
'check', json_object(
'system', rgr.checkSystem,
'content', (
select cc.content
from check_content cc
where cc.digest = rgr.checkDigest
limit 1
)
),
'fix', json_object(
'fixref', rgr.fixref,
'text', (
select ft.text
from fix_text ft
where ft.digest = rgr.fixDigest
limit 1
)
),
'ruleIds', coalesce(
(
select json_arrayagg(rvcd2.ruleId)
from rule_version_check_digest rvcd2
where rvcd2.version = rgr.version
and rvcd2.checkDigest = rgr.checkDigest
),
json_array()
),
'stigs', json_array(
json_object(
'benchmarkId', rev.benchmarkId,
'revisionStr', concat('V', rev.version, 'R', rev.release)
)
)
) as rule`)
}
if (projections.includes('detail')) {
columns.push('review.detail as "detail"')
}
if (projections.includes('comment')) {
columns.push('review.comment as "comment"')
}
const joins = [
'current_rev rev',
'left join rev_group_rule_map rgr using (revId)',
'left join rule_version_check_digest rvcd using (ruleId)',
'left join review on (rvcd.version = review.version and rvcd.checkDigest = review.checkDigest and review.assetId = :assetId)',
'left join result on review.resultId=result.resultId',
'left join status on review.statusId=status.statusId',
'left join enabled_asset a on review.assetId=a.assetId'
]
const predicates = {
statements: [],
binds: {}
}
if (inPredicates.assetId) {
predicates.binds.assetId = inPredicates.assetId
}
if (inPredicates.benchmarkId) {
predicates.statements.push('rev.benchmarkId = :benchmarkId')
predicates.binds.benchmarkId = inPredicates.benchmarkId
}
if (inPredicates.revisionStr !== 'latest') {
joins.splice(0, 1, 'revision rev')
const {version, release} = dbUtils.parseRevisionStr(inPredicates.revisionStr)
const revId = `${inPredicates.benchmarkId}-${version}-${release}`
predicates.statements.push('rev.revId = :revId')
predicates.binds.revId = revId
}
const groupBy = [
'rgr.rgrId',
'result.api',
'review.reviewId',
'status.api',
]
const orderBy = [
'substring(rgr.groupId from 3) + 0'
]
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, orderBy})
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
let [rows] = await connection.query( sql, predicates.binds )
return (rows)
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.cklFromAssetStigs = async function cklFromAssetStigs (assetId, stigs) {
let connection
try {
let revisionStrResolved // Will hold specific revision string value, as opposed to "latest"
const xmlJs = {
CHECKLIST: {
ASSET: {
ROLE: 'None',
ASSET_TYPE: 'Computing',
MARKING: null,
HOST_NAME: null,
HOST_IP: null,
HOST_MAC: null,
HOST_GUID: null,
HOST_FQDN: null,
TECH_AREA: null,
TARGET_KEY: '2777',
WEB_OR_DATABASE: 'false',
WEB_DB_SITE: null,
WEB_DB_INSTANCE: null
},
STIGS: {
iSTIG: []
}
}
}
const sqlGetAsset = "select name, fqdn, ip, mac, noncomputing, metadata from enabled_asset where assetId = ?"
const sqlGetChecklist =`SELECT
rgr.groupId,
rgr.severity,
rgr.groupTitle,
rgr.ruleId,
rgr.title as "ruleTitle",
rgr.weight,
rgr.version,
rgr.vulnDiscussion,
rgr.iaControls,
rgr.falsePositives,
rgr.falseNegatives,
rgr.documentable,
rgr.mitigations,
rgr.potentialImpacts,
rgr.thirdPartyTools,
rgr.mitigationControl,
rgr.responsibility,
rgr.severityOverrideGuidance,
result.ckl as "result",
LEFT(review.detail,32767) as "detail",
LEFT(review.comment,32767) as "comment",
cc.content as "checkContent",
ft.text as "fixText",
group_concat(rgrcc.cci ORDER BY rgrcc.cci) as "ccis"
FROM
revision rev
left join rev_group_rule_map rgr on rev.revId = rgr.revId
left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId
left join severity_cat_map sc on rgr.severity = sc.severity
left join rev_group_rule_cci_map rgrcc on rgr.rgrId = rgrcc.rgrId
left join check_content cc on rgr.checkDigest = cc.digest
left join fix_text ft on rgr.fixDigest = ft.digest
left join review on (rvcd.version = review.version and rvcd.checkDigest = review.checkDigest and review.assetId = ?)
left join result on review.resultId = result.resultId
left join status on review.statusId = status.statusId
WHERE
rev.revId = ?
GROUP BY
rgr.rgrId,
result.ckl,
review.detail,
review.comment
order by
substring(rgr.groupId from 3) + 0 asc
`
connection = await dbUtils.pool.getConnection()
// ASSET
const [resultGetAsset] = await connection.query(sqlGetAsset, [assetId])
xmlJs.CHECKLIST.ASSET.HOST_NAME = resultGetAsset[0].metadata.cklHostName ? resultGetAsset[0].metadata.cklHostName : resultGetAsset[0].name
xmlJs.CHECKLIST.ASSET.HOST_FQDN = resultGetAsset[0].fqdn
xmlJs.CHECKLIST.ASSET.HOST_IP = resultGetAsset[0].ip
xmlJs.CHECKLIST.ASSET.HOST_MAC = resultGetAsset[0].mac
xmlJs.CHECKLIST.ASSET.ASSET_TYPE = resultGetAsset[0].noncomputing ? 'Non-Computing' : 'Computing'
xmlJs.CHECKLIST.ASSET.ROLE = resultGetAsset[0].metadata.cklRole ?? 'None'
xmlJs.CHECKLIST.ASSET.TECH_AREA = resultGetAsset[0].metadata.cklTechArea ?? null
xmlJs.CHECKLIST.ASSET.WEB_OR_DATABASE = resultGetAsset[0].metadata.cklHostName ? 'true' : 'false'
xmlJs.CHECKLIST.ASSET.WEB_DB_SITE = resultGetAsset[0].metadata.cklWebDbSite ?? null
xmlJs.CHECKLIST.ASSET.WEB_DB_INSTANCE = resultGetAsset[0].metadata.cklWebDbInstance ?? null
// CHECKLIST.STIGS.iSTIG.STIG_INFO.SI_DATA
const markings = []
for (const stigItem of stigs) {
const revisionStr = stigItem.revisionStr || 'latest'
revisionStrResolved = revisionStr
const benchmarkId = stigItem.benchmarkId
let sqlGetBenchmarkId
if (revisionStr === 'latest') {
sqlGetBenchmarkId = `select
cr.benchmarkId,
s.title,
cr.revId,
cr.description,
cr.version,
cr.release,
cr.benchmarkDate,
cr.marking
from
current_rev cr
left join stig s on cr.benchmarkId = s.benchmarkId
where
cr.benchmarkId = ?`
}
else {
sqlGetBenchmarkId = `select
r.benchmarkId,
s.title,
r.description,
r.version,
r.release,
r.benchmarkDate,
r.marking
from
stig s
left join revision r on s.benchmarkId=r.benchmarkId
where
r.revId = ?`
}
// Calculate revId
let resultGetBenchmarkId, revId
if (revisionStr === 'latest') {
;[resultGetBenchmarkId] = await connection.query(sqlGetBenchmarkId, [benchmarkId])
revId = resultGetBenchmarkId[0].revId
revisionStrResolved = `V${resultGetBenchmarkId[0].version}R${resultGetBenchmarkId[0].release}`
}
else {
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
revId = `${benchmarkId}-${version}-${release}`
;[resultGetBenchmarkId] = await connection.execute(sqlGetBenchmarkId, [revId])
}
const stig = resultGetBenchmarkId[0]
// Set the marking
if (stig.marking) {
markings.push(stig.marking)
}
const siDataRefs = [
{ SID_NAME: 'version', SID_DATA: stig.version },
{ SID_NAME: 'classification' },
{ SID_NAME: 'customname' },
{ SID_NAME: 'stigid', SID_DATA: stig.benchmarkId },
{ SID_NAME: 'description', SID_DATA: stig.description },
{ SID_NAME: 'filename', SID_DATA: 'stig-manager-oss' },
{ SID_NAME: 'releaseinfo', SID_DATA: `Release: ${stig.release} Benchmark Date: ${stig.benchmarkDate}`},
{ SID_NAME: 'title', SID_DATA: stig.title },
{ SID_NAME: 'uuid', SID_DATA: '391aad33-3cc3-4d9a-b5f7-0d7538b7b5a2' },
{ SID_NAME: 'notice', SID_DATA: 'terms-of-use' },
{ SID_NAME: 'source', }
]
const iStigJs = {
STIG_INFO:
{
SI_DATA: []
},
VULN: []
}
const siDataArray = iStigJs.STIG_INFO.SI_DATA
for (const siDatum of siDataRefs) {
siDataArray.push(siDatum)
}
// CHECKLIST.STIGS.iSTIG.STIG_INFO.VULN
const [resultGetChecklist] = await connection.query(sqlGetChecklist, [assetId, revId])
const stigDataRef = [
['Vuln_Num', 'groupId' ],
['Severity', 'severity' ],
['Weight', 'weight' ],
['Group_Title', 'groupTitle' ],
['Rule_ID', 'ruleId' ],
['Rule_Ver', 'version' ],
['Rule_Title', 'ruleTitle' ],
['Vuln_Discuss', 'vulnDiscussion' ],
['IA_Controls', 'iaControls' ],
['Check_Content', 'checkContent' ],
['Fix_Text', 'fixText' ],
['False_Positives', 'falsePositives' ],
['False_Negatives', 'falseNegatives' ],
['Documentable', 'documentable' ],
['Mitigations', 'mitigations' ],
['Potential_Impact', 'potentialImpacts' ],
['Third_Party_Tools', 'thirdPartyTools' ],
['Mitigation_Control', 'mitigationControl' ],
['Responsibility', 'responsibility' ],
['Security_Override_Guidance', 'severityOverrideGuidance' ]
// STIGViewer bug requires using Security_Override_Guidance instead of Severity_Override_Guidance
]
// let vulnArray = xmlJs.CHECKLIST.STIGS.iSTIG.VULN
const vulnArray = iStigJs.VULN
for (const r of resultGetChecklist) {
const vulnObj = {
STIG_DATA: [],
STATUS: r.result || 'Not_Reviewed',
FINDING_DETAILS: r.detail,
COMMENTS: r.comment,
SEVERITY_OVERRIDE: null,
SEVERITY_JUSTIFICATION: null
}
for (const stigDatum of stigDataRef) {
vulnObj.STIG_DATA.push({
VULN_ATTRIBUTE: stigDatum[0],
ATTRIBUTE_DATA: r[stigDatum[1]]
})
}
// STIGRef
vulnObj.STIG_DATA.push({
VULN_ATTRIBUTE: 'STIGRef',
ATTRIBUTE_DATA: `${stig.title} :: Version ${stig.version}, Release: ${stig.release} Benchmark Date: ${stig.benchmarkDate}`
})
// CCI_REFs
if (r.ccis) {
const ccis = r.ccis.split(',')
for (const cci of ccis) {
vulnObj.STIG_DATA.push({
VULN_ATTRIBUTE: 'CCI_REF',
ATTRIBUTE_DATA: `CCI-${cci}`
})
}
}
vulnArray.push(vulnObj)
}
xmlJs.CHECKLIST.STIGS.iSTIG.push(iStigJs)
}
// calculate the marking for this checklist
let marking = config.settings.setClassification === 'NONE' ? 'U' : config.settings.setClassification
if (marking === 'U' || marking === 'CUI') {
const sortedMarkings = markings.toSorted((a, b) => a.localeCompare(b)) // because CUI, FOUO, U sort alphabetically
marking = sortedMarkings[0] || 'U'
}
return ({assetName: resultGetAsset[0].name, xmlJs, revisionStrResolved, marking})
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.cklbFromAssetStigs = async function cklbFromAssetStigs (assetId, stigs) {
let connection
try {
let revisionStrResolved // Will hold specific revision string value, as opposed to "latest"
const cklb = {
title: '',
id: randomUUID(),
active: false,
mode: 1,
has_path: true,
target_data: {
target_type: '',
host_name: '',
ip_address: '',
mac_address: '',
fqdn: '',
comments: '',
role: '',
is_web_database: false,
technology_area: '',
web_db_site: '',
web_db_instance: ''
},
stigs: []
}
const sqlGetAsset = "select name, fqdn, ip, mac, noncomputing, metadata from enabled_asset where assetId = ?"
const sqlGetChecklist =`SELECT
rgr.groupId,
rgr.severity,
rgr.groupTitle,
rgr.ruleId,
rgr.title as "ruleTitle",
rgr.weight,
rgr.version,
rgr.vulnDiscussion,
rgr.iaControls,
rgr.falsePositives,
rgr.falseNegatives,
rgr.documentable,
rgr.mitigations,
rgr.potentialImpacts,
rgr.thirdPartyTools,
rgr.mitigationControl,
rgr.responsibility,
rgr.severityOverrideGuidance,
result.cklb as "result",
LEFT(review.detail,32767) as "detail",
LEFT(review.comment,32767) as "comment",
review.ts as "createdAt",
review.touchTs as "updatedAt",
cc.content as "checkContent",
ft.text as "fixText",
group_concat(rgrcc.cci ORDER BY rgrcc.cci) as "ccis"
FROM
revision rev
left join rev_group_rule_map rgr on rev.revId = rgr.revId
left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId
left join severity_cat_map sc on rgr.severity = sc.severity
left join rev_group_rule_cci_map rgrcc on rgr.rgrId = rgrcc.rgrId
left join check_content cc on rgr.checkDigest = cc.digest
left join fix_text ft on rgr.fixDigest = ft.digest
left join review on (rvcd.version = review.version and rvcd.checkDigest = review.checkDigest and review.assetId = ?)
left join result on review.resultId = result.resultId
left join status on review.statusId = status.statusId
WHERE
rev.revId = ?
GROUP BY
rgr.rgrId,
result.cklb,
review.reviewId
order by
substring(rgr.groupId from 3) + 0 asc
`
connection = await dbUtils.pool.getConnection()
// cklb.target_data
const [resultGetAsset] = await connection.query(sqlGetAsset, [assetId])
cklb.target_data.host_name = resultGetAsset[0].metadata.cklHostName ? resultGetAsset[0].metadata.cklHostName : resultGetAsset[0].name
cklb.target_data.fqdn = resultGetAsset[0].fqdn ?? ''
cklb.target_data.ip_address = resultGetAsset[0].ip ?? ''
cklb.target_data.mac_address = resultGetAsset[0].mac ?? ''
cklb.target_data.target_type = resultGetAsset[0].noncomputing ? 'Non-Computing' : 'Computing'
cklb.target_data.role = resultGetAsset[0].metadata.cklRole ?? 'None'
cklb.target_data.technology_area = resultGetAsset[0].metadata.cklTechArea ?? ''
cklb.target_data.is_web_database = !!resultGetAsset[0].metadata.cklHostName
cklb.target_data.web_db_site = resultGetAsset[0].metadata.cklWebDbSite ?? ''
cklb.target_data.web_db_instance = resultGetAsset[0].metadata.cklWebDbInstance ?? ''
// cklb.stigs
const markings = []
for (const stigItem of stigs) {
const revisionStr = stigItem.revisionStr || 'latest'
revisionStrResolved = revisionStr
const benchmarkId = stigItem.benchmarkId
let sqlGetBenchmarkId
if (revisionStr === 'latest') {
sqlGetBenchmarkId = `select
cr.benchmarkId,
s.title,
cr.revId,
cr.description,
cr.version,
cr.release,
cr.benchmarkDate,
cr.ruleCount,
cr.marking
from
current_rev cr
left join stig s on cr.benchmarkId = s.benchmarkId
where
cr.benchmarkId = ?`
}
else {
sqlGetBenchmarkId = `select
r.benchmarkId,
s.title,
r.description,
r.version,
r.release,
r.benchmarkDate,
r.ruleCount,
r.marking
from
stig s
left join revision r on s.benchmarkId=r.benchmarkId
where
r.revId = ?`
}
// Calculate revId
let resultGetBenchmarkId, revId
if (revisionStr === 'latest') {
;[resultGetBenchmarkId] = await connection.query(sqlGetBenchmarkId, [benchmarkId])
revId = resultGetBenchmarkId[0].revId
revisionStrResolved = `V${resultGetBenchmarkId[0].version}R${resultGetBenchmarkId[0].release}`
}
else {
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
revId = `${benchmarkId}-${version}-${release}`
;[resultGetBenchmarkId] = await connection.execute(sqlGetBenchmarkId, [revId])
}
const stig = resultGetBenchmarkId[0]
// Set the marking
if (stig.marking) {
markings.push(stig.marking)
}
const stigUuid = randomUUID()
const stigObj = {
stig_name: stig.title,
display_name: stig.title.replace(' Security Technical Implementation Guide', ''),
stig_id: stig.benchmarkId,
version: `${stig.version}`,
release_info: `Release: ${stig.release} Benchmark Date: ${stig.benchmarkDate}`,
uuid: stigUuid,
reference_identifier: '0000',
size: stig.ruleCount,
rules: []
}
// cklb.stigs[x].rules
const [resultGetChecklist] = await connection.query(sqlGetChecklist, [assetId, revId])
for (const row of resultGetChecklist) {
const rule = {
uuid: randomUUID(),
stig_uuid: stigUuid,
target_key: null,
stig_ref: null,
group_id: row.groupId,
rule_id: row.ruleId.replace('_rule', ''),
rule_id_src: row.ruleId,
weight: row.weight,
classification: config.settings.setClassification,
severity: row.severity,
rule_version: row.version,
group_title: row.groupTitle,
rule_title: row.ruleTitle,
fix_text: row.fixText,
false_positives: row.falsePositives,
false_negatives: row.falseNegatives,
discussion: row.vulnDiscussion,
check_content: row.checkContent,
documentable: row.documentable,
mitigations: row.mitigations,
potential_impacts: row.potentialImpacts,
third_party_tools: row.thirdPartyTools,
mitigation_control: row.mitigationControl,
responsibility: row.responsibility,
security_override_guidance: row.severityOverrideGuidance,
ia_controls: row.iaControls,
check_content_ref: {
href: '',
name: 'M'
},
legacy_ids: [],
group_tree: [
{
id: row.groupId,
title: row.groupTitle,
description: ' '
}
],
createdAt: row.createdAt,
updatedAt: row.updatedAt,
STIGUuid: stigUuid,
status: row.result || 'not_reviewed',
overrides: {},
comments: row.comment ?? '',
finding_details: row.detail ?? ''
}
// CCI_REFs
rule.ccis = row.ccis ? row.ccis.split(',').map( cci => `CCI-${cci}`) : []
stigObj.rules.push(rule)
}
cklb.stigs.push(stigObj)
}
// calculate the marking for this checklist
let marking = config.settings.setClassification === 'NONE' ? 'U' : config.settings.setClassification
if (marking === 'U' || marking === 'CUI') {
const sortedMarkings = markings.toSorted((a, b) => a.localeCompare(b)) // because CUI, FOUO, U sort alphabetically
marking = sortedMarkings[0] || 'U'
}
return ({assetName: resultGetAsset[0].name, cklb, revisionStrResolved, marking})
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.xccdfFromAssetStig = async function (assetId, benchmarkId, revisionStr = 'latest') {
// queries and query methods
const sqlGetAsset = "select name, fqdn, ip, mac, noncomputing, metadata from enabled_asset where assetId = ?"
const sqlGetChecklist =`SELECT
rgr.groupId,
rgr.groupTitle,
rgr.ruleId,
rgr.title as "ruleTitle",
rgr.severity,
rgr.weight,
rgr.version,
rgr.checkSystem,
cc.content as "checkContent",
result.api as "result",
review.ts,
LEFT(review.detail,32767) as "detail",
LEFT(review.comment,32767) as "comment",
review.resultEngine
FROM
revision rev
left join rev_group_rule_map rgr on rev.revId = rgr.revId
left join check_content cc on rgr.checkDigest = cc.digest
left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId
left join review on (rvcd.version = review.version and rvcd.checkDigest = review.checkDigest and review.assetId = ?)
left join result on review.resultId = result.resultId
left join status on review.statusId = status.statusId
WHERE
rev.revId = ?
order by
substring(rgr.groupId from 3) + 0 asc
`
async function getBenchmarkRevision(connection, benchmarkId, revisionStr) {
let revisionStrResolved
// Benchmark, calculate revId
const sqlGetRevision = revisionStr === 'latest' ?
`select
cr.benchmarkId,
s.title,
cr.revId,
cr.description,
cr.version,
cr.release,
cr.benchmarkDate,
cr.status,
cr.statusDate,
cr.marking
from
current_rev cr
left join stig s on cr.benchmarkId = s.benchmarkId
where
cr.benchmarkId = ?`
:
`select
r.benchmarkId,
s.title,
r.revId,
r.description,
r.version,
r.release,
r.benchmarkDate,
r.status,
r.statusDate,
r.marking
from
stig s
left join revision r on s.benchmarkId=r.benchmarkId
where
r.revId = ?`
let result
if (revisionStr === 'latest') {
;[result] = await connection.query(sqlGetRevision, [benchmarkId])
revisionStrResolved = `V${result[0].version}R${result[0].release}`
}
else {
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
const revId = `${benchmarkId}-${version}-${release}`
;[result] = await connection.query(sqlGetRevision, [revId])
revisionStrResolved = revisionStr
}
result[0].revisionStr = revisionStrResolved
return result[0]
}
function prefixObjectProperties(prefix, obj) {
for (const k in obj)
{
if (typeof obj[k] == "object" && obj[k] !== null) {
prefixObjectProperties(prefix, obj[k])
}
if (!Array.isArray(obj)) {
obj[`${prefix}:${k}`] = obj[k]
delete obj[k]
}
}
}
function generateTargetFacts({metadata, ...assetFields}) {
const fact = []
for (const field in assetFields) {
if (assetFields[field]) {
fact.push({
'@_name': `tag:stig-manager@users.noreply.github.com,2020:asset:${field}`,
'@_type': 'string',
'#text': assetFields[field]
})
}
}
for (const key in metadata) {
if (key.startsWith('urn:')) {
fact.push({
'@_name': key,
'@_type': 'string',
'#text': metadata[key] || ''
})
}
else {
fact.push({
'@_name': `tag:stig-manager@users.noreply.github.com,2020:asset:metadata:${encodeURI(key)}`,
'@_type': 'string',
'#text': metadata[key] || ''
})
}
}
return {"cdf:fact": fact}
}
// reuse a connection for multiple SELECT queries
const connection = await dbUtils.pool.getConnection()
// target
const [resultGetAsset] = await connection.query(sqlGetAsset, [assetId])
// benchmark
const revision = await getBenchmarkRevision(connection, benchmarkId, revisionStr)
// checklist
const [resultGetChecklist] = await connection.query(sqlGetChecklist, [assetId, revision.revId])
// release connection
await connection.release()
// scaffold xccdf object with cdf namespace on all base elements
const xmlJs = {
"cdf:Benchmark": {
"@_xmlns:cdf": "http://checklists.nist.gov/xccdf/1.2",
"@_xmlns:dc": "http://purl.org/dc/elements/1.1/",
"@_xmlns:sm": "http://github.com/nuwcdivnpt/stig-manager",
"@_id": `xccdf_mil.disa.stig_benchmark_${revision.benchmarkId}`,
"cdf:status": {
"@_date": revision.statusDate,
"#text": revision.status
},
"cdf:title": revision.title,
"cdf:description": revision.description,
"cdf:platform": {
"@_idref": "cpe:2.3:a:disa:stig"
},
"cdf:version": revision.revisionStr,
"cdf:metadata": {
"dc:creator": "DISA",
"dc:publisher": "STIG Manager OSS"
},
"cdf:Group": [],
"cdf:TestResult": {
"@_id": `xccdf_mil.navy.nuwcdivnpt.stig-manager_testresult_${revision.benchmarkId}`,
"@_test-system": `cpe:/a:nuwcdivnpt:stig-manager:${config.version}`,
"@_end-time": new Date().toISOString(),
"@_version": "1.0",
"cdf:title": "",
"cdf:target": resultGetAsset[0].name,
"cdf:target-address": resultGetAsset[0].ip,
"cdf:target-facts": generateTargetFacts(resultGetAsset[0]),
"cdf:rule-result": [],
"cdf:score": "1.0"
}
}
}
// iterate through checklist query results
for (const r of resultGetChecklist) {
xmlJs["cdf:Benchmark"]["cdf:Group"].push({
"@_id": `xccdf_mil.disa.stig_group_${r.groupId}`,
"cdf:title": r.groupTitle,
"cdf:Rule": {
"@_id": `xccdf_mil.disa.stig_rule_${r.ruleId}`,
"@_weight": r.weight,
"@_severity": r.severity || undefined,
"cdf:title": r.ruleTitle,
"cdf:check": {
"@_system": r.checkSystem,
"cdf:check-content": r.checkContent
}
}
})
if (r.resultEngine) {
prefixObjectProperties('sm', r.resultEngine)
}
xmlJs["cdf:Benchmark"]["cdf:TestResult"]["cdf:rule-result"].push({
"cdf:result": r.result || "notchecked",
"@_idref": `xccdf_mil.disa.stig_rule_${r.ruleId}`,
"@_time": r.ts?.toISOString(),
"cdf:check": {
"@_system": r.checkSystem,
"cdf:check-content": {
"sm:detail": r.detail || undefined,
"sm:comment": r.comment || undefined,
"sm:resultEngine": r.resultEngine || undefined
}
}
})
}
let marking = config.settings.setClassification === 'NONE' ? 'U' : config.settings.setClassification
if (marking === 'U' || marking === 'CUI') {
marking = revision.marking || 'U' // if marking is not set, use U
}
return ({assetName: resultGetAsset[0].name, xmlJs, revisionStrResolved: revision.revisionStr, marking})
}
exports.createAssets = async function({ assets, collectionId, svcStatus = {} }) {
let insertedAssetIds = []
async function transactionFn(connection) {
await connection.query('DROP TEMPORARY TABLE IF EXISTS temp_assets')
// create temp table to hold incoming assets
const createTempTableSQL = `
CREATE TEMPORARY TABLE temp_assets (
tempId INT AUTO_INCREMENT PRIMARY KEY,
name VARCHAR(255),
fqdn VARCHAR(255),
ip VARCHAR(255),
mac VARCHAR(255),
description TEXT,
collectionId INT,
noncomputing TINYINT,
metadata JSON,
benchmarkIds JSON,
labelNames JSON,
assetId INT NULL
);`
await connection.query(createTempTableSQL)
const assetsJson = JSON.stringify(assets)
const insertTempAssetsSQL = `
INSERT INTO temp_assets (name, fqdn, ip, mac, description, collectionId, noncomputing, metadata, benchmarkIds, labelNames)
SELECT name, fqdn, ip, mac, description, collectionId, noncomputing, metadata, benchmarkIds, labelNames
FROM JSON_TABLE(?, '$[*]'
COLUMNS (
name VARCHAR(255) PATH '$.name',
fqdn VARCHAR(255) PATH '$.fqdn',
ip VARCHAR(255) PATH '$.ip',
mac VARCHAR(255) PATH '$.mac',
description TEXT PATH '$.description',
collectionId INT PATH '$.collectionId',
noncomputing TINYINT PATH '$.noncomputing',
metadata JSON PATH '$.metadata',
benchmarkIds JSON PATH '$.stigs',
labelNames JSON PATH '$.labelNames'
)
) AS jt`
await connection.query(insertTempAssetsSQL, [assetsJson]);
// insert into asset table
const insertAssetsSQL = `
INSERT INTO asset (name, fqdn, ip, mac, description, collectionId, noncomputing, metadata)
SELECT name, fqdn, ip, mac, description, collectionId, noncomputing, metadata
FROM temp_assets;`
await connection.query(insertAssetsSQL)
// update temp table with create assets assetIds
const updateTempWithAssetIdsSQL = `
UPDATE temp_assets t
INNER JOIN enabled_asset a
ON a.name = t.name
AND a.collectionId = t.collectionId
SET t.assetId = a.assetId;`
await connection.query(updateTempWithAssetIdsSQL)
const insertStigsSQL = `
INSERT INTO stig_asset_map (benchmarkId, assetId)
SELECT jt.benchmarkId, t.assetId
FROM temp_assets t
INNER JOIN JSON_TABLE(t.benchmarkIds, '$[*]'
COLUMNS (benchmarkId VARCHAR(255) PATH '$')
) AS jt
WHERE t.benchmarkIds IS NOT NULL;`
const [stigInsertResult] = await connection.query(insertStigsSQL)
const didInsertStigs = stigInsertResult.affectedRows > 0
// not sure abnout this left hoin ior not
const insertLabelsSQL = `
INSERT INTO collection_label_asset_map (assetId, clId)
SELECT t.assetId, cl.clId
FROM temp_assets t
INNER JOIN JSON_TABLE(t.labelNames, '$[*]'
COLUMNS (labelName VARCHAR(255) PATH '$')
) AS labels
LEFT JOIN collection_label cl
ON cl.name = labels.labelName
AND cl.collectionId = t.collectionId
WHERE t.labelNames IS NOT NULL;`
await connection.query(insertLabelsSQL)
// get assetIds of newly created assets
const [newAssets] = await connection.query('SELECT assetId FROM temp_assets')
insertedAssetIds = newAssets.map(asset => asset.assetId)
// if assets with stig assignment inserted, update default rev and collection revision map
if (didInsertStigs) {
await dbUtils.pruneCollectionRevMap(connection)
await dbUtils.updateDefaultRev(connection, { collectionId: parseInt(collectionId) })
}
}
await dbUtils.retryOnDeadlock2({ transactionFn, statusObj: svcStatus })
return insertedAssetIds
}
exports.deleteAsset = async function(assetId, userId, svcStatus) {
let connection
try {
connection = await dbUtils.pool.getConnection()
async function transaction () {
await connection.query('START TRANSACTION')
const sqlDelete = `UPDATE asset SET state = "disabled", stateDate = NOW(), stateUserId = ? where assetId = ?`
await connection.query(sqlDelete, [userId, assetId])
// changes above might have affected need for records in collection_rev_map
await dbUtils.pruneCollectionRevMap(connection)
await dbUtils.updateDefaultRev(connection, {})
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return true
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.deleteAssets = async function(assetIds, userId, svcStatus) {
let connection
try{
connection = await dbUtils.pool.getConnection()
async function transaction () {
await connection.query('START TRANSACTION')
const sqlDelete = `UPDATE asset SET state = "disabled", stateDate = NOW(), stateUserId = ? where assetId IN ?`
await connection.query(sqlDelete, [userId, [assetIds]])
// changes above might have affected need for records in collection_rev_map
await dbUtils.pruneCollectionRevMap(connection)
await dbUtils.updateDefaultRev(connection, {})
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.attachStigToAsset = async function ({assetId, benchmarkId, grant, svcStatus = {}}) {
let connection
try {
connection = await dbUtils.pool.getConnection()
async function transaction () {
await connection.query('START TRANSACTION')
const sqlInsert = `INSERT IGNORE INTO stig_asset_map (assetId, benchmarkId) VALUES (?, ?)`
const resultInsert = await connection.query(sqlInsert, [assetId, benchmarkId])
if (resultInsert[0].affectedRows != 0) {
// Inserted a new row, so update stats and default rev
await dbUtils.updateDefaultRev(connection, {
collectionId: grant.collectionId,
benchmarkId
})
await dbUtils.updateStatsAssetStig(connection, {
assetId,
benchmarkId
})
}
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return true
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw (err)
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.removeStigFromAsset = async function ({assetId, benchmarkId, grant, svcStatus} ) {
let connection
try{
connection = await dbUtils.pool.getConnection()
async function transaction () {
connection.query('START TRANSACTION')
const sqlDelete = `DELETE FROM stig_asset_map where assetId = ? and benchmarkId = ?`
await connection.query(sqlDelete, [assetId, benchmarkId])
// changes above might have affected need for records in collection_rev_map
await dbUtils.pruneCollectionRevMap(connection)
await dbUtils.updateDefaultRev(connection, {})
await connection.commit()
return true
}
return dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.removeStigsFromAsset = async function (assetId, grant, svcStatus) {
let connection
try{
connection = await dbUtils.pool.getConnection()
async function transaction () {
await connection.query('START TRANSACTION')
const sqlDelete = `DELETE FROM stig_asset_map where assetId = ?`
await connection.query(sqlDelete, [assetId])
// changes above might have affected need for records in collection_rev_map
await dbUtils.pruneCollectionRevMap(connection)
await dbUtils.updateDefaultRev(connection, {collectionId: grant.collectionId})
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return true
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.getAsset = async function({assetId, projections, grant}) {
const rows = await _this.queryAssets({
projections,
filter: {assetId},
grant})
return (rows[0])
}
exports.doesAssetExist = async function (assetId) {
const sql = `SELECT assetId FROM enabled_asset WHERE assetId = ?`
const [rows] = await dbUtils.pool.query(sql, [assetId])
return rows.length > 0
}
exports.getAssets = async function({filter, projections, grant}) {
return _this.queryAssets({
filter,
projections,
grant
})
}
exports.getStigsByAssetSlow = async function ({assetId, grant}) {
const ctes = []
const columns = [
'distinct sa.benchmarkId',
`concat('V', rev.version, 'R', rev.release) as revisionStr`,
`date_format(rev.benchmarkDateSql,'%Y-%m-%d') as revisionDate`,
'rev.ruleCount as ruleCount'
]
const joins = [
'enabled_asset a',
'left join enabled_collection c on a.collectionId = c.collectionId',
'inner join stig_asset_map sa on a.assetId = sa.assetId',
'left join default_rev dr on (sa.benchmarkId = dr.benchmarkId and a.collectionId = dr.collectionId)',
'left join revision rev on dr.revId = rev.revId'
]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
// PREDICATES
const predicates = {
statements: ['a.assetId = ?'],
binds: [assetId]
}
const orderBy = ['sa.benchmarkId']
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, orderBy, format: true})
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.getStigsByAsset = async function ({assetId, grant}) {
const ctes = []
const columns = [
'distinct sa.benchmarkId',
`concat('V', rev.version, 'R', rev.release) as revisionStr`,
`date_format(rev.benchmarkDateSql,'%Y-%m-%d') as revisionDate`,
'rev.ruleCount as ruleCount'
]
const joins = [
'enabled_asset a',
'left join enabled_collection c on a.collectionId = c.collectionId',
'inner join stig_asset_map sa on a.assetId = sa.assetId',
'left join default_rev dr on (sa.benchmarkId = dr.benchmarkId and a.collectionId = dr.collectionId)',
'left join revision rev on dr.revId = rev.revId'
]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
// PREDICATES
const predicates = {
statements: ['a.assetId = ?'],
binds: [assetId]
}
const orderBy = ['sa.benchmarkId']
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, orderBy, format: true})
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.getChecklistByAssetStig = async function(assetId, benchmarkId, revisionStr, format, projections = []) {
switch (format) {
case 'json':
case 'json-access': {
return _this.queryChecklist({
assetId,
benchmarkId,
revisionStr
}, projections)
}
case 'ckl':
return _this.cklFromAssetStigs(assetId, [{benchmarkId, revisionStr}])
case 'cklb':
return _this.cklbFromAssetStigs(assetId, [{benchmarkId, revisionStr}])
case 'xccdf':
return _this.xccdfFromAssetStig(assetId, benchmarkId, revisionStr)
}
}
exports.getChecklistByAsset = async function(assetId, benchmarks, format) {
switch (format) {
case 'ckl':
return _this.cklFromAssetStigs(assetId, benchmarks)
case 'cklb':
return _this.cklbFromAssetStigs(assetId, benchmarks)
}
}
exports.getAssetsByStig = async function({collectionId, benchmarkId, labels, grant}) {
const ctes = []
const columns = [
'DISTINCT CAST(a.assetId as char) as assetId',
'a.name',
'coalesce(any_value(cae.access), "rw") as access',
`coalesce(
(select
json_arrayagg(BIN_TO_UUID(cl.uuid,1))
from
collection_label_asset_map cla
left join collection_label cl on cla.clId = cl.clId
where
cla.assetId = a.assetId),
json_array()
) as assetLabelIds`,
`coalesce(
(select
json_arrayagg(json_object(
'labelId', BIN_TO_UUID(cl.uuid,1),
'name', cl.name,
'color', cl.color
))
from
collection_label_asset_map cla
left join collection_label cl on cla.clId = cl.clId
where
cla.assetId = a.assetId),
json_array()
) as assetLabels`,
'CAST(a.collectionId as char) as collectionId'
]
const joins = [
'enabled_collection c',
'inner join enabled_asset a on c.collectionId = a.collectionId',
'left join stig_asset_map sa on a.assetId = sa.assetId',
]
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push(`${grant.roleId === 1 ? 'inner' : 'left'} join cteAclEffective cae on sa.saId = cae.saId`)
// PREDICATES
const predicates = {
statements: [
'c.collectionId = ?',
'sa.benchmarkId = ?'
],
binds: [collectionId, benchmarkId]
}
if (labels?.labelNames || labels?.labelIds || labels?.labelMatch) {
joins.push(
'left join collection_label_asset_map cla2 on a.assetId = cla2.assetId',
'left join collection_label cl2 on cla2.clId = cl2.clId'
)
const labelPredicates = []
if (labels.labelIds) {
labelPredicates.push('cl2.uuid IN ?')
const uuidBinds = labels.labelIds.map( uuid => dbUtils.uuidToSqlString(uuid))
predicates.binds.push([uuidBinds])
}
if (labels.labelNames) {
labelPredicates.push('cl2.name IN ?')
predicates.binds.push([labels.labelNames])
}
if (labels.labelMatch === 'null') {
labelPredicates.push('cl2.uuid IS NULL')
}
const labelPredicatesClause = `(${labelPredicates.join(' OR ')})`
predicates.statements.push(labelPredicatesClause)
}
const groupBy = ['a.assetId']
const orderBy = [ 'a.name' ]
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.attachAssetsToStig = async function(collectionId, benchmarkId, assetIds, svcStatus = {}) {
let connection
try {
connection = await dbUtils.pool.getConnection()
async function transaction () {
await connection.query('START TRANSACTION')
let sqlDeleteBenchmarks = `
DELETE stig_asset_map FROM
stig_asset_map
left join enabled_asset a on stig_asset_map.assetId = a.assetId
WHERE
a.collectionId = ?
and stig_asset_map.benchmarkId = ?`
if (assetIds.length > 0) {
sqlDeleteBenchmarks += ' and stig_asset_map.assetId NOT IN ?'
}
// DELETE from stig_asset_map, which will cascade into user_stig_aset_map
await connection.query( sqlDeleteBenchmarks, [ collectionId, benchmarkId, [assetIds] ] )
// Push any bind values
let binds = []
assetIds.forEach( assetId => {
binds.push([benchmarkId, assetId])
})
if (binds.length > 0) {
// INSERT into stig_asset_map
let sqlInsertBenchmarks = `
INSERT IGNORE INTO
stig_asset_map (benchmarkId, assetId)
VALUES
?`
await connection.query(sqlInsertBenchmarks, [ binds ])
}
// changes above might have affected need for records in collection_rev_map
await dbUtils.pruneCollectionRevMap(connection)
await dbUtils.updateDefaultRev(connection, {
collectionId: collectionId,
benchmarkId: benchmarkId
})
await dbUtils.updateStatsAssetStig( connection, {
collectionId: collectionId,
benchmarkId: benchmarkId
})
// Commit the changes
await connection.commit()
}
return await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.updateAsset = async function( {assetId, body, currentCollectionId, transferring, svcStatus = {}} ) {
let connection
try {
// Extract or initialize non-scalar properties to separate variables
let binds
let { stigs, labelNames, ...assetFields } = body
// Convert boolean scalar values to database values (true=1 or false=0)
if (assetFields.hasOwnProperty('noncomputing')) {
assetFields.noncomputing = assetFields.noncomputing ? 1 : 0
}
if (assetFields.hasOwnProperty('metadata')) {
assetFields.metadata = JSON.stringify(assetFields.metadata)
}
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
async function transaction () {
await connection.query('START TRANSACTION')
// Process scalar properties
binds = { ...assetFields}
assetFields.collectionId ??= currentCollectionId
if (Object.keys(binds).length > 0) {
// UPDATE into assets
let sqlUpdate =
`UPDATE
asset
SET
?
WHERE
assetId = ?`
await connection.query(sqlUpdate, [assetFields, assetId])
if (transferring) {
await connection.query(
`DELETE FROM collection_grant_acl WHERE assetId = ?`,
[assetId]
)
const sqlGetAssetLabels = `SELECT name, description, color FROM collection_label_asset_map inner join collection_label using (clId) WHERE assetId = ?`
const [assetLabels] = await connection.query(sqlGetAssetLabels, [assetId])
const sqlDeleteLabels = `DELETE FROM collection_label_asset_map WHERE assetId = ?`
await connection.query(sqlDeleteLabels, [assetId])
if (assetLabels.length) {
const sqlGetCollectionLabels = `SELECT clId, name, description, color FROM collection_label WHERE collectionId = ?`
const [collectionLabels] = await connection.query(sqlGetCollectionLabels, [transferring.newCollectionId])
const collectionLabelNames = collectionLabels.reduce( (a,v) => {a[v.name] = v; return a}, {})
for (const assetLabel of assetLabels) {
if (collectionLabelNames[assetLabel.name]) {
await connection.query(`INSERT into collection_label_asset_map (assetId, clId) VALUES (?,?)`, [assetId, collectionLabelNames[assetLabel.name].clId])
}
else {
const [resultInsert] = await connection.query(`INSERT INTO collection_label (collectionId, name, description, color, uuid) VALUES (?, ?, ?, ?, UUID_TO_BIN(UUID(),1))`,
[transferring.newCollectionId, assetLabel.name, assetLabel.description, assetLabel.color])
const clId = resultInsert.insertId
await connection.query(`INSERT into collection_label_asset_map (assetId, clId) VALUES (?,?)`, [assetId, clId])
}
}
}
}
}
if (stigs) {
let sqlDeleteBenchmarks = `
DELETE FROM
stig_asset_map
WHERE
assetId = ?`
if (stigs.length > 0) {
sqlDeleteBenchmarks += ` and benchmarkId NOT IN ?`
}
// DELETE from stig_asset_map, which will cascade into user_stig_aset_map
await connection.query(sqlDeleteBenchmarks, [ assetId, [stigs] ])
if (stigs.length > 0) {
// Map bind values
let stigAssetMapBinds = stigs.map( benchmarkId => [benchmarkId, assetId])
// INSERT into stig_asset_map
let sqlInsertBenchmarks = `
INSERT IGNORE INTO
stig_asset_map (benchmarkId, assetId)
VALUES
?`
await connection.query(sqlInsertBenchmarks, [stigAssetMapBinds])
}
}
// Process labelIds, spec requires for CREATE/REPLACE not for UPDATE
if (labelNames) {
let sqlDeleteLabels = `
DELETE FROM
collection_label_asset_map
WHERE
assetId = ?`
await connection.query(sqlDeleteLabels, [ assetId ])
if (labelNames.length > 0) {
// INSERT into stig_asset_map
let sqlInsertLabels = `
INSERT INTO collection_label_asset_map (assetId, clId)
SELECT
?,
clId
FROM
collection_label
WHERE
name IN (?) and collectionId = ?`
await connection.query(sqlInsertLabels, [assetId, labelNames, assetFields.collectionId])
}
}
if (stigs || transferring) {
await dbUtils.pruneCollectionRevMap(connection)
if (transferring) {
await dbUtils.updateDefaultRev(connection, {collectionIds: [transferring.oldCollectionId, transferring.newCollectionId]})
}
else {
await dbUtils.updateDefaultRev(connection, {collectionId: currentCollectionId})
}
await dbUtils.updateStatsAssetStig( connection, {assetId} )
}
// Commit the changes
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return assetId
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.getAssetMetadataKeys = async function ( assetId ) {
const sql = `
select
JSON_KEYS(metadata) as keyArray
from
enabled_asset
where
assetId = ?`
const [rows] = await dbUtils.pool.query(sql, [assetId])
return rows.length > 0 ? rows[0].keyArray : []
}
exports.getAssetMetadata = async function ( assetId ) {
const sql = `
select
metadata
from
enabled_asset
where
assetId = ?`
const [rows] = await dbUtils.pool.query(sql, [assetId])
return rows.length > 0 ? rows[0].metadata : {}
}
exports.patchAssetMetadata = async function ( assetId, metadata ) {
const sql = `
update
asset
set
metadata = JSON_MERGE_PATCH(metadata, ?)
where
assetId = ?`
await dbUtils.pool.query(sql, [JSON.stringify(metadata), assetId])
return true
}
exports.putAssetMetadata = async function ( assetId, metadata ) {
const sql = `
update
asset
set
metadata = ?
where
assetId = ?`
await dbUtils.pool.query(sql, [JSON.stringify(metadata), assetId])
return true
}
exports.getAssetMetadataValue = async function ( assetId, key ) {
const sql = `
select
JSON_EXTRACT(metadata, ?) as value
from
enabled_asset
where
assetId = ?`
const [rows] = await dbUtils.pool.query(sql, [`$."${key}"`, assetId])
return rows.length > 0 ? rows[0].value : ""
}
exports.putAssetMetadataValue = async function ( assetId, key, value ) {
const sql = `
update
asset
set
metadata = JSON_SET(metadata, ?, ?)
where
assetId = ?`
const [rows] = await dbUtils.pool.query(sql, [`$."${key}"`, value, assetId])
return rows.length > 0 ? rows[0].value : ""
}
exports.deleteAssetMetadataKey = async function ( assetId, key ) {
const sql = `
update
asset
set
metadata = JSON_REMOVE(metadata, ?)
where
assetId = ?`
const [rows] = await dbUtils.pool.query(sql, [`$."${key}"`, assetId])
return rows.length > 0 ? rows[0].value : ""
}
================================================
FILE: api/source/service/CollectionService.js
================================================
'use strict';
const dbUtils = require('./utils')
const config = require('../utils/config.js')
const MyController = require('../controllers/Collection')
const SmError = require('../utils/error.js')
const _this = this
exports.queryCollection = async function ({collectionId, projections = [], elevate = false, grants = {}}) {
const groupBy = []
const orderBy = []
const ctes = []
const columns = [
'CAST(c.collectionId as char) as collectionId',
'c.name',
'c.description',
'c.settings',
'c.metadata'
]
const joins = ['enabled_collection c']
let requireCteGrantees = false
let requireCteAcls = false
let requireCteAssets = false
let requireCteStigs = false
let requireCteLabels = ''
const predicates = {
statements: [],
binds: []
}
const requesterRole = elevate ? 4 : grants[collectionId].roleId
const requesterGrantIds = grants[collectionId]?.grantIds
predicates.statements.push('c.collectionId = ?')
predicates.binds.push( collectionId )
if (projections.includes('assets')) {
let sqlAssets = `(select coalesce(${dbUtils.jsonArrayAgg({
value: `json_object(
'assetId', CAST(assetId as char),
'name', name)`,
orderBy: 'name'
})}, json_array()) from
${requesterRole === 1 ? 'cteAssets' : 'enabled_asset where collectionId = c.collectionId'}) as assets`
if (requesterRole === 1) {
requireCteAcls = true
requireCteAssets = true
}
columns.push(sqlAssets)
}
if (projections.includes('stigs')) {
if (requesterRole === 1) {
requireCteAcls = true
requireCteStigs = true
columns.push(`(select coalesce(json_arrayagg(json_object(
'benchmarkId', benchmarkId,
'revisionStr', revisionStr,
'benchmarkDate', benchmarkDate,
'revisionPinned', revisionPinned,
'ruleCount', ruleCount
)), json_array()) from cteStigs) as stigs`)
}
else {
columns.push(`(select coalesce(json_arrayagg(json_object(
'benchmarkId', cb.benchmarkId,
'revisionStr', revision.revisionStr,
'benchmarkDate', date_format(revision.benchmarkDateSql,'%Y-%m-%d'),
'revisionPinned', CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END,
'ruleCount', revision.ruleCount
)), json_array())
from
(select distinct sa.benchmarkId from enabled_asset a
inner join stig_asset_map sa on a.assetId = sa.assetId
where a.collectionId = c.collectionId) cb
left join default_rev dr on (cb.benchmarkId=dr.benchmarkId and dr.collectionId = c.collectionId)
left join revision on dr.revId = revision.revId) as stigs`)
}
}
if (projections.includes('grants')) {
columns.push(`(select
coalesce(
(select json_arrayagg(grantJson) from
(select
json_object(
'grantId', cast(grantId as char),
'user', json_object(
'userId', CAST(user_data.userId as char),
'username', user_data.username,
'displayName', COALESCE(
JSON_UNQUOTE(JSON_EXTRACT(user_data.lastClaims, "$.${config.oauth.claims.name}")),
user_data.username)),
'roleId', roleId)
as grantJson
from
collection_grant inner join user_data using (userId) where collectionId = c.collectionId
UNION
select
json_object(
'grantId', cast(grantId as char),
'userGroup', json_object(
'userGroupId', CAST(user_group.userGroupId as char),
'name', user_group.name,
'description', user_group.description
),
'roleId', roleId
) as grantJson
from collection_grant inner join user_group using (userGroupId) where collectionId = c.collectionId
) as grantJsons)
, json_array()
)
) as "grants"`)
}
if (projections.includes('users')) {
requireCteGrantees = true
columns.push(`(select
json_arrayagg(json_object(
'user', json_object(
'userId', CAST(ud.userId as char),
'username', ud.username,
'displayName', COALESCE(
JSON_UNQUOTE(JSON_EXTRACT(ud.lastClaims, "$.${config.oauth.claims.name}")),
ud.username)),
'roleId', cgs.roleId,
'grantees', cgs.grantees))
from cteGrantees cgs
inner join user_data ud on cgs.userId = ud.userId
) as users`)
}
if (projections.includes('labels')) {
if (requesterRole === 1) {
requireCteAcls = true
requireCteLabels = 'restricted'
}
else {
requireCteLabels = 'all'
}
columns.push(`(select
coalesce(json_arrayagg(json_object(
'labelId', labelId,
'name', name,
'description', description,
'color', color,
'uses', uses
)), json_array())
from
cteLabels) as labels`)
}
if (projections.includes('owners')) {
columns.push(`(select coalesce(json_arrayagg(grantJson),json_array()) from
(select user_data.username, json_object(
'userId', CAST(user_data.userId as char),
'username', user_data.username,
'displayName', JSON_UNQUOTE(JSON_EXTRACT(user_data.lastClaims, "$.${config.oauth.claims.name}"))
) as grantJson
from
collection_grant inner join user_data using (userId) where collectionId = c.collectionId and roleId = 4
UNION
select user_group.name, json_object(
'userGroupId', CAST(user_group.userGroupId as char),
'name', user_group.name,
'description', user_group.description
) as grantJson
from collection_grant inner join user_group using (userGroupId) where collectionId = c.collectionId and roleId = 4 order by username) o) as owners`)
}
if (projections.includes('statistics')) {
if (requesterRole === 1) {
requireCteGrantees = true
requireCteAcls = true
columns.push(`(select
json_object(
'created', DATE_FORMAT(c.created, '%Y-%m-%dT%TZ'),
'userCount', dt4.userCount,
'assetCount', dt4.assetCount,
'checklistCount', dt4.checklistCount
)
from
(SELECT
(select count(userId) from cteGrantees where collectionId = c.collectionId) as userCount,
(select count(distinct sa.assetId) from cteAclEffective cae left join stig_asset_map sa using (saId)) as assetCount,
(select count(saId) from cteAclEffective) as checklistCount) dt4
) as statistics`)
}
else {
requireCteGrantees = true
columns.push(`(select
json_object(
'created', DATE_FORMAT(c.created, '%Y-%m-%dT%TZ'),
'userCount', dt4.userCount,
'assetCount', dt4.assetCount,
'checklistCount', dt4.checklistCount
)
from
(SELECT
(select count(userId) from cteGrantees where collectionId = c.collectionId) as userCount,
(select count(distinct a.assetId) from enabled_asset a where a.collectionId = c.collectionId) as assetCount,
(select count(saId) from enabled_asset a left join stig_asset_map sa using (assetId) where a.collectionId = c.collectionId) as checklistCount) dt4
) as statistics`)
}
}
// setup ctes
if (requireCteGrantees) {
const cteGranteesParams = {collectionId: collectionId, returnCte: true}
ctes.push(dbUtils.sqlGrantees(cteGranteesParams))
}
if (requireCteAcls) {
ctes.push(dbUtils.cteAclEffective({grantIds: requesterGrantIds, includeColumnCollectionId: false}))
}
if (requireCteAssets) {
ctes.push(`cteAssets as (select distinct a.assetId, a.name from
cteAclRules ar
inner join stig_asset_map sa using (saId)
left join enabled_asset a using (assetId)
order by a.name)`)
}
if (requireCteStigs) {
ctes.push(`cteStigs as (
select distinct
sa.benchmarkId,
revision.revisionStr,
date_format(revision.benchmarkDateSql,'%Y-%m-%d') as benchmarkDate,
CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END as revisionPinned,
revision.ruleCount
from
cteAclRules ar
inner join stig_asset_map sa using (saId)
left join default_rev dr on (sa.benchmarkId=dr.benchmarkId and dr.collectionId = ${collectionId})
left join revision on dr.revId = revision.revId
order by sa.benchmarkId)`)
}
if (requireCteLabels) {
ctes.push(`cteLabels as (
select
BIN_TO_UUID(cl.uuid,1) labelId,
cl.name,
cl.description,
cl.color,
count(distinct cla.claId) as uses
from
collection_label cl
left join collection_label_asset_map cla on cla.clId = cl.clId
${requireCteLabels === 'restricted' ? 'left join stig_asset_map sa on cla.assetId = sa.assetId' : ''}
${requireCteLabels === 'restricted' ? 'inner join cteAclEffective cae on sa.saId = cae.saId' : ''}
where
cl.collectionId = ${collectionId}
group by
cl.clId)`)
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return rows[0]
}
/**
Generalized queries for collection(s).
**/
exports.queryCollections = async function ({projections = [], filter = {}, elevate = false, grants = {}, userId = ''}) {
const collectionIdsGranted = Object.keys(grants)
if (!collectionIdsGranted.length && !elevate) {
return []
}
const ctes = []
const columns = [
'CAST(c.collectionId as char) as collectionId',
'c.name',
'c.description',
'c.settings',
'c.metadata'
]
const joins = ['enabled_collection c']
const predicates = {
statements: [],
binds: []
}
const orderBy = ['c.name']
let requireCteGrantees = false
let requireCteAcls = false
let requesterGrantIds = []
if (!elevate) {
for (const collectionId in grants) {
requesterGrantIds.push(grants[collectionId].grantIds)
}
requesterGrantIds = requesterGrantIds.flat()
}
if (projections.includes('owners')) {
columns.push(`(select coalesce(json_arrayagg(grantJson),json_array()) from
(select json_object(
'userId', CAST(user_data.userId as char),
'username', user_data.username,
'displayName', JSON_UNQUOTE(JSON_EXTRACT(user_data.lastClaims, "$.${config.oauth.claims.name}"))
) as grantJson
from
collection_grant inner join user_data using (userId) where collectionId = c.collectionId and roleId = 4
UNION
select json_object(
'userGroupId', CAST(user_group.userGroupId as char),
'name', user_group.name,
'description', user_group.description
) as grantJson
from collection_grant inner join user_group using (userGroupId) where collectionId = c.collectionId and roleId = 4) o) as owners`)
}
if (projections.includes('statistics')) {
if (!elevate) {
requireCteGrantees = true
requireCteAcls = true
columns.push(`(select
json_object(
'created', DATE_FORMAT(c.created, '%Y-%m-%dT%TZ'),
'userCount', dt4.userCount,
'assetCount', case when dt4.roleId = 1 then dt4.assetGrantedCount else dt4.assetCount end,
'checklistCount', case when dt4.roleId = 1 then dt4.checklistGrantedCount else dt4.checklistCount end
)
from
(SELECT
(select roleId from cteGrantees where collectionId = c.collectionId and userId = ?) as roleId,
(select count(userId) from cteGrantees where collectionId = c.collectionId) as userCount,
(select count(distinct a.assetId) from enabled_asset a where a.collectionId = c.collectionId) as assetCount,
(select count(distinct sa.assetId) from cteAclEffective cae left join stig_asset_map sa using (saId) where cae.collectionId = c.collectionId) as assetGrantedCount,
(select count(sa.saId) from enabled_asset a left join stig_asset_map sa using (assetId) where a.collectionId = c.collectionId) as checklistCount,
(select count(saId) from cteAclEffective where collectionId = c.collectionId) as checklistGrantedCount
) dt4
) as statistics`)
predicates.binds.push(userId)
}
else {
requireCteGrantees = true
columns.push(`(select
json_object(
'created', DATE_FORMAT(c.created, '%Y-%m-%dT%TZ'),
'userCount', dt4.userCount,
'assetCount', dt4.assetCount,
'checklistCount', dt4.checklistCount
)
from
(SELECT
(select count(userId) from cteGrantees where collectionId = c.collectionId) as userCount,
(select count(distinct a.assetId) from enabled_asset a where a.collectionId = c.collectionId) as assetCount,
(select count(sa.saId) from enabled_asset a left join stig_asset_map sa using (assetId) where a.collectionId = c.collectionId) as checklistCount) dt4
) as statistics`)
}
}
// This projection is not exposed in the OAS, only used by Operation.getAppData()
if (projections.includes('grants')) {
columns.push(`(select
coalesce(
(select json_arrayagg(grantJson) from
(select
json_object(
'user', json_object(
'userId', CAST(user_data.userId as char),
'username', user_data.username,
'displayName', COALESCE(
JSON_UNQUOTE(JSON_EXTRACT(user_data.lastClaims, "$.${config.oauth.claims.name}")),
user_data.username)),
'roleId', roleId)
as grantJson
from
collection_grant inner join user_data using (userId) where collectionId = c.collectionId
UNION
select
json_object(
'userGroup', json_object(
'userGroupId', CAST(user_group.userGroupId as char),
'name', user_group.name,
'description', user_group.description
),
'roleId', roleId
) as grantJson
from collection_grant inner join user_group using (userGroupId) where collectionId = c.collectionId
) as grantJsons)
, json_array()
)
) as "grants"`)
}
if (!elevate) {
predicates.statements.push('c.collectionId IN (?)')
predicates.binds.push( collectionIdsGranted )
}
if ( filter.name ) {
let matchStr = '= ?'
if ( filter.nameMatch && filter.nameMatch !== 'exact') {
matchStr = 'LIKE ?'
switch (filter.nameMatch) {
case 'startsWith':
filter.name = `${filter.name}%`
break
case 'endsWith':
filter.name = `%${filter.name}`
break
case 'contains':
filter.name = `%${filter.name}%`
break
}
}
predicates.statements.push(`c.name ${matchStr}`)
predicates.binds.push( filter.name )
}
if ( filter.metadata ) {
for (const pair of filter.metadata) {
const [key, value] = pair.split(/:(.*)/s)
predicates.statements.push('JSON_CONTAINS(c.metadata, ?, ?)')
predicates.binds.push( `"${value}"`, `$.${key}`)
}
}
if (requireCteGrantees) {
const cteGranteesParams = elevate ? {returnCte: true} : {collectionIds: collectionIdsGranted, returnCte: true}
ctes.push(dbUtils.sqlGrantees(cteGranteesParams))
}
if (requireCteAcls) {
ctes.push(dbUtils.cteAclEffective({grantIds: requesterGrantIds}))
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return rows
}
exports.doesCollectionExist = async function (collectionId) {
const sql = `SELECT collectionId FROM enabled_collection WHERE collectionId = ?`
const [rows] = await dbUtils.pool.query(sql, [collectionId])
return rows.length > 0
}
exports.addOrUpdateCollection = async function(writeAction, collectionId, body, projection, userObject, svcStatus = {}) {
// CREATE: collectionId will be null
// REPLACE/UPDATE: collectionId is not null
let connection // available to try, catch, and finally blocks
try {
const {grants, labels, ...collectionFields} = body
// Stringify JSON values
collectionFields.metadata = JSON.stringify(collectionFields.metadata ?? {})
// Merge default settings with any provided settings
if( writeAction === dbUtils.WRITE_ACTION.CREATE || writeAction === dbUtils.WRITE_ACTION.REPLACE ) {
collectionFields.settings = JSON.stringify({...MyController.defaultSettings, ...collectionFields.settings})
}
else if(collectionFields.settings) {
collectionFields.settings = JSON.stringify(collectionFields.settings)
}
// Connect to MySQL
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
async function transaction () {
await connection.query('START TRANSACTION');
// Process scalar properties
if (writeAction === dbUtils.WRITE_ACTION.CREATE) {
// INSERT into collections
let sqlInsert =
`INSERT INTO
collection
(name, description, settings, metadata)
VALUES
(:name, :description, :settings, :metadata)`
let [rows] = await connection.execute(sqlInsert, collectionFields)
collectionId = rows.insertId
}
else if (writeAction === dbUtils.WRITE_ACTION.UPDATE || writeAction === dbUtils.WRITE_ACTION.REPLACE) {
if (Object.keys(collectionFields).length > 0) {
// UPDATE into collections
const sqlUpdate = `UPDATE collection SET ? WHERE collectionId = ?`
await connection.query(sqlUpdate, [collectionFields, collectionId])
}
}
else {
throw new SmError.InternalError('Invalid writeAction')
}
// process grants
if (grants) {
if (grants.length) {
const grantsByIdType = grants.reduce((accumulator, currentValue) => {
accumulator[currentValue.userId ? 'userGrants' : 'userGroupGrants'].push(currentValue)
return accumulator
}, {userGrants:[], userGroupGrants:[]})
if (grantsByIdType.userGrants.length) {
await connection.query(
`DELETE FROM collection_grant WHERE collectionId = ? and userId NOT IN (?)`,
[collectionId, grantsByIdType.userGrants.map(i => i.userId)]
)
const sqlInsertUserGrants = `INSERT
INTO
collection_grant (collectionId, userId, roleId)
VALUES
? as new
ON DUPLICATE KEY UPDATE
roleId = new.roleId`
const binds = grantsByIdType.userGrants.map(i => [collectionId, i.userId, i.roleId])
await connection.query(sqlInsertUserGrants, [binds])
}
else {
await connection.query(`DELETE FROM collection_grant WHERE collectionId = ? and userId is not null`, [collectionId])
}
if (grantsByIdType.userGroupGrants.length) {
await connection.query(
`DELETE FROM collection_grant WHERE collectionId = ? and userGroupId NOT IN (?)`,
[collectionId, grantsByIdType.userGroupGrants.map(i => i.userGroupId)]
)
const sqlInsertGroupGrants = `INSERT
INTO
collection_grant (collectionId, userGroupId, roleId)
VALUES
? as new
ON DUPLICATE KEY UPDATE
roleId = new.roleId`
const binds = grantsByIdType.userGroupGrants.map(i => [collectionId, i.userGroupId, i.roleId])
await connection.query(sqlInsertGroupGrants, [binds])
}
else {
await connection.query(`DELETE FROM collection_grant WHERE collectionId = ? and userGroupId is not null`, [collectionId])
}
}
else if (writeAction !== dbUtils.WRITE_ACTION.CREATE) {
await connection.query(`DELETE FROM collection_grant WHERE collectionId = ?`, [collectionId])
await connection.query(`DELETE FROM collection_grant_group WHERE collectionId = ?`, [collectionId])
}
}
// Process labels
if (labels && writeAction !== dbUtils.WRITE_ACTION.CREATE) {
// DELETE from collection_label
let sqlDeleteLabels = 'DELETE FROM collection_label where collectionId = ?'
await connection.execute(sqlDeleteLabels, [collectionId])
}
if (labels && labels.length > 0) {
// INSERT into collection_label
let sqlInsertLabels = `
INSERT INTO
collection_label (collectionId, name, description, color, uuid)
VALUES
?`
const binds = labels.map(i => [collectionId, i.name, i.description, i.color, {
toSqlString: function () {
return `UUID_TO_BIN(UUID(),1)`
}
}])
await connection.query(sqlInsertLabels, [binds])
}
// Commit the changes
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
await connection.rollback()
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
let row = await _this.getCollection(collectionId, projection, true, userObject)
return row
}
/**
* Create a Collection
*
* body CollectionAssign (optional)
* returns List
**/
exports.createCollection = async function(body, projection, userObject, svcStatus = {}) {
let row = await _this.addOrUpdateCollection(dbUtils.WRITE_ACTION.CREATE, null, body, projection, userObject, svcStatus)
return (row)
}
/**
* Delete a Collection
*
* collectionId Integer A path parameter that identifies a Collection
**/
exports.deleteCollection = async function(collectionId, userId) {
const sqlDelete = `UPDATE collection SET state = "disabled", stateDate = NOW(), stateUserId = ? where collectionId = ?`
return dbUtils.pool.query(sqlDelete, [userId, collectionId])
}
/**
* Return the Checklist for the supplied Collection and STIG
*
* collectionId Integer A path parameter that identifies a Collection
* benchmarkId String A path parameter that identifies a STIG
* revisionStr String A path parameter that identifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns CollectionChecklist
**/
exports.getChecklistByCollectionStig = async function (collectionId, benchmarkId, revisionStr, userObject ) {
const ctes = []
const groupBy = ['rgr.rgrId']
const orderBy = ['rgr.ruleId']
const columns = [
`rgr.ruleId
,rgr.title as ruleTitle
,rgr.severity
,rgr.\`version\`
,rgr.groupId
,rgr.groupTitle
,json_object(
'results', json_object(
'pass', sum(CASE WHEN r.resultId = 3 THEN 1 ELSE 0 END),
'fail', sum(CASE WHEN r.resultId = 4 THEN 1 ELSE 0 END),
'notapplicable', sum(CASE WHEN r.resultId = 2 THEN 1 ELSE 0 END),
'other', sum(CASE WHEN r.resultId is null OR (r.resultId != 2 AND r.resultId != 3 AND r.resultId != 4) THEN 1 ELSE 0 END)
),
'statuses', json_object(
'saved', sum(CASE WHEN r.statusId = 0 THEN 1 ELSE 0 END),
'submitted', sum(CASE WHEN r.statusId = 1 THEN 1 ELSE 0 END),
'rejected', sum(CASE WHEN r.statusId = 2 THEN 1 ELSE 0 END),
'accepted', sum(CASE WHEN r.statusId = 3 THEN 1 ELSE 0 END)
)
) as counts
,json_object(
'ts', json_object(
'min', DATE_FORMAT(MIN(r.ts),'%Y-%m-%dT%H:%i:%sZ'),
'max', DATE_FORMAT(MAX(r.ts),'%Y-%m-%dT%H:%i:%sZ')
),
'statusTs', json_object(
'min', DATE_FORMAT(MIN(r.statusTs),'%Y-%m-%dT%H:%i:%sZ'),
'max', DATE_FORMAT(MAX(r.statusTs),'%Y-%m-%dT%H:%i:%sZ')
),
'touchTs', json_object(
'min', DATE_FORMAT(MIN(r.touchTs),'%Y-%m-%dT%H:%i:%sZ'),
'max', DATE_FORMAT(MAX(r.touchTs),'%Y-%m-%dT%H:%i:%sZ')
)
) as timestamps`
]
const joins = [
'enabled_asset a',
'left join stig_asset_map sa using (assetId)',
'left join current_rev rev using (benchmarkId)',
'left join rev_group_rule_map rgr using (revId)',
'left join rule_version_check_digest rvcd using (ruleId)',
'left join review r on (rvcd.version=r.version and rvcd.checkDigest=r.checkDigest and sa.assetId=r.assetId)'
]
const predicates = {
statements: [
'a.collectionId = ?',
'rev.benchmarkId = ?',
],
binds: [
collectionId,
benchmarkId
]
}
// Non-current revision
if (revisionStr !== 'latest') {
joins.splice(2, 1, 'left join revision rev on sa.benchmarkId=rev.benchmarkId')
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
predicates.statements.push('rev.version = ?', 'rev.release = ?')
predicates.binds.push(version, release)
}
// Access control
const grant = userObject.grants[collectionId]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const sql = dbUtils.makeQueryString({
ctes,
columns,
joins,
predicates,
groupBy,
orderBy,
format: true
})
// Send query
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
/**
* Return a Collection
*
* collectionId Integer A path parameter that identifies a Collection
* returns CollectionInfo
**/
exports.getCollection = async function(collectionId, projections, elevate, userObject) {
return _this.queryCollection({
collectionId,
projections,
elevate,
grants: userObject.grants
})
}
exports.getFindingsByCollection = async function( {collectionId, aggregator, benchmarkId, assetId, acceptedOnly, projections = [], grant} ) {
let columns, groupBy, orderBy
switch (aggregator) {
case 'ruleId':
columns = [
'rgr.ruleId',
'rgr.title',
'rgr.severity',
'count(distinct a.assetId) as assetCount'
]
groupBy = [
'rgr.rgrId'
]
orderBy = ['rgr.ruleId']
break
case 'groupId':
columns = [
'rgr.groupId',
'rgr.groupTitle as title',
'rgr.severity',
'count(distinct a.assetId) as assetCount'
]
groupBy = [
'rgr.rgrId'
]
orderBy = ['substring(rgr.groupId from 3) + 0']
break
case 'cci':
columns = [
'cci.cci',
'cci.definition',
'cci.apAcronym',
'count(distinct a.assetId) as assetCount'
]
groupBy = [
'cci.cci'
]
orderBy = ['cci.cci']
break
}
const ctes = []
const joins = [
'enabled_collection c',
'inner join enabled_asset a on (c.collectionId = a.collectionId)',
'inner join stig_asset_map sa on a.assetId = sa.assetId',
'left join default_rev dr on (sa.benchmarkId = dr.benchmarkId and c.collectionId = dr.collectionId)',
'left join rev_group_rule_map rgr on dr.revId = rgr.revId',
'left join rev_group_rule_cci_map rgrcc using (rgrId)',
'left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId',
'inner join review rv on (rvcd.version = rv.version and rvcd.checkDigest = rv.checkDigest and a.assetId = rv.assetId and rv.resultId = 4)',
'inner join cci on rgrcc.cci = cci.cci',
'inner join cci_reference_map crm on cci.cci = crm.cci'
]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
// Not exposed in API, used internally
if (projections.includes('rulesWithDiscussion')) {
columns.push(`cast(concat('[', group_concat(distinct json_object (
'ruleId', rgr.ruleId,
'title', rgr.title,
'severity', rgr.severity,
'vulnDiscussion', rgr.vulnDiscussion) order by rgr.ruleId), ']') as json) as "rules"`)
}
if (projections.includes('rules')) {
columns.push(`cast(concat('[', group_concat(distinct json_object (
'ruleId', rgr.ruleId,
'title', rgr.title,
'version', rgr.version,
'severity', rgr.severity) order by rgr.ruleId), ']') as json) as "rules"`)
}
if (projections.includes('groups')) {
columns.push(`cast(concat('[', group_concat(distinct json_object (
'groupId', rgr.groupId,
'title', rgr.groupTitle,
'severity', rgr.groupSeverity) order by rgr.groupId), ']') as json) as "groups"`)
}
if (projections.includes('assets')) {
columns.push(`cast(concat('[', group_concat(distinct json_object (
'assetId', CAST(a.assetId as char),
'name', a.name) order by a.name), ']') as json) as "assets"`)
}
if (projections.includes('stigs')) {
joins.push('left join revision on dr.revId = revision.revId')
columns.push(`cast(
concat('[',
coalesce (
group_concat(distinct
case when revision.benchmarkId is not null then
json_object(
'benchmarkId', revision.benchmarkId,
'revisionStr', revision.revisionStr,
'benchmarkDate', date_format(revision.benchmarkDateSql,'%Y-%m-%d'),
'revisionPinned', CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END,
'ruleCount', revision.ruleCount)
else null end
order by revision.benchmarkId),
''),
']')
as json) as "stigs"`)
// columns.push(`cast( concat( '[', group_concat(distinct concat('"',dr.benchmarkId,'"')), ']' ) as json ) as "stigs"`)
}
if (projections.includes('ccis')) {
columns.push(`cast(concat('[',
coalesce(
group_concat(distinct
case when cci.cci is not null
then json_object(
'cci', cci.cci,
'definition', cci.definition,
'apAcronym', cci.apAcronym,
'control', crm.parentControl)
else null end order by cci.cci),
''),
']') as json) as "ccis"`)
}
const predicates = {
statements: [
'c.collectionId = ?'
],
binds: [collectionId]
}
if (assetId) {
predicates.statements.push('a.assetId = ?')
predicates.binds.push( assetId )
}
if (acceptedOnly) {
predicates.statements.push('rv.statusId = ?')
predicates.binds.push( 3 )
}
if (benchmarkId) {
predicates.statements.push('dr.benchmarkId = ?')
predicates.binds.push( benchmarkId )
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.getReviewAclByCollectionUser = async function (collectionId, userId, elevate, userObject) {
let rows = await _this.queryReviewAcl({collectionId, userId})
return (rows)
}
exports.getReviewAclByCollectionUserGroup = async function (collectionId, userGroupId, elevate, userObject) {
let rows = await _this.queryReviewAcl({collectionId, userGroupId})
return (rows)
}
exports.getStigsByCollection = async function({collectionId, labelIds, labelNames, labelMatch, grant, benchmarkId, projections}) {
const ctes = []
const columns = [
'sa.benchmarkId',
'stig.title',
'revision.revisionStr',
`date_format(revision.benchmarkDateSql,'%Y-%m-%d') as benchmarkDate`,
'CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END as revisionPinned',
'revision.ruleCount',
'count(sa.assetId) as assetCount'
]
const groupBy = ['sa.benchmarkId', 'revision.revId', 'dr.revisionPinned', 'stig.benchmarkId']
const orderBy = ['sa.benchmarkId']
const joins = [
'enabled_collection c',
'left join enabled_asset a on c.collectionId = a.collectionId',
'inner join stig_asset_map sa on a.assetId = sa.assetId',
'left join default_rev dr on (sa.benchmarkId = dr.benchmarkId and c.collectionId = dr.collectionId)',
'left join revision on dr.revId = revision.revId',
'left join stig on revision.benchmarkId = stig.benchmarkId'
]
// PREDICATES
const predicates = {
statements: [
'c.collectionId = ?'
],
binds: [collectionId]
}
if (labelIds || labelNames || labelMatch) {
joins.push(
'left join collection_label_asset_map cla2 on a.assetId = cla2.assetId',
'left join collection_label cl2 on cla2.clId = cl2.clId'
)
const labelPredicates = []
if (labelIds) {
labelPredicates.push('cl2.uuid IN ?')
const uuidBinds = labelIds.map( uuid => dbUtils.uuidToSqlString(uuid))
predicates.binds.push([uuidBinds])
}
if (labelNames) {
labelPredicates.push('cl2.name IN ?')
predicates.binds.push([labelNames])
}
if (labelMatch === 'null') {
labelPredicates.push('cl2.uuid IS NULL')
}
const labelPredicatesClause = `(${labelPredicates.join(' OR ')})`
predicates.statements.push(labelPredicatesClause)
}
if (benchmarkId) {
predicates.statements.push('sa.benchmarkId = ?')
predicates.binds.push( benchmarkId )
}
if (projections?.includes('assets')) {
columns.push(`cast(concat('[', group_concat(distinct json_object (
'assetId', CAST(a.assetId as char),
'name', a.name) order by a.name), ']') as json) as "assets"`)
}
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
/**
* Replace all properties of a Collection
*
* body CollectionAssign (optional)
* collectionId Integer A path parameter that identifies a Collection
* returns CollectionInfo
**/
exports.replaceCollection = async function( collectionId, body, projection, userObject, svcStatus = {}) {
let row = await _this.addOrUpdateCollection(dbUtils.WRITE_ACTION.REPLACE, collectionId, body, projection, userObject, svcStatus)
return (row)
}
/**
* Merge updates to a Collection
*
* body CollectionAssign (optional)
* collectionId Integer A path parameter that identifies a Collection
* returns CollectionInfo
**/
exports.updateCollection = async function( collectionId, body, projection, userObject, svcStatus = {}) {
let row = await _this.addOrUpdateCollection(dbUtils.WRITE_ACTION.UPDATE, collectionId, body, projection, userObject, svcStatus)
return (row)
}
exports.getCollectionMetadataKeys = async function ( collectionId ) {
const binds = []
let sql = `
select
JSON_KEYS(metadata) as keyArray
from
enabled_collection
where
collectionId = ?`
binds.push(collectionId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].keyArray : []
}
exports.getCollectionMetadata = async function ( collectionId ) {
const binds = []
let sql = `
select
metadata
from
enabled_collection
where
collectionId = ?`
binds.push(collectionId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].metadata : {}
}
exports.patchCollectionMetadata = async function ( collectionId, metadata ) {
const binds = []
let sql = `
update
collection
set
metadata = JSON_MERGE_PATCH(metadata, ?)
where
collectionId = ?`
binds.push(JSON.stringify(metadata), collectionId)
await dbUtils.pool.query(sql, binds)
return true
}
exports.putCollectionMetadata = async function ( collectionId, metadata ) {
const binds = []
let sql = `
update
collection
set
metadata = ?
where
collectionId = ?`
binds.push(JSON.stringify(metadata), collectionId)
await dbUtils.pool.query(sql, binds)
return true
}
exports.getCollectionMetadataValue = async function ( collectionId, key ) {
const binds = []
let sql = `
select
JSON_EXTRACT(metadata, ?) as value
from
enabled_collection
where
collectionId = ?`
binds.push(`$."${key}"`, collectionId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].value : ""
}
exports.putCollectionMetadataValue = async function ( collectionId, key, value ) {
const binds = []
let sql = `
update
collection
set
metadata = JSON_SET(metadata, ?, ?)
where
collectionId = ?`
binds.push(`$."${key}"`, value, collectionId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].value : ""
}
exports.deleteCollectionMetadataKey = async function ( collectionId, key ) {
const binds = []
let sql = `
update
collection
set
metadata = JSON_REMOVE(metadata, ?)
where
collectionId = ?`
binds.push(`$."${key}"`, collectionId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].value : ""
}
/*
Available only to level 3 or 4 users ("Manage" or "Owner")
Returns number of history entries deleted.
RetentionDate - Delete all review history entries prior to the specified date.
Asset Id - if provided, only delete entries for that asset.
*/
exports.deleteReviewHistoryByCollection = async function (collectionId, retentionDate, assetId) {
let sql = `
DELETE rh
FROM review_history rh
INNER JOIN review r on rh.reviewId = r.reviewId
INNER JOIN enabled_asset a on r.assetId = a.assetId
WHERE a.collectionId = :collectionId
AND rh.touchTs < :retentionDate`
if(assetId) {
sql += ' AND a.assetId = :assetId'
}
let binds = {
collectionId: collectionId,
retentionDate: retentionDate,
assetId: assetId
}
let [rows] = await dbUtils.pool.query(sql, binds)
let result = {
HistoryEntriesDeleted: rows.affectedRows
}
return (result)
}
/*
GET /collections/{collectionId}/review-history
Available to level 2 and higher users with a grant to the collection.
Returns block of review history entries that fit criteria. Takes optional:
Start Date
End Date
(If no dates provided, return all history. If only one date, return block from that date to current, or that date to oldest, as appropriate)
Asset ID - only return history for this asset id
Rule ID - only return history for this rule id
status- only return history with this status
If rule and asset id provided, return that intersection.
*/
exports.getReviewHistoryByCollection = async function (collectionId, startDate, endDate, assetId, ruleId, status) {
const columns = [
`CAST(innerQuery.assetId as char) as assetId,
json_arrayagg(
json_object(
'ruleId', innerQuery.ruleId,
'history', innerQuery.history
)
) as reviewHistories
from
(select
a.assetId,
rv.ruleId,
json_arrayagg(
json_object(
'ts', DATE_FORMAT(rh.ts, '%Y-%m-%dT%TZ'),
'ruleId', rh.ruleId,
'result', result.api,
'detail', COALESCE(LEFT(rh.detail,32767), ''),
'comment', COALESCE(LEFT(rh.comment,32767), ''),
'autoResult', rh.autoResult = 1,
'status', JSON_OBJECT(
'label', status.api,
'text', rh.statusText,
'user', JSON_OBJECT(
'userId', CAST(rh.statusUserId as char),
'username', udStatus.username
),
'ts', DATE_FORMAT(rh.statusTs, '%Y-%m-%dT%TZ')
),
'userId', CAST(rh.userId as char),
'username', ud.username,
'touchTs', DATE_FORMAT(rh.touchTs, '%Y-%m-%dT%TZ')
)
) as history`
]
const joins = [
'review_history rh',
'INNER JOIN review rv on rh.reviewId = rv.reviewId',
'INNER JOIN user_data ud on rh.userId = ud.userId',
'left join user_data udStatus on udStatus.userId=rh.statusUserId',
'INNER JOIN result on rh.resultId = result.resultId',
'INNER JOIN status on rh.statusId = status.statusId',
'inner join enabled_asset a on a.assetId = rv.assetId'
]
let predicates = {
statements: ['rv.assetId = a.assetId',
'a.collectionId = ?'],
binds: [collectionId]
}
let groupBy = []
if (startDate) {
predicates.binds.push(startDate)
predicates.statements.push('rh.touchTs >= ?')
}
if (endDate) {
predicates.binds.push(endDate)
predicates.statements.push('rh.touchTs <= ?')
}
if(ruleId) {
predicates.binds.push(ruleId)
predicates.statements.push('rv.ruleId = ?')
}
if(status) {
predicates. binds.push(dbUtils.REVIEW_STATUS_API[status])
predicates.statements.push('rh.statusId = ?')
}
if(assetId) {
predicates.binds.push(assetId)
predicates.statements.push('a.assetId = ?')
}
groupBy.push('rv.ruleId', 'a.assetId ) innerQuery\nGROUP BY\n innerQuery.assetId')
let sql = dbUtils.makeQueryString({columns, joins, predicates,groupBy })
let [rows] = await dbUtils.pool.query(sql, predicates.binds)
return (rows)
}
/*
GET /collections/{collectionId}/review-history/stats
Available to level 2 and higher users with a grant to the collection.
Return some simple stats about the number/properties of history entries.
Uses same params as GET review-history, expecting stats to be scoped to whatever would be returned by that query.
Projection: asset - Break out statistics by Asset in the specified collection
*/
exports.getReviewHistoryStatsByCollection = async function (collectionId, startDate, endDate, assetId, ruleId, status, projection) {
let binds = {
collectionId: collectionId
}
let sql = 'SELECT COUNT(*) as collectionHistoryEntryCount, MIN(rh.touchTs) as oldestHistoryEntryDate'
// If there is a response and the request included the asset projection
if (projection?.includes('asset')) {
sql += `, coalesce(
(SELECT json_arrayagg(
json_object(
'assetId', CAST(assetId as char) ,
'historyEntryCount', historyEntryCount,
'oldestHistoryEntry', oldestHistoryEntry
)
)
FROM
(
SELECT a.assetId, COUNT(*) as historyEntryCount, MIN(rh.touchTs) as oldestHistoryEntry
FROM review_history rh
INNER JOIN review rv on rh.reviewId = rv.reviewId
INNER JOIN enabled_asset a on rv.assetId = a.assetId
WHERE a.collectionId = :collectionId
additionalPredicates
GROUP BY a.assetId
) v
), json_array()
) as assetHistoryEntryCounts`
}
sql += `
FROM review_history rh
INNER JOIN review rv on rh.reviewId = rv.reviewId
INNER JOIN enabled_asset a on rv.assetId = a.assetId
WHERE a.collectionId = :collectionId
additionalPredicates
`
let additionalPredicates = ""
if (startDate) {
binds.startDate = startDate
additionalPredicates += " AND rh.touchTs >= :startDate"
}
if (endDate) {
binds.endDate = endDate
additionalPredicates += " AND rh.touchTs <= :endDate"
}
if(ruleId) {
binds.ruleId = ruleId
additionalPredicates += " AND rv.ruleId = :ruleId"
}
if(status) {
binds.statusId = dbUtils.REVIEW_STATUS_API[status]
additionalPredicates += ' AND rh.statusId = :statusId'
}
if(assetId) {
binds.assetId = assetId
additionalPredicates += " AND a.assetId = :assetId"
}
sql = sql.replace(/additionalPredicates/g, additionalPredicates)
let [rows] = await dbUtils.pool.query(sql, binds)
return (rows[0])
}
exports.getCollectionSettings = async function ( collectionId ) {
let sql = `
select
JSON_MERGE_PATCH('${JSON.stringify(MyController.defaultSettings)}', settings) as settings
from
enabled_collection
where
collectionId = ?`
let [rows] = await dbUtils.pool.query(sql, [collectionId])
return rows.length > 0 ? rows[0].settings : undefined
}
exports.getCollectionLabels = async function (collectionId, grant) {
const ctes = []
const columns = [
'BIN_TO_UUID(cl.uuid,1) labelId',
'cl.name',
'cl.description',
'cl.color',
'count(distinct cla.claId) as uses'
]
const joins = [
'collection_label cl',
'left join enabled_asset a on cl.collectionId = a.collectionId',
'left join stig_asset_map sa on a.assetId = sa.assetId',
'left join collection_label_asset_map cla on cla.clId = cl.clId and cla.assetId = a.assetId'
]
// const groupBy = [
// 'cl.uuid',
// 'cl.name',
// 'cl.description',
// 'cl.color'
// ]
const groupBy = ['cl.clId']
const predicates = {
statements: ['cl.collectionId = ?'],
binds: [collectionId]
}
const orderBy = [
'cl.name'
]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return rows
}
exports.createCollectionLabel = async function (collectionId, label) {
let [resultInsert] = await dbUtils.pool.query(
`INSERT INTO collection_label
(collectionId, name, description, color, uuid)
VALUES (?, ?, ?, ?, UUID_TO_BIN(UUID(),1))`,
[collectionId, label.name, label.description, label.color])
const [resultGet] = await dbUtils.pool.query(
`SELECT BIN_TO_UUID(uuid,1) as uuid from collection_label where clId = ?`,
[resultInsert.insertId]
)
return resultGet[0].uuid
}
exports.createCollectionLabels = async function (collectionId, labels) {
const placeholders = labels.map(() => '(?, ?, ?, ?, UUID_TO_BIN(UUID(),1))').join(', ')
const values = []
for (const label of labels) {
values.push(collectionId, label.name, label.description, label.color)
}
const insertSql = `
INSERT INTO collection_label (collectionId, name, description, color, uuid)
VALUES ${placeholders}
`
await dbUtils.pool.query(insertSql, values)
return labels.map(label => label.name)
}
exports.getCollectionLabelsByName = async function (collectionId, labelNames, grant) {
const ctes = []
const columns = [
'BIN_TO_UUID(cl.uuid,1) labelId',
'cl.name',
'cl.description',
'cl.color',
'count(distinct cla.claId) as uses'
]
const joins = [
'collection_label cl',
'left join enabled_asset a on cl.collectionId = a.collectionId',
'left join stig_asset_map sa on a.assetId = sa.assetId',
'left join collection_label_asset_map cla on cla.clId = cl.clId and cla.assetId = a.assetId'
]
const namePlaceholders = labelNames.map(() => '?').join(', ')
const predicates = {
statements: [
'cl.collectionId = ?',
`cl.name IN (${namePlaceholders})`
],
binds: [collectionId, ...labelNames]
}
const groupBy = ['cl.clId']
const orderBy = []
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.getCollectionLabelById = async function (collectionId, labelId, grant) {
const ctes = []
const columns = [
'BIN_TO_UUID(cl.uuid,1) labelId',
'cl.name',
'cl.description',
'cl.color',
'count(distinct cla.claId) as uses'
]
const joins = [
'collection_label cl',
'left join enabled_asset a on cl.collectionId = a.collectionId',
'left join stig_asset_map sa on a.assetId = sa.assetId',
'left join collection_label_asset_map cla on cla.clId = cl.clId and cla.assetId = a.assetId'
]
const predicates = {
statements: [
'cl.collectionId = ?',
'cl.uuid = UUID_TO_BIN(?,1)'
],
binds: [collectionId, labelId]
}
const groupBy = ['cl.clId']
const orderBy = []
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows[0])
}
exports.patchCollectionLabelById = async function (collectionId, labelId, label) {
const [rows] = await dbUtils.pool.query(
`UPDATE
collection_label
SET
?
WHERE
collectionId = ?
and uuid = UUID_TO_BIN(?,1)`,
[label, collectionId, labelId])
return rows.affectedRows
}
exports.deleteCollectionLabelById = async function (collectionId, labelId) {
const [rows] = await dbUtils.pool.query(
`DELETE FROM
collection_label
WHERE
collectionId = ?
and uuid = UUID_TO_BIN(?,1)`,
[collectionId, labelId])
return rows.affectedRows
}
exports.getAssetsByCollectionLabelId = async function (collectionId, labelId, grant) {
const ctes = []
const columns = [
'CAST(a.assetId as char) as assetId',
'a.name'
]
const joins = [
'collection_label cl',
'left join collection_label_asset_map cla on cla.clId = cl.clId',
'inner join enabled_asset a on cla.assetId = a.assetId',
]
const predicates = {
statements: [
'cl.collectionId = ?',
'cl.uuid = UUID_TO_BIN(?,1)'
],
binds: [collectionId, labelId]
}
const groupBy = []
const orderBy = ['a.name']
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push(
'left join stig_asset_map sa on a.assetId = sa.assetId',
'inner join cteAclEffective cae on sa.saId = cae.saId'
)
groupBy.push('a.assetId')
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.putAssetsByCollectionLabelId = async function (collectionId, labelId, assetIds, svcStatus = {}) {
let connection
try {
connection = await dbUtils.pool.getConnection()
async function transaction() {
await connection.query('START TRANSACTION')
const sqlGetClId = `select clId from collection_label where uuid = UUID_TO_BIN(?,1)`
const [clIdRows] = await connection.query( sqlGetClId, [ labelId ] )
const clId = clIdRows[0].clId
let sqlDelete = `
DELETE FROM
collection_label_asset_map
WHERE
clId = ?`
if (assetIds.length > 0) {
sqlDelete += ' and assetId NOT IN ?'
}
await connection.query( sqlDelete, [ clId, [assetIds] ] )
// Push any bind values
const binds = []
for (const assetId of assetIds) {
binds.push([clId, assetId])
}
if (binds.length > 0) {
let sqlInsert = `
INSERT IGNORE INTO
collection_label_asset_map (clId, assetId)
VALUES
?`
await connection.query(sqlInsert, [ binds ])
}
// Commit the changes
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.getUnreviewedAssetsByCollection = async function (params) {
return queryUnreviewedByCollection({ grouping: 'asset', ...params})
}
exports.getUnreviewedRulesByCollection = async function (params) {
return queryUnreviewedByCollection({ grouping: 'rule', ...params})
}
async function queryUnreviewedByCollection ({
grouping,
collectionId,
benchmarkId,
assetId,
ruleId,
severities,
labelIds,
labelNames,
projections,
grant,
userObject
}) {
let columns, groupBy, orderBy
let projectionMap = []
switch (grouping) {
case 'asset':
columns = [
'CAST(a.assetId as char) as assetId',
'a.name',
`coalesce(
(select
json_arrayagg(json_object(
'labelId', BIN_TO_UUID(cl2.uuid,1),
'name', cl2.name
))
from
collection_label_asset_map cla2
left join collection_label cl2 on cla2.clId = cl2.clId
where
cla2.assetId = a.assetId),
json_array()) as labels`,
`json_arrayagg(json_object(
'result', result.api,
'ruleId', rgr.ruleId,
'groupId', rgr.groupId,
${projections.includes('ruleTitle') ? "'ruleTitle', rgr.title," : ''}
${projections.includes('groupTitle') ? "'groupTitle', rgr.title," : ''}
'severity', rgr.severity,
'benchmarkId', cr.benchmarkId
)) as unreviewed`
]
groupBy = [
'a.assetId',
'a.name'
]
orderBy = [
'a.name'
]
break
case 'rule':
projectionMap = projections.map( p => `${p === 'groupTitle' ? 'rgr.groupTitle' : 'rgr.title'}`)
columns = [
'rgr.ruleId',
'rgr.groupId',
'cr.benchmarkId',
'rgr.severity',
...projectionMap,
`json_arrayagg(json_object(
'result', result.api,
'assetId', CAST(a.assetId as char),
'name', a.name,
'labels', coalesce(
(select
json_arrayagg(json_object(
'labelId', BIN_TO_UUID(cl2.uuid,1),
'name', cl2.name
))
from
collection_label_asset_map cla2
left join collection_label cl2 on cla2.clId = cl2.clId
where
cla2.assetId = a.assetId),
json_array())
)) as unreviewed`
]
groupBy = [
'rgr.ruleId',
'rgr.groupId',
'cr.benchmarkId',
'rgr.severity',
...projectionMap
]
orderBy = [
'rgr.ruleId'
]
}
const ctes = []
const joins = [
'enabled_asset a',
'left join collection_label_asset_map cla on cla.assetId = a.assetId',
'left join collection_label cl on cla.clId = cl.clId',
'left join stig_asset_map sa on a.assetId = sa.assetId',
'left join current_rev cr on sa.benchmarkId = cr.benchmarkId',
'left join rev_group_rule_map rgr on cr.revId = rgr.revId',
'left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId',
'left join review r on (a.assetId = r.assetId and rvcd.version = r.version and rvcd.checkDigest = r.checkDigest)',
'left join result on r.resultId = result.resultId'
]
const predicates = {
statements: [
'a.collectionId = ?',
// '(cg.userId = ? AND CASE WHEN cg.roleId = 1 THEN usa.userId = cg.userId ELSE TRUE END)',
'(r.reviewId is null or r.resultId not in (2,3,4))',
],
binds: [collectionId, userObject.userId]
}
if (assetId) {
predicates.statements.push('a.assetId = ?')
predicates.binds.push(assetId)
}
if (labelIds?.length) {
predicates.statements.push('cl.uuid IN ?')
const uuidBinds = labelIds.map( uuid => dbUtils.uuidToSqlString(uuid))
predicates.binds.push([uuidBinds])
}
if (labelNames?.length) {
predicates.statements.push('cl.name IN ?')
predicates.binds.push([labelNames])
}
if (benchmarkId) {
predicates.statements.push('cr.benchmarkId = ?')
predicates.binds.push(benchmarkId)
}
if (ruleId) {
predicates.statements.push('rgr.ruleId = ?')
predicates.binds.push(ruleId)
}
if (severities?.length) {
predicates.statements.push('rgr.severity IN ?')
predicates.binds.push([severities])
}
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.writeStigPropsByCollectionStig = async function ({collectionId, benchmarkId, defaultRevisionStr, assetIds, svcStatus = {}}) {
let connection
try {
let version, release
if (defaultRevisionStr) {
if (defaultRevisionStr !== 'latest') {
;({version, release} = dbUtils.parseRevisionStr(defaultRevisionStr))
}
}
connection = await dbUtils.pool.getConnection()
await dbUtils.retryOnDeadlock(transaction, svcStatus)
async function transaction () {
await connection.query('START TRANSACTION')
if (defaultRevisionStr === 'latest' || assetIds?.length === 0) {
await connection.query('DELETE FROM collection_rev_map WHERE collectionId = ? and benchmarkId = ?', [collectionId, benchmarkId])
}
else if (defaultRevisionStr && defaultRevisionStr !== 'latest') {
const [revisions] = await connection.query('SELECT revId FROM revision WHERE benchmarkId = ? and `version` = ? and `release` = ?', [benchmarkId, version, release])
if (revisions[0]?.revId) {
await connection.query(`INSERT INTO collection_rev_map (collectionId, benchmarkId, revId)
VALUES (?, ?, ?) AS new ON DUPLICATE KEY UPDATE revId = new.revId`, [collectionId, benchmarkId, revisions[0].revId])
}
}
if (assetIds) {
let sqlDeleteStigAsset = `
DELETE stig_asset_map FROM
stig_asset_map
left join enabled_asset a on stig_asset_map.assetId = a.assetId
WHERE
a.collectionId = ?
and stig_asset_map.benchmarkId = ?${assetIds.length > 0 ? ' and stig_asset_map.assetId NOT IN ?': ''}`
// DELETE from stig_asset_map, which will cascade into user_stig_aset_map
await connection.query( sqlDeleteStigAsset, [ collectionId, benchmarkId, [assetIds] ] )
if (assetIds.length) {
const binds = assetIds.map( assetId => [benchmarkId, assetId])
// INSERT into stig_asset_map
const sqlInsertBenchmarks = `INSERT IGNORE INTO stig_asset_map (benchmarkId, assetId) VALUES ?`
await connection.query(sqlInsertBenchmarks, [ binds ])
}
}
await dbUtils.updateDefaultRev(connection, {collectionId, benchmarkId})
await dbUtils.updateStatsAssetStig(connection, {collectionId, benchmarkId})
await connection.commit()
}
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw ( err )
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.doesCollectionIncludeAssets = async function ({collectionId, assetIds}) {
try {
const sql = `select jt.assetId, a.collectionId
from
JSON_TABLE(
?,
"$[*]"
COLUMNS(
assetId INT(11) PATH "$"
) ) AS jt
left join enabled_asset a using (assetId)
where a.collectionId != ? or a.collectionId is null`
const [rows] = await dbUtils.pool.query(sql, [JSON.stringify(assetIds), collectionId])
return rows.length === 0
}
catch (e) {
return false
}
}
exports.doesCollectionIncludeStig = async function ({collectionId, benchmarkId}) {
try {
const [rows] = await dbUtils.pool.query(
`select distinct sam.benchmarkId from enabled_asset a inner join stig_asset_map sam using (assetId) where a.collectionId = ?`,
[collectionId]
)
return rows.some(i => i.benchmarkId === benchmarkId)
}
catch (e) {
return false
}
}
exports.cloneCollection = async function ({collectionId, userObject, name, description, options, svcStatus = {}, progressCb = () => {}}) {
let connection, progressJson
try {
const sql = {
cloneCollection: {
query: `INSERT INTO collection (name, description, settings, metadata, state) SELECT @name,@description,settings, metadata, "cloning" from enabled_collection WHERE collectionId = @srcCollectionId`,
startText: 'Creating core properties',
finishText: 'Creating core properties'
},
selectLastInsertId: {
query: 'SELECT last_insert_id() into @destCollectionId',
startText: 'Creating core properties',
finishText: 'Created core properties'
},
cloneGrants: {
query: `INSERT INTO collection_grant (collectionId, userId, userGroupId, roleId) SELECT @destCollectionId, userId, userGroupId, roleId FROM collection_grant where collectionId = @srcCollectionId`,
startText: 'Creating Grants',
finishText: 'Creating Grants'
},
dropGrantMap: {
query: `DROP TEMPORARY TABLE IF EXISTS t_grantid_map`,
startText: 'Creating Grants',
finishText: 'Creating Grants'
},
createGrantMap: {
query: `CREATE TEMPORARY TABLE t_grantid_map SELECT cg1.grantId as srcGrantId, cg2.grantId as destGrantId FROM collection_grant cg1 left join collection_grant cg2 on (cg1.collectionId = @srcCollectionId and (cg1.userId = cg2.userId or cg1.userGroupId = cg2.userGroupId) and cg1.roleId = cg2.roleId) WHERE cg2.collectionId = @destCollectionId`,
startText: 'Creating Grants',
finishText: 'Creating Grants'
},
insertOwnerGrant: {
query: `INSERT INTO collection_grant (collectionId, userId, roleId) VALUES (@destCollectionId, @userId, 4) ON DUPLICATE KEY UPDATE roleId = 4`,
startText: 'Creating Grants',
finishText: 'Created Grants'
},
cloneLabels: {
query: `INSERT INTO collection_label (collectionId, name, description, color, uuid) SELECT @destCollectionId,name,description,color,UUID_TO_BIN(UUID(),1) FROM collection_label where collectionId = @srcCollectionId`,
startText: 'Creating Labels',
finishText: 'Created Labels'
},
cloneAssets: {
query: `INSERT INTO asset (name, fqdn, collectionId, ip, mac, description, noncomputing, metadata) SELECT name,fqdn,@destCollectionId,ip,mac,description,noncomputing,metadata from enabled_asset where collectionId = @srcCollectionId`,
startText: 'Creating Assets',
finishText: 'Creating Assets'
},
dropAssetMap: {
query: `DROP TEMPORARY TABLE IF EXISTS t_assetid_map`,
startText: 'Creating Assets',
finishText: 'Creating Assets'
},
createAssetMap: {
query: `CREATE TEMPORARY TABLE t_assetid_map SELECT a1.assetId as srcAssetId, a2.assetId as destAssetId FROM enabled_asset a1 left join enabled_asset a2 on (a1.collectionId = @srcCollectionId and a1.name = a2.name) WHERE a2.collectionId = @destCollectionId`,
startText: 'Creating Assets',
finishText: 'Created Assets'
},
dropLabelMap: {
query: `DROP TEMPORARY TABLE IF EXISTS t_clid_map`,
startText: 'Creating Asset/Label mappings',
finishText: 'Creating Asset/Label mappings'
},
createLabelMap: {
query: `CREATE TEMPORARY TABLE t_clid_map SELECT cl1.clId as srcClId, cl2.clId as destClId FROM collection_label cl1 left join collection_label cl2 on (cl1.collectionId = @srcCollectionId and cl1.name = cl2.name) WHERE cl2.collectionId = @destCollectionId`,
startText: 'Creating Asset/Label mappings',
finishText: 'Creating Asset/Label mappings'
},
cloneAssetLabels: {
query: `INSERT INTO collection_label_asset_map (assetId, clId) SELECT am.destAssetId,cm.destClId FROM collection_label_asset_map cla INNER JOIN t_clid_map cm on cla.clId = cm.srcClId INNER JOIN t_assetid_map am on cla.assetId = am.srcAssetId`,
startText: 'Creating Asset/Label mappings',
finishText: 'Created Asset/Label mappings'
},
cloneStigMappingsWithReviews: {
query: `INSERT INTO stig_asset_map (benchmarkId, assetId, minTs, maxTs, saved, savedResultEngine, submitted, submittedResultEngine, rejected, rejectedResultEngine, accepted, acceptedResultEngine, highCount, mediumCount, lowCount, notchecked, notcheckedResultEngine, notapplicable, notapplicableResultEngine, pass, passResultEngine, fail, failResultEngine, unknown, unknownResultEngine, error, errorResultEngine, notselected, notselectedResultEngine, informational, informationalResultEngine, fixed, fixedResultEngine, maxTouchTs, assessedHighCount, assessedMediumCount, assessedLowCount) SELECT benchmarkId, am.destAssetId, minTs, maxTs, saved, savedResultEngine, submitted, submittedResultEngine, rejected, rejectedResultEngine, accepted, acceptedResultEngine, highCount, mediumCount, lowCount, notchecked, notcheckedResultEngine, notapplicable, notapplicableResultEngine, pass, passResultEngine, fail, failResultEngine, unknown, unknownResultEngine, error, errorResultEngine, notselected, notselectedResultEngine, informational, informationalResultEngine, fixed, fixedResultEngine, maxTouchTs, assessedHighCount, assessedMediumCount, assessedLowCount FROM stig_asset_map sa INNER JOIN t_assetid_map am on sa.assetId = am.srcAssetId`,
startText: 'Creating Asset/STIG mappings with Metrics',
finishText: 'Created Asset/STIG mappings with Metrics'
},
cloneStigMappingsWithoutReviews: {
query: `INSERT INTO stig_asset_map (benchmarkId, assetId) SELECT benchmarkId, am.destAssetId FROM stig_asset_map sa INNER JOIN t_assetid_map am on sa.assetId = am.srcAssetId`,
startText: 'Creating Asset/STIG mappings',
finishText: 'Created Asset/STIG mappings'
},
cloneGrantAcls: {
query: `INSERT INTO collection_grant_acl (grantId, benchmarkId, assetId, clId, access)
SELECT
gm.destGrantId,
cg1.benchmarkId,
am.destAssetId,
cm.destClId,
cg1.access
FROM
collection_grant_acl cg1
inner join t_grantid_map gm on cg1.grantId = gm.srcGrantId
left join t_assetid_map am on cg1.assetId = am.srcAssetId
left join t_clid_map cm on cg1.clId = cm.srcClId`,
startText: 'Creating Collection Grant ACLs',
finishText: 'Created Collection Grant ACLs'
},
cloneRevisionsMatchSource: {
query: `INSERT INTO collection_rev_map (collectionId, benchmarkId, revId) SELECT @destCollectionId, benchmarkId, revId FROM collection_rev_map where collectionId = @srcCollectionId`,
startText: 'Creating Revision pins',
finishText: 'Creating Revision pins'
},
cloneRevisionsSourceDefaults: {
query: `INSERT INTO collection_rev_map (collectionId, benchmarkId, revId) SELECT @destCollectionId, benchmarkId, revId FROM default_rev where collectionId = @srcCollectionId`,
startText: 'Creating Revision pins',
finishText: 'Creating Revision pins'
},
insertDefaultRev: {
query: `INSERT INTO default_rev(collectionId, benchmarkId, revId, revisionPinned) SELECT collectionId, benchmarkId, revId, revisionPinned FROM v_default_rev WHERE collectionId = @destCollectionId`,
startText: 'Creating Revision pins',
finishText: 'Created Revision pins'
},
countReviewIds: {
query: `SELECT count(seq) as reviewCount from t_reviewId_list`,
startText: 'Creating Reviews',
finishText: 'Creating Reviews'
},
dropReviewIdList: {
query: `DROP TEMPORARY TABLE IF EXISTS t_reviewId_list`,
startText: 'Creating Reviews',
finishText: 'Creating Reviews'
},
createReviewIdList: {
query: `CREATE TEMPORARY TABLE t_reviewId_list (seq INT AUTO_INCREMENT PRIMARY KEY)
SELECT r.reviewId, am.destAssetId FROM enabled_asset a inner join t_assetid_map am on a.assetId = am.srcAssetId inner join review r on am.srcAssetId = r.assetId `,
startText: 'Creating Reviews',
finishText: 'Creating Reviews'
},
cloneReviews: {
query: `INSERT INTO review (assetId, ruleId, resultId, detail, comment, autoResult, ts, userId, statusId, statusText, statusUserId, statusTs, metadata, resultEngine, version, checkDigest)
SELECT rl.destAssetId, r.ruleId, r.resultId, r.detail, r.comment, r.autoResult, r.ts, r.userId, r.statusId, r.statusText, r.statusUserId, r.statusTs, r.metadata, r.resultEngine, r.version, r.checkDigest
FROM
t_reviewId_list rl
left join review r using (reviewId)
WHERE
rl.seq >= ? and rl.seq <= ?`,
startText: 'Creating Reviews',
finishText: 'Created Reviews'
},
enableCollection: `UPDATE collection SET state = "enabled" WHERE collectionId = @destCollectionId`
}
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = false
connection.query('set @srcCollectionId = ?, @userId = ?, @name = ?, @description = ?', [
parseInt(collectionId),
parseInt(userObject.userId),
name,
description
])
const collectionQueries = ['cloneCollection', 'selectLastInsertId']
const reviewQueries = []
if (options.grants) {
collectionQueries.push('cloneGrants', 'dropGrantMap', 'createGrantMap')
}
collectionQueries.push('insertOwnerGrant')
if (options.labels) {
collectionQueries.push('cloneLabels')
}
if (options.assets) {
collectionQueries.push('cloneAssets', 'dropAssetMap', 'createAssetMap')
if (options.labels) {
collectionQueries.push('dropLabelMap', 'createLabelMap', 'cloneAssetLabels')
}
if (options.stigMappings !== 'none') {
collectionQueries.push(options.stigMappings === 'withReviews' ? 'cloneStigMappingsWithReviews' : 'cloneStigMappingsWithoutReviews')
if (options.grants) {
collectionQueries.push('cloneGrantAcls')
// collectionQueries.push('cloneRestrictedUserGroupGrants')
}
collectionQueries.push(options.pinRevisions === 'matchSource' ? 'cloneRevisionsMatchSource' : 'cloneRevisionsSourceDefaults')
collectionQueries.push('insertDefaultRev')
}
if (options.stigMappings === 'withReviews') {
reviewQueries.push('dropReviewIdList', 'createReviewIdList', 'cloneReviews')
}
}
async function transactionCollection () {
const stage = 'collection'
const stepCount = collectionQueries.length + 1
progressJson = {stage, stepCount, step: 0}
await connection.query('START TRANSACTION')
for (const query of collectionQueries) {
progressJson.step++
progressJson.stepName = query
progressJson.status = 'running'
progressJson.message = sql[query].startText
progressCb(progressJson)
await connection.query(sql[query].query)
}
progressJson.step++
progressJson.stepName = 'commit'
progressJson.status = 'running'
progressJson.message = 'Saving Collection'
progressCb(progressJson)
await connection.commit()
progressJson.status = 'finished'
progressJson.message = 'Saved Collection'
progressCb(progressJson)
}
async function transactionReviews () {
const stage = 'reviews'
const stepCount = reviewQueries.length + 1
progressJson = {stage, stepCount, step: 0}
await connection.query('START TRANSACTION')
for (const query of reviewQueries) {
progressJson.stepName = query
progressJson.step++
progressJson.message = sql[query].startText
if (query === 'cloneReviews') {
let offset = 1
const chunkSize = 10000
let [result] = await connection.query(sql.countReviewIds.query)
progressJson.status = 'running'
progressJson.reviewsTotal = result[0].reviewCount
progressJson.reviewsCopied = 0
progressCb(progressJson)
do {
[result] = await connection.query(sql[query].query, [offset, offset + chunkSize - 1])
if (result.affectedRows != 0) {
progressJson.reviewsCopied += result.affectedRows
progressCb(progressJson)
}
offset += chunkSize
} while (result.affectedRows != 0)
}
else {
progressJson.status = 'running'
progressCb(progressJson)
await connection.query(sql[query].query)
}
}
progressJson.step++
progressJson.stepName = 'commit'
progressJson.status = 'running'
progressCb(progressJson)
await connection.commit()
progressJson.status = 'finished'
progressCb(progressJson)
}
await dbUtils.retryOnDeadlock(transactionCollection, svcStatus)
await dbUtils.retryOnDeadlock(transactionReviews, svcStatus)
await connection.query(sql.enableCollection)
const [rows] = await connection.query(`SELECT @destCollectionId as destCollectionId`)
return rows[0]
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
progressJson.status = 'error'
if (err.message.match(/Duplicate entry .* for key 'collection.index[2|3]'/)) {
progressJson.message = 'The requested Collection name is unavailable'
}
else {
progressJson.message = 'Unhandled error'
progressJson.error = err
progressJson.stack = err?.stack
}
progressCb(progressJson)
return null
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.exportToCollection = async function ({srcCollectionId, dstCollectionId, assetStigArguments, userObject, svcStatus = {}, progressCb = () => {}}) {
let connection, progressJson
try {
const sql = {
dropArg: {
query: `drop temporary table if exists t_arg`,
runningText: 'Preparing data'
},
createArg: {
query: `create temporary table t_arg (
assetId INT,
assetName VARCHAR(255),
benchmarkId VARCHAR(255),
revisionStr VARCHAR(255),
UNIQUE INDEX (assetId, benchmarkId, revisionStr),
INDEX (assetName)
)
select * from
json_table(
@json,
"$[*]"
COLUMNS(
assetId INT path "$.assetId",
assetName VARCHAR(255) path "$.assetName",
nested path "$.stigs[*]" COLUMNS(
benchmarkId VARCHAR(255) path "$.benchmarkId",
revisionStr VARCHAR(255) path "$.revisionStr"
)
)
) as arg`,
runningText: 'Preparing data'
},
dropCollectionSetting: {
query: `drop temporary table if exists t_collection_setting`,
runningText: 'Preparing data'
},
createCollectionSetting: {
query: `create temporary table t_collection_setting
SELECT
c.settings->>"$.fields.detail.required" as detailRequired,
c.settings->>"$.fields.comment.required" as commentRequired,
c.settings->>"$.status.canAccept" as canAccept,
c.settings->>"$.status.resetCriteria" as resetCriteria,
c.settings->>"$.status.minAcceptGrant" as minAcceptGrant,
c.settings->>"$.history.maxReviews" as historyMax
FROM
enabled_collection c
where
collectionId = @dstCollectionId`,
runningText: 'Preparing data'
},
dropSrcReviewId: {
query: `drop temporary table if exists t_src_reviewId`,
runningText: 'Preparing data'
},
createSrcReviewId: {
query: `create temporary table t_src_reviewId (seq INT AUTO_INCREMENT PRIMARY KEY, reviewId INT UNIQUE )
select
r.reviewId
from
t_arg
left join revision rev on (t_arg.benchmarkId collate utf8mb4_0900_as_cs = rev.benchmarkId and t_arg.revisionStr = rev.revisionStr)
left join rev_group_rule_map rgr on (rev.revId = rgr.revId)
left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId
inner join review r on (rvcd.version = r.version and rvcd.checkDigest = r.checkDigest and t_arg.assetId = r.assetId)`,
runningText: 'Preparing data'
},
countSrcReviewId: {
query: `select count(*) as total from t_src_reviewId`,
runningText: 'Preparing data'
},
insertAsset: {
query: `INSERT into asset (name, fqdn, collectionId, ip, mac, description, noncomputing, metadata, state, stateDate, stateUserId)
SELECT
srcAsset.name,
srcAsset.fqdn,
@dstCollectionId,
srcAsset.ip,
srcAsset.mac,
srcAsset.description,
srcAsset.noncomputing,
srcAsset.metadata,
'enabled',
NOW(),
@userId
FROM
t_arg
left join enabled_asset srcAsset on t_arg.assetId = srcAsset.assetId
left join enabled_asset dstAsset on (t_arg.assetName = dstAsset.name and dstAsset.collectionId = @dstCollectionId)
WHERE
dstAsset.assetId is null
GROUP BY
t_arg.assetId`,
runningText: "Preparing Assets"
},
dropAssetIdMap: {
query: `drop temporary table if exists t_assetId_map`,
runningText: "Preparing Assets"
},
createAssetIdMap: {
query: `create temporary table t_assetId_map (
srcAssetId INT,
dstAssetId INT,
INDEX (srcAssetId),
INDEX (dstAssetId)
)
select
srcAsset.assetId as srcAssetId,
dstAsset.assetId as dstAssetId
from
t_arg
inner join enabled_asset srcAsset on (t_arg.assetId = srcAsset.assetId)
inner join enabled_asset dstAsset on (t_arg.assetName = dstAsset.name and dstAsset.collectionId = @dstCollectionId)
group by
srcAsset.assetId, dstAsset.assetId`,
runningText: "Preparing Assets"
},
insertStigAssetMap: {
query: `INSERT into stig_asset_map (assetId, benchmarkId)
select
a.assetId,
t_arg.benchmarkId
from
t_arg
left join enabled_asset a on (t_arg.assetName = a.name and a.collectionId = @dstCollectionId)
left join stig_asset_map sa on (t_arg.benchmarkId collate utf8mb4_0900_as_cs = sa.benchmarkId and a.assetId = sa.assetId)
where
sa.saId is null`,
runningText: "Preparing Assets"
},
selectStigAssetMap: {
query: `select
sa.saId
from
t_arg
left join enabled_asset a on (t_arg.assetName = a.name and a.collectionId = @dstCollectionId)
left join stig_asset_map sa on (t_arg.benchmarkId collate utf8mb4_0900_as_cs = sa.benchmarkId and a.assetId = sa.assetId)`
},
deleteDefaultRev: {
query: `DELETE FROM default_rev where collectionId = @dstCollectionId`,
runningText: "Preparing Assets"
},
insertDefaultRev: {
query: `INSERT INTO default_rev(collectionId, benchmarkId, revId, revisionPinned) SELECT collectionId, benchmarkId, revId, revisionPinned FROM v_default_rev where collectionId = @dstCollectionId`,
finishText: 'Created Asset/STIG maps',
runningText: "Preparing Assets"
},
dropIncomingReview: {
query: `drop temporary table if exists t_incoming_review`,
runningText: `Preparing reviews`,
finishText: `Preparing reviews`
},
createIncomingReview: {
query: `create temporary table t_incoming_review
select
dstReview.reviewId,
t_assetId_map.dstAssetId as assetId,
srcReview.version,
srcReview.checkDigest,
srcReview.ruleId,
srcReview.resultId,
srcReview.detail,
srcReview.comment,
srcReview.resultEngine,
srcReview.metadata,
UTC_TIMESTAMP() as ts,
@userId as userId,
CASE WHEN dstReview.reviewId is null or rStatusReset.reviewId is not null
THEN 0
ELSE dstReview.statusId
END as statusId,
CASE WHEN dstReview.reviewId is null
THEN ''
ELSE
CASE WHEN rStatusReset.reviewId is not null
THEN 'Status reset due to a Review change or Collection setting'
ELSE dstReview.statusText
END
END as statusText,
CASE WHEN dstReview.reviewId is null or rStatusReset.reviewId is not null
THEN UTC_TIMESTAMP()
ELSE dstReview.statusTs
END as statusTs,
CASE WHEN dstReview.reviewId is null or rStatusReset.reviewId is not null
THEN @userId
ELSE dstReview.statusUserId
END as statusUserId
from
t_src_reviewId
left join t_collection_setting on true
inner join review srcReview on (t_src_reviewId.reviewId = srcReview.reviewId)
left join t_assetId_map on (srcReview.assetId = t_assetId_map.srcAssetId)
left join review dstReview on (srcReview.version = dstReview.version and srcReview.checkDigest = dstReview.checkDigest and t_assetId_map.dstAssetId = dstReview.assetId)
left join review rChangedResult on (
dstReview.reviewId = rChangedResult.reviewId
and 0 != rChangedResult.statusId
and srcReview.resultId != rChangedResult.resultId
)
left join review rChangedAny on (
dstReview.reviewId = rChangedAny.reviewId
and 0 != rChangedAny.statusId
and (srcReview.resultId != rChangedAny.resultId or srcReview.detail != rChangedAny.detail or srcReview.comment != rChangedAny.comment)
)
left join review rStatusReset on (
dstReview.reviewId = rStatusReset.reviewId and (
(t_collection_setting.resetCriteria = 'result' and rChangedResult.reviewId is not null)
or (t_collection_setting.resetCriteria = 'any' and rChangedAny.reviewId is not null)
or (t_collection_setting.detailRequired = 'always' and srcReview.detail = '')
or (t_collection_setting.commentRequired = 'always' and srcReview.comment = '')
or (t_collection_setting.detailRequired = 'findings' and srcReview.resultId = 4 and srcReview.detail = '')
or (t_collection_setting.commentRequired = 'findings' and srcReview.resultId = 4 and srcReview.comment = '')
)
)
where
t_src_reviewId.seq >= ? and t_src_reviewId.seq <= ?`,
runningText: `Preparing reviews`,
finishText: `Preparing reviews`
},
countIncomingReview: {
query: `select sum(reviewId is null) as inserted, sum(reviewId is not null) as updated from t_incoming_review`,
runningText: `Preparing reviews`,
},
pruneHistory: {
query: `with historyRecs AS (
select
rh.historyId,
ROW_NUMBER() OVER (PARTITION BY r.assetId, r.version, r.checkDigest ORDER BY rh.historyId DESC) as rowNum
from
review_history rh
inner join t_incoming_review r using (reviewId)
)
delete review_history
FROM
review_history
left join historyRecs on review_history.historyId = historyRecs.historyId
WHERE
historyRecs.rowNum > ((select historyMax from t_collection_setting) - 1)`,
runningText: `Preparing reviews`,
finishText: `Preparing reviews`
},
insertHistory: {
query: `INSERT INTO review_history (
reviewId,
ruleId,
resultId,
detail,
comment,
autoResult,
ts,
userId,
statusText,
statusUserId,
statusTs,
statusId,
touchTs,
resultEngine)
SELECT
r.reviewId,
r.ruleId,
r.resultId,
LEFT(r.detail,32767) as detail,
LEFT(r.comment,32767) as comment,
r.autoResult,
r.ts,
r.userId,
r.statusText,
r.statusUserId,
r.statusTs,
r.statusId,
r.touchTs,
r.resultEngine
FROM
review r
inner join t_incoming_review using (reviewId)`,
runningText: `Preparing reviews`,
finishText: `Prepared reviews`
},
upsertReview: {
query: `insert into review (reviewId, assetId, version, checkDigest, ruleId, resultId, detail, comment, resultEngine, metadata, ts, userId, statusId, statusText, statusTs, statusUserId)
select * from t_incoming_review as r
on duplicate key update
ruleId = r.ruleId,
resultId = r.resultId,
detail = r.detail,
comment = r.comment,
ts = r.ts,
userId = r.userId,
statusId = r.statusId,
statusText = r.statusText,
statusUserId = r.statusUserId,
statusTs = r.statusTs,
metadata = r.metadata,
resultEngine = r.resultEngine`
}
}
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = false
connection.query('set @srcCollectionId = ?, @dstCollectionId = ?, @userId = ?, @json = ?',
[parseInt(srcCollectionId), parseInt(dstCollectionId), parseInt(userObject.userId), JSON.stringify(assetStigArguments)])
const prepQueries = ['dropArg', 'createArg', 'dropCollectionSetting', 'createCollectionSetting', 'dropSrcReviewId', 'createSrcReviewId']
const assetQueries = ['insertAsset', 'dropAssetIdMap', 'createAssetIdMap', 'insertStigAssetMap', 'deleteDefaultRev', 'insertDefaultRev']
const reviewExportQueries = ['pruneHistory', 'insertHistory', 'upsertReview']
const counts = {
assetsCreated: 0,
stigsMapped: 0,
reviewsInserted: 0,
reviewsUpdated: 0
}
async function transaction () {
progressJson = {
stage: 'prepare',
stepCount: prepQueries.length,
step: 0
}
await connection.query('START TRANSACTION')
for (const query of prepQueries) {
progressJson.step++
progressJson.stepName = query
progressJson.status = 'running'
progressJson.message = sql[query].runningText
progressCb(progressJson)
await connection.query(sql[query].query)
}
progressJson.stage = 'assets'
progressJson.stepCount = assetQueries.length
progressJson.step = 0
for (const query of assetQueries) {
progressJson.step++
progressJson.stepName = query
progressJson.status = 'running'
progressJson.message = sql[query].runningText
progressCb(progressJson)
const [result] = await connection.query(sql[query].query)
if (query === 'insertAsset') {
counts.assetsCreated = result.affectedRows
}
if (query === 'insertStigAssetMap') {
counts.stigsMapped = result.affectedRows
}
}
const [count] = await connection.query(sql.countSrcReviewId.query)
let offset = 1
const chunkSize = 10000
let result
progressJson = {
stage: 'reviews',
status: 'running',
reviewsTotal: count[0].total,
reviewsExported: 0
}
progressCb(progressJson)
do {
await connection.query(sql.dropIncomingReview.query)
;[result] = await connection.query(sql.createIncomingReview.query, [offset, offset + chunkSize - 1])
if (result.affectedRows != 0) {
const [count] = await connection.query(sql.countIncomingReview.query)
counts.reviewsInserted += count[0].inserted
counts.reviewsUpdated += count[0].updated
for (const query of reviewExportQueries) {
await connection.query(sql[query].query)
}
progressJson.reviewsExported += result.affectedRows
progressCb(progressJson)
}
offset += chunkSize
} while (result.affectedRows != 0)
const [saIdResult] = await connection.query(sql.selectStigAssetMap.query)
progressJson = {
stage: 'metrics',
status: 'running',
metricsTotal: saIdResult.length,
metricsUpdated: 0
}
progressCb(progressJson)
const increment = 1000
for (let i = 0; i < saIdResult.length; i+=increment) {
const saIds = saIdResult.slice(i, i + increment).map(row => row.saId)
await dbUtils.updateStatsAssetStig(connection, {saIds})
progressJson.metricsUpdated += saIds.length
progressCb(progressJson)
}
progressJson = {
stage: 'commit',
status: 'running'
}
progressCb(progressJson)
await connection.commit()
progressCb({
stage: 'result',
counts
})
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
progressJson.status = 'error'
progressJson.message = 'Unhandled error'
progressJson.error = err
progressJson.stack = err?.stack
progressCb({progressJson})
return null
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.setGrantByCollection = async function ({collectionId, userId, userGroupId, roleId}) {
const sqlInsertGrant =
`INSERT INTO collection_grant (collectionId, ${userId ? 'userId' : 'userGroupId'}, roleId) VALUES (?, ?, ?) AS new ON DUPLICATE KEY UPDATE roleId = new.roleId`
const [response] = await dbUtils.pool.query(sqlInsertGrant, [collectionId, userId || userGroupId, roleId])
// resolving if we are inserting a new db record or updating an existing.
const httpStatus = (response.affectedRows === 1 && response.insertId !== 0) ? 201 : 200
return httpStatus
}
exports.getEffectiveAclByCollectionUser = async function ({collectionId, userId}) {
const sqlSelectEffectiveGrants = `
with cteGrantees as (
select
json_array(cg.grantId) as grantIds
from
collection_grant cg
inner join enabled_collection c on (cg.collectionId = c.collectionId)
left join user_data ud on cg.userId = ud.userId
where
cg.userId is not null
and cg.collectionId = ?
and cg.userId = ?
union
select
grantIds
from
(
select
ROW_NUMBER() OVER(PARTITION BY ugu.userId, cg.collectionId ORDER BY cg.roleId desc) as rn,
json_arrayagg(cg.grantId) OVER (PARTITION BY ugu.userId, cg.collectionId, cg.roleId) as grantIds
from
collection_grant cg
left join user_group_user_map ugu on cg.userGroupId = ugu.userGroupId
left join user_group ug on ugu.userGroupId = ug.userGroupId
left join collection_grant cgDirect on (cg.collectionId = cgDirect.collectionId and ugu.userId = cgDirect.userId)
inner join enabled_collection c on (cg.collectionId = c.collectionId)
where
cg.userGroupId is not null
and cgDirect.userId is null
and cg.collectionId = ?
and ugu.userId = ?
) dt
where
dt.rn = 1
),
cteAclRules as (select
sa.saId,
sa.assetId,
sa.benchmarkId,
cga.grantId,
cga.access,
json_object('assetId', cast(a.assetId as char), 'name', a.name) as asset,
json_object(
'grantee', json_remove(json_object(
CASE WHEN ud.userId is null THEN 'x' ELSE 'userId' END, CAST(ud.userId AS CHAR),
CASE WHEN ud.userId is null THEN 'x' ELSE 'username' END, ud.username,
CASE WHEN ug.userGroupId is null THEN 'x' ELSE 'userGroupId' END, CAST(ug.userGroupId AS CHAR),
CASE WHEN ug.userGroupId is null THEN 'x' ELSE 'name' END, ug.name,
'roleId', cg.roleId
), '$.x'),
'aclRule', json_remove(json_object(
CASE WHEN cga.benchmarkId is null THEN 'x' ELSE 'benchmarkId' END, cga.benchmarkId,
CASE WHEN cga.assetId is null THEN 'x' ELSE 'asset' END,
CASE WHEN cga.assetId is null THEN NULL ELSE json_object('assetId', cast(cga.assetId as char), 'name', a.name) END,
CASE WHEN cga.clId is null THEN 'x' ELSE 'label' END,
CASE WHEN cga.clId is null THEN NULL ELSE json_object('labelId', BIN_TO_UUID(cl.uuid,1), 'name', cl.name) END,
'access', cga.access
), '$.x')
) as aclSource,
case when cga.benchmarkId is not null then 1 else 0 end +
case when cga.assetId is not null then 1 else 0 end +
case when cga.assetId is not null and cga.benchmarkId is not null then 1 else 0 end +
case when cga.clId is not null then 1 else 0 end as specificity
from
collection_grant_acl cga
left join collection_grant cg on cga.grantId = cg.grantId
left join user_data ud on cg.userId = ud.userId
left join user_group ug on cg.userGroupId = ug.userGroupId
left join collection_label_asset_map cla on cga.clId = cla.clId
left join collection_label cl on cla.clId = cl.clId
inner join stig_asset_map sa on (
case when cga.assetId is not null
then cga.assetId = sa.assetId
else true
end and
case when cga.benchmarkId is not null
then cga.benchmarkId = sa.benchmarkId
else true
end and
case when cga.clId is not null
then cla.assetId = sa.assetId
else true
end)
inner join enabled_asset a on sa.assetId = a.assetId and cg.collectionId = a.collectionId
where
cga.grantId in (
select /*+ NO_MERGE() */ jt.grantId from cteGrantees left join json_table (cteGrantees.grantIds, '$[*]' COLUMNS (grantId INT PATH '$')) jt on true
)
),
cteAclRulesRanked as (
select /*+ NO_MERGE() */
saId,
access,
asset,
benchmarkId,
json_arrayagg(aclSource) over (partition by saId, access, specificity) as aclSources,
specificity,
row_number() over (partition by saId order by specificity desc, access asc) as rn
from
cteAclRules)
select /*+ NO_MERGE() */ access, asset, benchmarkId, aclSources from cteAclRulesRanked where rn = 1 and access != 'none'`
const [response] = await dbUtils.pool.query(sqlSelectEffectiveGrants, [collectionId, userId, collectionId, userId])
return response
}
exports.setValidatedAcl = async function({validatedAcl, grantId, attributionUserId, svcStatus = {}}) {
const sqlDelete = `DELETE from collection_grant_acl WHERE grantId = ?`
const values = validatedAcl.map(i => [i.grantId, i.assetId, i.benchmarkId, i.clId, i.access, attributionUserId])
if (values.length) {
return dbUtils.retryOnDeadlock2({
transactionFn,
statusObj: svcStatus
})
}
else {
return dbUtils.pool.query(sqlDelete, [grantId])
}
async function transactionFn (connection) {
const sqlInsert = `INSERT into collection_grant_acl (grantId, assetId, benchmarkId, clId, access, modifiedUserId) VALUES ?`
await connection.query(sqlDelete, [grantId])
await connection.query(sqlInsert, [values])
}
}
exports._reviewAclValidate = async function ({grantId, acl}) {
const sql = `
select
any_value(cg.grantId) as grantId,
group_concat(jt.itemNum) as itemNum,
case when count(jt.item) > 1 then json_arrayagg(jt.item) else any_value(jt.item) end as item,
jt.assetId,
jt.benchmarkId,
cl.clId,
group_concat(jt.access) as access,
group_concat(case when any_value(cg.roleId) != 1 and jt.access = 'none'
then 'roleId prohibits access:none'
else case when jt.assetId is not null and a.assetId is null
then 'asset not found in collection'
else case when jt.benchmarkId is not null and s.benchmarkId is null
then 'stig not installed'
else case when jt.labelId is not null and cl.clId is null
then 'label not found in collection'
else 'pass'
end
end
end
end) as validity,
count(jt.item) as dupCount
from
json_table(
?,
"$[*]" COLUMNS (
itemNum FOR ORDINALITY,
item JSON PATH '$',
assetId INT PATH '$.assetId',
benchmarkId VARCHAR(255) PATH '$.benchmarkId',
labelId VARCHAR(255) PATH '$.labelId',
access VARCHAR(255) PATH '$.access'
)) jt
left join collection_grant cg on (cg.grantId = ?)
left join collection_label cl on cl.uuid = UUID_TO_BIN(jt.labelId,1) and cg.collectionId = cl.collectionId
left join enabled_asset a on jt.assetId = a.assetId and cg.collectionId = a.collectionId
left join stig s on jt.benchmarkId collate utf8mb4_0900_as_cs = s.benchmarkId
group by
jt.assetId, jt.benchmarkId, jt.labelId, cl.clId
order by
itemNum`
const [rows] = await dbUtils.pool.query(sql, [JSON.stringify(acl), grantId])
const response = rows.reduce((a,v) => {
const disposition = v.validity === 'pass' ? 'pass' : 'fail'
if (disposition === 'fail') {
delete v.grantId
delete v.assetId
delete v.benchmarkId
delete v.clId
delete v.access
if (v.dupCount > 1) v.validity += ',duplicate resource definition'
}
delete v.dupCount
a[disposition].push(v)
return a
}, {pass:[], fail:[]})
return response
}
exports._getCollectionGrant = async function ({collectionId, grantId, grantIds, userId, userGroupId}) {
let sql = `select
case when user_data.userId
then json_object(
'grantId', cast(grantId as char),
'user', json_object(
'userId', CAST(user_data.userId as char),
'username', user_data.username,
'displayName', COALESCE(
JSON_UNQUOTE(JSON_EXTRACT(user_data.lastClaims, "$.name")),
user_data.username)),
'roleId', roleId)
else json_object(
'grantId', cast(grantId as char),
'userGroup', json_object(
'userGroupId', CAST(user_group.userGroupId as char),
'name', user_group.name,
'description', user_group.description
),
'roleId', roleId) end as grantJson
from
collection_grant
left join user_data using (userId)
left join user_group using (userGroupId)
where collectionId = ?`
if (grantId) {
sql += ' and grantId = ?'
}
else if (grantIds) {
sql += ' and grantId IN (?)'
}
else if (userId) {
sql += ' and userId = ?'
}
else if (userGroupId) {
sql += ' and userGroupId = ?'
}
const [response] = await dbUtils.pool.query(sql, [collectionId, grantId || grantIds || userId || userGroupId])
const grants = response.map(row => row.grantJson)
return grants
}
exports.putGrantById = function ({grantId, grant, isRoleChange = false, svcStatus = {}}) {
const sqlUpdate = `UPDATE collection_grant SET userId = ?,userGroupId = ?,roleId = ? where grantId = ?`
const bindsUpdate = [grant.userId, grant.userGroupId, grant.roleId, grantId]
if (isRoleChange) {
// need a transaction
async function transactionFn (connection) {
const sqlDelete = `DELETE from collection_grant_acl WHERE grantId = ? and access = 'none'`
await connection.query(sqlDelete, [grantId])
await connection.query(sqlUpdate, bindsUpdate)
}
return dbUtils.retryOnDeadlock2({
transactionFn,
statusObj: svcStatus
})
}
else {
return dbUtils.pool.query(sqlUpdate, bindsUpdate)
}
}
exports.deleteGrantById = async function (grantId) {
const sql = `DELETE from collection_grant WHERE grantId = ?`
return dbUtils.pool.query(sql, [grantId])
}
exports.postGrantsByCollection = async function (collectionId, grants) {
const binds = grants.map( g => [collectionId, g.userId, g.userGroupId, g.roleId])
const sql = `INSERT into collection_grant (collectionId, userId, userGroupId, roleId) VALUES ?`
const [result] = await dbUtils.pool.query(sql, [binds])
const grantIds = []
for (let x = 0; x < result.affectedRows; x++) {
grantIds.push(result.insertId + x)
}
return grantIds
}
exports._hasCollectionGrant = async function ({collectionId, userId}) {
const sql = `SELECT cg.grantId
FROM collection_grant cg
LEFT JOIN user_group ug ON cg.userGroupId = ug.userGroupId
LEFT JOIN user_data ud on cg.userID = ud.userId
LEFT JOIN user_group_user_map ugu ON ug.userGroupId = ugu.userGroupId
WHERE cg.collectionId = ? AND (ud.userId = ? OR ugu.userId = ?)`
const [response] = await dbUtils.pool.query(sql, [collectionId, userId, userId])
return !!response[0]
}
exports.queryReviewAcl = async function ({grantId, collectionId, userId, userGroupId}) {
const columns = [
`case when cg.roleId = 1 then 'none' else 'rw' end as defaultAccess`,
`case when count(cga.cgAclId) = 0
THEN json_array()
ELSE json_arrayagg(
json_remove(json_object(
CASE WHEN cga.benchmarkId is null THEN 'x' ELSE 'benchmarkId' END, cga.benchmarkId,
CASE WHEN cga.assetId is null THEN 'x' ELSE 'asset' END,
CASE WHEN cga.assetId is null THEN NULL ELSE json_object('assetId',cast(cga.assetId as char),'name',a.name) END,
CASE WHEN cga.clId is null THEN 'x' ELSE 'label' END,
CASE WHEN cga.clId is null THEN NULL ELSE json_object('labelId',BIN_TO_UUID(cl.uuid,1), 'name', cl.name, 'color', cl.color) END,
'access', cga.access
), '$.x'))
END as acl`
]
const joins = [
'collection_grant cg',
'inner join enabled_collection c on cg.collectionId = c.collectionId',
'left join collection_grant_acl cga on cg.grantId = cga.grantId',
'left join enabled_asset a on cga.assetId = a.assetId',
'left join collection_label cl on cga.clId = cl.clId'
]
const predicates = {
statements: [],
binds: []
}
if (grantId) {
predicates.statements.push('cg.grantId = ?')
predicates.binds.push(grantId)
}
else if (userId && collectionId) {
predicates.statements.push('cg.userId = ?', 'cg.collectionId = ?')
predicates.binds.push(userId, collectionId)
}
else if (userGroupId && collectionId) {
predicates.statements.push('cg.userGroupId = ?', 'cg.collectionId = ?')
predicates.binds.push(userGroupId, collectionId)
}
const sql = dbUtils.makeQueryString({columns, joins, predicates, format: true})
const [rows] = await dbUtils.pool.query(sql)
return rows?.[0]
}
================================================
FILE: api/source/service/JobService.js
================================================
const { randomUUID } = require('node:crypto')
const dbUtils = require('./utils')
const _this = this
exports.queryJobs = async function ({ projections = [], filters = {} } = {}) {
const columns = [
'CAST(job.jobId AS CHAR) AS jobId',
'job.name',
'job.description',
`json_object(
'userId', CAST(ud_creator.userId as char),
'username', ud_creator.username) AS createdBy`,
'job.created',
`IF(ud_updater.userId IS NULL, NULL, json_object(
'userId', CAST(ud_updater.userId as char),
'username', ud_updater.username)) AS updatedBy`,
'job.updated',
`(select
IF(COUNT(jt.taskId), json_arrayagg(json_object('taskId', CAST(jt.taskId as char), 'name', t.name, 'description', t.description)), json_array())
from job_task_map jt left join task t ON jt.taskId = t.taskId where jt.jobId = job.jobId) AS tasks`,
`(select ifnull(COUNT(*), 0) from job_run jr where jr.jobId = job.jobId) AS runCount`,
`(SELECT ifnull(JSON_OBJECT(
'runId', BIN_TO_UUID(jr.runId, 1),
'created', DATE_FORMAT(jr.created,'%Y-%m-%dT%H:%i:%sZ'),
'updated', IF(jr.updated IS NULL, NULL, DATE_FORMAT(jr.updated,'%Y-%m-%dT%H:%i:%sZ')),
'state', CASE WHEN jr.state = 'running' AND jr.created < CURRENT_TIMESTAMP - INTERVAL gs.VARIABLE_VALUE SECOND THEN 'shutdown' ELSE jr.state END
), null) FROM job_run jr left join performance_schema.global_status gs ON gs.VARIABLE_NAME = "Uptime" WHERE jr.jobId = job.jobId ORDER BY jr.jrId DESC LIMIT 1) AS lastRun`,
]
const joins = new Set([
'job',
'LEFT JOIN user_data ud_creator ON ud_creator.userId = job.createdBy',
'LEFT JOIN user_data ud_updater ON ud_updater.userId = job.updatedBy'
])
const groupBy = ['job.jobId']
const orderBy = ['job.jobId']
const eventValues = `
IF(e.event_type = 'ONE TIME',
JSON_OBJECT(
'eventId', e.event_name,
'type', 'once',
'starts', DATE_FORMAT(e.execute_at,'%Y-%m-%dT%H:%i:%sZ')
),
JSON_OBJECT(
'eventId', e.event_name,
'type', 'recurring',
'interval', JSON_OBJECT('value', CAST(e.interval_value as char), 'field', LCASE(e.interval_field)),
'starts', DATE_FORMAT(e.starts,'%Y-%m-%dT%H:%i:%sZ'),
'ends', DATE_FORMAT(e.ends,'%Y-%m-%dT%H:%i:%sZ'),
'enabled', e.status = 'ENABLED'
)
)`
columns.push(`(select
${eventValues} AS event
from
information_schema.events e
where
e.event_schema = database()
AND e.event_name LIKE CONCAT("job-", job.jobId, "-stigman")
LIMIT 1
) as event`)
const predicates = {
statements: [],
binds: []
}
if (filters.jobId) {
predicates.statements.push('job.jobId = ?')
predicates.binds.push(filters.jobId)
}
const sql = dbUtils.makeQueryString({ columns, joins, predicates, groupBy, orderBy, format: true })
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.getJobs = async ({ projections }) => {
return _this.queryJobs({ projections })
}
exports.getJob = async (jobId, { projections } = {}) => {
const jobs = await _this.queryJobs({ projections, filters: { jobId } })
return jobs[0]
}
exports.deleteJob = async (jobId) => {
const sql = 'select event_name from information_schema.events where event_schema = database() AND event_name LIKE CONCAT("job-", ?, "-%")'
const [events] = await dbUtils.pool.query(sql, [jobId])
if (events.length) {
const eventNames = events.map(r => r.EVENT_NAME)
for (const eventName of eventNames) {
const sqlDropEvent = `DROP EVENT IF EXISTS ??`
await dbUtils.pool.query(sqlDropEvent, [eventName])
}
}
const [result] = await dbUtils.pool.query('DELETE FROM job WHERE jobId = ?', [jobId])
return result.affectedRows > 0
}
async function createEventByJob(jobId, eventData) {
const eventName = getEventNameByJob(jobId)
if (eventData.type === 'once') {
const sqlCreateEvent = `
CREATE EVENT ??
ON SCHEDULE AT ?
DO CALL run_job(?, null)
`
const params = [eventName, eventData.starts, jobId]
await dbUtils.pool.query(sqlCreateEvent, params)
} else if (eventData.type === 'recurring') {
const intervalFields = {
minute: 'MINUTE', hour: 'HOUR', day: 'DAY',
week: 'WEEK', month: 'MONTH'
}
const intervalSql = intervalFields[eventData.interval.field]
const enabledSql = eventData.enabled === false ? 'DISABLE' : 'ENABLE'
const endsSql = eventData.ends ? 'ENDS ?' : ''
const sqlCreateEvent = `
CREATE EVENT ??
ON SCHEDULE EVERY ? ${intervalSql} STARTS ? ${endsSql}
${enabledSql}
DO CALL run_job(?, null)
`
const params = [eventName, eventData.interval.value, eventData.starts]
if (eventData.ends) params.push(eventData.ends)
params.push(jobId)
await dbUtils.pool.query(sqlCreateEvent, params)
}
return eventName
}
async function dropEventByJob(jobId) {
const eventName = getEventNameByJob(jobId)
const sqlDropEvent = `DROP EVENT IF EXISTS ??`
return dbUtils.pool.query(sqlDropEvent, [eventName])
}
function getEventNameByJob(jobId) {
return `job-${jobId}-stigman`
}
exports.createJob = async ({ jobData, userId, svcStatus } = {}) => {
const { tasks, event, ...jobFields } = jobData
async function transactionFn(connection) {
const sqlInsertJob = `INSERT into job (name, description, createdBy) VALUES ?`
const values = [
[jobFields.name, jobFields.description, userId]
]
const result = await connection.query(sqlInsertJob, [values])
const jobId = result[0].insertId
const sqlInsertTasks = `INSERT INTO job_task_map (jobId, taskId) VALUES ?`
const taskValues = tasks.map(t => [jobId, t])
if (taskValues.length) {
await connection.query(sqlInsertTasks, [taskValues])
}
return jobId
}
const jobId = await dbUtils.retryOnDeadlock2({
transactionFn,
statusObj: svcStatus
})
// Create events after committing the transaction
if (event) {
await createEventByJob(jobId, event)
}
return jobId
}
exports.patchJob = async ({jobId, jobData, userId, svcStatus = {}}) => {
const { tasks, event, ...jobFields } = jobData
async function transactionFn(connection) {
const sets = []
const binds = []
if (jobFields.name !== undefined) {
sets.push('name = ?')
binds.push(jobFields.name)
}
if (jobFields.description !== undefined) {
sets.push('description = ?')
binds.push(jobFields.description)
}
if (sets.length) {
sets.push('updatedBy = ?')
binds.push(userId)
binds.push(jobId)
const sqlUpdateJob = `UPDATE job SET ${sets.join(', ')}, updated = CURRENT_TIMESTAMP WHERE jobId = ?`
await connection.query(sqlUpdateJob, binds)
}
if (Array.isArray(tasks)) {
const sqlDeleteTasks = `DELETE FROM job_task_map WHERE jobId = ?`
await connection.query(sqlDeleteTasks, [jobId])
const sqlInsertTasks = `INSERT INTO job_task_map (jobId, taskId) VALUES ?`
const taskValues = tasks.map(t => [jobId, t])
if (taskValues.length) {
await connection.query(sqlInsertTasks, [taskValues])
}
}
return jobId
}
const updatedJobId = await dbUtils.retryOnDeadlock2({
transactionFn,
statusObj: svcStatus
})
if (event === null) {
await dropEventByJob(jobId)
} else if (event) {
await dropEventByJob(jobId)
await createEventByJob(jobId, event)
}
return updatedJobId
}
exports.getEventsByJob = async (jobId) => {
throw new Error('Not implemented')
}
exports.createEventByJob = async (jobId, eventData) => {
throw new Error('Not implemented')
}
exports.getRunById = async (runId) => {
const columns = [
`BIN_TO_UUID(jr.runId, 1) AS runId`,
`CASE WHEN jr.state = 'running' AND jr.created < CURRENT_TIMESTAMP - INTERVAL gs.VARIABLE_VALUE SECOND THEN 'shutdown' ELSE jr.state END AS state`,
'jr.created',
'jr.updated',
'CAST(jr.jobId AS CHAR) AS jobId'
]
const joins = new Set([
'job_run jr',
'left join performance_schema.global_status gs ON gs.VARIABLE_NAME = "Uptime"'
])
const predicates = {
statements: ['jr.runId = ?'],
binds: [dbUtils.uuidToSqlString(runId)]
}
const sql = dbUtils.makeQueryString({ columns, joins, predicates, format: true })
let [rows] = await dbUtils.pool.query(sql, [runId])
return (rows[0])
}
exports.getRunsByJob = async (jobId) => {
const columns = [
`BIN_TO_UUID(jr.runId, 1) AS runId`,
`CASE WHEN jr.state = 'running' AND jr.created < CURRENT_TIMESTAMP - INTERVAL gs.VARIABLE_VALUE SECOND THEN 'shutdown' ELSE jr.state END AS state`,
`jr.created`,
`jr.updated`,
`CAST(jr.jobId AS CHAR) AS jobId`
]
const joins = new Set([
'job_run jr',
'left join performance_schema.global_status gs ON gs.VARIABLE_NAME = "Uptime"'
])
const predicates = {
statements: ['jr.jobId = ?'],
binds: [jobId]
}
const orderBy = ['jr.created DESC']
const sql = dbUtils.makeQueryString({ columns, joins, predicates, orderBy, format: true })
let [rows] = await dbUtils.pool.query(sql, [jobId])
return (rows)
}
exports.runImmediateJob = async (jobId) => {
const runId = randomUUID()
const sql = `CREATE EVENT IF NOT EXISTS ??
ON SCHEDULE AT CURRENT_TIMESTAMP
DO CALL run_job(?,?)`
await dbUtils.pool.query(sql, [`job-${jobId}-${runId}`, jobId, runId])
return runId
}
exports.getOutputByRun = async (runId, {filters}) => {
const ctes = [
`Output AS (
SELECT
ROW_NUMBER() OVER (ORDER BY tout.seq ASC) as seq,
tout.ts,
tout.taskId,
t.name as task,
tout.type,
tout.message
FROM
task_output tout
left join task t ON tout.taskId = t.taskId
WHERE
runId = UUID_TO_BIN(?, 1))`
]
const columns = [
'Output.seq',
'Output.ts',
'Output.taskId',
'Output.task',
'Output.type',
'Output.message'
]
const joins = new Set(['Output'])
const predicates = {
statements: [],
binds: [runId]
}
if (filters?.afterSeq) {
predicates.statements.push('Output.seq > ?')
predicates.binds.push(filters.afterSeq)
}
const orderBy = ['Output.seq DESC']
const sql = dbUtils.makeQueryString({ ctes, columns, joins, predicates, orderBy, format: true })
let [rows] = await dbUtils.pool.query(sql, predicates.binds)
return (rows)
}
exports.getAllTasks = async () => {
const sql = `SELECT CAST(taskId AS CHAR(36)) AS taskId, name, description, command FROM task ORDER BY name`
let [rows] = await dbUtils.pool.query(sql)
return rows
}
exports.deleteRunById = async (runId) => {
const [result] = await dbUtils.pool.query('DELETE FROM job_run WHERE runId = UUID_TO_BIN(?,1)', [runId])
return result.affectedRows > 0
}
================================================
FILE: api/source/service/MetricsService.js
================================================
const dbUtils = require('./utils')
function genLabelPredicates ({labelNames, labelIds, labelMatch, collectionLabelTableAlias = 'cl'}) {
const clauses = []
const binds = []
if (labelNames) {
clauses.push(`${collectionLabelTableAlias}.name IN ?`)
binds.push([labelNames])
}
if (labelIds) {
const uuidBinds = labelIds.map( uuid => dbUtils.uuidToSqlString(uuid))
clauses.push(`${collectionLabelTableAlias}.uuid IN ?`)
binds.push([uuidBinds])
}
if (labelMatch === 'null') {
clauses.push(`${collectionLabelTableAlias}.uuid IS NULL`)
}
const statement = `(${clauses.join(' OR ')})`
return {statement, binds}
}
module.exports.queryMetrics = async function ({
collectionId,
filter = {},
grant,
aggregation = 'unagg',
style = 'detail',
returnType = 'json'
}) {
const predicates = {
statements: [
'a.collectionId = ? '
],
binds: [collectionId]
}
const ctes = []
const columns = returnType === 'csv' ? [...baseColsFlat[aggregation]] : [...baseCols[aggregation]]
const joins = [
'enabled_asset a',
'left join stig_asset_map sa on a.assetId = sa.assetId',
'left join default_rev dr on a.collectionId = dr.collectionId and sa.benchmarkId = dr.benchmarkId',
'left join revision rev on dr.revId = rev.revId',
'left join stig on rev.benchmarkId = stig.benchmarkId'
]
if (grant.roleId === 1) {
ctes.push(dbUtils.cteAclEffective({grantIds: grant.grantIds}))
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
}
const groupBy = []
const orderBy = []
// FILTERS
if (filter.labelNames || filter.labelIds || filter.labelMatch) {
const {statement, binds} = genLabelPredicates({
labelNames: filter.labelNames,
labelIds: filter.labelIds,
labelMatch: filter.labelMatch,
collectionLabelTableAlias: 'clPred'
})
const innerQueryRaw = `select distinct assetId from enabled_asset left join collection_label_asset_map using (assetId)
left join collection_label clPred using(clId) where a.collectionId = ? and ${statement}`
const innerQueryFormatted = dbUtils.pool.format(innerQueryRaw, [collectionId, ...binds])
predicates.statements.push(`a.assetId IN (${innerQueryFormatted})`)
}
if (filter.assetIds) {
predicates.statements.push(
'a.assetId IN ?'
)
predicates.binds.push([filter.assetIds])
}
if (filter.benchmarkIds) {
predicates.statements.push(
'sa.benchmarkId IN ?'
)
predicates.binds.push([filter.benchmarkIds])
}
switch (aggregation) {
case 'asset':
predicates.statements.push('a.assetId IS NOT NULL')
groupBy.push('a.assetId')
orderBy.push('a.name')
break
case 'stig':
predicates.statements.push('sa.benchmarkId IS NOT NULL')
groupBy.push('rev.revId', 'dr.revisionPinned')
orderBy.push('rev.benchmarkId')
break
case 'collection':
joins.push(`left join enabled_collection c on a.collectionId = c.collectionId`)
groupBy.push('c.collectionId')
orderBy.push('c.name')
break
case 'label':
predicates.statements.push('a.assetId IS NOT NULL')
groupBy.push('cl.description', 'cl.color', 'cl.uuid', 'cl.name')
joins.push(
'left join collection_label_asset_map cla on a.assetId = cla.assetId',
'left join collection_label cl on cla.clId = cl.clId'
)
orderBy.push('cl.name')
break
case 'unagg':
predicates.statements.push('sa.benchmarkId IS NOT NULL')
break
}
if (style === 'detail') {
if (returnType === 'csv' && aggregation === 'unagg') {
columns.push(...colsMetricsDetail)
}
else if (returnType === 'csv') {
columns.push(...colsMetricsDetailAgg)
}
else {
columns.push( aggregation === 'unagg' ? sqlMetricsDetail : sqlMetricsDetailAgg)
}
}
else {
if (returnType === 'csv' && aggregation === 'unagg') {
columns.push(...colsMetricsSummary)
}
else if (returnType === 'csv') {
columns.push(...colsMetricsSummaryAgg)
}
else {
columns.push( aggregation === 'unagg' ? sqlMetricsSummary : sqlMetricsSummaryAgg)
}
}
const sql = dbUtils.makeQueryString({
ctes,
columns,
joins,
predicates,
groupBy,
orderBy,
format: true
})
const [rows] = await dbUtils.pool.query(sql)
return (rows || [])
}
module.exports.queryMetaMetrics = async function ({
filter = {},
grants,
aggregation = 'meta',
style = 'detail',
returnType = 'json'
}) {
const ctes = []
const columns = returnType === 'csv' ? [...baseColsFlat[aggregation]] : [...baseCols[aggregation]]
const joins = [
'enabled_asset a',
'left join stig_asset_map sa on a.assetId = sa.assetId',
'left join default_rev dr on a.collectionId = dr.collectionId and sa.benchmarkId = dr.benchmarkId',
'left join revision rev on dr.revId = rev.revId',
'left join stig on rev.benchmarkId = stig.benchmarkId'
]
const predicates = {
statements: [],
binds: []
}
const groupBy = []
const orderBy = []
let grantedCollectionIds = []
let restrictedGrantIds = []
const restrictedCollectionIds = []
if (filter.collectionIds) {
for (const collectionId of filter.collectionIds) {
if (grants[collectionId]) {
grantedCollectionIds.push(collectionId)
}
}
}
else {
grantedCollectionIds = Object.keys(grants)
}
for (const collectionId of grantedCollectionIds) {
if (grants[collectionId].roleId === 1) {
restrictedCollectionIds.push(collectionId)
restrictedGrantIds.push(grants[collectionId].grantIds)
}
}
restrictedGrantIds = restrictedGrantIds.flat()
if (grantedCollectionIds.length) {
predicates.statements.push('a.collectionId IN (?)')
predicates.binds.push(grantedCollectionIds)
}
else {
predicates.statements.push('false')
}
if (restrictedCollectionIds.length) {
ctes.push(dbUtils.cteAclEffective({grantIds: restrictedGrantIds}))
joins.push('left join cteAclEffective cae on sa.saId = cae.saId')
predicates.statements.push('case when a.collectionId IN (?) then cae.saId = sa.saId else true end')
predicates.binds.push(restrictedCollectionIds)
}
if (filter.benchmarkIds) {
predicates.statements.push('sa.benchmarkId IN ?')
predicates.binds.push([filter.benchmarkIds])
}
if (filter.revisionIds) {
predicates.statements.push('rev.revId IN ?')
predicates.binds.push([filter.revisionIds])
}
switch (aggregation) {
case 'meta':
predicates.statements.push('sa.benchmarkId IS NOT NULL')
break
case 'collection':
joins.push('left join enabled_collection c on a.collectionId = c.collectionId')
groupBy.push('c.collectionId')
orderBy.push('c.name')
break
case 'metaStig':
predicates.statements.push('sa.benchmarkId IS NOT NULL')
groupBy.push('rev.revId')
orderBy.push('rev.benchmarkId')
break
}
if (style === 'detail') {
if (returnType === 'csv') {
columns.push(...colsMetricsDetailAgg)
}
else {
columns.push(sqlMetricsDetailAgg)
}
}
else { //style: 'summary'
if (returnType === 'csv') {
columns.push(...colsMetricsSummaryAgg)
}
else {
columns.push(sqlMetricsSummaryAgg)
}
}
const sql = dbUtils.makeQueryString({
ctes,
columns,
joins,
predicates,
groupBy,
orderBy,
format: true
})
const [rows] = await dbUtils.pool.query(sql)
return (rows || [])
}
const sqlMetricsDetail = `json_object(
'assessments', rev.ruleCount,
'assessmentsBySeverity', json_object(
'low', rev.lowCount,
'medium', rev.mediumCount,
'high', rev.highCount
),
'assessed', sa.pass + sa.fail + sa.notapplicable,
'assessedBySeverity', json_object(
'low', sa.assessedLowCount,
'medium', sa.assessedMediumCount,
'high', sa.assessedHighCount
),
'minTs', DATE_FORMAT(sa.minTs, '%Y-%m-%dT%H:%i:%sZ'),
'maxTs', DATE_FORMAT(sa.maxTs, '%Y-%m-%dT%H:%i:%sZ'),
'maxTouchTs', DATE_FORMAT(sa.maxTouchTs, '%Y-%m-%dT%H:%i:%sZ'),
'findings', json_object(
'low', sa.lowCount,
'medium', sa.mediumCount,
'high', sa.highCount
),
'statuses', json_object(
'saved', json_object('total',sa.saved,'resultEngine',sa.savedResultEngine),
'submitted', json_object('total',sa.submitted,'resultEngine',sa.submittedResultEngine),
'rejected', json_object('total',sa.rejected,'resultEngine',sa.rejectedResultEngine),
'accepted', json_object('total',sa.accepted,'resultEngine',sa.acceptedResultEngine)
),
'results', json_object(
'notchecked', json_object('total',sa.notchecked,'resultEngine',sa.notcheckedResultEngine),
'notapplicable', json_object('total',sa.notapplicable,'resultEngine',sa.notapplicableResultEngine),
'pass', json_object('total',sa.pass,'resultEngine',sa.passResultEngine),
'fail', json_object('total',sa.fail,'resultEngine',sa.failResultEngine),
'unknown', json_object('total',sa.unknown,'resultEngine',sa.unknownResultEngine),
'error', json_object('total',sa.error,'resultEngine',sa.errorResultEngine),
'notselected', json_object('total',sa.notselected,'resultEngine',sa.notselectedResultEngine),
'informational', json_object('total',sa.informational,'resultEngine',sa.informationalResultEngine),
'fixed', json_object('total',sa.fixed,'resultEngine',sa.fixedResultEngine)
)
) as metrics`
const sqlMetricsDetailAgg = `json_object(
'assessments', coalesce(sum(rev.ruleCount),0),
'assessmentsBySeverity', json_object(
'low', coalesce(sum(rev.lowCount),0),
'medium', coalesce(sum(rev.mediumCount),0),
'high', coalesce(sum(rev.highCount),0)
),
'assessed', coalesce(sum(sa.pass + sa.fail + sa.notapplicable),0),
'assessedBySeverity', json_object(
'low', coalesce(sum(sa.assessedLowCount),0),
'medium', coalesce(sum(sa.assessedMediumCount),0),
'high', coalesce(sum(sa.assessedHighCount),0)
),
'minTs', DATE_FORMAT(MIN(sa.minTs), '%Y-%m-%dT%H:%i:%sZ'),
'maxTs', DATE_FORMAT(MAX(sa.maxTs), '%Y-%m-%dT%H:%i:%sZ'),
'maxTouchTs', DATE_FORMAT(MAX(sa.maxTouchTs), '%Y-%m-%dT%H:%i:%sZ'),
'findings', json_object(
'low', coalesce(sum(sa.lowCount),0),
'medium', coalesce(sum(sa.mediumCount),0),
'high', coalesce(sum(sa.highCount),0)
),
'statuses', json_object(
'saved', json_object('total',coalesce(sum(sa.saved),0),'resultEngine',coalesce(sum(sa.savedResultEngine),0)),
'submitted', json_object('total',coalesce(sum(sa.submitted),0),'resultEngine',coalesce(sum(sa.submittedResultEngine),0)),
'rejected', json_object('total',coalesce(sum(sa.rejected),0),'resultEngine',coalesce(sum(sa.rejectedResultEngine),0)),
'accepted', json_object('total',coalesce(sum(sa.accepted),0),'resultEngine',coalesce(sum(sa.acceptedResultEngine),0))
),
'results', json_object(
'notchecked', json_object('total',coalesce(sum(sa.notchecked),0),'resultEngine',coalesce(sum(sa.notcheckedResultEngine),0)),
'notapplicable', json_object('total',coalesce(sum(sa.notapplicable),0),'resultEngine',coalesce(sum(sa.notapplicableResultEngine),0)),
'pass', json_object('total',coalesce(sum(sa.pass),0),'resultEngine',coalesce(sum(sa.passResultEngine),0)),
'fail', json_object('total',coalesce(sum(sa.fail),0),'resultEngine',coalesce(sum(sa.failResultEngine),0)),
'unknown', json_object('total',coalesce(sum(sa.unknown),0),'resultEngine',coalesce(sum(sa.unknownResultEngine),0)),
'error', json_object('total',coalesce(sum(sa.error),0),'resultEngine',coalesce(sum(sa.errorResultEngine),0)),
'notselected', json_object('total',coalesce(sum(sa.notselected),0),'resultEngine',coalesce(sum(sa.notselectedResultEngine),0)),
'informational', json_object('total',coalesce(sum(sa.informational),0),'resultEngine',coalesce(sum(sa.informationalResultEngine),0)),
'fixed', json_object('total',coalesce(sum(sa.fixed),0),'resultEngine',coalesce(sum(sa.fixedResultEngine),0))
)
) as metrics`
const sqlMetricsSummary = `json_object(
'assessments', rev.ruleCount,
'assessmentsBySeverity', json_object(
'low', rev.lowCount,
'medium', rev.mediumCount,
'high', rev.highCount
),
'assessed', sa.pass + sa.fail + sa.notapplicable,
'assessedBySeverity', json_object(
'low', sa.assessedLowCount,
'medium', sa.assessedMediumCount,
'high', sa.assessedHighCount
),
'minTs', DATE_FORMAT(sa.minTs, '%Y-%m-%dT%H:%i:%sZ'),
'maxTs', DATE_FORMAT(sa.maxTs, '%Y-%m-%dT%H:%i:%sZ'),
'maxTouchTs', DATE_FORMAT(sa.maxTouchTs, '%Y-%m-%dT%H:%i:%sZ'),
'results', json_object(
'pass', sa.pass,
'fail', sa.fail,
'notapplicable', sa.notapplicable,
'other', sa.notchecked + sa.unknown + sa.error + sa.notselected + sa.informational + sa.fixed
),
'statuses', json_object(
'saved', sa.saved,
'submitted', sa.submitted,
'accepted', sa.accepted,
'rejected', sa.rejected
),
'findings', json_object(
'low', sa.lowCount,
'medium', sa.mediumCount,
'high', sa.highCount
)
) as metrics`
const sqlMetricsSummaryAgg = `json_object(
'assessments', coalesce(sum(rev.ruleCount),0),
'assessmentsBySeverity', json_object(
'low', coalesce(sum(rev.lowCount),0),
'medium', coalesce(sum(rev.mediumCount),0),
'high', coalesce(sum(rev.highCount),0)
),
'assessed', coalesce(sum(sa.pass + sa.fail + sa.notapplicable),0),
'assessedBySeverity', json_object(
'low', coalesce(sum(sa.assessedLowCount),0),
'medium', coalesce(sum(sa.assessedMediumCount),0),
'high', coalesce(sum(sa.assessedHighCount),0)
),
'minTs', DATE_FORMAT(MIN(sa.minTs), '%Y-%m-%dT%H:%i:%sZ'),
'maxTs', DATE_FORMAT(MAX(sa.maxTs), '%Y-%m-%dT%H:%i:%sZ'),
'maxTouchTs', DATE_FORMAT(MAX(sa.maxTouchTs), '%Y-%m-%dT%H:%i:%sZ'),
'results', json_object(
'pass', coalesce(sum(sa.pass),0),
'fail', coalesce(sum(sa.fail),0),
'notapplicable', coalesce(sum(sa.notapplicable),0),
'other', coalesce(sum(sa.notchecked + sa.unknown + sa.error + sa.notselected + sa.informational + sa.fixed),0)
),
'statuses', json_object(
'saved', coalesce(sum(sa.saved),0),
'submitted', coalesce(sum(sa.submitted),0),
'accepted', coalesce(sum(sa.accepted),0),
'rejected', coalesce(sum(sa.rejected),0)
),
'findings', json_object(
'low', coalesce(sum(sa.lowCount),0),
'medium', coalesce(sum(sa.mediumCount),0),
'high', coalesce(sum(sa.highCount),0)
)
) as metrics`
const colsMetricsDetail = [
`rev.ruleCount as assessments`,
`rev.lowCount as assessmentsLow`,
`rev.mediumCount as assessmentsMedium`,
`rev.highCount as assessmentsHigh`,
`sa.pass + sa.fail + sa.notapplicable as assessed`,
`sa.assessedLowCount as assessedLow`,
`sa.assessedMediumCount as assessedMedium`,
`sa.assessedHighCount as assessedHigh`,
`DATE_FORMAT(sa.minTs, '%Y-%m-%dT%H:%i:%sZ') as minTs`,
`DATE_FORMAT(sa.maxTs, '%Y-%m-%dT%H:%i:%sZ') as maxTs`,
`DATE_FORMAT(sa.maxTouchTs, '%Y-%m-%dT%H:%i:%sZ') as maxTouchTs`,
`sa.lowCount as findingsLow`,
`sa.mediumCount as findingsMedium`,
`sa.highCount as findingsHigh`,
`sa.saved`,
`sa.savedResultEngine`,
`sa.submitted`,
`sa.submittedResultEngine`,
`sa.accepted`,
`sa.acceptedResultEngine`,
`sa.rejected`,
`sa.rejectedResultEngine`,
`sa.pass`,
`sa.passResultEngine`,
`sa.fail`,
`sa.failResultEngine`,
`sa.notapplicable`,
`sa.notapplicableResultEngine`,
`sa.notchecked`,
`sa.notcheckedResultEngine`,
`sa.unknown`,
`sa.unknownResultEngine`,
`sa.error`,
`sa.errorResultEngine`,
`sa.notselected`,
`sa.notselectedResultEngine`,
`sa.informational`,
`sa.informationalResultEngine`,
`sa.fixed`,
`sa.fixedResultEngine`
]
const colsMetricsDetailAgg = [
`coalesce(sum(rev.ruleCount),0) as assessments`,
`coalesce(sum(rev.lowCount),0) as assessmentsLow`,
`coalesce(sum(rev.mediumCount),0) as assessmentsMedium`,
`coalesce(sum(rev.highCount),0) as assessmentsHigh`,
`coalesce(sum(sa.pass + sa.fail + sa.notapplicable),0) as assessed`,
`coalesce(sum(sa.assessedLowCount),0) as assessedLow`,
`coalesce(sum(sa.assessedMediumCount),0) as assessedMedium`,
`coalesce(sum(sa.assessedHighCount),0) as assessedHigh`,
`DATE_FORMAT(min(sa.minTs), '%Y-%m-%dT%H:%i:%sZ') as minTs`,
`DATE_FORMAT(max(sa.maxTs), '%Y-%m-%dT%H:%i:%sZ') as maxTs`,
`DATE_FORMAT(max(sa.maxTouchTs), '%Y-%m-%dT%H:%i:%sZ') as maxTouchTs`,
`coalesce(sum(sa.lowCount),0) as findingsLow`,
`coalesce(sum(sa.mediumCount),0) as findingsMedium`,
`coalesce(sum(sa.highCount),0) as findingsHigh`,
`coalesce(sum(sa.saved),0) as saved`,
`coalesce(sum(sa.savedResultEngine),0) as savedResultEngine`,
`coalesce(sum(sa.submitted),0) as submitted`,
`coalesce(sum(sa.submittedResultEngine),0) as submittedResultEngine`,
`coalesce(sum(sa.accepted),0) as accepted`,
`coalesce(sum(sa.acceptedResultEngine),0) as acceptedResultEngine`,
`coalesce(sum(sa.rejected),0) as rejected`,
`coalesce(sum(sa.rejectedResultEngine),0) as rejectedResultEngine`,
`coalesce(sum(sa.pass),0) as pass`,
`coalesce(sum(sa.passResultEngine),0) as passResultEngine`,
`coalesce(sum(sa.fail),0) as fail`,
`coalesce(sum(sa.failResultEngine),0) as failResultEngine`,
`coalesce(sum(sa.notapplicable),0) as notapplicable`,
`coalesce(sum(sa.notapplicableResultEngine),0) as notapplicableResultEngine`,
`coalesce(sum(sa.notchecked),0) as notchecked`,
`coalesce(sum(sa.notcheckedResultEngine),0) as notcheckedResultEngine`,
`coalesce(sum(sa.unknown),0) as unknown`,
`coalesce(sum(sa.unknownResultEngine),0) as unknownResultEngine`,
`coalesce(sum(sa.error),0) as error`,
`coalesce(sum(sa.errorResultEngine),0) as errorResultEngine`,
`coalesce(sum(sa.notselected),0) as notselected`,
`coalesce(sum(sa.notselectedResultEngine),0) as notselectedResultEngine`,
`coalesce(sum(sa.informational),0) as informational`,
`coalesce(sum(sa.informationalResultEngine),0) as informationalResultEngine`,
`coalesce(sum(sa.fixed),0) as fixed`,
`coalesce(sum(sa.fixedResultEngine),0) as fixedResultEngine`
]
const colsMetricsSummary = [
'rev.ruleCount as "assessments"',
`rev.lowCount as assessmentsLow`,
`rev.mediumCount as assessmentsMedium`,
`rev.highCount as assessmentsHigh`,
'sa.pass + sa.fail + sa.notapplicable as "assessed"',
'sa.assessedLowCount as "assessedLow"',
'sa.assessedMediumCount as "assessedMedium"',
'sa.assessedHighCount as "assessedHigh"',
`DATE_FORMAT(sa.minTs, '%Y-%m-%dT%H:%i:%sZ') as minTs`,
`DATE_FORMAT(sa.maxTs, '%Y-%m-%dT%H:%i:%sZ') as maxTs`,
`DATE_FORMAT(sa.maxTouchTs, '%Y-%m-%dT%H:%i:%sZ') as maxTouchTs`,
'sa.lowCount as "findingsLow"',
'sa.mediumCount as "findingsMedium"',
'sa.highCount as "findingsHigh"',
'sa.pass as "pass"',
'sa.fail as "fail"',
'sa.notapplicable as "notapplicable"',
'sa.notchecked + sa.unknown + sa.error + sa.notselected + sa.informational + sa.fixed as "other"',
'sa.saved as "saved"',
'sa.submitted as "submitted"',
'sa.accepted as "accepted"',
'sa.rejected as "rejected"'
]
const colsMetricsSummaryAgg = [
'coalesce(sum(rev.ruleCount),0) as "assessments"',
`coalesce(sum(rev.lowCount),0) as assessmentsLow`,
`coalesce(sum(rev.mediumCount),0) as assessmentsMedium`,
`coalesce(sum(rev.highCount),0) as assessmentsHigh`,
'coalesce(sum(sa.pass + sa.fail + sa.notapplicable),0) as "assessed"',
'coalesce(sum(sa.assessedLowCount),0) as "assessedLow"',
'coalesce(sum(sa.assessedMediumCount),0) as "assessedMedium"',
'coalesce(sum(sa.assessedHighCount),0) as "assessedHigh"',
`DATE_FORMAT(MIN(sa.minTs), '%Y-%m-%dT%H:%i:%sZ') as minTs`,
`DATE_FORMAT(MAX(sa.maxTs), '%Y-%m-%dT%H:%i:%sZ') as maxTs`,
`DATE_FORMAT(MAX(sa.maxTouchTs), '%Y-%m-%dT%H:%i:%sZ') as maxTouchTs`,
'coalesce(sum(sa.lowCount),0) as "findingsLow"',
'coalesce(sum(sa.mediumCount),0) as "findingsMedium"',
'coalesce(sum(sa.highCount),0) as "findingsHigh"',
'coalesce(sum(sa.pass),0) as "pass"',
'coalesce(sum(sa.fail),0) as "fail"',
'coalesce(sum(sa.notapplicable),0) as "notapplicable"',
'coalesce(sum(sa.notchecked + sa.unknown + sa.error + sa.notselected + sa.informational + sa.fixed),0) as "other"',
'coalesce(sum(sa.saved),0) as "saved"',
'coalesce(sum(sa.submitted),0) as "submitted"',
'coalesce(sum(sa.accepted),0) as "accepted"',
'coalesce(sum(sa.rejected),0) as "rejected"'
]
const sqlLabels = `coalesce(
(select
json_arrayagg(json_object(
'labelId', BIN_TO_UUID(cl2.uuid,1),
'name', cl2.name,
'color', cl2.color
))
from
collection_label_asset_map cla2
left join collection_label cl2 on cla2.clId = cl2.clId
where
cla2.assetId = a.assetId),
json_array()) as labels`
const sqlLabelsFlat = `(
select
group_concat(cl2.name)
from
collection_label_asset_map cla2
left join collection_label cl2 on cla2.clId = cl2.clId
where
cla2.assetId = a.assetId) as "labels"`
const baseCols = {
unagg: [
'cast(a.assetId as char) as assetId',
'a.name',
sqlLabels,
'rev.benchmarkId',
'stig.title',
'rev.marking',
'rev.revisionStr',
'CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END as revisionPinned',
`DATE_FORMAT(rev.benchmarkDateSql, '%Y-%m-%d') as revisionDate`,
],
asset: [
'cast(a.assetId as char) as assetId',
'a.name',
sqlLabels,
'a.ip',
'a.fqdn',
'a.mac',
'case when count(sa.benchmarkId) > 0 THEN json_arrayagg(sa.benchmarkId) ELSE json_array() END as benchmarkIds'
],
collection: [
'cast(c.collectionId as char) as collectionId',
'c.name',
'count(distinct a.assetId) as assets',
'count(distinct sa.benchmarkId) as stigs',
'count(sa.saId) as checklists'
],
stig: [
'rev.benchmarkId',
'stig.title',
'rev.marking',
'rev.revisionStr',
'CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END as revisionPinned',
`DATE_FORMAT(rev.benchmarkDateSql, '%Y-%m-%d') as revisionDate`,
'count(distinct a.assetId) as assets',
'rev.ruleCount'
],
label: [
'BIN_TO_UUID(cl.uuid,1) as labelId',
'cl.name',
'cl.color',
'cl.description',
'count(distinct a.assetId) as assets'
],
meta: [
'count(distinct a.collectionId) as collections',
'count(distinct a.assetId) as assets',
'count(distinct sa.benchmarkId) as stigs',
'count(sa.saId) as checklists'
],
metaStig: [
'rev.benchmarkId',
'stig.title',
'rev.marking',
'rev.revisionStr',
`DATE_FORMAT(rev.benchmarkDateSql, '%Y-%m-%d') as revisionDate`,
'count(distinct a.collectionId) as collections',
'count(distinct a.assetId) as assets',
'rev.ruleCount'
]
}
const baseColsFlat = {
unagg: [
'cast(a.assetId as char) as assetId',
'a.name',
sqlLabelsFlat,
'rev.benchmarkId',
'stig.title',
'rev.marking',
'rev.revisionStr',
'CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END as revisionPinned',
`DATE_FORMAT(rev.benchmarkDateSql, '%Y-%m-%d') as revisionDate`,
],
asset: [
'cast(a.assetId as char) as assetId',
'a.name',
sqlLabelsFlat,
'group_concat(sa.benchmarkId) as benchmarkIds'
],
collection: [
'cast(c.collectionId as char) as collectionId',
'c.name',
'count(distinct a.assetId) as assets',
'count(sa.saId) as checklists'
],
stig: [
'rev.benchmarkId',
'stig.title',
'rev.marking',
'rev.revisionStr',
'CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END as revisionPinned',
`DATE_FORMAT(rev.benchmarkDateSql, '%Y-%m-%d') as revisionDate`,
'count(distinct a.assetId) as assets',
'rev.ruleCount'
],
label: [
'BIN_TO_UUID(cl.uuid,1) as labelId',
'cl.name',
'count(distinct a.assetId) as assets'
],
meta: [
'count(distinct a.collectionId) as collections',
'count(distinct a.assetId) as assets',
'count(distinct sa.benchmarkId) as stigs',
'count(sa.saId) as checklists'
],
metaStig: [
'rev.benchmarkId',
'stig.title',
'rev.marking',
'rev.revisionStr',
`DATE_FORMAT(rev.benchmarkDateSql, '%Y-%m-%d') as revisionDate`,
'count(distinct a.collectionId) as collections',
'count(distinct a.assetId) as assets',
'rev.ruleCount'
]
}
================================================
FILE: api/source/service/OperationService.js
================================================
'use strict';
const dbUtils = require('./utils')
const config = require('../utils/config')
const logger = require('../utils/logger')
const BJSON = require('../utils/buffer-json')
const { Readable, Transform } = require("node:stream")
const { pipeline } = require("node:stream/promises")
const zlib = require("node:zlib")
const klona = require('../utils/klona')
const os = require('node:os')
const Umzug = require('umzug')
const path = require('path')
/**
* Return version information
*
* returns ApiVersion
**/
exports.getConfiguration = async function() {
const sql = `SELECT * from config`
const [rows] = await dbUtils.pool.query(sql)
const config = {}
for (const row of rows) {
config[row.key] = row.value
}
return (config)
}
exports.setConfigurationItem = async function (key, value) {
const sql = 'INSERT INTO config (`key`, `value`) VALUES (?, ?) ON DUPLICATE KEY UPDATE value = VALUES(value)'
await dbUtils.pool.query(sql, [key, value])
return (true)
}
/**
* getAppData - streams JSONL records to the response. The JSONL are either
* data records from a MySQL table (always an array) or metadata records (always an object).
*
* @param {import('express').Response} res express response
* @returns {undefined}
* @example Abbreviated example of JSONL which is streamed to the response:
* {"version":"1.4.13","commit":{"branch":"na","sha":"na","tag":"na","describe":"na"},"date":"2024-08-18T15:29:16.784Z","lastMigration":33}\n
{"tables":[{"table":"stig","rowCount":4}, ... ], "totalRows": 4}\n
{"table":"stig","columns":"`benchmarkId`, `title`","rowCount":4}\n
["RHEL_7_STIG_TEST","Red Hat Enterprise Linux 7 Security Technical Implementation Guide"]\n
["VPN_SRG_TEST","Virtual Private Network (VPN) Security Requirements Guide"]\n
["VPN_SRG_Rule-fingerprint-match-test","Virtual Private Network (VPN) Security Requirements Guide - replaced"]\n
["Windows_10_STIG_TEST","Windows 10 Security Technical Implementation Guide"]\n ...
*/
exports.getAppData = async function (res, format) {
/** @type {string[]} tables to exclude from the appdata file */
const excludedTables = [
'_migrations',
'status',
'result',
'severity_cat_map',
'cci',
'cci_reference_map',
'config',
'job',
'job_run',
'job_task_map',
'task',
'task_output'
]
let sink
if (format === 'gzip') {
/** @type {zlib.Gzip} transform stream to compress JSONL records and write to the response */
sink = zlib.createGzip()
sink.pipe(res)
}
else {
/** @type {http.ServerResponse} */
sink = res
}
sink.setMaxListeners(Infinity)
// Write metadata record {version, commit, date, lastMigration}
const {version, commit, lastMigration} = config
sink.write(JSON.stringify({version, commit, date: new Date(), lastMigration}) + '\n')
// Execute SQL to retrieve a list of tables and their non-generated columns. The query binds
// to the schema name and the excluded tables.
/** @type {Array.} */
const sql = `SELECT
TABLE_NAME as \`table\`,
cast(concat('[', group_concat(CONCAT('"\`',COLUMN_NAME,'\`"') order by COLUMN_NAME), ']') as json) as columns
FROM
INFORMATION_SCHEMA.COLUMNS
where
TABLE_SCHEMA=?
and TABLE_NAME IN (select TABLE_NAME FROM INFORMATION_SCHEMA.TABLES where TABLE_SCHEMA=? and TABLE_TYPE='BASE TABLE')
and TABLE_NAME not in (?)
and EXTRA NOT LIKE '% GENERATED'
group by
TABLE_NAME`
const [tableRows] = await dbUtils.pool.query(sql, [config.database.schema, config.database.schema, excludedTables])
/**
* @type {Object.} object pivoted from tableRows[]
* @example
* '{
"asset": {
"columns": "`assetId`,`name`,`fqdn`, ... "
},
"check_content": {
"columns": "`ccId`,`content`"
},
"collection": {
"columns": "`collectionId`,`name`,`description`, ... "
}
}'
*/
const tableMetadata = tableRows.reduce((acc, value) => {
acc[value.table] = {columns:value.columns.join(',')}
return acc
}, {})
/** @type {string[]} */
const tableNames = Object.keys(tableMetadata)
/** @type {number} incremented by the row count of each table */
let totalRows = 0
/** @type {{table:string, rowCount:number}[]} */
let tables = []
// Select and handle the row count for each table.
for (const table of tableNames) {
const [row] = await dbUtils.pool.query(`select count(*) as cnt from ${table}`)
const rowCount = row[0].cnt
tableMetadata[table].rowCount = rowCount
tables.push({table, rowCount})
totalRows += rowCount
}
// Write metadata record {tables, totalRows}
sink.write(JSON.stringify({tables, totalRows}) + '\n')
for (const table of tableNames) {
// create readable stream using the non-promise interface of dbUtils.pool.pool
// select all rows for non-generated columns in table
// perform custom type casting of fields to JS
/** @type {Readable} */
const queryStream = dbUtils.pool.pool.query({
sql: `select ${tableMetadata[table].columns} from ${table}`,
rowsAsArray: true,
typeCast: function (field, next) {
// BIT fields returned as boolean
if ((field.type === "BIT") && (field.length === 1)) {
let bytes = field.buffer() || [0]
return (bytes[0] === 1)
}
// Designated fields returned as original MySQL strings
if (field.type === 'JSON' || field.type === 'DATETIME' || field.type === 'DATE' || field.type === 'TIMESTAMP' || field.type === 'TIME' || field.type === 'YEAR') {
return (field.string("utf8"))
}
return next()
}
}).stream()
// Write metadata record {table, columns, rowCount}
sink.write(JSON.stringify({table, ...tableMetadata[table]}) + '\n')
/** @type {Transform} writes a JSONL data record for each tuple of row data*/
const bjson = new Transform({
objectMode: true,
transform: (data, encoding, cb) => {
// BSJON supports stringify() and parse() of Buffer values
cb(null, BJSON.stringify(data) + '\n')
}
})
// pipeline writes data records [field, field, ...] to sink, ends without closing sink
await pipeline(queryStream, bjson, sink, { end: false })
}
// ending sink will also end the response
sink.end()
}
exports.getAppDataTables = async function () {
const sql = `SELECT
TABLE_NAME as name,
TABLE_ROWS as \`rows\`,
DATA_LENGTH as dataLength
FROM
information_schema.TABLES
WHERE
TABLE_SCHEMA=? and TABLE_TYPE='BASE TABLE'
ORDER BY
TABLE_NAME`
const [rows] = await dbUtils.pool.query(sql, [config.database.schema])
return (rows)
}
/**
* replaceAppData - process a file created by getAppData() and execute SQL queries with progress messages
*
* @param {Buffer} buffer - buffer with file content
* @param {function(Object)} progressCb - optional, argument is an object with progress status
* @returns {Promise} promise
*/
exports.replaceAppData = async function (buffer, contentType, progressCb = () => {}) {
/**
* ParseJSONLStream - Transform chunks of JSONL records into individual parsed AppData records (N:1).
* @extends Transform
*/
/** @type {boolean} needsMigrations - indicates if migrations are required */
let needsMigrations = false
class ParseJSONLStream extends Transform {
/**
* @param {Object} param
* @param {function(string):any} param.jsonParser - function for JSON parsing, default JSON.parse()
* @param {string} param.separator - character separating JSONL records, default '\n'
*/
constructor({jsonParser = JSON.parse, separator = '\n'} = {}) {
super({objectMode: true})
Object.assign(this, {separator, jsonParser})
/** @type {RegExp} RegExp for .split() that includes any trailing separator */
this.splitRegExp = new RegExp(`(?<=${separator})`)
/** @type {string} holds incoming chunk prefaced by any partial record from previous transform */
this.buffer = ''
}
/**
* @param {Buffer} chunk - buffer from Gunzip that can span multiple JSONL records
* @param {string} encoding - usually 'utf8'
* @param {function()} cb - signals completion
*/
_transform(chunk, encoding, cb) {
this.buffer += chunk.toString(encoding)
/** @type {string[]} list of JSONL, last item might be truncated or partial */
const candidates = this.buffer.split(this.splitRegExp)
/** @type {number} index of last candidates[] item */
const lastIndex = candidates.length - 1
// clear buffer for the next _transform() or _flush()
this.buffer = ''
/** index @type {number} */
/** candidate @type {string} */
for (const [index, candidate] of candidates.entries()) {
if (index === lastIndex && !candidate.endsWith(this.separator)) {
// this is the last candidate and there's no trailing separator
// initialize buffer for next _transform() or _flush()
this.buffer = candidate
}
else {
try {
// if parsable, write parsed value
this.push(this.jsonParser(candidate))
}
// swallow any parse error
catch {}
}
}
cb()
}
/** @param {function()} cb signals completion */
_flush(cb) {
try {
// if what's left in the buffer is parsable, write parsed value
if (this.buffer) this.push(this.jsonParser(this.buffer))
}
// swallow any parse error
catch {}
cb()
}
}
/**
* AppDataQueryStream - Transform AppData records into an SQL query object (N:1)
* @extends Transform
*/
class AppDataQueryStream extends Transform {
/**
* @param {Object} param
* @param {number} param.maxValues - maximum number of values for an insert query.
* @param {function(Object): any} param.onTablesFn - called when record {tables, ...} is read
* @param {function(Object): any} param.onMigrationFn - called when record {..., lastMigration} is read
*/
constructor({maxValues = 10000, onTablesFn = new Function(), onMigrationFn = async function () {}}) {
super({objectMode: true})
Object.assign(this, { maxValues, onTablesFn, onMigrationFn })
/** @type {null|Object} the last metadata record encountered */
this.currentMetadata = null
/** @type {Array} values for an insert query */
this.currentBinds = []
}
/**
* @param {Buffer} chunk a single AppData record
* @param {string} encoding usually 'utf8'
* @param {function()} cb signals completion
*/
async _transform(chunk, encoding, cb) {
if (Array.isArray(chunk)) {
this.currentBinds.push(chunk)
if (this.currentBinds.length === this.maxValues || this.currentBinds.length === 0) {
this.push(this.formatCurrentQuery())
this.currentBinds = []
}
}
else if (chunk.lastMigration) {
try {
await this.onMigrationFn(chunk)
}
catch (e) {
cb(e)
return
}
}
else if (chunk.table){
if (this.currentMetadata) {
this.push(this.formatCurrentQuery())
}
this.currentMetadata = chunk
this.currentBinds = []
this.push(this.formatCurrentQuery())
}
else if (chunk.tables) {
try {
this.onTablesFn(chunk)
}
catch (e) {
cb(e)
return
}
}
else {
this.currentMetadata = null
}
cb()
}
/** @param {function()} cb signals completion */
_flush(cb) {
this.push(this.formatCurrentQuery())
cb()
}
/**
* Creates an object with an SQL insert or truncate statement that operates
* on the current table and any current binds
* @returns {{table:string, sql:string, valueCount:number}} */
formatCurrentQuery() {
const sqlInsert = this.currentBinds.length
? `insert into ${this.currentMetadata.table}(${this.currentMetadata.columns}) values ?`
: `truncate ${this.currentMetadata.table}`
return {
table: this.currentMetadata.table,
sql: dbUtils.pool.format(sqlInsert, [this.currentBinds]),
valueCount: this.currentBinds.length
}
}
}
/**
* @param {any} record expected to be AppData metadata {..., lastMigration}
* @returns {undefined}
* @throws {Error}
*/
async function onMigrationFn(record) {
if (record.lastMigration === config.lastMigration) return
if (record.lastMigration > config.lastMigration) {
throw new Error(`API migration v${config.lastMigration} is less than the source migration v${record.lastMigration}`)
}
needsMigrations = true
await resetDatabase()
await migrateTo(record.lastMigration)
}
async function migrateTo(migration = config.lastMigration) {
const endMigration = migration.toString().padStart(4, '0') + '.js'
const umzug = new Umzug({
migrations: {
path: path.join(__dirname, './migrations'),
params: [dbUtils.pool]
},
storage: path.join(__dirname, './migrations/lib/umzug-mysql-storage'),
storageOptions: {
pool: dbUtils.pool
}
})
umzug.on('migrating', (name) => {
progressCb({migration: name, status: 'started'})
})
umzug.on('migrated', (name) => {
progressCb({migration: name, status: 'finished'})
})
await umzug.up({to: endMigration})
}
async function resetDatabase() {
const connection = await dbUtils.pool.getConnection()
const sql = `SELECT
table_name,
table_type
FROM
information_schema.TABLES
WHERE
TABLE_SCHEMA=?`
const [tables] = await connection.query(sql,[config.database.schema])
await connection.query('SET FOREIGN_KEY_CHECKS = 0')
for (const table of tables) {
const drop = `DROP ${table.TABLE_TYPE === 'BASE TABLE' ? 'TABLE' : 'VIEW'} ${table.TABLE_NAME}`
await connection.query(drop)
progressCb({sql: drop})
}
await connection.query('SET FOREIGN_KEY_CHECKS = 1')
await connection.release()
}
function createChunkedReadable(buffer, chunkSize = 64 * 1024) {
let offset = 0
return new Readable({
read() {
if (offset >= buffer.length) {
this.push(null) // No more data, signal end of stream
}
else {
const chunk = buffer.subarray(offset, offset + chunkSize)
this.push(chunk) // Push the next chunk
offset += chunkSize
}
}
})
}
/** @type {import('mysql2/promise').PoolConnection} */
let connection
try {
connection = await dbUtils.pool.getConnection()
await connection.query('SET FOREIGN_KEY_CHECKS=0')
const jsonl = new ParseJSONLStream({jsonParser: BJSON.parse})
const queries = new AppDataQueryStream({maxValues: 10000, onTablesFn: progressCb, onMigrationFn})
if (contentType === 'application/gzip' || contentType === 'application/x-gzip') {
pipeline(Readable.from(buffer), zlib.createGunzip(), jsonl, queries)
}
else {
pipeline(createChunkedReadable(buffer, 10 * 1024 * 1024), jsonl, queries)
}
let seq = 0
for await (const data of queries) {
await connection.query(data.sql)
seq++
progressCb({seq, table: data.table, valueCount: data.valueCount})
}
if (needsMigrations) await migrateTo(config.lastMigration)
progressCb({status: 'success'})
}
catch (err) {
progressCb({status: 'fail', error: err.message})
return undefined
}
finally {
if (typeof connection !== 'undefined') {
await connection.query('SET FOREIGN_KEY_CHECKS=1')
connection.release()
}
}
}
exports.getAppInfo = async function(options = {}) {
const { includeRowCounts } = options
const schema = 'stig-manager-appinfo-v1.1'
const sqlAnalyze = `ANALYZE TABLE collection, asset, review, review_history, user`
const sqlInfoSchema = `
SELECT
TABLE_NAME as tableName,
TABLE_ROWS as tableRows,
TABLE_COLLATION as tableCollation,
AVG_ROW_LENGTH as avgRowLength,
DATA_LENGTH as dataLength,
INDEX_LENGTH as indexLength,
AUTO_INCREMENT as autoIncrement,
CREATE_TIME as createTime,
UPDATE_TIME as updateTime
FROM
information_schema.TABLES
WHERE
TABLE_SCHEMA = ?
and TABLE_TYPE='BASE TABLE'
ORDER BY
TABLE_NAME`
const sqlCollectionAssetStigs = `
SELECT
CAST(sub.collectionId as char) as collectionId,
sum(case when sub.assetId is not null and sub.stigAssetCnt = 0 then 1 else 0 end) as range00,
sum(case when sub.stigAssetCnt >= 1 and sub.stigAssetCnt <= 5 then 1 else 0 end) as range01to05,
sum(case when sub.stigAssetCnt >= 6 and sub.stigAssetCnt <= 10 then 1 else 0 end) as range06to10,
sum(case when sub.stigAssetCnt >= 11 and sub.stigAssetCnt <= 15 then 1 else 0 end) as range11to15,
sum(case when sub.stigAssetCnt >= 16 then 1 else 0 end) as range16plus
FROM
(SELECT
c.collectionId,
c.name,
a.assetId,
COUNT(sa.assetId) as stigAssetCnt
FROM
collection c
LEFT JOIN asset a on a.collectionId = c.collectionId and a.state = "enabled"
LEFT JOIN stig_asset_map sa on sa.assetId = a.assetId
GROUP BY
c.collectionId,
c.name,
a.assetId) as sub
GROUP BY
sub.collectionId
ORDER BY
sub.collectionId
`
const sqlCountsByCollection = `
SELECT
cast(c.collectionId as char) as collectionId,
c.name,
c.state,
c.settings,
count(distinct if(a.state = "enabled", a.assetId, null)) as assets,
count(distinct if(a.state = "disabled", a.assetId, null)) as assetsDisabled,
count(distinct if(a.state = "enabled", sa.benchmarkId, null)) as uniqueStigs,
sum(if(a.state = "enabled" and sa.saId, 1, 0)) as stigAssignments,
sum(if(a.state = "enabled",rev.ruleCount,0)) as rules,
sum(if(a.state = "enabled", (sa.pass + sa.fail + sa.notapplicable + sa.notchecked + sa.notselected + sa.informational + sa.fixed + sa.unknown + sa.error), 0)) as reviews,
sum(if(a.state = "disabled", (sa.pass + sa.fail + sa.notapplicable + sa.notchecked + sa.notselected + sa.informational + sa.fixed + sa.unknown + sa.error), 0)) as reviewsDisabled
FROM
collection c
left join asset a on c.collectionId = a.collectionId
left join stig_asset_map sa on a.assetId = sa.assetId
left join default_rev dr on c.collectionId = dr.collectionId and sa.benchmarkId = dr.benchmarkId
left join revision rev on dr.revId = rev.revId
GROUP BY
c.collectionId
ORDER BY
c.collectionId
`
const sqlLabelCountsByCollection = `
SELECT
cast(c.collectionId as char) as collectionId,
count(distinct cl.clId) as collectionLabels,
count(distinct clam.assetId) as labeledAssets,
count(distinct clam.claId) as assetLabels
FROM
collection c
left join collection_label cl on cl.collectionId = c.collectionId
left join collection_label_asset_map clam on clam.clId = cl.clId
left join asset a on clam.assetId = a.assetId and a.state = "enabled"
GROUP BY
c.collectionId
`
const sqlGrantsByCollection = `
with ctePerGrantee as (
select
cg.collectionId,
json_object(
'grantId', cg.grantId,
'grantee', json_object(
'userId', cg.userId,
'userGroupId', cg.userGroupId
),
'ruleCounts', json_object(
'rw', SUM(CASE WHEN cga.access = 'rw' THEN 1 ELSE 0 END),
'r', SUM(CASE WHEN cga.access = 'r' THEN 1 ELSE 0 END),
'none', SUM(CASE WHEN cga.access = 'none' THEN 1 ELSE 0 END)
),
'uniqueAssets', count(distinct if(a.state = 'enabled', sam.assetId, null)),
'uniqueAssetsDisabled', count(distinct if(a.state = 'disabled', sam.assetId, null)),
'uniqueStigs', count(distinct if(a.state = 'enabled', sam.benchmarkId, null)),
'uniqueStigsDisabled', count(distinct if(a.state = 'disabled', sam.benchmarkId, null)),
'role',
case when cg.roleId = 1 then 'restricted' else
case when cg.roleId = 2 then 'full' else
case when cg.roleId = 3 then 'manage' else
case when cg.roleId = 4 then 'owner'
end
end
end
end
) as perGrantee
from
collection_grant cg
left join collection_grant_acl cga ON cg.grantId = cga.grantId
left join stig_asset_map sam on sam.assetId=cga.assetId and sam.benchmarkId=cga.benchmarkId
left join asset a on a.assetId = sam.assetId
group by
cg.grantId)
select
collectionId,
json_arrayagg(perGrantee) as grants
from
ctePerGrantee
group by
collectionId`
const sqlRoleCountsByCollection = `
SELECT
collectionId,
SUM(CASE WHEN roleId = 1 THEN 1 ELSE 0 END) AS restricted,
SUM(CASE WHEN roleId = 2 THEN 1 ELSE 0 END) AS full,
SUM(CASE WHEN roleId = 3 THEN 1 ELSE 0 END) AS manage,
SUM(CASE WHEN roleId = 4 THEN 1 ELSE 0 END) AS owner
FROM
collection_grant
GROUP BY
collectionId
ORDER BY
collectionId
`
const sqlUserInfo = `
select
ud.userId,
ud.username,
ud.created,
ud.lastAccess,
coalesce(
JSON_EXTRACT(ud.lastClaims, '$.${config.oauth.claims.privileges}'),
json_array()
) as privileges,
json_object(
"restricted", sum(case when cg.roleId = 1 then 1 else 0 end),
"full", sum(case when cg.roleId = 2 then 1 else 0 end),
"manage", sum(case when cg.roleId = 3 then 1 else 0 end),
"owner", sum(case when cg.roleId = 4 then 1 else 0 end)
) as roles
from
user_data ud
left join collection_grant cg using (userId)
group by
ud.userId
`
const sqlUserGroupInfo = `
select
ug.userGroupId,
ug.name,
count(distinct ugum.userId) as members,
ug.createdDate as created,
ug.modifiedDate,
json_object(
"restricted", count(distinct case when cg.roleId = 1 then cg.collectionId else null end),
"full", count(distinct case when cg.roleId = 2 then cg.collectionId else null end),
"manage", count(distinct case when cg.roleId = 3 then cg.collectionId else null end),
"owner", count(distinct case when cg.roleId = 4 then cg.collectionId else null end)
) as roles
from
user_group ug
left join collection_grant cg on cg.userGroupId = ug.userGroupId
left join user_group_user_map ugum ON ugum.userGroupId = ug.userGroupId
group by
ug.userGroupId
`
const sqlMySqlVersion = `SELECT VERSION() as version`
const mySqlVariablesOnly = [
'innodb_buffer_pool_size',
'innodb_buffer_pool_instances',
'innodb_log_buffer_size',
'innodb_log_file_size',
'innodb_redo_log_capacity',
'innodb_io_capacity',
'innodb_io_capacity_max',
'innodb_flush_sync',
'innodb_lock_wait_timeout',
'innodb_change_buffering',
'innodb_flush_log_at_trx_commit',
'innodb_doublewrite',
'tmp_table_size',
'max_heap_table_size',
'temptable_max_mmap',
'temptable_max_ram',
'key_buffer_size',
'sort_buffer_size',
'read_buffer_size',
'read_rnd_buffer_size',
'join_buffer_size',
'binlog_cache_size',
'max_connections',
'max_allowed_packet',
'thread_cache_size',
'table_open_cache',
'table_definition_cache',
'version',
'version_compile_machine',
'version_compile_os',
'long_query_time'
]
const sqlMySqlVariablesValues = `
SELECT
variable_name,
variable_value as value
FROM
performance_schema.global_variables
WHERE
variable_name IN (${mySqlVariablesOnly.map(v => `'${v}'`).join(',')})
ORDER by variable_name
`
const mySqlStatusOnly = [
// Network
'Bytes_received',
'Bytes_sent',
// Handler operations
'Handler_commit',
'Handler_update',
'Handler_write',
// Buffer pool health (performance monitoring)
'Innodb_buffer_pool_bytes_data',
'Innodb_buffer_pool_pages_total',
'Innodb_buffer_pool_pages_free',
'Innodb_buffer_pool_pages_dirty',
'Innodb_buffer_pool_pages_flushed',
'Innodb_buffer_pool_read_requests',
'Innodb_buffer_pool_reads',
'Innodb_buffer_pool_wait_free',
// Redo log / Checkpoint (detect checkpoint thrashing)
'Innodb_redo_log_current_lsn',
'Innodb_redo_log_checkpoint_lsn',
'Innodb_redo_log_flushed_to_disk_lsn',
'Innodb_log_waits',
'Innodb_log_writes',
'Innodb_os_log_fsyncs',
// I/O operations
'Innodb_data_reads',
'Innodb_data_writes',
'Innodb_data_fsyncs',
'Innodb_pages_read',
'Innodb_pages_written',
'Innodb_pages_created',
// Row operations
'Innodb_rows_read',
'Innodb_rows_updated',
'Innodb_rows_inserted',
'Innodb_rows_deleted',
// Row locking
'Innodb_row_lock_waits',
'Innodb_row_lock_current_waits',
'Innodb_row_lock_time',
'Innodb_row_lock_time_avg',
'Innodb_row_lock_time_max',
// Temp tables
'Created_tmp_tables',
'Created_tmp_disk_tables',
'Created_tmp_files',
// Table cache
'Open_tables',
'Opened_tables',
'Table_open_cache_hits',
'Table_open_cache_misses',
'Table_open_cache_overflows',
// Connections/Threads
'Connections',
'Max_used_connections',
'Threads_connected',
'Threads_running',
'Threads_created',
'Threads_cached',
'Aborted_connects',
'Aborted_clients',
// Queries
'Queries',
'Slow_queries',
'Select_scan',
'Select_full_join',
'Select_full_range_join',
// Sorts
'Sort_merge_passes',
'Sort_scan',
'Sort_range',
'Sort_rows',
// Table locks
'Table_locks_immediate',
'Table_locks_waited',
// Server
'Uptime',
'Uptime_since_flush_status'
]
const sqlMySqlStatusValues = `
SELECT
variable_name,
variable_value as value
FROM
performance_schema.global_status
WHERE
variable_name IN (
${mySqlStatusOnly.map( v => `'${v}'`).join(',')}
)
ORDER by variable_name
`
await dbUtils.pool.query(sqlAnalyze)
const [schemaInfoArray] = await dbUtils.pool.query(sqlInfoSchema, [config.database.schema])
const tables = createObjectFromKeyValue(schemaInfoArray, "tableName")
const queries = [
dbUtils.pool.query(sqlCollectionAssetStigs),
dbUtils.pool.query(sqlCountsByCollection),
dbUtils.pool.query(sqlLabelCountsByCollection),
dbUtils.pool.query(sqlGrantsByCollection),
dbUtils.pool.query(sqlRoleCountsByCollection),
dbUtils.pool.query(sqlUserInfo),
dbUtils.pool.query(sqlUserGroupInfo),
dbUtils.pool.query(sqlMySqlVersion),
dbUtils.pool.query(sqlMySqlVariablesValues),
dbUtils.pool.query(sqlMySqlStatusValues)
]
// Conditionally add row count queries
if (includeRowCounts) {
const rowCountQueries = []
for (const table in tables) {
rowCountQueries.push(dbUtils.pool.query(`SELECT "${table}" as tableName, count(*) as rowCount from ${table}`))
}
queries.push(Promise.all(rowCountQueries))
}
const results = await Promise.all(queries)
let [
[assetStigByCollection],
[countsByCollection],
[labelCountsByCollection],
[grantsByCollection],
[roleCountsByCollection],
[userInfo],
[userGroupInfo],
[mySqlVersion],
[mySqlVariables],
[mySqlStatus],
rowCountResults
] = results
// Set row counts from individual queries or use null when not counting
if (includeRowCounts) {
for (const result of rowCountResults) {
tables[result[0][0].tableName].rowCount = result[0][0].rowCount
}
} else {
// Use null to indicate exact row counts were not requested
for (const tableName in tables) {
tables[tableName].rowCount = null
}
}
// remove strings from user privileges array that are not meaningful to stigman
const stigmanPrivs = ['admin', 'create_collection']
for (const user of userInfo ) {
user.privileges = user.privileges.filter(v => stigmanPrivs.includes(v))
}
//count privilege assignments and break out by lastAccess time periods
const userPrivilegeCounts = breakOutPrivilegeUsage(userInfo)
//create working copy of operational stats
const requests = klona(logger.requestStats)
requests.operationIds = sortObjectByKeys(requests.operationIds)
// Create objects keyed by collectionId from arrays of objects
countsByCollection = createObjectFromKeyValue(countsByCollection, "collectionId")
labelCountsByCollection = createObjectFromKeyValue(labelCountsByCollection, "collectionId")
assetStigByCollection = createObjectFromKeyValue(assetStigByCollection, "collectionId")
grantsByCollection = createObjectFromKeyValue(grantsByCollection, "collectionId")
roleCountsByCollection = createObjectFromKeyValue(roleCountsByCollection, "collectionId")
// Bundle "byCollection" stats together by collectionId
for(const collectionId in countsByCollection) {
if (assetStigByCollection[collectionId]) {
countsByCollection[collectionId].assetStigRanges = assetStigByCollection[collectionId]
}
if (grantsByCollection[collectionId]) {
const grants = {}
// For each ACL in the collection's array of ACLs
for (const grant of grantsByCollection[collectionId].grants) {
grants[grant.grantId] = grant
delete grant.grantId
}
countsByCollection[collectionId].grants = grants
}
else {
countsByCollection[collectionId].grants = {}
}
if (roleCountsByCollection[collectionId]) {
countsByCollection[collectionId].roleCounts = roleCountsByCollection[collectionId]
}
else {
countsByCollection[collectionId].roleCounts = {
restricted: 0,
full: 0,
manage: 0,
owner: 0
}
}
if (labelCountsByCollection[collectionId]) {
countsByCollection[collectionId].labelCounts = labelCountsByCollection[collectionId]
}
}
const returnObj = {
date: new Date().toISOString(),
schema,
version: config.version,
collections: countsByCollection,
requests,
users: {
userInfo: createObjectFromKeyValue(userInfo, "userId", null),
userPrivilegeCounts
},
groups: createObjectFromKeyValue(userGroupInfo, "userGroupId", null),
mysql: {
version: mySqlVersion[0].version,
tables,
variables: createObjectFromKeyValue(mySqlVariables, "variable_name", "value"),
status: createObjectFromKeyValue(mySqlStatus, "variable_name", "value")
},
nodejs: getNodeValues()
}
return returnObj
// Reduce an array of objects to a single object, using the value of one property as keys
// and either assigning the rest of the object or the value of a second property as the value.
function createObjectFromKeyValue(data, keyPropertyName, valuePropertyName = null, includeKey = false) {
return data.reduce((acc, item) => {
const { [keyPropertyName]: key, ...rest } = item
acc[key] = valuePropertyName ? item[valuePropertyName] : includeKey ? item : rest
return acc
}, {})
}
function sortObjectByKeys(obj) {
// Create a new object and add properties in sorted order
const sortedObj = {}
for (const key of Object.keys(obj).sort()) {
sortedObj[key] = obj[key]
}
return sortedObj
}
function breakOutPrivilegeUsage(userInfo) {
let privilegeCounts = {
overall: {none:0},
activeInLast30Days: {none:0},
activeInLast90Days: {none:0}
}
// Calculate the timestamps for 30 and 90 days ago
const currentTime = Math.floor(Date.now() / 1000)
const thirtyDaysAgo = currentTime - (30 * 24 * 60 * 60)
const ninetyDaysAgo = currentTime - (90 * 24 * 60 * 60)
const updateCounts = (categoryCounts, userPrivs) => {
if (userPrivs.length === 0) {
categoryCounts.none++
}
for (const privilege of userPrivs) {
categoryCounts[privilege] = categoryCounts[privilege] ? categoryCounts[privilege] + 1 : 1
}
}
for (const user of userInfo) {
updateCounts(privilegeCounts.overall, user.privileges)
// Update counts for the last 30 and 90 days based on lastAccess
if (user.lastAccess >= ninetyDaysAgo) {
updateCounts(privilegeCounts.activeInLast90Days, user.privileges)
}
if (user.lastAccess >= thirtyDaysAgo) {
updateCounts(privilegeCounts.activeInLast30Days, user.privileges)
}
}
return privilegeCounts
}
function getNodeValues() {
const {environmentVariables, header, resourceUsage} = process.report.getReport()
const environment = {}
for (const [key, value] of Object.entries(environmentVariables)) {
if (/^(NODE|STIGMAN)_/.test(key)) {
environment[key] = key === 'STIGMAN_DB_PASSWORD' ? '***' : value
}
}
const {platform, arch, nodejsVersion, cpus, osMachine, osName, osRelease} = header
for (let x = 0; x < cpus.length; x++) {
cpus[x] = {model: cpus[x].model, speed: cpus[x].speed}
}
const loadAverage = os.loadavg().join(', ')
const memory = process.memoryUsage()
memory.maxRss = resourceUsage.maxRss
return {
version: nodejsVersion.substring(1),
uptime: process.uptime(),
os: {
platform,
arch,
osMachine,
osName,
osRelease,
loadAverage
},
environment,
memory,
cpus
}
}
}
================================================
FILE: api/source/service/ReviewService.js
================================================
'use strict';
const dbUtils = require('./utils')
let _this = this
exports.postReviewBatch = async function ({
source,
assets,
rules,
action,
updateFilters,
dryRun,
collectionId,
userId,
grant,
svcStatus,
historyMaxReviews,
skipGrantCheck = false
}) {
function cteReviewGen(obj) {
const cte = `SELECT
jtresult.resultId,
TRIM(jt.detail) as detail,
TRIM(jt.comment) as comment,
jt.resultEngine,
jt.metadata,
jtstatus.statusId,
jt.statusText
FROM
JSON_TABLE(
@review,
"$"
COLUMNS(
result VARCHAR(255) PATH "$.result",
detail MEDIUMTEXT PATH "$.detail" NULL ON EMPTY,
comment MEDIUMTEXT PATH "$.comment",
resultEngine JSON PATH "$.resultEngine" DEFAULT '0' ON EMPTY,
metadata JSON PATH "$.metadata",
statusLabel VARCHAR(255) PATH "$.status.label",
statusText VARCHAR(511) PATH "$.status.text"
)
) as jt
left join result jtresult on (jtresult.api = jt.result)
left join status jtstatus on (jtstatus.api = jt.statusLabel)`
return `cteReview AS (${cte})`
}
function cteAssetGen({assetIds = [], benchmarkIds = []}, roleId) {
let cte
if (assetIds?.length) {
const json = JSON.stringify(assetIds)
const sql = `select jtAssets.assetId
from
json_table(
?,
'$[*]'
COLUMNS (assetId INT PATH '$')
) as jtAssets`
cte = dbUtils.pool.format(sql,[json])
}
else if (benchmarkIds?.length) {
const sql = `select distinct assetId
from
enabled_asset a
left join stig_asset_map sa using (assetId)
${roleId === 1 ? 'inner' : 'left'} join cteAclEffective cae on sa.saId = cae.saId
where
a.collectionId = @collectionId
and coalesce(cae.access, 'rw') = 'rw'
and sa.benchmarkId IN ?`
cte = dbUtils.pool.format(sql,[[benchmarkIds]])
}
return `cteAsset AS (${cte})`
}
function cteRuleGen({ruleIds, benchmarkIds, collectionId}) {
let cte
if (ruleIds?.length) {
const json = JSON.stringify(ruleIds)
const sql = `select jtRules.ruleId
from
json_table(
?,
'$[*]'
COLUMNS (ruleId VARCHAR(255) PATH '$')
) as jtRules`
cte = dbUtils.pool.format(sql,[json])
}
else if (benchmarkIds?.length) {
const sql = `select rgr.ruleId from default_rev dr left join rev_group_rule_map rgr using (revId) where dr.benchmarkId IN ? and dr.collectionId = ?`
cte = dbUtils.pool.format(sql,[[benchmarkIds], collectionId])
}
return `cteRule AS (${cte})`
}
function cteGrantGen(roleId) {
const cte = `select
distinct a.assetId,
rgr.ruleId
from
enabled_asset a
left join stig_asset_map sa using (assetId)
${roleId === 1 ? 'inner' : 'left'} join cteAclEffective cae on sa.saId = cae.saId
left join revision rev on sa.benchmarkId = rev.benchmarkId
left join rev_group_rule_map rgr using (revId)
where
a.assetId IN (select assetId from cteAsset)
and rgr.ruleId IN (select ruleId from cteRule)
and coalesce(cae.access, 'rw') = 'rw'`
return `cteGrant AS (${cte})`
}
function cteCollectionSettingGen () {
const cte = `SELECT
c.settings->>"$.fields.detail.required" as detailRequired,
c.settings->>"$.fields.comment.required" as commentRequired,
c.settings->>"$.status.canAccept" as canAccept,
c.settings->>"$.status.resetCriteria" as resetCriteria,
c.settings->>"$.status.minAcceptGrant" as minAcceptGrant
FROM
enabled_collection c
where
collectionId = @collectionId`
return `cteCollectionSetting AS (${cte})`
}
const mergeFilterOperators = {
contains: 'LIKE',
beginsWith: 'LIKE',
endsWith: 'LIKE',
equals: '=',
notequal: '!=',
greaterThan: '>',
lessThan: '<',
}
function genFilter(filter) {
let {field, condition = 'equals', value} = filter
if (field === 'result') {
field = 'resultId'
value = dbUtils.REVIEW_RESULT_API[value]
}
if (field === 'status' || field === 'statusLabel') {
field = 'statusId'
value = dbUtils.REVIEW_STATUS_API[value]
}
value = field === 'userId' || field === 'statusUserId' ? parseInt(value) : value
const sqlOperator = mergeFilterOperators[condition]
const isDateValue = (field === 'ts' || field === 'touchTs' || field === 'statusTs')
let sqlValue
if (isDateValue) {
sqlValue = dbUtils.pool.escape(new Date(value))
}
else if (condition === 'contains') {
sqlValue = dbUtils.pool.escape(`%${value}%`)
}
else if (condition === 'beginsWith') {
sqlValue = dbUtils.pool.escape(`${value}%`)
}
else if (condition === 'endsWith') {
sqlValue = dbUtils.pool.escape(`%${value}`)
}
else {
sqlValue = dbUtils.pool.escape(value)
}
return `review.${field} ${sqlOperator} ${sqlValue}`
}
function cteCandidateGen ({skipGrantCheck = false, action, updateFilters}) {
let sqlFilterPredicates, sqlPredicates
if (updateFilters) {
sqlFilterPredicates = updateFilters.map( filter => genFilter(filter)).join(' AND ')
}
if (action === 'insert') {
sqlPredicates = `review.reviewId is null`
}
else if (action === 'update') {
sqlPredicates = sqlFilterPredicates || 'review.reviewId is not null'
}
else if (action === 'merge') {
sqlPredicates = `${sqlFilterPredicates ? `review.reviewId is null OR (${sqlFilterPredicates})` : ''}`
}
const cte = `
select
${!skipGrantCheck ? 'CASE WHEN cteGrant.assetId is not null then 1 else null end' : '1'} as granted,
review.reviewId,
cteAsset.assetId,
cteRule.ruleId,
rvcd.version,
rvcd.checkDigest,
COALESCE(cteReview.resultId, review.resultId) as resultId,
COALESCE(cteReview.detail, review.detail, '') as detail,
COALESCE(cteReview.comment, review.comment, '') as comment,
COALESCE(cteReview.metadata, review.metadata, '{}') as metadata,
CASE WHEN cteReview.resultEngine != 0 -- resultEngine present
THEN cteReview.resultEngine
ELSE
CASE WHEN cteReview.resultId is null or cteReview.resultId = review.resultId
THEN review.resultEngine
ELSE NULL
END
END as resultEngine,
CASE WHEN cteReview.statusId is not null
THEN cteReview.statusId
ELSE
CASE WHEN review.reviewId is null
or (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null)
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null)
THEN 0
ELSE review.statusId
END
END as statusId,
CASE WHEN cteReview.statusId is not null or review.reviewId is null
THEN cteReview.statusText
ELSE
CASE WHEN (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null)
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null)
THEN 'Review change triggered status update'
ELSE review.statusText
END
END as statusText,
CASE WHEN cteReview.statusId is not null
or review.reviewId is null
or (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null)
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null)
THEN UTC_TIMESTAMP()
ELSE review.statusTs
END as statusTs,
CASE WHEN cteReview.statusId is not null
or review.reviewId is null
or (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null)
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null)
THEN @userId
ELSE review.statusUserId
END as statusUserId,
CASE WHEN cteReview.resultId is not null
or cteReview.detail is not null
or cteReview.comment is not null
or review.reviewId is null
THEN @userId
ELSE review.userId
END as userId,
CASE WHEN cteReview.resultId is not null
or cteReview.detail is not null
or cteReview.comment is not null
or review.reviewId is null
THEN UTC_TIMESTAMP()
ELSE review.ts
END as ts
from
cteAsset
CROSS JOIN cteRule
LEFT JOIN cteReview on true
${!skipGrantCheck ? 'LEFT JOIN cteGrant on (cteAsset.assetId = cteGrant.assetId and cteRule.ruleId = cteGrant.ruleId)' : ''}
LEFT JOIN rule_version_check_digest rvcd on cteRule.ruleId = rvcd.ruleId
LEFT JOIN review on (cteAsset.assetId = review.assetId and rvcd.version = review.version and rvcd.checkDigest = review.checkDigest)
LEFT JOIN cteCollectionSetting on true
LEFT JOIN review rChangedResult on (
rChangedResult.reviewId = review.reviewId
and rChangedResult.statusId != 0
and rChangedResult.resultId != cteReview.resultId
)
LEFT JOIN review rChangedAny on (
rChangedAny.reviewId = review.reviewId
and rChangedAny.statusId != 0
and (rChangedAny.resultId != cteReview.resultId or rChangedAny.detail != cteReview.detail or rChangedAny.comment != cteReview.comment)
)
${sqlPredicates ? `WHERE ${sqlPredicates}` : ''}
`
return `cteCandidate AS (${cte})`
}
const cteReview = cteReviewGen()
const cteAsset = cteAssetGen(assets, grant.roleId)
if (rules.benchmarkIds) {
rules.collectionId = collectionId
}
const cteRule = cteRuleGen(rules)
let cteGrant
if (!skipGrantCheck) {
cteGrant = cteGrantGen(grant.roleId)
}
const cteCollectionSetting = cteCollectionSettingGen()
const cteCandidate = cteCandidateGen({skipGrantCheck, action, updateFilters})
const cteAclEffective = dbUtils.cteAclEffective({grantIds: grant.grantIds})
const sqlTempTable = `
CREATE TEMPORARY TABLE IF NOT EXISTS validated_reviews (
INDEX idx_reviewId (reviewId),
INDEX id_error (error)
)
WITH
${cteAclEffective},
${cteReview},
${cteAsset},
${cteRule},
${!skipGrantCheck ? `${cteGrant},` : ''}
${cteCollectionSetting},
${cteCandidate}
select
cteCandidate.reviewId,
cteCandidate.assetId,
cteCandidate.ruleId,
cteCandidate.version,
cteCandidate.checkDigest,
cteCandidate.resultId,
cteCandidate.detail,
cteCandidate.comment,
cteCandidate.resultEngine,
cteCandidate.metadata,
cteCandidate.statusId,
cteCandidate.statusText,
cteCandidate.statusUserId,
cteCandidate.statusTs,
cteCandidate.userId,
cteCandidate.ts,
CASE WHEN cteCandidate.granted IS NULL
THEN
'no grant for this asset/ruleId'
ELSE
CASE WHEN (cteCandidate.reviewId IS NULL AND cteCandidate.resultId IS NULL)
THEN
'cannot insert null result'
ELSE
CASE WHEN cteCandidate.statusId > 0 -- submitted, rejected, accepted
THEN
CASE WHEN (cteCandidate.resultId NOT IN (2,3,4))
THEN
'status is not allowed for the result'
ELSE
CASE WHEN (cteCollectionSetting.detailRequired = 'always' AND cteCandidate.detail = '')
THEN
'detail is empty and detail.required = always'
ELSE
CASE WHEN (cteCollectionSetting.commentRequired = 'always' AND cteCandidate.comment = '')
THEN
'comment is empty and comment.required = always'
ELSE
CASE WHEN cteCandidate.resultId = 4 -- fail
THEN
CASE WHEN (cteCollectionSetting.detailRequired = 'findings' AND cteCandidate.detail = '')
THEN
'detail is empty and detail.required = findings'
ELSE
CASE WHEN (cteCollectionSetting.commentRequired = 'findings' AND cteCandidate.comment = '')
THEN
'comment is empty and comment.required = findings '
END
END
END
END
END
END
END
END
END as error
from
cteCandidate
LEFT JOIN cteCollectionSetting on true`
const sqlHistoryPrune = `
with historyRecs AS (
select
rh.historyId,
ROW_NUMBER() OVER (PARTITION BY r.assetId, r.version, r.checkDigest ORDER BY rh.historyId DESC) as rowNum
from
review_history rh
left join review r using (reviewId)
where
reviewId IN (SELECT reviewId from validated_reviews where error is null and reviewId is not null)
)
delete review_history
FROM
review_history
left join historyRecs on review_history.historyId = historyRecs.historyId
WHERE
historyRecs.rowNum > ? - 1
`
const sqlHistory = `
INSERT INTO review_history (
reviewId,
ruleId,
resultId,
detail,
comment,
autoResult,
ts,
userId,
statusText,
statusUserId,
statusTs,
statusId,
touchTs,
resultEngine
) SELECT
reviewId,
ruleId,
resultId,
LEFT(detail,32767) as detail,
LEFT(comment,32767) as comment,
autoResult,
ts,
userId,
statusText,
statusUserId,
statusTs,
statusId,
touchTs,
CASE WHEN resultEngine = 0 THEN NULL ELSE resultEngine END
FROM
review
WHERE
reviewId IN (SELECT reviewId from validated_reviews where error is null and reviewId is not null)
FOR UPDATE
`
const sqlInsertReviews = `
insert into review (
assetId,
ruleId,
\`version\`,
checkDigest,
resultId,
resultEngine,
detail,
comment,
metadata,
statusId,
statusText,
statusUserId,
statusTs,
userId,
ts)
select
assetId,
ruleId,
\`version\`,
checkDigest,
resultId,
resultEngine,
detail,
comment,
metadata,
statusId,
statusText,
statusUserId,
statusTs,
userId,
ts
from
validated_reviews vr
where
error is null and reviewId is null
`
const sqlUpdateReviews = `
update
review r
inner join validated_reviews vr on (r.reviewId = vr.reviewId and vr.error is null)
set
r.resultId = vr.resultId,
r.resultEngine = vr.resultEngine,
r.detail = vr.detail,
r.comment = vr.comment,
r.metadata = vr.metadata,
r.statusId = vr.statusId,
r.statusText = vr.statusText,
r.statusUserId = vr.statusUserId,
r.statusTs = vr.statusTs,
r.userId = vr.userId,
r.ts = vr.ts
`
let connection
try {
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = false
const sqlVariables = `set @collectionId = ?, @userId = ?, @review = ?`
await connection.query(sqlVariables, [parseInt(collectionId), parseInt(userId), JSON.stringify(source.review)])
await connection.query(sqlTempTable)
let validationErrors = []
let [counts] = await connection.query(`select
coalesce(sum(case when error is not null then 1 else 0 end),0) as failedValidations,
coalesce(sum(case when error is null and reviewId is null then 1 else 0 end),0) as inserts,
coalesce(sum(case when error is null and reviewId is not null then 1 else 0 end),0) as updates
from validated_reviews`)
if (counts[0].failedValidations) {
;[validationErrors] = await connection.query('select CAST(assetId AS CHAR) as assetId, ruleId, error from validated_reviews where error is not null LIMIT 50')
}
async function transaction () {
await connection.query('START TRANSACTION')
if (counts[0].updates) {
await connection.query(sqlHistoryPrune, [ historyMaxReviews ])
if (historyMaxReviews !== 0) {
await connection.query(sqlHistory)
}
await connection.query(sqlUpdateReviews)
}
if (counts[0].inserts) {
await connection.query(sqlInsertReviews)
}
const statsParams = {
collectionId
}
if (assets.assetIds) {
statsParams.assetIds = assets.assetIds
}
else if (assets.benchmarkIds) {
statsParams.assetBenchmarkIds = assets.benchmarkIds
}
if (rules.ruleIds) {
statsParams.rules = rules.ruleIds
}
else if (rules.benchmarkIds) {
statsParams.benchmarkIds = rules.benchmarkIds
}
await dbUtils.updateStatsAssetStig(connection, statsParams)
await connection.commit()
}
if (!dryRun) {
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
if (dryRun) {
return {willInsert: counts[0].inserts, willUpdate: counts[0].updates, willFailValidation: counts[0].failedValidations, validationErrors}
}
return {inserted: counts[0].inserts, updated: counts[0].updates, failedValidation: counts[0].failedValidations, validationErrors}
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw (err) ;
}
finally {
if (typeof connection !== 'undefined') {
await connection.query('DROP TEMPORARY TABLE IF EXISTS validated_reviews')
await connection.release()
}
}
}
/**
Generalized queries for review(s).
**/
exports.getReviews = async function ({projections = [], filter = {}, grant}) {
const ctes = [dbUtils.cteAclEffective({grantIds: grant.grantIds})]
const hints = ['NO_MERGE(cae)']
const columns = [
'CAST(r.assetId as char) as assetId',
'a.name as "assetName"',
`coalesce(
(select
json_arrayagg(BIN_TO_UUID(cl.uuid,1))
from
collection_label_asset_map cla
left join collection_label cl on cla.clId = cl.clId
where
cla.assetId = r.assetId),
json_array()
) as assetLabelIds`,
`coalesce(
(select
json_arrayagg(json_object(
'labelId', BIN_TO_UUID(cl.uuid,1),
'name', cl.name,
'color', cl.color
))
from
collection_label_asset_map cla
left join collection_label cl on cla.clId = cl.clId
where
cla.assetId = r.assetId),
json_array()
) as assetLabels`,
'r.ruleId',
`coalesce(cast(concat('[', group_concat(distinct concat('"',rvcd2.ruleId,'"')), ']') as json), json_array()) as ruleIds`,
'result.api as "result"',
'CASE WHEN r.resultEngine = 0 THEN NULL ELSE r.resultEngine END as resultEngine',
"COALESCE(LEFT(r.detail,32767),'') as detail",
"COALESCE(LEFT(r.comment,32767),'') as comment",
'r.autoResult',
'CAST(r.userId as char) as userId',
'ud.username',
"DATE_FORMAT(r.ts, '%Y-%m-%dT%H:%i:%sZ') as ts",
"DATE_FORMAT(r.touchTs, '%Y-%m-%dT%H:%i:%sZ') as touchTs",
`JSON_OBJECT(
'label', status.api,
'text', r.statusText,
'user', JSON_OBJECT(
'userId', CAST(r.statusUserId as char),
'username', udStatus.username
),
'ts', DATE_FORMAT(r.statusTs, '%Y-%m-%dT%TZ')
) as status`
]
const groupBy = [
'r.reviewId',
'a.name',
'result.api',
'status.api',
'ud.username',
'udStatus.username',
]
const joins = [
'review r',
'left join rule_version_check_digest rvcd on (r.version = rvcd.version and r.checkDigest = rvcd.checkDigest)',
'left join rule_version_check_digest rvcd2 on (r.version = rvcd2.version and r.checkDigest = rvcd2.checkDigest)',
'left join rev_group_rule_map rgr on rvcd.ruleId = rgr.ruleId',
'left join revision on rgr.revId = revision.revId',
'left join result on r.resultId = result.resultId',
'left join status on r.statusId = status.statusId',
'left join user_data ud on r.userId = ud.userId',
'left join user_data udStatus on r.statusUserId = udStatus.userId',
'left join enabled_asset a on r.assetId = a.assetId',
'left join default_rev dr on (rgr.revId = dr.revId and a.collectionId = dr.collectionId)',
'left join enabled_collection c on a.collectionId = c.collectionId',
'left join stig_asset_map sa on (r.assetId = sa.assetId and revision.benchmarkId = sa.benchmarkId)',
]
if (grant.roleId === 1) {
joins.push('inner join cteAclEffective cae on sa.saId = cae.saId')
// newman tests will fail if we add the new column
columns.push('min(cae.access) as access')
}
else {
joins.push('left join cteAclEffective cae on sa.saId = cae.saId')
// newman tests will fail if we add the new column
columns.push("coalesce(min(cae.access), 'rw') as access")
}
if (projections.includes('metadata')) {
columns.push(`r.metadata`)
groupBy.push(`r.metadata`)
}
if (projections.includes('stigs')) {
columns.push(`cast(
concat('[',
coalesce (
group_concat(distinct
case when sa.benchmarkId is not null then
json_object(
'benchmarkId', sa.benchmarkId,
'revisionStr', revision.revisionStr,
'benchmarkDate', date_format(revision.benchmarkDateSql,'%Y-%m-%d'),
'revisionPinned', CASE WHEN dr.revisionPinned = 1 THEN CAST(true as json) ELSE CAST(false as json) END,
'isDefault', case when revision.revId = dr.revId then cast(true as json) else cast(false as json) end,
'ruleCount', revision.ruleCount)
else null end
order by sa.benchmarkId),
''),
']')
as json) as "stigs"`)
}
if (projections.includes('rule')) {
columns.push(`json_object(
'ruleId' , rgr.ruleId,
'title' , rgr.title,
'version' , rgr.version,
'severity' , rgr.severity) as "rule"`
)
groupBy.push('rgr.severity','rgr.title','rgr.version','rgr.ruleId')
}
if (projections.includes('history')) {
// OVER clauses and subquery needed to order the json_arrayagg
columns.push(`
(select
coalesce(
(select json_arrayagg(
json_object(
'ts' , DATE_FORMAT(rh.ts, '%Y-%m-%dT%H:%i:%sZ'),
'ruleId', rh.ruleId,
'result', result.api,
'resultEngine', CASE WHEN rh.resultEngine = 0 THEN NULL ELSE rh.resultEngine END,
'detail', COALESCE(LEFT(rh.detail,32767),''),
'comment', COALESCE(LEFT(rh.comment,32767),''),
'autoResult', cast(rh.autoResult is true as json),
'userId', CAST(rh.userId as char),
'username', ud.username,
'status', JSON_OBJECT(
'label', status.api,
'text', rh.statusText,
'user', JSON_OBJECT(
'userId', CAST(rh.statusUserId as char),
'username', udStatus.username
),
'ts', DATE_FORMAT(rh.statusTs, '%Y-%m-%dT%TZ')
),
'touchTs', DATE_FORMAT(rh.touchTs, '%Y-%m-%dT%TZ')
)
)
FROM
review_history rh
left join result on rh.resultId = result.resultId
left join status on rh.statusId = status.statusId
left join user_data ud on ud.userId=rh.userId
left join user_data udStatus on udStatus.userId=rh.statusUserId
where
rh.reviewId = r.reviewId),
json_array()
)
) as "history"`)
}
const predicates = {
statements: [],
binds: []
}
switch (filter.rules) {
case 'default-mapped':
predicates.statements.push(`dr.revId IS NOT NULL`)
predicates.statements.push(`sa.saId IS NOT NULL`)
break
case 'default':
predicates.statements.push(`dr.revId IS NOT NULL`)
break
case 'not-default-mapped':
predicates.statements.push(`dr.revId IS NULL`)
predicates.statements.push(`sa.saId IS NULL`)
break
case 'not-default':
predicates.statements.push(`dr.revId IS NULL`)
break
case 'not-mapped':
predicates.statements.push(`sa.saId IS NULL`)
break
case 'mapped':
predicates.statements.push(`sa.saId IS NOT NULL`)
break
}
if (filter.collectionId) {
predicates.statements.push('a.collectionId = ?')
predicates.binds.push(filter.collectionId)
}
if (filter.result) {
predicates.statements.push('result.api = ?')
predicates.binds.push(filter.result)
}
if (filter.status) {
predicates.statements.push('status.api = ?')
predicates.binds.push(filter.status)
}
if (filter.ruleId) {
predicates.statements.push('rvcd.ruleId = ?')
predicates.binds.push(filter.ruleId)
}
if (filter.groupId) {
predicates.statements.push(`rgr.groupId = ?`)
predicates.binds.push(filter.groupId)
}
if (filter.cci) {
predicates.statements.push(`rvcd.ruleId IN (
SELECT
distinct rgr.ruleId
FROM
rev_group_rule_cci_map rgrcc
left join rev_group_rule_map rgr using (rgrId)
WHERE
rgrcc.cci = ?
)` )
predicates.binds.push(filter.cci)
}
if (filter.userId) {
predicates.statements.push('r.userId = ?')
predicates.binds.push(filter.userId)
}
if (filter.assetId) {
predicates.statements.push('r.assetId = ?')
predicates.binds.push(filter.assetId)
}
if (filter.benchmarkId) {
predicates.statements.push(`revision.benchmarkId = ?`)
predicates.binds.push(filter.benchmarkId)
}
if ( filter.metadata ) {
for (const pair of filter.metadata) {
const [key, value] = pair.split(/:(.*)/s)
predicates.statements.push('JSON_CONTAINS(r.metadata, ?, ?)')
predicates.binds.push( `"${value}"`, `$.${key}`)
}
}
const sql = dbUtils.makeQueryString({ctes, hints, columns, joins, predicates, groupBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.exportReviews = async function (includeHistory = false) {
const columns = [
'CAST(r.assetId as char) as assetId',
'r.ruleId',
'result.api as "result"',
'CASE WHEN r.resultEngine = 0 THEN NULL ELSE r.resultEngine END as resultEngine',
'LEFT(r.detail,32767) as detail',
'LEFT(r.comment,32767) as comment',
'CAST(r.userId as char) as userId',
"DATE_FORMAT(r.ts, '%Y-%m-%dT%H:%i:%sZ') as ts",
"DATE_FORMAT(r.touchTs, '%Y-%m-%dT%H:%i:%sZ') as touchTs",
`JSON_OBJECT(
'label', status.api,
'text', r.statusText,
'userId', CAST(r.statusUserId as char),
'ts', DATE_FORMAT(r.statusTs, '%Y-%m-%dT%TZ')
) as status`,
'r.metadata'
]
const joins = [
'review r',
'inner join enabled_asset a on r.assetId = a.assetId',
'inner join enabled_collection c on c.collectionId = a.collectionId',
'left join result on r.resultId = result.resultId',
'left join status on r.statusId = status.statusId',
]
let groupBy
if (includeHistory) {
columns.push(`
(select
coalesce(
(select json_arrayagg(
json_object(
'ts' , DATE_FORMAT(rh.ts, '%Y-%m-%dT%H:%i:%sZ'),
'ruleId', rh.ruleId,
'result', result.api,
'resultEngine', CASE WHEN rh.resultEngine = 0 THEN NULL ELSE rh.resultEngine END,
'detail', LEFT(rh.detail,32767),
'comment', LEFT(rh.comment,32767),
'userId', CAST(rh.userId as char),
'status', JSON_OBJECT(
'label', status.api,
'text', rh.statusText,
'userId', CAST(rh.statusUserId as char),
'ts', DATE_FORMAT(rh.statusTs, '%Y-%m-%dT%TZ')
),
'touchTs', DATE_FORMAT(rh.touchTs, '%Y-%m-%dT%TZ')
)
)
FROM
review_history rh
left join result on rh.resultId = result.resultId
left join status on rh.statusId = status.statusId
where
rh.reviewId = r.reviewId),
json_array()
)
) as "history"`)
groupBy = [
'r.assetId',
'r.ruleId',
'r.resultId',
'result.api',
'r.resultEngine',
'r.detail',
'r.comment',
'status.api',
'r.userId',
'r.ts',
'r.statusText',
'r.statusUserId',
'r.statusTs',
'r.metadata',
'r.reviewId',
]
}
const sql = dbUtils.makeQueryString({columns, joins, groupBy})
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
/**
* Delete a Review
*
* reviewId Integer A path parameter that indentifies a Review
* projection List Additional properties to include in the response. (optional)
* returns ReviewProjected
**/
exports.deleteReviewByAssetRule = async function({assetId, ruleId, projections, grant, svcStatus = {}}) {
let connection
try {
let binds = {
assetId,
ruleId
}
let rows = await _this.getReviews({projections, filter: binds, grant})
binds = [assetId, ruleId]
connection = await dbUtils.pool.getConnection()
async function transaction () {
await connection.query('START TRANSACTION')
let sqlDelete = `DELETE review
FROM review
LEFT JOIN rule_version_check_digest rvcd
ON (rvcd.version = review.version and rvcd.checkDigest = review.checkDigest)
WHERE review.assetId = ? AND rvcd.ruleId = ?`
await connection.query(sqlDelete, binds)
await dbUtils.updateStatsAssetStig( connection, {ruleId, assetId})
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return (rows[0])
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw (err) ;
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
exports.putReviewsByAsset = async function ({
collectionId,
assetId,
reviews,
userId,
grant,
svcStatus
}) {
let connection
const sqlCreateTableValidatedReview = `
CREATE TEMPORARY TABLE IF NOT EXISTS tt_validated_review (
INDEX idx_reviewId (reviewId),
INDEX idx_error (error),
PRIMARY KEY (ruleId),
UNIQUE KEY (\`version\`, checkDigest)
)
REPLACE WITH ${dbUtils.cteAclEffective({grantIds: grant.grantIds})},
cteCollectionSetting AS (
SELECT
c.settings->>"$.fields.detail.required" AS detailRequired,
c.settings->>"$.fields.comment.required" AS commentRequired,
c.settings->>"$.status.canAccept" AS collectionCanAccept,
CASE WHEN c.settings->>"$.status.canAccept" = 'true' AND c.settings->>"$.status.minAcceptGrant" <= @roleId
THEN 'true'
ELSE 'false'
END AS userCanAccept,
c.settings->>"$.status.resetCriteria" AS resetCriteria,
c.settings->>"$.history.maxReviews" AS maxReviews
FROM
enabled_collection c
WHERE
c.collectionId = @collectionId
),
cteIncoming AS (
SELECT
jt.ruleId,
result.resultId,
TRIM(jt.detail) as detail,
TRIM(jt.comment) as comment,
jt.resultEngine,
jt.metadata,
coalesce(statuslabel.statusId, statusraw.statusId) as statusId,
jt.statusText
FROM
JSON_TABLE(
@reviews,
"$[*]"
COLUMNS(
ruleId VARCHAR(45) PATH "$.ruleId",
result VARCHAR(255) PATH "$.result",
detail MEDIUMTEXT PATH "$.detail" NULL ON EMPTY,
comment MEDIUMTEXT PATH "$.comment",
resultEngine JSON PATH "$.resultEngine",
metadata JSON PATH "$.metadata",
statusRaw VARCHAR(255) PATH "$.status",
statusLabel VARCHAR(255) PATH "$.status.label",
statusText VARCHAR(511) PATH "$.status.text"
)
) AS jt
left join result on (jt.result = result.api)
left join \`status\` statusraw on (jt.statusRaw = statusraw.api)
left join \`status\` statuslabel on (jt.statusLabel = statuslabel.api)
),
cteGrant AS (
select
distinct rgr.ruleId
from
enabled_asset a
left join stig_asset_map sa using (assetId)
${grant.roleId === 1 ? 'inner' : 'left'} join cteAclEffective cae on sa.saId = cae.saId
left join revision rev on sa.benchmarkId = rev.benchmarkId
left join rev_group_rule_map rgr using (revId)
where
a.assetId = @assetId
and a.collectionId = @collectionId
and coalesce(cae.access, 'rw') = 'rw'
),
cteCandidate AS (
select
CASE WHEN cteGrant.ruleId is not null then 1 else null end as granted,
review.reviewId,
@assetId as assetId,
cteIncoming.ruleId,
rvcd.version,
rvcd.checkDigest,
COALESCE(cteIncoming.resultId, review.resultId) as resultId,
COALESCE(cteIncoming.detail, review.detail, '') as detail,
COALESCE(cteIncoming.comment, review.comment, '') as comment,
COALESCE(cteIncoming.metadata, review.metadata, '{}') as metadata,
CASE WHEN cteIncoming.resultEngine != 0 -- resultEngine present
THEN cteIncoming.resultEngine
ELSE
CASE WHEN cteIncoming.resultId is null -- result absent, patch only
THEN review.resultEngine
ELSE NULL
END
END as resultEngine,
CASE WHEN cteIncoming.statusId is not null
THEN cteIncoming.statusId
ELSE
CASE WHEN review.reviewId is null
or (rChangedResult.reviewId is not null and cteCollectionSetting.resetCriteria = 'result')
or (rChangedAny.reviewId is not null and cteCollectionSetting.resetCriteria = 'any')
THEN 0
ELSE review.statusId
END
END as statusId,
CASE WHEN cteIncoming.statusId is not null or review.reviewId is null
THEN cteIncoming.statusText
ELSE
CASE WHEN (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null)
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null)
THEN 'Review change triggered status update'
ELSE review.statusText
END
END as statusText,
CASE WHEN cteIncoming.statusId is not null -- request contains a status
or review.reviewId is null -- no existing review
or (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null) -- status meets criteria for resetting
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null) -- status meets criteria for resetting
THEN @utcTimestamp -- now
ELSE review.statusTs -- saved time
END as statusTs,
CASE WHEN cteIncoming.statusId is not null -- request contains a status
or review.reviewId is null -- no existing review
or (cteCollectionSetting.resetCriteria = 'result' and rChangedResult.reviewId is not null) -- status meets criteria for resetting
or (cteCollectionSetting.resetCriteria = 'any' and rChangedAny.reviewId is not null) -- status meets criteria for resetting
THEN @userId -- this user
ELSE review.statusUserId -- saved user
END as statusUserId,
CASE WHEN review.reviewId is null -- no existing review
or cteIncoming.resultId is not null -- patch request contains result
or cteIncoming.detail is not null -- patch request contains detail
or cteIncoming.comment is not null -- patch request contains comment
THEN @userId -- this user
ELSE review.userId -- saved user
END as userId,
CASE WHEN review.reviewId is null -- no existing review
or cteIncoming.resultId is not null -- patch request contains result
or cteIncoming.detail is not null -- patch request contains detail
or cteIncoming.comment is not null -- patch request contains comment
THEN @utcTimestamp -- now
ELSE review.ts -- saved time
END as ts
from
cteIncoming
LEFT JOIN cteGrant on cteIncoming.ruleId = cteGrant.ruleId
LEFT JOIN rule_version_check_digest rvcd on cteGrant.ruleId = rvcd.ruleId
LEFT JOIN review on (@assetId = review.assetId and rvcd.version = review.version and rvcd.checkDigest = review.checkDigest)
LEFT JOIN cteCollectionSetting on true
LEFT JOIN review rChangedResult on (
review.reviewId = rChangedResult.reviewId
and rChangedResult.statusId != 0
and cteIncoming.resultId != rChangedResult.resultId
)
LEFT JOIN review rChangedAny on (
review.reviewId = rChangedAny.reviewId
and rChangedAny.statusId != 0
and (rChangedAny.resultId != cteIncoming.resultId or rChangedAny.detail != cteIncoming.detail or rChangedAny.comment != cteIncoming.comment)
)
)
select
CASE WHEN cteCandidate.granted IS NULL
THEN
'no grant for this asset/ruleId'
ELSE
CASE WHEN cteCandidate.statusId > 0 -- submitted, rejected, accepted
THEN
CASE WHEN (cteCollectionSetting.collectionCanAccept = 'false' and cteCandidate.statusId IN (2,3))
THEN
'status = accepted, rejected not allowed for this Collection'
ELSE
CASE WHEN (cteCollectionSetting.userCanAccept = 'false' and cteCandidate.statusId IN (2,3))
THEN
'status = accepted, rejected not allowed for this User'
ELSE
CASE WHEN (cteCandidate.resultId NOT IN (2,3,4))
THEN
'status is not allowed for the result'
ELSE
CASE WHEN (cteCollectionSetting.detailRequired = 'always' AND cteCandidate.detail = '')
THEN
'empty detail is not allowed for status = submitted, accepted, rejected'
ELSE
CASE WHEN (cteCollectionSetting.commentRequired = 'always' AND cteCandidate.comment = '')
THEN
'empty comment is not allowed for status = submitted, accepted, rejected'
ELSE
CASE WHEN cteCandidate.resultId = 4 -- fail
THEN
CASE WHEN (cteCollectionSetting.detailRequired = 'findings' AND cteCandidate.detail = '')
THEN
'result = fail and empty detail not allowed for status = submitted, accepted, rejected'
ELSE
CASE WHEN (cteCollectionSetting.commentRequired = 'findings' AND cteCandidate.comment = '')
THEN
'result = fail and empty comment not allowed for status = submitted, accepted, rejected'
END
END
END
END
END
END
END
END
END
END as error,
cteCandidate.reviewId,
cteCandidate.assetId,
cteCandidate.ruleId,
cteCandidate.version,
cteCandidate.checkDigest,
cteCandidate.resultId,
cteCandidate.detail,
cteCandidate.comment,
cteCandidate.resultEngine,
cteCandidate.metadata,
cteCandidate.statusId,
cteCandidate.statusText,
cteCandidate.statusUserId,
cteCandidate.statusTs,
cteCandidate.userId,
cteCandidate.ts
from
cteCandidate
LEFT JOIN cteCollectionSetting on true`
const sqlHistoryPrune = `
with historyRecs AS (
select
rh.historyId,
ROW_NUMBER() OVER (PARTITION BY r.assetId, r.version, r.checkDigest ORDER BY rh.historyId DESC) as rowNum
from
review_history rh
left join review r using (reviewId)
where
reviewId IN (SELECT reviewId from tt_validated_review where error is null and reviewId is not null)
)
delete review_history
FROM
review_history
left join historyRecs on review_history.historyId = historyRecs.historyId
WHERE
historyRecs.rowNum > (select c.settings->>"$.history.maxReviews" FROM enabled_collection c where collectionId = @collectionId) - 1
`
const sqlHistory = `
INSERT INTO review_history (
reviewId,
ruleId,
resultId,
detail,
comment,
autoResult,
ts,
userId,
statusText,
statusUserId,
statusTs,
statusId,
touchTs,
resultEngine
) SELECT
reviewId,
ruleId,
resultId,
LEFT(detail,32767) as detail,
LEFT(comment,32767) as comment,
autoResult,
ts,
userId,
statusText,
statusUserId,
statusTs,
statusId,
touchTs,
CASE WHEN resultEngine = 0 THEN NULL ELSE resultEngine END
FROM
review
WHERE
reviewId IN (SELECT reviewId from tt_validated_review where error is null and reviewId is not null)
FOR UPDATE
`
const sqlUpdateReviews = `
update
review r
inner join tt_validated_review vr on (r.reviewId = vr.reviewId and vr.error is null)
set
r.ruleId = vr.ruleId,
r.resultId = vr.resultId,
r.resultEngine = vr.resultEngine,
r.detail = vr.detail,
r.comment = vr.comment,
r.metadata = vr.metadata,
r.statusId = vr.statusId,
r.statusText = vr.statusText,
r.statusUserId = vr.statusUserId,
r.statusTs = vr.statusTs,
r.userId = vr.userId,
r.ts = vr.ts
`
const sqlInsertReviews = `
insert into review (
assetId,
ruleId,
\`version\`,
checkDigest,
resultId,
resultEngine,
detail,
comment,
metadata,
statusId,
statusText,
statusUserId,
statusTs,
userId,
ts)
select
assetId,
ruleId,
\`version\`,
checkDigest,
resultId,
resultEngine,
detail,
comment,
metadata,
statusId,
statusText,
statusUserId,
statusTs,
userId,
ts
from
tt_validated_review vr
where
error is null and reviewId is null
`
try {
connection = await dbUtils.pool.getConnection()
const sqlSetVariables = `set @collectionId = ?, @assetId = ?, @userId = ?, @roleId = ?, @reviews = ?, @utcTimestamp = UTC_TIMESTAMP()`
await connection.query(sqlSetVariables, [parseInt(collectionId), parseInt(assetId), parseInt(userId), grant.roleId, JSON.stringify(reviews)])
const [settings] = await connection.query(`select c.settings->>"$.history.maxReviews" as maxReviews FROM enabled_collection c where collectionId = @collectionId`)
const historyMaxReviews = settings[0].maxReviews
await connection.query(sqlCreateTableValidatedReview)
let [counts] = await connection.query(`select
coalesce(sum(case when error is not null then 1 else 0 end),0) as failedValidations,
coalesce(sum(case when error is null and reviewId is null then 1 else 0 end),0) as inserts,
coalesce(sum(case when error is null and reviewId is not null then 1 else 0 end),0) as updates
from tt_validated_review`)
let validationErrors = []
if (counts[0].failedValidations) {
;[validationErrors] = await connection.query('select ruleId, error as reason from tt_validated_review where error is not null LIMIT 50')
}
async function transaction () {
await connection.query('START TRANSACTION')
if (counts[0].updates) {
await connection.query(sqlHistoryPrune, [ historyMaxReviews ])
if (historyMaxReviews !== 0) {
await connection.query(sqlHistory)
}
await connection.query(sqlUpdateReviews)
}
if (counts[0].inserts) {
await connection.query(sqlInsertReviews)
}
await dbUtils.updateStatsAssetStig(connection, {assetId})
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return {
rejected: validationErrors,
affected: {
updated: counts[0].updates,
inserted: counts[0].inserts
}
}
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.query('DROP TEMPORARY TABLE IF EXISTS tt_validated_review')
await connection.release()
}
}
}
// Returns a Boolean
exports.checkRuleByAssetUser = async function ({ruleId, assetId, collectionId, grant, checkWritable}) {
const binds = []
let sql = `with ${dbUtils.cteAclEffective({grantIds: grant.grantIds})}
select
rgr.ruleId
from
enabled_asset a
left join stig_asset_map sa using (assetId)
${grant.roleId === 1 ? 'inner' : 'left'} join cteAclEffective cae on sa.saId = cae.saId
left join revision rev on sa.benchmarkId = rev.benchmarkId
left join rev_group_rule_map rgr using (revId)
where
a.assetId = ?
and rgr.ruleId = ?
${checkWritable ? "and coalesce(cae.access, 'rw') = 'rw'" : ''}
${collectionId ? "and a.collectionId = ?" : ''}`
binds.push(assetId, ruleId, collectionId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0
}
exports.getReviewMetadataKeys = async function ( assetId, ruleId ) {
const binds = []
let sql = `
select
JSON_KEYS(metadata) as keyArray
from
review r
left join rule_version_check_digest rvcd on (r.version = rvcd.version and r.checkDigest = rvcd.checkDigest)
where
r.assetId = ?
and rvcd.ruleId = ?`
binds.push(assetId, ruleId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].keyArray : []
}
exports.getReviewMetadata = async function ( assetId, ruleId ) {
const binds = []
let sql = `
select
metadata
from
review r
left join rule_version_check_digest rvcd on (r.version = rvcd.version and r.checkDigest = rvcd.checkDigest)
where
r.assetId = ?
and rvcd.ruleId = ?`
binds.push(assetId, ruleId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].metadata : {}
}
exports.patchReviewMetadata = async function ( assetId, ruleId, metadata ) {
const binds = []
let sql = `
update
review
left join rule_version_check_digest rvcd on (review.version = rvcd.version and review.checkDigest = rvcd.checkDigest)
set
review.metadata = JSON_MERGE_PATCH(metadata, ?)
where
review.assetId = ?
and rvcd.ruleId = ?`
binds.push(JSON.stringify(metadata), assetId, ruleId)
await dbUtils.pool.query(sql, binds)
return true
}
exports.putReviewMetadata = async function ( assetId, ruleId, metadata ) {
const binds = []
let sql = `
update
review
left join rule_version_check_digest rvcd on (review.version = rvcd.version and review.checkDigest = rvcd.checkDigest)
set
review.metadata = ?
where
review.assetId = ?
and rvcd.ruleId = ?`
binds.push(JSON.stringify(metadata), assetId, ruleId)
await dbUtils.pool.query(sql, binds)
return true
}
exports.getReviewMetadataValue = async function ( assetId, ruleId, key ) {
const binds = []
let sql = `
select
JSON_EXTRACT(metadata, ?) as value
from
review r
left join rule_version_check_digest rvcd on (r.version = rvcd.version and r.checkDigest = rvcd.checkDigest)
where
r.assetId = ?
and rvcd.ruleId = ?`
binds.push(`$."${key}"`, assetId, ruleId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].value : ""
}
exports.putReviewMetadataValue = async function ( assetId, ruleId, key, value ) {
const binds = []
let sql = `
update
review
left join rule_version_check_digest rvcd on (review.version = rvcd.version and review.checkDigest = rvcd.checkDigest)
set
review.metadata = JSON_SET(metadata, ?, ?)
where
review.assetId = ?
and rvcd.ruleId = ?`
binds.push(`$."${key}"`, value, assetId, ruleId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].value : ""
}
exports.deleteReviewMetadataKey = async function ( assetId, ruleId, key ) {
const binds = []
let sql = `
update
review
left join rule_version_check_digest rvcd on (review.version = rvcd.version and review.checkDigest = rvcd.checkDigest)
set
review.metadata = JSON_REMOVE(metadata, ?)
where
review.assetId = ?
and rvcd.ruleId = ?`
binds.push(`$."${key}"`, assetId, ruleId)
let [rows] = await dbUtils.pool.query(sql, binds)
return rows.length > 0 ? rows[0].value : ""
}
================================================
FILE: api/source/service/STIGService.js
================================================
'use strict';
const dbUtils = require('./utils')
const {createHash} = require('node:crypto')
const _this = this
function cteStigCollection ({elevate = false, unrestrictedCollectionIds = [], hasRestrictions = true}) {
const columns = [
'sa.benchmarkId',
`cast(concat('[', group_concat(distinct concat('"',a.collectionId,'"')),']') as json) as collectionIds`
]
const joins = [
'stig_asset_map sa',
'inner join enabled_asset a on a.assetId=sa.assetId',
'inner join enabled_collection c on c.collectionId=a.collectionId'
]
const predicates = {
statements: [],
binds: []
}
const groupBy = ['sa.benchmarkId']
if (!elevate) {
const statements = []
if (hasRestrictions) {
joins.push('left join cteAclEffective cae on sa.saId = cae.saId')
statements.push('cae.saId is not null')
}
if (unrestrictedCollectionIds.length) {
statements.push('c.collectionId in (?)')
predicates.binds.push(unrestrictedCollectionIds)
}
if (statements.length) predicates.statements.push(statements.join(' OR '))
}
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, format: true})
return `cte_stig_collection as (${sql})`
}
function cteRevCollection({elevate = false, unrestrictedCollectionIds = [], hasRestrictions = true}) {
const columns = [
'r.revId',
`cast(concat('[', group_concat(distinct concat('"',crm.collectionId,'"')),']') as json) as collectionIds`
]
const joins = [
'revision r',
'inner join collection_rev_map crm using (revId)'
]
const predicates = {
statements: [],
binds: []
}
const groupBy = ['r.revId']
if (!elevate) {
const statements = []
if (hasRestrictions) {
joins.push('left join stig_asset_map sa on r.benchmarkId = sa.benchmarkId','left join cteAclEffective cae on sa.saId = cae.saId')
statements.push('cae.saId is not null')
}
if (unrestrictedCollectionIds.length) {
statements.push('crm.collectionId in (?)')
predicates.binds.push(unrestrictedCollectionIds)
}
if (statements.length) predicates.statements.push(statements.join(' OR '))
}
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, format: true})
return `cte_rev_collection as (${sql})`
}
function parseGrants (grants, elevate = false) {
const unrestrictedCollectionIds = []
let requireCteAcls = false
let requesterGrantIds = []
if (!elevate) {
for (const collectionId in grants) {
if (grants[collectionId].roleId === 1) {
requesterGrantIds.push(grants[collectionId].grantIds)
}
else {
unrestrictedCollectionIds.push(collectionId)
}
}
requesterGrantIds = requesterGrantIds.flat()
requireCteAcls = !!requesterGrantIds.length
}
return {unrestrictedCollectionIds, requesterGrantIds, requireCteAcls }
}
/**
Generalized queries for STIGs
**/
exports.queryStigs = async function ({filter, projections, grants, elevate = false}) {
const {
unrestrictedCollectionIds,
requesterGrantIds,
requireCteAcls
} = parseGrants(grants, elevate)
const ctes = []
if (requireCteAcls) {
ctes.push(dbUtils.cteAclEffective({grantIds: requesterGrantIds}))
}
ctes.push(cteStigCollection({
elevate,
unrestrictedCollectionIds,
hasRestrictions: !!requesterGrantIds.length
}))
// cte_stig is used for the base query (no projections)
const cteStigColumns = [
'b.benchmarkId',
'b.title',
`cr.status`,
`cr.marking`,
`concat('V', cr.version, 'R', cr.release) as "lastRevisionStr"`,
`date_format(cr.benchmarkDateSql,'%Y-%m-%d') as "lastRevisionDate"`,
`cr.ruleCount`,
`coalesce(sc.collectionIds,json_array()) as collectionIds`,
`JSON_ARRAYAGG(concat('V',revision.version,'R',revision.release)) OVER (PARTITION BY b.benchmarkId ORDER BY revision.benchmarkDateSql DESC) as revisionStrs`,
`ROW_NUMBER() OVER (PARTITION BY b.benchmarkId ORDER BY revision.benchmarkDateSql ASC) as rownum`
]
const cteStigJoins = [
'stig b',
'left join current_rev cr on b.benchmarkId = cr.benchmarkId',
'left join cte_stig_collection sc on b.benchmarkId = sc.benchmarkId',
'left join revision on b.benchmarkId = revision.benchmarkId',
]
// PREDICATES
const cteStigPredicates = {
statements: [],
binds: []
}
if (filter.title) {
cteStigPredicates.statements.push("b.title LIKE CONCAT('%',?,'%')")
cteStigPredicates.binds.push( filter.title )
}
if (filter.benchmarkId) {
cteStigPredicates.statements.push('b.benchmarkId = ?')
cteStigPredicates.binds.push( filter.benchmarkId )
}
// Main query columns, can be modified by projections
const columns = [
'benchmarkId',
'title',
'`status`',
'marking',
`lastRevisionStr`,
`lastRevisionDate`,
`ruleCount`,
`revisionStrs`,
`collectionIds`,
]
if (projections.includes('revisions')) {
// add cte_rev_collection, add revision objects to cteStigColumns, add joins to cteStigJoins
ctes.push(cteRevCollection({
elevate,
unrestrictedCollectionIds,
hasRestrictions: !!requesterGrantIds.length
}))
cteStigColumns.push(`JSON_ARRAYAGG(
json_object(
"benchmarkId", revision.benchmarkId,
"revisionStr", concat('V',revision.version,'R',revision.release),
"version", cast(revision.version as char),
"release", revision.release,
"benchmarkDate", revision.benchmarkDateSql,
"status", revision.status,
"statusDate", revision.statusDate,
"marking", revision.marking,
"ruleCount", revision.ruleCount,
"collectionIds", coalesce(rc.collectionIds,json_array())
)) OVER (PARTITION BY b.benchmarkId ORDER BY revision.benchmarkDateSql DESC) as revisions`)
cteStigJoins.push('left join cte_rev_collection rc on revision.revId = rc.revId')
columns.push('revisions')
}
ctes.push(`cte_stig AS (${dbUtils.makeQueryString({columns:cteStigColumns, joins:cteStigJoins, predicates:cteStigPredicates, orderBy:['b.benchmarkId']})})`)
// CONSTRUCT MAIN QUERY
const joins = ['cte_stig']
const predicates = {
statements: ['rownum = 1'],
binds: cteStigPredicates.binds
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
/**
Generalized queries for Groups
**/
exports.queryGroups = async function ( inProjection, inPredicates ) {
let columns = [
'rgr.groupId as "groupId"',
'rgr.groupTitle as "title"',
]
const orderBy = ['substring(rgr.groupId from 3) + 0']
const groupBy = ['rgr.groupId', 'rgr.groupTitle']
let joins
let predicates = {
statements: [],
binds: []
}
predicates.statements.push('r.benchmarkId = ?')
predicates.binds.push(inPredicates.benchmarkId)
if (inPredicates.revisionStr != 'latest') {
joins = ['revision r']
const {version, release} = dbUtils.parseRevisionStr(inPredicates.revisionStr)
predicates.statements.push('r.version = ?')
predicates.binds.push(version)
predicates.statements.push('r.release = ?')
predicates.binds.push(release)
} else {
joins = ['current_rev r']
}
joins.push('inner join rev_group_rule_map rgr on r.revId = rgr.revId')
if (inPredicates.groupId) {
predicates.statements.push('rgr.groupId = ?')
predicates.binds.push(inPredicates.groupId)
}
// PROJECTIONS
if (inProjection?.includes('rules')) {
columns.push(`json_arrayagg(json_object(
'ruleId', rgr.ruleId,
'version', rgr.version,
'title', rgr.title,
'severity', rgr.severity)) as "rules"`)
}
// // CONSTRUCT MAIN QUERY
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, orderBy})
const [rows] = await dbUtils.pool.query(sql, predicates.binds)
return (rows.length > 0 ? rows : null)
}
/**
Generalized queries for Rules associated with a STIG
For specific Rule, allow for projections with Check and Fixes
**/
exports.queryBenchmarkRules = async function ( benchmarkId, revisionStr, inProjection, inPredicates ) {
let columns = [
'rgr.ruleId',
'rgr.title',
'rgr.groupId',
'rgr.groupTitle',
'rgr.version',
'rgr.severity'
]
let groupBy = [
'rgr.ruleId',
'rgr.title',
'rgr.groupId',
'rgr.groupTitle',
'rgr.version',
'rgr.severity',
'rgr.rgrId'
]
const orderBy = ['substring(rgr.ruleId from 4) + 0']
let joins
let predicates = {
statements: [],
binds: []
}
// PREDICATES
predicates.statements.push('rev.benchmarkId = ?')
predicates.binds.push(benchmarkId)
if (revisionStr != 'latest') {
joins = ['revision rev']
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
predicates.statements.push('rev.version = ?')
predicates.binds.push(version)
predicates.statements.push('rev.release = ?')
predicates.binds.push(release)
} else {
joins = ['current_rev rev']
}
if (inPredicates?.ruleId) {
predicates.statements.push('rgr.ruleId = ?')
predicates.binds.push(inPredicates.ruleId)
}
joins.push('left join rev_group_rule_map rgr using (revId)' )
// PROJECTIONS
if ( inProjection?.includes('detail') ) {
columns.push(`json_object(
'weight', rgr.weight,
'vulnDiscussion', rgr.vulnDiscussion,
'falsePositives', rgr.falsePositives,
'falseNegatives', rgr.falseNegatives,
'documentable', rgr.documentable,
'mitigations', rgr.mitigations,
'severityOverrideGuidance', rgr.severityOverrideGuidance,
'potentialImpacts', rgr.potentialImpacts,
'thirdPartyTools', rgr.thirdPartyTools,
'mitigationControl', rgr.mitigationControl,
'responsibility', rgr.responsibility
) as detail`)
groupBy.push(
'rgr.version',
'rgr.weight',
'rgr.vulnDiscussion',
'rgr.falsePositives',
'rgr.falseNegatives',
'rgr.documentable',
'rgr.mitigations',
'rgr.severityOverrideGuidance',
'rgr.potentialImpacts',
'rgr.thirdPartyTools',
'rgr.mitigationControl',
'rgr.responsibility',
'rgr.iacontrols'
)
}
if ( inProjection?.includes('ccis') ) {
columns.push(`(select
coalesce
(
(select json_arrayagg(
json_object(
'cci', rgrcc.cci,
'apAcronym', cci.apAcronym,
'definition', cci.definition,
'control', crm.parentControl
)
)
from
rev_group_rule_cci_map rgrcc
inner join cci cci using (cci)
left join cci_reference_map crm using (cci)
where
rgrcc.rgrId = rgr.rgrId
),
json_array()
)
) as "ccis"`)
}
if ( inProjection?.includes('check') ) {
joins.push('left join check_content cc on rgr.checkDigest = cc.digest' )
columns.push(`json_object(
'system', rgr.checkSystem,
'content', cc.content) as \`check\``)
}
if ( inProjection?.includes('fix') ) {
joins.push('left join fix_text ft on rgr.fixDigest = ft.digest' )
columns.push(`json_object(
'fixref', rgr.fixref,
'text', ft.text) as fix`)
}
// // CONSTRUCT MAIN QUERY
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, orderBy})
const [rows] = await dbUtils.pool.query(sql, predicates.binds)
return (rows)
}
/**
Generalized queries for a single Rule, optionally with Check and Fix
**/
exports.queryRules = async function ( ruleId, inProjection ) {
let columns = [
'rgr.ruleId',
'rgr.version',
'rgr.title',
'rgr.severity',
'rgr.groupId',
'rgr.groupTitle'
]
let groupBy = [
"rgr.ruleId",
"rgr.version",
"rgr.title",
"rgr.severity",
"rgr.groupId",
"rgr.groupTitle"
]
const orderBy = ['substring(rgr.ruleId from 4) + 0']
let joins = [
'rev_group_rule_map rgr'
]
let predicates = {
statements: [],
binds: []
}
// PREDICATES
predicates.statements.push('rgr.ruleId = ?')
predicates.binds.push(ruleId)
// PROJECTIONS
if ( inProjection?.includes('detail') ) {
columns.push(`json_object(
'weight', any_value(rgr.weight),
'vulnDiscussion', any_value(rgr.vulnDiscussion),
'falsePositives', any_value(rgr.falsePositives),
'falseNegatives', any_value(rgr.falseNegatives),
'documentable', any_value(rgr.documentable),
'mitigations', any_value(rgr.mitigations),
'severityOverrideGuidance', any_value(rgr.severityOverrideGuidance),
'potentialImpacts', any_value(rgr.potentialImpacts),
'thirdPartyTools', any_value(rgr.thirdPartyTools),
'mitigationControl', any_value(rgr.mitigationControl),
'responsibility', any_value(rgr.responsibility)
) as detail`)
}
if ( inProjection?.includes('ccis') ) {
columns.push(`CASE WHEN count(rgrcc.cci) = 0
THEN json_array()
ELSE CAST(CONCAT('[', GROUP_CONCAT(distinct json_object('cci', rgrcc.cci,'apAcronym',cci.apAcronym,'definition',cci.definition,'control',crm.parentControl)), ']') as json)
END as ccis`)
joins.push(
'left join rev_group_rule_cci_map rgrcc using (rgrId)',
'inner join cci using (cci)',
'inner join cci_reference_map crm on cci.cci = crm.cci'
)
}
if ( inProjection?.includes('check') ) {
columns.push(`json_object('system', any_value(rgr.checkSystem),'content', any_value(cc.content)) as \`check\``)
joins.push('left join check_content cc on rgr.checkDigest = cc.digest')
}
if ( inProjection?.includes('fix') ) {
columns.push(`json_object('fixref', any_value(rgr.fixref),'text', any_value(ft.text)) as fix`)
joins.push('left join fix_text ft on rgr.fixDigest = ft.digest')
}
if (inProjection?.includes('ruleIds')) {
columns.push(`cast(concat('[', group_concat(distinct '"' , rvcd.ruleId , '"'), ']') as json) as ruleIds`)
joins.push(
'left join rule_version_check_digest rvcd on (rgr.version = rvcd.version and rgr.checkDigest = rvcd.checkDigest)',
)
}
if (inProjection?.includes('stigs')) {
columns.push(`cast(concat('[', group_concat(distinct json_object('benchmarkId',revision.benchmarkId,'revisionStr',revision.revisionStr)), ']') as json) as stigs`)
joins.push('left join revision on rgr.revId = revision.revId')
}
// CONSTRUCT MAIN QUERY
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows[0])
}
exports.insertManualBenchmark = async function (b, clobber, svcStatus = {}) {
let connection
try {
const stats = {}
let totalstart = process.hrtime()
const {ddl, dml} = queriesFromBenchmarkData(b) // defined below
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
// check if this revision exists
const [revision] = await connection.query('select revId from revision where `benchmarkId` = ? and `version` = ? and `release` = ?', [
dml.revision.binds.benchmarkId,
dml.revision.binds.version,
dml.revision.binds.release
])
const gExistingRevision = revision?.[0]?.revId
if (gExistingRevision && !clobber) {
return {
benchmarkId: dml.revision.binds.benchmarkId,
revisionStr: `V${dml.revision.binds.version}R${dml.revision.binds.release}`,
marking: dml.revision.binds.marking,
action: 'preserved'
}
}
// create temporary tables outside the transaction
for (const tempTable of Object.keys(ddl)) {
await connection.query(ddl[tempTable].drop)
await connection.query(ddl[tempTable].create)
}
async function transaction() {
let result, hrstart, hrend, action = 'inserted'
await connection.query('START TRANSACTION')
// purge any exitsing records for this revision so we can replace
if (gExistingRevision) {
hrstart = process.hrtime()
await connection.query('DELETE FROM revision WHERE revId = ?', [gExistingRevision])
const cleanupDml = [
"DELETE FROM check_content WHERE digest NOT IN (select checkDigest from rev_group_rule_map)",
"DELETE FROM fix_text WHERE digest NOT IN (select digest from rev_group_rule_map)"
]
for (const query of cleanupDml) {
await connection.query(query)
}
hrend = process.hrtime(hrstart)
stats.delRev = `${hrend[0]}s ${hrend[1] / 1000000}ms`
action = 'replaced'
}
// insert new records for this revision
const queryOrder = [
'stig',
'revision',
'tempRuleCci',
'checkContent',
'fixText',
'revGroupRuleMap',
'revGroupRuleCciMap',
'ruleVersionCheckDigest'
]
for (const query of queryOrder) {
hrstart = process.hrtime()
if (Array.isArray(dml[query].binds)) {
if (dml[query].binds.length === 0) { continue }
;[result] = await connection.query(dml[query].sql, [dml[query].binds])
}
else {
;[result] = await connection.query(dml[query].sql, dml[query].binds)
}
hrend = process.hrtime(hrstart)
stats[query] = `${result.affectedRows} in ${hrend[0]}s ${hrend[1] / 1000000}ms`
}
// Update current_rev
hrstart = process.hrtime()
let sqlDeleteCurrentRev = 'DELETE from current_rev where benchmarkId = ?'
let sqlUpdateCurrentRev = `INSERT INTO current_rev (
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
marking,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount)
SELECT
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
marking,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount
FROM
v_current_rev
WHERE
v_current_rev.benchmarkId = ?`
await connection.query(sqlDeleteCurrentRev, [dml.stig.binds.benchmarkId])
await connection.query(sqlUpdateCurrentRev, [dml.stig.binds.benchmarkId])
hrend = process.hrtime(hrstart)
stats.current_rev = `${hrend[0]}s ${hrend[1] / 1000000}ms`
// Stats
hrstart = process.hrtime()
await dbUtils.updateDefaultRev(connection, {
benchmarkId: dml.stig.binds.benchmarkId
})
await dbUtils.updateStatsAssetStig(connection, {
benchmarkId: dml.stig.binds.benchmarkId
})
hrend = process.hrtime(hrstart)
stats.statistics = `${hrend[0]}s ${hrend[1] / 1000000}ms`
await connection.commit()
hrend = process.hrtime(totalstart)
stats.totalTime = `Completed in ${hrend[0]}s ${hrend[1] / 1000000}ms`
return {
benchmarkId: dml.revision.binds.benchmarkId,
revisionStr: `V${dml.revision.binds.version}R${dml.revision.binds.release}`,
marking: dml.revision.binds.marking,
action
}
}
return await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
function queriesFromBenchmarkData(b) {
const tempFlag = true
const ddl = {
tempRuleCci: {
drop: 'drop table if exists temp_rule_cci',
create: `CREATE${tempFlag ? ' TEMPORARY' : ''} TABLE temp_rule_cci (
ruleId varchar(255) NOT NULL,
cci varchar(20))`
}
}
const dml = {
stig: {
sql: "insert into stig (title, benchmarkId) VALUES (:title, :benchmarkId) as new on duplicate key update stig.title = new.title"
},
revision: {
sql: `insert into revision (
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
marking,
description,
groupCount,
checkCount,
fixCount,
lowCount,
mediumCount,
highCount
) VALUES (
:revId,
:benchmarkId,
:version,
:release,
:benchmarkDate,
STR_TO_DATE(:benchmarkDateSql, '%Y-%m-%d'),
:status,
:statusDate,
:marking,
:description,
:groupCount,
:checkCount,
:fixCount,
:lowCount,
:mediumCount,
:highCount)`,
},
checkContent: {
sql: `insert ignore into check_content (content) VALUES ?`,
binds: []
},
fixText: {
sql: `insert ignore into fix_text (\`text\`) VALUES ?`,
binds: []
},
tempRuleCci: {
sql: `insert ignore into temp_rule_cci (ruleId, cci) VALUES ?`,
binds: []
},
revGroupRuleMap: {
sql: `INSERT INTO rev_group_rule_map (
revId,
groupId, groupTitle, groupSeverity,
ruleId, \`version\`, title, severity, weight, vulnDiscussion,
falsePositives, falseNegatives, documentable, mitigations,
severityOverrideGuidance, potentialImpacts, thirdPartyTools, mitigationControl,
responsibility, iaControls, checkSystem, checkDigest, fixref, fixDigest)
VALUES ?`,
binds: []
},
revGroupRuleCciMap: {
sql: `INSERT IGNORE INTO rev_group_rule_cci_map (rgrId, cci)
SELECT
rgr.rgrId,
tt.cci
FROM
rev_group_rule_map rgr
inner join temp_rule_cci tt using (ruleId)
WHERE
rgr.revId = :revId`
},
ruleVersionCheckDigest: {
sql: `INSERT INTO rule_version_check_digest (ruleId, \`version\`, checkDigest)
with currentRuleVersionCheckDigest as (
select
rgr.ruleId,
rgr.version,
rgr.checkDigest,
rev.benchmarkDateSql,
rev.revId,
ROW_NUMBER() OVER (PARTITION BY rgr.ruleId ORDER BY rev.benchmarkDateSql DESC) as rowNum
from
rev_group_rule_map rgr
left join revision rev using (revId)
where
rgr.checkDigest is not null
and rev.benchmarkId = ?
)
select
ruleId,
\`version\`,
checkDigest
from
currentRuleVersionCheckDigest crvcd
where
rowNum = 1
ON DUPLICATE KEY UPDATE
\`version\`=crvcd.version,
checkDigest=crvcd.checkDigest`,
binds: []
}
}
let { revision, ...benchmarkBinds } = b
// QUERY: stig
dml.stig.binds = benchmarkBinds
delete dml.stig.binds.scap
let { groups, ...revisionBinds } = revision
delete revisionBinds.revisionStr
revisionBinds.benchmarkId = benchmarkBinds.benchmarkId
revisionBinds.revId = `${revisionBinds.benchmarkId}-${revisionBinds.version}-${revisionBinds.release}`
revisionBinds.benchmarkDateSql = revisionBinds.benchmarkDate8601
delete revisionBinds.benchmarkDate8601
revisionBinds.lowCount = revisionBinds.mediumCount = revisionBinds.highCount = 0
// QUERY: revision
dml.revision.binds = revisionBinds
let ruleCount = 0
let checkCount = 0
let fixCount = 0
for (const group of groups) {
let { rules, ...groupBinds } = group
let groupSeverity
for (const rule of rules) {
ruleCount++
let { checks, fixes, idents, ...ruleBinds } = rule
// Group severity calculation
if (!groupSeverity) {
groupSeverity = ruleBinds.severity
}
else if (groupSeverity !== ruleBinds.severity) {
groupSeverity = 'mixed'
}
checkCount += checks.length
fixCount += fixes.length
const checkSystem = checks.map( check => check.system).join(',')
const checkContent = checks.map( check => check.content).join('\n\n-----AND-----\n\n')
const checkDigest = createHash('sha256').update(checkContent).digest()
const fixref = fixes.map( fix => fix.fixref).join(',')
const fixText = fixes.map( fix => fix.text).join('\n\n-----AND-----\n\n')
const fixDigest = createHash('sha256').update(fixText).digest()
// QUERY: checkContent
dml.checkContent.binds.push([checkContent])
// QUERY: fixText
dml.fixText.binds.push([fixText])
// QUERY: revGroupRuleMap
dml.revGroupRuleMap.binds.push([
revisionBinds.revId,
groupBinds.groupId,
groupBinds.title,
ruleBinds.severity, // groupSeverity hack
ruleBinds.ruleId,
ruleBinds.version,
ruleBinds.title,
ruleBinds.severity,
ruleBinds.weight,
ruleBinds.vulnDiscussion,
ruleBinds.falsePositives,
ruleBinds.falseNegatives,
ruleBinds.documentable,
ruleBinds.mitigations,
ruleBinds.severityOverrideGuidance,
ruleBinds.potentialImpacts,
ruleBinds.thirdPartyTools,
ruleBinds.mitigationControl,
ruleBinds.responsibility,
ruleBinds.iaControls,
checkSystem,
checkDigest,
fixref,
fixDigest
])
for (const ident of idents) {
if (ident.system === 'http://iase.disa.mil/cci' || ident.system === 'http://cyber.mil/cci') {
dml.tempRuleCci.binds.push([
rule.ruleId,
ident.ident.replace('CCI-', '')])
}
}
}
// QUERY: rev_group_rule_cci_map
dml.revGroupRuleCciMap.binds = { revId: revisionBinds.revId }
}
dml.revision.binds.groupCount = groups.length
dml.revision.binds.checkCount = checkCount
dml.revision.binds.fixCount = fixCount
// add rule severity counts to the revision binds. groupRule[7] is the location of the severity value
dml.revision.binds = dml.revGroupRuleMap.binds.reduce((binds, groupRule) => {
const prop = `${groupRule[7]}Count`
binds[prop] = (binds[prop] ?? 0) + 1
return binds
}, dml.revision.binds)
// QUERY: ruleVersionCheckDigest
dml.ruleVersionCheckDigest.binds.push(benchmarkBinds.benchmarkId)
return {ddl, dml}
}
/**
* Deletes the specified revision of a STIG
*
* benchmarkId String A path parameter that identifies a STIG
* revisionStr String A path parameter that identifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns Revision
**/
exports.deleteRevisionByString = async function(benchmarkId, revisionStr, svcStatus = {}) {
let dmls = [
"DELETE from collection_rev_map where revId = (SELECT revId FROM revision WHERE benchmarkId = :benchmarkId and `version` = :version and `release` = :release)",
"DELETE FROM revision WHERE benchmarkId = :benchmarkId and `version` = :version and `release` = :release",
"DELETE FROM check_content WHERE digest NOT IN (select checkDigest from rev_group_rule_map)",
"DELETE FROM fix_text WHERE digest NOT IN (select fixDigest from rev_group_rule_map)",
"DELETE FROM rule_version_check_digest WHERE ruleId NOT IN (select DISTINCT ruleId from rev_group_rule_map)"
]
let currentRevDmls = [
"DELETE from current_rev where benchmarkId = :benchmarkId",
`INSERT INTO current_rev (
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
marking,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount)
SELECT
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
marking,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount
FROM
v_current_rev
WHERE
v_current_rev.benchmarkId = :benchmarkId`,
"DELETE FROM stig WHERE benchmarkId NOT IN (select benchmarkId FROM current_rev)"
]
let connection;
try {
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
let binds = {
benchmarkId: benchmarkId,
version: version,
release: release,
revId: `${benchmarkId}-${version}-${release}`
}
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
async function transaction () {
await connection.query('START TRANSACTION')
// note if this is the current revision
const [crRows] = await connection.query('SELECT * FROM current_rev WHERE benchmarkId = :benchmarkId and `version` = :version and `release` = :release', binds)
const wasCurrentRev = !!crRows.length
// note if this revision is used to calculate stats
const [drRows] = await connection.query('SELECT collectionId FROM default_rev WHERE benchmarkId = :benchmarkId and revId = :revId', binds)
const wasDefaultRev = !!drRows.length
// re-materialize current_rev if we're deleting the current revision
if (wasCurrentRev) {
dmls = dmls.concat(currentRevDmls)
}
for (const sql of dmls) {
await connection.query(sql, binds)
}
// re-calculate review statistics and repopulate default_rev from view if we've affected default_rev
if (wasDefaultRev) {
const collectionIds = drRows.map( row => row.collectionId)
await dbUtils.updateDefaultRev( connection, {collectionIds, benchmarkId})
await dbUtils.updateStatsAssetStig( connection, {collectionIds, benchmarkId})
}
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch(err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw (err)
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
/**
* Deletes a STIG (*** and all revisions ***)
*
* benchmarkId String A path parameter that indentifies a STIG
* returns STIG
**/
exports.deleteStigById = async function(benchmarkId, userObject, svcStatus = {}) {
let dmls = [
"DELETE from stig where benchmarkId = :benchmarkId",
"DELETE from current_rev where benchmarkId = :benchmarkId",
"DELETE from collection_rev_map where benchmarkId = :benchmarkId",
"DELETE from default_rev where benchmarkId = :benchmarkId",
"DELETE FROM check_content WHERE digest NOT IN (select checkDigest from rev_group_rule_map)",
"DELETE FROM fix_text WHERE digest NOT IN (select fixDigest from rev_group_rule_map)",
"DELETE FROM rule_version_check_digest WHERE ruleId NOT IN (select DISTINCT ruleId from rev_group_rule_map)"
]
let connection;
try {
let rows = await _this.queryStigs({
filter: {benchmarkId},
projections: [],
grants: userObject.grants
})
let binds = {
benchmarkId: benchmarkId
}
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
async function transaction () {
await connection.query('START TRANSACTION')
for (const sql of dmls) {
await connection.query(sql, binds)
}
await dbUtils.updateStatsAssetStig( connection, {benchmarkId})
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
return (rows[0])
}
catch (err) {
if (typeof connection !== 'undefined') {
await connection.rollback()
}
throw (err)
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
}
/**
* Return data for the specified CCI
*
* cci String A path parameter that indentifies a CCI
* returns List
**/
exports.getCci = async function(cci, inProjection, userObject) {
let columns = [
'c.cci',
'c.status',
'c.publishdate',
'c.contributor',
'c.type',
'c.definition'
]
const orderBy = ['c.cci']
let joins = [
'cci c '
]
let predicates = {
statements: [],
binds: []
}
// PREDICATES
predicates.statements.push('c.cci = ?')
predicates.binds.push(cci)
if ( inProjection?.includes('emassAp') ) {
columns.push(`case when c.apAcronym is null then null else json_object("apAcronym", c.apAcronym, "implementation", c.implementation, "assessmentProcedure", c.assessmentProcedure) END as "emassAp"`)
}
if ( inProjection?.includes('references') ) {
columns.push(`(select
coalesce
(
(
select json_arrayagg (json_object(
'creator', crm.creator,
'title', crm.title,
'version', crm.version,
'location', crm.location,
'indexDisa', crm.indexDisa,
'textRefNist', crm.textRefNist,
'parentControl', crm.parentControl
))
from cci_reference_map crm
where crm.cci = c.cci
),
json_array()
)
) as "references"`)
}
if ( inProjection?.includes('stigs') ) {
columns.push(`(select
coalesce
(
(
select json_arrayagg(stig)
from
(
select distinct json_object(
'benchmarkId', rv.benchmarkId,
'revisionStr', concat('V', rv.version, 'R', rv.release)
) as stig
from cci ci
left join rev_group_rule_cci_map rgrcc using (cci)
left join rev_group_rule_map rgr using (rgrId)
left join revision rv using (revId)
where ci.cci = c.cci and benchmarkId is not null
) as agg),
json_array()
)
) as "stigs"`)
}
const sql = dbUtils.makeQueryString({columns, joins, predicates, orderBy})
const [rows] = await dbUtils.pool.query(sql, predicates.binds)
return (rows[0])
}
/**
* Return a list of CCIs from a STIG revision
*
* benchmarkId String A path parameter that indentifies a STIG
* revisionStr String A path parameter that indentifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns List
**/
exports.getCcisByRevision = async function(benchmarkId, revisionStr, userObject) {
let columns = [
'c.cci',
'c.type',
`COALESCE((
SELECT JSON_ARRAYAGG(JSON_OBJECT(
"creator", crm.creator,
"title", crm.title,
"version", crm.version,
"location", crm.location,
"indexDisa", crm.indexDisa,
"textRefNist", crm.textRefNist,
"parentControl", crm.parentControl
))
FROM cci_reference_map crm
WHERE crm.cci = c.cci
), JSON_ARRAY()) AS "references"`
]
const orderBy = ['c.cci']
let joins = []
let predicates = {
statements: [],
binds: []
}
predicates.statements.push('r.benchmarkId = ?')
predicates.binds.push(benchmarkId)
if (revisionStr != 'latest') {
joins = ['revision r']
const {version, release} = dbUtils.parseRevisionStr(revisionStr)
predicates.statements.push('r.version = ?')
predicates.binds.push(version)
predicates.statements.push('r.release = ?')
predicates.binds.push(release)
}
else {
joins = ['current_rev r']
}
joins.push('LEFT JOIN rev_group_rule_map rgr using (revId)')
joins.push('INNER JOIN rev_group_rule_cci_map rgrcc using (rgrId)')
joins.push('INNER JOIN cci c using (cci)')
// joins.push('LEFT JOIN cci_reference_map crm using (cci)')
// CONSTRUCT MAIN QUERY
const sql = dbUtils.makeQueryString({columns, joins, predicates, orderBy})
const [rows] = await dbUtils.pool.query(sql, predicates.binds)
return rows
}
/**
* Return the rules, checks and fixes for a Group from a specified revision of a STIG.
* None
*
* benchmarkId String A path parameter that indentifies a STIG
* revisionStr String A path parameter that indentifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* groupId String A path parameter that indentifies a Group
* returns GroupObj
**/
exports.getGroupByRevision = async function(benchmarkId, revisionStr, groupId, projection, userObject) {
const rows = await _this.queryGroups( projection, {
benchmarkId: benchmarkId,
revisionStr: revisionStr,
groupId: groupId
})
return (rows[0])
}
/**
* Return the list of groups for the specified revision of a STIG.
*
* benchmarkId String A path parameter that indentifies a STIG
* revisionStr String A path parameter that indentifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns List
**/
exports.getGroupsByRevision = async function(benchmarkId, revisionStr, projection, userObject) {
return _this.queryGroups( projection, {
benchmarkId: benchmarkId,
revisionStr: revisionStr
})
}
/**
* Return metadata for the specified revision of a STIG
*
* benchmarkId String A path parameter that indentifies a STIG
* revisionStr String A path parameter that indentifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns Revision
**/
exports.getRevisionByString = async function({benchmarkId, revisionStr, grants, elevate = false}) {
const {
unrestrictedCollectionIds,
requesterGrantIds,
requireCteAcls
} = parseGrants(grants, elevate)
const ctes = []
if (requireCteAcls) {
ctes.push(dbUtils.cteAclEffective({grantIds: requesterGrantIds}))
}
ctes.push(cteRevCollection({
elevate,
unrestrictedCollectionIds,
hasRestrictions: !!requesterGrantIds.length
}))
const ro = dbUtils.parseRevisionStr(revisionStr)
const columns = [
`${ro.table_alias}.benchmarkId`,
`concat('V', ${ro.table_alias}.version, 'R', ${ro.table_alias}.release) as "revisionStr"`,
`cast(${ro.table_alias}.version as char) as version`,
` ${ro.table_alias}.release`,
`date_format(${ro.table_alias}.benchmarkDateSql,'%Y-%m-%d') as "benchmarkDate"`,
`${ro.table_alias}.status`,
`${ro.table_alias}.statusDate`,
`${ro.table_alias}.ruleCount`,
`coalesce(rc.collectionIds,json_array()) as collectionIds`
]
const joins = [
`${ro.table} ${ro.table_alias}`,
`left join cte_rev_collection rc on ${ro.table_alias}.revId = rc.revId`
]
const predicates = {
statements: [`${ro.table_alias}.benchmarkId = ?`],
binds: [benchmarkId]
}
if (ro.version) {
predicates.statements.push(
'r.version = ?',
'r.release = ? ')
predicates.binds.push(ro.version, ro.release)
}
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows[0])
}
/**
* Return a list of revisions for the specified STIG
*
* benchmarkId String A path parameter that indentifies a STIG
* returns List
**/
exports.getRevisionsByBenchmarkId = async function({benchmarkId, grants, userObject, elevate = false}) {
const {
unrestrictedCollectionIds,
requesterGrantIds,
requireCteAcls
} = parseGrants(grants, elevate)
const ctes = []
if (requireCteAcls) {
ctes.push(dbUtils.cteAclEffective({grantIds: requesterGrantIds}))
}
ctes.push(cteRevCollection({
elevate,
unrestrictedCollectionIds,
hasRestrictions: !!requesterGrantIds.length
}))
const columns = [
'r.benchmarkId',
`concat('V', r.version, 'R', r.release) as "revisionStr"`,
'CAST(r.version as char) as version',
'r.release',
`date_format(r.benchmarkDateSql,'%Y-%m-%d') as "benchmarkDate"`,
'r.status',
'r.statusDate',
'r.marking',
'r.ruleCount',
'coalesce(rc.collectionIds,json_array()) as collectionIds'
]
const joins = [
'revision r',
'left join cte_rev_collection rc on r.revId = rc.revId'
]
const predicates = {
statements: ['r.benchmarkId = ?'],
binds: [benchmarkId]
}
const orderBy = ['r.benchmarkDateSql desc']
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return (rows)
}
/**
* Return the defintion and associated checks and fixes for the specified Rule
*
* ruleId String A path parameter that indentifies a Rule
* returns Rule
**/
exports.getRuleByRuleId = async function(ruleId, projection, userObject) {
return _this.queryRules( ruleId, projection )
}
/**
* Return rule data for the specified Rule in a revision of a STIG.
*
* benchmarkId String A path parameter that indentifies a STIG
* revisionStr String A path parameter that indentifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns List
**/
exports.getRuleByRevision = async function(benchmarkId, revisionStr, ruleId, projection, userObject) {
const rows = await _this.queryBenchmarkRules( benchmarkId, revisionStr, projection, {
ruleId: ruleId
})
return (rows[0])
}
/**
* Return rule data for the specified revision of a STIG.
*
* benchmarkId String A path parameter that indentifies a STIG
* revisionStr String A path parameter that indentifies a STIG revision [ V{version_num}R{release_num} | 'latest' ]
* returns List
**/
exports.getRulesByRevision = async function(benchmarkId, revisionStr, projection, userObject) {
return _this.queryBenchmarkRules( benchmarkId, revisionStr, projection, {} )
}
/**
* Return a list of available STIGs
*
* title String A string found anywhere in a STIG title (optional)
* returns List
**/
exports.getSTIGs = async function(title, projections, userObject, elevate) {
return _this.queryStigs({
filter: {title},
projections,
grants: userObject.grants,
elevate
})
}
/**
* Return properties of the specified STIG
*
* benchmarkId String A path parameter that indentifies a STIG
* returns STIG
**/
exports.getStigById = async function(benchmarkId, userObject, elevate) {
const rows = await _this.queryStigs({
filter: {benchmarkId},
projections: ['revisions'],
grants: userObject.grants,
elevate
})
return (rows[0])
}
exports.getRevisionStrsByBenchmarkId = async function (benchmarkId) {
const sql = `SELECT
concat('V', r.version, 'R', r.release) as "revisionStr"
FROM
revision r
WHERE
r.benchmarkId = ?`
const [rows] = await dbUtils.pool.query(sql, [benchmarkId])
return rows.map( row => row.revisionStr)
}
exports.getRevisionStrsByBenchmarkIds = async function (benchmarkIds) {
const sql = `SELECT
r.benchmarkId,
json_arrayagg(concat('V', r.version, 'R', r.release)) as "revisionStrs"
FROM
revision r
WHERE
r.benchmarkId IN ?
GROUP BY
r.benchmarkId`
const [rows] = await dbUtils.pool.query(sql, [[benchmarkIds]])
const returnObj = {}
for (const row of rows) {
returnObj[row.benchmarkId] = row.revisionStrs
}
return returnObj
}
exports.getHighestMarkingByRevisions = async function (stigRevisions) {
if (stigRevisions.length === 0) {
return 'U'
}
const revisionCriteria = stigRevisions.map(() => {
return `(r.benchmarkId = ? AND r.revisionStr = ?)`
}).join(' OR ')
const binds = []
for (const {benchmarkId, revisionStr} of stigRevisions) {
binds.push(benchmarkId, revisionStr)
}
const sql = `
SELECT r.marking
FROM revision r
WHERE (${revisionCriteria}) AND r.marking IS NOT NULL
ORDER BY r.marking ASC
LIMIT 1
`
const [rows] = await dbUtils.pool.query(sql, binds)
if (rows.length === 0) {
return 'U'
}
return rows[0].marking || 'U'
}
================================================
FILE: api/source/service/UserService.js
================================================
'use strict';
const config = require('../utils/config');
const SmError = require('../utils/error');
const dbUtils = require('./utils')
const _this = this
/**
Generalized queries for users
**/
exports.queryUsers = async function (inProjection, inPredicates, elevate, userObject) {
const ctes = []
let needsCollectionGrantees = false
const columns = [
'CAST(ud.userId as char) as userId',
'ud.username',
'ud.lastAccess',
`json_extract(
ud.lastClaims, ?
) as email`,
`COALESCE(json_unquote(json_extract(
ud.lastClaims, ?
)), ud.username) as displayName`,
`json_object(
'create_collection', 'create_collection' member of(JSON_VALUE(ud.lastClaims, ? default '[]' on empty)),
'admin', 'admin' member of(JSON_VALUE(ud.lastClaims, ? default '[]' on empty))
) as 'privileges'`,
'ud.status',
"date_format(ud.statusDate, '%Y-%m-%dT%TZ') as statusDate",
'CAST(ud.statusUser as char) as statusUser'
]
const joins = new Set([
'user_data ud'
])
const groupBy = ['ud.userId']
const orderBy = ['ud.username']
// PROJECTIONS
if (inProjection?.includes('collectionGrants')) {
needsCollectionGrantees = true
joins.add('left join cteGrantees cgs on ud.userId = cgs.userId')
joins.add('left join enabled_collection c on cgs.collectionId = c.collectionId')
columns.push(`case when count(cgs.collectionId) > 0
then
${dbUtils.jsonArrayAggDistinct(`json_object(
'collection', json_object(
'collectionId', CAST(cgs.collectionId as char),
'name', c.name
),
'roleId', cgs.roleId,
'grantees', cgs.grantees
)`)}
else json_array()
end as collectionGrants`)
}
if (inProjection?.includes('statistics')) {
needsCollectionGrantees = true
joins.add('left join cteGrantees cgs on ud.userId = cgs.userId')
columns.push(`json_object(
'created', date_format(ud.created, '%Y-%m-%dT%TZ'),
'collectionGrantCount', count(distinct cgs.collectionId),
'lastClaims', ud.lastClaims
) as statistics`)
groupBy.push(
'ud.lastAccess',
'ud.lastClaims'
)
}
if (inProjection?.includes('userGroups')) {
joins.add('left join user_group_user_map ugu on ud.userId = ugu.userId')
joins.add('left join user_group ug on ugu.userGroupId = ug.userGroupId')
columns.push(`CASE WHEN COUNT(ugu.userGroupId) > 0
THEN cast(concat('[', group_concat( distinct JSON_OBJECT(
'userGroupId', cast(ugu.userGroupId as char),
'name', ug.name
)), ']') as json)
ELSE json_array()
END as userGroups`)
}
if(inProjection?.includes('webPreferences')) {
columns.push(`ud.webPreferences`)
}
// PREDICATES
let predicates = {
statements: [],
binds: [
`$.${config.oauth.claims.email}`,
`$.${config.oauth.claims.name}`,
`$.${config.oauth.claims.privileges}`,
`$.${config.oauth.claims.privileges}`
]
}
if (inPredicates.userId) {
predicates.statements.push('ud.userId = ?')
predicates.binds.push(inPredicates.userId)
}
if ( inPredicates.username ) {
let matchStr = '= ?'
if ( inPredicates.usernameMatch && inPredicates.usernameMatch !== 'exact') {
matchStr = 'LIKE ?'
switch (inPredicates.usernameMatch) {
case 'startsWith':
inPredicates.username = `${inPredicates.username}%`
break
case 'endsWith':
inPredicates.username = `%${inPredicates.username}`
break
case 'contains':
inPredicates.username = `%${inPredicates.username}%`
break
}
}
predicates.statements.push(`ud.username ${matchStr}`)
predicates.binds.push(inPredicates.username)
}
if (inPredicates.privilege) {
predicates.statements.push(
`JSON_CONTAINS(JSON_EXTRACT(ud.lastClaims, ?), ?) `
)
predicates.binds.push(`$.${config.oauth.claims.privileges}`, JSON.stringify([inPredicates.privilege]))
}
if (inPredicates.status) {
predicates.statements.push('ud.status = ?')
predicates.binds.push(inPredicates.status)
}
if (needsCollectionGrantees) {
ctes.push(dbUtils.sqlGrantees({userId: inPredicates.userId, username: inPredicates.username, returnCte: true}))
}
// CONSTRUCT MAIN QUERY
const sql = dbUtils.makeQueryString({ctes, columns, joins, predicates, groupBy, orderBy, format: true})
let [rows] = await dbUtils.pool.query(sql)
return (rows)
}
exports.addOrUpdateUser = async function (writeAction, userId, body, projection, elevate, userObject, svcStatus = {}) {
let connection
try {
// CREATE: userId will be null
// REPLACE/UPDATE: userId is not null
// Extract or initialize non-scalar properties to separate variables
let { collectionGrants, userGroups, ...userFields } = body
connection = await dbUtils.pool.getConnection()
connection.config.namedPlaceholders = true
async function transaction () {
await connection.query('START TRANSACTION');
// Process scalar properties
let binds
if (writeAction === dbUtils.WRITE_ACTION.CREATE) {
// INSERT into user_data
binds = {...userFields}
let sqlInsert =
`INSERT INTO
user_data
( username, status )
VALUES
(:username, :status )`
let [result] = await connection.query(sqlInsert, binds)
userId = result.insertId
}
else if (writeAction === dbUtils.WRITE_ACTION.UPDATE || writeAction === dbUtils.WRITE_ACTION.REPLACE) {
binds = {
userId: userId,
values: userFields
}
if (Object.keys(binds.values).length > 0) {
let sqlUpdate =
`UPDATE
user_data
SET
:values
WHERE
userid = :userId`
await connection.query(sqlUpdate, binds)
}
}
else {
throw new Error('Invalid writeAction')
}
// Process grants if present
if (collectionGrants) {
if ( writeAction !== dbUtils.WRITE_ACTION.CREATE ) {
// DELETE from collection_grant
const binds = [userId]
let sqlDeleteCollGrant = 'DELETE FROM collection_grant where userId = ?'
if (collectionGrants.length > 0) {
const collectionIds = collectionGrants.map(grant => grant.collectionId)
sqlDeleteCollGrant += ' and collectionId NOT IN (?)'
binds.push(collectionIds)
}
await connection.query(sqlDeleteCollGrant, binds)
}
if (collectionGrants.length > 0) {
let sqlInsertCollGrant = `
INSERT INTO
collection_grant (userId, collectionId, roleId)
VALUES
? as new
ON DUPLICATE KEY UPDATE
roleId = new.roleId`
binds = collectionGrants.map( grant => [userId, grant.collectionId, grant.roleId])
// INSERT into collection_grant
await connection.query(sqlInsertCollGrant, [binds] )
}
}
if (userGroups) {
if ( writeAction !== dbUtils.WRITE_ACTION.CREATE ) {
await connection.query('DELETE FROM user_group_user_map where userId = ?', [userId])
}
if (userGroups.length > 0) {
await connection.query(
`INSERT INTO user_group_user_map (userGroupId, userId) VALUES ?`,
[userGroups.map( userGroup => [userGroup, userId])]
)
}
}
// Commit the changes
await connection.commit()
}
await dbUtils.retryOnDeadlock(transaction, svcStatus)
}
catch (err) {
await connection.rollback()
throw err
}
finally {
if (typeof connection !== 'undefined') {
await connection.release()
}
}
// Fetch the new or updated User for the response
try {
let row = await _this.getUserByUserId(userId, projection, elevate, userObject)
return row
}
catch (err) {
throw ( {status: 500, message: err.message, stack: err.stack} )
}
}
/**
* Create a User
*
* body UserAssign
* projection List Additional properties to include in the response. (optional)
* returns List
**/
exports.createUser = async function(body, projection, elevate, userObject, svcStatus = {}) {
let row = await _this.addOrUpdateUser(dbUtils.WRITE_ACTION.CREATE, null, body, projection, elevate, userObject, svcStatus)
return (row)
}
/**
* Delete a User
*
* projection List Additional properties to include in the response. (optional)
* returns UserProjected
**/
exports.deleteUser = async function(userId, projection, elevate, userObject) {
try {
let row = await _this.queryUsers(projection, { userId: userId }, elevate, userObject)
let sqlDelete = `DELETE FROM user_data where userId = ?`
await dbUtils.pool.query(sqlDelete, [userId])
return (row[0])
}
catch (err) {
throw ( {status: 500, message: err.message, stack: err.stack} )
}
}
/**
* Return a User
*
* userId Integer Selects a User
* projection List Additional properties to include in the response. (optional)
* returns UserProjected
**/
exports.getUserByUserId = async function(userId, projection, elevate, userObject) {
try {
let rows = await _this.queryUsers( projection, {
userId: userId
}, elevate, userObject)
return (rows[0])
}
catch(err) {
throw ( {status: 500, message: err.message, stack: err.stack} )
}
}
exports.getUserByUsername = async function(username, projection, elevate, userObject) {
try {
let rows = await _this.queryUsers( projection, {
username: username
}, elevate, userObject)
return (rows[0])
}
catch(err) {
throw ( {status: 500, message: err.message, stack: err.stack} )
}
}
exports.getUsers = async function(username, usernameMatch, privilege, status, projection, elevate, userObject) {
try {
let rows = await _this.queryUsers( projection, {
username,
usernameMatch,
privilege,
status
}, elevate, userObject)
return (rows)
}
catch(err) {
throw ( {status: 500, message: err.message, stack: err.stack} )
}
}
exports.replaceUser = async function( userId, body, projection, elevate, userObject, svcStatus = {} ) {
const row = await _this.addOrUpdateUser(dbUtils.WRITE_ACTION.REPLACE, userId, body, projection, elevate, userObject, svcStatus)
return (row)
}
exports.updateUser = async function( userId, body, projection, elevate, userObject, svcStatus = {} ) {
if (body.status === 'unavailable' && (body.collectionGrants?.length || body.userGroups?.length)) {
throw new SmError.UserInconsistentError()
}
let row = await _this.addOrUpdateUser(dbUtils.WRITE_ACTION.UPDATE, userId, body, projection, elevate, userObject, svcStatus)
return (row)
}
exports.setUserData = async function (userObject, fields) {
if (userObject.userId) {
await dbUtils.pool.query(`UPDATE user_data SET ? WHERE userId = ?`, [fields, userObject.userId])
return userObject.userId
}
else {
const [result] = await dbUtils.pool.query(`INSERT INTO user_data SET ?`, [{username: userObject.username, ...fields}])
return result.insertId
}
}
exports.addOrUpdateUserGroup = async function ({userGroupId, userGroupFields, userIds, collectionGrants, createdUserId, modifiedUserId, svcStatus = {}}) {
// CREATE: userGroupId is falsey
// REPLACE/UPDATE: userGroupId is not falsey
const isUpdate = !!userGroupId
const sqlInsertUserGroup = `INSERT into user_group (name, description, createdUserId, modifiedUserId) VALUES (?,?,?,?)`
const sqlUpdateUserGroup = `UPDATE user_group SET ? WHERE userGroupId = ?`
const sqlInsertUserGroupUserMap = `INSERT into user_group_user_map (userGroupId, userId) VALUES ?`
const sqlDeleteUserGroupUserMap = `DELETE from user_group_user_map WHERE userGroupId = ?`
async function transactionFn (connection) {
if (Object.keys(userGroupFields).length) {
const sql = isUpdate ? sqlUpdateUserGroup : sqlInsertUserGroup
const binds = isUpdate ? [userGroupFields, userGroupId] : [userGroupFields.name, userGroupFields.description, createdUserId, modifiedUserId]
const [resultUserGroup] = await connection.query(sql, binds)
userGroupId = isUpdate ? userGroupId : resultUserGroup.insertId
}
if (userIds) {
if (isUpdate) {
await connection.query(sqlDeleteUserGroupUserMap, [userGroupId])
}
if (userIds.length) {
const binds = userIds.map( userId => [userGroupId, userId])
await connection.query(
sqlInsertUserGroupUserMap,
[binds]
)
}
}
// Process grants if present
if (collectionGrants) {
if (isUpdate) {
// DELETE from collection_grant
const binds = [userGroupId]
let sqlDeleteCollGrant = 'DELETE FROM collection_grant where userGroupId = ?'
if (collectionGrants.length > 0) {
const collectionIds = collectionGrants.map(grant => grant.collectionId)
sqlDeleteCollGrant += ' and collectionId NOT IN (?)'
binds.push(collectionIds)
}
await connection.query(sqlDeleteCollGrant, binds)
}
if (collectionGrants.length > 0) {
let sqlInsertCollGrant = `
INSERT INTO
collection_grant (userGroupId, collectionId, roleId)
VALUES
? as new
ON DUPLICATE KEY UPDATE
roleId = new.roleId`
const binds = collectionGrants.map( grant => [userGroupId, grant.collectionId, grant.roleId])
// INSERT into collection_grant
await connection.query(sqlInsertCollGrant, [binds] )
}
}
return userGroupId
}
return dbUtils.retryOnDeadlock2({
transactionFn,
statusObj: svcStatus
})
}
exports.queryUserGroups = async function ({projections = [], filters = {}, elevate = false, userObject = {}}) {
// query components
const columns = [
'CAST(ug.userGroupId as char) as userGroupId',
'ug.name',
'ug.description'
]
const joins = new Set([`user_group ug`])
const groupBy = new Set()
const orderBy = ['name']
const predicates = {
statements: [],
binds: []
}
// predicates
if (filters.userGroupId) {
predicates.statements.push('ug.userGroupId = ?')
predicates.binds.push(filters.userGroupId)
}
// projections
if (projections.includes('attributions')) {
joins.add('left join user_data udCreated on ug.createdUserId = udCreated.userId')
joins.add('left join user_data udModified on ug.modifiedUserId = udModified.userId')
columns.push(`json_object(
'created', json_object(
'userId', CAST(ug.createdUserId AS CHAR),
'username', udCreated.username,
'ts', DATE_FORMAT(ug.createdDate, '%Y-%m-%dT%H:%i:%sZ')
),
'modified', json_object(
'userId', CAST(ug.modifiedUserId AS CHAR),
'username', udModified.username,
'ts', DATE_FORMAT(ug.modifiedDate, '%Y-%m-%dT%H:%i:%sZ')
)
) as attributions`)
}
if (projections.includes('users')) {
joins.add('left join user_group_user_map ugu using (userGroupId)')
joins.add('left join user_data udUser on ugu.userId = udUser.userId')
groupBy.add('ug.userGroupId')
columns.push(`CASE WHEN count(ugu.userId)=0
THEN json_array()
ELSE cast(concat('[', group_concat(distinct json_object(
'userId', cast(ugu.userId as char),
'username', udUser.username,
'displayName', COALESCE(json_unquote(json_extract(
udUser.lastClaims, '$.${config.oauth.claims.name}'
)), udUser.username)
)
), ']') as json)
END as users`)
}
if (projections.includes('collections') || projections.includes('collectionGrants')) {
joins.add('left join collection_grant cgg using (userGroupId)')
joins.add('left join enabled_collection on cgg.collectionId = enabled_collection.collectionId')
groupBy.add('ug.userGroupId')
columns.push(`CASE WHEN count(cgg.collectionId)=0
THEN json_array()
ELSE cast(concat('[', group_concat(distinct json_object(
'roleId', cgg.roleId,
'collection', json_object(
'collectionId', cast(cgg.collectionId as char),
'name', enabled_collection.name
))
), ']') as json)
END as collectionGrants`)
}
const sql = dbUtils.makeQueryString({columns, joins, predicates, groupBy, orderBy, format: true})
const [rows] = await dbUtils.pool.query(sql)
return rows
}
exports.deleteUserGroup = async function({userGroupId}) {
const sqlDeleteUserGroup = `DELETE from user_group WHERE userGroupId = ?`
await dbUtils.pool.query(sqlDeleteUserGroup, [userGroupId])
return userGroupId
}
exports.getUserObject = async function (username) {
const sql = `
select
userId,
username,
lastAccess,
lastClaims,
status,
(select
coalesce(json_objectagg(
dt2.collectionId, json_object(
'collectionId', dt2.collectionId,
'name', dt2.name,
'roleId', dt2.roleId,
'grantIds', dt2.grantIds)), json_object())
from
(select
cg.collectionId,
c.name,
cg.roleId,
json_array(cg.grantId) as grantIds
from
collection_grant cg
inner join enabled_collection c on (cg.collectionId = c.collectionId)
left join user_data ud2 on cg.userId = ud2.userId
where
ud2.userId = ud.userId
union
select
collectionId,
name,
roleId,
grantIds
from
(select
ROW_NUMBER() OVER(PARTITION BY ugu.userId, cg.collectionId ORDER BY cg.roleId desc) as rn,
cg.collectionId,
c.name,
cg.roleId,
json_arrayagg(cg.grantId) OVER (PARTITION BY ugu.userId, cg.collectionId, cg.roleId) as grantIds
from
collection_grant cg
inner join enabled_collection c on (cg.collectionId = c.collectionId)
left join user_group_user_map ugu on cg.userGroupId = ugu.userGroupId
left join user_group ug on ugu.userGroupId = ug.userGroupId
left join user_data ud3 on ugu.userId = ud3.userId
left join collection_grant cgDirect on (cg.collectionId = cgDirect.collectionId and ugu.userId = cgDirect.userId)
where
cg.userGroupId is not null
and cgDirect.userId is null
and ud3.userId = ud.userId) dt
where
dt.rn = 1) dt2) as grants
from
user_data ud
where
ud.username = ?`
const [rows] = await dbUtils.pool.query(sql, [username])
return rows[0]
}
exports.getUserWebPreferences = async function (userId) {
const sql = `SELECT webPreferences FROM user_data WHERE userId = ?`
const [rows] = await dbUtils.pool.query(sql, [userId])
return rows[0]?.webPreferences
}
exports.patchUserWebPreferences = async function (userId, preferences) {
const sql = `UPDATE user_data SET webPreferences = JSON_MERGE_PATCH(webPreferences, ?) WHERE userId = ?`
await dbUtils.pool.query(sql, [JSON.stringify(preferences), userId])
return preferences
}
================================================
FILE: api/source/service/migrations/0000.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0001.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0002.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0003.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0004.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0005.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0006.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const fs = require('fs')
module.exports = {
up: async (pool) => {
const migrationName = path.basename(__filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'up')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
},
down: async(pool)=> {
try {
const migrationName = path.basename(__filename, '.js')
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
const importer = new Importer(pool)
const dir = path.join(__dirname, 'sql', migrationName, 'down')
const files = await fs.promises.readdir(dir)
for (const file of files) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message})
throw (e)
}
}
}
================================================
FILE: api/source/service/migrations/0007.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
'SET FOREIGN_KEY_CHECKS=0',
'ALTER TABLE stig MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'ALTER TABLE stig_asset_map MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'ALTER TABLE current_group_rule MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'ALTER TABLE current_rev MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'ALTER TABLE revision MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'ALTER TABLE rule_oval_map MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'ALTER TABLE stats_asset_stig MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs',
'SET FOREIGN_KEY_CHECKS=1'
]
const downMigration = [
'SET FOREIGN_KEY_CHECKS=0',
'ALTER TABLE stig MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'ALTER TABLE stig_asset_map MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'ALTER TABLE current_group_rule MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'ALTER TABLE current_rev MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'ALTER TABLE revision MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'ALTER TABLE rule_oval_map MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'ALTER TABLE stats_asset_stig MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_ci',
'SET FOREIGN_KEY_CHECKS=1'
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0008.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
'ALTER TABLE asset MODIFY COLUMN name VARCHAR(255) NOT NULL',
'ALTER TABLE asset MODIFY COLUMN ip VARCHAR(255) NULL DEFAULT NULL',
'ALTER TABLE asset MODIFY COLUMN mac VARCHAR(255) NULL DEFAULT NULL'
]
const downMigration = [
'ALTER TABLE asset MODIFY COLUMN name VARCHAR(45) NOT NULL',
'ALTER TABLE asset MODIFY COLUMN ip VARCHAR(45) NULL DEFAULT NULL',
'ALTER TABLE asset MODIFY COLUMN mac VARCHAR(17) NULL DEFAULT NULL'
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0009.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
'ALTER TABLE review ADD COLUMN metadata JSON NOT NULL DEFAULT (JSON_OBJECT())'
]
const downMigration = [
'ALTER TABLE review DROP COLUMN metadata'
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0010.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`
ALTER TABLE stig_asset_map
ADD COLUMN minTs datetime DEFAULT NULL,
ADD COLUMN maxTs datetime DEFAULT NULL,
ADD COLUMN savedManual int DEFAULT NULL,
ADD COLUMN savedAuto int DEFAULT NULL,
ADD COLUMN submittedManual int DEFAULT NULL,
ADD COLUMN submittedAuto int DEFAULT NULL,
ADD COLUMN rejectedManual int DEFAULT NULL,
ADD COLUMN rejectedAuto int DEFAULT NULL,
ADD COLUMN acceptedManual int DEFAULT NULL,
ADD COLUMN acceptedAuto int DEFAULT NULL,
ADD COLUMN highCount int DEFAULT NULL,
ADD COLUMN mediumCount int DEFAULT NULL,
ADD COLUMN lowCount int DEFAULT NULL;
`,
`
UPDATE stig_asset_map sam
INNER JOIN stats_asset_stig sas ON sam.benchmarkId = sas.benchmarkId AND sam.assetId = sas.assetId
SET sam.minTs = sas.minTs
, sam.maxTs = sas.maxTs
, sam.savedManual = sas.savedManual
, sam.savedAuto = sas.savedAuto
, sam.submittedManual = sas.submittedManual
, sam.submittedAuto = sas.submittedAuto
, sam.rejectedManual = sas.rejectedManual
, sam.rejectedAuto = sas.rejectedAuto
, sam.acceptedManual = sas.acceptedManual
, sam.acceptedAuto = sas.acceptedAuto
, sam.highCount = sas.highCount
, sam.mediumCount = sas.mediumCount
, sam.lowCount = sas.lowCount
`,
`DROP TABLE stats_asset_stig`
]
const downMigration = [
`
CREATE TABLE stats_asset_stig (
id int NOT NULL AUTO_INCREMENT,
assetId int DEFAULT NULL,
benchmarkId varchar(255) DEFAULT NULL,
minTs datetime DEFAULT NULL,
maxTs datetime DEFAULT NULL,
savedManual int DEFAULT NULL,
savedAuto int DEFAULT NULL,
submittedManual int DEFAULT NULL,
submittedAuto int DEFAULT NULL,
rejectedManual int DEFAULT NULL,
rejectedAuto int DEFAULT NULL,
acceptedManual int DEFAULT NULL,
acceptedAuto int DEFAULT NULL,
highCount int DEFAULT NULL,
mediumCount int DEFAULT NULL,
lowCount int DEFAULT NULL,
PRIMARY KEY (id),
UNIQUE KEY INDEX_2_2_C (assetId,benchmarkId),
KEY FK_STATS_ASSET_STIG_2 (benchmarkId),
CONSTRAINT FOREIGN KEY (assetId) REFERENCES asset (assetId) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
`,
`ALTER TABLE stats_asset_stig MODIFY benchmarkId VARCHAR(255) COLLATE utf8mb4_0900_as_cs`,
`
INSERT INTO stats_asset_stig(benchmarkId, assetId, minTs, maxTs, savedManual, savedAuto,
submittedManual, submittedAuto, rejectedManual, rejectedAuto, acceptedManual, acceptedAuto,
highCount, mediumCount, lowCount)
SELECT benchmarkId, assetId, minTs, maxTs, savedManual, savedAuto,
submittedManual, submittedAuto, rejectedManual, rejectedAuto, acceptedManual, acceptedAuto,
highCount, mediumCount, lowCount
FROM stig_asset_map sam
`,
`
ALTER TABLE stig_asset_map
DROP COLUMN minTs,
DROP COLUMN maxTs,
DROP COLUMN savedManual,
DROP COLUMN savedAuto,
DROP COLUMN submittedManual,
DROP COLUMN submittedAuto,
DROP COLUMN rejectedManual,
DROP COLUMN rejectedAuto,
DROP COLUMN acceptedManual,
DROP COLUMN acceptedAuto,
DROP COLUMN highCount,
DROP COLUMN mediumCount,
DROP COLUMN lowCount;
`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0011.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE review
CHANGE COLUMN \`resultComment\` \`detail\` MEDIUMTEXT DEFAULT NULL,
CHANGE COLUMN \`actionComment\` \`comment\` MEDIUMTEXT DEFAULT NULL,
CHANGE COLUMN \`ts\` \`ts\` DATETIME NOT NULL,
CHANGE COLUMN \`rejecttext\` \`statusText\` VARCHAR(255) DEFAULT NULL AFTER \`statusId\`,
CHANGE COLUMN \`rejectUserId\` \`statusUserId\` INT DEFAULT NULL AFTER \`statusText\`,
ADD COLUMN \`statusTs\` DATETIME DEFAULT NULL AFTER \`statusUserId\`,
ADD COLUMN \`touchTs\` DATETIME GENERATED ALWAYS AS (GREATEST(ts,statusTs)) STORED,
DROP COLUMN \`actionId\``,
`UPDATE review SET
statusText = CASE WHEN statusId = 2 THEN statusText ELSE NULL END,
statusUserId = userId,
statusTs = ts`,
`ALTER TABLE review_history
CHANGE COLUMN \`resultComment\` \`detail\` MEDIUMTEXT DEFAULT NULL,
CHANGE COLUMN \`actionComment\` \`comment\` MEDIUMTEXT DEFAULT NULL,
CHANGE COLUMN \`rejecttext\` \`statusText\` VARCHAR(255) DEFAULT NULL AFTER \`statusId\`,
CHANGE COLUMN \`rejectUserId\` \`statusUserId\` INT DEFAULT NULL AFTER \`statusText\`,
ADD COLUMN \`statusTs\` DATETIME DEFAULT NULL AFTER \`statusUserId\`,
ADD COLUMN \`touchTs\` DATETIME DEFAULT NULL,
DROP COLUMN \`actionId\``,
`UPDATE review_history SET
statusText = CASE WHEN statusId = 2 THEN statusText ELSE NULL END,
statusUserId = userId,
statusTs = ts,
touchTs = ts`,
'DROP TABLE IF EXISTS `action`',
]
const downMigration = [
'ALTER TABLE `review` RENAME COLUMN `detail` TO `resultComment`',
'ALTER TABLE `review` RENAME COLUMN `comment` TO `actionComment`',
`CREATE TABLE action (
actionId int(11) NOT NULL,
api varchar(16) NOT NULL,
en varchar(64) NOT NULL,
PRIMARY KEY (actionId)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`,
"INSERT INTO `action` VALUES (1,'remediate','Remediate'),(2,'mitigate','Mitigate'),(3,'exception','Exception')",
'ALTER TABLE `review` ADD COLUMN `actionId` INT DEFAULT NULL',
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0012.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE collection DROP COLUMN workflow, ADD COLUMN settings JSON NOT NULL AFTER description`,
`update collection
set settings = JSON_OBJECT(
'fields', JSON_OBJECT(
'comment', JSON_OBJECT(
'enabled', COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.fieldSettings', '$.commentEnabled')), 'findings'),
'required', COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.fieldSettings', '$.commentRequired')), 'findings')
),
'detail', JSON_OBJECT(
'enabled', COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.fieldSettings', '$.detailEnabled')), 'always'),
'required', COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.fieldSettings', '$.detailRequired')), 'always')
)
),
'status', JSON_OBJECT(
'canAccept', CAST(COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.statusSettings', '$.canAccept')), cast(true as json)) as json),
'minAcceptGrant', CAST(COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.statusSettings', '$.minGrant')), 3) as json),
'resetCriteria', COALESCE(JSON_UNQUOTE(JSON_EXTRACT(metadata->>'$.statusSettings', '$.resetCriteria')), 'result')
)
)`,
`update collection set metadata = JSON_REMOVE(metadata, '$.fieldSettings', '$.statusSettings')`
]
const downMigration = [
`update collection set metadata = JSON_INSERT(metadata,
'$.fieldSettings', CAST(
JSON_OBJECT(
'detailEnabled', JSON_EXTRACT(settings, '$.fields.detail.enabled'),
'detailRequired', JSON_EXTRACT(settings, '$.fields.detail.required'),
'commentEnabled', JSON_EXTRACT(settings, '$.fields.comment.enabled'),
'commentRequired', JSON_EXTRACT(settings, '$.fields.comment.required')
)
as char),
'$.statusSettings', CAST(
JSON_OBJECT(
'canAccept', JSON_EXTRACT(settings, '$.status.canAccept'),
'minGrant', JSON_EXTRACT(settings, '$.status.minAcceptGrant'),
'resetCriteria', JSON_EXTRACT(settings, '$.status.resetCriteria')
)
as char)
)`,
'ALTER TABLE `collection` DROP COLUMN settings, ADD COLUMN `workflow` VARCHAR(45) DEFAULT "emass"'
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0013.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`CREATE TABLE collection_label (
clId INT NOT NULL AUTO_INCREMENT,
collectionId INT NOT NULL,
name VARCHAR(36) NOT NULL,
description VARCHAR(45) NULL,
color VARCHAR(6) NOT NULL,
uuid BINARY(16) NOT NULL,
PRIMARY KEY (clId),
KEY index4 (uuid),
UNIQUE KEY colname (collectionId,name),
CONSTRAINT fk_collection_label_1
FOREIGN KEY (collectionId)
REFERENCES collection (collectionId)
ON DELETE CASCADE
ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
`,
`CREATE TABLE collection_label_asset_map (
claId int NOT NULL AUTO_INCREMENT,
assetId int NOT NULL,
clId int NOT NULL,
PRIMARY KEY (claId),
KEY fk_collection_label_asset_map_2 (clId),
UNIQUE KEY index4 (assetId,clId),
CONSTRAINT fk_collection_label_asset_map_1 FOREIGN KEY (assetId) REFERENCES asset (assetId) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT fk_collection_label_asset_map_2 FOREIGN KEY (clId) REFERENCES collection_label (clId) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
`
]
const downMigration = [
`drop table collection_label_asset_map`,
`drop table collection_label`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0014.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE review ADD COLUMN resultEngine JSON DEFAULT NULL, ALGORITHM=INSTANT`,
`ALTER TABLE review_history ADD COLUMN resultEngine JSON DEFAULT NULL, ALGORITHM=INSTANT`,
`UPDATE review SET resultEngine = JSON_OBJECT('type','scap','product','scc') WHERE autoResult = 1`,
`UPDATE review_history SET resultEngine = JSON_OBJECT('type','scap','product','scc') WHERE autoResult = 1`
]
const downMigration = [
`ALTER TABLE review DROP COLUMN resultEngine`,
`ALTER TABLE review_history DROP COLUMN resultEngine`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0015.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`UPDATE review SET resultEngine = NULL WHERE resultEngine = CAST('{"product":"scc","type":"scap"}' as JSON)`,
`UPDATE review_history SET resultEngine = NULL WHERE resultEngine = CAST('{"product":"scc","type":"scap"}' as JSON)`,
`ALTER TABLE review ADD COLUMN reProduct VARCHAR(255) GENERATED ALWAYS AS (resultEngine->>"$.product")`,
`ALTER TABLE review ADD INDEX idx_reProduct (reProduct)`,
`ALTER TABLE review ADD COLUMN reType VARCHAR(255) GENERATED ALWAYS AS (resultEngine->>"$.type")`,
`ALTER TABLE review ADD INDEX idx_reType (reType)`,
`ALTER TABLE review ADD COLUMN reAuthority VARCHAR(255) GENERATED ALWAYS AS (resultEngine->>"$.overrides[0].authority")`,
`ALTER TABLE review ADD INDEX idx_reAuthority (reAuthority)`,
`ALTER TABLE review_history ADD COLUMN reProduct VARCHAR(255) GENERATED ALWAYS AS (resultEngine->>"$.product")`,
`ALTER TABLE review_history ADD INDEX idx_reProduct (reProduct)`,
`ALTER TABLE review_history ADD COLUMN reType VARCHAR(255) GENERATED ALWAYS AS (resultEngine->>"$.type")`,
`ALTER TABLE review_history ADD INDEX idx_reType (reType)`,
`ALTER TABLE review_history ADD COLUMN reAuthority VARCHAR(255) GENERATED ALWAYS AS (resultEngine->>"$.overrides[0].authority")`,
`ALTER TABLE review_history ADD INDEX idx_reAuthority (reAuthority)`
]
const downMigration = [
'ALTER TABLE review DROP COLUMN reProduct',
'ALTER TABLE review DROP COLUMN reType',
'ALTER TABLE review DROP COLUMN reAuthority',
'ALTER TABLE review_history DROP COLUMN reProduct',
'ALTER TABLE review_history DROP COLUMN reType',
'ALTER TABLE review_history DROP COLUMN reAuthority'
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0016.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`
ALTER TABLE stig_asset_map
RENAME COLUMN savedManual TO saved,
RENAME COLUMN savedAuto TO savedResultEngine,
RENAME COLUMN submittedManual TO submitted,
RENAME COLUMN submittedAuto TO submittedResultEngine,
RENAME COLUMN rejectedManual to rejected,
RENAME COLUMN rejectedAuto TO rejectedResultEngine,
RENAME COLUMN acceptedManual TO accepted,
RENAME COLUMN acceptedAuto TO acceptedResultEngine,
ADD COLUMN notchecked int,
ADD COLUMN notcheckedResultEngine int,
ADD COLUMN notapplicable int,
ADD COLUMN notapplicableResultEngine int,
ADD COLUMN pass int,
ADD COLUMN passResultEngine int,
ADD COLUMN fail int,
ADD COLUMN failResultEngine int,
ADD COLUMN unknown int,
ADD COLUMN unknownResultEngine int,
ADD COLUMN error int,
ADD COLUMN errorResultEngine int,
ADD COLUMN notselected int,
ADD COLUMN notselectedResultEngine int,
ADD COLUMN informational int,
ADD COLUMN informationalResultEngine int,
ADD COLUMN fixed int,
ADD COLUMN fixedResultEngine int
`,
`
with source as
( select
sa.assetId,
sa.benchmarkId,
min(review.ts) as minTs,
max(review.ts) as maxTs,
sum(CASE WHEN review.statusId = 0 THEN 1 ELSE 0 END) as saved,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 0 THEN 1 ELSE 0 END) as savedResultEngine,
sum(CASE WHEN review.statusId = 1 THEN 1 ELSE 0 END) as submitted,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 1 THEN 1 ELSE 0 END) as submittedResultEngine,
sum(CASE WHEN review.statusId = 2 THEN 1 ELSE 0 END) as rejected,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 2 THEN 1 ELSE 0 END) as rejectedResultEngine,
sum(CASE WHEN review.statusId = 3 THEN 1 ELSE 0 END) as accepted,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 3 THEN 1 ELSE 0 END) as acceptedResultEngine,
sum(CASE WHEN review.resultId=4 and r.severity='high' THEN 1 ELSE 0 END) as highCount,
sum(CASE WHEN review.resultId=4 and r.severity='medium' THEN 1 ELSE 0 END) as mediumCount,
sum(CASE WHEN review.resultId=4 and r.severity='low' THEN 1 ELSE 0 END) as lowCount,
sum(CASE WHEN review.resultId = 1 THEN 1 ELSE 0 END) as notchecked,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 1 THEN 1 ELSE 0 END) as notcheckedResultEngine,
sum(CASE WHEN review.resultId = 2 THEN 1 ELSE 0 END) as notapplicable,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 2 THEN 1 ELSE 0 END) as notapplicableResultEngine,
sum(CASE WHEN review.resultId = 3 THEN 1 ELSE 0 END) as pass,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 3 THEN 1 ELSE 0 END) as passResultEngine,
sum(CASE WHEN review.resultId = 4 THEN 1 ELSE 0 END) as fail,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 4 THEN 1 ELSE 0 END) as failResultEngine,
sum(CASE WHEN review.resultId = 5 THEN 1 ELSE 0 END) as unknown,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 5 THEN 1 ELSE 0 END) as unknownResultEngine,
sum(CASE WHEN review.resultId = 6 THEN 1 ELSE 0 END) as error,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 6 THEN 1 ELSE 0 END) as errorResultEngine,
sum(CASE WHEN review.resultId = 7 THEN 1 ELSE 0 END) as notselected,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 7 THEN 1 ELSE 0 END) as notselectedResultEngine,
sum(CASE WHEN review.resultId = 8 THEN 1 ELSE 0 END) as informational,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 8 THEN 1 ELSE 0 END) as informationalResultEngine,
sum(CASE WHEN review.resultId = 9 THEN 1 ELSE 0 END) as fixed,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 9 THEN 1 ELSE 0 END) as fixedResultEngine
from
asset a
left join stig_asset_map sa using (assetId)
left join current_group_rule cgr using (benchmarkId)
left join rule r using (ruleId)
left join review on (r.ruleId=review.ruleId and review.assetId=sa.assetId)
group by
sa.assetId,
sa.benchmarkId
)
update stig_asset_map sam
inner join source on sam.assetId = source.assetId and source.benchmarkId = sam.benchmarkId
set sam.minTs = source.minTs,
sam.maxTs = source.maxTs,
sam.saved = source.saved,
sam.savedResultEngine = source.savedResultEngine,
sam.submitted = source.submitted,
sam.submittedResultEngine = source.submittedResultEngine,
sam.rejected = source.rejected,
sam.rejectedResultEngine = source.rejectedResultEngine,
sam.accepted = source.accepted,
sam.acceptedResultEngine = source.acceptedResultEngine,
sam.highCount = source.highCount,
sam.mediumCount = source.mediumCount,
sam.lowCount = source.lowCount,
sam.notchecked = source.notchecked,
sam.notcheckedResultEngine = source.notcheckedResultEngine,
sam.notapplicable = source.notapplicable,
sam.notapplicableResultEngine = source.notapplicableResultEngine,
sam.pass = source.pass,
sam.passResultEngine = source.passResultEngine,
sam.fail = source.fail,
sam.failResultEngine = source.failResultEngine,
sam.unknown = source.unknown,
sam.unknownResultEngine = source.unknownResultEngine,
sam.error = source.error,
sam.errorResultEngine = source.errorResultEngine,
sam.notselected = source.notselected,
sam.notselectedResultEngine = source.notselectedResultEngine,
sam.informational = source.informational,
sam.informationalResultEngine = source.informationalResultEngine,
sam.fixed = source.fixed,
sam.fixedResultEngine = source.fixedResultEngine
`
]
const downMigration = [
`
ALTER TABLE stig_asset_map
RENAME COLUMN saved TO savedManual,
RENAME COLUMN savedResultEngine TO savedAuto,
RENAME COLUMN submitted TO submittedManual,
RENAME COLUMN submittedResultEngine TO submittedAuto,
RENAME COLUMN rejected to rejectedManual,
RENAME COLUMN rejectedResultEngine TO rejectedAuto,
RENAME COLUMN accepted TO acceptedManual,
RENAME COLUMN acceptedResultEngine TO acceptedAuto,
DROP COLUMN notchecked ,
DROP COLUMN notcheckedResultEngine ,
DROP COLUMN notapplicable ,
DROP COLUMN notapplicableResultEngine ,
DROP COLUMN pass ,
DROP COLUMN passResultEngine ,
DROP COLUMN fail ,
DROP COLUMN failResultEngine ,
DROP COLUMN unknown ,
DROP COLUMN unknownResultEngine ,
DROP COLUMN error ,
DROP COLUMN errorResultEngine ,
DROP COLUMN notselected ,
DROP COLUMN notselectedResultEngine ,
DROP COLUMN informational ,
DROP COLUMN informationalResultEngine ,
DROP COLUMN fixed ,
DROP COLUMN fixedResultEngine
`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0017.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE current_rev DROP COLUMN ovalCount`,
`ALTER TABLE revision DROP COLUMN ovalCount`,
`
ALTER VIEW v_current_rev AS
select
rr.revId AS revId,
rr.benchmarkId AS benchmarkId,
rr.version AS version,
rr.release AS \`release\`,
rr.benchmarkDate AS benchmarkDate,
rr.benchmarkDateSql AS benchmarkDateSql,
rr.status AS status,
rr.statusDate AS statusDate,
rr.description AS description,
rr.active AS active,
rr.groupCount AS groupCount,
rr.ruleCount AS ruleCount,
rr.checkCount AS checkCount,
rr.fixCount AS fixCount
from (
select
r.revId AS revId,
r.benchmarkId AS benchmarkId,
r.version AS version,
r.release AS \`release\`,
r.benchmarkDate AS benchmarkDate,
r.benchmarkDateSql AS benchmarkDateSql,
r.status AS status,
r.statusDate AS statusDate,
r.description AS description,
r.active AS active,
r.groupCount AS groupCount,
r.ruleCount AS ruleCount,
r.checkCount AS checkCount,
r.fixCount AS fixCount,
row_number() OVER (
PARTITION BY r.benchmarkId
ORDER BY
FIELD(status, 'draft', 'accepted') desc,
(r.version + 0) desc,
(r.release + 0) desc ) AS rn
from
revision r) rr where (rr.rn = 1);
`,
`DROP TABLE IF EXISTS review_reject_string_map`,
`DROP TABLE IF EXISTS reject_string`,
`DROP TABLE IF EXISTS rev_xml_map`,
`DROP TABLE IF EXISTS rule_oval_map`
]
const downMigration = [
`
CREATE TABLE review_reject_string_map (
rrsId int(11) NOT NULL AUTO_INCREMENT,
assetId int(11) NOT NULL,
ruleId varchar(45) NOT NULL,
rejectId int(11) NOT NULL,
userId int(11) DEFAULT NULL,
PRIMARY KEY (rrsId),
UNIQUE KEY INDEX2 (assetId,ruleId,rejectId)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
`,
`
CREATE TABLE reject_string (
rejectId int(11) NOT NULL AUTO_INCREMENT,
shortStr varchar(45) NOT NULL,
longStr longtext ,
PRIMARY KEY (rejectId)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
`,
`
CREATE TABLE rule_oval_map (
roId int(11) NOT NULL AUTO_INCREMENT,
ruleId varchar(255) NOT NULL,
ovalRef varchar(255) NOT NULL,
benchmarkId varchar(255) NOT NULL,
releaseInfo varchar(255) NOT NULL,
PRIMARY KEY (roId),
KEY index2 (ruleId),
KEY index3 (benchmarkId)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
`,
`
CREATE TABLE rev_xml_map (
rxId int(11) NOT NULL AUTO_INCREMENT,
revId varchar(255) NOT NULL,
xml blob,
PRIMARY KEY (rxId),
UNIQUE KEY uidx_rxm_revId (revId)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
`,
`ALTER TABLE current_rev ADD COLUMN ovalCount int`,
`ALTER TABLE revision ADD COLUMN ovalCount int`,
`
ALTER VIEW v_current_rev AS
select
rr.revId AS revId,
rr.benchmarkId AS benchmarkId,
rr.version AS version,
rr.release AS \`release\`,
rr.benchmarkDate AS benchmarkDate,
rr.benchmarkDateSql AS benchmarkDateSql,
rr.status AS status,
rr.statusDate AS statusDate,
rr.description AS description,
rr.active AS active,
rr.groupCount AS groupCount,
rr.ruleCount AS ruleCount,
rr.checkCount AS checkCount,
rr.fixCount AS fixCount
from (
select
r.revId AS revId,
r.benchmarkId AS benchmarkId,
r.version AS version,
r.release AS \`release\`,
r.benchmarkDate AS benchmarkDate,
r.benchmarkDateSql AS benchmarkDateSql,
r.status AS status,
r.statusDate AS statusDate,
r.description AS description,
r.active AS active,
r.groupCount AS groupCount,
r.ruleCount AS ruleCount,
r.checkCount AS checkCount,
r.fixCount AS fixCount,
(select count(distinct ro.ruleId) from rule_oval_map ro where ro.ruleId IN (
SELECT rgr.ruleId from rev_group_map rg inner join rev_group_rule_map rgr on rg.rgId = rgr.rgId WHERE rg.revId = r.revId)) AS ovalCount,
row_number() OVER (
PARTITION BY r.benchmarkId
ORDER BY
FIELD(status, 'draft', 'accepted') desc,
(r.version + 0) desc,
(r.release + 0) desc ) AS rn
from
revision r) rr where (rr.rn = 1)
`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0018.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE stig_asset_map ADD COLUMN maxTouchTs datetime`,
`with source as (
select
sa.assetId,
sa.benchmarkId,
max(review.touchTs) as maxTouchTs
from
asset a
left join stig_asset_map sa using (assetId)
left join current_group_rule cgr using (benchmarkId)
left join review on (cgr.ruleId=review.ruleId and review.assetId=sa.assetId)
group by
sa.assetId,
sa.benchmarkId)
update stig_asset_map sam
inner join source on sam.assetId = source.assetId and source.benchmarkId = sam.benchmarkId
set sam.maxTouchTs = source.maxTouchTs
`
]
const downMigration = [
`ALTER TABLE stig_asset_map DROP COLUMN maxTouchTs`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0019.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE revision
ADD COLUMN lowCount INT NOT NULL DEFAULT 0,
ADD COLUMN mediumCount INT NOT NULL DEFAULT 0,
ADD COLUMN highCount INT NOT NULL DEFAULT 0,
CHANGE COLUMN ruleCount ruleCount INT GENERATED ALWAYS AS (highCount + mediumCount + lowCount) STORED`,
`update revision left join (select
rg.revId,
SUM(CASE WHEN r.severity = 'high' THEN 1 ELSE 0 END) as highCount,
SUM(CASE WHEN r.severity = 'medium' THEN 1 ELSE 0 END) as mediumCount,
SUM(CASE WHEN r.severity = 'low' THEN 1 ELSE 0 END) as lowCount
from
rev_group_map rg
left join rev_group_rule_map rgr on rg.rgId = rgr.rgId
left join rule r on rgr.ruleId = r.ruleId
group by
rg.revId) as sq on revision.revId = sq.revId
set
revision.lowCount = sq.lowCount,
revision.mediumCount = sq.mediumCount,
revision.highCount = sq.highCount`,
`ALTER TABLE current_rev
ADD COLUMN lowCount INT NOT NULL DEFAULT 0,
ADD COLUMN mediumCount INT NOT NULL DEFAULT 0,
ADD COLUMN highCount INT NOT NULL DEFAULT 0,
CHANGE COLUMN ruleCount ruleCount INT GENERATED ALWAYS AS (highCount + mediumCount + lowCount) STORED`,
`ALTER VIEW v_current_rev AS
select
rr.revId AS revId,
rr.benchmarkId AS benchmarkId,
rr.\`version\` AS \`version\`,
rr.\`release\` AS \`release\`,
rr.benchmarkDate AS benchmarkDate,
rr.benchmarkDateSql AS benchmarkDateSql,
rr.status AS status,
rr.statusDate AS statusDate,
rr.description AS description,
rr.active AS active,
rr.groupCount AS groupCount,
rr.ruleCount AS ruleCount,
rr.lowCount AS lowCount,
rr.mediumCount AS mediumCount,
rr.highCount AS highCount,
rr.checkCount AS checkCount,
rr.fixCount AS fixCount from (select r.revId AS revId,
r.benchmarkId AS benchmarkId,
r.\`version\` AS \`version\`,
r.\`release\` AS \`release\`,
r.benchmarkDate AS benchmarkDate,
r.benchmarkDateSql AS benchmarkDateSql,
r.status AS status,
r.statusDate AS statusDate,
r.description AS description,
r.active AS active,
r.groupCount AS groupCount,
r.ruleCount AS ruleCount,
r.lowCount AS lowCount,
r.mediumCount AS mediumCount,
r.highCount AS highCount,
r.checkCount AS checkCount,
r.fixCount AS fixCount,
row_number() OVER (PARTITION BY r.benchmarkId ORDER BY field(r.status,
'draft',
'accepted') desc,
(r.\`version\` + 0) desc,
(r.\`release\` + 0) desc ) AS rn from revision r) rr where (rr.rn = 1)`,
`DELETE FROM current_rev`,
`INSERT INTO current_rev (
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount)
SELECT
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount
FROM
v_current_rev`,
`CREATE TABLE check_content (
ccId INT NOT NULL AUTO_INCREMENT,
digest BINARY(32) GENERATED ALWAYS AS (UNHEX(SHA2(content, 256))) STORED,
content TEXT NOT NULL,
PRIMARY KEY (ccId),
UNIQUE INDEX digest_UNIQUE (digest ASC) VISIBLE)`,
'INSERT INTO check_content (content) SELECT content from `check` c ON DUPLICATE KEY UPDATE content=c.content',
'ALTER TABLE `check` ADD COLUMN ccId INT DEFAULT NULL',
'ALTER TABLE rule ADD COLUMN ccId INT DEFAULT NULL',
'UPDATE `check` SET ccId = (SELECT ccId from check_content WHERE digest = UNHEX(SHA2(`check`.content, 256)))',
'ALTER TABLE `check` DROP COLUMN content',
'ALTER TABLE `check` ADD INDEX (ccId)',
`ALTER TABLE \`check\` ADD CONSTRAINT fk_check_1 FOREIGN KEY (ccId) REFERENCES check_content (ccId) ON DELETE RESTRICT ON UPDATE RESTRICT`,
'ALTER TABLE rule ADD INDEX (ccId)',
`ALTER TABLE rule ADD CONSTRAINT fk_rule_1 FOREIGN KEY (ccId) REFERENCES check_content (ccId) ON DELETE RESTRICT ON UPDATE RESTRICT`,
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0020.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// if absent here, the query UPDATE rev_group_rule_map runs very slowly
`ALTER TABLE rule DROP FOREIGN KEY fk_rule_1`,
`ALTER TABLE rule DROP COLUMN ccId, DROP INDEX ccId`,
// temp table for rule_fix
`drop table if exists temp_rule_fix`,
`create temporary table temp_rule_fix(
rgrId INT PRIMARY KEY,
fixref varchar(255),
text TEXT,
digest BINARY(32) GENERATED ALWAYS AS (UNHEX(SHA2(text, 256))) STORED)`,
`insert into temp_rule_fix(rgrId, fixref, text)
select
rgrf.rgrId,
group_concat(fix.fixId) as fixref,
group_concat(fix.text separator '\n\n-----AND-----\n\n') as text
from
rev_group_rule_fix_map rgrf
left join fix using (fixId)
group by rgrf.rgrId`,
// create and populate fix_text
`CREATE TABLE fix_text (
ftId INT NOT NULL AUTO_INCREMENT,
digest BINARY(32) GENERATED ALWAYS AS (UNHEX(SHA2(text, 256))) STORED,
text TEXT NOT NULL,
PRIMARY KEY (ftId),
UNIQUE INDEX digest_UNIQUE (digest ASC) VISIBLE)`,
`INSERT INTO fix_text (text) SELECT text from temp_rule_fix ON DUPLICATE KEY UPDATE text=temp_rule_fix.text`,
// temp table for rule_check
`drop table if exists temp_rule_check`,
`create temporary table temp_rule_check(
rgrId INT PRIMARY KEY,
\`system\` varchar(255),
content TEXT,
digest BINARY(32) GENERATED ALWAYS AS (UNHEX(SHA2(content, 256))) STORED)`,
`insert into temp_rule_check(rgrId, \`system\`, content)
select
rgrc.rgrId,
group_concat(rgrc.checkId) as \`system\`,
group_concat(cc.content separator '\n\n-----AND-----\n\n') as content
from
rev_group_rule_check_map rgrc
left join \`check\` using (checkId)
left join check_content cc using (ccId)
group by rgrc.rgrId`,
// populate check_content with multi-check content only. Migration 0019 populated single-check content
`insert ignore into check_content(content) select content from temp_rule_check where \`system\` like '%,%'`,
// update rev_group_rule_map
`ALTER TABLE rev_group_rule_map DROP COLUMN checks, DROP COLUMN fixes, DROP COLUMN ccis`,
`ALTER TABLE rev_group_rule_map
ADD COLUMN \`revId\` varchar(255) AFTER rgrId,
ADD COLUMN \`groupId\` varchar(45) AFTER revId,
ADD COLUMN \`groupTitle\` varchar(255) AFTER groupId,
ADD COLUMN \`groupSeverity\` varchar(45) AFTER groupTitle,
ADD COLUMN \`version\` varchar(45),
ADD COLUMN \`title\` varchar(1000),
ADD COLUMN \`severity\` varchar(45),
ADD COLUMN \`weight\` varchar(45),
ADD COLUMN \`vulnDiscussion\` text,
ADD COLUMN \`falsePositives\` text,
ADD COLUMN \`falseNegatives\` text,
ADD COLUMN \`documentable\` varchar(45) ,
ADD COLUMN \`mitigations\` text,
ADD COLUMN \`severityOverrideGuidance\` text,
ADD COLUMN \`potentialImpacts\` text,
ADD COLUMN \`thirdPartyTools\` text,
ADD COLUMN \`mitigationControl\` text,
ADD COLUMN \`responsibility\` varchar(255) ,
ADD COLUMN \`iaControls\` varchar(255),
ADD COLUMN \`checkSystem\` varchar (255),
ADD COLUMN \`checkDigest\` BINARY(32),
ADD COLUMN \`fixref\` varchar(255),
ADD COLUMN \`fixDigest\` BINARY(32)`,
`UPDATE rev_group_rule_map rgr
LEFT JOIN rev_group_map rg using (rgId)
LEFT JOIN \`group\` g on rg.groupId = g.groupId
LEFT JOIN rule r using (ruleId)
LEFT JOIN temp_rule_check trc using (rgrId)
LEFT JOIN temp_rule_fix trf using (rgrId)
SET
rgr.revId = rg.revId,
rgr.groupId = rg.groupId,
rgr.groupTitle = g.title,
rgr.groupSeverity = g.severity,
rgr.\`version\` = r.\`version\`,
rgr.title = r.title,
rgr.severity = r.severity,
rgr.weight = r.weight,
rgr.vulnDiscussion = r.vulnDiscussion,
rgr.falsePositives = r.falsePositives,
rgr.falseNegatives = r.falseNegatives,
rgr.documentable = r.documentable,
rgr.mitigations = r.mitigations,
rgr.severityOverrideGuidance = r.severityOverrideGuidance,
rgr.potentialImpacts = r.potentialImpacts,
rgr.thirdPartyTools = r.thirdPartyTools,
rgr.mitigationControl = r.mitigationControl,
rgr.responsibility = r.responsibility,
rgr.iaControls = r.iaControls,
rgr.checkSystem = trc.system,
rgr.checkDigest = trc.digest,
rgr.fixref = trf.fixref,
rgr.fixDigest = trf.digest`,
`ALTER TABLE rev_group_rule_map DROP FOREIGN KEY FK_rev_group_rule_map_rule`,
`ALTER TABLE rev_group_rule_map DROP FOREIGN KEY FK_rev_group_rule_map_rev_group_map`,
`ALTER TABLE rev_group_rule_map DROP INDEX uidx_rgrm_rgId_ruleId`,
`ALTER TABLE rev_group_rule_map DROP COLUMN rgId`,
`ALTER TABLE rev_group_rule_map ADD INDEX index4 (checkDigest ASC) VISIBLE, ADD INDEX index5 (fixDigest ASC) VISIBLE`,
`ALTER TABLE rev_group_rule_map ADD UNIQUE INDEX rev_group_rule_UNIQUE (revId ASC, groupId ASC, ruleId ASC) VISIBLE`,
`ALTER TABLE rev_group_rule_map ADD CONSTRAINT fk_rev_group_rule_map_1 FOREIGN KEY (revId) REFERENCES revision (revId) ON DELETE CASCADE ON UPDATE CASCADE`,
// rev_group_rule_cci_map
`CREATE TABLE rev_group_rule_cci_map (
rgrccId INT NOT NULL AUTO_INCREMENT,
rgrId INT NOT NULL,
cci VARCHAR(20) NOT NULL,
PRIMARY KEY (rgrccId),
UNIQUE INDEX index2 (rgrId ASC, cci ASC) VISIBLE,
INDEX index3 (cci ASC) VISIBLE)`,
`INSERT INTO rev_group_rule_cci_map (rgrId, cci)
SELECT
rgrId,
rc.cci
FROM
rev_group_rule_map rgr
left join rule_cci_map rc using (ruleId)
WHERE
rc.cci is not null`,
// drop legacy tables
`DROP TABLE rev_group_map`,
`DROP TABLE \`group\``,
`DROP TABLE rule_cci_map`,
`DROP TABLE rule`,
`DROP table rev_group_rule_check_map`,
`DROP table rev_group_rule_fix_map`,
`DROP table \`check\``,
`DROP table fix`,
`DROP table poam_rar_entry`,
// VIEW for current_group_rule
`CREATE OR REPLACE VIEW v_current_group_rule AS
SELECT
cr.benchmarkId
,rgr.groupId
,rgr.groupTitle
,rgr.groupSeverity
,rgr.ruleId
,rgr.\`version\`
,rgr.title
,rgr.severity
,rgr.weight
,rgr.vulnDiscussion
,rgr.falsePositives
,rgr.falseNegatives
,rgr.documentable
,rgr.mitigations
,rgr.severityOverrideGuidance
,rgr.potentialImpacts
,rgr.thirdPartyTools
,rgr.mitigationControl
,rgr.responsibility
,rgr.iaControls
,rgr.checkSystem
,rgr.checkDigest
,rgr.fixref
,rgr.fixDigest
from current_rev cr left join rev_group_rule_map rgr using(revId)`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
// await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0021.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`DELETE FROM current_rev`,
`INSERT INTO current_rev (
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount)
SELECT
revId,
benchmarkId,
\`version\`,
\`release\`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
lowCount,
mediumCount,
highCount,
checkCount,
fixCount
FROM
v_current_rev`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0022.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// table: rule_version_check_digest
`drop table if exists rule_version_check_digest`,
`CREATE TABLE rule_version_check_digest (
ruleId varchar(255) NOT NULL,
\`version\` varchar(45) NOT NULL,
checkDigest binary(32) NOT NULL,
PRIMARY KEY index1 (ruleId),
KEY index_vcd (\`version\`, checkDigest)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`,
`INSERT INTO rule_version_check_digest (ruleId, \`version\`, checkDigest)
with currentDigest as (
select
rgr.ruleId,
rgr.version,
rgr.checkDigest,
rev.benchmarkDateSql,
rev.revId,
ROW_NUMBER() OVER (PARTITION BY rgr.ruleId ORDER BY rev.benchmarkDateSql DESC) as rowNum
from
rev_group_rule_map rgr
left join revision rev using (revId)
where
rgr.checkDigest is not null
)
select
ruleId,
\`version\`,
checkDigest
from
currentDigest
where
rowNum = 1`,
// table: review_history
`ALTER TABLE review_history ADD COLUMN ruleId VARCHAR(45) DEFAULT NULL`,
// table: review
`ALTER TABLE review
ADD COLUMN \`version\` VARCHAR(45) NOT NULL AFTER reAuthority,
ADD COLUMN checkDigest BINARY(32) NOT NULL AFTER \`version\``,
// table: temp_current_reviews
`drop table if exists temp_current_reviews`,
`CREATE TABLE temp_current_reviews (
reviewId INT,
\`version\` VARCHAR(45) NOT NULL,
checkDigest BINARY(32) NOT NULL,
PRIMARY KEY (reviewId))`,
`INSERT INTO temp_current_reviews (reviewId, \`version\`, checkDigest)
WITH ordered_reviews AS (
SELECT r.reviewId,rvcd.version,rvcd.checkDigest,ROW_NUMBER() OVER (PARTITION BY r.assetId, rvcd.version, rvcd.checkDigest ORDER BY r.touchTs DESC) as rowNum
FROM review r INNER JOIN rule_version_check_digest rvcd using (ruleId))
,active_reviews AS (SELECT reviewId, \`version\`, checkDigest from ordered_reviews where rowNum = 1)
SELECT reviewId, \`version\`, checkDigest from active_reviews`,
// update the reviews that are current
`UPDATE review r INNER JOIN temp_current_reviews t using (reviewId) SET r.version = t.version, r.checkDigest = t.checkDigest`,
// index the new columns
`ALTER TABLE review ADD INDEX idx_vcd (\`version\`, checkDigest)`,
`ALTER TABLE review ADD INDEX idx_asset_vcd (assetId, \`version\`, checkDigest)`,
`ALTER TABLE review DROP INDEX INDEX_ASSETID_RULEID`,
`drop table if exists temp_current_reviews`,
// recalculate metrics
`with source as
( select
sa.assetId,
sa.benchmarkId,
min(review.ts) as minTs,
max(review.ts) as maxTs,
max(review.touchTs) as maxTouchTs,
sum(CASE WHEN review.statusId = 0 THEN 1 ELSE 0 END) as saved,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 0 THEN 1 ELSE 0 END) as savedResultEngine,
sum(CASE WHEN review.statusId = 1 THEN 1 ELSE 0 END) as submitted,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 1 THEN 1 ELSE 0 END) as submittedResultEngine,
sum(CASE WHEN review.statusId = 2 THEN 1 ELSE 0 END) as rejected,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 2 THEN 1 ELSE 0 END) as rejectedResultEngine,
sum(CASE WHEN review.statusId = 3 THEN 1 ELSE 0 END) as accepted,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 3 THEN 1 ELSE 0 END) as acceptedResultEngine,
sum(CASE WHEN review.resultId=4 and cgr.severity='high' THEN 1 ELSE 0 END) as highCount,
sum(CASE WHEN review.resultId=4 and cgr.severity='medium' THEN 1 ELSE 0 END) as mediumCount,
sum(CASE WHEN review.resultId=4 and cgr.severity='low' THEN 1 ELSE 0 END) as lowCount,
sum(CASE WHEN review.resultId = 1 THEN 1 ELSE 0 END) as notchecked,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 1 THEN 1 ELSE 0 END) as notcheckedResultEngine,
sum(CASE WHEN review.resultId = 2 THEN 1 ELSE 0 END) as notapplicable,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 2 THEN 1 ELSE 0 END) as notapplicableResultEngine,
sum(CASE WHEN review.resultId = 3 THEN 1 ELSE 0 END) as pass,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 3 THEN 1 ELSE 0 END) as passResultEngine,
sum(CASE WHEN review.resultId = 4 THEN 1 ELSE 0 END) as fail,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 4 THEN 1 ELSE 0 END) as failResultEngine,
sum(CASE WHEN review.resultId = 5 THEN 1 ELSE 0 END) as unknown,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 5 THEN 1 ELSE 0 END) as unknownResultEngine,
sum(CASE WHEN review.resultId = 6 THEN 1 ELSE 0 END) as error,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 6 THEN 1 ELSE 0 END) as errorResultEngine,
sum(CASE WHEN review.resultId = 7 THEN 1 ELSE 0 END) as notselected,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 7 THEN 1 ELSE 0 END) as notselectedResultEngine,
sum(CASE WHEN review.resultId = 8 THEN 1 ELSE 0 END) as informational,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 8 THEN 1 ELSE 0 END) as informationalResultEngine,
sum(CASE WHEN review.resultId = 9 THEN 1 ELSE 0 END) as fixed,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 9 THEN 1 ELSE 0 END) as fixedResultEngine
from
asset a
left join stig_asset_map sa using (assetId)
left join v_current_group_rule cgr using (benchmarkId)
left join rule_version_check_digest rvcd using (ruleId)
left join review on (rvcd.version=review.version and rvcd.checkDigest=review.checkDigest and review.assetId=sa.assetId)
group by
sa.assetId,
sa.benchmarkId
)
update stig_asset_map sam
inner join source on sam.assetId = source.assetId and source.benchmarkId = sam.benchmarkId
set sam.minTs = source.minTs,
sam.maxTs = source.maxTs,
sam.maxTouchTs = source.maxTouchTs,
sam.saved = source.saved,
sam.savedResultEngine = source.savedResultEngine,
sam.submitted = source.submitted,
sam.submittedResultEngine = source.submittedResultEngine,
sam.rejected = source.rejected,
sam.rejectedResultEngine = source.rejectedResultEngine,
sam.accepted = source.accepted,
sam.acceptedResultEngine = source.acceptedResultEngine,
sam.highCount = source.highCount,
sam.mediumCount = source.mediumCount,
sam.lowCount = source.lowCount,
sam.notchecked = source.notchecked,
sam.notcheckedResultEngine = source.notcheckedResultEngine,
sam.notapplicable = source.notapplicable,
sam.notapplicableResultEngine = source.notapplicableResultEngine,
sam.pass = source.pass,
sam.passResultEngine = source.passResultEngine,
sam.fail = source.fail,
sam.failResultEngine = source.failResultEngine,
sam.unknown = source.unknown,
sam.unknownResultEngine = source.unknownResultEngine,
sam.error = source.error,
sam.errorResultEngine = source.errorResultEngine,
sam.notselected = source.notselected,
sam.notselectedResultEngine = source.notselectedResultEngine,
sam.informational = source.informational,
sam.informationalResultEngine = source.informationalResultEngine,
sam.fixed = source.fixed,
sam.fixedResultEngine = source.fixedResultEngine`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0023.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// table: revision
`ALTER TABLE revision ADD COLUMN revisionStr VARCHAR(45) GENERATED ALWAYS AS (concat("V", \`version\`, "R", \`release\`)) AFTER \`release\``,
`ALTER TABLE revision ADD INDEX idx_revision_benchmark_revisionStr (benchmarkId ASC, revisionStr ASC) VISIBLE`,
// table: collection_rev
`drop table if exists collection_rev_map`,
`CREATE TABLE collection_rev_map (
crId INT NOT NULL AUTO_INCREMENT,
collectionId INT NOT NULL,
benchmarkId VARCHAR(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs,
revId VARCHAR(255) NOT NULL,
PRIMARY KEY index1 (crId),
UNIQUE KEY index_collection_benchmark (collectionId, benchmarkId),
INDEX index_revId (revId),
CONSTRAINT fk_collection_rev_map_1 FOREIGN KEY (collectionId) REFERENCES collection (collectionId) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`,
// view: default_rev
`DROP VIEW IF EXISTS v_default_rev`,
`CREATE VIEW v_default_rev AS
SELECT DISTINCT
a.collectionId AS collectionId,
sa.benchmarkId AS benchmarkId,
CASE WHEN crm.revId IS NOT NULL THEN crm.revId ELSE cr.revId END as revId,
CASE WHEN crm.revId IS NOT NULL THEN 1 ELSE 0 END as revisionPinned
FROM
asset a
INNER JOIN stig_asset_map sa ON a.assetId = sa.assetId
LEFT JOIN current_rev cr ON sa.benchmarkId = cr.benchmarkId
LEFT JOIN collection_rev_map crm ON (sa.benchmarkId = crm.benchmarkId AND a.collectionId = crm.collectionId)`,
// table: default_rev
`DROP TABLE IF EXISTS default_rev`,
`CREATE TABLE default_rev (
vdId int NOT NULL AUTO_INCREMENT,
collectionId int NOT NULL,
benchmarkId varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs NOT NULL,
revId varchar(255) NOT NULL,
revisionPinned TINYINT NOT NULL,
PRIMARY KEY (vdId),
UNIQUE KEY index2 (collectionId,benchmarkId),
KEY index3 (benchmarkId),
KEY index4 (revId),
CONSTRAINT fk_default_rev_2 FOREIGN KEY (collectionId) REFERENCES collection (collectionId) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`,
`INSERT INTO default_rev(collectionId, benchmarkId, revId, revisionPinned)
SELECT collectionId, benchmarkId, revId, revisionPinned FROM v_default_rev`,
// view: v_latest_rev
`DROP VIEW IF EXISTS v_latest_rev`,
`CREATE VIEW v_latest_rev AS
select
rr.revId AS revId,
rr.benchmarkId AS benchmarkId,
concat('V',rr.version,'R',rr.release) as revisionStr
from
(
select
r.revId,
r.benchmarkId,
r.version,
r.release,
row_number() OVER (
PARTITION BY r.benchmarkId
ORDER BY
field(
r.status, 'draft', 'accepted'
) desc,
(r.version + 0) desc,
(r.release + 0) desc
) AS rn
from
revision r
) rr
where
(rr.rn = 1)`,
`ALTER TABLE rev_group_rule_map
DROP INDEX index4 ,
ADD INDEX idx_version_check_digest (\`version\` ASC, checkDigest ASC) VISIBLE`
]
const downMigration = [
`drop table if exists collection_rev_map`,
`DROP VIEW IF EXISTS v_default_rev`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0024.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// table: collection
`ALTER TABLE collection
ADD COLUMN state ENUM('enabled','disabled','cloning') NOT NULL,
ADD COLUMN createdUserId INT NULL,
ADD COLUMN stateDate DATETIME NULL,
ADD COLUMN stateUserId INT NULL,
ADD COLUMN isEnabled TINYINT GENERATED ALWAYS AS (case when (state = 'enabled') then 1 else null end),
DROP INDEX index2,
ADD UNIQUE INDEX index2 (name ASC, isEnabled ASC) VISIBLE`,
// table: asset
`ALTER TABLE asset ADD COLUMN state ENUM('enabled','disabled') NOT NULL,
ADD COLUMN stateDate DATETIME NULL,
ADD COLUMN stateUserId INT NULL,
ADD COLUMN isEnabled TINYINT GENERATED ALWAYS AS (case when (state = 'enabled') then 1 else null end),
DROP INDEX INDEX_NAMECOLLECTION,
ADD UNIQUE INDEX INDEX_NAME_COLLECTION_ENABLED (name ASC, collectionId ASC, isEnabled ASC) VISIBLE`,
// procedure: deleteDisabledCollections
`DROP procedure IF EXISTS deleteDisabledCollections`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0025.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// table: collection
`ALTER TABLE collection
ADD COLUMN isCloning TINYINT GENERATED ALWAYS AS (case when (state = 'cloning') then 1 else null end),
ADD UNIQUE INDEX index3 (name ASC, isCloning ASC) VISIBLE`,
// procedure: deleteDisabledCollections
`DROP procedure IF EXISTS deleteDisabledCollections`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0026.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// table: collection
`ALTER TABLE collection
CHANGE COLUMN isCloning isNameUnavailable TINYINT GENERATED ALWAYS AS ((case when (state = _utf8mb4'cloning') or (state = _utf8mb4'enabled') then 1 else NULL end)) VIRTUAL ;`,
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0027.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE result
ADD COLUMN cklb VARCHAR(32) NOT NULL AFTER ckl`,
`UPDATE result set cklb = 'not_reviewed' where resultId in (1, 5, 6, 7, 8)`,
`UPDATE result set cklb = 'not_applicable' where resultId = 2`,
`UPDATE result set cklb = 'not_a_finding' where resultId in (3, 9)`,
`UPDATE result set cklb = 'open' where resultId = 4`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0028.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
// table: review
`ALTER TABLE review MODIFY COLUMN statusText VARCHAR(512)`,
// table: review_history
`ALTER TABLE review_history MODIFY COLUMN statusText VARCHAR(512)`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0029.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`DROP VIEW IF EXISTS v_current_group_rule`,
`DROP TABLE IF EXISTS current_group_rule`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0032.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
const [cols] = await pool.query('SHOW COLUMNS FROM stig_asset_map')
const colNames = cols.map(row => row.Field)
const colStatements = []
if (colNames.includes('resultEngines')) {
colStatements.push(`ALTER TABLE stig_asset_map DROP COLUMN resultEngines`)
}
if (colNames.includes('users')) {
colStatements.push(`ALTER TABLE stig_asset_map DROP COLUMN users`)
}
if (colNames.includes('statusUsers')) {
colStatements.push(`ALTER TABLE stig_asset_map DROP COLUMN statusUsers`)
}
for (const statement of colStatements) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement })
await pool.query(statement)
}
}
module.exports = {
up: async pool => {
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', {status: 'finish', migrationName })
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', migrationName, message: e.message })
throw (e)
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0033.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`UPDATE collection
SET settings = JSON_SET(settings, '$.history.maxReviews', 15)
WHERE JSON_EXTRACT(settings, '$.history.maxReviews') = -1
OR JSON_EXTRACT(settings, '$.history.maxReviews') > 15
`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0034.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE asset ADD INDEX idx_state (state ASC)`,
`ALTER TABLE collection ADD INDEX idx_state (state ASC)`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0035.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE review_history CHANGE COLUMN historyId historyId BIGINT UNSIGNED NOT NULL AUTO_INCREMENT`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0036.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`DROP TABLE IF EXISTS collection_grant_acl`,
`DROP TABLE IF EXISTS collection_grant_group_acl`,
`DROP TABLE IF EXISTS collection_grant_group`,
`DROP TABLE IF EXISTS user_group_user_map`,
`DROP TABLE IF EXISTS user_group`,
// table: user_group
`CREATE TABLE user_group (
userGroupId INT NOT NULL AUTO_INCREMENT,
name VARCHAR(255) NOT NULL,
description VARCHAR(255) NULL,
createdUserId INT NOT NULL,
createdDate DATETIME DEFAULT CURRENT_TIMESTAMP,
modifiedUserId INT NOT NULL,
modifiedDate DATETIME DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (userGroupId),
UNIQUE INDEX idx_name (name ASC),
INDEX fk_user_group_1_idx (createdUserId ASC),
INDEX fk_user_group_2_idx (modifiedUserId ASC),
CONSTRAINT fk_user_group_1
FOREIGN KEY (createdUserId)
REFERENCES user_data (userId)
ON DELETE RESTRICT
ON UPDATE RESTRICT,
CONSTRAINT fk_user_group_2
FOREIGN KEY (modifiedUserId)
REFERENCES user_data (userId)
ON DELETE RESTRICT
ON UPDATE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`,
// table user_group_user_map
`CREATE TABLE user_group_user_map (
ugumId INT NOT NULL AUTO_INCREMENT,
userGroupId INT NOT NULL,
userId INT NOT NULL,
PRIMARY KEY (ugumId),
UNIQUE KEY INDEX_UG_USER (userGroupId,userId),
INDEX fk_user_group_map_2_idx (userId ASC) VISIBLE,
CONSTRAINT fk_user_group_map_1
FOREIGN KEY (userGroupId)
REFERENCES user_group (userGroupId)
ON DELETE CASCADE
ON UPDATE CASCADE,
CONSTRAINT fk_user_group_map_2
FOREIGN KEY (userId)
REFERENCES user_data (userId)
ON DELETE CASCADE
ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`,
// table collection_grant
`ALTER TABLE collection_grant DROP FOREIGN KEY fk_collection_grant_1`,
`ALTER TABLE collection_grant RENAME COLUMN cgId TO grantId`,
`ALTER TABLE collection_grant ADD COLUMN userGroupId INT NULL AFTER userId, CHANGE COLUMN userId userId INT NULL`,
`ALTER TABLE collection_grant ADD UNIQUE INDEX INDEX_USER_GROUP (userGroupId ASC, collectionId ASC) VISIBLE`,
`ALTER TABLE collection_grant CHANGE COLUMN accessLevel roleId INT NOT NULL`,
`ALTER TABLE collection_grant ADD CONSTRAINT fk_collection_grant_1 FOREIGN KEY (userId) REFERENCES user_data (userId) ON DELETE CASCADE ON UPDATE CASCADE`,
`ALTER TABLE collection_grant ADD CONSTRAINT fk_collection_grant_3 FOREIGN KEY (userGroupId) REFERENCES user_group (userGroupId) ON DELETE CASCADE ON UPDATE CASCADE`,
// table collection_grant_acl
`CREATE TABLE collection_grant_acl (
cgAclId INT NOT NULL AUTO_INCREMENT,
grantId INT NOT NULL,
benchmarkId VARCHAR(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs NULL,
assetId INT NULL,
clId INT NULL,
access enum('none','r', 'rw') NOT NULL,
modifiedUserId int NULL,
modifiedDate datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (cgAclId),
KEY fk_collection_grant_acl_1 (grantId),
KEY fk_collection_grant_acl_2 (assetId, benchmarkId),
KEY fk_collection_grant_acl_3 (benchmarkId, assetId),
KEY fk_collection_grant_acl_4 (clId, benchmarkId),
CONSTRAINT fk_collection_grant_acl_1 FOREIGN KEY (grantId) REFERENCES collection_grant (grantId) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT fk_collection_grant_acl_2 FOREIGN KEY (assetId) REFERENCES asset (assetId) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT fk_collection_grant_acl_3 FOREIGN KEY (benchmarkId) REFERENCES stig (benchmarkId) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT fk_collection_grant_acl_4 FOREIGN KEY (clId) REFERENCES collection_label (clId) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT fk_collection_grant_acl_5 FOREIGN KEY (benchmarkId, assetId) REFERENCES stig_asset_map (benchmarkId, assetId) ON DELETE CASCADE ON UPDATE CASCADE
)`,
// initialize collection_grant_acl
`INSERT INTO collection_grant_acl (grantId, assetId, benchmarkId, access, modifiedUserId, modifiedDate) SELECT
cg.grantId,
sa.assetId,
sa.benchmarkId,
'rw',
null,
null
FROM
user_stig_asset_map usa
left join stig_asset_map sa using (saId)
left join asset a on sa.assetId = a.assetId
left join collection_grant cg on (a.collectionId = cg.collectionId and usa.userId = cg.userId )
WHERE
cg.roleId = 1`,
`DROP TABLE user_stig_asset_map`
]
const downMigration = [
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0037.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
const [cols] = await pool.query('SHOW COLUMNS FROM user_data')
const colNames = cols.map(row => row.Field)
const colStatements = []
if (!colNames.includes('status')) {
colStatements.push(`ALTER TABLE user_data ADD COLUMN status ENUM('available', 'unavailable') NOT NULL DEFAULT 'available' AFTER lastClaims`)
colStatements.push(`ALTER TABLE user_data ADD INDEX INDEX_status (status ASC)`)
}
if (!colNames.includes('statusDate')) {
colStatements.push(`ALTER TABLE user_data ADD COLUMN statusDate DATETIME NOT NULL DEFAULT (created) AFTER status`)
}
if (!colNames.includes('statusUser')) {
colStatements.push(`ALTER TABLE user_data ADD COLUMN statusUser INT NULL DEFAULT NULL AFTER statusDate`)
}
if (colStatements.length === 0) {
logger.writeInfo('mysql', 'migration', {status: 'skipped', name: migrationName })
return
}
for (const statement of colStatements) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement })
await pool.query(statement)
}
}
module.exports = {
up: async pool => {
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', {status: 'finish', migrationName })
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', migrationName, message: e.message })
throw (e)
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0038.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
// Check if columns exist before adding them
const [cols] = await pool.query('SHOW COLUMNS FROM stig_asset_map')
const colNames = cols.map(row => row.Field)
// Define statements for adding columns
const colStatements = []
if (!colNames.includes('assessedHighCount')) {
colStatements.push(`ALTER TABLE stig_asset_map ADD COLUMN assessedHighCount INT DEFAULT NULL`)
}
if (!colNames.includes('assessedMediumCount')) {
colStatements.push(`ALTER TABLE stig_asset_map ADD COLUMN assessedMediumCount INT DEFAULT NULL`)
}
if (!colNames.includes('assessedLowCount')) {
colStatements.push(`ALTER TABLE stig_asset_map ADD COLUMN assessedLowCount INT DEFAULT NULL`)
}
// Execute column addition statements
for (const statement of colStatements) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement })
await pool.query(statement)
}
// Update the columns with calculated values
const updateStatement = `
UPDATE stig_asset_map sam
JOIN (
SELECT
sa.assetId,
sa.benchmarkId,
sum(CASE WHEN (review.resultId in (2,3,4)) and rgr.severity='high' THEN 1 ELSE 0 END) as assessedHighCount,
sum(CASE WHEN (review.resultId in (2,3,4)) and rgr.severity='medium' THEN 1 ELSE 0 END) as assessedMediumCount,
sum(CASE WHEN (review.resultId in (2,3,4)) and rgr.severity='low' THEN 1 ELSE 0 END) as assessedLowCount
FROM
asset a
left join stig_asset_map sa using (assetId)
left join default_rev dr on (sa.benchmarkId = dr.benchmarkId and a.collectionId = dr.collectionId)
left join rev_group_rule_map rgr on dr.revId = rgr.revId
left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId
left join review on (rvcd.version=review.version and rvcd.checkDigest=review.checkDigest and review.assetId=sa.assetId)
inner join collection c on c.collectionId = a.collectionId
WHERE
a.state = "enabled"
and c.state = "enabled"
GROUP BY
sa.assetId,
sa.benchmarkId
) src ON sam.assetId = src.assetId AND sam.benchmarkId = src.benchmarkId
SET
sam.assessedHighCount = src.assessedHighCount,
sam.assessedMediumCount = src.assessedMediumCount,
sam.assessedLowCount = src.assessedLowCount`
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement: updateStatement })
await pool.query(updateStatement)
}
module.exports = {
up: async pool => {
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', {status: 'finish', migrationName })
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', migrationName, message: e.message })
throw (e)
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0039.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const defaultImportOptions = {
autoStatus: 'saved',
unreviewed: 'commented',
unreviewedCommented: 'informational',
emptyDetail: 'replace',
emptyComment: 'ignore',
allowCustom: true
}
const schemaEnums = {
autoStatus: ["null", 'saved', 'submitted', 'accepted'],
unreviewed: ['never', 'commented', 'always'],
unreviewedCommented: ['notchecked', 'informational'],
emptyDetail: ['ignore', 'import', 'replace'],
emptyComment: ['ignore', 'import', 'replace'],
allowCustom: [true, false]
}
const isValidImportOptions = (options) => {
if (!options || typeof options !== 'object') return false
const allowedKeys = Object.keys(defaultImportOptions)
// contain only the allowed keys
const optionKeys = Object.keys(options)
if (optionKeys.length !== allowedKeys.length) return false
if (!optionKeys.every(key => allowedKeys.includes(key))) return false
// Each value must be valid for its key
for (const key of allowedKeys) {
const allowedValues = schemaEnums[key]
if (!allowedValues.includes(options[key])) return false
}
return true
}
const upFn = async (pool, migrationName) => {
const connection = await pool.getConnection()
const collectionsData = await connection.query(`SELECT c.collectionId, c.settings, c.metadata FROM collection c`)
const collections = collectionsData[0]
const updates = []
for(const { collectionId, metadata, } of collections) {
let importOptions = metadata?.importOptions
if (typeof importOptions === 'string') {
try {
importOptions = JSON.parse(importOptions)
} catch (e) {
importOptions = null // will be replaced with defaultImportOptions
}
}
const finalOptions = isValidImportOptions(importOptions) ? importOptions : defaultImportOptions
updates.push({
collectionId,
importOptions: finalOptions
})
}
logger.writeInfo('mysql', 'migration', {
status: 'running',
name: migrationName,
updates: updates.length
})
// get connection
await connection.query(`SET @json = ?`, [JSON.stringify(updates)])
await connection.query(`UPDATE
collection c
LEFT JOIN
JSON_TABLE(@json, '$[*]' COLUMNS(
collectionId INT PATH '$.collectionId',
importOptions JSON PATH '$.importOptions'
)) as jt on c.collectionId = jt.collectionId
SET
c.settings = JSON_SET(c.settings, '$.importOptions', jt.importOptions),
c.metadata = JSON_REMOVE(c.metadata, '$.importOptions')`)
await connection.release()
}
module.exports = {
up: async pool => {
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', {status: 'finish', migrationName })
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', migrationName, message: e.message })
throw (e)
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0040.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
const connection = await pool.getConnection()
const [collectionsData] = await connection.query(`
SELECT collectionId, settings
FROM collection
`)
const updates = []
for (const { collectionId, settings } of collectionsData) {
const legacyValue = settings.importOptions.autoStatus
updates.push({
collectionId,
autoStatus: {
fail: legacyValue,
notapplicable: legacyValue,
pass: legacyValue
}
})
}
logger.writeInfo('mysql', 'migration', {
status: 'running',
name: migrationName,
updates: updates.length,
data: updates
})
await connection.query(`SET @json = ?`, [JSON.stringify(updates)])
const updateStatement = `
UPDATE collection c
LEFT JOIN
JSON_TABLE(@json, '$[*]' COLUMNS(
collectionId INT PATH '$.collectionId',
autoStatus JSON PATH '$.autoStatus'
)) as jt
ON c.collectionId = jt.collectionId
SET c.settings = JSON_SET(c.settings, '$.importOptions.autoStatus', jt.autoStatus)
`
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement: updateStatement })
await connection.query(updateStatement)
await connection.release()
}
module.exports = {
up: async pool => {
try {
logger.writeInfo('mysql', 'migration', { status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', { status: 'finish', migrationName })
} catch (e) {
logger.writeError('mysql', 'migration', { status: 'error', migrationName, message: e.message })
throw e
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0041.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
const connection = await pool.getConnection()
// drop indexes that use virtual isEnabled column
// check if the indexes exist before dropping them
const [assetIndexExists] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.STATISTICS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'asset'
AND INDEX_NAME = 'INDEX_NAME_COLLECTION_ENABLED'`)
const [collectionIndexExists] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.STATISTICS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'collection'
AND INDEX_NAME = 'index2'`)
// If the indexes exist, drop them
if( assetIndexExists[0].count > 0) {
const dropEnabledAssetIndex = `ALTER TABLE asset DROP INDEX INDEX_NAME_COLLECTION_ENABLED`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: dropEnabledAssetIndex })
await connection.query(dropEnabledAssetIndex)
}
if( collectionIndexExists[0].count > 0) {
const dropEnabledCollectionIndex = `ALTER TABLE collection DROP INDEX index2`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: dropEnabledCollectionIndex })
await connection.query(dropEnabledCollectionIndex)
}
// Drop old virtual isEnabled column on 'asset' if it exists
const [assetColumnsDrop] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'asset'
AND COLUMN_NAME = 'isEnabled'`)
if (assetColumnsDrop[0].count > 0) {
const dropEnabledAssetColumn = `ALTER TABLE asset DROP COLUMN isEnabled`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: dropEnabledAssetColumn })
await connection.query(dropEnabledAssetColumn)
}
// Drop old virtual isEnabled column on 'collection' if it exists
const [collectionColumnsDrop] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'collection'
AND COLUMN_NAME = 'isEnabled'`)
if (collectionColumnsDrop[0].count > 0) {
const dropEnabledCollectionColumn = `ALTER TABLE collection DROP COLUMN isEnabled`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: dropEnabledCollectionColumn })
await connection.query(dropEnabledCollectionColumn)
}
// Check if 'isEnabled' exists on 'asset'
const [assetColumns] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'asset'
AND COLUMN_NAME = 'isEnabled'`)
// If it does not exist, create the new stored column
if (assetColumns[0].count === 0) {
const createEnabledAssetColumn = `
ALTER TABLE asset ADD COLUMN isEnabled
TINYINT GENERATED ALWAYS AS (CASE WHEN state = 'enabled' THEN 1 ELSE NULL END) STORED`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: createEnabledAssetColumn })
await connection.query(createEnabledAssetColumn)
}
// Check if 'isEnabled' exists on 'collection'
const [collectionColumns] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'collection'
AND COLUMN_NAME = 'isEnabled'`)
// If it does not exist, create the new stored column
if (collectionColumns[0].count === 0) {
const createEnabledCollectionColumn = `
ALTER TABLE collection ADD COLUMN isEnabled
TINYINT GENERATED ALWAYS AS (CASE WHEN state = 'enabled' THEN 1 ELSE NULL END) STORED`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: createEnabledCollectionColumn })
await connection.query(createEnabledCollectionColumn)
}
// recreate indexes for new stored isEnabled column
const [assetIndexes] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.STATISTICS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'asset'
AND INDEX_NAME = 'INDEX_NAME_COLLECTION_ENABLED'`)
// If the index does not exist, create it
if (assetIndexes[0].count === 0) {
const createEnabledAssetIndex = `ALTER TABLE asset ADD UNIQUE INDEX INDEX_NAME_COLLECTION_ENABLED (name, collectionId, isEnabled)`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: createEnabledAssetIndex })
await connection.query(createEnabledAssetIndex)
}
const [collectionIndexes] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.STATISTICS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'collection'
AND INDEX_NAME = 'index2'`)
if (collectionIndexes[0].count === 0) {
const createEnabledCollectionIndex = `ALTER TABLE collection ADD UNIQUE INDEX index2 (name, isEnabled)`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: createEnabledCollectionIndex })
await connection.query(createEnabledCollectionIndex)
}
// create or replace new views
const createEnabledAssetView = `CREATE OR REPLACE VIEW enabled_asset AS SELECT * FROM asset WHERE state = 'enabled'`
const createEnabledCollectionView = `CREATE OR REPLACE VIEW enabled_collection AS SELECT * FROM collection WHERE state = 'enabled'`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: createEnabledAssetView })
await connection.query(createEnabledAssetView)
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: createEnabledCollectionView })
await connection.query(createEnabledCollectionView)
await connection.release()
}
module.exports = {
up: async (pool) => {
try {
logger.writeInfo('mysql', 'migration', { status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', { status: 'finish', migrationName })
} catch (e) {
logger.writeError('mysql', 'migration', { status: 'error', migrationName, message: e.message })
throw e
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0042.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`ALTER TABLE revision ADD COLUMN marking VARCHAR(10) DEFAULT NULL AFTER statusDate`,
`ALTER TABLE current_rev ADD COLUMN marking VARCHAR(10) DEFAULT NULL AFTER statusDate`,
`ALTER VIEW v_current_rev AS
select
rr.revId AS revId,
rr.benchmarkId AS benchmarkId,
rr.\`version\` AS \`version\`,
rr.\`release\` AS \`release\`,
rr.benchmarkDate AS benchmarkDate,
rr.benchmarkDateSql AS benchmarkDateSql,
rr.status AS status,
rr.statusDate AS statusDate,
rr.marking AS marking,
rr.description AS description,
rr.active AS active,
rr.groupCount AS groupCount,
rr.ruleCount AS ruleCount,
rr.lowCount AS lowCount,
rr.mediumCount AS mediumCount,
rr.highCount AS highCount,
rr.checkCount AS checkCount,
rr.fixCount AS fixCount from (select r.revId AS revId,
r.benchmarkId AS benchmarkId,
r.\`version\` AS \`version\`,
r.\`release\` AS \`release\`,
r.benchmarkDate AS benchmarkDate,
r.benchmarkDateSql AS benchmarkDateSql,
r.status AS status,
r.statusDate AS statusDate,
r.marking AS marking,
r.description AS description,
r.active AS active,
r.groupCount AS groupCount,
r.ruleCount AS ruleCount,
r.lowCount AS lowCount,
r.mediumCount AS mediumCount,
r.highCount AS highCount,
r.checkCount AS checkCount,
r.fixCount AS fixCount,
row_number() OVER (PARTITION BY r.benchmarkId ORDER BY field(r.status,
'draft',
'accepted') desc,
(r.\`version\` + 0) desc,
(r.\`release\` + 0) desc ) AS rn from revision r) rr where (rr.rn = 1)`
]
const downMigration = [
`ALTER TABLE revision DROP COLUMN marking`,
`ALTER TABLE current_rev DROP COLUMN marking`
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0043.js
================================================
const logger = require('../../utils/logger')
const path = require('node:path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
const connection = await pool.getConnection()
// webPreferences column exists on user_data
const [cols] = await connection.query(`
SELECT COUNT(*) AS count FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_SCHEMA = DATABASE()
AND TABLE_NAME = 'user_data'
AND COLUMN_NAME = 'webPreferences'`)
// If it does not exist, create the webPreferences column
if (cols[0].count === 0) {
const addWebPreferencesColumn = `
ALTER TABLE user_data ADD COLUMN webPreferences JSON NOT NULL DEFAULT ('{"darkMode": true, "lastWhatsNew": "2000-01-01"}')`
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: addWebPreferencesColumn })
await connection.query(addWebPreferencesColumn)
}
await connection.release()
}
module.exports = {
up: async (pool) => {
try {
logger.writeInfo('mysql', 'migration', { status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', { status: 'finish', migrationName })
} catch (e) {
logger.writeError('mysql', 'migration', { status: 'error', migrationName, message: e.message })
throw e
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0044.js
================================================
const Importer = require('./lib/mysql-import.js')
const logger = require('../../utils/logger')
const path = require('path')
const migrationName = path.basename(__filename, '.js')
const upFn = async (pool, migrationName) => {
const connection = await pool.getConnection()
try {
// Truncate tables to remove all existing CCI data
const truncateCci = 'TRUNCATE TABLE `cci`'
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: 'TRUNCATE cci' })
await connection.query(truncateCci)
const truncateCciRefMap = 'TRUNCATE TABLE `cci_reference_map`'
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, statement: 'TRUNCATE cci_reference_map' })
await connection.query(truncateCciRefMap)
// Import Rev 5 CCI data from the current directory
const sqlFile = path.join(__dirname, 'sql', 'current', '31-rev5-cci-data.sql')
logger.writeInfo('mysql', 'migration', { status: 'running', name: migrationName, file: '31-rev5-cci-data.sql' })
const importer = new Importer(pool)
await importer.import(sqlFile)
} finally {
await connection.release()
}
}
module.exports = {
up: async (pool) => {
try {
logger.writeInfo('mysql', 'migration', { status: 'start', direction: 'up', migrationName })
await upFn(pool, migrationName)
logger.writeInfo('mysql', 'migration', { status: 'finish', migrationName })
} catch (e) {
logger.writeError('mysql', 'migration', { status: 'error', migrationName, message: e.message })
throw e
}
},
down: () => {}
}
================================================
FILE: api/source/service/migrations/0045.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`DROP TABLE IF EXISTS job_task_map`,
`DROP TABLE IF EXISTS task_output`,
`DROP TABLE IF EXISTS task`,
`DROP TABLE IF EXISTS job_run`,
`DROP TABLE IF EXISTS job`,
// table to hold each maintenance task, its name and its stored procedure command
`CREATE TABLE task (
taskId INT NOT NULL AUTO_INCREMENT,
name VARCHAR(45) NOT NULL,
description VARCHAR(255) NULL,
command VARCHAR(255) NOT NULL,
PRIMARY KEY (taskId),
UNIQUE INDEX idx_task_name (name)
)`,
`INSERT INTO task (taskId, name, description, command) VALUES
(1, 'WipeDeletedObjects', 'Wipe deleted collections and assets and their associated reviews', 'delete_disabled()'),
(2, 'DeleteUnmappedReviews', 'Delete reviews that no longer match any rule in the system', 'delete_unmapped("system")'),
(3, 'DeleteUnmappedAssetReviews', 'Delete reviews that no longer match an asset''s assigned rules', 'delete_unmapped("asset")'),
(4, 'AnalyzeReviewTables', 'Analyze database tables for performance', 'analyze_tables(JSON_ARRAY("reviews", "review_history"))')
`,
// table to hold each maintenance job, with its name, metadata user attributes
// users who have created or updated a job must exist in user_data table
`CREATE TABLE job (
jobId INT NOT NULL AUTO_INCREMENT,
name VARCHAR(45) NOT NULL,
description VARCHAR(255) NULL,
createdBy INT NULL,
updatedBy INT NULL,
created TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
updated TIMESTAMP(3) NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP(3),
PRIMARY KEY (jobId),
UNIQUE INDEX idx_job_name (name),
CONSTRAINT fk_job_updatedBy FOREIGN KEY (updatedBy) REFERENCES user_data(userId) ON DELETE RESTRICT,
CONSTRAINT fk_job_createdBy FOREIGN KEY (createdBy) REFERENCES user_data(userId) ON DELETE RESTRICT
)`,
// initial jobs with fixed jobIds for reference in code
`INSERT INTO job ( jobId, name, description, createdBy) VALUES
(1, 'Cleanup Database', 'Wipe deleted collections and assets and their associated reviews', null),
(2, 'Delete Unmapped Reviews', 'Delete reviews that no longer match any rule in the system', null),
(3, 'Delete Unmapped Asset Reviews', 'Delete reviews that no longer match an asset''s assigned rules', null)
`,
`ALTER TABLE job AUTO_INCREMENT = 100`,
// mapping jobs to tasks
// if a job or task is deleted, the mapping is deleted too
// defines the execution order (via jtId insertion order)
`CREATE TABLE job_task_map (
jtId INT NOT NULL AUTO_INCREMENT,
jobId INT NOT NULL,
taskId INT NOT NULL,
created TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
updated TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) ON UPDATE CURRENT_TIMESTAMP(3),
PRIMARY KEY (jtId),
CONSTRAINT fk_job_task_jobId FOREIGN KEY (jobId) REFERENCES job(jobId) ON DELETE CASCADE,
CONSTRAINT fk_job_task_taskId FOREIGN KEY (taskId) REFERENCES task(taskId) ON DELETE CASCADE
)`,
// pre map initial jobs to tasks
`INSERT INTO job_task_map (jtId, jobId, taskId) VALUES
(1, 1, 1),
(2, 1, 4),
(3, 2, 2),
(4, 2, 4),
(5, 3, 3),
(6, 3, 4)
`,
`ALTER TABLE job_task_map AUTO_INCREMENT = 1000`,
// table to hold each run of a job, its state and timestamps
`CREATE TABLE job_run (
jrId INT NOT NULL AUTO_INCREMENT,
jobId INT NOT NULL,
runId BINARY(16) NOT NULL,
state VARCHAR(255) NULL,
created TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
updated TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) ON UPDATE CURRENT_TIMESTAMP(3),
PRIMARY KEY (jrId),
UNIQUE INDEX idx_job_run_runId (runId),
CONSTRAINT fk_job_run_jobId FOREIGN KEY (jobId) REFERENCES job(jobId) ON DELETE CASCADE
)`,
`DROP TABLE IF EXISTS task_output`,
// captures output from stored procedures
// runid must exist in job_run table
// taskid must match a task
`CREATE TABLE task_output (
seq INT NOT NULL AUTO_INCREMENT,
ts TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
runId BINARY(16) NULL,
taskId INT NULL,
type VARCHAR(45) NOT NULL,
message VARCHAR(255) NOT NULL,
PRIMARY KEY (seq),
CONSTRAINT fk_task_output_runId FOREIGN KEY (runId) REFERENCES job_run(runId) ON DELETE CASCADE,
CONSTRAINT fk_task_output_taskId FOREIGN KEY (taskId) REFERENCES task(taskId) ON DELETE CASCADE
)`,
`DROP procedure IF EXISTS run_job`,
// takes in a jobId and optional runId
// cursor is a pointer that can iterate through rows for the parameter in_jobId, get all task names and commands mapped to that job in order of execution
// declare continue: : when the cursor has no more rows, set v_done to true
// declare exit: if any SQL exception occurs, log it and set the job run state to failed
// @runId is the binary(16) uuid for this job run it could be null so we can generate one
// @taskId is the current task being executed, null if no task is running
// INSERT INTO job_run = create new job run record with the runId
// OPEN curr == -- opening the cursor which contains all tasks info for this job
// FETCH curr -- pulls a single task from the cursor
// SET @sql = CONCAT('CALL ', v_currentCommand); -- create the sql to run the task's stored procedure command
// SET @taskId = NULL; -- clear the current task id and log task end
`CREATE PROCEDURE run_job(
IN in_jobId INT,
IN in_runIdStr VARCHAR(36)
)
main:BEGIN
DECLARE v_done INT DEFAULT FALSE;
DECLARE v_jrId INT;
DECLARE v_numTasks INT;
DECLARE v_currentTaskId INT;
DECLARE v_currentTaskName VARCHAR(255);
DECLARE v_currentCommand VARCHAR(255);
DECLARE v_currentTaskNum INT DEFAULT 0;
DECLARE v_param_string TEXT;
DECLARE cur CURSOR FOR
SELECT
jt.taskId,
t.name,
t.command
FROM
job_task_map jt
inner join task t on (jt.taskId = t.taskId)
WHERE
jobId = in_jobId
ORDER BY jtId ASC;
DECLARE CONTINUE HANDLER FOR NOT FOUND SET v_done = TRUE;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1 err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error', concat('code: ', err_code, ' message: ', err_msg));
UPDATE job_run SET state = 'failed' WHERE runId = @runId;
END;
-- setup runtime context (null if running outside a job)
IF in_runIdStr IS NOT NULL AND in_runIdStr REGEXP '^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$' THEN
SET @runId = UUID_TO_BIN(in_runIdStr, 1);
ELSE
SET @runId = UUID_TO_BIN(UUID(), 1);
END IF;
SET @taskId = NULL;
INSERT INTO job_run(jobId, runId, state) VALUES (in_jobId, @runId, 'running');
CALL task_output('info', concat('run started for jobId ', in_jobId));
-- Get the number of tasks for the job
SELECT COUNT(*) INTO v_numTasks FROM job_task_map WHERE jobId = in_jobId;
IF v_numTasks = 0 THEN
CALL task_output('error', 'no tasks to run');
UPDATE job_run SET state = 'failed' WHERE runId = @runId AND state = 'running';
LEAVE main; -- No tasks to run, exit the procedure
END IF;
OPEN cur;
read_loop: LOOP
FETCH cur INTO v_currentTaskId, v_currentTaskName, v_currentCommand;
IF v_done THEN
LEAVE read_loop;
END IF;
SET v_currentTaskNum = v_currentTaskNum + 1;
SET @sql = CONCAT('CALL ', v_currentCommand);
PREPARE stmt_run_job FROM @sql;
CALL task_output('info', concat('Beginning task ', v_currentTaskName, ' (', v_currentTaskNum, '/', v_numTasks, ')'));
SET @taskId = v_currentTaskId;
EXECUTE stmt_run_job;
DEALLOCATE PREPARE stmt_run_job;
SET @taskId = NULL;
CALL task_output('info', concat('Ended task ', v_currentTaskName, ' (', v_currentTaskNum, '/', v_numTasks, ')'));
END LOOP;
CLOSE cur;
-- === Post-task-loop logic ===
UPDATE job_run SET state = 'completed' WHERE runId = @runId AND state = 'running';
CALL task_output('info', concat('run completed for jobId ', in_jobId));
END`,
`DROP procedure IF EXISTS task_output`,
// write a message to the task_output table
// if in_message is null, set it to empty string
// insert into task_output = -- INSERT a row into task_output(runId, taskId, type, message) using: runId = @runId (set by run_job) taskId = @taskId (set around each task) type = in_type (e.g., 'info', 'error') message= in_message
`CREATE PROCEDURE task_output(
IN in_type VARCHAR(45),
IN in_message VARCHAR(255)
)
BEGIN
IF in_message IS NULL THEN SET in_message = ''; END IF;
insert into task_output (runId, taskId, type, message) values (@runId, @taskId, in_type, in_message);
END`,
// deleted disabled objects in batches, uses the variables to "page"? through deletes
// uses temporary tables to hold ids to delete
`DROP PROCEDURE IF EXISTS delete_disabled`,
`CREATE PROCEDURE delete_disabled()
BEGIN
DECLARE v_incrementValue INT DEFAULT 10000;
DECLARE v_curMinId BIGINT DEFAULT 1;
DECLARE v_curMaxId BIGINT DEFAULT v_incrementValue + 1;
DECLARE v_numCollectionIds INT;
DECLARE v_numAssetIds INT;
DECLARE v_numReviewIds INT;
DECLARE v_numHistoryIds INT;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1 err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error', concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info','task started');
drop temporary table if exists t_collectionIds;
create temporary table t_collectionIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select collectionId from collection where isEnabled is null;
select max(seq) into v_numCollectionIds from t_collectionIds;
CALL task_output('info', concat('found ', ifnull(v_numCollectionIds, 0), ' collections to delete'));
drop temporary table if exists t_assetIds;
create temporary table t_assetIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select assetId from asset where isEnabled is null or collectionId in (select collectionId from t_collectionIds);
select max(seq) into v_numAssetIds from t_assetIds;
CALL task_output('info', concat('found ', ifnull(v_numAssetIds, 0), ' assets to delete'));
drop temporary table if exists t_reviewIds;
create temporary table t_reviewIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select reviewId from review where assetId in (select assetId from t_assetIds);
select max(seq) into v_numReviewIds from t_reviewIds;
CALL task_output('info', concat('found ', ifnull(v_numReviewIds, 0), ' reviews to delete'));
drop temporary table if exists t_historyIds;
create temporary table t_historyIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select historyId from review_history where reviewId in (select reviewId from t_reviewIds);
select max(seq) into v_numHistoryIds from t_historyIds;
CALL task_output('info', concat('found ', ifnull(v_numHistoryIds, 0), ' history records to delete'));
IF v_numHistoryIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numHistoryIds, ' history records'));
REPEAT
delete from review_history where historyId IN (
select historyId from t_historyIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_historyIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numReviewIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numReviewIds, ' reviews'));
REPEAT
delete from review where reviewId IN (
select reviewId from t_reviewIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_reviewIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numAssetIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numAssetIds, ' assets'));
REPEAT
delete from asset where assetId IN (
select assetId from t_assetIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_assetIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numCollectionIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numCollectionIds, ' collections'));
REPEAT
delete from collection where collectionId IN (
select collectionId from t_collectionIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_collectionIds;
CALL task_output('info', 'task finished');
END`,
`DROP PROCEDURE IF EXISTS delete_unmapped`,
// deletes unmapped reviews in batches
// deletes by system and asset
// system is reviews that dont match a rule in rev_group_rule_map
// asset is reviews that dont match a rule assigned to the asset via rev_group_rule_map, revision, and stig_asset_map
// in_context is a param that is either 'system' or 'asset'
// IF in_context = 'system' insert into t_reviewIds the reviewIds to delete
// IF v_numReviewIds > 0 THEN -- if there are reviews to delete, delete their history first, then the reviews
// IF v_numHistoryIds > 0 THEN -- if there are history records to delete, delete them first
// REPEAT delete from review_history where historyId IN ( select ... -- delete in batches until no more rows deleted(do while loop basically)
`CREATE PROCEDURE delete_unmapped(IN in_context VARCHAR(255))
BEGIN
DECLARE v_numReviewIds INT;
DECLARE v_numHistoryIds INT;
DECLARE v_incrementValue INT DEFAULT 10000;
DECLARE v_curMinId BIGINT DEFAULT 1;
DECLARE v_curMaxId BIGINT DEFAULT v_incrementValue + 1;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1
err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error',concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info', 'task started');
drop temporary table if exists t_reviewIds;
create temporary table t_reviewIds (seq INT AUTO_INCREMENT PRIMARY KEY, reviewId INT);
-- Context-specific logic
IF in_context = 'system' THEN
INSERT into t_reviewIds (reviewId)
select r.reviewId from review r
left join rev_group_rule_map rgr on (r.version = rgr.version and r.checkDigest = rgr.checkDigest)
where rgr.rgrId is null;
ELSEIF in_context = 'asset' THEN
INSERT into t_reviewIds (reviewId)
select
r.reviewId
from
review r
left join rev_group_rule_map rgr on (r.version = rgr.version and r.checkDigest = rgr.checkDigest)
left join revision on (rgr.revId = revision.revId)
left join stig_asset_map sa on (r.assetId = sa.assetId and revision.benchmarkId = sa.benchmarkId)
group by
r.reviewId
having
count(sa.saId) = 0;
END IF;
select max(seq) into v_numReviewIds from t_reviewIds;
CALL task_output('info', concat('found ', ifnull(v_numReviewIds, 0), ' reviews to delete'));
IF v_numReviewIds > 0 THEN
drop temporary table if exists t_historyIds;
create temporary table t_historyIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select historyId from review_history where reviewId in (select reviewId from t_reviewIds);
select max(seq) into v_numHistoryIds from t_historyIds;
CALL task_output('info', concat('found ', ifnull(v_numHistoryIds, 0), ' history records to delete'));
IF v_numHistoryIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numHistoryIds, ' history records'));
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
REPEAT
delete from review_history where historyId IN (
select historyId from t_historyIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
CALL task_output('info', concat('deleting ', v_numReviewIds, ' reviews'));
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
REPEAT
delete from review where reviewId IN (
select reviewId from t_reviewIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
CALL task_output('info', 'task finished');
END;`,
`DROP PROCEDURE IF EXISTS analyze_tables`,
// analyzes tables for performance
// in_tables is a json array of table names to analyze
`CREATE PROCEDURE analyze_tables (IN in_tables JSON)
BEGIN
DECLARE v_itemCount INT;
DECLARE v_currentCount INT;
DECLARE v_table VARCHAR(255);
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1
err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
IF err_msg = NULL THEN
SET err_msg = '';
END IF;
CALL task_output('error',concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info', 'task started');
select JSON_LENGTH(in_tables) INTO v_itemCount;
SET v_currentCount = 0;
WHILE v_currentCount < v_itemCount DO
SET v_table = json_unquote(json_extract(in_tables, concat('$[', v_currentCount, ']')));
CALL task_output('info', concat('analyze table: ', v_table));
SET @sql = CONCAT('ANALYZE TABLE ', v_table);
PREPARE stmt_analyze_tables FROM @sql;
EXECUTE stmt_analyze_tables;
DEALLOCATE PREPARE stmt_analyze_tables;
SET v_currentCount = v_currentCount + 1;
END WHILE;
CALL task_output('info', 'task finished');
END`,
`DROP EVENT IF EXISTS \`job-1-stigman\``,
// default event schedule for job 1 created at migration time
`CREATE EVENT IF NOT EXISTS \`job-1-stigman\`
ON SCHEDULE EVERY 1 DAY
STARTS '2025-10-01 05:00:00'
DISABLE
DO
CALL run_job(1, NULL)`,
]
const downMigration = [
`DROP TABLE IF EXISTS job_task_map`,
`DROP TABLE IF EXISTS task_output`,
`DROP TABLE IF EXISTS task`,
`DROP TABLE IF EXISTS job_run`,
`DROP TABLE IF EXISTS job`,
`DROP procedure IF EXISTS run_job`,
`DROP procedure IF EXISTS task_output`,
`DROP PROCEDURE IF EXISTS delete_disabled`,
`DROP PROCEDURE IF EXISTS delete_unmapped`,
`DROP PROCEDURE IF EXISTS analyze_tables`,
`DROP EVENT IF EXISTS \`job-1-stigman\``,
]
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/0046.js
================================================
const MigrationHandler = require('./lib/MigrationHandler')
const upMigration = [
`DROP PROCEDURE IF EXISTS get_runtime`,
`DROP procedure IF EXISTS run_job`,
`CREATE PROCEDURE run_job(
IN in_jobId INT,
IN in_runIdStr VARCHAR(36)
)
main:BEGIN
DECLARE v_done INT DEFAULT FALSE;
DECLARE v_jrId INT;
DECLARE v_numTasks INT;
DECLARE v_currentTaskId INT;
DECLARE v_currentTaskName VARCHAR(255);
DECLARE v_currentCommand VARCHAR(255);
DECLARE v_currentTaskNum INT DEFAULT 0;
DECLARE v_param_string TEXT;
DECLARE cur CURSOR FOR
SELECT
jt.taskId,
t.name,
t.command
FROM
job_task_map jt
inner join task t on (jt.taskId = t.taskId)
WHERE
jobId = in_jobId
ORDER BY jtId ASC;
DECLARE CONTINUE HANDLER FOR NOT FOUND SET v_done = TRUE;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1 err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error', concat('code: ', err_code, ' message: ', err_msg));
UPDATE job_run SET state = 'failed' WHERE runId = @runId;
END;
-- setup runtime context (null if running outside a job)
IF in_runIdStr IS NOT NULL AND in_runIdStr REGEXP '^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$' THEN
SET @runId = UUID_TO_BIN(in_runIdStr, 1);
ELSE
SET @runId = UUID_TO_BIN(UUID(), 1);
END IF;
SET @taskId = NULL;
INSERT INTO job_run(jobId, runId, state) VALUES (in_jobId, @runId, 'running');
CALL task_output('info', concat('run started for jobId ', in_jobId));
-- Get the number of tasks for the job
SELECT COUNT(*) INTO v_numTasks FROM job_task_map WHERE jobId = in_jobId;
IF v_numTasks = 0 THEN
CALL task_output('error', 'no tasks to run');
UPDATE job_run SET state = 'failed' WHERE runId = @runId AND state = 'running';
LEAVE main; -- No tasks to run, exit the procedure
END IF;
OPEN cur;
read_loop: LOOP
FETCH cur INTO v_currentTaskId, v_currentTaskName, v_currentCommand;
IF v_done THEN
LEAVE read_loop;
END IF;
SET v_currentTaskNum = v_currentTaskNum + 1;
SET @sql = CONCAT('CALL ', v_currentCommand);
PREPARE stmt_run_job FROM @sql;
CALL task_output('info', concat('Beginning task ', v_currentTaskName, ' (', v_currentTaskNum, '/', v_numTasks, ')'));
SET @taskId = v_currentTaskId;
EXECUTE stmt_run_job;
DEALLOCATE PREPARE stmt_run_job;
SET @taskId = NULL;
CALL task_output('info', concat('Ended task ', v_currentTaskName, ' (', v_currentTaskNum, '/', v_numTasks, ')'));
END LOOP;
CLOSE cur;
-- === Post-task-loop logic ===
UPDATE job_run SET state = 'completed' WHERE runId = @runId AND state = 'running';
CALL task_output('info', concat('run completed for jobId ', in_jobId));
END`,
`DROP procedure IF EXISTS task_output`,
`CREATE PROCEDURE task_output(
IN in_type VARCHAR(45),
IN in_message VARCHAR(255)
)
BEGIN
IF in_message IS NULL THEN SET in_message = ''; END IF;
insert into task_output (runId, taskId, type, message) values (@runId, @taskId, in_type, in_message);
END`,
`DROP PROCEDURE IF EXISTS delete_disabled`,
`CREATE PROCEDURE delete_disabled()
BEGIN
DECLARE v_incrementValue INT DEFAULT 10000;
DECLARE v_curMinId BIGINT DEFAULT 1;
DECLARE v_curMaxId BIGINT DEFAULT v_incrementValue + 1;
DECLARE v_numCollectionIds INT;
DECLARE v_numAssetIds INT;
DECLARE v_numReviewIds INT;
DECLARE v_numHistoryIds INT;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1 err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error', concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info','task started');
drop temporary table if exists t_collectionIds;
create temporary table t_collectionIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select collectionId from collection where isEnabled is null;
select max(seq) into v_numCollectionIds from t_collectionIds;
CALL task_output('info', concat('found ', ifnull(v_numCollectionIds, 0), ' collections to delete'));
drop temporary table if exists t_assetIds;
create temporary table t_assetIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select assetId from asset where isEnabled is null or collectionId in (select collectionId from t_collectionIds);
select max(seq) into v_numAssetIds from t_assetIds;
CALL task_output('info', concat('found ', ifnull(v_numAssetIds, 0), ' assets to delete'));
drop temporary table if exists t_reviewIds;
create temporary table t_reviewIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select reviewId from review where assetId in (select assetId from t_assetIds);
select max(seq) into v_numReviewIds from t_reviewIds;
CALL task_output('info', concat('found ', ifnull(v_numReviewIds, 0), ' reviews to delete'));
drop temporary table if exists t_historyIds;
create temporary table t_historyIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select historyId from review_history where reviewId in (select reviewId from t_reviewIds);
select max(seq) into v_numHistoryIds from t_historyIds;
CALL task_output('info', concat('found ', ifnull(v_numHistoryIds, 0), ' history records to delete'));
IF v_numHistoryIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numHistoryIds, ' history records'));
REPEAT
delete from review_history where historyId IN (
select historyId from t_historyIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_historyIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numReviewIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numReviewIds, ' reviews'));
REPEAT
delete from review where reviewId IN (
select reviewId from t_reviewIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_reviewIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numAssetIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numAssetIds, ' assets'));
REPEAT
delete from asset where assetId IN (
select assetId from t_assetIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_assetIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numCollectionIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numCollectionIds, ' collections'));
REPEAT
delete from collection where collectionId IN (
select collectionId from t_collectionIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_collectionIds;
CALL task_output('info', 'task finished');
END`,
`DROP PROCEDURE IF EXISTS delete_unmapped`,
`CREATE PROCEDURE delete_unmapped(IN in_context VARCHAR(255))
BEGIN
DECLARE v_numReviewIds INT;
DECLARE v_numHistoryIds INT;
DECLARE v_incrementValue INT DEFAULT 10000;
DECLARE v_curMinId BIGINT DEFAULT 1;
DECLARE v_curMaxId BIGINT DEFAULT v_incrementValue + 1;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1
err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error',concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info', 'task started');
drop temporary table if exists t_reviewIds;
create temporary table t_reviewIds (seq INT AUTO_INCREMENT PRIMARY KEY, reviewId INT);
-- Context-specific logic
IF in_context = 'system' THEN
INSERT into t_reviewIds (reviewId)
select r.reviewId from review r
left join rev_group_rule_map rgr on (r.version = rgr.version and r.checkDigest = rgr.checkDigest)
where rgr.rgrId is null;
ELSEIF in_context = 'asset' THEN
INSERT into t_reviewIds (reviewId)
select
r.reviewId
from
review r
left join rev_group_rule_map rgr on (r.version = rgr.version and r.checkDigest = rgr.checkDigest)
left join revision on (rgr.revId = revision.revId)
left join stig_asset_map sa on (r.assetId = sa.assetId and revision.benchmarkId = sa.benchmarkId)
group by
r.reviewId
having
count(sa.saId) = 0;
END IF;
select max(seq) into v_numReviewIds from t_reviewIds;
CALL task_output('info', concat('found ', ifnull(v_numReviewIds, 0), ' reviews to delete'));
IF v_numReviewIds > 0 THEN
drop temporary table if exists t_historyIds;
create temporary table t_historyIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select historyId from review_history where reviewId in (select reviewId from t_reviewIds);
select max(seq) into v_numHistoryIds from t_historyIds;
CALL task_output('info', concat('found ', ifnull(v_numHistoryIds, 0), ' history records to delete'));
IF v_numHistoryIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numHistoryIds, ' history records'));
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
REPEAT
delete from review_history where historyId IN (
select historyId from t_historyIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
CALL task_output('info', concat('deleting ', v_numReviewIds, ' reviews'));
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
REPEAT
delete from review where reviewId IN (
select reviewId from t_reviewIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
CALL task_output('info', 'task finished');
END;`,
`DROP PROCEDURE IF EXISTS analyze_tables`,
`CREATE PROCEDURE analyze_tables (IN in_tables JSON)
BEGIN
DECLARE v_itemCount INT;
DECLARE v_currentCount INT;
DECLARE v_table VARCHAR(255);
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1
err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
IF err_msg = NULL THEN
SET err_msg = '';
END IF;
CALL task_output('error',concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info', 'task started');
select JSON_LENGTH(in_tables) INTO v_itemCount;
SET v_currentCount = 0;
WHILE v_currentCount < v_itemCount DO
SET v_table = json_unquote(json_extract(in_tables, concat('$[', v_currentCount, ']')));
CALL task_output('info', concat('analyze table: ', v_table));
SET @sql = CONCAT('ANALYZE TABLE ', v_table);
PREPARE stmt_analyze_tables FROM @sql;
EXECUTE stmt_analyze_tables;
DEALLOCATE PREPARE stmt_analyze_tables;
SET v_currentCount = v_currentCount + 1;
END WHILE;
CALL task_output('info', 'task finished');
END`,
]
const downMigration = []
const migrationHandler = new MigrationHandler(upMigration, downMigration)
module.exports = {
up: async (pool) => {
await migrationHandler.up(pool, __filename)
},
down: async (pool) => {
await migrationHandler.down(pool, __filename)
}
}
================================================
FILE: api/source/service/migrations/lib/MigrationHandler.js
================================================
"use strict";
const path = require('path')
const logger = require('../../../utils/logger')
module.exports = class MigrationHandler {
constructor(upCommands = [], downCommands = []) {
this._upCommands = upCommands;
this._downCommands = downCommands;
}
async up(pool, filename) {
let connection
let migrationName = path.basename(filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'up', name: migrationName })
connection = await pool.getConnection()
for (const statement of this._upCommands) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement })
await connection.query(statement)
}
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message })
throw (e)
}
finally {
await connection.release()
logger.writeInfo('mysql', 'migration', {status: 'finish', name: migrationName })
}
}
async down(pool, filename) {
let connection
let migrationName = path.basename(filename, '.js')
try {
logger.writeInfo('mysql', 'migration', {status: 'start', direction: 'down', name: migrationName })
connection = await pool.getConnection()
for (const statement of this._downCommands) {
logger.writeInfo('mysql', 'migration', {status: 'running', name: migrationName, statement })
await connection.query(statement)
}
await connection.release()
}
catch (e) {
logger.writeError('mysql', 'migration', {status: 'error', name: migrationName, message: e.message })
throw (e)
}
finally {
await connection.release()
logger.writeInfo('mysql', 'migration', {status: 'finish', name: migrationName })
}
}
}
================================================
FILE: api/source/service/migrations/lib/mysql-import.js
================================================
/**
* mysql-import - v4.0.24
* Import .sql into a MySQL database with Node.
* @author Rob Parham
* @website https://github.com/pamblam/mysql-import#readme
* @license MIT
*
* Modified to support mysql2 PromisePool
* https://github.com/NUWCDIVNPT/stig-manager/api/source/service/migrations/lib/mysql-import.js
**/
'use strict';
const mysql = require('mysql2');
const fs = require('fs');
const path = require("path");
/**
* mysql-import - Importer class
* @version 4.0.24
* https://github.com/Pamblam/mysql-import
*/
class Importer{
/**
* new Importer(pool)
* @param pool - mysql2/promise pool
*/
constructor(pool){
this._connection_settings = pool;
this._pool = pool;
this._conn = null;
this._encoding = 'utf8';
this._imported = [];
}
/**
* Get an array of the imported files
* @returns {Array}
*/
getImported(){
return this._imported.slice(0);
}
/**
* Set the encoding to be used for reading the dump files.
* @param string - encoding type to be used.
* @throws {Error} - if unsupported encoding type.
* @returns {undefined}
*/
setEncoding(encoding){
var supported_encodings = [
'utf8',
'ucs2',
'utf16le',
'latin1',
'ascii',
'base64',
'hex'
];
if(!supported_encodings.includes(encoding)){
throw new Error("Unsupported encoding: "+encoding);
}
this._encoding = encoding;
}
/**
* Set or change the database to be used
* @param string - database name
* @returns {Promise}
*/
use(database){
return new Promise((resolve, reject)=>{
if(!this._conn){
this._connection_settings.database = database;
return;
}
this._conn.changeUser({database}, err=>{
if (err){
reject(err);
}else{
resolve();
}
});
});
}
/**
* Import (an) .sql file(s).
* @param string|array input - files or paths to scan for .sql files
* @returns {Promise}
*/
import(...input){
return new Promise(async (resolve, reject)=>{
try{
await this._connect();
var files = await this._getSQLFilePaths(...input);
var error = null;
await slowLoop(files, (file, index, next)=>{
if(error){
next();
return;
}
this._importSingleFile(file).then(()=>{
next();
}).catch(err=>{
error = err;
next();
});
});
if(error) throw error;
await this.disconnect();
resolve();
}catch(err){
reject(err);
}
});
};
/**
* Disconnect mysql. This is done automatically, so shouldn't need to be manually called.
* @param bool graceful - force close?
* @returns {Promise}
*/
async disconnect(){
try {
if (!this._conn) {
return
}
await this._conn.release()
this._conn = null
}
catch (e) {
throw (e)
}
}
////////////////////////////////////////////////////////////////////////////
// Private methods /////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/**
* Import a single .sql file into the database
* @param {type} filepath
* @returns {Promise}
*/
_importSingleFile(filepath){
return new Promise((resolve, reject)=>{
fs.readFile(filepath, this._encoding, (err, queriesString) => {
if(err){
reject(err);
return;
}
var queries = new queryParser(queriesString).queries;
var error = null;
slowLoop(queries, (query, index, next)=>{
if(error){
next();
return;
}
this._conn.query(query)
.catch(err => { error = err })
.then(() => { next() })
}).then(()=>{
if(error){
reject(error);
}else{
this._imported.push(filepath);
resolve();
}
});
});
});
}
/**
* Connect to the mysql server
* @returns {Promise}
*/
async _connect(){
try {
if (this._conn) {
return (this._conn)
}
this._conn = await this._pool.getConnection()
}
catch (e) {
throw (e)
}
}
/**
* Check if a file exists
* @param string filepath
* @returns {Promise}
*/
_fileExists(filepath){
return new Promise((resolve, reject)=>{
fs.access(filepath, fs.constants.F_OK, err=>{
if(err){
reject(err);
}else{
resolve();
}
});
});
}
/**
* Get filetype information
* @param string filepath
* @returns {Promise}
*/
_statFile(filepath){
return new Promise((resolve, reject)=>{
fs.lstat(filepath, (err, stat)=>{
if(err){
reject(err);
}else{
resolve(stat);
}
});
});
}
/**
* Read contents of a directory
* @param string filepath
* @returns {Promise}
*/
_readDir(filepath){
return new Promise((resolve, reject)=>{
fs.readdir(filepath, (err, files)=>{
if(err){
reject(err);
}else{
resolve(files);
}
});
});
}
/**
* Parses the input argument(s) for Importer.import into an array sql files.
* @param strings|array paths
* @returns {Promise}
*/
_getSQLFilePaths(...paths){
return new Promise(async (resolve, reject)=>{
var full_paths = [];
var error = null;
paths = [].concat.apply([], paths); // flatten array of paths
await slowLoop(paths, async (filepath, index, next)=>{
if(error){
next();
return;
}
try{
await this._fileExists(filepath);
var stat = await this._statFile(filepath);
if(stat.isFile()){
if(filepath.toLowerCase().substring(filepath.length-4) === '.sql'){
full_paths.push(path.resolve(filepath));
}
next();
}else if(stat.isDirectory()){
var more_paths = await this._readDir(filepath);
more_paths = more_paths.map(p=>path.join(filepath, p));
var sql_files = await this._getSQLFilePaths(...more_paths);
full_paths.push(...sql_files);
next();
}else{
next();
}
}catch(err){
error = err;
next();
}
});
if(error){
reject(error);
}else{
resolve(full_paths);
}
});
}
}
/**
* Build version number
*/
Importer.version = '4.0.24';
module.exports = Importer;
/**
* Execute the loopBody function once for each item in the items array,
* waiting for the done function (which is passed into the loopBody function)
* to be called before proceeding to the next item in the array.
* @param {Array} items - The array of items to iterate through
* @param {Function} loopBody - A function to execute on each item in the array.
* This function is passed 3 arguments -
* 1. The item in the current iteration,
* 2. The index of the item in the array,
* 3. A function to be called when the iteration may continue.
* @returns {Promise} - A promise that is resolved when all the items in the
* in the array have been iterated through.
*/
function slowLoop(items, loopBody) {
return new Promise(f => {
if(!items.length) return f();
let done = arguments[2] || f;
let idx = arguments[3] || 0;
let cb = items[idx + 1] ? () => slowLoop(items, loopBody, done, idx + 1) : done;
loopBody(items[idx], idx, cb);
});
}
class queryParser{
constructor(queriesString){
// Input string containing SQL queries
this.queriesString = queriesString.trim();
// The quote type (' or ") if the parser
// is currently inside of a quote, else false
this.quoteType = false;
// An array of complete queries
this.queries = [];
// An array of chars representing the substring
// the is currently being parsed
this.buffer = [];
// Is the current char escaped
this.escaped = false;
// The string that denotes the end of a query
this.delimiter = ';';
// Are we currently seeking new delimiter
this.seekingDelimiter = false;
// Does the sql set change delimiter?
this.hasDelimiter = queriesString.toLowerCase().includes('delimiter ');
// Iterate over each char in the string
for (let i = 0; i < this.queriesString.length; i++) {
let char = this.queriesString[i];
this.parseChar(char);
}
}
// Parse the next char in the string
parseChar(char){
this.checkEscapeChar();
this.buffer.push(char);
if (this.hasDelimiter) {
this.checkNewDelimiter(char);
}
this.checkQuote(char);
this.checkEndOfQuery();
}
// Check if the current char has been escaped
// and update this.escaped
checkEscapeChar(){
if(!this.buffer.length) return;
if(this.buffer[this.buffer.length - 1] === "\\"){
this.escaped = !this.escaped;
}else{
this.escaped = false;
}
}
// Check to see if a new delimiter is being assigned
checkNewDelimiter(char){
var buffer_str = this.buffer.join('').toLowerCase().trim();
if(buffer_str === 'delimiter' && !this.quoteType){
this.seekingDelimiter = true;
this.buffer = [];
}else{
var isNewLine = char === "\n" || char === "\r";
if(isNewLine && this.seekingDelimiter){
this.seekingDelimiter = false;
this.delimiter = this.buffer.join('').trim();
this.buffer = [];
}
}
}
// Check if the current char is a quote
checkQuote(char){
var isQuote = (char === '"' || char === "'") && !this.escaped;
if (isQuote && this.quoteType === char){
this.quoteType = false;
}else if(isQuote && !this.quoteType){
this.quoteType = char;
}
}
// Check if we're at the end of the query
checkEndOfQuery(){
var demiliterFound = false;
if(!this.quoteType && this.buffer.length >= this.delimiter.length){
demiliterFound = this.buffer.slice(-this.delimiter.length).join('') === this.delimiter;
}
if (demiliterFound) {
// trim the delimiter off the end
this.buffer.splice(-this.delimiter.length, this.delimiter.length);
this.queries.push(this.buffer.join('').trim());
this.buffer = [];
}
}
}
================================================
FILE: api/source/service/migrations/lib/umzug-mysql-storage.js
================================================
module.exports = class MyStorage {
constructor(options) {
this.pool = options.pool
this.hasMigrationTable = false
}
async createMigrationTable () {
await this.pool.query(`CREATE TABLE IF NOT EXISTS _migrations (
createdAt DATETIME DEFAULT CURRENT_TIMESTAMP,
updatedAt DATETIME ON UPDATE CURRENT_TIMESTAMP,
name VARCHAR(128)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci`)
this.hasMigrationTable = true
}
async logMigration(migrationName) {
// This function logs a migration as executed.
// It will get called once a migration was
// executed successfully.
if (!this.hasMigrationTable) {
await this.createMigrationTable()
}
await this.pool.query('INSERT into _migrations (name) VALUES (?)', [migrationName])
}
async unlogMigration(migrationName) {
// This function removes a previously logged migration.
// It will get called once a migration has been reverted.
if (!this.hasMigrationTable) {
await this.createMigrationTable()
}
await this.pool.query('DELETE from _migrations WHERE name = ?', [migrationName])
}
async executed() {
// This function lists the names of the logged
// migrations. It will be used to calculate
// pending migrations. The result has to be an
// array with the names of the migration files.
if (!this.hasMigrationTable) {
await this.createMigrationTable()
}
let [rows] = await this.pool.query('SELECT name from _migrations')
return rows.map(r => r.name)
}
}
================================================
FILE: api/source/service/migrations/sql/0000/up/10-stigman-schema.sql
================================================
-- MySQL dump 10.13-csmig Distrib 8.0.18-csmig, for Linux (x86_64)
--
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `action`
--
DROP TABLE IF EXISTS `action`;
CREATE TABLE `action` (
`actionId` int(11) NOT NULL AUTO_INCREMENT,
`api` varchar(16) NOT NULL,
`en` varchar(64) NOT NULL,
PRIMARY KEY (`actionId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `asset`
--
DROP TABLE IF EXISTS `asset`;
CREATE TABLE `asset` (
`assetId` int NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
`collectionId` int NOT NULL,
`ip` varchar(45) DEFAULT NULL,
`description` varchar(255) DEFAULT NULL,
`noncomputing` bit(1) NOT NULL DEFAULT b'0',
`metadata` json NOT NULL,
PRIMARY KEY (`assetId`),
UNIQUE KEY `INDEX_NAMECOLLECTION` (`name`, `collectionId`),
KEY `INDEX_COMPUTING` (`noncomputing`),
KEY `INDEX_COLLECTIONID` (`collectionId`),
CONSTRAINT `FK_ASSET_2` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `cci`
--
DROP TABLE IF EXISTS `cci`;
CREATE TABLE `cci` (
`cci` varchar(20) NOT NULL,
`status` varchar(20) NOT NULL,
`publishdate` date NOT NULL,
`contributor` varchar(255) NOT NULL,
`type` varchar(20) NOT NULL,
`definition` text NOT NULL,
`apAcronym` varchar(20) DEFAULT NULL,
`implementation` text,
`assessmentProcedure` text,
PRIMARY KEY (`cci`),
KEY `ap` (`apAcronym`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `cci_reference_map`
--
DROP TABLE IF EXISTS `cci_reference_map`;
CREATE TABLE `cci_reference_map` (
`cciRefId` int(11) NOT NULL AUTO_INCREMENT,
`cci` varchar(20) NOT NULL,
`creator` varchar(255) NOT NULL,
`title` varchar(255) NOT NULL,
`version` varchar(255) NOT NULL,
`location` varchar(255) NOT NULL,
`indexDisa` varchar(255) NOT NULL,
`textRefNist` varchar(255) NOT NULL,
`parentControl` varchar(255) NOT NULL,
PRIMARY KEY (`cciRefId`),
KEY `cci` (`cci`),
KEY `textRefNist` (`textRefNist`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `check`
--
DROP TABLE IF EXISTS `check`;
CREATE TABLE `check` (
`checkId` varchar(255) NOT NULL,
`content` text,
PRIMARY KEY (`checkId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection`
--
DROP TABLE IF EXISTS `collection`;
CREATE TABLE `collection` (
`collectionId` int NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
`workflow` varchar(45) NOT NULL,
`metadata` json NOT NULL,
PRIMARY KEY (`collectionId`),
UNIQUE KEY `index2` (`name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection_grant`
--
DROP TABLE IF EXISTS `collection_grant`;
CREATE TABLE `collection_grant` (
`cgId` int NOT NULL AUTO_INCREMENT,
`collectionId` int NOT NULL,
`userId` int NOT NULL,
`accessLevel` int NOT NULL,
PRIMARY KEY (`cgId`),
UNIQUE KEY `INDEX_USER` (`userId`,`collectionId`),
KEY `INDEX_COLLECTION` (`collectionId`,`accessLevel`),
CONSTRAINT `fk_collection_grant_1` FOREIGN KEY (`userId`) REFERENCES `user_data` (`userId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_2` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `current_group_rule`
--
DROP TABLE IF EXISTS `current_group_rule`;
CREATE TABLE `current_group_rule` (
`cgrId` int(11) NOT NULL AUTO_INCREMENT,
`benchmarkId` varchar(255) NOT NULL,
`groupId` varchar(45) NOT NULL,
`ruleId` varchar(255) NOT NULL,
PRIMARY KEY (`cgrId`),
KEY `idx_benchmarkId` (`benchmarkId`),
KEY `idx_rule` (`ruleId`),
KEY `idx_group` (`groupId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `current_rev`
--
DROP TABLE IF EXISTS `current_rev`;
CREATE TABLE `current_rev` (
`revId` varchar(255) NOT NULL,
`benchmarkId` varchar(255) NOT NULL,
`version` int(11) NOT NULL,
`release` varchar(45) NOT NULL,
`benchmarkDate` varchar(45) DEFAULT NULL,
`benchmarkDateSql` date DEFAULT NULL,
`status` varchar(45) DEFAULT NULL,
`statusDate` varchar(45) DEFAULT NULL,
`description` varchar(4000) DEFAULT NULL,
`active` tinyint(4) DEFAULT NULL,
`groupCount` int(11) DEFAULT 0 NOT NULL,
`ruleCount` int(11) DEFAULT 0 NOT NULL,
`checkCount` int(11) DEFAULT 0 NOT NULL,
`fixCount` int(11) DEFAULT 0 NOT NULL,
`ovalCount` int(11) DEFAULT 0 NOT NULL,
PRIMARY KEY (`revId`),
UNIQUE KEY `index2` (`benchmarkId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `fix`
--
DROP TABLE IF EXISTS `fix`;
CREATE TABLE `fix` (
`fixId` varchar(45) NOT NULL,
`text` mediumtext,
PRIMARY KEY (`fixId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `group`
--
DROP TABLE IF EXISTS `group`;
CREATE TABLE `group` (
`groupId` varchar(45) NOT NULL,
`title` varchar(255) DEFAULT NULL,
`severity` varchar(45) DEFAULT NULL,
PRIMARY KEY (`groupId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `config`
--
DROP TABLE IF EXISTS `config`;
CREATE TABLE `config` (
`key` varchar(45) NOT NULL,
`value` varchar(255) NOT NULL,
PRIMARY KEY (`key`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `poam_rar_entry`
--
DROP TABLE IF EXISTS `poam_rar_entry`;
CREATE TABLE `poam_rar_entry` (
`preId` int(11) NOT NULL AUTO_INCREMENT,
`collectionId` int(11) NOT NULL,
`groupId` varchar(45) NOT NULL,
`iacontrol` varchar(45) DEFAULT NULL,
`status` varchar(45) DEFAULT NULL,
`poc` varchar(255) DEFAULT NULL,
`resources` varchar(255) DEFAULT NULL,
`compdate` datetime DEFAULT NULL,
`milestone` longtext,
`poamComment` longtext,
`likelihood` varchar(50) DEFAULT NULL,
`mitdesc` longtext,
`residualRisk` int(11) DEFAULT NULL,
`recCorrAct` longtext,
`remdesc` longtext,
`rarComment` longtext,
PRIMARY KEY (`preId`),
UNIQUE KEY `unique_collectionId_groupId` (`collectionId`,`groupId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `reject_string`
--
DROP TABLE IF EXISTS `reject_string`;
CREATE TABLE `reject_string` (
`rejectId` int(11) NOT NULL AUTO_INCREMENT,
`shortStr` varchar(45) NOT NULL,
`longStr` longtext ,
PRIMARY KEY (`rejectId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
DROP TABLE IF EXISTS `result`;
CREATE TABLE `result` (
`resultId` int(11) NOT NULL AUTO_INCREMENT,
`api` varchar(32) NOT NULL,
`ckl` varchar(32) NOT NULL,
`abbr` varchar(2) NOT NULL,
`en` varchar(64) NOT NULL,
PRIMARY KEY (`resultId`),
UNIQUE KEY `RESULT_API` (`api`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_group_map`
--
DROP TABLE IF EXISTS `rev_group_map`;
CREATE TABLE `rev_group_map` (
`rgId` int(11) NOT NULL AUTO_INCREMENT,
`revId` varchar(255) DEFAULT NULL,
`groupId` varchar(45) DEFAULT NULL,
`rules` JSON DEFAULT NULL,
PRIMARY KEY (`rgId`),
UNIQUE KEY `uidx_rgm_revId_groupId` (`revId`,`groupId`),
KEY `idx_rgm_groupId` (`groupId`),
CONSTRAINT `FK_rev_group_map_group` FOREIGN KEY (`groupId`) REFERENCES `group` (`groupId`),
CONSTRAINT `FK_rev_group_map_revision` FOREIGN KEY (`revId`) REFERENCES `revision` (`revId`) ON DELETE CASCADE ON UPDATE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_group_rule_check_map`
--
DROP TABLE IF EXISTS `rev_group_rule_check_map`;
CREATE TABLE `rev_group_rule_check_map` (
`rgrcId` int(11) NOT NULL AUTO_INCREMENT,
`rgrId` int(11) NOT NULL,
`checkId` varchar(255) NOT NULL,
PRIMARY KEY (`rgrcId`),
UNIQUE KEY `uidx_rcm_ruleId_checkId` (`rgrId`,`checkId`),
KEY `idx_rcm_checkId` (`checkId`),
CONSTRAINT `FK_rev_group_rule_check_map_check` FOREIGN KEY (`checkId`) REFERENCES `check` (`checkId`),
CONSTRAINT `FK_rev_group_rule_check_map_rev_group_rule_map` FOREIGN KEY (`rgrId`) REFERENCES `rev_group_rule_map` (`rgrId`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_group_rule_fix_map`
--
DROP TABLE IF EXISTS `rev_group_rule_fix_map`;
CREATE TABLE `rev_group_rule_fix_map` (
`rgrfId` int(11) NOT NULL AUTO_INCREMENT,
`rgrId` int(11) NOT NULL,
`fixId` varchar(255) NOT NULL,
PRIMARY KEY (`rgrfId`),
UNIQUE KEY `uidx_rfm_ruleId_fixId` (`rgrId`,`fixId`),
KEY `idx_rfm_fixId` (`fixId`),
CONSTRAINT `FK_rev_group_rule_fix_map_fix` FOREIGN KEY (`fixId`) REFERENCES `fix` (`fixId`),
CONSTRAINT `FK_rev_group_rule_fix_map_rev_group_rule_map` FOREIGN KEY (`rgrId`) REFERENCES `rev_group_rule_map` (`rgrId`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_group_rule_map`
--
DROP TABLE IF EXISTS `rev_group_rule_map`;
CREATE TABLE `rev_group_rule_map` (
`rgrId` int(11) NOT NULL AUTO_INCREMENT,
`rgId` int(11) NOT NULL,
`ruleId` varchar(255) DEFAULT NULL,
`checks` JSON DEFAULT NULL,
`fixes` JSON DEFAULT NULL,
`ccis` JSON DEFAULT NULL,
PRIMARY KEY (`rgrId`),
UNIQUE KEY `uidx_rgrm_rgId_ruleId` (`rgId`,`ruleId`),
KEY `idx_rgrm_ruleId` (`ruleId`),
CONSTRAINT `FK_rev_group_rule_map_rev_group_map` FOREIGN KEY (`rgId`) REFERENCES `rev_group_map` (`rgId`) ON DELETE CASCADE ON UPDATE RESTRICT,
CONSTRAINT `FK_rev_group_rule_map_rule` FOREIGN KEY (`ruleId`) REFERENCES `rule` (`ruleId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_xml_map`
--
DROP TABLE IF EXISTS `rev_xml_map`;
CREATE TABLE `rev_xml_map` (
`rxId` int(11) NOT NULL AUTO_INCREMENT,
`revId` varchar(255) NOT NULL,
`xml` blob,
PRIMARY KEY (`rxId`),
UNIQUE KEY `uidx_rxm_revId` (`revId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `review`
--
DROP TABLE IF EXISTS `review`;
CREATE TABLE `review` (
`reviewId` int(11) NOT NULL AUTO_INCREMENT,
`assetId` int(11) DEFAULT NULL,
`ruleId` varchar(45) DEFAULT NULL,
`resultId` int(11) DEFAULT NULL,
`resultComment` longtext ,
`actionId` int(11) DEFAULT NULL,
`actionComment` longtext ,
`autoResult` bit(1) DEFAULT 0,
`ts` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`userId` int(11) DEFAULT NULL,
`rejecttext` longtext ,
`rejectUserId` int(11) DEFAULT NULL,
`statusId` int(11) NOT NULL,
PRIMARY KEY (`reviewId`),
UNIQUE KEY `INDEX_ASSETID_RULEID` (`assetId`,`ruleId`),
KEY `INDEX_RESULTID` (`resultId`),
KEY `INDEX_RULEID` (`ruleId`),
KEY `INDEX_STATUSID` (`statusId`),
CONSTRAINT `FK_REVIEWS_1` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `review_history`
--
DROP TABLE IF EXISTS `review_history`;
CREATE TABLE `review_history` (
`historyId` int(11) NOT NULL AUTO_INCREMENT,
`reviewId` int(11) NOT NULL,
`resultId` int(11) NOT NULL,
`resultComment` longtext,
`actionId` int(11) DEFAULT NULL,
`actionComment` longtext,
`autoResult` bit(1) DEFAULT NULL,
`ts` datetime NOT NULL,
`userId` int(11) DEFAULT NULL,
`rejectText` longtext,
`rejectUserId` int(11) DEFAULT NULL,
`statusId` int(11) NOT NULL,
PRIMARY KEY (`historyId`),
KEY `index_reviewId` (`reviewId`),
CONSTRAINT `fk_review_history_1` FOREIGN KEY (`reviewId`) REFERENCES `review` (`reviewId`) ON DELETE CASCADE ON UPDATE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `review_reject_string_map`
--
DROP TABLE IF EXISTS `review_reject_string_map`;
CREATE TABLE `review_reject_string_map` (
`rrsId` int(11) NOT NULL AUTO_INCREMENT,
`assetId` int(11) NOT NULL,
`ruleId` varchar(45) NOT NULL,
`rejectId` int(11) NOT NULL,
`userId` int(11) DEFAULT NULL,
PRIMARY KEY (`rrsId`),
UNIQUE KEY `INDEX2` (`assetId`,`ruleId`,`rejectId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `revision`
--
DROP TABLE IF EXISTS `revision`;
CREATE TABLE `revision` (
`revId` varchar(255) NOT NULL,
`benchmarkId` varchar(255) NOT NULL,
`version` int(11) NOT NULL,
`release` varchar(45) NOT NULL,
`benchmarkDate` varchar(45) DEFAULT NULL,
`benchmarkDateSql` date DEFAULT NULL,
`status` varchar(45) DEFAULT NULL,
`statusDate` varchar(45) DEFAULT NULL,
`description` varchar(4000) DEFAULT NULL,
`active` tinyint(4) DEFAULT '1',
`groupCount` int(11) DEFAULT 0 NOT NULL,
`ruleCount` int(11) DEFAULT 0 NOT NULL,
`checkCount` int(11) DEFAULT 0 NOT NULL,
`fixCount` int(11) DEFAULT 0 NOT NULL,
`ovalCount` int(11) DEFAULT 0 NOT NULL,
PRIMARY KEY (`revId`),
UNIQUE KEY `uidx_revision_benchmarkId_version_release` (`benchmarkId`,`version`,`release`),
CONSTRAINT `FK_REVISION_1` FOREIGN KEY (`benchmarkId`) REFERENCES `stig` (`benchmarkId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rule`
--
DROP TABLE IF EXISTS `rule`;
CREATE TABLE `rule` (
`ruleId` varchar(255) NOT NULL,
`version` varchar(45) NOT NULL,
`title` varchar(1000) DEFAULT NULL,
`severity` varchar(45) DEFAULT NULL,
`weight` varchar(45) DEFAULT NULL,
`vulnDiscussion` text,
`falsePositives` text,
`falseNegatives` text,
`documentable` varchar(45) DEFAULT NULL,
`mitigations` text,
`severityOverrideGuidance` text,
`potentialImpacts` text,
`thirdPartyTools` text,
`mitigationControl` text,
`responsibility` varchar(255) DEFAULT NULL,
`iaControls` varchar(255) DEFAULT NULL,
PRIMARY KEY (`ruleId`),
KEY `idx_rule_severity` (`severity`),
KEY `idx_title` (`title`(100))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rule_cci_map`
--
DROP TABLE IF EXISTS `rule_cci_map`;
CREATE TABLE `rule_cci_map` (
`rcId` int(11) NOT NULL AUTO_INCREMENT,
`ruleId` varchar(255) NOT NULL,
`cci` varchar(60) NOT NULL,
PRIMARY KEY (`rcId`),
UNIQUE KEY `rule_cci_unique` (`ruleId`,`cci`),
KEY `index_cci` (`cci`),
CONSTRAINT `FK_rule_cci_map_1` FOREIGN KEY (`ruleId`) REFERENCES `rule` (`ruleId`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rule_oval_map`
--
DROP TABLE IF EXISTS `rule_oval_map`;
CREATE TABLE `rule_oval_map` (
`roId` int(11) NOT NULL AUTO_INCREMENT,
`ruleId` varchar(255) NOT NULL,
`ovalRef` varchar(255) NOT NULL,
`benchmarkId` varchar(255) NOT NULL,
`releaseInfo` varchar(255) NOT NULL,
PRIMARY KEY (`roId`),
KEY `index2` (`ruleId`),
KEY `index3` (`benchmarkId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `severity_cat_map`
--
DROP TABLE IF EXISTS `severity_cat_map`;
CREATE TABLE `severity_cat_map` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`severity` varchar(45) NOT NULL,
`cat` int(11) NOT NULL,
`roman` varchar(45) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_scm_severity` (`severity`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `stats_asset_stig`
--
DROP TABLE IF EXISTS `stats_asset_stig`;
CREATE TABLE `stats_asset_stig` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`assetId` int(11) DEFAULT NULL,
`benchmarkId` varchar(255) DEFAULT NULL,
`minTs` datetime DEFAULT NULL,
`maxTs` datetime DEFAULT NULL,
`savedManual` int(11) DEFAULT NULL,
`savedAuto` int(11) DEFAULT NULL,
`submittedManual` int(11) DEFAULT NULL,
`submittedAuto` int(11) DEFAULT NULL,
`rejectedManual` int(11) DEFAULT NULL,
`rejectedAuto` int(11) DEFAULT NULL,
`acceptedManual` int(11) DEFAULT NULL,
`acceptedAuto` int(11) DEFAULT NULL,
`highCount` int(11) DEFAULT NULL,
`mediumCount` int(11) DEFAULT NULL,
`lowCount` int(11) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `INDEX_2_2_C` (`assetId`,`benchmarkId`),
KEY `FK_STATS_ASSET_STIG_2` (`benchmarkId`),
CONSTRAINT `FK_STATS_ASSET_STIG_1` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `status`
--
DROP TABLE IF EXISTS `status`;
CREATE TABLE `status` (
`statusId` int(11) NOT NULL,
`api` varchar(16) NOT NULL,
`en` varchar(16) NOT NULL,
PRIMARY KEY (`statusId`),
UNIQUE KEY `IDX_API` (`api`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `benchmark`
--
DROP TABLE IF EXISTS `stig`;
CREATE TABLE `stig` (
`benchmarkId` varchar(255) NOT NULL,
`title` varchar(255) NOT NULL,
PRIMARY KEY (`benchmarkId`),
KEY `idx_benchmark_title` (`title`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `stig_asset_map`
--
DROP TABLE IF EXISTS `stig_asset_map`;
CREATE TABLE `stig_asset_map` (
`saId` int(11) NOT NULL AUTO_INCREMENT,
`benchmarkId` varchar(255) NOT NULL,
`assetId` int(11) NOT NULL,
`userIds` JSON DEFAULT NULL,
PRIMARY KEY (`saId`),
UNIQUE KEY `IDX_BAID` (`benchmarkId`,`assetId`),
KEY `IDX_ASSETID` (`assetId`),
CONSTRAINT `FK_STIG_ASSET_MAP_1` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `FK_STIG_ASSET_MAP_2` FOREIGN KEY (`benchmarkId`) REFERENCES `stig` (`benchmarkId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `user`
--
DROP TABLE IF EXISTS `user_data`;
CREATE TABLE `user_data` (
`userId` int NOT NULL AUTO_INCREMENT,
`username` varchar(255) NOT NULL,
`display` varchar(255) NOT NULL,
`email` varchar(255) NOT NULL,
`globalAccess` bit(1) NOT NULL DEFAULT b'0',
`canCreateCollection` bit(1) NOT NULL DEFAULT b'0',
`canAdmin` bit(1) NOT NULL DEFAULT b'0',
`metadata` json NOT NULL,
`created` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
`lastAccess` int DEFAULT NULL,
`disabled` bit(1) NOT NULL DEFAULT b'0',
PRIMARY KEY (`userId`),
UNIQUE KEY `INDEX_username` (`username`),
KEY `INDEX_display` (`display`),
KEY `email` (`email`),
KEY `INDEX_globalAccess` (`globalAccess`),
KEY `INDEX_canAdmin` (`canAdmin`),
KEY `INDEX_canCreateCollection` (`canCreateCollection`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `user_stig_asset_map`
--
DROP TABLE IF EXISTS `user_stig_asset_map`;
CREATE TABLE `user_stig_asset_map` (
`id` int NOT NULL AUTO_INCREMENT,
`userId` int NOT NULL,
`saId` int NOT NULL,
-- `benchmarkId` varchar(255) NOT NULL,
-- `assetId` int NOT NULL,
PRIMARY KEY (`id`),
-- UNIQUE KEY `usa_Unique` (`benchmarkId`,`assetId`,`userId`),
-- KEY `usa_sa` (`benchmarkId`,`assetId`),
-- KEY `usa_a` (`assetId`),
KEY `fk_user_stig_asset_map_2` (`userId`),
-- CONSTRAINT `fk_user_stig_asset_map_1` FOREIGN KEY (`benchmarkId`, `assetId`) REFERENCES `stig_asset_map` (`benchmarkId`, `assetId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_user_stig_asset_map_1` FOREIGN KEY (`saId`) REFERENCES `stig_asset_map` (`saId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_user_stig_asset_map_2` FOREIGN KEY (`userId`) REFERENCES `user_data` (`userId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Temporary view structure for view `v_current_rev`
--
DROP TABLE IF EXISTS `v_current_rev`;
/*!50001 DROP VIEW IF EXISTS `v_current_rev`*/;
/*!50001 CREATE VIEW `v_current_rev` AS SELECT
1 AS `revId`,
1 AS `benchmarkId`,
1 AS `version`,
1 AS `release`,
1 AS `benchmarkDate`,
1 AS `benchmarkDateSql`,
1 AS `status`,
1 AS `statusDate`,
1 AS `description`,
1 AS `active`,
1 AS `groupCount`,
1 AS `ruleCount`,
1 AS `checkCount`,
1 AS `fixCount`,
1 AS `ovalCount`*/;
--
-- Final view structure for view `v_current_rev`
--
/*!50001 DROP VIEW IF EXISTS `v_current_rev`*/;
/*!50001 CREATE ALGORITHM=UNDEFINED */
/*!50001 VIEW `v_current_rev` AS select `rr`.`revId` AS `revId`,`rr`.`benchmarkId` AS `benchmarkId`,`rr`.`version` AS `version`,`rr`.`release` AS `release`,`rr`.`benchmarkDate` AS `benchmarkDate`,`rr`.`benchmarkDateSql` AS `benchmarkDateSql`,`rr`.`status` AS `status`,`rr`.`statusDate` AS `statusDate`,`rr`.`description` AS `description`,`rr`.`active` AS `active`,`rr`.`groupCount` AS `groupCount`,`rr`.`ruleCount` AS `ruleCount`,`rr`.`checkCount` AS `checkCount`,`rr`.`fixCount` AS `fixCount`,`rr`.`ovalCount` AS `ovalCount` from (select `r`.`revId` AS `revId`,`r`.`benchmarkId` AS `benchmarkId`,`r`.`version` AS `version`,`r`.`release` AS `release`,`r`.`benchmarkDate` AS `benchmarkDate`,`r`.`benchmarkDateSql` AS `benchmarkDateSql`,`r`.`status` AS `status`,`r`.`statusDate` AS `statusDate`,`r`.`description` AS `description`,`r`.`active` AS `active`,`r`.`groupCount` AS `groupCount`,`r`.`ruleCount` AS `ruleCount`,`r`.`checkCount` AS `checkCount`,`r`.`fixCount` AS `fixCount`,(SELECT COUNT(roId) FROM rule_oval_map where benchmarkId = `r`.`benchmarkId`) AS `ovalCount`,row_number() OVER (PARTITION BY `r`.`benchmarkId` ORDER BY (`r`.`version` + 0) desc,(`r`.`release` + 0) desc ) AS `rn` from `revision` `r` where `r`.`status` = 'accepted') `rr` where (`rr`.`rn` = 1) */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2020-05-05 21:54:37
================================================
FILE: api/source/service/migrations/sql/0000/up/31-stigman-static.sql
================================================
-- MySQL dump 10.13 Distrib 8.0.18, for Linux (x86_64)
--
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Dumping data for table `action`
--
LOCK TABLES `action` WRITE;
/*!40000 ALTER TABLE `action` DISABLE KEYS */;
INSERT INTO `action` VALUES (1,'remediate','Remediate'),(2,'mitigate','Mitigate'),(3,'exception','Exception');
/*!40000 ALTER TABLE `action` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `reject_string`
--
LOCK TABLES `reject_string` WRITE;
/*!40000 ALTER TABLE `reject_string` DISABLE KEYS */;
INSERT INTO `reject_string` VALUES (1,'Evaluation comment not specific.','The comment supporting the result of the evaluation does not contain enough specific information. Comments should mention the specific setting(s) or value(s) contained in the check text.'),(2,'Recommendation comment not specific.','The comment describing the recommended action is not specific.'),(3,'Documentation is not attached.','The review requires the submission of documentation for the result of the evaluation to be accepted.');
/*!40000 ALTER TABLE `reject_string` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `state`
--
LOCK TABLES `result` WRITE;
/*!40000 ALTER TABLE `result` DISABLE KEYS */;
INSERT INTO `result` VALUES (1,'notchecked','Not_Reviewed','NR','Not checked'),
(2,'notapplicable','Not_Applicable','NA','Not Applicable'),
(3,'pass','NotAFinding','NF','Not a Finding'),
(4,'fail','Open','O','Open'),
(5,'unknown','Not_Reviewed','U','Unknown'),
(6,'error','Not_Reviewed','E','Error'),
(7,'notselected','Not_Reviewed','NS','Not selected'),
(8,'informational','Not_Reviewed','I','Informational'),
(9,'fixed','NotAFinding','NF','Fixed');
/*!40000 ALTER TABLE `result` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `severity_cat_map`
--
LOCK TABLES `severity_cat_map` WRITE;
/*!40000 ALTER TABLE `severity_cat_map` DISABLE KEYS */;
INSERT INTO `severity_cat_map` VALUES (1,'high',1,'I'),(2,'medium',2,'II'),(3,'low',3,'III'),(4,'mixed',4,'IV');
/*!40000 ALTER TABLE `severity_cat_map` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `status`
--
LOCK TABLES `status` WRITE;
/*!40000 ALTER TABLE `status` DISABLE KEYS */;
INSERT INTO `status` VALUES (0,'saved','Saved'),
(1,'submitted','Submitted'),
(2,'rejected','Rejected'),
(3,'accepted','Accepted');
/*!40000 ALTER TABLE `status` ENABLE KEYS */;
UNLOCK TABLES;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2020-05-13 14:47:04
================================================
FILE: api/source/service/migrations/sql/0000/up/32-cci-data.sql
================================================
-- MySQL dump 10.13-csmig Distrib 8.0.18-csmig, for Linux (x86_64)
--
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Dumping data for table `cci`
--
LOCK TABLES `cci` WRITE;
/*!40000 ALTER TABLE `cci` DISABLE KEYS */;
INSERT INTO `cci` VALUES ('000001','draft','2009-05-13','DISA FSO','policy','The organization develops an access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','AC-1.3','The organization being inspected/assessed develops and documents an access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','The organization conducting the inspection/assessment obtains and examines the access control policy to ensure the organization being inspected/assessed develops and documents an access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.'),
('000002','draft','2009-09-14','DISA FSO','policy','The organization disseminates the access control policy to organization-defined personnel or roles.','AC-1.4','The organization being inspected/assessed disseminates via an information sharing capability to all personnel. DoD has defined the personnel or roles as all personnel.','The organization conducting the inspection/assessment examines the access control policy via the organization\'s information sharing capability to ensure the organization being inspected/assessed disseminates the policy to all personnel. DoD has defined the personnel or roles as all personnel.'),
('000003','draft','2009-09-14','DISA FSO','policy','The organization reviews and updates the access control policy in accordance with organization-defined frequency.','AC-1.7','The organization being inspected/assessed annually reviews and updates the access control policy. The organization must maintain review and update activity as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed annually reviews and updates the access control policy. DoD has defined the frequency as annually.'),
('000004','draft','2009-05-13','DISA FSO','policy','The organization develops procedures to facilitate the implementation of the access control policy and associated access controls.','AC-1.5','The organization being inspected/assessed develops and documents procedures to facilitate the implementation of the access control policy and associated access controls.','The organization conducting the inspection/assessment obtains and examines the procedures to facilitate the implementation of the access control policy and associated access controls to ensure the organization being inspected/assessed develops and documents procedures to facilitate the implementation of the access control policy and associated access controls.'),
('000005','draft','2009-09-14','DISA FSO','policy','The organization disseminates the procedures to facilitate access control policy and associated access controls to the organization-defined personnel or roles.','AC-1.6','The organization being inspected/assessed disseminates via an information sharing capability to all personnel the procedures to facilitate access control policy and associated access controls. DoD has defined the personnel or roles as all personnel.','The organization conducting the inspection/assessment examines the procedures to facilitate access control policy and associated access controls via the organization\'s information sharing capability to ensure the organization being inspected/assessed disseminates the procedures to all personnel. DoD has defined the personnel or roles as all personnel.'),
('000006','draft','2009-09-14','DISA FSO','policy','The organization reviews and updates the access control procedures in accordance with organization-defined frequency.','AC-1.9','The organization being inspected/assessed annually reviews and updates the access control procedures. The organization must maintain review and update activity as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed annually reviews and updates the access control procedures. DoD has defined the frequency as annually.'),
('000007','draft','2009-05-13','DISA FSO','policy','The organization manages information system accounts by identifying account types (i.e., individual, group, system, application, guest/anonymous, and temporary).',NULL,NULL,NULL),
('000008','draft','2009-09-14','DISA FSO','policy','The organization establishes conditions for group membership.','AC-2.4','The organization being inspected/assessed documents conditions for adding accounts as members of groups.','The organization conducting the inspection/assessment obtains and examines the documented conditions for adding accounts as members of groups to ensure that the conditions are established.'),
('000009','draft','2009-05-13','DISA FSO','policy','The organization manages information system accounts by identifying authorized users of the information system and specifying access privileges.',NULL,NULL,NULL),
('000010','draft','2009-05-13','DISA FSO','policy','The organization requires approvals by organization-defined personnel or roles for requests to create information system accounts.','AC-2.11','The organization being inspected/assessed implements a process for the ISSM or ISSO to approve information system account requests. The organization being inspected/assessed maintains an audit trail of approvals. DoD has defined the personnel or roles as the ISSM or ISSO.','The organization conducting the inspection/assessment obtains and examines the audit trail of approvals to ensure that the organization being inspected/assessed implements a process for the ISSM or ISSO to approve information system account requests. DoD has defined the personnel or roles as the ISSM or ISSO.'),
('000011','draft','2009-05-13','DISA FSO','policy','The organization creates, enables, modifies, disables, and removes information system accounts in accordance with organization-defined procedures or conditions.','AC-2.13','The organization being inspected/assessed implements account maintenance processes to create, enable, modify, disable, and remove information system accounts in accordance with procedures or conditions defined in AC-2, 2121. The organization being inspected/assessed maintains an audit trail of account maintenance activities.','The organization conducting the inspection/assessment obtains and examines the audit trail of account maintenance activities to ensure the organization being inspected/assessed implements account maintenance processes to create, enable, modify, disable, remove, and track information system accounts in accordance with procedures or conditions defined in AC-2, 2121.'),
('000012','draft','2009-09-14','DISA FSO','policy','The organization reviews information system accounts for compliance with account management requirements per organization-defined frequency.','AC-2.22','The organization being inspected/assessed implements a process to review information system accounts for compliance with account management requirements at a minimum, annually. The organization being inspected/assessed maintains an audit trail of reviews. DoD has defined the frequency as at a minimum, annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews to ensure the organization being inspected/assessed implements a process to review information system accounts for compliance with account management requirements at a minimum, annually.\nDoD has defined the frequency as at a minimum, annually.'),
('000013','draft','2009-09-14','DISA FSO','policy','The organization manages information system accounts by notifying account managers when temporary accounts are no longer required and when information system users are terminated, transferred, or information system usage or need-to-know/need-to-share changes.',NULL,NULL,NULL),
('000014','draft','2009-09-14','DISA FSO','policy','The organization manages information system accounts by granting access to the system based on a valid access authorization; intended system usage; and other attributes as required by the organization or associated missions/business functions.',NULL,NULL,NULL),
('000015','draft','2009-05-13','DISA FSO','technical','The organization employs automated mechanisms to support the information system account management functions.','AC-2(1).1','The organization being inspected/assessed configures the information system to employ automated mechanisms to support the information system account management functions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 000015.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ automated mechanisms to support the information system account management functions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 000015.'),
('000016','draft','2009-05-13','DISA FSO','technical','The information system automatically removes or disables temporary accounts after an organization-defined time period for each type of account.','AC-2(2).1','The organization being inspected/assessed configures the information system to automatically remove or disable temporary accounts after 72 hours. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 000016. DoD has defined the time period as 72 hours. ','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically remove or disable temporary accounts after 72 hours. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 000016. DoD has defined the time period as 72 hours.'),
('000017','draft','2009-05-13','DISA FSO','technical','The information system automatically disables inactive accounts after an organization-defined time period.','AC-2(3).1','The organization being inspected/assessed configures the information system to disable inactive accounts after 35 days. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 000017. DoD has defined the time period as 35 days.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to disable inactive accounts after 35 days. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 000017. DoD has defined the time period as 35 days.'),
('000018','draft','2009-05-13','DISA FSO','technical','The information system automatically audits account creation actions.','AC-2(4).1','The organization being inspected/assessed configures the information system to automatically audit account creation actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 18.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically audit account creation actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 18.'),
('000019','draft','2009-09-14','DISA FSO','policy','The organization requires that users log out in accordance with the organization-defined time period of inactivity or description of when to log out.','AC-2(5).2','The organization being inspected/assessed documents in the user policies that users are required to log out at the end of the users standard work period unless otherwise defined in formal organizational policy and IAW conditions defined in AC-2 (5) CCI 2133. DoD has defined the time period as at the end of the users standard work period unless otherwise defined in formal organizational policy.','The organization conducting the inspection/assessment obtains and examines the user policies to ensure that users are required to log out at the end of the users standard work period unless otherwise defined in formal organizational policy and IAW conditions defined in AC-2 (5) CCI 2133. DoD has defined the time period as at the end of the users standard work period unless otherwise defined in formal organizational policy.'),
('000020','draft','2009-09-14','DISA FSO','technical','The information system dynamically manages user privileges and associated access authorizations.',NULL,NULL,NULL),
('000021','draft','2009-05-13','DISA FSO','technical','The information system enforces dual authorization for organization-defined privileged commands and/or other organization-defined actions.','AC-3(2).1','The organization being inspected/assessed configures the information system to enforce dual authorization for privileged commands defined in AC-3 (2), CCI 1408 and/or other actions defined in AC-3 (2), CCI 2152. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 21.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce dual authorization for privileged commands defined in AC-3 (2), CCI 1408 and/or other actions defined in AC-3 (2), CCI 2152. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 21.'),
('000022','draft','2009-05-13','DISA FSO','technical','The information system enforces one or more organization-defined nondiscretionary access control policies over an organization-defined set of users and resources.',NULL,NULL,NULL),
('000023','draft','2009-11-03','DISA FSO','policy','The organization develops an organization-wide information security program plan that provides sufficient information about the program management controls and common controls (including specification of parameters for any assignment and selection operations either explicitly or by reference) to enable an implementation that is unambiguously compliant with the intent of the plan, and a determination of the risk to be incurred if the plan is implemented as intended.',NULL,NULL,NULL),
('000024','draft','2009-09-14','DISA FSO','technical','The information system prevents access to organization-defined security-relevant information except during secure, non-operable system states.','AC-3(5).1','The organization being inspected/assessed configures the information system to prevent access to security-relevant information defined in AC-3 (5), CCI 1411 except during secure, non-operable system states. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 24.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent access to security-relevant information defined in AC-3 (5), CCI 1411 except during secure, non-operable system states. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 24.'),
('000025','draft','2009-09-14','DISA FSO','technical','The information system enforces information flow control using explicit security attributes on information, source, and destination objects as a basis for flow control decisions.',NULL,NULL,NULL),
('000026','draft','2009-05-13','DISA FSO','technical','The information system uses protected processing domains to enforce organization-defined information flow control policies as a basis for flow control decisions.','AC-4(2).1','The organization being inspected/assessed configures the information system to use protected processing domains to enforce information flow control policies defined in AC-4 (2), CCI 2191 as a basis for flow control decisions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 000026.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to use protected processing domains to enforce information flow control policies defined in AC-4 (2), CCI 2191 as a basis for flow control decisions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 000026.'),
('000027','draft','2009-05-13','DISA FSO','technical','The information system enforces dynamic information flow control based on organization-defined policies.','AC-4(3).1','The organization being inspected/assessed configures the information system to enforce dynamic information flow control based on policies defined in AC-4 (3), CCI 2192. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 27.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce dynamic information flow control based on policies defined in AC-4 (3), CCI 2192. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 27.'),
('000028','draft','2009-05-13','DISA FSO','policy','The information system prevents encrypted information from bypassing content-checking mechanisms by employing organization-defined procedures or methods.','AC-4(4).1','The organization being inspected/assessed configures the information system to prevent encrypted information from bypassing content-checking mechanisms by employing procedures or methods defined in AC-4 (4), CCI 2193. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 28.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent encrypted information from bypassing content-checking mechanisms by employing procedures or methods defined in AC-4 (4), CCI 2193. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 28.'),
('000029','draft','2009-05-13','DISA FSO','technical','The information system enforces organization-defined limitations on the embedding of data types within other data types.','AC-4(5).1','The organization being inspected/assessed configures the information system to enforce limitations defined in AC-4 (5), CCI 1415 on the embedding of data types within other data types. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 29.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce limitations defined in AC-4 (5), CCI 1415 on the embedding of data types within other data types. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 29.'),
('000030','draft','2009-05-13','DISA FSO','technical','The information system enforces information flow control based on organization-defined metadata.','AC-4(6).1','The organization being inspected/assessed configures the information system to enforce information flow control based on metadata defined in AC-4 (6), CCI 2194. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 30.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce information flow control based on metadata defined in AC-4 (6), CCI 2194. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 30.'),
('000031','draft','2009-05-13','DISA FSO','technical','The information system enforces organization-defined one-way flows using hardware mechanisms.','AC-4(7).1','The organization being inspected/assessed configures the information system to enforce one-way flows defined in AC-4 (7), CCI 1416 using hardware mechanisms. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 31.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce one-way flows defined in AC-4 (7), CCI 1416 using hardware mechanisms. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 31.'),
('000032','draft','2009-09-14','DISA FSO','technical','The information system enforces information flow control using organization-defined security policy filters as a basis for flow control decisions for organization-defined information flows.','AC-4(8).1','The organization being inspected/assessed configures the information system to enforce information flow control using security policy filters defined in AC-4 (8), CCI 1417 as a basis for flow control decisions for all information flows. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 32. DoD has defined the information flows as all information flows.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce information flow control using security policy filters defined in AC-4 (8), CCI 1417 as a basis for flow control decisions for all information flows. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 32. DoD has defined the information flows as all information flows.'),
('000033','draft','2009-05-13','DISA FSO','policy','The information system enforces the use of human review for organization-defined security policy filters when the system is not capable of making an information flow control decision.',NULL,NULL,NULL),
('000034','draft','2009-05-13','DISA FSO','technical','The information system provides the capability for a privileged administrator to enable/disable organization-defined security policy filters under organization-defined conditions.','AC-4(10).1','The organization being inspected/assessed configures the information system to provide the capability for a privileged administrator to enable/disable security policy filters defined in AC-4 (10), CCI 1553 under conditions defined in AC-4 (10), CCI 2199. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 34.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for a privileged administrator to enable/disable security policy filters defined in AC-4 (10), CCI 1553 under conditions defined in AC-4 (10), CCI 2199. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 34.'),
('000035','draft','2009-09-14','DISA FSO','technical','The information system provides the capability for privileged administrators to configure the organization-defined security policy filters to support different security policies.','AC-4(11).1','The organization being inspected/assessed configures the information system to provide the capability for privileged administrators to configure the security policy filters defined in AC-4 (11), CCI 1554 to support different security policies. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 35.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for privileged administrators to configure the security policy filters defined in AC-4 (11), CCI 1554 to support different security policies. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 35.'),
('000036','draft','2009-05-19','DISA FSO','policy','The organization separates organization-defined duties of individuals.','AC-5.1','The organization being inspected/assessed documents and implements processes to maintain separation of the duties defined in AC-5, CCI 2219 across different individuals within the organization.','The organization conducting the inspection/assessment obtains and examines the documented processes to ensure the organization being inspected/assessed maintains separation of the duties defined in AC-5, CCI 2219 across different individuals within the organization.'),
('000037','draft','2009-09-14','DISA FSO','technical','The organization implements separation of duties through assigned information system access authorizations.',NULL,NULL,NULL),
('000038','draft','2009-05-19','DISA FSO','policy','The organization explicitly authorizes access to organization-defined security functions and security-relevant information.',NULL,NULL,NULL),
('000039','draft','2009-09-14','DISA FSO','policy','The organization requires that users of information system accounts or roles, with access to organization-defined security functions or security-relevant information, use non-privileged accounts, or roles, when accessing nonsecurity functions.','AC-6(2).1','The organization being inspected/assessed documents and implements a process to require that users of information system accounts or roles, with access to any privileged security functions or security-relevant information, use non-privileged accounts, or roles, when accessing nonsecurity functions. DoD has defined the security functions and security-relevant information as any privileged security functions or security-relevant information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires that users of information system accounts or roles, with access to any privileged security functions or security-relevant information, use non-privileged accounts, or roles, when accessing nonsecurity functions. DoD has defined the security functions and security-relevant information as any privileged security functions or security-relevant information.'),
('000040','draft','2009-09-14','DISA FSO','technical','The organization audits any use of privileged accounts, or roles, with access to organization-defined security functions or security-relevant information, when accessing other system functions.',NULL,NULL,NULL),
('000041','draft','2009-05-19','DISA FSO','policy','The organization authorizes network access to organization-defined privileged commands only for organization-defined compelling operational needs.','AC-6(3).1','The organization being inspected/assessed authorizes network access to privileged commands defined in AC-6 (3), CCI 1420 only for compelling operational needs defined in AC-6 (3), CCI 2224.','The organization conducting the inspection/assessment obtains and examines a sampling of network access authorizations to ensure the organization being inspected/assessed authorizes network access to privileged commands defined in AC-6 (3), CCI 1420 only for compelling operational needs defined in AC-6 (3), CCI 2224.'),
('000042','draft','2009-05-19','DISA FSO','policy','The organization documents the rationale for authorized network access to organization-defined privileged commands in the security plan for the information system.','AC-6(3).2','The organization being inspected/assessed documents the rationale for authorized network access to privileged commands defined in AC-6 (3), CCI 1420 in the security plan for the information system.','The organization conducting the inspection/assessment obtains and examines the documented rationale to ensure the organization being inspected/assessed documents the rationale for authorized network access to privileged commands defined in AC-6 (3), CCI 1420 in the security plan for the information system.'),
('000043','draft','2009-05-19','DISA FSO','policy','The organization defines the maximum number of consecutive invalid logon attempts to the information system by a user during an organization-defined time period.','AC-7.1','DoD has defined the maximum number as three.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the maximum number as three.'),
('000044','draft','2009-09-14','DISA FSO','technical','The information system enforces the organization-defined limit of consecutive invalid logon attempts by a user during the organization-defined time period.','AC-7.2','The organization being inspected/assessed configures the information system to limit invalid logon attempts by a user to three attempts during a 15 minute time period. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 44. DoD has defined the maximum number as three. DoD has defined the time period as 15 minutes.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to limit invalid logon attempts by a user to three attempts during a 15 minute time period. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 44. DoD has defined the maximum number as three. DoD has defined the time period as 15 minutes.'),
('000045','draft','2009-09-14','DISA FSO','policy','The organization defines in the security plan, explicitly or by reference, the time period for lock out mode or delay period.',NULL,NULL,NULL),
('000046','draft','2009-09-14','DISA FSO','policy','The organization selects either a lock out mode for the organization-defined time period or delays the next login prompt for the organization-defined delay period for information system responses to consecutive invalid access attempts.',NULL,NULL,NULL),
('000047','draft','2009-09-14','DISA FSO','technical','The information system delays next login prompt according to the organization-defined delay algorithm, when the maximum number of unsuccessful attempts is exceeded, automatically locks the account/node for an organization-defined time period or locks the account/node until released by an Administrator IAW organizational policy.',NULL,NULL,NULL),
('000048','draft','2009-05-19','DISA FSO','technical','The information system displays an organization-defined system use notification message or banner before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.','AC-8.1','The organization being inspected/assessed configures the information system to display the DoD Information Systems Standard Consent Banner and User Agreement before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 48. DoD has defined the use notification message or banner as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display the DoD Information Systems Standard Consent Banner and User Agreement before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 48. DoD has defined the use notification message or banner as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013.'),
('000049','draft','2009-05-19','DISA FSO','policy','The organization defines a system use notification message or banner displayed before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance and states that: (i) users are accessing a U.S. Government information system; (ii) system usage may be monitored, recorded, and subject to audit; (iii) unauthorized use of the system is prohibited and subject to criminal and civil penalties; and (iv) use of the system indicates consent to monitoring and recording.',NULL,NULL,NULL),
('000050','draft','2009-09-14','DISA FSO','technical','The information system retains the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the information system.','AC-8.7','The organization being inspected/assessed configures the information system to retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 50.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 50.'),
('000051','draft','2009-05-19','DISA FSO','policy','The organization approves the information system use notification message before its use.',NULL,NULL,NULL),
('000052','draft','2009-09-14','DISA FSO','technical','The information system notifies the user, upon successful logon (access) to the system, of the date and time of the last logon (access).','AC-9.1','The organization being inspected/assessed configures the information system to notify the user, upon successful logon (access) to the system, of the date and time of the last logon (access). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 52.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the user, upon successful logon (access) to the system, of the date and time of the last logon (access). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 52.'),
('000053','draft','2009-09-14','DISA FSO','technical','The information system notifies the user, upon successful logon/access, of the number of unsuccessful logon/access attempts since the last successful logon/access.','AC-9(1).1','The organization being inspected/assessed configures the information system to notify the user, upon successful logon/access, of the number of unsuccessful logon/access attempts since the last successful logon/access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 53.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the user, upon successful logon/access, of the number of unsuccessful logon/access attempts since the last successful logon/access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 53.'),
('000054','draft','2009-05-19','DISA FSO','technical','The information system limits the number of concurrent sessions for each organization-defined account and/or account type to an organization-defined number of sessions.','AC-10.1','The organization being inspected/assessed configures the information system to limit the number of concurrent sessions for all accounts and/or account types to a number of sessions defined in AC-10, CCI 55. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 54. DoD has defined the account types and/or accounts as all account types and/or accounts.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to limit the number of concurrent sessions for all accounts and/or account types to a number of sessions defined in AC-10, CCI 55. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 54. DoD has defined the account types and/or accounts as all account types and/or accounts.'),
('000055','draft','2009-05-19','DISA FSO','policy','The organization defines the maximum number of concurrent sessions to be allowed for each organization-defined account and/or account type.','AC-10.2','The organization being inspected/assessed defines and documents the maximum number of concurrent sessions to be allowed for each organization-defined account and/or account type. The maximum number of concurrent sessions should be defined based upon the systems operational environment and mission needs. DoD has determined the maximum number is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented maximum number to ensure the organization being inspected/assessed defines the maximum number of concurrent sessions to be allowed for each organization-defined account and/or account type. DoD has determined the maximum number is not appropriate to define at the Enterprise level.'),
('000056','draft','2009-09-14','DISA FSO','technical','The information system retains the session lock until the user reestablishes access using established identification and authentication procedures.','AC-11.3','The organization being inspected/assessed configures the information system to retain the session lock until the user reestablishes access using established identification and authentication procedures. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 56.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to retain the session lock until the user reestablishes access using established identification and authentication procedures. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 56.'),
('000057','draft','2009-05-19','DISA FSO','technical','The information system initiates a session lock after the organization-defined time period of inactivity.',NULL,NULL,NULL),
('000058','draft','2009-05-19','DISA FSO','technical','The information system provides the capability for users to directly initiate session lock mechanisms.','AC-11.1','The organization being inspected/assessed configures the information system to provide the capability for users to directly initiate session lock mechanisms. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 58.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for users to directly initiate session lock mechanisms. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 58.'),
('000059','draft','2009-09-14','DISA FSO','policy','The organization defines the time period of inactivity after which the information system initiates a session lock.','AC-11.2','DoD has defined the time period as 15 minutes.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 15 minutes.'),
('000060','draft','2009-05-19','DISA FSO','technical','The information system conceals, via the session lock, information previously visible on the display with a publicly viewable image.','AC-11(1).1','The organization being inspected/assessed configures the information system to conceal, via the session lock, information previously visible on the display with a publicly viewable image. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 60.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to conceal, via the session lock, information previously visible on the display with a publicly viewable image. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 60.'),
('000061','draft','2009-09-14','DISA FSO','policy','The organization identifies and defines organization-defined user actions that can be performed on the information system without identification or authentication consistent with organizational missions/business functions.','AC-14.1','The organization being inspected/assessed identifies, defines, and documents user actions that can be performed on the information system without identification or authentication consistent with organizational missions/business functions. DoD has determined the user actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented user actions to ensure the organization being inspected/assessed identifies and defines the user actions that can be performed on the information system without identification and authentication. DoD has determined the user actions are not appropriate to define at the Enterprise level.'),
('000062','draft','2009-05-19','DISA FSO','policy','The organization permits actions to be performed without identification and authentication only to the extent necessary to accomplish mission/business objectives.',NULL,NULL,NULL),
('000063','draft','2009-09-14','DISA FSO','policy','The organization defines allowed methods of remote access to the information system.','AC-17.1','The organization being inspected/assessed defines and documents the allowed methods of remote access to the information system. The methods should be defined IAW ports, protocols, and service requirements, as well as access control requirements for any STIGs applicable to the technology in use. DoD has determined the allowed methods of remote access are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented methods to ensure the organization being inspected/assessed defines allowed methods of remote access to the information system. DoD has determined the allowed methods of remote access are not appropriate to define at the Enterprise level.'),
('000064','draft','2009-05-19','DISA FSO','policy','The organization establishes usage restrictions and implementation guidance for each allowed remote access method.',NULL,NULL,NULL),
('000065','draft','2009-09-14','DISA FSO','policy','The organization authorizes remote access to the information system prior to allowing such connections.','AC-17.5','The organization being inspected/assessed authorizes remote access to the information system prior to allowing such connections. The organization must maintain an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed authorizes remote access to the information system prior to allowing such connections.'),
('000066','draft','2009-09-14','DISA FSO','technical','The organization enforces requirements for remote connections to the information system.',NULL,NULL,NULL),
('000067','draft','2009-09-14','DISA FSO','technical','The information system monitors remote access methods.','AC-17(1).1','The organization being inspected/assessed configures the information system to monitor remote access methods. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 67.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to monitor remote access methods. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 67.'),
('000068','draft','2009-09-14','DISA FSO','technical','The information system implements cryptographic mechanisms to protect the confidentiality of remote access sessions.','AC-17(2).1','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the confidentiality of remote access sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 68.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the confidentiality of remote access sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 68.'),
('000069','draft','2009-05-19','DISA FSO','policy','The information system routes all remote accesses through an organization-defined number of managed network access control points.','AC-17(3).1','The organization being inspected/assessed configures the information system to route all remote accesses through the number of managed network access control points defined in AC-17 (3), CCI 2315. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 69.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to route all remote accesses through the number of managed network access control points defined in AC-17 (3), CCI 2315. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 69.'),
('000070','draft','2009-05-19','DISA FSO','policy','The organization authorizes the execution of privileged commands via remote access only for organization-defined needs.','AC-17(4).1','The organization being inspected/assessed authorizes the execution of privileged commands via remote access only for needs defined in AC-17 (4), CCI 2317. The organization being inspected/assessed maintains an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed authorizes the execution of privileged commands via remote access only for needs defined in AC-17 (4), CCI 2317.'),
('000071','draft','2009-05-19','DISA FSO','technical','The organization monitors for unauthorized remote connections to the information system on an organization-defined frequency.',NULL,NULL,NULL),
('000072','draft','2009-09-25','DISA FSO','policy','The organization ensures that users protect information about remote access mechanisms from unauthorized use and disclosure.','AC-17(6).1','The organization being inspected/assessed implements and documents a process to ensure that users protect information about remote access mechanisms from unauthorized use and disclosure.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure that the organization being inspected/assessed ensures that users protect information about remote access mechanisms from unauthorized use and disclosure.'),
('000073','draft','2009-11-03','DISA FSO','policy','The organization develops an organization-wide information security program plan that provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements.','PM-1.1','DoDI 8500.01 and the Knowledge Service meet the requirement for this CCI; individual organizations and system owners must provide documentation of common control implementation in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('000074','draft','2009-11-03','DISA FSO','policy','The organization develops an organization-wide information security program plan that is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.','PM-1.8','DoDI 8500.01 and the Knowledge Service meet the requirement for this CCI; individual organizations and system owners must provide documentation of common control implementation in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('000075','draft','2009-11-03','DISA FSO','policy','The organization reviews the organization-wide information security program plan on an organization-defined frequency.','PM-1.9','DoDI 8500.01 and the Knowledge Service meet the requirement for this CCI; individual organizations and system owners must provide documentation of common control implementation in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('000076','draft','2009-11-03','DISA FSO','policy','The organization defines the frequency with which to review the organization-wide information security program plan.','PM-1.10','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000077','draft','2009-11-03','DISA FSO','policy','The organization updates the plan to address organizational changes and problems identified during plan implementation or security control assessments.','PM-1.11','DoDI 8500.01 and the Knowledge Service meet the requirement for this CCI; individual organizations and system owners must provide documentation of common control implementation in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('000078','draft','2009-11-03','DISA FSO','policy','The organization appoints a senior information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program.','PM-2.1','The Deputy DoD CIO for Cyber Security is the DoD Senior Information Security Officer (SISO), appointed in writing with the mission and resources to coordinate, develop, implement and maintain a DoD-wide information security program.','DoD organizations are automatically compliant with this CCI as they are covered by the appointment of the DoD SISO.'),
('000079','draft','2009-09-14','DISA FSO','policy','The organization ensures that remote sessions for accessing an organization-defined list of security functions and security-relevant information employ organization-defined additional security measures.',NULL,NULL,NULL),
('000080','draft','2009-11-03','DISA FSO','policy','The organization ensures that all capital planning and investment requests include the resources needed to implement the information security program and documents all exceptions to this requirement.','PM-3.1','The organization being inspected/assessed documents and implements a process to ensure that all capital planning and investment requests include the resources needed to implement the information security program and documents all exceptions to this requirement.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that all capital planning and investment requests include the resources needed to implement the information security program and documents all exceptions to this requirement.'),
('000081','draft','2009-11-03','DISA FSO','policy','The organization employs a business case/Exhibit 300/Exhibit 53 to record the resources required.','PM-3.2','The organization being inspected/assessed documents and implements a process to employ a business case/Exhibit 300/Exhibit 53 to record the resources required.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs a business case/Exhibit 300/Exhibit 53 to record the resources required.'),
('000082','draft','2009-05-19','DISA FSO','policy','The organization establishes usage restrictions for organization-controlled mobile devices.','AC-19.1','The organization being inspected/assessed establishes and documents usage restrictions for organization controlled mobile devices.','The organization conducting the inspection/assessment obtains and examines the documented usage restrictions to ensure the organization being inspected/assessed establishes usage restrictions for organization controlled mobile devices.'),
('000083','draft','2009-05-19','DISA FSO','policy','The organization establishes implementation guidance for organization-controlled mobile devices.','AC-19.2','The organization being inspected/assessed establishes and documents implementation guidance for organization controlled mobile devices.','The organization conducting the inspection/assessment obtains and examines the documented implementation guidance to ensure the organization being inspected/assessed establishes implementation guidance for organization controlled mobile devices.'),
('000084','draft','2009-09-14','DISA FSO','policy','The organization authorizes connection of mobile devices to organizational information systems.','AC-19.5','The organization being inspected/assessed authorizes connection of mobile devices to organizational information systems. The organization must maintain an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed authorizes connection of mobile devices to organizational information systems.'),
('000085','draft','2009-05-19','DISA FSO','technical','The organization monitors for unauthorized connections of mobile devices to organizational information systems.',NULL,NULL,NULL),
('000086','draft','2009-05-19','DISA FSO','technical','The organization enforces requirements for the connection of mobile devices to organizational information systems.',NULL,NULL,NULL),
('000087','draft','2009-05-19','DISA FSO','technical','The organization disables information system functionality that provides the capability for automatic execution of code on mobile devices without user direction.',NULL,NULL,NULL),
('000088','draft','2009-09-14','DISA FSO','policy','The organization issues specially configured mobile devices to individuals traveling to locations that the organization deems to be of significant risk in accordance with organizational policies and procedures.',NULL,NULL,NULL),
('000089','draft','2009-09-14','DISA FSO','policy','The organization applies organization-defined inspection and preventative measures to mobile devices returning from locations that the organization deems to be of significant risk in accordance with organizational policies and procedures.',NULL,NULL,NULL),
('000090','draft','2009-05-19','DISA FSO','policy','The organization restricts the use of writable, removable media in organizational information systems.',NULL,NULL,NULL),
('000091','draft','2009-05-19','DISA FSO','policy','The organization prohibits the use of personally-owned, removable media in organizational information systems.',NULL,NULL,NULL),
('000092','draft','2009-05-19','DISA FSO','policy','The organization prohibits the use of removable media in organizational information systems when the media has no identifiable owner.',NULL,NULL,NULL),
('000093','draft','2009-09-14','DISA FSO','policy','The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to access the information system from the external information systems.','AC-20.1','The organization being inspected/assessed establishes and documents terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to access the information system from the external information systems.','The organization conducting the inspection/assessment obtains and examines the documented terms and conditions to ensure the organization being inspected/assessed establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to access the information system from the external information systems.'),
('000094','draft','2009-05-19','DISA FSO','policy','The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to process organization-controlled information using the external information systems.',NULL,NULL,NULL),
('000095','draft','2009-05-19','DISA FSO','policy','The organization prohibits authorized individuals from using an external information system to access the information system except in situations where the organization can verify the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.',NULL,NULL,NULL),
('000096','draft','2009-05-19','DISA FSO','policy','The organization prohibits authorized individuals from using an external information system to access the information system or to process, store, or transmit organization-controlled information except in situations where the organization has approved information system connection or processing agreements with the organizational entity hosting the external information system.',NULL,NULL,NULL),
('000097','draft','2009-09-14','DISA FSO','policy','The organization restricts or prohibits the use of organization-controlled portable storage devices by authorized individuals on external information systems.','AC-20(2).1','The organization being inspected/assessed','The organization conducting the inspection/assessment obtains and examines'),
('000098','draft','2009-05-19','DISA FSO','policy','The organization facilitates information sharing by enabling authorized users to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for organization-defined information circumstances where user discretion is required.','AC-21.1','The organization being inspected/assessed documents and implements a process to determine whether access authorizations assigned to the sharing partner match the access restrictions on the information for information circumstances defined in AC-21, CCI 1470 where user discretion is required.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed determines whether access authorizations assigned to the sharing partner match the access restrictions on the information for information circumstances defined in AC-21, CCI 1470 where user discretion is required.'),
('000099','draft','2009-05-19','DISA FSO','policy','The information system enforces information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.','AC-21(1).1','The organization being inspected/assessed configures the information system to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 99.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 99.'),
('000100','draft','2009-05-20','DISA FSO','policy','The organization develops and documents a security awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','AT-1.3','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.\n\n\nComment:\nDoDD 8570.01 will be updated with DoDD 8140 once signed.\n\nThe organization\'s use of their higher command policy/procedures meets this requirement if more stringent.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.\n\nComment:\nThe organization\'s use of their higher command policy/procedures meets this requirement if more stringent.'),
('000101','draft','2009-05-20','DISA FSO','policy','The organization disseminates a security awareness and training policy to organization-defined personnel or roles.','AT-1.4','DoD disseminates DoDD 8570.01 organization-wide via the DoD Issuances website.\nhttp://www.dtic.mil/whs/directives/corres/dir.html','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000102','draft','2009-05-20','DISA FSO','policy','The organization reviews and updates the current security awareness and training policy in accordance with organization-defined frequency.','AT-1.8','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000103','draft','2009-05-20','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls.','AT-1.6','DoD develops and documents procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls within DoDD 8570.01. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000104','draft','2009-05-20','DISA FSO','policy','The organization disseminates security awareness and training procedures to organization-defined personnel or roles.','AT-1.7','DoD disseminates DoDD 8570.01 organization-wide via the DoD Issuances website.\nhttp://www.dtic.mil/whs/directives/corres/dir.html\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.\n\nDoD has defined the roles as organizational personnel with security awareness and training responsibilities.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.\n\nDoD has defined the roles as organizational personnel with security awareness and training responsibilities.'),
('000105','draft','2009-05-20','DISA FSO','policy','The organization reviews and updates the current security awareness and training procedures in accordance with an organization-defined frequency.','AT-1.9','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.\n\nDoD has defined the frequency as annually.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.\n\nDoD has defined the frequency as annually.'),
('000106','draft','2009-09-14','DISA FSO','policy','The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors) as part of initial training for new users.','AT-2.2','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000107','draft','2009-05-20','DISA FSO','policy','The organization includes practical exercises in security awareness training that simulate actual cyber attacks.','AT-2(1).1','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000108','draft','2009-05-20','DISA FSO','policy','The organization provides role-based security training to personnel with assigned security roles and responsibilities before authorizing access to the information system or performing assigned duties.','AT-3.1','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT for privileged users is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT for privileged users is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000109','draft','2009-05-20','DISA FSO','policy','The organization provides role-based security training to personnel with assigned security roles and responsibilities when required by information system changes.','AT-3.2','Privileged user type Security-related education/training available through DISA IASE (e.g. VTE, Skill Soft, other professional sources) meets the provision of this control. The organization being inspected/assessed may define specific requirements within the above listed sources for their personnel.','The organization conducting the inspection/assessment obtains and examines documented records (IAW AT-4) of their privileged users training.'),
('000110','draft','2009-05-20','DISA FSO','policy','The organization provides refresher role-based security training to personnel with assigned security roles and responsibilities in accordance with organization-defined frequency.','AT-3.3','Privileged user type Security-related education/training available through DISA IASE (e.g. VTE, Skill Soft, other professional sources) meets the provision of this control. The organization being inspected/assessed may define specific requirements within the above listed sources for their personnel. ','The organization conducting the inspection/assessment obtains and examines documented records (IAW AT-4) of their privileged users training. '),
('000111','draft','2009-05-20','DISA FSO','policy','The organization defines a frequency for providing refresher role-based security training.','AT-3.4','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000112','draft','2009-05-20','DISA FSO','policy','The organization provides basic security awareness training to information system users (including managers, senior executives, and contractors) when required by information system changes.','AT-2.3','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('000113','draft','2009-09-14','DISA FSO','policy','The organization documents individual information system security training activities, including basic security awareness training and specific information system security training.','AT-4.1','The organization being inspected/assessed identifies and documents training activities to include basic security awareness training (per AT-2) and role-based security related training (per AT-3) IAW DoD 8570.01M.','The organization conducting the inspection/assessment obtains and examines the security awareness training activities to ensure the organization being inspected/assessed documents training activities to include basic security awareness training (per AT-2) and role-based security related training (per AT-3) IAW DoD 8570.01M.'),
('000114','draft','2009-09-14','DISA FSO','policy','The organization monitors individual information system security training activities, including basic security awareness training and specific information system security training.','AT-4.2','The organization being inspected/assessed maintains and monitors records identifying personnel who have received training and the date the training was received','The organization conducting the inspection/assessment obtains and examines records identifying personnel who have received training and the date the training was received'),
('000115','draft','2009-09-14','DISA FSO','policy','The organization establishes contact with selected groups and associations within the security community to facilitate ongoing security education and training; to stay up to date with the latest recommended security practices, techniques, and technologies; and to share current security-related information including threats, vulnerabilities, and incidents.',NULL,NULL,NULL),
('000116','draft','2009-09-14','DISA FSO','policy','The organization institutionalizes contact with selected groups and associations within the security community to facilitate ongoing security education and training; to stay up to date with the latest recommended security practices, techniques, and technologies; and to share current security-related information including threats, vulnerabilities, and incidents.',NULL,NULL,NULL),
('000117','draft','2009-05-20','DISA FSO','policy','The organization develops and documents an audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','AU-1.3','The organization being inspected/assessed develops and documents an audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','The organization conducting the inspection/assessment obtains and examines the audit and accountability policy to ensure that the audit and accountability policy addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.'),
('000118','draft','2009-05-20','DISA FSO','policy','The organization disseminates a formal, documented, audit and accountability policy to elements within the organization having associated audit and accountability roles and responsibilities.',NULL,NULL,NULL),
('000119','draft','2009-05-20','DISA FSO','policy','The organization reviews and updates the audit and accountability policy on an organization-defined frequency.','AU-1.7','The organization being inspected/assessed reviews and updates the audit and accountability policy annually. The organization must maintain an audit trail of reviews and updates. Any changes or acceptance of the document without change must be captured in the audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates the audit and accountability policy annually. DoD has defined the frequency as annually.'),
('000120','draft','2009-05-20','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.','AU-1.5','The organization being inspected/assessed develops and documents procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.','The organization conducting the inspection/assessment obtains and examines the audit and accountability procedures to ensure that the procedures facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.'),
('000121','draft','2009-05-20','DISA FSO','policy','The organization disseminates formal, documented, procedures to elements within the organization having associated audit and accountability roles and responsibilities.',NULL,NULL,NULL),
('000122','draft','2009-05-20','DISA FSO','policy','The organization reviews and updates the audit and accountability procedures on an organization-defined frequency.','AU-1.9','The organization being inspected/assessed reviews and updates the audit and accountability procedures annually. The organization must maintain an audit trail of reviews and updates. Any changes or acceptance of the document without change must be captured in the audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates the audit and accountability procedures annually. DoD has defined the frequency as annually.'),
('000123','draft','2009-09-15','DISA FSO','policy','The organization determines the information system must be capable of auditing an organization-defined list of auditable events.','AU-2.1','The organization being inspected/assessed determines whether the information system is capable of auditing:\n - Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g. Classification levels),\n - Successful and unsuccessful logon attempts,\n - Privileged activities or other system level access,\n - Starting and ending time for user access to the system,\n - Concurrent logons from different workstations,\n - Successful and unsuccessful accesses to objects,\n - All program initiations,\n - All direct access to the information system,\n - All account creations, modifications, disabling, and terminations,\n - All kernel module load, unload, and restart. The organization must document those auditable events that are not captured.\n\nDoD has defined the information system auditable events as successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g. classification levels). Successful and unsuccessful logon attempts, Privileged activities or other system level access, Starting and ending time for user access to the system, Concurrent logons from different workstations, Successful and unsuccessful accesses to objects, All program initiations, All direct access to the information system. All account creations, modifications, disabling, and terminations. All kernel module load, unload, and restart.','The organization conducting the inspection/assessment obtains and examines the documentation of the auditable events to ensure the information system is capable of auditing the:\n - Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g. Classification levels),\n - Successful and unsuccessful logon attempts,\n - Privileged activities or other system level access,\n - Starting and ending time for user access to the system,\n - Concurrent logons from different workstations,\n - Successful and unsuccessful accesses to objects,\n - All program initiations,\n - All direct access to the information system,\n - All account creations, modifications, disabling, and terminations,\n - All kernel module load, unload, and restart.\n\n DoD has defined the information system auditable events as successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g. classification levels). Successful and unsuccessful logon attempts, Privileged activities or other system level access, Starting and ending time for user access to the system, Concurrent logons from different workstations, Successful and unsuccessful accesses to objects, All program initiations, All direct access to the information system. All account creations, modifications, disabling, and terminations. All kernel module load, unload, and restart.'),
('000124','draft','2009-09-15','DISA FSO','policy','The organization coordinates the security audit function with other organizational entities requiring audit-related information to enhance mutual support and to help guide the selection of auditable events.','AU-2.3','The organization being inspected/assessed documents and implements within the audit and accountability policy and procedures, a process to coordinate the additional auditable events. The objective is to enhance mutual support and to help guide the selection of auditable events.\n\nThe organization must maintain artifacts of the coordination.','The organization conducting the inspection/assessment obtains and examines the audit and accountability policy and procedures as well as artifacts of the coordination to determine if coordination is necessary and if necessary, whether it has been performed.'),
('000125','draft','2009-09-15','DISA FSO','policy','The organization provides a rationale for why the list of auditable events is deemed to be adequate to support after-the-fact investigations of security incidents.','AU-2.4','The organization being inspected/assessed documents in the audit and accountability policy the list of auditable system events, the organization provides clearly stated rationale for the selection of each system event. The rationale will support any after-action investigations of security event.','The organization conducting the inspection/assessment obtains and examines the audit and accountability policy and procedures to ensure the organization being inspected/assess has defined the auditable system events, rationale for the selection, and that the organization has defined how the auditable events will support after-action investigations of security events.'),
('000126','draft','2009-09-15','DISA FSO','policy','The organization determines that the organization-defined subset of the auditable events defined in AU-2 are to be audited within the information system.','AU-2.5','The organization conducting the inspection/assessment reviews the documented audit process as well as audit logs to ensure that the organization being inspected/assessed audits all auditable events defined in AU-2 (a) per occurrence.\n\nDoD has defined the actions as all auditable events defined in AU-2 (a) per occurrence.','The organization conducting the inspection/assessment reviews the documented audit process as well as audit logs to ensure that the organization being inspected/assessed audits all auditable events defined in AU-2 (a) per occurrence.\n\nDoD has defined the actions as all auditable events defined in AU-2 (a) per occurrence.'),
('000127','draft','2009-05-20','DISA FSO','policy','The organization reviews and updates the list of organization-defined audited events on an organization-defined frequency.','AU-2(3).1','The organization being inspected/assessed will conduct reviews of the list of auditable events as defined in AU-2 (d), CCI 1485 annually or more frequently upon changes to situational awareness of threats or vulnerabilities. The organization will generate and maintain an audit trail to document the completion of the review and update actions. DoD has defined the frequency as annually or more frequently upon changes to situational awareness of threats or vulnerabilities.','The organization conducting the inspection/assessment reviews the audit trail showing reviews and updates to the list of audited events to ensure that the list is reviewed and updated annually or more frequently upon changes to situational awareness of threats or vulnerabilities. DoD has defined the frequency as annually or more frequently upon changes to situational awareness of threats or vulnerabilities.'),
('000128','draft','2009-05-20','DISA FSO','policy','The organization includes execution of privileged functions in the list of events to be audited by the information system.',NULL,NULL,NULL),
('000129','draft','2009-09-15','DISA FSO','policy','The organization defines in the auditable events that the information system must be capable of auditing based on a risk assessment and mission/business needs.',NULL,NULL,NULL),
('000130','draft','2009-05-20','DISA FSO','technical','The information system generates audit records containing information that establishes what type of event occurred.','AU-3.1','The organization being inspected/assessed configures the information system to generate audit records containing information that establishes what type of event occurred For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 130.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing information that establishes what type of event occurred. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain information that establishes what type of event occurred. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 130.'),
('000131','draft','2009-05-20','DISA FSO','technical','The information system generates audit records containing information that establishes when an event occurred.','AU-3.2','The organization being inspected/assessed configures the information system to generate audit records containing information that establishes when an event occurred For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 131.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing information that establishes when an event occurred. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain information that establishes when an event occurred. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 131.'),
('000132','draft','2009-05-20','DISA FSO','technical','The information system generates audit records containing information that establishes where the event occurred.','AU-3.3','The organization being inspected/assessed configures the information system to generate audit records containing information that establishes where the event occurred For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 132.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing information that establishes where the event occurred. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain information that establishes where the event occurred. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 132.'),
('000133','draft','2009-05-20','DISA FSO','technical','The information system generates audit records containing information that establishes the source of the event.','AU-3.4','The organization being inspected/assessed configures the information system to generate audit records containing information that establishes the source of the event. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 133.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing information that establishes the source of the event. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain information that establishes the source of the event. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 133.'),
('000134','draft','2009-05-20','DISA FSO','technical','The information system generates audit records containing information that establishes the outcome of the event.','AU-3.5','The organization being inspected/assessed configures the information system to generate audit records containing information that establishes the outcome of the event. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 134.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing information that establishes the outcome of the event. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain information that establishes the outcome of the event. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 134.'),
('000135','draft','2009-05-20','DISA FSO','technical','The information system generates audit records containing the organization-defined additional, more detailed information that is to be included in the audit records.','AU-3(1).1','The organization being inspected/assessed configures the information system to generate audit records containing the organization defined additional, more detailed information as defined in AU-3 (1), CCI 1488 that is to be included in the audit records.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 135.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing the organization defined additional, more detailed information as defined in AU-3 (1), CCI 1488 that is to be included in the audit records. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain organization defined additional, more detailed information that is to be included in the audit records.\n\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 135.'),
('000136','draft','2009-05-20','DISA FSO','technical','The organization centrally manages the content of audit records generated by organization-defined information system components.',NULL,NULL,NULL),
('000137','draft','2009-05-20','DISA FSO','policy','The organization allocates audit record storage capacity.',NULL,NULL,NULL),
('000138','draft','2009-05-20','DISA FSO','technical','The organization configures auditing to reduce the likelihood of storage capacity being exceeded.',NULL,NULL,NULL),
('000139','draft','2009-09-15','DISA FSO','technical','The information system alerts designated organization-defined personnel or roles in the event of an audit processing failure.','AU-5.1','The organization being inspected/assessed configures the information system to alert at a minimum, the SCA and ISSO in the event of an audit processing failure. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 139. DoD has defined the personnel or roles as at a minimum, the SCA and ISSO. ','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to alert at a minimum, the SCA and ISSO in the event of an audit processing failure. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 139. DoD has defined the personnel or roles as at a minimum, the SCA and ISSO. '),
('000140','draft','2009-05-20','DISA FSO','technical','The information system takes organization-defined actions upon audit failure (e.g., shut down information system, overwrite oldest audit records, stop generating audit records).','AU-5.3','The organization being inspected/assessed configures the information system to take actions as defined in AU-5, CCI 1490 upon audit failure. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 140.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to take actions as defined in AU-5, CCI 1490 upon audit failure. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 140.'),
('000141','draft','2009-11-03','DISA FSO','policy','The organization ensures that information security resources are available for expenditure as planned.','PM-3.3','The organization being inspected/assessed documents and implements a process to ensure that information security resources are available for expenditure as planned.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensure that information security resources are available for expenditure as planned.'),
('000142','draft','2009-11-03','DISA FSO','policy','The organization implements a process for ensuring that plans of action and milestones for the security program and the associated organizational information systems are maintained.','PM-4.1','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to maintain a process for plans of action and milestones for the security program.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to maintain a process for plans of action and milestones for the security program.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.'),
('000143','draft','2009-05-20','DISA FSO','technical','The information system provides a warning when allocated audit record storage volume reaches an organization-defined percentage of maximum audit record storage capacity.',NULL,NULL,NULL),
('000144','draft','2009-05-20','DISA FSO','technical','The information system provides a real-time alert when organization-defined audit failure events occur.',NULL,NULL,NULL),
('000145','draft','2009-05-20','DISA FSO','policy','The information system enforces configurable network communications traffic volume thresholds reflecting limits on auditing capacity by delaying or rejecting network traffic which exceeds the organization-defined thresholds.','AU-5(3).1','The organization being inspected/assessed configures the information system to delay network communications traffic exceeding the thresholds defined in AU-5 (3), CCI 1859. DoD has defined the action to take as delay. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 145.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to delay network communications traffic exceeding the thresholds defined in AU-5 (3), CCI 1859. DoD has defined the action to take as delay. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 145.'),
('000146','draft','2009-05-20','DISA FSO','policy','The organization defines the percentage of maximum audit record storage capacity that when exceeded, a warning is provided.',NULL,NULL,NULL),
('000147','draft','2009-05-22','DISA FSO','policy','The organization defines the audit failure events requiring real-time alerts.','AU-5(2).1','DoD has defined the audit failure events as all.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the audit failure events as all.'),
('000148','draft','2009-05-22','DISA FSO','policy','The organization reviews and analyzes information system audit records on an organization-defined frequency for indications of organization-defined inappropriate or unusual activity.','AU-6.1','The organization being inspected/assessed documents and implements a process to review and analyze information system audit records every seven days or more frequently if required by an alarm event or anomaly for indications of activity defined in AU-6, CCI 1862. The organization must maintain an audit trail of the reviews. DoD has defined the frequency as every seven days or more frequently if required by an alarm event or anomaly.','The organization conducting the inspection/assessment obtains and examines the documented process for audit trail reviews as well as the audit trail showing the reviews to ensure the organization being inspected/assessed reviews and analyzes information system audit records every seven days or more frequently if required by an alarm event or anomaly for indications of activity defined in AU-6, CCI 1862. DoD has defined the frequency as every seven days or more frequently if required by an alarm event or anomaly.'),
('000149','draft','2009-05-22','DISA FSO','policy','The organization reports any findings to organization-defined personnel or roles for indications of organization-defined inappropriate or unusual activity.','AU-6.4','The organization being inspected/assessed documents and implements a process for reporting any findings of inappropriate or unusual activity as defined in AU-6, CCI 1862 to at a minimum, the ISSO and ISSM. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines the documented process for reporting findings as well as a sampling of historical reports to ensure the organization being inspected/assessed reports any findings of inappropriate or unusual activity as defined in AU-6, CCI 1862 to at a minimum, the ISSO and ISSM. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('000150','draft','2009-09-15','DISA FSO','policy','The organization adjusts the level of audit review, analysis, and reporting within the information system when there is a change in risk to organizational operations, organizational assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information.',NULL,NULL,NULL),
('000151','draft','2009-09-15','DISA FSO','policy','The organization defines the frequency for the review and analysis of information system audit records for organization-defined inappropriate or unusual activity.','AU-6.2','DoD has defined the frequency as every seven days or more frequently if required by an alarm event or anomaly.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every seven days or more frequently if required by an alarm event or anomaly.'),
('000152','draft','2009-05-22','DISA FSO','technical','The information system integrates audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities.',NULL,NULL,NULL),
('000153','draft','2009-05-22','DISA FSO','policy','The organization analyzes and correlates audit records across different repositories to gain organization-wide situational awareness.','AU-6(3).1','The organization being inspected/assessed documents and implements a process to analyze and correlate audit records across different repositories to gain organization-wide situational awareness. The organization must maintain a record of the analysis.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of analysis to ensure the organization being inspected/assessed analyzes and correlates audit records across different repositories to gain organization-wide situational awareness.'),
('000154','draft','2009-05-22','DISA FSO','technical','The information system provides the capability to centrally review and analyze audit records from multiple components within the system.','AU-6(4).1','The organization being inspected/assessed configures the information system to provide a capability to centrally review and analyze audit records from multiple components within the system. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 154.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to provide a capability to centrally review and analyze audit records from multiple components within the system. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 154.'),
('000155','draft','2009-09-15','DISA FSO','policy','The organization integrates analysis of audit records with analysis of vulnerability scanning information, performance data, and network monitoring information to further enhance the ability to identify inappropriate or unusual activity.',NULL,NULL,NULL),
('000156','draft','2009-05-22','DISA FSO','technical','The information system provides an audit reduction capability.',NULL,NULL,NULL),
('000157','draft','2009-05-22','DISA FSO','technical','The information system provides a report generation capability.',NULL,NULL,NULL),
('000158','draft','2009-05-22','DISA FSO','technical','The information system provides the capability to process audit records for events of interest based on organization-defined audit fields within audit records.','AU-7(1).1','The organization being inspected/assessed must employ information systems that provide the capability to process audit records for events of interest based on audit fields within audit records defined in AU-7 (1), CCI 1883. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 158.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provides the capability to process audit records for events of interest based on audit fields within audit records as defined in AU-7 (1), CCI 1883. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 158.'),
('000159','draft','2009-05-22','DISA FSO','technical','The information system uses internal system clocks to generate time stamps for audit records.','AU-8.1','The organization being inspected/assessed configures the information system to use internal system clocks to generate time stamps for audit records. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 159.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to use internal system clocks to generate time stamps for audit records. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 159.'),
('000160','draft','2009-05-22','DISA FSO','technical','The information system synchronizes internal information system clocks on an organization-defined frequency with an organization-defined authoritative time source.',NULL,NULL,NULL),
('000161','draft','2009-05-22','DISA FSO','policy','The organization defines the frequency for the synchronization of internal information system clocks.','AU-8(1).1','DoD has defined the frequency as every 24 hours for networked systems.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 24 hours for networked systems.'),
('000162','draft','2009-05-22','DISA FSO','technical','The information system protects audit information from unauthorized access.','AU-9.1','The organization being inspected/assessed configures the information system to disallow unauthorized access to audit information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 162.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to disallow unauthorized access to audit information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 162.'),
('000163','draft','2009-05-22','DISA FSO','technical','The information system protects audit information from unauthorized modification.','AU-9.2','The organization being inspected/assessed configures the information system to disallow unauthorized modification of audit information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 163.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to disallow unauthorized modification of audit information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 163.'),
('000164','draft','2009-05-22','DISA FSO','technical','The information system protects audit information from unauthorized deletion.','AU-9.3','The organization being inspected/assessed configures the information system to disallow unauthorized deletion of audit information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 164.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to disallow unauthorized deletion of audit information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 164.'),
('000165','draft','2009-05-22','DISA FSO','policy','The information system writes audit records to hardware-enforced, write-once media.','AU-9(1).1','The organization being inspected/assessed configures the information system to write audit records to hardware-enforced, write-once media. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 165.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to write audit records to hardware-enforced, write-once media. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 165.'),
('000166','draft','2009-05-22','DISA FSO','technical','The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.','AU-10.1','The organization being inspected/assessed configures the information system to protect against an individual falsely denying having performed actions to be covered by non-repudiation defined in DoDI 8520.02 and DoDI 8520.03. DoDI 8520.02 and DoDI 8520.03 meet the DoD requirement to define the actions to be covered by non-repudiation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 166.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed protects against an individual falsely denying having performed actions to be covered by non-repudiation defined in DoDI 8520.02 and DoDI 8520.03. DoDI 8520.02 and DoDI 8520.03 meet the DoD requirement to define the actions to be covered by non-repudiation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 166.'),
('000167','draft','2009-05-22','DISA FSO','policy','The organization retains audit records for an organization-defined time period to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements.','AU-11.1','The organization being inspected/assessed will take action to ensure it retains audit records for 5 years for SAMI; otherwise for at least 1 year to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements. DoD has defined the time period as 5 years for SAMI; otherwise for at least 1 year.','The organization conducting the inspection/assessment reviews the information system audit records and any other relevant documents or records to ensure the organization being inspected/assessed retains its audit records for 5 years for SAMI; otherwise for at least 1 year. DoD has defined the time period as 5 years for SAMI; otherwise for at least 1 year.'),
('000168','draft','2009-09-15','DISA FSO','policy','The organization defines the time period for retention of audit records, which is consistent with its records retention policy, to provide support for after-the-fact investigations of security incidents and meet regulatory and organizational information retention requirements.','AU-11.2','DoD has defined the time period as 5 years for SAMI; otherwise for at least 1 year.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 5 years for SAMI; otherwise for at least 1 year.'),
('000169','draft','2009-05-22','DISA FSO','technical','The information system provides audit record generation capability for the auditable events defined in AU-2 a. at organization-defined information system components.','AU-12.1','The organization being inspected/assessed acquires or designs all information system and network components that provide audit record generation capability for the auditable events defined in AU-2 a. DoD has defined the information system components as all information system and network components.','The organization conducting the inspection/assessment examines the information system to ensure that all information system and network components provide audit record generation capability for the auditable events defined in AU-2 a. DoD has defined the information system components as all information system and network components.'),
('000170','draft','2009-11-03','DISA FSO','policy','The organization implements a process for ensuring that plans of action and milestones for the security program and associated organizational information systems document the remedial information security actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation.','PM-4.3','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to maintain a process to document the remedial information security actions that mitigate risk to organizational operations and assets, individuals, other organizations, and the Nation.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to maintain a process to document the remedial information security actions that mitigate risk to organizational operations and assets, individuals, other organizations, and the Nation.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.'),
('000171','draft','2009-09-15','DISA FSO','technical','The information system allows organization-defined personnel or roles to select which auditable events are to be audited by specific components of the information system.','AU-12.3','The organization being inspected/assessed configures the information system to ensure that only the ISSM or individuals appointed by the ISSM select which auditable events are to be audited by specific components of the information system. DoD has defined the personnel or roles as the ISSM or individuals appointed by the ISSM.','The organization conducting the inspection/assessment examines a sampling of information system components and confirms that the individuals capable of selecting auditable events are the ISSM or individuals appointed by the ISSM. DoD has defined the personnel or roles as the ISSM or individuals appointed by the ISSM.'),
('000172','draft','2009-09-15','DISA FSO','technical','The information system generates audit records for the events defined in AU-2 d. with the content defined in AU-3.','AU-12.5','The organization being inspected/assessed configures the information system to generate audit records for the events defined in AU-2 d with the content defined in AU-3. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 172.','The organization conducting the inspection/assessment examines the information system to ensure that the system generates audit records for the events defined in AU-2 d with the content defined in AU-3. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 172.'),
('000173','draft','2009-09-15','DISA FSO','policy','The organization defines the level of tolerance for relationship between time stamps of individual records in the audit trail that will be used for correlation.','AU-12(1).1','The organization being inspected/assessed will define and document their level of tolerance for variation in the time stamps applied to the audit data generated by the organization\'s information systems.\n\nDoD has determined that the level of tolerance is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment reviews the organization\'s audit and accountability policy and procedures addressing audit record generation and retention; information system audit configuration settings and associated documentation; information system audit records; and any other relevant documents or records. The objective is to validate the organization has defined and documented its level of tolerance for variation in the time stamps applied to the audit data generated by the organization\'s information systems.\n\nDoD has determined that the level of tolerance is not appropriate to define at the Enterprise level.'),
('000174','draft','2009-05-22','DISA FSO','technical','The information system compiles audit records from organization-defined information system components into a system-wide (logical or physical) audit trail that is time-correlated to within an organization-defined level of tolerance for relationship between time stamps of individual records in the audit trail.','AU-12(1).2','The organization being inspected/assessed configures the information system to compile audit records from information system components defined in AU-12 (1), CCI 1577 into a system-wide (logical or physical) audit trail that is time-correlated to within the level of tolerance defined in AU-12 (1), CCI-000173 for relationship between time stamps of individual records in the audit trail.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 174.','The organization conducting the inspection/assessment examines the information system to ensure the information system is configured to compile audit records from information system components defined in AU-12 (1), CCI 1577 into a system-wide (logical or physical) audit trail that is time-correlated to within the level of tolerance defined in AU-12 (1), CCI-000173 for relationship between time stamps of individual records in the audit trail.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 174.'),
('000175','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators for users and devices by verifying, as part of the initial authenticator distribution, the identity of the individual and/or device receiving the authenticator.',NULL,NULL,NULL),
('000176','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by establishing initial authenticator content for authenticators defined by the organization.','IA-5.2','The organization being inspected/assessed defines and documents procedures for setting initial authenticator content.','The organization conducting the inspection/assessment obtains and examines the documented procedures for setting initial authenticator content to ensure they have been defined.'),
('000177','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators for users and devices by establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised, or damaged authenticators, and for revoking authenticators.',NULL,NULL,NULL),
('000178','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators for users and devices by changing default content of authenticators upon information system installation.',NULL,NULL,NULL),
('000179','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by establishing minimum lifetime restrictions for authenticators.','IA-5.13','The organization being inspected/assessed defines and documents minimum lifetime restrictions for authenticators.','The organization conducting the inspection/assessment obtains and examines the documented minimum lifetime restrictions for authenticators to ensure they have been defined.'),
('000180','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by establishing maximum lifetime restrictions for authenticators.','IA-5.14','Per IA-5, CCI 1610, DoD has established the maximum lifetime restrictions for authenticators as CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years.','Per IA-5, CCI 1610, DoD has established the maximum lifetime restrictions for authenticators as CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years.'),
('000181','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by establishing reuse conditions for authenticators.','IA-5.15','The organization being inspected/assessed defines and documents the reuse conditions for authenticators.','The organization conducting the inspection/assessment obtains and examines the documented reuse conditions for authenticators to ensure they have been defined.'),
('000182','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by changing/refreshing authenticators in accordance with the organization-defined time period by authenticator type.','IA-5.16','The organization being inspected/assessed documents and implements procedures for changing/refreshing authenticators in the following time periods: CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years. DoD has defined the time period as CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years.','The organization conducting the inspection/assessment obtains and examines the documented procedures for authenticator change/refresh to ensure the procedures are defined. The organization conducting the inspection/assessment obtains and examines a sampling of authenticator age data to ensure that authenticators are changed or refreshed in the following time periods: CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years. DoD has defined the time period as CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years.'),
('000183','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by protecting authenticator content from unauthorized disclosure.','IA-5.19','The organization being inspected/assessed documents and implements procedures to protect authenticator content from unauthorized disclosure.','The organization conducting the inspection/assessment obtains and examines the documented procedures to protect authenticator content from unauthorized disclosure to ensure the procedures are defined.'),
('000184','draft','2009-05-22','DISA FSO','policy','The organization manages information system authenticators by requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators.',NULL,NULL,NULL),
('000185','draft','2009-09-15','DISA FSO','technical','The information system, for PKI-based authentication, validates certifications by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information.','IA-5(2).1','The information system performing hardware token-based authentication must be configured to validate DoD-approved PKI credentials in accordance with RFC 5280. The information system must be configured to perform a revocation check as part of the certificate validation process. Revocation checking may be performed using certificate revocation lists (CRLs) published by the issuing PKI or Online Certificate Status Protocol (OCSP) services. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 185.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to validate DoD-approved PKI credentials in accordance with RFC 5280. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to perform a revocation check as part of the certificate validation process. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 185.'),
('000186','draft','2009-09-15','DISA FSO','technical','The information system, for PKI-based authentication, enforces authorized access to the corresponding private key.','IA-5(2).2','Information systems must not have access to users private keys. The cryptographic container in which the private keys are stored (e.g. smart card or software module) implements access controls and protections to ensure that only the authorized user can activate the private key. DoD users agree to protect their PKI credentials in accordance with the DD-2842 agreement that is executed for each credential. They are reminded of these responsibilities in annual IA training. The private key identifying the information system must be stored in a cryptographic container that is FIPS 140-2 validated. Only authorized information system operators should have access to activation data (e.g. password or PIN) for the private key.','The organization conducting the inspection/assessment examines the information system to ensure the information system does not contain any users private keys. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to store its own private key in a FIPS 140-2 validated cryptographic module.'),
('000187','draft','2009-09-15','DISA FSO','technical','The information system, for PKI-based authentication, maps the authenticated identity to the account of the individual or group.','IA-5(2).3','The information system performing PKI-based authentication must be configured to map the authenticated PKI credential to a corresponding network or information system account or role in accordance with DoDI 8520.03. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 187.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to map authenticated PKI credentials to corresponding network or information system accounts or roles in accordance with DoDI 8520.03. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 187.'),
('000188','draft','2009-09-15','DISA FSO','policy','The organization requires that the registration process to receive an organizational-defined type of authenticator be carried out in person before a designated registration authority with authorization by a designated organizational official (e.g., a supervisor).',NULL,NULL,NULL),
('000189','draft','2009-09-15','DISA FSO','policy','The organization employs automated tools to determine if authenticators are sufficiently strong to resist attacks intended to discover or otherwise compromise the authenticators.',NULL,NULL,NULL),
('000190','draft','2009-09-15','DISA FSO','policy','The organization requires vendors/manufacturers of information system components to provide unique authenticators or change default authenticators prior to delivery.',NULL,NULL,NULL),
('000191','deprecated','2009-09-15','DISA FSO','policy','The organization enforces password complexity by the number of special characters used.',NULL,NULL,NULL),
('000192','draft','2009-09-15','DISA FSO','technical','The information system enforces password complexity by the minimum number of upper case characters used.','IA-5(1).1','The organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of upper case characters used. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 192.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of upper case characters used. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 192.'),
('000193','draft','2009-09-15','DISA FSO','technical','The information system enforces password complexity by the minimum number of lower case characters used.','IA-5(1).2','The organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of lower case characters used. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 193.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of lower case characters used. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 193.'),
('000194','draft','2009-09-15','DISA FSO','technical','The information system enforces password complexity by the minimum number of numeric characters used.','IA-5(1).4','The organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of numeric characters used. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 194.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of numeric characters used. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 194.'),
('000195','draft','2009-09-15','DISA FSO','technical','The information system, for password-based authentication, when new passwords are created, enforces that at least an organization-defined number of characters are changed.','IA-5(1).10','The organization being inspected/assessed configures the information system to enforce that at least 50% of the minimum password length is changed.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 195.\nDoD has defined the minimum number of characters as 50% of the minimum password length.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce that at least 50% of the minimum password length is changed.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 195.\nDoD has defined the minimum number of characters as 50% of the minimum password length.'),
('000196','draft','2009-09-15','DISA FSO','technical','The information system, for password-based authentication, stores only cryptographically-protected passwords.','IA-5(1).12','The organization being inspected/assessed configures the information system to store only encrypted representations of passwords.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 196.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to store only encrypted representations of passwords.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 196.'),
('000197','draft','2009-09-15','DISA FSO','technical','The information system, for password-based authentication, transmits only cryptographically-protected passwords.','IA-5(1).13','The organization being inspected/assessed configures the information system to transmit only encrypted representations of passwords.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 197.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to transmit only encrypted representations of passwords.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 197.'),
('000198','draft','2009-09-15','DISA FSO','technical','The information system enforces minimum password lifetime restrictions.','IA-5(1).14','The organization being inspected/assessed configures the information system to enforce minimum password lifetime restrictions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 198.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce minimum password lifetime restrictions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 198.'),
('000199','draft','2009-09-15','DISA FSO','technical','The information system enforces maximum password lifetime restrictions.','IA-5(1).15','The organization being inspected/assessed configures the information system to enforce maximum password lifetime restrictions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 199.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce maximum password lifetime restrictions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 199.'),
('000200','draft','2009-05-22','DISA FSO','technical','The information system prohibits password reuse for the organization-defined number of generations.','IA-5(1).18','The organization being inspected/assessed configures the information system to prohibit reuse for a minimum of 5 generations. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 200. DoD has defined the number of generations as a minimum of 5.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prohibit reuse for a minimum of 5 generations. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 200. DoD has defined the number of generations as a minimum of 5.'),
('000201','draft','2009-05-22','DISA FSO','policy','The organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access.','IA-5(6).1','The organization being inspected/assessed documents and implements procedures to protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed protects authenticators commensurate with the security category of the information to which use of the authenticator permits access.'),
('000202','draft','2009-05-22','DISA FSO','policy','The organization ensures unencrypted static authenticators are not embedded in access scripts.','IA-5(7).1','The organization being inspected/assessed documents and implements requirements that unencrypted static authenticators not be embedded in access scripts.','The organization conducting the inspection/assessment obtains and examines the requirements that unencrypted static authenticators not be embedded in access scripts to ensure the organization being inspected/assessed ensures unencrypted static authenticators are not embedded in access scripts.'),
('000203','draft','2009-05-22','DISA FSO','policy','The organization ensures unencrypted static authenticators are not stored on function keys.','IA-5(7).2','The organization being inspected/assessed documents and implements requirements that unencrypted static authenticators not be stored on function keys.','The organization conducting the inspection/assessment obtains and examines the requirements that unencrypted static authenticators not be stored on function keys to ensure the organization being inspected/assessed ensures unencrypted static authenticators are not stored on function keys.'),
('000204','draft','2009-05-22','DISA FSO','policy','The organization defines the security safeguards required to manage the risk of compromise due to individuals having accounts on multiple information systems.','IA-5(8).1','DoD has defined the security safeguards as policies and user training including advising users not to use the same password for any of the following: Domains of differing classification levels. More than one domain of a classification level (e.g., internal agency network and Intelink). More than one privilege level (e.g., user, administrator).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security safeguards as policies and user training including advising users not to use the same password for any of the following: Domains of differing classification levels. More than one domain of a classification level (e.g., internal agency network and Intelink). More than one privilege level (e.g., user, administrator).'),
('000205','draft','2009-05-22','DISA FSO','technical','The information system enforces minimum password length.','IA-5(1).3','The organization being inspected/assessed configures the information system to enforce minimum password length. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 205.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce minimum password length. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 205.'),
('000206','draft','2009-05-22','DISA FSO','technical','The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.','IA-6.1','The organization being inspected/assessed configures the information system to obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 206.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 206.'),
('000207','draft','2009-11-03','DISA FSO','policy','The organization develops and maintains an inventory of its information systems.','PM-5.1','DITPR is the inventory for all DoD information systems.\n\nThe organization being inspected/assessed must register and maintain their information systems in DITPR.','DITPR is the inventory for all DoD information systems.\n\nThe organization conducting the inspection/assessment obtains and examines the inventory of information systems via DITPR to ensure the organization being inspected/assessed registers their information systems in DITPR.'),
('000208','draft','2009-09-14','DISA FSO','policy','The organization determines normal time-of-day and duration usage for information system accounts.',NULL,NULL,NULL),
('000209','draft','2009-11-03','DISA FSO','policy','The organization develops the results of information security measures of performance.','PM-6.1','The Federal Information Systems Management Act (FISMA) meets the DoD requirements for information security performance measures of performance.','The Federal Information Systems Management Act (FISMA) meets the DoD requirements for information security performance measures of performance.\n\nDoD organizations are automatically compliant with this CCI as they are covered at the DoD level by FISMA.'),
('000210','draft','2009-11-03','DISA FSO','policy','The organization monitors the results of information security measures of performance.','PM-6.2','The Federal Information Systems Management Act (FISMA) meets the DoD requirements for information security performance measures of performance.','The Federal Information Systems Management Act (FISMA) meets the DoD requirements for information security performance measures of performance.\n\nDoD organizations are automatically compliant with this CCI as they are covered at the DoD level by FISMA.'),
('000211','draft','2009-11-03','DISA FSO','policy','The organization reports on the results of information security measures of performance.','PM-6.3','The organization being inspected/assessed reports the results of information security measures of performance IAW FISMA reporting guidance.','The organization conducting the inspection/assessment obtains and examines FISMA reporting documentation.'),
('000212','draft','2009-11-03','DISA FSO','policy','The organization develops an enterprise architecture with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-7.1','The GIG IA Architecture meets the DoD requirements for enterprise architecture.\n\nDoD components are automatically compliant with this CCI as they covered at the DoD level.','The GIG IA Architecture meets the DoD requirements for enterprise architecture.\n\nDoD components are automatically compliant with this CCI as they covered at the DoD level.'),
('000213','draft','2009-09-14','DISA FSO','technical','The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies.','AC-3.1','The organization being inspected/assessed configures the information system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 213.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 213.'),
('000214','draft','2009-09-14','DISA FSO','policy','The organization establishes a Discretionary Access Control (DAC) policy that limits propagation of access rights.',NULL,NULL,NULL),
('000215','draft','2009-09-14','DISA FSO','policy','The organization establishes a Discretionary Access Control (DAC) policy that includes or excludes access to the granularity of a single user.',NULL,NULL,NULL),
('000216','draft','2009-11-03','DISA FSO','policy','The organization develops and documents a critical infrastructure and key resource protection plan that addresses information security issues.','PM-8.1','DoDD 3020.40 meets the DoD requirement for the development of a critical infrastructure and key resource protection plan.\n\nDoD components are automatically compliant with this CCI as they are covered by the DoD level, DoDD 3020.40.','DoDD 3020.40 meets the DoD requirement for the development of a critical infrastructure and key resource protection plan.\n\nDoD components are automatically compliant with this CCI as they are covered by the DoD level, DoDD 3020.40.'),
('000217','draft','2009-09-24','DISA FSO','policy','The organization defines a time period after which inactive accounts are automatically disabled.','AC-2(3).2','DoD has defined the time period as 35 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 35 days.'),
('000218','draft','2009-09-14','DISA FSO','technical','The information system, when transferring information between different security domains, identifies information flows by data type specification and usage.',NULL,NULL,NULL),
('000219','draft','2009-09-14','DISA FSO','technical','The information system, when transferring information between different security domains, decomposes information into organization-defined policy-relevant subcomponents for submission to policy enforcement mechanisms.','AC-4(13).1','The organization being inspected/assessed configures the information system to decompose information into policy-relevant subcomponents defined in AC-4 (13), CCI 2202 for submission to policy enforcement mechanisms when transferring information between different security domains For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 219.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to decompose information into policy-relevant subcomponents defined in AC-4 (13), CCI 2202 for submission to policy enforcement mechanisms when transferring information between different security domains For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 219.'),
('000221','draft','2009-09-14','DISA FSO','technical','The information system enforces security policies regarding information on interconnected systems.',NULL,NULL,NULL),
('000223','draft','2009-09-14','DISA FSO','technical','The information system binds security attributes to information to facilitate information flow policy enforcement.',NULL,NULL,NULL),
('000224','draft','2009-09-14','DISA FSO','technical','The information system tracks problems associated with the security attribute binding.',NULL,NULL,NULL),
('000225','draft','2009-09-14','DISA FSO','policy','The organization employs the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions.','AC-6.1','The organization being inspected/assessed documents and implements the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions.','The organization conducting the inspection/assessment obtains and examines the documented processes to ensure that the organization being inspected/assessed implements the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions.'),
('000226','draft','2009-09-14','DISA FSO','technical','The information system provides the capability for a privileged administrator to configure organization-defined security policy filters to support different security policies.',NULL,NULL,NULL),
('000227','draft','2009-11-03','DISA FSO','policy','The organization develops a comprehensive strategy to manage risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of information systems.','PM-9.1','DoD Risk Management Framework meets the requirement for a comprehensive organizational risk strategy.\n\nDoD components are automatically compliant with this CCI because they are covered by the DoD Risk Management Framework (DoDI 8510.01).','DoD Risk Management Framework meets the requirement for a comprehensive organizational risk strategy.\n\nDoD components are automatically compliant with this CCI because they are covered by DoD Risk Management Framework (DoDI 8510.01).'),
('000228','draft','2009-11-03','DISA FSO','policy','The organization implements a comprehensive strategy to manage risk to organization operations and assets, individuals, other organizations, and the Nation associated with the operation and use of information systems consistently across the organization.','PM-9.2','DoD Risk Management Framework meets the requirement for a comprehensive organizational risk strategy.\n\nDoD components are automatically compliant with this CCI because they are covered by the DoD Risk Management Framework (DoDI 8510.01).','DoD Risk Management Framework meets the requirement for a comprehensive organizational risk strategy.\n\nDoD components are automatically compliant with this CCI because they are covered by DoD Risk Management Framework (DoDI 8510.01).'),
('000229','draft','2009-11-03','DISA FSO','policy','The organization documents the security state of organizational information systems and the environments in which those systems operate through security authorization processes.','PM-10.1','DoDI 8510.01 meets the DoD requirement to manage the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement to manage the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.'),
('000230','draft','2009-11-03','DISA FSO','policy','The organization tracks the security state of organizational information systems and the environments in which those systems operate through security authorization processes.','PM-10.2','DoDI 8510.01 meets the DoD requirement to manage the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement to manage the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.'),
('000231','draft','2009-11-03','DISA FSO','policy','The organization reports the security state of organizational information systems and the environments in which those systems operate through security authorization processes.','PM-10.3','DoDI 8510.01 meets the DoD requirement to manage the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement to manage the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.'),
('000232','draft','2009-09-14','DISA FSO','policy','The organization documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification and authentication.','AC-14.2','The organization being inspected/assessed documents supporting rationale in the security plan for the actions defined in AC-14, CCI 61 to not require identification and authentication.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed documents the supporting rationale for the actions defined in AC-14, CCI 61 to not require identification and authentication.'),
('000233','draft','2009-11-03','DISA FSO','policy','The organization designates individuals to fulfill specific roles and responsibilities within the organizational risk management process.','PM-10.4','DoDI 8510.01 meets the DoD requirement to designate roles and responsibilities for the risk management process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement to designate roles and responsibilities for the risk management process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.'),
('000234','draft','2009-11-03','DISA FSO','policy','The organization fully integrates the security authorization processes into an organization-wide risk management program.','PM-10.5','DoDI 8510.01 meets the DoD requirement to fully integrate the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement to fully integrate the security authorization process.\n\nDoD components are automatically compliant with this CCI because they are covered at the DoD level, DoDI 8510.01.'),
('000235','draft','2009-11-04','DISA FSO','policy','The organization defines mission/business processes with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-11.1','DoDI 8510.01 meets the DoD requirement to define mission/business processes.\n\nDoD components are automatically complaint with this CCI as they are covered at the DoD level, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement to define mission/business processes.\n\nDoD components are automatically complaint with this CCI as they are covered at the DoD level, DoDI 8510.01.'),
('000236','draft','2009-11-04','DISA FSO','policy','The organization determines information protection needs arising from the defined mission/business processes and revises the processes as necessary, until an achievable set of protection needs are obtained.','PM-11.2','The organization being inspected/assessed determines information protection needs IAW CNSSI 1253 and as identified in RA-2.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the security categorization has been documented IAW CNSSI 1253.'),
('000237','draft','2009-06-23','DISA FSO','policy','The organization manages information system accounts by specifically authorizing and monitoring the use of guest/anonymous accounts and temporary accounts.',NULL,NULL,NULL),
('000238','draft','2009-09-15','DISA FSO','policy','The organization defines the frequency to review and update the current security assessment and authorization policy.','CA-1.7','DoD has defined the frequency as every 5 years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 5 years.'),
('000239','draft','2009-09-15','DISA FSO','policy','The organization develops and documents a security assessment and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','CA-1.3','DoDI 8510.01 meets the DoD requirement for security assessment authorization policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement for security assessment authorization policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.'),
('000240','draft','2009-09-15','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles a security assessment and authorization policy.','CA-1.4','DoD disseminates DoDI 8510.01 organization-wide via the DoD Issuances website. http://www.dtic.mil/whs/directives/corres/ins1.html','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.'),
('000241','draft','2009-09-15','DISA FSO','policy','The organization reviews and updates the current security assessment and authorization policy in accordance with organization-defined frequency.','CA-1.8','DoDI 8510.01 meets the DoD requirement for security assessment authorization policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.','DoDI 8510.01 meets the DoD requirement for security assessment authorization policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.'),
('000242','draft','2009-09-15','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls.','CA-1.5','The organization being inspected/assessed develops and documents, IAW DoDI 8510.01, procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls.','The organization conducting the inspection/assessment obtains and examines the procedures to ensure the organization being inspected/assessed develops and documents procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls IAW DoDI 8510.01'),
('000243','draft','2009-09-15','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls.','CA-1.6','The organization being inspected/assessed will require all personnel to register at the DTIC website to receive update notifications to facilitate the implementation of the security assessment and authorization policy and associated security assessment and authorization controls.\n\nDoD has defined the personnel or roles as all personnel.','The organization conducting the inspection/assessment obtains and examines the AUP (Acceptable Use Policy), appointment orders, or written policy requiring that all personnel register at the DTIC website to receive update notifications.\n\nDoD has defined the personnel or roles as all personnel.'),
('000244','draft','2009-09-15','DISA FSO','policy','The organization reviews and updates the current security assessment and authorization procedures in accordance with organization-defined frequency.','CA-1.9','The organization being inspected/assessed reviews and updates, IAW DoDI 8510.01, the current security assessment and authorization procedures annually.\n\nThe organization must maintain an audit trail of review and update activity.\n\nDoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of review and update activity to ensure the organization being inspected/assessed reviews and updates, IAW DoDI 8510.01, the current security assessment and authorization procedures annually.'),
('000245','draft','2009-09-15','DISA FSO','policy','The organization develops a security assessment plan for the information system and its environment of operation.','CA-2.1','The organization being inspected/assessed will document these security assessment plan requirements as part of the DoD approved Security Plan. Security plan templates are provided through eMASS and the Knowledge Service. *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','The organization conducting the inspection/assessment obtains and examines the Security Plan to validate *security assessment blocks* are complete.'),
('000246','draft','2009-09-15','DISA FSO','policy','The organization\'s security assessment plan describes the security controls and control enhancements under assessment.','CA-2.2','The organization being inspected/assessed will ensure the Security Plan identifies the security controls and control enhancements under assessment. *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','The organization conducting the inspection/assessment obtains the security assessment plan to verify the plan identifies the security controls and those control enhancements under assessment.'),
('000247','draft','2009-09-15','DISA FSO','policy','The organization\'s security assessment plan describes assessment procedures to be used to determine security control effectiveness.','CA-2.3','The implementation guidance and validation procedures posted on the Knowledge Service constitutes assessment procedures for DoD.\n\nIf organizations being inspected/assessed use assessment procedures other than those posted on the Knowledge Service, those procedures must be documented.\n\n*Comment*\nThe items required within this CCI are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','DoD components are automatically compliant with this CCI if using the implementation guidance and validation procedures on the Knowledge Service.\n\nIf the organization being inspected/assessed is using alternative implementation guidance and validation procedures, the organization conducting the inspection/assessment will obtain and examine those procedures.'),
('000248','draft','2009-09-15','DISA FSO','policy','The organization\'s security assessment plan describes assessment environment.','CA-2.4','The organization being inspected/assessed will provide a description of the authorization boundary in their Security Plan. Authorization boundary can be described via one or more of the following: network diagrams, data flow diagrams, system design documents, or a list of information system components. Authorization boundary as defined in CNSSI 4009. *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','The organization conducting the inspection/assessment obtains and examines the organization\'s authorization boundary. Authorization boundary can be described via one or more of the following: network diagrams, data flow diagrams, system design documents, or a list of information system components.'),
('000249','draft','2009-09-15','DISA FSO','policy','The organizations security assessment plan describes the assessment team.',NULL,NULL,NULL),
('000250','draft','2009-09-15','DISA FSO','policy','The organization\'s security assessment plan describes assessment roles and responsibilities.',NULL,NULL,NULL),
('000251','draft','2009-09-15','DISA FSO','policy','The organization assesses, on an organization-defined frequency, the security controls in the information system and its environment of operation to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements.','CA-2.6','In accordance with DoD\'s published guidance, the organization being inspected/assessed will utilize the implementation guidance and validation procedures published on the Knowledge Service to evaluate the implementation status of the applicable controls. DoD has defined the frequency as annually for technical controls, annually for a portion of management and operational controls, such that all are reviewed in a 3 year period, except for those requiring more frequent review as defined in other site or overarching policy. (NOTE: Technical, Management and Operational is IAW NIST SP 800-53 Table 1-1). *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','See CA-2 c \"The organization conducting the inspection/assessment obtains and examines the security assessment report to verify that it includes the compliance/non-compliance status of all controls and specific deficiencies for all non-compliant controls.\"'),
('000252','draft','2009-09-15','DISA FSO','policy','The organization defines the frequency on which the security controls in the information system and its environment of operation are assessed.','CA-2.7','DoD has defined the frequency as annually for technical controls, annually for a portion of management and operation controls such that all are reviewed in a 3 year period except for those requiring more frequent review as defined in other site or overarching policy. NOTE: Technical, Management and Operational is IAW NIST SP 800-53 Table 1-1. *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually for technical controls, annually for a portion of management and operation controls such that all are reviewed in a 3 year period except for those requiring more frequent review as defined in other site or overarching policy. NOTE: Technical, Management and Operational is IAW NIST SP 800-53 Table 1-1.'),
('000253','draft','2009-09-15','DISA FSO','policy','The organization produces a security assessment report that documents the results of the assessment against the information system and its environment of operation.','CA-2.8','The organization being inspected/assessed will develop a SAR that includes the compliance/non-compliance status of all controls and specific deficiencies for all non-compliant controls using the template available on the Knowledge Service. *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact.','The organization conducting the inspection/assessment obtains and examines the SAR to verify that it includes the compliance/non-compliance status of all controls and specific deficiencies for all non-compliant controls.'),
('000254','draft','2009-09-15','DISA FSO','policy','The organization provides the results of the security control assessment against the information system and its environment of operation to organization-defined individuals or roles.','CA-2.9','The organization being inspected/assessed will provide the SAR to at a minimum, the ISSO and ISSM. DoD has defined the individuals or roles as at a minimum, the ISSO and ISSM. *Comment* The items required within this control are being split into the security plan and security assessment report to eliminate creation of an additional artifact. ','The organization conducting the inspection/assessment interviews at a minimum, the ISSO and ISSM to ensure the SAR has been received. DoD has defined the individuals or roles as at a minimum, the ISSO and ISSM. '),
('000255','draft','2009-09-15','DISA FSO','policy','The organization employs assessors or assessment teams with an organization-defined level of independence to conduct security control assessments of organizational information systems.','CA-2(1).1','The organization being inspected/assessed will employ assessors and assessor teams with the level of independence defined in CA-2 (1), CCI 2064 to conduct security control assessments of organizational information systems.','The organization conducting the inspection/assessment obtains and examines the level of independence defined in CA-2 (1), CCI 2064 to ensure that they, as the assessor, meet the required level of independence.'),
('000256','draft','2009-09-15','DISA FSO','policy','The organization includes, as part of security control assessments announced or unannounced, one or more of the following: in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment; performance/load testing; and organization-defined other forms of security assessment on an organization-defined frequency.','CA-2(2).1','The organization being assessed/inspected must document how they will annually conduct tests and exercises of the implemented security controls in their security assessment plan. The tests and exercises may consist of activities such as in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment; performance/load testing; or other forms of security assessment defined in CA-2 (2), CCI 1582. Vulnerability scans are not the same as penetration testing. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the test and exercise plan documented in the security assessment plan as well as the results of one or more of the latest security assessments to ensure the organization being inspected/assessed is conducting the assessments required in their security assessment plan annually. DoD has defined the frequency as annually.'),
('000257','draft','2009-09-15','DISA FSO','policy','The organization authorizes connections from the information system to other information systems through the use of Interconnection Security Agreements.','CA-3.1','The organization being inspected/assessed will develop and certify, by appropriate signatures (e.g. AO, network managers), Interconnection Security Agreements (e.g., MOU, MOA, SLA) authorizing the connection of its information systems to other information systems. Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.','The organization conducting the inspection/assessment obtains and examines documentation of the Interconnection Security Agreements to include appropriate signatures. Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.'),
('000258','draft','2009-09-15','DISA FSO','policy','The organization documents, for each interconnection, the interface characteristics.','CA-3.2','The organization being inspected/assessed will document the interface characteristics for each interconnection. Use of external reporting databases for these characteristics when tied to the specific interconnection is acceptable (e.g., ports, protocols, and services). Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.','The organization conducting the inspection/assessment obtains and examines interconnection security agreement documentation. Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.'),
('000259','draft','2009-09-15','DISA FSO','policy','The organization documents, for each interconnection, the security requirements.','CA-3.3','The organization being inspected/assessed will, for each interconnection, identify and document any additional security controls to be implemented to protect the confidentiality, integrity, and availability of the connected systems and the data passing between them. Controls should be appropriate for the systems to be connected and the environment in which the interconnection will operate. Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.','The organization conducting the inspection/assessment obtains and examines interconnection security agreement documentation, specifically looking at any additional security controls identified for implementation. Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.'),
('000260','draft','2009-09-15','DISA FSO','policy','The organization documents, for each interconnection, the nature of the information communicated.','CA-3.4','The organization being inspected/assessed will document in the interconnection security agreement the type of information being transferred/transmitted. Characteristics will include but are not limited to: classification, information type (e.g. PII, HIPAA, FOUO, financial data, etc.) Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.','The organization conducting the inspection/assessment obtains and examines the interconnection security agreement documentation, specifically to identify the type of information being transferred/transmitted. Characteristics will include but are not limited to: classification, information type (e.g. PII, HIPAA, FOUO, financial data, etc.) Policy Note: Interconnection security agreements are required for systems connecting between enclaves that require the hosting enclave to enable PPS outside of their already established and approved business practices. Connections can include both DoD enclaves or non DoD enclaves.'),
('000261','draft','2009-09-15','DISA FSO','policy','The organization monitors the information system connections on an ongoing basis to verify enforcement of security requirements.',NULL,NULL,NULL),
('000262','draft','2009-09-15','DISA FSO','policy','The organization prohibits the direct connection of an organization-defined unclassified, national security system to an external network without the use of an organization-defined boundary protection device.','CA-3(1).1','The organization being inspected/assessed documents in its policy and procedures addressing information system connections, the organization will prohibit DoD has defined the unclassified, national security systems as all unclassified NSS from having a direct connection to an external network without the use of a boundary protection device defined in CA-3 (1), CCI 262. DoD has defined the unclassified, national security systems as all unclassified NSS.','The organization conducting the inspection/assessment obtains and examines policy document prohibiting direct connection of all unclassified NSS to external networks without the use of a boundary protection device defined in CA-3 (1), CCI 262. DoD has defined the unclassified, national security systems as all unclassified NSS.'),
('000263','draft','2009-09-15','DISA FSO','policy','The organization prohibits the direct connection of a classified, national security system to an external network without the use of organization-defined boundary protection device.','CA-3(2).1','The organization being inspected/assessed does not connect any national security systems to an external network without the use of protection devices defined in CA-3 (2), CCI 2074.','The organization conducting the inspection/assessment obtains and examines network topology diagrams and examines the information system to ensure the organization being inspected/assessed does not connect any national security systems to an external network without the use of protection devices defined in CA-3 (2), CCI 2074.'),
('000264','draft','2009-09-15','DISA FSO','policy','The organization develops a plan of action and milestones for the information system to document the organization^s planned remedial actions to correct weaknesses or deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system.','CA-5.1','The organization being inspected/assessed will develop a security POA&M in accordance with DoDI 8510.01 Enclosure 6. POA&M templates are available on the Knowledge Service.','The organization conducting the inspection/assessment obtains and examines the security POA&M for compliance with DoDI 8510.01.'),
('000265','draft','2009-09-15','DISA FSO','policy','The organization defines the frequency with which to update the existing plan of action and milestones for the information system.','CA-5.2','DoD has defined the frequency as at least every 90 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least every 90 days.'),
('000266','draft','2009-09-15','DISA FSO','policy','The organization updates, on an organization-defined frequency, the existing plan of action and milestones for the information system based on the findings from security controls assessments, security impact analyses, and continuous monitoring activities.','CA-5.3','The organization being inspected/assessed will update the POA&M at least every 90 days. The updates are to be based upon the assessment of the identified vulnerabilities and weaknesses, prioritization of the vulnerabilities and weaknesses, progress being made in addressing and resolving the security weaknesses and vulnerabilities found in programs and systems, and continuous monitoring activities. DoD has defined the frequency as at least every 90 days.','The organization conducting the inspection/assessment obtains and examines current POA&M. The objective is to validate the organization is providing updates to the POA&M at least every 90 days. Review of POA&M without change must be documented (i.e., adding review date to the POA&M header information). DoD has defined the frequency as at least every 90 days.'),
('000267','draft','2009-09-15','DISA FSO','policy','The organization employs automated mechanisms to help ensure the plan of action and milestones for the information system is accurate.','CA-5(1).1','The organization being inspected/assessed will identify and document the automated mechanisms in use to ensure the security POA&M is accurate.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000268','draft','2009-09-15','DISA FSO','policy','The organization employs automated mechanisms to help ensure the plan of action and milestones for the information system is up to date.','CA-5(1).2','The organization being inspected/assessed will identify and document the automated mechanisms in use to ensure the POA&M is up to date.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000269','draft','2009-09-15','DISA FSO','policy','The organization employs automated mechanisms to help ensure the plan of action and milestones for the information system is readily available.','CA-5(1).3','The organization being inspected/assessed will identify and document the automated mechanisms in use to ensure the POA&M is readily available.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000270','draft','2009-09-15','DISA FSO','policy','The organization assigns a senior-level executive or manager as the authorizing official for the information system.','CA-6.1','The organization being inspected/assessed will assign a senior-level executive or manager as the official role, and the responsibility, for authorizing the information system(s). Assignment must be in writing and IAW with DoDI 8510.01 (i.e. Appointment memorandum).','The organization conducting the inspection/assessment obtains and examines the written appointment memorandum.'),
('000271','draft','2009-09-15','DISA FSO','policy','The organization ensures the authorizing official authorizes the information system for processing before commencing operations.','CA-6.2','The organization being inspected/assessed will ensure that an authorization document (e.g. authorization to operate (ATO), interim authorization to operate (IATO)) has been issued by the authorizing official (AO) prior to placing the information system into an operational status.','The organization conducting the inspection/assessment obtains and examines the authorization document to ensure the information system is authorized prior to being placed into operational status.'),
('000272','draft','2009-09-15','DISA FSO','policy','The organization updates the security authorization on an organization-defined frequency.','CA-6.3','The organization being inspected/assessed updates the security authorization at least every three years, whenever there is a significant change to the system, or if there is a change to the environment in which the system operates. DoD has defined the frequency as at least every three years, whenever there is a significant change to the system, or if there is a change to the environment in which the system operates.','The organization conducting the inspection/assessment obtains and examines the security authorization documentation to confirm the security authorization has been updated within the last three years, when there was a significant change to the system, or if there was a change to the environment in which the system operates. DoD has defined the frequency as at least every three years, whenever there is a significant change to the system, or if there is a change to the environment in which the system operates.'),
('000273','draft','2009-09-15','DISA FSO','policy','The organization defines the frequency with which to update the security authorization.','CA-6.4','DoD has defined the frequency as at least every three years, whenever there is a significant change to the system, or if there is a change to the environment in which the system operates.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least every three years, whenever there is a significant change to the system, or if there is a change to the environment in which the system operates.'),
('000274','draft','2009-09-15','DISA FSO','policy','The organization develops a continuous monitoring strategy.','CA-7.1','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('000275','draft','2009-09-15','DISA FSO','policy','The organization implements a continuous monitoring program that includes a configuration management process for the information system.',NULL,NULL,NULL),
('000276','draft','2009-09-15','DISA FSO','policy','The organization implements a continuous monitoring program that includes a configuration management process for the information system constituent components.',NULL,NULL,NULL),
('000277','draft','2009-09-15','DISA FSO','policy','The organization implements a continuous monitoring program that includes a determination of the security impact of changes to the information system.',NULL,NULL,NULL),
('000278','draft','2009-09-15','DISA FSO','policy','The organization implements a continuous monitoring program that includes a determination of the security impact of changes to the environment of operation.',NULL,NULL,NULL),
('000279','draft','2009-09-15','DISA FSO','policy','The organization implements a continuous monitoring program that includes ongoing security control assessments in accordance with the organizational continuous monitoring strategy.','CA-7.5','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('000280','draft','2009-09-15','DISA FSO','policy','The organization implements a continuous monitoring program that includes reporting the security status of the organization and the information system to organization-defined personnel or roles on an organization-defined frequency.','CA-7.9','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('000281','draft','2009-09-15','DISA FSO','policy','The organization defines the frequency with which to report the security status of the organization and the information system to organization-defined personnel or roles.','CA-7.10','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('000282','draft','2009-09-15','DISA FSO','policy','The organization employs assessors or assessment teams with an organization-defined level of independence to monitor the security controls in the information system on an ongoing basis.','CA-7(1).1','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('000283','draft','2009-09-15','DISA FSO','policy','The organization plans announced or unannounced assessments (in-depth monitoring, malicious user testing, penetration testing, red team exercises, or other organization-defined forms of security assessment), on an organization-defined frequency, to ensure compliance with all vulnerability mitigation procedures.',NULL,NULL,NULL),
('000284','draft','2009-09-15','DISA FSO','policy','The organization schedules announced or unannounced assessments (in-depth monitoring, malicious user testing, penetration testing, red team exercises, or other organization-defined forms of security assessment), on an organization-defined frequency, to ensure compliance with all vulnerability mitigation procedures.',NULL,NULL,NULL),
('000285','draft','2009-09-15','DISA FSO','policy','The organization conducts announced or unannounced assessments (in-depth monitoring, malicious user testing, penetration testing, red team exercises, or other organization-defined forms of security assessment), on an organization-defined frequency, to ensure compliance with all vulnerability mitigation procedures.',NULL,NULL,NULL),
('000286','draft','2009-09-17','DISA FSO','policy','The organization defines a frequency with which to review and update the configuration management policies.','CM-1.7','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000287','draft','2009-09-17','DISA FSO','policy','The organization develops and documents a configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','CM-1.3','The organization being inspected/assessed develops and documents a configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','The organization conducting the inspection/assessment obtains and examines the configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.'),
('000288','draft','2009-09-17','DISA FSO','policy','The organization disseminates formal, documented configuration management policy to elements within the organization having associated configuration management roles and responsibilities.',NULL,NULL,NULL),
('000289','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates, on an organization-defined frequency, the configuration management policy.','CM-1.8','The organization being inspected/assessed reviews and updates, annually, the configuration management policy. The organization must document each occurrence of the reviews and update actions as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines documentation of occurrence of reviews and update actions for the configuration management policy to ensure annual review and necessary updates are occurring. DoD has defined the frequency as annually.'),
('000290','draft','2009-09-17','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.','CM-1.5','The organization being inspected/assessed develops and documents procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.','The organization conducting the inspection/assessment obtains and examines the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.'),
('000291','draft','2009-09-17','DISA FSO','policy','The organization disseminates formal, documented procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.',NULL,NULL,NULL),
('000292','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates, on an organization-defined frequency, the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.','CM-1.9','The organization being inspected/assessed reviews and updates, annually, the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls. The organization must document each occurrence of the reviews and update actions as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines documentation of occurrence of reviews and update actions for the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls to ensure annual review and necessary updates are occurring. DoD has defined the frequency as annually.'),
('000293','draft','2009-09-17','DISA FSO','policy','The organization develops a current baseline configuration of the information system.','CM-2.1','The organization being inspected/assessed develops and documents a current baseline configuration of the information system.','The organization conducting the inspection/assessment obtains and examines the documented baseline configuration.'),
('000294','draft','2009-09-17','DISA FSO','policy','The organization documents a baseline configuration of the information system.',NULL,NULL,NULL),
('000295','draft','2009-09-17','DISA FSO','policy','The organization maintains, under configuration control, a current baseline configuration of the information system.','CM-2.2','The organization being inspected/assessed maintains a current baseline configuration of the information system.','The organization conducting the inspection/assessment obtains and examines the current baseline to ensure the current configuration matches the current documented baseline.'),
('000296','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates the baseline configuration of the information system at an organization-defined frequency.','CM-2(1).1','The organization being inspected/assessed reviews and updates the baseline configuration of the information system annually. The organization must document each occurrence of the reviews and update actions as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines documentation of organizational reviews and update actions for the baseline configuration to ensure annual review and necessary updates are occurring. DoD has defined the frequency as annually.'),
('000297','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates the baseline configuration of the information system when required due to organization-defined circumstances.','CM-2(1).3','The organization being inspected/assessed reviews and updates the baseline configuration of the information system when required due to baseline configuration changes or as events dictate such as changes due to USCYBERCOM tactical orders/ directives or cyber attacks. The organization must document each occurrence of the reviews and update actions as an audit trail. DoD has defined the circumstances as baseline configuration changes or as events dictate such as changes due to USCYBERCOM tactical orders/ directives or cyber attacks.','The organization conducting the inspection/assessment obtains and examines documentation of organizational reviews and update actions for the baseline configuration of the information system when required due to baseline configuration changes or as events dictate such as changes due to USCYBERCOM tactical orders/ directives or cyber attacks to ensure review and necessary updates are occurring. DoD has defined the circumstances as baseline configuration changes or as events dictate such as changes due to USCYBERCOM tactical orders/ directives or cyber attacks.'),
('000298','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates the baseline configuration of the information system as an integral part of information system component installations.','CM-2(1).5','The organization being inspected/assessed reviews and updates the baseline configuration of the information system as an integral part of information system component installations. The organization must document each occurrence of the reviews and update actions as an audit trail.','The organization conducting the inspection/assessment obtains and examines documentation of organizational reviews and update actions for the baseline configuration of the information system as an integral part of information system component installations to ensure review and necessary updates are occurring.'),
('000299','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates the baseline configuration of the information system as an integral part of information system component upgrades.','CM-2(1).6','The organization being inspected/assessed reviews and updates the baseline configuration of the information system as an integral part of information system component upgrades. The organization must document each occurrence of the reviews and update actions as an audit trail.','The organization conducting the inspection/assessment obtains and examines documentation of organizational reviews and update actions for the baseline configuration of the information system as an integral part of information system component upgrades to ensure review and necessary updates are occurring.'),
('000300','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to maintain a complete baseline configuration of the information system.','CM-2(2).1','The organization being inspected/assessed identifies, documents, and implements automated mechanisms used to maintain complete baseline configuration of the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms used to maintain complete baseline configuration of the information system. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000301','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to maintain an up-to-date baseline configuration of the information system.','CM-2(2).2','The organization being inspected/assessed identifies, documents, and implements automated mechanisms used to maintain an up-to-date baseline configuration of the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms used to maintain an up-to-date baseline configuration of the information system. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000302','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to maintain an accurate baseline configuration of the information system.','CM-2(2).3','The organization being inspected/assessed identifies, documents, and implements automated mechanisms used to maintain accurate baseline configuration of the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms used to maintain accurate baseline configuration of the information system. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000303','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to maintain a readily available baseline configuration of the information system.','CM-2(2).4','The organization being inspected/assessed identifies, documents, and implements automated mechanisms used to maintain readily available baseline configuration of the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms used to maintain readily available baseline configuration of the information system. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000304','draft','2009-09-17','DISA FSO','policy','The organization retains organization-defined previous versions of baseline configurations of the information system to support rollback.','CM-2(3).1','The organization being inspected/assessed retains the previous approved baseline configuration of IS components for a minimum of 3 months and documents baseline configuration to support rollback. The goal is to verify that the IS can roll back components to previous versions. DoD has defined the previous versions as the previous approved baseline configuration of IS components for a minimum of 3 months.','The organization conducting the inspection/assessment obtains and examines the documentation of the previous version of the baseline configuration to determine if all IS components necessary for rollback are retained. DoD has defined the previous versions as the previous approved baseline configuration of IS components for a minimum of 3 months.'),
('000305','draft','2009-09-17','DISA FSO','policy','The organization develops a list of software programs not authorized to execute on the information system.',NULL,NULL,NULL),
('000306','draft','2009-09-17','DISA FSO','policy','The organization maintains the list of software programs not authorized to execute on the information system.',NULL,NULL,NULL),
('000307','draft','2009-09-17','DISA FSO','policy','The organization employs an allow-all, deny-by-exception authorization policy to identify software allowed to execute on the information system.',NULL,NULL,NULL),
('000308','draft','2009-09-17','DISA FSO','policy','The organization develops the list of software programs authorized to execute on the information system.',NULL,NULL,NULL),
('000309','draft','2009-09-17','DISA FSO','policy','The organization maintains the list of software programs authorized to execute on the information system.',NULL,NULL,NULL),
('000310','draft','2009-09-17','DISA FSO','policy','The organization employs a deny-all, permit-by-exception authorization policy to identify software allowed to execute on the information system.',NULL,NULL,NULL),
('000311','draft','2009-09-17','DISA FSO','policy','The organization maintains a baseline configuration for information system development environments that is managed separately from the operational baseline configuration.','CM-2(6).1','The organization being inspected/assessed establishes and maintains a development environment baseline configuration managed separately from the operational baseline configuration.','The organization conducting the inspection/assessment obtains and examines development environment baseline configuration documentation and ensures the organization is maintaining and managing a baseline configuration for the development environment separate from the operational baseline configuration.'),
('000312','draft','2009-09-17','DISA FSO','policy','The organization maintains a baseline configuration for information system test environments that is managed separately from the operational baseline configuration.','CM-2(6).2','The organization being inspected/assessed establishes and maintains a test environment baseline configuration managed separately from the operational baseline configuration.','The organization conducting the inspection/assessment obtains and examines test environment baseline configuration documentation and ensures the organization is maintaining and managing a baseline configuration for the test environment separate from the operational baseline configuration.'),
('000313','draft','2009-09-17','DISA FSO','policy','The organization determines the types of changes to the information system that are configuration controlled.','CM-3.1','The organization being inspected/assessed determines the types of changes to the information system that are to be configuration controlled. This action will be implemented by the CCB as defined in CM-3, CCI 1586.','The organization conducting the inspection/assessment obtains and examines the configuration management policy and plan to ensure the organization identifies the types of changes to the information system that are configuration controlled.'),
('000314','draft','2009-09-17','DISA FSO','policy','The organization approves or disapproves configuration-controlled changes to the information system, with explicit consideration for security impact analysis.','CM-3.2','The organization being inspected/assessed approves or disapproves configuration controlled changes to the information system with explicit consideration for security impact analysis. The organization must maintain an audit trail of approval/disapproval of configuration controlled changes. This action will be implemented by the CCB as defined in CM-3, CCI 1586.','The organization conducting the inspection/assessment obtains and examines the audit trail of the approval/disapproval of configuration controlled changes to ensure a security impact analysis was conducted.'),
('000315','draft','2009-09-17','DISA FSO','policy','The organization documents approved configuration-controlled changes to the system.',NULL,NULL,NULL),
('000316','draft','2009-09-17','DISA FSO','policy','The organization retains records of configuration-controlled changes to the information system for an organization-defined time period.','CM-3.6','The organization being inspected/assessed retains records of all configuration-controlled changes to the information system, as a result of CM-3, CCI 1819, for a time period defined by the organization\'s CCB.\n\nDoD has defined the time period as a time period defined by the organization\'s CCB.','The organization conducting the inspection/assessment obtains and examines the records of all configuration-controlled changes to the information system to ensure the organization being inspected/assessed retains the records of all configuration controlled changes for a time period defined by the organization\'s CCB.\n\nDoD has defined the time period as a time period defined by the organization\'s CCB.'),
('000317','draft','2009-09-17','DISA FSO','policy','The organization reviews records of configuration-controlled changes to the system.',NULL,NULL,NULL),
('000318','draft','2009-09-17','DISA FSO','policy','The organization audits and reviews activities associated with configuration-controlled changes to the system.','CM-3.8','The organization being inspected/assessed audits and reviews activities associated with configuration-controlled changes to the information system. The organization must maintain an audit trail to include review activities associated with configuration-controlled changes.','The organization conducting the inspection/assessment obtains and examines the audit trail documenting the review activities associated with configuration-controlled changes to the information system to ensure the organization being inspected/assessed audits and reviews activities associated with the changes.'),
('000319','draft','2009-09-17','DISA FSO','policy','The organization coordinates and provides oversight for configuration change control activities through an organization-defined configuration change control element (e.g., committee, board) that convenes at the organization-defined frequency and/or for any organization-defined configuration change conditions.','CM-3.9','The organization being inspected/assessed coordinates and provides oversight for configuration change control activities through a configuration control board (CCB) that convenes at a frequency determined by the CCB and/or for any configuration change conditions determined by the CCB. DoD has defined the configuration change control element as a configuration control board. DoD has defined the frequency as at a frequency determined by the CCB. DoD has defined the configuration change conditions as configuration change conditions determined by the CCB.','The organization conducting the inspection/assessment obtains and examines the organization\'s configuration management policy and plan; document/charter establishing the organization\'s CCB; meeting minutes; information system change control records; and any other relevant documents or records. The objective of the review is to validate the organization is coordinating and overseeing the configuration change control activities through a CCB.'),
('000320','draft','2009-09-17','DISA FSO','policy','The organization defines the frequency with which to convene the configuration change control element.','CM-3.10','The organization being inspected/assessed defines within their CCB Charter, the frequency for configuration change control review. DoD has defined the frequency as at a frequency determined by the CCB.','The organization conducting the inspection/assessment obtains and examines the CCB Charter to ensure the frequency for configuration change control review is defined. DoD has defined the frequency as at a frequency determined by the CCB.'),
('000321','draft','2009-09-17','DISA FSO','policy','The organization defines configuration change conditions that prompt the configuration change control element to convene.','CM-3.11','The organization being inspected/assessed defines within their CCB Charter, the configuration change conditions that prompt the configuration change control element to convene. DoD has defined the configuration change conditions as configuration change conditions determined by the CCB.','The organization conducting the inspection/assessment obtains and examines the CCB Charter to ensure the configuration change conditions that prompt the configuration change control element to convene are defined. DoD has defined the configuration change conditions as configuration change conditions determined by the CCB.'),
('000322','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to document proposed changes to the information system.','CM-3(1).1','The organization being inspected/assessed documents and employs the automated mechanisms (e.g., Remedy, ticketing mechanism, etc.) to document proposed changes to the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system documents proposed changes. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000323','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to notify organization-defined approval authorities of proposed changes to the information system and request change approval.','CM-3(1).2','The organization being inspected/assessed documents and employs the automated mechanisms (e.g., Remedy, ticketing mechanism, etc.) to notify designated approval authorities of proposed changes to the information system and request change approval.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system notifies designated approval authorities of proposed changes to the information system and request change approval. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000324','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to highlight proposed changes to the information system that have not been approved or disapproved by an organization-defined time period.','CM-3(1).4','The organization being inspected/assessed documents and employs the automated mechanisms (e.g., Remedy, ticketing mechanism, etc.) to highlight proposed changes to the information system that have not been approved or disapproved by 7 days. DoD has defined the time period as 7 days.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system highlights proposed changes to the information system that have not been approved or disapproved by 7 days. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms. DoD has defined the time period as 7 days.'),
('000325','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to prohibit changes to the information system until designated approvals are received.','CM-3(1).6','The organization being inspected/assessed documents and employs the automated mechanisms to prohibit changes to the information system until designated approvals are received.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system prohibits changes. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000326','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to document all changes to the information system.','CM-3(1).7','The organization being inspected/assessed documents and employs the automated mechanisms (e.g., Remedy, ticketing mechanism, etc.) to document all changes to the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system documents all changes. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000327','draft','2009-09-17','DISA FSO','policy','The organization tests changes to the information system before implementing the changes on the operational system.','CM-3(2).1','The organization being inspected/assessed documents and implements a process to test changes to the information system before implementing the changes on the operational system. The organization must maintain an audit trail of testing activity.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of testing activity to ensure the organization being inspected/assessed tests changes to the information system before implementing the changes on the operational system.'),
('000328','draft','2009-09-17','DISA FSO','policy','The organization validates changes to the information system before implementing the changes on the operational system.','CM-3(2).2','The organization being inspected/assessed documents and implements a process to validate changes to the information system before implementing the changes on the operational system. The organization must maintain an audit trail of validation activity.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of validation activity to ensure the organization being inspected/assessed validates changes to the information system before implementing the changes on the operational system.'),
('000329','draft','2009-09-17','DISA FSO','policy','The organization documents changes to the information system before implementing the changes on the operational system.','CM-3(2).3','The organization being inspected/assessed documents and implements a process to document changes to the information system before implementing the changes on the operational system.','The organization conducting the inspection/assessment obtains and examines the documented process as well as documentation of changes to the information system to ensure the organization has established, published, and is complying with the requirement to document all changes to be made to its operational information system(s) prior to their implementation.'),
('000330','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to implement changes to the current information system baseline.','CM-3(3).1','The organization being inspected/assessed documents and employs the automated mechanisms (e.g., software deployment tools) to implement changes to the current information system baseline.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system implements changes to the current information system baseline. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000331','draft','2009-09-17','DISA FSO','policy','The organization deploys the updated information system baseline across the installed base.','CM-3(3).2','The organization being inspected/assessed documents and employs procedures for deploying the updated information system baseline across the installed base. The information system must maintain an audit trail of automated baseline deployments.','The organization conducting the inspection/assessment obtains and examines the documented deployment procedures and a sampling of the audit trail of automated baseline deployments to ensure the organization being inspected/assessed is deploying the updated information system baseline across the installed base.'),
('000332','draft','2009-09-17','DISA FSO','policy','The organization requires an information security representative to be a member of the organization-defined configuration change control element.','CM-3(4).1','The organization being inspected/assessed requires an information security representative to be a member of the configuration control board. DoD has defined the configuration change control element as the configuration control board.','The organization conducting the inspection/assessment obtains and examines the membership list of the organization\'s configuration control board to ensure an information security representative is a member of the organization\'s configuration control board.'),
('000333','draft','2009-09-18','DISA FSO','policy','The organization analyzes changes to the information system to determine potential security impacts prior to change implementation.','CM-4.1','The organization being inspected/assessed analyzes changes to the information system to determine potential security impacts prior to change implementation. The organization must maintain records of analysis of changes to the information system.','The organization conducting the inspection/assessment obtains and examines the records of analyses to ensure the organization is conducting a security impact analysis of changes to the information system(s) prior to their implementation.'),
('000334','draft','2009-09-18','DISA FSO','policy','The organization analyzes new software in a separate test environment before installation in an operational environment.',NULL,NULL,NULL),
('000335','draft','2009-09-18','DISA FSO','policy','The organization, after the information system is changed, checks the security functions to verify the functions are implemented correctly.','CM-4(2).1','The organization being inspected/assessed documents and implements a process to verify in an operational environment, following changes to the information system, the security functions are implemented correctly. The organization must maintain an audit trail of the verification of security functions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of the verification of security functions to ensure the organization being inspected/assessed verifies in an operational environment, following changes to the information system, the security functions are implemented correctly.'),
('000336','draft','2009-09-18','DISA FSO','policy','The organization, after the information system is changed, checks the security functions to verify the functions are operating as intended.','CM-4(2).2','The organization being inspected/assessed documents and implements a process to verify in an operational environment, following changes to the information system, the security functions are operating as intended. The organization must maintain an audit trail of the verification of security functions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of the verification of security functions to ensure the organization being inspected/assessed verifies in an operational environment, following changes to the information system, the security functions are operating as intended.'),
('000337','draft','2009-09-18','DISA FSO','policy','The organization, after the information system is changed, checks the security functions to verify the functions are producing the desired outcome with regard to meeting the security requirements for the system.','CM-4(2).3','The organization being inspected/assessed documents and implements a process to verify in an operational environment, following changes to the information system, the security functions are producing the desired outcome with regard to meeting the security requirements for the system. The organization must maintain an audit trail of the verification of security functions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of the verification of security functions to ensure the organization being inspected/assessed verifies in an operational environment, following changes to the information system, the security functions are producing the desired outcome with regard to meeting the security requirements for the system.'),
('000338','draft','2009-09-18','DISA FSO','policy','The organization defines physical access restrictions associated with changes to the information system.','CM-5.1','The organization being inspected/assessed defines and documents in the configuration management policy, physical access restrictions associated with changes to the information system.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines physical access restrictions associated with changes to the information system.'),
('000339','draft','2009-09-18','DISA FSO','policy','The organization documents physical access restrictions associated with changes to the information system.','CM-5.2','The organization being inspected/assessed documents, in the configuration management policy, physical access restrictions associated with changes to the information system.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed documents physical access restrictions associated with changes to the information system.'),
('000340','draft','2009-09-18','DISA FSO','policy','The organization approves physical access restrictions associated with changes to the information system.','CM-5.3','The organization being inspected/assessed documents and implements a process to approve physical access restrictions associated with changes to the information system. The organization must maintain an audit trail of approvals.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of approvals to ensure the organization being inspected/assessed approves physical access restrictions associated with changes to the information system.'),
('000341','draft','2009-09-18','DISA FSO','policy','The organization enforces physical access restrictions associated with changes to the information system.','CM-5.4','The organization being inspected/assessed documents and implements a process to enforce physical access restrictions associated with changes to the information system.','The organization conducting the inspection/assessment the documented process to ensure the organization being inspected/assessed enforces physical access restrictions associated with changes to the information system as documented in the configuration management policy.'),
('000342','draft','2009-09-18','DISA FSO','policy','The organization defines logical access restrictions associated with changes to the information system.','CM-5.5','The organization being inspected/assessed defines and documents in the configuration management policy, logical access restrictions associated with changes to the information system.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines logical access restrictions associated with changes to the information system.'),
('000343','draft','2009-09-18','DISA FSO','policy','The organization documents logical access restrictions associated with changes to the information system.','CM-5.6','The organization being inspected/assessed documents, in the configuration management policy, logical access restrictions associated with changes to the information system.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed documents logical access restrictions associated with changes to the information system.'),
('000344','draft','2009-09-18','DISA FSO','policy','The organization approves logical access restrictions associated with changes to the information system.','CM-5.7','The organization being inspected/assessed documents and implements a process to approve logical access restrictions associated with changes to the information system. The organization must maintain an audit trail of approvals.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of approvals to ensure the organization being inspected/assessed approves logical access restrictions associated with changes to the information system.'),
('000345','draft','2009-09-18','DISA FSO','policy','The organization enforces logical access restrictions associated with changes to the information system.','CM-5.8','The organization being inspected/assessed documents and implements a process to enforce logical access restrictions associated with changes to the information system. The information system must maintain an audit trail of logical access to the information system pertaining to information system changes.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the logical access audit trail to ensure the organization being inspected/assessed enforces logical access restrictions associated with changes to the information system as documented in the configuration management policy.'),
('000346','draft','2009-09-18','DISA FSO','technical','The organization employs automated mechanisms to enforce access restrictions.',NULL,NULL,NULL),
('000347','draft','2009-09-18','DISA FSO','technical','The organization employs automated mechanisms to support auditing of the enforcement actions.',NULL,NULL,NULL),
('000348','draft','2009-09-18','DISA FSO','policy','The organization defines a frequency with which to conduct reviews of information system changes.','CM-5(2).1','DoD has defined the frequency as every 90 days or more frequently as the organization defines for high systems AND at least annually or more frequently as the organization defines for low and moderate systems.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as every 90 days or more frequently as the organization defines for high systems AND at least annually or more frequently as the organization defines for low and moderate systems.'),
('000349','draft','2009-09-18','DISA FSO','policy','The organization reviews information system changes per organization-defined frequency to determine whether unauthorized changes have occurred.','CM-5(2).2','The organization being inspected/assessed documents in the configuration management policy and implements a process to review information system changes every 90 days or more frequently as the organization defines for high systems AND at least annually or more frequently as the organization defines for low and moderate systems to determine whether unauthorized changes have occurred.\n\nThe organization must maintain this review as an audit trail.\n\nDoD has defined the frequency as every 90 days or more frequently as the organization defines for high systems AND at least annually or more frequently as the organization defines for low and moderate systems.','The organization conducting the inspection/assessment obtains and examines the documented process for information system change review as well as the audit trail of reviews to ensure the organization being inspected/assessed reviews IS changes every 90 days or more frequently as the organization defines for high systems AND at least annually or more frequently as the organization defines for low and moderate systems to determine whether unauthorized changes have occurred.\n\nDoD has defined the frequency as every 90 days or more frequently as the organization defines for high systems AND at least annually or more frequently as the organization defines for low and moderate systems.'),
('000350','draft','2009-09-18','DISA FSO','policy','The organization reviews information system changes upon organization-defined circumstances to determine whether unauthorized changes have occurred.','CM-5(2).3','The organization being inspected/assessed documents and implements a process to review the information system changes when there is an incident or when planned changes have been performed to determine whether unauthorized changes have occurred.\n\nThe organization must maintain this review as an audit trail.\n\nDoD has defined the circumstances as when there is an incident or when planned changes have been performed.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reviews to ensure the organization being inspected/assessed reviews the information system changes when there is an incident or when planned changes have been performed to determine whether unauthorized changes have occurred.\n\nDoD has defined the circumstances as when there is an incident or when planned changes have been performed.'),
('000351','draft','2009-09-18','DISA FSO','policy','The organization defines critical software programs that the information system will prevent from being installed if such software programs are not signed with a recognized and approved certificate.',NULL,NULL,NULL),
('000352','draft','2009-09-18','DISA FSO','technical','The information system prevents the installation of organization-defined critical software programs that are not signed with a certificate that is recognized and approved by the organization.',NULL,NULL,NULL),
('000353','draft','2009-09-18','DISA FSO','policy','The organization defines information system components requiring enforcement of a dual authorization for information system changes.','CM-5(4).1','The organization being inspected/assessed defines and documents information system components requiring enforcement of a dual authorization for information system changes. DoD has determined to the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components requiring enforcement of a dual authorization for information system changes.\n\nDoD has determined to the information system components are not appropriate to define at the Enterprise level.'),
('000354','draft','2009-09-18','DISA FSO','policy','The organization enforces dual authorization for changes to organization-defined information system components.','CM-5(4).2','The organization being inspected/assessed documents and implements a process to enforce dual authorization for changes to information system components defined in CM-5 (4), CCI 353.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed enforces dual authorization for changes to information system components defined in CM-5 (4), CCI 353.'),
('000355','draft','2009-09-18','DISA FSO','policy','The organization limits information system developer/integrator privileges to change hardware components directly within a production environment.',NULL,NULL,NULL),
('000356','draft','2009-09-18','DISA FSO','policy','The organization limits information system developer/integrator privileges to change software components directly within a production environment.',NULL,NULL,NULL),
('000357','draft','2009-09-18','DISA FSO','policy','The organization limits information system developer/integrator privileges to change firmware components directly within a production environment.',NULL,NULL,NULL),
('000358','draft','2009-09-18','DISA FSO','policy','The organization limits information system developer/integrator privileges to change system information directly within a production environment.',NULL,NULL,NULL),
('000359','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency to review information system developer/integrator privileges.',NULL,NULL,NULL),
('000360','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency to reevaluate information system developer/integrator privileges.',NULL,NULL,NULL),
('000361','draft','2009-09-18','DISA FSO','policy','The organization reviews information system developer/integrator privileges per organization-defined frequency.',NULL,NULL,NULL),
('000362','draft','2009-09-18','DISA FSO','policy','The organization reevaluates information system developer/integrator privileges per organization-defined frequency.',NULL,NULL,NULL),
('000363','draft','2009-09-18','DISA FSO','policy','The organization defines security configuration checklists to be used to establish and document configuration settings for the information system technology products employed.','CM-6.1','DoD has defined the security configuration checklists as DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.). The organization being inspected/assessed documents in the security plan, the configuration guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) which apply to their information system components.','DoD has defined the security configuration checklists as DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.). The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed has documented the configuration guidance which apply to their information system components. The organization conducting the inspection/assessment reviews the list of documented guidance to ensure that all applicable guidance is identified given the information system components within the authorization boundary.'),
('000364','draft','2009-09-18','DISA FSO','policy','The organization establishes configuration settings for information technology products employed within the information system using organization-defined security configuration checklists.','CM-6.2','DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) meet the DoD requirement for establishing configuration settings.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.).','DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) meet the DoD requirement for establishing configuration settings.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.).'),
('000365','draft','2009-09-18','DISA FSO','policy','The organization documents configuration settings for information technology products employed within the information system using organization-defined security configuration checklists that reflect the most restrictive mode consistent with operational requirements.','CM-6.3','DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) meet the DoD requirement for documenting configuration settings.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.).','DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) meet the DoD requirement for documenting configuration settings.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.).'),
('000366','draft','2009-09-18','DISA FSO','policy','The organization implements the security configuration settings.','CM-6.5','The organization being inspected/assessed must develop and document a process for implementing DoD security configuration or implementation guidance (e.g. STIGs, NSA configuration guides, CTOs, DTMs etc.). DoD has defined the security configuration checklists as DoD security configuration or implementation guidance (e.g. STIGs, NSA configuration guides, CTOs, DTMs etc.).','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements DoD security configuration or implementation guidance (e.g. STIGs, NSA configuration guides, CTOs, DTMs etc.). The organization conducting the inspection/assessment tests a sampling of information system components to ensure they comply with the required settings. DoD has defined the security configuration checklists as DoD security configuration or implementation guidance (e.g. STIGs, NSA configuration guides, CTOs, DTMs etc.). '),
('000367','draft','2009-09-18','DISA FSO','policy','The organization identifies any deviations from the established configuration settings for organization-defined information system components based on organization-defined operational requirements.','CM-6.6','The organization being inspected/assessed documents in the security plan and POA&M, if applicable, the information system components as defined in CM-6, CCI 1755 which deviate from configuration settings, and which settings as defined in CM-6, CCI 1756.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed has documented deviations from configuration settings for information system components.'),
('000368','draft','2009-09-18','DISA FSO','policy','The organization documents any deviations from the established configuration settings for organization-defined information system components based on organization-defined operational requirements.','CM-6.7','The organization being inspected/assessed documents in the security plan and POA&M, if applicable, all configurable information system components which deviate from configuration settings, and which settings as defined in CM-6, CCI 1756.\n\nDoD has defined the information system components as all configurable information system components.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed has documented deviations from configuration settings for information system components.'),
('000369','draft','2009-09-18','DISA FSO','policy','The organization approves any deviations from the established configuration settings for organization-defined information system components based on organization-defined operational requirements.','CM-6.8','The organization being inspected/assessed manages and approves changes to the security plan documenting deviations IAW CM-3, CCI 314. The organization must maintain an audit trail of approved changes to the security plan.','The organization conducting the inspection/assessment obtains and examines the security plan and the audit trail of approved changes to ensure the deviations are approved IAW CM-3, CCI 314.'),
('000370','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to centrally manage configuration settings for organization-defined information system components.','CM-6(1).1','The organization being inspected/assessed identifies, documents in the configuration management policy, and implements automated mechanisms to centrally manage configuration settings.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed identifies automated mechanisms to centrally manage configuration settings. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000371','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to centrally apply configuration settings for organization-defined information system components.','CM-6(1).2','The organization being inspected/assessed identifies, documents in the configuration management policy, and implements automated mechanisms to centrally apply configuration settings.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed identifies automated mechanisms to centrally apply configuration settings. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000372','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to centrally verify configuration settings for organization-defined information system components.','CM-6(1).3','The organization being inspected/assessed identifies, documents in the configuration management policy, and implements automated mechanisms to centrally verify configuration settings.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed identifies automated mechanisms to centrally verify configuration settings. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('000373','draft','2009-09-18','DISA FSO','policy','The organization defines configuration settings for which unauthorized changes are responded to by automated mechanisms.',NULL,NULL,NULL),
('000374','draft','2009-09-18','DISA FSO','technical','The organization employs automated mechanisms to respond to unauthorized changes to organization-defined configuration settings.',NULL,NULL,NULL),
('000375','draft','2009-09-18','DISA FSO','policy','The organization incorporates detection of unauthorized, security-relevant configuration changes into the organizations incident response capability.',NULL,NULL,NULL),
('000376','draft','2009-09-18','DISA FSO','policy','The organization ensures unauthorized, security-relevant configuration changes detected are monitored.',NULL,NULL,NULL),
('000377','draft','2009-09-18','DISA FSO','policy','The organization ensures unauthorized, security-relevant configuration changes detected are corrected.',NULL,NULL,NULL),
('000378','draft','2009-09-18','DISA FSO','policy','The organization ensures unauthorized, security-relevant configuration changes detected are available for historical purposes.',NULL,NULL,NULL),
('000379','draft','2009-09-18','DISA FSO','policy','The information system (including modifications to the baseline configuration) demonstrates conformance to security configuration guidance (i.e., security checklists) prior to being introduced into a production environment.',NULL,NULL,NULL),
('000380','draft','2009-09-18','DISA FSO','policy','The organization defines prohibited or restricted functions, ports, protocols, and/or services for the information system.','CM-7.2','DoD has defined the information system prohibited or restricted functions, ports, protocols, and/or services as IAW DoDI 8551.01.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system prohibited or restricted functions, ports, protocols, and/or services as IAW DoDI 8551.01.'),
('000381','draft','2009-09-18','DISA FSO','technical','The organization configures the information system to provide only essential capabilities.','CM-7.1','The organization being inspected/assessed documents in the security plan, essential capabilities which the information system must provide. The organization being inspected/assessed configures the information system to provide only those documented essential capabilities.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed has identified essential capabilities. The organization conducting the inspection/assessment inspects the information system to ensure that it provides only those documented essential capabilities.'),
('000382','draft','2009-09-18','DISA FSO','technical','The organization configures the information system to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services.','CM-7.3','The organization being inspected/assessed configures the information system to prohibit or restrict the use of functions, ports, protocols, and/or services IAW DoDI 8551.01. DoD has defined the information system prohibited or restricted functions, ports, protocols, and/or services as IAW DoDI 8551.01.','The organization conducting the inspection/assessment inspects the information system to ensure the organization being inspected/assessed prohibits or restricts the use of functions, ports, protocols, and/or services IAW DoDI 8551.01. DoD has defined the information system prohibited or restricted functions, ports, protocols, and/or services as IAW DoDI 8551.01.'),
('000383','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency of information system reviews to identify and eliminate unnecessary functions, ports, protocols and/or services.',NULL,NULL,NULL),
('000384','draft','2009-09-18','DISA FSO','policy','The organization reviews the information system per organization-defined frequency to identify unnecessary and nonsecure functions, ports, protocols, and services.','CM-7(1).1','The organization being inspected/assessed documents and implements a process to review the information system every 30 days to identify unnecessary and nonsecure functions, ports, protocols, and services. The organization must maintain an audit trail of the reviews. DoD has defined the frequency as every 30 days.','The organization conducting the inspection/assessment obtains and examines the documented process and audit trail of reviews to ensure the organization being inspected/assessed reviews the information system every 30 days to identify unnecessary and nonsecure functions, ports, protocols, and services. DoD has defined the frequency as every 30 days.'),
('000385','draft','2009-09-18','DISA FSO','policy','The organization reviews the information system per organization-defined frequency to eliminate unnecessary functions, ports, protocols, and/or services.',NULL,NULL,NULL),
('000386','draft','2009-09-18','DISA FSO','technical','The organization employs automated mechanisms to prevent program execution on the information system in accordance with the organization-defined specifications.',NULL,NULL,NULL),
('000387','draft','2009-09-18','DISA FSO','policy','The organization defines registration requirements for functions, ports, protocols, and services.','CM-7(3).1','DoD has defined the registration requirements as IAW DoDI 8551.01.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the registration requirements as IAW DoDI 8551.01.'),
('000388','draft','2009-09-18','DISA FSO','policy','The organization ensures compliance with organization-defined registration requirements for functions, ports, protocols, and services.','CM-7(3).2','The organization being inspected/assessed implements DoDI 8551.01. DoD has defined the registration requirements as IAW DoDI 8551.01.','The organization conducting the inspection/assessment obtains and examines a documented listing of ports, protocols, and services in use, and reviews a sampling of those ports, protocols, and services to ensure the organization being inspected/assessed is compliant with DoDI 8551.01. DoD has defined the registration requirements as IAW DoDI 8551.01.'),
('000389','draft','2009-09-18','DISA FSO','policy','The organization develops an inventory of information system components that accurately reflects the current information system.','CM-8.1','The organization being inspected/assessed documents inventory of information system components that accurately reflects the current information system.','The organization conducting the inspection/assessment obtains and examines the documented inventory and examines a sampling of information system components to ensure inventory accurately reflects the current information system.'),
('000390','draft','2009-09-18','DISA FSO','policy','The organization documents an inventory of information system components that accurately reflects the current information system.',NULL,NULL,NULL),
('000391','draft','2009-09-18','DISA FSO','policy','The organization maintains an inventory of information system components that accurately reflects the current information system.',NULL,NULL,NULL),
('000392','draft','2009-09-18','DISA FSO','policy','The organization develops an inventory of information system components that includes all components within the authorization boundary of the information system.','CM-8.2','The organization being inspected/assessed documents inventory of information system components that includes all components within the authorization boundary of the information system.','The organization conducting the inspection/assessment obtains and examines the documented inventory and examines a sampling of information system components to ensure inventory includes all components within the authorization boundary of the information system.'),
('000393','draft','2009-09-18','DISA FSO','policy','The organization documents an inventory of information system components that includes all components within the authorization boundary of the information system.',NULL,NULL,NULL),
('000394','draft','2009-09-18','DISA FSO','policy','The organization maintains an inventory of information system components that is consistent with the authorization boundary of the information system.',NULL,NULL,NULL),
('000395','draft','2009-09-18','DISA FSO','policy','The organization develops an inventory of information system components that is at the level of granularity deemed necessary for tracking and reporting.','CM-8.3','The organization being inspected/assessed documents inventory of information system components that is at the level of granularity deemed necessary for tracking and reporting.','The organization conducting the inspection/assessment obtains and examines the documented inventory and examines a sampling of information system components to ensure inventory is at the level of granularity deemed necessary for tracking and reporting.'),
('000396','draft','2009-09-18','DISA FSO','policy','The organization documents an inventory of information system components that is at the level of granularity deemed necessary for tracking and reporting.',NULL,NULL,NULL),
('000397','draft','2009-09-18','DISA FSO','policy','The organization maintains an inventory of information system components that is at the level of granularity deemed necessary for tracking and reporting.',NULL,NULL,NULL),
('000398','draft','2009-09-18','DISA FSO','policy','The organization defines information deemed necessary to achieve effective information system component accountability.','CM-8.4','DoD has defined the information as hardware inventory specifications (manufacturer, type, model, serial number, physical location), software license information, information system/component owner, and for a networked component/device, the machine name.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information as hardware inventory specifications (manufacturer, type, model, serial number, physical location), software license information, information system/component owner, and for a networked component/device, the machine name.'),
('000399','draft','2009-09-18','DISA FSO','policy','The organization develops an inventory of information system components that includes organization-defined information deemed necessary to achieve effective information system component accountability.','CM-8.5','The organization being inspected/assessed documents inventory of information system components that includes organization defined information deemed necessary to achieve effective information system component accountability.','The organization conducting the inspection/assessment obtains and examines the documented inventory and examines a sampling of information system components to ensure inventory includes organization defined information deemed necessary to achieve effective information system component accountability.'),
('000400','draft','2009-09-18','DISA FSO','policy','The organization documents an inventory of information system components that includes organization-defined information deemed necessary to achieve effective information system component accountability.',NULL,NULL,NULL),
('000401','draft','2009-09-18','DISA FSO','policy','The organization maintains an inventory of information system components that includes organization-defined information deemed necessary to achieve effective property accountability.',NULL,NULL,NULL),
('000402','draft','2009-09-18','DISA FSO','policy','The organization develops an inventory of information system components that is available for review by designated organizational officials.',NULL,NULL,NULL),
('000403','draft','2009-09-18','DISA FSO','policy','The organization documents an inventory of information system components that is available for review by designated organizational officials.',NULL,NULL,NULL),
('000404','draft','2009-09-18','DISA FSO','policy','The organization maintains an inventory of information system components that is available for review by designated organizational officials.',NULL,NULL,NULL),
('000405','draft','2009-09-18','DISA FSO','policy','The organization develops an inventory of information system components that is available for audit by designated organizational officials.',NULL,NULL,NULL),
('000406','draft','2009-09-18','DISA FSO','policy','The organization documents an inventory of information system components that is available for audit by designated organizational officials.',NULL,NULL,NULL),
('000407','draft','2009-09-18','DISA FSO','policy','The organization maintains an inventory of information system components that is available for audit by designated organizational officials.',NULL,NULL,NULL),
('000408','draft','2009-09-18','DISA FSO','policy','The organization updates the inventory of information system components as an integral part of component installations.','CM-8(1).1','The organization being inspected/assessed documents and implements a process to update the inventory of information system components as an integral part of component installations. The organization must maintain an audit trail of updates. The audit trail may be recorded within the inventory itself.','The organization conducting the inspection/assessment obtains and examines the documented process for updates as well as the audit trail of updates and the log of changes to the information system to ensure the organization being inspected/assessed updates the inventory of information system components as an integral part of component installations.'),
('000409','draft','2009-09-18','DISA FSO','policy','The organization updates the inventory of information system components as an integral part of component removals.','CM-8(1).2','The organization being inspected/assessed documents and implements a process to update the inventory of information system components as an integral part of component removals. The organization must maintain an audit trail of updates. The audit trail may be recorded within the inventory itself.','The organization conducting the inspection/assessment obtains and examines the documented process for updates as well as the audit trail of updates and the log of changes to the information system to ensure the organization being inspected/assessed updates the inventory of information system components as an integral part of component removals.'),
('000410','draft','2009-09-18','DISA FSO','policy','The organization updates the inventory of information system components as an integral part of information system updates.','CM-8(1).3','The organization being inspected/assessed documents and implements a process to update the inventory of information system components as an integral part of information system updates. The organization must maintain an audit trail of updates. The audit trail may be recorded within the inventory itself.','The organization conducting the inspection/assessment obtains and examines the documented process for updates as well as the audit trail of updates and the log of changes to the information system to ensure the organization being inspected/assessed updates the inventory of information system components as an integral part of information system updates.'),
('000411','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to help maintain an up-to-date inventory of information system components.','CM-8(2).1','The organization being inspected/assessed documents and implements automated mechanisms to help maintain an up-to-date inventory of information system components. An automated mechanism implemented IAW CM-2 (2) satisfies the requirements of this CCI if the automated mechanism maintains an up-to-date inventory.','The organization conducting the inspection/assessment obtains and examines the documentation identifying the automated mechanism used to help maintain an up-to-date inventory of information system components and examines the mechanism to ensure the organization being inspected/assessed employs automated mechanisms to help maintain an up-to-date inventory of information system components.'),
('000412','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to help maintain a complete inventory of information system components.','CM-8(2).2','The organization being inspected/assessed documents and implements automated mechanisms to help maintain a complete inventory of information system components. An automated mechanism implemented IAW CM-2 (2) satisfies the requirements of this CCI if the automated mechanism maintains a complete inventory.','The organization conducting the inspection/assessment obtains and examines the documentation identifying the automated mechanism used to help maintain a complete inventory of information system components and examines the mechanism to ensure the organization being inspected/assessed employs automated mechanisms to help maintain a complete inventory of information system components.'),
('000413','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to help maintain an accurate inventory of information system components.','CM-8(2).3','The organization being inspected/assessed documents and implements automated mechanisms to help maintain an accurate inventory of information system components. An automated mechanism implemented IAW CM-2 (2) satisfies the requirements of this CCI if the automated mechanism maintains an accurate inventory.','The organization conducting the inspection/assessment obtains and examines the documentation identifying the automated mechanism used to help maintain an accurate inventory of information system components and examines the mechanism to ensure the organization being inspected/assessed employs automated mechanisms to help maintain an accurate inventory of information system components.'),
('000414','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to help maintain a readily available inventory of information system components.','CM-8(2).4','The organization being inspected/assessed documents and implements automated mechanisms to help maintain a readily available inventory of information system components. An automated mechanism implemented IAW CM-2 (2) satisfies the requirements of this CCI if the automated mechanism maintains a readily available inventory.','The organization conducting the inspection/assessment obtains and examines the documentation identifying the automated mechanism used to help maintain a readily available inventory of information system components and examines the mechanism to ensure the organization being inspected/assessed employs automated mechanisms to help maintain a readily available inventory of information system components.'),
('000415','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency of employing automated mechanisms to detect the presence of unauthorized hardware, software, and firmware components within the information system.','CM-8(3).1','DoD has defined the frequency as continuously.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as continuously.'),
('000416','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms, per organization-defined frequency, to detect the presence of unauthorized hardware, software, and firmware components within the information system.','CM-8(3).2','The organization being inspected/assessed documents and implements automated mechanisms to detect the presence of unauthorized hardware, software, and firmware components within the information system continuously. DoD has defined the frequency as continuously.','The organization conducting the inspection/assessment obtains and examines the documentation identifying the automated mechanisms and examines the implemented automated mechanisms to ensure the organization being inspected/assessed employs automated mechanisms, continuously, to detect the presence of unauthorized hardware, software, and firmware components within the information system. DoD has defined the frequency as continuously.'),
('000417','draft','2009-09-18','DISA FSO','technical','The organization disables network access by unauthorized components/devices or notifies designated organizational officials.',NULL,NULL,NULL),
('000418','draft','2009-09-18','DISA FSO','policy','The organization includes, in the information system component inventory information, a means for identifying by name, position, and/or role, individuals responsible/accountable for administering those components.','CM-8(4).1','The organization being inspected/assessed documents within their information system component inventory, the name and position or role of individuals responsible/accountable for administering those components or a means of identifying those individuals.','The organization conducting the inspection/assessment obtains and examines the information system component inventory to verify that the organization being inspected/assessed identifies within their inventory, the name and position or role of individuals responsible/accountable for administering those components or a means of identifying those individuals.'),
('000419','draft','2009-09-18','DISA FSO','policy','The organization verifies that all components within the authorization boundary of the information system are not duplicated in other information system component inventories.','CM-8(5).1','The organization being inspected/assessed verifies that all components within the authorization boundary of the information system are not duplicated in other information system inventories.','The organization conducting the inspection/assessment obtains and examines the inventory list of the authorized information system and verifies that all components identified during the inspection are not duplicated in other information system inventories.'),
('000420','draft','2009-09-18','DISA FSO','policy','The organization includes assessed component configurations and any approved deviations to current deployed configurations in the information system component inventory.','CM-8(6).1','The organization being inspected/assessed will institute procedures to ensure assessed component configurations, and any approved deviations to current deployed configurations, are included in the information system component inventory.','The organization conducting the inspection/assessment obtains and examines the organization\'s configuration management policy and plan; procedures addressing information system component inventory; information system design documentation; information system inventory records; information system component installation records; and any other relevant documents or records. The purpose of the reviews is to validate the organization is including assessed component configurations, and any approved deviations to deployed configurations, in the information system component\'s inventory.'),
('000421','draft','2009-09-18','DISA FSO','policy','The organization develops a configuration management plan for the information system that addresses roles, responsibilities, and configuration management processes and procedures.','CM-9.1','The organization being inspected/assessed will develop and document a configuration management plan for the information system that addresses roles, responsibilities, and configuration management processes and procedures.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to verify that it addresses and documents roles, responsibilities, and configuration management processes and procedures'),
('000422','draft','2009-09-18','DISA FSO','policy','The organization documents a configuration management plan for the information system that addresses roles, responsibilities, and configuration management processes and procedures.',NULL,NULL,NULL),
('000423','draft','2009-09-18','DISA FSO','policy','The organization implements a configuration management plan for the information system that addresses roles, responsibilities, and configuration management processes and procedures.','CM-9.2','The organization being inspected/assessed will implement a configuration management plan for the information system that addresses roles, responsibilities, and configuration management processes and procedures.','The organization conducting the inspection/assessment obtains and examines the configuration management plan as well as evidence of implementation (e.g., completed change requests, meeting minutes, and other relevant documents) to ensure the organization being inspected/assessed implements a configuration management plan for the information system that addresses roles, responsibilities, and configuration management processes and procedures.'),
('000424','draft','2009-09-18','DISA FSO','policy','The organization develops a configuration management plan for the information system that defines the configuration items for the information system.','CM-9.7','The organization being inspected/assessed will develop and document a configuration management plan for the information system that defines the configuration items.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to ensure it defines and documents the configuration items for the information system.'),
('000425','draft','2009-09-18','DISA FSO','policy','The organization documents a configuration management plan for the information system that defines the configuration items for the information system.',NULL,NULL,NULL),
('000426','draft','2009-09-18','DISA FSO','policy','The organization implements a configuration management plan for the information system that defines the configuration items for the information system.','CM-9.8','The organization being inspected/assessed will implement a configuration management plan for the information system that defines the configuration items.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to ensure the organization being inspected/assessed implements a configuration management plan for the information system that defines the configuration items.'),
('000427','draft','2009-09-18','DISA FSO','policy','The organization develops a configuration management plan for the information system when in the system development life cycle the configuration items are placed under configuration management.',NULL,NULL,NULL),
('000428','draft','2009-09-18','DISA FSO','policy','The organization documents a configuration management plan for the information system when in the system development life cycle the configuration items are placed under configuration management.',NULL,NULL,NULL),
('000429','draft','2009-09-18','DISA FSO','policy','The organization implements a configuration management plan for the information system when in the system development life cycle the configuration items are placed under configuration management.',NULL,NULL,NULL),
('000430','draft','2009-09-18','DISA FSO','policy','The organization develops a configuration management plan for the information system that establishes the means for identifying configuration items throughout the system development life cycle.',NULL,NULL,NULL),
('000431','draft','2009-09-18','DISA FSO','policy','The organization documents a configuration management plan for the information system that establishes the means for identifying configuration items throughout the system development life cycle.',NULL,NULL,NULL),
('000432','draft','2009-09-18','DISA FSO','policy','The organization implements a configuration management plan for the information system that establishes the means for identifying configuration items throughout the system development life cycle.',NULL,NULL,NULL),
('000433','draft','2009-09-18','DISA FSO','policy','The organization develops a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.',NULL,NULL,NULL),
('000434','draft','2009-09-18','DISA FSO','policy','The organization documents a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.',NULL,NULL,NULL),
('000435','draft','2009-09-18','DISA FSO','policy','The organization implements a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.',NULL,NULL,NULL),
('000436','draft','2009-09-18','DISA FSO','policy','The organization assigns responsibility for developing the configuration management process to organizational personnel that are not directly involved in information system development.','CM-9(1).1','The organization being inspected/assessed will assign responsibility for developing the configuration management process to organizational personnel that are not directly involved in information system development.','The organization conducting the inspection/assessment obtains and examines documentation of stakeholder role assignments to verify that the personnel assigned CM roles are not assigned roles for information system development.'),
('000437','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency with which to review and update the current contingency planning policy.','CP-1.7','DoD has defined the frequency as every 5 years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 5 years.'),
('000438','draft','2009-09-18','DISA FSO','policy','The organization develops and documents a contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','CP-1.1','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.'),
('000439','draft','2009-09-18','DISA FSO','policy','The organization disseminates a contingency planning policy to organization-defined personnel or roles.','CP-1.2','DoD disseminates DoDI 8500.01 organization-wide via the DoD Issuances website. http://www.dtic.mil/whs/directives/corres/dir.html NIST disseminates NIST SP 800-34 via http://csrc.nist.gov/publications/PubsSPs.html','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.'),
('000440','draft','2009-09-18','DISA FSO','policy','The organization reviews and updates the current contingency planning policy in accordance with an organization-defined frequency.','CP-1.8','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.'),
('000441','draft','2009-09-18','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls.','CP-1.4','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.'),
('000443','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that identifies essential missions.','CP-2.1','The organization being inspected/assessed must clearly and accurately document essential missions for its information system(s). Impact of loss of essential mission functions must be defined using CNSSI 1253.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents essential missions for its information system(s).'),
('000444','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that identifies essential business functions.','CP-2.2','The organization being inspected/assessed must clearly and accurately document essential business functions for its information system(s). Impact of loss of essential business functions must be defined using CNSSI 1253.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents essential business functions for its information system(s).'),
('000445','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that identifies associated contingency requirements.','CP-2.3','The organization being inspected/assessed must clearly and accurately document associated contingency requirements for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents associated contingency requirements for its information system(s).'),
('000446','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that provides recovery objectives.','CP-2.4','The organization being inspected/assessed must clearly and accurately document recovery objectives for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents recovery objectives for its information system(s).'),
('000447','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that provides restoration priorities.','CP-2.5','The organization being inspected/assessed must clearly and accurately document restoration priorities for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents restoration priorities for its information system(s).'),
('000448','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that provides metrics.','CP-2.6','The organization being inspected/assessed must clearly and accurately document metrics for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents metrics for its information system(s).'),
('000449','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses contingency roles, responsibilities, assigned individuals with contact information.','CP-2.7','The organization being inspected/assessed must clearly and accurately document contingency roles, responsibilities, assigned individuals with contact information for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents contingency roles, responsibilities, assigned individuals with contact information for its information system(s).'),
('000450','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses maintaining essential missions despite an information system disruption.','CP-2.8','The organization being inspected/assessed must clearly and accurately document maintaining essential missions despite an information system disruption for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining essential missions despite an information system disruption for its information system(s).'),
('000451','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses maintaining essential business functions despite an information system disruption.','CP-2.9','The organization being inspected/assessed must clearly and accurately document maintaining business functions despite an information system disruption for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining business functions despite an information system disruption for its information system(s).'),
('000452','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses maintaining essential missions despite an information system compromise.','CP-2.10','The organization being inspected/assessed must clearly and accurately document maintaining essential missions despite an information system compromise for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining essential missions despite an information system compromise for its information system(s).'),
('000453','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses maintaining essential business functions despite an information system compromise.','CP-2.11','The organization being inspected/assessed must clearly and accurately document maintaining business functions despite an information system compromise for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining business functions despite an information system compromise for its information system(s).'),
('000454','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses maintaining essential missions despite an information system failure.','CP-2.12','The organization being inspected/assessed must clearly and accurately document maintaining essential missions despite an information system failure for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining essential missions despite an information system failure for its information system(s).'),
('000455','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses maintaining essential business functions despite an information system failure.','CP-2.13','The organization being inspected/assessed must clearly and accurately document maintaining business functions despite an information system failure for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining business functions despite an information system failure for its information system(s).'),
('000456','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that addresses eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented.','CP-2.14','The organization being inspected/assessed must clearly and accurately document eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented for its information system(s).','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents eventual, full information system restoration without deterioration of the security safeguards originally planned and implemented for its information system(s).'),
('000457','draft','2009-09-18','DISA FSO','policy','The organization develops a contingency plan for the information system that is reviewed and approved by organization-defined personnel or roles.','CP-2.15','The organization being inspected/assessed reviews and approves the contingency plan by at a minimum, the ISSM and ISSO. The organization must maintain an audit trail of the review and approval activity. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.','The organization conducting the inspection/assessment obtains and examines the audit trail to ensure the contingency plan has been reviewed and approved by at a minimum, the ISSM and ISSO. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.'),
('000458','draft','2009-09-18','DISA FSO','policy','The organization defines a list of key contingency personnel (identified by name and/or by role) and organizational elements designated to receive copies of the contingency plan.','CP-2.17','DoD has defined the list as all stakeholders identified in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the list as all stakeholders identified in the contingency plan.'),
('000459','draft','2009-09-18','DISA FSO','policy','The organization distributes copies of the contingency plan to an organization-defined list of key contingency personnel (identified by name and/or by role) and organizational elements.','CP-2.18','The organization being inspected/assessed ensures the contingency plan is disseminated to all stakeholders identified in the contingency plan via an information sharing capability.\n\nDoD has defined the list as all stakeholders identified in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the contingency plan via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated. '),
('000460','draft','2009-09-18','DISA FSO','policy','The organization coordinates contingency planning activities with incident handling activities.','CP-2.19','The organization being inspected/assessed will coordinate the contingency plan and incident response plan (IR-8) to ensure they do not contradict each other\'s objectives or result in duplicate efforts/activities.','The organization conducting the inspection/assessment obtains and examines the contingency plan and the incident response plan (IR-8) to ensure they do not contradict each other\'s objectives or result in duplicate efforts/activities.'),
('000461','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency with which to review the contingency plan for the information system.','CP-2.20','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000462','draft','2009-09-18','DISA FSO','policy','The organization reviews the contingency plan for the information system in accordance with organization-defined frequency.','CP-2.21','The organization being inspected/assessed annually reviews the contingency plan. The organization must maintain an audit trail of annual reviews.','The organization conducting the inspection/assessment obtains and examines the audit trail to ensure the contingency plan is reviewed annually.'),
('000463','draft','2009-09-18','DISA FSO','policy','The organization updates the contingency plan to address changes to the organization.','CP-2.22','The organization being inspected/assessed must clearly and accurately update the contingency plan to address organizational changes. The organization must document the update activities as an audit trail.','The organization conducting the inspection/assessment obtains and examines the contingency plan and audit trail to ensure the organization clearly and accurately updates the contingency plan to address organizational changes.'),
('000464','draft','2009-09-18','DISA FSO','policy','The organization updates the contingency plan to address changes to the information system.','CP-2.23','The organization being inspected/assessed must clearly and accurately update the contingency plan to address changes to the information system. The organization must document the update activities as an audit trail.','The organization conducting the inspection/assessment obtains and examines the contingency plan and audit trail to ensure the organization clearly and accurately updates the contingency plan to address information system changes.'),
('000465','draft','2009-09-18','DISA FSO','policy','The organization updates the contingency plan to address changes to the environment of operation.','CP-2.24','The organization being inspected/assessed must clearly and accurately revise the contingency plan to address changes to the environment of operation. The organization must document the update activities as an audit trail.','The organization conducting the inspection/assessment obtains and examines the contingency plan and audit trail to ensure the organization clearly and accurately revises the contingency plan to address changes to the environment of operation.'),
('000466','draft','2009-09-18','DISA FSO','policy','The organization updates the contingency plan to address problems encountered during contingency plan implementation, execution, or testing.','CP-2.25','The organization being inspected/assessed must clearly and accurately revise the contingency plan to address problems encountered during contingency plan implementation, execution, or testing. The organization must document the update activities as an audit trail.','The organization conducting the inspection/assessment obtains and examines the contingency plan and audit trail to ensure the organization clearly and accurately revises the contingency plan to address problems encountered during contingency plan implementation, execution, or testing.'),
('000468','draft','2009-09-18','DISA FSO','policy','The organization communicates contingency plan changes to an organization-defined list of key contingency personnel (identified by name and/or by role) and organizational elements.','CP-2.26','The organization being inspected/assessed communicates contingency plan changes to all stakeholders identified in the contingency plan. DoD has defined the list as all stakeholders identified in the contingency plan. ','The organization conducting the inspection/assessment examines the contingency plan via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure the most current version has been communicated.'),
('000469','draft','2009-09-18','DISA FSO','policy','The organization coordinates contingency plan development with organizational elements responsible for related plans.','CP-2(1).1','The organization being inspected/assessed coordinates the development of its contingency plan with other organizational elements responsible for related plans. The organization documents any applicable agreements with responsible internal or external entities. For external entities the agreements could entail MOUs, MOAs, SLAs or contracts.','The organization conducting the inspection/assessment obtains and examines documentation of agreements with entities responsible for the contingency or related plans to ensure there is evidence of coordination of those plans.'),
('000470','draft','2009-09-18','DISA FSO','policy','The organization conducts capacity planning so that necessary capacity for information processing exists during contingency operations.','CP-2(2).1','The organization being inspected/assessed must conduct and document capacity planning to ensure that necessary capacity for information processing exists during contingency operations.','The organization conducting the inspection/assessment obtains and examines the documented capacity planning to ensure that the organization has performed capacity planning.'),
('000471','draft','2009-09-18','DISA FSO','policy','The organization conducts capacity planning so that necessary capacity for telecommunications exists during contingency operations.','CP-2(2).2','The organization being inspected/assessed must conduct and document capacity planning to ensure that necessary capacity for telecommunications exists during contingency operations.','The organization conducting the inspection/assessment obtains and examines the documented capacity planning to ensure that the organization has performed capacity planning.'),
('000472','draft','2009-09-18','DISA FSO','policy','The organization conducts capacity planning so that necessary capacity for environmental support exists during contingency operations.','CP-2(2).3','The organization being inspected/assessed must conduct and document capacity planning to ensure that necessary capacity for environmental support exists during contingency operations.','The organization conducting the inspection/assessment obtains and examines the documented capacity planning to ensure that the organization has performed capacity planning.'),
('000473','draft','2009-09-18','DISA FSO','policy','The organization defines the time period for planning the resumption of essential missions as a result of contingency plan activation.','CP-2(3).1','DoD has defined the time period as 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000474','draft','2009-09-18','DISA FSO','policy','The organization defines the time period for planning the resumption of essential business functions as a result of contingency plan activation.','CP-2(3).2','DoD has defined the time period as 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000475','draft','2009-09-18','DISA FSO','policy','The organization plans for the resumption of essential missions within the organization-defined time period of contingency plan activation.','CP-2(3).3','The organization being inspected/assessed shall document within their contingency plan, procedures for resumption of essential missions within 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains the contingency plan to ensure it contains procedures for resumption of essential missions within 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000476','draft','2009-09-18','DISA FSO','policy','The organization plans for the resumption of essential business functions within the organization-defined time period of contingency plan activation.','CP-2(3).4','The organization being inspected/assessed shall document within their contingency plan, procedures for resumption of essential business functions within 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains the contingency plan to ensure it contains procedures for resumption of essential business functions within 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000477','draft','2009-09-18','DISA FSO','policy','The organization defines the time period for planning the resumption of all missions as a result of contingency plan activation.','CP-2(4).1','DoD has defined the time period as 1 hour (Availability High ) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.'),
('000478','draft','2009-09-18','DISA FSO','policy','The organization defines the time period for planning the resumption of all business functions as a result of contingency plan activation.','CP-2(4).2','DoD has defined the time period as 1 hour (Availability High ) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.'),
('000479','draft','2009-09-18','DISA FSO','policy','The organization plans for the resumption of all missions within an organization-defined time period of contingency plan activation.','CP-2(4).3','The organization being inspected/assessed shall document within their contingency plan, procedures for full resumption of affected missions within 1 hour (Availability High ) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains the contingency plan to ensure it contains procedures for full resumption of affected missions within 1 hour (Availability High ) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.'),
('000480','draft','2009-09-18','DISA FSO','policy','The organization plans for the resumption of all business functions within an organization-defined time period of contingency plan activation.','CP-2(4).4','The organization being inspected/assessed shall document within their contingency plan, procedures for full resumption of affected business functions within 1 hour (Availability High) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains the contingency plan to ensure it contains procedures for full resumption of affected business functions within 1 hour (Availability High) 1-5 days (Availability Moderate) 5-30 days (Availability Low) as defined in the contingency plan.'),
('000481','draft','2009-09-18','DISA FSO','policy','The organization plans for the continuance of essential missions with little or no loss of operational continuity.','CP-2(5).1','The organization being inspected/assessed plans for the continuance of essential missions with little or no loss of operational continuity IAW CP-2a.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining essential missions despite an information system disruption for its information system(s).'),
('000482','draft','2009-09-18','DISA FSO','policy','The organization plans for the continuance of essential business functions with little or no loss of operational continuity.','CP-2(5).2','The organization being inspected/assessed plans for the continuance of essential business functions with little or no loss of operational continuity IAW CP-2a.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it clearly and accurately documents maintaining essential business functions despite an information system disruption for its information system(s).'),
('000483','draft','2009-09-18','DISA FSO','policy','The organization plans for the transfer of essential missions to alternate processing and/or storage sites with little or no loss of operational continuity.','CP-2(6).1','The organization being inspected/assessed documents within their continuity plan, a process to transfer essential missions to alternate processing and/or storage sites with little or no loss of operational continuity.','The organization conducting the inspection/assessment obtains and examines the continuity plan to ensure the organization being inspected/assessed documents a process to transfer essential missions to alternate processing and/or storage sites with little or no loss of operational continuity.'),
('000484','draft','2009-09-18','DISA FSO','policy','The organization plans for the transfer of essential business functions to alternate processing and/or storage sites with little or no loss of operational continuity.','CP-2(6).2','The organization being inspected/assessed documents within their continuity plan, a process to transfer essential business functions to alternate processing and/or storage sites with little or no loss of operational continuity.','The organization conducting the inspection/assessment obtains and examines the continuity plan to ensure the organization being inspected/assessed documents a process to transfer essential business functions to alternate processing and/or storage sites with little or no loss of operational continuity.'),
('000485','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of refresher contingency training to information system users.','CP-3.4','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually'),
('000486','draft','2009-09-21','DISA FSO','policy','The organization provides contingency training to information system users consistent with assigned roles and responsibilities within an organization-defined time period of assuming a contingency role or responsibility.','CP-3.1','The organization being inspected/assessed provides initial contingency training to personnel with contingency roles and responsibilities IAW CP-2, CCI 449 at a maximum, 10 working days of assuming a contingency role or responsibility.\n\nThe organization will maintain documentation of the training activity dates, location, and personnel for audit trail purposes and future reference (e.g., scheduling refresher training, etc.).\n\nDoD has defined the time period as at a maximum, 10 working days.','The organization conducting the inspection/assessment obtains and examines the list of contingency personnel and documentation of initial contingency training for the purpose of ensuring that all personnel with contingency roles and responsibilities have received initial contingency training at a maximum, 10 working days of assuming a contingency role or responsibility. DoD has defined the time period as at a maximum, 10 working days. '),
('000487','draft','2009-09-21','DISA FSO','policy','The organization provides refresher contingency training to information system users consistent with assigned roles and responsibilities in accordance with organization-defined frequency.','CP-3.5','The organization being inspected/assessed provides refresher contingency training to personnel with contingency roles and responsibilities IAW CP-2, CCI 449 at least annually. The organization will maintain documentation of the training activity dates, location, and personnel for audit trail purposes and future reference (e.g., scheduling refresher training, etc.). DoD has defined the frequency as at least annually.','The organization conducting the inspection/assessment obtains and examines the list of contingency personnel and documentation of refresher contingency training for the purpose of ensuring that all personnel with contingency roles and responsibilities have received refresher contingency training at least annually. DoD has defined the frequency as at least annually.'),
('000488','draft','2009-09-21','DISA FSO','policy','The organization incorporates simulated events into contingency training to facilitate effective response by personnel in crisis situations.','CP-3(1).1','The organization being inspected/assessed will include simulated events into contingency training to facilitate effective response by personnel in crisis situations.','The organization conducting the inspection/assessment obtains and examines contingency training materials to ensure that simulated events have been included.'),
('000489','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to provide a more thorough and realistic contingency training environment.','CP-3(2).1','The organization being inspected/assessed employs an automated mechanism such as scenario-based interactive online training/CBT providing a realistic contingency training environment.','The organization conducting the inspection/assessment obtains and examines the automated mechanism such as scenario-based interactive online training/CBT to verify that it provides a realistic contingency training environment.'),
('000490','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to test the contingency plan for the information system.','CP-4.1','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually.'),
('000491','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency to exercise the contingency plan for the information system.',NULL,NULL,NULL),
('000492','draft','2009-09-21','DISA FSO','policy','The organization defines contingency plan tests to be conducted for the information system.','CP-4.2','The organization being inspected/assessed defines and documents contingency plan tests to be conducted for the information system. DoD has determined the contingency plan tests are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented contingency plan tests to ensure the organization being inspected/assessed defines contingency plan tests to be conducted for the information system. DoD has determined the contingency plan tests are not appropriate to define at the Enterprise level.'),
('000493','draft','2009-09-21','DISA FSO','policy','The organization defines contingency plan exercises to be conducted for the information system.',NULL,NULL,NULL),
('000494','draft','2009-09-21','DISA FSO','policy','The organization tests the contingency plan for the information system in accordance with organization-defined frequency using organization-defined tests to determine the effectiveness of the plan and the organizational readiness to execute the plan.','CP-4.3','The organization being inspected/assessed conduct tests defined in CP-4, 492 at least annually to determine the effectiveness of the plan and the organizational readiness to execute the plan. The organization must maintain a record of test results. DoD has defined the frequency as at least annually.','The organization conducting the inspection/assessment obtains and examines the record of test results to ensure the organization being inspected/assessed conduct tests defined in CP-4, 492 at least annually to determine the effectiveness of the plan and the organizational readiness to execute the plan. DoD has defined the frequency as at least annually.'),
('000495','draft','2009-09-21','DISA FSO','policy','The organization exercises the contingency plan using organization-defined exercises in accordance with organization-defined frequency.',NULL,NULL,NULL),
('000496','draft','2009-09-21','DISA FSO','policy','The organization reviews the contingency plan test results.','CP-4.4','The organization being inspected/assessed will review the contingency plan test results. The organization must maintain an audit trail of issues identified during the reviews of the contingency plan test results.','The organization conducting the inspection/assessment obtains and examines the audit trail of issues identified during the reviews of the contingency plan test results to ensure the organization being inspected/assessed reviews the contingency plan test results.'),
('000497','draft','2009-09-21','DISA FSO','policy','The organization initiates corrective actions, if needed, after reviewing the contingency plan test results.','CP-4.5','The organization being inspected/assessed identifies and documents any corrective actions required after reviewing the contingency plan test results. The organization initiates corrective actions and tracks those actions within the POA&M.','The organization conducting the inspection/assessment obtains and examines the contingency plan test results as well as any documented corrective actions required and ensures the corrective actions are being implemented and tracked within the POA&M.'),
('000498','draft','2009-09-21','DISA FSO','policy','The organization coordinates contingency plan testing with organizational elements responsible for related plans.','CP-4(1).1','The organization being inspected/assessed coordinates the testing of its contingency plan with other organizational elements responsible for related plans. The organization documents any applicable agreements with responsible internal or external entities. For external entities the agreements could entail MOUs, MOAs, SLAs or contracts.','The organization conducting the inspection/assessment obtains and examines documentation of agreements with entities responsible for the contingency or related plans to ensure there is evidence of coordination of those tests.'),
('000499','draft','2009-09-21','DISA FSO','policy','The organization coordinates contingency plan exercises with organizational elements responsible for related plans.',NULL,NULL,NULL),
('000500','draft','2009-09-21','DISA FSO','policy','The organization tests the contingency plan at the alternate processing site to familiarize contingency personnel with the facility and available resources.','CP-4(2).1','The organization being inspected/assessed will include personnel expected to implement the contingency plan at the alternate site in the testing at the alternate site to familiarize contingency personnel with the facility and available resources. The organization must maintain a record of personnel who participated in the contingency plan testing at the alternate site.','The organization conducting the inspection/assessment obtains and examines the record of personnel who participated in the contingency plan testing at the alternate site to ensure the organization being inspected/assessed tests the contingency plan at the alternate processing site to familiarize personnel expected to implement the contingency plan at the alternate site with the facility and available resources.'),
('000501','draft','2009-09-21','DISA FSO','policy','The organization exercises the contingency plan at the alternate processing site to familiarize contingency personnel with the facility and available resources and to evaluate the site^s capabilities to support contingency operations.',NULL,NULL,NULL),
('000502','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to more thoroughly and effectively test the contingency plan.','CP-4(3).1','The organization being inspected/assessed will identify and employ automated mechanisms to thoroughly test the contingency plan, for example by providing more complete coverage of contingency issues, selecting more realistic test scenarios and environments, and more effectively stressing the information system and supported missions.','The organization conducting the inspection/assessment obtains and examines the identified automated mechanisms in use to thoroughly test the contingency plan.'),
('000503','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to more thoroughly and effectively exercise the contingency plan by providing more complete coverage of contingency issues, selecting more realistic exercise scenarios and environments, and more effectively stressing the information and supported missions.',NULL,NULL,NULL),
('000504','draft','2009-09-21','DISA FSO','policy','The organization includes a full recovery and reconstitution of the information system to a known state as part of contingency plan testing.','CP-4(4).1','The organization being inspected/assessed demonstrates full recovery and reconstitution of its information system to a known state as part of its contingency plan testing. The organization documents full recovery and reconstitution as part of its contingency plan testing results.','The organization conducting the inspection/assessment obtains and examines the full recovery and reconstitution procedures and contingency plan testing results to ensure all tests were performed IAW CP-2, CCIs 446 and 447.'),
('000505','draft','2009-09-21','DISA FSO','policy','The organization establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information.','CP-6.1','The organization being inspected/assessed establishes an alternate storage site and documents relevant information within the contingency plan.','The organization conducting the inspection/assessment obtains and examines the contingency plan to confirm the organization has established an alternate storage site.'),
('000506','draft','2009-09-21','DISA FSO','policy','The organization initiates necessary alternate storage site agreements to permit the storage and recovery of information system backup information.',NULL,NULL,NULL),
('000507','draft','2009-09-21','DISA FSO','policy','The organization identifies an alternate storage site that is separated from the primary storage site to reduce susceptibility to the same threats.','CP-6(1).1','The organization being inspected/assessed identifies and documents within the contingency plan an alternate storage site not susceptible to the same threats that exist at the primary storage site. The organization must document threats in the risk management strategy IAW PM-9, CCI 000227.','The organization conducting the inspection/assessment obtains and examines the risk management strategy and the contingency plan to ensure the organization identifies an alternate storage site that is separated from the primary storage site so as not to be susceptible to the same threats identified at the primary site.'),
('000508','draft','2009-09-21','DISA FSO','policy','The organization configures the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives.','CP-6(2).1','The organization being inspected/assessed configures the alternate storage site to facilitate recovery operations IAW CP-2, CCIs 446 and 447.','The organization conducting the inspection/assessment obtains and examines the contingency plan and conducts a walk-through of the alternate storage site to ensure the organization\'s documented recovery time and recovery point objectives have been met.'),
('000509','draft','2009-09-21','DISA FSO','policy','The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster.','CP-6(3).1','The organization being inspected/assessed must identify and document in the contingency plan potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure the organization has documented potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster.'),
('000510','draft','2009-09-21','DISA FSO','policy','The organization defines the time period consistent with recovery time and recovery point objectives for essential missions/business functions to permit the transfer and resumption of organization-defined information system operations at an alternate processing site when the primary processing capabilities are unavailable.','CP-7.1','DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan'),
('000511','draft','2009-09-21','DISA FSO','policy','The organization defines the time period for achieving the recovery time objectives for business functions within which processing must be resumed at the alternate processing site.',NULL,NULL,NULL),
('000512','draft','2009-09-21','DISA FSO','policy','The organization establishes an alternate processing site.',NULL,NULL,NULL),
('000513','draft','2009-09-21','DISA FSO','policy','The organization establishes an alternate processing site including necessary agreements to permit the transfer and resumption of organization-defined information system operations for essential missions within an organization-defined time period consistent with recovery time and recovery point objectives when the primary processing capabilities are unavailable.','CP-7.2','The organization being inspected/assessed documents and gains approval for alternate processing site agreements that permit the transfer and resumption of information system operations for essential missions within 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the approved alternate processing site agreements to ensure the organization has alternate processing site support that will permit the transfer and resumption of information system operations for essential missions within 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000514','draft','2009-09-21','DISA FSO','policy','The organization establishes an alternate processing site including necessary agreements to permit the transfer and resumption of organization-defined information system operations for essential business functions within an organization-defined time period consistent with recovery time and recovery point objectives when the primary processing capabilities are unavailable.','CP-7.3','The organization being inspected/assessed documents and gains approval for alternate processing site agreements that permit the transfer and resumption of information system operations for business functions within 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the approved alternate processing site agreements to ensure the organization has alternate processing site support that will permit the transfer and resumption of information system operations for business functions within 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000515','draft','2009-09-21','DISA FSO','policy','The organization ensures that equipment and supplies required to transfer and resume operations are available at the alternate processing site or contracts are in place to support delivery to the site within the organization-defined time period for transfer/resumption.','CP-7.5','The organization being inspected/assessed maintains an inventory of equipment and supplies required to transfer and resume operations, or engages contract support that meets required timelines to support 1 hour (Availability High) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines:\n1. Inventory of equipment and supplies or,\n2. Contract documentation\nto ensure the organization has the equipment and supply resources necessary, or provisions to obtain the resources to transfer and resume operations at the alternate processing site within 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000516','draft','2009-09-21','DISA FSO','policy','The organization identifies an alternate processing site that is separated from the primary processing site to reduce susceptibility to the same threats.','CP-7(1).1','The organization being inspected/assessed identifies and documents within the contingency plan an alternate processing site not susceptible to the same threats that exist at the primary processing site. The organization must document threats in the risk management strategy IAW PM-9, CCI 000227.','The organization conducting the inspection/assessment obtains and examines the risk management strategy and the contingency plan to ensure the organization identifies an alternate processing site that is separated from the primary processing site so as not to be susceptible to the same threats identified at the primary site.'),
('000517','draft','2009-09-21','DISA FSO','policy','The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster.','CP-7(2).1','The organization being inspected/assessed must identify and document in the contingency plan potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure the organization has documented potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster.'),
('000518','draft','2009-09-21','DISA FSO','policy','The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with the organizational availability requirements (including recovery time objectives).','CP-7(3).1','The organization being inspected/assessed documents and gains approval for alternate processing site agreements that contain priority-of-service provisions in accordance with CP-2, CCI 447 (including recovery time objectives).','The organization conducting the inspection/assessment obtains and examines the approved alternate processing site agreements to ensure they contain priority-of-service provisions in accordance with CP-2, CCI 447 for alternate processing site support (including recovery time objectives).'),
('000519','draft','2009-09-21','DISA FSO','policy','The organization prepares the alternate processing site so that it is ready to be used as the operational site supporting essential missions.','CP-7(4).1','The organization being inspected/assessed prepares the alternate processing site so that it is ready to be used as the operational site supporting essential missions IAW CP-2, CCI 443.','The organization conducting the inspection/assessment obtains and examines the contingency plan and conducts a walk-through of the alternate processing site to ensure it is ready to be used as the operational site supporting essential missions.'),
('000520','draft','2009-09-21','DISA FSO','policy','The organization prepares the alternate processing site so that it is ready to be used as the operational site supporting essential business functions.','CP-7(4).2','The organization being inspected/assessed prepares the alternate processing site so that it is ready to be used as the operational site supporting business functions IAW CP-2, CCI 444.','The organization conducting the inspection/assessment obtains and examines the contingency plan and conducts a walk-through of the alternate processing site to ensure it is ready to be used as the operational site supporting business functions.'),
('000521','draft','2009-09-21','DISA FSO','policy','The organization ensures that the alternate processing site provides information security safeguards equivalent to that of the primary site.','CP-7.6','The organization being inspected/assessed documents the information security safeguards that are in place at both the primary and alternate sites and evidence that the alternate site was approved based on an assessment that security is equivalent at the alternate site.','The organization conducting the inspection/assessment obtains and examines the documentation of the primary/alternate site information security safeguards that are in place as well as evidence that the alternate site was approved based on an assessment that security is equivalent at the alternate site.'),
('000522','draft','2009-09-21','DISA FSO','policy','The organization defines the time period within which to permit the resumption of organization-defined information system operations for essential missions when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-8.1','DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000523','draft','2009-09-21','DISA FSO','policy','The organization defines the time period within which to permit the resumption of organization-defined information system operations for essential business functions when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-8.2','DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000524','draft','2009-09-21','DISA FSO','policy','The organization establishes alternate telecommunication services including necessary agreements to permit the resumption of organization-defined information system operations for essential missions within an organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-8.3','The organization being inspected/assessed documents and gains approval for alternate telecommunications service agreements that permit the resumption of telecommunications services for essential missions IAW DoDI 8100.04. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the approved alternate telecommunications service agreements to ensure they permit the resumption of telecommunications services for essential mission IAW DoDI 8100.04. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000525','draft','2009-09-21','DISA FSO','policy','The organization establishes alternate telecommunication services including necessary agreements to permit the resumption of organization-defined information system operations for essential business functions within an organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-8.4','The organization being inspected/assessed documents and gains approval for alternate telecommunications service agreements that permit the resumption of telecommunications services for business functions IAW DoDI 8100.04. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the approved alternate telecommunications service agreements to ensure they permit the resumption of telecommunications services for business functions IAW DoDI 8100.04. DoD has defined the time period as 1 hour (Availability High ) 12 hours (Availability Moderate) as defined in the contingency plan.'),
('000526','draft','2009-09-21','DISA FSO','policy','The organization develops primary telecommunications service agreements that contain priority-of-service provisions in accordance with the organization^s availability requirements (including recovery time objectives).','CP-8(1).1','The organization being inspected/assessed documents and gains approval for primary telecommunications service agreements that contain priority-of-service provisions IAW DoDI 8100.04 (including recovery time objectives).','The organization conducting the inspection/assessment obtains and examines the approved primary telecommunications service agreements to ensure they contain priority-of-service provisions IAW DoDI 8100.04 (including recovery time objectives).'),
('000527','draft','2009-09-21','DISA FSO','policy','The organization develops alternate telecommunications service agreements that contain priority-of-service provisions in accordance with the organization^s availability requirements (including recovery time objectives).','CP-8(1).2','The organization being inspected/assessed documents and gains approval for alternate telecommunications service agreements that contain priority-of-service provisions IAW DoDI 8100.04 (including recovery time objectives).','The organization conducting the inspection/assessment obtains and examines the approved alternate telecommunications service agreements to ensure they contain priority-of-service provisions IAW DoDI 8100.04 (including recovery time objectives).'),
('000528','draft','2009-09-21','DISA FSO','policy','The organization requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary telecommunications services are provided by a common carrier.','CP-8(1).3','The organization being inspected/assessed identifies and documents within the contingency plan any telecommunications services used for national security emergency preparedness. If the primary telecommunications services are provided by a common carrier, the organization formally requests Telecommunications Service Priority IAW the DHS Telecommunications Service Priority Process http://www.dhs.gov/telecommunications-service-priority-tsp. If the primary telecommunications services are provided by a mid-tier provider instead of a common carrier (for example, DISA) the organization must insure that their provider formally requests Telecommunications Service Priority on their behalf.','The organization conducting the inspection/assessment obtains and examines the contingency plan, the telecommunication service agreement, and any existing formal requests for Telecommunications Service Priority.\n\nThe purpose of the review is to ensure the organization or the mid-tier provider has requested Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness where the primary telecommunications services are provided by a common carrier.'),
('000529','draft','2009-09-21','DISA FSO','policy','The organization requests Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the alternate telecommunications services are provided by a common carrier.','CP-8(1).4','The organization being inspected/assessed identifies and documents within the contingency plan telecommunications services used for national security emergency preparedness in the event the alternate telecommunications services are provided by a common carrier. For each service, the organization formally requests Telecommunications Service Priority, IAW the DHS Telecommunications Service Priority Process http://tsp.ncs.gov/request.html.','The organization conducting the inspection/assessment obtains and examines the contingency plan, the telecommunication service agreement, and any existing formal requests for Telecommunications Service Priority. The purpose of the review is to ensure the organization has requested Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event the alternate telecommunications services are provided by a common carrier.'),
('000530','draft','2009-09-21','DISA FSO','policy','The organization obtains alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services.','CP-8(2).1','The organization being inspected/assessed obtains alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services IAW DoDI 8100.04.','The organization conducting the inspection/assessment obtains and examines agreements with their service providers to ensure that a single point of failure is not shared.'),
('000531','draft','2009-09-21','DISA FSO','policy','The organization obtains alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats.','CP-8(3).1','The organization being inspected/assessed obtains alternate telecommunications services from providers that are separated from primary service providers so as not to be susceptible to the same hazards IAW DoDI 8100.04.','The organization conducting the inspection/assessment obtains and examines agreements with alternate service providers to ensure they are not susceptible to the same hazards as the primary service provider.'),
('000532','draft','2009-09-21','DISA FSO','policy','The organization requires primary telecommunications service providers to have contingency plans.','CP-8(4).1','The organization being inspected/assessed includes in their primary telecommunications service provider agreements requirements for the primary service provider to have contingency plans.','The organization conducting the inspection/assessment obtains and examines the primary telecommunications service provider agreements to ensure the organization requires the primary service provider to have contingency plans.'),
('000533','draft','2009-09-21','DISA FSO','policy','The organization requires alternate telecommunications service providers to have contingency plans.','CP-8(4).2','The organization being inspected/assessed includes in their alternate telecommunications service provider agreements requirements for the alternate service provider to have contingency plans.','The organization conducting the inspection/assessment obtains and examines the alternate telecommunications service provider agreements to ensure the organization requires the alternate service provider to have contingency plans.'),
('000534','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of conducting user-level information backups to support recovery time objectives and recovery point objectives.','CP-9.1','DoD has defined the frequency as at least weekly as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least weekly as defined in the contingency plan.'),
('000535','draft','2009-09-21','DISA FSO','policy','The organization conducts backups of user-level information contained in the information system per organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-9.2','The organization being inspected/assessed must identify user level information within the backup strategy and configure the system to perform backups at least weekly as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and reviews the backup strategy, and examines a sample of systems to ensure they are configured to perform back ups at least weekly as defined in the contingency plan.'),
('000536','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of conducting system-level information backups to support recovery time objectives and recovery point objectives.','CP-9.3','DoD has defined the frequency as at least weekly and as required by system baseline configuration changes in accordance with the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least weekly and as required by system baseline configuration changes in accordance with the contingency plan.'),
('000537','draft','2009-09-21','DISA FSO','policy','The organization conducts backups of system-level information contained in the information system per organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-9.4','The organization being inspected/assessed must identify system-level information within the backup strategy and configure the system to perform backups at least weekly and as required by system baseline configuration changes in accordance with the contingency plan.','The organization conducting the inspection/assessment obtains and reviews the backup strategy, and examines a sample of systems to ensure they are configured to perform back ups at least weekly and as required by system baseline configuration changes in accordance with the contingency plan.'),
('000538','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of conducting information system documentation backups, including security-related documentation, to support recovery time objectives and recovery point objectives.','CP-9.5','DoD has defined the frequency as when created or received, when updated, and as required by system baseline configuration changes in accordance with the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as when created or received, when updated, and as required by system baseline configuration changes in accordance with the contingency plan.'),
('000539','draft','2009-09-21','DISA FSO','policy','The organization conducts backups of information system documentation, including security-related documentation, per an organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-9.6','The organization being inspected/assessed conducts backups of information system documentation including security-related documentation when created or received, when updated, and as required by system baseline configuration changes in accordance with the contingency plan.','The organization conducting the inspection/assessment obtains and examines the latest version of the information system documentation including security-related documentation to verify it is the same version as contained in backups.'),
('000540','draft','2009-09-21','DISA FSO','policy','The organization protects the confidentiality, integrity, and availability of backup information at storage locations.','CP-9.7','The organization being inspected/assessed will protect the confidentiality, integrity, and availability of backup information at the storage location IAW the system security plan.','The organization conducting the inspection/assessment obtains and examines the system security plan and ensures backup information at the storage location is protected IAW the system security plan.'),
('000541','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to test backup information to verify media reliability and information integrity.','CP-9(1).1','DoD has defined the frequency as at least monthly in accordance with contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least monthly in accordance with contingency plan.'),
('000542','draft','2009-09-21','DISA FSO','policy','The organization tests backup information per an organization-defined frequency to verify media reliability and information integrity.','CP-9(1).2','The organization being inspected/assessed tests and logs backup information at least monthly in accordance with contingency plan to verify media reliability and information integrity.','The organization conducting the inspection/assessment obtains and examines the backup plan and verifies that the organization has tested and logged backup information.'),
('000543','draft','2009-09-21','DISA FSO','policy','The organization uses a sample of backup information in the restoration of selected information system functions as part of contingency plan testing.','CP-9(2).1','The organization being inspected/assessed restores a sample of backup information as part of the restoration of selected information system functions during contingency plan testing. Organizations must identify a sample of backup information in the contingency plan test results.','The organization conducting the inspection/assessment obtains and examines the contingency plan test results to verify that the sample of backup information was restored as part of the restoration of selected information system functions.'),
('000544','draft','2009-09-21','DISA FSO','policy','The organization stores backup copies of the operating system in a separate facility or in a fire-rated container that is not colocated with the operational system.',NULL,NULL,NULL),
('000545','draft','2009-09-21','DISA FSO','policy','The organization stores backup copies of critical information system software in a separate facility or in a fire-rated container that is not colocated with the operational system.',NULL,NULL,NULL),
('000546','draft','2009-09-21','DISA FSO','policy','The organization stores backup copies of the information system inventory (including hardware, software, and firmware components) in a separate facility or in a fire-rated container that is not colocated with the operational system.',NULL,NULL,NULL),
('000547','draft','2009-09-21','DISA FSO','policy','The organization defines the time period and transfer rate of the information system backup information to the alternate storage site consistent with the recovery time and recovery point objectives.','CP-9(5).1','DoD has defined the time period as Continuously (Availability High ) 24 hours (Availability Moderate) 7 days (Availability Low) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as Continuously (Availability High ) 24 hours (Availability Moderate) 7 days (Availability Low) as defined in the contingency plan.'),
('000548','draft','2009-09-21','DISA FSO','policy','The organization transfers information system backup information to the alternate storage site in accordance with the organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives.','CP-9(5).2','The organization being inspected/assessed performs the transfer of information system backup information to the alternate site Continuously (Availability High) 24 hours (Availability Moderate) 7 days (Availability Low) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the contingency plan and related logs to ensure the organization transfers information system backup information to the alternate site Continuously (Availability High) 24 hours (Availability Moderate) 7 days (Availability Low) as defined in the contingency plan.'),
('000549','draft','2009-09-21','DISA FSO','policy','The organization maintains a redundant secondary information system that is not collocated with the primary system.','CP-9(6).1','The organization being inspected/assessed establishes and maintains a redundant, secondary backup system that is not co-located with the primary system.','The organization conducting the inspection/assessment determines if the organization is maintaining a redundant, secondary backup system that is not co-located with the primary system.'),
('000550','draft','2009-09-21','DISA FSO','policy','The organization provides for the recovery and reconstitution of the information system to a known state after a disruption.','CP-10.1','The organization being inspected/assessed provides automated mechanisms or manual procedures, or a combination of the two, for the recovery and reconstitution of its information system to a known state after a disruption. The organization must identify the selected method in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it identifies the recovery and reconstitution method for its information system to a known state after a disruption.'),
('000551','draft','2009-09-21','DISA FSO','policy','The organization provides for the recovery and reconstitution of the information system to a known state after a compromise.','CP-10.2','The organization being inspected/assessed provides automated mechanisms or manual procedures, or a combination of the two, for the recovery and reconstitution of its information system to a known state after a compromise. The organization must identify the selected method in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it identifies the recovery and reconstitution method for its information system to a known state after a compromise.'),
('000552','draft','2009-09-21','DISA FSO','policy','The organization provides for the recovery and reconstitution of the information system to a known state after a failure.','CP-10.3','The organization being inspected/assessed provides automated mechanisms or manual procedures, or a combination of the two, for the recovery and reconstitution of its information system to a known state after a failure. The organization must identify the selected method in the contingency plan.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it identifies the recovery and reconstitution method for its information system to a known state after a failure.'),
('000553','draft','2009-09-21','DISA FSO','policy','The information system implements transaction recovery for systems that are transaction-based.','CP-10(2).1','The organization being inspected/assessed identifies, documents, and implements transaction recovery capability for systems that are transaction-based. The organization must document transaction recovery results as part of contingency plan testing.','The organization conducting the inspection/assessment obtains and examines the contingency plan test results to verify transaction recovery.'),
('000554','draft','2009-09-21','DISA FSO','policy','The organization defines in the security plan, explicitly or by reference, the circumstances that can inhibit recovery and reconstitution of the information system to a known state.',NULL,NULL,NULL),
('000555','draft','2009-09-21','DISA FSO','policy','The organization provides compensating security controls for organization-defined circumstances that can inhibit recovery and reconstitution of the information system to a known state.',NULL,NULL,NULL),
('000556','draft','2009-09-21','DISA FSO','policy','The organization defines restoration time periods within which to restore information system components from configuration-controlled and integrity-protected information representing a known, operational state for the components.','CP-10(4).1','DoD has defined the time period as 1 hour (Availability High ) 24 hours (Availability Moderate) 1 - 5 days (Availability Low) as defined in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 hour (Availability High ) 24 hours (Availability Moderate) 1 - 5 days (Availability Low) as defined in the contingency plan.'),
('000557','draft','2009-09-21','DISA FSO','policy','The organization provides the capability to restore information system components within organization-defined restoration time periods from configuration-controlled and integrity-protected information representing a known, operational state for the components.','CP-10(4).2','The organization being inspected/assessed exercises the capability to restore information system components from configuration-controlled and integrity-protected information representing a secure, operational state for the components within the defined time period during contingency plan testing: 1 hour (Availability High ) 24 hours (Availability Moderate) 1 - 5 days (Availability Low) as defined in the contingency plan.','The organization conducting the inspection/assessment obtains and examines contingency plan test results to verify the organization exercises the capability to restore information system components from configuration-controlled and integrity-protected information representing a secure, operational state for the components, and that restoration occurred within the defined time period: 1 hour (Availability High ) 24 hours (Availability Moderate) 1 - 5 days (Availability Low) as defined in the contingency plan.'),
('000558','draft','2009-09-21','DISA FSO','policy','The organization defines the real-time or near-real-time failover capability to be provided for the information system.','SI-13(5).1','The organization being inspected/assessed defines and documents the real-time or near-real-time failover capability to be provided for the information system. DoD has determined the failover capability is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented failover capability to ensure the organization being inspected/assessed defines the real-time or near-real-time failover capability to be provided for the information system. DoD has determined the failover capability is not appropriate to define at the Enterprise level.'),
('000559','draft','2009-09-21','DISA FSO','policy','The organization provides real-time or near-real-time organization-defined failover capability for the information system.','SI-13(5).2','The organization being inspected/assessed designs the information system to provide real-time or near-real-time failover capability defined in SI-13 (5), CCI 558 for the information system.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed provides real-time or near-real-time failover capability defined in SI-13 (5), CCI 558 for the information system.'),
('000560','draft','2009-09-21','DISA FSO','policy','The organization protects backup and restoration hardware.','CP-10(6).1','The organization being inspected/assessed implements and documents policies and back up procedures designed to protect its backup and restoration hardware.','The organization conducting the inspection/assessment obtains and examines documentation of protection measures to ensure the organization is actively protecting backup and restoration hardware.'),
('000561','draft','2009-09-21','DISA FSO','policy','The organization protects backup and restoration firmware.','CP-10(6).2','The organization being inspected/assessed implements and documents policies and back up procedures designed to protect its backup and restoration firmware.','The organization conducting the inspection/assessment obtains and examines documentation of protection measures to ensure the organization is actively protecting backup and restoration firmware.'),
('000562','draft','2009-09-21','DISA FSO','policy','The organization protects backup and restoration software.','CP-10(6).3','The organization being inspected/assessed implements and documents policies and back up procedures designed to protect its backup and restoration software.','The organization conducting the inspection/assessment obtains and examines documentation of protection measures to ensure the organization is actively protecting backup and restoration software.'),
('000563','draft','2009-09-21','DISA FSO','policy','The organization develops and documents a security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PL-1.3','DoDI 8510.01 meets the requirements for a security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.','DoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.'),
('000564','draft','2009-09-21','DISA FSO','policy','The organization disseminates a security planning policy to organization-defined personnel or roles.','PL-1.4','DoD disseminates DoDI 8510.01 via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) to organizational personnel with planning responsibilities or information security responsibilities.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the roles as organizational personnel with planning responsibilities or information security responsibilities.','DoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the roles as organizational personnel with planning responsibilities or information security responsibilities.'),
('000565','deprecated','2009-09-21','DISA FSO','policy','The organization reviews/updates, per organization-defined frequency, a formal, documented security planning policy.',NULL,NULL,NULL),
('000566','draft','2009-09-21','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the security planning policy and associated security planning controls.','PL-1.5','DoDI 8510.01 meets the requirements for developing and documenting procedures to facilitate the implementation of the security planning policy and associated security planning controls.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.','DoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.'),
('000567','draft','2009-09-21','DISA FSO','policy','The organization disseminates security planning procedures to organization-defined personnel or roles.','PL-1.8','DoD disseminates DoDI 8510.01 via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) to organizational personnel with planning responsibilities or information security responsibilities.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the roles as organizational personnel with planning responsibilities or information security responsibilities.','DoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the roles as organizational personnel with planning responsibilities or information security responsibilities.'),
('000568','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current security planning procedures in accordance with organization-defined frequency.','PL-1.9','DoDI 8510.01 meets the requirements for a security planning policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.','DoDI 8510.01 meets the requirements for a security planning policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000570','draft','2009-09-21','DISA FSO','policy','The organization develops a security plan for the information system that is consistent with the organization^s enterprise architecture; explicitly defines the authorization boundary for the system; describes the operational context of the information system in terms of mission and business processes; provides the security category and impact level of the information system, including supporting rationale; describes the operational environment for the information system; describes relationships with, or connections to, other information systems; provides an overview of the security requirements for the system; and describes the security controls in place or planned for meeting those requirements, including a rationale for the tailoring and supplemental decisions.',NULL,NULL,NULL),
('000571','draft','2009-09-21','DISA FSO','policy','The organization^s security plan for the information system is reviewed and approved by the authorizing official or designated representative prior to plan implementation.','PL-2.10','The organization being inspected/assessed obtains security plan approval by the authorizing official or designated representative prior to plan implementation.','The organization conducting the inspection/assessment obtains and examines the security plan approval to ensure the organization being inspected/assessed obtains security plan approval by the authorizing official or designated representative prior to plan implementation.'),
('000572','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency for reviewing the security plan for the information system.','PL-2.15','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000573','draft','2009-09-21','DISA FSO','policy','The organization reviews the security plan for the information system in accordance with organization-defined frequency.','PL-2.16','The information system owner as part of the annual security control review will also review the security plan annually. Documentation of security plan reviews is required as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit records of security plan reviews to verify the security plan has been reviewed annually. DoD has defined the frequency as annually.'),
('000574','draft','2009-09-21','DISA FSO','policy','The organization updates the plan to address changes to the information system/environment of operation or problems identified during plan implementation or security control assessments.','PL-2.17','The information system owner will update the security plan as necessary to address changes to information system/environment of operation or problems identified during plan implementation or security control assessments. Documentation of security plan updates are required as an audit trail.','The organization conducting the inspection/assessment obtains and examines the audit records of security plan updates to verify the security plan is current. The purpose of the reviews is to validate the organization is updating the Information System (IS) security plan to address changes to the IS, its environment of operation, or problems identified during plan implementation or security control assessments.'),
('000576','draft','2009-09-21','DISA FSO','policy','The organization develops a security Concept of Operations (CONOPS) for the information system containing, at a minimum: the purpose of the system; a description of the system architecture; the security authorization schedule; and the security categorization and associated factors considered in determining the categorization.',NULL,NULL,NULL),
('000577','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review and update the security CONOPS.','PL-7.2','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000578','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the security CONOPS in accordance with organization-defined frequency.','PL-7.3','The organization being inspected/assessed reviews and updates the security CONOPS annually. The organization must maintain an audit trail of reviews and updates. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates the security CONOPS annually. DoD has defined the frequency as annually.'),
('000580','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains external interfaces.',NULL,NULL,NULL),
('000581','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains the information being exchanged across the interfaces.',NULL,NULL,NULL),
('000582','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains the protection mechanisms associated with each interface.',NULL,NULL,NULL),
('000583','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains user roles.',NULL,NULL,NULL),
('000584','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains the access privileges assigned to each role.',NULL,NULL,NULL),
('000585','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains unique security requirements.',NULL,NULL,NULL),
('000586','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains types of information processed by the information system.',NULL,NULL,NULL),
('000587','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains types of information stored by the information system.',NULL,NULL,NULL),
('000588','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains types of information transmitted by the information system.',NULL,NULL,NULL),
('000589','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains any specific protection needs in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.',NULL,NULL,NULL),
('000590','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains restoration priority of information.',NULL,NULL,NULL),
('000591','draft','2009-09-21','DISA FSO','policy','The organization develops a functional architecture for the information system that identifies and maintains restoration priority of information system services.',NULL,NULL,NULL),
('000592','draft','2009-09-21','DISA FSO','policy','The organization establishes the rules describing the responsibilities and expected behavior, with regard to information and information system usage, for individuals requiring access to the information system.','PL-4.1','The organization being inspected/assessed must develop and document rules that describe information system user responsibilities and expected behavior with regard to information and information system usage, acceptable use policy (AUP). Organizations should reference Joint Ethics Regulations (DoD 5500.7-R) when developing this policy.','The organization conducting the inspection/assessment obtains and examines the organization\'s AUP to ensure the organization has clearly defined and established rules describing information system user responsibilities and expected behavior with regard to information and information system usage.'),
('000593','draft','2009-09-21','DISA FSO','policy','The organization receives a signed acknowledgment from individuals requiring access to the information system, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system.','PL-4.3','The organization being inspected/assessed will obtain signed acknowledgment (paper or electronic signature) from individuals indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the information system.','The organization conducting the inspection/assessment obtains a list of individuals with active accounts and validates the existence of signed acknowledgements (paper or electronic signature) of the organizational AUP associated with a sampling of individuals selected from the list.'),
('000594','draft','2009-09-21','DISA FSO','policy','The organization includes in the rules of behavior explicit restrictions on the use of social media/networking sites.','PL-4(1).1','The organization being inspected/assessed includes in the rules of behavior, IAW DoDI 8550.01, explicit restrictions on the use of social media/networking sites.','The organization conducting the inspection/assessment obtains and examines the rules of behavior to ensure the organization being inspected/assessed includes explicit restrictions on the use of social media/networking sites IAW DoDI 8550.01.'),
('000595','draft','2009-09-21','DISA FSO','policy','The organization includes in the rules of behavior explicit restrictions on posting organizational information on public websites.','PL-4(1).2','The organization being inspected/assessed includes in the rules of behavior, IAW DoDI 8550.01, explicit restrictions on posting organizational information on public websites.','The organization conducting the inspection/assessment obtains and examines the rules of behavior to ensure the organization being inspected/assessed includes explicit restrictions on posting organizational information on public websites IAW DoDI 8550.01.'),
('000596','draft','2009-09-21','DISA FSO','policy','The organization includes in the rules of behavior, explicit restrictions on sharing information system account information.',NULL,NULL,NULL),
('000597','draft','2009-09-21','DISA FSO','policy','The organization conducts a privacy impact assessment on the information system in accordance with OMB policy.',NULL,NULL,NULL),
('000598','draft','2009-09-21','DISA FSO','policy','The organization plans and coordinates security-related activities affecting the information system before conducting such activities in order to reduce the impact on organizational operations (i.e., mission, functions, image, and reputation).',NULL,NULL,NULL),
('000599','draft','2009-09-21','DISA FSO','policy','The organization plans and coordinates security-related activities affecting the information system before conducting such activities in order to reduce the impact on organizational assets.',NULL,NULL,NULL),
('000600','draft','2009-09-21','DISA FSO','policy','The organization plans and coordinates security-related activities affecting the information system before conducting such activities in order to reduce the impact on organizational individuals.',NULL,NULL,NULL),
('000601','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review and update the current system and services acquisition policy.','SA-1.7','DoD has defined the frequency as every 5 years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 5 years.'),
('000602','draft','2009-09-21','DISA FSO','policy','The organization develops and documents a system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SA-1.4','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.'),
('000603','draft','2009-09-21','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles a system and services acquisition policy.','SA-1.3','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.'),
('000604','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current system and services acquisition policy in accordance with organization-defined frequency.','SA-1.8','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.'),
('000605','draft','2009-09-21','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls.','SA-1.5','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.'),
('000606','draft','2009-09-21','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls.','SA-1.6','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.'),
('000607','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current system and services acquisition procedures in accordance with organization-defined frequency.','SA-1.9','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.','DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1 meet the DoD requirements for system and services acquisition policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDD 5000.01, DoDI 5000.02, and DoDI 8580.1.'),
('000608','draft','2009-09-21','DISA FSO','policy','The organization includes a determination of information security requirements for the information system in mission process planning.',NULL,NULL,NULL),
('000609','draft','2009-09-21','DISA FSO','policy','The organization includes a determination of information security requirements for the information system in business process planning.',NULL,NULL,NULL),
('000610','draft','2009-09-21','DISA FSO','policy','The organization determines the resources required to protect the information system or information system service as part of its capital planning and investment control process.','SA-2.2','The organization being inspected/assessed determines the resources (funding, staffing, etc.) required for the cybersecurity requirements to protect the information system or information system service as part of its planning, programming, and budget process (PPBE).','The organization conducting the inspection/assessment obtains and examines the planning, programming, and budget documentation to ensure the organization being inspected/assessed has determined the resources required for cybersecurity requirements to protect the information system or information system service.'),
('000611','draft','2009-09-21','DISA FSO','policy','The organization documents the resources required to protect the information system or information system service as part of its capital planning and investment control process.','SA-2.3','The organization being inspected/assessed documents the resources (funding, staffing, etc.) required for the cybersecurity requirements to protect the information system or information system service as part of its planning, programming, and budget process (PPBE).','The organization conducting the inspection/assessment obtains and examines the planning, programming, and budget documentation to ensure the organization being inspected/assessed has documented the resources required for cybersecurity requirements to protect the information system or information system service.'),
('000612','draft','2009-09-21','DISA FSO','policy','The organization allocates the resources required to protect the information system or information system service as part of its capital planning and investment control process.','SA-2.4','The organization being inspected/assessed allocates the resources (funding, staffing, etc.) required for the cybersecurity requirements to protect the information system or information system service as part of its planning, programming, and budget process (PPBE).','The organization conducting the inspection/assessment obtains and examines the planning, programming, and budget documentation to ensure the organization being inspected/assessed has allocated the resources required for cybersecurity requirements to protect the information system or information system service.'),
('000613','draft','2009-09-21','DISA FSO','policy','The organization establishes a discrete line item for information security in organizational programming documentation.','SA-2.5','The organization being inspected/assessed identifies and establishes an individual line item for cybersecurity requirements to protect the information system as part of the planning, programming, and budget process (PPBE).','The organization conducting the inspection/assessment obtains and examines the planning, programming, and budget documentation to ensure the organization being inspected/assessed has identified and established an individual line item for cybersecurity requirements to protect the information system.'),
('000614','draft','2009-09-21','DISA FSO','policy','The organization establishes a discrete line item for information security in organizational budgeting documentation.','SA-2.6','The organization being inspected/assessed identifies and establishes an individual line item for cybersecurity requirements to protect the information system as part of the planning, programming, and budget process (PPBE).','The organization conducting the inspection/assessment obtains and examines the planning, programming, and budget documentation to ensure the organization being inspected/assessed has identified and established an individual line item for cybersecurity requirements to protect the information system.'),
('000615','draft','2009-09-21','DISA FSO','policy','The organization manages the information system using an organization-defined system development life cycle that incorporates information security considerations.','SA-3.1','The organization being inspected/assessed documents and implements a process to manage the information system using the system development life cycle defined in SA-3, CCI 3092 that incorporates information security considerations IAW DoDI 8580.1.','The organization conducting the inspection/assessment obtains and examines the documented process and artifacts of the system development life cycle process to ensure the organization being inspected/assessed manages the information system using the system development life cycle defined in SA-3, CCI 3092 that incorporates information security considerations IAW DoDI 8580.1.'),
('000616','draft','2009-09-21','DISA FSO','policy','The organization defines and documents information system security roles and responsibilities throughout the system development life cycle.','SA-3.3','The organization being inspected/assessed defines and documents information system security roles and responsibilities throughout the system development life cycle IAW DoDI 8580.1.','The organization conducting the inspection/assessment obtains and examines the information system security roles and responsibilities to ensure the organization being inspected/assessed defines and documents information system security roles and responsibilities throughout the system development life cycle IAW DoDI 8580.1.'),
('000617','draft','2009-09-21','DISA FSO','policy','The organization documents information system security roles and responsibilities throughout the system development life cycle.',NULL,NULL,NULL),
('000618','draft','2009-09-21','DISA FSO','policy','The organization identifies individuals having information system security roles and responsibilities.','SA-3.4','The organization being inspected/assessed identifies and documents individuals having information system security roles and responsibilities.','The organization conducting the inspection/assessment obtains and examines the documented individuals having information system security roles and responsibilities to ensure the organization being inspected/assessed identifies individuals having information system security roles and responsibilities.'),
('000619','draft','2009-09-21','DISA FSO','policy','The organization includes security functional requirements/specifications, explicitly or by reference, in information system acquisition contracts based on an assessment of risk and in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.',NULL,NULL,NULL),
('000620','draft','2009-09-21','DISA FSO','policy','The organization includes security-related documentation requirements, explicitly or by reference, in information system acquisition contracts based on an assessment of risk and in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.',NULL,NULL,NULL),
('000621','draft','2009-09-21','DISA FSO','policy','The organization includes developmental and evaluation-related assurance requirements, explicitly or by reference, in information system acquisition contracts based on an assessment of risk and in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.',NULL,NULL,NULL),
('000623','draft','2009-09-21','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide a description of the functional properties of the security controls to be employed.','SA-4(1).1','DoDI 8510.01 system categorization meets the DoD requirement for providing a description of the functional properties of the security controls to be employed.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.','DoDI 8510.01 system categorization meets the DoD requirement for providing a description of the functional properties of the security controls to be employed.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01.'),
('000624','draft','2009-09-21','DISA FSO','policy','The organization requires in acquisition documents that vendors/contractors provide information describing the design details of the security controls to be employed within the information system, information system components, or information system services (including functional interfaces among control components) in sufficient detail to permit analysis and testing of the controls.',NULL,NULL,NULL),
('000625','draft','2009-09-21','DISA FSO','policy','The organization requires in acquisition documents that vendors/contractors provide information describing the implementation details of the security controls to be employed within the information system, information system components, or information system services (including functional interfaces among control components) in sufficient detail to permit analysis and testing of the controls.',NULL,NULL,NULL),
('000626','draft','2009-09-21','DISA FSO','policy','The organization requires software vendors/manufacturers to minimize flawed or malformed software by demonstrating that their software development process employs state-of-the-practice software and security engineering methods.',NULL,NULL,NULL),
('000627','draft','2009-09-21','DISA FSO','policy','The organization requires software vendors/manufacturers to minimize flawed or malformed software by demonstrating that their software development process employs quality control processes.',NULL,NULL,NULL),
('000628','draft','2009-09-21','DISA FSO','policy','The organization requires software vendors/manufacturers to minimize flawed or malformed software by demonstrating that their software development processes employ validation techniques.',NULL,NULL,NULL),
('000629','draft','2009-09-21','DISA FSO','policy','The organization ensures each information system component acquired is explicitly assigned to an information system, and that the owner of the system acknowledges this assignment.',NULL,NULL,NULL),
('000630','draft','2009-09-21','DISA FSO','policy','The organization requires in acquisition documents, that information system components are delivered in a secure, documented configuration, and that the secure configuration is the default configuration for any software reinstalls or upgrades.',NULL,NULL,NULL),
('000631','draft','2009-09-21','DISA FSO','policy','The organization employs only government off-the-shelf (GOTS) or commercial off-the-shelf (COTS) information assurance (IA) and IA-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted.','SA-4(6).1','The organization being inspected/assessed must identify and use NSA-approved encryption technologies to protect classified information when the networks or transmission medium used to transmit the information are at a lower classification level than the information being transmitted.','The organization conducting the inspection/assessment examines and verifies identified encryption technologies in use by the organization being inspected/assessed are NSA-approved.'),
('000632','deprecated','2009-09-21','DISA FSO','policy','The organization employs only commercial off-the-shelf (COTS) information assurance (IA) and IA-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted.',NULL,NULL,NULL),
('000633','draft','2009-09-21','DISA FSO','policy','The organization ensures that government off-the-shelf (GOTS) or commercial-off-the-shelf(COTS) information assurance (IA) and IA-enabled information technology products have been evaluated and/or validated by the NSA or in accordance with NSA-approved procedures.','SA-4(6).2','The organization being inspected/assessed must identify and use NSA-approved encryption technologies to protect classified information when the networks or transmission medium used to transmit the information are at a lower classification level than the information being transmitted.','The organization conducting the inspection/assessment examines and verifies identified encryption technologies in use by the organization being inspected/assessed are NSA-approved.'),
('000634','draft','2009-09-21','DISA FSO','policy','The organization limits the use of commercially provided information assurance (IA) and IA-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance Partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists.','SA-4(7).1','The organization being inspected/assessed, when using commercially provided IA and IA-enabled IT products uses only products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists.','The organization conducting the inspection/assessment obtains and examines the hardware and software lists to ensure the organization being inspected/assessed, when using commercially provided IA and IA-enabled IT products uses only products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists.'),
('000635','draft','2009-09-21','DISA FSO','policy','The organization requires, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated.','SA-4(7).2','The organization being inspected/assessed, when using commercially provided IA or IA enabled IT products for which there is no NIAP-approved protection profile, relies on FIPS-validated cryptographic modules.','The organization conducting the inspection/assessment obtains and examines the hardware and software lists to ensure the organization being inspected/assessed, when using commercially provided IA or IA enabled IT products for which there is no NIAP-approved protection profile, relies on FIPS-validated cryptographic modules.'),
('000636','draft','2009-09-21','DISA FSO','policy','The organization obtains administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.',NULL,NULL,NULL),
('000637','draft','2009-09-21','DISA FSO','policy','The organization protects, as required, administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.',NULL,NULL,NULL),
('000638','draft','2009-09-21','DISA FSO','policy','The organization makes available to authorized personnel administrator documentation for the information system that describes secure configuration, installation, and operation of the information system; effective use and maintenance of the security features/functions; and known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.',NULL,NULL,NULL),
('000639','draft','2009-09-21','DISA FSO','policy','The organization obtains user documentation for the information system that describes user-accessible security features/functions and how to effectively use those security features/functions; methods for user interaction with the information system, which enables individuals to use the system in a more secure manner; and user responsibilities in maintaining the security of the information and information system.',NULL,NULL,NULL),
('000640','draft','2009-09-21','DISA FSO','policy','The organization protects, as required, user documentation for the information system that describes user-accessible security features/functions and how to effectively use those security features/functions; methods for user interaction with the information system, which enables individuals to use the system in a more secure manner; and user responsibilities in maintaining the security of the information and information system.',NULL,NULL,NULL),
('000641','draft','2009-09-21','DISA FSO','policy','The organization makes available to authorized personnel user documentation for the information system that describes user-accessible security features/functions and how to effectively use those security features/functions; methods for user interaction with the information system, which enables individuals to use the system in a more secure manner; and user responsibilities in maintaining the security of the information and information system.',NULL,NULL,NULL),
('000642','draft','2009-09-21','DISA FSO','policy','The organization documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent.','SA-5.11','The organization being inspected/assessed documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent.','The organization conducting the inspection/assessment obtains and examines the documented attempts to ensure the organization being inspected/assessed documents attempts to obtain information system, system component, or information system service documentation when such documentation is either unavailable or nonexistent.'),
('000643','draft','2009-09-21','DISA FSO','policy','The organization obtains vendor/manufacturer documentation that describes the functional properties of the security controls employed within the information system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('000644','draft','2009-09-21','DISA FSO','policy','The organization protects, as required, vendor/manufacturer documentation that describes the functional properties of the security controls employed within the information system.',NULL,NULL,NULL),
('000645','draft','2009-09-21','DISA FSO','policy','The organization makes available to authorized personnel vendor/manufacturer documentation that describes the functional properties of the security controls employed within the information system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('000646','draft','2009-09-21','DISA FSO','policy','The organization obtains vendor/manufacturer documentation that describes the security-relevant external interfaces to the information system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('000647','draft','2009-09-21','DISA FSO','policy','The organization obtains vendor/manufacturer documentation that describes the high-level design of the information system in terms of subsystems and implementation details of the security controls employed within the system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('000648','draft','2009-09-21','DISA FSO','policy','The organization protects, as required, vendor/manufacturer documentation that describes the high-level design of the information system in terms of subsystems and implementation details of the security controls employed within the system.',NULL,NULL,NULL),
('000650','draft','2009-09-21','DISA FSO','policy','The organization obtains vendor/manufacturer documentation that describes the low-level design of the information system in terms of modules and implementation details of the security controls employed within the system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('000651','draft','2009-09-21','DISA FSO','policy','The organization protects, as required, vendor/manufacturer documentation that describes the low-level design of the information system in terms of modules and implementation details of the security controls employed within the system.',NULL,NULL,NULL),
('000653','draft','2009-09-21','DISA FSO','policy','The organization obtains the source code for the information system to permit analysis and testing.',NULL,NULL,NULL),
('000654','draft','2009-09-21','DISA FSO','policy','The organization protects, as required, the source code for the information system to permit analysis and testing.',NULL,NULL,NULL),
('000655','draft','2009-09-21','DISA FSO','policy','The organization uses software and associated documentation in accordance with contract agreements and copyright laws.',NULL,NULL,NULL),
('000656','draft','2009-09-21','DISA FSO','policy','The organization employs tracking systems for software and associated documentation protected by quantity licenses to control copying and distribution.',NULL,NULL,NULL),
('000657','draft','2009-09-21','DISA FSO','policy','The organization controls the use of peer-to-peer file sharing technology to ensure this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.',NULL,NULL,NULL),
('000658','draft','2009-09-21','DISA FSO','policy','The organization documents the use of peer-to-peer file sharing technology to ensure this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.',NULL,NULL,NULL),
('000659','draft','2009-09-21','DISA FSO','policy','The organization prohibits the use of binary executable code from sources with limited or no warranty without accompanying source code.',NULL,NULL,NULL),
('000660','draft','2009-09-21','DISA FSO','policy','The organization prohibits the use of machine executable code from sources with limited or no warranty without accompanying source code.',NULL,NULL,NULL),
('000661','draft','2009-09-21','DISA FSO','policy','The organization provides exceptions to the source code requirement only when no alternative solutions are available to support compelling mission/operational requirements.',NULL,NULL,NULL),
('000662','draft','2009-09-21','DISA FSO','policy','The organization obtains express written consent of the authorizing official for exceptions to the source code requirement.',NULL,NULL,NULL),
('000663','draft','2009-09-21','DISA FSO','technical','The organization (or information system) enforces explicit rules governing the installation of software by users.',NULL,NULL,NULL),
('000664','draft','2009-09-21','DISA FSO','policy','The organization applies information system security engineering principles in the specification of the information system.','SA-8.1','The organization managing the acquisition/development of the information system (e.g. PM) applies and documents system security engineering (SSE) principles as part of the overall systems engineering process IAW DoDD 5000.01 and DoDI 5000.02. The primary source of general and DoD-specific guidance on SSE can be found in the NIST SP 800-160 - Systems Security Engineering, currently in draft form, and can be found here: http://csrc.nist.gov/publications/PubsSPs.html. Additional guidance can be found in the Defense Acquisition Guidebook (DAG) Chapters 4 and 13, found here: https://dag.dau.mil/.\n\n\nThis CCI does not apply to COTS products.\n\nThe organization managing the acquisition/development of the information system must ensure that the system requirements documents reflect the system security engineering principles that can be applied to information systems in development, systems undergoing major upgrades and to the extent feasible systems in sustainment. Security engineering principles include:\n 1. Developing layered protections;\n 2. Establishing sound security policy, architecture, and controls as the foundation for design;\n 3. Incorporating security requirements into all phases of the system development life cycle;\n 4. Delineating physical and logical security boundaries;\n 5. Ensuring that system developers are trained on how to design and build secure software;\n 6. Tailoring security controls and protections to meet system-specific requirements and operational needs;\n 7. Performing threat modeling to identify use cases, threat agents, attack vectors, and attack patterns as well as compensating controls and design patterns needed to mitigate risk.','The organization conducting the inspection/assessment obtains and examines the system requirements documents to ensure that the organization being inspected/assessed applies information system security engineering principles in the specification of the information system.'),
('000665','draft','2009-09-21','DISA FSO','policy','The organization applies information system security engineering principles in the design of the information system.','SA-8.2','The organization managing the acquisition/development of the information system (e.g. PM) applies and documents system security engineering (SSE) principles as part of the overall systems engineering process IAW DoDD 5000.01 and DoDI 5000.02. The primary source of general and DoD-specific guidance on SSE can be found in the NIST SP 800-160 - Systems Security Engineering, currently in draft form, and can be found here: http://csrc.nist.gov/publications/PubsSPs.html. Additional guidance can be found in the Defense Acquisition Guidebook (DAG) Chapters 4 and 13, found here: https://dag.dau.mil/.\n\n\nThis CCI does not apply to COTS products.\n\nThe organization managing the acquisition/development of the information system must ensure that the design documents reflect the system security engineering principles that can be applied to information systems in development, systems undergoing major upgrades and to the extent feasible systems in sustainment. Security engineering principles include:\n 1. Developing layered protections;\n 2. Establishing sound security policy, architecture, and controls as the foundation for design;\n 3. Incorporating security requirements into all phases of the system development life cycle;\n 4. Delineating physical and logical security boundaries;\n 5. Ensuring that system developers are trained on how to design and build secure software;\n 6. Tailoring security controls and protections to meet system-specific requirements and operational needs;\n 7. Performing threat modeling to identify use cases, threat agents, attack vectors, and attack patterns as well as compensating controls and design patterns needed to mitigate risk.','The organization conducting the inspection/assessment obtains and examines the design documents to ensure that the organization being inspected/assessed applies information system security engineering principles in the design of the information system.'),
('000666','draft','2009-09-21','DISA FSO','policy','The organization applies information system security engineering principles in the development of the information system.','SA-8.3','The organization managing the acquisition/development of the information system (e.g. PM) applies and documents system security engineering (SSE) principles as part of the overall systems engineering process IAW DoDD 5000.01 and DoDI 5000.02. The primary source of general and DoD-specific guidance on SSE can be found in the NIST SP 800-160 - Systems Security Engineering, currently in draft form, and can be found here: http://csrc.nist.gov/publications/PubsSPs.html. Additional guidance can be found in the Defense Acquisition Guidebook (DAG) Chapters 4 and 13, found here: https://dag.dau.mil/.\n\n\nThis CCI does not apply to COTS products.\n\nThe organization managing the acquisition/development of the information system must ensure that the development procedures reflect the system security engineering principles that can be applied to information systems in development, systems undergoing major upgrades and to the extent feasible systems in sustainment. Security engineering principles include:\n 1. Developing layered protections;\n 2. Establishing sound security policy, architecture, and controls as the foundation for design;\n 3. Incorporating security requirements into all phases of the system development life cycle;\n 4. Delineating physical and logical security boundaries;\n 5. Ensuring that system developers are trained on how to design and build secure software;\n 6. Tailoring security controls and protections to meet system-specific requirements and operational needs;\n 7. Performing threat modeling to identify use cases, threat agents, attack vectors, and attack patterns as well as compensating controls and design patterns needed to mitigate risk.\n\nExamples of development procedures that should reflect SSE principles are configuration management plans, code review procedures, and coding style guides. Configuration management plans should be IAW CM-9, CCI 001790.','The organization conducting the inspection/assessment obtains and examines the system development procedures (e.g. configuration management plans, code review procedures, and coding style guides) to ensure that the organization being inspected/assessed applies information system security engineering principles in the development of the information system.'),
('000667','draft','2009-09-21','DISA FSO','policy','The organization applies information system security engineering principles in the implementation of the information system.','SA-8.4','The organization managing the acquisition/development of the information system (e.g. PM) applies and documents system security engineering (SSE) principles as part of the overall systems engineering process IAW DoDD 5000.01 and DoDI 5000.02. The primary source of general and DoD-specific guidance on SSE can be found in the NIST SP 800-160 - Systems Security Engineering, currently in draft form, and can be found here: http://csrc.nist.gov/publications/PubsSPs.html. Additional guidance can be found in the Defense Acquisition Guidebook (DAG) Chapters 4 and 13, found here: https://dag.dau.mil/.\n\n\nThis CCI does not apply to COTS products.\n\nThe organization managing the acquisition/development of the information system must employ the procedures identified in SA-8, CCI, 000666 during the implementation of the information system. The system owner must maintain an audit trail of the activities conducted IAW SA-8, CCI 000666. An example of artifacts is CCB minutes, code review results, and source code analysis results.','The organization conducting the inspection/assessment obtains and examines the audit trail artifacts that were created during the implementation of SA-8, CCI 000666 to ensure that the organization being inspected/assessed applies information system security engineering principles in the implementation of the information system and that changes are made IAW the configuration management plan (CM-9, CCI 001790).'),
('000668','draft','2009-09-21','DISA FSO','policy','The organization applies information system security engineering principles in the modification of the information system.','SA-8.5','The organization managing the acquisition/development of the information system (e.g. PM) applies and documents system security engineering (SSE) principles as part of the overall systems engineering process IAW DoDD 5000.01 and DoDI 5000.02. The primary source of general and DoD-specific guidance on SSE can be found in the NIST SP 800-160 - Systems Security Engineering, currently in draft form, and can be found here: http://csrc.nist.gov/publications/PubsSPs.html. Additional guidance can be found in the Defense Acquisition Guidebook (DAG) Chapters 4 and 13, found here: https://dag.dau.mil/.\n\n\nThis CCI does not apply to COTS products.\n\nThe organization managing the acquisition/development of the information system must employ the procedures identified in SA-8, CCI, 000666 during the modification of the information system. The system owner must maintain an audit trail of the activities conducted IAW SA-8, CCI 000666. An example of artifacts is CCB minutes, code review results, and source code analysis results.','The organization conducting the inspection/assessment obtains and examines the audit trail artifacts that were created during the modification of SA-8, CCI 000666 to ensure that the organization being inspected/assessed applies information system security engineering principles in the modification of the information system and that changes are made IAW the configuration management plan (CM-9, CCI 001790).'),
('000669','draft','2009-09-21','DISA FSO','policy','The organization requires that providers of external information system services comply with organizational information security requirements.','SA-9.1','The organization being inspected/assessed documents within contracts/agreements, requirements that providers of external information system services comply with any organization-specific information security requirements.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that providers of external information system services comply with any organization-specific information security requirements.'),
('000670','draft','2009-09-21','DISA FSO','policy','The organization requires that providers of external information system services employ organization-defined security controls in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.','SA-9.2','The organization being inspected/assessed documents within contracts/agreements, the\nrequirement that providers of external information system services employ security controls defined in CNSSI 1253.\n\nDoD has defined the security controls as security controls defined by CNSSI 1253.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that providers of external information system services employ security controls defined in CNSSI 1253.\n\nDoD has defined the security controls as security controls defined by CNSSI 1253.'),
('000671','draft','2009-09-21','DISA FSO','policy','The organization defines government oversight with regard to external information system services.','SA-9.4','The organization being inspected/assessed must define in the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) the government oversight to be conducted on external information system services and service provider.','The organization conducting the inspection/assessment obtains and examines the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) to confirm the organization has clearly defined the government oversight to be conducted on external information system services and service providers.'),
('000672','draft','2009-09-21','DISA FSO','policy','The organization documents government oversight with regard to external information system services.','SA-9.5','The organization being inspected/assessed must establish in the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) the government oversight to be conducted on external information system services and service provider.','The organization conducting the inspection/assessment obtains and examines the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) to confirm the organization has clearly established the government oversight to be conducted on external information system services and service providers.'),
('000673','draft','2009-09-21','DISA FSO','policy','The organization defines user roles and responsibilities with regard to external information system services.','SA-9.6','The organization being inspected/assessed must define in the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) the roles and responsibilities of all types of users of the external information system services.','The organization conducting the inspection/assessment obtains and examines the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) to confirm the organization has clearly defined the roles and responsibilities of all types of users of the external information system services.'),
('000674','draft','2009-09-21','DISA FSO','policy','The organization documents user roles and responsibilities with regard to external information system services.','SA-9.7','The organization being inspected/assessed must establish in the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) the roles and responsibilities of all types of users of the external information system services.','The organization conducting the inspection/assessment obtains and examines the official documentation governing the provision of the external IT services (e.g. contract, MOU, MOA, SLA, etc.) to confirm the organization has clearly established the roles and responsibilities of all types of users of the external information system services.'),
('000675','draft','2009-09-21','DISA FSO','policy','The organization monitors security control compliance by external service providers.',NULL,NULL,NULL),
('000676','draft','2009-09-21','DISA FSO','policy','The organization conducts an organizational assessment of risk prior to the acquisition of dedicated information security services.',NULL,NULL,NULL),
('000677','draft','2009-09-21','DISA FSO','policy','The organization conducts an organizational assessment of risk prior to the outsourcing of dedicated information security services.',NULL,NULL,NULL),
('000678','draft','2009-09-21','DISA FSO','policy','The organization defines the senior organizational official designated to approve acquisition of dedicated information security services.',NULL,NULL,NULL),
('000679','draft','2009-09-21','DISA FSO','policy','The organization defines the senior organizational official designated to approve outsourcing of dedicated information security services.',NULL,NULL,NULL),
('000680','draft','2009-09-21','DISA FSO','policy','The organization ensures the acquisition of dedicated information security services is approved by an organization-designated senior organizational official.',NULL,NULL,NULL),
('000681','draft','2009-09-21','DISA FSO','policy','The organization ensures the outsourcing of dedicated information security services is approved by an organization-designated senior organizational official.',NULL,NULL,NULL),
('000682','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform configuration management during information system design.',NULL,NULL,NULL),
('000683','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform configuration management during information system development.',NULL,NULL,NULL),
('000684','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform configuration management during information system implementation.',NULL,NULL,NULL),
('000685','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform configuration management during information system operation.',NULL,NULL,NULL),
('000686','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to perform configuration management during information system design.',NULL,NULL,NULL),
('000687','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to perform configuration management during information system development.',NULL,NULL,NULL),
('000688','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to perform configuration management during information system implementation.',NULL,NULL,NULL),
('000689','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to perform configuration management during information system operation.',NULL,NULL,NULL),
('000690','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to manage and control changes to the information system during design.',NULL,NULL,NULL),
('000691','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to manage and control changes to the information system during design.',NULL,NULL,NULL),
('000692','draft','2009-09-22','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to implement only organization-approved changes to the system, component, or service.','SA-10.6','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service implement only organization-approved changes to the system, component, or service throughout its life cycle.','The organization conducting the inspection/assessment obtains and examines contracts/agreements between the organization and the IS developer to confirm the organization has established in its acquisition contracts/agreements the requirement that the IS developer implement only organization-approved changes to the system, component, or service throughout its life cycle.'),
('000693','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to implement only organization-approved changes.',NULL,NULL,NULL),
('000694','draft','2009-09-22','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to document approved changes to the system, component, or service.','SA-10.7','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service document approved changes to the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document approved changes to the system, component, or service.'),
('000695','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to document approved changes to the information system.',NULL,NULL,NULL),
('000696','draft','2009-09-22','DISA FSO','policy','The organization requires that information system developers track security flaws and flaw resolution.',NULL,NULL,NULL),
('000697','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to track security flaws and flaw resolution.',NULL,NULL,NULL),
('000698','draft','2009-09-22','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to enable integrity verification of software and firmware components.','SA-10(1).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service enable integrity verification of software and firmware components.\n\nThe organization being inspected/assessed requires the developer to enable integrity verification of software and firmware that may include:\n1. Stipulating and monitoring logical delivery of products and services, requiring downloading from approved, verification-enhanced sites;\n2. Encrypting elements (software, software patches, etc.) and supply chain process data in transit (motion) and at rest throughout delivery;\n3. Requiring suppliers to provide their elements secure by default, so that additional configuration is required to make the element insecure;\n4. Implementing software designs using programming languages and tools that reduce the likelihood of weaknesses;\n5. Implementing cryptographic hash verification; and\n6. Establishing performance and sub-element baseline for the system and system elements to help detect unauthorized tampering/modification during repairs/refurbishing.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service enable integrity verification of software and firmware components.'),
('000699','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to provide an integrity check of software to facilitate organizational verification of software integrity after delivery.',NULL,NULL,NULL),
('000700','draft','2009-09-22','DISA FSO','policy','The organization provides an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team.','SA-10(2).1','The organization being inspected/assessed, in the absence of a dedicated software developer configuration management team, establishes an alternate configuration management process that is staffed with appropriate key organizational personnel.','The organization conducting the inspection/assessment obtains and examines the Configuration Control Board (CCB) charter to determine if the organization, in the absence of a dedicated software developer configuration management team, has established an alternate configuration management process that is staffed with key organizational personnel.'),
('000701','draft','2009-09-22','DISA FSO','policy','The organization provides an alternative configuration management process with organizational personnel in the absence of a dedicated integrator configuration management team.',NULL,NULL,NULL),
('000702','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers, in consultation with associated security personnel (including security engineers), to create a security test and evaluation plan.',NULL,NULL,NULL),
('000703','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers, in consultation with associated security personnel (including security engineers), to implement a security test and evaluation plan.',NULL,NULL,NULL),
('000704','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators, in consultation with associated security personnel (including security engineers), to create a security test and evaluation plan.',NULL,NULL,NULL),
('000705','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators, in consultation with associated security personnel (including security engineers), to implement a security test and evaluation plan.',NULL,NULL,NULL),
('000706','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers, in consultation with associated security personnel (including security engineers), to implement a verifiable flaw remediation process to correct weaknesses and deficiencies identified during the security testing and evaluation process.',NULL,NULL,NULL),
('000707','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators, in consultation with associated security personnel (including security engineers), to implement a verifiable flaw remediation process to correct weaknesses and deficiencies identified during the security testing and evaluation process.',NULL,NULL,NULL),
('000708','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers, in consultation with associated security personnel (including security engineers), to document the results of the security testing/evaluation processes.',NULL,NULL,NULL),
('000709','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers, in consultation with associated security personnel (including security engineers), to document the results of the security flaw remediation processes.',NULL,NULL,NULL),
('000710','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators, in consultation with associated security personnel (including security engineers), to document the results of the security testing/evaluation processes.',NULL,NULL,NULL),
('000711','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators, in consultation with associated security personnel (including security engineers), to document the results of the security flaw remediation processes.',NULL,NULL,NULL),
('000712','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to employ code analysis tools to examine software for common flaws and document the results of the analysis.',NULL,NULL,NULL),
('000713','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to employ code analysis tools to examine software for common flaws and document the results of the analysis.',NULL,NULL,NULL),
('000714','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform a vulnerability analysis to document vulnerabilities.',NULL,NULL,NULL),
('000715','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform a vulnerability analysis to document exploitation potential.',NULL,NULL,NULL),
('000716','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers to perform a vulnerability analysis to document risk mitigations.',NULL,NULL,NULL),
('000717','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to perform a vulnerability analysis to document vulnerabilities.',NULL,NULL,NULL),
('000718','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to perform a vulnerability analysis to document exploitation potential.',NULL,NULL,NULL),
('000719','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators perform a vulnerability analysis to document risk mitigations.',NULL,NULL,NULL),
('000720','draft','2009-09-22','DISA FSO','policy','The organization requires information system developers implement the security test and evaluation plan under the witness of an independent verification and validation agent.',NULL,NULL,NULL),
('000721','draft','2009-09-22','DISA FSO','policy','The organization requires information system integrators to implement the security test and evaluation plan under the witness of an independent verification and validation agent.',NULL,NULL,NULL),
('000722','draft','2009-09-22','DISA FSO','policy','The organization defines the security safeguards to employ to protect against supply chain threats to the information system, system component, or information system service.','SA-12.1','DoD has defined the requirements to protect against supply chain threats in DoDI 5200.44, \"Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN).\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the requirements to protect against supply chain threats in DoDI 5200.44, \"Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN).\"'),
('000723','draft','2009-09-22','DISA FSO','policy','The organization protects against supply chain threats to the information system, system component, or information system service by employing organization-defined security safeguards as part of a comprehensive, defense-in-breadth information security strategy.','SA-12.2','The organization being inspected/assessed must identify and document in the Security Plan whether the system is a covered system IAW DoDI 5200.44. If it is a covered system, the organization must implement the requirements below:\n1. Conduct a criticality analysis to identify mission critical functions and critical components and reduce the vulnerability of such functions and components through secure system design;\n2. Request threat analysis of suppliers of critical components from the TSN focal point and manage access to and control of threat analysis products containing U.S. person information;\n3. Engage TSN focal points for guidance on managing identified risk using DoD Components and Enterprise risk management resources; and\n4. Apply TSN best practices, processes, techniques, and procurement tools prior to the acquisition of critical components or their integration into applicable systems, at any point in the system lifecycle. Such tools and practices include contract requirements and the SCRM key practices Guide.','The organization conducting the inspection/assessment obtains and examines the Security Plan for the system to determine whether the system is a covered system IAW DoDI 5200.44.\n\nIf it is a covered system, the organization conducting the inspection/assessment obtains and examines documentation of compliance with DoDI 5200.44, to ensure the organization being inspected/assessed has:\n1. Conducted a criticality analysis to identify mission critical functions and critical components and reduced the vulnerability of such functions and components through secure system design;\n2. Requested threat analysis of suppliers of critical components from the TSN focal point and managed access to and control of threat analysis products containing U.S. person information;\n3. Engaged TSN focal points for guidance on managing identified risk using DoD Components and Enterprise risk management resources; and\n4. Applied TSN best practices, processes, techniques, and procurement tools prior to the acquisition of critical components or their integration into applicable systems, at any point in the system lifecycle. Such tools and practices include contract requirements and the SCRM key practices Guide.'),
('000724','draft','2009-09-22','DISA FSO','policy','The organization purchases all anticipated information system components and spares in the initial acquisition.',NULL,NULL,NULL),
('000725','draft','2009-09-22','DISA FSO','policy','The organization conducts a due diligence review of suppliers prior to entering into contractual agreements to acquire information system hardware.',NULL,NULL,NULL),
('000726','draft','2009-09-22','DISA FSO','policy','The organization conducts a due diligence review of suppliers prior to entering into contractual agreements to acquire information system software.',NULL,NULL,NULL),
('000727','draft','2009-09-22','DISA FSO','policy','The organization conducts a due diligence review of suppliers prior to entering into contractual agreements to acquire information system firmware.',NULL,NULL,NULL),
('000728','draft','2009-09-22','DISA FSO','policy','The organization conducts a due diligence review of suppliers prior to entering into contractual agreements to acquire information system services.',NULL,NULL,NULL),
('000729','draft','2009-09-22','DISA FSO','policy','The organization uses trusted shipping for information systems.',NULL,NULL,NULL),
('000730','draft','2009-09-22','DISA FSO','policy','The organization uses trusted shipping for information system components.',NULL,NULL,NULL),
('000731','draft','2009-09-22','DISA FSO','policy','The organization uses trusted shipping for information technology products.',NULL,NULL,NULL),
('000732','draft','2009-09-22','DISA FSO','policy','The organization uses trusted warehousing for information systems.',NULL,NULL,NULL),
('000733','draft','2009-09-22','DISA FSO','policy','The organization uses trusted warehousing for information system components.',NULL,NULL,NULL),
('000734','draft','2009-09-22','DISA FSO','policy','The organization uses trusted warehousing for information technology products.',NULL,NULL,NULL),
('000735','draft','2009-09-22','DISA FSO','policy','The organization employs a diverse set of suppliers for information systems.',NULL,NULL,NULL),
('000736','draft','2009-09-22','DISA FSO','policy','The organization employs a diverse set of suppliers for information system components.',NULL,NULL,NULL),
('000737','draft','2009-09-22','DISA FSO','policy','The organization employs a diverse set of suppliers for information technology products.',NULL,NULL,NULL),
('000738','draft','2009-09-22','DISA FSO','policy','The organization employs a diverse set of suppliers for information system services.',NULL,NULL,NULL),
('000739','draft','2009-09-22','DISA FSO','policy','The organization employs standard configurations for information systems.',NULL,NULL,NULL),
('000740','draft','2009-09-22','DISA FSO','policy','The organization employs standard configurations for information system components.',NULL,NULL,NULL),
('000741','draft','2009-09-22','DISA FSO','policy','The organization employs standard configurations for information technology products.',NULL,NULL,NULL),
('000742','draft','2009-09-22','DISA FSO','policy','The organization minimizes the time between purchase decisions and delivery of information systems.',NULL,NULL,NULL),
('000743','draft','2009-09-22','DISA FSO','policy','The organization minimizes the time between purchase decisions and delivery of information system components.',NULL,NULL,NULL),
('000744','draft','2009-09-22','DISA FSO','policy','The organization minimizes the time between purchase decisions and delivery of information technology products.',NULL,NULL,NULL),
('000745','draft','2009-09-22','DISA FSO','policy','The organization employs independent analysis and penetration testing against delivered information systems.',NULL,NULL,NULL),
('000746','draft','2009-09-22','DISA FSO','policy','The organization employs independent analysis and penetration testing against delivered information system components.',NULL,NULL,NULL),
('000747','draft','2009-09-22','DISA FSO','policy','The organization employs independent analysis and penetration testing against delivered information technology products.',NULL,NULL,NULL),
('000748','draft','2009-09-22','DISA FSO','policy','The organization defines level of trustworthiness for the information system.',NULL,NULL,NULL),
('000749','draft','2009-09-22','DISA FSO','policy','The organization requires that the information system meets the organization-defined level of trustworthiness.',NULL,NULL,NULL),
('000750','draft','2009-09-22','DISA FSO','policy','The organization defines the list of critical information system components that require re-implementation.',NULL,NULL,NULL),
('000751','draft','2009-09-22','DISA FSO','policy','The organization determines the organization-defined list of critical information system components that require re-implementation.',NULL,NULL,NULL),
('000752','draft','2009-09-22','DISA FSO','policy','The organization re-implements organization-defined critical information system components.',NULL,NULL,NULL),
('000753','draft','2009-09-22','DISA FSO','policy','The organization identifies information system components for which alternative sourcing is not viable.',NULL,NULL,NULL),
('000754','draft','2009-09-22','DISA FSO','policy','The organization defines measures to be employed to prevent critical security controls for information system components from being compromised.',NULL,NULL,NULL),
('000755','draft','2009-09-22','DISA FSO','policy','The organization employs organization-defined measures to ensure critical security controls for the information system components are not compromised.',NULL,NULL,NULL),
('000756','draft','2009-09-17','DISA FSO','policy','The organization develops an identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','IA-1.2','DoD developed DoDI 8520.02 and DoDI 8520.03 as the identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 8520.02 and DoDI 8520.03.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.'),
('000757','draft','2009-09-17','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles an identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','IA-1.3','DoD disseminates the DoDI 8520.02 and DoDI 8520.03 via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) to the ISSO and ISSM and others as the local organization deems appropriate as an identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the personnel or roles to be recipients of the identification and authentication policy and the procedures as the ISSO and ISSM and others as the local organization deems appropriate.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the personnel or roles to be recipients of the identification and authentication policy and the procedures as the ISSO and ISSM and others as the local organization deems appropriate.'),
('000758','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates identification and authentication policy in accordance with the organization-defined frequency.','IA-1.6','DoD reviews and updates identification and authentication policy (DoDI 8520.02 and DoDI 8520.03) annually.\n\nDoD Components are automatically compliant with this CCI because they are covered at the DoD level policies, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('000759','draft','2009-09-17','DISA FSO','policy','The organization defines a frequency for reviewing and updating the identification and authentication policy.','IA-1.7','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('000760','draft','2009-09-17','DISA FSO','policy','The organization develops procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.','IA-1.4','DoD develops within DoDI 8520.02 and DoDI 8520.03, procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.'),
('000761','draft','2009-09-17','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.','IA-1.5','DoD disseminates the DoDI 8520.02 and DoDI 8520.03 to the ISSO and ISSM and others as the local organization deems appropriate via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html). DoDI 8520.02 and DoDI 8520.03 are procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 8520.02 and DoDI 8520.03.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the personnel or roles to be recipients of the identification and authentication policy and the procedures as the ISSO and ISSM and others as the local organization deems appropriate.'),
('000762','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates identification and authentication procedures in accordance with the organization-defined frequency.','IA-1.8','DoD reviews and updates identification and authentication procedures (DoDI 8520.02 and DoDI 8520.03) annually.\n\nThe organization being inspected/assessed is automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000763','draft','2009-09-17','DISA FSO','policy','The organization defines a frequency for reviewing and updating the identification and authentication procedures.','IA-1.9','DoD has defined the frequency as review annually - update as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as review annually - update as appropriate.'),
('000764','draft','2009-09-17','DISA FSO','technical','The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users).','IA-2.1','The organization being inspected/assessed configures the information system to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 764.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 764.'),
('000765','draft','2009-09-17','DISA FSO','technical','The information system implements multifactor authentication for network access to privileged accounts.','IA-2(1).1','The organization being inspected/assessed configures the information system to implement multifactor authentication for network access to privileged accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 765.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for network access to privileged accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 765.'),
('000766','draft','2009-09-17','DISA FSO','technical','The information system implements multifactor authentication for network access to non-privileged accounts.','IA-2(2).1','The organization being inspected/assessed configures the information system to implement multifactor authentication for network access to non-privileged accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 766.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for network access to non-privileged accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 766.'),
('000767','draft','2009-09-17','DISA FSO','technical','The information system implements multifactor authentication for local access to privileged accounts.','IA-2(3).1','The organization being inspected/assessed configures the information system to implement multifactor authentication for local access to privileged accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 767.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for local access to privileged accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 767.'),
('000768','draft','2009-09-17','DISA FSO','technical','The information system implements multifactor authentication for local access to non-privileged accounts.','IA-2(4).1','The organization being inspected/assessed configures the information system to implement multifactor authentication for local access to non-privileged accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 768.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for local access to non-privileged accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 768.'),
('000769','draft','2009-09-17','DISA FSO','policy','The organization allows the use of group authenticators only when used in conjunction with an individual/unique authenticator.',NULL,NULL,NULL),
('000770','draft','2009-09-17','DISA FSO','policy','The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed.','IA-2(5).1','The organization being inspected/assessed requires individuals or configures the information system to require individuals to be authenticated with an individual authenticator when a group authenticator is employed. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 770.','The organization conducting the inspection/assessment obtains and examines standard operating procedures or system documentation to ensure the organization being inspected/assessed requires individuals to be authenticated with an individual authenticator when a group authenticator is employed. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 770.'),
('000771','draft','2009-09-17','DISA FSO','technical','The information system uses multifactor authentication for network access to privileged accounts where one of the factors is provided by a device separate from the information system being accessed.',NULL,NULL,NULL),
('000772','draft','2009-09-17','DISA FSO','technical','The information system uses multifactor authentication for network access to non-privileged accounts where one of the factors is provided by a device separate from the information system being accessed.',NULL,NULL,NULL),
('000773','draft','2009-09-17','DISA FSO','policy','The organization defines replay-resistant authentication mechanisms to be used for network access to privileged accounts.',NULL,NULL,NULL),
('000774','draft','2009-09-17','DISA FSO','technical','The information system uses organization-defined replay-resistant authentication mechanisms for network access to privileged accounts.',NULL,NULL,NULL),
('000775','draft','2009-09-17','DISA FSO','policy','The organization defines replay-resistant authentication mechanisms to be used for network access to non-privileged accounts.',NULL,NULL,NULL),
('000776','draft','2009-09-17','DISA FSO','technical','The information system uses organization-defined replay-resistant authentication mechanisms for network access to non-privileged accounts.',NULL,NULL,NULL),
('000777','draft','2009-09-17','DISA FSO','policy','The organization defines a list of specific and/or types of devices for which identification and authentication is required before establishing a connection to the information system.','IA-3.1','DoD has defined the value as all mobile devices and network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the value as all mobile devices and network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs). '),
('000778','draft','2009-09-17','DISA FSO','technical','The information system uniquely identifies an organization-defined list of specific and/or types of devices before establishing a local, remote, or network connection.','IA-3.2','The organization being inspected/assessed configures the network infrastructure to identify all mobile devices and network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs) before establishing a local, remote, network connection. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 778. DoD has defined the value as all mobile devices and network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs). ','The organization conducting the inspection/assessment examine a sampling of the network infrastructure device configurations to ensure devices connecting to the infrastructure are uniquely identified. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 778.'),
('000779','draft','2009-09-17','DISA FSO','technical','The information system authenticates devices before establishing remote network connections using bidirectional authentication between devices that is cryptographically based.',NULL,NULL,NULL),
('000780','draft','2009-09-17','DISA FSO','technical','The information system authenticates devices before establishing wireless network connections using bidirectional authentication between devices that is cryptographically based.',NULL,NULL,NULL),
('000781','draft','2009-09-17','DISA FSO','technical','The information system authenticates devices before establishing network connections using bidirectional authentication between devices that is cryptographically based.',NULL,NULL,NULL),
('000782','draft','2009-09-17','DISA FSO','policy','The organization standardizes, with regard to dynamic address allocation, Dynamic Host Control Protocol (DHCP) lease information and the time assigned to DHCP-enabled devices.',NULL,NULL,NULL),
('000783','draft','2009-09-17','DISA FSO','technical','The organization audits lease information when assigned to a device.','IA-3(3).5','The organization being inspected/assessed configures the information system to record lease information in the audit log. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 783.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to record lease information in the audit log and examine the audit records to ensure the records have captured the appropriate information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 783.'),
('000784','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by receiving authorization from a designated organizational official to assign a user identifier.',NULL,NULL,NULL),
('000785','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by receiving authorization from a designated organizational official to assign a device identifier.',NULL,NULL,NULL),
('000786','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by selecting an identifier that uniquely identifies an individual.',NULL,NULL,NULL),
('000787','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by selecting an identifier that uniquely identifies a device.',NULL,NULL,NULL),
('000788','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by assigning the user identifier to the intended party.',NULL,NULL,NULL),
('000789','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by assigning the device identifier to the intended device.',NULL,NULL,NULL),
('000790','draft','2009-09-17','DISA FSO','policy','The organization defines a time period for which the reuse of user identifiers is prohibited.',NULL,NULL,NULL),
('000791','draft','2009-09-17','DISA FSO','policy','The organization defines a time period for which the reuse of device identifiers is prohibited.',NULL,NULL,NULL),
('000792','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by preventing reuse of user identifiers for an organization-defined time period.',NULL,NULL,NULL),
('000793','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers for users and devices by preventing reuse of device identifiers for an organization-defined time period.',NULL,NULL,NULL),
('000794','draft','2009-09-17','DISA FSO','policy','The organization defines a time period of inactivity after which the identifier is disabled.','IA-4.7','DoD has defined the time period as 35 days of inactivity.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 35 days of inactivity.'),
('000795','draft','2009-09-17','DISA FSO','policy','The organization manages information system identifiers by disabling the identifier after an organization-defined time period of inactivity.','IA-4.8','The organization being inspected/assessed configures the information system to disable identifiers after 35 days of inactivity. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 795. DoD has defined the time period as 35 days of inactivity.','The organization conducting the inspection/assessment examines the information system configuration to ensure that identifiers are disabled after 35 days of inactivity. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 795. DoD has defined the time period as 35 days of inactivity.'),
('000796','draft','2009-09-17','DISA FSO','policy','The organization prohibits the use of information system account identifiers that are the same as public identifiers for individual electronic mail accounts.','IA-4(1).1','The organization being inspected/assessed documents and implements a process to prohibit the use of information system account identifiers that are the same as public identifiers for individual electronic mail accounts.','The organization conducting the inspection/assessment obtains and examines documented process to ensure the organization being inspected/assessed prohibits the use of information system account identifiers that are the same as public identifiers for individual electronic mail accounts.'),
('000797','draft','2009-09-17','DISA FSO','policy','The organization requires that registration to receive a user ID and password include authorization by a supervisor.',NULL,NULL,NULL),
('000798','draft','2009-09-17','DISA FSO','policy','The organization requires that registration to receive a user ID and password be done in person before a designated registration authority.',NULL,NULL,NULL),
('000799','draft','2009-09-17','DISA FSO','policy','The organization requires multiple forms of certification of individual identification, such as documentary evidence or a combination of documents and biometrics, be presented to the registration authority.','IA-4(3).1','The organization being inspected/assessed documents and implements a process to require multiple forms of certification of individual identification, such as documentary evidence or a combination of documents and biometrics be presented to the registration authority.','The organization conducting the inspection/assessment obtains and examines the documented process and interviews personnel with identifier management responsibilities to ensure the organization being inspected/assessed requires multiple forms of certification of individual identification, such as documentary evidence or a combination of documents and biometrics be presented to the registration authority.'),
('000800','draft','2009-09-17','DISA FSO','policy','The organization defines characteristics for identifying individual status.','IA-4(4).1','DoD has defined the characteristics as contractor or government employee and by nationality. User identifiers will follow the same format as DoD user e-mail addresses (john.smith.ctr@army.mil or john.smith.uk@army.mil); - DoD user e-mail display names (e.g., John Smith, Contractor or John Smith, United Kingdom ); and - automated signature blocks (e.g., John Smith, Contractor, J-6K, Joint Staff or John Doe, Australia, LNO, Combatant Command). Contractors who are also foreign nationals are identified as both, e.g., john.smith.ctr.uk@army.mil','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the characteristics as contractor or government employee and by nationality. User identifiers will follow the same format as DoD user e-mail addresses (john.smith.ctr@army.mil or john.smith.uk@army.mil); - DoD user e-mail display names (e.g., John Smith, Contractor or John Smith, United Kingdom ); and - automated signature blocks (e.g., John Smith, Contractor, J-6K, Joint Staff or John Doe, Australia, LNO, Combatant Command). Contractors who are also foreign nationals are identified as both, e.g., john.smith.ctr.uk@army.mil'),
('000801','draft','2009-09-17','DISA FSO','policy','The organization manages individual identifiers by uniquely identifying each individual by organization-defined characteristics identifying individual status.',NULL,NULL,NULL),
('000802','draft','2009-09-17','DISA FSO','technical','The information system dynamically manages identifiers, attributes, and associated access authorizations.',NULL,NULL,NULL),
('000803','draft','2009-09-17','DISA FSO','technical','The information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.','IA-7.1','The organization being inspected/assessed configures the information system to implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 803.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 803.'),
('000804','draft','2009-09-17','DISA FSO','technical','The information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users).','IA-8.1','The organization being inspected/assessed configures the information system to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 804.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 804.'),
('000805','draft','2009-09-17','DISA FSO','policy','The organization develops and documents an incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','IR-1.3','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.'),
('000806','draft','2009-09-17','DISA FSO','policy','The organization disseminates an incident response policy to organization-defined personnel or roles.','IR-1.4','DoD disseminates via http://www.dtic.mil/cjcs_directives/, CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 to all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.'),
('000807','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates the current incident response policy in accordance with organization-defined frequency.','IR-1.7','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.'),
('000808','draft','2009-09-17','DISA FSO','policy','The organization defines the frequency with which to review and update the current incident response policy.','IR-1.8','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of issuance.'),
('000809','draft','2009-09-17','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the incident response policy and associated incident response controls.','IR-1.6','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meets the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.'),
('000810','draft','2009-09-17','DISA FSO','policy','The organization disseminates incident response procedures to organization-defined personnel or roles.','IR-1.5','DoD disseminates via http://www.dtic.mil/cjcs_directives/, CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 to all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.\n\nDoD has defined the roles as all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.\n\nDoD has defined the roles as all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.'),
('000811','draft','2009-09-17','DISA FSO','policy','The organization reviews and updates the current incident response procedures in accordance with organization-defined frequency.','IR-1.9','DoD (in conjunction with Joint Staff for CJCSIs) reviews and updates current incident response procedures (CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2) annually.\n\nDoD Components are automatically compliant with this CCI because they are covered at the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.','CJCSI 6510.01F \"Information Assurance and Support to Computer Network Defense,\" CJCSM 6510.01B, \"Cyber Incident Handling Program,\" DoDD O-8530.1, and DoDI O-8530.2 meet the DoD requirements for incident response policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered at the DoD level with the following policies: CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000812','draft','2009-09-17','DISA FSO','policy','The organization defines the frequency with which to review and update the current incident response procedures.','IR-1.10','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000813','draft','2009-09-17','DISA FSO','policy','The organization provides incident response training to information system users consistent with assigned roles and responsibilities within an organization-defined time period of assuming an incident response role or responsibility.','IR-2.1','The organization being inspected/assessed documents and implement a process to provide incident response training to information system users consistent with assigned roles and responsibilities within 30 working days of assuming an incident response role or responsibility. The organization must maintain a record of training. DoD has defined the time period as 30 working days.','The organization conducting the inspection/assessment obtains and examines the documented process as well as training records for a sampling of information system users to ensure the organization being inspected/assessed provides incident response training to information system users consistent with assigned roles and responsibilities within 30 working days of assuming an incident response role or responsibility. DoD has defined the time period as 30 working days.'),
('000814','draft','2009-09-17','DISA FSO','policy','The organization provides incident response training in accordance with organization-defined frequency.','IR-2.3','The organization being inspected/assessed documents and implements a process to provide incident response training to information system users, other than general users, consistent with assigned roles and responsibilities annually. For general users, DoD components are automatically compliant with the requirement based on DoDD 8570.01 requirements for IA awareness training. The organization must maintain a record of training. DoD has defined the frequency as annually. ','The organization conducting the inspection/assessment obtains and examines the documented process as well as training records for a sampling of information system users to ensure the organization being inspected/assessed provides incident response training to information system users, other than general users, consistent with assigned roles and responsibilities annually. For general users, DoD components are automatically compliant with the requirement based on DoDD 8570.01 requirements for IA awareness training. DoD has defined the frequency as annually.'),
('000815','draft','2009-09-17','DISA FSO','policy','The organization defines a frequency for incident response training.','IR-2.4','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000816','draft','2009-09-17','DISA FSO','policy','The organization incorporates simulated events into incident response training to facilitate effective response by personnel in crisis situations.','IR-2(1).1','The organization being inspected/assessed will document a process to include simulated events into incident response training to facilitate effective response by personnel in crisis situations. The process to include simulated events shall be documented IAW CJCSI 6510.01F, CJCSM 6510.01B, DoDD O-8530.1, and DoDI O-8530.2. The organization must maintain a record of incident response training to include simulated events.','The organization conducting the inspection/assessment obtains and examines incident response training materials and a record of training events to ensure that simulated events have been included.'),
('000817','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to provide a more thorough and realistic incident response training environment.','IR-2(2).1','The organization being inspected/assessed employs an automated mechanism such as scenario-based interactive online training/CBT providing a realistic incident response training environment.','The organization conducting the inspection/assessment obtains and examines the automated mechanism such as scenario-based interactive online training/CBT to verify that it provides a realistic incident response training environment.'),
('000818','draft','2009-09-17','DISA FSO','policy','The organization tests the incident response capability for the information system on an organization-defined frequency using organization-defined tests to determine the incident response effectiveness.','IR-3.1','The organization being inspected/assessed documents and implements a process to test its incident response capability for the information system at least every six months for high availability and at least annually for low/med availability using tests and as defined in the incident response plan. The organization must maintain a record of test results. DoD has defined the frequency as at least every six months for high availability and at least annually for low/med availability. DoD has defined the tests as tests as defined in the incident response plan.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of test results to ensure the organization being inspected/assessed tests its incident response capability for the information system at least every six months for high availability and at least annually for low/med availability using tests and as defined in the incident response plan. DoD has defined the frequency as at least every six months for high availability and at least annually for low/med availability. DoD has defined the tests as tests as defined in the incident response plan.'),
('000819','draft','2009-09-17','DISA FSO','policy','The organization defines a frequency for incident response tests.','IR-3.2','DoD has defined the frequency as at least every six months for high availability and at least annually for low/med availability.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least every six months for high availability and at least annually for low/med availability.'),
('000820','draft','2009-09-17','DISA FSO','policy','The organization defines tests for incident response.','IR-3.3','DoD has defined the tests as tests as defined in the incident response plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the tests as tests as defined in the incident response plan.'),
('000821','draft','2009-09-17','DISA FSO','policy','The organization employs automated mechanisms to more thoroughly and effectively test the incident response capability.','IR-3(1).1','The organization being inspected/assessed will identify and employ automated mechanisms to test the incident response capability for the information system.','The organization conducting the inspection/assessment obtains and examines the identified automated mechanisms in use to test the incident response capability for the information system.'),
('000822','draft','2009-09-18','DISA FSO','policy','The organization implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery.','IR-4.1','The organization being inspected/assessed must have a documented and certified CNDSP and documented procedures for information system users and site security personnel to handle incidents until they are transferred to the responsibility of the CNDSP. ','The organization conducting the inspection/assessment obtains and examines the documentation identifying the CNDSP leveraged as well as the documented procedures for incident handling to ensure that there is a certified CNDSP in use and that there are procedures implemented to handle incidents until they are transferred to the responsibility of the CNDSP. '),
('000823','draft','2009-09-18','DISA FSO','policy','The organization coordinates incident handling activities with contingency planning activities.','IR-4.2','The organization being inspected/assessed will coordinate the incident response plan (IR-8) and contingency plan (CP-2) to ensure they allow for an effective transfer of information system activity and maintain confidentiality and integrity of the contingency assets.','The organization conducting the inspection/assessment obtains and examines the incident response plan (IR-8) and contingency plan (CP-2) to ensure they allow for an effective transfer of information system activity and maintain confidentiality and integrity of the contingency assets.'),
('000824','draft','2009-09-18','DISA FSO','policy','The organization incorporates lessons learned from ongoing incident handling activities into incident response procedures, training, and testing/exercises.','IR-4.3','The organization being inspected/assessed will conduct after action reviews from incidents to identify lessons learned and will incorporate them into procedures, training, and testing/exercises. The organization must maintain records of after action reviews.','The organization conducting the inspection/assessment obtains and examines after action reports or meeting minutes to identify actionable lessons learned to verify that lessons learned are incorporated into the plan as changes are necessary.'),
('000825','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to support the incident handling process.','IR-4(1).1','The organization being inspected/assessed will document within their incident handling plan, procedures to leverage the Joint Incident Management System (JIMS). For the DoD, JIMS is the automated mechanism.','The organization conducting the inspection/assessment obtains and examines the incident handling plan to ensure that there are procedures identified to leverage the JIMS.'),
('000826','draft','2009-09-18','DISA FSO','policy','The organization includes dynamic reconfiguration of organization-defined information system components as part of the incident response capability.','IR-4(2).1','The organization being inspected/assessed will ensure that their incident response plan includes procedures for dynamic reconfiguration of information system components defined in IR-4 (2), CCI 2781 as part of the incident response capability IAW CM-3.\n\nDynamic reconfiguration bypasses the organization\'s standard CCB process and may include, for example, changes to router rules, access control lists, intrusion detection/prevention systems, firewalls, etc. Organizations will have procedures to examine dynamic reconfiguration changes at the earliest opportunity IAW CCB.','The organization conducting the inspection/assessment obtains and examines the incident response plan and verifies it has procedures addressing dynamic reconfiguration of information system components defined in IR-4 (2), CCI 2781 as part of the incident response capability IAW CM-3.'),
('000827','draft','2009-09-18','DISA FSO','policy','The organization defines and identifies classes of incidents for which organization-defined actions are to be taken to ensure continuation of organizational mission and business functions.','IR-4(3).1','CJCSM 6510.01B has already identified DoD\'s classes of incidents.\n\nDoD Components are automatically compliant with this CCI because DoD has defined the classes of incidents as classes of incidents defined in CJCSM 6510.01B Appendix A- Enclosure B.','CJCSM 6510.01B has already identified DoD\'s classes of incidents. The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the classes of incidents as classes of incidents defined in CJCSM 6510.01B Appendix A- Enclosure B.6510.01M'),
('000828','draft','2009-09-18','DISA FSO','policy','The organization defines and identifies actions to take in response to organization-defined classes of incidents to ensure continuation of organizational missions and business functions.','IR-4(3).2','CJCSM 6510.01B has already identified DoD\'s actions to take in response to classes of incidents.\n\nDoD Components are automatically compliant with this CCI because DoD has defined the actions as actions defined in CJCSM 6510.01B.','CJCSM 6510.01B has already identified DoD\'s actions to take in response to classes of incidents. The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the actions as actions defined in CJCSM 6510.01B.'),
('000829','draft','2009-09-18','DISA FSO','policy','The organization correlates incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response.','IR-4(4).1','The organization being inspected/assessed defines procedures to examine incident information gathered and the actual actions taken by both the individuals affected and the incident response personnel. These procedures shall be defined IAW CJCSM 6510.01B. The end goal is to achieve a top level perspective of the effectiveness of the incident response and awareness. ','The organization conducting the inspection/assessment obtains and examines proof of the analysis (such as minutes from an incident response after action meeting or other similar activity) to ensure that incident information is being examined and correlated. '),
('000830','draft','2009-09-18','DISA FSO','policy','The organization defines security violations that, if detected, initiate a configurable capability to automatically disable the information system.','IR-4(5).1','The organization being inspected/assessed defines and document a list of security violations that upon occurrence initiate an automated action to disable or shutdown the information system. Violations may be identified by specific activity or by class/type of activity. DoD has determined the security violations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the list of documented security violations to ensure the organization has clearly identified those violations that initiate an automated disabling or shut down of the information system. DoD has determined the security violations are not appropriate to define at the Enterprise level.'),
('000831','draft','2009-09-18','DISA FSO','technical','The organization implements a configurable capability to automatically disable the information system if organization-defined security violations are detected.','IR-4(5).2','The organization being inspected/assessed will clearly identify, document, and implement a configurable automated mechanism (or mechanisms) that utilizes the list of security violations identified in IR-4 (5), CCI 000830 to disable or shutdown the information system. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 831. ','The organization conducting the inspection/assessment examines the information system to ensure an automated mechanism is configured to disable or shutdown the information system based on the identified security violations (IR-4 (5), CCI 000830). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 831.'),
('000832','draft','2009-09-18','DISA FSO','policy','The organization tracks and documents information system security incidents.','IR-5.1','The organization being inspected/assessed will document within their incident handling plan, procedures to leverage the Joint Incident Management System (JIMS). For the DoD, JIMS is the automated mechanism. ','The organization conducting the inspection/assessment obtains and examines the incident handling plan to ensure that there are procedures identified to leverage the JIMS.'),
('000833','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to assist in the tracking of security incidents.','IR-5(1).1','The organization being inspected/assessed will document within their incident handling plan, procedures to leverage the Joint Incident Management System (JIMS). For the DoD, JIMS is the automated mechanism. ','The organization conducting the inspection/assessment obtains and examines the incident handling plan to ensure that there are procedures identified to leverage the JIMS.'),
('000834','draft','2009-09-18','DISA FSO','policy','The organization defines a time period for personnel to report suspected security incidents to the organizational incident response capability.','IR-6.1','DoD has defined the time period as the timeframes specified by CJCSM 6510.01B (Table C-A-1) unless the data owner provides more restrictive guidance. If organizations decide to be more restrictive than the guidance in the CJCSM, then they should address the more restrictive response time requirements in their incident response plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as the timeframes specified by CJCSM 6510.01B (Table C-A-1) unless the data owner provides more restrictive guidance. The organization conducting the inspection/assessment obtains and examines the incident response plan to determine if more stringent response time requirements have been identified.'),
('000835','draft','2009-09-18','DISA FSO','policy','The organization requires personnel to report suspected security incidents to the organizational incident response capability within the organization-defined time period.','IR-6.2','The organization being inspected/assessed documents within the user agreement the requirement for all system users to report suspected security incidents to the organizational incident response capability within the timeframes specified by CJCSM 6510.01B (Table C-A-1) unless the data owner provides more restrictive guidance. DoD has defined the time period as the timeframes specified by CJCSM 6510.01B (Table C-A-1) unless the data owner provides more restrictive guidance.','The organization conducting the inspection/assessment obtains and examines the user agreement to ensure users are required to report suspected security incidents to the organizational incident response capability within the timeframes specified by CJCSM 6510.01B (Table C-A-1) unless the data owner provides more restrictive guidance. DoD has defined the time period as the timeframes specified by CJCSM 6510.01B (Table C-A-1) unless the data owner provides more restrictive guidance.'),
('000836','draft','2009-09-18','DISA FSO','policy','The organization reports security incident information to organization-defined authorities.','IR-6.3','The organization being inspected/assessed documents and implements a process to report to the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT). Any security incidents IAW the incident response plan (IR-8). Reporting shall be conducted IAW CJCSM 6510.01B.\n\nDoD has defined the authorities as the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT).','The organization conducting the inspection/assessment obtains and examines a sample of previous security incidents to ensure the incidents were reported to the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT). Any security incidents IAW the incident response plan (IR-8). Reporting shall be conducted IAW CJCSM 6510.01B.\n\nDoD has defined the authorities as the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT).'),
('000837','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to assist in the reporting of security incidents.','IR-6(1).1','The organization being inspected/assessed will document within their incident handling plan, procedures to leverage the Joint Incident Management System (JIMS). For the DoD, JIMS is the automated mechanism. ','The organization conducting the inspection/assessment obtains and examines the incident handling plan to ensure that there are procedures identified to leverage the JIMS. '),
('000838','draft','2009-09-18','DISA FSO','policy','The organization reports information system vulnerabilities associated with reported security incidents to organization-defined personnel or roles.','IR-6(2).1','The organization being inspected/assessed documents and implements a process to report to personnel defined in IR-6 (2), CCI 2792 information system vulnerabilities associated with reported security incident IAW the incident response plan (IR-8). Reporting shall be conducted IAW CJCSM 6510.01B. ','The organization conducting the inspection/assessment obtains and examines a sample of previous security incidents to ensure the associated vulnerabilities were reported to personnel defined in IR-6 (2), CCI 2792 IAW the incident response plan (IR-8). Reporting shall be conducted IAW CJCSM 6510.01B.'),
('000839','draft','2009-09-18','DISA FSO','policy','The organization provides an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the information system for the handling and reporting of security incidents.','IR-7.1','The organization being inspected/assessed will establish an incident response support service, analogous to an IT help desk, to provide advice and assistance to users for handling and reporting of security incidents. ','The organization conducting the inspection/assessment will interview organizational users to determine awareness of incident response support services and quality of assistance of those services when used. If interviewing organizational users is not feasible, then review users manuals/documentation to ensures it identifies an incident response support service to contact.'),
('000840','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to increase the availability of incident response-related information and support.','IR-7(1).1','The organization being inspected/assessed will implement an automated intra-organization incident response information sharing capability to provide the following incident related information and support, for example:\n1. SOP for incident reporting\n2. Incident handling FAQ\n3. Current incident activity awareness information\n4. Incident response contact information\n5. Incident report submission','The organization conducting the inspection/assessment obtains and examines the incident response information sharing capability to validate the information sharing capability is available to organizational users.'),
('000841','draft','2009-09-18','DISA FSO','policy','The organization establishes a direct, cooperative relationship between its incident response capability and external providers of information system protection capability.','IR-7(2).1','The organization being inspected/assessed must establish a formal agreement with a computer network defense service provider (CNDSP). ','The organization conducting the inspection/assessment obtains and examines the formal agreement document between the organization and CNDSP to validate it is current and valid.'),
('000842','draft','2009-09-18','DISA FSO','policy','The organization identifies organizational incident response team members to the external providers.','IR-7(2).2','The organization being inspected/assessed must provide and update the list of internal incident response team members as necessary throughout the lifecycle of the CNDSP agreement, in conjunction with the CNDSP agreement.','The organization conducting the inspection/assessment obtains and examines the list of internal incident response team members to validate it is accurate and current. Interviews with CNDSP personnel and organizational incident response team members may also be conducted.'),
('000843','draft','2009-09-18','DISA FSO','policy','The organization develops an incident response plan that provides the organization with a roadmap for implementing its incident response capability; describes the structure and organization of the incident response capability; provides a high-level approach for how the incident response capability fits into the overall organization; meets the unique requirements of the organization, which relate to mission, size, structure, and functions; defines reportable incidents; provides metrics for measuring the incident response capability within the organization; and defines the resources and management support needed to effectively maintain and mature an incident response capability.',NULL,NULL,NULL),
('000844','draft','2009-09-18','DISA FSO','policy','The organization develops an incident response plan that is reviewed and approved by organization-defined personnel or roles.','IR-8.10','The organization being inspected/assessed will have an incident response plan signed and approved by at a minimum, the ISSM and ISSO. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.','The organization conducting the inspection/assessment obtains and examines the incident response plan to validate it has been properly signed by at a minimum, the ISSM and ISSO. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.'),
('000845','draft','2009-09-18','DISA FSO','policy','The organization defines incident response personnel (identified by name and/or by role) and organizational elements to whom copies of the incident response plan are distributed.','IR-8.11','DoD has defined the list as all stakeholders identified in the incident response plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the list as all stakeholders identified in the incident response plan.'),
('000846','draft','2009-09-18','DISA FSO','policy','The organization distributes copies of the incident response plan to organization-defined incident response personnel (identified by name and/or by role) and organizational elements.','IR-8.12','The organization being inspected/assessed makes available to all stakeholders identified in the incident response plan via organizationally approved information sharing mechanism. DoD has defined the list as all stakeholders identified in the incident response plan.','The organization conducting the inspection/assessment obtains and examines organizationally approved information sharing mechanism to validate all stakeholders identified in the incident response plan have adequate access to the incident response plan. DoD has defined the list as all stakeholders identified in the incident response plan.'),
('000847','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency for reviewing the incident response plan.','IR-8.13','DoD has defined the frequency as at least annually (incorporating lessons learned from past incidents).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually (incorporating lessons learned from past incidents).'),
('000848','draft','2009-09-18','DISA FSO','policy','The organization reviews the incident response plan on an organization-defined frequency.','IR-8.14','The organization being inspected/assessed will conduct reviews of its incident response plan at least annually. DoD has defined the frequency as at least annually (incorporating lessons learned from past incidents).','The organization conducting the inspection/assessment obtains and examines the incident response plan to validate it is current and has been reviewed within the last year. DoD has defined the frequency as at least annually (incorporating lessons learned from past incidents). '),
('000849','draft','2009-09-18','DISA FSO','policy','The organization updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing.','IR-8.15','The organization being inspected/assessed must update the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing and incorporate lessons learned from past incidents (IR-4a). The organization must document the update actions as an audit trail.','The organization conducting the inspection/assessment obtains and examines documentation of the update actions for the incident response plan to ensure the organization is updating the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing and incorporating lessons learned from past incidents (IR-4a).'),
('000850','draft','2009-09-18','DISA FSO','policy','The organization communicates incident response plan changes to organization-defined incident response personnel (identified by name and/or by role) and organizational elements.','IR-8.16','The organization being inspected/assessed communicates incident response plan changes to all stakeholders identified in the incident response plan, not later than 30 days after the change is made. DoD has defined the incident response personnel as all stakeholders identified in the incident response plan, not later than 30 days after the change is made.','The organization conducting the inspection/assessment examines the incident response plan via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been communicated to all stakeholders identified in the incident response plan, not later than 30 days after the change is made. DoD has defined the incident response personnel as all stakeholders identified in the incident response plan, not later than 30 days after the change is made.'),
('000851','draft','2009-09-18','DISA FSO','policy','The organization defines the frequency with which to review and update the current system maintenance policy.','MA-1.7','DoD has defined the frequency as every 5 years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 5 years.'),
('000852','draft','2009-09-18','DISA FSO','policy','The organization develops and documents a system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','MA-1.3','The organization being inspected/assessed develops and documents a system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','The organization conducting the inspection/assessment obtains and examines the documented maintenance policy to ensure the organization being inspected/assessed develops and documents a system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.'),
('000853','draft','2009-09-18','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles a system maintenance policy.','MA-1.4','The organization being inspected/assessed ensures the maintenance policy is disseminated to the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.\n\nDoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.','The organization conducting the inspection/assessment obtains and examines the maintenance policy via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated to the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.\n\nDoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.'),
('000854','draft','2009-09-18','DISA FSO','policy','The organization reviews and updates the current system maintenance policy in accordance with organization-defined frequency.','MA-1.8','The organization being inspected/assessed reviews the current system maintenance policy every 5 years and revises as necessary to comply with DoD regulations.\n\nThe organization must document each occurrence of the reviews and update actions as an audit trail.\n\nDoD has defined the frequency as every 5 years.','The organization conducting the inspection/assessment obtains and examines documentation of occurrence of reviews and update actions for the maintenance policy to ensure review is occurring every 5 years and updates are made as necessary.\n\nDoD has defined the frequency as every 5 years.'),
('000855','draft','2009-09-18','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls.','MA-1.5','The organization being inspected/assessed documents the maintenance procedures within the Security Plan. The maintenance procedures shall be developed IAW maintenance policy provided in DoDI 8500.01..','The organization conducting the inspection/assessment obtains and examines the Security Plan to ensure maintenance procedures are documented and are developed IAW maintenance policy provided in DoDI 8500.01..'),
('000856','draft','2009-09-18','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls.','MA-1.6','The organization being inspected/assessed ensures the maintenance procedures are disseminated to the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system via an information sharing capability. DoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.','The organization conducting the inspection/assessment examines the maintenance procedures via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated to the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system. DoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.'),
('000857','draft','2009-09-18','DISA FSO','policy','The organization reviews and updates the current system maintenance procedures in accordance with organization-defined frequency.','MA-1.9','The organization being inspected/assessed reviews the current system maintenance procedures annually and revises as needed to comply with DoD regulations. The organization must document each occurrence of the reviews and update actions as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines documentation of occurrence of reviews and update actions for the maintenance procedures to ensure annual review and necessary updates are occurring. DoD has defined the frequency as annually.'),
('000858','draft','2009-09-18','DISA FSO','policy','The organization schedules, performs, documents, and reviews records of maintenance and repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.',NULL,NULL,NULL),
('000859','draft','2009-09-18','DISA FSO','policy','The organization approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location.','MA-2.9','The organization being inspected/assessed approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location. The organization must maintain records of all approvals and monitoring activities.','The organization conducting the inspection/assessment obtains and examines records of all approvals and monitoring activities to ensure the organization being inspected/assessed approves and monitors all maintenance activities whether performed on site or remotely and whether the equipment is serviced on site or removed to another location.'),
('000860','draft','2009-09-18','DISA FSO','policy','The organization requires that organization-defined personnel or roles explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs.','MA-2.10','The organization being inspected/assessed documents within their risk management strategy personnel or roles defined in MA-2, CCI 2874 who must explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs. The organization must maintain written records of approval for the removal of the information system or system components from organizational facilities for off-site maintenance or repairs.','The organization conducting the inspection/assessment obtains and examines:\n1. the organization\'s risk management strategy to ensure the personnel or roles defined in MA-2, CCI 2874 have been designated to approve the removal of the information system or system components;\n2. and written records of approval for the removal of the information system or system components from organizational facilities for off-site maintenance or repairs to ensure the removal is explicitly approved.'),
('000861','draft','2009-09-18','DISA FSO','policy','The organization sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs.','MA-2.12','The organization being inspected/assessed sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs IAW DoDM 5200.01-V3 for classified media and DoDM 5200.01-V4 for unclassified media. The organization must maintain written records of media sanitization.','The organization conducting the inspection/assessment obtains and examines written records of media sanitization to ensure the organization sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs.'),
('000862','draft','2009-09-18','DISA FSO','policy','The organization checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions.','MA-2.13','The organization being inspected/assessed identifies and documents the impacted security controls and takes steps to verify that the controls are still functioning properly following maintenance or repair actions.','The organization conducting the inspection/assessment obtains and examines documented evidence of the verification of security controls following maintenance and repair actions to ensure that the organization being inspected/assessed checks all potentially impacted security controls to verify that they are still functioning properly.'),
('000863','draft','2009-09-18','DISA FSO','policy','The organization maintains maintenance records for the information system that include the date and time of maintenance, the name of the individual performing the maintenance, the name of escort, if necessary, a description of the maintenance performed, and a list of equipment removed or replaced (including identification numbers, if applicable).',NULL,NULL,NULL),
('000864','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to schedule, conduct, and document maintenance and repairs as required.',NULL,NULL,NULL),
('000865','draft','2009-09-18','DISA FSO','policy','The organization approves information system maintenance tools.','MA-3.1','The organization being inspected/assessed documents the approved maintenance tools within the Security Plan.','The organization conducting the inspection/assessment:\n1. obtains and examines the Security Plan to ensure the list of approved maintenance tools is documented;\n2. ensures only the approved maintenance tools are used within the system.'),
('000866','draft','2009-09-18','DISA FSO','policy','The organization controls information system maintenance tools.','MA-3.2','The organization being inspected/assessed controls information system maintenance tools that are approved IAW MA-3, CCI 865.','The organization conducting the inspection/assessment:\n1. obtains and examines the Security Plan to identify the list of approved maintenance tools;\n2. ensures the organization being inspected/assessed controls the approved information system maintenance tools.'),
('000867','draft','2009-09-18','DISA FSO','policy','The organization monitors information system maintenance tools.','MA-3.3','The organization being inspected/assessed develops and implements procedures to monitor the use of the approved information system maintenance tools IAW MA-3, CCI 865. Records of monitoring activity must be maintained.','The organization conducting the inspection/assessment obtains and examines:\n1. the Security Plan to identify the list of approved maintenance tools; and\n2. documented procedures to identify how the use of maintenance tools is monitored; and 3. reviews evidence that the monitoring is conducted IAW the documented procedures.'),
('000868','draft','2009-09-18','DISA FSO','policy','The organization maintains, on an ongoing basis, information system maintenance tools.',NULL,NULL,NULL),
('000869','draft','2009-09-18','DISA FSO','policy','The organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications.','MA-3(1).1','The organization being inspected/assessed documents the procedures for and implements inspections of the maintenances tools carried into a facility by maintenance personnel for improper or unauthorized modifications. Records of inspection must be maintained.','The organization conducting the inspection/assessment obtains and examines procedures for, and records of inspection of the maintenance tools carried into a facility by maintenance personnel to ensure the tools are inspected for improper or unauthorized modifications.'),
('000870','draft','2009-09-18','DISA FSO','policy','The organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system.','MA-3(2).1','The organization being inspected/assessed:\n1. documents and implements procedures to check all media containing diagnostic and test programs for malicious code before the media are used in the information system; and\n2. Runs an automated tool set to check all media containing diagnostic and test programs for malicious code before the media are used in the information system.\nThe organization must maintain configuration files for the automated tool set and audit logs of the tool set used to check media.','The organization conducting the inspection/assessment obtains and examines the procedures for checking all diagnostic and test media for malicious code, and a sampling of configuration files and audit logs of the tool set used to check media. The purpose of the review is to ensure the organization being inspected/assessed checks all media containing diagnostic and test programs for malicious code before the media are used in the information system.'),
('000871','draft','2009-09-18','DISA FSO','policy','The organization prevents the unauthorized removal of maintenance equipment containing organizational information by: (a) verifying that there is no organizational information contained on the equipment; (b) sanitizing or destroying the equipment; (c) retaining the equipment within the facility; or (d) obtaining an exemption from organization-defined personnel or roles explicitly authorizing removal of the equipment from the facility.','MA-3(3).1','The organization being inspected/assessed documents and implements a process to take one of the following actions before authorizing removal of information equipment from the facility:\n1. verify there is no organizational information contained on maintenance equipment;\n2. Sanitize or destroy the equipment;\n3. Retain the equipment within the facility; or\n4. Obtain an exemption from personnel or roles defined in MA-3 (3), CCI 2882 explicitly authorizing removal of the equipment from the facility.\nThe organization must maintain a record of maintenance equipment removal and actions taken.','The organization conducting the inspection/assessment obtains and examines the documented process and record of maintenance equipment removal to ensure the organization being inspected/assessed takes one of the four actions listed in the implementation guidance.'),
('000872','draft','2009-09-18','DISA FSO','policy','The organization employs automated mechanisms to restrict the use of maintenance tools to authorized personnel only.',NULL,NULL,NULL),
('000873','draft','2009-09-18','DISA FSO','policy','The organization approves nonlocal maintenance and diagnostic activities.','MA-4.1','The organization being inspected/assessed documents the procedures for approving non-local maintenance and diagnostic activities within the Security Plan. The organization must maintain records of approved non-local maintenance and diagnostic activities.','The organization conducting the inspection/assessment obtains and examines:\n1. the Security Plan to ensure the procedures for approving non-local maintenance and diagnostic activities are documented; and\n2. records approving non-local maintenance and diagnostic activities.'),
('000874','draft','2009-09-18','DISA FSO','policy','The organization monitors nonlocal maintenance and diagnostic activities.','MA-4.2','The organization being inspected/assessed develops and implements procedures to monitor non-local maintenance and diagnostic activities. Records of monitoring activity must be maintained.','The organization conducting the inspection/assessment obtains and examines:\n1. the Security Plan to identify the authorized non-local maintenance and diagnostic activities; and\n2. documented procedures to identify how the use of non-local maintenance and diagnostic activities are monitored; and\n3. reviews evidence that the monitoring is conducted IAW the documented procedures.'),
('000875','draft','2009-09-18','DISA FSO','policy','The organization controls non-local maintenance and diagnostic activities.',NULL,NULL,NULL),
('000876','draft','2009-09-18','DISA FSO','policy','The organization allows the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the information system.','MA-4.3','The organization being inspected/assessed:\n1. documents within the Security Plan the non-local maintenance and diagnostic tools that are allowed; and\n2. allows the use of non-local maintenance and diagnostic tools IAW the tools identified in the Security Plan and MA-4, CCI 873.','The organization conducting the inspection/assessment obtains and examines:\n1. the Security Plan to ensure non-local maintenance and diagnostic tools have been identified; and\n2. maintenance records to ensure only those tools allowed are used IAW MA-4, CCI 873.'),
('000877','draft','2009-09-18','DISA FSO','technical','The organization employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.','MA-4.4','The organization being inspected/assessed configures the information system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 877.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 877.'),
('000878','draft','2009-09-18','DISA FSO','policy','The organization maintains records for nonlocal maintenance and diagnostic activities.','MA-4.5','The organization being inspected/assessed maintains records of authorized non-local maintenance and diagnostic activities.','The organization conducting the inspection/assessment obtains records of authorized non-local maintenance and diagnostic activities, and examines a sampling to verify the organization is maintaining records for all non-local maintenance and diagnostic activities.'),
('000879','draft','2009-09-18','DISA FSO','technical','The organization terminates sessions and network connections when nonlocal maintenance is completed.','MA-4.6','The organization being inspected/assessed terminates session and network connections when non-local maintenance is completed. The organization must retain audit logs of session and network connections termination for non-local maintenance.','The organization conducting the inspection/assessment obtains and examines audit logs of session and network connections termination for non-local maintenance to ensure session and network connections are terminated when non-local maintenance is completed.'),
('000880','draft','2009-09-18','DISA FSO','technical','The organization audits non-local maintenance and diagnostic sessions.',NULL,NULL,NULL),
('000881','draft','2009-09-18','DISA FSO','policy','The organization documents, in the security plan for the information system, the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections.','MA-4(2).1','The organization being inspected/assessed documents within the Security Plan the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections.','The organization conducting the inspection/assessment obtains and examines the Security Plan to ensure the plan identifies the establishment and use of non-local maintenance and diagnostic connections.'),
('000882','draft','2009-09-18','DISA FSO','policy','The organization requires that nonlocal maintenance and diagnostic services be performed from an information system that implements a security capability comparable to the capability implemented on the system being serviced.','MA-4(3).1','The organization being inspected/assessed clearly defines in its contracts and/or service level agreements the requirement that any IS used to conduct non-local maintenance and diagnostic services will have a security level at least as high as the security level implemented on the IS being serviced. Alternatively, the organization being inspected/assessed complies with MA-4 (3) CCIs 883 and 1631.','The organization conducting the inspection/assessment obtains and examines contracts and/or service level agreements for all non-local maintenance and diagnostic services to ensure that any IS used for those services is required to have security level at least as high as the security level implemented on the IS being serviced. Alternatively, the organization conducting the inspection/assessment ensures the organization being inspected/assessed complies with MA-4 (3) CCIs 883 and 1631.'),
('000883','draft','2009-09-18','DISA FSO','policy','The organization removes the component to be serviced from the information system and prior to nonlocal maintenance or diagnostic services, sanitizes the component (with regard to organizational information) before removal from organizational facilities.','MA-4(3).2','The organization being inspected/assessed removes the component to be serviced from the information system and prior to non-local maintenance or diagnostic services, sanitizes the component (with regard to organizational information) before removal from organizational facilities. Alternatively, the organization being inspected/assessed complies with MA-4 (3) CCI 882.','The organization conducting the inspection/assessment obtains and examines maintenance procedures for all non-local maintenance and diagnostic services to ensure that the organization being inspected/assessed sanitizes components before removal from organizational facilities. Alternatively, the organization conducting the inspection/assessment ensures the organization being inspected/assessed complies with MA-4 (3) CCI 882.'),
('000884','draft','2009-09-18','DISA FSO','technical','The organization protects nonlocal maintenance sessions by employing organization-defined authenticators that are replay resistant.','MA-4(4).1','The organization being inspected/assessed configures the information system to protect nonlocal maintenance sessions by employing authenticators defined in MA-4 (4), CCI 2887 that are replay resistant. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 884.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect nonlocal maintenance sessions by employing authenticators defined in MA-4 (4), CCI 2887 that are replay resistant. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 884.'),
('000885','draft','2009-09-18','DISA FSO','policy','The organization requires that maintenance personnel notify organization-defined personnel when non-local maintenance is planned (i.e., date/time).',NULL,NULL,NULL),
('000886','draft','2009-09-18','DISA FSO','policy','The organization defines the personnel or roles to be notified of the date and time of planned nonlocal maintenance.','MA-4(5).3','DoD has defined the personnel or roles as the user base which could be impacted by the maintenance event.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the user base which could be impacted by the maintenance event.'),
('000887','draft','2009-09-18','DISA FSO','policy','The organization requires the approval of each nonlocal maintenance session by organization-defined personnel or roles.','MA-4(5).1','The organization being inspected/assessed defines within their maintenance procedures a process for the ISSO to approve the non-local maintenance. Written approval must be maintained. DoD has defined the personnel or roles as the ISSO.','The organization conducting the inspection/assessment obtains and examines the maintenance procedures and historical approvals to ensure that the ISSO approves the non-local maintenance. DoD has defined the personnel or roles as the ISSO.'),
('000888','draft','2009-09-18','DISA FSO','technical','The organization employs cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications.',NULL,NULL,NULL),
('000889','draft','2009-09-18','DISA FSO','policy','The organization employs remote disconnect verification at the termination of non-local maintenance and diagnostic sessions.',NULL,NULL,NULL),
('000890','draft','2009-09-18','DISA FSO','policy','The organization establishes a process for maintenance personnel authorization.','MA-5.1','The organization being inspected/assessed clearly defines, documents, and establishes a process for the authorization of maintenance personnel.','The organization conducting the inspection/assessment obtains and examines procedures addressing maintenance personnel to ensure that the organization being inspected/assessed has established processes for the authorization of maintenance personnel.'),
('000891','draft','2009-09-18','DISA FSO','policy','The organization maintains a list of authorized maintenance organizations or personnel.','MA-5.2','The organization being inspected/assessed maintains a current list of authorized maintenance organizations or personnel.','The organization conducting the inspection/assessment obtains and examines the current list of authorized maintenance organizations or personnel to ensure the organization being inspected/assessed is maintaining the list.'),
('000892','draft','2009-09-18','DISA FSO','policy','The organization ensures that personnel performing maintenance on the information system have required access authorizations or designates organizational personnel with required access authorizations and technical competence deemed necessary to supervise information system maintenance.',NULL,NULL,NULL),
('000893','draft','2009-09-18','DISA FSO','policy','The organization implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens.','MA-5(1).1','The organization being inspected/assessed documents and implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. Citizens in the procedures documented IAW MA-5, CCI 890.','The organization conducting the inspection/assessment obtains and examines the procedures identified in MA-5, CCI 890 to ensure it includes specific procedures for maintenance personnel that lack appropriate security clearances or are not U.S. citizens.'),
('000894','draft','2009-09-18','DISA FSO','policy','The organization requires maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals to be escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified.','MA-5(1).2','The organization being inspected/assessed requires maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals to be escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified. The organization must maintain records of maintenance personnel who access the system including information on escorts.','The organization conducting the inspection/assessment obtains and examines the records of maintenance personnel who access the system to ensure the organization being inspected/assessed requires maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals to be escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified.'),
('000895','draft','2009-09-18','DISA FSO','policy','The organization requires that, prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the information system be sanitized and all nonvolatile storage media be removed or physically disconnected from the system and secured.','MA-5(1).3','The organization being inspected/assessed documents and implements a process to sanitize, remove, or physically disconnect all nonvolatile storage media from the system prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed sanitizes, removes, or physically disconnects all nonvolatile storage media from the system prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals.'),
('000896','draft','2009-09-18','DISA FSO','policy','The organization requires that in the event an information system component cannot be sanitized, the procedures contained in the security plan for the system be enforced.',NULL,NULL,NULL),
('000897','draft','2009-09-18','DISA FSO','policy','The organization ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for all compartments of information on the system.','MA-5(2).1','The organization being inspected/assessed documents and implements a process to ensure that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for all compartments of information on the system.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for all compartments of information on the system.'),
('000898','draft','2009-09-18','DISA FSO','policy','The organization ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information are U.S. citizens.','MA-5(3).1','The organization being inspected/assessed documents and implements a process to ensure that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information are U.S. citizens.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that personnel performing maintenance and diagnostic activities on an information system processing, storing, or transmitting classified information are U.S. citizens.'),
('000899','draft','2009-09-18','DISA FSO','policy','The organization ensures that cleared foreign nationals (i.e., foreign nationals with appropriate security clearances) are used to conduct maintenance and diagnostic activities on classified information systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments.','MA-5(4).1','The organization being inspected/assessed documents and implements a process to ensure that cleared foreign nationals (i.e., foreign nationals with appropriate security clearances), are used to conduct maintenance and diagnostic activities on classified information systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that cleared foreign nationals (i.e., foreign nationals with appropriate security clearances), are used to conduct maintenance and diagnostic activities on classified information systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments.'),
('000900','draft','2009-09-18','DISA FSO','policy','The organization ensures that approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified information systems are fully documented within Memoranda of Agreements.','MA-5(4).2','The organization being inspected/assessed documents and implements a process to ensure that approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified information systems are fully documented within Memorandum of Agreements.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified information systems are fully documented within Memorandum of Agreements.'),
('000901','draft','2009-09-18','DISA FSO','policy','The organization defines a list of security-critical information system components and/or key information technology components for which it will obtain maintenance support and/or spare parts.',NULL,NULL,NULL),
('000902','draft','2009-09-18','DISA FSO','policy','The organization defines a time period for obtaining maintenance support and/or spare parts for security-critical information system components and/or key information technology components.',NULL,NULL,NULL),
('000903','draft','2009-09-18','DISA FSO','policy','The organization obtains maintenance support and/or spare parts for organization-defined information system components within an organization-defined time period of failure.','MA-6.1','The organization being inspected/assessed obtains maintenance support and/or spare parts for information system components defined in MA-6, CCI 2896 within 24 hours (Low and Moderate Availability) or immediately upon failure for (High Availability). DoD has defined the time period as within 24 hours (Low and Moderate Availability) or immediately upon failure for (High Availability). ','The organization conducting the inspection/assessment obtains evidence that maintenance support is available for information system components defined in MA-6, CCI 2896 and that the support will be provided within 24 hours (Low and Moderate Availability) or immediately upon failure for (High Availability). Evidence can include maintenance support contracts, inventories of spare parts, etc. DoD has defined the time period as within 24 hours (Low and Moderate Availability) or immediately upon failure for (High Availability). '),
('000904','draft','2009-09-21','DISA FSO','policy','The organization develops and documents a physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PE-1.3','DoDI 5200.08 and DoD 5200.08-R meet the requirement for Physical and Environmental Policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.','DoDI 5200.08 and DoD 5200.08-R meet the requirement for Physical and Environmental Policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.'),
('000905','draft','2009-09-21','DISA FSO','policy','The organization disseminates a physical and environmental protection policy to organization-defined personnel or roles.','PE-1.4','DoD disseminates DoDI 5200.08 and DoD 5200.08-R organization-wide via the DoD Issuances website.\nhttp://www.dtic.mil/whs/directives/corres/dir.html\n\nDoD has defined the personnel or roles as organizational personnel with physical and environmental protection responsibilities.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 5200.08 and DoD 5200.08-R\n\nDoD has defined the personnel or roles as organizational personnel with physical and environmental protection responsibilities.'),
('000906','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current physical and environmental protection policy in accordance with organization-defined frequency.','PE-1.7','DoDI 5200.08 and DoD 5200.08-R meet the requirement for Physical and Environmental Policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','DoDI 5200.08 and DoD 5200.08-R meet the requirement for Physical and Environmental Policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('000907','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review and update the physical and environmental protection policy.','PE-1.8','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('000908','draft','2009-09-21','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls.','PE-1.5','DoDI 5200.08 and DoD 5200.08-R meet the requirement for Physical and Environmental Policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.'),
('000909','draft','2009-09-21','DISA FSO','policy','The organization disseminates physical and environmental protection procedures to organization-defined personnel or roles.','PE-1.6','DoD disseminates DoDI 5200.08 and DoD 5200.08-R organization-wide via the DoD Issuances website.\nhttp://www.dtic.mil/whs/directives/corres/dir.html\n\nDoD has defined the personnel or roles as organizational personnel with physical and environmental protection responsibilities.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 5200.08 and DoD 5200.08-R\n\nDoD has defined the personnel or roles as organizational personnel with physical and environmental protection responsibilities.'),
('000910','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current physical and environmental protection procedures in accordance with organization-defined frequency.','PE-1.9','DoDI 5200.08 and DoD 5200.08-R meet the requirement for Physical and Environmental Policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.08 and DoD 5200.08-R.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000911','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review and update the physical and environmental protection procedures.','PE-1.10','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('000912','draft','2009-09-21','DISA FSO','policy','The organization develops a list of individuals with authorized access to the facility where the information system resides.','PE-2.1','The organization being inspected/assessed will develop and maintain a list of personnel with authorized access to the facilities where information systems reside. The organization will also take action to identify and officially designate its publicly accessible areas where access authorization is not required.','The organization conducting the inspection/assessment obtains and examines the list of personnel with authorized access to facilities where information systems reside to ensure it is current within every 90 days. The review process should also determine if the organization has identified and officially designated its publicly accessible areas where access authorization is not required. DoD has defined the frequency as every 90 days.'),
('000913','draft','2009-09-21','DISA FSO','policy','The organization issues authorization credentials for facility access.','PE-2.4','The organization being inspected/assessed utilizes the list of personnel with authorized access (IAW PE-2, CCI-000912) and issues credentials accordingly. The organization must document the credential issuing activity as an audit trail.','The organization conducting the inspection/assessment obtains and examines documentation of credential issuing activities to ensure credentials are issued to personnel with authorized access.'),
('000914','draft','2009-09-21','DISA FSO','policy','The organization reviews the access list detailing authorized facility access by individuals in accordance with organization-defined frequency.','PE-2.5','The organization being inspected/assessed will review the access list and authorization credentials every 90 days and document these review and approval actions as an audit trail. DoD has defined the frequency as every 90 days.','The organization conducting the inspection/assessment obtains and examines the audit records of the review actions to ensure that reviews are conducted every 90 days. DoD has defined the frequency as every 90 days.'),
('000915','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review the access list detailing authorized facility access by individuals.','PE-2.6','DoD has defined the frequency as every 90 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 90 days.'),
('000916','draft','2009-09-21','DISA FSO','policy','The organization authorizes physical access to the facility where the information system resides based on position or role.','PE-2(1).1','The organization being inspected/assessed must:\n1. Develop and document a list of roles or positions that have access to the facility where the information system resides.\n2. Identify and document personnel assigned to those roles.\n3. Authorize and document access to the facility to personnel in identified roles','The organization conducting the inspection/assessment obtains and examines:\n1. The list of roles or positions that have access to the facility where the information system resides.\n2. The list of personnel assigned to those roles\nRecommended:\n3. Access logs to verify access to the facility was authorized based on the appropriate roles and positions'),
('000917','draft','2009-09-21','DISA FSO','policy','The organization requires two forms of identification from an organization-defined list of acceptable forms of identification for visitor access to the facility where the information system resides.','PE-2(2).1','The organization being inspected/assessed will only grant access to the facility with two organization approved government issued forms of identification defined in PE-2 (2), CCI 2912. This requirement must be documented within the organization\'s physical security policy. The organization must maintain access control documentation as an auditable event per AU-2, CCI 000123.','The organization conducting the inspection/assessment obtains and examines the inspected organization\'s physical security policy for requirements and implementation guidance to have two forms of identification defined in PE-2 (2), CCI 2912 and physical access control logs or records; and any other relevant documents or records to validate compliance.'),
('000918','draft','2009-09-21','DISA FSO','policy','The organization restricts physical access to the facility containing an information system that processes classified information to authorized personnel with appropriate clearances and access authorizations.',NULL,NULL,NULL),
('000919','draft','2009-09-21','DISA FSO','policy','The organization enforces physical access authorizations at organization-defined entry/exit points to the facility where the information system resides.','PE-3.1','The organization being inspected/assessed will implement physical access authorizations at entry/exit points defined in PE-3, CCI 2915 and secure those physical access points (i.e. doors and/or windows) that are not intended for normal access.','The organization conducting the inspection/assessment performs a physical inspection of facility entry/exit points defined in PE-3, CCI 2915 to ensure that either physical access authorization controls are in place for those access points considered normal access points or are properly secured. Physical access points that are not documented or are not secured would be a failure of this control.'),
('000920','draft','2009-09-21','DISA FSO','policy','The organization verifies individual access authorizations before granting access to the facility.','PE-3.3','The organization being inspected/assessed verifies and grants access to facilities based upon individual access authorizations.','The organization conducting the inspection/assessment obtains and examines the access authorization list of personnel that have access to the facility (per access list implemented through PE-2, CCI 000912) where the information system resides. Inspect selected facilities to confirm the inspected organization is granting access at all physical access points to only authorized personnel.'),
('000921','draft','2009-09-21','DISA FSO','policy','The organization controls ingress/egress to the facility where the information system resides using one or more organization-defined physical access control systems/devices or guards.','PE-3.4','The organization being inspected/assessed will control ingress/egress to the facility using the physical access control devices and/or guards defined in PE-3, CCI 2916.','The organization conducting the inspection/assessment obtains and examines the list of physical access control devices and/or guards in use defined in PE-3, CCI 2916 and conducts random inspections of entry points. The purpose is to determine whether the organization is using those physical access devices and/or guards to control entry of personnel into the facility hosting the information system.'),
('000922','draft','2009-09-21','DISA FSO','policy','The organization controls access to areas officially designated as publicly accessible in accordance with the organization^s assessment of risk.',NULL,NULL,NULL),
('000923','draft','2009-09-21','DISA FSO','policy','The organization secures keys, combinations, and other physical access devices.','PE-3.14','The organization being inspected/assessed will secure as appropriate (in safes or secure containers) items used for physical access control such as keys, combinations, portable locks, etc. Fixed access control devices such as card readers, installed locks, key pads, etc. should be protected from tampering.','The organization conducting the inspection/assessment conducts physical inspections and interviews physical security/safety personnel to validate the organization has taken the proper precautions, and established the proper procedures to ensure it has adequately secured its keys, combinations, and other physical devices.'),
('000924','draft','2009-09-21','DISA FSO','policy','The organization inventories organization-defined physical access devices on an organization-defined frequency.','PE-3.15','The organization being inspected/assessed conducts and documents an inventory of minimally keys or any other physical token used to gain access annually. Inventory documents must be retained for at least one year beyond the completion of the next inventory. DoD has defined the frequency as annually. DoD has defined the physical access devices as minimally keys or any other physical token used to gain access.','The organization conducting the inspection/assessment obtains and examines the records of inventory of minimally keys or any other physical token used to gain access to ensure the inventory is being conducted annually.\n\nDoD has defined the frequency as annually.\n\nDoD has defined the physical access devices as minimally keys or any other physical token used to gain access.'),
('000925','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency for conducting inventories of organization-defined physical access devices.','PE-3.16','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000926','draft','2009-09-21','DISA FSO','policy','The organization changes combinations and keys in accordance with organization-defined frequency and/or when keys are lost, combinations are compromised, or individuals are transferred or terminated.','PE-3.18','The organization being inspected/assessed will document each occurrence of these change actions, with the reason for the action, as an audit trail for future reference. DoD has defined the frequency as required by security relevant events.','The organization conducting the inspection/assessment obtains and examines documentation of these change actions to validate the organization is changing its keys and combinations upon occurrence of security relevant events and when keys are lost, combinations are compromised, or individuals are transferred or terminated. DoD has defined the frequency as required by security relevant events.'),
('000927','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for changing combinations and keys.','PE-3.19','DoD has defined the frequency as required by security relevant event.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as required by security relevant event.'),
('000928','draft','2009-09-21','DISA FSO','policy','The organization enforces physical access authorizations to the information system in addition to the physical access controls for the facility where the information system resides at organization-defined physical spaces containing one or more components of the information system.','PE-3(1).1','The organization being inspected/assessed will provide documentation of additional physical access authorizations for the facility/facilities at physical spaces containing one or more components of the information system defined in PE-3 (1), CCI 2926. The organization will ensure that these controls are separate from, and independent of, the physical access controls established for the facility.','The organization conducting the inspection/assessment obtains and examines the documented list of additional physical access authorizations for the facility/facilities at physical spaces containing one or more components of the information system. The objective of the examination is to determine if the organization is enforcing additional physical access authorizations to areas of the facility at physical spaces containing one or more components of the information system defined in PE-3 (1), CCI 2926. These controls are independent of the physical access controls established for the facility.'),
('000929','draft','2009-09-21','DISA FSO','policy','The organization performs security checks in accordance with organization-defined frequency at the physical boundary of the facility or information system for unauthorized exfiltration of information or removal of information system components.','PE-3(2).1','The organization being inspected/assessed documents and implements procedures to perform security checks at the physical boundary of the facility or information system at a minimum, annually. The organization must maintain an audit trail of security checks at the physical boundary. DoD has defined the frequency as at a minimum, annually.','The organization conducting the inspection/assessment obtains and examines the documented procedures as well as the audit trail of security checks at the physical boundary to ensure the organization being inspected/assessed performs security checks at the physical boundary of the facility or information system at a minimum, annually.\n\nDoD has defined the frequency as at a minimum, annually.'),
('000930','draft','2009-09-21','DISA FSO','policy','The organization employs guards and/or alarms to monitor every physical access point to the facility where the information system resides 24 hours per day, 7 days per week.','PE-3(3).1','The organization being inspected/assessed employs guards and/or alarms to monitor every physical access point to the facility where the information system resides 24 hours per day, 7 days per week. The organization must create and maintain a list of guards or alarms for every physical access point to the facility where the information system resides 24 hours per day, 7 days per week.','The organization conducting the inspection/assessment obtains the list of guards or alarms for every physical access point to the facility where the information system resides and visually verifies a sampling of access points to ensure the appropriate guard or alarm to monitor is in place 24 hours per day, 7 days per week.'),
('000931','draft','2009-09-21','DISA FSO','policy','The organization uses lockable physical casings to protect organization-defined information system components from unauthorized physical access.','PE-3(4).1','The organization being inspected/assessed will deploy and install lockable physical casings designed to protect organization-defined information system components from unauthorized physical access.','The organization conducting the inspection/assessment performs a sample inspection of the lockable physical casings. The objective of the reviews is to validate the organization is using lockable physical casings to protect organization-defined information system components from unauthorized physical access.'),
('000932','draft','2009-09-21','DISA FSO','policy','The organization defines information system components to be protected from unauthorized physical access using lockable physical casings.','PE-3(4).2','The organization being inspected/assessed defines and documents information system components to be protected from unauthorized physical access using lockable physical casings.\n\nDoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines information system components to be protected from unauthorized physical access using lockable physical casings.\n\nDoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('000933','draft','2009-09-21','DISA FSO','policy','The organization employs organization-defined security safeguards to deter and/or prevent physical tampering or alteration of organization-defined hardware components within the information system.','PE-3(5).1','The organization being inspected/assessed employs security safeguards defined in PE-3 (5), CCI 2928 to deter and or prevent physical tampering or alteration of hardware components defined in PE-3 (5), CCI 2929 within the information system.','The organization conducting the inspection/assessment inspects the information system to ensure the organization being inspected/assessed employs security safeguards defined in PE-3 (5), CCI 2928 to deter and or prevent physical tampering or alteration of hardware components defined in PE-3 (5), CCI 2929 within the information system.'),
('000934','draft','2009-09-21','DISA FSO','policy','The organization employs a penetration testing process that includes unannounced attempts to bypass or circumvent security controls associated with physical access points to the facility on an organization-defined frequency.','PE-3(6).1','The organization being inspected/assessed executes a penetration testing process annually, that includes unannounced attempts, as defined in its physical security assessment plan for testing effectiveness of security controls in place for physical access points to the facility. Results of all penetration testing will be documented as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the inspected organization\'s physical security assessment plan and reviews documented results to ensure annual penetration testing of physical access points occurred. DoD has defined the frequency as annually.'),
('000935','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of unannounced attempts to be included in a penetration testing process to bypass or circumvent security controls associated with physical access points to the facility.','PE-3(6).2','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('000936','draft','2009-09-21','DISA FSO','policy','The organization controls physical access to organization-defined information system distribution and transmission lines within organizational facilities using organization-defined security safeguards.','PE-4.1','The organization being inspected/assessed controls physical access to information system distribution and transmission lines defined in PE-4, CCI 2930 within organizational facilities using security safeguards defined in PE-4, CCI 2931.','The organization conducting the inspection/assessment inspects the information system distribution and transmission lines defined in PE-4, CCI 2930 to ensure the security safeguards defined in PE-4, CCI 2931 are in place.'),
('000937','draft','2009-09-21','DISA FSO','policy','The organization controls physical access to information system output devices to prevent unauthorized individuals from obtaining the output.','PE-5.1','The organization being inspected/assessed will identify, document, and execute any additional access controls required for output devices above and beyond physical access controls already in place for the facility IAW DoD 5200.08-R and DoD 5200.01-M (Volumes 1-4).','The organization conducting the inspection/assessment obtains and examines the list of additional access controls for output devices. Physical inspection is required to ensure these access controls are properly implemented.'),
('000938','draft','2009-09-21','DISA FSO','policy','The organization monitors physical access to the information system to detect and respond to physical security incidents.',NULL,NULL,NULL),
('000939','draft','2009-09-21','DISA FSO','policy','The organization reviews physical access logs in accordance with organization-defined frequency.','PE-6.4','The organization being inspected/assessed will review physical access logs every 30 days. The organization must document each occurrence the physical access log review, with results of any necessary incident analysis and action taken, as an audit trail for future reference. DoD has defined the frequency as every 30 days.','The organization conducting the inspection/assessment obtains and examines the inspected organization\'s physical access logs or records; physical access incident reports; and any other relevant documents or records. The purpose of the reviews is to determine if the organization is conducting reviews of the physical access logs every 30 days. DoD has defined the frequency as every 30 days.'),
('000940','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for reviewing physical access logs.','PE-6.5','DoD has defined the frequency as every 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 30 days.'),
('000941','draft','2009-09-21','DISA FSO','policy','The organization coordinates results of reviews and investigations with the organization^s incident response capability.','PE-6.6','The organization being inspected/assessed will coordinate the results of reviews and investigations of physical security incidents with the organization\'s incident response capability (for physical security incidents).','The organization conducting the inspection/assessment obtains and examines documentation of physical security incidents to ensure coordination with the inspected organization\'s incident response capability occurred.'),
('000942','draft','2009-09-21','DISA FSO','policy','The organization monitors physical intrusion alarms and surveillance equipment.','PE-6(1).1','The organization being inspected/assessed will actively monitor physical intrusion alarms and surveillance equipment.','The organization conducting the inspection/assessment will observe and interview security personnel conducting monitoring activities to validate the organization is actively monitoring all physical intrusion alarms and surveillance equipment.'),
('000943','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to recognize potential intrusions and initiate designated response actions.',NULL,NULL,NULL),
('000944','draft','2009-09-21','DISA FSO','policy','The organization controls physical access to the information system by authenticating visitors before authorizing access to the facility where the information system resides other than areas designated as publicly accessible.',NULL,NULL,NULL),
('000945','draft','2009-09-21','DISA FSO','policy','The organization escorts visitors and monitors visitor activity, when required.',NULL,NULL,NULL),
('000946','draft','2009-09-21','DISA FSO','policy','The organization requires two forms of identification for visitor access to the facility.',NULL,NULL,NULL),
('000947','draft','2009-09-21','DISA FSO','policy','The organization maintains visitor access records to the facility where the information system resides for an organization-defined time period.','PE-8.1','The organization being inspected/assessed must maintain visitor access records for their facilities for at least one year. DoD has defined the time period as at least one year.','The organization conducting the inspection/assessment obtains and examines visitor access records to determine if the organization is maintaining visitor access records to the facility where the information system resides for at least one year. DoD has defined the time period as at least one year.'),
('000948','draft','2009-09-21','DISA FSO','policy','The organization reviews visitor access records in accordance with organization-defined frequency.','PE-8.3','The organization being inspected/assessed conducts reviews of visitor access records every 30 days and must establish and maintain a documented audit trail within the authorization lifecycle. DoD has defined the frequency as every 30 days.','The organization conducting the inspection/assessment obtains and examines the audit documentation of visitor access record review to ensure the inspected organization is conducting reviews every 30 days. DoD has defined the frequency as every 30 days.'),
('000949','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review the visitor access records for the facility where the information system resides.','PE-8.4','DoD has defined the frequency as every 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 30 days.'),
('000950','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to facilitate the maintenance and review of access records.','PE-8(1).1','The organization being inspected/assessed will identify, document, and employ automated mechanisms to facilitate the maintenance and review of access records.','The organization conducting the inspection/assessment:\n1. obtains documentation identifying the automated mechanism in use by the inspected organization to facilitate the maintenance and review of access records\n2. Observes the use of the automated mechanism by the inspected organization'),
('000951','draft','2009-09-21','DISA FSO','policy','The organization maintains a record of all physical access, both visitor and authorized individuals.',NULL,NULL,NULL),
('000952','draft','2009-09-21','DISA FSO','policy','The organization protects power equipment and power cabling for the information system from damage and destruction.','PE-9.1','The organization being inspected/assessed provides a list of protective measures in place to prevent damage and/or destruction of power equipment and power cabling for their information system environment, IAW CP-2 (1), CCI 469.','The organization conducting the inspection/assessment obtains and examines the list of protective measures. Physical inspection of power equipment and power cabling will be done to ensure identified protective measures are in place.'),
('000953','draft','2009-09-21','DISA FSO','policy','The organization employs redundant and parallel power cabling paths.',NULL,NULL,NULL),
('000954','draft','2009-09-21','DISA FSO','policy','The organization employs automatic voltage controls for organization-defined critical information system components.','PE-9(2).1','The organization being inspected/assessed employs automatic voltage controls for all IT Components Critical to Execution of Missions. Automatic voltage controls are devices intended to eliminate voltage fluctuations (e.g., spikes). This controls apply to voltage controls for mission critical IT Components and not for facilities. DoD has defined the list of critical information system components as all IT Components Critical to Execution of Missions.','The organization conducting the inspection/assessment obtains the documentation of the all mission critical IT Components required to have automatic voltage controls mechanisms devices in place (IAW PE-9 (2), CCI 955) and does a visual inspection of at least a sample of the above list to ensure automatic voltage control mechanisms are in place. DoD has defined the list of critical information system components as all IT Components Critical to Execution of Missions.'),
('000955','draft','2009-09-21','DISA FSO','policy','The organization defines critical information system components that require automatic voltage controls.','PE-9(2).2','The organization being inspected/assessed must document all IT Components Critical to Execution of Missions. DoD has defined the list of critical information system components as all IT Components Critical to Execution of Missions.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the list of critical information system components as all IT Components Critical to Execution of Missions.'),
('000956','draft','2009-09-21','DISA FSO','policy','The organization provides the capability of shutting off power to the information system or individual system components in emergency situations.','PE-10.1','This control does not apply to individual workstations, laptops, printers, etc. This control only applies to facilities containing concentrations of information system resources (e.g., datacenters, server rooms, mainframe computer rooms). The organization being inspected/assessed will establish and document the capability to shut off the power to facilities or areas within facilities containing concentrations of information system resources (e.g., datacenters, server rooms, mainframe computer rooms) in emergency situations.','The organization conducting the inspection/assessment obtains and examines documentation of the capability to shut off the power to facilities or areas within facilities containing concentrations of information system resources (e.g., datacenters, server rooms, mainframe computer rooms) in emergency situations. The purpose is to validate the organization has provided the capability of shutting off power in emergency situations.'),
('000957','draft','2009-09-21','DISA FSO','policy','The organization places emergency shutoff switches or devices in an organization-defined location by information system or system component to facilitate safe and easy access for personnel.','PE-10.2','This control does not apply to individual workstations, laptops, printers, etc. This control only applies to facilities containing concentrations of information system resources (e.g., datacenters, server rooms, mainframe computer rooms). The organization being inspected/assessed places emergency shutoff switches or devices near more than one egress point of the IT area and ensure it is labeled and protected by a cover to prevent accidental shut-off to facilitate safe and easy access for personnel. DoD has defined the location as near more than one egress point of the IT area and ensure it is labeled and protected by a cover to prevent accidental shut-off.','The organization conducting the inspection/assessment will physically inspect emergency shutoff switches or devices for placement to validate the organization has installed the emergency shutoff switches or devices near more than one egress point of the IT area and ensure it is labeled and protected by a cover to prevent accidental shut-off to facilitate safe and easy access for personnel. DoD has defined the location as near more than one egress point of the IT area and ensure it is labeled and protected by a cover to prevent accidental shut-off.'),
('000958','draft','2009-09-21','DISA FSO','policy','The organization defines a location for emergency shutoff switches or devices by information system or system component.','PE-10.3','DoD has defined the location as near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the location as near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off.'),
('000959','draft','2009-09-21','DISA FSO','policy','The organization protects emergency power shutoff capability from unauthorized activation.','PE-10.4','The organization being inspected/assessed will protect emergency power shutoff capability. DoD has defined the location as near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off.','The organization conducting the inspection/assessment will ensure that the inspected organization has protected emergency power shutoff capability. DoD has defined the location as near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off.'),
('000960','draft','2009-09-21','DISA FSO','policy','The organization provides a short-term uninterruptible power supply to facilitate an orderly shutdown of the information system in the event of a primary power source loss.',NULL,NULL,NULL),
('000961','draft','2009-09-21','DISA FSO','policy','The organization provides a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability in the event of an extended loss of the primary power source.','PE-11(1).1','The organization being inspected/assessed will:\n1. implement alternate power supply capable of supporting minimal operational capability over the long term.\n2. Provide a list of physical IT assets within the boundary of the information system that require a long term alternate power supply. This list may come from the inspected organization\'s security plan, continuity plan, or other documentation.','The organization conducting the inspection/assessment obtains and examines the list of physical IT assets within the boundary of the information system that require a long term alternate power supply. Physically inspect a sample from the list to ensure that long term power supply capability supporting minimal operational capability has been provided.'),
('000962','draft','2009-09-21','DISA FSO','policy','The organization provides a long-term alternate power supply for the information system that is self-contained and not reliant on external power generation.',NULL,NULL,NULL),
('000963','draft','2009-09-21','DISA FSO','policy','The organization employs and maintains automatic emergency lighting for the information system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility.','PE-12.1','The organization being inspected/assessed must install and maintain automatic emergency lighting for the information system that activates in the event of a power outage or disruption and covers emergency exits and evacuation routes within the facility in compliance with established OSHA requirements.','The organization conducting the inspection/assessment conducts visual inspections and interviews physical security personnel to validate the organization is in compliance with established OSHA requirements by employing and maintaining emergency lighting for the information system, the emergency lighting activates in the event of a power outage or disruption, and it covers emergency exits and evacuation routes within the facility'),
('000964','draft','2009-09-21','DISA FSO','policy','The organization provides emergency lighting for all areas within the facility supporting essential missions and business functions.',NULL,NULL,NULL),
('000965','draft','2009-09-21','DISA FSO','policy','The organization employs and maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source.','PE-13.1','The organization being inspected/assessed must implement and maintain fire suppression and detection devices/systems for the information system that are supported by an independent energy source. An independent energy source is some source other than the primary energy source for that facility. Examples include sprinkler systems, hand held fire extinguishers, fixed fire hoses, and smoke detectors.','The organization conducting the inspection/assessment will conduct visual observation and interview organizational personnel with responsibilities for fire detection and suppression devices/systems. The purpose of the reviews and interviews is to validate the fire suppression and detection devices/systems for the information system are supported by an independent energy source.'),
('000966','draft','2009-09-21','DISA FSO','policy','The organization employs fire detection devices/systems for the information system that activate automatically and notify the organization and emergency responders in the event of a fire.',NULL,NULL,NULL),
('000967','draft','2009-09-21','DISA FSO','policy','The organization employs fire suppression devices/systems for the information system that provide automatic notification of any activation to the organization and emergency responders.',NULL,NULL,NULL),
('000968','draft','2009-09-21','DISA FSO','policy','The organization employs an automatic fire suppression capability for the information system when the facility is not staffed on a continuous basis.','PE-13(3).1','The organization being inspected/assessed must implement and maintain an automatic fire suppression capability that is fully operational when the facility is not staffed on a continuous basis.','The organization conducting the inspection/assessment conducts visual inspections and interviews physical security/safety personnel to validate the organization has installed and implemented an automatic fire suppression capability which is operational during those times the facility is not staffed.'),
('000969','draft','2009-09-21','DISA FSO','policy','The organization ensures that the facility undergoes, on an organization-defined frequency, fire marshal inspections and promptly resolves identified deficiencies.',NULL,NULL,NULL),
('000970','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for fire marshal inspections.',NULL,NULL,NULL),
('000971','draft','2009-09-21','DISA FSO','policy','The organization maintains temperature and humidity levels within the facility where the information system resides at organization-defined acceptable levels.','PE-14.1','Humidity controls are not required for general office areas where information system components may be in use and are only required where there are concentrations of information systems such as server farms, mainframes, etc. The organization being inspected/assessed must maintain temperature and where applicable humidity levels of for commercial grade information systems: 64.4 80.6 degrees F; 45% 60% Relative Humidity; Dew Point 41.9 59F; measured at the air intake inlet of the IT equipment casing; for other systems, levels within manufacturer specifications. DoD has defined the acceptable levels as for commercial grade information systems: 64.4 80.6 degrees F; 45% 60% Relative Humidity; Dew Point 41.9 59F; measured at the air intake inlet of the IT equipment casing; for other systems, levels within manufacturer specifications.','The organization conducting the inspection/assessment reviews temperature and humidity controls to validate that they are set within DoD specified guidelines. DoD has defined the acceptable levels as for commercial grade information systems: 64.4 80.6 degrees F; 45% 60% Relative Humidity; Dew Point 41.9 59F; measured at the air intake inlet of the IT equipment casing; for other systems, levels within manufacturer specifications.'),
('000972','draft','2009-09-21','DISA FSO','policy','The organization defines acceptable temperature and humidity levels to be maintained within the facility where the information system resides.','PE-14.2','DoD has defined the acceptable levels as for commercial grade information systems: 64.4 80.6 degrees F; 45% 60% Relative Humidity; Dew Point 41.9 59F; measured at the air intake inlet of the IT equipment casing; for other systems, levels within manufacturer specifications.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the acceptable levels as for commercial grade information systems: 64.4 80.6 degrees F; 45% 60% Relative Humidity; Dew Point 41.9 59F; measured at the air intake inlet of the IT equipment casing; for other systems, levels within manufacturer specifications.'),
('000973','draft','2009-09-21','DISA FSO','policy','The organization monitors temperature and humidity levels in accordance with organization-defined frequency.','PE-14.3','The organization being inspected/assessed will maintain an independent monitor device for temperature and humidity levels not located in the immediate vicinity of the controller continuously unless manufacturer specifications allow for a wide enough tolerance that control is not required. Records of monitoring must be maintained as an audit trail within the authorization lifecycle. DoD has defined the frequency as continuously unless manufacturer specifications allow for a wide enough tolerance that control is not required.','The organization conducting the inspection/assessment will visually observe the inspected organization\'s independent monitoring device, obtain and examine audit logs, and interview physical security/safety personnel to validate the inspected organization monitors temperature and humidity levels continuously unless manufacturer specifications allow for a wide enough tolerance that control is not required. DoD has defined the frequency as continuously unless manufacturer specifications allow for a wide enough tolerance that control is not required.'),
('000974','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for monitoring temperature and humidity levels.','PE-14.4','DoD has defined the frequency as continuously unless manufacturer specifications allow for a wide enough tolerance that control is not required.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as continuously unless manufacturer specifications allow for a wide enough tolerance that control is not required.'),
('000975','draft','2009-09-21','DISA FSO','policy','The organization employs automatic temperature and humidity controls in the facility to prevent fluctuations potentially harmful to the information system.','PE-14(1).1','Humidity controls are not required for general office areas where information system components may be in use and are only required where there are concentrations of information systems such as server farms, mainframes, etc. The organization being inspected/assessed must implement and maintain automatic temperature and humidity controls in the facility designed to prevent temperature and humidity fluctuations that would be potentially harmful to the information system.','The organization conducting the inspection/assessment conducts visual inspections and interviews personnel responsible for maintaining automatic temperature and humidity controls to validate the organization is employing automatic temperature and humidity controls for the information system to prevent fluctuations potentially harmful to the information system.'),
('000976','draft','2009-09-21','DISA FSO','policy','The organization employs temperature and humidity monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment.','PE-14(2).1','Humidity controls are not required for general office areas where information system components may be in use and are only required where there are concentrations of information systems such as server farms, mainframes, etc. The organization being inspected/assessed must implement and maintain automatic temperature and humidity controls in the facility and provides an alarm or notification of changes to either of these environmental conditions that are potentially harmful to personnel or equipment.','The organization conducting the inspection/assessment conducts visual inspections and interviews personnel responsible for maintaining automatic temperature and humidity controls to validate the inspected organization is employing automatic temperature and humidity controls that provide an alarm or notification of changes potentially harmful to personnel or equipment.'),
('000977','draft','2009-09-21','DISA FSO','policy','The organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible.','PE-15.1','The organization being inspected/assessed must provide master shutoff valves that are accessible to protect the information system from damage resulting from water leakage.','The organization conducting the inspection/assessment will inspect the master shutoff valves to ensure they are installed and accessible.'),
('000978','draft','2009-09-21','DISA FSO','policy','The organization protects the information system from damage resulting from water leakage by providing master shutoff or isolation valves that are working properly.','PE-15.2','The organization being inspected/assessed will ensure that master shutoff valves are working properly and have been inspected by the appropriate organization (e.g., fire marshal, department of public works).','The organization conducting the inspection/assessment will visually inspect master shutoff valve inspection documentation (e.g., inspection form, tag attached to valve).'),
('000979','draft','2009-09-21','DISA FSO','policy','Key personnel have knowledge of the master water shutoff or isolation valves.','PE-15.3','The organization being inspected/assessed will identify and document key personnel and will provide training on the location and procedures for use of master shutoff valves.','The organization conducting the inspection/assessment obtains and examines list of key personnel with knowledge of location and activation procedures for master shutoff valves and any other relevant documents or records. Interview key personnel from the list to determine if identified key personnel within the organization have knowledge of the master shutoff valves.'),
('000980','draft','2009-09-21','DISA FSO','policy','The organization employs mechanisms that, without the need for manual intervention, protect the information system from water damage in the event of a water leak.',NULL,NULL,NULL),
('000981','draft','2009-09-21','DISA FSO','policy','The organization authorizes organization-defined types of information system components entering and exiting the facility.','PE-16.1','The organization being inspected/assessed authorizes and maintains authorization records of all system components entering and exiting the facility. DoD has defined the types of information system components as all system components.','The organization conducting the inspection/assessment obtains and examines records authorizing all system components entering and exiting the facility. DoD has defined the types of information system components as all system components.'),
('000982','draft','2009-09-21','DISA FSO','policy','The organization monitors organization-defined types of information system components entering and exiting the facility.','PE-16.2','The organization being inspected/assessed monitors all system components entering and exiting the facility. DoD has defined the types of information system components as all system components.','The organization conducting the inspection/assessment obtains and examines records monitoring all system components entering and exiting the facility. DoD has defined the types of information system components as all system components.'),
('000983','draft','2009-09-21','DISA FSO','policy','The organization controls organization-defined types of information system components entering and exiting the facility.','PE-16.3','The organization being inspected/assessed:\n1. Documents in their physical and environmental protection plan (PE-1) controls for all system components entering and exiting the facility.\n2. Implements documented controls for system components entering and exiting the facility. DoD has defined the types of information system components as all system components.','The organization conducting the inspection/assessment obtains and examines the physical and environmental protection plan to determine if controls have been documented for all system components entering and exiting the facility and visually inspects the controls (e.g., logs, scans, etc.) to ensure implementation. DoD has defined the types of information system components as all system components.'),
('000984','draft','2009-09-21','DISA FSO','policy','The organization maintains records of information system components entering and exiting the facility.','PE-16.4','The organization being inspected/assessed will maintain records of all information system components entering and exiting the facility. If the organization is following General Records Schedule (GRS) 18, Section 12 they are automatically compliant.','The organization conducting the inspection/assessment obtains and examines records of physical entry and exit events to the facility. The purpose of the reviews is to ensure the organization is maintaining detailed and accurate records of information system components that enter and exit the facility. If the organization is following GRS 18, Section 12 they are automatically compliant.'),
('000985','draft','2009-09-21','DISA FSO','policy','The organization employs organization-defined security controls at alternate work sites.','PE-17.1','The organization being inspected/assessed implements security controls defined in PE-17, CCI 2975 at alternate work sites. Alternate work sites are further defined in the definitions associated with this implementation guide. Organizational telework policies should be used to address alternate work sites that are private residences. Comment: For classified information see DoD 5200.01 Vol 3 Manual','The organization conducting the inspection/assessment obtains and examines the alternate work site policy of the organization being inspected/assessed to ensure the organization implements security controls defined in PE-17, CCI 2975 at alternate work sites.'),
('000986','draft','2009-09-21','DISA FSO','policy','The organization defines management, operational, and technical information system security controls to be employed at alternate work sites.',NULL,NULL,NULL),
('000987','draft','2009-09-21','DISA FSO','policy','The organization assesses as feasible, the effectiveness of security controls at alternate work sites.','PE-17.3','The organization being inspected/assessed must implement procedures to assess, when feasible, the effectiveness of the documented alternate work site security controls. The organization must document results of conducted assessments as part of an audit trail. Alternate work sites are further defined in the definitions associated with this implementation guide.','The organization conducting the inspection/assessment obtains and examines:\n1. The procedures for assessing the effectiveness of alternate work site security controls.\n2. The audit records of assessments they have conducted of security controls effectiveness for alternate work sites.'),
('000988','draft','2009-09-21','DISA FSO','policy','The organization provides a means for employees to communicate with information security personnel in case of security incidents or problems.','PE-17.4','The organization being inspected/assessed must disseminate current contact information for appropriate security personnel to all employees; for example, telephone or e-mail.','The organization conducting the inspection/assessment obtains and examines contact information for appropriate security personnel to ensure its accuracy and dissemination.'),
('000989','draft','2009-09-21','DISA FSO','policy','The organization positions information system components within the facility to minimize potential damage from organization-defined physical and environmental hazards.','PE-18.1','The organization being inspected/assessed positions information system components within the facility to minimize potential damage from physical and environmental hazards defined in PE-18, CCI 2976 specific to the location of the information system as documented in PE-1, CCI 000904.','The organization conducting the inspection/assessment reviews the physical and environmental protection policy developed in PE-1, CCI 000904 to validate that the systems have been positioned according to the environmental policy.'),
('000990','draft','2009-09-21','DISA FSO','policy','The organization positions information system components within the facility to minimize potential damage from environmental hazards.',NULL,NULL,NULL),
('000991','draft','2009-09-21','DISA FSO','policy','The organization positions information system components within the facility to minimize the opportunity for unauthorized access.','PE-18.2','The organization being inspected/assessed positions information system components within the facility to minimize the opportunity for unauthorized access specific to the location of the information system as documented in PE-1, CCI 00904.','The organization conducting the inspection/assessment reviews the physical and environmental protection policy developed in PE-1, CCI 000904 to validate that the systems have been positioned according to the environmental policy.'),
('000992','draft','2009-09-21','DISA FSO','policy','The organization plans the location or site of the facility where the information system resides with regard to physical and environmental hazards, and for existing facilities, considers the physical and environmental hazards in its risk mitigation strategy.',NULL,NULL,NULL),
('000993','draft','2009-09-21','DISA FSO','policy','The organization protects the information system from information leakage due to electromagnetic signals emanations.','PE-19.1','The organization being inspected/assessed will obtain a TEMPEST countermeasure review and implement the required countermeasures in order to protect the information system from information leakage due to electromagnetic signals emanations.','The organization conducting the inspection/assessment obtains and examines the TEMPEST countermeasures review and inspects the information system to ensure those countermeasures have been implemented.'),
('000994','draft','2009-09-21','DISA FSO','policy','The organization ensures that information system components, associated data communications, and networks are protected in accordance with national emissions and TEMPEST policies and procedures based on the security category or classification of the information.','PE-19(1).1','The organization being inspected/assessed will obtain a TEMPEST countermeasure review and implement the required countermeasures in order to protect the information system from information leakage due to electromagnetic signals emanations.','The organization conducting the inspection/assessment obtains and examines the TEMPEST countermeasures review and inspects the information system to ensure those countermeasures have been implemented.'),
('000995','draft','2009-09-21','DISA FSO','policy','The organization develops and documents a media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','MP-1.1','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.'),
('000996','draft','2009-09-21','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles a media protection policy.','MP-1.2','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures and is disseminated to all users via http://www.dtic.mil/whs/directives/corres/ins1.html.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.'),
('000997','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current media protection policy in accordance with organization-defined frequency.','MP-1.6','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.'),
('000998','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for reviewing and updating the current media protection policy.','MP-1.7','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('000999','draft','2009-09-21','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the media protection policy and associated media protection controls.','MP-1.4','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.'),
('001000','draft','2009-09-21','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the media protection policy and associated media protection controls.','MP-1.5','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures and is disseminated to all users via http://www.dtic.mil/whs/directives/corres/ins1.html.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.'),
('001001','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current media protection procedures in accordance with organization-defined frequency.','MP-1.8','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.','DoDI 5200.01 and DoDM 5200.01 Vol. 1-4 meet the DoD requirements for media protection policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 5200.01 and DoDM 5200.01 Vol. 1-4.'),
('001002','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for reviewing and updating the current media protection procedures.','MP-1.9','DoD has defined the frequency as reviewed annually as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually as appropriate.'),
('001003','draft','2009-09-21','DISA FSO','policy','The organization restricts access to organization-defined types of digital and/or non-digital media to organization-defined personnel or roles.','MP-2.1','The organization being inspected/assessed restricts access to all types of digital and/or non-digital media containing information not cleared for public release to the personnel or roles defined in MP-2, CCI 1005. DoD has defined the types of digital and non-digital media as all types of digital and/or non-digital media containing information not cleared for public release.','The organization conducting the inspection/assessment interviews organizational personnel with information system media protection responsibilities to ensure the organization being inspected/assessed restricts access to all types of digital and/or non-digital media containing information not cleared for public release to the personnel or roles defined in MP-2, CCI 1005. DoD has defined the types of digital and non-digital media as all types of digital and/or non-digital media containing information not cleared for public release. '),
('001004','draft','2009-09-21','DISA FSO','policy','The organization defines types of digital and/or non-digital media for which the organization restricts access.','MP-2.2','DoD has defined the types of digital and non-digital media as all types of digital and/or non-digital media containing information not cleared for public release. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the types of digital and non-digital media as all types of digital and/or non-digital media containing information not cleared for public release. '),
('001005','draft','2009-09-21','DISA FSO','policy','The organization defines personnel or roles from which to restrict access to organization-defined types of digital and/or non-digital media.','MP-2.3','The organization being inspected/assessed will define and document personnel or roles to restrict access to media IAW DoD 5200.01-M, CTO 10-133, and CTO 08-001. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level, but personnel must be identified IAW DoD 5200.01-M, CTO 10-133, and CTO 08-001.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to restrict access to media to ensure the access is granted IAW DoD 5200.01-M, CTO 10-133, and CTO 08-001. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level, but personnel must be identified IAW DoD 5200.01-M, CTO 10-133, and CTO 08-001.'),
('001006','draft','2009-09-21','DISA FSO','policy','The organization defines security measures for restricting access to media.',NULL,NULL,NULL),
('001007','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to restrict access to media storage areas.','MP-4(2).1','The organization being inspected/assessed implements automated mechanisms to restrict access to media storage areas.','The organization conducting the inspection/assessment examines the information system\'s environment to ensure the organization being inspected/assessed implements automated mechanisms to restrict access to media storage areas.'),
('001008','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to audit access attempts and access granted to media storage areas.','MP-4(2).2','The organization being inspected/assessed implements automated mechanisms to audit access attempts and access granted to media storage areas.','The organization conducting the inspection/assessment examines the information system\'s environment to ensure the organization being inspected/assessed implements automated mechanisms to audit access attempts and access granted to media storage areas.'),
('001009','draft','2009-09-21','DISA FSO','technical','The information system uses cryptographic mechanisms to protect and restrict access to information on portable digital media.',NULL,NULL,NULL),
('001010','draft','2009-09-21','DISA FSO','policy','The organization marks information system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information.','MP-3.1','The organization being inspected/assessed marks information system media and information system output IAW DoDM 5200.01 Vol. 1-4.','The organization conducting the inspection/assessment obtains a sampling of information system media and information system output to verify that it is marked in compliance with DoDM 5200.01 Vol. 1-4.'),
('001011','draft','2009-09-21','DISA FSO','policy','The organization exempts organization-defined types of information system media from marking as long as the media remain within organization-defined controlled areas.','MP-3.2','All information system media must be marked in all areas IAW DoDM 5200.01 Vol. 1-4.','The organization conducting the inspection/assessment examines information system media to ensure it is marked IAW DoDM 5200.01 Vol. 1-4.'),
('001012','draft','2009-09-21','DISA FSO','policy','The organization defines types of information system media to exempt from marking as long as the media remain within organization-defined controlled areas.','MP-3.3','DoD has defined the list of information system media as nothing unless otherwise exempted by DoDI 5200.01 and DoDM 5200.01 Vol 1-4.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the list of information system media as nothing unless otherwise exempted by DoDI 5200.01 and DoDM 5200.01 Vol 1-4'),
('001013','draft','2009-09-21','DISA FSO','policy','The organization defines controlled areas where organization-defined types of information system media are exempt from being marked.','MP-3.4','DoD has defined the controlled areas as all areas unless otherwise exempted by DoDI 5200.01 and DoDM 5200.01 Vol 1-4','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the controlled areas as all areas unless otherwise exempted by DoDI 5200.01 and DoDM 5200.01 Vol 1-4'),
('001014','draft','2009-09-21','DISA FSO','policy','The organization physically controls and securely stores organization-defined types of digital and/or non-digital media within organization-defined controlled areas.','MP-4.1','The organization being inspected/assessed physically controls and securely stores all digital and non-digital media containing sensitive, controlled, and/or classified information within areas approved for processing or storing data IAW the sensitivity and/or classification level of the information contained on/within the media. DoD has defined the digital and non-digital media types as all digital and non-digital media containing sensitive, controlled, and/or classified information. DoD has defined the controlled areas as areas approved for processing or storing data IAW the sensitivity and/or classification level of the information contained on/within the media.','The organization conducting the inspection/assessment obtains and examines the list of all digital and non-digital media containing sensitive, controlled, and/or classified information within areas approved for processing or storing data IAW the sensitivity and/or classification level of the information contained on/within the media to ensure that physical controls are in place and that it is securely stored as defined in PE-3. DoD has defined the digital and non-digital media types as all digital and non-digital media containing sensitive, controlled, and/or classified information. DoD has defined the controlled areas as areas approved for processing or storing data IAW the sensitivity and/or classification level of the information contained on/within the media.'),
('001015','draft','2009-09-21','DISA FSO','policy','The organization defines types of digital and/or non-digital media to physically control and securely store within organization-defined controlled areas.','MP-4.2','DoD has defined the digital and non-digital media types as all digital and non-digital media containing sensitive, controlled, and/or classified information.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the digital and non-digital media types as all digital and non-digital media containing sensitive, controlled, and/or classified information.'),
('001016','draft','2009-09-21','DISA FSO','policy','The organization defines controlled areas where organization-defined types of digital and/or non-digital media are physically controlled and securely stored.','MP-4.3','DoD has defined the controlled areas as areas approved for processing or storing data IAW the sensitivity and/or classification level of the information contained on/within the media.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the controlled areas as areas approved for processing or storing data IAW the sensitivity and/or classification level of the information contained on/within the media.'),
('001017','draft','2009-09-21','DISA FSO','policy','The organization defines security measures for securing media storage.',NULL,NULL,NULL),
('001018','draft','2009-09-21','DISA FSO','policy','The organization protects information system media until the media are destroyed or sanitized using approved equipment, techniques, and procedures.','MP-4.4','The organization being inspected/assessed protects information system media IAW DoDM 5200.01 M Vol. 1-4.','The organization conducting the inspection/assessment obtains and examines the list of media and verifies it is being stored and protected IAW DoDM 5200.01 M Vol. 1-4.'),
('001019','draft','2009-09-21','DISA FSO','technical','The organization employs cryptographic mechanisms to protect information in storage.',NULL,NULL,NULL),
('001020','draft','2009-09-21','DISA FSO','policy','The organization protects and controls organization-defined types of information system media during transport outside of controlled areas using organization-defined security safeguards.','MP-5.1','The organization being inspected/assessed protects and controls information system media during transport outside of controlled areas using security measures defined in DoDM 5200.01 M Vol. 1-4 and DoDD 5015.2.','The organization conducting the inspection/assessment obtains and examines the organization\'s records management policy or process to ensure appropriate protection of information according to its classification or designation during transport outside of controlled areas, IAW security measures defined in DoDM 5200.01 M Vol. 1-4 and DoDD 5015.2.'),
('001021','draft','2009-09-21','DISA FSO','policy','The organization defines types of information system media protected and controlled during transport outside of controlled areas.','MP-5.2','DoD has defined the types of information system media as all digital and non-digital media containing sensitive, controlled, and/or classified information.','DoD has defined the types of information system media as all digital and non-digital media containing sensitive, controlled, and/or classified information. The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.'),
('001022','draft','2009-09-21','DISA FSO','policy','The organization defines security safeguards to be used to protect and control organization-defined types of information system media during transport outside of controlled areas.','MP-5.3','DoD has defined the security safeguards as DoDI 5200.1R and other organizationally defined security safeguards.','DoD has defined the security safeguards as DoDI 5200.1R and other organizationally defined security safeguards. The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.'),
('001023','draft','2009-09-21','DISA FSO','policy','The organization maintains accountability for information system media during transport outside of controlled areas.','MP-5.4','The organization being inspected/assessed ensures the organization defined security measures (MP-2) includes method of accountability for information system media during transport outside of controlled areas, IAW DoDM 5200.01 M Vol. 1-4 and DoDD 5015.2.','The organization conducting the inspection/assessment obtains and examines the list of organization defined security measures (MP-2) to ensure method of accountability for information system media during transport outside of controlled areas has been identified.'),
('001024','draft','2009-09-21','DISA FSO','policy','The organization restricts the activities associated with the transport of information system media to authorized personnel.','MP-5.6','The organization being inspected/assessed ensures the organization defined security measures (MP-2) includes a requirement to develop and maintain a list of personnel authorized to transport information system media outside of controlled areas, IAW DoDM 5200.01 M Vol. 1-4 and DoDD 5015.2. Develop and maintain the list of personnel authorized to transport information system media outside of controlled areas.','The organization conducting the inspection/assessment obtains and examines the list of personnel authorized to transport information system media outside of controlled areas. Organizational personnel with information system media transport responsibilities and security management personnel are to be interviewed. The purpose of the reviews and reviews is to determine if the organization has established restrictions associated with the transport of information system media to authorized personnel only.'),
('001025','draft','2009-09-21','DISA FSO','policy','The organization documents activities associated with the transport of information system media.','MP-5.5','The organization being inspected/assessed documents activities associated with the transport of information system media.','The organization conducting the inspection/assessment obtains and examines the documented activities to ensure the organization being inspected/assessed documents activities associated with the transport of information system media.'),
('001026','draft','2009-09-21','DISA FSO','policy','The organization employs an identified custodian during transport of information system media outside of controlled areas.','MP-5(3).1','The organization being inspected/assessed identifies and documents a custodian that is at all times responsible for the transport of the all information system media, from pick-up to final delivery and receipt acknowledgement.','The organization conducting the inspection/assessment obtains and examines documentation identifying the custodian that is at all times responsible for the transport of the all information system media, from pick-up to final delivery and receipt acknowledgement.'),
('001027','draft','2009-09-21','DISA FSO','policy','The information system implements cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas.','MP-5(4).1','The organization being inspected/assessed shall document within their Security Plan, and implement, FIPS 140-2 or other NSA approved cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas.','The organization conducting the inspection/assessment obtains and examines the Security Plan to ensure the organization being inspected has identified FIPS 140-2 or other NSA approved cryptographic mechanisms to protect the confidentiality and integrity of information stored on digital media during transport outside of controlled areas.'),
('001028','draft','2009-09-21','DISA FSO','policy','The organization sanitizes organization-defined information system media prior to disposal, release out of organizational control, or release for reuse using organization-defined sanitization techniques and procedures in accordance with applicable federal and organizational standards and policies.','MP-6.1','The organization being inspected/assessed sanitizes all media prior to disposal, release out of organizational control, or release for reuse IAW DoDM 5200.01 Vol. 1-4 using techniques and procedures IAW NIST SP 800-88. DoD has defined the sanitization techniques as techniques and procedures IAW NIST SP 800-88. DoD has defined the information system media as all media.','The organization conducting the inspection/assessment obtains and examines media sanitization records, audit records, any other relevant documents or records, and sanitization tools to ensure sanitization is in compliance with DoDM 5200.01 Vol. 1-4 and uses techniques and procedures IAW NIST SP 800-88. The objective of the review is to verify the organization is sanitizing its digital and non-digital information system media prior to disposal, release for reuse, or release out of the organizational control. DoD has defined the sanitization techniques as techniques and procedures IAW NIST SP 800-88. DoD has defined the information system media as all media.'),
('001029','draft','2009-09-21','DISA FSO','policy','The organization tracks, documents, and verifies media sanitization and disposal actions.',NULL,NULL,NULL),
('001030','draft','2009-09-21','DISA FSO','policy','The organization tests sanitization equipment and procedures in accordance with the organization-defined frequency to verify that the intended sanitization is being achieved.','MP-6(2).1','The organization being inspected/assessed shall document plans to implement their sanitization equipment and procedures every 180 days to verify correct performance. DoD has defined the frequency as every 180 days.','The organization conducting the inspection/assessment obtains and examines documented test plans and evidence of past tests to ensure that tests are conducted every 180 days to verify correct performance of sanitization equipment and procedures. DoD has defined the frequency as every 180 days.'),
('001031','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for testing sanitization equipment and procedures to verify that the intended sanitization is being achieved.','MP-6(2).2','DoD has defined the frequency as every 180 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 180 days.'),
('001032','draft','2009-09-21','DISA FSO','policy','The organization applies nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the information system in accordance with organization-defined circumstances requiring sanitization of portable storage devices.','MP-6(3).1','The organization being inspected/assessed documents and implements plans to apply nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the information system when such devices are first purchased from the manufacturer or vendor prior to initial use, when being considered for reuse, or when the organization loses a positive chain of custody for the device. Media obtained from unknown sources shall not be sanitized and reused. Portable storage devices include but are not limited to thumb drives, flash drives, and external storage devices. DoD has defined the circumstances as when such devices are first purchased from the manufacturer or vendor prior to initial use, when being considered for reuse, or when the organization loses a positive chain of custody for the device. Media obtained from unknown sources shall not be sanitized and reused.','The organization conducting the inspection/assessment obtains and examines media sanitization records, audit records, and any other relevant documents or records. The objective of the reviews is to confirm the organization is in compliance with the list of defined circumstances requiring the sanitization of portable storage devices prior to connecting such devices to the information system.'),
('001033','draft','2009-09-21','DISA FSO','policy','The organization defines circumstances requiring sanitization of portable storage devices prior to connecting such devices to the information system.','MP-6(3).2','DoD has defined the list circumstances as when such devices are first purchased from the manufacturer or vendor prior to initial use, when being considered for reuse, or when the organization loses a positive chain of custody for the device. Media obtained from unknown sources shall not be sanitized and reused.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the circumstances as when such devices are first purchased from the manufacturer or vendor prior to initial use, when being considered for reuse, or when the organization loses a positive chain of custody for the device. Media obtained from unknown sources shall not be sanitized and reused.'),
('001034','draft','2009-09-21','DISA FSO','policy','The organization sanitizes information system media containing Controlled Unclassified Information (CUI) or other sensitive information in accordance with applicable organizational and/or federal standards and policies.',NULL,NULL,NULL),
('001035','draft','2009-09-21','DISA FSO','policy','The organization sanitizes information system media containing classified information in accordance with NSA standards and policies.',NULL,NULL,NULL),
('001036','draft','2009-09-21','DISA FSO','policy','The organization destroys information system media that cannot be sanitized.',NULL,NULL,NULL),
('001037','draft','2009-09-21','DISA FSO','policy','The organization develops and documents a risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','RA-1.3','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.'),
('001038','draft','2009-09-21','DISA FSO','policy','The organization disseminates a risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance to organization-defined personnel or roles.','RA-1.4','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures and is disseminated via the NIST publications site: http://csrc.nist.gov/publications/PubsSPs.html\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.'),
('001039','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current risk assessment policy in accordance with organization-defined frequency.','RA-1.7','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.'),
('001040','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review and update the current risk assessment policy.','RA-1.8','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('001041','draft','2009-09-21','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls.','RA-1.5','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.'),
('001042','draft','2009-09-21','DISA FSO','policy','The organization disseminates risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls to organization-defined personnel or roles.','RA-1.6','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures and is disseminated via the NIST publications site: http://csrc.nist.gov/publications/PubsSPs.html\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.'),
('001043','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the current risk assessment procedures in accordance with organization-defined frequency.','RA-1.9','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','NIST SP 800-30 meets the DoD requirements for risk assessment policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.'),
('001044','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency with which to review and update the current risk assessment procedures.','RA-1.10','DoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.','DoD Components are automatically compliant with this CCI because they are covered by the DoDi 8510.01 which adopts NIST SP 800-30 as the DoD risk assessment policy.\n\nDoD has defined the frequency as annually - updated as appropriate.'),
('001045','draft','2009-09-21','DISA FSO','policy','The organization categorizes information and the information system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.','RA-2.1','The organization being inspected/assessed documents and implements a process to categorize information and the information system in accordance with CNSSI 1253 and applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. ','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed categorizes information and the information system in accordance with CNSSI 1253 and applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. '),
('001046','draft','2009-09-21','DISA FSO','policy','The organization documents the security categorization results (including supporting rationale) in the security plan for the information system.','RA-2.2','The organization being inspected/assessed documents the security categorization results (including supporting rationale) in the security plan for the information system IAW CNSSI 1253. ','The organization conducting the inspection/assessment obtains and examines the documented security categorization results to ensure the organization being inspected/assessed documents the security categorization results (including supporting rationale) in the security plan for the information system IAW CNSSI 1253.'),
('001047','draft','2009-09-21','DISA FSO','policy','The organization ensures the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative.','RA-2.3','The organization being inspected/assessed documents and implements a process IAW CNSSI 1253 to ensure the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative.'),
('001048','draft','2009-09-21','DISA FSO','policy','The organization conducts an assessment of risk of the information system and the information it processes, stores, or transmits that includes the likelihood and magnitude of harm from the unauthorized access, use, disclosure, disruption, modification, or destruction.','RA-3.1','The organization being inspected/assessed conducts an assessment of risk of the information system and the information it processes, stores, or transmits that includes the likelihood and magnitude of harm from the unauthorized access, use, disclosure, disruption, modification, or destruction. The organization must maintain an audit trail of assessments.','The organization conducting the inspection/assessment obtains and examines the audit trail of assessments to ensure the organization being inspected/assessed conducts an assessment of risk of the information system and the information it processes, stores, or transmits that includes the likelihood and magnitude of harm from the unauthorized access, use, disclosure, disruption, modification, or destruction.'),
('001049','draft','2009-09-21','DISA FSO','policy','The organization documents risk assessment results in the organization-defined document.','RA-3.2','The organization being inspected/assessed documents risk assessment results in the risk assessment report. DoD has defined the document as a risk assessment report.','The organization conducting the inspection/assessment obtains and examines the risk assessment report to ensure the organization being inspected/assessed documents risk assessment results in the risk assessment report. DoD has defined the document as a risk assessment report.'),
('001050','draft','2009-09-21','DISA FSO','policy','The organization reviews risk assessment results on an organization-defined frequency.','RA-3.4','The organization being inspected/assessed reviews risk assessment results upon re-accreditation. The organization must maintain a record of reviews. DoD has defined the frequency as upon re-accreditation. ','The organization conducting the inspection/assessment obtains and examines the record of reviews to ensure the organization being inspected/assessed reviews risk assessment results upon re-accreditation. DoD has defined the frequency as upon re-accreditation. '),
('001051','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for reviewing risk assessment results.','RA-3.5','DoD has defined the frequency as upon re-accreditation. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as upon re-accreditation. '),
('001052','draft','2009-09-21','DISA FSO','policy','The organization updates the risk assessment on an organization-defined frequency or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system.','RA-3.8','The organization being inspected/assessed updates the risk assessment upon re-accreditation or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system.\n\nDoD has defined the frequency as upon re-accreditation.','The organization conducting the inspection/assessment obtains and examines historical versions of the risk assessment as well as records of changes to the system to ensure the organization being inspected/assessed updates the risk assessment upon re-accreditation or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system. DoD has defined the frequency as upon re-accreditation. '),
('001053','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for updating the risk assessment.','RA-3.9','DoD has defined the frequency as upon re-accreditation. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as upon re-accreditation. '),
('001054','draft','2009-09-21','DISA FSO','policy','The organization scans for vulnerabilities in the information system and hosted applications on an organization-defined frequency.','RA-5.1','The organization being inspected/assessed will define, document, and implement procedures for vulnerability scans of the information system and hosted applications; and scan for vulnerabilities in the information system and hosted applications every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs). This control is not targeted at security control compliance scanning. DoD has defined the frequency as every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization conducting the inspection/assessment obtains and examines the organization\'s vulnerability scanning procedures and results for the 90 days preceding the inspection/assessment. If the system in question has not been operational for more than 90 days the organization will provide all available scan(s).'),
('001055','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for scanning for vulnerabilities in the information system and hosted applications.','RA-5.2','DoD has defined the frequency as every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).'),
('001056','draft','2009-09-21','DISA FSO','policy','The organization scans for vulnerabilities in the information system and hosted applications when new vulnerabilities potentially affecting the system/applications are identified and reported.','RA-5.3','The organization being inspected/assessed will conduct vulnerability scans of the information system and hosted applications when new vulnerabilities potentially affecting the system/applications are identified and reported via authoritative sources (e.g., IAVM, CTO, DTM, STIG, product vendor).','The organization conducting the inspection/assessment obtains and examines the organization\'s vulnerability scanning procedures and results in order to validate the organization conducts vulnerability scans of its Information System (IS) and hosted applications when new vulnerabilities potentially affecting the IS and/or applications are identified and reported.'),
('001057','draft','2009-09-21','DISA FSO','policy','The organization employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: enumerating platforms, software flaws, and improper configurations; formatting checklists and test procedures; and measuring vulnerability impact.','RA-5.6','The organization being inspected/assessed employs the DoD Enterprise scanning tool.','The organization conducting the inspection/assessment obtains and examines the software list or vulnerability scanning procedures to ensure the organization being inspected/assessed employs the DoD Enterprise scanning tool.'),
('001058','draft','2009-09-21','DISA FSO','policy','The organization analyzes vulnerability scan reports and results from security control assessments.','RA-5.7','The organization being inspected/assessed analyzes vulnerability scan reports and security control assessment results with the intent of identifying legitimate vulnerabilities and the relationship between vulnerabilities and security controls.','The organization conducting the inspection/assessment will interview organizational personnel with security control assessment and vulnerability scanning responsibilities. The purpose of the reviews and interviews is to validate the organization is conducting an analysis of the vulnerability scan reports and results from the security control assessments.'),
('001059','draft','2009-09-21','DISA FSO','policy','The organization remediates legitimate vulnerabilities in organization-defined response times in accordance with an organizational assessment risk.','RA-5.8','The organization being inspected/assessed takes corrective actions as appropriate on legitimate vulnerabilities identified in RA-5, CCI 001058 IAW an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs). Audit records of actions must be maintained IAW applicable DoD, CYBERCOM, and/or component policies. DoD has defined the response times as IAW an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization conducting the inspection/assessment obtains and examines audit records to validate the organization is taking action to remediate legitimate vulnerabilities within the required response times (IAW an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs). The organization conducting the inspection/assessment may conduct independent vulnerability scans to compare those scan results with audit records of remediation actions. DoD has defined the response times as IAW an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).'),
('001060','draft','2009-09-21','DISA FSO','policy','The organization defines response times for remediating legitimate vulnerabilities in accordance with an organization assessment of risk.','RA-5.9','DoD has defined the response times as IAW an authoritative source (e.g. IAVM, CTOs, DTMs).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the response times as IAW an authoritative source (e.g. IAVM, CTOs, DTMs).'),
('001061','draft','2009-09-21','DISA FSO','policy','The organization shares information obtained from the vulnerability scanning process and security control assessments with organization-defined personnel or roles to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies).','RA-5.10','The organization being inspected/assessed documents and implements a process to share information obtained from the vulnerability scanning process and security control assessments with at a minimum, the ISSM and ISSO to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies). DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed shares information obtained from the vulnerability scanning process and security control assessments with at a minimum, the ISSM and ISSO to help eliminate similar vulnerabilities in other information systems (i.e., systemic weaknesses or deficiencies). DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('001062','draft','2009-09-21','DISA FSO','policy','The organization employs vulnerability scanning tools that include the capability to readily update the information system vulnerabilities to be scanned.','RA-5(1).1','The organization being inspected/assessed will employ scanning tools that maintain currency with industry standard information system vulnerabilities to ensure that scanning activities are conducted with the most up to date list of known vulnerabilities to include USCYBERCOM issued IAVMs.\n\nDoD has provided an enterprise scanning tool that fully meets this requirement. Organizations that choose not to use the enterprise scanning tool must identify which scanning tool they are using and ensure that it meets these requirements.','The organization conducting the inspection/assessment will:\n1. If the inspected organization is using the DoD provided enterprise scanning tool, compliance with this control is complete.\n2. Validate the identified tool in use by the inspected organization is able to maintain current up to date information system vulnerability data.'),
('001063','draft','2009-09-21','DISA FSO','policy','The organization updates the information system vulnerabilities scanned on an organization-defined frequency, prior to a new scan, and/or when new vulnerabilities are identified and reported.','RA-5(2).1','The organization being inspected/assessed will update the list of information system vulnerabilities scanned for prior to running scans. The organization must maintain a record of scans including the list of vulnerabilities scanned for. DoD has defined the frequency as prior to running scans.','The organization conducting the inspection/assessment obtains and examines the record of scans to ensure the latest most up to date scanning policies are present.'),
('001064','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for updating the information system vulnerabilities scanned.','RA-5(2).2','DoD has defined the frequency as prior to running scans.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as prior to running scans.'),
('001065','draft','2009-09-21','DISA FSO','policy','The organization employs vulnerability scanning procedures that can demonstrate the breadth of coverage (i.e., information system components scanned).',NULL,NULL,NULL),
('001066','draft','2009-09-21','DISA FSO','policy','The organization determines what information about the information system is discoverable by adversaries.','RA-5(4).1','If the organization being inspected/assessed is conducting vulnerability scans IAW base control RA-5, they are compliant with this CCI.','The organization conducting the inspection/assessment will review results of validation of base control RA-5, if the inspected organization is compliant with the requirements of RA-5, they are compliant with this CCI.'),
('001067','draft','2009-09-21','DISA FSO','technical','The information system implements privileged access authorization to organization-identified information system components for selected organization-defined vulnerability scanning activities.','RA-5(5).1','The organization being inspected/assessed configures the information system to implement privileged access authorization to all information systems and infrastructure components for selected vulnerability scanning activities defined in RA-5 (5), CCI 2906. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1067. DoD has defined the information system components as all information systems and infrastructure components.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement privileged access authorization to all information systems and infrastructure components for selected vulnerability scanning activities defined in RA-5 (5), CCI 2906. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1067. DoD has defined the information system components as all information systems and infrastructure components.'),
('001068','draft','2009-09-21','DISA FSO','policy','The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities.','RA-5(6).1','The organization being inspected/assessed must configure and implement automated mechanisms which provide the capability to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities.','The organization conducting the inspection/assessment validates the organization is employing automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities.'),
('001069','draft','2009-09-21','DISA FSO','technical','The organization employs automated mechanisms to detect the presence of unauthorized software on organizational information systems and notify designated organizational officials in accordance with the organization-defined frequency.',NULL,NULL,NULL),
('001070','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for employing automated mechanisms to detect the presence of unauthorized software on organizational information systems and notify designated organizational officials.',NULL,NULL,NULL),
('001071','draft','2009-09-21','DISA FSO','policy','The organization reviews historic audit logs to determine if a vulnerability identified in the information system has been previously exploited.','RA-5(8).1','The organization being inspected/assessed reviews audit logs and determines if the identified vulnerability has been previously exploited within the information system. Any findings must be documented and acted upon IAW IR-1.','The organization conducting the inspection/assessment obtains and examines the audit trail to determine if the organization has documented any previously identified exploited vulnerabilities.'),
('001072','draft','2009-09-21','DISA FSO','policy','The organization employs an independent penetration agent or penetration team to conduct a vulnerability analysis on the information system.',NULL,NULL,NULL),
('001073','draft','2009-09-21','DISA FSO','policy','The organization employs an independent penetration agent or penetration team to perform penetration testing on the information system based on the vulnerability analysis to determine the exploitability of identified vulnerabilities.',NULL,NULL,NULL),
('001074','draft','2009-09-21','DISA FSO','policy','The organization develops a system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SC-1.3','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for developing a system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for developing a system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.'),
('001075','draft','2009-09-21','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles the system and communications protection policy.','SC-1.4','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for disseminating the system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for disseminating the system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.'),
('001076','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the system and communications protection policy in accordance with organization-defined frequency.','SC-1.7','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for reviewing and updating the system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for reviewing and updating the system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.'),
('001077','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency for reviewing and updating the system and communications protection policy.','SC-1.8','DoD has defined the frequency as every 5 years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 5 years.'),
('001078','draft','2009-09-21','DISA FSO','policy','The organization develops system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','SC-1.5','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for developing system and communications protection procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for developing system and communications protection procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.'),
('001079','draft','2009-09-21','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles the procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','SC-1.6','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for disseminating the procedures to facilitate the implementation of the system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.','DoDI 8523.01 \"Communications Security (COMSEC)\" meets the DoD requirement for disseminating the procedures to facilitate the implementation of the system and communications protection policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.'),
('001080','draft','2009-09-21','DISA FSO','policy','The organization reviews and updates the system and communications protection procedures in accordance with organization-defined frequency.','SC-1.9','DoDI 8523.01 \"Communications Security (COMSEC)\"meets the DoD requirement for reviewing and updating the system and communications protection procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.','DoDI 8523.01 \"Communications Security (COMSEC)\"meets the DoD requirement for reviewing and updating the system and communications protection procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8523.01.'),
('001081','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of system and communications protection procedure reviews and updates.','SC-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001082','draft','2009-09-21','DISA FSO','technical','The information system separates user functionality (including user interface services) from information system management functionality.','SC-2.1','The organization being inspected/assessed configures the information system to separate user functionality (including user interface services) from information system management functionality. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1082.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to separate user functionality (including user interface services) from information system management functionality. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1082.'),
('001083','draft','2009-09-21','DISA FSO','technical','The information system prevents the presentation of information system management-related functionality at an interface for non-privileged users.','SC-2(1).1','The organization being inspected/assessed configures the information system to prevent the presentation of information system management-related functionality at an interface for non-privileged users. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1083.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent the presentation of information system management-related functionality at an interface for non-privileged users. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1083.'),
('001084','draft','2009-09-21','DISA FSO','technical','The information system isolates security functions from nonsecurity functions.','SC-3.1','The organization being inspected/assessed configures the information system to isolate security functions from nonsecurity functions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1084.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to isolate security functions from nonsecurity functions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1084.'),
('001085','draft','2009-09-21','DISA FSO','technical','The information system utilizes underlying hardware separation mechanisms to implement security function isolation.','SC-3(1).1','The organization being inspected/assessed configures the information system to utilize underlying hardware separation mechanisms to implement security function isolation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1085.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to utilize underlying hardware separation mechanisms to implement security function isolation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1085.'),
('001086','draft','2009-09-21','DISA FSO','technical','The information system isolates security functions enforcing access and information flow control from both nonsecurity functions and from other security functions.','SC-3(2).1','The organization being inspected/assessed configures the information system to isolate security functions enforcing access and information flow control from both nonsecurity functions and from other security functions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1086.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to isolate security functions enforcing access and information flow control from both nonsecurity functions and from other security functions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1086.'),
('001087','draft','2009-09-21','DISA FSO','technical','The organization implements an information system isolation boundary to minimize the number of nonsecurity functions included within the boundary containing security functions.',NULL,NULL,NULL),
('001088','draft','2009-09-21','DISA FSO','policy','The organization implements security functions as largely independent modules that avoid unnecessary interactions between modules.',NULL,NULL,NULL),
('001089','draft','2009-09-21','DISA FSO','technical','The organization implements security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.','SC-3(5).1','The organization being inspected/assessed configures the information system to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1089.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1089.'),
('001090','draft','2009-09-21','DISA FSO','technical','The information system prevents unauthorized and unintended information transfer via shared system resources.','SC-4.1','The organization being inspected/assessed configures the information system to prevent unauthorized and unintended information transfer via shared system resources. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1090.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent unauthorized and unintended information transfer via shared system resources. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1090.'),
('001091','draft','2009-09-21','DISA FSO','technical','The information system does not share resources that are used to interface with systems operating at different security levels.',NULL,NULL,NULL),
('001092','draft','2009-09-21','DISA FSO','technical','The information system protects against or limits the effects of the organization-defined or referenced types of denial of service attacks.',NULL,NULL,NULL),
('001093','draft','2009-09-21','DISA FSO','policy','The organization defines the types of denial of service attacks (or provides references to sources of current denial of service attacks) that can be addressed by the information system.','SC-5.1','The organization being inspected/assessed defines and documents the types of denial of service attacks (or provides references to sources of current denial of service attacks) that can be addressed by the information system. DoD has determined the types of denial of service attacks are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented types of denial of service attacks to ensure the organization being inspected/assessed defines the types of denial of service attacks (or provides references to sources of current denial of service attacks) that can be addressed by the information system. DoD has determined the types of denial of service attacks are not appropriate to define at the Enterprise level.'),
('001094','draft','2009-09-21','DISA FSO','technical','The information system restricts the ability of individuals to launch organization-defined denial of service attacks against other information systems.','SC-5(1).1','The organization being inspected/assessed configures the information system to restrict the ability of individuals to launch denial of service attacks defined in SC-5 (1), CCI 2387 against other information systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1094.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to restrict the ability of individuals to launch denial of service attacks defined in SC-5 (1), CCI 2387 against other information systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1094.'),
('001095','draft','2009-09-21','DISA FSO','technical','The information system manages excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial of service attacks.','SC-5(2).1','The organization being inspected/assessed configures the information system to manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial of service attacks. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1095.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial of service attacks. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1095.'),
('001096','draft','2009-09-21','DISA FSO','technical','The information system limits the use of resources by priority.',NULL,NULL,NULL),
('001097','draft','2009-09-21','DISA FSO','policy','The information system monitors and controls communications at the external boundary of the information system and at key internal boundaries within the system.','SC-7.1','The organization being inspected/assessed documents and implements processes to monitor and control communications at the external boundary of the system and at key internal boundaries within the system. The organization must maintain an audit trail of monitoring activities.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring activities to ensure the organization being inspected/assessed monitors and controls communications at the external boundary of the system and at key internal boundaries within the system.'),
('001098','draft','2009-09-21','DISA FSO','policy','The information system connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture.','SC-7.3','The organization being inspected/assessed designs the information system to enforce requirements that components connect to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying component connectivity to ensure the organization being inspected/assessed connects to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture.'),
('001099','draft','2009-09-21','DISA FSO','policy','The organization physically allocates publicly accessible information system components to separate subnetworks with separate physical network interfaces.',NULL,NULL,NULL),
('001100','draft','2009-09-21','DISA FSO','technical','The information system prevents public access into the organization\'s internal networks except as appropriately mediated by managed interfaces employing boundary protection devices.',NULL,NULL,NULL),
('001101','draft','2009-09-21','DISA FSO','policy','The organization limits the number of external network connections to the information system.','SC-7(3).1','The organization being inspected/assessed documents and implements information system access control mechanisms to limit the number of external connections to the information system.','The organization conducting the inspection/assessment obtains and examines the documented access control mechanisms to ensure that the organization being inspected/assessed limits the number of external network connections to the information system.'),
('001102','draft','2009-09-21','DISA FSO','policy','The organization implements a managed interface for each external telecommunication service.','SC-7(4).1','The organization being inspected/assessed designs the information system to have a managed interface for each telecommunication service.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying system interfaces to ensure the organization being inspected/assessed implements a managed interface for each external telecommunication service.'),
('001103','draft','2009-09-21','DISA FSO','policy','The organization establishes a traffic flow policy for each managed interface for each external telecommunication service.','SC-7(4).2','The organization being inspected/assessed defines and documents a traffic flow policy for each managed interface for each external telecommunication service.','The organization conducting the inspection/assessment obtains and examines the documented traffic flow policy to ensure the organization being inspected/assessed establishes a traffic flow policy for each managed interface for each external telecommunication service.'),
('001104','draft','2009-09-21','DISA FSO','policy','The organization employs security controls as needed to protect the confidentiality and integrity of the information being transmitted.',NULL,NULL,NULL),
('001105','draft','2009-09-21','DISA FSO','policy','The organization documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need for each external telecommunication service.','SC-7(4).4','The organization being inspected/assessed documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need for each external telecommunication service.','The organization conducting the inspection/assessment obtains and examines the documented exceptions to the traffic flow policy to ensure the organization being inspected/assessed identifies each exception with supporting mission/business need and duration of that need for each external telecommunication service.'),
('001106','draft','2009-09-21','DISA FSO','policy','The organization reviews exceptions to the traffic flow policy on an organization-defined frequency for each external telecommunication service.','SC-7(4).5','The organization being inspected/assessed implements a process to review exceptions to the traffic flow policy every 180 days for each external telecommunication service. The organization must maintain an audit trail of reviews. DoD has defined the frequency as every 180 days.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews to ensure the organization being inspected/assessed reviews exceptions to the traffic flow policy every 180 days for each external telecommunication service. DoD has defined the frequency as every 180 days.'),
('001107','draft','2009-09-21','DISA FSO','policy','The organization defines a frequency for the review of exceptions to the traffic flow policy for each external telecommunication service.','SC-7(4).6','DoD has defined the frequency as every 180 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 180 days.'),
('001108','draft','2009-09-21','DISA FSO','policy','The organization removes traffic flow policy exceptions that are no longer supported by an explicit mission/business need for each external telecommunication service.','SC-7(4).7','The organization being inspected/assessed documents and implements a process to remove traffic flow policy exceptions that are no longer supported by an explicit mission/business need for each external telecommunication service.','The organization conducting the inspection/assessment obtains and examines the documented process as well as a sampling of existing exceptions to ensure the organization being inspected/assessed removes traffic flow policy exceptions that are no longer supported by an explicit mission/business need for each external telecommunication service.'),
('001109','draft','2009-09-21','DISA FSO','technical','The information system at managed interfaces denies network communications traffic by default and allows network communications traffic by exception (i.e., deny all, permit by exception).','SC-7(5).1','The organization being inspected/assessed configures the information system to deny network communications traffic at managed interfaces by default and allows network communications traffic by exception (i.e., deny all, permit by exception). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1109.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to deny network communications traffic at managed interfaces by default and allows network communications traffic by exception (i.e., deny all, permit by exception). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1109.'),
('001110','draft','2009-09-21','DISA FSO','policy','The organization prevents the unauthorized release of information outside of the information system boundary or any unauthorized communication through the information system boundary when there is an operational failure of the boundary protection mechanisms.',NULL,NULL,NULL),
('001111','draft','2009-09-21','DISA FSO','technical','The information system prevents remote devices that have established a non-remote connection with the system from communicating outside of that communications path with resources in external networks.',NULL,NULL,NULL),
('001112','draft','2009-09-21','DISA FSO','policy','The information system routes organization-defined internal communications traffic to organization-defined external networks through authenticated proxy servers at managed interfaces.','SC-7(8).1','The organization being inspected/assessed configures the information system to route protocols as designated by PPSM guidance (e.g. HTTPS, HTTP, FTP, SNMP) to any network external to the authorization boundary through authenticated proxy servers at managed interfaces. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1112. DoD has defined the internal communications traffic as protocols as designated by PPSM guidance (e.g. HTTPS, HTTP, FTP, SNMP). DoD has defined the external networks as any network external to the authorization boundary.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to route protocols as designated by PPSM guidance (e.g. HTTPS, HTTP, FTP, SNMP) to any network external to the authorization boundary through authenticated proxy servers at managed interfaces. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1112. DoD has defined the internal communications traffic as protocols as designated by PPSM guidance (e.g. HTTPS, HTTP, FTP, SNMP). DoD has defined the external networks as any network external to the authorization boundary.'),
('001113','draft','2009-09-21','DISA FSO','policy','The organization defines the internal communications traffic to be routed to external networks.','SC-7(8).2','DoD has defined the internal communications traffic as protocols as designated by PPSM guidance (e.g. HTTPS, HTTP, FTP, SNMP).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the internal communications traffic as protocols as designated by PPSM guidance (e.g. HTTPS, HTTP, FTP, SNMP).'),
('001114','draft','2009-09-21','DISA FSO','policy','The organization defines the external networks to which organization-defined internal communications traffic should be routed.','SC-7(8).3','DoD has defined the external networks as any network external to the authorization boundary.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external networks as any network external to the authorization boundary.'),
('001115','draft','2009-09-21','DISA FSO','technical','The information system, at managed interfaces, denies network traffic and audits internal users (or malicious code) posing a threat to external information systems.',NULL,NULL,NULL),
('001116','draft','2009-09-21','DISA FSO','policy','The organization prevents the unauthorized exfiltration of information across managed interfaces.','SC-7(10).1','The organization being inspected/assessed documents and implements mechanisms to prevent the unauthorized exfiltration of information across managed interfaces.','The organization conducting the inspection/assessment obtains and examines the documented mechanisms to ensure the organization being inspected/assessed prevents the unauthorized exfiltration of information across managed interfaces.'),
('001117','draft','2009-09-21','DISA FSO','technical','The information system checks incoming communications to ensure the communications are coming from an authorized source and routed to an authorized destination.',NULL,NULL,NULL),
('001118','draft','2009-09-21','DISA FSO','technical','The information system implements host-based boundary protection mechanisms for servers, workstations, and mobile devices.',NULL,NULL,NULL),
('001119','draft','2009-09-21','DISA FSO','policy','The organization isolates organization-defined information security tools, mechanisms, and support components from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system.','SC-7(13).1','The organization being inspected/assessed designs the information system to isolate key information security tools, mechanisms, and support components such as, but not limited to PKI, Patching infrastructure, HBSS, CND Tools, Special Purpose Gateway, vulnerability tracking systems, honeypots, internet access points (IAPs); network element and data center administrative/management traffic; Demilitarized Zones (DMZs), Server farms/computing centers, centralized audit log servers etc. from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system. DoD has defined the key information security tools, mechanisms, and support components as key information security tools, mechanisms, and support components such as, but not limited to PKI, Patching infrastructure, HBSS, CND Tools, Special Purpose Gateway, vulnerability tracking systems, honeypots, internet access points (IAPs); network element and data center administrative/management traffic; Demilitarized Zones (DMZs), Server farms/computing centers, centralized audit log servers etc. ','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying component partitioning to ensure the organization being inspected/assessed isolates key information security tools, mechanisms, and support components such as, but not limited to PKI, Patching infrastructure, HBSS, CND Tools, Special Purpose Gateway, vulnerability tracking systems, honeypots, internet access points (IAPs); network element and data center administrative/management traffic; Demilitarized Zones (DMZs), Server farms/computing centers, centralized audit log servers etc. from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system. DoD has defined the key information security tools, mechanisms, and support components as key information security tools, mechanisms, and support components such as, but not limited to PKI, Patching infrastructure, HBSS, CND Tools, Special Purpose Gateway, vulnerability tracking systems, honeypots, internet access points (IAPs); network element and data center administrative/management traffic; Demilitarized Zones (DMZs), Server farms/computing centers, centralized audit log servers etc.'),
('001120','draft','2009-09-21','DISA FSO','policy','The organization defines key information security tools, mechanisms, and support components to be isolated.','SC-7(13).2','DoD has defined the key information security tools, mechanisms, and support components as key information security tools, mechanisms, and support components such as, but not limited to PKI, Patching infrastructure, HBSS, CND Tools, Special Purpose Gateway, vulnerability tracking systems, honeypots, internet access points (IAPs); network element and data center administrative/management traffic; Demilitarized Zones (DMZs), Server farms/computing centers, centralized audit log servers etc.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the key information security tools, mechanisms, and support components as key information security tools, mechanisms, and support components such as, but not limited to PKI, Patching infrastructure, HBSS, CND Tools, Special Purpose Gateway, vulnerability tracking systems, honeypots, internet access points (IAPs); network element and data center administrative/management traffic; Demilitarized Zones (DMZs), Server farms/computing centers, centralized audit log servers etc.'),
('001121','draft','2009-09-21','DISA FSO','policy','The organization protects against unauthorized physical connections at organization-defined managed interfaces.','SC-7(14).1','The organization being inspected/assessed documents and implements mechanisms to protect against unauthorized physical connections at internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways. DoD has defined the managed interfaces as internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.','The organization conducting the inspection/assessment obtains and examines the documented mechanisms to ensure the organization being inspected/assessed protects against unauthorized physical connections at internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.\n\nDoD has defined the managed interfaces as internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.'),
('001122','draft','2009-09-21','DISA FSO','policy','The organization defines the managed interfaces where boundary protections against unauthorized physical connections are to be implemented.','SC-7(14).2','DoD has defined the managed interfaces as internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the managed interfaces as internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.'),
('001123','draft','2009-09-21','DISA FSO','policy','The information system routes all networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.','SC-7(15).1','The organization being inspected/assessed designs the information system to route all networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying network data flow to ensure the organization being inspected/assessed routes all networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.'),
('001124','draft','2009-09-21','DISA FSO','technical','The information system prevents discovery of specific system components composing a managed interface.','SC-7(16).1','The organization being inspected/assessed configures the information system to prevent discovery of specific system components composing a managed interface. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1124.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent discovery of specific system components composing a managed interface. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1124.'),
('001125','draft','2009-09-21','DISA FSO','technical','The information system enforces adherence to protocol format.','SC-7(17).1','The organization being inspected/assessed configures the information system to enforce adherence to protocol format. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1125.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce adherence to protocol format. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1125.'),
('001126','draft','2009-09-21','DISA FSO','technical','The information system fails securely in the event of an operational failure of a boundary protection device.','SC-7(18).1','The organization being inspected/assessed configures the information system to fail securely in the event of an operational failure of a boundary protection device. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1126.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to fail securely in the event of an operational failure of a boundary protection device. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1126.'),
('001127','draft','2009-09-21','DISA FSO','technical','The information system protects the integrity of transmitted information.',NULL,NULL,NULL),
('001128','draft','2009-09-21','DISA FSO','technical','The organization employs cryptographic mechanisms to recognize changes to information during transmission unless otherwise protected by alternative physical measures.',NULL,NULL,NULL),
('001129','draft','2009-09-21','DISA FSO','technical','The information system maintains the integrity of information during aggregation, packaging, and transformation in preparation for transmission.',NULL,NULL,NULL),
('001130','draft','2009-09-21','DISA FSO','technical','The information system protects the confidentiality of transmitted information.',NULL,NULL,NULL),
('001131','draft','2009-09-21','DISA FSO','technical','The organization employs cryptographic mechanisms to prevent unauthorized disclosure of information during transmission unless otherwise protected by alternative physical measures.',NULL,NULL,NULL),
('001132','draft','2009-09-21','DISA FSO','technical','The information system maintains the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission.',NULL,NULL,NULL),
('001133','draft','2009-09-21','DISA FSO','technical','The information system terminates the network connection associated with a communications session at the end of the session or after an organization-defined time period of inactivity.','SC-10.1','The organization being inspected/assessed configures the information system to terminate the network connection associated with a communications session at the end of the session or after 10 minutes in band management and 15 minutes for user sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1133. DoD has defined the time period as 10 minutes in band management and 15 minutes for user sessions.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to terminate the network connection associated with a communications session at the end of the session or after 10 minutes in band management and 15 minutes for user sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1133. DoD has defined the time period as 10 minutes in band management and 15 minutes for user sessions.'),
('001134','draft','2009-09-21','DISA FSO','policy','The organization defines the time period of inactivity after which the information system terminates a network connection associated with a communications session.','SC-10.2','DoD has defined the time period as 10 minutes in band management and 15 minutes for user sessions.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 10 minutes in band management and 15 minutes for user sessions.'),
('001135','draft','2009-09-21','DISA FSO','policy','The information system establishes a trusted communications path between the user and organization-defined security functions within the information system.','SC-11.1','The organization being inspected/assessed designs and configures the information system to establish a trusted communications path between the user and providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling) within the information system. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1135. DoD has defined the security functions as providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling).','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to establish a trusted communications path between the user and providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling) within the information system. Additionally, the organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying data flow to ensure the organization being inspected/assessed establishes a trusted communications path between the user and providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling) within the information system. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1135. DoD has defined the security functions as providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling).'),
('001136','draft','2009-09-21','DISA FSO','policy','The organization defines security functions include information system authentication and reauthentication.',NULL,NULL,NULL),
('001137','draft','2009-09-21','DISA FSO','policy','The organization establishes cryptographic keys for required cryptography employed within the information system.',NULL,NULL,NULL),
('001138','draft','2009-09-21','DISA FSO','policy','The organization manages cryptographic keys for required cryptography employed within the information system.',NULL,NULL,NULL),
('001139','draft','2009-09-21','DISA FSO','policy','The organization maintains availability of information in the event of the loss of cryptographic keys by users.','SC-12(1).1','The organization being inspected/assessed documents and implements a process to maintain availability of information in the event of the loss of cryptographic keys by users.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed maintains availability of information in the event of the loss of cryptographic keys by users.'),
('001140','draft','2009-09-21','DISA FSO','technical','The organization produces, controls, and distributes symmetric cryptographic keys using NIST-approved or NSA-approved key management technology and processes.',NULL,NULL,NULL),
('001141','draft','2009-09-21','DISA FSO','technical','The organization produces, controls, and distributes symmetric and asymmetric cryptographic keys using NSA-approved key management technology and processes.',NULL,NULL,NULL),
('001142','draft','2009-09-21','DISA FSO','technical','The organization produces, controls, and distributes asymmetric cryptographic keys using approved PKI Class 3 certificates or prepositioned keying material.',NULL,NULL,NULL),
('001143','draft','2009-09-21','DISA FSO','technical','The organization produces, controls, and distributes asymmetric cryptographic keys using approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user\'s private key.',NULL,NULL,NULL),
('001144','draft','2009-09-21','DISA FSO','technical','The information system implements required cryptographic protections using cryptographic modules that comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.',NULL,NULL,NULL),
('001145','draft','2009-09-21','DISA FSO','technical','The organization employs, at a minimum, FIPS-validated cryptography to protect unclassified information.',NULL,NULL,NULL),
('001146','draft','2009-09-21','DISA FSO','technical','The organization employs NSA-approved cryptography to protect classified information.',NULL,NULL,NULL),
('001147','draft','2009-09-21','DISA FSO','technical','The organization employs, at a minimum, FIPS-validated cryptography to protect information when such information must be separated from individuals who have the necessary clearances yet lack the necessary access approvals.',NULL,NULL,NULL),
('001148','draft','2009-09-21','DISA FSO','technical','The organization employs FIPS-validated or NSA-approved cryptography to implement digital signatures.',NULL,NULL,NULL),
('001149','draft','2009-09-21','DISA FSO','technical','The information system protects the integrity and availability of publicly available information and applications.',NULL,NULL,NULL),
('001150','draft','2009-09-21','DISA FSO','technical','The information system prohibits remote activation of collaborative computing devices, excluding the organization-defined exceptions where remote activation is to be allowed.','SC-15.1','The organization being inspected/assessed configures the information system to prohibit remote activation of collaborative computing devices excluding dedicated VTC suites located in approved VTC locations that are centrally managed. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1150. DoD has defined the exceptions as dedicated VTC suites located in approved VTC locations that are centrally managed.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prohibit remote activation of collaborative computing devices excluding dedicated VTC suites located in approved VTC locations that are centrally managed. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1150. DoD has defined the exceptions as dedicated VTC suites located in approved VTC locations that are centrally managed.'),
('001151','draft','2009-09-21','DISA FSO','policy','The organization defines exceptions to the prohibition of collaborative computing devices where remote activation is to be allowed.','SC-15.2','DoD has defined the exceptions as dedicated VTC suites located in approved VTC locations that are centrally managed.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the exceptions as dedicated VTC suites located in approved VTC locations that are centrally managed.'),
('001152','draft','2009-09-21','DISA FSO','technical','The information system provides an explicit indication of use to users physically present at collaborative computing devices.','SC-15.3','The organization being inspected/assessed configures the information system to provide an explicit indication of use to users physically present at collaborative computing devices. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1152.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide an explicit indication of use to users physically present at collaborative computing devices. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1152.'),
('001153','draft','2009-09-21','DISA FSO','technical','The information system provides physical disconnect of collaborative computing devices in a manner that supports ease of use.','SC-15(1).1','The organization being inspected/assessed provides a means of physical disconnect of collaborative computing devices in a manner that supports ease of use. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1153.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed provides a means of physical disconnect of collaborative computing devices in a manner that supports ease of use. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1153.'),
('001154','draft','2009-09-21','DISA FSO','technical','The information system or supporting environment blocks both inbound and outbound traffic between instant messaging clients that are independently configured by end users and external service providers.',NULL,NULL,NULL),
('001155','draft','2009-09-21','DISA FSO','policy','The organization disables or removes collaborative computing devices from organization-defined information systems or information system components in organization-defined secure work areas.','SC-15(3).1','The organization being inspected/assessed implements a process to disable or remove any device used that may incorporate camera, microphone, or smart board capability in secure work areas defined in SC-15 (3), CCI 1156. DoD has defined information systems or information system components as any device used that may incorporate camera, microphone, or smart board capability.','The organization conducting the inspection/assessment obtains and examines the organization defined secure work area to ensure that any device that may incorporate camera, microphone, or smart board capability has been disabled or removed. DoD has defined information systems or information system components as any device used that may incorporate camera, microphone, or smart board capability.'),
('001156','draft','2009-09-21','DISA FSO','policy','The organization defines secure work areas where collaborative computing devices are to be disabled or removed.','SC-15(3).2','The organization being inspected/assessed defines and documents secure work areas where collaborative computing devices are to be disabled or removed. DoD has determined the secure work areas are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented secure work areas to ensure the organization being inspected/assessed defines secure work areas where collaborative computing devices are to be disabled or removed. DoD has determined the secure work areas are not appropriate to define at the Enterprise level.'),
('001157','draft','2009-09-21','DISA FSO','policy','The information system associates organization-defined security attributes with information exchanged between information systems.','SC-16.1','The organization being inspected/assessed implements association of security attributes defined in SC-16, CCI 2454 with information exchanged between information systems.','The organization conducting the inspection/assessment examines the information system to ensure it associates security attributes defined in SC-16, CCI 2454 with information exchanged between information systems.'),
('001158','draft','2009-09-21','DISA FSO','technical','The information system validates the integrity of transmitted security attributes.','SC-16(1).1','The organization being inspected/assessed configures the information system to validate the integrity of transmitted security attributes. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1158.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to validate the integrity of transmitted security attributes. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1158.'),
('001159','draft','2009-09-21','DISA FSO','policy','The organization issues public key certificates under an organization-defined certificate policy or obtains public key certificates from an approved service provider.','SC-17.1','The organization being inspected/assessed configures the information system to issue public key certificates under DoDI 8520.02, \"Public Key Infrastructure (PKI) and Public Key (PK) Enabling\" or obtains public key certificates from an approved service provider. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1159. DoD has defined the certificate policy as DoDI 8520.02, \"Public Key Infrastructure (PKI) and Public Key (PK) Enabling.\"','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to issue public key certificates under DoDI 8520.02, \"Public Key Infrastructure (PKI) and Public Key (PK) Enabling\" or obtains public key certificates from an approved service provider. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1159. DoD has defined the certificate policy as DoDI 8520.02, \"Public Key Infrastructure (PKI) and Public Key (PK) Enabling.\"'),
('001160','draft','2009-09-21','DISA FSO','policy','The organization defines acceptable and unacceptable mobile code and mobile code technologies.','SC-18.1','The organization being inspected/assessed defines and documents acceptable and unacceptable mobile code and mobile code technologies IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must define IAW the STIG/SRG guidance that pertains to CCI 1160.','The organization conducting the inspection/assessment obtains and examines the documented acceptable and unacceptable mobile code and mobile code technologies to ensure the organization being inspected/assessed defines acceptable and unacceptable mobile code and mobile code technologies IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has defined acceptable and unacceptable mobile code and mobile code technologies IAW the applicable STIGs and SRGs pertaining to CCI 1160.'),
('001161','draft','2009-09-21','DISA FSO','policy','The organization establishes usage restrictions for acceptable mobile code and mobile code technologies.','SC-18.2','The organization being inspected/assessed documents usage restrictions for acceptable mobile code and mobile code technologies IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must establish IAW the STIG/SRG guidance that pertains to CCI 1161.','The organization conducting the inspection/assessment obtains and examines the documented usage restrictions to ensure the organization being inspected/assessed establishes usage restrictions for acceptable mobile code and mobile code technologies IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has established usage restrictions IAW the applicable STIGs and SRGs pertaining to CCI 1161.'),
('001162','draft','2009-09-21','DISA FSO','policy','The organization establishes implementation guidance for acceptable mobile code and mobile code technologies.','SC-18.3','The Protection Profile for Web Browsers and Application SRG\nmeet the DoD requirement to establish implementation guidance for acceptable mobile code and mobile code technologies.\n\nDoD Components are automatically compliant with this CCI because they are covered by the Protection Profile for Web Browsers and Application SRG.','The Protection Profile for Web Browsers and Application SRG\nmeet the DoD requirement to establish implementation guidance for acceptable mobile code and mobile code technologies.\n\nDoD Components are automatically compliant with this CCI because they are covered by the Protection Profile for Web Browsers and Application SRG.'),
('001163','draft','2009-09-21','DISA FSO','policy','The organization authorizes the use of mobile code within the information system.','SC-18.4','The organization being inspected/assessed documents mobile code which is authorized for use within the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of mobile code which is authorized for use within the information system and examines the information system to ensure that all used mobile code is authorized.'),
('001164','draft','2009-09-21','DISA FSO','policy','The organization monitors the use of mobile code within the information system.','SC-18.5','The organization being inspected/assessed documents and implements a process to monitor the use of mobile code within the information system.','The organization conducting the inspection/assessment obtains and examines the documented process as well as any artifacts applicable to monitoring of mobile code to ensure the organization being inspected/assessed monitors the use of mobile code within the information system.'),
('001165','draft','2009-09-21','DISA FSO','policy','The organization controls the use of mobile code within the information system.','SC-18.6','The organization being inspected/assessed documents and implements a process to control the use of mobile code within the information system.','The organization conducting the inspection/assessment obtains and examines the documented process and examines the information system to ensure the organization being inspected/assessed controls the use of mobile code within the information system.'),
('001166','draft','2009-09-21','DISA FSO','technical','The information system identifies organization-defined unacceptable mobile code.','SC-18(1).1','The organization being inspected/assessed configures the information system to identify unacceptable mobile code defined in SC-18 (1), CCI 2458. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1166.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to identify unacceptable mobile code defined in SC-18 (1), CCI 2458. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1166.'),
('001167','draft','2009-09-21','DISA FSO','policy','The organization ensures the development of mobile code to be deployed in information systems meets organization-defined mobile code requirements.','SC-18(2).1','The organization being inspected/assessed documents and implements a process to develop mobile code IAW the requirements defined in CCI 1168. ','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed develops mobile code IAW the requirements defined in CCI 1168.'),
('001168','draft','2009-09-21','DISA FSO','policy','The organization defines requirements for the acquisition, development, and use of mobile code.','SC-18(2).2','The organization being inspected/assessed defines and documents requirements for the acquisition, development, and use of mobile code. The requirements must result in the acquisition and development of mobile code which complies with the Protection Profile for Web Browsers and Application SRG.\nDoD has determined the requirements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented requirements to ensure the organization being inspected/assessed defines requirements for the acquisition, development, and use of mobile code.\nDoD has determined the requirements are not appropriate to define at the Enterprise level.'),
('001169','draft','2009-09-21','DISA FSO','technical','The information system prevents the download of organization-defined unacceptable mobile code.','SC-18(3).1','The organization being inspected/assessed configures the information system to prevent the download of unacceptable mobile code defined in CCI 2459.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1169.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent the download of unacceptable mobile code defined in CCI 2459.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1169.'),
('001170','draft','2009-09-21','DISA FSO','technical','The information system prevents the automatic execution of mobile code in organization-defined software applications.','SC-18(4).1','The organization being inspected/assessed configures the information system to prevent the automatic execution of unacceptable mobile code in software applications defined in CCI 1171.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1170.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent the automatic execution of unacceptable mobile code in software applications defined in CCI 1171.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1170.'),
('001171','draft','2009-09-21','DISA FSO','policy','The organization defines software applications in which automatic mobile code execution is to be prohibited.','SC-18(4).2','DoD has defined the software applications in which automatic mobile code execution is to be prohibited as the software applications defined in the Protection Profile for Web Browsers and Application SRG.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\nDoD has defined the software applications in which automatic mobile code execution is to be prohibited as the software applications defined in the Protection Profile for Web Browsers and Application SRG.'),
('001172','draft','2009-09-21','DISA FSO','policy','The organization defines actions to be enforced by the information system before executing mobile code.','SC-18(4).3','DoD has defined the actions as the user be prompted.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the actions as the user be prompted.'),
('001173','draft','2009-09-21','DISA FSO','policy','The organization establishes usage restrictions for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously.','SC-19.1','The organization being inspected/assessed establishes and documents usage restrictions for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously.','The organization conducting the inspection/assessment obtains and examines the documented usage restrictions to ensure the organization being inspected/assessed establishes usage restrictions for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously.'),
('001174','draft','2009-09-21','DISA FSO','policy','The organization establishes implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously.','SC-19.2','The Voice and Video over Internet Protocol (V-VoIP) STIG meets the DoD requirement for establishing implementation guidance for Voice over Internet Protocol (VoIP) technologies.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, V-VoIP STIG.','The V-VoIP STIG meets the DoD requirement for establishing implementation guidance for Voice over Internet Protocol (VoIP) technologies.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, V-VoIP STIG.'),
('001175','draft','2009-09-21','DISA FSO','policy','The organization authorizes the use of VoIP within the information system.','SC-19.3','The organization being inspected/assessed authorizes any appropriate usage of VoIP within the information system and documents those authorizations.','The organization conducting the inspection/assessment obtains and examines the documented authorizations and *insert language* to ensure the organization being inspected/assessed authorizes any appropriate usage of VoIP within the information system and documents those authorizations.'),
('001176','draft','2009-09-21','DISA FSO','policy','The organization monitors the use of VoIP within the information system.','SC-19.4','The organization being inspected/assessed documents and implements a process to monitor the use of VoIP within the information system. The organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trial of monitoring to ensure the organization being inspected/assessed monitors the use of VoIP within the information system.'),
('001177','draft','2009-09-21','DISA FSO','policy','The organization controls the use of VoIP within the information system.','SC-19.5','The organization being inspected/assessed designs the information system to control the use of VoIP within the information system','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying the use of VoIP to ensure the organization being inspected/assessed controls the use of VoIP within the information system.'),
('001178','draft','2009-09-21','DISA FSO','technical','The information system provides additional data origin authentication artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries.','SC-20.1','The organization being inspected/assessed configures the authoritative name server software for external queries to enable DNSSEC and creates resource records with digital signatures (RRSig) for each A record. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 1178.','The organization conducting the inspection/assessment:\n1. inspects the configuration files for the presence of DNSSEC records for each A record hosted in a zone;\n2. utilizes DNSSEC diagnostic tools, such as dig; and\n3. performs queries which will exercise the data flow path for authoritative name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 1178.'),
('001179','draft','2009-09-21','DISA FSO','technical','The information system, when operating as part of a distributed, hierarchical namespace, provides the means to indicate the security status of child zones.','SC-20.3','The organization being inspected/assessed configures the authoritative name server software to enable DNSSEC and creates delegation signer (DS) resource records for each child zone and place those records in the parent zone. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 1179.','The organization conducting the inspection/assessment inspect the configuration files for the presence of Delegation Signer (DS) Records for any child domains. Note: This is only applicable for zones with child domains. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 1179.'),
('001180','draft','2009-09-21','DISA FSO','technical','The information system performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources when requested by client systems.',NULL,NULL,NULL),
('001181','draft','2009-09-21','DISA FSO','technical','The information system performs data origin authentication and data integrity verification on all resolution responses received whether or not local client systems explicitly request this service.',NULL,NULL,NULL),
('001182','draft','2009-09-21','DISA FSO','policy','The information systems that collectively provide name/address resolution service for an organization are fault-tolerant.','SC-22.1','The organization being inspected/assessed implements a name service resolution architecture consisting of primary and secondary servers. The organization must document the architecture in the site security plan. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1182.','The organization conducting the inspection/assessment reviews the sites implementation documentation of the name resolution servers and verifies primary and alternate services are available. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1182.'),
('001183','draft','2009-09-21','DISA FSO','policy','The information systems that collectively provide name/address resolution service for an organization implement internal/external role separation.','SC-22.2','The organization being inspected/assessed implements a name service resolution architecture where recursive and authoritative server software is not installed on the same information system. The organization must document the architecture in the site security plan. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1183.','The organization conducting the inspection/assessment reviews the sites implementation documentation of the name resolution servers and verifies authoritative and recursive services are not hosted on the same information system. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1183.'),
('001184','draft','2009-09-21','DISA FSO','technical','The information system protects the authenticity of communications sessions.','SC-23.1','The organization being inspected/assessed configures the information system to protect the authenticity of communications sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1184.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect the authenticity of communications sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1184.'),
('001185','draft','2009-09-21','DISA FSO','technical','The information system invalidates session identifiers upon user logout or other session termination.','SC-23(1).1','The organization being inspected/assessed configures the information system to invalidate session identifiers upon user logout or other session termination. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1185.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to invalidate session identifiers upon user logout or other session termination. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1185.'),
('001186','draft','2009-09-21','DISA FSO','technical','The information system provides a readily observable logout capability whenever authentication is used to gain access to web pages.',NULL,NULL,NULL),
('001187','draft','2009-09-21','DISA FSO','technical','The information system generates a unique session identifier for each session.',NULL,NULL,NULL),
('001188','draft','2009-09-21','DISA FSO','technical','The information system generates unique session identifiers for each session with organization-defined randomness requirements.','SC-23(3).1','The organization being inspected/assessed configures the information system to generate unique session identifiers for each session with randomness requirements defined in SC-23 (3), CCI 1189. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1188.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to generate unique session identifiers for each session with randomness requirements defined in SC-23 (3), CCI 1189. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1188.'),
('001189','draft','2009-09-21','DISA FSO','policy','The organization defines randomness requirements for generating unique session identifiers.','SC-23(3).2','The organization being inspected/assessed defines and documents randomness requirements for generating unique session identifiers. DoD has determined the randomness requirements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented randomness requirements to ensure the organization being inspected/assessed defines randomness requirements for generating unique session identifiers. DoD has determined the randomness requirements are not appropriate to define at the Enterprise level.'),
('001190','draft','2009-09-21','DISA FSO','technical','The information system fails to an organization-defined known-state for organization-defined types of failures.','SC-24.1','The organization being inspected/assessed configures the information system to fail to a secure state for failures during system initialization, shutdown, and aborts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1190. DoD has defined the known state as secure state. DoD has defined the types of failures as failures during system initialization, shutdown, and aborts.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to fail to a secure state for failures during system initialization, shutdown, and aborts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1190. DoD has defined the known state as secure state. DoD has defined the types of failures as failures during system initialization, shutdown, and aborts.'),
('001191','draft','2009-09-21','DISA FSO','policy','The organization defines the known states the information system should fail to in the event of an organization-defined system failure.','SC-24.2','DoD has defined the known state as secure state.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the known state as secure state.'),
('001192','draft','2009-09-21','DISA FSO','policy','The organization defines types of failures for which the information system should fail to an organization-defined known state.','SC-24.3','DoD has defined the types of failures as failures during system initialization, shutdown, and aborts.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the types of failures as failures during system initialization, shutdown, and aborts.'),
('001193','draft','2009-09-21','DISA FSO','policy','The organization defines system state information that should be preserved in the event of a system failure.','SC-24.4','DoD has defined system state information as information necessary to determine cause of failure and to return to operations with least disruption to mission/ business processes.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined system state information as information necessary to determine cause of failure and to return to operations with least disruption to mission/ business processes.'),
('001194','draft','2009-09-21','DISA FSO','policy','The information system employs organization-defined information system components with minimal functionality and information storage.','SC-25.1','The organization being inspected/assessed employs information system components defined in SC-25, CCI 2471 with minimal functionality and information storage.','The organization conducting the inspection/assessment obtains and examines the hardware list to ensure the organization being inspected/assessed employs information system components defined in SC-25, CCI 2471 with minimal functionality and information storage.'),
('001195','draft','2009-09-21','DISA FSO','policy','The information system includes components specifically designed to be the target of malicious attacks for the purpose of detecting, deflecting, and analyzing such attacks.','SC-26.1','The organization being inspected/assessed designs the information system to include decoy components specifically designed to be the target of malicious attacks for the purpose of detecting, deflecting, and analyzing such attacks.','The organization conducting the inspection/assessment obtains and examines the network topology diagrams, architecture documentation, or any other documentation identifying decoy components to be attacked to ensure the organization being inspected/assessed includes components specifically designed to be the target of malicious attacks for the purpose of detecting, deflecting, and analyzing such attacks.'),
('001196','draft','2009-09-21','DISA FSO','policy','The information system includes components that proactively seek to identify malicious websites and/or web-based malicious code.','SC-35.1','The organization being inspected/assessed includes components in the information system that proactively seek to identify malicious websites and/or web-based malicious code.','The organization conducting the inspection/assessment obtains and examines the software list to ensure the organization being inspected/assessed includes components in the information system that proactively seek to identify malicious websites and/or web-based malicious code.'),
('001197','draft','2009-09-21','DISA FSO','policy','The information system includes organization-defined platform-independent applications.','SC-27.1','The organization being inspected/assessed includes platform-independent applications defined in SC-27, CCI 1198.','The organization conducting the inspection/assessment obtains and examines the software list to ensure the organization being inspected/assessed includes platform-independent applications defined in SC-27, CCI 1198.'),
('001198','draft','2009-09-21','DISA FSO','policy','The organization defines applications that are platform independent.','SC-27.2','The organization being inspected/assessed defines and documents applications that are platform independent. DoD has determined the applications are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented applications to ensure the organization being inspected/assessed defines applications that are platform independent. DoD has determined the applications are not appropriate to define at the Enterprise level.'),
('001199','draft','2009-09-21','DISA FSO','technical','The information system protects the confidentiality and/or integrity of organization-defined information at rest.','SC-28.1','The organization being inspected/assessed configures the information system to protect the confidentiality and/or integrity of organization-defined information at rest. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1199.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect the confidentiality and/or integrity of organization-defined information at rest. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1199.'),
('001200','draft','2009-09-21','DISA FSO','technical','The organization employs cryptographic mechanisms to prevent unauthorized disclosure of information at rest unless otherwise protected by alternative physical measures.',NULL,NULL,NULL),
('001201','draft','2009-09-21','DISA FSO','policy','The organization employs a diverse set of information technologies for organization-defined information system components in the implementation of the information system.','SC-29.1','The organization being inspected/assessed designs the information system to employ a diverse set of information technologies for information system components defined in SC-29, CCI 2480 in the implementation of the information system.','The organization conducting the inspection/assessment obtains and examines the hardware and software lists to ensure the organization being inspected/assessed employs a diverse set of information technologies for information system components defined in SC-29, CCI 2480 in the implementation of the information system.'),
('001202','draft','2009-09-21','DISA FSO','policy','The organization employs virtualization techniques to present information system components as other types of components, or components with differing configurations.',NULL,NULL,NULL),
('001203','draft','2009-09-21','DISA FSO','policy','The organization employs virtualization techniques to support the deployment of a diversity of operating systems that are changed on an organization-defined frequency.','SC-29(1).1','The organization being inspected/assessed designs the information system to employ virtualization techniques to support the deployment of a diversity of operating systems that are changed on the frequency defined in SC-29 (1), CCI 1204.','The organization conducting the inspection/assessment obtains and examines the hardware and software lists to ensure the organization being inspected/assessed employs virtualization techniques to support the deployment of a diversity of operating systems that are changed on the frequency defined in SC-29 (1), CCI 1204.'),
('001204','draft','2009-09-21','DISA FSO','policy','The organization defines the frequency of changes to operating systems and applications to support a diversity of deployments.','SC-29(1).2','The organization being inspected/assessed defines and documents the frequency of changes to operating systems and applications to support a diversity of deployments. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency of changes to operating systems and applications to support a diversity of deployments. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('001205','draft','2009-09-21','DISA FSO','policy','The organization employs randomness in the implementation of the virtualization techniques.',NULL,NULL,NULL),
('001206','draft','2009-09-21','DISA FSO','policy','The organization requires that information system developers/integrators perform a covert channel analysis to identify those aspects of system communication that are potential avenues for covert storage and timing channels.',NULL,NULL,NULL),
('001207','draft','2009-09-21','DISA FSO','policy','The organization tests a subset of the identified covert channels to determine which channels are exploitable.','SC-31(1).1','The organization being inspected/assessed tests a subset of the identified covert channels to determine which channels are exploitable. The organization must maintain an audit trail of testing.','The organization conducting the inspection/assessment obtains and examines the test results to ensure the organization being inspected/assessed tests a subset of the identified covert channels to determine which channels are exploitable.'),
('001208','draft','2009-09-21','DISA FSO','policy','The organization partitions the information system into components residing in separate physical domains (or environments) as deemed necessary.',NULL,NULL,NULL),
('001209','draft','2009-09-21','DISA FSO','technical','The information system protects the integrity of information during the processes of data aggregation, packaging, and transformation in preparation for transmission.',NULL,NULL,NULL),
('001210','draft','2009-09-21','DISA FSO','technical','The information system, at organization-defined information system components, loads and executes the operating environment from hardware-enforced, read-only media.','SC-34.2','The organization being inspected/assessed configures the information system to load and execute the operating environment from hardware-enforced, read-only media at information system components defined in SC-34, CCI 1212. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1210.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to load and execute the operating environment from hardware-enforced, read-only media at information system components defined in SC-34, CCI 1212. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1210.'),
('001211','draft','2009-09-21','DISA FSO','technical','The information system, at organization-defined information system components, loads and executes organization-defined applications from hardware-enforced, read-only media.','SC-34.3','The organization being inspected/assessed configures the information system to load and execute applications defined in SC-34, CCI 1213 from hardware-enforced, read-only media at information system components defined in SC-34, CCI 1212. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1211.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to load and execute applications defined in SC-34, CCI 1213 from hardware-enforced, read-only media at information system components defined in SC-34, CCI 1212. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1211.'),
('001212','draft','2009-09-21','DISA FSO','policy','The organization defines information system components on which the operating environment and organization-defined applications are loaded and executed from hardware-enforced, read-only media.','SC-34.1','The organization being inspected/assessed defines and documents information system components for which the operating environment and organization-defined applications are loaded and executed from hardware-enforced, read-only media. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines information system components for which the operating environment and organization-defined applications are loaded and executed from hardware-enforced, read-only media. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('001213','draft','2009-09-21','DISA FSO','policy','The organization defines applications that will be loaded and executed from hardware-enforced, read-only media.','SC-34.4','The organization being inspected/assessed defines and documents applications that will be loaded and executed from hardware-enforced, read-only media. DoD has determined the applications are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented applications to ensure the organization being inspected/assessed defines applications that will be loaded and executed from hardware-enforced, read-only media. DoD has determined the applications are not appropriate to define at the Enterprise level.'),
('001214','draft','2009-09-21','DISA FSO','policy','The organization employs organization-defined information system components with no writeable storage that are persistent across component restart or power on/off.','SC-34(1).1','The organization being inspected/assessed designs the information system to employ information system components defined in SC-34 (1), CCI 1215 with no writeable storage that are persistent across component restart or power on/off.','The organization conducting the inspection/assessment obtains and examines the hardware list to ensure the organization being inspected/assessed employs information system components defined in SC-34 (1), CCI 1215 with no writeable storage that are persistent across component restart or power on/off.'),
('001215','draft','2009-09-21','DISA FSO','policy','The organization defines the information system components to be employed with no writeable storage.','SC-34(1).2','The organization being inspected/assessed defines and documents the information system components to be employed with no writeable storage. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components to be employed with no writeable storage. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('001216','draft','2009-09-21','DISA FSO','policy','The organization protects the integrity of information prior to storage on read-only media.','SC-34(2).1','The organization being inspected/assessed documents and implements mechanisms to protect the integrity of the information prior to storage on read-only media.','The organization conducting the inspection/assessment obtains and examines the documented mechanisms to ensure the organization being inspected/assessed protects the integrity of the information prior to storage on read-only media.'),
('001217','draft','2009-09-22','DISA FSO','policy','The organization develops and documents a system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SI-1.2','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).'),
('001218','draft','2009-09-22','DISA FSO','policy','The organization disseminates the system and information integrity policy to organization-defined personnel or roles.','SI-1.3','DoD disseminates DoDI 8510.01 via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) that meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).'),
('001219','draft','2009-09-22','DISA FSO','policy','The organization reviews and updates system and information integrity policy in accordance with organization-defined frequency.','SI-1.6','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).'),
('001220','draft','2009-09-22','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the system and information integrity policy and associated system integrity controls.','SI-1.4','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) .'),
('001221','draft','2009-09-22','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the system and information integrity policy and associated system integrity controls.','SI-1.5','DoD disseminates DoDI 8510.01 via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) that meets the DoD requirement for a system and information integrity policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).'),
('001222','draft','2009-09-22','DISA FSO','policy','The organization reviews and updates system and information integrity procedures in accordance with organization-defined frequency.','SI-1.8','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).','Documenting and implementing the Risk Management Framework (RMF) for DoD IT (DoDI 8510.01) meets the DoD requirement for a system and information integrity procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, Risk Management Framework (RMF) for DoD IT (DoDI 8510.01).'),
('001223','draft','2009-09-22','DISA FSO','policy','The organization defines the frequency of system and information integrity policy reviews and updates.','SI-1.7','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10.'),
('001224','draft','2009-09-22','DISA FSO','policy','The organization defines the frequency of system and information integrity procedure reviews and updates.','SI-1.9','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('001225','draft','2009-09-22','DISA FSO','policy','The organization identifies information system flaws.','SI-2.1','The organization being inspected/assessed documents and implements a process to identify information system flaws. The process shall include review of the system through automated scans and manual checks to determine the existence of flaws such as IAVM, CVE, or other resources.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed identifies information system flaws.'),
('001226','draft','2009-09-22','DISA FSO','policy','The organization reports information system flaws.','SI-2.2','The organization being inspected/assessed reports information system flaws according to DoD Cybersecurity policy and organizational roles and responsibilities. The organization must report information system flaws in their POA&M.','The organization conducting the inspection/assessment obtains and examines the authorization package, verifies the POA&M is up to date and includes recently identified information system flaws, and verifies that the organization has notified appropriate personnel as defined by DoD Cybersecurity policy and organizational roles and responsibilities.'),
('001227','draft','2009-09-22','DISA FSO','policy','The organization corrects information system flaws.','SI-2.3','The organization being inspected/assessed corrects information system flaws within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).\n\nThe organization documents the corrections on their POA&M.\n\nDoD has defined the time period as within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization conducting the inspection/assessment obtains and examines the information system POA&M and examines the information system to ensure the organization being inspected/assessed corrects information system flaws.'),
('001228','draft','2009-09-22','DISA FSO','policy','The organization tests software updates related to flaw remediation for effectiveness before installation.','SI-2.4','The organization being inspected/assessed documents and implements a process to test software updates related to flaw remediation for effectiveness before installation. If the software update is being provided by a vendor who has documented the effectiveness of the update in fixing the affected IAVM/CVE, further testing by the organization may not be required.','The organization conducting the inspection/assessment obtains and examines the documented process and test results to ensure the organization being inspected/assessed tests software updates related to flaw remediation for effectiveness before installation.'),
('001229','draft','2009-09-22','DISA FSO','policy','The organization tests software updates related to flaw remediation for potential side effects before installation.','SI-2.5','The organization being inspected/assessed documents and implements a process for regression testing IAW CM-4 to identify any potential side effects before installation of software updates.','The organization conducting the inspection/assessment obtains and examines the documented process and test results to ensure the organization being inspected/assessed tests software updates related to flaw remediation for potential side effects before installation.'),
('001230','draft','2009-09-22','DISA FSO','policy','The organization incorporates flaw remediation into the organizational configuration management process.','SI-2.12','The organization being inspected/assessed documents within their configuration management plan, flaw remediation processes.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to ensure that it incorporates flaw remediation.'),
('001231','draft','2009-09-22','DISA FSO','policy','The organization centrally manages the flaw remediation process.','SI-2(1).1','The organization being inspected/assessed documents and implements a process to centrally manage the flaw remediation process.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed centrally manages the flaw remediation process.'),
('001232','draft','2009-09-22','DISA FSO','technical','The organization installs software updates automatically.',NULL,NULL,NULL),
('001233','draft','2009-09-22','DISA FSO','technical','The organization employs automated mechanisms on an organization-defined frequency to determine the state of information system components with regard to flaw remediation.','SI-2(2).1','The organization being inspected/assessed configures the information system to employ automated mechanisms continuously with HBSS; 30 days for any additional internal network scans not covered by HBSS; annually for external scans by (Computer Network Defense Service Provider) CNDSP to determine the state of information system components with regard to flaw remediation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1233. DoD has defined the frequency as continuously with HBSS; 30 days for any additional internal network scans not covered by HBSS; annually for external scans by (Computer Network Defense Service Provider) CNDSP.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ automated mechanisms continuously with HBSS; 30 days for any additional internal network scans not covered by HBSS; annually for external scans by (Computer Network Defense Service Provider) CNDSP to determine the state of information system components with regard to flaw remediation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1233. DoD has defined the frequency as continuously with HBSS; 30 days for any additional internal network scans not covered by HBSS; annually for external scans by (Computer Network Defense Service Provider) CNDSP.'),
('001234','draft','2009-09-22','DISA FSO','policy','The organization defines a frequency for employing automated mechanisms to determine the state of information system components with regard to flaw remediation.','SI-2(2).2','DoD has defined the frequency as continuously with HBSS; 30 days for any additional internal network scans not covered by HBSS; annually for external scans by (Computer Network Defense Service Provider) CNDSP.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as continuously with HBSS; 30 days for any additional internal network scans not covered by HBSS; annually for external scans by (Computer Network Defense Service Provider) CNDSP.'),
('001235','draft','2009-09-22','DISA FSO','policy','The organization measures the time between flaw identification and flaw remediation.','SI-2(3).1','The organization being inspected/assessed documents and implements a process to measure the time between flaw identification and flaw remediation. The organization must maintain an audit trail of flaw identification and flaw remediation.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of flaw identification and flaw remediation to ensure the organization being inspected/assessed measures the time between flaw identification and flaw remediation.'),
('001236','draft','2009-09-22','DISA FSO','policy','The organization defines benchmarks for the time taken to apply corrective actions after flaw identification.','SI-2(3).2','DoD has defined the benchmarks as within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the benchmarks as within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).'),
('001237','draft','2009-09-22','DISA FSO','technical','The organization employs automated patch management tools to facilitate flaw remediation to organization-defined information system components.',NULL,NULL,NULL),
('001238','draft','2009-09-22','DISA FSO','policy','The organization defines information system components for which automated patch management tools are to be employed to facilitate flaw remediation.',NULL,NULL,NULL),
('001239','draft','2009-09-22','DISA FSO','technical','The organization employs malicious code protection mechanisms at information system entry and exit points to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means or inserted through the exploitation of information system vulnerabilities.',NULL,NULL,NULL),
('001240','draft','2009-09-22','DISA FSO','technical','The organization updates malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures.','SI-3.5','The organization being inspected/assessed configures the information system to update malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1240.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to update malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1240.'),
('001241','draft','2009-09-22','DISA FSO','technical','The organization configures malicious code protection mechanisms to perform periodic scans of the information system on an organization-defined frequency.','SI-3.8','The organization being inspected/assessed configures malicious code protection mechanisms to perform periodic scans of the information system on every 7 days. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1241. DoD has defined the frequency as every 7 days.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures malicious code protection mechanisms to perform periodic scans of the information system on every 7 days. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1241. DoD has defined the frequency as every 7 days.'),
('001242','draft','2009-09-22','DISA FSO','technical','The organization configures malicious code protection mechanisms to perform real-time scans of files from external sources at endpoints as the files are downloaded, opened, or executed in accordance with organizational security policy.','SI-3.9','The organization being inspected/assessed configures malicious code protection mechanisms to perform real-time scans of files from external sources at endpoints as the files are downloaded, opened, or executed in accordance with organizational security policy. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1242.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures malicious code protection mechanisms to perform real-time scans of files from external sources at endpoints as the files are downloaded, opened, or executed in accordance with organizational security policy. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1242.'),
('001243','draft','2009-09-22','DISA FSO','technical','The organization configures malicious code protection mechanisms to perform organization-defined action(s) in response to malicious code detection.','SI-3.10','The organization being inspected/assessed configures malicious code protection mechanisms to perform block and quarantine malicious code and then send an alert to the administrator immediately in near real-time in response to malicious code detection. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1243. DoD has defined the actions as block and quarantine malicious code and then send an alert to the administrator immediately in near real-time.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures malicious code protection mechanisms to perform block and quarantine malicious code and then send an alert to the administrator immediately in near real-time in response to malicious code detection. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1243. DoD has defined the actions as block and quarantine malicious code and then send an alert to the administrator immediately in near real-time.'),
('001244','draft','2009-09-22','DISA FSO','policy','The organization defines one or more actions to perform in response to malicious code detection, such as blocking malicious code, quarantining malicious code, or sending alerts to administrators.','SI-3.11','DoD has defined the actions as block and quarantine malicious code and then send an alert to the administrator immediately in near real-time.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the actions as block and quarantine malicious code and then send an alert to the administrator immediately in near real-time.'),
('001245','draft','2009-09-22','DISA FSO','policy','The organization addresses the receipt of false positives during malicious code detection and eradication, and the resulting potential impact on the availability of the information system.','SI-3.12','The organization being inspected/assessed configures the information system to address the receipt of false positives during malicious code detection and eradication, and the resulting potential impact on the availability of the information system. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1245.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to address the receipt of false positives during malicious code detection and eradication, and the resulting potential impact on the availability of the information system. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1245.'),
('001246','draft','2009-09-22','DISA FSO','policy','The organization centrally manages malicious code protection mechanisms.','SI-3(1).1','The organization being inspected/assessed documents and implements a process to centrally manage malicious code protection mechanisms.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed centrally manages malicious code protection mechanisms.'),
('001247','draft','2009-09-22','DISA FSO','technical','The information system automatically updates malicious code protection mechanisms.','SI-3(2).1','The organization being inspected/assessed configures the information system to automatically update malicious code protection mechanisms. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1247.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically update malicious code protection mechanisms. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1247.'),
('001248','draft','2009-09-22','DISA FSO','technical','The information system prevents non-privileged users from circumventing malicious code protection capabilities.',NULL,NULL,NULL),
('001249','draft','2009-09-22','DISA FSO','technical','The information system updates malicious code protection mechanisms only when directed by a privileged user.','SI-3(4).1','The organization being inspected/assessed configures the information system to update malicious code protection mechanisms only when directed by a privileged user. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1249. This control enhancement may be appropriate for situations where for reasons of security or operational continuity, updates are only applied when selected/approved by designated organizational personnel.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to update malicious code protection mechanisms only when directed by a privileged user. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1249.'),
('001250','draft','2009-09-22','DISA FSO','technical','The organization does not allow users to introduce removable media into the information system.',NULL,NULL,NULL),
('001251','draft','2009-09-22','DISA FSO','policy','The organization tests malicious code protection mechanisms on an organization-defined frequency by introducing a known benign, non-spreading test case into the information system.','SI-3(6).1','The organization being inspected/assessed documents and implement a process to test malicious code protection mechanisms twice annually or when substantial changes are made to the malicious code protection mechanisms by introducing a known benign, non-spreading test case into the information system. DoD has defined the frequency as twice annually or when substantial changes are made to the malicious code protection mechanisms.','The organization conducting the inspection/assessment obtains and examines the documented process and test results to ensure the organization being inspected/assessed tests malicious code protection mechanisms twice annually or when substantial changes are made to the malicious code protection mechanisms by introducing a known benign, non-spreading test case into the information system. DoD has defined the frequency as twice annually or when substantial changes are made to the malicious code protection mechanisms.'),
('001252','draft','2009-09-22','DISA FSO','policy','The organization monitors events on the information system in accordance with organization-defined monitoring objectives and detects information system attacks.',NULL,NULL,NULL),
('001253','draft','2009-09-22','DISA FSO','policy','The organization defines the objectives of monitoring for attacks and indicators of potential attacks on the information system.','SI-4.1','DoD has defined the monitoring objectives as sensor placement and monitoring requirements within CJCSI 6510.01F.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the monitoring objectives as sensor placement and monitoring requirements within CJCSI 6510.01F.'),
('001254','draft','2009-09-22','DISA FSO','policy','The organization identifies unauthorized use of the information system.',NULL,NULL,NULL),
('001255','draft','2009-09-22','DISA FSO','policy','The organization deploys monitoring devices strategically within the information system to collect organization-determined essential information.','SI-4.8','The organization being inspected/assessed documents and implements a process to deploy monitoring devices strategically within the information system to collect organization determined essential information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed deploys monitoring devices strategically within the information system to collect organization determined essential information.'),
('001256','draft','2009-09-22','DISA FSO','policy','The organization deploys monitoring devices at ad hoc locations within the system to track specific types of transactions of interest to the organization.','SI-4.9','The organization being inspected/assessed documents and implements a process to deploy monitoring devices at ad hoc locations within the system to track specific types of transactions of interest to the organization.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed deploys monitoring devices at ad hoc locations within the system to track specific types of transactions of interest to the organization.'),
('001257','draft','2009-09-22','DISA FSO','policy','The organization heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information.','SI-4.13','The organization being inspected/assessed documents and implements a process to heighten the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information.'),
('001258','draft','2009-09-22','DISA FSO','policy','The organization obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations.','SI-4.14','The organization being inspected/assessed obtains and documents legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations.','The organization conducting the inspection/assessment obtains and examines the documented legal opinion to ensure the organization being inspected/assessed obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations.'),
('001259','draft','2009-09-22','DISA FSO','technical','The organization interconnects and configures individual intrusion detection tools into a systemwide intrusion detection system using common protocols.',NULL,NULL,NULL),
('001260','draft','2009-09-22','DISA FSO','policy','The organization employs automated tools to support near real-time analysis of events.','SI-4(2).1','The organization being inspected/assessed documents and implements automated tools to support near real-time analysis of events.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated tools to ensure the organization being inspected/assessed employs automated tools to support near real-time analysis of events. The organization being inspected/assessed may be required to demonstrate use of their automated tools.'),
('001261','draft','2009-09-22','DISA FSO','policy','The organization employs automated tools to integrate intrusion detection tools into access control and flow control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination.',NULL,NULL,NULL),
('001262','draft','2009-09-22','DISA FSO','technical','The information system monitors inbound and outbound communications for unusual or unauthorized activities or conditions.',NULL,NULL,NULL),
('001263','draft','2009-09-22','DISA FSO','technical','The information system provides near real-time alerts when any of the organization-defined list of compromise or potential compromise indicators occurs.',NULL,NULL,NULL),
('001264','draft','2009-09-22','DISA FSO','policy','The organization defines indicators of compromise or potential compromise to the security of the information system which will result in information system alerts being provided to organization-defined personnel or roles.','SI-4(5).1','DoD has defined the compromise indicators as real time intrusion detection and when there are threats identified by authoritative sources (e.g. CTOs) and IAW incident categories I, II, IV, & VII within CJCSM 6510.01B.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the compromise indicators as real time intrusion detection and when there are threats identified by authoritative sources (e.g. CTOs) and IAW incident categories I, II, IV, & VII within CJCSM 6510.01B.'),
('001265','draft','2009-09-22','DISA FSO','technical','The information system prevents non-privileged users from circumventing intrusion detection and prevention capabilities.',NULL,NULL,NULL),
('001266','draft','2009-09-22','DISA FSO','technical','The information system notifies an organization-defined list of incident response personnel (identified by name and/or by role) of detected suspicious events.','SI-4(7).1','The organization being inspected/assessed configures the information system to notify incident response personnel defined in the incident response plan of detected suspicious events. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1266. DoD has defined the incident response personnel as incident response personnel defined in the incident response plan.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify incident response personnel defined in the incident response plan of detected suspicious events. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1266. DoD has defined the incident response personnel as incident response personnel defined in the incident response plan.'),
('001267','draft','2009-09-22','DISA FSO','policy','The organization defines a list of incident response personnel (identified by name and/or by role) to be notified of detected suspicious events.','SI-4(7).2','DoD has defined the incident response personnel as incident response personnel defined in the incident response plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the incident response personnel as incident response personnel defined in the incident response plan.'),
('001268','draft','2009-09-22','DISA FSO','policy','The organization defines a list of least-disruptive actions to be taken by the information system to terminate suspicious events.','SI-4(7).3','The organization being inspected/assessed defines and documents a list of least-disruptive actions to be taken by the information system to terminate suspicious events. DoD has determined the least-disruptive actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list of least-disruptive actions to ensure the organization being inspected/assessed defines a list of least-disruptive actions to be taken by the information system to terminate suspicious events. DoD has determined the least-disruptive actions are not appropriate to define at the Enterprise level.'),
('001269','draft','2009-09-22','DISA FSO','technical','The organization protects information obtained from intrusion monitoring tools from unauthorized access, modification, and deletion.',NULL,NULL,NULL),
('001270','draft','2009-09-22','DISA FSO','policy','The organization tests intrusion monitoring tools at an organization-defined frequency.','SI-4(9).1','The organization being inspected/assessed documents and implements a process to test intrusion monitoring tools every 30 days. The organization must maintain an audit trail of test results. DoD has defined the frequency as every 30 days.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of test results to ensure the organization being inspected/assessed tests intrusion monitoring tools every 30 days. DoD has defined the frequency as every 30 days.'),
('001271','draft','2009-09-22','DISA FSO','policy','The organization defines the frequency for testing intrusion monitoring tools.','SI-4(9).2','DoD has defined the frequency as every 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 30 days.'),
('001272','draft','2009-09-22','DISA FSO','technical','The organization makes provisions so encrypted traffic is visible to information system monitoring tools.',NULL,NULL,NULL),
('001273','draft','2009-09-22','DISA FSO','policy','The organization analyzes outbound communications traffic at the external boundary of the information system to discover anomalies.','SI-4(11).1','The organization being inspected/assessed documents and implements a process to analyze outbound communications traffic at the external boundary of the information system to discover anomalies. The organization must maintain a record of any discovered anomalies.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of any discovered anomalies to ensure the organization being inspected/assessed analyzes outbound communications traffic at the external boundary of the information system to discover anomalies.'),
('001274','draft','2009-09-22','DISA FSO','policy','The organization employs automated mechanisms to alert security personnel of organization-defined inappropriate or unusual activities with security implications.','SI-4(12).1','The organization being inspected/assessed documents and implements automated mechanisms to alert security personnel when there are threats identified by authoritative sources (e.g. CTOs) and IAW with CJCSM 6510.01B. For automated alert mechanisms that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1274. DoD has defined the activities that trigger alerts as when there are threats identified by authoritative sources (e.g. CTOs) and IAW with CJCSM 6510.01B.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms used to alert security personnel when there are threats identified by authoritative sources (e.g. CTOs) and IAW with CJCSM 6510.01B. For automated alert mechanisms that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1274. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms. DoD has defined the activities that trigger alerts as when there are threats identified by authoritative sources (e.g. CTOs) and IAW with CJCSM 6510.01B.'),
('001275','draft','2009-09-22','DISA FSO','policy','The organization defines the activities which will trigger alerts to security personnel of inappropriate or unusual activities.','SI-4(12).2','DoD has defined the activities that trigger alerts as when there are threats identified by authoritative sources (e.g. CTOs) and IAW with CJCSM 6510.01B.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the activities that trigger alerts as when there are threats identified by authoritative sources (e.g. CTOs) and IAW with CJCSM 6510.01B.'),
('001276','draft','2009-09-22','DISA FSO','policy','The organization analyzes communications traffic/event patterns for the information system.','SI-4(13).1','The organization being inspected/assessed documents and implements a process to analyze communications traffic/event patterns for the information system. The organization must maintain a record of the analysis.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of analysis to ensure the organization being inspected/assessed analyzes communications traffic/event patterns for the information system.'),
('001277','draft','2009-09-22','DISA FSO','policy','The organization develops profiles representing common traffic patterns and/or events.','SI-4(13).2','The organization being inspected/assessed develops and documents profiles representing common traffic patterns and/or events.','The organization conducting the inspection/assessment obtains and examines the documented profiles to ensure the organization being inspected/assessed develops profiles representing common traffic patterns and/or events.'),
('001278','draft','2009-09-22','DISA FSO','policy','The organization uses the traffic/event profiles in tuning system monitoring devices to reduce the number of false positives to an organization-defined measure of false positives and the number of false negatives to an organization-defined measure of false negatives.',NULL,NULL,NULL),
('001279','draft','2009-09-22','DISA FSO','policy','The organization defines the respective measurements to which the organization must tune system monitoring devices to reduce the number of false positives.',NULL,NULL,NULL),
('001280','draft','2009-09-22','DISA FSO','policy','The organization defines the respective measurements to which the organization must tune system monitoring devices to reduce the number of false negatives.',NULL,NULL,NULL),
('001281','draft','2009-09-22','DISA FSO','policy','The organization employs a wireless intrusion detection system.',NULL,NULL,NULL),
('001282','draft','2009-09-22','DISA FSO','policy','The organization employs an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.','SI-4(15).1','The organization being inspected/assessed documents and implements an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified intrusion detection system to ensure the organization being inspected/assessed employs an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks. The organization being inspected/assessed may be required to demonstrate use of the intrusion detection system.'),
('001283','draft','2009-09-22','DISA FSO','policy','The organization correlates information from monitoring tools employed throughout the information system.','SI-4(16).1','The organization being inspected/assessed documents and implements a process to correlate information from monitoring tools employed throughout the information system.','The organization conducting the inspection/assessment obtains and examines the documented process and the correlated results to ensure the organization being inspected/assessed correlates information from monitoring tools employed throughout the information system.'),
('001284','draft','2009-09-22','DISA FSO','policy','The organization correlates information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.','SI-4(17).1','The organization being inspected/assessed documents and implements a process to correlate information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.','The organization conducting the inspection/assessment obtains and examines the documented process and the correlated results to ensure the organization being inspected/assessed correlates information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.'),
('001285','draft','2009-09-22','DISA FSO','policy','The organization receives information system security alerts, advisories, and directives from organization-defined external organizations on an ongoing basis.','SI-5.1','The organization being inspected/assessed receives information system security alerts, advisories, and directives from at a minimum, USCYBERCOM on an ongoing basis. DoD has defined the external organizations as at a minimum, USCYBERCOM.','The organization conducting the inspection/assessment obtains and examines alerts, advisories, and directives received by the organization being inspected/assessed to ensure they receive information system security alerts, advisories, and directives from at a minimum, USCYBERCOM on an ongoing basis. DoD has defined the external organizations as at a minimum, USCYBERCOM.'),
('001286','draft','2009-09-22','DISA FSO','policy','The organization generates internal security alerts, advisories, and directives as deemed necessary.','SI-5.3','The organization being inspected/assessed documents and implements a process to generate internal security alerts, advisories, and directives as deemed necessary.','The organization conducting the inspection/assessment obtains and examines documented process as well as the generated internal security alerts, advisories, and directives to ensure the organization being inspected/assessed generates internal security alerts, advisories, and directives as deemed necessary.'),
('001287','draft','2009-09-22','DISA FSO','policy','The organization disseminates security alerts, advisories, and directives to organization-defined personnel or roles, organization-defined elements within the organization, and/or organization-defined external organizations.','SI-5.4','The organization being inspected/assessed disseminates security alerts, advisories, and directives to the ISSO and ISSM and/or external organizations defined in SI-5, CCI 2694. DoD has defined the personnel or roles as the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines any applicable artifacts showing dissemination of security alerts, advisories, and directives to ensure the organization being inspected/assessed disseminates security alerts, advisories, and directives to the ISSO and ISSM and/or external organizations defined in SI-5, CCI 2694. DoD has defined the personnel or roles as the ISSO and ISSM.'),
('001288','draft','2009-09-22','DISA FSO','policy','The organization defines the personnel or roles to whom the organization will disseminate security alerts, advisories, and directives.','SI-5.5','DoD has defined the personnel or roles as the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSO and ISSM.'),
('001289','draft','2009-09-22','DISA FSO','policy','The organization implements security directives in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance.','SI-5.8','The organization being inspected/assessed implements security directives in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance.','The organization conducting the inspection/assessment examines the information system and obtains and examines records of compliance and/or non-compliance reporting to ensure that security directives have been implemented in accordance with established time frames, or notifies the issuing organization of the degree of noncompliance.'),
('001290','draft','2009-09-22','DISA FSO','policy','The organization employs automated mechanisms to make security alert and advisory information available throughout the organization.','SI-5(1).1','The organization being inspected/assessed documents and implements automated mechanisms to make security alert and advisory information available throughout the organization.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure the organization being inspected/assessed employs automated mechanisms to make security alert and advisory information available throughout the organization. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('001291','draft','2009-09-22','DISA FSO','technical','The information system verifies the correct operation of security functions in accordance with organization-defined conditions and in accordance with organization-defined frequency (if periodic verification).',NULL,NULL,NULL),
('001292','draft','2009-09-22','DISA FSO','policy','The organization defines the appropriate conditions, including the system transitional states if applicable, for verifying the correct operation of security functions.',NULL,NULL,NULL),
('001293','draft','2009-09-22','DISA FSO','policy','The organization defines the information system responses and alternative action(s) to anomalies discovered during security function verification.',NULL,NULL,NULL),
('001294','draft','2009-09-22','DISA FSO','technical','The information system notifies organization-defined personnel or roles of failed security verification tests.','SI-6.6','The organization being inspected/assessed configures the information system to notify the ISSO and ISSM of failed security verification tests. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1294. DoD has defined the personnel or roles as the ISSO and ISSM.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the ISSO and ISSM of failed security verification tests. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1294. DoD has defined the personnel or roles as the ISSO and ISSM.'),
('001295','draft','2009-09-22','DISA FSO','technical','The information system implements automated mechanisms to support the management of distributed security testing.','SI-6(2).1','The organization being inspected/assessed configures the information system to implement automated mechanisms to support the management of distributed security testing. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1295.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement automated mechanisms to support the management of distributed security testing. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1295.'),
('001296','draft','2009-09-22','DISA FSO','policy','The organization reports the results of security function verification to organization-defined personnel or roles.','SI-6(3).1','The organization being inspected/assessed documents and implements a process to report the result of security function verification to at a minimum, the ISSO and ISSM. The organization must maintain an audit trail of reporting. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reporting to ensure the organization being inspected/assessed reports the result of security function verification to at a minimum, the ISSO and ISSM. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('001297','draft','2009-09-22','DISA FSO','technical','The information system detects unauthorized changes to software and information.',NULL,NULL,NULL),
('001298','draft','2009-09-22','DISA FSO','policy','The organization reassesses the integrity of software and information by performing, on an organization-defined frequency, integrity scans of the information system.',NULL,NULL,NULL),
('001299','draft','2009-09-22','DISA FSO','policy','The organization defines the frequency of integrity scans to be performed on the information system.',NULL,NULL,NULL),
('001300','draft','2009-09-22','DISA FSO','policy','The organization employs automated tools that provide notification to organization-defined personnel or roles upon discovering discrepancies during integrity verification.','SI-7(2).1','The organization being inspected/assessed documents and implements automated tools that provide notification to at a minimum, the ISSO and ISSM upon discovering discrepancies during integrity verification. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated tools to ensure the organization being inspected/assessed employs automated tools that provide notification to at a minimum, the ISSO and ISSM upon discovering discrepancies during integrity verification. The organization being inspected/assessed may be required to demonstrate use of their identified automated tools. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('001301','draft','2009-09-22','DISA FSO','policy','The organization employs centrally managed integrity verification tools.','SI-7(3).1','The organization being inspected/assessed documents and implements centrally managed integrity verification tools.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified centrally managed integrity verification tools to ensure the organization being inspected/assessed employs centrally managed integrity verification tools. The organization being inspected/assessed may be required to demonstrate use of their identified integrity verification tools.'),
('001302','draft','2009-09-22','DISA FSO','policy','The organization requires use of tamper-evident packaging for organization-defined information system components during organization-defined conditions.',NULL,NULL,NULL),
('001303','draft','2009-09-22','DISA FSO','policy','The organization defines information system components that require tamper-evident packaging.',NULL,NULL,NULL),
('001304','draft','2009-09-22','DISA FSO','policy','The organization defines conditions (i.e., transportation from vendor to operational site, during operation, both) under which tamper-evident packaging must be used for organization-defined information system components.',NULL,NULL,NULL),
('001305','draft','2009-09-22','DISA FSO','technical','The organization employs spam protection mechanisms at information system entry and exit points to detect and take action on unsolicited messages transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means.',NULL,NULL,NULL),
('001306','draft','2009-09-22','DISA FSO','policy','The organization updates spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.','SI-8.3','The organization being inspected/assessed documents and implements a process to update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.','The organization conducting the inspection/assessment obtains and examines the documented process and examines the spam protection mechanisms to ensure the organization being inspected/assessed updates spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.'),
('001307','draft','2009-09-22','DISA FSO','policy','The organization centrally manages spam protection mechanisms.','SI-8(1).1','The organization being inspected/assessed documents and implements a process to centrally manage spam protection mechanisms.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed centrally manages spam protection mechanisms.'),
('001308','draft','2009-09-22','DISA FSO','technical','The information system automatically updates spam protection mechanisms.','SI-8(2).1','The organization being inspected/assessed configures the information system to automatically update spam protection mechanisms. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1308.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically update spam protection mechanisms. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1308.'),
('001309','draft','2009-09-22','DISA FSO','policy','The organization restricts the capability to input information to the information system to authorized personnel.',NULL,NULL,NULL),
('001310','draft','2009-09-22','DISA FSO','technical','The information system checks the validity of organization-defined inputs.','SI-10.1','The organization being inspected/assessed configures the information system to check the validity of all inputs except those identified specifically by the organization. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1310. DoD has defined the information inputs as all inputs except those identified specifically by the organization.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to check the validity of all inputs except those identified specifically by the organization. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1310. DoD has defined the information inputs as all inputs except those identified specifically by the organization.'),
('001311','draft','2009-09-22','DISA FSO','technical','The information system identifies potentially security-relevant error conditions.',NULL,NULL,NULL),
('001312','draft','2009-09-22','DISA FSO','technical','The information system generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.','SI-11.1','The organization being inspected/assessed configures the information system to generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1312.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1312.'),
('001313','draft','2009-09-22','DISA FSO','policy','The organization defines sensitive or potentially harmful information that should not be contained in error logs and administrative messages.',NULL,NULL,NULL),
('001314','draft','2009-09-22','DISA FSO','technical','The information system reveals error messages only to organization-defined personnel or roles.','SI-11.2','The organization being inspected/assessed configures the information system to reveal error messages only to the ISSO, ISSM, and SCA. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1314. DoD has defined the personnel or roles as the ISSO, ISSM, and SCA.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to reveal error messages only to the ISSO, ISSM, and SCA. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1314. DoD has defined the personnel or roles as the ISSO, ISSM, and SCA.'),
('001315','draft','2009-09-22','DISA FSO','policy','The organization handles information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','SI-12.1','The organization being inspected/assessed identifies and documents federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements which apply to the information within the information system. The organization documents and implements a process to handle information IAW those documented federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','The organization conducting the inspection/assessment obtains and examines the documented list of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements which apply to the information within the information system, as well as the documented process for information handling to ensure the organization being inspected/assessed handles information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.'),
('001316','draft','2009-09-22','DISA FSO','policy','The organization protects the information system from harm by considering mean time to failure rates for an organization-defined list of information system components in specific environments of operation.',NULL,NULL,NULL),
('001317','draft','2009-09-22','DISA FSO','policy','The organization defines a list of information system components for which mean time to failure rates should be considered to protect the information system from harm.',NULL,NULL,NULL),
('001318','draft','2009-09-22','DISA FSO','policy','The organization provides substitute information system components.','SI-13.3','The organization being inspected/assessed documents and implements a process to provide substitute information system components.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides substitute information system components.'),
('001319','draft','2009-09-22','DISA FSO','policy','The organization takes information system components out of service by transferring component responsibilities to a substitute component no later than an organization-defined fraction or percentage of mean time to failure (MTTF).','SI-13(1).1','The organization being inspected/assessed documents and implements a process to take the information system components out of service by transferring component responsibilities to a substitute component no later than a fraction or percentage of mean time to failure defined in SI-13 (1), CCI 1320. The organization must maintain a log of component substitution.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the log of component substitution to ensure the organization being inspected/assessed takes the information system components out of service by transferring component responsibilities to a substitute component no later than a fraction or percentage of mean time to failure defined in SI-13 (1), CCI 1320.'),
('001320','draft','2009-09-22','DISA FSO','policy','The organization defines the maximum fraction or percentage of mean time to failure (MTTF) used to determine when information system components are taken out of service by transferring component responsibilities to substitute components.','SI-13(1).2','The organization being inspected/assessed defines and documents the maximum fraction or percentage of mean time to failure used to determine when information system components are taken out of service by transferring component responsibilities to substitute components. DoD has determined the fraction or percentage is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented fraction or percentage to ensure the organization being inspected/assessed defines the maximum fraction or percentage of mean time to failure used to determine when information system components are taken out of service by transferring component responsibilities to substitute components. DoD has determined the fraction or percentage is not appropriate to define at the Enterprise level.'),
('001321','draft','2009-09-22','DISA FSO','policy','The organization does not allow a process to execute without supervision for more than an organization-defined time period.','SI-7(16).1','The organization being inspected/assessed does not allow a process to execute without supervision for more than the time period defined in SI-7 (16), CCI 1322.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of process supervision to ensure the organization being inspected/assessed does not allow a process to execute without supervision for more than the time period defined in SI-7 (16), CCI 1322.'),
('001322','draft','2009-09-22','DISA FSO','policy','The organization defines a time period that is the longest a process is allowed to execute without supervision.','SI-7(16).2','The organization being inspected/assessed defines and documents a time period that is the most a process is allowed to execute without supervision. DoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure the organization being inspected/assessed defines a time period that is the most a process is allowed to execute without supervision. DoD has determined the time period is not appropriate to define at the Enterprise level.'),
('001323','draft','2009-09-22','DISA FSO','policy','The organization manually initiates a transfer between active and standby information system components in accordance with organization-defined frequency if the mean time to failure (MTTF) exceeds an organization-defined time period.',NULL,NULL,NULL),
('001324','draft','2009-09-22','DISA FSO','policy','The organization defines the minimum frequency at which the organization manually initiates a transfer between active and standby information system components if the mean time to failure (MTTF) exceeds the organization-defined time period.','SI-13(3).1','The organization being inspected/assessed defines and documents the minimum frequency at which the organization manually initiates a transfer between active and standby information system components if the mean time to failure exceeds the organization-defined time period. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the minimum frequency at which the organization manually initiates a transfer between active and standby information system components if the mean time to failure exceeds the organization-defined time period. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('001325','draft','2009-09-22','DISA FSO','policy','The organization defines a time period that the mean time to failure (MTTF) must exceed before the organization manually initiates a transfer between active and standby information system components.','SI-13(3).2','The organization being inspected/assessed defines and documents a time period that the mean time to failure must exceed before the organization manually initiates a transfer between active and standby information system components. The time period should be based on organizational need to maintain readiness of standby components. DoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure the organization being inspected/assessed defines a time period that the mean time to failure must exceed before the organization manually initiates a transfer between active and standby information system components. DoD has determined the time period is not appropriate to define at the Enterprise level.'),
('001326','draft','2009-09-22','DISA FSO','policy','The organization, if information system component failures are detected, ensures standby components are successfully and transparently installed within an organization-defined time period.','SI-13(4).1','The organization being inspected/assessed documents and implements a process to transparently install standby components within a time period defined in SI-13 (4), CCI 1327 if information system component failures are detected. The organization must maintain a log of standby component installation to include time periods.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the log of standby component installation to ensure the organization being inspected/assessed transparently installs standby components within a time period defined in SI-13 (4), CCI 1327 if information system component failures are detected.'),
('001327','draft','2009-09-22','DISA FSO','policy','The organization defines a time period for a standby information system component to be successfully and transparently installed for the information system component that has failed.','SI-13(4).2','The organization being inspected/assessed defines and documents a time period for a standby information system component to be successfully and transparently installed for the information system component that has failed\n\nDoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure the organization being inspected/assessed defines a time period for a standby information system component to be successfully and transparently installed for the information system component that has failed. DoD has determined the time period is not appropriate to define at the Enterprise level.'),
('001328','draft','2009-09-22','DISA FSO','technical','The organization, if an information system component failure is detected, activates an organization-defined alarm and/or automatically shuts down the information system.','SI-13(4).3','The organization being inspected/assessed configures the information system to activate an alarm defined in SI-13( 4), CCI 1329 and/or automatically shuts down the information system if an information system component failure is detected. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1328.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to activate an alarm defined in SI-13( 4), CCI 1329 and/or automatically shuts down the information system if an information system component failure is detected. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1328.'),
('001329','draft','2009-09-22','DISA FSO','policy','The organization defines the alarm to be activated when an information system component failure is detected.','SI-13(4).4','The organization being inspected/assessed defines and documents the alarm to be activated when an information system component failure is detected. DoD has determined the alarm is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented alarm to ensure the organization being inspected/assessed defines the alarm to be activated when an information system component failure is detected. DoD has determined the alarm is not appropriate to define at the Enterprise level.'),
('001330','draft','2009-09-22','DISA FSO','policy','The organization prohibits the use of unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official.','AC-19(4).1','The organization being inspected/assessed documents and implements a process to prohibit the use of unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed prohibits the use of unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official.'),
('001331','draft','2009-09-22','DISA FSO','policy','The organization prohibits connection of unclassified mobile devices to classified information systems.','AC-19(4).2','The organization being inspected/assessed documents and implements a process to prohibit connection of unclassified mobile devices to classified information systems.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed prohibits connection of unclassified mobile devices to classified information systems.'),
('001332','draft','2009-09-22','DISA FSO','policy','The organization requires approval from the authorizing official for the connection of unclassified mobile devices to unclassified information systems.','AC-19(4).3','The organization being inspected/assessed documents and implements a process to require approval from the authorizing official for the connection of unclassified mobile devices to unclassified information systems. The organization must maintain an audit trail of approvals.','The organization conducting the inspection/assessment obtains and examines the documented process and the audit trail of approvals to ensure the organization being inspected/assessed requires approval from the authorizing official for the connection of unclassified mobile devices to unclassified information systems.'),
('001333','draft','2009-09-22','DISA FSO','policy','The organization prohibits use of internal or external modems or wireless interfaces within unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information.','AC-19(4).4','The organization being inspected/assessed documents and implements a process to prohibit use of internal or external modems or wireless interfaces within unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed prohibits use of internal or external modems or wireless interfaces within unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information.'),
('001334','draft','2009-09-22','DISA FSO','policy','The organization requires that unclassified mobile devices used in facilities containing information systems processing, storing, or transmitting classified information and the information stored on those devices be subject to random reviews and inspections by organization-defined security officials.','AC-19(4).5','The organization being inspected/assessed documents and implements a process to require that unclassified mobile devices used in facilities containing information systems processing, storing, or transmitting classified information and the information stored on those devices are subject to random reviews and inspections by the ISSM/ISSO. DoD has defined the security officials as the ISSM/ISSO.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires that unclassified mobile devices used in facilities containing information systems processing, storing, or transmitting classified information and the information stored on those devices are subject to random reviews and inspections by the ISSM/ISSO. DoD has defined the security officials as the ISSM/ISSO.'),
('001335','draft','2009-09-22','DISA FSO','policy','The organization defines security officials to perform reviews and inspections of unclassified mobile devices in facilities containing information systems processing, storing, or transmitting classified information.','AC-19(4).6','DoD has defined the security officials as the ISSM/ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security officials as the ISSM/ISSO.'),
('001336','draft','2009-09-22','DISA FSO','policy','The organization retains individual training records for an organization-defined time period.','AT-4.3','The organization being inspected/assessed will maintain records training records for at least 5 years or 5 years after completion of a specific training program. DoD has defined the frequency as at least 5 years or 5 years after completion of a specific training program.','The organization conducting the inspection/assessment obtains and examines training records to ensure records have been maintained for at least 5 years or 5 years after completion of a specific training program. DoD has defined the frequency as at least 5 years or 5 years after completion of a specific training program.'),
('001337','draft','2009-09-22','DISA FSO','policy','The organization defines a time period for retaining individual training records.','AT-4.4','DoD has defined the frequency as at least 5 years or 5 years after completion of a specific training program.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least 5 years or 5 years after completion of a specific training program.'),
('001338','draft','2009-09-22','DISA FSO','technical','The information system associates the identity of the information producer with the information.',NULL,NULL,NULL),
('001339','draft','2009-09-22','DISA FSO','technical','The information system validates the binding of the information producer\'s identity to the information.',NULL,NULL,NULL),
('001340','draft','2009-09-22','DISA FSO','technical','The information system maintains reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released.','AU-10(3).1','The organization being inspected/assessed configures the information system to maintain reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1340.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1340.'),
('001341','draft','2009-09-22','DISA FSO','technical','The information system validates the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer between organization-defined security domains.','AU-10(4).1','The organization being inspected/assessed configures the information system to validate the binding of the information reviewers identity at the transfer or release points between security domains defined in AU-10 (4), CCI 1907.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to validate the binding of the information reviewers identity at the transfer or release points between security domains defined in AU-10 (4), CCI 1907.'),
('001342','deprecated','2009-09-22','DISA FSO','technical','The organization employs either FIPS-validated or NSA-approved cryptography to implement digital signatures.',NULL,NULL,NULL),
('001343','draft','2009-09-22','DISA FSO','technical','The information system invokes a system shutdown in the event of an audit failure, unless an alternative audit capability exists.',NULL,NULL,NULL),
('001344','draft','2009-09-22','DISA FSO','policy','The organization specifies the permitted actions for each authorized information system process, role, and/or user in the audit and accountability policy.',NULL,NULL,NULL),
('001345','deprecated','2009-09-22','DISA FSO','technical','The organization employs automated mechanisms to alert security personnel of any organization-defined inappropriate or unusual activities with security implications.',NULL,NULL,NULL),
('001346','draft','2009-09-22','DISA FSO','policy','The organization defines a list of inappropriate or unusual activities with security implications that are to result in alerts to security personnel.',NULL,NULL,NULL),
('001347','draft','2009-09-22','DISA FSO','policy','The organization performs, in a physically dedicated information system, full-text analysis of privileged functions executed.',NULL,NULL,NULL),
('001348','draft','2009-09-22','DISA FSO','technical','The information system backs up audit records on an organization-defined frequency onto a different system or system component than the system or component being audited.','AU-9(2).1','The organization being inspected/assessed configures the information system to back up audit records at least every seven days. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1348. DoD has defined the frequency as every seven days.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to back up audit records at least every seven days. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1348. DoD has defined the frequency as every seven days.'),
('001349','draft','2009-09-22','DISA FSO','policy','The organization defines a frequency for backing up system audit records onto a different system or system component than the system or component being audited.','AU-9(2).2','DoD has defined the frequency as every seven days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every seven days.'),
('001350','draft','2009-09-22','DISA FSO','technical','The information system implements cryptographic mechanisms to protect the integrity of audit information.','AU-9(3).1','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the integrity of audit information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1350.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to implement cryptographic mechanisms to protect the integrity of audit information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1350.'),
('001351','draft','2009-09-22','DISA FSO','policy','The organization authorizes access to management of audit functionality to only an organization-defined subset of privileged users.','AU-9(4).2','The organization being inspected/assessed authorizes access to the management of audit functionality to only the subset of privileged users defined in AU-9 (4), CCI 1894.','The organization conducting the inspection/assessment obtains and examines the documentation of access authorizations for the management of audit functionality to ensure only the subset of privileged users defined in AU-9 (4), CCI 1894 have been granted access authorization.'),
('001352','draft','2009-09-22','DISA FSO','technical','The organization protects the audit records of non-local accesses to privileged accounts and the execution of privileged functions.',NULL,NULL,NULL),
('001353','draft','2009-09-22','DISA FSO','technical','The information system produces a system-wide (logical or physical) audit trail composed of audit records in a standardized format.','AU-12(2).1','The organization being inspected/assessed configures the information system to produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1353.','The organization conducting the inspection/assessment examines the information system to ensure the information system is configured to produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1353.'),
('001354','draft','2009-09-22','DISA FSO','policy','The organization manages information system accounts by deactivating temporary accounts that are no longer required.',NULL,NULL,NULL),
('001355','draft','2009-09-22','DISA FSO','policy','The organization manages information system accounts by deactivating accounts of terminated or transferred users.',NULL,NULL,NULL),
('001356','draft','2009-09-22','DISA FSO','technical','The organization monitors for atypical usage of information system accounts.',NULL,NULL,NULL),
('001357','draft','2009-09-22','DISA FSO','policy','The organization reports atypical usage to designated organizational officials.',NULL,NULL,NULL),
('001358','draft','2009-09-22','DISA FSO','policy','The organization establishes privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.','AC-2(7).1','The organization being inspected/assessed documents and implements a process to establish privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.','The organization conducting the inspection/assessment obtains and examines documented processes for privileged user account creation to ensure the organization being inspected/assessed establishes privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.'),
('001359','draft','2009-09-22','DISA FSO','policy','The organization tracks privileged role assignments.',NULL,NULL,NULL),
('001360','draft','2009-09-22','DISA FSO','policy','The organization monitors privileged role assignments.','AC-2(7).3','The organization being inspected/assessed implements a process to monitor privileged role assignments. The organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the audit trail of monitoring to ensure the organization being inspected/assessed monitors privileged role assignments.'),
('001361','draft','2009-09-24','DISA FSO','policy','The organization defines a time period after which temporary accounts are automatically terminated.','AC-2(2).2','DoD has defined the time period as 72 hours. The time period of 72 hours applies to temporary user accounts.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 72 hours. The time period of 72 hours applies to temporary user accounts.'),
('001362','draft','2009-09-22','DISA FSO','technical','The information system enforces a Discretionary Access Control (DAC) policy that allows users to specify and control sharing by named individuals or groups of individuals, or by both.',NULL,NULL,NULL),
('001363','draft','2009-09-22','DISA FSO','policy','The organization establishes a Discretionary Access Control (DAC) policy that allows users to specify and control sharing by named individuals or groups of individuals, or by both.',NULL,NULL,NULL),
('001365','draft','2009-09-24','DISA FSO','policy','The organization defines a time period after which emergency accounts are automatically terminated.','AC-2(2).3','DoD has defined the time period as never. The time period of never applies to emergency admin accounts.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as never. The time period of never applies to emergency admin accounts.'),
('001366','draft','2009-09-22','DISA FSO','policy','The organization defines user information to be encrypted or stored off-line in a secure location.',NULL,NULL,NULL),
('001367','draft','2009-09-22','DISA FSO','policy','The organization defines system information to be encrypted or stored off-line in a secure location.',NULL,NULL,NULL),
('001368','draft','2009-09-22','DISA FSO','technical','The information system enforces approved authorizations for controlling the flow of information within the system based on organization-defined information flow control policies.','AC-4.1','The organization being inspected/assessed configures the information system to enforce approved authorizations for controlling the flow of information within the system based on information flow control policies defined in AC-4, CCI 1548. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1368.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce approved authorizations for controlling the flow of information within the system based on information flow control policies defined in AC-4, CCI 1548. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1368.'),
('001371','draft','2009-09-22','DISA FSO','policy','The organization defines information security policy filters requiring fully enumerated formats which are to be implemented when transferring information between different security domains.','AC-4(14).1','The organization being inspected/assessed defines and documents information security policy filters requiring fully enumerated formats which are to be implemented when transferring information between different security domains. DoD has determined the information security policy filters are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information security policy filters to ensure the organization being inspected/assessed defines. information security policy filters requiring fully enumerated formats which are to be implemented when transferring information between different security domains. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('001372','draft','2009-09-22','DISA FSO','technical','The information system, when transferring information between different security domains, implements organization-defined security policy filters requiring fully enumerated formats that restrict data structure and content.','AC-4(14).2','The organization being inspected/assessed configures the information system to implement security policy filters defined in AC-4 (14), CCI 1371 requiring fully enumerated formats that restrict data structure and content. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1372.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement security policy filters defined in AC-4 (14), CCI 1371 requiring fully enumerated formats that restrict data structure and content. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1372.'),
('001373','draft','2009-09-22','DISA FSO','technical','The information system, when transferring information between different security domains, examines the information for the presence of organization-defined unsanctioned information.','AC-4(15).1','The organization being inspected/assessed configures the information system to examine the information for the presence of unsanctioned information defined in AC-4 (15), CCI 2203 when transferring information between different security domains. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1373.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to examine the information for the presence of unsanctioned information defined in AC-4 (15), CCI 2203 when transferring information between different security domains. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1373.'),
('001374','draft','2009-09-22','DISA FSO','technical','The information system, when transferring information between different security domains, prohibits the transfer of organization-defined unsanctioned information in accordance with the organization-defined security policy.','AC-4(15).2','The organization being inspected/assessed configures the information system to prohibit the transfer of unsanctioned information defined in AC-4 (15), CCI 2203 in accordance with the security policy defined in AC-4 (15), CCI 2204. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1374.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prohibit the transfer of unsanctioned information defined in AC-4 (15), CCI 2203 in accordance with the security policy defined in AC-4 (15), CCI 2204. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1374.'),
('001376','draft','2009-09-22','DISA FSO','technical','The information system uniquely identifies source domains for information transfer.',NULL,NULL,NULL),
('001377','draft','2009-09-22','DISA FSO','technical','The information system uniquely authenticates source domains for information transfer.',NULL,NULL,NULL),
('001380','draft','2009-09-22','DISA FSO','policy','The organization documents separation of duties of individuals.','AC-5.3','The organization being inspected/assessed documents separation of duties of individuals.','The organization conducting the inspection/assessment obtains and examines the documented separation of duties to ensure the organization being inspected/assessed documents separation of duties of individuals.'),
('001382','draft','2009-09-22','DISA FSO','policy','The organization defines the number of consecutive, unsuccessful login attempts to the mobile device.',NULL,NULL,NULL),
('001383','draft','2009-09-22','DISA FSO','technical','The information system provides additional protection for mobile devices accessed via login by purging information from the device after an organization-defined number of consecutive, unsuccessful login attempts to the mobile device.',NULL,NULL,NULL),
('001384','draft','2009-09-22','DISA FSO','technical','The information system, for publicly accessible systems, displays system use information organization-defined conditions before granting further access.','AC-8.8','The organization being inspected/assessed configures the information system to display the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems - Standard Consent Banner and User Agreement,\" March 2013 before granting further access for publicly accessible systems For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1384. DoD has defined the conditions as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems - Standard Consent Banner and User Agreement,\" March 2013.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems - Standard Consent Banner and User Agreement,\" March 2013 before granting further access for publicly accessible systems For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1384. DoD has defined the conditions as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems - Standard Consent Banner and User Agreement,\" March 2013.'),
('001385','draft','2009-09-22','DISA FSO','technical','The information system, for publicly accessible systems, displays references, if any, to monitoring that are consistent with privacy accommodations for such systems that generally prohibit those activities.','AC-8.10','The organization being inspected/assessed configures the information system to display references, if any, to monitoring that are consistent with privacy accommodations for such systems that generally prohibit those activities for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1385.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display references, if any, to monitoring that are consistent with privacy accommodations for such systems that generally prohibit those activities for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1385.'),
('001386','draft','2009-09-22','DISA FSO','technical','The information system, for publicly accessible systems, displays references, if any, to recording that are consistent with privacy accommodations for such systems that generally prohibit those activities.','AC-8.11','The organization being inspected/assessed configures the information system to display references, if any, to recording that are consistent with privacy accommodations for such systems that generally prohibit those activities for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1386.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display references, if any, to recording that are consistent with privacy accommodations for such systems that generally prohibit those activities for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1386.'),
('001387','draft','2009-09-22','DISA FSO','technical','The information system, for publicly accessible systems, displays references, if any, to auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities.','AC-8.12','The organization being inspected/assessed configures the information system to display references, if any, to auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1387.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display references, if any, to auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1387.'),
('001388','draft','2009-09-22','DISA FSO','technical','The information system, for publicly accessible systems, includes a description of the authorized uses of the system.','AC-8.13','The organization being inspected/assessed configures the information system to include a description of the authorized uses of the system for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1388.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to include a description of the authorized uses of the system for publicly accessible systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1388.'),
('001389','draft','2009-09-22','DISA FSO','policy','The organization defines the time period that the information system notifies the user of the number of successful logon/access attempts.','AC-9(2).1','DoD has determined this CCI is not applicable because this option is not selected.','DoD has determined this CCI is not applicable because this option is not selected.'),
('001390','draft','2009-09-22','DISA FSO','policy','The organization defines the time period that the information system notifies the user of the number of unsuccessful logon/access attempts.','AC-9(2).2','DoD has defined the time period as the time since the last successful login (for unsuccessful logon/access attempts). ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as the time since the last successful login (for unsuccessful logon/access attempts). '),
('001391','draft','2009-09-22','DISA FSO','technical','The information system notifies the user of the number of successful logins/accesses that occur during the organization-defined time period.','AC-9(2).3','DoD has determined this CCI is not applicable because this option is not selected.','DoD has determined this CCI is not applicable because this option is not selected.'),
('001392','draft','2009-09-22','DISA FSO','technical','The information system notifies the user of the number of unsuccessful login/access attempts that occur during organization-defined time period.','AC-9(2).4','The organization being inspected/assessed configures the information system to notify the user of the number of unsuccessful login/access attempts that occur during the time period defined in AC-9 (2), CCI 1389. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1392.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the user of the number of unsuccessful login/access attempts that occur during the time period defined in AC-9 (2), CCI 1389. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1392.'),
('001393','draft','2009-09-22','DISA FSO','policy','The organization defines the security-related characteristics/parameters of the user^s account which, when changed, will result in a notification being provided to the user during the organization-defined time period.','AC-9(3).1','DoD has defined the security-related characteristics/parameters as access and/or privilege parameters.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security-related characteristics/parameters as access and/or privilege parameters.'),
('001394','draft','2009-09-22','DISA FSO','policy','The organization defines the time period during which organization-defined security-related changes to the user^s account are to be tracked.','AC-9(3).2','DoD has defined the time period as since last successful login.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as since last successful login.'),
('001395','draft','2009-09-22','DISA FSO','technical','The information system notifies the user of changes to organization-defined security-related characteristics/parameters of the user^s account that occur during the organization-defined time period.','AC-9(3).3','The organization being inspected/assessed configures the information system to notify the user of changes to access and/or privilege parameters that occur since last successful login. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1395. DoD has defined the time period as since last successful login. DoD has defined the security-related characteristics/parameters as access and/or privilege parameters.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the user of changes to access and/or privilege parameters that occur since last successful login. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1395. DoD has defined the time period as since last successful login. DoD has defined the security-related characteristics/parameters as access and/or privilege parameters.'),
('001396','draft','2009-09-22','DISA FSO','policy','The organization defines security attributes for which the information system supports and maintains the bindings for information in storage.',NULL,NULL,NULL),
('001397','draft','2009-09-22','DISA FSO','policy','The organization defines security attributes for which the information system supports and maintains the bindings for information in process.',NULL,NULL,NULL),
('001398','draft','2009-09-22','DISA FSO','policy','The organization defines security attributes for which the information system supports and maintains the bindings for information in transmission.',NULL,NULL,NULL),
('001399','draft','2009-09-22','DISA FSO','technical','The information system supports and maintains the binding of organization-defined security attributes to information in storage.',NULL,NULL,NULL),
('001400','draft','2009-09-22','DISA FSO','technical','The information system supports and maintains the binding of organization-defined security attributes to information in process.',NULL,NULL,NULL),
('001401','draft','2009-09-22','DISA FSO','technical','The information system supports and maintains the binding of organization-defined security attributes to information in transmission.',NULL,NULL,NULL),
('001402','draft','2009-09-22','DISA FSO','policy','The organization monitors for unauthorized remote access to the information system.',NULL,NULL,NULL),
('001403','draft','2009-09-24','DISA FSO','technical','The information system automatically audits account modification actions.','AC-2(4).2','The organization being inspected/assessed configures the information system to automatically audit account modification actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1403.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically audit account modification actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1403.'),
('001404','draft','2009-09-24','DISA FSO','technical','The information system automatically audits account disabling actions.','AC-2(4).3','The organization being inspected/assessed configures the information system to automatically audit account disabling actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1404.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically audit account disabling actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1404.'),
('001405','draft','2009-09-24','DISA FSO','technical','The information system automatically audits account removal actions.','AC-2(4).4','The organization being inspected/assessed configures the information system to automatically audit account removal actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1405.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically audit account removal actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1405.'),
('001406','draft','2009-09-24','DISA FSO','policy','The organization defines a time period of expected inactivity when users are required to log out.','AC-2(5).3','DoD has defined the time period as at the end of the users standard work period unless otherwise defined in formal organizational policy.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as at the end of the users standard work period unless otherwise defined in formal organizational policy.'),
('001407','draft','2009-09-24','DISA FSO','policy','The organization administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.','AC-2(7).2','The organization being inspected/assessed documents and implements a process to administer privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.','The organization conducting the inspection/assessment obtains and examines documented processes for privileged user account creation to ensure the organization being inspected/assessed administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.'),
('001408','draft','2009-09-24','DISA FSO','policy','The organization defines privileged commands for which dual authorization is to be enforced.','AC-3(2).2','The organization being inspected/assessed defines and documents privileged commands for which dual authorization is to be enforced. DoD has determined the other actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented privileged commands to ensure they have been defined. DoD has determined the other actions are not appropriate to define at the Enterprise level.'),
('001409','draft','2009-09-24','DISA FSO','policy','The organization defines nondiscretionary access control policies to be enforced over the organization-defined set of users and resources, where the rule set for each policy specifies access control information employed by the policy rule set (e.g., position, nationality, age, project, time of day) and required relationships among the access control information to permit access.',NULL,NULL,NULL),
('001410','draft','2009-09-24','DISA FSO','policy','The organization defines the set of users and resources over which the information system is to enforce nondiscretionary access control policies.',NULL,NULL,NULL),
('001411','draft','2009-09-24','DISA FSO','policy','The organization defines security-relevant information to which the information system prevents access except during secure, non-operable system states.','AC-3(5).2','The organization being inspected/assessed defines and documents security-relevant information to which the information system prevents access except during secure, nonoperable system states. At a minimum, the security-relevant information shall include installing and updating crypto keys. DoD has determined the security-relevant information is not appropriate to define at the Enterprise level, but at a minimum, installing and updating crypto keys.','The organization conducting the inspection/assessment obtains and examines the documented security-relevant information to ensure it has been defined and at a minimum, includes installing and updating crypto keys. DoD has determined the security-relevant information is not appropriate to define at the Enterprise level, but at a minimum, installing and updating crypto keys.'),
('001412','draft','2009-09-24','DISA FSO','policy','The organization encrypts or stores off-line, in a secure location, organization-defined user information.',NULL,NULL,NULL),
('001413','draft','2009-09-24','DISA FSO','policy','The organization encrypts or stores off-line, in a secure location, organization-defined system information.',NULL,NULL,NULL),
('001414','draft','2009-09-24','DISA FSO','technical','The information system enforces approved authorizations for controlling the flow of information between interconnected systems based on organization-defined information flow control policies.','AC-4.2','The organization being inspected/assessed configures the information system to enforce approved authorizations for controlling the flow of information between interconnected systems based on information flow control policies defined in AC-4, CCI 1549. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1414.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce approved authorizations for controlling the flow of information between interconnected systems based on information flow control policies defined in AC-4, CCI 1549. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1414.'),
('001415','draft','2009-09-24','DISA FSO','policy','The organization defines limitations for the embedding of data types within other data types.','AC-4(5).2','The organization being inspected/assessed defines and documents the limitations of the embedding of data types within other data types. DoD has determined the limitations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented limitations to ensure the organization being inspected/assessed defines the limitations of the embedding of data types within other data types. DoD has determined the limitations are not appropriate to define at the Enterprise level.'),
('001416','draft','2009-09-24','DISA FSO','policy','The organization defines one-way information flows to be enforced by the information system.','AC-4(7).2','The organization being inspected/assessed defines and documents one-way information flows to be enforced by the information system. DoD has determined the one-way information flow is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented one-way information flows to ensure the organization being inspected/assessed defines one-way information flows to be enforced by the information system. DoD has determined the one-way information flow is not appropriate to define at the Enterprise level.'),
('001417','draft','2009-09-24','DISA FSO','policy','The organization defines security policy filters to be enforced by the information system and used as a basis for flow control decisions.','AC-4(8).2','The organization being inspected/assessed defines and documents security policy filters to be enforced by the information system and used as a basis for flow control decisions. DoD has determined the security policy filters are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policy filters to ensure the organization being inspected/assessed defines security policy filters to be enforced by the information system and used as a basis for flow control decisions. DoD has determined the security policy filters are not appropriate to define at the Enterprise level.'),
('001418','draft','2009-09-24','DISA FSO','policy','The organization defines security policy filters for which the information system enforces the use of human review.',NULL,NULL,NULL),
('001419','draft','2009-09-25','DISA FSO','policy','The organization defines the security functions or security-relevant information to which users of information system accounts, or roles, have access.','AC-6(2).2','DoD has defined the security functions and security-relevant information as any privileged security functions or security-relevant information.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security functions and security-relevant information as any privileged security functions or security-relevant information.'),
('001420','draft','2009-09-25','DISA FSO','policy','The organization defines the privileged commands to which network access is to be authorized only for organization-defined compelling operational needs.','AC-6(3).3','The organization being inspected/assessed defines and documents the privileged commands to which network access is to be authorized only for organization-defined compelling operational needs. DoD has determined the privileged commands are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented privileged commands to ensure the organization being inspected/assessed defines the privileged commands to which network access is to be authorized only for organization-defined compelling operational needs. DoD has determined the privileged commands are not appropriate to define at the Enterprise level.'),
('001421','draft','2009-09-25','DISA FSO','policy','The organization limits authorization to super user accounts on the information system to designated system administration personnel.',NULL,NULL,NULL),
('001422','draft','2009-09-25','DISA FSO','policy','The organization prohibits privileged access to the information system by non-organizational users.','AC-6(6).1','The organization being inspected/assessed implements as a step in the access authorization process, a check to prohibit privileged access to the information system by non-organizational users.','The organization conducting the inspection/assessment obtains and examines the access authorization process as well as a sampling of information system access agreements to ensure that the organization being inspected/assessed prohibits privileged access to the information system by non-organizational users.'),
('001423','draft','2009-09-25','DISA FSO','policy','The organization defines the time period in which the organization-defined maximum number of consecutive invalid logon attempts occur.','AC-7.3','DoD has defined the time period as 15 minutes.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 15 minutes.'),
('001424','draft','2009-09-25','DISA FSO','technical','The information system dynamically associates security attributes with organization-defined subjects in accordance with organization-defined security policies as information is created and combined.','AC-16(1).1','The organization being inspected/assessed configures the information system to dynamically associates security attributes with the subjects defined in AC-16 (1), CCI 2274 in accordance with the security policies defined in AC-16 (1), CCI 2273 as information is created and combined. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1424.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to dynamically associates security attributes with the subjects defined in AC-16 (1), CCI 2274 in accordance with the security policies defined in AC-16 (1), CCI 2273 as information is created and combined. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1424.'),
('001425','draft','2009-09-25','DISA FSO','technical','The information system provides authorized individuals (or processes acting on behalf of individuals) the capability to change the value of associated security attributes.','AC-16(2).1','The organization being inspected/assessed configures the information system to provide authorized individuals (or processes acting on behalf of individuals) the capability to change the value of associated security attributes. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1425.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provides authorized individuals (or processes acting on behalf of individuals) the capability to change the value of associated security attributes. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1425.'),
('001426','draft','2009-09-25','DISA FSO','technical','The information system maintains the binding of security attributes to information with sufficient assurance that the information--attribute association can be used as the basis for automated policy actions.',NULL,NULL,NULL),
('001427','draft','2009-09-25','DISA FSO','technical','The information system allows authorized users to associate security attributes with information.',NULL,NULL,NULL),
('001428','draft','2009-09-25','DISA FSO','technical','The information system displays security attributes in human-readable form on each object that the system transmits to output devices to identify organization-identified special dissemination, handling, or distribution instructions using organization-identified human-readable, standard naming conventions.','AC-16(5).1','The organization being inspected/assessed configures the information system to display security attributes in human readable form on each object that the system transmits to output devices to identify special dissemination, handling, or distribution instructions defined in AC-16 (5), CCI 1429 using human readable, standard naming conventions defined in AC-16 (5), CCI 1430. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1428.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display security attributes in human readable form on each object that the system transmits to output devices to identify special dissemination, handling, or distribution instructions defined in AC-16 (5), CCI 1429 using human readable, standard naming conventions defined in AC-16 (5), CCI 1430. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1428.'),
('001429','draft','2009-09-25','DISA FSO','policy','The organization identifies special dissemination, handling, or distribution instructions for identifying security attributes on output.','AC-16(5).2','DoD has defined the instructions as for instructions relating to classification, special dissemination, handling, or distribution instructions IAW DODI 5200.1R; for SCI and SAP, IAW Controlled Access Program Coordination Office (CAPCO) register. For all other instructions, not appropriate to define at the Enterprise level. The organization being inspected/assessed defines and documents special dissemination, handling, or distribution instructions not relating to classification, for identifying security attributes on output.','DoD has defined the instructions as for instructions relating to classification, special dissemination, handling, or distribution instructions IAW DODI 5200.1R; for SCI and SAP, IAW Controlled Access Program Coordination Office (CAPCO) register. For all other instructions, not appropriate to define at the Enterprise level. The organization conducting the inspection/assessment obtains and examines the documented instructions not relating to classification to ensure the organization being inspected/assessed identifies special dissemination, handling, or distribution instructions for identifying security attributes on output.'),
('001430','draft','2009-09-25','DISA FSO','policy','The organization identifies human-readable, standard naming conventions for identifying security attributes on output.','AC-16(5).3','DoD has defined the human readable, standard naming conventions for security attributes relating to classification as human readable, standard naming conventions IAW DODI 5200.1R; for TS SCI, IAW Controlled Access Program Coordination Office (CAPCO) register. For all other security attributes, not appropriate to define at the Enterprise level. The organization being inspected/assessed defines and documents all other security attributes not relating to classification.','DoD has defined the human readable, standard naming conventions for security attributes relating to classification as human readable, standard naming conventions IAW DODI 5200.1R; for TS SCI, IAW Controlled Access Program Coordination Office (CAPCO) register. For all other security attributes, not appropriate to define at the Enterprise level. The organization conducting the inspection/assessment obtains and examines the documented security attributes not relating to classification to ensure the organization being inspected/assessed identifies human readable, standard naming conventions for identifying security attributes on output.'),
('001431','draft','2009-09-25','DISA FSO','policy','The organization defines a frequency for monitoring for unauthorized remote connections to the information system.',NULL,NULL,NULL),
('001432','draft','2009-09-25','DISA FSO','policy','The organization takes appropriate action if an unauthorized remote connection to the information system is discovered.',NULL,NULL,NULL),
('001433','draft','2009-09-25','DISA FSO','policy','The organization defines a list of security functions and security-relevant information that for remote access sessions have organization-defined security measures employed and are audited.',NULL,NULL,NULL),
('001434','draft','2009-09-25','DISA FSO','policy','The organization defines additional security measures to be employed when an organization-defined list of security functions and security-relevant information is accessed remotely.',NULL,NULL,NULL),
('001435','draft','2009-09-25','DISA FSO','policy','The organization defines networking protocols within the information system deemed to be nonsecure.',NULL,NULL,NULL),
('001436','draft','2009-09-25','DISA FSO','technical','The organization disables organization-defined networking protocols within the information system deemed to be nonsecure except for explicitly identified components in support of specific operational requirements.',NULL,NULL,NULL),
('001437','draft','2009-09-25','DISA FSO','policy','The organization documents the rationale for the execution of privileged commands and access to security-relevant information in the security plan for the information system.',NULL,NULL,NULL),
('001438','draft','2009-09-25','DISA FSO','policy','The organization establishes usage restrictions for wireless access.','AC-18.1','The organization being inspected/assessed establishes and documents usage restrictions for wireless access.','The organization conducting the inspection/assessment obtains and examines documented usage restrictions to ensure the organization being inspected/assessed establishes usage restrictions for wireless access.'),
('001439','draft','2009-09-25','DISA FSO','policy','The organization establishes implementation guidance for wireless access.','AC-18.2','The organization being inspected/assessed establishes and documents implementation guidance for wireless access.','The organization conducting the inspection/assessment obtains and examines the documented implementation guidance to ensure the organization being inspected/assessed establishes implementation guidance for wireless access.'),
('001440','draft','2009-09-25','DISA FSO','policy','The organization monitors for unauthorized wireless access to the information system.',NULL,NULL,NULL),
('001441','draft','2009-09-25','DISA FSO','policy','The organization authorizes wireless access to the information system prior to allowing such connections.','AC-18.4','The organization being inspected/assessed authorizes wireless access to the information system prior to allowing such connections. The organization must maintain an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed authorizes wireless access to the information system prior to allowing such connections.'),
('001442','draft','2009-09-25','DISA FSO','policy','The organization enforces requirements for wireless connections to the information system.',NULL,NULL,NULL),
('001443','draft','2009-09-25','DISA FSO','technical','The information system protects wireless access to the system using authentication of users and/or devices.','AC-18(1).1','The organization being inspected/assessed configures the information system to protect wireless access to the system using authentication of users and/or devices. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1443.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect wireless access to the system using authentication of users and/or devices. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1443.'),
('001444','draft','2009-09-25','DISA FSO','technical','The information system protects wireless access to the system using encryption.','AC-18(1).2','The organization being inspected/assessed configures the information system to protect wireless access to the system using encryption. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1444.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect wireless access to the system using encryption. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1444.'),
('001445','draft','2009-09-25','DISA FSO','policy','The organization monitors for unauthorized wireless connections to the information system on an organization-defined frequency.',NULL,NULL,NULL),
('001446','draft','2009-09-25','DISA FSO','policy','The organization scans for unauthorized wireless access points on an organization-defined frequency.',NULL,NULL,NULL),
('001447','draft','2009-09-25','DISA FSO','policy','The organization defines a frequency of monitoring for unauthorized wireless connections to information system, including scans for unauthorized wireless access points.',NULL,NULL,NULL),
('001448','draft','2009-09-25','DISA FSO','policy','The organization takes appropriate action if an unauthorized wireless connection is discovered.',NULL,NULL,NULL),
('001449','draft','2009-09-25','DISA FSO','policy','The organization disables, when not intended for use, wireless networking capabilities internally embedded within information system components prior to issuance and deployment.','AC-18(3).1','The organization being inspected/assessed documents and implements a process to disable wireless networking capabilities internally embedded within information system components prior to issuance and deployment when not intended for use.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed disables, when not intended for use, wireless networking capabilities internally embedded within information system components prior to issuance and deployment. The organization conducting the inspection/assessment obtains and examines a sampling of information systems to ensure that any internally embedded wireless networking capabilities are disabled unless a documented need exists.'),
('001450','draft','2009-09-25','DISA FSO','policy','The organization does not allow users to independently configure wireless networking capabilities.',NULL,NULL,NULL),
('001451','draft','2009-09-25','DISA FSO','policy','The organization selects radio antennas and calibrates transmission power levels to reduce the probability that usable signals can be received outside of organization-controlled boundaries.','AC-18(5).1','The organization being inspected/assessed documents and implements a process to select radio antennas and calibrate transmission power levels to reduce the probability that usable signals can be received outside of organization-controlled boundaries.','The organization conducting the inspection/assessment obtains and examines the documentation from radio antenna installation to ensure that the organization being inspected/assessed selects radio antennas and calibrates transmission power levels to reduce the probability that usable signals can be received outside of organization-controlled boundaries.'),
('001452','draft','2009-05-25','DISA FSO','technical','The information system enforces the organization-defined time period during which the limit of consecutive invalid access attempts by a user is counted.',NULL,NULL,NULL),
('001453','draft','2009-09-29','DISA FSO','technical','The information system implements cryptographic mechanisms to protect the integrity of remote access sessions.','AC-17(2).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the integrity of remote access sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1453.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the integrity of remote access sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1453.'),
('001454','draft','2009-09-29','DISA FSO','technical','The organization ensures that remote sessions for accessing an organization-defined list of security functions and security-relevant information are audited.',NULL,NULL,NULL),
('001455','draft','2009-09-29','DISA FSO','policy','The organization explicitly identifies components needed in support of specific operational requirements.',NULL,NULL,NULL),
('001456','draft','2009-09-29','DISA FSO','policy','The organization defines locations that the organization deems to be of significant risk in accordance with organizational policies and procedures.',NULL,NULL,NULL),
('001457','draft','2009-09-29','DISA FSO','policy','The organization defines inspection and preventative measures to be applied on mobile devices returning from locations that the organization deems to be of significant risk in accordance with organizational policies and procedures.',NULL,NULL,NULL),
('001458','draft','2009-09-29','DISA FSO','policy','The organization requires that if classified information is found on mobile devices, the incident handling policy be followed.','AC-19(4).7','The organization being inspected/assessed documents and implements a process to require that if classified information is found on mobile devices, the incident handling policy is followed.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires that if classified information is found on mobile devices, the incident handling policy is followed.'),
('001459','draft','2009-09-29','DISA FSO','policy','The organization defines information system components that provide audit record generation capability.','AU-12.2','DoD has defined the information system components as all information system and network components.','DoD has defined the information system components as all information system and network components.'),
('001460','draft','2009-09-29','DISA FSO','policy','The organization monitors organization-defined open source information and/or information sites per organization-defined frequency for evidence of unauthorized exfiltration or disclosure of organizational information.','AU-13.1','The organization being inspected/assessed documents and implements a process to monitor open source information and/or information sites defined in AU-13, CCI 1915 for evidence of unauthorized exfiltration or disclosure of organizational information on a frequency defined in AU-13, CCI 1461. The organization must maintain an audit trail of monitoring activity.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring activity to ensure the organization being inspected/assessed monitors open source information and/or information sites defined in AU-13, CCI 1915 for evidence of unauthorized exfiltration or disclosure of organizational information on a frequency defined in AU-13, CCI 1461.'),
('001461','draft','2009-09-29','DISA FSO','policy','The organization defines a frequency for monitoring open source information and/or information sites for evidence of unauthorized exfiltration or disclosure of organizational information.','AU-13.2','The organization being inspected/assessed defines and documents the frequency for monitoring open source information and/or information sites for evidence of unauthorized exfiltration or disclosure of organizational information.\n\nDoD has determined that the frequency should be defined at the Component level, not appropriate to define at the Enterprise level. Note: The value in this control may not be used to deny reciprocal acceptance of a C&A (A&A) package.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency for monitoring open source information and/or information sites for evidence of unauthorized exfiltration or disclosure of organizational information.\n\nDoD has determined that the frequency should be defined at the Component level, not appropriate to define at the Enterprise level. Note: The value in this control may not be used to deny reciprocal acceptance of a C&A (A&A) package.'),
('001462','draft','2009-09-29','DISA FSO','technical','The information system provides the capability for authorized users to capture/record and log content related to a user session.','AU-14(2).1','The organization being inspected/assessed configures the information system to provide the capability for authorized users to capture/record and log content related to a user session. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1462.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for authorized users to capture/record and log content related to a user session. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1462.'),
('001463','draft','2009-09-29','DISA FSO','technical','The information system provides the capability to remotely view/hear all content related to an established user session in real time.',NULL,NULL,NULL),
('001464','draft','2009-09-29','DISA FSO','technical','The information system initiates session audits at system start-up.','AU-14(1).1','The organization being inspected/assessed configures the information system to initiate session audits at system start-up. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1464.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to initiate session audits at system start-up. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1464.'),
('001465','draft','2009-09-29','DISA FSO','policy','The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to store organization-controlled information using the external information systems.',NULL,NULL,NULL),
('001466','draft','2009-09-29','DISA FSO','policy','The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to transmit organization-controlled information using the external information systems.',NULL,NULL,NULL),
('001467','draft','2009-09-29','DISA FSO','policy','The organization prohibits authorized individuals from using an external information system to process organization-controlled information except in situations where the organization can verify the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.',NULL,NULL,NULL),
('001468','draft','2009-09-29','DISA FSO','policy','The organization prohibits authorized individuals from using an external information system to store organization-controlled information except in situations where the organization can verify the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.',NULL,NULL,NULL),
('001469','draft','2009-09-29','DISA FSO','policy','The organization prohibits authorized individuals from using an external information system to transmit organization-controlled information except in situations where the organization can verify the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.',NULL,NULL,NULL),
('001470','draft','2009-09-29','DISA FSO','policy','The organization defines information sharing circumstances where user discretion is required.','AC-21.2','The organization being inspected/assessed defines and documents information sharing circumstances where user discretion is required. DoD has determined the information sharing circumstances are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information sharing circumstances to ensure the organization being inspected/assessed defines information sharing circumstances where user discretion is required. DoD has determined the information sharing circumstances are not appropriate to define at the Enterprise level.'),
('001471','draft','2009-09-29','DISA FSO','policy','The organization employs organization-defined automated mechanisms or manual processes required to assist users in making information sharing/collaboration decisions.','AC-21.3','The organization being inspected/assessed implements the process defined in AC-21, CCI 1472 to assist users in making information sharing/collaboration decisions.','The organization conducting the inspection/assessment obtains and examines the documented process defined per AC-21, CCI 1472 to ensure the organization being inspected/assessed assists users in making information sharing/collaboration decisions.'),
('001472','draft','2009-09-29','DISA FSO','policy','The organization defines the automated mechanisms or manual processes required to assist users in making information sharing/collaboration decisions.','AC-21.4','The organization being inspected/assessed defines and documents the automated mechanisms or manual processes required to assist users in making information sharing/collaboration decisions. DoD has determined the automated mechanisms or manual processes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented automated mechanisms to ensure the organization being inspected/assessed defines the automated mechanisms or manual processes required to assist users in making information sharing/collaboration decisions. DoD has determined the automated mechanisms or manual processes are not appropriate to define at the Enterprise level.'),
('001473','draft','2009-09-29','DISA FSO','policy','The organization designates individuals authorized to post information onto a publicly accessible information system.','AC-22.1','The organization being inspected/assessed identifies and documents individuals authorized to post information onto a publicly accessible information system.','The organization conducting the inspection/assessment obtains and examines the list of individuals to ensure the organization being inspected/assessed designates individuals authorized to post information onto a publicly accessible information system.'),
('001474','draft','2009-09-29','DISA FSO','policy','The organization trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information.','AC-22.2','The organization being inspected/assessed documents and implements a process to train authorized individuals to ensure that publicly accessible information does not contain nonpublic information. The organization must maintain an audit trail of the training conducted.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of the training conducted to ensure the organization being inspected/assessed trains authorized individuals to ensure that publicly accessible information does not contain nonpublic information.'),
('001475','draft','2009-09-29','DISA FSO','policy','The organization reviews the proposed content of information prior to posting onto the publicly accessible information system to ensure that nonpublic information is not included.','AC-22.3','The organization being inspected/assessed','The organization conducting the inspection/assessment obtains and examines'),
('001476','draft','2009-09-29','DISA FSO','policy','The organization reviews the content on the publicly accessible information system for nonpublic information on an organization-defined frequency.','AC-22.4','The organization being inspected/assessed documents and implements a process to review the content on the publicly accessible information system for nonpublic information on an organization-defined frequency. The organization must maintain an audit trail of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reviews to ensure the organization being inspected/assessed reviews the content on the publicly accessible information system for nonpublic information on an organization-defined frequency.'),
('001477','draft','2009-09-29','DISA FSO','policy','The organization defines a frequency for reviewing the content on the publicly accessible information system for nonpublic information.','AC-22.5','DoD has defined the frequency as every 90 days or as new information is posted.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 90 days or as new information is posted.'),
('001478','draft','2009-09-29','DISA FSO','policy','The organization removes nonpublic information from the publicly accessible information system, if discovered.','AC-22.6','The organization being inspected/assessed documents and implements a process to remove nonpublic information from the publicly accessible information system, if discovered.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed removes nonpublic information from the publicly accessible information system, if discovered.'),
('001479','draft','2009-09-29','DISA FSO','policy','The organization provides refresher security awareness training to all information system users (including managers, senior executives, and contractors) in accordance with the organization-defined frequency.','AT-2.4','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.','DoDD 8570.01 meets the DoD requirement for IA awareness training policy and procedures. DISA\'s DoD IA awareness CBT is the DoD baseline standard.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDD 8570.01.'),
('001480','draft','2009-09-29','DISA FSO','policy','The organization defines the frequency for providing refresher security awareness training to all information system users (including managers, senior executives, and contractors).','AT-2.1','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level (DoDD 8570.01). DoD has defined the frequency as annually.'),
('001481','draft','2009-09-29','DISA FSO','policy','The organization provides organization-defined personnel or roles with initial training in the employment and operation of environmental controls.','AT-3(1).1','The organization being inspected/assessed:\n1. Identifies and documents environmental controls that require training.\n2. Identifies the personnel defined in AT-3 (1), CCI 2050\n3. Ensures designated personnel receive this training.\n4. Maintains and monitors records of personnel who have received this training.','The organization conducting the inspection/assessment obtains and examines:\n1. Documentation of environmental controls that require training.\n2. Documented list of personnel defined in AT-3 (1), CCI 2050\n3. Ensures identified personnel have received the initial training.'),
('001482','draft','2009-09-29','DISA FSO','policy','The organization provides organization-defined personnel or roles with refresher training in the employment and operation of environmental controls in accordance with the organization-defined frequency.','AT-3(1).2','The organization being inspected/assessed:\n1. Identifies and documents environmental controls that require training.\n2. Identifies the personnel defined in AT-3 (1), CCI 2050\n3. Ensures designated personnel receive this training annually\n4. Maintains and monitors records of personnel who have received this training.\n\nDoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines:\n1. Documentation of environmental controls that require training.\n2. Documented list of personnel defined in AT-3 (1), CCI 2050\n3. Ensures identified personnel have received training annually.\n\nDoD has defined the frequency as annually.'),
('001483','draft','2009-09-29','DISA FSO','policy','The organization defines a frequency for providing employees with refresher training in the employment and operation of environmental controls.','AT-3(1).3','DoD has defined the frequency as annual.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annual.'),
('001484','draft','2009-09-29','DISA FSO','policy','The organization defines frequency of (or situation requiring) auditing for each identified event.','AU-2.6','DoD has defined the frequency as all auditable events defined in AU-2 (a) per occurrence.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as all auditable events defined in AU-2 (a) per occurrence.'),
('001485','draft','2009-09-29','DISA FSO','policy','The organization defines the events which are to be audited on the information system on an organization-defined frequency of (or situation requiring) auditing for each identified event.','AU-2.7','The organization being inspected/assessed defines and documents events which are to be audited on the information system. Events should be selected from the events the information system is capable of auditing as defined in AU-2 (a) and should be based on ongoing risk assessments of current threat information and environment.\n\nDoD has determined that the events are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines\nthe documented list of events which are to be audited on the information system to ensure those events have been defined.\n\nDoD has determined that the events are not appropriate to define at the Enterprise level.'),
('001486','draft','2009-09-29','DISA FSO','policy','The organization defines a frequency for reviewing and updating the list of organization-defined auditable events.','AU-2(3).2','DoD has defined the frequency as annually or more frequently upon changes to situational awareness of threats or vulnerabilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually or more frequently upon changes to situational awareness of threats or vulnerabilities.'),
('001487','draft','2009-09-29','DISA FSO','technical','The information system generates audit records containing information that establishes the identity of any individuals or subjects associated with the event.','AU-3.6','The organization being inspected/assessed configures the information system to generate audit records containing information that establishes the identity of any individuals or subjects associated with the event. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1487.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate audit records containing information that establishes the identity of any individuals or subjects associated with the event. The organization conducting the inspection/assessment reviews the audit records generated to ensure that the records contain information that establishes the identity of any individuals or subjects associated with the event. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1487.'),
('001488','draft','2009-09-29','DISA FSO','policy','The organization defines additional, more detailed information to be included in the audit records.','AU-3(1).2','The organization being inspected/assessed defines and documents additional, more detailed information to be included in the audit records. The additional information must include at a minimum, full-text recording of privileged commands or the individual identities of group account users. The additional information must provide sufficient detail to reconstruct events to determine cause of compromise and magnitude of damage, malfunction, or security violation.\n\nDoD has determined that additional, more detailed information must include, at a minimum, full-text recording of privileged commands or the individual identities of group account users. DoD has determined that all additional, more detailed information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list of additional more detailed information to be included in the audit records to ensure that:\n1. The list is defined; and\n2. The list includes full-text recording of privileged commands or the individual identities of group account users.\n\nDoD has determined that additional, more detailed information must include, at a minimum, full-text recording of privileged commands or the individual identities of group account users. DoD has determined that it is not appropriate to define at the Enterprise level.'),
('001489','draft','2009-09-29','DISA FSO','policy','The organization defines information system components for which generated audit records are centrally managed by the organization.',NULL,NULL,NULL),
('001490','draft','2009-09-29','DISA FSO','policy','The organization defines actions to be taken by the information system upon audit failure (e.g., shut down information system, overwrite oldest audit records, stop generating audit records).','AU-5.4','The organization being inspected/assessed will define and document actions to be taken by the information system upon audit failure. The organization shall consider trade-offs between the needs for system availability and audit integrity when defining the actions. Unless availability is an overriding concern, the default action should be to shut down the information system. DoD has determined that the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented actions to ensure the organization being inspected/assessed has defined the actions to be taken by the information system upon audit failure. DoD has determined that the actions are not appropriate to define at the Enterprise level.'),
('001491','draft','2009-09-29','DISA FSO','policy','The organization correlates information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.','AU-6(6).1','The organization being inspected/assessed will document and implement a process to correlate information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.','The organization conducting the inspection/assessment obtains and examines the documented process and correlated results to ensure the organization being inspected/assessed correlates information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.'),
('001492','draft','2009-09-29','DISA FSO','policy','The organization defines an authoritative time source for the synchronization of internal information system clocks.','AU-8(1).2','DoD has defined the authoritative time source as an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet / SIPRNet) and/or the Global Positioning System (GPS).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the authoritative time source as an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet / SIPRNet) and/or the Global Positioning System (GPS).'),
('001493','draft','2009-09-29','DISA FSO','technical','The information system protects audit tools from unauthorized access.','AU-9.4','The organization being inspected/assessed configures the information system to disallow unauthorized access to audit tools. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1493.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to disallow unauthorized access to audit tools. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1493.'),
('001494','draft','2009-09-29','DISA FSO','technical','The information system protects audit tools from unauthorized modification.','AU-9.5','The organization being inspected/assessed configures the information system to disallow unauthorized modification of audit tools. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1494.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to disallow unauthorized modification of audit tools. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1494.'),
('001495','draft','2009-09-29','DISA FSO','technical','The information system protects audit tools from unauthorized deletion.','AU-9.6','The organization being inspected/assessed configures the information system to disallow unauthorized deletion of audit tools. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1495.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to disallow unauthorized deletion of audit tools. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1495.'),
('001496','draft','2009-09-29','DISA FSO','technical','The information system implements cryptographic mechanisms to protect the integrity of audit tools.','AU-9(3).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the integrity of audit tools. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1496.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to implement cryptographic mechanisms to protect the integrity of audit tools. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1496.'),
('001497','draft','2009-09-29','DISA FSO','policy','The organization defines a frequency for the reviews and updates to the baseline configuration of the information system.','CM-2(1).2','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001498','draft','2009-09-29','DISA FSO','policy','The organization defines a time period after which proposed changes to the information system that have not been approved or disapproved are highlighted.','CM-3(1).5','DoD has defined the time period as 7 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 7 days.'),
('001499','draft','2009-09-29','DISA FSO','technical','The organization limits privileges to change software resident within software libraries.','CM-5(6).1','The organization being inspected/assessed documents and implements a process to limit privileges to accounts authorized to change software resident within software libraries. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1499.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed limits privileges to change software resident within software libraries. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1499.'),
('001500','draft','2009-09-29','DISA FSO','technical','The information system automatically implements organization-defined safeguards and countermeasures if security functions (or mechanisms) are changed inappropriately.',NULL,NULL,NULL),
('001501','draft','2009-09-29','DISA FSO','policy','The organization defines safeguards and countermeasures to be employed by the information system if security functions (or mechanisms) are changed inappropriately.',NULL,NULL,NULL),
('001502','draft','2009-09-29','DISA FSO','policy','The organization monitors changes to the configuration settings in accordance with organizational policies and procedures.','CM-6.11','The organization being inspected/assessed develops and documents a process for monitoring changes to the configuration settings in accordance with organizational policies and procedures.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed monitors changes to the configuration settings in accordance with organizational policies and procedures.'),
('001503','draft','2009-09-29','DISA FSO','policy','The organization controls changes to the configuration settings in accordance with organizational policies and procedures.','CM-6.12','The organization being inspected/assessed develops and documents a process for controlling changes to the configuration settings in accordance with organizational policies and procedures.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed controls changes to the configuration settings in accordance with organizational policies and procedures.'),
('001504','draft','2009-11-02','DISA FSO','policy','The organization develops and documents a personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PS-1.3','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.'),
('001505','draft','2009-11-02','DISA FSO','policy','The organization disseminates a personnel security policy to organization-defined personnel or roles.','PS-1.4','DoD disseminates DoD 5200.2-R via the DoD Issuance site: http://www.dtic.mil/whs/directives/corres/pub1.html to meet the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.'),
('001506','draft','2009-11-02','DISA FSO','policy','The organization reviews and updates the current personnel security policy in accordance with organization-defined frequency.','PS-1.7','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.'),
('001507','draft','2009-11-02','DISA FSO','policy','The organization defines the frequency with which to review and update the current personnel security policy.','PS-1.8','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('001508','draft','2009-11-02','DISA FSO','policy','The organization defines the frequency with which to review and update the current personnel security procedures.','PS-1.10','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('001509','draft','2009-11-02','DISA FSO','policy','The organization develops and documents procedures to facilitate the implementation of the personnel security policy and associated personnel security controls.','PS-1.6','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.'),
('001510','draft','2009-11-02','DISA FSO','policy','The organization disseminates personnel security procedures to organization-defined personnel or roles.','PS-1.5','DoD disseminates DoD 5200.2-R via the DoD Issuance site: http://www.dtic.mil/whs/directives/corres/pub1.html to meet the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.'),
('001511','draft','2009-11-02','DISA FSO','policy','The organization reviews and updates the current personnel security procedures in accordance with organization-defined frequency.','PS-1.9','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for personnel security policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD 5200.2-R.'),
('001512','draft','2009-11-02','DISA FSO','policy','The organization assigns a risk designation to all organizational positions.','PS-2.1','The organization being inspected/assessed will designate and document all organizational positions, to include government and contract positions, with the appropriate ADP/IT level designation, IAW DoD 5200.2-R.','The organization conducting the inspection/assessment obtains and examines documentation of the ADP/IT level designations.'),
('001513','draft','2009-11-02','DISA FSO','policy','The organization establishes screening criteria for individuals filling organizational positions.','PS-2.2','DoD 5200.2-R meets the DoD requirements for establishing screening criteria for individuals filling organizational positions.\n\nDoD organizations are automatically compliant with this CCI as they are covered at the DoD level by DoD 5200.2-R.','DoD 5200.2-R meets the DoD requirements for establishing screening criteria for individuals filling organizational positions.\n\nDoD organizations are automatically compliant with this CCI as they are covered at the DoD level by DoD 5200.2-R.'),
('001514','draft','2009-11-02','DISA FSO','policy','The organization reviews and updates position risk designations in accordance with organization-defined frequency.','PS-2.3','The organization being inspected/assessed reviews position risk designations annually and revises designations as required based on the reviews. Records of these reviews must be maintained as an audit trail. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment reviews the audit records of the position designation reviews to ensure reviews are done annually. DoD has defined the frequency as annually.'),
('001515','draft','2009-11-02','DISA FSO','policy','The organization defines the frequency with which to review and update position risk designations.','PS-2.4','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001516','draft','2009-11-02','DISA FSO','policy','The organization screens individuals prior to authorizing access to the information system.','PS-3.1','The organization being inspected/assessed will screen all government and contract personnel to ensure they meet the appropriate ADP/IT level designation requirements IAW DoD 5200.2-R prior to authorizing access to the information system.','The organization conducting the inspection/assessment obtains and examines the information system access list (AC-2) and compares a sampling of authorized users to manning documents (PS-2) to ensure access was granted appropriately IAW ADP/IT level designation requirements within DoD 5200.2-R.'),
('001517','draft','2009-11-02','DISA FSO','policy','The organization rescreens individuals with authorized access to the information system according to organization-defined conditions requiring rescreening, and where rescreening is so indicated, on the organization-defined frequency of such rescreening.','PS-3.2','The information system owner will rescreen individuals according to system owner defined list of conditions requiring rescreening (CCI-001518) individuals for access to the information system and frequency (CCI - 001519) of such rescreening. Rescreening actions will be maintained as an audit trail (AU-2).','The organization conducting the inspection/assessment obtains and examines audit records of rescreening actions to ensure the system owner is rescreening individuals according to a system owner-defined list of conditions requiring rescreening and, where re-screening is so indicated, based on the system owner-defined frequency of such rescreening.'),
('001518','draft','2009-11-02','DISA FSO','policy','The organization defines the conditions requiring rescreening of individuals with authorized access to the information system.','PS-3.3','The information system owner will develop and document the list of conditions requiring rescreening individuals for access to the information system. DoD has determined the list of conditions is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documentation of conditions requiring rescreening of individuals for access to the information system. DoD has determined the list of conditions is not appropriate to define at the Enterprise level.'),
('001519','draft','2009-11-02','DISA FSO','policy','The organization defines the frequency for rescreening individuals with authorized access to the information system when organization-defined conditions requiring rescreening are met.','PS-3.4','The information system owner will define and document the required frequency of rescreening for access to the information system. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documentation defining the required frequency for rescreening individuals for access to the system. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('001520','draft','2009-11-02','DISA FSO','policy','The organization ensures that individuals accessing an information system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the information to which they have access on the system.','PS-3(1).1','The organization being inspected/assessed ensures that individuals accessing an information system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the information to which they have access on the system.','The organization conducting the inspection/assessment obtains and examines security clearance data for all individuals using the classified information system and the system account list (AC-2) and compares lists to ensure all personnel accessing the system are cleared and indoctrinated to the highest classification level of the information to which they have access on the system.'),
('001521','draft','2009-11-02','DISA FSO','policy','The organization ensures that individuals accessing an information system processing, storing, or transmitting types of classified information which require formal indoctrination, are formally indoctrinated for all of the relevant types of information to which they have access on the system.','PS-3(2).1','The organization being inspected/assessed ensures that individuals accessing an information system processing, storing, or transmitting types of classified information (e.g. Special Access Programs (SAP), Restricted Data (RD), and Sensitive Compartmented Information (SCI)) which require formal indoctrination, is formally indoctrinated for all of the relevant types of information to which they have access on the system.','The organization conducting the inspection/assessment obtains and examines security clearance data for all individuals using the classified information system and the system account list (AC-2) and compares lists to ensure all personnel accessing the system are formally indoctrinated for all of the relevant types of information to which they have access on the system.'),
('001522','draft','2009-11-02','DISA FSO','policy','The organization, upon termination of individual employment, disables information system access within an organization-defined time period.','PS-4.1','The organization being inspected/assessed upon termination of individual employment, terminates information system access immediately and IAW organization security policy and procedures. The organization must retain an audit trail of account termination actions (AU-2). DoD has defined the time period as immediately.','The organization conducting the inspection/assessment obtains and examines organizational security policy and procedures documentation and audit records of account termination actions to ensure account termination actions are conducted immediately and IAW organizational security policy and procedures. DoD has defined the time period as immediately.'),
('001523','draft','2009-11-02','DISA FSO','policy','The organization, upon termination of individual employment, conducts exit interviews that include a discussion of organization-defined information security topics.','PS-4.4','The organization being inspected/assessed, conducts exit interviews that include a discussion of information security topics defined in PS-4, CCI 3024 upon termination of individual employment IAW organization security policy and procedures. The organization must retain an audit trail of conducted exit interviews (AU-2)','The organization conducting the inspection/assessment obtains and examines documentation of departed personnel and the audit trail of conducted exit interviews to ensure all departed personnel had exit interviews conducted that include a discussion of information security topics defined in PS-4, CCI 3024.'),
('001524','draft','2009-11-02','DISA FSO','policy','The organization, upon termination of individual employment, retrieves all security-related organizational information system-related property.','PS-4.6','The organization being inspected/assessed upon termination of individual employment retrieves all security-related organizational information systems-related property IAW organization security policy and procedures. The organization must retain an audit trail of all retrieved security-related organizational information systems-related property (AU-2).','The organization conducting the inspection/assessment obtains and examines appropriate organization security-related organizational information systems-related property documentation/logs and compares to audit trail of all retrieved security-related organizational information systems-related property (AU-2) to ensure all property has been retrieved.'),
('001525','draft','2009-11-02','DISA FSO','policy','The organization, upon termination of individual employment, retains access to organizational information formerly controlled by the terminated individual.','PS-4.7','The organization being inspected/assessed upon termination of individual employment retains access to organizational information formerly controlled by terminated individual IAW organization security policy and procedures. Organizational information formerly controlled by terminated individuals generally refers to online work-product including email files.','The organization conducting the inspection/assessment interviews appropriate IT and security personnel to validate the organization has procedures in place which, upon termination of individual\'s employment, will ensure it retains access to organizational information formerly controlled by the terminated individual.'),
('001526','draft','2009-11-02','DISA FSO','policy','The organization, upon termination of individual employment, retains access to organizational information systems formerly controlled by the terminated individual.','PS-4.8','The organization being inspected/assessed upon termination of individual employment retains access to organizational information systems formerly controlled by terminated individual IAW organization security policy and procedures. Organizational information systems formerly controlled by terminated individuals generally refers to issued hardware (e.g. laptops, BlackBerrys, PEDs, removable media, etc.)','The organization conducting the inspection/assessment interviews appropriate IT and security personnel to validate the organization has procedures in place which, upon termination of individual\'s employment, will ensure it retains access to organizational information systems formerly controlled by the terminated individual.'),
('001527','draft','2009-11-03','DISA FSO','policy','The organization reviews and confirms the ongoing operational need for current logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization.','PS-5.1','The organization being inspected/assessed reviews and confirms ongoing operational need for logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization. The organization must maintain an audit trail of reviews.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews to ensure that the organization has confirmed the ongoing operational need for logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization.'),
('001528','draft','2009-11-03','DISA FSO','policy','The organization initiates organization-defined transfer or reassignment actions within an organization-defined time period following the formal personnel transfer action.','PS-5.2','The organization being inspected/assessed initiates transfer or reassignment actions to ensure all system accesses no longer required are removed and actions to ensure all system accesses required due to the individual\'s new position are granted immediately when personnel are reassigned or transferred to other positions. DoD defines transfer or reassignment actions as actions to ensure all system accesses no longer required are removed. DoD defines the time period as immediately.','The organization conducting the inspection/assessment obtains and examines appropriate organization security-related organizational physical and logical access documentation/logs and compares to transferred personnel documentation to ensure appropriate logical and physical access have been revoked for previous positions and granted for new positions immediately. DoD defines the time period as immediately.'),
('001529','draft','2009-11-03','DISA FSO','policy','The organization defines transfer or reassignment actions to initiate within an organization-defined time period following the formal personnel transfer action.','PS-5.3','DoD defines transfer or reassignment actions as actions to ensure all system accesses no longer required are removed.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD defines transfer or reassignment actions as actions to ensure all system accesses no longer required are removed.'),
('001530','draft','2009-11-03','DISA FSO','policy','The organization defines the time period within which the organization initiates organization-defined transfer or reassignment actions following the formal personnel transfer action.','PS-5.4','DoD defines the time period as immediately.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD defines the time period as immediately.'),
('001531','draft','2009-11-03','DISA FSO','policy','The organization ensures that individuals requiring access to organizational information and information systems sign appropriate access agreements prior to being granted access.','PS-6.4','The organization being inspected/assessed will ensure all individuals have appropriate access agreements in place prior to being granted access to information and information systems. DD Form 2875 is the accepted DoD methodology of requesting and granting of access to information and information systems.','The organization conducting the inspection/assessment obtains a list of organizational individuals with active accounts and validates the existence of signed DD Form 2875 (paper or electronic) associated with a sampling of individuals selected from the list.'),
('001532','draft','2009-11-03','DISA FSO','policy','The organization reviews and updates access agreements for organizational information systems in accordance with organization-defined frequency.','PS-6.2','The organization being inspected/assessed reviews/updates the access agreements annually of employees who have signed access agreements. The purpose of this review/update is to ensure access agreements are current and departed employees no longer have access agreements. The organization must maintain an audit trail of the review and update activity for review. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail to ensure review/update occurred annually and departed employees no longer have valid access agreements.'),
('001533','draft','2009-11-03','DISA FSO','policy','The organization defines the frequency with which to review and update access agreements for organizational information systems.','PS-6.3','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001534','draft','2009-11-03','DISA FSO','policy','The organization ensures that access to information with special protection measures is granted only to individuals who have a valid access authorization that is demonstrated by assigned official government duties.',NULL,NULL,NULL),
('001535','draft','2009-11-03','DISA FSO','policy','The organization ensures that access to information with special protection measures is granted only to individuals who satisfy associated personnel security criteria.',NULL,NULL,NULL),
('001536','draft','2009-11-03','DISA FSO','policy','The organization ensures that access to classified information requiring special protection is granted only to individuals who have a valid access authorization that is demonstrated by assigned official government duties.','PS-6(2).1','The organization being inspected/assessed will grant access to classified information requiring special protection only to individuals who have a valid access authorization that is demonstrated by assigned official government duties. DD Form 2875 is the accepted DoD methodology of requesting and granting of access to information and information systems.','The organization conducting the inspection/assessment obtains a list of organizational individuals with active accounts and validates the existence of signed DD Form 2875 (paper or electronic) associated with individuals requiring access to classified information with special protection.'),
('001537','draft','2009-11-03','DISA FSO','policy','The organization ensures that access to classified information requiring special protection is granted only to individuals who satisfy associated personnel security criteria.','PS-6(2).2','The organization being inspected/assessed ensures all authorized access to classified information requiring special protection is granted only to those individuals who have satisfied the associated personnel security criteria. DD Form 2875 is the accepted DoD methodology of requesting and granting of access to information and information systems.','The organization conducting the inspection/assessment reviews access agreements; access authorizations; personnel security criteria; along with other relevant documents or records to ensure the organization has granted authorized access to classified information requiring special protection only to those individuals who have satisfied the associated personnel security criteria.'),
('001538','draft','2009-11-03','DISA FSO','policy','The organization ensures that access to classified information requiring special protection is granted only to individuals who have read, understood, and signed a nondisclosure agreement.','PS-6(2).3','The organization being inspected/assessed grants access to classified information requiring special protection only to individuals who have read, understood, and signed a nondisclosure agreement.','The organization conducting the inspection/assessment obtains and examines the access roster and requests the signed nondisclosure agreements of a sampling of individuals to validate the organization requires all access to classified information requiring special protection is granted only to individuals who have a signed nondisclosure agreement.'),
('001539','draft','2009-11-03','DISA FSO','policy','The organization establishes personnel security requirements including security roles and responsibilities for third-party providers.','PS-7.1','DoD 5220.22-M, DoD 5220.22-R, DoD 5200.2-R, DoD 8570.01-M and DoDI 3020.41 meet the DoD personnel security requirements including security roles and responsibilities for third-party providers.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoD 5220.22-M, DoD 5220.22-R, DoD 5200.2-R, DoD 8570.01-M and DoDI 3020.41.','DoD 5220.22-M, DoD 5220.22-R, DoD 5200.2-R, DoD 8570.01-M and DoDI 3020.41 meet the DoD personnel security requirements including security roles and responsibilities for third-party providers.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoD 5220.22-M, DoD 5220.22-R, DoD 5200.2-R, DoD 8570.01-M and DoDI 3020.41.'),
('001540','draft','2009-11-03','DISA FSO','policy','The organization documents personnel security requirements for third-party providers.','PS-7.3','The organization being inspected/assessed documents personnel security requirements for third-party providers.','The organization conducting the inspection/assessment obtains and examines the personnel security requirements to ensure the organization being inspected/assessed documents personnel security requirements for third-party providers.'),
('001541','draft','2009-11-03','DISA FSO','policy','The organization monitors third-party provider compliance with personnel security requirements.','PS-7.7','The organization being inspected/assessed monitors third-party provider compliance with personnel security requirements. The organization must maintain an audit trail of monitoring activity.','The organization conducting the inspection/assessment obtains and examines the audit trail of monitoring activity to ensure the organization being inspected/assessed monitors third-party provider compliance with personnel security requirements.'),
('001542','draft','2009-11-03','DISA FSO','policy','The organization employs a formal sanctions process for individuals failing to comply with established information security policies and procedures.','PS-8.1','The organization being inspected/assessed will develop formal procedures within the organizational security policy to employ formal sanctions for personnel failing to comply with established information security policies and procedures.','The organization conducting the inspection/assessment obtains and examines the organizational security policy to ensure it addresses formal procedures for sanctions and interviews security personnel to validate the organization employs a formal sanctions process for personnel failing to comply with established information security policies and procedures.'),
('001543','draft','2009-11-03','DISA FSO','policy','The organization disseminates the most recent information security program plan to appropriate entities in the organization that includes roles, responsibilities, management commitment, coordination among organizational entities, and compliance.',NULL,NULL,NULL),
('001544','draft','2009-11-30','DISA FSO','policy','The organization manages information system authenticators by ensuring that authenticators have sufficient strength of mechanism for their intended use.','IA-5.3','The organization being inspected/assessed documents and implements authenticator strength mechanisms sufficient for the intended use of the authenticators.','The organization conducting the inspection/assessment obtains and examines documented authenticator strength mechanisms to ensure that they are defined and that the mechanisms have sufficient strength for the intended use of the authenticators.'),
('001545','draft','2010-05-11','DISA FSO','policy','The organization defines a frequency for reviewing and updating the access control policy.','AC-1.8','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001546','draft','2010-05-11','DISA FSO','policy','The organization defines a frequency for reviewing and updating the access control procedures.','AC-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001547','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency on which it will review information system accounts for compliance with account management requirements.','AC-2.23','DoD has defined the frequency as at a minimum, annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at a minimum, annually.'),
('001548','draft','2010-05-11','DISA FSO','policy','The organization defines the information flow control policies for controlling the flow of information within the system.','AC-4.3','The organization being inspected/assessed defines and documents the information flow control policies for controlling the flow of information within the system. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information flow control policies to ensure the organization being inspected/assessed defines the information flow control policies for controlling the flow of information within the system. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.'),
('001549','draft','2010-05-11','DISA FSO','policy','The organization defines the information flow control policies for controlling the flow of information between interconnected systems.','AC-4.4','The organization being inspected/assessed defines and documents the information flow control policies for controlling the flow of information between interconnected systems. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information flow control policies to ensure the organization being inspected/assessed defines the information flow control policies for controlling the flow of information between interconnected systems. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.'),
('001550','draft','2010-05-11','DISA FSO','policy','The organization defines approved authorizations for controlling the flow of information within the system.','AC-4.5','The organization being inspected/assessed defines and documents approved authorizations for controlling the flow of information within the system.','The organization conducting the inspection/assessment obtains and examines the documented approved authorizations to ensure the organization being inspected/assessed defines approved authorizations for controlling the flow of information within the system.'),
('001551','draft','2010-05-11','DISA FSO','policy','The organization defines approved authorizations for controlling the flow of information between interconnected systems.','AC-4.6','The organization being inspected/assessed defines and documents approved authorizations for controlling the flow of information between interconnected systems.','The organization conducting the inspection/assessment obtains and examines the documented approved authorizations to ensure the organization being inspected/assessed defines approved authorizations for controlling the flow of information between interconnected systems.'),
('001552','draft','2010-05-11','DISA FSO','policy','The organization defines policy that allows or disallows information flows based on changing conditions or operational considerations.',NULL,NULL,NULL),
('001553','draft','2010-05-11','DISA FSO','policy','The organization defines the security policy filters that privileged administrators have the capability to enable/disable.','AC-4(10).2','The organization being inspected/assessed defines and documents the security policy filters that privileged administrators have the capability to enable/disable. DoD has determined the security policy filters are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policy filters to ensure the organization being inspected/assessed defines the security policy filters that privileged administrators have the capability to enable/disable. DoD has determined the security policy filters are not appropriate to define at the Enterprise level.'),
('001554','draft','2010-05-11','DISA FSO','policy','The organization defines the security policy filters that privileged administrators have the capability to configure.','AC-4(11).2','The organization being inspected/assessed defines and documents the security policy filters that privileged administrators have the capability to configure. DoD has determined the security policy filters are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policy filters to ensure the organization being inspected/assessed defines the security policy filters that privileged administrators have the capability to configure. DoD has determined the security policy filters are not appropriate to define at the Enterprise level.'),
('001555','draft','2010-05-11','DISA FSO','technical','The information system uniquely identifies destination domains for information transfer.',NULL,NULL,NULL),
('001556','draft','2010-05-11','DISA FSO','technical','The information system uniquely authenticates destination domains for information transfer.',NULL,NULL,NULL),
('001557','draft','2010-05-11','DISA FSO','technical','The information system tracks problems associated with the information transfer.',NULL,NULL,NULL),
('001558','draft','2010-05-11','DISA FSO','policy','The organization defines the security functions (deployed in hardware, software, and firmware) for which access must be explicitly authorized.','AC-6(1).1','DoD has defined the security functions as all functions not publicly accessible.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security functions as all functions not publicly accessible.'),
('001559','draft','2010-05-11','DISA FSO','policy','The organization identifies the individuals authorized to change the value of associated security attributes.','AC-16(2).2','The organization being inspected/assessed identifies and documents the individuals authorized to change the value of associated security attributes.','The organization conducting the inspection/assessment obtains and examines the documented individuals to ensure the organization being inspected/assessed identifies the individuals authorized to change the value of associated security attributes.'),
('001560','draft','2010-05-11','DISA FSO','policy','The organization identifies individuals (or processes acting on behalf of individuals) authorized to associate organization-defined security attributes with organization-defined objects.','AC-16(4).1','The organization being inspected/assessed identifies and documents individuals (or processes acting on behalf of individuals) authorized to associate security attributes defined in AC-16 (4), CCI 2288 with objects defined in AC-16 (4), CCI 2287.','The organization conducting the inspection/assessment obtains and examines the documented individuals to ensure the organization being inspected/assessed identifies individuals (or processes acting on behalf of individuals) authorized to associate security attributes defined in AC-16 (4), CCI 2288 with objects defined in AC-16 (4), CCI 2287.'),
('001561','draft','2010-05-11','DISA FSO','policy','The organization defines managed access control points for remote access to the information system.','AC-17(3).2','The organization being inspected/assessed defines and documents managed access control points for remote access to the information system.','The organization conducting the inspection/assessment obtains and examines the documented managed access points to ensure the organization being inspected/assessed defines managed access control points for remote access to the information system.'),
('001562','draft','2010-05-11','DISA FSO','policy','The organization defines the appropriate action(s) to be taken if an unauthorized remote connection is discovered.',NULL,NULL,NULL),
('001563','draft','2010-05-11','DISA FSO','policy','The organization defines the appropriate action(s) to be taken if an unauthorized wireless connection is discovered.',NULL,NULL,NULL),
('001564','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency of security awareness and training policy reviews and updates.','AT-1.5','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('001565','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency of security awareness and training procedure reviews and updates.','AT-1.10','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('001566','draft','2010-05-11','DISA FSO','policy','The organization provides organization-defined personnel or roles with initial training in the employment and operation of physical security controls.','AT-3(2).1','The organization being inspected/assessed:\n1. Identifies and documents physical security controls that require training.\n2. Identifies the personnel defined in AT-3 (2), CCI 2051\n3. Ensures designated personnel receive this training.\n4. Maintains and monitors records of personnel who have received this training.','The organization conducting the inspection/assessment obtains and examines:\n1. Documentation of physical security controls that require training.\n2. Documented list of personnel defined in AT-3 (2), CCI 2051\n3. Ensures identified personnel have received the initial training.'),
('001567','draft','2010-05-11','DISA FSO','policy','The organization provides organization-defined personnel or roles with refresher training in the employment and operation of physical security controls in accordance with the organization-defined frequency.','AT-3(2).2','The organization being inspected/assessed:\n1. Identifies and documents physical security controls that require training.\n2. Identifies personnel defined in AT-3 (2), CCI 2051\n3. Ensures designated personnel receive this training annually\n4. Maintains and monitors records of personnel who have received this training.\n\nDoD has defined the frequency as annual.','The organization conducting the inspection/assessment obtains and examines:\n1. Documentation of physical security controls that require training.\n2. Documented list of personnel defined in AT-3 (2), CCI 2051\n3. Ensures identified personnel have received training annually.\n\nDoD has defined the frequency as annual.'),
('001568','draft','2010-05-11','DISA FSO','policy','The organization defines a frequency for providing employees with refresher training in the employment and operation of physical security controls.','AT-3(2).3','DoD has defined the frequency as annual.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annual.'),
('001569','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency on which it will review and update the audit and accountability policy.','AU-1.8','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001570','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency on which it will review and update the audit and accountability procedures.','AU-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001571','draft','2010-05-11','DISA FSO','policy','The organization defines the information system auditable events.','AU-2.2','DoD has defined the information system auditable events as successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g. classification levels). Successful and unsuccessful logon attempts, Privileged activities or other system level access, Starting and ending time for user access to the system, Concurrent logons from different workstations, Successful and unsuccessful accesses to objects, All program initiations, All direct access to the information system. All account creations, modifications, disabling, and terminations. All kernel module load, unload, and restart.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system auditable events as successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g. classification levels). Successful and unsuccessful logon attempts, Privileged activities or other system level access, Starting and ending time for user access to the system, Concurrent logons from different workstations, Successful and unsuccessful accesses to objects, All program initiations, All direct access to the information system. All account creations, modifications, disabling, and terminations. All kernel module load, unload, and restart.'),
('001572','draft','2010-05-11','DISA FSO','policy','The organization defines the personnel or roles to be alerted in the event of an audit processing failure.','AU-5.2','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the SCA and ISSO, who shall be alerted in the event of audit processing failure. If there are no additional personnel or roles, the organization must also document that. DoD has defined the personnel or roles as at a minimum, the SCA and ISSO.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles who should be alerted in the event of audit processing failure to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles. DoD has defined the personnel or roles as at a minimum, the SCA and ISSO.'),
('001573','draft','2010-05-11','DISA FSO','policy','The organization defines whether to reject or delay network traffic that exceeds organization-defined thresholds.','AU-5(3).2','DoD has defined the action to take as delay.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the action to take as delay.'),
('001574','draft','2010-05-11','DISA FSO','technical','The information system rejects or delays, as defined by the organization, network traffic which exceed the organization-defined thresholds.','AU-5(3).3','The organization being inspected/assessed configures the information system to delay network communications traffic exceeding the thresholds defined in AU-5 (3), CCI 1859. DoD has defined the action to take as delay. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1574.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to delay network communications traffic exceeding the thresholds defined in AU-5 (3), CCI 1859. DoD has defined the action to take as delay. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1574.'),
('001575','draft','2010-05-11','DISA FSO','policy','The organization defines the system or system component for storing audit records that is a different system or system component than the system or component being audited.','AU-9(2).3','The organization being inspected/assessed defines and documents a system or storage media that will be used to store information system audit data different and separate from the system or media generating the audit data.','The organization conducting the inspection/assessment obtains and examines the information system or media documentation addressing the storage of backups of information system audit records; information system audit records; and any other relevant documents or records. The purpose of the reviews is to ensure the organization has defined and documented a system or storage media different from the system or media being audited.'),
('001576','deprecated','2010-05-11','DISA FSO','technical','The information system produces a system-wide (logical or physical) audit trail of information system audit records.',NULL,NULL,NULL),
('001577','draft','2010-05-11','DISA FSO','policy','The organization defines the information system components from which audit records are to be compiled into the system-wide audit trail.','AU-12(1).3','The organization being inspected/assessed will define and document the information system components from which audit records are to be compiled into the system-wide audit trail. The organization will periodically update this list to ensure it is current. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the system-wide audit trail documentation to ensure the organization being inspected/assessed maintains a current list of information system components. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('001578','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency to review and update the current security assessment and authorization procedures.','CA-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001579','draft','2010-05-11','DISA FSO','policy','The organization conducts security control assessments using organization-defined forms of testing in accordance with organization-defined frequency and assessment techniques.',NULL,NULL,NULL),
('001580','draft','2010-05-11','DISA FSO','policy','The organization identifies connections to external information systems (i.e., information systems outside of the authorization boundary).',NULL,NULL,NULL),
('001581','draft','2010-05-11','DISA FSO','policy','The organization defines personnel or roles to whom the security status of the organization and the information system should be reported.','CA-7.11','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('001582','draft','2010-05-11','DISA FSO','policy','The organization defines other forms of security assessments other than in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment; and performance/load testing that should be included as part of security control assessments.','CA-2(2).2','The organization being inspected/assessed defines and documents other forms of security assessments other than in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment and performance/load testing that should be included as part of security control assessments. DoD has determined the other forms of security assessments are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented other forms of security assessments to ensure the organization being inspected/assessed defines other forms of security assessments other than in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment and performance/load testing that should be included as part of security control assessments. DoD has determined the other forms of security assessments are not appropriate to define at the Enterprise level.'),
('001583','draft','2010-05-11','DISA FSO','policy','The organization selects announced or unannounced assessments for each form of security control assessment.','CA-2(2).3','The organization being inspected/assessed selects and documents whether announced or unannounced assessments are required for each form of security control assessment that was selected as part of CA-2 (2), CCI 2064. DoD has determined the announced or unannounced nature of the assessments is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list of security control assessment techniques defined in CA-2 (2), CCI 2064 and verifies that the security assessment plan defines whether the assessment is announced or unannounced.'),
('001584','draft','2010-05-11','DISA FSO','policy','The organization defines the frequency with which to review and update configuration management procedures.','CM-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001585','draft','2010-05-12','DISA FSO','policy','The organization defines the circumstances that require reviews and updates to the baseline configuration of the information system.','CM-2(1).4','DoD has defined the circumstances as baseline configuration changes or as events dictate such as changes due to USCYBERCOM tactical orders/ directives or cyber attacks.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the circumstances as baseline configuration changes or as events dictate such as changes due to USCYBERCOM tactical orders/ directives or cyber attacks.'),
('001586','draft','2010-05-12','DISA FSO','policy','The organization defines the configuration change control element (e.g., committee, board) responsible for coordinating and providing oversight for configuration change control activities.','CM-3.12','DoD has defined the configuration change control element as a configuration control board (CCB).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the configuration change control element as a configuration control board (CCB).'),
('001587','draft','2010-05-12','DISA FSO','policy','The organization, when analyzing new software in a separate test environment, looks for security impacts due to flaws, weaknesses, incompatibility, or intentional malice.',NULL,NULL,NULL),
('001588','draft','2010-05-12','DISA FSO','policy','The organization-defined security configuration checklists reflect the most restrictive mode consistent with operational requirements.','CM-6.4','DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) meet the DoD requirement for ensuring security configuration checklists reflect the most restrictive mode consistent with operational requirements.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.).','DoD security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.) meet the DoD requirement for ensuring security configuration checklists reflect the most restrictive mode consistent with operational requirements.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level security configuration or implementation guidance (e.g. STIGs, SRGs, NSA configuration guides, CTOs, DTMs etc.).'),
('001589','draft','2010-05-12','DISA FSO','technical','The organization incorporates detection of unauthorized, security-relevant configuration changes into the organization’s incident response capability to ensure they are tracked.',NULL,NULL,NULL),
('001590','deprecated','2010-05-12','DISA FSO','policy','The organization develops a list of software programs authorized to execute on the information system.',NULL,NULL,NULL),
('001591','deprecated','2010-05-12','DISA FSO','policy','The organization develops a list of software programs not authorized to execute on the information system.',NULL,NULL,NULL),
('001592','draft','2010-05-12','DISA FSO','policy','The organization defines the rules authorizing the terms and conditions of software program usage on the information system.','CM-7(2).1','The organization being inspected/assessed defines and documents their rules for approval of software program usage. For network capable software programs, the organization being inspected/assessed complies with DoDI 8551. DoD has determined that the rules authorizing the terms and conditions of software program usage on the information system are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the rules as well as the software list to ensure that all network capable software programs are DoDI 8551 compliant and that the rules authorizing the use of all other programs are defined. DoD has determined that the rules authorizing the terms and conditions of software program usage on the information system are not appropriate to define at the Enterprise level'),
('001593','deprecated','2010-05-12','DISA FSO','policy','The organization maintains a list of software programs authorized to execute on the information system.',NULL,NULL,NULL),
('001594','deprecated','2010-05-12','DISA FSO','policy','The organization maintains a list of software programs not authorized to execute on the information system.',NULL,NULL,NULL),
('001595','draft','2010-05-12','DISA FSO','policy','The organization maintains rules authorizing the terms and conditions of software program usage on the information system.',NULL,NULL,NULL),
('001596','draft','2010-05-12','DISA FSO','policy','The organization defines the frequency with which to review and update the current contingency planning procedures.','CP-1.9','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001597','draft','2010-05-12','DISA FSO','policy','The organization disseminates contingency planning procedures to organization-defined personnel or roles.','CP-1.5','DoD disseminates DoDI 8500.01 organization-wide via the DoD Issuances website. http://www.dtic.mil/whs/directives/corres/dir.html NIST disseminates NIST SP 800-34 via http://csrc.nist.gov/publications/PubsSPs.html','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.'),
('001598','draft','2010-05-12','DISA FSO','policy','The organization reviews and updates the current contingency planning procedures in accordance with the organization-defined frequency.','CP-1.10','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.','DoDI 8500.01 and NIST SP 800-34 meet the DoD requirements for contingency planning policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and NIST SP 800-34.'),
('001599','draft','2010-05-12','DISA FSO','policy','The organization sustains operational continuity of essential missions until full information system restoration at primary processing and/or storage sites.','CP-2(5).3','The organization being inspected/assessed develops and documents procedures within the contingency plan to sustain operational continuity of essential missions until full information system restoration at primary processing and/or storage sites.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it documents procedures to sustain operational continuity of essential missions until full information system restoration at primary processing and/or storage sites.'),
('001600','draft','2010-05-12','DISA FSO','policy','The organization sustains operational continuity of essential business functions until full information system restoration at primary processing and/or storage sites.','CP-2(5).4','The organization being inspected/assessed develops and documents procedures within the contingency plan to sustain operational continuity of essential business functions until full information system restoration at primary processing and/or storage sites.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure it documents procedures to sustain operational continuity of essential business functions until full information system restoration at primary processing and/or storage sites.'),
('001601','draft','2010-05-12','DISA FSO','policy','The organization sustains operational continuity of essential missions at alternate processing and/or storage sites until information system restoration at primary processing and/or storage sites.','CP-2(6).3','The organization being inspected/assessed documents within their continuity plan a process for continuation of essential missions at alternate processing and/or storage sites until information system restoration at primary processing and/or storage sites.','The organization conducting the inspection/assessment obtains and examines the continuity plan to ensure the organization being inspected/assessed documents a process for continuation of essential missions at alternate processing and/or storage sites until information system restoration at primary processing and/or storage sites.'),
('001602','draft','2010-05-12','DISA FSO','policy','The organization sustains operational continuity of essential business functions at alternate processing and/or storage sites until information system restoration at primary processing and/or storage sites.','CP-2(6).4','The organization being inspected/assessed documents within their continuity plan a process for continuation of essential business functions at alternate processing and/or storage sites until information system restoration at primary processing and/or storage sites.','The organization conducting the inspection/assessment obtains and examines the continuity plan to ensure the organization being inspected/assessed documents a process for continuation of essential business functions at alternate processing and/or storage sites until information system restoration at primary processing and/or storage sites.'),
('001603','draft','2010-05-12','DISA FSO','policy','The contingency plan identifies the primary storage site hazards.',NULL,NULL,NULL),
('001604','draft','2010-05-12','DISA FSO','policy','The organization outlines explicit mitigation actions for organization identified accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster.','CP-6(3).2','The organization being inspected/assessed must identify and document in the contingency plan explicit mitigation actions for accessibility problems identified in CP-6 (3), CCI 509 to the alternate storage site in the event of an area-wide disruption or disaster.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure the organization has documented explicit mitigation actions for accessibility problems identified in CP-6 (3), CCI 509 to the alternate storage site in the event of an area-wide disruption or disaster.'),
('001605','draft','2010-05-12','DISA FSO','policy','The contingency plan identifies the primary processing site hazards.',NULL,NULL,NULL),
('001606','draft','2010-05-12','DISA FSO','policy','The organization outlines explicit mitigation actions for organization-identified potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster.','CP-7(2).2','The organization being inspected/assessed must identify and document in the contingency plan explicit mitigation actions for accessibility problems identified in CP-7 (2), CCI 517 to the alternate processing site in the event of an area-wide disruption or disaster.','The organization conducting the inspection/assessment obtains and examines the contingency plan to ensure the organization has documented explicit mitigation actions for accessibility problems identified in CP-7 (2), CCI 517 to the alternate processing site in the event of an area-wide disruption or disaster.'),
('001607','draft','2010-05-12','DISA FSO','policy','The organization establishes alternate telecommunications services to support the information system.',NULL,NULL,NULL),
('001608','draft','2010-05-12','DISA FSO','policy','The organization identifies the primary provider\'s telecommunications service hazards.',NULL,NULL,NULL),
('001609','draft','2010-05-12','DISA FSO','policy','The organization can activate the redundant secondary information system that is not collocated with the primary system without loss of information or disruption to operations.','CP-9(6).2','The organization being inspected/assessed establishes a service level agreement which will provide for redundant secondary system support that is not co-located with the primary system, and has configured the system so that it can be activated to accomplish system backups without a loss of information or operational disruption.','The organization conducting the inspection/assessment determines if the organization has established a service level agreement for a redundant secondary system support that is not co-located with the primary system, and has configured the system so it can be activated to accomplish system backups without a loss of information or operational disruption.'),
('001610','draft','2010-05-12','DISA FSO','policy','The organization defines the time period (by authenticator type) for changing/refreshing authenticators.','IA-5.17','DoD has defined the time period as CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as CAC - every 3 years, or 1 year from term of contract Password: 60 days Biometrics: every 3 years.'),
('001611','draft','2010-05-12','DISA FSO','policy','The organization defines the minimum number of special characters for password complexity enforcement.','IA-5(1).5','DoD has defined the minimum number of special characters for password complexity enforcement as one special character.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the minimum number of special characters for password complexity enforcement as one special character.'),
('001612','draft','2010-05-12','DISA FSO','policy','The organization defines the minimum number of upper case characters for password complexity enforcement.','IA-5(1).6','DoD has defined the minimum number of upper case characters for password complexity enforcement as one upper-case character.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the minimum number of upper case characters for password complexity enforcement as one upper-case character.'),
('001613','draft','2010-05-12','DISA FSO','policy','The organization defines the minimum number of lower case characters for password complexity enforcement.','IA-5(1).7','DoD has defined the minimum number of lower case characters for password complexity enforcement as one lower-case character.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the minimum number of lower case characters for password complexity enforcement as one lower-case character.'),
('001614','draft','2010-05-12','DISA FSO','policy','The organization defines the minimum number of numeric characters for password complexity enforcement.','IA-5(1).8','DoD has defined the minimum number of numeric characters for password complexity enforcement as one numeric character.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the minimum number of numeric characters for password complexity enforcement as one numeric character.'),
('001615','draft','2010-05-12','DISA FSO','policy','The organization defines the minimum number of characters that are changed when new passwords are created.','IA-5(1).11','DoD has defined the minimum number of characters as 50% of the minimum password length.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\nDoD has defined the minimum number of characters as 50% of the minimum password length.'),
('001616','draft','2010-05-12','DISA FSO','policy','The organization defines minimum password lifetime restrictions.','IA-5(1).16','DoD has defined the minimum password lifetime restrictions as 24 hours.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the minimum password lifetime restrictions as 24 hours.'),
('001617','draft','2010-05-12','DISA FSO','policy','The organization defines maximum password lifetime restrictions.','IA-5(1).17','DoD has defined the maximum password lifetime restrictions as 60 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the maximum password lifetime restrictions as 60 days.'),
('001618','draft','2010-05-12','DISA FSO','policy','The organization defines the number of generations for which password reuse is prohibited.','IA-5(1).19','DoD has defined the number of generations as a minimum of 5.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the number of generations as a minimum of 5.'),
('001619','draft','2010-05-12','DISA FSO','technical','The information system enforces password complexity by the minimum number of special characters used.','IA-5(1).9','The organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of special characters used. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1619.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce password complexity by the minimum number of special characters used. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1619.'),
('001620','draft','2010-05-12','DISA FSO','policy','The organization defines the types of and/or specific authenticators for which the registration process must be carried out in person before a designated registration authority with authorization by a designated organizational official (e.g., a supervisor).',NULL,NULL,NULL),
('001621','draft','2010-05-12','DISA FSO','policy','The organization implements organization-defined security safeguards to manage the risk of compromise due to individuals having accounts on multiple information systems.','IA-5(8).2','The organization being inspected/assessed documents and implements policies and user training including advising users not to use the same password for any of the following: Domains of differing classification levels. More than one domain of a classification level (e.g., internal agency network and Intelink). More than one privilege level (e.g., user, administrator).','The organization conducting the inspection/assessment obtains and examines the documented policies as well as training records to ensure that the organization being inspected/assessed implements policies and training advising users not to use the same password for any of the following: Domains of differing classification levels. More than one domain of a classification level (e.g., internal agency network and Intelink). More than one privilege level (e.g., user, administrator).'),
('001622','draft','2010-05-12','DISA FSO','policy','The organization identifies personnel with incident response roles and responsibilities with respect to the information system.',NULL,NULL,NULL),
('001623','draft','2010-05-12','DISA FSO','policy','The incident response training material addresses the procedures and activities necessary to fulfill identified organizational incident response roles and responsibilities.',NULL,NULL,NULL),
('001624','draft','2010-05-12','DISA FSO','policy','The organization documents the results of incident response tests.','IR-3.4','The organization being inspected/assessed will document the results of incident response tests.','The organization conducting the inspection/assessment obtains and examines:\n1. the organization\'s incident response plan to identify organization\'s testing schedule and,\n2. results of previous incident response tests to ensure the organization is documenting the results IAW their incident response plan.'),
('001625','draft','2010-05-12','DISA FSO','policy','The organization implements the resulting incident handling activity changes to incident response procedures, training, and testing/exercises accordingly.','IR-4.4','The organization being inspected/assessed will follow the latest incident response plan (IR-8) that has been revised (based on IR-4, CCI-000824) and disseminated. ','The organization conducting the inspection/assessment obtains and examines recent changes to the incident response plan (based on IR-4, CCI 000824) to verify that they have been disseminated and reviews the most recent after action report to ensure that changes have been followed. '),
('001626','draft','2010-05-12','DISA FSO','policy','The organization employs automated mechanisms to assist in the collection of security incident information.','IR-5(1).2','The organization being inspected/assessed will document within their incident handling plan, procedures to leverage the Joint Incident Management System (JIMS). For the DoD, JIMS is the automated mechanism. ','The organization conducting the inspection/assessment obtains and examines the incident handling plan to ensure that there are procedures identified to leverage the JIMS.'),
('001627','draft','2010-05-12','DISA FSO','policy','The organization employs automated mechanisms to assist in the analysis of security incident information.','IR-5(1).3','The organization being inspected/assessed will document within their incident handling plan, procedures to leverage the Joint Incident Management System (JIMS). For the DoD, JIMS is the automated mechanism. ','The organization conducting the inspection/assessment obtains and examines the incident handling plan to ensure that there are procedures identified to leverage the JIMS. '),
('001628','draft','2010-05-12','DISA FSO','policy','The organization defines a frequency with which to review and update the current system maintenance procedures.','MA-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('001629','draft','2010-05-12','DISA FSO','policy','The organization employs automated mechanisms to produce up-to-date, accurate, complete, and available records of all maintenance and repair actions needed, in process, and complete.',NULL,NULL,NULL),
('001630','draft','2010-05-12','DISA FSO','policy','Designated organizational personnel review the maintenance records of the non-local maintenance and diagnostic sessions.',NULL,NULL,NULL),
('001631','draft','2010-05-12','DISA FSO','policy','The organization, before removal from organizational facilities, and after the service is performed, inspects and sanitizes the component (with regard to potentially malicious software) before reconnecting the component to the information system.','MA-4(3).3','The organization being inspected/assessed sanitizes and inspects serviced components prior to reusing them on any information system. Alternatively, the organization being inspected/assessed complies with MA-4 (3) CCI 882.','The organization conducting the inspection/assessment obtains and examines maintenance procedures for all non-local maintenance and diagnostic services to ensure that the organization being inspected/assessed sanitizes and inspects serviced components prior to reusing them on any information system. Alternatively, the organization conducting the inspection/assessment ensures the organization being inspected/assessed complies with MA-4 (3) CCI 882.'),
('001632','draft','2010-05-12','DISA FSO','technical','The organization protects nonlocal maintenance sessions by separating the maintenance session from other network sessions with the information system by either physically separated communications paths or logically separated communications paths based upon encryption.','MA-4(4).3','The organization being inspected/assessed configures the information system to protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the information system by either physically separated communications paths or logically separated communications paths based upon encryption. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1632.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the information system by either physically separated communications paths or logically separated communications paths based upon encryption. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1632.'),
('001633','draft','2010-05-12','DISA FSO','policy','The organization defines removable media types and information output requiring marking.',NULL,NULL,NULL),
('001634','draft','2010-05-12','DISA FSO','policy','The organization identifies authorized personnel with appropriate clearances and access authorizations for gaining physical access to the facility containing an information system that processes classified information.',NULL,NULL,NULL),
('001635','draft','2010-05-12','DISA FSO','policy','The organization removes individuals from the facility access list when access is no longer required.','PE-2.7','The organization being inspected/assessed will remove personnel from the authorized access list who no longer have approved access and revoke their credentials, as identified in actions per PE-2, CCI 914. The organization must document each removal and revocation action as an audit trail.','The organization conducting the inspection/assessment obtains and examines the review and approval actions documentation to ensure that personnel no longer requiring access have been removed from the authorized access list and their credentials have been revoked.'),
('001636','draft','2010-05-12','DISA FSO','policy','The organization defines the frequency with which to review and update the current security planning policy.','PL-1.6','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('001637','draft','2010-05-12','DISA FSO','policy','The organization reviews and updates the current security planning policy in accordance with organization-defined frequency.','PL-1.7','DoDI 8510.01 meets the requirements for a security planning policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the frequency as every 5 years.','DoDI 8510.01 meets the requirements for a security planning policy.\n\nDoD Components are automatically compliant with this CCI because they are covered by DoD level policy, DoDI 8510.01.\n\nDoD has defined the frequency as every 5 years.'),
('001638','draft','2010-05-12','DISA FSO','policy','The organization defines the frequency with which to review and update the current security planning procedures.','PL-1.10','DoD has defined the frequency as reviewed annually - updated as appropriate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate.'),
('001639','draft','2010-05-12','DISA FSO','policy','The organization makes readily available to individuals requiring access to the information system the rules that describe their responsibilities and expected behavior with regard to information and information system usage.','PL-4.2','The organization being inspected/assessed must disseminate to all information system users, via an information sharing capability, rules that describe information system user responsibilities and expected behavior with regard to information and information system usage, acceptable use policy (AUP). Organizations should disseminate the rules by providing to users and requiring signature of acceptance.','The organization conducting the inspection/assessment obtains and examines rules that describe information system user responsibilities via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated.'),
('001640','draft','2010-05-12','DISA FSO','policy','The organization updates the critical infrastructure and key resources protection plan that addresses information security issues.','PM-8.2','DoDD 3020.40 meets the DoD requirement for the development of a critical infrastructure and key resource protection plan.\n\nDoD components are automatically compliant with this CCI as they are covered by the DoD level, DoDD 3020.40.','DoDD 3020.40 meets the DoD requirement for the development of a critical infrastructure and key resource protection plan.\n\nDoD components are automatically compliant with this CCI as they are covered by the DoD level, DoDD 3020.40.'),
('001641','draft','2010-05-12','DISA FSO','policy','The organization defines the process for conducting random vulnerability scans on the information system and hosted applications.','RA-5.4','DoD has defined the requirement for vulnerability scanning periodicity of every 30 days. If the organization being inspected/assessed has determined a requirement for random scanning they must document that process. DoD has defined the frequency as every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization conducting the inspection/assessment obtains and examines random vulnerability process documentation (if applicable) to validate the organization has clearly defined and documented a process for conducting random vulnerability scans on the information system and hosted applications. If the organization being inspected/assessed has determined they have no requirement for random scanning, there is no requirement for a process.'),
('001642','draft','2010-05-12','DISA FSO','policy','The organization defines the organizational document in which risk assessment results are documented (e.g., security plan, risk assessment report).','RA-3.3','DoD has defined the document as a risk assessment report.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the document as a risk assessment report.'),
('001643','draft','2010-05-12','DISA FSO','policy','The organization scans for vulnerabilities in the information system and hosted applications in accordance with the organization-defined process for random scans.','RA-5.5','The organization being inspected/assessed will conduct random vulnerability scans every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).\n\nThe organization will document the vulnerability scans as an audit trail for future reference. The audit trail must be maintained IAW DoD, CYBERCOM, or component policies.\n\nDoD has defined the frequency as every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).\n.','The organization conducting the inspection/assessment obtains and examines\nthe vulnerability scanning results every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs) to verify compliance with the organization being inspected/assessed random vulnerability scanning process.\n\nDoD has defined the frequency as every 30 days or as directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).'),
('001644','draft','2010-05-12','DISA FSO','policy','The organization employs vulnerability scanning procedures that can demonstrate the depth of coverage (i.e., vulnerabilities checked).',NULL,NULL,NULL),
('001645','draft','2010-05-12','DISA FSO','policy','The organization identifies the information system components to which privileged access is authorized for selected organization-defined vulnerability scanning activities.','RA-5(5).2','DoD has defined the information system components as all information systems and infrastructure components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as all information systems and infrastructure components.'),
('001646','draft','2010-05-12','DISA FSO','policy','The organization defines the frequency with which to review and update the current system and services acquisition procedures.','SA-1.10','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.');
INSERT INTO `cci` VALUES ('001647','draft','2010-05-12','DISA FSO','policy','The organization requires the use of a FIPS-validated, cryptographic module for a technology product that relies on cryptographic functionality to enforce its security policy when no U.S. Government Protection Profile exists for such a specific technology type.',NULL,NULL,NULL),
('001648','draft','2010-05-12','DISA FSO','policy','The organization makes available to authorized personnel the source code for the information system to permit analysis and testing.',NULL,NULL,NULL),
('001649','draft','2010-05-12','DISA FSO','policy','The organization identifies and documents (as appropriate) explicit rules to be enforced when governing the installation of software by users.',NULL,NULL,NULL),
('001650','draft','2010-05-12','DISA FSO','policy','The organization requires the information system developers to manage and control changes to the information system during development.',NULL,NULL,NULL),
('001651','draft','2010-05-12','DISA FSO','policy','The organization requires the information system integrators to manage and control changes to the information system during development.',NULL,NULL,NULL),
('001652','draft','2010-05-12','DISA FSO','policy','The organization requires the information system developers to manage and control changes to the information system during implementation.',NULL,NULL,NULL),
('001653','draft','2010-05-12','DISA FSO','policy','The organization requires the information system integrators to manage and control changes to the information system during implementation.',NULL,NULL,NULL),
('001654','draft','2010-05-12','DISA FSO','policy','The organization requires the information system developers to manage and control changes to the information system during modification.',NULL,NULL,NULL),
('001655','draft','2010-05-12','DISA FSO','policy','The organization requires the information system integrators to manage and control changes to the information system during modification.',NULL,NULL,NULL),
('001656','draft','2010-05-12','DISA FSO','policy','The organization defines the security functions of the information system to be isolated from nonsecurity functions.',NULL,NULL,NULL),
('001657','draft','2010-05-12','DISA FSO','policy','The organization defines the external boundary of the information system.',NULL,NULL,NULL),
('001658','draft','2010-05-12','DISA FSO','policy','The organization defines key internal boundaries of the information system.',NULL,NULL,NULL),
('001659','draft','2010-05-12','DISA FSO','policy','The organization defines the mediation necessary for public access to the organization\'s internal networks.',NULL,NULL,NULL),
('001660','draft','2010-05-12','DISA FSO','policy','The organization defines the measures to protect against unauthorized physical connections across boundary protections implemented at organization-defined managed interfaces.',NULL,NULL,NULL),
('001661','draft','2010-05-12','DISA FSO','policy','The organization defines the security functions, to minimally include information system authentication and re-authentication, within the information system to be included in a trusted communications path.','SC-11.2','DoD has defined the security functions as providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security functions as providers of authentication, reauthentication, and all privileged commands (administration, monitoring, and controlling).'),
('001662','draft','2010-05-12','DISA FSO','technical','The information system takes organization-defined corrective action when organization-defined unacceptable mobile code is identified.','SC-18(1).2','The organization being inspected/assessed configures the information system to take corrective actions defined in SC-18 (1), CCI 2457 when unacceptable mobile code defined in SC-18 (1), CCI 2458 is identified. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1662.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to take corrective actions defined in SC-18 (1), CCI 2457 when unacceptable mobile code defined in SC-18 (1), CCI 2458 is identified. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1662.'),
('001663','draft','2010-05-12','DISA FSO','technical','The information system, when operating as part of a distributed, hierarchical namespace, provides the means to enable verification of a chain of trust among parent and child domains (if the child supports secure resolution services).','SC-20.4','The organization being inspected/assessed installs and utilizes software capable of validating the chain of trust (Examples of software include dig, dnsviz, dnssec-debugger, dnssec validator for Mozilla, etc.). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1663.','The organization conducting the inspection/assessment utilizes DNSSEC diagnostic tools, such as dig, and performs queries which will exercise the data flow path for authoritative name resolution services where parent and child domains exist. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that pertains to CCI 1663.'),
('001664','draft','2010-05-12','DISA FSO','technical','The information system recognizes only session identifiers that are system-generated.','SC-23(3).3','The organization being inspected/assessed configures the information system to recognize only session identifiers that are system-generated. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1664.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to recognize only session identifiers that are system-generated. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1664.'),
('001665','draft','2010-05-12','DISA FSO','technical','The information system preserves organization-defined system state information in the event of a system failure.','SC-24.5','The organization being inspected/assessed configures the information system to preserve information necessary to determine cause of failure and to return to operations with least disruption to mission/ business processes in the event of a system failure. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1665. DoD has defined system state information as information necessary to determine cause of failure and to return to operations with least disruption to mission/ business processes.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to preserve information necessary to determine cause of failure and to return to operations with least disruption to mission/ business processes in the event of a system failure. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1665. DoD has defined system state information as information necessary to determine cause of failure and to return to operations with least disruption to mission/ business processes.'),
('001666','draft','2010-05-12','DISA FSO','policy','The organization employs cryptographic mechanisms to prevent unauthorized modification of information at rest unless otherwise protected by alternative physical measures.',NULL,NULL,NULL),
('001667','draft','2010-05-12','DISA FSO','policy','The organization compares the time measured between flaw identification and flaw remediation with organization-defined benchmarks.',NULL,NULL,NULL),
('001668','draft','2010-05-12','DISA FSO','technical','The organization employs malicious code protection mechanisms at workstations, servers, or mobile computing devices on the network to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means or inserted through the exploitation of information system vulnerabilities.',NULL,NULL,NULL),
('001669','draft','2010-05-12','DISA FSO','policy','The organization defines the frequency of testing malicious code protection mechanisms.','SI-3(6).2','DoD has defined the frequency as twice annually or when substantial changes are made to the malicious code protection mechanisms.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as twice annually or when substantial changes are made to the malicious code protection mechanisms.'),
('001670','draft','2010-05-12','DISA FSO','technical','The information system takes organization-defined least-disruptive actions to terminate suspicious events.','SI-4(7).4','The organization being inspected/assessed configures the information system to take least-disruptive actions defined in SI-4 (7), CCI 1268 to terminate suspicious events. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1670.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to take least-disruptive actions defined in SI-4 (7), CCI 1268 to terminate suspicious events. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1670.'),
('001671','draft','2010-05-12','DISA FSO','policy','The organization analyzes outbound communications traffic at selected organization-defined interior points within the system (e.g., subnetworks, subsystems) to discover anomalies.','SI-4(11).2','The organization being inspected/assessed documents and implements a process to analyze outbound communications traffic at selected interior points defined in SI-4 (11), CCI 2668 within the system (e.g., subnetworks, subsystems) to discover anomalies. The organization must maintain a record of any discovered anomalies.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of any discovered anomalies to ensure the organization being inspected/assessed analyzes outbound communications traffic at selected interior points defined in SI-4 (11), CCI 2668 within the system (e.g., subnetworks, subsystems) to discover anomalies.'),
('001672','draft','2010-05-12','DISA FSO','technical','The organization employs a wireless intrusion detection system to identify rogue wireless devices.',NULL,NULL,NULL),
('001673','draft','2010-05-12','DISA FSO','policy','The organization employs a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system.','SI-4(14).1','The organization being inspected/assessed documents and implements a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified wireless intrusion detection system and the system hardware/software list to ensure the organization being inspected/assessed employs a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises/breaches to the information system. The organization being inspected/assessed may be required to demonstrate use of the wireless intrusion detection system.'),
('001674','draft','2010-05-12','DISA FSO','technical','The information system responds to security function anomalies in accordance with organization-defined responses and alternative action(s).',NULL,NULL,NULL),
('001675','draft','2010-05-12','DISA FSO','policy','The organization defines the personnel or roles that are to receive reports on the results of security function verification.','SI-6(3).2','DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('001676','draft','2010-05-12','DISA FSO','policy','The organization defines, for periodic security function verification, the frequency of the verifications.',NULL,NULL,NULL),
('001677','draft','2010-05-12','DISA FSO','technical','The organization employs spam protection mechanisms at workstations, servers, or mobile computing devices on the network to detect and take action on unsolicited messages transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means.',NULL,NULL,NULL),
('001678','draft','2010-05-12','DISA FSO','policy','The organization retains information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','SI-12.2','The organization being inspected/assessed identifies and documents federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements which apply to the information within the information system. The organization documents and implements a process to retain information IAW those documented federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','The organization conducting the inspection/assessment obtains and examines the documented list of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements which apply to the information within the information system, as well as the documented process for information retention to ensure the organization being inspected/assessed retains information within the information system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.'),
('001679','draft','2010-05-12','DISA FSO','policy','The organization provides a mechanism to exchange active and standby roles of the components.',NULL,NULL,NULL),
('001680','draft','2010-06-09','DISA FSO','policy','The organization develops an organization-wide information security program plan that includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PM-1.4','DoDI 8500.01 and the Knowledge Service meet the requirement for this CCI; individual organizations and system owners must provide documentation of common control implementation in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('001681','deprecated','2011-04-26','DISA FSO','policy','The organization defines the frequency at which each form of security control assessment should be conducted.',NULL,NULL,NULL),
('001682','draft','2011-05-03','DISA FSO','technical','The information system automatically removes or disables emergency accounts after an organization-defined time period for each type of account.','AC-2(2).4','The organization being inspected/assessed configures the information system to never automatically remove or disable emergency accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1682. DoD has defined the time period as never. ','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to never automatically remove or disable emergency accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1682. DoD has defined the time period as never.'),
('001683','draft','2011-05-03','DISA FSO','technical','The information system notifies organization-defined personnel or roles for account creation actions.','AC-2(4).5','The organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account creation actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1683. DoD has defined the personnel or roles as the system administrator and ISSO.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account creation actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1683. DoD has defined the personnel or roles as the system administrator and ISSO.'),
('001684','draft','2011-05-03','DISA FSO','technical','The information system notifies organization-defined personnel or roles for account modification actions.','AC-2(4).6','The organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account modification actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1684. DoD has defined the personnel or roles as the system administrator and ISSO.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account modification actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1684. DoD has defined the personnel or roles as the system administrator and ISSO.'),
('001685','draft','2011-05-03','DISA FSO','technical','The information system notifies organization-defined personnel or roles for account disabling actions.','AC-2(4).7','The organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account disabling actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1685. DoD has defined the personnel or roles as the system administrator and ISSO.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account disabling actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1685. DoD has defined the personnel or roles as the system administrator and ISSO.'),
('001686','draft','2011-05-03','DISA FSO','technical','The information system notifies organization-defined personnel or roles for account removal actions.','AC-2(4).8','The organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account removal actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1686. DoD has defined the personnel or roles as the system administrator and ISSO.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account removal actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1686. DoD has defined the personnel or roles as the system administrator and ISSO.'),
('001687','draft','2011-05-03','DISA FSO','policy','The organization ensures the use of mobile code to be deployed in information systems meets organization-defined mobile code requirements.','SC-18(2).3','The organization being inspected/assessed documents and implements a process to use mobile code IAW the requirements defined in CCI 1168.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed uses mobile code IAW the requirements defined in CCI 1168.'),
('001688','draft','2011-05-03','DISA FSO','policy','The organization ensures the acquisition of mobile code to be deployed in information systems meets organization-defined mobile code requirements.','SC-18(2).4','The organization being inspected/assessed documents and implements a process to acquire mobile code IAW the requirements defined in CCI 1168.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed acquire mobile code IAW the requirements defined in CCI 1168.'),
('001689','draft','2011-05-27','DISA FSO','policy','The organization, if an information system component failure is detected, automatically shuts down the information system.',NULL,NULL,NULL),
('001690','draft','2011-10-07','DISA FSO','policy','The organization protects, as required, vendor/manufacturer documentation that describes the security-relevant external interfaces to the information system.',NULL,NULL,NULL),
('001691','draft','2011-10-07','DISA FSO','policy','The organization makes available to authorized personnel vendor/manufacturer documentation that describes the security-relevant external interfaces to the information system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('001692','draft','2011-10-07','DISA FSO','policy','The organization makes available to authorized personnel vendor/manufacturer documentation that describes the low-level design of the information system in terms of modules and implementation details of the security controls employed within the system with sufficient detail to permit analysis and testing.',NULL,NULL,NULL),
('001693','draft','2011-10-07','DISA FSO','technical','The information system enforces a Discretionary Access Control (DAC) policy that limits propagation of access rights.',NULL,NULL,NULL),
('001694','draft','2011-10-07','DISA FSO','technical','The information system enforces a Discretionary Access Control (DAC) policy that includes or excludes access to the granularity of a single user.',NULL,NULL,NULL),
('001695','draft','2011-10-07','DISA FSO','technical','The information system prevents the execution of organization-defined unacceptable mobile code.','SC-18(3).2','The organization being inspected/assessed configures the information system to prevent the execution of unacceptable mobile code defined in CCI 2459.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1695.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent the execution of unacceptable mobile code defined in CCI 2459.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1695.'),
('001726','draft','2013-02-28','DISA FSO','policy','The organization uses software in accordance with contract agreements.','CM-10.1','The organization being inspected/assessed uses software in accordance with contract agreements.','The organization conducting the inspection/assessment obtains and examines a sampling of contract agreements and supporting evidence concerning the usage of software to ensure compliance with the contract agreements.'),
('001727','draft','2013-02-28','DISA FSO','policy','The organization uses software documentation in accordance with contract agreements.','CM-10.2','The organization being inspected/assessed uses software documentation in accordance with contract agreements.','The organization conducting the inspection/assessment obtains and examines a sampling of contract agreements associated with software documentation and supporting evidence concerning the usage of software documentation to ensure compliance with contract agreements.'),
('001728','draft','2013-02-28','DISA FSO','policy','The organization uses software in accordance with copyright laws.','CM-10.3','The organization being inspected/assessed uses software in accordance with copyright laws.','The organization conducting the inspection/assessment obtains and examines supporting evidence concerning the usage of software to ensure compliance with copyright laws.'),
('001729','draft','2013-02-28','DISA FSO','policy','The organization uses software documentation in accordance with copyright laws.','CM-10.4','The organization being inspected/assessed uses software documentation in accordance with copyright laws.','The organization conducting the inspection/assessment obtains and examines supporting evidence concerning the usage of software documentation to ensure compliance with copyright laws.'),
('001730','draft','2013-02-28','DISA FSO','policy','The organization tracks the use of software protected by quantity licenses to control copying of the software.','CM-10.5','The organization being inspected/assessed tracks the use of software protected by quantity licenses to control copying of the software. Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs.','The organization conducting the inspection/assessment obtains and examines the tracking records to ensure the organization being inspected/assessed tracks the use of software protected by quantity licenses to control copying of the software.'),
('001731','draft','2013-02-28','DISA FSO','policy','The organization tracks the use of software documentation protected by quantity licenses to control distribution of the software documentation.','CM-10.6','The organization being inspected/assessed tracks the use of software documentation protected by quantity licenses to control distribution of the software documentation. Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs.','The organization conducting the inspection/assessment obtains and examines the tracking records to ensure the organization being inspected/assessed tracks the use of software documentation protected by quantity licenses to control distribution of the software documentation.'),
('001732','draft','2013-02-28','DISA FSO','policy','The organization controls the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.','CM-10.9','The organization being inspected/assessed reviews and authorizes in order to control the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. The organization must maintain an audit trail of peer-to-peer file sharing technology reviews and authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of peer-to-peer file sharing technology reviews and authorizations to ensure the organization being inspected/assessed controls the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.'),
('001733','draft','2013-02-28','DISA FSO','policy','The organization documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.','CM-10.10','The organization being inspected/assessed documents the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.','The organization conducting the inspection/assessment obtains and examines the documentation for the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.'),
('001734','draft','2013-02-28','DISA FSO','policy','The organization defines the restrictions to be followed on the use of open source software.','CM-10(1).1','DoD has defined the restrictions as IAW DoD Memorandum \"Clarifying Guidance Regarding Open Source Software (OSS)\" 16 Oct 2009 (http://dodcio.defense.gov/Home/Issuances/DoDCIOMemorandums.aspx).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the restrictions as IAW DoD Memorandum \"Clarifying Guidance Regarding Open Source Software (OSS)\" 16 Oct 2009 (http://dodcio.defense.gov/Home/Issuances/DoDCIOMemorandums.aspx).'),
('001735','draft','2013-02-28','DISA FSO','policy','The organization establishes organization-defined restrictions on the use of open source software.','CM-10(1).2','DoD Memorandum \"Clarifying Guidance Regarding Open Source Software (OSS)\" 16 Oct 2009 (http://dodcio.defense.gov/Home/Issuances/DoDCIOMemorandums.aspx) meets the DoD requirement for establishing restrictions on the use of open source software.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD Memorandum \"Clarifying Guidance Regarding Open Source Software (OSS).\"','DoD Memorandum \"Clarifying Guidance Regarding Open Source Software (OSS)\" 16 Oct 2009 (http://dodcio.defense.gov/Home/Issuances/DoDCIOMemorandums.aspx) meets the DoD requirement for establishing restrictions on the use of open source software.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoD Memorandum \"Clarifying Guidance Regarding Open Source Software (OSS).\"'),
('001736','draft','2013-02-28','DISA FSO','policy','The organization defines the previous versions of the baseline configuration of the information system required to support rollback.','CM-2(3).2','DoD has defined the previous versions as the previous approved baseline configuration of IS components for a minimum of 3 month.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the previous versions as the previous approved baseline configuration of IS components for a minimum of 3 month.'),
('001737','draft','2013-02-28','DISA FSO','policy','The organization defines the information systems, system components, or devices that are to have organization-defined configurations applied when located in areas of significant risk.','CM-2(7).1','The organization being inspected/assessed defines and documents, in the configuration management policy, the information systems, system components, or devices that are to have configurations defined in CM-2 (7), CCI 1738 applied when located in areas of significant risk. DoD has determined that this value is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines the information systems, system components, or devices that are to have configurations defined in CM-2 (7), CCI 1738 applied when located in areas of significant risk. DoD has determined that this value is not appropriate to define at the Enterprise level.'),
('001738','draft','2013-02-28','DISA FSO','policy','The organization defines the security configurations to be implemented on information systems, system components, or devices when they are located in areas of significant risk.','CM-2(7).2','The organization being inspected/assessed defines and documents, in the configuration management policy, the security configurations to be implemented on information systems, system components, or devices when they are located in areas of significant risk. DoD has determined that this value is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines the security configurations to be implemented on information systems, system components, or devices when they are located in areas of significant risk. DoD has determined that this value is not appropriate to define at the Enterprise level.'),
('001739','draft','2013-02-28','DISA FSO','policy','The organization issues organization-defined information systems, system components, or devices with organization-defined configurations to individuals traveling to locations the organization deems to be of significant risk.','CM-2(7).3','The organization being inspected/assessed issues information systems, system components, or devices as defined in CM-2 (7) CCI 1737 with configurations as defined in CM-2 (7) CCI 1738 to individuals traveling to locations the organization deems to be of significant risk.','The organization conducting the inspection/assessment interviews organizational personnel with configuration management responsibilities to ensure that individuals traveling to locations that the organization deems to be of significant risk are issued information systems, system components, or devices as defined in CM-2 (7) CCI 1737 with configurations as defined in CM-2 (7) CCI 1738.'),
('001740','draft','2013-02-28','DISA FSO','policy','The organization reviews proposed configuration-controlled changes to the information system.','CM-3.3','The organization being inspected/assessed conducts reviews of records documenting the proposed configuration controlled changes to each information system. The organization will maintain an audit trail of each proposed configuration controlled change. This action will be implemented by the CCB as defined in CM-3, CCI 1586.','The organization conducting the inspection/assessment obtains and examines the audit trail of a sampling of proposed configuration controlled changes to ensure the reviews are being conducted.'),
('001741','draft','2013-02-28','DISA FSO','policy','The organization documents configuration change decisions associated with the information system.','CM-3.4','The organization being inspected/assessed documents configuration change decisions associated with the information system. The organization must maintain an audit trail of configuration change decisions. This action will be implemented by the CCB as defined in CM-3, CCI 1586.','The organization conducting the inspection/assessment obtains and examines the audit trail documenting configuration change decisions associated with the information system to ensure the organization being inspected/assessed has documented their decisions.'),
('001742','draft','2013-02-28','DISA FSO','policy','The organization defines the approval authorities to be notified when proposed changes to the information system are received.','CM-3(1).3','DoD has defined the approval authorities as the configuration control board (CCB).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the approval authorities as the configuration control board (CCB).'),
('001743','draft','2013-02-28','DISA FSO','policy','The organization defines the security responses to be automatically implemented by the information system if baseline configurations are changed in an unauthorized manner.','CM-3(5).1','The organization being inspected/assessed defines and documents, in the configuration management policy, the security responses to be automatically implemented by the information system if baseline configurations are changed in an unauthorized manner. DoD has determined that the value is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines the security responses to be automatically implemented by the information system if baseline configurations are changed in an unauthorized manner. DoD has determined that the value is not appropriate to define at the Enterprise level.'),
('001744','draft','2013-02-28','DISA FSO','technical','The information system implements organization-defined security responses automatically if baseline configurations are changed in an unauthorized manner.','CM-3(5).2','The organization being inspected/assessed implements security responses, as defined in CM-3 (5), CCI 1743, automatically if baseline configurations are changed in an unauthorized manner. The information system must maintain an audit trail of automatic security responses to unauthorized changes in baseline configurations.','The organization conducting the inspection/assessment obtains and examines the audit trail to ensure the organization being inspected/assessed implements security responses, as defined in CM-3 (5), CCI 1743, automatically if baseline configurations are changed in an unauthorized manner.'),
('001745','draft','2013-02-28','DISA FSO','policy','The organization defines the security safeguards that are to be provided by the cryptographic mechanisms which are employed by the organization.','CM-3(6).1','DoD has defined the security safeguards as all security safeguards.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security safeguards as all security safeguards.'),
('001746','draft','2013-02-28','DISA FSO','policy','The organization ensures that cryptographic mechanisms used to provide organization-defined security safeguards are under configuration management.','CM-3(6).2','The organization being inspected/assessed ensures that cryptographic mechanisms used to provide all security safeguards are under configuration management. DoD has defined the security safeguards as all security safeguards.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure that cryptographic mechanisms used to provide all security safeguards are documented in the policy. DoD has defined the security safeguards as all security safeguards.'),
('001747','draft','2013-02-28','DISA FSO','policy','The organization defines critical software components the information system will prevent from being installed without verification the component has been digitally signed using a certificate that is recognized and approved by the organization.','CM-5(3).1','DoD has defined the software components as any software components when the vendor provides digitally signed products.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the software components as any software components when the vendor provides digitally signed products.'),
('001748','draft','2013-02-28','DISA FSO','policy','The organization defines critical firmware components the information system will prevent from being installed without verification the component has been digitally signed using a certificate that is recognized and approved by the organization.','CM-5(3).2','DoD has defined the critical firmware components as any firmware components when the vendor provides digitally signed products.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the critical firmware components as any firmware components when the vendor provides digitally signed products.'),
('001749','draft','2013-02-28','DISA FSO','technical','The information system prevents the installation of organization-defined software components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.','CM-5(3).3','The organization being inspected/assessed documents and implements a process to prevent the installation of software onto any software components when the vendor provides digitally signed products without verification that software has been digitally signed using a certificate and approved by the organization.\n\nDoD has defined the software components as any software components when the vendor provides digitally signed products.','The organization conducting the inspection/assessment obtains and examines the documented process for preventing the installation of software onto any software components when the vendor provides digitally signed products without verification that software has been digitally signed using a certificate and approved by the organization.\n\nThe organization conducting the inspection/assessment reviews software on a sampling of the defined components to ensure that only software digitally signed by a defined CA is installed.\n\nDoD has defined the software components as any software components when the vendor provides digitally signed products.'),
('001750','draft','2013-02-28','DISA FSO','technical','The information system prevents the installation of organization-defined firmware components without verification the firmware component has been digitally signed using a certificate that is recognized and approved by the organization.','CM-5(3).4','The organization being inspected/assessed documents and implements a process to prevent the installation of firmware onto any firmware components when the vendor provides digitally signed products without verification that firmware has been digitally signed using a certificate and approved by the organization.\n\nDoD has defined the critical firmware components as any firmware components when the vendor provides digitally signed products.','The organization conducting the inspection/assessment obtains and examines the documented process for preventing the installation of firmware onto any firmware components when the vendor provides digitally signed products without verification that firmware has been digitally signed using a certificate and approved by the organization.\n\nThe organization conducting the inspection/assessment reviews firmware on a sampling of the defined components to ensure that only firmware digitally signed by a defined CA is installed.'),
('001751','draft','2013-02-28','DISA FSO','policy','The organization defines system-level information requiring enforcement of a dual authorization for information system changes.','CM-5(4).3','The organization being inspected/assessed defines and documents system-level information requiring enforcement of a dual authorization for information system changes.\n\nDoD has determined to the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented system-level information to ensure the organization being inspected/assessed defines the system-level information requiring enforcement of a dual authorization for information system changes.\n\nDoD has determined to the information is not appropriate to define at the Enterprise level.'),
('001752','draft','2013-02-28','DISA FSO','policy','The organization enforces dual authorization for changes to organization-defined system-level information.','CM-5(4).4','The organization being inspected/assessed documents and implements a process to enforce dual authorization for changes to system-level information defined in CM-5 (4), CCI 1751.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed enforces dual authorization for changes to system-level information defined in CM-5 (4), CCI 1751.'),
('001753','draft','2013-02-28','DISA FSO','policy','The organization limits privileges to change information system components within a production or operational environment.','CM-5(5).1','The organization being inspected/assessed documents and implements a process to limit privileges to change information system components within a production or operational environment.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed limits privileges to change information system components within a production or operational environment.'),
('001754','draft','2013-02-28','DISA FSO','policy','The organization limits privileges to change system-related information within a production or operational environment.','CM-5(5).2','The organization being inspected/assessed documents and implements a process to limit privileges to change system-related information within a production or operational environment.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed limits privileges to change system-related information within a production or operational environment.'),
('001755','draft','2013-02-28','DISA FSO','policy','The organization defines the information system components for which any deviation from the established configuration settings are to be identified, documented, and approved.','CM-6.9','DoD has defined the information system components as all configurable information system components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the information system components as all configurable information system components.'),
('001756','draft','2013-02-28','DISA FSO','policy','The organization defines the operational requirements on which the configuration settings for the organization-defined information system components are to be based.','CM-6.10','The organization being inspected/assessed must define and document in the system security plan, the requirements which may deviate from the approved configuration settings on the information system components defined in CM-6, CCI 1755. DoD has determined that it is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the system security plan to ensure the organization being inspected/assessed defines the requirements which may deviate from the approved configuration settings on the information system components defined in CM-6, CCI 1755. DoD has determined that it is not appropriate to define at the Enterprise level.'),
('001757','draft','2013-02-28','DISA FSO','policy','The organization defines the security safeguards the organization is to employ when responding to unauthorized changes to the organization-defined configuration settings.','CM-6(2).1','The organization being inspected/assessed must define and document in the configuration management policy, the security safeguards the organization is to employ when responding to unauthorized changes to the configuration settings defined in CM-6 (2), CCI 1758. DoD has determined that it is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines the security safeguards the organization is to employ when responding to unauthorized changes to the configuration settings defined in CM-6 (2), CCI 1758. DoD has determined that it is not appropriate to define at the Enterprise level.'),
('001758','draft','2013-02-28','DISA FSO','policy','The organization defines configuration settings for which the organization will employ organization-defined security safeguards in response to unauthorized changes.','CM-6(2).2','The organization being inspected/assessed must define and document in the configuration management policy, the configuration settings for which the organization will employ security safeguards defined in CM-6 (2), CCI 1757 in response to unauthorized changes. DoD has defined the configuration settings as security related configuration settings defined at the program/system level.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines the configuration settings for which the organization will employ security safeguards CM-6 (2), CCI 1757 in response to unauthorized changes. DoD has defined the configuration settings as security related configuration settings defined at the program/system level. '),
('001759','draft','2013-02-28','DISA FSO','policy','The organization employs organization-defined security safeguards to respond to unauthorized changes to organization-defined configuration settings.','CM-6(2).3','The organization being inspected/assessed documents and implements security safeguards defined in CM-6 (2), CCI 1757 to respond to unauthorized changes to security related configuration settings defined at the program/system level. The organization must maintain an audit trail of security safeguard implementation. DoD has defined the configuration settings as security related configuration settings defined at the program/system level. ','The organization conducting the inspection/assessment obtains and examines the documented process and the audit trail of security safeguard implementation to ensure the organization being inspected/assessed implements security safeguards defined in CM-6 (2), CCI 1757 to respond to unauthorized changes to security related configuration settings defined at the program/system level. DoD has defined the configuration settings as security related configuration settings defined at the program/system level. '),
('001760','draft','2013-02-28','DISA FSO','policy','The organization defines the frequency of information system reviews to identify unnecessary and/or nonsecure functions, ports, protocols, and services.','CM-7(1).2','DoD has defined the frequency as every 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 30 days.'),
('001761','draft','2013-02-28','DISA FSO','policy','The organization defines the functions, ports, protocols, and services within the information system that are to be disabled when deemed unnecessary and/or nonsecure.','CM-7(1).3','The organization being inspected/assessed must define and document in the system security plan, the functions, ports, protocols and services within the information system that are to be disabled when deemed unnecessary. DoD has determined that it is not appropriate to define unnecessary functions, ports, protocols and service at the Enterprise level. Nonsecure functions, ports, protocols and services are defined in DoDI 8551.01.','The organization conducting the inspection/assessment obtains and examines the system security plan to ensure the organization being inspected/assessed defines the functions, ports, protocols and services within the information system that are to be disabled when deemed unnecessary. DoD has determined that it is not appropriate to define unnecessary functions, ports, protocols and service at the Enterprise level. Nonsecure functions, ports, protocols and services are defined in DoDI 8551.01.'),
('001762','draft','2013-02-28','DISA FSO','technical','The organization disables organization-defined functions, ports, protocols, and services within the information system deemed to be unnecessary and/or nonsecure.','CM-7(1).4','The organization being inspected/assessed must disable functions, ports, protocols, and services within the information system deemed to be unnecessary and/or nonsecure as defined in CM-7 (1), CCI 1761.','The organization conducting the inspection/assessment inspects the information system to ensure the organization being inspected/assessed disables functions, ports, protocols, and services within the information system deemed to be unnecessary and/or nonsecure as defined in CM-7 (1), CCI 1761.'),
('001763','draft','2013-02-28','DISA FSO','policy','The organization defines the policies regarding software program usage and restrictions.','CM-7(2).2','The organization being inspected/assessed defines and documents their rules for approval of software program usage. For network capable software programs, the organization being inspected/assessed complies with DoDI 8551. DoD has determined that the rules authorizing the terms and conditions of software program usage on the information system are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the rules as well as the software list to ensure that all network capable software programs are DoDI 8551 compliant and that the rules authorizing the use of all other programs are defined. DoD has determined that the rules authorizing the terms and conditions of software program usage on the information system are not appropriate to define at the Enterprise level.'),
('001764','draft','2013-02-28','DISA FSO','technical','The information system prevents program execution in accordance with organization-defined policies regarding software program usage and restrictions, and/or rules authorizing the terms and conditions of software program usage.','CM-7(2).3','The organization being inspected/assessed configures the information system to prevent the execution of programs not authorized in accordance with CM-7 (2) CCIs 1592 and 1763.','The organization conducting the inspection/assessment examines the information systems to ensure the systems are configured to prevent the execution of programs not authorized in accordance with CM-7 (2) CCIs 1592 and 1763.'),
('001765','draft','2013-02-28','DISA FSO','policy','The organization defines the software programs not authorized to execute on the information system.','CM-7(4).1','The organization being inspected/assessed must define and document software programs not authorized to execute on the information system. For network capable software, the organization-defined list must include all software programs as defined IAW DoDI 8551.01. DoD has determined that a comprehensive list of unauthorized software programs is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list of software programs not authorized to execute to ensure that list is defined. The organization conducting the inspection/assessment reviews the list to ensure that any network capable software is included IAW DoDI 8551.01. DoD has determined that a comprehensive list of unauthorized software programs is not appropriate to define at the Enterprise level.'),
('001766','draft','2013-02-28','DISA FSO','policy','The organization identifies the organization-defined software programs not authorized to execute on the information system.','CM-7(4).2','The organization being inspected/assessed must define and document software programs not authorized to execute on the information system. For network capable software, the organization-defined list must include all software programs as defined IAW DoDI 8551.01.','The organization conducting the inspection/assessment obtains and examines the documented list of software programs not authorized to execute to ensure that list is defined. The organization conducting the inspection/assessment reviews the list to ensure that any network capable software is included IAW DoDI 8551.01.'),
('001767','draft','2013-02-28','DISA FSO','technical','The organization employs an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the information system.','CM-7(4).3','Within the DoD, this control cannot be implemented.','Within the DoD, this control cannot be implemented.'),
('001768','draft','2013-02-28','DISA FSO','policy','The organization defines the frequency on which it will review and update the list of unauthorized software programs.','CM-7(4).4','DoD has defined the frequency as monthly.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as monthly.'),
('001769','deprecated','2013-02-28','DISA FSO','policy','The organization defines the frequency on which it will update the list of unauthorized software programs.',NULL,NULL,NULL),
('001770','draft','2013-02-28','DISA FSO','policy','The organization reviews and updates the list of unauthorized software programs per organization-defined frequency.','CM-7(4).5','The organization being inspected/assessed documents and implements a process to review and update the list of unauthorized software programs monthly. The organization must maintain an audit trail of the review and update activity. DoD has defined the frequency as monthly.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reviews and updates to ensure that the organization being inspected/assessed reviews and updates the list of unauthorized software programs monthly. DoD has defined the frequency as monthly.'),
('001771','deprecated','2013-02-28','DISA FSO','policy','The organization updates the list of unauthorized software programs per organization-defined frequency.',NULL,NULL,NULL),
('001772','draft','2013-02-28','DISA FSO','policy','The organization defines the software programs authorized to execute on the information system.','CM-7(5).1','The organization being inspected/assessed must define and document software programs that are authorized to execute on the information system.\n\nDoD has determined that a comprehensive list of unauthorized software programs is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list of software programs that are authorized to execute to ensure that list is defined.\n\nDoD has determined that a comprehensive list of unauthorized software programs is not appropriate to define at the Enterprise level.'),
('001773','draft','2013-02-28','DISA FSO','policy','The organization identifies the organization-defined software programs authorized to execute on the information system.','CM-7(5).2','The organization being inspected/assessed must define and document software programs that are authorized to execute on the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of software programs that are authorized to execute to ensure that list is defined.'),
('001774','draft','2013-02-28','DISA FSO','technical','The organization employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system.','CM-7(5).3','The organization being inspected/assessed configures the information system to deny-all and only permit by exception the execution of authorized software programs on the information system.','The organization conducting the inspection/assessment examines the information system to ensure that it is configured to deny-all and only permit by exception the execution of authorized software programs on the information system.'),
('001775','draft','2013-02-28','DISA FSO','policy','The organization defines the frequency on which it will review and update the list of authorized software programs.','CM-7(5).4','DoD has defined the frequency as monthly.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as monthly.'),
('001776','deprecated','2013-02-28','DISA FSO','policy','The organization defines the frequency on which it will update the list of authorized software programs.',NULL,NULL,NULL),
('001777','draft','2013-02-28','DISA FSO','policy','The organization reviews and updates the list of authorized software programs per organization-defined frequency.','CM-7(5).5','The organization being inspected/assessed documents and implements a process to review and update the list of authorized software programs monthly. The organization must maintain an audit trail of the review and update activity. DoD has defined the frequency as monthly.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reviews and updates to ensure that the organization being inspected/assessed reviews and updates the list of authorized software programs monthly. DoD has defined the frequency as monthly.'),
('001778','deprecated','2013-02-28','DISA FSO','policy','The organization updates the list of authorized software programs per organization-defined frequency.',NULL,NULL,NULL),
('001779','draft','2013-02-28','DISA FSO','policy','The organization defines the frequency on which the information system component inventory is to be reviewed and updated.','CM-8.6','DoD has defined the frequency as at a minimum, annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as at a minimum, annually.'),
('001780','draft','2013-02-28','DISA FSO','policy','The organization reviews and updates the information system component inventory per organization-defined frequency.','CM-8.7','The organization being inspected/assessed documents and implements a process to review and update the information system component inventory at a minimum, annually.\n\nThe organization must maintain an audit trail of review and update activity.\n\nDoD has defined the frequency as at a minimum, annually.','The organization conducting the inspection/assessment obtains and examines the documented process for reviews and updates as well as the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates the information system component inventory at a minimum, annually.\n\nDoD has defined the frequency as at a minimum, annually.'),
('001781','deprecated','2013-03-01','DISA FSO','policy','The organization defines the frequency on which the information system component inventory is to be updated.',NULL,NULL,NULL),
('001782','deprecated','2013-03-01','DISA FSO','policy','The organization updates the information system component inventory per organization-defined frequency.',NULL,NULL,NULL),
('001783','draft','2013-03-01','DISA FSO','policy','The organization defines the personnel or roles to be notified when unauthorized hardware, software, and firmware components are detected within the information system.','CM-8(3).3','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the ISSO or ISSM, to be notified when unauthorized hardware, software, and firmware components are detected within the information system. If there are no additional personnel or roles, the organization must also document that. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles to be notified when unauthorized hardware, software, and firmware components are detected within the information system to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001784','draft','2013-03-01','DISA FSO','policy','When unauthorized hardware, software, and firmware components are detected within the information system, the organization takes action to disable network access by such components, isolates the components, and/or notifies organization-defined personnel or roles.','CM-8(3).4','The organization being inspected/assessed documents and implements a process to take action to disable network access by unauthorized software, hardware, and firmware components, isolate the components, and/or notify the ISSO and ISSM and others as the local organization deems appropriate. The organization must maintain an audit trail of actions taken upon detection of unauthorized software, hardware, and firmware components. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the documented process and audit trail for taking action upon detection of unauthorized components to ensure the organization being inspected/assessed takes action to disable network access by unauthorized software, hardware, and firmware components, isolate the components, and/or notify the ISSO and ISSM and others as the local organization deems appropriate. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001785','draft','2013-03-01','DISA FSO','policy','The organization provides a centralized repository for the inventory of information system components.','CM-8(7).1','The organization being inspected/assessed documents and implements a centralized repository for the inventory of information system components.','The organization conducting the inspection/assessment obtains and examines the documentation of a centralized repository to ensure the organization being inspected/assessed provides a centralized repository for the inventory of information system components.'),
('001786','draft','2013-03-01','DISA FSO','policy','The organization employs automated mechanisms to support tracking of information system components by geographic location.','CM-8(8).1','The organization being inspected/assessed documents and implements automated mechanisms to support tracking of information system components by geographic location.','The organization conducting the inspection/assessment obtains and examines the documentation of the automated mechanisms to ensure the organization being inspected/assessed employs automated mechanisms to support tracking of information system components by geographic location.'),
('001787','draft','2013-03-01','DISA FSO','policy','The organization defines the acquired information system components that are to be assigned to an information system.','CM-8(9).1','The organization being inspected/assessed defines and documents the acquired information system components that are to be assigned to an information system.\n\nAt no lower than the AO level, the organization must define and document the criteria for or types of information system components where assignment must be tracked. For example, all information system components that collect, store, or process information and are not themselves simply a storage media.\n\nDoD has determined that the acquired information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documentation of acquired information system components to ensure the organization being inspected/assessed defines the acquired information system components that are to be assigned to an information system. DoD has determined that the acquired information system components are not appropriate to define at the Enterprise level.'),
('001788','draft','2013-03-01','DISA FSO','policy','The organization assigns organization-defined acquired information system components to an information system.','CM-8(9).2','The organization being inspected/assessed assigns and documents the assignment of acquired information system components, as defined in CM-8 (9), CCI 1787, to an information system.','The organization conducting the inspection/assessment obtains and examines the documentation pertaining to the acquisition of information system components to ensure the organization being inspected/assessed assigns acquired information system components, as defined in CM-8 (9), CCI 1787, to an information system.'),
('001789','draft','2013-03-01','DISA FSO','policy','The organization receives an acknowledgement from the information system owner of the assignment of the acquired information system components to an information system.','CM-8(9).3','The organization being inspected/assessed documents and implements a process to ensure the organization receives an acknowledgement from the information system owner of the assignment of the acquired information system components to an information system. The organization must maintain an audit trail of the acknowledgements.','The organization conducting the inspection/assessment obtains and examines the documented process and audit trail of acknowledgements to ensure the organization being inspected/assessed receives an acknowledgement from the information system owner of the assignment of the acquired information system components to an information system.'),
('001790','draft','2013-03-01','DISA FSO','policy','The organization develops a configuration management plan for the information system that establishes a process for identifying configuration items throughout the system development life cycle.','CM-9.3','The organization being inspected/assessed will develop and document a configuration management plan for the information system that establishes a process for identifying configuration items throughout the system development life cycle.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to verify it establishes and documents a process for identifying configuration items throughout the system development life cycle.'),
('001791','draft','2013-03-01','DISA FSO','policy','The organization documents a configuration management plan for the information system that establishes a process for identifying configuration items throughout the system development life cycle.',NULL,NULL,NULL),
('001792','draft','2013-03-01','DISA FSO','policy','The organization implements a configuration management plan for the information system that establishes a process for identifying configuration items throughout the system development life cycle.','CM-9.4','The organization being inspected/assessed will implement a configuration management plan for the information system that establishes a process for identifying configuration items throughout the system development life cycle.','The organization conducting the inspection/assessment obtains and examines the configuration management plan as well as evidence of implementation (e.g., completed change requests, meeting minutes, and other relevant documents) to ensure the organization being inspected/assessed implements a configuration management plan for the information system that establishes a process for identifying configuration items throughout the system development life cycle. Checks should include verification that items being processed for CM are the items identified and that identified configuration items have not been changed without going through the documented process.'),
('001793','draft','2013-03-01','DISA FSO','policy','The organization develops a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.','CM-9.5','The organization being inspected/assessed will develop and document a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to ensure it establishes and documents a process for managing the configuration of the configuration items.'),
('001794','draft','2013-03-01','DISA FSO','policy','The organization documents a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.',NULL,NULL,NULL),
('001795','draft','2013-03-01','DISA FSO','policy','The organization implements a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.','CM-9.6','The organization being inspected/assessed will implement a configuration management plan that has a process for controlling changes to configuration items.','The organization conducting the inspection/assessment obtains and examines the configuration management plan as well as evidence of implementation (e.g., completed change requests, meeting minutes, and other relevant documents) to ensure the organization being inspected/assessed implements a configuration management plan for the information system that establishes a process for managing the configuration of the configuration items.'),
('001796','draft','2013-03-01','DISA FSO','policy','The organization develops a configuration management plan for the information system that places the configuration items under configuration management.','CM-9.9','The organization being inspected/assessed will develop and document a configuration management plan for the information system that places the configuration items under configuration management.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to ensure the organization being inspected/assessed documents that configuration items are placed under configuration management.'),
('001797','draft','2013-03-01','DISA FSO','policy','The organization documents a configuration management plan for the information system that places the configuration items under configuration management.',NULL,NULL,NULL),
('001798','draft','2013-03-01','DISA FSO','policy','The organization implements a configuration management plan for the information system that places the configuration items under configuration management.','CM-9.10','The organization being inspected/assessed will implement a configuration management plan for the information system that places the configuration items under configuration management.','The organization conducting the inspection/assessment obtains and examines the configuration management plan as well as evidence of implementation (e.g., completed change requests, meeting minutes, and other relevant documents) to ensure the organization being inspected/assessed implements a configuration management plan for the information system and that configuration items identified are under configuration management.'),
('001799','draft','2013-03-01','DISA FSO','policy','The organization develops and documents a configuration management plan for the information system that protects the configuration management plan from unauthorized disclosure and modification.','CM-9.11','The organization being inspected/assessed must develop and document a plan to protect the configuration management plan from unauthorized disclosure and modification. Measures must include marking, labeling, and handling to prevent improper disclosure. The organization being inspected/assessed must ensure that all changes to the CM plan are approved.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to verify that it identifies the protection measures.'),
('001800','deprecated','2013-03-01','DISA FSO','policy','The organization documents a configuration management plan for the information system that protects the configuration management plan from unauthorized disclosure and modification.',NULL,NULL,NULL),
('001801','draft','2013-03-01','DISA FSO','policy','The organization implements a configuration management plan for the information system that protects the configuration management plan from unauthorized disclosure and modification.','CM-9.12','The organization being inspected/assessed must implement a plan to protect the configuration management plan from unauthorized disclosure and modification. Measures must include marking, labeling, and handling to prevent improper disclosure. The organization being inspected/assessed must ensure that all changes to the CM plan are approved.','The organization conducting the inspection/assessment obtains and examines the configuration management plan to verify that the identified protection measures are implemented.'),
('001802','draft','2013-03-01','DISA FSO','policy','The organization tracks the use of software documentation protected by quantity licenses to control copying of the software documentation.','CM-10.7','The organization being inspected/assessed tracks the use of software documentation protected by quantity licenses to control copying of the software documentation. Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs.','The organization conducting the inspection/assessment obtains and examines the tracking records to ensure the organization being inspected/assessed tracks the use of software documentation protected by quantity licenses to control copying of the software documentation.'),
('001803','draft','2013-03-01','DISA FSO','policy','The organization tracks the use of software protected by quantity licenses to control distribution of the software.','CM-10.8','The organization being inspected/assessed tracks the use of software protected by quantity licenses to control distribution of the software. Software license tracking can be accomplished by manual methods (e.g., simple spreadsheets) or automated methods (e.g., specialized tracking applications) depending on organizational needs.','The organization conducting the inspection/assessment obtains and examines the tracking records to ensure the organization being inspected/assessed tracks the use of software protected by quantity licenses to control distribution of the software.'),
('001804','draft','2013-03-01','DISA FSO','policy','The organization defines the policies for governing the installation of software by users.','CM-11.1','The organization being inspected/assessed must define policies governing the installation of software by users. DoD has determined the policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines policies governing the installation of software by users (e.g., user agreements, CM plan, etc.) to ensure the organization being inspected/assessed defines the policies for governing the installation of software by users. DoD has determined the policies are not appropriate to define at the Enterprise level.'),
('001805','draft','2013-03-01','DISA FSO','policy','The organization establishes organization-defined policies governing the installation of software by users.','CM-11.2','The organization being inspected/assessed documents their policies governing the installation of software by users (e.g., user agreements, CM plan, etc.).','The organization conducting the inspection/assessment obtains and examines documented policies governing the installation of software by users (e.g., user agreements, CM plan, etc.) to ensure the organization being inspected/assessed establishes policies governing the installation of software by users.'),
('001806','draft','2013-03-01','DISA FSO','policy','The organization defines methods to be employed to enforce the software installation policies.','CM-11.3','The organization being inspected/assessed must define and document the methods employed to enforce the software installation policies. DoD has determined the policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines documentation of the methods employed to ensure the organization being inspected/assessed defines methods to be employed to enforce the software installation policies. DoD has determined the policies are not appropriate to define at the Enterprise level.'),
('001807','draft','2013-03-01','DISA FSO','policy','The organization enforces software installation policies through organization-defined methods.','CM-11.4','The organization being inspected/assessed must enforce software installation policies as defined in CM-11, CCI 1804 through methods defined in CM-11, CCI 1806.','The organization conducting the inspection/assessment obtains and examines software installation policies defined in CM-11, CCI 1804 and inspects the methods defined in CM-11, CCI 1806 to verify they are properly implemented.'),
('001808','draft','2013-03-01','DISA FSO','policy','The organization defines the frequency on which it will monitor software installation policy compliance.','CM-11.5','DoD has defined the frequency as at least monthly.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least monthly.'),
('001809','draft','2013-03-01','DISA FSO','policy','The organization monitors software installation policy compliance per an organization-defined frequency.','CM-11.6','The organization being inspected/assessed must monitor software installation policy compliance at least monthly. The organization must maintain audit trails of monitoring activity. DoD has defined the frequency as at least monthly.','The organization conducting the inspection/assessment obtains and examines the audit trails of monitoring activities to ensure the organization being inspected/assessed monitors software installation policy compliance at least monthly. DoD has defined the frequency as at least monthly.'),
('001810','draft','2013-03-01','DISA FSO','policy','The organization defines the personnel or roles to be notified when unauthorized software is detected.','CM-11(1).1','The organization being inspected/assessed must define and document the personnel or roles to be notified when unauthorized software is detected. DoD has defined the personnel or roles that must be notified when unauthorized software is detected as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the documentation of the personnel or roles to be notified when unauthorized software is detected to ensure that ISSO and ISSM and others as the local organization deems appropriate are defined. DoD has defined the personnel or roles that must be notified when unauthorized software is detected as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001811','draft','2013-03-01','DISA FSO','technical','The information system alerts organization-defined personnel or roles when the unauthorized installation of software is detected.','CM-11(1).2','The organization being inspected/assessed must configure the information system to alert ISSO and ISSM and others as the local organization deems appropriate when the unauthorized installation of software is detected. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1811. DoD has defined the personnel or roles that must be notified when unauthorized software is detected as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the configuration of the automated mechanism or evidence that alerts are occurring when unauthorized software is installed to ensure the information system alerts the ISSO and ISSM and others as the local organization deems appropriate when the unauthorized installation of software is detected.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1811.\n\nDoD has defined the personnel or roles that must be notified when unauthorized software is detected as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001812','draft','2013-03-01','DISA FSO','technical','The information system prohibits user installation of software without explicit privileged status.','CM-11(2).1','The organization being inspected/assessed must configure the information system to prevent the installation of software by non-privileged users. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1812.','The organization conducting the inspection/assessment obtains and examines the configuration of the information system components to ensure that installation of software without explicit privileged status is prohibited. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1812.'),
('001813','draft','2013-03-01','DISA FSO','technical','The information system enforces access restrictions.','CM-5(1).1','The organization being inspected/assessed documents and implements a process to enforce access restrictions provided by the information system.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the configuration of the information system to ensure access restrictions are implemented.'),
('001814','draft','2013-03-01','DISA FSO','technical','The Information system supports auditing of the enforcement actions.','CM-5(1).2','The organization being inspected/assessed leverages only information systems which support auditing of enforcement actions.','The organization conducting the inspection/assessment reviews vendor documentation to ensure the information system supports auditing of the enforcement actions. If vendor documentation is not available, the organization conducting the inspection/assessment tests the information system for the capability.'),
('001815','draft','2013-03-01','DISA FSO','policy','The organization defines the security safeguards to be applied to devices when they return from areas of significant risk.','CM-2(7).4','The organization being inspected/assessed defines and documents, in the configuration management policy, the security safeguards to be applied to devices when they return from areas of significant risk. DoD has determined that this value is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the configuration management policy to ensure the organization being inspected/assessed defines the security safeguards to be applied to devices when they return from areas of significant risk. DoD has determined that this value is not appropriate to define at the Enterprise level.'),
('001816','draft','2013-03-01','DISA FSO','policy','The organization applies organization-defined security safeguards to devices when individuals return from areas of significant risk.','CM-2(7).5','The organization being inspected/assessed applies security safeguards as defined in CM-2 (7) CCI 1815 to devices when individuals return from areas of significant risk.','The organization conducting the inspection/assessment interviews organizational personnel with configuration management responsibilities to ensure that when individuals return from areas of significant risk, security safeguards as defined in CM-2 (7) CCI 1815 are applied to devices as defined in CM-2 (7) CCI 1737.'),
('001817','draft','2013-03-01','DISA FSO','policy','The organization, when analyzing changes to the information system, looks for security impacts due to flaws, weaknesses, incompatibility, or intentional malice.','CM-4(1).1','The organization being inspected/assessed documents within their process for analyzing changes to the information system, methods for identifying security impacts due to flaws, weaknesses, incompatibility, or intentional malice. The organization implements the documented process and must maintain a record of analysis.','The organization conducting the inspection/assessment obtains and examines the documented process and record of analysis to ensure the organization being inspected/assessed, when analyzing changes to the information system, looks for security impacts due to flaws, weaknesses, incompatibility, or intentional malice.'),
('001818','draft','2013-03-01','DISA FSO','policy','The organization analyzes changes to the information system in a separate test environment before installation in an operational environment.','CM-4(1).2','The organization being inspected/assessed documents and employs a policy to analyze changes to the information system in a separate test environment before installation in an operational environment, looking for security impacts due to flaws, weaknesses, incompatibility, or intentional malice. The organization must maintain records of analysis of changes to the information system.','The organization conducting the inspection/assessment obtains and examines the documented policy for analyzing changes as well as records of analysis to ensure the organization being inspected/assessed analyzes changes to the information system in a separate test environment before installation in an operational environment, looking for security impacts due to flaws, weaknesses, incompatibility, or intentional malice.'),
('001819','draft','2013-03-01','DISA FSO','policy','The organization implements approved configuration-controlled changes to the information system.','CM-3.5','The organization being inspected/assessed implements approved configuration-controlled changes to the information system. The organization must maintain an audit trail of the implementation of approved configuration-controlled changes.','The organization conducting the inspection/assessment obtains and examines the audit trail documenting the implementation of approved configuration-controlled changes to the information system to ensure the organization being inspected/assessed has implemented the approved changes.'),
('001820','deprecated','2013-03-01','DISA FSO','policy','The organization documents a configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.',NULL,NULL,NULL),
('001821','draft','2013-03-01','DISA FSO','policy','The organization defines the organizational personnel or roles to whom the configuration management policy is to be disseminated.','CM-1.1',' DoD has defined the organizational personnel or roles as all stakeholders in the configuration management process.',' The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the organizational personnel or roles as all stakeholders in the configuration management process.'),
('001822','draft','2013-03-01','DISA FSO','policy','The organization disseminates the configuration management policy to organization-defined personnel or roles.','CM-1.4','The organization being inspected/assessed disseminates a configuration management policy via an information sharing capability (e.g. portal, intranet, email, etc.) to all stakeholders in the configuration management process.\n\nDoD has defined the organizational personnel or roles as all stakeholders in the configuration management process.','The organization conducting the inspection/assessment obtains and examines the configuration management policy via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated.'),
('001823','deprecated','2013-03-01','DISA FSO','policy','The organization documents the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.',NULL,NULL,NULL),
('001824','draft','2013-03-01','DISA FSO','policy','The organization defines the organizational personnel or roles to whom the configuration management procedures are to be disseminated.','CM-1.2',' DoD has defined the organizational personnel or roles as all stakeholders in the configuration management process.',' The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the organizational personnel or roles as all stakeholders in the configuration management process.'),
('001825','draft','2013-03-01','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.','CM-1.6','The organization being inspected/assessed disseminates the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls via an information sharing capability (e.g. portal, intranet, email, etc.) to all stakeholders in the configuration management process.\n\nDoD has defined the organizational personnel or roles as all stakeholders in the configuration management process.','The organization conducting the inspection/assessment obtains and examines the procedures to facilitate the implementation of the configuration management policy and associated configuration management controls via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated.'),
('001826','draft','2013-03-05','DISA FSO','policy','The organization defines the circumstances upon which the organization reviews the information system changes to determine whether unauthorized changes have occurred.','CM-5(2).4','DoD has defined the circumstances as when there is an incident or when planned changes have been performed.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the circumstances as when there is an incident or when planned changes have been performed.'),
('001827','draft','2013-03-05','DISA FSO','policy','The organization defines the frequency with which to review information system privileges.','CM-5(5).3','DoD has defined the frequency as every 90 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 90 days.'),
('001828','draft','2013-03-05','DISA FSO','policy','The organization defines the frequency with which to reevaluate information system privileges.','CM-5(5).4','DoD has defined the frequency as every 90 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 90 days.'),
('001829','draft','2013-03-05','DISA FSO','policy','The organization reviews information system privileges per an organization-defined frequency.','CM-5(5).5','The organization being inspected/assessed reviews information system privileges every 90 days. The organization must maintain the reviews as an audit trail. DoD has defined the frequency as every 90 days.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews to ensure the organization being inspected/assessed reviews information system privileges every 90 days . DoD has defined the frequency as every 90 days.'),
('001830','draft','2013-03-05','DISA FSO','policy','The organization reevaluates information system privileges per an organization-defined frequency.','CM-5(5).6','The organization being inspected/assessed reevaluates information system privileges every 90 days . The organization must maintain the reevaluations as an audit trail. DoD has defined the frequency as every 90 days.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews to ensure the organization being inspected/assessed reevaluates information system privileges every 90 days. DoD has defined the frequency as every 90 days.'),
('001831','deprecated','2013-03-14','DISA FSO','policy','The organization documents an audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.',NULL,NULL,NULL),
('001832','draft','2013-03-14','DISA FSO','policy','The organization disseminates the audit and accountability policy to organization-defined personnel or roles.','AU-1.4','The organization being inspected/assessed disseminates, via an information sharing capability, to the ISSO and ISSM and others as the local organization deems appropriate an audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.\n\nDoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the audit and accountability procedures via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated.'),
('001833','deprecated','2013-03-14','DISA FSO','policy','The organization documents procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.',NULL,NULL,NULL),
('001834','draft','2013-03-14','DISA FSO','policy','The organization disseminates to organization-defined personnel or roles procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.','AU-1.6','The organization being inspected/assessed disseminates, via an information sharing capability, to the ISSO and ISSM and others as the local organization deems appropriate audit and accountability procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.\n\nDoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the audit and accountability procedures via the inspected organization\'s information sharing capability (e.g. portal, intranet, email, etc.) to ensure it has been disseminated.'),
('001835','deprecated','2013-03-14','DISA FSO','policy','The organization defines the frequency on which it will review the audit and accountability policy.',NULL,NULL,NULL),
('001836','deprecated','2013-03-14','DISA FSO','policy','The organization defines the frequency on which it will update the audit and accountability policy.',NULL,NULL,NULL),
('001837','deprecated','2013-03-14','DISA FSO','policy','The organization reviews the audit and accountability policy on an organization-defined frequency.',NULL,NULL,NULL),
('001838','deprecated','2013-03-14','DISA FSO','policy','The organization updates the audit and accountability policy on an organization-defined frequency.',NULL,NULL,NULL),
('001839','deprecated','2013-03-14','DISA FSO','policy','The organization defines the frequency on which it will review the audit and accountability procedures.',NULL,NULL,NULL),
('001840','deprecated','2013-03-14','DISA FSO','policy','The organization defines the frequency on which it will update the audit and accountability procedures.',NULL,NULL,NULL),
('001841','deprecated','2013-03-14','DISA FSO','policy','The organization reviews the audit and accountability procedures on an organization-defined frequency.',NULL,NULL,NULL),
('001842','deprecated','2013-03-14','DISA FSO','policy','The organization updates the audit and accountability procedures on an organization-defined frequency.',NULL,NULL,NULL),
('001843','deprecated','2013-03-14','DISA FSO','policy','The organization defines a frequency for updating the list of organization-defined auditable events.',NULL,NULL,NULL),
('001844','draft','2013-03-14','DISA FSO','technical','The information system provides centralized management and configuration of the content to be captured in audit records generated by organization-defined information system components.','AU-3(2).1','The organization being inspected/assessed configures the information system to provide centralized management and configuration of the content to be captured in audit records generated by all information system and network components. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1844. DoD has defined the information system components as all information system and network components.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to provide centralized management and configuration of the content to be captured in audit records generated by all information system and network components. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1844. DoD has defined the information system components as all information system and network components.'),
('001845','deprecated','2013-03-14','DISA FSO','technical','The information system provides centralized configuration of the content to be captured in audit records generated by organization-defined information system components.',NULL,NULL,NULL),
('001846','draft','2013-03-14','DISA FSO','policy','The organization defines information system components that will generate the audit records which are to be captured for centralized management of the content.','AU-3(2).2','DoD has defined the information system components as all information system and network components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as all information system and network components.'),
('001847','draft','2013-03-14','DISA FSO','policy','The organization defines information system components that will generate the audit records which are to be captured for centralized configuration of the content.','AU-3(2).3','DoD has defined the information system components as all information system and network components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as all information system and network components.'),
('001848','draft','2013-03-14','DISA FSO','policy','The organization defines the audit record storage requirements.','AU-4.1','The organization being inspected/assessed defines and documents the required audit record storage capacity. DoD has determined the audit record storage requirements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented audit record storage requirements to ensure the organization being inspected/assessed has defined those requirements. DoD has determined the audit record storage requirements are not appropriate to define at the Enterprise level.'),
('001849','draft','2013-03-14','DISA FSO','policy','The organization allocates audit record storage capacity in accordance with organization-defined audit record storage requirements.','AU-4.2','The organization being inspected/assessed allocates, and configures the information system to allocate audit record storage capacity as defined in AU-4, CCI 1848. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1849.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to allocate audit record storage capacity as defined in AU-4, CCI 1848. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1849.'),
('001850','draft','2013-03-14','DISA FSO','policy','The organization defines the frequency on which the information system off-loads audit records onto a different system or media than the system being audited.','AU-4(1).1','DoD has defined the frequency as at a minimum, real-time for interconnected systems and weekly for stand-alone systems.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at a minimum, real-time for interconnected systems and weekly for stand-alone systems.'),
('001851','draft','2013-03-14','DISA FSO','technical','The information system off-loads audit records per organization-defined frequency onto a different system or media than the system being audited.','AU-4(1).2','The organization being inspected/assessed configures the information system to off-load audit records at a minimum, in real-time for interconnected systems and weekly for stand-alone systems onto a different system or media than the system being audited. DoD has defined the frequency as at a minimum, real-time for interconnected systems and weekly for stand-alone systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1851.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to off-load audit records at a minimum, in real-time for interconnected systems and weekly for stand-alone systems onto a different system or media than the system being audited. DoD has defined the frequency as at a minimum, real-time for interconnected systems and weekly for stand-alone systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1851.'),
('001852','draft','2013-03-14','DISA FSO','policy','The organization defines the personnel, roles and/or locations to receive a warning when allocated audit record storage volume reaches a defined percentage of maximum audit records storage capacity.','AU-5(1).1','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the ISSO/PMO and ISSM, who shall receive a warning when allocated audit record storage volume reaches a defined percentage of maximum audit records storage capacity. If there are no additional personnel or roles, the organization must also document that.\n\nDoD has defined the personnel or roles as at a minimum, the ISSO/PMO and ISSM.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles who should receive a warning when allocated audit record storage volume reaches a defined percentage of maximum audit records storage capacity to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles beyond the ISSO/PMO and ISSM.\n\nDoD has defined the personnel or roles as at a minimum, the ISSO/PMO and ISSM.'),
('001853','draft','2013-03-14','DISA FSO','policy','The organization defines the time period within which organization-defined personnel, roles, and/or locations are to receive warnings when allocated audit record storage volume reaches an organization-defined percentage of maximum audit records storage capacity.','AU-5(1).2','DoD has defined the time period as immediate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediate.'),
('001854','draft','2013-03-14','DISA FSO','policy','The organization defines the percentage of maximum audit record storage capacity that is to be reached, at which time the information system will provide a warning to organization-defined personnel, roles, and/or locations.','AU-5(1).3','DoD has defined the percentage as 75 percent.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the percentage as 75 percent.'),
('001855','draft','2013-03-14','DISA FSO','technical','The information system provides a warning to organization-defined personnel, roles, and/or locations within an organization-defined time period when allocated audit record storage volume reaches an organization-defined percentage of repository maximum audit record storage capacity.','AU-5(1).4','The organization being inspected/assessed configures the information system to immediately provide a warning to personnel, roles, and/or locations defined in AU-5 (1), CCI 1852 when allocated audit record storage volume reaches 75 percent of repository maximum audit record storage capacity. DoD has defined the time period as immediate. DoD has defined the percentage as 75 percent. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1855.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to immediately provide a warning to personnel, roles, and/or locations defined in AU-5 (1), CCI 1852 when allocated audit record storage volume reaches 75 percent of repository maximum audit record storage capacity. DoD has defined the time period as immediate. DoD has defined the percentage as 75 percent. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1855.'),
('001856','draft','2013-03-14','DISA FSO','policy','The organization defines the real-time period within which the information system is to provide an alert when organization-defined audit failure events occur.','AU-5(2).2','DoD has defined the real-time period as immediate.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the real-time period as immediate.'),
('001857','draft','2013-03-14','DISA FSO','policy','The organization defines the personnel, roles, and/or locations to receive alerts when organization-defined audit failure events occur.','AU-5(2).3','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the SCA and ISSO, who shall receive alerts when all audit failure events occur. If there are no additional personnel or roles, the organization must also document that. DoD has defined the personnel or roles as at a minimum, the SCA and ISSO. DoD has defined the audit failure events as all.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles who should receive alerts when all audit failure events occur to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles. DoD has defined the audit failure events as all.'),
('001858','draft','2013-03-14','DISA FSO','technical','The information system provides a real-time alert in an organization-defined real-time period to organization-defined personnel, roles, and/or locations when organization-defined audit failure events requiring real-time alerts occur.','AU-5(2).4','The organization being inspected/assessed configures the information system to immediately provide a real-time alert to personnel, roles, and/or locations defined in AU-5 (2), CCI 1857 when all audit failure events requiring real-time alerts occur. DoD has defined the real-time period as immediate. DoD has defined the audit failure events as all. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1858.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configured the information system to immediately provide a real-time alert to personnel, roles, and/or locations defined in AU-5 (2), CCI 1857 when all audit failure events requiring real-time alerts occur. DoD has defined the real-time period as immediate. DoD has defined the audit failure events as all. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1858.'),
('001859','draft','2013-03-14','DISA FSO','policy','The organization defines the network communication traffic volume thresholds reflecting limits on auditing capacity, specifying when the information system will reject or delay network traffic that exceed those thresholds.','AU-5(3).4','The organization being inspected/assessed defines and documents the network communication traffic volume thresholds reflecting limits on auditing capacity, specifying when the information system will reject or delay network traffic that exceed those thresholds.','The organization conducting the inspection/assessment obtains and examines the documented network communication traffic volume thresholds to ensure they have been defined.'),
('001860','draft','2013-03-14','DISA FSO','policy','The organization defines the audit failures which, should they occur, will invoke an organization-defined system mode.','AU-5(4).1','DoD has defined the audit failures as all.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the audit failures as all.'),
('001861','draft','2013-03-14','DISA FSO','technical','The information system invokes an organization-defined system mode, in the event of organization-defined audit failures, unless an alternate audit capability exists.','AU-5(4).2','The organization being inspected/assessed configures the information system to invoke the system mode defined in AU-5 (4), CCI 2907 in the event all audit failures, unless an alternate audit capability exists. DoD has defined the audit failures as all. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1861. ','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed invokes the system mode defined in AU-5 (4), CCI 2907 in the event all audit failures, unless an alternate audit capability exists.\n\nDoD has defined the audit failures as all.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1861'),
('001862','draft','2013-03-15','DISA FSO','policy','The organization defines the types of inappropriate or unusual activity to be reviewed and analyzed in the audit records.','AU-6.3','The organization being inspected/assessed defines and documents the types of inappropriate or unusual activity to be reviewed and analyzed in the audit records. DoD has determined that the types of inappropriate or unusual activity are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented types of inappropriate or unusual activity to ensure they have been defined. DoD has determined that the types of inappropriate or unusual activity are not appropriate to define at the Enterprise level.'),
('001863','draft','2013-03-15','DISA FSO','policy','The organization defines the personnel or roles to receive the reports of organization-defined inappropriate or unusual activity.','AU-6.5','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the ISSO and ISSM, who shall receive the reports of inappropriate or unusual activity defined in AU-6, CCI 1862. If there are no additional personnel or roles, the organization must also document that. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles who should receive the reports of inappropriate or unusual activity defined in AU-6, CCI 1862 to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles.'),
('001864','draft','2013-03-15','DISA FSO','policy','The organization employs automated mechanisms to integrate audit review and analysis to support organizational processes for investigation of and response to suspicious activities.','AU-6(1).1','The organization being inspected/assessed identifies and implements automated mechanisms to integrate audit review and analysis. The goal is to support organizational investigation of and response to suspicious activities.','The organization conducting the inspection/assessment obtains and examines documentation identifying automated mechanisms to integrate audit review and analysis to ensure such mechanisms have been identified. The organization conducting the inspection/assessment examines the identified automated mechanisms to ensure they have been implemented.'),
('001865','draft','2013-03-15','DISA FSO','policy','The organization employs automated mechanisms to integrate reporting processes to support organizational investigation of and response to suspicious activities.','AU-6(1).2','The organization being inspected/assessed identifies and implements automated mechanisms to integrate reporting processes (e.g., centralized log analysis tools). The goal is to support organizational investigation of and response to suspicious activities.','The organization conducting the inspection/assessment obtains and examines documentation identifying automated mechanisms to integrate reporting processes to ensure such mechanisms have been identified. The organization conducting the inspection/assessment examines the identified automated mechanisms to ensure they have been implemented.'),
('001866','draft','2013-03-15','DISA FSO','policy','The organization defines the data/information to be collected from other sources to enhance its ability to identify inappropriate or unusual activity.','AU-6(5).1','The organization being inspected/assessed defines and documents the data/information to be collected from other sources to enhance its ability to identify inappropriate or unusual activity. If no additional data/information is to be collected, that should also be documented. DoD has determined that the data/information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines documented data/information from other sources to ensure the information has been defined. DoD has determined that the data/information is not appropriate to define at the Enterprise level.'),
('001867','draft','2013-03-15','DISA FSO','policy','The organization integrates analysis of audit records with analysis of vulnerability scanning information, performance data, information system monitoring information, and/or organization-defined data/information collected from other sources to further enhance its ability to identify inappropriate or unusual activity.','AU-6(5).2','The organization being inspected/assessed documents and implements a process to integrate the analysis of audit records with the data/information defined in AU-6 (5), CCI 1866 (if any) to further enhance its ability to identify inappropriate or unusual activity.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed integrates the analysis of audit records with the data/information defined in AU-6 (5), CCI 1866 (if any) to further enhance its ability to identify inappropriate or unusual activity.'),
('001868','draft','2013-03-15','DISA FSO','policy','The organization specifies the permitted actions for each information system process, role, and/or user associated with the review and analysis of audit information.','AU-6(7).1','The organization being inspected/assessed specifies and documents the permitted actions for each information system process, role, and/or user associated with the review and analysis of audit information.','The organization conducting the inspection/assessment obtains and examines the documented permitted actions to ensure the organization being inspected/assessed specifies the permitted actions for each information system process, role, and/or user associated with the review and analysis of audit information.'),
('001869','draft','2013-03-15','DISA FSO','policy','The organization specifies the permitted actions for each information system process, role, and/or user associated with the reporting of audit information.','AU-6(7).2','The organization being inspected/assessed specifies and documents the permitted actions for each information system process, role, and/or user associated with the reporting of audit information.','The organization conducting the inspection/assessment obtains and examines the documented permitted actions to ensure the organization being inspected/assessed specifies the permitted actions for each information system process, role, and/or user associated with the reporting of audit information.'),
('001870','draft','2013-03-15','DISA FSO','policy','The organization performs a full-text analysis of audited privileged commands in a physically-distinct component or subsystem of the information system, or other information system that is dedicated to that analysis.','AU-6(8).1','The organization being inspected/assessed documents and implements a process to perform a full-text analysis of audited privileged commands in a physically-distinct component or subsystem of the information system, or other information system that is dedicated to that analysis.','The organization conducting the inspection/assessment obtains and examines the documented process and supporting records (e.g., analysis results) to ensure the organization being inspected/assessed performs a full-text analysis of audited privileged commands in a physically-distinct component or subsystem of the information system, or other information system that is dedicated to that analysis.'),
('001871','draft','2013-03-15','DISA FSO','policy','The organization correlates information from non-technical sources with audit information to enhance organization-wide situational awareness.','AU-6(9).1','The organization being inspected/assessed documents and implements a process to correlate information from non-technical sources with audit information to enhance organization-wide situational awareness.','The organization conducting the inspection/assessment obtains and examines the documented process and supporting records to ensure the organization being inspected/assessed correlates information from non-technical sources with audit information to enhance organization-wide situational awareness.'),
('001872','draft','2013-03-15','DISA FSO','policy','The organization adjusts the level of audit review and analysis within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.','AU-6(10).1','The organization being inspected/assessed documents and implements a process for adjusting the level of audit review within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information (e.g., INFOCON).','The organization conducting the inspection/assessment obtains and examines the documented process and supporting records to ensure the organization being inspected/assessed adjusts the level of audit review within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.'),
('001873','deprecated','2013-03-15','DISA FSO','policy','The organization adjusts the level of audit analysis within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.',NULL,NULL,NULL),
('001874','draft','2013-03-15','DISA FSO','policy','The organization adjusts the level of audit reporting within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.','AU-6(10).2','The organization being inspected/assessed documents and implements a process for adjusting the level of audit reporting within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information (e.g., INFOCON).','The organization conducting the inspection/assessment obtains and examines the documented process and supporting records to ensure the organization being inspected/assessed adjusts the level of audit reporting within the information system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.'),
('001875','draft','2013-03-15','DISA FSO','technical','The information system provides an audit reduction capability that supports on-demand audit review and analysis.','AU-7.1','The organization being inspected/assessed must employ information systems that provide an audit reduction capability that support on-demand audit review and analysis (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1875.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide an audit reduction capability that support on-demand audit review and analysis (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1875.'),
('001876','draft','2013-03-15','DISA FSO','technical','The information system provides an audit reduction capability that supports on-demand reporting requirements.','AU-7.2','The organization being inspected/assessed must employ information systems that provide an audit reduction capability that support on-demand reporting requirements (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1876.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide an audit reduction capability that supports on-demand reporting requirements (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1876.'),
('001877','draft','2013-03-15','DISA FSO','technical','The information system provides an audit reduction capability that supports after-the-fact investigations of security incidents.','AU-7.3','The organization being inspected/assessed must employ information systems that provide an audit reduction capability that support after-the-fact investigations of security incidents (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1877.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide an audit reduction capability that supports after-the-fact investigations of security incidents (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1877.'),
('001878','draft','2013-03-15','DISA FSO','technical','The information system provides a report generation capability that supports on-demand audit review and analysis.','AU-7.4','The organization being inspected/assessed must employ information systems that provide a report generation capability that support on-demand audit review and analysis (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1878.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide a report generation capability that supports on-demand audit review and analysis (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1878.'),
('001879','draft','2013-03-15','DISA FSO','technical','The information system provides a report generation capability that supports on-demand reporting requirements.','AU-7.5','The organization being inspected/assessed must employ information systems that provide a report generation capability that support on-demand reporting requirements (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1879.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide a report generation capability that supports on-demand reporting requirements (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1879.'),
('001880','draft','2013-03-15','DISA FSO','technical','The information system provides a report generation capability that supports after-the-fact investigations of security incidents.','AU-7.6','The organization being inspected/assessed must employ information systems that provide a report generation capability that support after-the-fact investigations of security incidents (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1880.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide a report generation capability that supports after-the-fact investigations of security incidents (either natively or through the use of third-party tools). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1880.'),
('001881','draft','2013-03-15','DISA FSO','technical','The information system provides an audit reduction capability that does not alter original content or time ordering of audit records.','AU-7.7','The organization being inspected/assessed must ensure that the audit reduction capability does not alter the original audit records. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1881.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs an audit reduction capability that does not alter original audit records. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1881.'),
('001882','draft','2013-03-15','DISA FSO','technical','The information system provides a report generation capability that does not alter original content or time ordering of audit records.','AU-7.8','The organization being inspected/assessed must ensure that the report generation capability does not alter the original audit records. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1882.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs a report generation capability that does not alter original audit records. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1882.'),
('001883','draft','2013-03-15','DISA FSO','policy','The organization defines the audit fields within audit records to be processed for events of interest by the information system.','AU-7(1).2','The organization being inspected/assessed must define and document the audit fields within audit records to be processed for events of interest by the information system. DoD has determined that the audit fields are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented audit fields to ensure the organization being inspected/assessed defines the audit fields within audit records to be processed for events of interest by the information system. DoD has determined that the audit fields are not appropriate to define at the Enterprise level.'),
('001884','draft','2013-03-15','DISA FSO','policy','The organization defines the audit fields within audit records to be sorted for events of interest by the information system.','AU-7(2).1','The organization being inspected/assessed must define and document the audit fields within audit records to be sorted for events of interest by the information system. DoD has determined that the audit fields are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented audit fields to ensure the organization being inspected/assessed defines the audit fields within audit records to be sorted for events of interest by the information system. DoD has determined that the audit fields are not appropriate to define at the Enterprise level.'),
('001885','draft','2013-03-15','DISA FSO','policy','The organization defines the audit fields within audit records to be searched for events of interest by the information system.','AU-7(2).2','The organization being inspected/assessed must define and document the audit fields within audit records to be searched for events of interest by the information system. DoD has determined that the audit fields are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented audit fields to ensure the organization being inspected/assessed defines the audit fields within audit records to be searched for events of interest by the information system. DoD has determined that the audit fields are not appropriate to define at the Enterprise level.'),
('001886','draft','2013-03-15','DISA FSO','technical','The information system provides the capability to sort audit records for events of interest based on the content of organization-defined audit fields within audit records.','AU-7(2).3','The organization being inspected/assessed must employ information systems that provide the capability to sort audit records for events of interest based on the content of audit fields within audit records as defined in AU-7 (2), CCI 1884. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1886.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide the capability to sort audit records for events of interest based on the content of audit fields within audit records as defined in AU-7 (2), CCI 1884. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1886.'),
('001887','draft','2013-03-15','DISA FSO','technical','The information system provides the capability to search audit records for events of interest based on the content of organization-defined audit fields within audit records.','AU-7(2).4','The organization being inspected/assessed must employ information systems that provide the capability to search audit records for events of interest based on the content of audit fields within audit records as defined in AU-7 (2), CCI 1885. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1887.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed employs information systems that provide the capability to search audit records for events of interest based on the content of audit fields within audit records as defined in AU-7 (2), CCI 1885. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1887.'),
('001888','draft','2013-03-15','DISA FSO','policy','The organization defines the granularity of time measurement for time stamps generated for audit records.','AU-8.2','DoD has defined the granularity of time measurement as one second.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the granularity of time measurement as one second.'),
('001889','draft','2013-03-15','DISA FSO','technical','The information system records time stamps for audit records that meet organization-defined granularity of time measurement.','AU-8.3','The organization being inspected/assessed configures the information system to generate time in the time stamps for audit records that meets one second granularity of time measurement. DoD has defined the granularity of time measurement as one second. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1889.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate time in the time stamps for audit records that meets one second granularity of time measurement. DoD has defined the granularity of time measurement as one second. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1889.'),
('001890','draft','2013-03-15','DISA FSO','technical','The information system records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).','AU-8.4','The organization being inspected/assessed configures the information system to generate time stamps for audit records that contain time zones or time offsets that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1890.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to generate time stamps for audit records that contain time zones or time offsets that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1890.'),
('001891','draft','2013-03-15','DISA FSO','technical','The information system compares internal information system clocks on an organization-defined frequency with an organization-defined authoritative time source.','AU-8(1).3','The organization being inspected/assessed configures the information system to synchronize internal information system clocks every 24 hours for networked systems with an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet / SIPRNet) and/or the Global Positioning System (GPS) when the time difference is greater than the difference defined in AU-8 (1), CCI 1892.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1891.\n\nDoD has defined the frequency as every 24 hours for networked systems.\n\nDoD has defined the authoritative time source as an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet / SIPRNet) and/or the Global Positioning System (GPS).','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to synchronize internal information system clocks every 24 hours for networked systems with an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet / SIPRNet) and/or the Global Positioning System (GPS) when the time difference is greater than the difference defined in AU-8 (1), CCI 1892.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1891.\n\nDoD has defined the frequency as every 24 hours for networked systems.\n\nDoD has defined the authoritative time source as an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet / SIPRNet) and/or the Global Positioning System (GPS).'),
('001892','draft','2013-03-15','DISA FSO','policy','The organization defines the time difference which, when exceeded, will require the information system to synchronize the internal information system clocks to the organization-defined authoritative time source.','AU-8(1).4','The organization being inspected/assessed defines and documents the time difference, which, when exceeded, will require the information system to synchronize the internal information system clocks.\n\nDoD has determined the time difference is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time difference to ensure the organization being inspected/assessed defines the time difference which, when exceeded, will require the information system to synchronize the internal information system clocks.\n\nDoD has determined the time difference is not appropriate to define at the Enterprise level.'),
('001893','draft','2013-03-15','DISA FSO','technical','The information system identifies a secondary authoritative time source that is located in a different geographic region than the primary authoritative time source.','AU-8(2).1','The organization being inspected/assessed configures the information system to use a secondary authoritative time source that is located in a different geographic region than the primary authoritative time source. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1893.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed uses a secondary authoritative time source that is located in a different geographic region than the primary authoritative time source. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1893.'),
('001894','draft','2013-03-15','DISA FSO','policy','The organization defines the subset of privileged users who will be authorized access to the management of audit functionality.','AU-9(4).1','The organization being inspected/assessed defines and documents the subset of privileged users to be authorized access to the management of audit functionality. DoD has determined the subset of privileged users is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented subset of privileged users to be authorized access to the management of audit functionality, to ensure the organization being inspected/assessed defines and documents the subset of privileged users to be authorized access to the management of audit functionality. DoD has determined the subset of privileged users is not appropriate to define at the Enterprise level.'),
('001895','draft','2013-03-15','DISA FSO','policy','The organization defines the audit information requiring dual authorization for movement or deletion actions.','AU-9(5).1','The organization being inspected/assessed defines and documents the audit information requiring dual authorization for movement or deletion actions. DoD has determined the audit information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the definition of audit information requiring dual authorization for movement or deletion actions, to ensure the organization being inspected/assessed defines and documents the audit information requiring dual authorization for movement or deletion actions. DoD has determined the audit information is not appropriate to define at the Enterprise level.'),
('001896','draft','2013-03-15','DISA FSO','technical','The organization enforces dual authorization for movement and/or deletion of organization-defined audit information.','AU-9(5).2','The organization being inspected/assessed configures the information system to enforce dual authorization for movement and/or deletion of audit information defined in AU-9 (5), CCI 1895. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1896.','The organization conducting the inspection/assessment examines the information system to ensure that the organization being inspected/assessed has configured the information system to enforce dual authorization for movement and/or deletion of audit information defined in AU-9 (5), CCI 1895. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1896.'),
('001897','draft','2013-03-15','DISA FSO','policy','The organization defines the subset of privileged users who will be authorized read-only access to audit information.','AU-9(6).1','The organization being inspected/assessed defines and documents the subset of privileged users who will be authorized read-only access to audit information. DoD has determined that the subset of privileged users is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the subset of privileged users who will be authorized read-only access to audit information, to ensure the organization being inspected/assessed defines and documents subset of privileged users who will be authorized read-only access to audit information. DoD has determined that the subset of privileged users is not appropriate to define at the Enterprise level.'),
('001898','draft','2013-03-15','DISA FSO','policy','The organization authorizes read-only access to audit information to an organization-defined subset of privileged users.','AU-9(6).2','The organization being inspected/assessed authorizes read only access to audit information to only the subset of privileged users defined in AU-9 (6), CCI 1897.','The organization conducting the inspection/assessment obtains and examines the documentation of read only access authorizations for audit information to ensure only the subset of privileged users defined in AU-9 (6), CCI 1897 have been granted access authorization.'),
('001899','draft','2013-03-15','DISA FSO','policy','The organization defines the actions to be covered by non-repudiation.','AU-10.2','DoD has defined the actions to be covered by non-repudiation as actions defined by DoDI 8520.02 and DoDI 8520.03. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the actions to be covered by non-repudiation as actions defined by DoDI 8520.02 and DoDI 8520.03. '),
('001900','draft','2013-03-15','DISA FSO','policy','The organization defines the strength of binding to be applied to the binding of the identity of the information producer with the information.','AU-10(1).1','The organization being inspected/assessed defines and documents the strength of binding and where within the information system it has been implemented, to be applied to the binding of the identity of the information producer with the information. DoD has determined that the strength of binding is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented strength of binding to ensure the organization being inspected/assessed defines the strength of binding and where within the information system it has been implemented, to be applied to the binding of the identity of the information producer with the information. DoD has determined that the strength of binding is not appropriate to define at the Enterprise level.'),
('001901','draft','2013-03-15','DISA FSO','technical','The information system binds the identity of the information producer with the information to an organization-defined strength of binding.','AU-10(1).2','The organization being inspected/assessed configures the information system to bind the identify of the information producer with the information with the strength of binding defined in AU-10 (1) CCI 1900. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1901.','The organization conducting the inspection/assessment examines the information system to ensure the producer identity is bound to the information with the strength of binding defined in AU-10 (1) CCI 1900. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1901.'),
('001902','draft','2013-03-15','DISA FSO','technical','The information system provides the means for authorized individuals to determine the identity of the producer of the information.','AU-10(1).3','The organization being inspected/assessed configures the information system to provide a means for authorized individuals to determine the identity of the producer of the information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1902.','The organization conducting the inspection/assessment examines the information system to ensure authorized individuals are able to determine the identity of the producer of the information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1902.'),
('001903','draft','2013-03-15','DISA FSO','policy','The organization defines the frequency on which the information system is to validate the binding of the information producer identity to the information.','AU-10(2).1','DoD has defined the frequency as according to the tool\'s capability frequency, but at a minimum, upon first access or hourly in cases of continued access.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as according to the tool\'s capability frequency, but at a minimum, upon first access or hourly in cases of continued access.'),
('001904','draft','2013-03-15','DISA FSO','technical','The information system validates the binding of the information producer identity to the information at an organization-defined frequency.','AU-10(2).2','The organization being inspected/assessed configures the information system to validate the binding of the information producer identity to the information according to the tool\'s capability frequency, but at a minimum, upon first access or hourly in cases of continued access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1904. DoD has defined the frequency as according to the tool\'s capability frequency, but at a minimum, upon first access or hourly in cases of continued access.','The organization conducting the inspection/assessment examines the information system to ensure the information system is configured to validate the binding of the information producer identity to the information according to the tool\'s capability frequency, but at a minimum, upon first access or hourly in cases of continued access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1904. DoD has defined the frequency as according to the tool\'s capability frequency, but at a minimum, upon first access or hourly in cases of continued access.'),
('001905','draft','2013-03-15','DISA FSO','policy','The organization defines the actions to be performed in the event of an error when validating the binding of the information producer identity to the information.','AU-10(2).3','The organization being inspected/assessed defines and documents the actions to be performed in the event of an error when validating the binding of the information producer identity to the information. The organization should consider the system\'s environment and impact of the errors when defining the actions. Examples of actions include automated notification to administrators, halt system process or read action DoD has determined the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented actions to ensure the organization being inspected/assessed defines the actions to be performed in the event of an error when validating the binding of the information producer identity to the information. DoD has determined the actions are not appropriate to define at the Enterprise level.'),
('001906','draft','2013-03-15','DISA FSO','technical','The information system performs organization-defined actions in the event of an error when validating the binding of the information producer identity to the information.','AU-10(2).4','The organization being inspected/assessed configures the information system to perform the actions defined in AU-10 (2), CCI 1905 in the event of an error when validating the binding of the information producer identity to the information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1906.','The organization conducting the inspection/assessment examines the information system to ensure the information system is configured to perform the actions defined in AU-10 (2), CCI 1905 in the event of an error when validating the binding of the information producer identity to the information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1906.'),
('001907','draft','2013-03-15','DISA FSO','policy','The organization defines the security domains which will require the information system validate the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer.','AU-10(4).2','The organization being inspected/assessed defines and documents the security domains which require the information system validate the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer. DoD has determined the security domains are not appropriate to define at the Enterprise level. Note: Security domain as defined by CNSSI 4009.','The organization conducting the inspection/assessment obtains and examines the documented security domains to ensure the organization being inspected/assessed defines the security domains which require the information system validate the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer. DoD has determined the security domains are not appropriate to define at the Enterprise level.'),
('001908','draft','2013-03-15','DISA FSO','policy','The organization defines the action the information system is to perform in the event of an information reviewer identity binding validation error.','AU-10(4).3','The organization being inspected/assessed defines and documents the actions the information system is to perform in the event of a information reviewer identity binding validation error. At a minimum, the actions must include alerting the data/information owner of a validation error on a reviewers identity.\n\nDoD has determined that all actions are not appropriate to define at the Enterprise level. At a minimum, the actions must include alerting the data/information owner of a validation error on a reviewers identity.','The organization conducting the inspection/assessment obtains and examines the documented actions to ensure the organization being inspected/assessed defines the actions the information system is to perform in the event of a information reviewer identity binding validation error. At a minimum, the actions must include alerting the data/information owner of a validation error on a reviewers identity.\n\nDoD has determined that all actions are not appropriate to define at the Enterprise level. At a minimum, the actions must include alerting the data/information owner of a validation error on a reviewers identity.'),
('001909','draft','2013-03-15','DISA FSO','technical','The information system performs organization-defined actions in the event of an information reviewer identity binding validation error.','AU-10(4).4','The organization being inspected/assessed configures the information system to perform actions defined in AU-10 (4), CCI 1908 in the event of an information reviewer identity binding validation error. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1909.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to perform actions defined in AU-10 (4), CCI 1908 in the event of an information reviewer identity binding validation error. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1909.'),
('001910','draft','2013-03-15','DISA FSO','policy','The organization defines the personnel or roles allowed to select which auditable events are to be audited by specific components of the information system.','AU-12.4','DoD has defined the personnel or roles as the ISSM or individuals appointed by the ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSM or individuals appointed by the ISSM.'),
('001911','draft','2013-03-15','DISA FSO','policy','The organization defines the selectable event criteria to be used as the basis for changes to the auditing to be performed on organization-defined information system components, by organization-defined individuals or roles, within organization-defined time thresholds.','AU-12(3).1','The organization being inspected/assessed defines and documents the selectable event criteria for which changed auditing is to be performed. DoD has determined the selectable event criteria is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented selectable event criteria to ensure the organization being inspected/assessed defines the selectable event criteria for which changed auditing is to be performed. DoD has determined the selectable event criteria is not appropriate to define at the Enterprise level.'),
('001912','draft','2013-03-15','DISA FSO','policy','The organization defines the time thresholds for organization-defined individuals or roles to change the auditing to be performed based on organization-defined selectable event criteria.','AU-12(3).2','The organization being inspected/assessed defines and documents the time thresholds for individuals or roles to change the auditing to be performed on information system components based on selectable event criteria defined in AU-12 (3), CCI 1911 occurs. DoD has determined the time thresholds are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time thresholds to ensure the organization being inspected/assessed defines the time thresholds for individuals or roles to change the auditing to be performed on information system components based on selectable event criteria defined in AU-12 (3), CCI 1911 occurs. DoD has determined the time thresholds are not appropriate to define at the Enterprise level.'),
('001913','draft','2013-03-15','DISA FSO','policy','The organization defines the individuals or roles that are to be provided the capability to change the auditing to be performed based on organization-defined selectable event criteria, within organization-defined time thresholds.','AU-12(3).3','The organization being inspected/assessed defines and documents the individuals or roles that are to be provided the capability to change the auditing to be performed based on the selectable event criteria defined in AU-12 (3), CCI 1911, within the time thresholds defined in AU-12 (3), CCI 1912. DoD has determined that the individuals or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented individuals or roles to ensure the organization being inspected/assessed defines the individuals or roles that are to be provided the capability to change the auditing to be performed based on the selectable event criteria defined in AU-12 (3), CCI 1911, within the time thresholds defined in AU-12 (3), CCI 1912. DoD has determined that the individuals or roles are not appropriate to define at the Enterprise level.'),
('001914','draft','2013-03-15','DISA FSO','technical','The information system provides the capability for organization-defined individuals or roles to change the auditing to be performed on organization-defined information system components based on organization-defined selectable event criteria within organization-defined time thresholds.','AU-12(3).4','The organization being inspected/assessed configures the information system to provide the capability for individuals or roles defined in AU-12 (3), CCI 1913 to change the auditing to be performed on information system components defined in AU-12 (3), CCI 2047 based on selectable event criteria defined in AU-12 (3), CCI 1911 within time thresholds defined in AU-12 (3), CCI 1912. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1914.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for individuals or roles defined in AU-12 (3), CCI 1913 to change the auditing to be performed on information system components defined in AU-12 (3), CCI 2047 based on selectable event criteria defined in AU-12 (3), CCI 1911 within time thresholds defined in AU-12 (3), CCI 1912. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1914.'),
('001915','draft','2013-03-15','DISA FSO','policy','The organization defines the open source information and/or information sites to be monitored for evidence of unauthorized exfiltration or disclosure of organizational information.','AU-13.3','The organization being inspected/assessed defines and documents the open source information and/or information sites to be monitored for evidence of unauthorized exfiltration or disclosure of organizational information.\n\nDoD has determined that open source information and/or information sites should be defined at the Component level, not appropriate to define at the Enterprise level. Note: The value in this control may not be used to deny reciprocal acceptance of a C&A (A&A) package.','The organization conducting the inspection/assessment obtains and examines the documented open source information and/or information sites to ensure the organization being inspected/assessed defines the open source information and/or information sites to be monitored for evidence of unauthorized exfiltration or disclosure of organizational information.\n\nDoD has determined that open source information and/or information sites should be defined at the Component level, not appropriate to define at the Enterprise level. Note: The value in this control may not be used to deny reciprocal acceptance of a C&A (A&A) package.'),
('001916','draft','2013-03-15','DISA FSO','policy','The organization employs automated mechanisms to determine if organizational information has been disclosed in an unauthorized manner.','AU-13(1).1','The organization being inspected/assessed documents and employs an automated mechanism to determine if organizational information has been disclosed in an unauthorized manner.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated mechanisms to ensure that the identified system determines if organizational information has been disclosed in an unauthorized manner. The organization being inspected/assessed may be required to demonstrate use of their identified automated mechanisms.'),
('001917','draft','2013-03-15','DISA FSO','policy','The organization defines the frequency for reviewing the open source information sites being monitored.','AU-13(2).1','The organization being inspected/assessed defines and documents the frequency for reviewing the open source information sites being monitored.\n\nDoD has determined that the frequency should be defined at the Component level, not appropriate to define at the Enterprise level. Note: The value in this control may not be used to deny reciprocal acceptance of a C&A (A&A) package.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency for reviewing the open source information sites being monitored.\n\nDoD has determined that the frequency should be defined at the Component level, not appropriate to define at the Enterprise level. Note: The value in this control may not be used to deny reciprocal acceptance of a C&A (A&A) package.'),
('001918','draft','2013-03-15','DISA FSO','policy','The organization reviews the open source information sites being monitored per organization-defined frequency.','AU-13(2).2','The organization being inspected/assessed documents and implements a process to review the open source information sites being monitored per the frequency defined in AU-13 (2), CCI 1917.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed reviews the open source information sites being monitored per the frequency defined in AU-13 (2), CCI 1917.'),
('001919','draft','2013-03-15','DISA FSO','technical','The information system provides the capability for authorized users to select a user session to capture/record or view/hear.','AU-14.1','The organization being inspected/assessed configures the information system to provide the capability for authorized users to select a user session to capture/record or view/hear. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1919.','The organization conducting the inspection/assessments examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for authorized users to select a user session to capture/record or view/hear. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1919.'),
('001920','draft','2013-03-15','DISA FSO','technical','The information system provides the capability for authorized users to remotely view/hear all content related to an established user session in real time.','AU-14(3).1','The organization being inspected/assessed configures the information system to provide the capability for authorized users to remotely view/hear all content related to an established user session in real time. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1920.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability for authorized users to remotely view/hear all content related to an established user session in real time. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1920.'),
('001921','draft','2013-03-15','DISA FSO','policy','The organization defines the alternative audit functionality to be provided in the event of a failure in the primary audit capability.','AU-15.1','The organization being inspected/assessed will define and document the alternative audit functionality to be provided in the event of a failure in the primary audit capability. The organization shall consider trade-offs between the needs for system availability and audit integrity when defining the actions. Unless availability is an overriding concern, the default action should be to shut down the information system. DoD has determined that the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented alternative audit functionality to ensure the organization being inspected/assessed has defined the alternative audit functionality to be provided in the event of a failure in the primary audit capability. DoD has determined that the actions are not appropriate to define at the Enterprise level.'),
('001922','draft','2013-03-15','DISA FSO','policy','The organization provides an alternative audit capability in the event of a failure in primary audit capability that provides organization-defined alternative audit functionality.','AU-15.2','The organization being inspected/assessed configures the information system to implement an alternative audit capability in the event of a failure in primary audit capability that provides the alternative audit functionality defined in AU-15, CCI 1921. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1922.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement an alternative audit capability in the event of a failure in primary audit capability that provides the alternative audit functionality defined in AU-15, CCI 1921. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1922.'),
('001923','draft','2013-03-15','DISA FSO','policy','The organization defines the audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries.','AU-16.1','The organization being inspected/assessed defines and documents the audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries. DoD has determined the methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented audit information to ensure the organization being inspected/assessed defines the audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries. DoD has determined the methods are not appropriate to define at the Enterprise level.'),
('001924','draft','2013-03-15','DISA FSO','policy','The organization defines the methods to be employed when coordinating audit information among external organizations when audit information is transmitted across organizational boundaries.','AU-16.2','The organization being inspected/assessed defines and documents the methods to be employed when coordinating audit information among external organizations when audit information is transmitted across organizational boundaries. DoD has determined the methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented methods to ensure the organization being inspected/assessed defines the methods to be employed when coordinating audit information among external organizations when audit information is transmitted across organizational boundaries. DoD has determined the methods are not appropriate to define at the Enterprise level.'),
('001925','draft','2013-03-15','DISA FSO','policy','The organization employs organization-defined methods for coordinating organization-defined audit information among external organizations when audit information is transmitted across organizational boundaries.','AU-16.3','The organization being inspected/assessed documents and implements a process to employ the methods defined in AU-16, CCI 1924 for coordinating audit information defined in AU-16, CCI 1923 among external organizations when audit information is transmitted across organizational boundaries.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs a process to employ the methods defined in AU-16, CCI 1924 for coordinating audit information defined in AU-16, CCI 1923 among external organizations when audit information is transmitted across organizational boundaries.'),
('001926','draft','2013-03-15','DISA FSO','policy','The organization requires that the identity of individuals be preserved in cross-organizational audit trails.','AU-16(1).1','The organization being inspected/assessed implements a process to ensure that the identity of individuals be preserved in cross organizational audit trails.','The organization conducting the inspection/assessment obtains and examines a sampling of cross organizational audit trails to ensure that the identify of individuals conducting audited actions is preserved.'),
('001927','draft','2013-03-15','DISA FSO','policy','The organization defines the organizations that will be provided cross-organizational audit information.','AU-16(2).1','The organization being inspected/assessed defines and documents the organizations that will be provided cross-organizational audit information. DoD has determined the cross-organizational sharing agreements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented organizations to ensure the organization being inspected/assessed defines the organizations that will be provided cross-organizational audit information. DoD has determined the cross-organizational sharing agreements are not appropriate to define at the Enterprise level.'),
('001928','draft','2013-03-15','DISA FSO','policy','The organization defines the cross-organizational sharing agreements to be established with organization-defined organizations authorized to be provided cross-organizational sharing of audit information.','AU-16(2).2','The organization being inspected/assessed defines and documents the cross-organizational sharing agreements to be established with organizations defined in AU-16 (2), CCI 1927 authorized to be provided cross-organizational sharing of audit information. DoD has determined the cross-organizational sharing agreements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented sharing agreements to ensure the organization being inspected/assessed defines the cross-organizational sharing agreements to be established with organizations defined in AU-16 (2), CCI 1927 authorized to be provided cross-organizational sharing of audit information. DoD has determined the cross-organizational sharing agreements are not appropriate to define at the Enterprise level.'),
('001929','draft','2013-03-15','DISA FSO','policy','The organization provides cross-organizational audit information to organization-defined organizations based on organization-defined cross organizational sharing agreements.','AU-16(2).3','The organization being inspected/assessed provides cross-organizational audit information to organizations defined in AU-16 (2), CCI 1927 based on cross organizational sharing agreements defined in AU-16 (2), CCI 1928.','The organization conducting the inspection/assessment obtains and examines the audit information that provides cross-organizational audit information to organizations defined in AU-16 (2), CCI 1927 based on cross organizational sharing agreements defined in AU-16 (2), CCI 1928.'),
('001930','draft','2013-04-08','DISA FSO','policy','The organization defines the organizational personnel or roles to whom the audit and accountability policy is to be disseminated.','AU-1.1','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the ISSO or ISSM, to whom the audit and accountability policy is to be disseminated. If there are no additional personnel or roles, the organization must also document that. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles to whom the audit and accountability policy is to be disseminated to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001931','draft','2013-04-08','DISA FSO','policy','The organization defines the organizational personnel or roles to whom the audit and accountability procedures are to be disseminated.','AU-1.2','The organization being inspected/assessed defines and documents any personnel or roles, in addition to the ISSO or ISSM, to whom the audit and accountability procedures are to be disseminated. If there are no additional personnel or roles, the organization must also document that. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.','The organization conducting the inspection/assessment obtains and examines the documented list of personnel or roles to whom the audit and accountability procedures are to be disseminated to ensure the organization being inspected/assessed has either defined additional personnel or roles, or identified that there are no additional personnel or roles. DoD has defined the personnel or roles as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001932','draft','2013-05-03','DISA FSO','policy','The organization documents an identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.',NULL,NULL,NULL),
('001933','draft','2013-05-03','DISA FSO','policy','The organization defines the personnel or roles to be recipients of the identification and authentication policy and the procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.','IA-1.1','DoD has defined the roles to be recipients of the identification and authentication policy and the procedures as the ISSO and ISSM and others as the local organization deems appropriate.\n\nDoDI 8520.02 and DoDI 8520.03 meet the DoD requirement for Identification and Authentication policy and procedures.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policies, DoDI 8520.02 and DoDI 8520.03.','DoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8520.02 and DoDI 8520.03.\n\nDoD has defined the roles to be recipients of the identification and authentication policy and the procedures as the ISSO and ISSM and others as the local organization deems appropriate.'),
('001934','draft','2013-05-03','DISA FSO','policy','The organization documents procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.',NULL,NULL,NULL),
('001935','draft','2013-05-03','DISA FSO','policy','The organization defines the strength of mechanism requirements for the device that is separate from the system gaining access to privileged accounts.','IA-2(6).1','For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.'),
('001936','draft','2013-05-03','DISA FSO','technical','The information system implements multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access.','IA-2(6).2','The organization being inspected/assessed configures the information system to implement multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1936.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1936.'),
('001937','draft','2013-05-03','DISA FSO','technical','The device used in the information system implementation of multifactor authentication for network access to privileged accounts meets organization-defined strength of mechanism requirements.','IA-2(6).3','The organization being inspected/assessed will use DoD PKI or a technology approved by their Authorizing Official that meet Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1937.','The organization conducting the inspection/assessment obtains and examines the device used to ensure that the device implemented for multifactor authentication for network access to privileged accounts meets Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1937.'),
('001938','draft','2013-05-03','DISA FSO','policy','The organization defines the strength of mechanism requirements for the device that is separate from the system gaining access to non-privileged accounts.','IA-2(7).1','For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.'),
('001939','draft','2013-05-03','DISA FSO','technical','The information system implements multifactor authentication for network access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access.','IA-2(7).2','The organization being inspected/assessed configures the information system to implement multifactor authentication for network access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1939.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for network access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1939,'),
('001940','draft','2013-05-03','DISA FSO','technical','The device used in the information system implementation of multifactor authentication for network access to non-privileged accounts meets organization-defined strength of mechanism requirements.','IA-2(7).3','The organization being inspected/assessed will use DoD PKI or a technology approved by their Authorizing Official that meet Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1940.','The organization conducting the inspection/assessment obtains and examines the device used to ensure that the device implemented for multifactor authentication for network access to non-privileged accounts meets Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1940.'),
('001941','draft','2013-05-03','DISA FSO','technical','The information system implements replay-resistant authentication mechanisms for network access to privileged accounts.','IA-2(8).1','The organization being inspected/assessed configures the information system to implement replay-resistant authentication mechanisms for network access to privileged accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1941.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement replay-resistant authentication mechanisms for network access to privileged accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1941.'),
('001942','draft','2013-05-03','DISA FSO','technical','The information system implements replay-resistant authentication mechanisms for network access to non-privileged accounts.','IA-2(9).1','The organization being inspected/assessed configures the information system to implement replay-resistant authentication mechanisms for network access to non-privileged accounts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1942.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement replay-resistant authentication mechanisms for network access to non-privileged accounts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1942.'),
('001943','draft','2013-05-03','DISA FSO','policy','The organization defines the information system accounts for which single sign-on capability will be provided.','IA-2(10).1','The organization being inspected/assessed defines and documents any accounts for which a single sign-on capability is provided. For single sign-on providers (creator/maintainer of the single sign-on user accounts) this will be a list of accounts or groups that are authorized to use single sign-on capability. For single sign-on services this will be a per provider list of accounts or groups authorized to use the service. DoD has determined the system services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list of system accounts to ensure the organization being inspected/assessed defines any accounts for which a single sign-on capability is provided. DoD has determined the system services are not appropriate to define at the Enterprise level.'),
('001944','draft','2013-05-03','DISA FSO','policy','The organization defines the information system services for which single sign-on capability will be provided.','IA-2(10).2','The organization being inspected/assessed defines and documents any services (e.g., websites) for which a single sign-on capability is provided. DoD has determined the system services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented system services to ensure the organization being inspected/assessed defines any services (e.g., websites) for which a single sign-on capability is provided. DoD has determined the system services are not appropriate to define at the Enterprise level.'),
('001945','draft','2013-05-03','DISA FSO','technical','The information system provides a single sign-on capability for an organization-defined list of information system accounts.','IA-2(10).3','The organization being inspected/assessed configures the information system to provide a single sign-on capability for the list of information system accounts defined in IA-2 (10), CCI 1943. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1945.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide a single sign-on capability for the list of information system accounts defined in IA-2 (10), CCI 1943. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1945.'),
('001946','draft','2013-05-03','DISA FSO','technical','The information system provides a single sign-on capability for an organization-defined list of information system services.','IA-2(10).4','The organization being inspected/assessed configures the information system to provide a single sign-on capability for the list of information system services defined in IA-2 (10), CCI 1944. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1946.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide a single sign-on capability for the list of information system services defined in IA-2 (10), CCI 1944. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1946.'),
('001947','draft','2013-05-03','DISA FSO','policy','The organization defines the strength of mechanism requirements for the device that is separate from the system gaining access and is to provide one factor of a multifactor authentication for remote access to privileged accounts.','IA-2(11).1','For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.'),
('001948','draft','2013-05-03','DISA FSO','technical','The information system implements multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access.','IA-2(11).2','The organization being inspected/assessed configures the information system to implement multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1948.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1948.'),
('001949','draft','2013-05-03','DISA FSO','technical','The device used in the information system implementation of multifactor authentication for remote access to privileged accounts meets organization-defined strength of mechanism requirements.','IA-2(11).3','The organization being inspected/assessed will use DoD PKI or a technology approved by their Authorizing Official that meet Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1949.','The organization conducting the inspection/assessment obtains and examines the device used to ensure that the device implemented for multifactor authentication for remote access to privileged accounts meets Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1949.'),
('001950','draft','2013-05-03','DISA FSO','policy','The organization defines the strength of mechanism requirements for the device that is separate from the system gaining access and is to provide one factor of a multifactor authentication for remote access to non-privileged accounts.','IA-2(11).4','For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. For the strength of mechanism requirements DoD has defined requirements as DoD PKI or a technology approved by their Authorizing Official, FIPS 140-2, NIAP Certification, or NSA approval.'),
('001951','draft','2013-05-03','DISA FSO','technical','The information system implements multifactor authentication for remote access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access.','IA-2(11).5','The organization being inspected/assessed configures the information system to implement multifactor authentication for remote access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1951.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement multifactor authentication for remote access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1951.'),
('001952','draft','2013-05-03','DISA FSO','technical','The device used in the information system implementation of multifactor authentication for remote access to non-privileged accounts meets organization-defined strength of mechanism requirements.','IA-2(11).6','The organization being inspected/assessed will use DoD PKI or a technology approved by their Authorizing Official that meet Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1952.','The organization conducting the inspection/assessment obtains and examines the device used to ensure that the device implemented for multifactor authentication for remote access to non-privileged accounts meets Federal standards for authentication such as FIPS 140-2, NIAP Certification, or NSA approval. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1952.'),
('001953','draft','2013-05-03','DISA FSO','technical','The information system accepts Personal Identity Verification (PIV) credentials.','IA-2(12).1','The organization being inspected/assessed configures the information system to accept PIV/CAC authentication. This control enhancement applies to organizations implementing logical access control systems (LACS) and physical access control systems (PACS). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1953','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to accept PIV/CAC authentication. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1953.'),
('001954','draft','2013-05-03','DISA FSO','technical','The information system electronically verifies Personal Identity Verification (PIV) credentials.','IA-2(12).2','The organization being inspected/assessed configures the information system to verify PIV/CAC authentication. This control enhancement applies to organizations implementing logical access control systems (LACS) and physical access control systems (PACS). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1954.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to verify PIV/CAC authentication. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1954.'),
('001955','draft','2013-05-03','DISA FSO','policy','The organization defines the out-of-band authentication to be implemented by the information system under organization-defined conditions.','IA-2(13).1','The organization being inspected/assessed defines and documents the out-of-band authentication to be implemented by the information system under organization-defined conditions. DoD has determined the out-of-band authentication is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented out-of-band authentication to ensure the organization being inspected/assessed defines the out-of-band authentication to be implemented by the information system under organization-defined conditions. DoD has determined the out-of-band authentication is not appropriate to define at the Enterprise level.'),
('001956','draft','2013-05-03','DISA FSO','policy','The organization defines the conditions for which the information system implements organization-defined out-of-band authentication.','IA-2(13).2','The organization being inspected/assessed defines and documents the conditions for which the information system implements organization-defined out-of-band authentication. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure the organization being inspected/assessed defines the conditions for which the information system implements organization-defined out-of-band authentication. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('001957','draft','2013-05-03','DISA FSO','technical','The information system implements organization-defined out-of-band authentication under organization-defined conditions.','IA-2(13).3','The organization being inspected/assessed configures the information system to implement out-of-band authentication defined in IA-2 (13), CCI 1955 under conditions defined in IA-2 (13), CCI 1956. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1957.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement out-of-band authentication defined in IA-2 (13), CCI 1955 under conditions defined in IA-2 (13), CCI 1956. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1957.'),
('001958','draft','2013-05-03','DISA FSO','technical','The information system authenticates an organization-defined list of specific and/or types of devices before establishing a local, remote, or network connection.','IA-3.3','The organization being inspected/assessed configures the network infrastructure to authenticate all mobiles devices and network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs) before establishing a local, remote, network connection. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1958. DoD has defined the value as all mobile devices and network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs). ','The organization conducting the inspection/assessment examine a sampling of the network infrastructure device configurations to ensure devices connecting to the infrastructure are uniquely authenticated. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1958.'),
('001959','draft','2013-05-03','DISA FSO','policy','The organization defines the specific devices and/or type of devices the information system is to authenticate before establishing a connection.','IA-3(1).1','DoD has defined the value as all network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the value as all network connected endpoint devices (including but not limited to: workstations, printers, servers (outside a datacenter), VoIP Phones, VTC CODECs).'),
('001960','draft','2013-05-03','DISA FSO','policy','The organization defines the lease information to be assigned to devices.','IA-3(3).1','The organization being inspected/assessed defines and documents the lease information to be assigned to devices. DoD has determined the lease information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented lease information assigned to devices. DoD has determined the lease information is not appropriate to define at the Enterprise level.'),
('001961','draft','2013-05-03','DISA FSO','policy','The organization defines the lease duration to be assigned to devices.','IA-3(3).2','The organization being inspected/assessed defines and documents the lease duration to be assigned to devices. DoD has determined the lease duration is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented lease duration to ensure the organization being inspected/assessed defines the lease duration to be assigned to devices. DoD has determined the lease duration is not appropriate to define at the Enterprise level'),
('001962','draft','2013-05-03','DISA FSO','technical','The organization standardizes dynamic address allocation lease information assigned to devices in accordance with organization-defined lease information.','IA-3(3).3','The organization being inspected/assessed configures the information system to grant leases containing organization defined lease information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1962.','The organization conducting the inspection/assessment examines the information system granting the lease to ensure the organization configures the information system to implement dynamic address allocation in accordance with CCI 1961. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1962.'),
('001963','draft','2013-05-03','DISA FSO','technical','The organization standardizes dynamic address allocation lease duration assigned to devices in accordance with organization-defined lease duration.','IA-3(3).4','The organization being inspected/assessed configures the information system to grant the leases assigned to devices in accordance with organization-defined lease duration. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1963.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to grant the leases assigned to devices in accordance with organization-defined lease duration. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1963.'),
('001964','deprecated','2013-05-03','DISA FSO','policy','The organization defines the configuration management process that is to handle the device identification procedures.',NULL,NULL,NULL),
('001965','draft','2013-05-03','DISA FSO','policy','The organization defines the configuration management process that is to handle the device authentication procedures.','IA-3(4).1','The organization being inspected/assessed defines and documents the configuration management process that is to handle the device authentication procedures. DoD has determined the configuration management process is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented configuration management process to ensure the organization being inspected/assessed defines the configuration management process that is to handle the device authentication procedures. DoD has determined the configuration management process is not appropriate to define at the Enterprise level.'),
('001966','draft','2013-05-03','DISA FSO','policy','The organization ensures that device identification based on attestation is handled by the organization-defined configuration management process.','IA-3(4).2','The organization being inspected/assessed ensures that device identification based on attestation is handled by the configuration management process defined in IA-3 (4), CCI 1968.','The organization conducting the inspection/assessment obtains and examines the documented configuration management process to ensure the organization being inspected/assessed has device identification based on attestation handled via the configuration management process.'),
('001967','draft','2013-05-03','DISA FSO','technical','The information system authenticates organization-defined devices and/or types of devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.','IA-3(1).2','The organization being inspected/assessed configures the information system to use cryptographically based bidirectional authentication. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1967.','The organization conducting the inspection/assessment examine a sampling of the network infrastructure device configurations to ensure devices connecting to the infrastructure use cryptographically based bidirectional authentication. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1967.'),
('001968','draft','2013-05-03','DISA FSO','policy','The organization defines the configuration management process that is to handle the device identification procedures.','IA-3(4).3','The organization being inspected/assessed defines and documents the configuration management process that is to handle the device identification procedures. DoD has determined the configuration management process is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented configuration management process to ensure the organization being inspected/assessed defines the configuration management process that is to handle the device identification procedures. DoD has determined the configuration management process is not appropriate to define at the Enterprise level.'),
('001969','draft','2013-05-03','DISA FSO','policy','The organization ensures that device authentication based on attestation is handled by the organization-defined configuration management process.','IA-3(4).4','The organization being inspected/assessed ensures that device authentication based on attestation is handled by the configuration management process defined in IA-3 (4), CCI 1965.','The organization conducting the inspection/assessment obtains and examines the documented configuration management process to ensure the organization being inspected/assessed has device authentication based on attestation handled via the configuration management process.'),
('001970','draft','2013-05-03','DISA FSO','policy','The organization defines the personnel or roles that authorize the assignment of individual, group, role, and device identifiers.','IA-4.1','DoD has defined the personnel or roles as the ISSM or ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the personnel or roles as the ISSM or ISSO.'),
('001971','draft','2013-05-03','DISA FSO','policy','The organization manages information system identifiers by receiving authorization from organization-defined personnel or roles to assign an individual, group, role, or device identifier.','IA-4.2','The organization being inspected/assessed implements a process to manage information system identifiers by receiving authorization from the ISSM or ISSO to assign an individual, group, role or device identifier.\n\nDoD has defined the personnel or roles as the ISSM or ISSO.','The organization conducting the inspection/assessment obtains and examines documentation and system configuration information to ensure the organization being inspected/assessed manages information system identifiers by receiving authorization from the ISSM or ISSO to assign an individual, group, role or device identifier.\n\nDoD has defined the personnel or roles as the ISSM or ISSO.'),
('001972','draft','2013-05-03','DISA FSO','policy','The organization manages information system identifiers by selecting an identifier that identifies an individual, group, role, or device.','IA-4.3','The organization being inspected/assessed implements a process to manage information system identifiers by selecting an identifier that identifies an individual, group, role, or device.','The organization conducting the inspection/assessment obtains and examines documentation or system configuration information to ensure the organization being inspected/assessed manages information system identifiers by selecting an identifier that identifies an individual, group, role, or device.'),
('001973','draft','2013-05-03','DISA FSO','policy','The organization manages information system identifiers by assigning the identifier to the intended individual, group, role, or device.','IA-4.4','The organization being inspected/assessed implements a process to manage information system identifiers by assigning the identifier to the intended individual, group, role, or device.','The organization conducting the inspection/assessment obtains and examines documentation or system configuration information to ensure the organization being inspected/assessed manages information system identifiers by assigning the identifier to the intended individual, group, role, or device.'),
('001974','draft','2013-05-03','DISA FSO','policy','The organization defines the time period for which the reuse of identifiers is prohibited.','IA-4.5','DoD has defined the time period as 1 year for user identifiers (DoD is not going to specify value for device identifier).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 1 year for user identifiers (DoD is not going to specify value for device identifier).'),
('001975','draft','2013-05-03','DISA FSO','policy','The organization manages information system identifiers by preventing reuse of identifiers for an organization-defined time period.','IA-4.6','The organization being inspected/assessed implements a process for information system identifiers to prevent reuse of identifiers for 1 year for user identifiers (DoD is not going to specify value for device identifier). DoD has defined the time period as 1 year for user identifiers (DoD is not going to specify value for device identifier).','The organization conducting the inspection/assessment obtains and examines documentation or system configuration information to ensure the organization being inspected/assessed prevents the reuse of identifiers for 1 year for user identifiers (DoD is not going to specify value for device identifier). DoD has defined the time period as 1 year for user identifiers (DoD is not going to specify value for device identifier).'),
('001976','draft','2013-05-03','DISA FSO','technical','The information system dynamically manages identifiers.','IA-4(5).1','The organization being inspected/assessed configures the information system to dynamically manage identifiers. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1976.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to dynamically manage identifiers. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1976.'),
('001977','draft','2013-05-03','DISA FSO','policy','The organization defines the external organizations with which it will coordinate for cross-management of identifiers.','IA-4(6).1','DoD has defined the external organizations as any external organization that shares cross-organizational identifiers.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external organizations as any external organization that shares cross-organizational identifiers.'),
('001978','draft','2013-05-03','DISA FSO','policy','The organization coordinates with organization-defined external organizations for cross-organization management of identifiers.','IA-4(6).2','The organization being inspected/assessed documents and implements a process to coordinate with any external organization that shares cross-organizational identifiers. DoD has defined the external organizations as any external organization that shares cross-organizational identifiers.','The organization conducting the inspection/assessment obtains and examines the documentation (e.g., Service Level Agreements (SLAs), Memorandum of Understanding (MOU), Memorandum of Agreement (MOA), contracts, etc.) to ensure the organization being inspected/assessed implements a process to coordinate with any external organization that shares cross-organizational identifiers. DoD has defined the external organizations as any external organization that shares cross-organizational identifiers.'),
('001979','draft','2013-05-03','DISA FSO','policy','The organization requires the registration process to receive an individual identifier be conducted in person before a designated registration authority.','IA-4(7).1','The organization being inspected/assessed documents and implements a process to require the registration process to receive an individual identifier be conducted in person before a designated registration authority.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires the registration process to receive an individual identifier be conducted in person before a designated registration authority.'),
('001980','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator.','IA-5.1','The organization being inspected/assessed defines and documents procedures for the secure distribution of authenticators. The process shall include verification of the identify of the individual, group, role, or device receiving the authenticator.','The organization conducting the inspection/assessment obtains and examines the documented procedures for the secure distribution of authenticators to ensure they have been defined and that they include a method to verify the identify of the individual, group, role, or device receiving the authenticator.'),
('001981','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by establishing administrative procedures for initial authenticator distribution.','IA-5.4','The organization being inspected/assessed defines and documents procedures for the secure distribution of authenticators.','The organization conducting the inspection/assessment obtains and examines the documented procedures for the secure distribution of authenticators to ensure they have been defined.'),
('001982','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by establishing administrative procedures for lost/compromised authenticators.','IA-5.5','The organization being inspected/assessed defines and documents procedures for lost/compromised authenticators.','The organization conducting the inspection/assessment obtains and examines the documented procedures for lost/compromised authenticators to ensure they have been defined.'),
('001983','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by establishing administrative procedures for damaged authenticators.','IA-5.6','The organization being inspected/assessed defines and documents procedures for the secure disposal of damaged authenticators.','The organization conducting the inspection/assessment obtains and examines the documented procedures for the secure disposal of damaged authenticators to ensure they have been defined.'),
('001984','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by establishing administrative procedures for revoking authenticators.','IA-5.7','The organization being inspected/assessed defines and documents procedures for revoking authenticators.','The organization conducting the inspection/assessment obtains and examines the documented procedures for revoking authenticators to ensure the procedures are defined.'),
('001985','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by implementing administrative procedures for initial authenticator distribution.','IA-5.8','The organization being inspected/assessed implements administrative procedures for initial authenticator distribution as documented in IA-5, CCIs 1980 & 1981.','The organization conducting the inspection/assessment obtains and examines records of initial authenticator distribution and interviews individuals responsible for authenticator distribution to ensure that the organization being inspected/assessed implements the process as defined in IA-5, CCIs 1980 & 1981.'),
('001986','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by implementing administrative procedures for lost/compromised authenticators.','IA-5.9','The organization being inspected/assessed implements administrative procedures for the response to lost/compromised authenticators as documented in IA-5, CCI 1982.','The organization conducting the inspection/assessment obtains and examines documented procedures for the response to lost/compromised authenticators to ensure that the organization being inspected/assessed implements the process as defined in IA-5, CCI 1982.'),
('001987','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by implementing administrative procedures for damaged authenticators.','IA-5.10','The organization being inspected/assessed implements administrative procedures for the response to damaged authenticators as documented in IA-5, CCI 1983.','The organization conducting the inspection/assessment obtains and examines documented procedures for the response to damaged authenticators to ensure that the organization being inspected/assessed implements the process as defined in IA-5, CCI 1983.'),
('001988','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by implementing administrative procedures for revoking authenticators.','IA-5(5).1','The organization being inspected/assessed documents and enforces a requirement for developers/installers of information system components to provide unique authenticators or change default authenticators prior to delivery/installation.','The organization conducting the inspection/assessment obtains and examines the documented requirements placed upon developers/installers of information system components to ensure that there is a documented requirement to provide unique authenticators or change default authenticators prior to delivery/installation.'),
('001989','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by changing default content of authenticators prior to information system installation.','IA-5.12','The organization being inspected/assessed documents and implements a procedures to change default authenticators prior to information system installation.','The organization conducting the inspection/assessment obtains and examines the documented procedures to change default authenticators to ensure the procedures are defined. The organization conducting the inspection/assessment obtains and examines a sampling of authenticator age data for default accounts to ensure that default authenticators are changed prior to installation.'),
('001990','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by changing authenticators for group/role accounts when membership to those accounts changes.','IA-5.22','The organization being inspected/assessed documents and implements procedures for changing authenticators for group/role accounts when membership to those accounts changes.','The organization conducting the inspection/assessment obtains and examines the documented procedures for group/role authenticator change to ensure the procedures are defined and applied when membership to those accounts changes. The organization conducting the inspection/assessment obtains and examines a sampling of authenticator age data and documentation of personnel role changes to ensure that group/role authenticators are changed when membership changes.'),
('001991','draft','2013-05-03','DISA FSO','technical','The information system, for PKI-based authentication, implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network.','IA-5(2).4','The information system must be configured to locally cache revocation data to support path discovery and validation in case of inability to access revocation information via the network. The information system may meet this requirement by locally caching certificate revocation lists (CRLs), Online Certificate Status Protocol (OCSP) responses, or a combination thereof. Cached revocation data must include revocation information from all PKIs serving known or anticipated users of the information system. Cached data must be refreshed with a frequency shorter than the life of the data (e.g. if a CRL is valid for 7 days, a new CRL must be retrieved and cached more frequently than every 7 days) to ensure that cached data is valid and not expired. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 1991.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to locally cache revocation data (CRLs and/or OCSP responses) to support path discovery and validation in case of inability to access revocation information via the network. The organization conducting the inspection/assessment examines the information system to ensure that revocation data is cached for all PKIs serving known or anticipated users of the information system. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured a process for the information system to refresh cached revocation data prior to the datas expiration. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 1991.'),
('001992','draft','2013-05-03','DISA FSO','policy','The organization defines the personnel or roles responsible for authorizing the organization^s registration authority accountable for the authenticator registration process.','IA-5(3).1','The DoD PKI Registration Authority (RA) Local Registration Authority (LRA) Certification Practice Statement (CPS) defines the nomination process for DoD PKI RAs. The NSS PKI DoD Registration Practice Statement (RPS) defines the nomination process for NSS PKI RAs for DoD.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI RA-LRA CPS and NSS PKI DoD RPS.','The DoD PKI RALRA CPS defines the nomination process for DoD PKI RAs. The NSS PKI DoD RPS defines the nomination process for NSS PKI RAs for DoD.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI RA-LRA CPS and NSS PKI DoD RPS.'),
('001993','draft','2013-05-03','DISA FSO','policy','The organization defines the registration authority accountable for the authenticator registration process.','IA-5(3).2','The DoD PKI Certificate Policy (CP) defines the role and responsibilities of a DoD PKI Registration Authority (RA). The NSS PKI CP defines the role and responsibilities of an NSS PKI RA.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI CP and NSS PKI CP.','The DoD PKI CP defines the role and responsibilities of a DoD PKI Registration Authority (RA). The NSS PKI CP defines the role and responsibilities of an NSS PKI RA.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI CP and NSS PKI CP.'),
('001994','draft','2013-05-03','DISA FSO','policy','The organization defines the types of and/or specific authenticators that are subject to the authenticator registration process.','IA-5(3).3','The DoD PKI Certificate Policy (CP) defines DoD PKI subscribers (entities identified as the subject of PKI certificates) and the authentication requirements for issuance of credentials to subscribers. The NSS PKI CP defines NSS PKI subscribers and the authentication requirements for issuance of credentials to subscribers.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI CP and NSS PKI CP.','The DoD PKI CP defines DoD PKI subscribers and the authentication requirements for issuance of credentials to subscribers. The NSS PKI CP defines NSS PKI subscribers and the authentication requirements for issuance of credentials to subscribers.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI CP and NSS PKI CP.'),
('001995','draft','2013-05-03','DISA FSO','policy','The organization requires that the registration process, to receive organization-defined types of and/or specific authenticators, be conducted in person, or by a trusted third-party, before an organization-defined registration authority with authorization by organization-defined personnel or roles.','IA-5(3).4','The DoD PKI Certificate Policy (CP) requires in-person authentication of DoD PKI applicants in accordance with each Certificate Management Authoritys (CMAs) Certification Practice Statement (CPS) prior to issuance of credentials. The NSS PKI CP requires in-person authentication of NSS PKI applicants by a Registration Authority (RA) or Trusted Agent (TA) prior to issuance of credentials.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI CP and NSS PKI CP.','The DoD PKI CP requires in-person authentication of DoD PKI applicants in accordance with each CMAs CPS prior to issuance of credentials. The NSS PKI CP requires in-person authentication of NSS PKI applicants by an RA or TA prior to issuance of credentials.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD PKI CP and NSS PKI CP.'),
('001996','draft','2013-05-03','DISA FSO','policy','The organization defines the requirements required by the automated tools to determine if password authenticators are sufficiently strong.','IA-5(4).1','DoD has defined the requirements as the complexity as identified in IA-5 (1) Part A.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the requirements as the complexity as identified in IA-5 (1) Part A.'),
('001997','draft','2013-05-03','DISA FSO','policy','The organization employs automated tools to determine if password authenticators are sufficiently strong to satisfy organization-defined requirements.','IA-5(4).2','The organization being inspected/assessed implements automated tools to check passwords strength per the complexity requirements defined in IA-5 (1) Part A.','The organization conducting the inspection/assessment examines the automated tools and inspects the configuration of the automated tools to ensure that they are implemented to check password strength per the complexity requirements defined in IA-5 (1) Part A.'),
('001998','draft','2013-05-03','DISA FSO','policy','The organization requires developers/installers of information system components to provide unique authenticators or change default authenticators prior to delivery/installation.','IA-5.11','The organization being inspected/assessed implements administrative procedures for revoking authenticators as documented in IA-5, CCI 1984.','The organization conducting the inspection/assessment obtains and examines documented procedures for revoking authenticators to ensure that the organization being inspected/assessed implements the process as defined in IA-5, CCI 1984.'),
('001999','draft','2013-05-03','DISA FSO','policy','The organization defines the external organizations to be coordinated with for cross-organization management of credentials.','IA-5(9).2','DoD has defined the external organizations as any external organization that shares cross-organizational identifiers.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the external organizations as any external organization that shares cross-organizational identifiers.'),
('002000','draft','2013-05-03','DISA FSO','policy','The organization coordinates with organization-defined external organizations for cross-organization management of credentials.','IA-5(9).1','The organization being inspected/assessed documents and implements a process to coordinate with external organizations defined in IA-5 (9), CCI 1999 for cross-organization management of credentials. The organization maintains records of coordination.','The organization conducting the inspection/assessment obtains and examines the documented process and a sampling of coordination records to ensure the organization being inspected/assessed coordinates with external organizations defined in IA-5 (9), CCI 1999 for cross-organization management of credentials.'),
('002001','draft','2013-05-03','DISA FSO','technical','The information system dynamically provisions identities.','IA-5(10).1','The organization being inspected/assessed configures the information system to dynamically provision identities. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2001.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to dynamically provision identities. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2001.'),
('002002','draft','2013-05-03','DISA FSO','policy','The organization defines the token quality requirements to be employed by the information system mechanisms for token-based authentication.','IA-5(11).1','DoDI 8520.03 defines types of authentication credentials that are acceptable for authentication to different systems based on the systems information sensitivity levels and the users access environments. The definitions for credential strengths D, E and H found in DoDI 8520.03 Enclosure 3, Section 3 specifically deal with acceptable types of hardware PKI credentials.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD-level policy, DoDI 8520.03.','DoDI 8520.03 defines types of authentication credentials that are acceptable for authentication to different systems based on the systems information sensitivity levels and the users access environments. The definitions for credential strengths D, E and H found in DoDI 8520.03 Enclosure 3, Section 3 specifically deal with acceptable types of hardware PKI credentials.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD-level policy, DoDI 8520.03.'),
('002003','draft','2013-05-03','DISA FSO','technical','The information system, for token-based authentication, employs mechanisms that satisfy organization-defined token quality requirements.','IA-5(11).2','The information system performing hardware token-based authentication must be configured to accept only DoD-approved PKI credentials in accordance with DoDI 8520.02 and DoDI 8520.03. For unclassified systems, DoD-approved PKI credentials include DoD PKI credentials, External Certification Authority (ECA) PKI credentials, and DoD-approved external PKI credentials. For SIPRNet, DoD-approved PKI credentials include DoD PKI credentials and NSS PKI credentials. If the information system accepts DoD-approved external PKI credentials, the information system must be configured to accept only certificates at approved assurance levels, as represented by the Certificate Policy Object Identifiers (OIDs) asserted in the certificate. The current list of DoD-approved external PKIs and acceptable Object Identifiers (OIDs) for each approved external PKI is available at http://iase.disa.mil/pki-pke/interoperability.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to accept only DoD-approved PKI credentials in accordance with (IAW) DoDI 8520.02 and DoDI 8520.03. If the information system accepts DoD-approved external PKI credentials, the organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to accept only DoD-approved external PKI credentials that assert an approved Certificate Policy OID and reject credentials issued off of DoD-approved external PKIs that do not assert an approved OID.'),
('002004','draft','2013-05-03','DISA FSO','policy','The organization defines the biometric quality requirements to be employed by the information system mechanisms for biometric-based authentication.','IA-5(12).1','The organization being inspected/assessed defines and documents quality requirements to be employed by the information system mechanisms. Quality requirements shall include minimum requirements for accurate identification. NIST has draft documentation for biometrics available at http://csrc.nist.gov/publications/PubsSPs.html. DoD has determined the biometric quality requirements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines documented requirements to ensure they have been defined and include minimum requirements for accurate identification. DoD has determined the biometric quality requirements are not appropriate to define at the Enterprise level.'),
('002005','draft','2013-05-03','DISA FSO','technical','The information system, for biometric-based authentication, employs mechanisms that satisfy organization-defined biometric quality requirements.','IA-5(12).2','The organization being inspected/assessed configures the information system to employ mechanisms that satisfy biometric quality requirements as defined in IA-5 (12), CCI 2004 for biometric-based authentication. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2005.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ mechanisms that satisfy biometric quality requirements as defined in IA-5 (12), CCI 2004 for biometric-based authentication. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2005.'),
('002006','draft','2013-05-03','DISA FSO','policy','The organization defines the time period after which the use of cached authenticators is prohibited.','IA-5(13).1','The organization being inspected/assessed defines and documents the time period after which the use of cached authenticators are prohibited. DoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure it has been defined. DoD has determined the time period is not appropriate to define at the Enterprise level.'),
('002007','draft','2013-05-03','DISA FSO','technical','The information system prohibits the use of cached authenticators after an organization-defined time period.','IA-5(13).2','The organization being inspected/assessed configures the information system to prohibit the use of cached authenticators after an organization defined time period. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2007.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prohibit the use of cached authenticators after an organization defined time period. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2007.'),
('002008','draft','2013-05-03','DISA FSO','policy','The organization, for PKI-based authentication, employs a deliberate organization-wide methodology for managing the content of PKI trust stores installed across all platforms including networks, operating systems, browsers, and applications.','IA-5(14).1','DoD trust store management requirements are defined in information system components applicable STIGs and SRGs. All information systems are required to undergo a STIG compliance review as part of their certification and accreditation process prior to being granted an authority to operate.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD-level STIGs and SRGs.','DoD trust store management requirements are defined in information system components applicable STIGs and SRGs. All information systems are required to undergo a STIG compliance review as part of their certification and accreditation process prior to being granted an authority to operate.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD-level STIGs and SRGs.'),
('002009','draft','2013-05-03','DISA FSO','technical','The information system accepts Personal Identity Verification (PIV) credentials from other federal agencies.','IA-8(1).1','The information system performing hardware token-based authentication must be configured to accept DoD-approved external PKI PIV credentials to authenticate federal agency users in accordance with DoDI 8520.02 and DoDI 8520.03. The information system must be configured to accept only certificates at approved assurance levels, as represented by the Certificate Policy Object Identifiers (OIDs) asserted in the certificate. The current list of DoD-approved external PKIs and acceptable Object Identifiers (OIDs) for each approved external PKI is available at http://iase.disa.mil/pki-pke/interoperability. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2009.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to accept DoD-approved external PKI PIV credentials in accordance with DoDI 8520.02 and DoDI 8520.03. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to accept only DoD-approved external PKI PIV credentials that assert an approved Certificate Policy OID and reject credentials issued off of DoD-approved external PKIs that do not assert an approved OID. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2009.'),
('002010','draft','2013-05-03','DISA FSO','technical','The information system electronically verifies Personal Identity Verification (PIV) credentials from other federal agencies.','IA-8(1).2','The information system performing hardware token-based authentication must be configured to validate DoD-approved external PKI PIV credentials to authenticate federal agency users in accordance with RFC 5280. The information system must be configured to perform a revocation check as part of the certificate validation process. Revocation checking may be performed using certificate revocation lists (CRLs) published by the issuing PKI or Online Certificate Status Protocol (OCSP) services. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2010.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to validate DoD-approved external PKI PIV credentials in accordance with RFC 5280. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to perform a revocation check as part of the certificate validation process. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2010.'),
('002011','draft','2013-05-03','DISA FSO','technical','The information system accepts FICAM-approved third-party credentials.','IA-8(2).1','The organization being inspected/assessed configures the information system to accept Federal Identity, Credential, and Access Management (FICAM)-approved third-party credentials. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2011. FICAM Guidance is available at http://www.idmanagement.gov.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to accept FICAM-approved third-party credentials For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2011.'),
('002012','draft','2013-05-03','DISA FSO','policy','The organization defines the information systems which will employ only FICAM-approved information system components.','IA-8(3).1','The organization being inspected/assessed defines and documents the information systems which will employ only Federal Identity, Credential, and Access Management (FICAM)-approved information system components. DoD has determined the information systems are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems to ensure they have been defined. DoD has determined the information systems are not appropriate to define at the Enterprise level.'),
('002013','draft','2013-05-03','DISA FSO','policy','The organization employs only FICAM-approved information system components in organization-defined information systems to accept third-party credentials.','IA-8(3).2','The organization being inspected/assessed employs only Federal Identity, Credential, and Access Management (FICAM)-approved information system components to accept third-party credentials in information systems defined in IA-8 (3), CCI 2012. FICAM Guidance is available at http://www.idmanagement.gov.','The organization conducting the inspection/assessment obtains and examines the list of information system components in use to ensure the organization being inspected/assessed uses only FICAM-approved components in information systems defined in IA-8 (3), CCI 2012.'),
('002014','draft','2013-05-03','DISA FSO','technical','The information system conforms to FICAM-issued profiles.','IA-8(4).1','The organization being inspected/assessed configures the information system to conform to Federal Identity, Credential, and Access Management (FICAM)-issued profiles. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2014. FICAM Guidance is available at http://www.idmanagement.gov.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to conform to FICAM-issued profiles. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2014.'),
('002015','draft','2013-05-03','DISA FSO','technical','The information system accepts Personal Identity Verification-I (PIV-I) credentials.','IA-8(5).1','The information system performing hardware token-based authentication must be configured to accept DoD-approved external PKI PIV-I credentials in accordance with DoDI 8520.02, DoDI 8520.03, and DoD CIO Memorandum Department of Defense Requirements for Accepting Non-Federally Issued Identity Credentials dated 24 January 2013. The information system must be configured to accept only certificates at approved assurance levels, as represented by the Certificate Policy Object Identifiers (OIDs) asserted in the certificate. The current list of DoD-approved external PKIs and acceptable Object Identifiers (OIDs) for each approved external PKI is available at http://iase.disa.mil/pki-pke/interoperability. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2015.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to accept DoD-approved external PKI PIV-I credentials in accordance with DoDI 8520.02, DoDI 8520.03, and DoD CIO Memorandum Department of Defense Requirements for Accepting Non-Federally Issued Identity Credentials dated 24 January 2013. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to accept only DoD-approved external PKI PIV-I credentials that assert an approved Certificate Policy OID and reject credentials issued off of DoD-approved external PKIs that do not assert an approved OID. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2015.'),
('002016','draft','2013-05-03','DISA FSO','technical','The information system electronically verifies Personal Identity Verification-I (PIV-I) credentials.','IA-8(5).2','The information system performing hardware token-based authentication must be configured to validate DoD-approved external PKI PIV-I credentials in accordance with RFC 5280. The information system must be configured to perform a revocation check as part of the certificate validation process. Revocation checking may be performed using certificate revocation lists (CRLs) published by the issuing PKI or Online Certificate Status Protocol (OCSP) services. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2016.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to validate DoD-approved external PKI PIV-I credentials in accordance with RFC 5280. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed has configured the information system to perform a revocation check as part of the certificate validation process. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2016.'),
('002017','draft','2013-05-03','DISA FSO','policy','The organization defines the information system services requiring identification.','IA-9.1','The organization being inspected/assessed defines and documents the information system services requiring identification. DoD has determined the information system services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system services to ensure they have been defined. DoD has determined the information system services are not appropriate to define at the Enterprise level.'),
('002018','draft','2013-05-03','DISA FSO','policy','The organization defines the information system services requiring authentication.','IA-9.2','The organization being inspected/assessed defines and documents the information system services requiring authentication. DoD has determined the information system services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system services to ensure they have been defined. DoD has determined the information system services are not appropriate to define at the Enterprise level.'),
('002019','draft','2013-05-03','DISA FSO','policy','The organization defines the security safeguards to be used when identifying information system services.','IA-9.3','The organization being inspected/assessed defines and documents the security safeguards to be used when identifying information system services. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure they have been defined and offers sufficient security. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002020','draft','2013-05-03','DISA FSO','policy','The organization defines the security safeguards to be used when authenticating information system services.','IA-9.4','The organization being inspected/assessed defines and documents the security safeguards to be used when authenticating information system services. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure they have been defined and offers sufficient security. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002021','draft','2013-05-03','DISA FSO','policy','The organization identifies organization-defined information system services using organization-defined security safeguards.','IA-9.5','The organization being inspected/assessed documents and implements a process to identify information system services defined in IA-9, CCIs 2017 & 2018 using security safeguards defined in IA-9, CCIs 2019-2020.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed identifies information system services defined in IA-9, CCIs 2017 & 2018 using security safeguards defined in IA-9, CCIs 2019-2020.'),
('002022','draft','2013-05-03','DISA FSO','policy','The organization authenticates organization-defined information system services using organization-defined security safeguards.','IA-9.6','The organization being inspected/assessed documents and implements a process to authenticate information system services defined in IA-9, CCIs 2017 & 2018 using security safeguards defined in IA-9, CCIs 2019-2020.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed authenticates information system services defined in IA-9, CCIs 2017 & 2018 using security safeguards defined in IA-9, CCIs 2019-2020.'),
('002023','draft','2013-05-03','DISA FSO','policy','The organization ensures that service providers receive identification information.','IA-9(1).1','The organization being inspected/assessed implements a process to ensure that service providers receive identification information.','The organization conducting the inspection/assessment reviews the process to ensure that service providers receive identification information to ensure the process is effectively implemented.'),
('002024','draft','2013-05-03','DISA FSO','policy','The organization ensures that service providers validate identification information.','IA-9(1).2','The organization being inspected/assessed implements a process to ensure that service providers validate identification information.','The organization conducting the inspection/assessment reviews the process to ensure that service providers validate identification information to ensure the process is effectively implemented.'),
('002025','draft','2013-05-03','DISA FSO','policy','The organization ensures that service providers transmit identification information.','IA-9(1).3','The organization being inspected/assessed implements a process to ensure that service providers transmit identification information.','The organization conducting the inspection/assessment reviews the process to ensure that service providers transmit identification information to ensure the process is effectively implemented.'),
('002026','draft','2013-05-03','DISA FSO','policy','The organization ensures that service providers receive authentication information.','IA-9(1).4','The organization being inspected/assessed implements a process to ensure that service providers receive authentication information.','The organization conducting the inspection/assessment reviews the process to ensure that service providers receive authentication information to ensure the process is effectively implemented.'),
('002027','draft','2013-05-03','DISA FSO','policy','The organization ensures that service providers validate authentication information.','IA-9(1).5','The organization being inspected/assessed implements a process to ensure that service providers validate authentication information.','The organization conducting the inspection/assessment reviews the process to ensure that service providers validate authentication information to ensure the process is effectively implemented. .'),
('002028','draft','2013-05-03','DISA FSO','policy','The organization ensures that service providers transmit authentication information.','IA-9(1).6','The organization being inspected/assessed implements a process to ensure that service providers transmit authentication information.','The organization conducting the inspection/assessment reviews the process to ensure that service providers transmit authentication information to ensure the process is effectively implemented.'),
('002029','draft','2013-05-03','DISA FSO','policy','The organization defines the services between which identification decisions are to be transmitted.','IA-9(2).1','The organization being inspected/assessed defines and documents the services between which identification decisions are to be transmitted. DoD has determined the services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented services to ensure they have been defined. DoD has determined the services are not appropriate to define at the Enterprise level.'),
('002030','draft','2013-05-03','DISA FSO','policy','The organization defines the services between which authentication decisions are to be transmitted.','IA-9(2).2','The organization being inspected/assessed defines and documents the services between which authentication decisions are to be transmitted. DoD has determined the services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented services to ensure they have been defined. DoD has determined the services are not appropriate to define at the Enterprise level.'),
('002031','draft','2013-05-03','DISA FSO','policy','The organization ensures that identification decisions are transmitted between organization-defined services consistent with organizational policies.','IA-9(2).3','The organization being inspected/assessed implements a process to ensure that identification decisions are transmitted between services defined in IA-9 (2), CCI 2029 consistent with organizational policies.','The organization conducting the inspection/assessment reviews the process to ensure the organization being inspected/assessed implements policies for transmitting identification decisions between services defined in IA-9 (2), CCI 2029.'),
('002032','draft','2013-05-03','DISA FSO','policy','The organization ensures that authentication decisions are transmitted between organization-defined services consistent with organizational policies.','IA-9(2).4','The organization being inspected/assessed implements a process to ensure that authentication decisions are transmitted between services defined in IA-9 (2), CCI 2030 consistent with organizational policies.','The organization conducting the inspection/assessment reviews the process to ensure the organization being inspected/assessed implements policies for transmitting authentication decisions between services defined in IA-9 (2), CCI 2030.'),
('002033','draft','2013-05-03','DISA FSO','policy','The organization defines the specific circumstances or situations when individuals accessing an information system employ organization-defined supplemental authentication techniques or mechanisms.','IA-10.1','The organization being inspected/assessed defines and documents the specific circumstances or situations when individuals accessing an information system employ organization-defined supplemental authentication techniques or mechanisms. DoD has determined the circumstances or situations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances or situations to ensure they have been defined. DoD has determined the circumstances or situations are not appropriate to define at the Enterprise level.'),
('002034','draft','2013-05-03','DISA FSO','policy','The organization defines the supplemental authentication techniques or mechanisms to be employed in specific organization-defined circumstances or situations by individuals accessing the information system.','IA-10.2','The organization being inspected/assessed defines and documents the supplemental authentication techniques or mechanisms to be employed in specific organization-defined circumstances or situations by individuals accessing the information system. DoD has determined the supplemental authentication techniques or mechanisms are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented supplemental authentication techniques or mechanisms to ensure they have been defined. DoD has determined the supplemental authentication techniques or mechanisms are not appropriate to define at the Enterprise level.'),
('002035','draft','2013-05-03','DISA FSO','policy','The organization requires that individuals accessing the information system employ organization-defined supplemental authentication techniques or mechanisms under specific organization-defined circumstances or situations.','IA-10.3','The organization being inspected/assessed implements a process to require that individuals accessing the information system employ supplemental authentication techniques or mechanisms defined in IA-10, CCI 2034 under specific circumstances or situations defined in IA-10, CCI 2033.','The organization conducting the inspection/assessment reviews the process to ensure the organization being inspected/assessed requires that individuals accessing the information system employ supplemental authentication techniques or mechanisms defined in IA-10, CCI 2034 under specific circumstances or situations defined in IA-10, CCI 2033.'),
('002036','draft','2013-05-03','DISA FSO','policy','The organization defines the circumstances or situations under which users will be required to reauthenticate.','IA-11.1','The organization being inspected/assessed defines and documents the circumstances or situations when users will be required to reauthenticate. DoD has determined the circumstances or situations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances or situations to ensure they have been defined. DoD has determined the circumstances or situations are not appropriate to define at the Enterprise level.'),
('002037','draft','2013-05-03','DISA FSO','policy','The organization defines the circumstances or situations under which devices will be required to reauthenticate.','IA-11.2','The organization being inspected/assessed defines and documents the circumstances or situations when devices will be required to reauthenticate. DoD has determined the circumstances or situations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances or situations to ensure they have been defined. DoD has determined the circumstances or situations are not appropriate to define at the Enterprise level.'),
('002038','draft','2013-05-03','DISA FSO','technical','The organization requires users to reauthenticate upon organization-defined circumstances or situations requiring reauthentication.','IA-11.3','The organization being inspected/assessed implements a process to require users to reauthenticate when circumstances or situations requiring reauthentication as defined in IA-11, CCI 2036.','The organization conducting the inspection/assessment reviews the process to ensure the organization being inspected/assessed requires users to reauthenticate when circumstances or situations requiring reauthentication as defined in IA-11, CCI 2036.'),
('002039','draft','2013-05-03','DISA FSO','technical','The organization requires devices to reauthenticate upon organization-defined circumstances or situations requiring reauthentication.','IA-11.4','The organization being inspected/assessed implements a process to require devices to reauthenticate when circumstances or situations requiring reauthentication as defined in IA-11, CCI 2037.','The organization conducting the inspection/assessment reviews the process to ensure the organization being inspected/assessed requires devices to reauthenticate when circumstances or situations requiring reauthentication as defined in IA-11, CCI 2037.'),
('002040','draft','2013-05-03','DISA FSO','policy','The organization requires that the registration process to receive an individual identifier includes supervisor authorization.','IA-4(2).1','The organization being inspected/assessed documents and implements a process that requires supervisor authorization to assign individual identifiers.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires supervisor authorization to assign individual identifiers.'),
('002041','draft','2013-05-03','DISA FSO','technical','The information system allows the use of a temporary password for system logons with an immediate change to a permanent password.','IA-5(1).20','The organization being inspected/assessed configures the information system to allow the use of a temporary password for system logons with an immediate change to a permanent password. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2041.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to allow the use of a temporary password for system logons with an immediate change to a permanent password. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2041.'),
('002042','draft','2013-05-03','DISA FSO','policy','The organization manages information system authenticators by protecting authenticator content from unauthorized modification.','IA-5.18','The organization being inspected/assessed configures the information system to manage information system authenticators by protecting authenticator content from unauthorized modification. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2042.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to manage information system authenticators by protecting authenticator content from unauthorized modification. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2042.'),
('002043','draft','2013-05-03','DISA FSO','policy','The organization uses only FICAM-approved path discovery and validation products and services.','IA-5(15).1','The organization being inspected/assessed uses only Federal Identity, Credential, and Access Management (FICAM)-approved path discovery and validation products and services. FICAM Guidance is available at http://www.idmanagement.gov.','The organization conducting the inspection/assessment obtains and examines the list of path discovery and validation products and services in use to ensure the organization being inspected/assessed uses only FICAM-approved path discovery and validation products and services.'),
('002044','draft','2013-05-29','DISA FSO','policy','The organization defines measures to be employed to ensure that long-term audit records generated by the information system can be retrieved.','AU-11(1).1','The organization being inspected/assessed defines and documents measures to be employed to ensure that long-term audit records generated by the information system can be retrieved. DoD has determined that the measures are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented measures to ensure the organization being inspected/assessed defines measures to be employed to ensure that long-term audit records generated by the information system can be retrieved. DoD has determined that the measures are not appropriate to define at the Enterprise level.'),
('002045','draft','2013-05-29','DISA FSO','policy','The organization employs organization-defined measures to ensure that long-term audit records generated by the information system can be retrieved.','AU-11(1).2','The organization being inspected/assessed employs the measures defined in AU-11 (1), CCI 2044 to ensure that long-term audit records generated by the information system can be retrieved.','The organization conducting the inspection/assessment obtains and examines the documented measures to ensure the organization being inspected/assessed employs the measures defined in AU-11 (1), CCI 2044 to ensure that long-term audit records generated by the information system can be retrieved.'),
('002046','draft','2013-05-29','DISA FSO','technical','The information system synchronizes the internal system clocks to the authoritative time source when the time difference is greater than the organization-defined time period.','AU-8(1).5','The organization being inspected/assessed configures the information system to synchronize the internal system clocks to the authoritative time source when the time difference is greater than the time period defined in AU-8 (1), CCI 1892.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2046.','The organization conducting the inspection/assessment examines the information system to ensure the system synchronizes the internal system clocks to the authoritative time source when the time difference is greater than the time period defined in AU-8 (1), CCI 1892.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2046.'),
('002047','draft','2013-05-29','DISA FSO','policy','The organization defines the information system components on which the auditing that is to be performed can be changed by organization-defined individuals or roles.','AU-12(3).5','The organization being inspected/assessed defines and documents the information system components on which the auditing that is to be performed can be changed by individuals or roles defined in AU-12 (3), CCI 1913. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed has defined the information system components on which the auditing that is to be performed can be changed by the individuals or roles defined in AU-12 (3), CCI 1913. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002048','draft','2013-06-05','DISA FSO','policy','The organization defines the personnel or roles to whom the security awareness and training policy is disseminated.','AT-1.1','DoD has defined the roles as organizational personnel with security awareness and training responsibilities.\n\nDoD disseminates DoDD 8570.01 organization-wide via the DoD Issuances website.\nhttp://www.dtic.mil/whs/directives/corres/dir.html','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as organizational personnel with security awareness and training responsibilities.'),
('002049','draft','2013-06-05','DISA FSO','policy','The organization defines the personnel or roles to whom the security awareness and training procedures are disseminated.','AT-1.2','DoD has defined the roles as organizational personnel with security awareness and training responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as organizational personnel with security awareness and training responsibilities.'),
('002050','draft','2013-06-05','DISA FSO','policy','The organization defines the personnel or roles to whom initial and refresher training in the employment and operation of environmental controls is to be provided.','AT-3(1).4','The organization being inspected/assessed defines and documents the personnel or roles to whom initial and refresher training in the employment and operation of environmental controls is to be provided. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to whom initial and refresher training in the employment and operation of environmental controls is to be provided. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002051','draft','2013-06-05','DISA FSO','policy','The organization defines the personnel or roles to whom initial and refresher training in the employment and operation of physical security controls is to be provided.','AT-3(2).4','The organization being inspected/assessed defines and documents the personnel or roles to whom initial and refresher training in the employment and operation of physical security controls is to be provided. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to whom initial and refresher training in the employment and operation of physical security controls is to be provided. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002052','draft','2013-06-05','DISA FSO','policy','The organization includes practical exercises in security training that reinforce training objectives.','AT-3(3).1','The organization being inspected/assessed includes practical exercises in security training that reinforce training objectives.','The organization conducting the inspection/assessment obtains and examines the security training materials to ensure the organization being inspected/assessed includes practical exercises in security training that reinforce training objectives.'),
('002053','draft','2013-06-05','DISA FSO','policy','The organization provides training to its personnel on organization-defined indicators of malicious code to recognize suspicious communications and anomalous behavior in organizational information systems.','AT-3(4).1','The organization being inspected/assessed provides training to its personnel on indicators of malicious code defined in AT-3 (4), CCI 2054 to recognize suspicious communications and anomalous behavior in organizational information systems.','The organization conducting the inspection/assessment obtains and examines the training materials and indicators of malicious code defined in AT-3 (4), CCI 2054 to ensure the organization being inspected/assessed provides users with the means to recognize suspicious communications and anomalous behavior in organizational information systems.'),
('002054','draft','2013-06-05','DISA FSO','policy','The organization defines indicators of malicious code to recognize suspicious communications and anomalous behavior in organizational information systems.','AT-3(4).2','The organization being inspected/assessed defines and documents indicators of malicious code to recognize suspicious communications and anomalous behavior in organizational information systems. DoD has determined the indicators are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented indicators to ensure the organization being inspected/assessed defines indicators of malicious code to recognize suspicious communications and anomalous behavior in organizational information systems. DoD has determined the indicators are not appropriate to define at the Enterprise level.'),
('002055','draft','2013-06-05','DISA FSO','policy','The organization includes security awareness training on recognizing and reporting potential indicators of insider threat.','AT-2(2).1','The IA Awareness CBT, \"Cyber Awareness Challenge,\" and Virtual Training Environment (VTE) Courses: \"Introduction to Insider Threat\" and \"Monitoring for Insider Threat\" available on the IASE website meet the DoD requirement to include security awareness training on recognizing and reporting potential indicators of insider threat.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level training available on the IASE website.','The IA Awareness CBT, \"Cyber Awareness Challenge,\" and Virtual Training Environment (VTE) Courses: \"Introduction to Insider Threat\" and \"Monitoring for Insider Threat\" available on the IASE website meet the DoD requirement to include security awareness training on recognizing and reporting potential indicators of insider threat.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level training available on the IASE website.'),
('002056','draft','2013-06-11','DISA FSO','policy','The organization defines the time period the records of configuration-controlled changes are to be retained.','CM-3.7','DoD has defined the time period as a time period defined by the organization\'s CCB.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the time period as a time period defined by the organization\'s CCB.'),
('002057','draft','2013-06-11','DISA FSO','policy','The organization defines the personnel to be notified when approved changes to the information system are completed.','CM-3(1).8','The organization being inspected/assessed defines and documents the personnel to be notified when approved changes to the information system are completed, which must include, at a minimum, the CCB. DoD has defined the personnel as at a minimum, the CCB.','The organization conducting the inspection/assessment obtains and examines the documented personnel to ensure the organization being inspected/assessed defines the personnel to be notified when approved changes to the information system are completed, which must include, at a minimum, the CCB. DoD has defined the personnel as at a minimum, the CCB.'),
('002058','draft','2013-06-11','DISA FSO','policy','The organization employs automated mechanisms to notify organization-defined personnel when approved changes to the information system are completed.','CM-3(1).9','The organization being inspected/assessed notifies at a minimum, the CCB when approved changes to the information system are completed. The organization must maintain an audit trail of notifications of completed changes to the information system. DoD has defined the personnel as at a minimum, the CCB.','The organization conducting the inspection/assessment obtains and examines the audit trail of notifications of completed changes to the information system to ensure the organization being inspected/assessed notifies at a minimum, the CCB when approved changes to the information system are completed. DoD has defined the personnel as at a minimum, the CCB. '),
('002059','draft','2013-06-11','DISA FSO','policy','The organization defines the information system components for which the organization will employ automated mechanisms to centrally manage, apply, and verify configuration settings.','CM-6(1).4','The organization being inspected/assessed defines and documents the information system components for which the organization will employ automated mechanisms to centrally manage, apply, and verify configuration settings. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examine the documented information system components to ensure the organization being inspected/assessed defines the information system components for which the organization will employ automated mechanisms to centrally manage, apply, and verify configuration settings. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002060','deprecated','2013-06-21','DISA FSO','policy','The organization develops and documents a security assessment and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.',NULL,NULL,NULL),
('002061','draft','2013-06-21','DISA FSO','policy','The organization defines the personnel or roles to whom security assessment and authorization policy is to be disseminated.','CA-1.1','DoD has defined the personnel or roles as all personnel. DoD disseminates DoDI 8510.01 organization-wide via the DoD Issuances website. http://www.dtic.mil/whs/directives/corres/ins1.html','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all personnel.'),
('002062','draft','2013-06-21','DISA FSO','policy','The organization defines the personnel or roles to whom the security assessment and authorization procedures are to be disseminated.','CA-1.2','DoD has defined the personnel or roles as all personnel.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all personnel.'),
('002063','draft','2013-06-21','DISA FSO','policy','The organization defines the level of independence for assessors or assessment teams to conduct security control assessments of organizational information systems.','CA-2(1).2','The organization being inspected/assessed defines and documents the level of independence for assessors or assessment teams to conduct security control assessments of organizational information systems. DoD has determined the level of independence is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of independence to ensure the organization being inspected/assessed defines the level of independence for assessors or assessment teams to conduct security control assessments of organizational information systems. DoD has determined the level of independence is not appropriate to define at the Enterprise level.'),
('002064','draft','2013-06-21','DISA FSO','policy','The organization selects one or more security assessment techniques to be conducted.','CA-2(2).4','The organization being inspected/assessed selects and documents one or more security assessment techniques to be conducted. Techniques include in-depth monitoring; vulnerability scanning; malicious user testing; insider threat assessment and performance/load testing, as well as any other techniques identified in CA-2 (2), CCI 1582. DoD has determined the other forms of security assessments are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the selected list of assessment techniques that are to be conducted to ensure the selections have been documented.'),
('002065','draft','2013-06-21','DISA FSO','policy','The organization defines the frequency at which to conduct security control assessments.','CA-2(2).5','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually.'),
('002066','draft','2013-06-21','DISA FSO','policy','The organization accepts the results of an assessment of the organization-defined information system performed by an organization-defined external organization when the assessment meets organization-defined requirements.','CA-2(3).1','The organization being inspected/assessed accepts the results of an assessment of the information system defined in CA-2 (3), CCI 2067 performed by external organization defined in CA-2 (3), CCI 2068 when the assessment meets requirements defined in CA-2 (3), CCI 2069. The organization must maintain records of acceptance or rejection of external organization assessment results.','The organization conducting the inspection/assessment obtains and examines a sampling of records of acceptance or rejection of external organization assessment results to ensure the organization being inspected/assessed accepts the results of an assessment of the information system defined in CA-2 (3), CCI 2067 performed by external organization defined in CA-2 (3), CCI 2068 when the assessment meets requirements defined in CA-2 (3), CCI 2069.'),
('002067','draft','2013-06-21','DISA FSO','policy','The organization defines the information systems for which they will accept the results of an assessment performed by an external organization.','CA-2(3).2','The organization being inspected/assessed defines and documents the information systems for which they will accept the results of an assessment performed by an external organization. DoD has determined the information systems are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems to ensure the organization being inspected/assessed defines the information systems for which they will accept the results of an assessment performed by an external organization. DoD has determined the information systems are not appropriate to define at the Enterprise level.'),
('002068','draft','2013-06-21','DISA FSO','policy','The organization defines the external organizations from which assessment results for organization-defined information systems will be accepted.','CA-2(3).3','The organization being inspected/assessed defines and documents the external organizations from which assessment results for organization-defined information systems will be accepted. DoD has determined the external organizations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented external organizations to ensure the organization being inspected/assessed defines the external organizations from which assessment results for organization-defined information systems will be accepted. DoD has determined the external organizations are not appropriate to define at the Enterprise level.'),
('002069','draft','2013-06-21','DISA FSO','policy','The organization defines the requirements the assessments for organization-defined information systems from organization-defined external organizations must meet.','CA-2(3).4','The organization being inspected/assessed defines and documents the requirements the assessments for organization-defined information systems from organization-defined external organizations must meet. DoD has determined the requirements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examine the documented requirements to ensure the organization being inspected/assessed defines the requirements the assessments for organization-defined information systems from organization-defined external organizations must meet. DoD has determined the requirements are not appropriate to define at the Enterprise level.'),
('002070','draft','2013-06-21','DISA FSO','policy','The organization^s security assessment plan describes the assessment team, and assessment roles and responsibilities.','CA-2.5','The organization being inspected/assessed lists their assessment team members and their associated assessment roles and responsibilities in the security assessment plan.','The organization conducting the inspection/assessment obtains and examines the security assessment plan to ensure the organization being inspected/assessed lists their assessment team members and their associated assessment roles and responsibilities in the security assessment plan.'),
('002071','draft','2013-06-21','DISA FSO','policy','The organization defines the individuals or roles to whom the results of the security control assessment are to be provided.','CA-2.10','DoD has defined the individuals or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the individuals or roles as at a minimum, the ISSO and ISSM.'),
('002072','draft','2013-06-21','DISA FSP','policy','The organization defines the unclassified, national security systems that are prohibited from directly connecting to an external network without the use of an organization-defined boundary protection device.','CA-3(1).2','DoD has defined the unclassified, national security systems as all unclassified NSS.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the unclassified, national security systems as all unclassified NSS.'),
('002073','draft','2013-06-21','DISA FSO','policy','The organization defines the boundary protection device to be used to connect organization-defined unclassified, national security systems to an external network.','CA-3(1).3','The organization being inspected/assessed defines and documents the boundary protection device to be used to connect organization-defined unclassified, national security systems to an external network. DoD has determined the boundary protection device is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented boundary protection device to ensure the organization being inspected/assessed defines the boundary protection device to be used to connect organization-defined unclassified, national security systems to an external network. DoD has determined the boundary protection device is not appropriate to define at the Enterprise level.'),
('002074','draft','2013-06-21','DISA FSO','policy','The organization defines the boundary protection device to be used for the direct connection of classified, national security system to an external network.','CA-3(2).2','The organization being inspected/assessed defines and documents the boundary protection device to be used for the direct connection of classified, national security system to an external network.\n\nDoD has determined the boundary protection device is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented boundary protection device to ensure the organization being inspected/assessed defines the boundary protection device to be used for the direct connection of classified, national security system to an external network.\n\nDoD has determined the boundary protection device is not appropriate to define at the Enterprise level.'),
('002075','draft','2013-06-21','DISA FSO','policy','The organization prohibits the direct connection of an organization-defined unclassified, non-national security system to an external network without the use of organization-defined boundary protection device.','CA-3(3).1','The organization being inspected/assessed does not connect any national security systems to an external network without the use of protection devices defined in CA-3 (3), CCI 2077.','The organization conducting the inspection/assessment obtains and examines network topology diagrams and examines the information system to ensure the organization being inspected/assessed does not connect any national security systems to an external network without the use of protection devices defined in CA-3 (3), CCI 2077.'),
('002076','draft','2013-06-21','DISA FSO','policy','The organization defines the unclassified, non-national security system that is prohibited from directly connecting to an external network without the use of an organization-defined boundary protection device.','CA-3(3).2','The organization being inspected/assessed defines and documents the unclassified, non-national security system that is prohibited from directly connecting to an external network without the use of an organization-defined boundary protection device. DoD has determined the unclassified, non-national security system is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented unclassified, non-national security system to ensure the organization being inspected/assessed defines the unclassified, non-national security system that is prohibited from directly connecting to an external network without the use of an organization-defined boundary protection device. DoD has determined the unclassified, non-national security system is not appropriate to define at the Enterprise level.'),
('002077','draft','2013-06-21','DISA FSO','policy','The organization defines the boundary protection device to be used to directly connect an organization-defined unclassified, non-national security system to an external network.','CA-3(3).3','The organization being inspected/assessed defines and documents the boundary protection device to be used to directly connect an organization-defined unclassified, non-national security system to an external network. DoD has determined the boundary protection device is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented boundary protection device to ensure the organization being inspected/assessed defines the boundary protection device to be used to directly connect an organization-defined unclassified, non-national security system to an external network. DoD has determined the boundary protection device is not appropriate to define at the Enterprise level.'),
('002078','draft','2013-06-21','DISA FSO','policy','The organization prohibits the direct connection of an organization-defined information system to a public network.','CA-3(4).1','The organization being inspected/assessed does not connect any information system defined in CA-3 (4), CCI 2079 to a public network.','The organization conducting the inspection/assessment obtains and examines network topology diagrams and examines the information system to ensure the organization being inspected/assessed does not connect any information system defined in CA-3 (4), CCI 2079 to a public network.'),
('002079','draft','2013-06-21','DISA FSO','policy','The organization defines the information system that is prohibited from directly connecting to a public network.','CA-3(4).2','The organization being inspected/assessed defines and documents the information system that is prohibited from directly connecting to a public network. DoD has determined the information system is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system to ensure the organization being inspected/assessed defines the information system that is prohibited from directly connecting to a public network. DoD has determined the information system is not appropriate to define at the Enterprise level.'),
('002080','draft','2013-06-21','DISA FSO','policy','The organization employs either an allow-all, deny-by-exception or a deny-all, permit-by-exception policy for allowing organization-defined information systems to connect to external information systems.','CA-3(5).1','The organization being inspected/assessed configures the information system to employ a deny-all, permit by exception policy for allowing any systems requiring external connectivity to connect to external information systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2080. DoD has defined the information systems as any systems requiring external connectivity.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ a deny-all, permit by exception policy for allowing any systems requiring external connectivity to connect to external information systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2080. DoD has defined the information systems as any systems requiring external connectivity.'),
('002081','draft','2013-06-21','DISA FSO','policy','The organization defines the information systems that employ either an allow-all, deny-by-exception or a deny-all, permit-by-exception policy for allowing connections to external information systems.','CA-3(5).2','DoD has defined the information systems as any systems requiring external connectivity.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information systems as any systems requiring external connectivity.'),
('002082','draft','2013-06-21','DISA FSO','policy','The organization selects either an allow-all, deny-by-exception or a deny-all, permit-by-exception policy for allowing organization-defined information systems to connect to external information systems.','CA-3(5).3','The organization being inspected/assessed selects deny-all, permit by exception policy for allowing any systems requiring external connectivity to connect to external information systems. DoD has defined the information systems as any systems requiring external connectivity.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed selects deny-all, permit by exception policy for allowing any systems requiring external connectivity to connect to external information systems. DoD has defined the information systems as any systems requiring external connectivity.'),
('002083','draft','2013-06-21','DISA FSO','policy','The organization reviews and updates Interconnection Security Agreements on an organization-defined frequency.','CA-3.5','The organization being inspected/assessed reviews and updates Interconnection Security Agreements at least annually. The organization must maintain an audit trail of reviews and updates. DoD has defined the frequency as at least annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates Interconnection Security Agreements at least annually. DoD has defined the frequency as at least annually.'),
('002084','draft','2013-06-21','DISA FSO','policy','The organization defines the frequency at which reviews and updates to the Interconnection Security Agreements must be conducted.','CA-3.6','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually.'),
('002085','draft','2013-06-21','DISA FSO','policy','The organization defines the level of independence the assessors or assessment teams must have to monitor the security controls in the information system on an ongoing basis.','CA-7(1).2','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002086','draft','2013-06-21','DISA FSO','policy','The organization employs trend analyses to determine if security control implementations, the frequency of continuous monitoring activities, and/or the types of activities used in the continuous monitoring process need to be modified based on empirical data.','CA-7(3).1','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002087','draft','2013-06-21','DISA FSO','policy','The organization establishes and defines the metrics to be monitored for the continuous monitoring program.','CA-7.2','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002088','draft','2013-06-21','DISA FSO','policy','The organization establishes and defines the frequencies for continuous monitoring.','CA-7.3','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002089','draft','2013-06-21','DISA FSO','policy','The organization establishes and defines the frequencies for assessments supporting continuous monitoring.','CA-7.4','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002090','draft','2013-06-21','DISA FSO','policy','The organization implements a continuous monitoring program that includes ongoing security status monitoring of organization-defined metrics in accordance with the organizational continuous monitoring strategy.','CA-7.6','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002091','draft','2013-06-21','DISA FSO','policy','The organization implements a continuous monitoring program that includes correlation and analysis of security-related information generated by assessments and monitoring.','CA-7.7','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002092','draft','2013-06-21','DISA FSO','policy','The organization implements a continuous monitoring program that includes response actions to address results of the analysis of security-related information.','CA-7.8','Future DoD-wide CM guidance to be published','Future DoD-wide CM guidance to be published'),
('002093','draft','2013-06-21','DISA FSO','policy','The organization conducts penetration testing in accordance with organization-defined frequency on organization-defined information systems or system components.','CA-8.1','The organization being inspected/assessed documents and implements a process to conduct penetration testing in accordance with the frequency defined in CA-8, CCI 2094 on information systems or system components defined in CA-8, CCI 2095. The organization must maintain a record of penetration test results.','The organization conducting the inspection/assessment obtains and examines the documented process as well as a sampling of the penetration test results to ensure the organization being inspected/assessed conducts penetration testing in accordance with the frequency defined in CA-8, CCI 2094 on information systems or system components defined in CA-8, CCI 2095.'),
('002094','draft','2013-06-21','DISA FSO','policy','The organization defines the frequency for conducting penetration testing on organization-defined information systems or system components.','CA-8.2','The organization being inspected/assessed defines and documents the frequency for conducting penetration testing on organization-defined information systems or system components. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency for conducting penetration testing on organization-defined information systems or system components. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('002095','draft','2013-06-21','DISA FSO','policy','The organization defines the information systems or system components on which penetration testing will be conducted.','CA-8.3','The organization being inspected/assessed defines and documents the information systems or system components on which penetration testing will be conducted. DoD has determined the information systems or system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems or system components to ensure the organization being inspected/assessed defines the information systems or system components on which penetration testing will be conducted. DoD has determined the information systems or system components are not appropriate to define at the Enterprise level.'),
('002096','draft','2013-06-21','DISA FSO','policy','The organization employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components.','CA-8(1).1','The organization being inspected/assessed employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components. The organization must maintain a record of penetration test results.','The organization conducting the inspection/assessment obtains and examines a sampling of the penetration test results to ensure the organization being inspected/assessed employs an independent penetration agent or penetration team to perform penetration testing on the information system or system components.'),
('002097','draft','2013-06-21','DISA FSP','policy','The organization defines red team exercises to simulate attempts by adversaries to compromise organizational information systems.','CA-8(2).1','The organization being inspected/assessed defines and documents red team exercises to simulate attempts by adversaries to compromise organizational information systems. DoD has determined the red team exercises are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented red team exercises to ensure the organization being inspected/assessed defines red team exercises to simulate attempts by adversaries to compromise organizational information systems. DoD has determined the red team exercises are not appropriate to define at the Enterprise level.'),
('002098','draft','2013-06-21','DISA FSO','policy','The organization defines rules of engagement for red team exercises to simulate attempts by adversaries to compromise organizational information systems.','CA-8(2).2','The organization being inspected/assessed defines and documents rules of engagement for red team exercise to simulate attempts by adversaries to compromise organizational information systems. DoD has determined the rules of engagement are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented rules of engagement to ensure the organization being inspected/assessed defines the rules of engagement for red team exercise to simulate attempts by adversaries to compromise organizational information systems. DoD has determined the rules of engagement are not appropriate to define at the Enterprise level.'),
('002099','draft','2013-06-21','DISA FSO','policy','The organization employs organization-defined red team exercises to simulate attempts by adversaries to compromise organizational information systems in accordance with organization-defined rules of engagement.','CA-8(2).3','The organization being inspected/assessed employs red team exercises defined in CA-8 (2), CCI 2097 to simulate attempts by adversaries to compromise organizational information systems in accordance with rules of engagement defined in CA-8 (2), CCI 2098. The organization must maintain a record of red team exercises and results.','The organization conducting the inspection/assessment obtains and examines the record of red team exercises and results to ensure the organization being inspected/assessed employs red team exercises defined in CA-8 (2), CCI 2097 to simulate attempts by adversaries to compromise organizational information systems in accordance with rules of engagement defined in CA-8 (2), CCI 2098.'),
('002100','draft','2013-06-21','DISA FSO','policy','The information system performs security compliance checks on constituent components prior to the establishment of the internal connection.','CA-9(1).1','The organization being inspected/assessed documents and implements a process to perform security compliance checks on constituent components prior to the establishment of the internal connection. The organization must maintain a record of security compliance checks.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of security compliance checks to ensure the organization being inspected/assessed performs security compliance checks on constituent components prior to the establishment of the internal connection.'),
('002101','draft','2013-06-21','DISA FSO','policy','The organization authorizes internal connections of organization-defined information system components or classes of components to the information system.','CA-9.1','The organization being inspected/assessed authorizes internal connections of information system components defined in CA-9, CCI 2102 or classes of components to the information system. The organization must maintain an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed authorizes internal connections of information system components defined in CA-9, CCI 2102 or classes of components to the information system.'),
('002102','draft','2013-06-21','DISA FSO','policy','The organization defines the information system components or classes of components that are authorized internal connections to the information system.','CA-9.2','The organization being inspected/assessed defines and documents the information system components or classes of components that that are authorized internal connections to the information system. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components or classes of components that that are authorized internal connections to the information system. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002103','draft','2013-06-21','DISA FSO','policy','The organization documents, for each internal connection, the interface characteristics.','CA-9.3','The organization being inspected/assessed documents, for each internal connection, the interface characteristics.','The organization conducting the inspection/assessment obtains and examines the documented interface characteristics as well as the network topology to ensure the organization being inspected/assessed documents, for each internal connection, the interface characteristics.'),
('002104','draft','2013-06-21','DISA FSO','policy','The organization documents, for each internal connection, the security requirements.','CA-9.4','The organization being inspected/assessed documents, for each internal connection, the security requirements.','The organization conducting the inspection/assessment obtains and examines the documented security requirements as well as the network topology to ensure the organization being inspected/assessed documents, for each internal connection, the security requirements.'),
('002105','draft','2013-06-21','DISA FSO','policy','The organization documents, for each internal connection, the nature of the information communicated.','CA-9.5','The organization being inspected/assessed documents, for each internal connection, the nature of the information communicated.','The organization conducting the inspection/assessment obtains and examines the documented nature of information communication as well as the network topology to ensure the organization being inspected/assessed documents, for each internal connection, the nature of the information communicated.'),
('002106','draft','2013-06-24','DISA FSO','policy','The organization documents the access control policy.',NULL,NULL,NULL),
('002107','draft','2013-06-24','DISA FSO','policy','The organization defines the personnel or roles to be recipients of the access control policy necessary to facilitate the implementation of the access control policy and associated access controls.','AC-1.1','DoD has defined the personnel or roles as all personnel.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all personnel.'),
('002108','draft','2013-06-24','DISA FSO','policy','The organization defines the personnel or roles to be recipients of the procedures necessary to facilitate the implementation of the access control policy and associated access controls.','AC-1.2','DoD has defined the personnel or roles as all personnel.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all personnel.'),
('002109','draft','2013-06-24','DISA FSO','policy','The organization documents procedures to facilitate the implementation of the access control policy and associated access controls.',NULL,NULL,NULL),
('002110','draft','2013-06-24','DISA FSO','policy','The organization defines the information system account types that support the organizational missions/business functions.','AC-2.1','The organization being inspected/assessed defines and documents the information system account types that support the organizational missions/business functions. DoD has determined the information system account types are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system account types to ensure the organization being inspected/assessed defines the information system account types that support the organizational missions/business functions. DoD has determined the information system account types are not appropriate to define at the Enterprise level.'),
('002111','draft','2013-06-24','DISA FSO','policy','The organization identifies and selects the organization-defined information system account types of information system accounts which support organizational missions/business functions.','AC-2.2','The account types are defined per AC-2, CCI 2110.','The account types are defined per AC-2, CCI 2110.'),
('002112','draft','2013-06-24','DISA FSO','policy','The organization assigns account managers for information system accounts.','AC-2.3','The organization being inspected/assessed documents personnel responsible for the management of system accounts.','The organization conducting the inspection/assessment obtains and examines the documented appointment of management personnel to ensure that the organization being inspected/assessed has documented personnel responsible for the management of system accounts.'),
('002113','draft','2013-06-24','DISA FSO','policy','The organization establishes conditions for role membership.','AC-2.5','The organization being inspected/assessed documents conditions for adding accounts as members of roles.','The organization conducting the inspection/assessment obtains and examines the documented conditions for adding accounts as members of roles to ensure that the conditions are established.'),
('002114','deprecated','2013-06-24','DISA FSO','policy','The organization specifies authorized users of the information system for each account.',NULL,NULL,NULL),
('002115','draft','2013-06-24','DISA FSO','policy','The organization specifies authorized users of the information system.','AC-2.6','The organization being inspected/assessed documents authorized users of the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of authorized users for a sampling of information system accounts to ensure that the authorized users are specified.'),
('002116','draft','2013-06-24','DISA FSO','policy','The organization specifies authorized group membership on the information system.','AC-2.7','The organization being inspected/assessed documents authorized group membership on the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of authorized groups for a sampling of information system accounts to ensure that the authorized groups are specified.'),
('002117','draft','2013-06-24','DISA FSO','policy','The organization specifies authorized role membership on the information system.','AC-2.8','The organization being inspected/assessed documents authorized role membership on the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of authorized roles for a sampling of information system accounts to ensure that the authorized roles are specified'),
('002118','draft','2013-06-24','DISA FSO','policy','The organization specifies access authorizations (i.e., privileges) for each account on the information system.','AC-2.9','The organization being inspected/assessed documents access authorizations (i.e., privileges) for each account on the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of access authorizations for a sampling of information system accounts to ensure that the access authorizations are specified.'),
('002119','draft','2013-06-24','DISA FSO','policy','The organization specifies other attributes for each account on the information system.','AC-2.10','The organization being inspected/assessed documents other attributes for each account on the information system.','The organization conducting the inspection/assessment obtains and examines the documented list of other attributes for a sampling of information system accounts to ensure that other attributes are specified.'),
('002120','draft','2013-06-24','DISA FSO','policy','The organization defines the personnel or roles authorized to approve the creation of information system accounts.','AC-2.12','DoD has defined the personnel or roles as the ISSM or ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSM or ISSO.'),
('002121','draft','2013-06-24','DISA FSO','policy','The organization defines the procedures or conditions to be employed when creating, enabling, modifying, disabling, and removing information system accounts.','AC-2.14','The organization being inspected/assessed defines and documents the procedures or conditions to be employed when creating, enabling, modifying, disabling, and removing information system accounts. DoD has determined the procedures or conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented procedures or conditions to ensure the organization being inspected/assessed defines the procedures or conditions to be employed when creating, enabling, modifying, disabling, and removing information system accounts. DoD has determined the procedures or conditions are not appropriate to define at the Enterprise level.'),
('002122','draft','2013-06-24','DISA FSO','policy','The organization monitors the use of information system accounts.','AC-2.15','The organization being inspected/assessed implements a process to monitor the use of information system accounts.','The organization conducting the inspection/assessment obtains and examines the audit trail to ensure that the organization being inspected/assessed implements a process to monitor the use of information system accounts.'),
('002123','draft','2013-06-24','DISA FSO','policy','The organization notifies account managers when accounts are no longer required.','AC-2.16','The organization being inspected/assessed implements a process to notify account managers when accounts are no longer required. The organization being inspected/assessed maintains an audit trail of notifications.','The organization conducting the inspection/assessment obtains and examines the audit trail of notifications to ensure the organization being inspected/assessed implements a process to notify account managers when accounts are no longer required.'),
('002124','draft','2013-06-24','DISA FSO','policy','The organization notifies account managers when users are terminated or transferred.','AC-2.17','The organization being inspected/assessed implements a process to notify account managers when users are terminated or transferred. The organization being inspected/assessed maintains an audit trail of notifications.','The organization conducting the inspection/assessment obtains and examines the audit trail of notifications to ensure the organization being inspected/assessed implements a process to notify account managers when users are terminated or transferred.'),
('002125','draft','2013-06-24','DISA FSO','policy','The organization notifies account managers when individual information system usage or need-to-know changes.','AC-2.18','The organization being inspected/assessed implements a process to notify account managers when individual information system usage or need-to-know changes. The organization being inspected/assessed maintains an audit trail of notifications.','The organization conducting the inspection/assessment obtains and examines the audit trail of notifications to ensure the organization being inspected/assessed implements a process to notify account managers when individual information system usage or need-to-know changes.'),
('002126','draft','2013-06-24','DISA FSO','policy','The organization authorizes access to the information system based on a valid access authorization.','AC-2.19','The organization being inspected/assessed authorizes access to the information system based on the access authorization process. The organization being inspected/assessed maintains an audit trail of approved access.','The organization conducting the inspection/assessment obtains and examines the audit trail of approved access to ensure the organization being inspected/assessed authorizes access to the information system based on the access authorization process.'),
('002127','draft','2013-06-24','DISA FSO','policy','The organization authorizes access to the information system based on intended system usage.','AC-2.20','The organization being inspected/assessed authorizes access to the information system based on intended system usage. The organization being inspected/assessed maintains an audit trail of approved access.','The organization conducting the inspection/assessment obtains and examines the audit trail of approved access to ensure the organization being inspected/assessed authorizes access to the information system based on intended system usage.'),
('002128','draft','2013-06-24','DISA FSO','policy','The organization authorizes access to the information system based on other attributes as required by the organization or associated missions/business functions.','AC-2.21','The organization being inspected/assessed authorizes access to the information system based on other attributes as required by the organization or associated missions/business functions. The organization being inspected/assessed maintains an audit trail of approved access.','The organization conducting the inspection/assessment obtains and examines the audit trail of approved access to ensure the organization being inspected/assessed authorizes access to the information system based on other attributes as required by the organization or associated missions/business functions.'),
('002129','draft','2013-06-24','DISA FSO','policy','The organization establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group.','AC-2.24','The organization being inspected/assessed includes in the account management procedures a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group.','The organization conducting the inspection/assessment obtains and examines the account management procedures to ensure the organization being inspected/assessed includes in the account management procedures a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group.'),
('002130','draft','2013-06-24','DISA FSO','technical','The information system automatically audits account enabling actions.','AC-2(4).9','The organization being inspected/assessed configures the information system to automatically audit account enabling actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2130.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically audit account enabling actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2130.'),
('002131','draft','2013-06-24','DISA FSO','policy','The organization defines the personnel or roles to be notified on account creation, modification, enabling, disabling, and removal actions.','AC-2(4).10','DoD has defined the personnel or roles as the system administrator and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the system administrator and ISSO.'),
('002132','draft','2013-06-24','DISA FSO','technical','The information system notifies organization-defined personnel or roles for account enabling actions.','AC-2(4).11','The organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account enabling actions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2132. DoD has defined the personnel or roles as the system administrator and ISSO.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the system administrator and ISSO for account enabling actions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2132. DoD has defined the personnel or roles as the system administrator and ISSO.'),
('002133','draft','2013-06-24','DISA FSO ','policy','The organization defines other conditions when users are required to log out.','AC-2(5).1','The organization being inspected/assessed defines and documents the other conditions when users are required to log out. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure they have been defined. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002134','draft','2013-06-24','DISA FSO','policy','The organization defines a list of dynamic privilege management capabilities to be implemented by the information system.','AC-2(6).1','The organization being inspected/assessed defines and documents a list of dynamic privilege management capabilities to be implemented by the information system. DoD has determined the list is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented list to ensure the dynamic privilege management capabilities have been defined. DoD has determined the list is not appropriate to define at the Enterprise level.'),
('002135','draft','2013-06-24','DISA FSO','technical','The information system implements the organization-defined list of dynamic privilege management capabilities.','AC-2(6).2','The organization being inspected/assessed configures the information system to implement the list of dynamic privilege management capabilities defined in AC-2 (6), CCI 2134. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2135.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement the list of dynamic privilege management capabilities defined in AC-2 (6), CCI 2134. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2135.'),
('002136','draft','2013-06-24','DISA FSO','policy','The organization defines the actions to be taken when privileged role assignments are no longer appropriate.','AC-2(7).4','DoD has defined the actions as disables (or revokes) privileged user account.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the actions as disables (or revokes) privileged user account.'),
('002137','draft','2013-06-24','DISA FSO','policy','The organization takes organization-defined actions when privileged role assignments are no longer appropriate.','AC-2(7).5','The organization being inspected/assessed documents and implements a process to disable (or revoke) the privileged user account when privileged role assignments are no longer appropriate. The organization must maintain an audit trail of the actions taken. DoD has defined the actions as disables (or revokes) privileged user account.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of actions taken to ensure the organization being inspected/assessed disables (or revokes) the privileged user account when privileged role assignments are no longer appropriate.\nDoD has defined the actions as disables (or revokes) privileged user account.'),
('002138','draft','2013-06-24','DISA FSO','policy','The organization defines the information system accounts that can be dynamically created.','AC-2(8).1','The organization being inspected/assessed defines and documents the information system accounts that can be dynamically created. DoD has determined the information system accounts are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system accounts to ensure they have been defined. DoD has determined the information system accounts are not appropriate to define at the Enterprise level.'),
('002139','draft','2013-06-24','DISA FSO','technical','The information system creates organization-defined information system accounts dynamically.','AC-2(8).2','The organization being inspected/assessed configures the information system to dynamically create information system accounts defined in AC-2 (8), CCI 2138. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2139.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to dynamically create information system accounts defined in AC-2 (8), CCI 2138. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2139.'),
('002140','draft','2013-06-24','DISA FSO ','policy','The organization defines the conditions for establishing shared/group accounts.','AC-2(9).1','The organization being inspected/assessed defines and documents the conditions for establishing shared/group accounts. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure they have been defined. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002141','draft','2013-06-24','DISA FSO','policy','The organization only permits the use of shared/group accounts that meet organization-defined conditions for establishing shared/group accounts.','AC-2(9).2','The organization being inspected/assessed only permits the use of shared/group accounts that meet the conditions for establishing shared/group accounts defined in AC-2 (9), CCI 2140.','The organization conducting the inspection/assessment examines the shared/group accounts to ensure the organization being inspected/assessed only permits the use of shared/group accounts that meet the conditions for establishing shared/group accounts defined in AC-2 (9), CCI 2140.'),
('002142','draft','2013-06-24','DISA FSO','technical','The information system terminates shared/group account credentials when members leave the group.','AC-2(10).1','The organization being inspected/assessed configures the information system to terminate shared/group account credentials when members leave the group. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2142.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to terminate shared/group account credentials when members leave the group. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2142.'),
('002143','draft','2013-06-24','DISA FSO','policy','The organization defines the circumstances and/or usage conditions that are to be enforced for organization-defined information system accounts.','AC-2(11).1','The organization being inspected/assessed defines and documents the circumstances and/or usage conditions that are to be enforced for organization-defined information system accounts. DoD has determined the circumstances and/or usage conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances and/or usage conditions to ensure they have been defined. DoD has determined the circumstances and/or usage conditions are not appropriate to define at the Enterprise level.'),
('002144','draft','2013-06-24','DISA FSO ','policy','The organization defines the information system accounts that are to be subject to the enforcement of organization-defined circumstances and/or usage conditions.','AC-2(11).2','The organization being inspected/assessed defines and documents the information system accounts that are to be subject to the enforcement of organization-defined circumstances and/or usage conditions. DoD has determined the information system accounts are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system accounts to ensure they have been defined. DoD has determined the information system accounts are not appropriate to define at the Enterprise level.'),
('002145','draft','2013-06-24','DISA FSO','technical','The information system enforces organization-defined circumstances and/or usage conditions for organization-defined information system accounts.','AC-2(11).3','The organization being inspected/assessed configures the information system to enforce the circumstances and/or usage conditions defined in AC-2 (11), CCI 2143 for information system accounts defined in AC-2 (11), CCI 2144. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2145.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the circumstances and/or usage conditions defined in AC-2 (11), CCI 2143 for information system accounts defined in AC-2 (11), CCI 2144. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2145.'),
('002146','draft','2013-06-24','DISA FSO','policy','The organization defines atypical usage for which the information system accounts are to be monitored.','AC-2(12).1','The organization being inspected/assessed defines and documents atypical usage for which the information system accounts are to be monitored. DoD has determined atypical usage is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented atypical usage to ensure it has been defined. DoD has determined atypical usage is not appropriate to define at the Enterprise level.'),
('002147','draft','2013-06-24','DISA FSO','policy','The organization monitors information system accounts for organization-defined atypical use.','AC-2(12).2','The organization being inspected/assessed monitors information system accounts for atypical use defined in AC-2 (12), CCI 2146. The organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the audit trail of monitoring to ensure the organization being inspected/assessed monitors information system accounts for atypical use defined in AC-2 (12), CCI 2146.'),
('002148','draft','2013-06-24','DISA FSO','policy','The organization defines the personnel or roles to whom atypical usage of information system accounts are to be reported.','AC-2(12).3','DoD has defined the personnel or roles as at a minimum, the ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\nDoD has defined the personnel or roles as at a minimum, the ISSO.'),
('002149','draft','2013-06-24','DISA FSO','policy','The organization reports atypical usage of information system accounts to organization-defined personnel or roles.','AC-2(12).4','The organization being inspected/assessed documents and implements a process to report atypical usage defined in AC-2 (12), CCI 2146 of information system accounts to at a minimum, the ISSO.\nThe organization must maintain an audit trail of reporting.\nDoD has defined the personnel or roles as at a minimum, the ISSO.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reporting to ensure the organization being inspected/assessed reports atypical usage defined in AC-2 (12), CCI 2146 of information system accounts to at a minimum, the ISSO.\nDoD has defined the personnel or roles as at a minimum, the ISSO.'),
('002150','draft','2013-06-24','DISA FSO','policy','The organization defines the time period within which the accounts of users posing a significant risk are to be disabled after discovery of the risk.','AC-2(13).1','DoD has defined the time period as 30 minutes unless otherwise defined in formal organizational policy. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 30 minutes unless otherwise defined in formal organizational policy. '),
('002151','draft','2013-06-24','DISA FSO','policy','The organization disables accounts of users posing a significant risk within an organization-defined time period of discovery of the risk.','AC-2(13).2','The organization being inspected/assessed documents and implements a process to disable accounts of users posing a significant risk within 30 minutes unless otherwise defined in formal organizational policy. DoD has defined the time period as 30 minutes unless otherwise defined in formal organizational policy. ','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed disables accounts of users posing a significant risk within 30 minutes unless otherwise defined in formal organizational policy. DoD has defined the time period as 30 minutes unless otherwise defined in formal organizational policy. '),
('002152','draft','2013-06-24','DISA FSO','policy','The organization defines other actions necessary for which dual authorization is to be enforced.','AC-3(2).3','The organization being inspected/assessed defines and documents the other actions necessary for which dual authorization is to be enforced. DoD has determined the other actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented actions to ensure they have been defined. DoD has determined the other actions are not appropriate to define at the Enterprise level.'),
('002153','draft','2013-06-24','DISA FSO','policy','The organization defines the mandatory access control policies that are to be enforced over all subjects and objects.','AC-3(3).1','The organization being inspected/assessed defines and documents the mandatory access control policies that are to be enforced over all subjects and objects. DoD has determined the mandatory access control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented mandatory access control policies to ensure they have been defined. DoD has determined the mandatory access control policies are not appropriate to define at the Enterprise level.'),
('002154','draft','2013-06-24','DISA FSO','policy','The mandatory access control policy specifies that the policy is uniformly enforced across all subjects and objects within the boundary of the information system.','AC-3(3).2','The organization being inspected/assessed configures the information system to uniformly enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 across all subjects and objects within the boundary of the information system For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2154.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to uniformly enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 across all subjects and objects within the boundary of the information system For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2154.'),
('002155','draft','2013-06-24','DISA FSO','policy','The mandatory access control policy specifies that a subject that has been granted access to information is constrained from passing the information to unauthorized subjects or objects.','AC-3(3).3','The organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from passing the information to unauthorized subjects or objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2155.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from passing the information to unauthorized subjects or objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2155.'),
('002156','draft','2013-06-24','DISA FSO','policy','The mandatory access control policy specifies that a subject that has been granted access to information is constrained from granting its privileges to other subjects.','AC-3(3).4','The organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from granting its privileges to other subjects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2156.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from granting its privileges to other subjects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2156.'),
('002157','draft','2013-06-24','DISA FSO','policy','The mandatory access control policy specifies that a subject that has been granted access to information is constrained from changing one or more security attributes on subjects, objects, the information system, or information system components.','AC-3(3).5','The organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from changing one or more security attributes on subjects, objects, the information system, or information system components. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2157.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from changing one or more security attributes on subjects, objects, the information system, or information system components. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2157.'),
('002158','draft','2013-06-24','DISA FSO','policy','The mandatory access control policy specifies that a subject that has been granted access to information is constrained from choosing the security attributes to be associated with newly created or modified objects.','AC-3(3).6','The organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from choosing the security attributes to be associated with newly created or modified objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2158.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from choosing the security attributes to be associated with newly created or modified objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2158.'),
('002159','draft','2013-06-24','DISA FSO ','policy','The mandatory access control policy specifies that a subject that has been granted access to information is constrained from choosing the attribute values to be associated with newly created or modified objects.','AC-3(3).7','The organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from choosing the attribute values to be associated with newly created or modified objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2159.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from choosing the attribute values to be associated with newly created or modified objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2159.'),
('002160','draft','2013-06-24','DISA FSO','policy','The mandatory access control policy specifies that a subject that has been granted access to information is constrained from changing the rules governing access control.','AC-3(3).8','The organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from changing the rules governing access control. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2160.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the mandatory access control policies defined in AC-3 (3), CCI 2153 which specifies that a subject that has been granted access to information is constrained from changing the rules governing access control. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2160.'),
('002161','draft','2013-06-24','DISA FSO','policy','The organization defines subjects which may explicitly be granted organization-defined privileges such that they are not limited by some or all of the mandatory access control constraints.','AC-3(3).9','The organization being inspected/assessed defines and documents subjects which may explicitly be granted organization-defined privileges such that they are not limited by some or all of the mandatory access control constraints. DoD has determined that the subjects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented subjects to ensure they have been defined. DoD has determined that the subjects are not appropriate to define at the Enterprise level.'),
('002162','draft','2013-06-24','DISA FSO','policy','The organization defines the privileges that may explicitly be granted to organization-defined subjects such that they are not limited by some or all of the mandatory access control constraints.','AC-3(3).10','The organization being inspected/assessed defines and documents the privileges that may explicitly be granted to organization-defined subjects such that they are not limited by some or all of the mandatory access control constraints. DoD has determined the privileges are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented privileges to ensure they have been defined. DoD has determined the privileges are not appropriate to define at the Enterprise level.'),
('002163','draft','2013-06-24','DISA FSO','policy','The organization defines the discretionary access control policies the information system is to enforce over subjects and objects.','AC-3(4).1','The organization being inspected/assessed defines and documents the discretionary access control policies the information system is to enforce over subjects and objects. DoD has determined that the discretionary access control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented access control policies to ensure they have been defined. DoD has determined that the discretionary access control policies are not appropriate to define at the Enterprise level.'),
('002164','draft','2013-06-24','DISA FSO','policy','The organization specifies in the discretionary access control policies that a subject that has been granted access to information can do one or more of the following: pass the information to any other subjects or objects; grant its privileges to other subjects; change security attributes on subjects, objects, the information system, or the information system^s components; choose the security attributes to be associated with newly created or revised objects; and/or change the rules governing access control.','AC-3(4).2','The organization being inspected/assessed documents the discretionary access control policies that a subject which has been granted access to information can do one or more of the following: pass the information to any other subjects or objects; grant its privileges to other subjects; change security attributes on subjects, objects, the information system, or the information systems components; choose the security attributes to be associated with newly created or revised objects; and/or change the rules governing access control.','The organization conducting the inspection/assessment obtains and examines the documented discretionary access control policies to ensure the organization being inspected/assessed specifies that a subject which has been granted access to information can do one or more of the following: pass the information to any other subjects or objects; grant its privileges to other subjects; change security attributes on subjects, objects, the information system, or the information systems components; choose the security attributes to be associated with newly created or revised objects; and/or change the rules governing access control.'),
('002165','draft','2013-06-24','DISA FSO','technical','The information system enforces organization-defined discretionary access control policies over defined subjects and objects.','AC-3(4).3','The organization being inspected/assessed configures the information system to enforce the discretionary access control policies defined in AC-3 (4), CCI 2163 over defined subjects and objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2165.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the discretionary access control policies defined in AC-3 (4), CCI 2163 over defined subjects and objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2165.'),
('002166','draft','2013-06-24','DISA FSO','policy','The organization defines the role-based access control policies the information system is to enforce over all subjects and objects.','AC-3(7).1','The organization being inspected/assessed defines and documents the role-based access control policies the information system is to enforce over all subjects and objects.','The organization conducting the inspection/assessment obtains and examines the documented role-based access control policies to ensure the organization being inspected/assessed defines the role-based access control policies the information system is to enforce over all subjects and objects.'),
('002167','draft','2013-06-24','DISA FSO ','policy','The organization defines the subjects over which the information system will enforce a role-based access control policy.','AC-3(7).2','The organization being inspected/assessed defines and documents the subjects over which the information system will enforce a role-based access control policy.','The organization conducting the inspection/assessment obtains and examines the documented subjects to ensure the organization being inspected/assessed defines the subjects over which the information system will enforce a role-based access control policy.'),
('002168','draft','2013-06-24','DISA FSO','policy','The organization defines the objects over which the information system will enforce a role-based access control policy.','AC-3(7).3','The organization being inspected/assessed defines and documents the objects over which the information system will enforce a role-based access control policy.','The organization conducting the inspection/assessment obtains and examines the documented objects to ensure the organization being inspected/assessed defines the objects over which the information system will enforce a role-based access control policy.'),
('002169','draft','2013-06-24','DISA FSO','technical','The information system enforces a role-based access control policy over defined subjects and objects.','AC-3(7).4','The organization being inspected/assessed configures the information system to enforce a roles-based access control policy over defined subjects and objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2169.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce a roles-based access control policy over defined subjects and objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2169.'),
('002170','draft','2013-06-24','DISA FSO','policy','The information system controls access based upon organization-defined roles and users authorized to assume such roles.','AC-3(7).5','The organization being inspected/assessed configures the information system to control access based upon the roles and users defined in AC-3 (7), CCIs 2173 and 2174 authorized to assume such roles. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2170.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to control access based upon the roles and users defined in AC-3 (7), CCIs 2173 and 2174 authorized to assume such roles. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2170.'),
('002171','deprecated','2013-06-24','DISA FSO','technical','The information system enforces a role-based access control policy over organization-defined subjects.',NULL,NULL,NULL),
('002172','deprecated','2013-06-24','DISA FSO ','technical','The information system enforces a role-based access control policy over organization-defined objects.',NULL,NULL,NULL),
('002173','draft','2013-06-24','DISA FSO','policy','The organization defines the roles for which the information system will control access based upon the organization-defined role-based access control policy.','AC-3(7).6','The organization being inspected/assessed defines and documents the roles the information system will control access based upon the organization-defined role-based access control policy. DoD has determined the roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented roles to ensure the organization being inspected/assessed defines the roles the information system will control access based upon the organization-defined role-based access control policy. DoD has determined the roles are not appropriate to define at the Enterprise level.'),
('002174','draft','2013-06-24','DISA FSO','policy','The organization defines the users for which the information system will control access based upon the organization-defined role-based access control policy.','AC-3(7).7','The organization being inspected/assessed defines and documents the users the information system will control access based upon the organization-defined role-based access control policy. DoD has determined the users are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented roles to ensure the organization being inspected/assessed defines the users the information system will control access based upon the organization-defined role-based access control policy. DoD has determined the users are not appropriate to define at the Enterprise level.'),
('002175','deprecated','2013-06-24','DISA FSO','technical','The information system controls access based upon organization-defined roles authorized to assume such roles, employing the organization-defined role-based access control policy.',NULL,NULL,NULL),
('002176','deprecated','2013-06-24','DISA FSO','technical','The information system controls access based upon organization-defined users authorized to assume such roles, employing the organization-defined role-based access control policy.',NULL,NULL,NULL),
('002177','draft','2013-06-24','DISA FSO','policy','The organization defines the rules which will govern the timing of revocation of access authorizations.','AC-3(8).1','The organization being inspected/assessed defines and documents the rules which will govern the timing of revocation of access authorizations. DoD has determined the rules are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented rules to ensure the organization being inspected/assessed defines the rules which will govern the timing of revocation of access authorizations. DoD has determined the rules are not appropriate to define at the Enterprise level.'),
('002178','draft','2013-06-24','DISA FSO','technical','The information system enforces the revocation of access authorizations resulting from changes to the security attributes of subjects based on organization-defined rules governing the timing of revocations of access authorizations.','AC-3(8).2','The organization being inspected/assessed configures the information system to enforce the revocation of access authorizations resulting from changes to the security attributes of subjects based on the rules defined in AC-3 (8), CCI 2177 governing the timing of revocations of access authorizations. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2178.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the revocation of access authorizations resulting from changes to the security attributes of subjects based on the rules defined in AC-3 (8), CCI 2177 governing the timing of revocations of access authorizations. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2178.'),
('002179','draft','2013-06-24','DISA FSO','technical','The information system enforces the revocation of access authorizations resulting from changes to the security attributes of objects based on organization-defined rules governing the timing of revocations of access authorizations.','AC-3(8).3','The organization being inspected/assessed configures the information system to enforce the revocation of access authorizations resulting from changes to the security attributes of objects based on the rules defined in AC-3 (8), CCI 2177 governing the timing of revocations of access authorizations. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2179.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the revocation of access authorizations resulting from changes to the security attributes of objects based on the rules defined in AC-3 (8), CCI 2177 governing the timing of revocations of access authorizations. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2179.'),
('002180','draft','2013-06-24','DISA FSO','policy','The organization defines the security safeguards the organization-defined information system or system component is to provide to protect information released outside the established system boundary.','AC-3(9).1','The organization being inspected/assessed defines and documents the security safeguards the organization-defined information system or system component is to provide to protect information released outside the established system boundary. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards the organization-defined information system or system component is to provide to protect information released outside the established system boundary. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002181','draft','2013-06-24','DISA FSO','policy','The organization defines information systems or system components that are to provide organization-defined security safeguards to protect information received outside the established system boundary.','AC-3(9).2','The organization being inspected/assessed defines and documents the information systems or system components that are to provide organization-defined security safeguards to protect information received outside the established system boundary. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems or system components to ensure the organization being inspected/assessed defines the information systems or system components that are to provide organization-defined security safeguards to protect information received outside the established system boundary. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002182','draft','2013-06-24','DISA FSO','policy','The information system does not release information outside of the established system boundary unless the receiving organization-defined information system or system component provides organization-defined security safeguards.','AC-3(9).3','The organization being inspected/assessed configures the information system to not release information outside of the established system boundary unless the receiving information system or system component defined in AC-3 (9), CCI 2181 provides security safeguards defined in AC-3 (9), CCI 2180. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2182.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to not release information outside of the established system boundary unless the receiving information system or system component defined in AC-3 (9), CCI 2181 provides security safeguards defined in AC-3 (9), CCI 2180. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2182.'),
('002183','draft','2013-06-24','DISA FSO ','policy','The organization defines the security safeguards to be used to validate the appropriateness of the information designated for release.','AC-3(9).4','The organization being inspected/assessed defines and documents the security safeguards to be used to validate the appropriateness of the information designated for release. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be used to validate the appropriateness of the information designated for release. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002184','draft','2013-06-24','DISA FSO','policy','The information system does not release information outside of the established system boundary unless organization-defined security safeguards are used to validate the appropriateness of the information designated for release.','AC-3(9).5','The organization being inspected/assessed configures the information system to not release information outside of the established system boundary unless security safeguards defined in AC-3 (9), CCI 2183 are used to validate the appropriateness of the information designated for release. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2184.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to not release information outside of the established system boundary unless security safeguards defined in AC-3 (9), CCI 2183 are used to validate the appropriateness of the information designated for release. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2184.'),
('002185','draft','2013-06-24','DISA FSO','policy','The organization defines the conditions on which it will employ an audited override of automated access control mechanisms.','AC-3(10).1','The organization being inspected/assessed defines and documents the conditions in which it will employ an audited override of automated access control mechanisms. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure the organization being inspected/assessed defines the conditions in which it will employ an audited override of automated access control mechanisms. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002186','draft','2013-06-24','DISA FSO','technical','The organization employs an audited override of automated access control mechanisms under organization-defined conditions.','AC-3(10).2','The organization being inspected/assessed configures the information system to employ an audited override of automated access control mechanisms under conditions defined in AC-3 (10), CCI 2185. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2186.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ an audited override of automated access control mechanisms under conditions defined in AC-3 (10), CCI 2185. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2186.'),
('002187','draft','2013-06-24','DISA FSO','policy','The organization defines the security attributes to be used to enforce organization-defined information flow control policies.','AC-4(1).1','The organization being inspected/assessed defines and documents the security attributes to be used to enforce organization-defined information flow control policies. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines the security attributes to be used to enforce organization-defined information flow control policies. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002188','draft','2013-06-24','DISA FSO','policy','The organization defines the information, source, and destination objects with which the organization-defined security attributes are to be associated.','AC-4(1).2','The organization being inspected/assessed defines and documents the information, source and destination objects with which the organization-defined security attributes are to be associated. DoD has determined the information, source and destination objects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information, source, and destination objects to ensure the organization being inspected/assessed defines the information, source and destination objects with which the organization-defined security attributes are to be associated. DoD has determined the information, source and destination objects are not appropriate to define at the Enterprise level.'),
('002189','draft','2013-06-24','DISA FSO','policy','The organization defines the information flow control policies to be enforced for flow control decisions.','AC-4(1).3','The organization being inspected/assessed defines and documents the information flow control policies to be enforced for flow control decisions. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information flow control policies to ensure the organization being inspected/assessed defines the information flow control policies to be enforced for flow control decisions. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.'),
('002190','draft','2013-06-24','DISA FSO','technical','The information system uses organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions.','AC-4(1).4','The organization being inspected/assessed configures the information system to use the security attributes defined in AC-4 (1), CCI 287 associated with the information, source, and destination objects defined in AC-4 (1), CCI 2188 to enforce information flow control policies defined in AC-4 (1), CCI 2189 as a basis for flow control decisions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2190.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to use the security attributes defined in AC-4 (1), CCI 287 associated with the information, source, and destination objects defined in AC-4 (1), CCI 2188 to enforce information flow control policies defined in AC-4 (1), CCI 2189 as a basis for flow control decisions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2190.'),
('002191','draft','2013-06-24','DISA FSO','policy','The organization defines the information flow control policies to be enforced by the information system using protected processing domains.','AC-4(2).2','The organization being inspected/assessed defines and documents the information flow control policies to be enforced by the information system using protected processing domains. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the information flow control policies to ensure the organization being inspected/assessed defines the information flow control policies to be enforced by the information system using protected processing domains. DoD has determined the information flow control policies are not appropriate to define at the Enterprise level.'),
('002192','draft','2013-06-24','DISA FSO','policy','The organization defines the policies the information system is to enforce to achieve dynamic information flow control.','AC-4(3).2','The organization being inspected/assessed defines and documents the policies the information system is to enforce to achieve dynamic information flow control. The policies shall address dynamic reconfiguration of data flow based upon predefined rules. DoD has determined the policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented policies to ensure the organization being inspected/assessed defines the policies the information system is to enforce to achieve dynamic information flow control. DoD has determined the policies are not appropriate to define at the Enterprise level'),
('002193','draft','2013-06-24','DISA FSO','policy','The organization defines procedures or methods to be employed by the information system to prevent encrypted information from bypassing content-checking mechanisms, such as decrypting the information, blocking the flow of the encrypted information, and/or terminating communications sessions attempting to pass encrypted information.','AC-4(4).2','The organization being inspected/assessed selects or defines, and documents the mechanism to prevent encrypted information from bypassing content-checking mechanisms, such as decrypting the information, blocking the flow of the encrypted information, and/or terminating communications sessions attempting to pass encrypted information. Alternatively, the organization may define their own procedure or method. DoD has determined the procedures or methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented mechanism to ensure the organization being inspected/assessed selects or defines the mechanism to prevent encrypted information from bypassing content-checking mechanisms. DoD has determined the procedures or methods are not appropriate to define at the Enterprise level.'),
('002194','draft','2013-06-24','DISA FSO','policy','The organization defines the metadata the information system uses to enforce information flow control.','AC-4(6).2','The organization being inspected/assessed defines and documents the metadata the information system uses to enforce information flow control. DoD has determined the metadata is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented metadata to ensure the organization being inspected/assessed defines the metadata the information system uses to enforce information flow control. DoD has determined the metadata is not appropriate to define at the Enterprise level.'),
('002195','draft','2013-06-24','DISA FSO','policy','The organization defines the information flows against which the organization-defined security policy filters are to be enforced.','AC-4(8).3','DoD has defined the information flows as all information flows.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information flows as all information flows.'),
('002196','draft','2013-06-24','DISA FSO','policy','The organization defines the information flows for which the information system will enforce the use of human reviews under organization-defined conditions.','AC-4(9).1','The organization being inspected/assessed defines and documents the information flows for which the information system will enforce the use of human reviews under organization-defined conditions. DoD has determined the information flows are not appropriate to define at the Enterprise level','The organization conducting the inspection/assessment obtains and examines the documented information flows to ensure the organization being inspected/assessed defines the information flows for which the information system will enforce the use of human reviews under organization-defined conditions. DoD has determined the information flows are not appropriate to define at the Enterprise level.'),
('002197','draft','2013-06-24','DISA FSO','policy','The organization defines the conditions which will require the use of human reviews of organization-defined information flows.','AC-4(9).2','The organization being inspected/assessed defines and documents the conditions which will require the use of human reviews of organization-defined information flows. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure the organization being inspected/assessed defines the conditions which will require the use of human reviews of organization-defined information flows. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002198','draft','2013-06-24','DISA FSO','technical','The information system enforces the use of human reviews for organization-defined information flows under organization-defined conditions.','AC-4(9).3','The organization being inspected/assessed configures the information system to enforce the use of human reviews for information flows defined in AC-4 (9), CCI 2196 under conditions defined in AC-4 (9), CCI 2197. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2198.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce the use of human reviews for information flows defined in AC-4 (9), CCI 2196 under conditions defined in AC-4 (9), CCI 2197. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2198.'),
('002199','draft','2013-06-24','DISA FSO','policy','The organization defines the conditions under which the information system provides the capability for privileged administrators to enable/disable organization-defined security policy filters.','AC-4(10).3','The organization being inspected/assessed defines and documents the conditions under which the information system provides the capability for privileged administrators to enable/disable organization-defined security policy filters. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure the organization being inspected/assessed defines the conditions under which the information system provides the capability for privileged administrators to enable/disable organization-defined security policy filters. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002200','draft','2013-06-24','DISA FSO','policy','The organization defines the data type identifiers to be used to validate data being transferred between different security domains.','AC-4(12).1','The organization being inspected/assessed defines and documents the data type identifiers to be used to validate data being transferred between different security domains. DoD has determined the data type identifiers are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented data type identifiers to ensure the organization being inspected/assessed defines the data type identifiers to be used to validate data being transferred between different security domains. DoD has determined the data type identifiers are not appropriate to define at the Enterprise level.'),
('002201','draft','2013-06-24','DISA FSO','technical','The information system, when transferring information between different security domains, uses organization-defined data type identifiers to validate data essential for information flow decisions.','AC-4(12).2','The organization being inspected/assessed configures the information system to use data type identifiers defined in AC-4 (12), CCI 2200 to validate data essential for information flow decisions when transferring information between different security domains. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2201.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to use data type identifiers defined in AC-4 (12), CCI 2200 to validate data essential for information flow decisions when transferring information between different security domains. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2201.'),
('002202','draft','2013-06-24','DISA FSO','policy','The organization defines the policy-relevant subcomponents into which information being transferred between different security domains is to be decomposed for submission to policy enforcement mechanisms.','AC-4(13).2','The organization being inspected/assessed defines and documents the policy relevant subcomponents into which information being transferred between different security domains is to be decomposed into for submission to policy enforcement mechanisms. DoD has determined the policy-relevant subcomponents are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented policy-relevant subcomponents to ensure the organization being inspected/assessed defines the policy relevant subcomponents into which information being transferred between different security domains is to be decomposed into for submission to policy enforcement mechanisms. DoD has determined the policy-relevant subcomponents are not appropriate to define at the Enterprise level.'),
('002203','draft','2013-06-24','DISA FSO ','policy','The organization defines the unsanctioned information the information system is to examine when transferring information between different security domains.','AC-4(15).3','The organization being inspected/assessed defines and documents the unsanctioned information for which the information system is to examine when transferring information between different security domains. DoD has determined the unsanctioned information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented unsanctioned information to ensure the organization being inspected/assessed defines the unsanctioned information for which the information system is to examine when transferring information between different security domains. DoD has determined the unsanctioned information is not appropriate to define at the Enterprise level.'),
('002204','draft','2013-06-24','DISA FSO ','policy','The organization defines a security policy which prohibits the transfer of unsanctioned information between different security domains.','AC-4(15).4','The organization being inspected/assessed defines and documents security policy which prohibits the transfer of unsanctioned information between different security domains. DoD has determined the security policy is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policy to ensure the organization being inspected/assessed defines security policy which prohibits the transfer of unsanctioned information between different security domains. DoD has determined the security policy is not appropriate to define at the Enterprise level.'),
('002205','draft','2013-06-24','DISA FSO ','technical','The information system uniquely identifies and authenticates source by organization, system, application, and/or individual for information transfer.','AC-4(17).1','The organization being inspected/assessed configures the information system to uniquely identify and authenticate source by organization, system, application, and/or individual for information transfer. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2205.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to uniquely identify and authenticate source by organization, system, application, and/or individual for information transfer. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2205.'),
('002206','deprecated','2013-06-24','DISA FSO ','technical','The information system uniquely authenticates source by organization, system, application, and/or individual for information transfer.',NULL,NULL,NULL),
('002207','draft','2013-06-24','DISA FSO ','technical','The information system uniquely identifies and authenticates destination by organization, system, application, and/or individual for information transfer.','AC-4(17).2','The organization being inspected/assessed configures the information system to uniquely and authenticate identify destination by organization, system, application, and/or individual for information transfer. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2207.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to uniquely identify and authenticate destination by organization, system, application, and/or individual for information transfer. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2207.'),
('002208','deprecated','2013-06-24','DISA FSO ','technical','The information system uniquely authenticates destination by organization, system, application, and/or individual for information transfer.',NULL,NULL,NULL),
('002209','draft','2013-06-24','DISA FSO ','policy','The organization defines the techniques to be used to bind security attributes to information.','AC-4(18).1','The organization being inspected/assessed defines and documents the techniques to be used to bind security attributes to information. DoD has determined the techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques to ensure the organization being inspected/assessed defines the techniques to be used to bind security attributes to information. DoD has determined the techniques are not appropriate to define at the Enterprise level'),
('002210','draft','2013-06-24','DISA FSO ','technical','The information system binds security attributes to information using organization-defined binding techniques to facilitate information flow policy enforcement.','AC-4(18).2','The organization being inspected/assessed configures the information system to bind security attributes to information using binding techniques defined in AC-4 (18), CCI 2209 to facilitate information flow policy enforcement. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2210.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to bind security attributes to information using binding techniques defined in AC-4 (18), CCI 2209 to facilitate information flow policy enforcement. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2210.'),
('002211','draft','2013-06-24','DISA FSO ','technical','The information system, when transferring information between different security domains, applies the same security policy filtering to metadata as it applies to data payloads.','AC-4(19).1','The organization being inspected/assessed configures the information system to apply the same security policy filtering to metadata as it applies to data payloads when transferring information between different security domains. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2211.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to apply the same security policy filtering to metadata as it applies to data payloads when transferring information between different security domains. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2211.'),
('002212','draft','2013-06-24','DISA FSO ','policy','The organization defines the solutions in approved configurations to be employed to control the flow of organization-defined information across security domains.','AC-4(20).1','The organization being inspected/assessed defines and documents the solutions in approved configurations to be employed to control the flow of information defined in AC-4 (20), CCI 2213 across security domains. DoD has determined the solutions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented solutions to ensure the organization being inspected/assessed defines the solutions in approved configurations to be employed to control the flow of information defined in AC-4 (20), CCI 2213 across security domains. DoD has determined the solutions are not appropriate to define at the Enterprise level.'),
('002213','draft','2013-06-24','DISA FSO','policy','The organization defines the information to be subjected to flow control across security domains.','AC-4(20).2','The organization being inspected/assessed defines and documents the information to be subjected to flow control across security domains. DoD has determined the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information to ensure the organization being inspected/assessed defines the information to be subjected to flow control across security domains. DoD has determined the information is not appropriate to define at the Enterprise level.'),
('002214','draft','2013-06-24','DISA FSO ','policy','The organization employs organization-defined solutions in approved configurations to control the flow of organization-defined information across security domains.','AC-4(20).3','The organization being inspected/assessed documents and implements solutions defined in AC-4 (20), CCI 2212 in approved configurations to control the flow of information defined in AC-4 (20), CCI 2213 across security domains.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs solutions defined in AC-4 (20), CCI 2212 in approved configurations to control the flow of information defined in AC-4 (20), CCI 2213 across security domains.'),
('002215','draft','2013-06-24','DISA FSO','policy','The organization defines the mechanisms and/or techniques to be used to logically or physically separate information flows.','AC-4(21).1','The organization being inspected/assessed defines and documents the mechanisms and/or techniques to be used to logically or physically separate information flows. DoD has determined the mechanisms are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented mechanisms to ensure the organization being inspected/assessed defines the mechanisms and/or techniques to be used to logically or physically separate information flows. DoD has determined the mechanisms are not appropriate to define at the Enterprise level.'),
('002216','draft','2013-06-24','DISA FSO','policy','The organization defines the types of information required to accomplish logical or physical separation of information flows.','AC-4(21).2','The organization being inspected/assessed defines and documents the types of information required to accomplish logical or physical separation of information flows. DoD has determined the types of information are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented types of information to ensure the organization being inspected/assessed defines the types of information required to accomplish logical or physical separation of information flows. DoD has determined the types of information are not appropriate to define at the Enterprise level.'),
('002217','draft','2013-06-24','DISA FSO','policy','The information system separates information flows logically or physically using organization-defined mechanisms and/or techniques to accomplish organization-defined required separations by types of information.','AC-4(21).3','The organization being inspected/assessed configures the information system to separate information flows logically or physically using mechanisms and/or techniques defined in AC-4 (21), CCI 2215 to accomplish required separations by types of information defined in AC-4 (21), CCI 2216. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2217.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to separate information flows logically or physically using mechanisms and/or techniques defined in AC-4 (21), CCI 2215 to accomplish required separations by types of information defined in AC-4 (21), CCI 2216. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2217.'),
('002218','draft','2013-06-24','DISA FSO','technical','The information system provides access from a single device to computing platforms, applications, or data residing on multiple different security domains, while preventing any information flow between the different security domains.','AC-4(22).1','The organization being inspected/assessed configures the information system to provide access from a single device to computing platforms, applications, or data residing on multiple different security domains, while preventing any information flow between the different security domains. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2218.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide access from a single device to computing platforms, applications, or data residing on multiple different security domains, while preventing any information flow between the different security domains. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2218.'),
('002219','draft','2013-06-24','DISA FSO','policy','The organization defines the duties of individuals that are to be separated.','AC-5.2','The organization being inspected/assessed defines and documents the duties of individuals that are to be separated. DoD has determined the duties are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented duties to ensure the organization being inspected/assessed defines the duties of individuals that are to be separated. DoD has determined the duties are not appropriate to define at the Enterprise level.'),
('002220','draft','2013-06-24','DISA FSO','policy','The organization defines information system access authorizations to support separation of duties.','AC-5.4','The organization being inspected/assessed defines and documents the information system access authorizations to support separation of duties.','The organization conducting the inspection/assessment obtains and examines the documented information system access authorizations to ensure the organization being inspected/assessed defines information system access authorizations to support separation of duties.'),
('002221','draft','2013-06-24','DISA FSO','policy','The organization defines the security-relevant information for which access must be explicitly authorized.','AC-6(1).2','DoD has defined the security-relevant information as all security-relevant information not publicly available.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security-relevant information as all security-relevant information not publicly available.'),
('002222','draft','2013-06-24','DISA FSO','policy','The organization explicitly authorizes access to organization-defined security functions.','AC-6(1).3','The organization being inspected/assessed documents and implements a process to explicitly authorize access to all functions not publicly accessible. Explicit authorization can be in the form of an acceptable use policy signed by the user at the time of access being granted. DoD has defined the security functions as all functions not publicly accessible.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed explicitly authorizes access to all functions not publicly accessible. DoD has defined the security functions as all functions not publicly accessible.'),
('002223','draft','2013-06-24','DISA FSO','policy','The organization explicitly authorizes access to organization-defined security-relevant information.','AC-6(1).4','The organization being inspected/assessed documents and implements a process to explicitly authorize access to all security-relevant information not publicly available. Explicit authorization can be in the form of an acceptable use policy signed by the user at the time of access being granted. DoD has defined the security-relevant information as all security-relevant information not publicly available.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed explicitly authorizes access to all security-relevant information not publicly available. DoD has defined the security-relevant information as all security-relevant information not publicly available.'),
('002224','draft','2013-06-24','DISA FSO','policy','The organization defines the compelling operational needs that must be met in order to be authorized network access to organization-defined privileged commands.','AC-6(3).4','The organization being inspected/assessed defines and documents the compelling operational needs that must be met in order to be authorized network access to organization-defined privileged commands. DoD has determined the compelling operational needs are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented compelling operational needs to ensure the organization being inspected/assessed defines the compelling operational needs that must be met in order to be authorized network access to organization-defined privileged commands. DoD has determined the compelling operational needs are not appropriate to define at the Enterprise level.'),
('002225','draft','2013-06-24','DISA FSO ','policy','The information system provides separate processing domains to enable finer-grained allocation of user privileges.','AC-6(4).1','The organization being inspected/assessed configures the information system to provide separate processing domains to enable finer-grained allocation of user privileges. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2225.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide separate processing domains to enable finer-grained allocation of user privileges. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2225.'),
('002226','draft','2013-06-24','DISA FSO','policy','The organization defines the personnel or roles to whom privileged accounts are to be restricted on the information system.','AC-6(5).1','The organization being inspected/assessed defines and documents the personnel or roles to whom privileged accounts are to be restricted on the information system. DoD has determined the personnel and roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to whom privileged accounts are to be restricted on the information system. DoD has determined the personnel and roles are not appropriate to define at the Enterprise level.'),
('002227','draft','2013-06-24','DISA FSO','policy','The organization restricts privileged accounts on the information system to organization-defined personnel or roles.','AC-6(5).2','The organization being inspected/assessed implements a process to only provide privileged accounts on the information system to personnel or roles defined in AC-6 (5), CCI 2226.','The organization conducting the inspection/assessment obtains and examines a sampling of information system access authorizations to ensure the organization being inspected/assessed implements a process to only provide privileged accounts on the information system to personnel or roles defined in AC-6 (5), CCI 2226.'),
('002228','draft','2013-06-24','DISA FSO','policy','The organization defines the frequency on which it conducts reviews of the privileges assigned to organization-defined roles or classes of users.','AC-6(7).1','DoD has defined the frequency as at a minimum, annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at a minimum, annually.'),
('002229','draft','2013-06-24','DISA FSO','policy','The organization defines the roles or classes of users that are to have their privileges reviewed on an organization-defined frequency.','AC-6(7).2','DoD has defined the roles or classes of users as all users.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the roles or classes of users as all users.'),
('002230','draft','2013-06-24','DISA FSO','policy','The organization reviews the privileges assigned to organization-defined roles or classes of users on an organization-defined frequency to validate the need for such privileges.','AC-6(7).3','The organization being inspected/assessed documents and implements a process to review the privileges assigned to all users at a minimum, annually to validate the need for such privileges. The organization must maintain an audit trail of reviews. DoD has defined the roles or classes of users as all users. DoD has defined the frequency as at a minimum, annually.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of reviews to ensure the organization being inspected/assessed reviews the privileges assigned to all users at a minimum, annually. to validate the need for such privileges. DoD has defined the roles or classes of users as all users. DoD has defined the frequency as at a minimum, annually.'),
('002231','draft','2013-06-24','DISA FSO','policy','The organization reassigns or removes privileges, if necessary, to correctly reflect organizational mission/business needs.','AC-19(5).1','The organization being inspected/assessed documents and implements a process for full-device encryption or container encryption to protect the integrity of information on mobile devices defined in AC-19 (5), CCI 2329.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs full-device encryption or container encryption to protect the integrity of information on mobile devices defined in AC-19 (5), CCI 2329.'),
('002232','draft','2013-06-24','DISA FSO','policy','The organization defines software that is restricted from executing at a higher privilege than users executing the software.','AC-6(8).1','DoD has defined the software as any software except software explicitly documented.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the software as any software except software explicitly documented.'),
('002233','draft','2013-06-24','DISA FSO','technical','The information system prevents organization-defined software from executing at higher privilege levels than users executing the software.','AC-6(8).2','The organization being inspected/assessed configures the information system to any software except software explicitly documented from executing at higher privilege levels than users executing the software. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2233. DoD has defined the software as any software except software explicitly documented.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent any software except software explicitly documented from executing at higher privilege levels than users executing the software. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2233. DoD has defined the software as any software except software explicitly documented.'),
('002234','draft','2013-06-24','DISA FSO','technical','The information system audits the execution of privileged functions.','AC-6(9).1','The organization being inspected/assessed configures the information system to audit the execution of privileged functions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2234.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to audit the execution of privileged functions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2234.'),
('002235','draft','2013-06-24','DISA FSO','technical','The information system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.','AC-6(10).1','The organization being inspected/assessed configures the information system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2235.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2235.'),
('002236','draft','2013-06-24','DISA FSO','policy','The organization defines the time period the information system will automatically lock the account or node when the maximum number of unsuccessful logon attempts is exceeded.','AC-7.4','DoD has defined the time period as until released by an administrator.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as until released by an administrator.'),
('002237','draft','2013-06-24','DISA FSO','policy','The organization defines the delay algorithm to be employed by the information system to delay the next logon prompt when the maximum number of unsuccessful logon attempts is exceeded.','AC-7.5','DoD has defined the delay algorithm as a minimum of 5 seconds.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the delay algorithm as a minimum of 5 seconds.'),
('002238','draft','2013-06-24','DISA FSO','technical','The information system automatically locks the account or node for either an organization-defined time period, until the locked account or node is released by an administrator, or delays the next logon prompt according to the organization-defined delay algorithm when the maximum number of unsuccessful logon attempts is exceeded.','AC-7.6','The organization being inspected/assessed configures the information system to automatically lock the account or node until the locked account is released by an administrator and delays the next login prompt for a minimum of 5 seconds when the maximum number of unsuccessful attempts is exceeded. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2238. DoD has defined the delay algorithm as a minimum of 5 seconds. DoD has defined the time period as until released by an administrator.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically lock the account or node until the locked account is released by an administrator and delays the next login prompt for a minimum of 5 seconds when the maximum number of unsuccessful attempts is exceeded. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2238. DoD has defined the delay algorithm as a minimum of 5 seconds. DoD has defined the time period as until released by an administrator.'),
('002239','draft','2013-06-24','DISA FSO','policy','The organization defines the mobile devices that are to be purged/wiped by the information system after an organization-defined number of consecutive, unsuccessful device logon attempts.','AC-7(2).1','The organization being inspected/assessed defines and documents the mobile devices that are to be purged/wiped by the information system after an organization-defined number of consecutive, unsuccessful device logon attempts. Mobile devices may be defined in terms of manufacturer and model name. DoD has determined the mobile devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented mobile devices to ensure the organization being inspected/assessed defines the mobile devices that are to be purged/wiped by the information system after an organization-defined number of consecutive, unsuccessful device logon attempts. DoD has determined the mobile devices are not appropriate to define at the Enterprise level.'),
('002240','draft','2013-06-24','DISA FSO','policy','The organization defines the purging/wiping requirements/techniques to be used by the information system on organization-defined mobile devices after an organization-defined number of consecutive, unsuccessful device logon attempts.','AC-7(2).2','DoD has defined the purging/wiping requirements/techniques as requirements and techniques identified in NIST SP 800-88, \"Guidelines for Media Sanitization.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the purging/wiping requirements/techniques as requirements and techniques identified in NIST SP 800-88, \"Guidelines for Media Sanitization.\"'),
('002241','draft','2013-06-24','DISA FSO','policy','The organization defines the number of consecutive, unsuccessful device logon attempts after which the information system will purge/wipe organization-defined mobile devices.','AC-7(2).3','DoD has defined the number as 10.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the number as 10.'),
('002242','draft','2013-06-24','DISA FSO','technical','The information system purges/wipes information from organization-defined mobile devices based on organization-defined purging/wiping requirements/techniques after an organization-defined number of consecutive, unsuccessful device logon attempts.','AC-7(2).4','The organization being inspected/assessed configures the information system to purge/wipe information from mobile devices defined in AC-7 (2), CCI 2239 based on requirements and techniques identified in NIST SP 800-88, \"Guidelines for Media Sanitization\" after 10 consecutive, unsuccessful device logon attempts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2242. DoD has defined the number as 10. DoD has defined the purging/wiping requirements/techniques as requirements and techniques identified in NIST SP 800-88, \"Guidelines for Media Sanitization.\"','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to purge/wipe information from mobile devices defined in AC-7 (2), CCI 2239 based on requirements and techniques identified in NIST SP 800-88, \"Guidelines for Media Sanitization\" after 10 consecutive, unsuccessful device logon attempts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2242. DoD has defined the number as 10. DoD has defined the purging/wiping requirements/techniques as requirements and techniques identified in NIST SP 800-88, \"Guidelines for Media Sanitization.\"'),
('002243','draft','2013-06-24','DISA FSO','policy','The organization-defined information system use notification message or banner is to state that users are accessing a U.S. Government information system.','AC-8.3','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.'),
('002244','draft','2013-06-24','DISA FSO','policy','The organization-defined information system use notification message or banner is to state that information system usage may be monitored, recorded, and subject to audit.','AC-8.4','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.'),
('002245','draft','2013-06-24','DISA FSO','policy','The organization-defined information system use notification message or banner is to state that unauthorized use of the information system is prohibited and subject to criminal and civil penalties.','AC-8.5','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.'),
('002246','draft','2013-06-24','DISA FSO','policy','The organization-defined information system use notification message or banner is to state that use of the information system indicates consent to monitoring and recording.','AC-8.6','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.','DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013 meets the DoD requirements the information system use notification message or banner.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DTM 08-060.'),
('002247','draft','2013-06-24','DISA FSO','policy','The organization defines the use notification message or banner the information system displays to users before granting access to the system.','AC-8.2','DoD has defined the use notification message or banner as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the use notification message or banner as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013.'),
('002248','draft','2013-06-24','DISA FSO','policy','The organization defines the conditions of use which are to be displayed to users of the information system before granting further access.','AC-8.9','DoD has defined the conditions as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the conditions as the content of DTM 08-060, \"Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement,\" March 2013.'),
('002249','draft','2013-06-24','DISA FSO','policy','The organization defines the information, in addition to the date and time of the last logon (access), to be included in the notification to the user upon successful logon (access).','AC-9(4).1','The organization being inspected/assessed defines and documents the information, in addition to the date and time of the last logon (access) to be included in the notification to the user upon successful logon (access). DoD has determined the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information to ensure the organization being inspected/assessed defines the information, in addition to the date and time of the last logon (access) to be included in the notification to the user upon successful logon (access). DoD has determined the information is not appropriate to define at the Enterprise level.'),
('002250','draft','2013-06-24','DISA FSO','technical','The information system notifies the user, upon successful logon (access), of the organization-defined information to be included in addition to the date and time of the last logon (access).','AC-9(4).2','The organization being inspected/assessed configures the information system to notify the user, upon successful logon (access), of the information defined in AC-9 (4), CCI 2249 to be included in addition to the date and time of the last logon (access). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2250. ','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to notify the user, upon successful logon (access), of the information defined in AC-9 (4), CCI 2249 to be included in addition to the date and time of the last logon (access). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2250.'),
('002251','deprecated','2013-06-24','DISA FSO','technical','The information system notifies the user, upon successful logon (access), of the date and time of the last logon (access).',NULL,NULL,NULL),
('002252','draft','2013-06-24','DISA FSO','policy','The organization defines the accounts and/or account types for which the information system will limit the number of concurrent sessions.','AC-10.3','DoD has defined the account types and/or accounts as all account types and/or accounts.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the account types and/or accounts as all account types and/or accounts.'),
('002253','deprecated','2013-06-24','DISA FSO','policy','The organization defines the account types for which the information system will limit the number of concurrent sessions.',NULL,NULL,NULL),
('002254','deprecated','2013-06-24','DISA FSO','policy','The organization defines the conditions or trigger events requiring session disconnect to be employed by the information system when automatically terminating a user session.',NULL,NULL,NULL),
('002255','deprecated','2013-06-24','DISA FSO','policy','The organization defines the user actions that can be performed on the information system without identification and authentication.',NULL,NULL,NULL),
('002256','draft','2013-06-24','DISA FSO','policy','The organization defines security attributes having organization-defined types of security attribute values which are associated with information in storage.','AC-16.1','The organization being inspected/assessed defines and documents the security attributes having organization-defined types of security attribute values which are associated with information in storage. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines security attributes having organization-defined types of security attribute values which are associated with information in storage. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002257','draft','2013-06-24','DISA FSO','policy','The organization defines security attributes having organization-defined types of security attribute values which are associated with information in process.','AC-16.2','The organization being inspected/assessed defines and documents the security attributes having organization-defined types of security attribute values which are associated with information in process. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines security attributes having organization-defined types of security attribute values process. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002258','draft','2013-06-24','DISA FSO','policy','The organization defines security attributes, having organization-defined types of security attribute values, which are associated with information in transmission.','AC-16.3','The organization being inspected/assessed defines and documents the security attributes having organization-defined types of security attribute values which are associated with information in transmission. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines security attributes having organization-defined types of security attribute values which are associated with information in transmission. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002259','draft','2013-06-24','DISA FSO','policy','The organization defines security attribute values associated with organization-defined types of security attributes for information in storage.','AC-16.4','The organization being inspected/assessed defines and documents the security attributes values associated with organization-defined types of security attributes for information in storage. DoD has determined the security attribute values are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attribute values to ensure the organization being inspected/assessed defines security attribute values associated with organization-defined types of security attributes for information in storage. DoD has determined the security attribute values are not appropriate to define at the Enterprise level.'),
('002260','draft','2013-06-24','DISA FSO','policy','The organization defines security attribute values associated with organization-defined types of security attributes for information in process.','AC-16.5','The organization being inspected/assessed defines and documents the security attributes values associated with organization-defined types of security attributes for information in process. DoD has determined the security attribute values are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attribute values to ensure the organization being inspected/assessed defines security attribute values associated with organization-defined types of security attributes for information in process. DoD has determined the security attribute values are not appropriate to define at the Enterprise level.'),
('002261','draft','2013-06-24','DISA FSO','policy','The organization defines security attribute values associated with organization-defined types of security attributes for information in transmission.','AC-16.6','The organization being inspected/assessed defines and documents the security attributes values associated with organization-defined types of security attributes for information in transmission. DoD has determined the security attribute values are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attribute values to ensure the organization being inspected/assessed defines security attribute values associated with organization-defined types of security attributes for information in transmission. DoD has determined the security attribute values are not appropriate to define at the Enterprise level.'),
('002262','draft','2013-06-24','DISA FSO','technical','The organization provides the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in storage.','AC-16.7','The organization being inspected/assessed configures the information system to provide the means to associate types of security attributes in defined in AC-16, CCI 2256 having security attribute values defined in AC-16, CCI 2259 with information in storage. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2262.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the means to associate types of security attributes in defined in AC-16, CCI 2256 having security attribute values defined in AC-16, CCI 2259 with information in storage. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2262.'),
('002263','draft','2013-06-24','DISA FSO','technical','The organization provides the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in process.','AC-16.8','The organization being inspected/assessed configures the information system to provide the means to associate types of security attributes in defined in AC-16, CCI 2257 having security attribute values defined in AC-16, CCI 2260 with information in process. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2263.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the means to associate types of security attributes in defined in AC-16, CCI 2257 having security attribute values defined in AC-16, CCI 2260 with information in process. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2263.'),
('002264','draft','2013-06-24','DISA FSO','technical','The organization provides the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.','AC-16.9','The organization being inspected/assessed configures the information system to provide the means to associate types of security attributes in defined in AC-16, CCI 2258 having security attribute values defined in AC-16, CCI 2261 with information in transmission. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2264.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the means to associate types of security attributes in defined in AC-16, CCI 2258 having security attribute values defined in AC-16, CCI 2261 with information in transmission. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2264.'),
('002265','draft','2013-06-24','DISA FSO','policy','The organization ensures that the security attribute associations are made with the information.','AC-16.10','The organization being inspected/assessed documents and implements a process to ensure that the security attribute associations are made with the information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that the security attribute associations are made with the information.'),
('002266','draft','2013-06-24','DISA FSO','policy','The organization ensures that the security attribute associations are retained with the information.','AC-16.11','The organization being inspected/assessed documents and implements a process to ensure that the security attribute associations are retained with the information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that the security attribute associations are retained with the information.'),
('002267','draft','2013-06-24','DISA FSO','policy','The organization defines the security attributes that are permitted for organization-defined information systems.','AC-16.12','DoD has defined the security attributes as the security attributes defined in AC-16, CCIs 2256-2258.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security attributes as the security attributes defined in AC-16, CCIs 2256-2258.'),
('002268','draft','2013-06-24','DISA FSO','policy','The organization defines the information systems for which permitted organization-defined attributes are to be established.','AC-16.13','DoD has defined the information systems as all information systems.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information systems as all information systems.'),
('002269','draft','2013-06-24','DISA FSO','policy','The organization establishes the permitted organization-defined security attributes for organization-defined information systems.','AC-16.14','The organization being inspected/assessed establishes and documents the permitted security attributes for all information systems as a subset of the security attributes defined in AC-16, CCI 2267. DoD has defined the information systems as all information systems.','The organization conducting the inspection/assessment obtains and examines the documented list of permitted security attributes to ensure the organization being inspected/assessed has established the list of permitted security attributes for all information systems as a subset of the security attributes defined in AC-16, CCI 2267. DoD has defined the information systems as all information systems.'),
('002270','draft','2013-06-24','DISA FSO','policy','The organization defines the values or ranges permitted for each of the established security attributes.','AC-16.15','DoD has defined the values or ranges as the values defined in AC-16, CCIs 2259-2261.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the values or ranges as the values defined in AC-16, CCIs 2259-2261.'),
('002271','draft','2013-06-24','DISA FSO','policy','The organization determines the permitted organization-defined values or ranges for each of the established security attributes.','AC-16.16','The organization being inspected/assessed establishes and documents the permitted values or ranges for each of the established security attributes as a subset of the values or ranges defined in AC-16, CCI 2270.','The organization conducting the inspection/assessment obtains and examines the documented permitted values or ranges to ensure the organization being inspected/assessed has established the permitted values or ranges for each of the established security attributes as a subset of the values or ranges defined in AC-16, CCI 2270.'),
('002272','draft','2013-06-24','DISA FSO','technical','The information system dynamically associates security attributes with organization-defined objects in accordance with organization-defined security policies as information is created and combined.','AC-16(1).2','The organization being inspected/assessed configures the information system to dynamically associates security attributes with the objects defined in AC-16 (1), CCI 2275 in accordance with the security policies defined in AC-16 (1), CCI 2273 as information is created and combined. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2272.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to dynamically associates security attributes with the objects defined in AC-16 (1), CCI 2275 in accordance with the security policies defined in AC-16 (1), CCI 2273 as information is created and combined. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2272.'),
('002273','draft','2013-06-24','DISA FSO','policy','The organization defines the security policies the information system is to adhere to when dynamically associating security attributes with organization-defined subjects and objects.','AC-16(1).3','The organization being inspected/assessed defines and documents the security policies the information system is to adhere to when dynamically associating security attributes with organization-defined subjects and objects. DoD has determined the security policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policies to ensure the organization being inspected/assessed defines the security policies the information system is to adhere to when dynamically associating security attributes with organization-defined subjects and objects. DoD has determined the security policies are not appropriate to define at the Enterprise level.'),
('002274','draft','2013-06-24','DISA FSO','policy','The organization defines the subjects with which the information system is to dynamically associate security attributes as information is created and combined.','AC-16(1).4','The organization being inspected/assessed defines and documents the subjects the information system is to dynamically associate security attributes to as information is created and combined. DoD has determined the subjects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented objects to ensure the organization being inspected/assessed defines the subjects the information system is to dynamically associate security attributes to as information is created and combined. DoD has determined the subjects are not appropriate to define at the Enterprise level.'),
('002275','draft','2013-06-24','DISA FSO','policy','The organization defines the objects with which the information system is to dynamically associate security attributes as information is created and combined.','AC-16(1).5','The organization being inspected/assessed defines and documents the objects the information system is to dynamically associate security attributes to as information is created and combined. DoD has determined the objects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented objects to ensure the organization being inspected/assessed defines the objects the information system is to dynamically associate security attributes to as information is created and combined. DoD has determined the objects are not appropriate to define at the Enterprise level.'),
('002276','draft','2013-06-24','DISA FSO','policy','The organization identifies the individuals authorized to define the value of associated security attributes.','AC-16(2).3','The organization being inspected/assessed identifies and documents the individuals authorized to define the value of associated security attributes.','The organization conducting the inspection/assessment obtains and examines the documented individuals to ensure the organization being inspected/assessed identifies the individuals authorized to define the value of associated security attributes.'),
('002277','draft','2013-06-24','DISA FSO','technical','The information system provides authorized individuals (or processes acting on behalf of individuals) the capability to define the value of associated security attributes.','AC-16(2).4','The organization being inspected/assessed configures the information system to provide authorized individuals (or processes acting on behalf of individuals) the capability to define the value of associated security attributes. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2277.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide authorized individuals (or processes acting on behalf of individuals) the capability to define the value of associated security attributes. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2277.'),
('002278','draft','2013-06-24','DISA FSO','policy','The organization defines security attributes for which the association and integrity to organization-defined subjects and objects is maintained by the information system.','AC-16(3).1','he organization being inspected/assessed defines and documents the security attributes for which the association and integrity to organization-defined subjects and objects is maintained by the information system DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines the security attributes for which the association and integrity to organization-defined subjects and objects is maintained by the information system. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002279','draft','2013-06-24','DISA FSO','policy','The organization defines subjects for which the association and integrity of organization-defined security attributes is maintained by the information system.','AC-16(3).2','The organization being inspected/assessed defines and documents the subjects for which the association and integrity of organization-defined security attributes is maintained by the information system. DoD has determined the subjects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented subjects to ensure the organization being inspected/assessed defines the subjects for which the association and integrity of organization-defined security attributes is maintained by the information system. DoD has determined the subjects are not appropriate to define at the Enterprise level.'),
('002280','draft','2013-06-24','DISA FSO','policy','The organization defines objects for which the association and integrity of organization-defined security attributes is maintained by the information system.','AC-16(3).3','The organization being inspected/assessed defines and documents the objects for which the association and integrity of organization-defined security attributes is maintained by the information system. DoD has determined the objects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented subjects to ensure the organization being inspected/assessed defines the objects for which the association and integrity of organization-defined security attributes is maintained by the information system. DoD has determined the objects are not appropriate to define at the Enterprise level.'),
('002281','draft','2013-06-24','DISA FSO','technical','The information system maintains the association of organization-defined security attributes to organization-defined subjects.','AC-16(3).4','The organization being inspected/assessed configures the information system to maintain the association of the security attributes defined in AC-16 (3), CCI 2278 to subjects defined in AC-16 (3), CCI 2279. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2281.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain the association of the security attributes defined in AC-16 (3), CCI 2278 to subjects defined in AC-16 (3), CCI 2280 For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2281.'),
('002282','draft','2013-06-24','DISA FSO','technical','The information system maintains the association of organization-defined security attributes to organization-defined objects.','AC-16(3).5','The organization being inspected/assessed configures the information system to maintain the association of the security attributes defined in AC-16 (3), CCI 2278 to objects defined in AC-16 (3), CCI 2280. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2282.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain the association of the security attributes defined in AC-16 (3), CCI 2278 to objects defined in AC-16 (3), CCI 2280 For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2282.'),
('002283','draft','2013-06-24','DISA FSO','technical','The information system maintains the integrity of organization-defined security attributes associated with organization-defined subjects.','AC-16(3).6','The organization being inspected/assessed configures the information system to maintain the integrity of the security attributes defined in AC-16 (3), CCI 2278 to subjects defined in AC-16 (3), CCI 2279. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2283.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain the integrity of the security attributes defined in AC-16 (3), CCI 2278 to subjects defined in AC-16 (3), CCI 2279. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2283.'),
('002284','draft','2013-06-24','DISA FSO','technical','The information system maintains the integrity of organization-defined security attributes associated with organization-defined objects.','AC-16(3).7','The organization being inspected/assessed configures the information system to maintain the integrity of the security attributes defined in AC-16 (3), CCI 2278 to objects defined in AC-16 (3), CCI 2280. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2284.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information to maintain the integrity of the security attributes defined in AC-16 (3), CCI 2278 to objects defined in AC-16 (3), CCI 2280. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2284.'),
('002285','draft','2013-06-24','DISA FSO','policy','The organization identifies individuals (or processes acting on behalf of individuals) authorized to associate organization-defined security attributes with organization-defined subjects.','AC-16(4).2','The organization being inspected/assessed identifies and documents individuals (or processes acting on behalf of individuals) authorized to associate security attributes defined in AC-16 (4), CCI 2288 with subjects defined in AC-16 (4), CCI 2286.','The organization conducting the inspection/assessment obtains and examines the documented individuals to ensure the organization being inspected/assessed identifies individuals (or processes acting on behalf of individuals) authorized to associate security attributes defined in AC-16 (4), CCI 2288 with subjects defined in AC-16 (4), CCI 2286.'),
('002286','draft','2013-06-24','DISA FSO','policy','The organization defines the subjects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals).','AC-16(4).3','The organization being inspected/assessed defines and documents the subjects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals). DoD has defined the subjects as not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented objects to ensure the organization being inspected/assessed defines the subjects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals). DoD has defined the subjects as not appropriate to define at the Enterprise level.'),
('002287','draft','2013-06-24','DISA FSO','policy','The organization defines the objects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals).','AC-16(4).4','The organization being inspected/assessed defines and documents the objects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals). DoD has defined the objects as not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented objects to ensure the organization being inspected/assessed defines the objects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals). DoD has defined the objects as not appropriate to define at the Enterprise level.'),
('002288','draft','2013-06-24','DISA FSO','policy','The organization defines the security attributes authorized individuals (or processes acting on behalf of individuals) are permitted to associate with organization-defined subjects and objects.','AC-16(4).5','The organization being inspected/assessed defines and documents the security attributes authorized individuals (or processes acting on behalf of individuals) are permitted to associate with organization-defined subjects and objects. DoD has defined the security attributes as not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines the security attributes authorized individuals (or processes acting on behalf of individuals) are permitted to associate with organization-defined subjects and objects. DoD has defined the security attributes as not appropriate to define at the Enterprise level.'),
('002289','draft','2013-06-24','DISA FSO','technical','The information system supports the association of organization-defined security attributes with organization-defined subjects by authorized individuals (or processes acting on behalf of individuals).','AC-16(4).6','The organization being inspected/assessed configures the information system to support the association of security attributes defined in AC-16 (4), CCI 2288 with the subjects defined in AC-16 (4), CCI 2286 by authorized individuals (or processes acting on behalf of individuals). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2289.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to support the association of security attributes defined in AC-16 (4), CCI 2288 with the subjects defined in AC-16 (4), CCI 2286 by authorized individuals (or processes acting on behalf of individuals). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2289.'),
('002290','draft','2013-06-24','DISA FSO','technical','The information system supports the association of organization-defined security attributes with organization-defined objects by authorized individuals (or processes acting on behalf of individuals).','AC-16(4).7','The organization being inspected/assessed configures the information system to support the association of security attributes defined in AC-16 (4), CCI 2288 with the objects defined in AC-16 (4), CCI 2287 by authorized individuals (or processes acting on behalf of individuals). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2290.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to support the association of security attributes defined in AC-16 (4), CCI 2288 with the objects defined in AC-16 (4), CCI 2287 by authorized individuals (or processes acting on behalf of individuals). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2290.'),
('002291','draft','2013-06-24','DISA FSO','policy','The organization defines the security policies to be followed by personnel when associating organization-defined security attributes with organization-defined subjects and objects.','AC-16(6).1','The organization being inspected/assessed defines and documents the security policies to be followed by personnel when associating organization-defined security attributes with organization-defined subjects and objects. DoD has determined the security policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policies to ensure the organization being inspected/assessed defines the security policies to be followed by personnel when associating organization-defined security attributes with organization-defined subjects and objects. DoD has determined the security policies are not appropriate to define at the Enterprise level.'),
('002292','draft','2013-06-24','DISA FSO','policy','The organization defines the security attributes which are to be associated with organization-defined subjects and objects.','AC-16(6).2','The organization being inspected/assessed defines and documents the security attributes which are to be associated with organization-defined subjects and objects. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines the security attributes which are to be associated with organization-defined subjects and objects. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002293','draft','2013-06-24','DISA FSO','policy','The organization defines the subjects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies.','AC-16(6).3','The organization being inspected/assessed defines and documents the subjects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies. DoD has determined the subjects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented subjects to ensure the organization being inspected/assessed defines the subjects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies. DoD has determined the subjects are not appropriate to define at the Enterprise level.'),
('002294','draft','2013-06-24','DISA FSO','policy','The organization defines the objects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies.','AC-16(6).4','The organization being inspected/assessed defines and documents the objects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies. DoD has determined the objects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented objects to ensure the organization being inspected/assessed defines the objects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies. DoD has determined the objects are not appropriate to define at the Enterprise level.'),
('002295','draft','2013-06-24','DISA FSO','policy','The organization allows personnel to associate organization-defined security attributes with organization-defined subjects in accordance with organization-defined security policies.','AC-16(6).5','The organization being inspected/assessed documents and implements a process requiring personnel to associate security attributes defined in AC-16 (6), CCI 2292 with subjects defined in AC-16 (6), CCI 2293 in accordance with security policies defined in AC-16 (6), CCI 2291.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires personnel to associate security attributes defined in AC-16 (6), CCI 2292 with subjects defined in AC-16 (6), CCI 2293 in accordance with security policies defined in AC-16 (6), CCI 2291.'),
('002296','draft','2013-06-24','DISA FSO','policy','The organization allows personnel to associate organization-defined security attributes with organization-defined objects in accordance with organization-defined security policies.','AC-16(6).6','The organization being inspected/assessed documents and implements a process requiring personnel to associate security attributes defined in AC-16 (6), CCI 2292 with objects defined in AC-16 (6), CCI 2294 in accordance with security policies defined in AC-16 (6), CCI 2291.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires personnel to associate security attributes defined in AC-16 (6), CCI 2292 with objects defined in AC-16 (6), CCI 2294 in accordance with security policies defined in AC-16 (6), CCI 2291.'),
('002297','draft','2013-06-24','DISA FSO','policy','The organization allows personnel to maintain the association of organization-defined security attributes with organization-defined subjects in accordance with organization-defined security policies.','AC-16(6).7','The organization being inspected/assessed documents and implements a process requiring personnel to maintain the association of security attributes defined in AC-16 (6), CCI 2292 with subjects defined in AC-16 (6), CCI 2293 in accordance with security policies defined in AC-16 (6), CCI 2291.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires personnel to maintain the association of security attributes defined in AC-16 (6), CCI 2292 with subjects defined in AC-16 (6), CCI 2293 in accordance with security policies defined in AC-16 (6), CCI 2291.'),
('002298','draft','2013-06-24','DISA FSO','policy','The organization allows personnel to maintain the association of organization-defined security attributes with organization-defined objects in accordance with organization-defined security policies.','AC-16(6).8','The organization being inspected/assessed documents and implements a process requiring personnel to maintain the association of security attributes defined in AC-16 (6), CCI 2292 with objects defined in AC-16 (6), CCI 2294 in accordance with security policies defined in AC-16 (6), CCI 2291.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires personnel to maintain the association of security attributes defined in AC-16 (6), CCI 2292 with objects defined in AC-16 (6), CCI 2294 in accordance with security policies defined in AC-16 (6), CCI 2291.'),
('002299','draft','2013-06-24','DISA FSO','policy','The organization provides a consistent interpretation of security attributes transmitted between distributed information system components.','AC-16(7).1','The organization being inspected/assessed documents and implements a process to provide a consistent interpretation of security attributes transmitted between distributed information system components.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides a consistent interpretation of security attributes transmitted between distributed information system components.'),
('002300','draft','2013-06-24','DISA FSO','policy','The organization defines the techniques or technologies to be implemented when associating security attributes with information.','AC-16(8).1','The organization being inspected/assessed defines and documents the techniques or technologies to be implemented when associating security attributes with information. DoD has determined the technique or technologies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques and technologies to ensure the organization being inspected/assessed defines the techniques or technologies to be implemented when associating security attributes with information. DoD has determined the technique or technologies are not appropriate to define at the Enterprise level.'),
('002301','draft','2013-06-24','DISA FSO','policy','The organization defines the level of assurance to be provided when implementing organization-defined techniques or technologies in associating security attributes to information.','AC-16(8).2','The organization being inspected/assessed defines and documents the level of assurance to be provided when implementing organization-defined techniques or technologies in associating security attributes to information. DoD has determined the level of assurance is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of assurance to ensure the organization being inspected/assessed defines the level of assurance to be provided when implementing organization-defined techniques or technologies in associating security attributes to information. DoD has determined the level of assurance is not appropriate to define at the Enterprise level.'),
('002302','draft','2013-06-24','DISA FSO','technical','The information system implements organization-defined techniques or technologies with an organization-defined level of assurance in associating security attributes to information.','AC-16(8).3','The organization being inspected/assessed configures the information system to implement the techniques or technologies defined in AC-16 (8), CCI 2300 with the level of assurance defined in AC-16 (8), CCI 2301 in associating security attributes to information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2302.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement the techniques or technologies defined in AC-16 (8), CCI 2300 with the level of assurance defined in AC-16 (8), CCI 2301 in associating security attributes to information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2302.'),
('002303','draft','2013-06-24','DISA FSO ','policy','The organization defines the techniques or procedures to be employed to validate re-grading mechanisms.','AC-16(9).1','The organization being inspected/assessed defines and documents the techniques or procedures to be employed to validate re-grading mechanisms. DoD has determined the techniques or procedures are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques or procedures to ensure the organization being inspected/assessed defines the techniques or procedures to be employed to validate re-grading mechanisms. DoD has determined the techniques or procedures are not appropriate to define at the Enterprise level.'),
('002304','draft','2013-06-24','DISA FSO','policy','The organization ensures security attributes associated with information are reassigned only via re-grading mechanisms validated using organization-defined techniques or procedures.','AC-16(9).2','The organization being inspected/assessed documents and implements a process to ensure security attributes associated with information are reassigned only via re-grading mechanisms validated using techniques or procedures defined in AC-16 (9), CCI 2303.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures security attributes associated with information are reassigned only via re-grading mechanisms validated using techniques or procedures defined in AC-16 (9), CCI 2303.'),
('002305','draft','2013-06-24','DISA FSO','policy','The organization identifies individuals authorized to define or change the type and value of security attributes available for association with subjects and objects.','AC-16(10).1','The organization being inspected/assessed identifies and documents individuals authorized to define or change the type and value of security attributes available for association with subjects and objects.','The organization conducting the inspection/assessment obtains and examines the documented individuals to ensure the organization being inspected/assessed identifies individuals authorized to define or change the type and value of security attributes available for association with subjects and objects.'),
('002306','draft','2013-06-24','DISA FSO','technical','The information system provides authorized individuals the capability to define or change the type of security attributes available for association with subjects.','AC-16(10).2','The organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the type of security attributes available for association with subjects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2306.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the type of security attributes available for association with subjects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2306.'),
('002307','draft','2013-06-24','DISA FSO','technical','The information system provides authorized individuals the capability to define or change the value of security attributes available for association with subjects.','AC-16(10).3','The organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the value of security attributes available for association with subjects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2307.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the value of security attributes available for association with subjects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2307.'),
('002308','draft','2013-06-24','DISA FSO','technical','The information system provides authorized individuals the capability to define or change the type of security attributes available for association with objects.','AC-16(10).4','The organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the type of security attributes available for association with objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2308.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the type of security attributes available for association with objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2308.'),
('002309','draft','2013-06-24','DISA FSO','technical','The information system provides authorized individuals the capability to define or change the value of security attributes available for association with objects.','AC-16(10).5','The organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the value of security attributes available for association with objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2309.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide authorized individuals the capability to define or change the value of security attributes available for association with objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2309.'),
('002310','draft','2013-06-24','DISA FSO','policy','The organization establishes and documents usage restrictions for each type of remote access allowed.','AC-17.2','The organization being inspected/assessed establishes and documents usage restrictions for each type of remote access allowed.','The organization conducting the inspection/assessment obtains and examines the documented usage restrictions to ensure the organization being inspected/assessed establishes and documents usage restrictions for each type of remote access allowed.'),
('002311','draft','2013-06-24','DISA FSO','policy','The organization establishes and documents configuration/connection requirements for each type of remote access allowed.','AC-17.3','The organization being inspected/assessed establishes and documents configuration/connection requirements for each type of remote access allowed.','The organization conducting the inspection/assessment obtains and examines the documented requirements to ensure the organization being inspected/assessed establishes and documents configuration/connection requirements for each type of remote access allowed.'),
('002312','draft','2013-06-24','DISA FSO','policy','The organization establishes and documents implementation guidance for each type of remote access allowed.','AC-17.4','The organization being inspected/assessed establishes and documents implementation guidance for each type of remote access allowed.','The organization conducting the inspection/assessment obtains and examines the documented implementation guidance to ensure the organization being inspected/assessed establishes and documents implementation guidance for each type of remote access allowed.'),
('002313','deprecated','2013-06-24','DISA FSO','technical','The information system controls remote access methods.',NULL,NULL,NULL),
('002314','draft','2013-06-24','DISA FSO','technical','The information system controls remote access methods.','AC-17(1).2','The organization being inspected/assessed configures the information system to control remote access methods. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2314.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to control remote access methods. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2314.'),
('002315','draft','2013-06-24','DISA FSO','policy','The organization defines the number of managed network access control points through which the information system routes all remote access.','AC-17(3).3','The organization being inspected/assessed defines and documents the number of managed network access control points through which the information system routes all remote access. DoD has determined the number is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented number to ensure the organization being inspected/assessed defines the number of managed network access control points through which the information system routes all remote access. DoD has determined the number is not appropriate to define at the Enterprise level.'),
('002316','draft','2013-06-24','DISA FSO','policy','The organization authorizes access to security-relevant information via remote access only for organization-defined needs.','AC-17(4).2','The organization being inspected/assessed authorizes the access to security-relevant information via remote access only for needs defined in AC-17 (4), CCI 2318. The organization being inspected/assessed maintains an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed authorizes the access to security-relevant information via remote access only for needs defined in AC-17 (4), CCI 2318.'),
('002317','draft','2013-06-24','DISA FSO','policy','The organization defines the operational needs for when the execution of privileged commands via remote access is to be authorized.','AC-17(4).3','The organization being inspected/assessed defines and documents the operational needs when the execution of privileged commands via remote access is to be authorized. DoD has determined the operational needs are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented operational needs to ensure the organization being inspected/assessed defines the operational needs when the execution of privileged commands via remote access is to be authorized. DoD has determined the operational needs are not appropriate to define at the Enterprise level.'),
('002318','draft','2013-06-24','DISA FSO','policy','The organization defines the operational needs for when access to security-relevant information via remote access is to be authorized.','AC-17(4).4','The organization being inspected/assessed defines and documents the operational needs when access to security-relevant information via remote access is to be authorized. DoD has determined the operational needs are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented operational needs to ensure the organization being inspected/assessed defines the operational needs when access to security-relevant information via remote access is to be authorized. DoD has determined the operational needs are not appropriate to define at the Enterprise level.'),
('002319','draft','2013-06-24','DISA FSO','policy','The organization documents in the security plan for the information system the rationale for authorization of the execution of privilege commands via remote access.','AC-17(4).5','The organization being inspected/assessed documents in the security plan for the information system the rationale for authorization of the execution of privilege commands via remote access.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed documents in the security plan for the information system the rationale for authorization of the execution of privilege commands via remote access.'),
('002320','draft','2013-06-24','DISA FSO','policy','The organization documents in the security plan for the information system the rationale for authorization of access to security-relevant information via remote access.','AC-17(4).6','The organization being inspected/assessed documents in the security plan for the information system the rationale for authorization of access to security-relevant information via remote access.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed documents in the security plan for the information system the rationale for authorization of access to security-relevant information via remote access.'),
('002321','draft','2013-06-24','DISA FSO','policy','The organization defines the time period within which it disconnects or disables remote access to the information system.','AC-17(9).1','DoD has defined the time period as immediately.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediately.'),
('002322','draft','2013-06-24','DISA FSO','technical','The organization provides the capability to expeditiously disconnect or disable remote access to the information system within the organization-defined time period.','AC-17(9).2','The organization being inspected/assessed configures the information system to provide the capability to expeditiously disconnect or disable remote access to the information system immediately. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2322. DoD has defined the time period as immediately.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability to expeditiously disconnect or disable remote access to the information system immediately. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2322. DoD has defined the time period as immediately.'),
('002323','draft','2013-06-24','DISA FSO','policy','The organization establishes configuration/connection requirements for wireless access.','AC-18.3','The organization being inspected/assessed establishes and documents configuration/connection requirements for wireless access.','The organization conducting the inspection/assessment obtains and examines the documented configuration/connection requirements to ensure the organization being inspected/assessed establishes configuration/connection requirements for wireless access.'),
('002324','draft','2013-06-24','DISA FSO','policy','The organization identifies and explicitly authorizes users allowed to independently configure wireless networking capabilities.','AC-18(4).1','The organization being inspected/assessed identifies and explicitly authorizes users allowed to independently configure wireless networking capabilities. The organization must maintain an audit trail of authorizations.','The organization conducting the inspection/assessment obtains and examines the audit trail of authorizations to ensure the organization being inspected/assessed identifies and explicitly authorizes users allowed to independently configure wireless networking capabilities.'),
('002325','draft','2013-06-24','DISA FSO','policy','The organization establishes configuration requirements for organization-controlled mobile devices.','AC-19.3','DoD is automatically compliant with this CCI because existing STIGs establish configuration requirements for approved mobile devices.','DoD is automatically compliant with this CCI because existing STIGs establish configuration requirements for approved mobile devices.'),
('002326','draft','2013-06-24','DISA FSO','policy','The organization establishes connection requirements for organization-controlled mobile devices.','AC-19.4','The organization being inspected/assessed establishes and documents connection requirements for organization controlled mobile devices.','The organization conducting the inspection/assessment obtains and examines the documented connection requirements to ensure the organization being inspected/assessed establishes connection requirements for organization controlled mobile devices.'),
('002327','draft','2013-06-24','DISA FSO','policy','The organization defines the security policies which restrict the connection of classified mobile devices to classified information systems.','AC-19(4).8','The organization being inspected/assessed defines and documents the security policies which restrict the connection of classified mobile devices to classified information systems. DoD has determined the security policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security policies to ensure the organization being inspected/assessed defines the security policies which restrict the connection of classified mobile devices to classified information systems. DoD has determined the security policies are not appropriate to define at the Enterprise level.'),
('002328','draft','2013-06-24','DISA FSO','policy','The organization restricts the connection of classified mobile devices to classified information systems in accordance with organization-defined security policies.','AC-19(4).9','The organization being inspected/assessed documents and implements a process to restrict the connection of classified mobile devices to classified information systems in accordance with the security policies defined in AC-19 (4), CCI 2327.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed restricts the connection of classified mobile devices to classified information systems in accordance with the security policies defined in AC-19 (4), CCI 2327.'),
('002329','draft','2013-06-24','DISA FSO','policy','The organization defines the mobile devices that are to employ full-device or container encryption to protect the confidentiality and integrity of the information on the device.','AC-19(5).2','The organization being inspected/assessed defines and documents the mobile devices that are to employ full-device or container encryption to protect the confidentiality and integrity of the information on device. DoD has determined the mobile devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented mobile devices to ensure the organization being inspected/assessed defines the mobile devices that are to employ full-device or container encryption to protect the confidentiality and integrity of the information on device. DoD has determined the mobile devices are not appropriate to define at the Enterprise level.'),
('002330','draft','2013-06-24','DISA FSO','policy','The organization employs full-device encryption or container encryption to protect the confidentiality of information on organization-defined mobile devices.','AC-19(5).3','The organization being inspected/assessed documents and implements a process for full-device encryption or container encryption to protect the confidentiality of information on mobile devices defined in AC-19 (5), CCI 2329. ','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs full-device encryption or container encryption to protect the confidentiality of information on mobile devices defined in AC-19 (5), CCI 2329.'),
('002331','draft','2013-06-24','DISA FSO','policy','The organization employs full-device encryption or container encryption to protect the integrity of information on organization-defined mobile devices.','AC-6(7).4','The organization being inspected/assessed documents and implements a process to reassign or remove privileges, if necessary, to correctly reflect organizational mission/business needs.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed reassigns or removes privileges, if necessary, to correctly reflect organizational mission/business needs.'),
('002332','draft','2013-06-24','DISA FSO','policy','The organization establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to process, store, or transmit organization-controlled information using the external information systems.','AC-20.2','The organization being inspected/assessed establishes and documents the terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to process, store or transmit organization-controlled information using the external information systems.','The organization conducting the inspection/assessment obtains and examines the documented terms and conditions to ensure the organization being inspected/assessed establishes terms and conditions, consistent with any trust relationships established with other organizations owning, operating, and/or maintaining external information systems, allowing authorized individuals to process, store or transmit organization-controlled information using the external information systems.'),
('002333','draft','2013-06-24','DISA FSO','policy','The organization permits authorized individuals to use an external information system to access the information system only when the organization verifies the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.','AC-20(1).1','The organization being inspected/assessed documents and implements a process to permit authorized individuals to use an external information system to access the information system only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed permits authorized individuals to use an external information system to access the information system only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.'),
('002334','draft','2013-06-24','DISA FSO','policy','The organization permits authorized individuals to use an external information system to process organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.','AC-20(1).2','The organization being inspected/assessed documents and implements a process to permit authorized individuals to use an external information system to process organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed permits authorized individuals to use an external information system to process organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.'),
('002335','draft','2013-06-24','DISA FSO','policy','The organization permits authorized individuals to use an external information system to store organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.','AC-20(1).3','The organization being inspected/assessed documents and implements a process to permit authorized individuals to use an external information system to store organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed permits authorized individuals to use an external information system to store organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.'),
('002336','draft','2013-06-24','DISA FSO','policy','The organization permits authorized individuals to use an external information system to transmit organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organization^s information security policy and security plan.','AC-20(1).4','The organization being inspected/assessed documents and implements a process to permit authorized individuals to use an external information system to transmit organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed permits authorized individuals to use an external information system to transmit organization-controlled information only when the organization verifies the implementation of required security controls on the external system as specified in the organizations information security policy and security plan.'),
('002337','draft','2013-06-24','DISA FSO','policy','The organization permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization retains approved information system connection or processing agreements with the organizational entity hosting the external information system.','AC-20(1).5','The organization being inspected/assessed documents and implements a process to permit authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization retains approved information system connection or processing agreements with the organizational entity hosting the external information system.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed permits authorized individuals to use an external information system to access the information system or to process, store, or transmit organization-controlled information only when the organization retains approved information system connection or processing agreements with the organizational entity hosting the external information system.'),
('002338','draft','2013-06-24','DISA FSO','policy','The organization restricts or prohibits the use of non-organizationally owned information systems, system components, or devices to process, store, or transmit organizational information.','AC-20(3).1','The organization being inspected/assessed documents and implements a process to restrict or prohibit the use of non-organizationally owned information systems, system components, or devices to process, store, or transmit organizational information.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed restricts or prohibits the use of non-organizationally owned information systems, system components, or devices to process, store, or transmit organizational information.'),
('002339','draft','2013-06-24','DISA FSO','policy','The organization defines the network accessible storage devices that are to be prohibited from being used in external information systems.','AC-20(4).1','The organization being inspected/assessed defines and documents the network accessible storage devices that are to be prohibited from being used in external information systems. DoD has determined the network accessible storage devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented network accessible storage devices to ensure the organization being inspected/assessed defines the network accessible storage devices that are to be prohibited from being used in external information systems. DoD has determined the network accessible storage devices are not appropriate to define at the Enterprise level.'),
('002340','draft','2013-06-24','DISA FSO','policy','The organization prohibits the use of organization-defined network accessible storage devices in external information systems.','AC-20(4).2','The organization being inspected/assessed documents and implements a process to prohibit the use of network accessible storage devices defined in AC-20 (4), CCI 2339 in external information systems.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed prohibits the use of network accessible storage devices defined in AC-20 (4), CCI 2339 in external information systems.'),
('002341','draft','2013-06-25','DISA FSO','policy','The organization defines the information sharing restrictions to be enforced by the information system for information search and retrieval services.','AC-21(2).1','The organization being inspected/assessed defines and documents the information sharing restrictions to be enforced by the information system for information search and retrieval services. DoD has determined the information sharing restrictions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information sharing restrictions to ensure the organization being inspected/assessed defines the information sharing restrictions to be enforced by the information system for information search and retrieval services. DoD has determined the information sharing restrictions are not appropriate to define at the Enterprise level.'),
('002342','draft','2013-06-25','DISA FSO','technical','The information system implements information search and retrieval services that enforce organization-defined information sharing restrictions.','AC-21(2).2','The organization being inspected/assessed configures the information system to configure the information system to implement information search and retrieval services that enforce information sharing restrictions defined in AC-21 (2), CCI 2341. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2342.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement information search and retrieval services that enforce information sharing restrictions defined in AC-21 (2), CCI 2341. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2342.'),
('002343','draft','2013-06-25','DISA FSO','policy','The organization defines the data mining prevention techniques to be employed to adequately protect organization-defined data storage objects against data mining.','AC-23.1','The organization being inspected/assessed defines and documents the data mining prevention techniques to be employed to adequately protect organization-defined data storage objects against data mining. DoD has determined the data mining prevention techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented data mining prevention techniques to ensure the organization being inspected/assessed defines the data mining prevention techniques to be employed to adequately protect organization-defined data storage objects against data mining. DoD has determined the data mining prevention techniques are not appropriate to define at the Enterprise level.'),
('002344','draft','2013-06-25','DISA FSO','policy','The organization defines the data mining detection techniques to be employed to adequately detect data mining attempts against organization-defined data storage objects.','AC-23.2','The organization being inspected/assessed defines and documents the data mining detection techniques to be employed to adequately detect data mining attempts against organization-defined data storage objects. DoD has determined the data mining detection techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented data mining detection techniques to ensure the organization being inspected/assessed defines the data mining detection techniques to be employed to adequately detect data mining attempts against organization-defined data storage objects. DoD has determined the data mining detection techniques are not appropriate to define at the Enterprise level.'),
('002345','draft','2013-06-25','DISA FSO','policy','The organization defines the data storage objects that are to be protected against data mining attempts.','AC-23.3','The organization being inspected/assessed defines and documents the data storage objects that are to be protected against data mining attempts. DoD has determined the data storage objects are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented data storage objects to ensure the organization being inspected/assessed defines the data storage objects that are to be protected against data mining attempts. DoD has determined the data storage objects are not appropriate to define at the Enterprise level.'),
('002346','draft','2013-06-25','DISA FSO','technical','The organization employs organization-defined data mining prevention techniques for organization-defined data storage objects to adequately protect against data mining.','AC-23.4','The organization being inspected/assessed configures the information system to employ data mining prevention techniques defined in AC-23, CCI 2343 for data storage objects defined in AC-23, CCI 2345 to adequately detect data mining attempts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2346.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ data mining prevention techniques defined in AC-23, CCI 2343 for data storage objects defined in AC-23, CCI 2345 to adequately detect data mining attempts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2346.'),
('002347','draft','2013-06-25','DISA FSO','technical','The organization employs organization-defined data mining detection techniques for organization-defined data storage objects to adequately detect data mining attempts.','AC-23.5','The organization being inspected/assessed configures the information system to employ data mining detection techniques defined in AC-23, CCI 2344 for data storage objects defined in AC-23, CCI 2345 to adequately detect data mining attempts. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2347.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ data mining detection techniques defined in AC-23, CCI 2344 for data storage objects defined in AC-23, CCI 2345 to adequately detect data mining attempts. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2347.'),
('002348','draft','2013-06-25','DISA FSO','policy','The organization defines the access control decisions that are to be applied to each access request prior to access enforcement.','AC-24.1','The organization being inspected/assessed defines and documents the access control decisions that are to be applied to each access request prior to access enforcement. DoD has determined the access control decisions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented access control decisions to ensure the organization being inspected/assessed defines the access control decisions that are to be applied to each access request prior to access enforcement. DoD has determined the access control decisions are not appropriate to define at the Enterprise level.'),
('002349','draft','2013-06-25','DISA FSO','policy','The organization establishes procedures to ensure organization-defined access control decisions are applied to each access request prior to access enforcement.','AC-24.2','The organization being inspected/assessed establishes and documents procedures to ensure access control decisions defined in AC-24, CCI 2348 are applied to each access request prior to access enforcement.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed establishes procedures to ensure access control decisions defined in AC-24, CCI 2348 are applied to each access request prior to access enforcement.'),
('002350','draft','2013-06-25','DISA FSO','policy','The organization defines the access authorization information that is to be transmitted using organization-defined security safeguards to organization-defined information systems that enforce access control decisions.','AC-24(1).1','The organization being inspected/assessed defines and documents the access authorization information that is to be transmitted using organization-defined security safeguards to organization-defined information systems that enforce access control decisions. DoD has determined the access authorization information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented access authorization information to ensure the organization being inspected/assessed defines the access authorization information that is to be transmitted using organization-defined security safeguards to organization-defined information systems that enforce access control decisions. DoD has determined the access authorization information is not appropriate to define at the Enterprise level.'),
('002351','draft','2013-06-25','DISA FSO','policy','The organization defines the security safeguards to be employed when transmitting organization-defined access authorization information to organization-defined information systems that enforce access control decisions.','AC-24(1).2','The organization being inspected/assessed defines and documents the security safeguards to be employed when transmitting organization-defined access authorization information to organization-defined information systems that enforce access control decisions. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be employed when transmitting organization-defined access authorization information to organization-defined information systems that enforce access control decisions. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002352','draft','2013-06-25','DISA FSO','policy','The organization defines the information systems that are to be recipients of organization-defined access authorization information using organization-defined security safeguards.','AC-24(1).3','The organization being inspected/assessed defines and documents the information systems that are to be recipients of organization-defined access authorization information using organization-defined security safeguards. DoD has determined the information systems are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems to ensure the organization being inspected/assessed defines the information systems that are to be recipients of organization-defined access authorization information using organization-defined security safeguards. DoD has determined the information systems are not appropriate to define at the Enterprise level.'),
('002353','draft','2013-06-25','DISA FSO','technical','The information system transmits organization-defined access authorization information using organization-defined security safeguards to organization-defined information systems which enforce access control decisions.','AC-24(1).4','The organization being inspected/assessed configures the information system to transmit access authorization information defined in AC-24 (1), CCI 2350 using security safeguards defined in AC-24 (1), CCI 2351 to information systems defined in AC-24 (1), CCI 2352 which enforce access control decisions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2353.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to transmit access authorization information defined in AC-24 (1), CCI 2350 using security safeguards defined in AC-24 (1), CCI 2351 to information systems defined in AC-24 (1), CCI 2352 which enforce access control decisions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2353.'),
('002354','draft','2013-06-25','DISA FSO','policy','The organization defines the security attributes, not to include the identity of the user or process acting on behalf of the user, to be used as the basis for enforcing access control decisions.','AC-24(2).1','The organization being inspected/assessed defines and documents the security attributes, not to include the identity of the user or process acting on behalf of the user, to be used as the basis for enforcing access control decisions. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines the security attributes, not to include the identity of the user or process acting on behalf of the user, to be used as the basis for enforcing access control decisions. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002355','draft','2013-06-25','DISA FSO','technical','The information system enforces access control decisions based on organization-defined security attributes that do not include the identity of the user or process acting on behalf of the user.','AC-24(2).2','The organization being inspected/assessed configures the information system to enforce access control decisions based on security attributes defined in AC-24 (2), CCI 2354 that do not include the identity of the user or process acting on behalf of the user. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2355.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce access control decisions based on security attributes defined in AC-24 (2), CCI 2354 that do not include the identity of the user or process acting on behalf of the user. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2355.'),
('002356','draft','2013-06-25','DISA FSO','policy','The organization defines the access control policies to be implemented by the information system^s reference monitor.','AC-25.1','The organization being inspected/assessed defines and documents the access control policies to be implemented by the information system\'s reference monitor. DoD has determined the access control policies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented access control policies to ensure the organization being inspected/assessed defines the access control policies to be implemented by the information system\'s reference monitor. DoD has determined the access control policies are not appropriate to define at the Enterprise level.'),
('002357','draft','2013-06-25','DISA FSO','technical','The information system implements a reference monitor for organization-defined access control policies that is tamperproof.','AC-25.2','The organization being inspected/assessed configures the information system to implement a reference monitor for access control policies defined in AC-25, CCI 2356 that is tamperproof. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2357.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement a reference monitor for access control policies defined in AC-25, CCI 2356 that is tamperproof. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2357.'),
('002358','draft','2013-06-25','DISA FSO','technical','The information system implements a reference monitor for organization-defined access control policies that is always invoked.','AC-25.3','The organization being inspected/assessed configures the information system to implement a reference monitor for access control policies defined in AC-25, CCI 2356 that is always invoked. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2358.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement a reference monitor for access control policies defined in AC-25, CCI 2356 that is always invoked. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2358.'),
('002359','draft','2013-06-25','DISA FSO','technical','The information system implements a reference monitor for organization-defined access control policies that is small enough to be subject to analysis and testing, the completeness of which can be assured.','AC-25.4','The organization being inspected/assessed configures the information system to implement a reference monitor for access control policies defined in AC-25, CCI 2356 that is small enough to be subject to analysis and testing, the completeness of which can be assured. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2359.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement a reference monitor for access control policies defined in AC-25, CCI 2356 that is small enough to be subject to analysis and testing, the completeness of which can be assured. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2359.'),
('002360','draft','2013-06-26','DISA FSO','policy','The organization defines the conditions or trigger events requiring session disconnect to be employed by the information system when automatically terminating a user session.','AC-12.1','The organization being inspected/assessed defines and documents the conditions or trigger events requiring session disconnect to be employed by the information system when automatically terminating a user session. DoD has determined the conditions or trigger events are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions or trigger events to ensure the organization being inspected/assessed defines the conditions or trigger events requiring session disconnect to be employed by the information system when automatically terminating a user session. DoD has determined the conditions or trigger events are not appropriate to define at the Enterprise level.'),
('002361','draft','2013-06-26','DISA FSO','technical','The information system automatically terminates a user session after organization-defined conditions or trigger events requiring session disconnect.','AC-12.2','The organization being inspected/assessed configures the information system to automatically terminate a user session after conditions or trigger events requiring session disconnect, as defined in AC-12, CCI 2360. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2361.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically terminate a user session after conditions or trigger events requiring session disconnect, as defined in AC-12, CCI 2360. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2361.'),
('002362','draft','2013-06-26','DISA FSO','policy','The organization defines the resources requiring information system authentication in order to gain access.','AC-12(1).1','DoD has defined the resources as all.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the resources as all.'),
('002363','draft','2013-06-26','DISA FSO','technical','The information system provides a logout capability for user-initiated communications sessions whenever authentication is used to gain access to organization-defined information resources.','AC-12(1).2','The organization being inspected/assessed configures the information system to provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to all information resources. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2363. DoD has defined the resources as all.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to all information resources. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2363. DoD has defined the resources as all.'),
('002364','draft','2013-06-26','DISA FSO','technical','The information system displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions.','AC-12(1).3','The organization being inspected/assessed configures the information system to display an explicit logout message to users indicating the reliable termination of authenticated communications sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2364.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to display an explicit logout message to users indicating the reliable termination of authenticated communications sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2364.'),
('002365','draft','2013-06-26','DISA FSO','policy','The organization manages information system authenticators by requiring individuals to take specific security safeguards to protect authenticators.','IA-5.20','The organization being inspected/assessed documents within user agreements that individuals shall safeguard authenticators.','The organization conducting the inspection/assessment obtains and examines the user agreements of the organization being inspected/assessed to ensure that there are requirements for individuals to safeguard authenticators.'),
('002366','draft','2013-06-26','DISA FSO','policy','The organization manages information system authenticators by having devices implement specific security safeguards to protect authenticators.','IA-5.21','The organization being inspected/assessed configures the information system to manage information system authenticators by having devices implement, specific security safeguards to protect authenticators. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2366.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to manage information system authenticators by having devices implement, specific security safeguards to protect authenticators. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2366.'),
('002367','draft','2013-06-26','DISA FSO','policy','The organization ensures unencrypted static authenticators are not embedded in applications.','IA-5(7).3','The organization being inspected/assessed documents and implements requirements that static authenticators are not embedded in applications.','The organization conducting the inspection/assessment obtains and examines the requirements that static authenticators are not embedded in applications to ensure the organization being inspected/assessed ensures unencrypted static authenticators are not embedded in applications.'),
('002368','draft','2013-07-01','DISA FSO','policy','The organization defines the personnel or roles to whom the risk assessment policy is disseminated.','RA-1.1','DoD has defined the roles as at a minimum, the ISSM and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.'),
('002369','draft','2013-07-01','DISA FSO','policy','The organization defines the personnel or roles to whom the risk assessment procedures are disseminated.','RA-1.2','DoD has defined the roles as at a minimum, the ISSM and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.'),
('002370','draft','2013-07-01','DISA FSO','policy','The organization disseminates risk assessment results to organization-defined personnel or roles.','RA-3.6','The organization being inspected/assessed documents and implements a process to disseminates risk assessment results to the ISSM, ISSO, AO, and PM. DoD has defined the personnel or roles as the ISSM, ISSO, AO, and PM.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed disseminates the risk assessment results to the ISSM, ISSO, AO, and PM. DoD has defined the personnel or roles as the ISSM, ISSO, AO, and PM.'),
('002371','draft','2013-07-01','DISA FSO','policy','The organization defines the personnel or roles to whom the risk assessment results will be disseminated.','RA-3.7','DoD has defined the personnel or roles as the ISSM, ISSO, AO, and PM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSM, ISSO, AO, and PM.'),
('002372','draft','2013-07-01','DISA FSO','policy','The organization correlates the output from vulnerability scanning tools to determine the presence of multi-vulnerability/multi-hop attack vectors.','RA-5(10).1','The organization being inspected/assessed documents and implements a process to correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability/multi-hop attack vectors.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed correlates the output from vulnerability scanning tools to determine the presence of multi-vulnerability/ multi-hop attack vectors.'),
('002373','draft','2013-07-01','DISA FSO','policy','The organization employs vulnerability scanning procedures that can identify the breadth and depth of coverage (i.e., information system components scanned and vulnerabilities checked).','RA-5(3).1','The organization being inspected/assessed employs the DoD Enterprise scanning tool.','The organization conducting the inspection/assessment obtains and examines the software list or vulnerability scanning procedures to ensure the organization being inspected/assessed employs the DoD Enterprise scanning tool.'),
('002374','draft','2013-07-01','DISA FSO','policy','The organization defines the corrective actions when information about the information system is discoverable by adversaries.','RA-5(4).2','The organization being inspected/assessed defines and documents the corrective actions when information about the information system is discoverable by adversaries. DoD has determined the corrective actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented corrective actions to ensure the organization being inspected/assessed defines the corrective actions when information about the information system is discoverable by adversaries. DoD has determined the corrective actions are not appropriate to define at the Enterprise level.'),
('002375','draft','2013-07-02','DISA FSO','policy','The organization takes organization-defined corrective actions when information about the information system is discoverable by adversaries.','RA-5(4).3','The organization being inspected/assessed documents and implements a process to take the corrective actions defined in RA-5 (4), CCI 2374 when information about the information system is discoverable by adversaries. The organization must maintain a record of actions taken.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of actions taken to ensure the organization being inspected/assessed takes the corrective actions defined in RA-5 (4), CCI 2374 when information about the information system is discoverable by adversaries.'),
('002376','draft','2013-07-02','DISA FSO','policy','The organization defines the personnel or roles with whom the information obtained from the vulnerability scanning process and security control assessments will be shared.','RA-5.11','DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002377','draft','2013-07-02','DISA FSO','policy','The organization documents the system and communications protection policy.',NULL,NULL,NULL),
('002378','draft','2013-07-02','DISA FSO','policy','The organization defines the personnel or roles to be recipients of the system and communications protection policy.','SC-1.1','The organization being inspected/assessed defines and documents personnel or roles to be recipients of the system and communications protection policy. The personnel or roles must include at a minimum, the ISSM/ISSO. DoD has defined the personnel or roles as at a minimum, the ISSO/ISSM.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to be recipients of the system and communications protection policy. The personnel or roles must include at a minimum, the ISSM/ISSO. DoD has defined the personnel or roles as at a minimum, the ISSO/ISSM.'),
('002379','draft','2013-07-02','DISA FSO','policy','The organization documents procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.',NULL,NULL,NULL),
('002380','draft','2013-07-02','DISA FSO','policy','The organization defines the personnel or roles to be recipients of the procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','SC-1.2','The organization being inspected/assessed defines and documents personnel or roles to be recipients of the procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls. The personnel or roles must include at a minimum, the ISSM/ISSO. DoD has defined the personnel or roles as at a minimum, the ISSO/ISSM.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to be recipients of the procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls. The personnel or roles must include at a minimum, the ISSM/ISSO. DoD has defined the personnel or roles as at a minimum, the ISSO/ISSM.'),
('002381','draft','2013-07-02','DISA FSO','technical','The organization minimizes the number of nonsecurity functions included within the isolation boundary containing security functions.','SC-3(3).1','The organization being inspected/assessed configures the information system to minimize the number of nonsecurity functions included within the isolation boundary containing security functions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2381.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to minimize the number of nonsecurity functions included within the isolation boundary containing security functions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2381.'),
('002382','draft','2013-07-02','DISA FSO','technical','The organization implements security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.','SC-3(4).1','The organization being inspected/assessed configures the information system to implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2382.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2382.'),
('002383','draft','2013-07-02','DISA FSO','policy','The organization defines the procedures to be employed to prevent unauthorized information transfer via shared resources when system processing explicitly switches between different information classification levels or security categories.','SC-4(2).1','The organization being inspected/assessed defines and documents the procedures to be employed to prevent the unauthorized information transfer via shared resources when system processing explicitly switches between different information classification levels or security categories. DoD has determined the procedures are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed defines the procedures to be employed to prevent the unauthorized information transfer via shared resources when system processing explicitly switches between different information classification levels or security categories. DoD has determined the procedures are not appropriate to define at the Enterprise level.'),
('002384','draft','2013-07-02','DISA FSO','technical','The information system prevents unauthorized information transfer via shared resources in accordance with organization-defined procedures when system processing explicitly switches between different information classification levels or security categories.','SC-4(2).2','The organization being inspected/assessed configures the information system to prevent unauthorized information transfer via shared resources in accordance with procedures defined in SC-4 (2), CCI 2383 when system processing explicitly switches between different information classification levels or security categories. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2384.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent unauthorized information transfer via shared resources in accordance with procedures defined in SC-4 (2), CCI 2383 when system processing explicitly switches between different information classification levels or security categories. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2384.'),
('002385','draft','2013-07-02','DISA FSO','technical','The information system protects against or limits the effects of organization-defined types of denial of service attacks by employing organization-defined security safeguards.','SC-5.2','The organization being inspected/assessed configures the information system to protect against or limits the effects of types of denial of service attacks defined in SC-5, CCI 1093 by employing security safeguards defined in SC-5, CCI 2386. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2385.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect against or limits the effects of types of denial of service attacks defined in SC-5, CCI 1093 by employing security safeguards defined in SC-5, CCI 2386. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2385.'),
('002386','draft','2013-07-02','DISA FSO','policy','The organization defines the security safeguards to be employed to protect the information system against, or limit the effects of, denial of service attacks.','SC-5.3','The organization being inspected/assessed defines and documents the security safeguards to be employed to protect the information system against, or limit the effects of, denial of service attacks. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be employed to protect the information system against, or limit the effects of, denial of service attacks. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002387','draft','2013-07-02','DISA FSO','policy','The organization defines the denial of service attacks against other information systems that the information system is to restrict the ability of individuals to launch.','SC-5(1).2','The organization being inspected/assessed defines and documents the denial of service attacks against other information systems the information system is to restrict the ability of individuals to launch. DoD has determined the denial of service attacks as not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented denial of service attacks to ensure the organization being inspected/assessed defines the denial of service attacks against other information systems the information system is to restrict the ability of individuals to launch. DoD has determined the denial of service attacks as not appropriate to define at the Enterprise level.'),
('002388','draft','2013-07-02','DISA FSO','policy','The organization defines a list of monitoring tools to be employed to detect indicators of denial of service attacks against the information system.','SC-5(3).1','The organization being inspected/assessed defines and documents a list of monitoring tools to be employed to detect indicators of denial of service attacks against the information system. DoD has determined the monitoring tools are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented monitoring tools to ensure the organization being inspected/assessed defines a list of monitoring tools to be employed to detect indicators of denial of service attacks against the information system. DoD has determined the monitoring tools are not appropriate to define at the Enterprise level.'),
('002389','draft','2013-07-02','DISA FSO','policy','The organization employs an organization-defined list of monitoring tools to detect indicators of denial of service attacks against the information system.','SC-5(3).2','The organization being inspected/assessed implements the monitoring tools defined in SC-5 (3), CCI 2388 to detect indicators of denial of service attacks against the information system.','The organization conducting the inspection/assessment obtains and examines the list of monitoring tools as defined in SC-5 (3), CCI 2388 and a sampling of monitoring results to ensure the organization being inspected/assessed employs organization-defined list of monitoring tools to detect indicators of denial of service attacks against the information system.'),
('002390','draft','2013-07-02','DISA FSO','policy','The organization defines the information system resources to be monitored to determine if sufficient resources exist to prevent effective denial of service attacks.','SC-5(3).3','The organization being inspected/assessed defines and documents the information system resources to be monitored to determine if sufficient resources exist to prevent effective denial of service attacks. DoD has determined the information system resources are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system resources to ensure the organization being inspected/assessed defines the information system resources to be monitored to determine if sufficient resources exist to prevent effective denial of service attacks. DoD has determined the information system resources are not appropriate to define at the Enterprise level.'),
('002391','draft','2013-07-02','DISA FSO','policy','The organization monitors organization-defined information system resources to determine if sufficient resources exist to prevent effective denial of service attacks.','SC-5(3).4','The organization being inspected/assessed monitors information system resources defined in SC-5 (3), CCI 2390 to determine if sufficient resources exist to prevent effective denial of service attacks.','The organization conducting the inspection/assessment obtains and examines the documented monitoring procedures and any available artifacts from the monitoring process to ensure the organization being inspected/assessed monitors information system resources defined in SC-5 (3), CCI 2390 to determine if sufficient resources exist to prevent effective denial of service attacks.'),
('002392','draft','2013-07-02','DISA FSO','policy','The organization defines the resources to be allocated to protect the availability of information system resources.','SC-6.1','The organization being inspected/assessed defines and documents the resources to be allocated to protect the availability of information system resources. DoD has determined the resources are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented resources to ensure the organization being inspected/assessed defines the resources to be allocated to protect the availability of information system resources. DoD has determined the resources are not appropriate to define at the Enterprise level.'),
('002393','draft','2013-07-02','DISA FSO','policy','The organization defines the security safeguards to be employed to protect the availability of information system resources.','SC-6.2','The organization being inspected/assessed defines and documents security safeguards to be employed to protect the availability of information system resources. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be employed to protect the availability of information system resources. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002394','draft','2013-07-02','DISA FSO','technical','The information system protects the availability of resources by allocating organization-defined resources based on priority, quota, and/or organization-defined security safeguards.','SC-6.3','The organization being inspected/assessed configures the information system to protect the availability of resources by allocating resources defined in SC-6, CCI 2392 based on priority, quota, and/or security safeguards defined in SC-6, CCI 2393. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2394.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect the availability of resources by allocating resources defined in SC-6, CCI 2392 based on priority, quota, and/or security safeguards defined in SC-6, CCI 2393. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2394.'),
('002395','draft','2013-07-02','DISA FSO','policy','The information system implements subnetworks for publicly accessible system components that are physically and/or logically separated from internal organizational networks.','SC-7.2','The organization being inspected/assessed designs the information system to leverage subnetworks so that publicly accessible system components are physically and/or logically separated from internal organizational networks.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying component partitioning to ensure the organization being inspected/assessed implements subnetworks for publicly accessible system components that are physically and/or logically separated from internal organizational networks.'),
('002396','draft','2013-07-02','DISA FSO','policy','The organization protects the confidentiality and integrity of the information being transmitted across each interface for each external telecommunication service.','SC-7(4).3','The organization being inspected/assessed documents and implements mechanisms to protect the confidentiality and integrity of the information being transmitted across each interface for each external telecommunication service.','The organization conducting the inspection/assessment obtains and examines the documented mechanisms to ensure the organization being inspected/assessed protects the confidentiality and integrity of the information being transmitted across each interface for each external telecommunication service.'),
('002397','draft','2013-07-02','DISA FSO','technical','The information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks.','SC-7(7).1','The organization being inspected/assessed configures the information system to prevent the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2397.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prevent the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2397.'),
('002398','draft','2013-07-02','DISA FSO','policy','The information system detects outgoing communications traffic posing a threat to external information systems.','SC-7(9).1','The organization being inspected/assessed configures the information system to detect outgoing communications traffic posing a threat to external information systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2398.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to detect outgoing communications traffic posing a threat to external information systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2398.'),
('002399','draft','2013-07-02','DISA FSO','policy','The information system denies outgoing communications traffic posing a threat to external information systems.','SC-7(9).2','The organization being inspected/assessed configures the information system to deny outgoing communications traffic posing a threat to external information systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2399.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to deny outgoing communications traffic posing a threat to external information systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2399.'),
('002400','draft','2013-07-02','DISA FSO','technical','The information system audits the identity of internal users associated with denied outgoing communications traffic posing a threat to external information systems.','SC-7(9).3','The organization being inspected/assessed configures the information system to audit the identity of internal users associated with denied outgoing communications traffic posing a threat to external information systems. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2400.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to audit the identity of internal users associated with denied outgoing communications traffic posing a threat to external information systems. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2400.'),
('002401','draft','2013-07-02','DISA FSO','policy','The organization defines the authorized sources from which the information system will allow incoming communications.','SC-7(11).1','The organization being inspected/assessed defines and documents the authorized sources from which the information system will allow incoming communications. DoD has determined the authorized sources are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented authorized sources to ensure the organization being inspected/assessed defines the authorized sources from which the information system will allow incoming communications. DoD has determined the authorized sources are not appropriate to define at the Enterprise level.'),
('002402','draft','2013-07-02','DISA FSO','policy','The organization defines the authorized destinations for routing inbound communications.','SC-7(11).2','The organization being inspected/assessed defines and documents the authorized destinations for routing inbound communications. DoD has determined the authorized destinations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented authorized destinations to ensure the organization being inspected/assessed defines the authorized destinations for routing inbound communications. DoD has determined the authorized destinations are not appropriate to define at the Enterprise level.'),
('002403','draft','2013-07-02','DISA FSO','technical','The information system only allows incoming communications from organization-defined authorized sources routed to organization-defined authorized destinations.','SC-7(11).3','The organization being inspected/assessed configures the information system to allow incoming communications from authorized sources defined in SC-7 (11), CCI 2401 routed to authorized destinations defined in SC-7 (11), CCI 2402. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2403.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to allow incoming communications from authorized sources defined in SC-7 (11), CCI 2401 routed to authorized destinations defined in SC-7 (11), CCI 2402. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2403.'),
('002404','draft','2013-07-02','DISA FSO','policy','The organization defines the host-based boundary protection mechanisms that are to be implemented at organization-defined information system components.','SC-7(12).1','DoD has defined the information system components as McAfee Host Intrusion Prevention (HIPS).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as McAfee Host Intrusion Prevention (HIPS).'),
('002405','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components at which organization-defined host-based boundary protection mechanisms will be implemented.','SC-7(12).2','DoD has defined the information system components as all information system components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as all information system components.'),
('002406','draft','2013-07-02','DISA FSO','policy','The organization implements organization-defined host-based boundary protection mechanisms at organization-defined information system components.','SC-7(12).3','The organization being inspected/assessed implements McAfee Host Intrusion Prevention (HIPS) on all information system components. DoD has defined the host-based boundary protection mechanisms as McAfee Host Intrusion Prevention (HIPS). DoD has defined the information system components as all information system components.','The organization conducting the inspection/assessment examines a sampling of information system components to ensure the organization being inspected/assessed implements McAfee Host Intrusion Prevention (HIPS) on all information system components. DoD has defined the host-based boundary protection mechanisms as McAfee Host Intrusion Prevention (HIPS). DoD has defined the information system components as all information system components.'),
('002407','draft','2013-07-02','DISA FSO','policy','The organization defines the managed interfaces at which the organization protects against unauthorized physical connections.','SC-7(14).3','DoD has defined the managed interfaces as internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the managed interfaces as internet access points, enclave LAN to WAN, cross domain solutions, and any DoD Approved Alternate Gateways.'),
('002408','draft','2013-07-02','DISA FSO','policy','The organization defines the independently configured communication clients, which are configured by end users and external service providers, between which the information system will block both inbound and outbound communications traffic.','SC-7(19).1','The organization being inspected/assessed defines and documents the independently configured communication clients, which are configured by end users and external service providers, between which the information system will block both inbound and outbound communications traffic. DoD has determined the communication clients are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented communication clients to ensure the organization being inspected/assessed defines the independently configured communication clients, which are configured by end users and external service providers, between which the information system will block both inbound and outbound communications traffic. DoD has determined the communication clients are not appropriate to define at the Enterprise level.'),
('002409','draft','2013-07-02','DISA FSO','technical','The information system blocks both inbound and outbound communications traffic between organization-defined communication clients that are independently configured by end users and external service providers.','SC-7(19).2','The organization being inspected/assessed configures the information system to block both inbound and outbound communications traffic between communication clients defined in SC-7 (19), CCI 2408 that are independently configured by end users and external service providers. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2409.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to block both inbound and outbound communications traffic between communication clients defined in SC-7 (19), CCI 2408 that are independently configured by end users and external service providers. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2409.'),
('002410','draft','2013-07-02','DISA FSO','policy','The organization defines information system components that are to be dynamically isolated/segregated from other components of the information system.','SC-7(20).1','The organization being inspected/assessed defines and documents information system components that are to be dynamically isolated/segregated from other components of the information system. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines information system components that are to be dynamically isolated/segregated from other components of the information system. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002411','draft','2013-07-02','DISA FSO','technical','The information system provides the capability to dynamically isolate/segregate organization-defined information system components from other components of the system.','SC-7(20).2','The organization being inspected/assessed configures the information system to provide the capability to dynamically isolate/segregate information system components defined in SC-7 (20), CCI 2410 from other components of the system. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2411.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability to dynamically isolate/segregate information system components defined in SC-7 (20), CCI 2410 from other components of the system. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2411.'),
('002412','deprecated','2013-07-02','DISA FSO','policy','The organization defines the information system components supporting organization-defined missions and/or business functions that are to be separated using boundary protection mechanisms.',NULL,NULL,NULL),
('002413','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components supporting organization-defined missions and/or business functions that are to be separated using boundary protection mechanisms.','SC-7(21).1','The organization being inspected/assessed defines and documents the information system components supporting organization-defined missions and/or business functions that are to be separated using boundary protection mechanisms. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components supporting organization-defined missions and/or business functions that are to be separated using boundary protection mechanisms. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002414','draft','2013-07-02','DISA FSO','policy','The organization defines the missions and/or business functions for which boundary protection mechanisms will be employed to separate the supporting organization-defined information system components.','SC-7(21).2','The organization being inspected/assessed defines and documents the missions and/or business functions for which boundary protection mechanisms will be employed to separate the supporting organization-defined information system components. DoD has determined the missions and/or business functions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented missions and/or business functions to ensure the organization being inspected/assessed defines the missions and/or business functions for which boundary protection mechanisms will be employed to separate the supporting organization-defined information system components. DoD has determined the missions and/or business functions are not appropriate to define at the Enterprise level.'),
('002415','draft','2013-07-02','DISA FSO','policy','The organization employs boundary protection mechanisms to separate organization-defined information system components supporting organization-defined missions and/or business functions.','SC-7(21).3','The organization being inspected/assessed designs the information system to employ boundary protection mechanisms to separate information system components defined in SC-7 (21), CCI 2413 supporting missions and/or business functions defined in SC-7 (21), CCI 2414.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying component partitioning to ensure the organization being inspected/assessed employs boundary protection mechanisms to separate information system components defined in SC-7 (21), CCI 2413 supporting missions and/or business functions defined in SC-7 (21), CCI 2414.'),
('002416','draft','2013-07-02','DISA FSO','policy','The information system implements separate network addresses (i.e., different subnets) to connect to systems in different security domains.','SC-7(22).1','The organization being inspected/assessed designs the information system to implement separate network addresses (i.e., different subnets) to connect to systems in different security domains.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying component partitioning to ensure the organization being inspected/assessed implements separate network addresses (i.e., different subnets) to connect to systems in different security domains.'),
('002417','draft','2013-07-02','DISA FSO','technical','The information system disables feedback to senders on protocol format validation failure.','SC-7(23).1','The organization being inspected/assessed configures the information system to disable feedback to senders on protocol format validation failure For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2417.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to disable feedback to senders on protocol format validation failure For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2417.'),
('002418','draft','2013-07-02','DISA FSO','policy','The information system protects the confidentiality and/or integrity of transmitted information.','SC-8.1','The organization being inspected/assessed configures the information system to protect the confidentiality and/or integrity of transmitted information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2418.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to protect the confidentiality and/or integrity of transmitted information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2418.'),
('002419','draft','2013-07-02','DISA FSO','policy','The organization defines the alternative physical safeguards to be employed when cryptographic mechanisms are not implemented to protect information during transmission.','SC-8(1).1','DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).'),
('002420','draft','2013-07-02','DISA FSO','technical','The information system maintains the confidentiality and/or integrity of information during preparation for transmission.','SC-8(2).1','The organization being inspected/assessed configures the information system to maintain the confidentiality and integrity of information during preparation for transmission. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2420. DoD has defined the selection as both confidentiality and integrity.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain the confidentiality and integrity of information during preparation for transmission. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2420.'),
('002421','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission unless otherwise protected by organization-defined alternative physical safeguards.','SC-8(1).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent unauthorized disclosure of information and detect changes to information during transmission unless otherwise protected by Protected Distribution System (PDS). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2421. DoD has defined the selection as both prevention of unauthorized disclosure and detection of changes to information. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent unauthorized disclosure of information and detect changes to information during transmission unless otherwise protected by Protected Distribution System (PDS). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2421. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).'),
('002422','draft','2013-07-02','DISA FSO','technical','The information system maintains the confidentiality and/or integrity of information during reception.','SC-8(2).2','The organization being inspected/assessed configures the information system to maintain the confidentiality and integrity of information during reception. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2422. DoD has defined the selection as both confidentiality and integrity.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain the confidentiality and integrity of information during reception. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2422.'),
('002423','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to protect message externals (e.g., message headers and routing information) unless otherwise protected by organization-defined alternative physical safeguards.','SC-8(3).1','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect message externals (e.g., message headers and routing information) unless otherwise protected by Protected Distribution System (PDS). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2423. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect message externals (e.g., message headers and routing information) unless otherwise protected by Protected Distribution System (PDS). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2423. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).'),
('002424','draft','2013-07-02','DISA FSO','policy','The organization defines the alternative physical safeguards to be employed when cryptographic mechanisms are not implemented by the information system.','SC-8(4).1','DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).'),
('002425','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by organization-defined alternative physical safeguards.','SC-8(4).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by Protected Distribution System (PDS). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2426. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by Protected Distribution System (PDS). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2426. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).'),
('002426','draft','2013-07-02','DISA FSO','technical','The information system provides a trusted communications path that is logically isolated and distinguishable from other paths.','SC-11(1).1','The organization being inspected/assessed configures the information system to provide a trusted communications path that is logically isolated and distinguishable from other paths. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2426.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide a trusted communications path that is logically isolated and distinguishable from other paths. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2426.'),
('002427','draft','2013-07-02','DISA FSO','policy','The organization defines the alternative physical safeguards to be employed to protect message externals (e.g., message headers and routing information) when cryptographic mechanisms are not implemented.','SC-8(3).2','DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the alternative physical safeguards as Protected Distribution System (PDS).'),
('002428','draft','2013-07-02','DISA FSO','policy','The organization defines the requirements for cryptographic key generation to be employed within the information system.','SC-12.1','DoD has defined the requirements for key generation as requirements for key generation defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the requirements for key generation as requirements for key generation defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002429','draft','2013-07-02','DISA FSO','policy','The organization defines the requirements for cryptographic key distribution to be employed within the information system.','SC-12.2','DoD has defined the requirements for key distribution as requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the requirements for key distribution as requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002430','draft','2013-07-02','DISA FSO','policy','The organization defines the requirements for cryptographic key storage to be employed within the information system.','SC-12.3','DoD has defined the requirements for key storage as requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the requirements for key storage as requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002431','draft','2013-07-02','DISA FSO','policy','The organization defines the requirements for cryptographic key access to be employed within the information system.','SC-12.4','DoD has defined the requirements for key access as requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the requirements for key access as requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002432','draft','2013-07-02','DISA FSO','policy','The organization defines the requirements for cryptographic key destruction to be employed within the information system.','SC-12.5','DoD has defined the requirements for key destruction as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the requirements for key destruction as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002433','draft','2013-07-02','DISA FSO','policy','The organization establishes cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key generation.','SC-12.6','The organization being inspected/assessed documents and implements a process to establish cryptographic keys for required cryptography employed within the information system in accordance with requirements for key generation defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key generation as requirements for key generation defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes cryptographic keys for required cryptography employed within the information system in accordance with requirements for key generation defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key generation as requirements for key generation defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002434','draft','2013-07-02','DISA FSO','policy','The organization establishes cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key distribution.','SC-12.7','The organization being inspected/assessed documents and implements a process to establish cryptographic keys for required cryptography employed within the information system in accordance with requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key distribution as requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes cryptographic keys for required cryptography employed within the information system in accordance with requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key distribution as requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002435','draft','2013-07-02','DISA FSO','policy','The organization establishes cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key storage.','SC-12.8','The organization being inspected/assessed documents and implements a process to establish cryptographic keys for required cryptography employed within the information system in accordance with requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key storage as requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes cryptographic keys for required cryptography employed within the information system in accordance with requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key storage as requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002436','draft','2013-07-02','DISA FSO','policy','The organization establishes cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key access.','SC-12.9','The organization being inspected/assessed documents and implements a process to establish cryptographic keys for required cryptography employed within the information system in accordance with requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key access as requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes cryptographic keys for required cryptography employed within the information system in accordance with requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key access as requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002437','draft','2013-07-02','DISA FSO','policy','The organization establishes cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key destruction.','SC-12.10','The organization being inspected/assessed documents and implements a process to establish cryptographic keys for required cryptography employed within the information system in accordance with requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key destruction as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes cryptographic keys for required cryptography employed within the information system in accordance with requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key destruction as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002438','draft','2013-07-02','DISA FSO','policy','The organization manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key generation.','SC-12.11','The organization being inspected/assessed documents and implements a process to manage cryptographic keys for required cryptography employed within the information system in accordance with requirements for key destruction defined DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key generation as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed manages cryptographic keys for required cryptography employed within the information system in accordance with requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key generation as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002439','draft','2013-07-02','DISA FSO','policy','The organization manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key distribution.','SC-12.12','The organization being inspected/assessed documents and implements a process to manage cryptographic keys for required cryptography employed within the information system in accordance with requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key distribution as requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed manages cryptographic keys for required cryptography employed within the information system in accordance with requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key distribution as requirements for key distribution defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002440','draft','2013-07-02','DISA FSO','policy','The organization manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key storage.','SC-12.13','The organization being inspected/assessed documents and implements a process to manage cryptographic keys for required cryptography employed within the information system in accordance with requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key storage as requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed manages cryptographic keys for required cryptography employed within the information system in accordance with requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key storage as requirements for key storage defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002441','draft','2013-07-02','DISA FSO','policy','The organization manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key access.','SC-12.14','The organization being inspected/assessed documents and implements a process to manage cryptographic keys for required cryptography employed within the information system in accordance with requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key access as requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed manages cryptographic keys for required cryptography employed within the information system in accordance with requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key access as requirements for key access defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002442','draft','2013-07-02','DISA FSO','policy','The organization manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key destruction.','SC-12.15','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed manages cryptographic keys for required cryptography employed within the information system in accordance with requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key destruction as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"','The organization being inspected/assessed documents and implements a process to manage cryptographic keys for required cryptography employed within the information system in accordance with requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\" DoD has defined the requirements for key destruction as requirements for key destruction defined in DoDI 8520.02 \"Public Key Infrastructure and Public Key Enabling\" and DoDI 8520.03 \"Identity Authentication for Information Systems.\"'),
('002443','draft','2013-07-02','DISA FSO','policy','The organization produces symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes.','SC-12(2).1','The organization being inspected/assessed documents and implements a process to produce symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes. An example process would be implementation of Key Management Infrastructure (KMI). DoD requires a minimum of NIST approved cryptography for unclassified systems. Classified systems require NSA approved cryptography.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed produces appropriate symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes.'),
('002444','draft','2013-07-02','DISA FSO','policy','The organization controls symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes.','SC-12(2).2','The organization being inspected/assessed documents and implements a process to control symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes. An example process would be implementation of Key Management Infrastructure (KMI). DoD requires a minimum of NIST approved cryptography for unclassified systems. Classified systems require NSA approved cryptography.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed controls appropriate symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes.'),
('002445','draft','2013-07-02','DISA FSO','policy','The organization distributes symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes.','SC-12(2).3','The organization being inspected/assessed documents and implements a process to distribute symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes. DoD requires a minimum of NIST approved cryptography for unclassified systems. Classified systems require NSA approved cryptography.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed distributes appropriate symmetric cryptographic keys using NIST FIPS-compliant or NSA-approved key management technology and processes.'),
('002446','draft','2013-07-02','DISA FSO','policy','The organization produces asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; or approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user^s private key.','SC-12(3).1','The organization being inspected/assessed implements a process to produce asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI medium certificates or prepositioned keying material; or, approved PKI medium or FORTEZZA certificates and hardware security tokens that protect the user\'s private key.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of asymmetric cryptographic key production to ensure the organization being inspected/assessed produces asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI medium certificates or prepositioned keying material; or, approved PKI medium or FORTEZZA certificates and hardware security tokens that protect the user\'s private key.'),
('002447','draft','2013-07-02','DISA FSO','policy','The organization controls asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; or approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user^s private key.','SC-12(3).2','The organization being inspected/assessed implements a process to control asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI medium certificates or prepositioned keying material; or, approved PKI medium or FORTEZZA certificates and hardware security tokens that protect the user\'s private key.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of asymmetric cryptographic key control to ensure the organization being inspected/assessed controls asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI medium certificates or prepositioned keying material; or, approved PKI medium or FORTEZZA certificates and hardware security tokens that protect the user\'s private key.'),
('002448','draft','2013-07-02','DISA FSO','policy','The organization distributes asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; or approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user^s private key.','SC-12(3).3','The organization being inspected/assessed implements a process to distribute asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI medium certificates or prepositioned keying material; or, approved PKI medium or FORTEZZA certificates and hardware security tokens that protect the user\'s private key.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of asymmetric cryptographic key distribution to ensure the organization being inspected/assessed distributes asymmetric cryptographic keys using: NSA-approved key management technology and processes; approved PKI medium certificates or prepositioned keying material; or, approved PKI medium or FORTEZZA certificates and hardware security tokens that protect the user\'s private key.'),
('002449','draft','2013-07-02','DISA FSO','policy','The organization defines the cryptographic uses, and type of cryptography required for each use, to be implemented by the information system.','SC-13.1','DoD has defined the cryptographic uses and type of cryptography required for each use as protection of classified information: NSA-approved cryptography; provision of digital signatures and hashing: FIPS-validated cryptography.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the cryptographic uses and type of cryptography required for each use as protection of classified information: NSA-approved cryptography; provision of digital signatures and hashing: FIPS-validated cryptography.'),
('002450','draft','2013-07-02','DISA FSO','technical','The information system implements organization-defined cryptographic uses and type of cryptography required for each use in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.','SC-13.2','The organization being inspected/assessed configures the information system to implement, for, protection of classified information: NSA-approved cryptography; for provision of digital signatures and hashing: FIPS-validated cryptography in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2450. DoD has defined the cryptographic uses and type of cryptography required for each use as protection of classified information: NSA-approved cryptography; provision of digital signatures and hashing: FIPS-validated cryptography.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement, for, protection of classified information: NSA-approved cryptography; for provision of digital signatures and hashing: FIPS-validated cryptography in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2450. DoD has defined the cryptographic uses and type of cryptography required for each use as protection of classified information: NSA-approved cryptography; provision of digital signatures and hashing: FIPS-validated cryptography.'),
('002451','draft','2013-07-02','DISA FSO','policy','The organization defines the information systems or information system components from which collaborative computing devices in organization-defined secure work areas are to be disabled or removed.','SC-15(3).3','DoD has defined information systems or information system components as any device used that may incorporate camera, microphone, or smart board capability.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined information systems or information system components as any device used that may incorporate camera, microphone, or smart board capability.'),
('002452','draft','2013-07-02','DISA FSO','policy','The organization defines the online meetings and teleconferences for which the information system provides an explicit indication of current participants.','SC-15(4).1','DoD has defined the online meetings and teleconferences as all VTC and all IP based online meetings and conferences (excludes audio only teleconferences using traditional telephony).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the online meetings and teleconferences as all VTC and all IP based online meetings and conferences (excludes audio only teleconferences using traditional telephony).'),
('002453','draft','2013-07-02','DISA FSO','technical','The information system provides an explicit indication of current participants in organization-defined online meetings and teleconferences.','SC-15(4).2','The organization being inspected/assessed configures the information system to provide an explicit indication of current participants in all VTC and all IP based online meetings and conferences (excludes audio only teleconferences using traditional telephony). For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2453. DoD has defined the online meetings and teleconferences as all VTC and all IP based online meetings and conferences (excludes audio only teleconferences using traditional telephony).','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide an explicit indication of current participants in all VTC and all IP based online meetings and conferences (excludes audio only teleconferences using traditional telephony). For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2453. DoD has defined the online meetings and teleconferences as all VTC and all IP based online meetings and conferences (excludes audio only teleconferences using traditional telephony).'),
('002454','draft','2013-07-02','DISA FSO','policy','The organization defines the security attributes the information system is to associate with the information being exchanged between information systems and between information system components.','SC-16.2','The organization being inspected/assessed defines and documents the security attributes the information system is to associate with the information being exchanged between information systems and between information system components. DoD has determined the security attributes are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security attributes to ensure the organization being inspected/assessed defines the security attributes the information system is to associate with the information being exchanged between information systems and between information system components. DoD has determined the security attributes are not appropriate to define at the Enterprise level.'),
('002455','draft','2013-07-02','DISA FSO','technical','The information system associates organization-defined security attributes with information exchanged between information system components.','SC-16.3','The organization being inspected/assessed configures the information system to associate the security attributes defined in SC-16, CCI 2454 with information exchanged between information system components. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2455.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to associate the security attributes defined in SC-16, CCI 2454 with information exchanged between information system components. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2455.'),
('002456','draft','2013-07-02','DISA FSO','policy','The organization defines the certificate policy employed to issue public key certificates.','SC-17.2','DoD has defined the certificate policy as DoDI 8520.02, \"Public Key Infrastructure (PKI) and Public Key (PK) Enabling.\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the certificate policy as DoDI 8520.02, \"Public Key Infrastructure (PKI) and Public Key (PK) Enabling.'),
('002457','draft','2013-07-02','DISA FSO','policy','The organization defines the corrective actions to be taken when organization-defined unacceptable mobile code is identified.','SC-18(1).3','DoD has defined the corrective actions to be taken when organization-defined unacceptable mobile code is identified as the corrective actions defined in the Protection Profile for Web Browsers and Application SRG.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\nDoD has defined the corrective actions to be taken when organization-defined unacceptable mobile code is identified as the corrective actions defined in the Protection Profile for Web Browsers and Application SRG.'),
('002458','draft','2013-07-02','DISA FSO','policy','The organization defines what constitutes unacceptable mobile code for its information systems.','SC-18(1).4','The organization being inspected/assessed defines and documents unacceptable mobile code IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must define IAW the STIG/SRG guidance that pertains to CCI 2458.\nDoD has determined the unacceptable mobile code is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented acceptable and unacceptable mobile code and mobile code technologies to ensure the organization being inspected/assessed defines unacceptable mobile code IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has defined unacceptable mobile code IAW the applicable STIGs and SRGs pertaining to CCI 2458.\nDoD has determined the unacceptable mobile code is not appropriate to define at the Enterprise level.'),
('002459','draft','2013-07-02','DISA FSO','policy','The organization defines the unacceptable mobile code of which the information system is to prevent download and execution.','SC-18(3).3','The organization being inspected/assessed defines and documents unacceptable mobile code of which the information system is to prevent download and execution IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must define IAW the STIG/SRG guidance that pertains to CCI 2459.\nDoD has determined the unacceptable mobile code is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented unacceptable mobile code to ensure the organization being inspected/assessed defines unacceptable mobile code of which the information system is to prevent download and execution IAW the Protection Profile for Web Browsers and Application SRG.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has defined unacceptable mobile code IAW the applicable STIGs and SRGs pertaining to CCI 2459.\nDoD has determined the unacceptable mobile code is not appropriate to define at the Enterprise level.'),
('002460','draft','2013-07-02','DISA FSO','technical','The information system enforces organization-defined actions prior to executing mobile code.','SC-18(4).4','The organization being inspected/assessed configures the information system to prompt the user prior to executing the code.\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2460.\nDoD has defined the actions as the user be prompted.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prompt the user prior to executing the code.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2460.\nDoD has defined the actions as the user be prompted.'),
('002461','draft','2013-07-02','DISA FSO','policy','The organization allows execution of permitted mobile code only in confined virtual machine environments.','SC-18(5).1','The organization being inspected/assessed documents within the system and communications protection policy and implements mechanisms to allow the execution of permitted mobile code only in confined virtual machine environments.\n\nUnacceptable mobile code is defined in SC-18 (3).','The organization conducting the inspection/assessment obtains and examines the system and communications protection policy and inspects the information systems to ensure the organization being inspected/assessed implements mechanisms to allow the execution of permitted mobile code only in confined virtual machine environments.'),
('002462','draft','2013-07-02','DISA FSO','technical','The information system provides additional data integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries.','SC-20.2','The organization being inspected/assessed configures the authoritative name server software for external queries to enable DNSSEC and creates resource records with digital signatures (RRSig) for each A record. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2462.','The organization conducting the inspection/assessment:\n1. inspects the configuration files for the presence of DNSSEC records for each A record hosted in a zone;\n2. utilizes DNSSEC diagnostic tools, such as dig; and\n3. performs queries which will exercise the data flow path for authoritative name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2462.'),
('002463','draft','2013-07-02','DISA FSO','technical','The information system provides data origin artifacts for internal name/address resolution queries.','SC-20(2).1','The organization being inspected/assessed configures the authoritative name server software for internal queries to enable DNSSEC and creates resource records with digital signatures (RRSig) for each A record. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2463.','The organization conducting the inspection/assessment:\n1. inspects the configuration files for the presence of DNSSEC records for each A record hosted in a zone;\n2. utilizes DNSSEC diagnostic tools, such as dig; and\n3. performs queries which will exercise the data flow path for authoritative name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2463.'),
('002464','draft','2013-07-02','DISA FSO','technical','The information system provides data integrity protection artifacts for internal name/address resolution queries.','SC-20(2).2','The organization being inspected/assessed configures the authoritative name server software for internal software to enable DNSSEC and creates resource records with digital signatures(RRSig) for each A record. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2464.','The organization conducting the inspection/assessment:\n1. inspects the configuration files for the presence of DNSSEC records for each A record hosted in a zone;\n2. utilizes DNSSEC diagnostic tools, such as dig; and\n3. performs queries which will exercise the data flow path for authoritative name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2464.'),
('002465','draft','2013-07-02','DISA FSO','technical','The information system requests data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.','SC-21.1','The organization being inspected/assessed configures the:\n1. recursive/caching name server software to enable DNSSEC;\n2. software to enable DNSSEC validation; and\n3. software to establish a secure entry point trust anchor by installing key signing keys in the software configuration of trusted keys. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2465.','The organization conducting the inspection/assessment utilizes DNSSEC diagnostic tools, such as dig, and performs queries which will exercise the data flow path for recursive name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2465.'),
('002466','draft','2013-07-02','DISA FSO','technical','The information system requests data integrity verification on the name/address resolution responses the system receives from authoritative sources.','SC-21.2','The organization being inspected/assessed configures the:\n1. recursive/caching name server software to enable DNSSEC;\n2. software to enable DNSSEC validation; and\n3. software to establish a secure entry point trust anchor by installing key signing keys in the software configuration of trusted keys. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2466.','The organization conducting the inspection/assessment utilizes DNSSEC diagnostic tools, such as dig, and performs queries which will exercise the data flow path for recursive name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2466.'),
('002467','draft','2013-07-02','DISA FSO','technical','The information system performs data integrity verification on the name/address resolution responses the system receives from authoritative sources.','SC-21.3','The organization being inspected/assessed configures the:\n1. recursive/caching name server software to enable DNSSEC;\n2. software to enable DNSSEC validation; and\n3. software to establish a secure entry point trust anchor by installing key signing keys in the software configuration of trusted keys. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2467.','The organization conducting the inspection/assessment utilizes DNSSEC diagnostic tools, such as dig, and performs queries which will exercise the data flow path for recursive name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2467.'),
('002468','draft','2013-07-02','DISA FSO','technical','The information system performs data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.','SC-21.4','The organization being inspected/assessed configures the:\n1. recursive/caching name server software to enable DNSSEC;\n2. software to enable DNSSEC validation; and\n3. software to establish a secure entry point trust anchor by installing key signing keys in the software configuration of trusted keys. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that determines the name server software configuration files and pertains to CCI 2468.','The organization conducting the inspection/assessment utilizes DNSSEC diagnostic tools, such as dig, and performs queries which will exercise the data flow path for recursive name resolution services. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs that determine the name server software configuration files and pertain to CCI 2468.'),
('002469','draft','2013-07-02','DISA FSO','policy','The organization defines the certificate authorities the information system will allow to be used on the information system.','SC-23(5).1','DoD has defined the certificate authorities as DoD PKI established certificate authorities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the certificate authorities as DoD PKI established certificate authorities.'),
('002470','draft','2013-07-02','DISA FSO','technical','The information system only allows the use of organization-defined certificate authorities for verification of the establishment of protected sessions.','SC-23(5).2','The organization being inspected/assessed configures the information system to allow the use of DoD PKI established certificate authorities for verification of the establishment of protected sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2470. DoD has defined the certificate authorities as DoD PKI established certificate authorities.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to allow the use of DoD PKI established certificate authorities for verification of the establishment of protected sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2470. DoD has defined the certificate authorities as DoD PKI established certificate authorities.'),
('002471','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components, with minimal functionality and information storage, to be employed.','SC-25.2','The organization being inspected/assessed defines and documents the information system components, with minimal functionality and information storage, to be employed. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components, with minimal functionality and information storage, to be employed. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002472','draft','2013-07-02','DISA FSO','policy','The organization defines the information at rest that is to be protected by the information system.','SC-28.2','The organization being inspected/assessed defines and documents the information at rest that is to be protected by the information system which must include, at a minimum, PII and classified information. DoD has determined the information at rest is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information at rest to ensure the organization being inspected/assessed defines and documents the information at rest that is to be protected by the information system which must include, at a minimum, PII and classified information. DoD has determined the information at rest is not appropriate to define at the Enterprise level.'),
('002473','draft','2013-07-02','DISA FSO','policy','The organization defines the information at rest for which cryptographic mechanisms will be implemented.','SC-28(1).1','The organization being inspected/assessed defines and documents the information at rest that is to be protected by the information system which must include, at a minimum, PII and classified information. DoD has determined the information at rest is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information at rest to ensure the organization being inspected/assessed defines and documents the information at rest that is to be protected by the information system which must include, at a minimum, PII and classified information. DoD has determined the information at rest is not appropriate to define at the Enterprise level.'),
('002474','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components which require the implementation of cryptographic mechanisms to prevent unauthorized disclosure and modification of organization-defined information at rest.','SC-28(1).2','DoD has defined the information system components as any information system components storing data defined in SC-28 (1), 2473.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as any information system components storing data defined in SC-28 (1), 2473.'),
('002475','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components.','SC-28(1).3','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent unauthorized modification of information at rest defined in SC-28 (1), CCI 2473 on any information system components storing data defined in SC-28 (1), 2473. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2475. DoD has defined the information system components as any information system components storing data defined in SC-28 (1), 2473.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent unauthorized modification of information at rest defined in SC-28 (1), CCI 2473 on any information system components storing data defined in SC-28 (1), 2473. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2475. DoD has defined the information system components as any information system components storing data defined in SC-28 (1), 2473.'),
('002476','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined information system components.','SC-28(1).4','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent unauthorized disclosure of information at rest defined in SC-28 (1), CCI 2473 on any information system components storing data defined in SC-28 (1), 2473. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2476. DoD has defined the information system components as any information system components storing data defined in SC-28 (1), 2473.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent unauthorized disclosure of information at rest defined in SC-28 (1), CCI 2473 on any information system components storing data defined in SC-28 (1), 2473. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2476. DoD has defined the information system components as any information system components storing data defined in SC-28 (1), 2473.'),
('002477','draft','2013-07-02','DISA FSO','policy','The organization defines the information at rest to be removed from online storage and stored in an off-line secure location.','SC-28(2).1','The organization being inspected/assessed defines and documents the information at rest to be removed from on-line storage and stored in an off-line secure location. DoD has determined the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information to ensure the organization being inspected/assessed defines the information at rest to be removed from on-line storage and stored in an off-line secure location. DoD has determined the information is not appropriate to define at the Enterprise level.'),
('002478','draft','2013-07-02','DISA FSO','policy','The organization removes organization-defined information at rest from online storage.','SC-28(2).2','The organization being inspected/assessed documents and implements a process to remove information at rest defined in SC-28 (2), CCI 2477 from online storage.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed removes information at rest defined in SC-28 (2), CCI 2477 from online storage. Additionally, the organization conducting the inspection/assessment examines the information system to ensure that information defined in SC-28 (2), CCI 2477 is not stored on the information system.'),
('002479','draft','2013-07-02','DISA FSO','policy','The organization stores organization-defined information at rest in an off-line secure location.','SC-28(2).3','The organization being inspected/assessed documents and implements a process to store information at rest defined in SC-28 (2), CCI 2477 in an off-line secure location.','The organization conducting the inspection/assessment obtains and examines the documented process and off-line storage records to ensure the organization being inspected/assessed stores information at rest defined in SC-28 (2), CCI 2477 in an off-line secure location.'),
('002480','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components for which a diverse set of information technologies are to be employed.','SC-29.2','The organization being inspected/assessed defines and documents the information system components for which a diverse set of information technologies are to be employed. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components for which a diverse set of information technologies are to be employed. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002481','draft','2013-07-02','DISA FSP','policy','The organization employs virtualization techniques to support the deployment of a diversity of applications that are changed per organization-defined frequency.','SC-29(1).3','The organization being inspected/assessed designs the information system to employ virtualization techniques to support the deployment of a diversity of applications that are changed per the frequency defined in SC-29 (1), CCI 1204.','The organization conducting the inspection/assessment obtains and examines the hardware and software lists to ensure the organization being inspected/assessed employs virtualization techniques to support the deployment of a diversity of applications that are changed per the frequency defined in SC-29 (1), CCI 1204.'),
('002482','draft','2013-07-02','DISA FSO','policy','The organization defines the concealment and misdirection techniques employed for organization-defined information systems to confuse and mislead adversaries.','SC-30.1','The organization being inspected/assessed defines and documents the concealment and misdirection techniques employed for organization-defined information systems to confuse and mislead adversaries. DoD has determined the concealment and misdirection techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented concealment and misdirection techniques to ensure the organization being inspected/assessed defines the concealment and misdirection techniques employed for organization-defined information systems to confuse and mislead adversaries..\nDoD has determined the concealment and misdirection techniques are not appropriate to define at the Enterprise level.'),
('002483','draft','2013-07-02','DISA FSO','policy','The organization defines the information systems for which organization-defined concealment and misdirection techniques are to be employed.','SC-30.2','The organization being inspected/assessed defines and documents the information systems for which organization-defined concealment and misdirection techniques are to be employed. DoD has determined the information systems are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems to ensure the organization being inspected/assessed defines the information systems for which organization-defined concealment and misdirection techniques are to be employed. DoD has determined the information systems are not appropriate to define at the Enterprise level.'),
('002484','draft','2013-07-02','DISA FSO','policy','The organization defines the time periods at which it will employ organization-defined concealment and misdirection techniques on organization-defined information systems.','SC-30.3','The organization being inspected/assessed defines and documents the time periods at which it will employ organization-defined concealment and misdirection techniques on organization-defined information systems. DoD has determined the time periods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time periods to ensure the organization being inspected/assessed defines the time periods at which it will employ organization-defined concealment and misdirection techniques on organization-defined information systems. DoD has determined the time periods are not appropriate to define at the Enterprise level.'),
('002485','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined concealment and misdirection techniques for organization-defined information systems at organization-defined time periods to confuse and mislead adversaries.','SC-30.4','The organization being inspected/assessed designs the information system to employ concealment and misdirection techniques defined in SC-30, CCI 2482 for information systems defined in SC-30, 2483 at time periods defined in SC-30, CCI 2484 to confuse and mislead adversaries.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying concealment and misdirection techniques to ensure the organization being inspected/assessed employs concealment and misdirection techniques defined in SC-30, CCI 2482 for information systems defined in SC-30, 2483 at time periods defined in SC-30, CCI 2484 to confuse and mislead adversaries.'),
('002486','draft','2013-07-02','DISA FSO','policy','The organization defines the techniques to be employed to introduce randomness into organizational operations and assets.','SC-30(2).1','The organization being inspected/assessed defines and documents the techniques to be employed to introduce randomness into organizational operations and assets. DoD has determined the techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques to ensure the organization being inspected/assessed defines the techniques to be employed to introduce randomness into organizational operations and assets. DoD has determined the techniques are not appropriate to define at the Enterprise level.'),
('002487','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined techniques to introduce randomness into organizational operations.','SC-30(2).2','The organization being inspected/assessed employs techniques defined in SC-30 (2), CCI 2486 to introduce randomness into organizational operations.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of techniques used to introduce randomness to ensure the organization being inspected/assessed employs techniques defined in SC-30 (2), CCI 2486 to introduce randomness into organizational operations.'),
('002488','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined techniques to introduce randomness into organizational assets.','SC-30(2).3','The organization being inspected/assessed employs techniques defined in SC-30 (2), CCI 2486 to introduce randomness into organizational assets.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of techniques used to introduce randomness to ensure the organization being inspected/assessed employs techniques defined in SC-30 (2), CCI 2486 to introduce randomness into organizational assets.'),
('002489','draft','2013-07-02','DISA FSO','policy','The organization defines the processing and/or storage locations to be changed at random intervals or at an organization-defined frequency.','SC-30(3).1','The organization being inspected/assessed defines and documents the processing and/or storage locations to be changed at random intervals or at an organization-defined frequency. DoD has determined the processing and/or storage sites are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented processing and/or storage sites to ensure the organization being inspected/assessed defines the processing and/or storage locations to be changed at random intervals or at an organization-defined frequency. DoD has determined the processing and/or storage sites are not appropriate to define at the Enterprise level.'),
('002490','draft','2013-07-02','DISA FSO','policy','The organization defines the frequency at which it changes the location of organization-defined processing and/or storage.','SC-30(3).2','The organization being inspected/assessed defines and documents the frequency at which it changes the location of organization-defined processing and/or storage. The frequency can be defined as random time intervals. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency at which it changes the location of organization-defined processing and/or storage. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('002491','deprecated','2013-07-02','DISA FSO','policy','The organization changes the location of organization-defined processing and/or storage at an organization-defined time frequency or at random time intervals.',NULL,NULL,NULL),
('002492','draft','2013-07-02','DISA FSO','policy','The organization changes the location of organization-defined processing and/or storage at an organization-defined time frequency or at random time intervals.','SC-30(3).3','The organization being inspected/assessed documents and implements a process to change the location of the processing and/or storage defined in SC-30 (3), CCI 2489 at the time frequency defined in SC-30 (3), CCI 2490 or at random time intervals. The organization must maintain an audit trail of changes.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of changes to ensure the organization being inspected/assessed changes the location of the processing and/or storage defined in SC-30 (3), CCI 2489 at the time frequency defined in SC-30 (3), CCI 2490 or at random time intervals.'),
('002493','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components in which it will employ realistic but misleading information regarding its security state or posture.','SC-30(4).1','The organization being inspected/assessed defines and documents the information system components in which it will employ realistic but misleading information regarding its security state or posture. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components in which it will employ realistic but misleading information regarding its security state or posture. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002494','draft','2013-07-02','DISA FSO','policy','The organization employs realistic, but misleading, information in organization-defined information system components with regard to its security state or posture.','SC-30(4).2','The organization being inspected/assessed employs realistic, but misleading, information in information system components defined in SC-30 (4), CCI 2493 with regard to its security state or posture.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of methods to employ misinformation to ensure the organization being inspected/assessed employs realistic, but misleading, information in information system components defined in SC-30 (4), CCI 2493 with regard to its security state or posture.'),
('002495','draft','2013-07-02','DISA FSO','policy','The organization defines the techniques to be employed to hide or conceal organization-defined information system components.','SC-30(5).1','The organization being inspected/assessed defines and documents the techniques to be employed to hide or conceal organization-defined information system components. DoD has determined the techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques to ensure the organization being inspected/assessed defines the techniques to be employed to hide or conceal organization-defined information system components. DoD has determined the techniques are not appropriate to define at the Enterprise level.'),
('002496','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components to be hidden or concealed.','SC-30(5).2','The organization being inspected/assessed defines and documents the information system components to be hidden or concealed. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components to be hidden or concealed. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002497','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined techniques to hide or conceal organization-defined information system components.','SC-30(5).3','The organization being inspected/assessed employs techniques defined in SC-30 (5), CCI 2495 to hide or conceal information system components defined in SC-30 (5), CCI 2496.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of techniques to conceal information to ensure the organization being inspected/assessed employs techniques defined in SC-30 (5), CCI 2495 to hide or conceal information system components defined in SC-30 (5), CCI 2496.'),
('002498','draft','2013-07-02','DISA FSO','policy','The organization performs a covert channel analysis to identify those aspects of communications within the information system that are potential avenues for covert storage and/or timing channels.','SC-31.1','The organization being inspected/assessed performs a covert channel analysis to identify those aspects of communications within the information system that are potential avenues for covert storage and/or timing channels. The organization must maintain an audit trail of analyses.','The organization conducting the inspection/assessment obtains and examines the results of the analysis to ensure the organization being inspected/assessed performs a covert channel analysis to identify those aspects of communications within the information system that are potential avenues for covert storage and/or timing channels.'),
('002499','draft','2013-07-02','DISA FSO','policy','The organization estimates the maximum bandwidth of the covert storage and timing channels.','SC-31.2','The organization being inspected/assessed implements a process to estimate the maximum bandwidth of the covert storage and timing channels.','The organization conducting the inspection/assessment obtains and examines the estimate to ensure the organization being inspected/assessed estimates the maximum bandwidth of the covert storage and timing channels.'),
('002500','draft','2013-07-02','DISA FSO','policy','The organization defines the maximum bandwidth values to which covert storage and/or timing channels are to be reduced.','SC-31(2).1','The organization being inspected/assessed defines and documents the maximum bandwidth values to which covert storage and/or timing channels are to be reduced. DoD has determined the maximum bandwidth values are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented maximum bandwidth values to ensure the organization being inspected/assessed defines the maximum bandwidth values to which covert storage and/or timing channels are to be reduced. DoD has determined the maximum bandwidth values are not appropriate to define at the Enterprise level.'),
('002501','draft','2013-07-02','DISA FSO','policy','The organization reduces the maximum bandwidth for identified covert storage and/or timing channels to organization-defined values.','SC-31(2).2','The organization being inspected/assessed reduces the maximum bandwidth for identified covert storage and/or timing channels to values defined in SC-31 (2), CCI 2500.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of bandwidth reduction to ensure the organization being inspected/assessed reduces the maximum bandwidth for identified covert storage and/or timing channels to values defined in SC-31 (2), CCI 2500.'),
('002502','draft','2013-07-02','DISA FSO','policy','The organization defines the subset of identified covert channels in the operational environment of the information system that are to have the bandwidth measured.','SC-31(3).1','The organization being inspected/assessed defines and documents the subset of identified covert channels in the operational environment of the information system that are to have the bandwidth measured. DoD has determined the subset is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented subset of identified covert channels to ensure the organization being inspected/assessed defines the subset of identified covert channels in the operational environment of the information system that are to have the bandwidth measured. DoD has determined the subset is not appropriate to define at the Enterprise level.'),
('002503','draft','2013-07-02','DISA FSO','policy','The organization measures the bandwidth of an organization-defined subset of identified covert channels in the operational environment of the information system.','SC-31(3).2','The organization being inspected/assessed measures the bandwidth of a subset of identified covert channels defined in SC-31 (3), CCI 2502 in the operational environment of the information system.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of measurements to ensure the organization being inspected/assessed measures the bandwidth of a subset of identified covert channels defined in SC-31 (3), CCI 2502 in the operational environment of the information system.'),
('002504','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components into which the information system is partitioned.','SC-32.1','The organization being inspected/assessed defines and documents the information system components into which the information system is partitioned. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed defines the information system components into which the information system is partitioned. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002505','draft','2013-07-02','DISA FSO','policy','The organization defines the circumstances under which the information system components are to be physically separated to support partitioning.','SC-32.2','The organization being inspected/assessed defines and documents the circumstances under which the information system components are to be physically separated to support partitioning. DoD has determined the circumstances are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances to ensure the organization being inspected/assessed defines the circumstances under which the information system components are to be physically separated to support partitioning. DoD has determined the circumstances are not appropriate to define at the Enterprise level.'),
('002506','draft','2013-07-02','DISA FSO','policy','The organization partitions the information system into organization-defined information system components residing in separate physical domains or environments based on organization-defined circumstances for physical separation of components.','SC-32.3','The organization being inspected/assessed designs the information system to partition components defined in SC-32, CCI 2504 residing in separate physical domains or environments based on circumstances defined in SC-32, CCI 2505 for physical separation of components.','The organization conducting the inspection/assessment obtains and examines network topology diagrams, architecture documentation, or any other documentation identifying component partitioning to ensure the organization being inspected/assessed partitions components defined in SC-32, CCI 2504 residing in separate physical domains or environments based on circumstances defined in SC-32, CCI 2505 for physical separation of components.'),
('002507','draft','2013-07-02','DISA FSO','policy','The organization controls read-only media after information has been recorded onto the media.','SC-34(2).2','The organization being inspected/assessed documents and implements mechanisms to control the read-only media after information has been recorded onto the media.','The organization conducting the inspection/assessment obtains and examines the documented mechanisms to ensure the organization being inspected/assessed controls the read-only media after information has been recorded onto the media.'),
('002508','draft','2013-07-02','DISA FSO','policy','The organization defines the information system firmware components for which hardware-based, write-protect is employed.','SC-34(3).1','The organization being inspected/assessed defines and documents the information system firmware components for which hardware-based, write-protect is employed. DoD has determined the information system firmware components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system firmware components to ensure the organization being inspected/assessed defines the information system firmware components for which hardware-based, write-protect is employed. DoD has determined the information system firmware components are not appropriate to define at the Enterprise level.'),
('002509','draft','2013-07-02','DISA FSO','policy','The organization employs hardware-based, write-protect for organization-defined information system firmware components.','SC-34(3).2','The organization being inspected/assessed employs hardware-based, write-protect for information system firmware components defined in SC-34 (3), CCI 2508.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of hardware-based, write-protect to ensure the organization being inspected/assessed employs hardware-based, write-protect for information system firmware components defined in SC-34 (3), CCI 2508.'),
('002510','draft','2013-07-02','DISA FSO','policy','The organization defines the individuals authorized to manually disable hardware-based, write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode.','SC-34(3).3','The organization being inspected/assessed defines and documents the individuals authorized to manually disable hardware-based, write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode. DoD has determined the individuals are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented authorized individuals to ensure the organization being inspected/assessed defines the individuals authorized to manually disable hardware-based, write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode. DoD has determined the individuals are not appropriate to define at the Enterprise level.'),
('002511','draft','2013-07-02','DISA FSO','policy','The organization implements specific procedures for organization-defined authorized individuals to manually disable hardware-based, write-protect for firmware modifications.','SC-34(3).4','The organization being inspected/assessed documents and implements specific procedures for authorized individuals defined in SC-34 (3), CCI 2510 to manually disable hardware-based, write-protect for firmware modifications.','The organization conducting the inspection/assessment obtains and examines the documented procedures and a sampling of the information system components defined in SC-34 (3), CCI 2508 to ensure the organization being inspected/assessed implements specific procedures for authorized individuals defined in SC-34 (3), CCI 2510 to manually disable hardware-based, write-protect for firmware modifications.'),
('002512','draft','2013-07-02','DISA FSO','policy','The organization implements specific procedures for organization-defined authorized individuals to manually re-enable hardware write-protect prior to returning to operational mode.','SC-34(3).5','The organization being inspected/assessed documents and implements specific procedures for authorized individuals defined in SC-34 (3), CCI 2510 to manually re-enable the write-protect prior to returning to operational mode.','The organization conducting the inspection/assessment obtains and examines the documented procedures and a sampling of the information system components defined in SC-34 (3), CCI 2508 to ensure the organization being inspected/assessed implements specific procedures for authorized individuals defined in SC-34 (3), CCI 2510 to manually re-enable the write-protect prior to returning to operational mode.'),
('002513','draft','2013-07-02','DISA FSO','policy','The organization defines the processing that is to be distributed across multiple physical locations.','SC-36.1','The organization being inspected/assessed defines and documents the processing that is to be distributed across multiple physical locations. DoD has determined the processing is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented processing to ensure the organization being inspected/assessed defines the processing that is to be distributed across multiple physical locations. DoD has determined the processing is not appropriate to define at the Enterprise level.'),
('002514','draft','2013-07-02','DISA FSO','policy','The organization defines the storage that is to be distributed across multiple physical locations.','SC-36.2','The organization being inspected/assessed defines and documents the storage that is to be distributed across multiple physical locations. DoD has determined the storage is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented storage to ensure the organization being inspected/assessed defines the storage that is to be distributed across multiple physical locations. DoD has determined the storage is not appropriate to define at the Enterprise level.'),
('002515','draft','2013-07-02','DISA FSO','policy','The organization distributes organization-defined processing across multiple physical locations.','SC-36.3','The organization being inspected/assessed distributes processing defined in SC-36, CCI 2513 across multiple physical locations.','The organization conducting the inspection/assessment obtains and examines hardware lists and other applicable artifacts to ensure the organization being inspected/assessed distributes processing defined in SC-36, CCI 2513 across multiple physical locations.'),
('002516','draft','2013-07-02','DISA FSO','policy','The organization distributes organization-defined storage across multiple physical locations.','SC-36.4','The organization being inspected/assessed distributes storage defined in SC-36, CCI 2514 across multiple physical locations.','The organization conducting the inspection/assessment obtains and examines hardware lists and other applicable artifacts to ensure the organization being inspected/assessed distributes storage defined in SC-36, CCI 2514 across multiple physical locations.'),
('002517','draft','2013-07-02','DISA FSO','policy','The organization defines the distributed processing components that are to be polled to identify potential faults, errors, or compromises.','SC-36(1).1','The organization being inspected/assessed defines and documents the distributed processing components that are to be polled to identify potential faults, errors, or compromises. DoD has determined the distributed processing components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented distributed processing components to ensure the organization being inspected/assessed defines the distributed processing components that are to be polled to identify potential faults, errors, or compromises. DoD has determined the distributed processing components are not appropriate to define at the Enterprise level.'),
('002518','draft','2013-07-02','DISA FSO','policy','The organization defines the distributed storage components that are to be polled to identify potential faults, errors, or compromises.','SC-36(1).2','The organization being inspected/assessed defines and documents the distributed storage components that are to be polled to identify potential faults, errors, or compromises. DoD has determined the distributed storage components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented distributed storage components to ensure the organization being inspected/assessed defines the distributed storage components that are to be polled to identify potential faults, errors, or compromises. DoD has determined the distributed storage components are not appropriate to define at the Enterprise level.'),
('002519','draft','2013-07-02','DISA FSO','policy','The organization employs polling techniques to identify potential faults, errors, or compromises to organization-defined distributed processing components.','SC-36(1).3','The organization being inspected/assessed designs and configures the information system to employ polling techniques to identify potential faults, errors, or compromises to distributed processing components defined in SC-36 (1), CCI 2517. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2519.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ polling techniques to identify potential faults, errors, or compromises to distributed processing components defined in SC-36 (1), CCI 2517. If there is no applicable STIG for the polling technique in use, the organization conducting the inspection/assessment obtains and examines system design documents to ensure the organization being inspected/assessed employs polling techniques to identify potential faults, errors, or compromises to distributed processing components defined in SC-36 (1), CCI 2517. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2519.'),
('002520','draft','2013-07-02','DISA FSO','policy','The organization employs polling techniques to identify potential faults, errors, or compromises to organization-defined distributed storage components.','SC-36(1).4','The organization being inspected/assessed designs and configures the information system to employ polling techniques to identify potential faults, errors, or compromises to distributed storage components defined in SC-36 (1), CCI 2518. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2520.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to employ polling techniques to identify potential faults, errors, or compromises to distributed storage components defined in SC-36 (1), CCI 2518. If there is no applicable STIG for the polling technique in use, the organization conducting the inspection/assessment obtains and examines system design documents to ensure the organization being inspected/assessed employs polling techniques to identify potential faults, errors, or compromises to distributed storage components defined in SC-36 (1), CCI 2518. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2520.'),
('002521','draft','2013-07-02','DISA FSO','policy','The organization defines the out-of-band channels to be employed for the physical delivery or electronic transmission of organization-defined information, information system components, or devices.','SC-37.1','The organization being inspected/assessed defines and documents the out-of-band channels to be employed for the physical delivery or electronic transmission of organization-defined information, information system components, or devices. DoD has determined the out-of-band channels are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented out-of-band channels to ensure the organization being inspected/assessed defines the out-of-band channels to be employed for the physical delivery or electronic transmission of organization-defined information, information system components, or devices. DoD has determined the out-of-band channels are not appropriate to define at the Enterprise level.'),
('002522','draft','2013-07-02','DISA FSO','policy','The organization defines the information, information system components, or devices that are to be electronically transmitted or physically delivered via organization-defined out-of-band channels.','SC-37.2','The organization being inspected/assessed defines and documents the information, information system components or devices that are to be electronically transmitted or physically delivered via organization-defined out-of-band channels. DoD has determined the information, information system components, or devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information, information system components or devices to ensure the organization being inspected/assessed defines the information, information system components or devices that are to be electronically transmitted or physically delivered via organization-defined out-of-band channels. DoD has determined the information, information system components, or devices are not appropriate to define at the Enterprise level.'),
('002523','draft','2013-07-02','DISA FSO','policy','The organization defines the individuals or information systems authorized to be recipients of organization-defined information, information system components, or devices to be delivered by employing organization-defined out-of-band channels for electronic transmission or physical delivery.','SC-37.3','The organization being inspected/assessed defines and documents the individuals or information systems authorized to be recipients of organization-defined information, information system components, or devices to be delivered by employing organization-defined out-of-band channels for electronic transmission or physical delivery.\n\nDoD has determined the individuals or information systems are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information, information system components, or devices to ensure the organization being inspected/assessed defines the individuals or information systems authorized to be recipients of organization-defined information, information system components, or devices to be delivered by employing organization-defined out-of-band channels for electronic transmission or physical delivery. DoD has determined the individuals or information systems are not appropriate to define at the Enterprise level.'),
('002524','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined out-of-band channels for the electronic transmission or physical delivery of organization-defined information, information system components, or devices to organization-defined individuals or information systems.','SC-37.4','The organization being inspected/assessed employs out-of-band channels defined in SC-37, CCI 2521 for the electronic transmission or physical delivery of information, information system components, or devices defined in SC-37, CCI 2522 to individuals or information systems defined in SC-37, CCI 2523.','The organization conducting the inspection/assessment obtains and examines any applicable evidence of out-of-band channels to ensure the organization being inspected/assessed employs out-of-band channels defined in SC-37, CCI 2521 for the electronic transmission or physical delivery of information, information system components, or devices defined in SC-37, CCI 2522 to individuals or information systems defined in SC-37, CCI 2523.'),
('002525','draft','2013-07-02','DISA FSO','policy','The organization defines the security safeguards to be employed to ensure only organization-defined individuals or information systems receive organization-defined information, information system components, or devices.','SC-37(1).2','The organization being inspected/assessed defines and documents the security safeguards to be employed to ensure only organization-defined individuals or information systems receive organization-defined information, information system components or devices. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examine the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be employed to ensure only organization-defined individuals or information systems receive organization-defined information, information system components or devices. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002526','draft','2013-07-02','DISA FSO','policy','The organization defines the information, information system components, or devices which are to be received only by organization-defined individuals or information systems.','SC-37(1).3','The organization being inspected/assessed defines and documents the information, information system components or devices which are to be received only by organization-defined individuals or information systems. DoD has determined the information, information system components or devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information, information system components or devices to ensure the organization being inspected/assessed defines the information, information system components or devices which are to be received only by organization-defined individuals or information systems. DoD has determined the information, information system components or devices are not appropriate to define at the Enterprise level.'),
('002527','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined security safeguards to ensure only organization-defined individuals or information systems receive the organization-defined information, information system components, or devices.','SC-37(1).4','The organization being inspected/assessed implements security safeguards defined in SC-37 (1), CCI 2525 to ensure only individuals or information systems defined in SC-37 (1), CCI 2523 receive the information, information system components, or devices defined in SC-37 (1), CCI 2526. The organization must maintain an audit trail of security safeguard implementation.','The organization conducting the inspection/assessment obtains and examines the audit trail of security safeguard implementation to ensure the organization being inspected/assessed employs security safeguards defined in SC-37 (1), CCI 2525 to ensure only individuals or information systems defined in SC-37 (1), CCI 2523 receive the information, information system components, or devices defined in SC-37 (1), CCI 2526.'),
('002528','draft','2013-07-02','DISA FSO','policy','The organization defines the operations security safeguards to be employed to protect key organizational information throughout the system development life cycle.','SC-38.1','The organization being inspected/assessed defines and documents the operations security safeguards to be employed to protect key organizational information throughout the system development life cycle. DoD has determined the operations security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented operations security safeguards to ensure the organization being inspected/assessed defines the operations security safeguards to be employed to protect key organizational information throughout the system development life cycle. DoD has determined the operations security safeguards are not appropriate to define at the Enterprise level.'),
('002529','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined operations security safeguards to protect key organizational information throughout the system development life cycle.','SC-38.2','The organization being inspected/assessed implements operations security safeguards defined in SC-38, CCI 2528 to protect key organizational information throughout the system development life cycle. The organization must maintain an audit trail of security safeguard implementation.','The organization conducting the inspection/assessment obtains and examines the audit trail of security safeguard implementation to ensure the organization being inspected/assessed employs operations security safeguards defined in SC-38, CCI 2528 to protect key organizational information throughout the system development life cycle.'),
('002530','draft','2013-07-02','DISA FSO','technical','The information system maintains a separate execution domain for each executing process.','SC-39.1','The organization being inspected/assessed configures the information system to maintain a separate execution domain for each executing process. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2530.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain a separate execution domain for each executing process. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2530.'),
('002531','draft','2013-07-02','DISA FSO','technical','The information system implements underlying hardware separation mechanisms to facilitate process separation.','SC-39(1).1','The organization being inspected/assessed configures the information system to implement underlying hardware separation mechanisms to facilitate process separation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2531.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement underlying hardware separation mechanisms to facilitate process separation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2531.'),
('002532','draft','2013-07-02','DISA FSO','policy','The organization defines the multi-threaded processing in which a separate execution domain is maintained by the information system for each thread.','SC-39(2).1','The organization being inspected/assessed defines and documents the multi-threaded processing in which a separate execution domain is maintained by the information system for each thread. DoD has determined the multi-threaded processing is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented multi-thread processing to ensure the organization being inspected/assessed defines the multi-threaded processing in which a separate execution domain is maintained by the information system for each thread. DoD has determined the multi-threaded processing is not appropriate to define at the Enterprise level.'),
('002533','draft','2013-07-02','DISA FSO','technical','The information system maintains a separate execution domain for each thread in organization-defined multi-threaded processing.','SC-39(2).2','The organization being inspected/assessed configures the information system to maintain a separate execution domain for each thread in multi-threaded processing defined in SC-39 (2), CCI 2532. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2533.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to maintain a separate execution domain for each thread in multi-threaded processing defined in SC-39 (2), CCI 2532. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2533.'),
('002534','draft','2013-07-02','DISA FSO','policy','The organization defines types of signal parameter attacks or references to sources for such attacks from which the information system protects organization-defined wireless links.','SC-40.1','The organization being inspected/assessed defines and documents the types of signal parameter attacks or references to sources for such attacks from which the information system protects organization-defined wireless links. DoD has determined the signal parameter attacks or references to sources for such attacks are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented signal parameter attacks or references to sources for such attacks to ensure the organization being inspected/assessed defines types of signal parameter attacks or references to sources for such attacks from which the information system protects organization-defined wireless links. DoD has determined the signal parameter attacks or references to sources for such attacks are not appropriate to define at the Enterprise level.'),
('002535','draft','2013-07-02','DISA FSO','policy','The organization defines the external and internal wireless links the information system is to protect from organization-defined types of signal parameter attacks or references to sources for such attacks.','SC-40.2','DoD has defined the wireless links as all non-COTS wireless links.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the wireless links as all non-COTS wireless links.'),
('002536','draft','2013-07-02','DISA FSO','technical','The information system protects organization-defined external and internal wireless links from organization-defined types of signal parameter attacks or references to sources for such attacks.','SC-40.3','The organization being inspected/assessed designs the information system to protect all non-COTS wireless links from types of signal parameter attacks or references to sources for such attacks defined in SC-40, CCI 2534. DoD has defined the wireless links as all non-COTS wireless links.','The organization conducting the inspection/assessment obtains and examines design documentation for wireless links to ensure the organization being inspected/assessed protects all non-COTS wireless links from types of signal parameter attacks or references to sources for such attacks defined in SC-40, CCI 2534. DoD has defined the wireless links as all non-COTS wireless links.'),
('002537','draft','2013-07-02','DISA FSO','policy','The organization defines the level of protection against the effects of intentional electromagnetic interference to be achieved by implemented cryptographic mechanisms.','SC-40(1).1','The organization being inspected/assessed defines and documents the level of protection against the effects of intentional electromagnetic interference to be achieved by implemented cryptographic mechanisms. DoD has determined the level of protection is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of protection to ensure the organization being inspected/assessed defines the level of protection against the effects of intentional electromagnetic interference to be achieved by implemented cryptographic mechanisms. DoD has determined the level of protection is not appropriate to define at the Enterprise level.'),
('002538','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms that achieve an organization-defined level of protection against the effects of intentional electromagnetic interference.','SC-40(1).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms that achieve level of protection defined in SC-40 (1), CCI 2537 against the effects of intentional electromagnetic interference. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2538.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms that achieve level of protection defined in SC-40 (1), CCI 2537 against the effects of intentional electromagnetic interference. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2538.'),
('002539','draft','2013-07-02','DISA FSO','policy','The organization defines the level of reduction the information system is to implement to reduce the detection potential of wireless links.','SC-40(2).1','The organization being inspected/assessed defines and documents the level of reduction the information system is to implement to reduce the detection potential of wireless links. DoD has determined the level of reduction is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of reduction to ensure the organization being inspected/assessed defines the level of reduction the information system is to implement to reduce the detection potential of wireless links. DoD has determined the level of reduction is not appropriate to define at the Enterprise level.'),
('002540','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to reduce the detection potential of wireless links to an organization-defined level of reduction.','SC-40(2).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to reduce the detection potential of wireless links to the level of reduction defined in SC-40 (2), CCI 2539. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2540.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to reduce the detection potential of wireless links to the level of reduction defined in SC-40 (2), CCI 2539. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2540.'),
('002541','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.','SC-40(3).1','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2541.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2541.'),
('002542','draft','2013-07-02','DISA FSO','policy','The organization defines the wireless transmitters that are to have cryptographic mechanisms implemented by the information system to prevent the identification of the wireless transmitters.','SC-40(4).1','The organization being inspected/assessed defines and documents the wireless transmitters that are to have cryptographic mechanisms implemented by the information system to prevent the identification of the wireless transmitters. DoD has determined the wireless transmitters are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented wireless transmitters to ensure the organization being inspected/assessed defines the wireless transmitters that are to have cryptographic mechanisms implemented by the information system to prevent the identification of the wireless transmitters. DoD has determined the wireless transmitters are not appropriate to define at the Enterprise level.'),
('002543','draft','2013-07-02','DISA FSO','technical','The information system implements cryptographic mechanisms to prevent the identification of organization-defined wireless transmitters by using the transmitter signal parameters.','SC-40(4).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent the identification of wireless transmitters defined in SC-40 (4), CCI 2542 by using the transmitter signal parameters. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2543.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to prevent the identification of wireless transmitters defined in SC-40 (4), CCI 2542 by using the transmitter signal parameters. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2543.'),
('002544','draft','2013-07-02','DISA FSO','policy','The organization defines the information systems or information system components on which organization-defined connection ports or input/output devices are to be physically disabled or removed.','SC-41.1','The organization being inspected/assessed defines and documents the information systems or information system components on which organization-defined connection ports or input/output devices are to be physically disabled or removed. DoD has determined the information systems or information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems or information system components to ensure the organization being inspected/assessed defines the information systems or information system components on which organization-defined connection ports or input/output devices are to be physically disabled or removed. DoD has determined the information systems or information system components are not appropriate to define at the Enterprise level.'),
('002545','draft','2013-07-02','DISA FSO','policy','The organization defines the connection ports or input/output devices that are to be physically disabled or removed from organization-defined information systems or information system components.','SC-41.2','The organization being inspected/assessed defines and documents the connection ports or input/output devices that are to be physically disabled or removed from organization-defined information systems or information system components. DoD has determined the connection ports or input/output devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented connection ports or input/output devices to ensure the organization being inspected/assessed defines the connection ports or input/output devices that are to be physically disabled or removed from organization-defined information systems or information system components. DoD has determined the connection ports or input/output devices are not appropriate to define at the Enterprise level.'),
('002546','draft','2013-07-02','DISA FSO','technical','The organization physically disables or removes organization-defined connection ports or input/output devices on organization-defined information systems or information system components.','SC-41.3','The organization being inspected/assessed physically disables or removes connection ports or input/output devices defined in SC-41, CCI 2545 on information systems or information system components defined in SC-41, CCI 2544.','The organization conducting the inspection/assessment examines a sampling of devices to ensure the organization being inspected/assessed physically disables or removes connection ports or input/output devices defined in SC-41, CCI 2545 on information systems or information system components defined in SC-41, CCI 2544.'),
('002547','draft','2013-07-02','DISA FSO','policy','The organization defines the exceptions where remote activation of sensors is allowed.','SC-42.1','The organization being inspected/assessed defines and documents the exceptions where remote activation of sensors is allowed. DoD has determined the exceptions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented exceptions to ensure the organization being inspected/assessed defines the exceptions where remote activation of sensors is allowed. DoD has determined the exceptions are not appropriate to define at the Enterprise level.'),
('002548','draft','2013-07-02','DISA FSO','technical','The information system prohibits the remote activation of environmental sensing capabilities except for the organization-defined exceptions where remote activation of sensors is allowed.','SC-42.2','The organization being inspected/assessed configures the information system to prohibit the remote activation of environmental sensing capabilities except for the exceptions defined in SC-42, CCI 2547 where remote activation of sensors is allowed. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2548.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to prohibit the remote activation of environmental sensing capabilities except for the exceptions defined in SC-42, CCI 2547 where remote activation of sensors is allowed. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2548.'),
('002549','draft','2013-07-02','DISA FSO','policy','The organization defines the class of users to receive explicit indication of sensor use.','SC-42.3','DoD has defined the class of users all users unless documented by exception.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the class of users all users unless documented by exception.'),
('002550','draft','2013-07-02','DISA FSO','technical','The information system provides an explicit indication of sensor use to the organization-defined class of users.','SC-42.4','The organization being inspected/assessed configures the information system to provide an explicit indication of sensor use to all users unless documented by exception. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2550. DoD has defined the class of users all users unless documented by exception.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide an explicit indication of sensor use to all users unless documented by exception. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2550. DoD has defined the class of users all users unless documented by exception.'),
('002551','draft','2013-07-02','DISA FSO','policy','The organization defines the sensors to be configured so that collected data or information is reported only to authorized individuals or roles.','SC-42(1).1','The organization being inspected/assessed defines and documents the sensors to be configured so that collected data or information is reported only to authorized individuals or roles. DoD has determined the sensors are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented sensors to ensure the organization being inspected/assessed defines the sensors to be configured so that collected data or information is reported only to authorized individuals or roles. DoD has determined the sensors are not appropriate to define at the Enterprise level.'),
('002552','draft','2013-07-02','DISA FSO','policy','The organization ensures that the information system is configured so that data or information collected by the organization-defined sensors is only reported to authorized individuals or roles.','SC-42(1).2','The organization being inspected/assessed documents and implements a process to ensure that the information system is configured so that data or information collected by the sensors defined in SC-42 (1), CCI 2551 is only reported to authorized individuals or roles.','The organization conducting the inspection/assessed obtains and examines the documented process as well as a sampling of devices to ensure the organization being inspected/assessed configures the information system so that data or information collected by the sensors defined in SC-42 (1), CCI 2551 is only reported to authorized individuals or roles.'),
('002553','draft','2013-07-02','DISA FSO','policy','The organization defines the measures to be employed to ensure data or information collected by organization-defined sensors is used only for authorized purposes.','SC-42(2).1','The organization being inspected/assessed defines and documents the measures to be employed to ensure data or information collected by sensors defined in SC-42 (2), CCI 2554 is used only for authorized purposes. DoD has determined the measures are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented measures to ensure the organization being inspected/assessed defines the measures to be employed to ensure data or information collected by sensors defined in SC-42 (2), CCI 2554 is used only for authorized purposes. DoD has determined the measures are not appropriate to define at the Enterprise level.'),
('002554','draft','2013-07-02','DISA FSO','policy','The organization defines the sensors that are to collect data or information for authorized purposes.','SC-42(2).2','The organization being inspected/assessed defines and documents the sensors that are to collect data or information for authorized purposes. DoD has determined the sensors are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented sensors to ensure the organization being inspected/assessed defines the sensors that are to collect data or information for authorized purposes. DoD has determined the sensors are not appropriate to define at the Enterprise level.'),
('002555','draft','2013-07-02','DISA FSO','policy','The organization employs organization-defined measures, so that data or information collected by organization-defined sensors is only used for authorized purposes.','SC-42(2).3','The organization being inspected/assessed employs measures defined in SC-42 (2), CCI 2553 so that data or information collected by sensors defined in SC-42 (2), CCI 2554 is only used for authorized purposes.','The organization conducting the inspection/assessment ensures the measures defined in SC-42 (2), CCI 2553 are employed so that data or information collected by sensors defined in SC-42 (2), CCI 2554 is only used for authorized purposes.'),
('002556','draft','2013-07-02','DISA FSO','policy','The organization defines the environmental sensing capabilities prohibited on devices used in organization-defined facilities, areas, or systems.','SC-42(3).1','DoD has defined the environmental sensing capabilities as environmental sensing capabilities such as the recording audio or imagery (still or video) or transmitting information (i.e., cell phones, two way radios).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\nDoD has defined the environmental sensing capabilities as environmental sensing capabilities such as the recording audio or imagery (still or video) or transmitting information (i.e., cell phones, two way radios).'),
('002557','draft','2013-07-02','DISA FSO','policy','The organization defines the facilities, areas, or systems where devices processing organization-defined environmental sensing capabilities are prohibited.','SC-42(3).2','DoD has defined the facilities, areas, and systems as spaces where Classified information is stored, processed, displayed, or discussed.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the facilities, areas, and systems as spaces where Classified information is stored, processed, displayed, or discussed.'),
('002558','draft','2013-07-02','DISA FSO','policy','The organization prohibits the use of devices possessing organization-defined environmental sensing capabilities in organization-defined facilities, areas, or systems.','SC-42(3).3','The organization being inspected/assessed documents and implements a process to prohibit the use of devices possessing environmental sensing capabilities such as the recording audio or imagery (still or video) or transmitting information (i.e., cell phones, two way radios) in spaces where Classified information is stored, processed, displayed, or discussed.\nDoD has defined the environmental sensing capabilities as environmental sensing capabilities such as the recording audio or imagery (still or video) or transmitting information (i.e., cell phones, two way radios).\nDoD has defined the facilities, areas, and systems as spaces where Classified information is stored, processed, displayed, or discussed.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed prohibits the use of devices possessing environmental sensing capabilities such as the recording audio or imagery (still or video) or transmitting information (i.e., cell phones, two way radios) in spaces where Classified information is stored, processed, displayed, or discussed.\nDoD has defined the environmental sensing capabilities as environmental sensing capabilities such as the recording audio or imagery (still or video) or transmitting information (i.e., cell phones, two way radios).\nDoD has defined the facilities, areas, and systems as spaces where Classified information is stored, processed, displayed, or discussed.'),
('002559','draft','2013-07-02','DISA FSO','policy','The organization defines the information system components for which usage restrictions and implementation guidance are to be established.','SC-43.1','DoD has defined the information system components as all information system components (through the use of an acceptable use agreement).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as all information system components (through the use of an acceptable use agreement).'),
('002560','draft','2013-07-02','DISA FSO','policy','The organization establishes usage restrictions and implementation guidance for organization-defined information system components based on the potential to cause damage to the information system if used maliciously.','SC-43.2','The organization being inspected/assessed develops and implements usage restrictions and implementation guidance for all information system components (through the use of an acceptable use agreement). DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). ','The organization conducting the inspection/assessment obtains and examines implementation guidance and usage restrictions and verifies that the organization has implemented them for all information system components (through the use of an acceptable use agreement). DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). '),
('002561','draft','2013-07-02','DISA FSO','policy','The organization authorizes the use of organization-defined information system components which have the potential to cause damage to the information system if used maliciously.','SC-43.3','The organization being inspected/assessed documents and implements a process to authorize the use of all information system components (through the use of an acceptable use agreement) which have the potential to cause damage to the information system if used maliciously. The organization must maintain an audit trail of authorizations. DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). ','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of authorizations to ensure the organization being inspected/assessed authorizes the use of all information system components (through the use of an acceptable use agreement) which have the potential to cause damage to the information system if used maliciously. DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). '),
('002562','draft','2013-07-02','DISA FSO','policy','The organization monitors the use of organization-defined information system components which have the potential to cause damage to the information system if used maliciously.','SC-43.4','The organization being inspected/assessed documents and implements a process to monitor the use of all information system components (through the use of an acceptable use agreement) which have the potential to cause damage to the information system if used maliciously. The organization must maintain an audit trail of monitoring. DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). ','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring to ensure the organization being inspected/assessed monitors the use of all information system components (through the use of an acceptable use agreement). DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). '),
('002563','draft','2013-07-02','DISA FSO','policy','The organization controls the use of organization-defined information system components which have the potential to cause damage to the information system if used maliciously.','SC-43.5','The organization being inspected/assessed documents and implements a process to control the use of all information system components (through the use of an acceptable use agreement) which have the potential to cause damage to the information system if used maliciously. DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). ','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed controls the use of all information system components (through the use of an acceptable use agreement). DoD has defined the information system components as all information system components (through the use of an acceptable use agreement). '),
('002564','draft','2013-07-02','DISA FSO','policy','The organization defines the information system, system component, or location where a detonation chamber (i.e., dynamic execution environments) capability is employed.','SC-44.1','The organization being inspected/assessed defines and documents the information system, system components, or location where a detonation chamber (i.e., dynamic execution environments) capability is employed. DoD has determined the defines the information system, system components, or location are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system, system components, or location to ensure the organization being inspected/assessed defines the information system, system components, or location where a detonation chamber (i.e., dynamic execution environments) capability is employed. DoD has determined the defines the information system, system components, or location are not appropriate to define at the Enterprise level.'),
('002565','draft','2013-07-02','DISA FSO','policy','The organization employs a detonation chamber (i.e., dynamic execution environments) capability within an organization-defined information system, system component, or location.','SC-44.2','The organization being inspected/assessed implements a detonation chamber (i.e., dynamic execution environments, sandbox) capability within an information system, system component, or location defined in SC-44, CCI 2564. The organization must maintain an audit trail of detonation chamber implementation.','The organization conducting the inspection/assessment obtains and examines the documented detonation chamber to ensure the organization being inspected/assessed employs a detonation chamber (i.e., dynamic execution environments, sandbox) capability within an information system, system component, or location defined in SC-44, CCI 2564.'),
('002566','draft','2013-07-09','DISA FSO','policy','The organization defines personnel or roles to whom a documented media protection policy and procedures will be disseminated.','MP-1.3','DoD has defined the personnel or roles as all users.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all users.'),
('002567','draft','2013-07-09','DISA FSO','policy','The organization reviews and approves media sanitization.','MP-6(1).1','The organization being inspected/assessed documents and implements a process for reviewing and approving media sanitization. The process must include procedures for reviewing and approving sanitization actions. The organization must maintain a record of media sanitization actions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of media sanitization actions to ensure the organization being inspected/assessed reviews and approves media sanitization actions.'),
('002568','draft','2013-07-09','DISA FSO','policy','The organization tracks and documents media sanitization.','MP-6(1).2','The organization being inspected/assessed documents and implements a process for tracking media sanitization. The process must include procedures for tracking sanitization actions. The organization must maintain a record of media sanitization actions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of media sanitization actions to ensure the organization being inspected/assessed tracks and documents media sanitization actions.'),
('002569','draft','2013-07-09','DISA FSO','policy','The organization verifies media sanitization.','MP-6(1).3','The organization being inspected/assessed documents and implements a process for media sanitization. The process must include procedures for verification of sanitization actions. The organization must maintain a record of media sanitization actions including verification information.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of media sanitization actions to ensure the organization being inspected/assessed verifies media sanitization actions.'),
('002570','draft','2013-07-09','DISA FSO','policy','The organization reviews and approves media disposal actions.','MP-6(1).4','The organization being inspected/assessed documents and implements a process for reviewing and approving media disposal. The process must include procedures for reviewing and approving disposal actions. The organization must maintain a record of media disposal actions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of media disposal actions to ensure the organization being inspected/assessed reviews and approves media disposal actions.'),
('002571','draft','2013-07-09','DISA FSO','policy','The organization tracks and documents media disposal actions.','MP-6(1).5','The organization being inspected/assessed documents and implements a process for tracking media disposal. The process must include procedures for tracking disposal actions. The organization must maintain a record of media disposal actions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of media disposal actions to ensure the organization being inspected/assessed tracks and documents media disposal actions.'),
('002572','draft','2013-07-09','DISA FSO','policy','The organization verifies media disposal actions.','MP-6(1).6','The organization being inspected/assessed documents and implements a process for media disposal. The process must include procedures for verification of disposal actions. The organization must maintain a record of media disposal actions including verification information.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of media disposal actions to ensure the organization being inspected/assessed verifies media disposal actions.'),
('002573','draft','2013-07-09','DISA FSO','policy','The organization enforces dual authorization for the sanitization of organization-defined information system media.','MP-6(7).1','The organization being inspected/assessed documents and implements a process for dual authorization for the sanitization of information system media defined in MP-6 (7), CCI 2574. The organization must maintain a record of sanitization actions for media defined in MP-6 (7), CCI 2574.','The organization conducting the inspection/assessment obtains and examines the documented process as well as a sampling of records of sanitization actions to ensure the organization being inspected/assessed enforces dual authorization for the sanitization of information system media defined in MP-6 (7), CCI 2574.'),
('002574','draft','2013-07-09','DISA FSO','policy','The organization defines the information system media that dual authorization is enforced for sanitization.','MP-6(7).2','The organization being inspected/assessed defines and documents the information system media that dual authorization should be enforced for sanitization. DoD has determined the information system media is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system media to ensure the organization being inspected/assessed defines the information system media that dual authorization should be enforced for sanitization. DoD has determined the information system media is not appropriate to define at the Enterprise level.'),
('002575','draft','2013-07-09','DISA FSO','policy','The organization defines information systems, system components, or devices from which information is to be purged/wiped, either remotely or under the organization-defined conditions.','MP-6(8).1','The organization being inspected/assessed defines and documents information systems, system components, or devices that information should be purged/wiped either remotely or under the organization-defined conditions. DoD has determined the information systems, system components, or devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems, system components, or devices to ensure the organization being inspected/assessed defines information systems, system components, or devices that information should be purged/wiped either remotely or under the organization-defined conditions. DoD has determined the information systems, system components, or devices are not appropriate to define at the Enterprise level.'),
('002576','draft','2013-07-09','DISA FSO','policy','The organization defines conditions under which information from organization-defined information systems, system components, or devices should be purged/wiped.','MP-6(8).2','The organization being inspected/assessed defines and documents conditions in which information from organization-defined information systems, system components, or devices should be purged/wiped. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure the organization being inspected/assessed defines conditions in which information from organization-defined information systems, system components, or devices should be purged/wiped. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002577','draft','2013-07-09','DISA FSO','policy','The organization provides the capability to purge/wipe information from organization-defined information systems, system components, or devices either remotely or under organization-defined conditions.','MP-6(8).3','The organization being inspected/assessed documents and implements a process to purge /wipe information from information systems, system components, or devices defined in MP-6 (8), CCI 2575 either remotely or under conditions defined in MP-6 (8), CCI 2576.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides the capability to purge /wipe information from information systems, system components, or devices defined in MP-6 (8), CCI 2575 either remotely or under conditions defined in MP-6 (8), CCI 2576.'),
('002578','draft','2013-07-09','DISA FSO','policy','The organization defines information system media to sanitize prior to disposal, release out of organizational control, or release for reuse using organization-defined sanitization techniques and procedures in accordance with applicable federal and organizational standards and policies.','MP-6.2','DoD has defined the information system media as all media.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system media as all media.'),
('002579','draft','2013-07-09','DISA FSO','policy','The organization defines the sanitization techniques and procedures to be used to sanitize organization-defined information system media prior to disposal, release out of organizational control, or release for reuse in accordance with applicable federal and organization standards and policies.','MP-6.3','DoD has defined the sanitization techniques as techniques and procedures IAW NIST SP 800-88.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the sanitization techniques as techniques and procedures IAW NIST SP 800-88.'),
('002580','draft','2013-07-09','DISA FSO','policy','The organization employs sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information.','MP-6.4','The organization being inspected/assessed implements sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information. The organization must maintain an audit trail of sanitization actions.','The organization conducting the inspection/assessment obtains and examines the audit trail of sanitization actions to ensure the organization being inspected/assessed implements sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information.'),
('002581','draft','2013-07-09','DISA FSO','policy','The organization defines the types of information system media to restrict or prohibit on organization-defined information systems or system components using organization-defined security safeguards.','MP-7.1','The organization being inspected/assessed defines and documents the types of information system media to restrict or prohibit on organization-defined information systems or system components using organization-defined security safeguards. DoD has determined the types of information system media are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented type of information system media to ensure the organization being inspected/assessed defines the types of information system media to restrict or prohibit on organization-defined information systems or system components using organization-defined security safeguards. DoD has determined the types of information system media are not appropriate to define at the Enterprise level.'),
('002582','draft','2013-07-09','DISA FSO','policy','The organization defines the information systems or system components on which to restrict or prohibit the use of organization-defined types of information system media using organization-defined security safeguards.','MP-7.2','The organization being inspected/assessed defines and documents the information systems or system components to restrict or prohibit the use of organization-defined types of information system media using organization-defined security safeguards. DoD has determined the information systems or system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems or system components to ensure the organization being inspected/assessed defines the information systems or system components to restrict or prohibit the use of organization-defined types of information system media using organization-defined security safeguards. DoD has determined the information systems or system components are not appropriate to define at the Enterprise level.'),
('002583','draft','2013-07-09','DISA FSO','policy','The organization defines the security safeguards to use for restricting or prohibiting the use of organization-defined types of information system media on organization-defined information systems or system components.','MP-7.3','The organization being inspected/assessed defines and documents the security safeguards to use for restricting or prohibiting the use of organization-defined types of information system media on organization-defined information systems or system components. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to use for restricting or prohibiting the use of organization-defined types of information system media on organization-defined information systems or system components. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002584','draft','2013-07-09','DISA FSO','policy','The organization restricts or prohibits the use of organization-defined types of information system media on organization-defined information systems or system components using organization-defined security safeguards.','MP-7.4','The organization being inspected/assessed documents and enforces controls for the use of media defined in MP-7, CCI 2581 on systems defined in MP-7, CCI 2582 using security safeguards defined in MP-7, CCI 2583.','The organization conducting the inspection/assessment obtains and examines the documented controls and examines information system procedures associated with the use of media to ensure the organization being inspected/assessed documents and enforces controls for the use of media defined in MP-7, CCI 2581 on systems defined in MP-7, CCI 2582 using security safeguards defined in MP-7, CCI 2583.'),
('002585','draft','2013-07-09','DISA FSO','policy','The organization prohibits the use of portable storage devices in organizational information systems when such devices have no identifiable owner.','MP-7(1).1','The organization being inspected/assessed does not use portable storage devices in organization information systems when such devices have no identifiable owner.','The organization conducting the inspection/assessment examines a sampling of portable storage devices used in the information system to ensure that the devices have an identifiable owner.'),
('002586','draft','2013-07-09','DISA FSO','policy','The organization prohibits the use of sanitization-resistant media in organizational information systems.','MP-7(2).1','The organization being inspected/assessed does not use sanitization-resistant media in organizational information systems.','The organization conducting the inspection/assessment examines a sampling of media used in the information system to ensure sanitization-resistant media is not used.'),
('002587','draft','2013-07-09','DISA FSO','policy','The organization documents information system media downgrading actions.','MP-8(1).1','The organization being inspected/assessed documents information system media downgrading actions.','The organization conducting the inspection/assessment obtains and examines the documented information system media downgrading actions to ensure the organization being inspected/assessed documents information system media downgrading actions.'),
('002588','draft','2013-07-09','DISA FSO','policy','The organization employs organization-defined tests of downgrading equipment in accordance with organization-defined frequency.','MP-8(2).1','The organization being inspected/assessed implements tests defined in MP-8 (2), CCI 2590 at a minimum annually to verify correct performance of equipment. The organization must maintain a record of tests. DoD has defined the frequency as at a minimum annually.','The organization conducting the inspection/assessment obtains and examines the record of tests to ensure the organization being inspected/assessed implements tests defined in MP-8 (2), CCI 2590 at a minimum annually to verify correct performance of equipment. DoD has defined the frequency as at a minimum annually. '),
('002589','draft','2013-07-09','DISA FSO','policy','The organization employs procedures to verify correct performance of organization-defined tests of downgrading equipment in accordance with organization-defined frequency.','MP-8(2).2','The organization being inspected/assessed implements tests defined in MP-8 (2), CCI 2590 at a minimum annually to verify correct performance of procedures. The organization must maintain a record of tests. DoD has defined the frequency as at a minimum annually.','The organization conducting the inspection/assessment obtains and examines the record of tests to ensure the organization being inspected/assessed implements tests defined in MP-8 (2), CCI 2590 at a minimum annually to verify correct performance of procedures. DoD has defined the frequency as at a minimum annually. '),
('002590','draft','2013-07-09','DISA FSO','policy','The organization defines tests to employ for downgrading equipment.','MP-8(2).3','The organization being inspected/assessed defines and documents tests to employ for downgrading equipment. DoD has determined the tests are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented tests to ensure the organization being inspected/assessed defines tests to employ for downgrading equipment. DoD has determined the tests are not appropriate to define at the Enterprise level.'),
('002591','draft','2013-07-09','DISA FSO','policy','The organization defines the frequency with which to employ tests of downgrading equipment and procedures to verify correct performance.','MP-8(2).4','DoD has defined the frequency as at a minimum annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at a minimum annually.'),
('002592','draft','2013-07-09','DISA FSO','policy','The organization defines Controlled Unclassified Information (CUI).','MP-8(3).1','DoD has defined the Controlled Unclassified Information (CUI) as any Controlled Unclassified Information (CUI).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the Controlled Unclassified Information (CUI) as any Controlled Unclassified Information (CUI).'),
('002593','draft','2013-07-09','DISA FSO','policy','The organization downgrades information system media containing organization-defined Controlled Unclassified Information (CUI) prior to public release in accordance with applicable federal and organizational standards and policies.','MP-8(3).2','The organization being inspected/assessed implements a process to downgrade information system media containing any Controlled Unclassified Information (CUI) prior to public release in accordance with applicable federal and organizational standards and policies. The organization must maintain a record of public release of media and a record of information system media downgrade. DoD has defined the Controlled Unclassified Information (CUI) as any Controlled Unclassified Information (CUI).','The organization conducting the inspection/assessment obtains and examines the record of public release of media as well as records of information system media downgrade to ensure the organization being inspected/assessed implements a process to downgrade information system media containing any Controlled Unclassified Information (CUI) prior to public release in accordance with applicable federal and organizational standards and policies. DoD has defined the Controlled Unclassified Information (CUI) as any Controlled Unclassified Information (CUI).'),
('002594','draft','2013-07-09','DISA FSO','policy','The organization downgrades information system media containing classified information prior to release to individuals without required access authorizations in accordance with NSA standards and policies.','MP-8(4).1','The organization being inspected/assessed implements a process to downgrade information system media containing classified information prior to release to individuals without required access authorizations in accordance with NSA standards and policies. The organization must maintain a record of release of media containing classified information and a record of information system media downgrade.','The organization conducting the inspection/assessment obtains and examines the record of release of media containing classified information as well as records of information system media downgrade to ensure the organization being inspected/assessed implements a process to downgrade information system media containing classified information prior to release to individuals without required access authorizations in accordance with NSA standards and policies.'),
('002595','deprecated','2013-07-09','DISA FSO','policy','The organization establishes an organization-defined information system media downgrading process that includes employing downgrading mechanisms with organization-defined strength and integrity.',NULL,NULL,NULL),
('002596','draft','2013-07-09','DISA FSO','policy','The organization establishes and defines an information system media downgrading process that includes employing downgrading mechanisms with organization-defined strength and integrity.','MP-8.1','The organization being inspected/assessed defines and documents an information system media downgrading process that includes employing downgrading mechanisms with organization-defined strength and integrity. DoD has determined the information system media downgrading process is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system media downgrading process to ensure the organization being inspected/assessed defines an information system media downgrading process that includes employing downgrading mechanisms with organization-defined strength and integrity. DoD has determined the information system media downgrading process is not appropriate to define at the Enterprise level.'),
('002597','draft','2013-07-09','DISA FSO','policy','The organization defines strength and integrity for downgrading mechanisms to establish an organization-defined information system media downgrading process.','MP-8.2','The organization being inspected/assessed defines and documents strength and integrity for downgrading mechanisms to establish an organization-defined information system media downgrading process. DoD has determined the strength and integrity are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented strength and integrity to ensure the organization being inspected/assessed defines strength and integrity for downgrading mechanisms to establish an organization-defined information system media downgrading process. DoD has determined the strength and integrity are not appropriate to define at the Enterprise level.'),
('002598','draft','2013-07-09','DISA FSO','policy','The organization ensures that the information system media downgrading process is commensurate with the security category and/or classification level of the information to be removed and the access authorizations of the potential recipients of the downgraded information.','MP-8.3','The organization being inspected/assessed includes within the process defined in MP-8, CCI 2596, processes which are commensurate with the security category and/or classification level of the information to be removed and the access authorizations of the potential recipients of the downgraded information.','The organization conducting the inspection/assessment obtains and examines the documented process defined in MP-8, CCI 2596 to ensure it is commensurate with the security category and/or classification level of the information to be removed and the access authorizations of the potential recipients of the downgraded information.'),
('002599','draft','2013-07-09','DISA FSO','policy','The organization defines and identifies the information system media requiring downgrading.','MP-8.4','The organization being inspected/assessed defines, identifies, and documents the information system media requiring downgrading. DoD has determined the information system media is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system media to ensure the organization being inspected/assessed defines and identifies the information system media requiring downgrading. DoD has determined the information system media is not appropriate to define at the Enterprise level.'),
('002600','draft','2013-07-09','DISA FSO','policy','The organization downgrades the identified information system media using the established process.','MP-8.5','The organization being inspected/assessed implements the process defined in MP-8, CCI 2596 to downgrade media defined in MP-8, CCI 2599. The organization must maintain a record of downgrade activities.','The organization conducting the inspection/assessment obtains and examines the record of downgrade activities to ensure the organization being inspected/assessed implements the process defined in MP-8, CCI 2596 to downgrade media defined in MP-8, CCI 2599.'),
('002601','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles to whom the system and information integrity policy and procedures are to be disseminated.','SI-1.1','DoD has defined the personnel or roles as all appointed information assurance personnel.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the personnel or roles as all appointed information assurance personnel.'),
('002602','draft','2013-07-11','DISA FSO','policy','The organization tests firmware updates related to flaw remediation for effectiveness before installation.','SI-2.6','The organization being inspected/assessed documents and implements a process to test firmware updates related to flaw remediation for effectiveness before installation. If the firmware update is being provided by a vendor who has documented the effectiveness of the update in fixing the affected IAVM/CVE, further testing by the organization may not be required.','The organization conducting the inspection/assessment obtains and examines the documented process and test results to ensure the organization being inspected/assessed tests firmware updates related to flaw remediation for effectiveness before installation.'),
('002603','draft','2013-07-11','DISA FSO','policy','The organization tests firmware updates related to flaw remediation for potential side effects before installation.','SI-2.7','The organization being inspected/assessed documents and implements a process for regression testing IAW CM-4 to identify any potential side effects before installation of software updates.','The organization conducting the inspection/assessment obtains and examines the documented process and test results to ensure the organization being inspected/assessed tests firmware updates related to flaw remediation for potential side effects before installation.'),
('002604','draft','2013-07-11','DISA FSO','policy','The organization defines the time period following the release of updates within which security-related software updates are to be installed.','SI-2.8','DoD has defined the time period as 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the time period as 30 days'),
('002605','draft','2013-07-11','DISA FSO','technical','The organization installs security-relevant software updates within an organization-defined time period of the release of the updates.','SI-2.9','The organization being inspected/assessed configures the information system to install security-relevant software updates within 30 days of the release of the updates\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2605.\nDoD has defined the time period as 30 days.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to install security-relevant software updates within 30 days of the release of the updates.\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2605.\nDoD has defined the time period as 30 days.'),
('002606','draft','2013-07-11','DISA FSO','policy','The organization defines the time period following the release of updates within which security-related firmware updates are to be installed.','SI-2.10','DoD has defined the time period as 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the time period as 30 days'),
('002607','draft','2013-07-11','DISA FSO','technical','The organization installs security-relevant firmware updates within an organization-defined time period of the release of the updates.','SI-2.11','The organization being inspected/assessed configures the information system to install security-relevant firmware updates within 30 days of the release of the updates.\n\nFor information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2607.\n\nDoD has defined the time period as 30 days.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to install security-relevant firmware updates within 30 days of the release of the updates.\n\nFor information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2607.\n\nDoD has defined the time period as 30 days.'),
('002608','draft','2013-07-11','DISA FSO','policy','The organization establishes organization-defined benchmarks for the time taken to apply corrective actions after flaw identification.','SI-2(3).3','The organization being inspected/assessed implements benchmarks for the time taken to apply corrective actions after flaw identification IAW the period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).\n\nDoD has defined the benchmarks as within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).','The organization conducting the inspection/assessment obtains and examines records of corrective actions taken to ensure the organization being inspected/assessed implements benchmarks for the time taken to apply corrective actions after flaw identification IAW the period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).\n\nDoD has defined the benchmarks as within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, STIGs).'),
('002609','draft','2013-07-11','DISA FSO','policy','The organization defines the information system components on which organization-defined security-relevant software updates will be automatically installed.','SI-2(5).1','The organization being inspected/assessed defines and documents the information system components on which organization-defined security-relevant software updates will be automatically installed. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components on which organization-defined security-relevant software updates will be automatically installed. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002610','draft','2013-07-11','DISA FSO','policy','The organization defines the information system components on which organization-defined security-relevant firmware updates will be automatically installed.','SI-2(5).2','The organization being inspected/assessed defines and documents the information system components on which organization-defined security-relevant firmware updates will be automatically installed. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components on which organization-defined security-relevant firmware updates will be automatically installed. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002611','draft','2013-07-11','DISA FSO','policy','The organization defines the security-relevant software updates to be automatically installed on organization-defined information system components.','SI-2(5).3','The organization being inspected/assessed defines and documents the security-relevant software updates to be automatically installed on organization-defined information system components. DoD has determined the security-relevant software updates are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security-relevant software updates to ensure the organization being inspected/assessed defines the security-relevant software updates to be automatically installed on organization-defined information system components. DoD has determined the security-relevant software updates are not appropriate to define at the Enterprise level.'),
('002612','draft','2013-07-11','DISA FSO','policy','The organization defines the security-relevant firmware updates to be automatically installed on organization-defined information system components.','SI-2(5).4','The organization being inspected/assessed defines and documents the security-relevant firmware updates to be automatically installed on organization-defined information system components. DoD has determined the security-relevant firmware updates are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security-relevant firmware updates to ensure the organization being inspected/assessed defines the security-relevant firmware updates to be automatically installed on organization-defined information system components. DoD has determined the security-relevant firmware updates are not appropriate to define at the Enterprise level.'),
('002613','draft','2013-07-11','DISA FSO','technical','The organization installs organization-defined security-relevant software updates automatically to organization-defined information system components.','SI-2(5).5','The organization being inspected/assessed configures the information system to install security-relevant software updates defined in SI-2 (5), CCI 2611 automatically to information system components defined in SI-2 (5), CCI 2609. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2613.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to install security-relevant software updates defined in SI-2 (5), CCI 2611 automatically to information system components defined in SI-2 (5), CCI 2609. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2613.'),
('002614','draft','2013-07-11','DISA FSO','technical','The organization installs organization-defined security-relevant firmware updates automatically to organization-defined information system components.','SI-2(5).6','The organization being inspected/assessed configures the information system to install security-relevant firmware updates defined in SI-2 (5), CCI 2612 automatically to information system components defined in SI-2 (5), CCI 2610. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2614.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to install security-relevant firmware updates defined in SI-2 (5), CCI 2612 automatically to information system components defined in SI-2 (5), CCI 2610. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2614.'),
('002615','draft','2013-07-11','DISA FSO','policy','The organization defines the software components to be removed (e.g., previous versions) after updated versions have been installed.','SI-2(6).1','DoD has defined the software components as all upgraded/replaced software components that are no longer required for operation.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the software components as all upgraded/replaced software components that are no longer required for operation.'),
('002616','draft','2013-07-11','DISA FSO','policy','The organization defines the firmware components to be removed (e.g., previous versions) after updated versions have been installed.','SI-2(6).2','DoD has defined the firmware components as all upgraded/replaced firmware components that are no longer required for operation.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the firmware components as all upgraded/replaced firmware components that are no longer required for operation.'),
('002617','draft','2013-07-11','DISA FSO','technical','The organization removes organization-defined software components (e.g., previous versions) after updated versions have been installed.','SI-2(6).3','The organization being inspected/assessed configures the information system to remove all upgraded/replaced software components that are no longer required for operation (e.g., previous versions) after updated versions have been installed. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2617. DoD has defined the software components as all upgraded/replaced software components that are no longer required for operation.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to remove all upgraded/replaced software components that are no longer required for operation (e.g., previous versions) after updated versions have been installed. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2617. DoD has defined the software components as all upgraded/replaced software components that are no longer required for operation.'),
('002618','draft','2013-07-11','DISA FSO','technical','The organization removes organization-defined firmware components (e.g., previous versions) after updated versions have been installed.','SI-2(6).4','The organization being inspected/assessed configures the information system to remove all upgraded/replaced firmware components that are no longer required for operation e.g., previous versions) after updated versions have been installed. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2618. DoD has defined the firmware components as all upgraded/replaced firmware components that are no longer required for operation.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to remove all upgraded/replaced firmware components that are no longer required for operation (e.g., previous versions) after updated versions have been installed. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2618. DoD has defined the firmware components as all upgraded/replaced firmware components that are no longer required for operation.'),
('002619','draft','2013-07-11','DISA FSO','policy','The organization employs malicious code protection mechanisms at information system entry points to detect malicious code.','SI-3.1','The organization being inspected/assessed identifies and documents the information system entry points and implements malicious code protection mechanisms at those entry points to detect malicious code. Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies.','The organization conducting the inspection/assessment examines the information system architecture as well as the organization\'s documentation of information system entry points and verifies that malicious code protection mechanisms are implemented.'),
('002620','draft','2013-07-11','DISA FSO','policy','The organization employs malicious code protection mechanisms at information system exit points to detect malicious code.','SI-3.2','The organization being inspected/assessed identifies and documents the information system exit points and implements malicious code protection mechanisms at those exit points to detect malicious code. Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies.','The organization conducting the inspection/assessment examines the information system architecture as well as the organization\'s documentation of information system exit points and verifies that malicious code protection mechanisms are implemented.'),
('002621','draft','2013-07-11','DISA FSO','policy','The organization employs malicious code protection mechanisms at information system entry points to eradicate malicious code.','SI-3.3','The organization being inspected/assessed configures the malicious code protection mechanisms identified in SI-3, CCI 2619 to eradicate malicious code.','The organization conducting the inspection/assessment examines the information system architecture as well as the organization\'s documentation of information system entry points and verifies that malicious code protection mechanisms are implemented to eradicate malicious code.'),
('002622','draft','2013-07-11','DISA FSO','policy','The organization employs malicious code protection mechanisms at information system exit points to eradicate malicious code.','SI-3.4','The organization being inspected/assessed configures the malicious code protection mechanisms identified in SI-3, CCI 2620 to eradicate malicious code.','The organization conducting the inspection/assessment examines the information system architecture as well as the organization\'s documentation of information system exit points and verifies that malicious code protection mechanisms are implemented to eradicate malicious code.'),
('002623','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency for performing periodic scans of the information system for malicious code.','SI-3.6','DoD has defined the frequency as every 7 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as every 7 days.'),
('002624','draft','2013-07-11','DISA FSO','policy','The organization configures malicious code protection mechanisms to perform real-time scans of files from external sources at network entry/exit points as the files are downloaded, opened, or executed in accordance with organizational security policy.','SI-3.7','The organization being inspected/assessed configures the malicious code protection mechanisms to perform real-time scans of files from external sources at network entry/exit points as the files are downloaded, opened, or executed in accordance with organizational security policy. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2624.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures malicious code protection mechanisms to perform real-time scans of files from external sources at network entry/exit points as the files are downloaded, opened, or executed in accordance with organizational security policy. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2624.'),
('002625','draft','2013-07-11','DISA FSO','policy','The organization, when testing malicious code protection mechanisms, verifies the detection of the test case occurs.','SI-3(6).3','The organization being inspected/assessed verifies the detection of the test case occurs when testing malicious code protection mechanisms. The organization must maintain an audit trail of test cases and successful or failed detection.','The organization conducting the inspection/assessment obtains and examines the audit trail of test cases and successful or failed detection to ensure the organization being inspected/assessed verifies the detection of the test case occurs when testing malicious code protection mechanisms.'),
('002626','draft','2013-07-11','DISA FSO','policy','The organization, when testing malicious code protection mechanisms, verifies the incident reporting of the test case occurs.','SI-3(6).4','The organization being inspected/assessed verifies the incident reporting of the test case occurs when testing malicious code protection mechanisms. The organization must maintain an audit trail of test cases and success or failure.','The organization conducting the inspection/assessment obtains and examines the audit trail of test cases and success or failure to ensure the organization being inspected/assessed verifies the incident reporting of the test case occurs when testing malicious code protection mechanisms.'),
('002627','draft','2013-07-11','DISA FSO','technical','The information system implements nonsignature-based malicious code detection mechanisms.','SI-3(7).1','The organization being inspected/assessed configures the information system to implement nonsignature-based malicious code detection mechanisms. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2627. Nonsignature-based detection mechanisms include, for example, the use of heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide safeguards against malicious code for which signatures do not yet exist or for which existing signatures may not be effective.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement nonsignature-based malicious code detection mechanisms. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2627.'),
('002628','draft','2013-07-11','DISA FSO','policy','The organization defines the unauthorized operating system commands that are to be detected through the kernel application programming interface by organization-defined information system hardware components.','SI-3(8).1','The organization being inspected/assessed defines and documents the unauthorized operating system commands that are to be detected through the kernel application programming interface by organization-defined information system hardware components. DoD has determined the unauthorized operating system commands are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented unauthorized operating system commands to ensure the organization being inspected/assessed defines the unauthorized operating system commands that are to be detected through the kernel application programming interface by organization-defined information system hardware components. DoD has determined the unauthorized operating system commands are not appropriate to define at the Enterprise level.'),
('002629','draft','2013-07-11','DISA FSO','policy','The organization defines the information system hardware components that are to detect organization-defined unauthorized operating system commands through the kernel programming application interface.','SI-3(8).2','The organization being inspected/assessed defines and documents the information system hardware components that are to detect organization-defined unauthorized operating system commands through the kernel application interface. DoD has determined the information system hardware components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system hardware components to ensure the organization being inspected/assessed defines the information system hardware components that are to detect organization-defined unauthorized operating system commands through the kernel application interface. DoD has determined the information system hardware components are not appropriate to define at the Enterprise level.'),
('002630','draft','2013-07-11','DISA FSO','technical','The information system detects organization-defined unauthorized operating system commands through the kernel application programming interface at organization-defined information system hardware components.','SI-3(8).3','The organization being inspected/assessed configures the information system to detect unauthorized operating system commands defined in SI-3 (8), CCI 2628 through the kernel application programming interface at information system hardware components defined in SI-3 (8), CCI 2629. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2630.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to detect unauthorized operating system commands defined in SI-3 (8), CCI 2628 through the kernel application programming interface at information system hardware components defined in SI-3 (8), CCI 2629. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2630.'),
('002631','draft','2013-07-11','DISA FSO','technical','The information system issues a warning, audits the command execution, or prevents the execution of the command when organization-defined unauthorized operating system commands are detected.','SI-3(8).4','The organization being inspected/assessed configures the information system to issue a warning, audits the command execution, or prevents the execution of the command when unauthorized operating system commands defined in SI-3 (8), CCI 2628 are detected. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2631.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to issue a warning, audits the command execution, or prevents the execution of the command when unauthorized operating system commands defined in SI-3 (8), CCI 2628 are detected. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2631.'),
('002632','draft','2013-07-11','DISA FSO','policy','The organization defines the remote commands that are to be authenticated using organization-defined safeguards for malicious code protection.','SI-3(9).1','The organization being inspected/assessed defines and documents the remote commands that are to be authenticated using organization-defined safeguards for malicious code protection. DoD has determined the remote commands are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented remote commands to ensure the organization being inspected/assessed defines the remote commands that are to be authenticated using organization-defined safeguards for malicious code protection. DoD has determined the remote commands are not appropriate to define at the Enterprise level.'),
('002633','draft','2013-07-11','DISA FSO','policy','The organization defines the security safeguards to be implemented to authenticate organization-defined remote commands for malicious code protection.','SI-3(9).2','The organization being inspected/assessed defines and documents the security safeguards to be implemented to authenticate organization-defined remote commands for malicious code protection. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be implemented to authenticate organization-defined remote commands for malicious code protection. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002634','draft','2013-07-11','DISA FSO','policy','The organization defines the tools to be employed to analyze the characteristics and behavior of malicious code.','SI-3(10).1','The organization being inspected/assessed defines and documents the tools to be employed to analyze the characteristics and behavior of malicious code. DoD has determined the tools are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented tools to ensure the organization being inspected/assessed defines the tools to be employed to analyze the characteristics and behavior of malicious code. DoD has determined the tools are not appropriate to define at the Enterprise level.'),
('002635','draft','2013-07-11','DISA FSO','policy','The organization defines the techniques to be employed to analyze the characteristics and behavior of malicious code.','SI-3(10).2','The organization being inspected/assessed defines and documents the techniques to be employed to analyze the characteristics and behavior of malicious code. DoD has determined the techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques to ensure the organization being inspected/assessed defines the techniques to be employed to analyze the characteristics and behavior of malicious code. DoD has determined the techniques are not appropriate to define at the Enterprise level.'),
('002636','draft','2013-07-11','DISA FSO','policy','The organization employs organization-defined tools to analyze the characteristics and behavior of malicious code.','SI-3(10).3','The organization being inspected/assessed documents and implements tools defined in SI-3 (10), CCI 2634 to analyze the characteristics and behavior of malicious code.','The organization conducting the inspection/assessment obtains and examines the documented tools to ensure the organization being inspected/assessed employs tools defined in SI-3 (10), CCI 2634 to analyze the characteristics and behavior of malicious code.'),
('002637','draft','2013-07-11','DISA FSO','technical','The information system implements organization-defined security safeguards to authenticate organization-defined remote commands for malicious code protection.','SI-3(9).3','The organization being inspected/assessed configures the information system to implement security safeguards defined in SI-3 (9), CCI 2633 to authenticate remote commands for malicious code protection defined in SI-3 (9), CCI 2632. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2637.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement security safeguards defined in SI-3 (9), CCI 2633 to authenticate remote commands for malicious code protection defined in SI-3 (9), CCI 2632. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2637.'),
('002638','draft','2013-07-11','DISA FSO','policy','The organization employs organization-defined techniques to analyze the characteristics and behavior of malicious code.','SI-3(10).4','The organization being inspected/assessed documents and implements techniques defined in SI-3 (10), CCI 2635 to analyze the characteristics and behavior of malicious code.','The organization conducting the inspection/assessment obtains and examines the documented techniques to ensure the organization being inspected/assessed employs techniques defined in SI-3 (10), CCI 2635 to analyze the characteristics and behavior of malicious code.'),
('002639','draft','2013-07-11','DISA FSO','policy','The organization incorporates the results from malicious code analysis into organizational incident response processes.','SI-3(10).5','The organization being inspected/assessed incorporates the results from malicious code analysis into organizational incident response processes.','The organization conducting the inspection/assessment obtains and examines the organizational incident response processes to ensure the organization being inspected/assessed incorporates the results from malicious code analysis into organizational incident response processes.'),
('002640','draft','2013-07-11','DISA FSO','policy','The organization incorporates the results from malicious code analysis into organizational flaw remediation processes.','SI-3(10).6','The organization being inspected/assessed incorporates the results from malicious code analysis into organizational flaw remediation processes.','The organization conducting the inspection/assessment obtains and examines the flaw remediation processes to ensure the organization being inspected/assessed incorporates the results from malicious code analysis into organizational flaw remediation processes.'),
('002641','draft','2013-07-11','DISA FSO','policy','The organization monitors the information system to detect attacks and indicators of potential attacks in accordance with organization-defined monitoring objectives.','SI-4.2','The organization being inspected/assessed documents and implements a process to monitor the information system to detect attacks and indicators of potential attacks in accordance with sensor placement and monitoring requirements within CJCSI 6510.01F. The organization must maintain an audit trail of monitoring. DoD has defined the monitoring objectives as sensor placement and monitoring requirements within CJCSI 6510.01F.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring to ensure the organization being inspected/assessed monitors the information system to detect attacks and indicators of potential attacks in accordance with sensor placement and monitoring requirements within CJCSI 6510.01F.'),
('002642','draft','2013-07-11','DISA FSO','policy','The organization monitors the information system to detect unauthorized local connections.','SI-4.3','The organization being inspected/assessed documents and implements a process to monitor the information system to detect unauthorized local connections. The organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring to ensure the organization being inspected/assessed monitors the information system to detect unauthorized local connections.'),
('002643','draft','2013-07-11','DISA FSO','policy','The organization monitors the information system to detect unauthorized network connections.','SI-4.4','The organization being inspected/assessed documents and implements a process to monitor the information system to detect unauthorized network connections. The organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring to ensure the organization being inspected/assessed monitors the information system to detect unauthorized network connections.'),
('002644','draft','2013-07-11','DISA FSO','policy','The organization monitors the information system to detect unauthorized remote connections.','SI-4.5','The organization being inspected/assessed documents and implements a process to monitor information system to detect unauthorized remote connections. The organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring to ensure the organization being inspected/assessed monitors the information system to detect unauthorized remote connections.'),
('002645','draft','2013-07-11','DISA FSO','policy','The organization defines the techniques and methods to be used to identify unauthorized use of the information system.','SI-4.6','The organization being inspected/assessed defines and documents the techniques and methods to be used to identify unauthorized use of the information system. DoD has determined the techniques and methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented techniques to ensure the organization being inspected/assessed defines the techniques and methods to be used to identify unauthorized use of the information system. DoD has determined the techniques and methods are not appropriate to define at the Enterprise level.'),
('002646','draft','2013-07-11','DISA FSO','policy','The organization identifies unauthorized use of the information system through organization-defined techniques and methods.','SI-4.7','The organization being inspected/assessed identifies unauthorized use of the information system through techniques and methods defined in SI-4, CCI 2645. The organization must maintain an audit trail of identified instances of unauthorized use.','The organization conducting the inspection/assessment obtains and examines the audit trail of identified instances of unauthorized use to ensure the organization being inspected/assessed identifies unauthorized use of the information system through techniques and methods defined in SI-4, CCI 2645.'),
('002647','draft','2013-07-11','DISA FSO','policy','The organization protects information obtained from intrusion-monitoring tools from unauthorized access.','SI-4.10','The organization being inspected/assessed documents and implements a process to protect information obtained from intrusion-monitoring tools from unauthorized access.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed protects information obtained from intrusion-monitoring tools from unauthorized access.'),
('002648','draft','2013-07-11','DISA FSO','policy','The organization protects information obtained from intrusion-monitoring tools from unauthorized modification.','SI-4.11','The organization being inspected/assessed documents and implements a process to protect information obtained from intrusion-monitoring tools from unauthorized modification.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed protects information obtained from intrusion-monitoring tools from unauthorized modification.'),
('002649','draft','2013-07-11','DISA FSO','policy','The organization protects information obtained from intrusion-monitoring tools from unauthorized deletion.','SI-4.12','The organization being inspected/assessed documents and implements a process to protect information obtained from intrusion-monitoring tools from unauthorized deletion.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed protects information obtained from intrusion-monitoring tools from unauthorized deletion.'),
('002650','draft','2013-07-11','DISA FSO','policy','The organization defines the information system monitoring information that is to be provided the organization-defined personnel or roles.','SI-4.15','The organization being inspected/assessed defines and documents the information system monitoring information that is to be provided the organization-defined personnel or roles. DoD has determined the information system monitoring information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system monitoring information to ensure the organization being inspected/assessed defines the information system monitoring information that is to be provided the organization-defined personnel or roles. DoD has determined the information system monitoring information is not appropriate to define at the Enterprise level.'),
('002651','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles that are to be provided organization-defined information system monitoring information.','SI-4.16','The organization being inspected/assessed defines and documents the personnel or roles that are to be provided organization-defined information system monitoring information. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles that are to be provided organization-defined information system monitoring information. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002652','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency at which the organization will provide the organization-defined information system monitoring information to organization-defined personnel or roles.','SI-4.17','The organization being inspected/assessed defines and documents the frequency at which the organization will provide the organization-defined information system monitoring information to organization-defined personnel or roles DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency at which the organization will provide the organization-defined information system monitoring information to organization-defined personnel or roles. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('002653','deprecated','2013-07-11','DISA FSO','policy','The organization provides organization-defined information system monitoring information to organization-defined personnel or roles as needed or per organization-defined frequency.',NULL,NULL,NULL),
('002654','draft','2013-07-11','DISA FSO','policy','The organization provides organization-defined information system monitoring information to organization-defined personnel or roles as needed or per organization-defined frequency.','SI-4.18','The organization being inspected/assessed provides information system monitoring information defined in SI-4, CCI 2650 to personnel or roles defined in SI-4, CCI 2651 as needed or per the frequency defined in SI-4, CCI 2652. The organization must maintain an audit trail of when information is provided.','The organization conducting the inspection/assessment obtains and examines the audit trail of when information is provided to ensure the organization being inspected/assessed provides information system monitoring information defined in SI-4, CCI 2650 to personnel or roles defined in SI-4, CCI 2651 as needed or per the frequency defined in SI-4, CCI 2652.'),
('002655','draft','2013-07-11','DISA FSO','policy','The organization connects individual intrusion detection tools into an information system-wide intrusion detection system.','SI-4(1).1','The organization being inspected/assessed connects individual intrusion detection tools into an information system-wide intrusion detection system.','The organization conducting the inspection/assessment examines the information system-wide intrusion detection system architecture and individuals tools to ensure the organization being inspected/assessed connects individual intrusion detection tools into an information system-wide intrusion detection system.'),
('002656','draft','2013-07-11','DISA FSO','technical','The organization configures individual intrusion detection tools into an information system-wide intrusion detection system.','SI-4(1).2','The organization being inspected/assessed configures individual intrusion detection tools into an information system-wide intrusion detection system. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2656.','The organization conducting the inspection/assessment examines the information system-wide intrusion detection system to ensure the organization being inspected/assessed configures individual intrusion detection tools into an information system-wide intrusion detection system. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2656.'),
('002657','draft','2013-07-11','DISA FSO','policy','The organization employs automated tools to integrate intrusion detection tools into access control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination.','SI-4(3).1','The organization being inspected/assessed documents and implements automated tools to integrate intrusion detection tools into access control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated tools to ensure the organization being inspected/assessed employs automated tools to integrate intrusion detection tools into access control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination. The organization being inspected/assessed may be required to demonstrate use of their automated tools.'),
('002658','draft','2013-07-11','DISA FSO','policy','The organization employs automated tools to integrate intrusion detection tools into flow control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination.','SI-4(3).2','The organization being inspected/assessed documents and implements automated tools to integrate intrusion detection tools into flow control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination.','The organization conducting the inspection/assessment obtains and examines documentation of the use of the identified automated tools to ensure the organization being inspected/assessed employs automated tools to integrate intrusion detection tools into flow control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination. The organization being inspected/assessed may be required to demonstrate use of their automated tools.'),
('002659','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency on which it will monitor inbound communications for unusual or unauthorized activities or conditions.','SI-4(4).1','DoD has defined the frequency as continuously.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as continuously.'),
('002660','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency on which it will monitor outbound communications for unusual or unauthorized activities or conditions.','SI-4(4).2','DoD has defined the frequency as continuously.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as continuously.'),
('002661','draft','2013-07-11','DISA FSO','technical','The information system monitors inbound communications traffic per organization-defined frequency for unusual or unauthorized activities or conditions.','SI-4(4).3','The organization being inspected/assessed configures the information system to monitor inbound communications traffic continuously for unusual or unauthorized activities or conditions. DoD has defined the frequency as continuously.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to monitor inbound communications traffic continuously for unusual or unauthorized activities or conditions. DoD has defined the frequency as continuously.'),
('002662','draft','2013-07-11','DISA FSO','technical','The information system monitors outbound communications traffic per organization-defined frequency for unusual or unauthorized activities or conditions.','SI-4(4).4','The organization being inspected/assessed configures the information system to monitor outbound communications traffic continuously for unusual or unauthorized activities or conditions. DoD has defined the frequency as continuously.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to monitor outbound communications traffic continuously for unusual or unauthorized activities or conditions. DoD has defined the frequency as continuously.'),
('002663','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles to receive information system alerts when organization-defined indicators of compromise or potential compromise occur.','SI-4(5).2','DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO. '),
('002664','draft','2013-07-11','DISA FSO','technical','The information system alerts organization-defined personnel or roles when organization-defined compromise indicators reflect the occurrence of a compromise or a potential compromise.','SI-4(5).3','The organization being inspected/assessed configures the information system to alert at a minimum, the ISSM and ISSO when real time intrusion detection and when there are threats identified by authoritative sources (e.g. CTOs) and IAW incident categories I, II, IV, & VII within CJCSM 6510.01B reflect the occurrence of a compromise or a potential compromise. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2664. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO. DoD has defined the compromise indicators as real time intrusion detection and when there are threats identified by authoritative sources (e.g. CTOs) and IAW incident categories I, II, IV, & VII within CJCSM 6510.01B.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to alert at a minimum, the ISSM and ISSO when real time intrusion detection and when there are threats identified by authoritative sources (e.g. CTOs) and IAW incident categories I, II, IV, & VII within CJCSM 6510.01B reflect the occurrence of a compromise or a potential compromise. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2664. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO. DoD has defined the compromise indicators as real time intrusion detection and when there are threats identified by authoritative sources (e.g. CTOs) and IAW incident categories I, II, IV, & VII within CJCSM 6510.01B.'),
('002665','draft','2013-07-11','DISA FSO','policy','The organization defines the encrypted communications traffic that is to be visible to organization-defined information system monitoring tools.','SI-4(10).1','The organization being inspected/assessed defines and documents the encrypted communications traffic that are to be visible to organization-defined information system monitoring tools. DoD has determined the encrypted traffic is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented encrypted traffic to ensure the organization being inspected/assessed defines the encrypted communications traffic that are to be visible to organization-defined information system monitoring tools. DoD has determined the encrypted traffic is not appropriate to define at the Enterprise level.'),
('002666','draft','2013-07-11','DISA FSO','policy','The organization defines the information system monitoring tools that will have visibility into organization-defined encrypted communications traffic.','SI-4(10).2','The organization being inspected/assessed defines and documents the information system monitoring tools that will have visibility into organization-defined encrypted communications traffic. DoD has determined the information system monitoring tools are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system monitoring tools to ensure the organization being inspected/assessed defines the information system monitoring tools that will have visibility into organization-defined encrypted communications traffic. DoD has determined the information system monitoring tools are not appropriate to define at the Enterprise level.'),
('002667','draft','2013-07-11','DISA FSO','policy','The organization makes provisions so that organization-defined encrypted communications traffic is visible to organization-defined information system monitoring tools.','SI-4(10).3','The organization being inspected/assessed makes provisions so that encrypted communications traffic defined in SI-4 (10), CCI 2665 is visible to information system monitoring tools defined in SI-4 (10), CCI 2666.','The organization conducting the inspection/assessment examines the information system architecture to verify that the encrypted communications traffic is visible to information system monitoring tools defined in SI-4 (10), CCI 2666.'),
('002668','draft','2013-07-11','DISA FSO','policy','The organization defines the interior points within the information system (e.g., subnetworks, subsystems) where outbound communications will be analyzed to discover anomalies.','SI-4(11).3','The organization being inspected/assessed defines and documents the interior points within the information system (e.g., subnetworks, subsystems) where outbound communications will be analyzed to discover anomalies. DoD has determined the interior points are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented interior points to ensure the organization being inspected/assessed defines the interior points within the information system (e.g., subnetworks, subsystems) where outbound communications will be analyzed to discover anomalies. DoD has determined the interior points are not appropriate to define at the Enterprise level.'),
('002669','draft','2013-07-11','DISA FSO','policy','The organization uses the traffic/event profiles in tuning system-monitoring devices to reduce the number of false positives and false negatives.','SI-4(13).3','The organization being inspected/assessed documents and implements a process to use the traffic/event profiles in tuning system-monitoring devices to reduce the number of false positives and false negatives. The organization must maintain an audit log of tuning events.','The organization conducting the inspection/assessment obtains and examines the documented process as well as audit logs of tuning events to ensure the organization being inspected/assessed uses the traffic/event profiles in tuning system-monitoring devices to reduce the number of false positives and false negatives.'),
('002670','draft','2013-07-11','DISA FSO','policy','The organization defines the interior points within the system (e.g., subsystems, subnetworks) where outbound communications will be analyzed to detect covert exfiltration of information.','SI-4(18).1','The organization being inspected/assessed defines and documents the interior points within the system (e.g., subsystems, subnetworks) where outbound communications will be analyzed to detect covert exfiltration of information. DoD has determined the interior points are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented interior points to ensure the organization being inspected/assessed defines the interior points within the system (e.g., subsystems, subnetworks) where outbound communications will be analyzed to detect covert exfiltration of information. DoD has determined the interior points are not appropriate to define at the Enterprise level.'),
('002671','draft','2013-07-11','','policy','The organization analyzes outbound communications traffic at the external boundary of the information system (i.e., system perimeter) to detect covert exfiltration of information.','SI-4(18).2','The organization being inspected/assessed documents and implements a process to analyze outbound communications traffic at the external boundary of the information system (i.e., system perimeter) to detect covert exfiltration of information. The organization must maintain a record of the analysis.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of analysis to ensure the organization being inspected/assessed analyzes outbound communications traffic at the external boundary of the information system (i.e., system perimeter) to detect covert exfiltration of information.'),
('002672','draft','2013-07-11','DISA FSO','policy','The organization analyzes outbound communications traffic at organization-defined interior points within the system (e.g., subsystems, subnetworks) to detect covert exfiltration of information.','SI-4(18).3','The organization being inspected/assessed documents and implements a process to analyze outbound communications traffic at interior points defined in SI-4 (18), CCI 2670 within the system (e.g., subsystems, subnetworks) to detect covert exfiltration of information. The organization must maintain a record of the analysis.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of analysis to ensure the organization being inspected/assessed analyzes outbound communications traffic at interior points defined in SI-4 (18), CCI 2670 within the system (e.g., subsystems, subnetworks) to detect covert exfiltration of information.'),
('002673','draft','2013-07-11','DISA FSO','policy','The organization defines the additional monitoring to be implemented for individuals identified as posing an increased level of risk.','SI-4(19).1','The organization being inspected/assessed defines and documents the additional monitoring to be implemented for individuals identified as posing an increased level of risk. DoD has determined the additional monitoring is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented additional monitoring to ensure the organization being inspected/assessed defines the additional monitoring to be implemented for individuals identified as posing an increased level of risk. DoD has determined the additional monitoring is not appropriate to define at the Enterprise level.'),
('002674','draft','2013-07-11','DISA FSO','policy','The organization defines the sources that may be used to identify individuals who pose an increased level of risk.','SI-4(19).2','The organization being inspected/assessed defines and documents the sources that may be used to identify individuals who pose an increased level of risk. DoD has determined the sources are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented sources to ensure the organization being inspected/assessed defines the sources that may be used to identify individuals who pose an increased level of risk. DoD has determined the sources are not appropriate to define at the Enterprise level.'),
('002675','draft','2013-07-11','DISA FSO','policy','The organization implements organization-defined additional monitoring of individuals who have been identified by organization-defined sources as posing an increased level of risk.','SI-4(19).3','The organization being inspected/assessed implements additional monitoring defined in SI-4 (19), CCI 2673 of individuals who have been identified by sources defined in SI-4 (19), CCI 2674 as posing an increased level of risk. The organization must maintain an audit trail of additional monitoring.','The organization conducting the inspection/assessment obtains and examines the audit trail of additional monitoring to ensure the organization being inspected/assessed implements additional monitoring defined in SI-4 (19), CCI 2673 of individuals who have been identified by sources defined in SI-4 (19), CCI 2674 as posing an increased level of risk.'),
('002676','draft','2013-07-11','DISA FSO','policy','The organization defines additional monitoring to be implemented for privileged users.','SI-4(20).1','The organization being inspected/assessed defines and documents additional monitoring to be implemented for privileged users. DoD has determined the additional monitoring is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented additional monitoring to ensure the organization being inspected/assessed defines additional monitoring to be implemented for privileged users. DoD has determined the additional monitoring is not appropriate to define at the Enterprise level.'),
('002677','draft','2013-07-11','DISA FSO','policy','The organization implements organization-defined additional monitoring of privileged users.','SI-4(20).2','The organization being inspected/assessed implements additional monitoring defined in SI-4 (20), CCI 2676 of privileged users. The organization must maintain an audit trail of additional monitoring.','The organization conducting the inspection/assessment obtains and examines the audit trail of additional monitoring to ensure the organization being inspected/assessed implements additional monitoring defined in SI-4 (20), CCI 2676 of privileged users.'),
('002678','draft','2013-07-11','DISA FSO','policy','The organization defines additional monitoring to be implemented for individuals during an organization-defined probationary period.','SI-4(21).1','The organization being inspected/assessed defines and documents additional monitoring to be implemented for individuals during an organization-defined probationary period. DoD has determined the additional monitoring is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented additional monitoring to ensure the organization being inspected/assessed defines additional monitoring to be implemented for individuals during an organization-defined probationary period. DoD has determined the additional monitoring is not appropriate to define at the Enterprise level.'),
('002679','draft','2013-07-11','DISA FSO','policy','The organization defines the probationary period during which additional monitoring will be implemented for individuals.','SI-4(21).2','The organization defines and documents the probationary period during which additional monitoring will be implemented for individuals. DoD has determined the probationary period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented probationary period to ensure the organization being inspected/assessed defines the probationary period during which additional monitoring will be implemented for individuals. DoD has determined the probationary period is not appropriate to define at the Enterprise level.'),
('002680','draft','2013-07-11','DISA FSO','policy','The organization implements organization-defined additional monitoring of individuals during an organization-defined probationary period.','SI-4(21).3','The organization being inspected/assessed implements additional monitoring defined in SI-4 (21), CCI 2678 of individuals during the probationary period defined in SI-4 (21), CCI 2679. The organization must maintain an audit trail of additional monitoring.','The organization conducting the inspection/assessment obtains and examines the audit trail of additional monitoring to ensure the organization being inspected/assessed implements additional monitoring defined in SI-4 (21), CCI 2678 of individuals during the probationary period defined in SI-4 (21), CCI 2679.'),
('002681','draft','2013-07-11','DISA FSO','policy','The organization defines the authorization or approval process for network services.','SI-4(22).1','DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002682','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles to be alerted when unauthorized or unapproved network services are detected.','SI-4(22).2','DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002683','draft','2013-07-11','DISA FSO','policy','The information system detects network services that have not been authorized or approved by the organization-defined authorization or approval processes.','SI-4(22).3','The organization being inspected/assessed documents and implements a process to detect network services that have not been authorized or approved by at a minimum, the ISSO and ISSM. For network service detection mechanisms that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2683. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines the documented process, and examines the implemented detection mechanisms to ensure the organization being inspected/assessed implements a process to detect network services that have not been authorized or approved by at a minimum, the ISSO and ISSM.\nFor network service detection mechanisms that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2683.\nDoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002684','draft','2013-07-11','DISA FSO','technical','The information system audits and/or alerts organization-defined personnel when unauthorized network services are detected.','SI-4(22).4','The organization being inspected/assessed configures the information system to audit and/or alert at a minimum, the ISSO and ISSM when unauthorized network services are detected. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2684. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to audit and/or alert at a minimum, the ISSO and ISSM when unauthorized network services are detected. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2684. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002685','draft','2013-07-11','DISA FSO','policy','The organization defines the host-based monitoring mechanisms to be implemented at organization-defined information system components.','SI-4(23).1','DoD has defined the host-based monitoring mechanisms as HBSS.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the host-based monitoring mechanisms as HBSS.'),
('002686','draft','2013-07-11','DISA FSO','policy','The organization defines the information system components at which organization-defined host-based monitoring mechanisms are to be implemented.','SI-4(23).2','DoD has defined the information system components as all components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system components as all components.'),
('002687','draft','2013-07-11','DISA FSO','policy','The organization implements organization-defined host-based monitoring mechanisms at organization-defined information system components.','SI-4(23).3','The organization being inspected/assessed documents and implements HBSS at all components. DoD has defined the host-based monitoring mechanisms as HBSS. DoD has defined the information system components as all components.','The organization conducting the inspection/assessment obtains and examines documentation of the use of HBSS to ensure the organization being inspected/assessed implements HBSS at all components. The organization being inspected/assessed may be required to demonstrate use of HBSS. DoD has defined the host-based monitoring mechanisms as HBSS. DoD has defined the information system components as all components.'),
('002688','draft','2013-07-11','DISA FSO','technical','The information system discovers indicators of compromise.','SI-4(24).1','The organization being inspected/assessed configures the information system to discover indicators of compromise. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2688.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to discover indicators of compromise. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2688.'),
('002689','draft','2013-07-11','DISA FSO','technical','The information system collects indicators of compromise.','SI-4(24).2','The organization being inspected/assessed configures the information system to collect indicators of compromise. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2689.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to collect indicators of compromise. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2689.'),
('002690','draft','2013-07-11','DISA FSO','technical','The information system distributes indicators of compromise.','SI-4(24).3','The organization being inspected/assessed configures the information system to distribute indicators of compromise. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2690.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to distribute indicators of compromise. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2690.'),
('002691','draft','2013-07-11','DISA FSO','technical','The information system uses indicators of compromise.','SI-4(24).4','The organization being inspected/assessed configures the information system to use indicators of compromise to react to known indicators and prevent future exploitation of them. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2691.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to use indicators of compromise to react to known indicators and prevent future exploitation of them. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2691.'),
('002692','draft','2013-07-11','DISA FSO','policy','The organization defines the external organizations from which it receives information system security alerts, advisories, and directives.','SI-5.2','DoD has defined the external organizations as at a minimum, USCYBERCOM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external organizations as at a minimum, USCYBERCOM.'),
('002693','draft','2013-07-11','DISA FSO','policy','The organization defines the elements within the organization to whom the organization will disseminate security alerts, advisories, and directives.','SI-5.6','DoD has determined the elements are not applicable as elements are not selected as recipients of security alerts, advisories and directives.','DoD has determined the elements are not applicable as elements are not selected as recipients of security alerts, advisories and directives.'),
('002694','draft','2013-07-11','DISA FSO','policy','The organization defines the external organizations to which the organization will disseminate security alerts, advisories, and directives.','SI-5.7','DoD has defined the external organizations as CNDSP Tier 1 for vetting. The CNDSP Tier 1 will pass the information to the accredited Tier 2 CNDSPs. Tier 2 CNDSPs are responsible for ensuring all Tier 3 entities receive the information. Tier 3 organizations will ensure all local Op Centers/LAN shops receive information (i.e. Component IT System and Security Personnel) (e.g. ISSM, ISSOs, and system administrators).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external organizations as CNDSP Tier 1 for vetting. The CNDSP Tier 1 will pass the information to the accredited Tier 2 CNDSPs. Tier 2 CNDSPs are responsible for ensuring all Tier 3 entities receive the information. Tier 3 organizations will ensure all local Op Centers/LAN shops receive information (i.e. Component IT System and Security Personnel) (e.g. ISSM, ISSOs, and system administrators).'),
('002695','draft','2013-07-11','DISA FSO','policy','The organization defines the security functions that require verification of correct operation.','SI-6.1','The organization being inspected/assessed defines and documents the security functions that require verification of correct operation. DoD has determined the security functions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security functions to ensure the organization being inspected/assessed defines the security functions that require verification of correct operation. DoD has determined the security functions are not appropriate to define at the Enterprise level.'),
('002696','draft','2013-07-11','DISA FSO','technical','The information system verifies correct operation of organization-defined security functions.','SI-6.2','The organization being inspected/assessed configures the information system to verify correct operation of security functions defined in SI-6, CCI 2695. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2696.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to verify correct operation of security functions defined in SI-6, CCI 2695. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2696.'),
('002697','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency at which it will verify correct operation of organization-defined security functions.','SI-6.3','DoD has defined the frequency as 30 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as 30 days.'),
('002698','draft','2013-07-11','DISA FSO','policy','The organization defines the system transitional states when the information system will verify correct operation of organization-defined security functions.','SI-6.4','DoD has defined the system transitional states as upon system startup, and/or restart, upon command by user with appropriate privileges.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the system transitional states as upon system startup, and/or restart, upon command by user with appropriate privileges.'),
('002699','draft','2013-07-11','DISA FSO','technical','The information system performs verification of the correct operation of organization-defined security functions: when the system is in an organization-defined transitional state; upon command by a user with appropriate privileges; and/or on an organization-defined frequency.','SI-6.5','The organization being inspected/assessed configures the information system to perform verification of the correct operation of security functions defined in SI-6, CCI 1294: when the system is in a transitional state defined in SI-6, CCI 2698; upon command by a user with appropriate privileges; and/or 30 days. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2699. DoD has defined the frequency as 30 days.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to perform verification of the correct operation of security functions defined in SI-6, CCI 1294: when the system is in a transitional state defined in SI-6, CCI 2698; upon command by a user with appropriate privileges; and/or 30 days. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2699. DoD has defined the frequency as 30 days.'),
('002700','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles to be notified when security verification tests fail.','SI-6.7','DoD has defined the personnel or roles as the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSO and ISSM.'),
('002701','draft','2013-07-11','DISA FSO','policy','The organization defines alternative action(s) to be taken when the information system discovers anomalies in the operation of organization-defined security functions.','SI-6.8','DoD has defined the alternative action(s) as notifies system administrator.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the alternative action(s) as notifies system administrator.'),
('002702','draft','2013-07-11','DISA FSO','technical','The information system shuts the information system down, restarts the information system, and/or initiates organization-defined alternative action(s) when anomalies in the operation of the organization-defined security functions are discovered.','SI-6.9','The organization being inspected/assessed configures the information system to shut the information system down, restarts the information system, and/or notifies system administrator when anomalies in the operation of the security functions defined in SI-6, CCI 2695 are discovered. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2702. DoD has defined the alternative action(s) as notifies system administrator.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to shut the information system down, restarts the information system, and/or notifies system administrator when anomalies in the operation of the security functions defined in SI-6, CCI 2695 are discovered. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2702. DoD has defined the alternative action(s) as notifies system administrator.'),
('002703','draft','2013-07-11','DISA FSO','policy','The organization defines the software, firmware, and information which will be subjected to integrity verification tools to detect unauthorized changes.','SI-7.1','The organization being inspected/assessed defines and documents the software, firmware, and information which will be subjected to integrity verification tools to detect unauthorized changes. DoD has determined the software, firmware, and information are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented software, firmware, and information to ensure the organization being inspected/assessed defines the software, firmware, and information which will be subjected to integrity verification tools to detect unauthorized changes. DoD has determined the software, firmware, and information are not appropriate to define at the Enterprise level.'),
('002704','draft','2013-07-11','DISA FSO','policy','The organization employs integrity verification tools to detect unauthorized changes to organization-defined software, firmware, and information.','SI-7.2','The organization being inspected/assessed designs the information system to employ integrity verification tools to detect unauthorized changes to software, firmware, and information defined in SI-7, CCI 2703.','The organization conducting the inspection/assessment obtains and examines the hardware/software lists and any other documentation applicable to integrity verification tools to ensure the organization being inspected/assessed employs integrity verification tools to detect unauthorized changes to software, firmware, and information defined in SI-7, CCI 2703.'),
('002705','draft','2013-07-11','DISA FSO','policy','The organization defines the software on which integrity checks will be performed.','SI-7(1).1','The organization being inspected/assessed defines and documents the software on which integrity checks will be performed. DoD has determined the software is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented software to ensure the organization being inspected/assessed defines the firmware on which integrity checks will be performed. DoD has determined the software is not appropriate to define at the Enterprise level.'),
('002706','draft','2013-07-11','DISA FSO','policy','The organization defines the firmware on which integrity checks will be performed.','SI-7(1).2','The organization being inspected/assessed defines and documents the firmware on which integrity checks will be performed. DoD has determined the firmware is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented firmware to ensure the organization being inspected/assessed defines the firmware on which integrity checks will be performed. DoD has determined the firmware is not appropriate to define at the Enterprise level.'),
('002707','draft','2013-07-11','DISA FSO','policy','The organization defines the information on which integrity checks will be performed.','SI-7(1).3','The organization being inspected/assessed defines and documents the information on which integrity checks will be performed. DoD has determined the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information to ensure the organization being inspected/assessed defines the information on which integrity checks will be performed. DoD has determined the information is not appropriate to define at the Enterprise level.'),
('002708','draft','2013-07-11','DISA FSO','policy','The organization defines the transitional state or security-relevant events when the information system will perform integrity checks on software, firmware, and information.','SI-7(1).4','The organization being inspected/assessed defines and documents the transitional state or security-relevant events when the information system will perform integrity checks on software, firmware and information. DoD has determined the transitional state or security-relevant events are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented transitional state or security-relevant event to ensure the organization being inspected/assessed defines the transitional state or security-relevant events when the information system will perform integrity checks on software, firmware and information. DoD has determined the transitional state or security-relevant events are not appropriate to define at the Enterprise level.'),
('002709','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency at which it will perform integrity checks of software, firmware, and information.','SI-7(1).5','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('002710','draft','2013-07-11','DISA FSO','technical','The information system performs an integrity check of organization-defined software at startup, at organization-defined transitional states or security-relevant events, or on an organization-defined frequency.','SI-7(1).6','The organization being inspected/assessed configures the information system to perform an integrity check of software defined in SI-7 (1), CCI 2705 at startup, at transitional states or security-relevant events defined in SI-7 (1), CCI 2708, or annually. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2710. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to perform an integrity check of software defined in SI-7 (1), CCI 2705 at startup, at transitional states or security-relevant events defined in SI-7 (1), CCI 2708, or annually. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2710. DoD has defined the frequency as annually.'),
('002711','draft','2013-07-11','DISA FSO','technical','The information system performs an integrity check of organization-defined firmware at startup, at organization-defined transitional states or security-relevant events, or on an organization-defined frequency.','SI-7(1).7','The organization being inspected/assessed configures the information system to perform an integrity check of firmware defined in SI-7 (1), CCI 2706 at startup, at transitional states or security-relevant events defined in SI-7 (1), CCI 2708, or annually. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2711. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to perform an integrity check of firmware defined in SI-7 (1), CCI 2706 at startup, at transitional states or security-relevant events defined in SI-7 (1), CCI 2708, or annually. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2711. DoD has defined the frequency as annually.'),
('002712','draft','2013-07-11','DISA FSO','technical','The information system performs an integrity check of organization-defined information at startup, at organization-defined transitional states or security-relevant events, or on an organization-defined frequency.','SI-7(1).8','The organization being inspected/assessed configures the information system to perform an integrity check of information defined in SI-7 (1), CCI 2707 at startup, at transitional states or security-relevant events defined in SI-7 (1), CCI 2708, or annually. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2712. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to perform an integrity check of information defined in SI-7 (1), CCI 2707 at startup, at transitional states or security-relevant events defined in SI-7 (1), CCI 2708, or annually. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2712. DoD has defined the frequency as annually.'),
('002713','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles to be notified when discrepancies are discovered during integrity verification.','SI-7(2).2','DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002714','draft','2013-07-11','DISA FSO','policy','The organization defines the security safeguards that are to be employed when integrity violations are discovered.','SI-7(5).1','The organization being inspected/assessed defines and documents the security safeguards that are to be employed when integrity violations are discovered. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards that are to be employed when integrity violations are discovered. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002715','draft','2013-07-11','DISA FSO','technical','The information system automatically shuts the information system down, restarts the information system, and/or implements organization-defined security safeguards when integrity violations are discovered.','SI-7(5).2','The organization being inspected/assessed configures the information system to automatically shut the information system down, restart the information system, and/or implement security safeguards defined in SI-7 (5), CCI 2714 when integrity violations are discovered. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2715.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to automatically shut the information system down, restart the information system, and/or implement security safeguards defined in SI-7 (5), CCI 2714 when integrity violations are discovered. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2715.'),
('002716','draft','2013-07-11','DISA FSO','technical','The information system implements cryptographic mechanisms to detect unauthorized changes to software.','SI-7(6).1','The organization being inspected/assessed configures the information system to implement FIPS-approved cryptographic mechanisms to detect unauthorized changes to software. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2716.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement FIPS-approved cryptographic mechanisms to detect unauthorized changes to software. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2716.'),
('002717','draft','2013-07-11','DISA FSO','technical','The information system implements cryptographic mechanisms to detect unauthorized changes to firmware.','SI-7(6).2','The organization being inspected/assessed configures the information system to implement FIPS-approved cryptographic mechanisms to detect unauthorized changes to firmware. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2717.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement FIPS-approved cryptographic mechanisms to detect unauthorized changes to firmware. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2717.'),
('002718','draft','2013-07-11','DISA FSO','technical','The information system implements cryptographic mechanisms to detect unauthorized changes to information.','SI-7(6).3','The organization being inspected/assessed configures the information system to implement FIPS-approved cryptographic mechanisms to detect unauthorized changes to information. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2718.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement FIPS-approved cryptographic mechanisms to detect unauthorized changes to information. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2718.'),
('002719','draft','2013-07-11','DISA FSO','policy','The organization defines the unauthorized security-relevant changes to the information system that are to be incorporated into the organizational incident response capability.','SI-7(7).1','The organization being inspected/assessed defines and documents the unauthorized security-relevant changes to the information system that are to be incorporated into the organizational incident response capability. DoD has determined the security-relevant changes to the information are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security-relevant changes to the information to ensure the organization being inspected/assessed defines the unauthorized security-relevant changes to the information system that are to be incorporated into the organizational incident response capability. DoD has determined the security-relevant changes to the information are not appropriate to define at the Enterprise level.'),
('002720','draft','2013-07-11','DISA FSO','policy','The organization incorporates the detection of unauthorized organization-defined security-relevant changes to the information system into the organizational incident response capability.','SI-7(7).2','The organization being inspected/assessed incorporates the detection of unauthorized security-relevant changes to the information system defined in SI-7 (7), CCI 2719 into the organizational incident response capability.','The organization conducting the inspection/assessment examines the organizational incident response capability to ensure the organization being inspected/assessed incorporates the detection of unauthorized security-relevant changes to the information system defined in SI-7 (7), CCI 2719.'),
('002721','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles that are to be alerted by the information system when it detects a potential integrity violation.','SI-7(8).1','DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002722','draft','2013-07-11','DISA FSO','policy','The organization defines other actions that can be taken when the information system detects a potential integrity violation.','SI-7(8).2','The organization being inspected/assessed defines and documents other actions that can be taken when the information system detects a potential integrity violation. DoD has determined the other actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented other actions to ensure the organization being inspected/assessed defines other actions that can be taken when the information system detects a potential integrity violation. DoD has determined the other actions are not appropriate to define at the Enterprise level.'),
('002723','draft','2013-07-11','DISA FSO','technical','The information system, upon detection of a potential integrity violation, provides the capability to audit the event.','SI-7(8).3','The organization being inspected/assessed configures the information system to provide the capability to audit the event upon detection of a potential integrity violation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2723.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability to audit the event upon detection of a potential integrity violation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2723.'),
('002724','draft','2013-07-11','DISA FSO','technical','The information system, upon detection of a potential integrity violation, initiates one or more of the following actions: generates an audit record; alerts the current user; alerts organization-defined personnel or roles; and/or organization-defined other actions.','SI-7(8).4','The organization being inspected/assessed configures the information system to initiate one or more of following actions: generates an audit record; alerts current user; alerts at a minimum, the ISSO and ISSM; and/or other actions defined in SI-7 (8), CCI 2722 upon detection of a potential integrity violation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2724. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to initiate one or more of following actions: generates an audit record; alerts current user; alerts at a minimum, the ISSO and ISSM; and/or other actions defined in SI-7 (8), CCI 2722 upon detection of a potential integrity violation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2724. DoD has defined the personnel or roles as at a minimum, the ISSO and ISSM.'),
('002725','draft','2013-07-11','DISA FSO','policy','The organization defines the devices which will have the integrity of the boot process verified.','SI-7(9).1','DoD has defined the devices as all devices capable of verification of the boot process.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the devices as all devices capable of verification of the boot process.'),
('002726','draft','2013-07-11','DISA FSO','technical','The information system verifies the integrity of the boot process of organization-defined devices.','SI-7(9).2','The organization being inspected/assessed configures the information system to verify the integrity of the boot process of all devices capable of verification of the boot process. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2726. DoD has defined the devices as all devices capable of verification of the boot process.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to verify the integrity of the boot process of all devices capable of verification of the boot process. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2726. DoD has defined the devices as all devices capable of verification of the boot process.'),
('002727','draft','2013-07-11','DISA FSO','policy','The organization defines the security safeguards to be implemented to protect the integrity of the boot firmware in organization-defined devices.','SI-7(10).1','The organization being inspected/assessed defines and documents the security safeguards to be implemented to protect the integrity of the boot firmware in organization-defined devices. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be implemented to protect the integrity of the boot firmware in organization-defined devices. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002728','draft','2013-07-11','DISA FSO','policy','The organization defines the devices on which organization-defined security safeguards will be implemented to protect the integrity of the boot firmware.','SI-7(10).2','The organization being inspected/assessed defines and documents the devices on which organization-defined security safeguards will be implemented to protect the integrity of the boot firmware. DoD has determined the devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented devices to ensure the organization being inspected/assessed defines the devices on which organization-defined security safeguards will be implemented to protect the integrity of the boot firmware. DoD has determined the devices are not appropriate to define at the Enterprise level.'),
('002729','draft','2013-07-11','DISA FSO','technical','The information system implements organization-defined security safeguards to protect the integrity of boot firmware in organization-defined devices.','SI-7(10).3','The organization being inspected/assessed configures the information system to implement security safeguards defined in SI-7 (10), CCI 2727 to protect the integrity of boot firmware in devices defined in SI-7 (10), CCI 2728. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2729.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement security safeguards defined in SI-7 (10), CCI 2727 to protect the integrity of boot firmware in devices defined in SI-7 (10), CCI 2728. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2729.'),
('002730','draft','2013-07-11','DISA FSO','policy','The organization defines the user-installed software that is to be executed in a confined physical or virtual machine environment with limited privileges.','SI-7(11).1','The organization being inspected/assessed defines and documents the user-installed software that is to be executed in a confined physical or virtual machine environment with limited privileges. DoD has determined the user-installed software is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented user-installed software to ensure the organization being inspected/assessed defines the user-installed software that is to be executed in a confined physical or virtual machine environment with limited privileges. DoD has determined the user-installed software is not appropriate to define at the Enterprise level.'),
('002731','draft','2013-07-11','DISA FSO','policy','The organization requires that organization-defined user-installed software execute in a confined physical or virtual machine environment with limited privileges.','SI-7(11).2','The organization being inspected/assessed requires that user-installed software defined in SI-7 (11), CCI 2730 execute in a confined physical or virtual machine environment with limited privileges.','The organization conducting the inspection/assessment examines the information system to ensure that software defined in SI-7 (11), CCI 2730 executes in a confined physical or virtual machine environment with limited privileges.'),
('002732','draft','2013-07-11','DISA FSO','policy','The organization defines the user-installed software that is to have its integrity verified prior to execution.','SI-7(12).1','DoD has defined the user-installed software as all user installed software (NOTE: the key is the term \"user installed.\").','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the user-installed software as all user installed software (NOTE: the key is the term \"user installed.\").'),
('002733','draft','2013-07-11','DISA FSO','policy','The organization requires that the integrity of organization-defined user-installed software be verified prior to execution.','SI-7(12).2','The organization being inspected/assessed requires that the integrity of all user installed software (NOTE: the key is the term \"user installed.\") be verified prior to execution. DoD has defined the user-installed software as all user installed software (NOTE: the key is the term \"user installed.\").','The organization conducting the inspection/assessment examines the information system to ensure that all user installed software (NOTE: the key is the term \"user installed.\") is verified prior to execution. DoD has defined the user-installed software as all user installed software (NOTE: the key is the term \"user installed.\").'),
('002734','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles which have the authority to explicitly approve binary or machine-executable code.','SI-7(13).1','DoD has defined has personnel or roles as the ISSO or ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined has personnel or roles as the ISSO or ISSM.'),
('002735','draft','2013-07-11','DISA FSO','policy','The organization allows execution of binary or machine-executable code obtained from sources with limited or no warranty and without the provision of source code only in confined physical or virtual machine environments.','SI-7(13).2','The organization being inspected/assessed allows execution of binary or machine-executable code obtained from sources without vendor support or with no warranty and without the provision of source code only in confined physical or virtual machine environments.','The organization conducting the inspection/assessment obtains and examines the software list and examines the information system to ensure the organization being inspected/assessed allows execution of binary or machine-executable code obtained from sources without vendor support or with no warranty and without the provision of source code only in confined physical or virtual machine environments.'),
('002736','draft','2013-07-11','DISA FSO','policy','The organization allows execution of binary or machine-executable code obtained from sources with limited or no warranty and without the provision of source code only with the explicit approval of organization-defined personnel or roles.','SI-7(13).3','The organization being inspected/assessed allows execution of binary or machine-executable code obtained from sources without vendor support or with no warranty and without the provision of source code only with the explicit approval of the ISSO or ISSM. DoD has defined has personnel or roles as the ISSO or ISSM.','The organization conducting the inspection/assessment obtains and examines the software list and examines the information system to ensure the organization being inspected/assessed allows execution of binary or machine-executable code obtained from sources without vendor support or with no warranty and without the provision of source code only with the explicit approval of the ISSO or ISSM. DoD has defined has personnel or roles as the ISSO or ISSM.'),
('002737','draft','2013-07-11','DISA FSO','policy','The organization prohibits the use of binary or machine-executable code from sources with limited or no warranty and without the provision of source code.','SI-7(14).1','The organization being inspected/assessed prohibits the use of binary or machine-executable code obtained from sources without vendor support or with no warranty and without the provision of source code.','The organization conducting the inspection/assessment obtains and examines the software list and examines the information system to ensure the organization being inspected/assessed prohibits the use of binary or machine-executable code obtained from sources without vendor support or with no warranty and without the provision of source code.'),
('002738','draft','2013-07-11','DISA FSO','policy','The organization provides exceptions to the source code requirement only for compelling mission/operational requirements and with the approval of the authorizing official.','SI-7(14).2','The organization being inspected/assessed documents and provides exceptions to the source code requirement only for compelling mission/operational requirements and with the approval of the authorizing official.','The organization conducting the inspection/assessment obtains and examines the documented exceptions to the source code requirement to ensure the organization being inspected/assessed provides justification and approval of the authorizing official for all exceptions to the source code requirement.'),
('002739','draft','2013-07-11','DISA FSO','policy','The organization defines the software or firmware components on which cryptographic mechanisms are to be implemented to support authentication prior to installation.','SI-7(15).1','DoD has defined the software or firmware components as all software and firmware from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the software or firmware components as all software and firmware from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity.'),
('002740','draft','2013-07-11','DISA FSO','technical','The information system implements cryptographic mechanisms to authenticate organization-defined software or firmware components prior to installation.','SI-7(15).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to authenticate all software and firmware from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity prior to installation. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2740. DoD has defined the software or firmware components as all software and firmware from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to authenticate all software and firmware from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity prior to installation. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2740. DoD has defined the software or firmware components as all software and firmware from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity.'),
('002741','draft','2013-07-11','DISA FSO','policy','The organization employs spam protection mechanisms at information system entry points to detect and take action on unsolicited messages.','SI-8.1','The organization being inspected/assessed implements spam protection mechanisms at information system entry points to detect and take action on unsolicited messages.','The organization conducting the inspection/assessment obtains and examines the hardware/software list to ensure the organization being inspected/assessed implements spam protection mechanisms at information system entry points to detect and take action on unsolicited messages. The organization may be required to demonstrate the use of the identified spam protection mechanisms.'),
('002742','draft','2013-07-11','DISA FSO','policy','The organization employs spam protection mechanisms at information system exit points to detect and take action on unsolicited messages.','SI-8.2','The organization being inspected/assessed implements spam protection mechanisms at information system exit points to detect and take action on unsolicited messages.','The organization conducting the inspection/assessment obtains and examines the hardware/software list to ensure the organization being inspected/assessed implements spam protection mechanisms at information system exit points to detect and take action on unsolicited messages. The organization may be required to demonstrate the use of the identified spam protection mechanisms.'),
('002743','draft','2013-07-11','DISA FSO','technical','The information system implements spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic.','SI-8(3).1','The organization being inspected/assessed configures the information system to implement spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2743.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2743.'),
('002744','draft','2013-07-11','DISA FSO','policy','The organization defines the inputs on which the information system is to conduct validity checks.','SI-10.2','The organization being inspected/assessed defines and documents specific inputs which do not require validity checks. DoD has defined the information inputs as all inputs except those identified specifically by the organization.','The organization conducting the DoD has defined the information inputs as all inputs except those identified specifically by the organization.'),
('002745','draft','2013-07-11','DISA FSO','policy','The organization defines the inputs for which the information system provides a manual override capability for input validation.','SI-10(1).1','The organization being inspected/assessed defines and documents the inputs for which the information system provides a manual override capability for input validation. DoD has determined the inputs are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented inputs to ensure the organization being inspected/assessed defines the inputs for which the information system provides a manual override capability for input validation. DoD has determined the inputs are not appropriate to define at the Enterprise level.'),
('002746','draft','2013-07-11','DISA FSO','technical','The information system provides a manual override capability for input validation of organization-defined inputs.','SI-10(1).2','The organization being inspected/assessed configures the information system to provide a manual override capability for input validation of inputs defined in SI-10 (1), CCI 2745. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2746.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide a manual override capability for input validation of inputs defined in SI-10 (1), CCI 2745. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2746.'),
('002747','draft','2013-07-11','DISA FSO','policy','The organization defines the individuals who have the authorization to use the manual override capability for input validation.','SI-10(1).3','The organization being inspected/assessed defines and documents the authorized individuals who have the capability to use the manual override capability for input validation. DoD has determined the authorized individuals are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented authorized individuals to ensure the organization being inspected/assessed defines the authorized individuals who have the capability to use the manual override capability for input validation. DoD has determined the authorized individuals are not appropriate to define at the Enterprise level.'),
('002748','draft','2013-07-11','DISA FSO','technical','The information system restricts the use of the manual override capability to only organization-defined authorized individuals.','SI-10(1).4','The organization being inspected/assessed configures the information system to restrict the use of the manual override capability to only the authorized individuals defined in SI-10 (1), CCI 2747. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2748.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to restrict the use of the manual override capability to only the authorized individuals defined in SI-10 (1), CCI 2747. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2748.'),
('002749','draft','2013-07-11','DISA FSO','technical','The information system audits the use of the manual override capability.','SI-10(1).5','The organization being inspected/assessed configures the information system to audit the use of the manual override capability. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2749.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to audit the use of the manual override capability. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2749.'),
('002750','draft','2013-07-11','DISA FSO','policy','The organization defines the time period within which input validation errors are to be reviewed.','SI-10(2).1','The organization being inspected/assessed defines and documents the time period within which input validation errors are reviewed. DoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure the organization being inspected/assessed defines the time period within which input validation errors are reviewed. DoD has determined the time period is not appropriate to define at the Enterprise level.'),
('002751','draft','2013-07-11','DISA FSO','policy','The organization defines the time period within which input validation errors are to be resolved.','SI-10(2).2','The organization being inspected/assessed defines and documents the time period within which input validation errors are resolved. DoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure the organization being inspected/assessed defines the time period within which input validation errors are resolved. DoD has determined the time period is not appropriate to define at the Enterprise level.'),
('002752','draft','2013-07-11','DISA FSO','policy','The organization ensures that input validation errors are reviewed within an organization-defined time period.','SI-10(2).3','The organization being inspected/assessed documents and implements a process to review input validation errors within the time period defined in SI-10 (2), CCI 2750. The organization must maintain records of review.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of review to ensure the organization being inspected/assessed reviews input validation errors within the time period defined in SI-10 (2), CCI 2750.'),
('002753','draft','2013-07-11','DISA FSO','policy','The organization ensures that input validation errors are resolved within an organization-defined time period.','SI-10(2).4','The organization being inspected/assessed documents and implements a process to resolve input validation errors within the time period defined in SI-10 (2), CCI 2751. The organization must maintain records of resolution.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of resolution to ensure the organization being inspected/assessed resolves input validation errors within the time period defined in SI-10 (2), CCI 2751.'),
('002754','draft','2013-07-11','DISA FSO','policy','The information system behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.','SI-10(3).1','The organization being inspected/assessed documents proper behavior that reflects organizational and system objectives for when invalid inputs are received. The organization being inspected/assessed configures the information system to behave in the documented manner when invalid inputs are received. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2754.','The organization conducting the inspection/assessment obtains and examines the documented behavior to ensure the organization being inspected/assessed documents proper behavior that reflects organizational and system objectives for when invalid inputs are received. The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to behave in the documented manner when invalid inputs are received. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2754.'),
('002755','draft','2013-07-11','DISA FSO','policy','The organization accounts for timing interactions among information system components in determining appropriate responses for invalid inputs.','SI-10(4).1','The organization being inspected/assessed designs the information system to account for timing interactions among information system components in determining appropriate responses for invalid inputs.','The organization conducting the inspection/assessment obtains and examines system design artifacts to ensure the organization being inspected/assessed accounts for timing interactions among information system components in determining appropriate responses for invalid inputs.'),
('002756','draft','2013-07-11','DISA FSO','policy','The organization defines the trusted sources to which the usage of information inputs will be restricted (e.g., whitelisting).','SI-10(5).1','The organization being inspected/assessed defines and documents the trusted sources to which the usage of information inputs will be restricted (e.g., whitelisting). DoD has determined the trusted sources are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented trusted sources to ensure the organization being inspected/assessed defines the trusted sources to which the usage of information inputs will be restricted (e.g., whitelisting). DoD has determined the trusted sources are not appropriate to define at the Enterprise level.'),
('002757','draft','2013-07-11','DISA FSO','policy','The organization defines the acceptable formats to which information inputs are restricted.','SI-10(5).2','The organization being inspected/assessed defines and documents the acceptable formats to which information inputs are restricted. DoD has determined the acceptable formats are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented acceptable formats to ensure the organization being inspected/assessed defines the acceptable formats to which information inputs are restricted. DoD has determined the acceptable formats are not appropriate to define at the Enterprise level.'),
('002758','draft','2013-07-11','DISA FSO','policy','The organization restricts the use of information inputs to organization-defined trusted sources and/or organization-defined formats.','SI-10(5).3','The organization being inspected/assessed designs the information system to restrict the use of information inputs to trusted sources defined in SI-10 (5), CCI 2756 and/or formats defined in SI-10 (5), CCI 2757.','The organization conducting the inspection/assessment obtains and examines system design artifacts to ensure the organization being inspected/assessed restricts the use of information inputs to trusted sources defined in SI-10 (5), CCI 2756 and/or formats defined in SI-10 (5), CCI 2757.'),
('002759','draft','2013-07-11','DISA FSO','policy','The organization defines the personnel or roles to whom error messages are to be revealed.','SI-11.3','DoD has defined the personnel or roles as the ISSO, ISSM, and SCA.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSO, ISSM, and SCA.'),
('002760','draft','2013-07-11','DISA FSO','policy','The organization determines mean time to failure (MTTF) for organization-defined information system components in specific environments of operation.','SI-13.1','The organization being inspected/assessed determines through testing or research and documents the mean time to failure (MTTF) for any component within a system requiring high availability in specific environments of operation. DoD has defined the system components as any component within a system requiring high availability.','The organization conducting the inspection/assessment obtains and examines documented mean time to failure (MTTF) to ensure the organization being inspected/assessed has determined the mean time to failure (MTTF) for any component within a system requiring high availability in specific environments of operation. DoD has defined the system components as any component within a system requiring high availability.'),
('002761','draft','2013-07-11','DISA FSO','policy','The organization defines the system components in specific environments of operation for which the mean time to failure (MTTF) is to be determined.','SI-13.2','DoD has defined the system components as any component within a system requiring high availability.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the system components as any component within a system requiring high availability.'),
('002762','draft','2013-07-11','DISA FSO','policy','The organization defines the mean time to failure (MTTF) substitution criteria to be employed as a means to determine the need to exchange active and standby components.','SI-13.4','The organization being inspected/assessed defines and documents the mean time to failure substitution criteria to be employed as a means to determine the need to exchange active and standby components. DoD has determined the mean time to failure is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented mean time to failure to ensure the organization being inspected/assessed defines the mean time to failure substitution criteria to be employed as a means to determine the need to exchange active and standby components. DoD has determined the mean time to failure is not appropriate to define at the Enterprise level.'),
('002763','draft','2013-07-11','DISA FSO','policy','The organization provides a means to exchange active and standby components in accordance with the organization-defined mean time to failure (MTTF) substitution criteria.','SI-13.5','The organization being inspected/assessed documents and implements a process to exchange active and standby components in accordance with the mean time to failure substitution criteria defined in SI-13, CCI 2762.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides a means to exchange active and standby components in accordance with the mean time to failure substitution criteria defined in SI-13, CCI 2762.'),
('002764','draft','2013-07-11','DISA FSO','policy','The organization defines non-persistent information system components and services to be implemented.','SI-14.1','The organization being inspected/assessed defines and documents non-persistent information system components and services to be implemented. DoD has determined the information system components and services are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components and services to ensure the organization being inspected/assessed defines non-persistent information system components and services to be implemented. DoD has determined the information system components and services are not appropriate to define at the Enterprise level.'),
('002765','draft','2013-07-11','DISA FSO','policy','The organization defines the frequency at which it will terminate organization-defined non-persistent information system components and services.','SI-14.2','The organization being inspected/assessed defines and documents the frequency at which it will terminate organization-defined non-persistent information system components and services. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency at which it will terminate organization-defined non-persistent information system components and services. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('002766','draft','2013-07-11','DISA FSO','policy','The organization implements organization-defined non-persistence information system components and services that are initiated in a known state.','SI-14.3','The organization being inspected/assessed designs the information system to implement non-persistence information system components and services defined in SI-14, CCI 2764 that are initiated in a known state.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed implements non-persistence information system components and services defined in SI-14, CCI 2764 that are initiated in a known state.'),
('002767','draft','2013-07-11','DISA FSO','policy','The organization implements organization-defined non-persistence information system components and services that are terminated upon end of session of use and/or periodically at an organization-defined frequency.','SI-14.4','The organization being inspected/assessed designs the information system to implement non-persistence information system components and services defined in SI-14, CCI 2764 that are terminated upon end of session of use and/or periodically at the frequency defined in SI-14, CCI 2765.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed implements non-persistence information system components and services defined in SI-14, CCI 2764 that are terminated upon end of session of use and/or periodically at the frequency defined in SI-14, CCI 2765.'),
('002768','draft','2013-07-11','DISA FSO','policy','The organization defines the trusted sources from which it obtains software and data employed during the refreshing of non-persistent information system components and services.','SI-14(1).1','The organization being inspected/assessed defines and documents the trusted sources from which it obtains software and data employed during the refreshing of non-persistent information system component and service. DoD has determined the trusted sources are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented trusted sources to ensure the organization being inspected/assessed defines the trusted sources from which it obtains software and data employed during the refreshing of non-persistent information system component and service. DoD has determined the trusted sources are not appropriate to define at the Enterprise level.'),
('002769','draft','2013-07-11','DISA FSO','policy','The organization ensures that software and data employed during non-persistent information system component and service refreshes are obtained from organization-defined trusted sources.','SI-14(1).2','The organization being inspected/assessed documents and implements a process to obtain software and data used during non-persistent information system component and service refreshes from trusted sources defined in SI-14 (1), CCI 2768.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that software and data used during non-persistent information system component and service refreshes from trusted sources defined in SI-14 (1), CCI 2768.'),
('002770','draft','2013-07-11','DISA FSO','policy','The organization defines the software programs and/or applications from which the information system is to validate the information output to ensure the information is consistent with expected content.','SI-15.1','The organization being inspected/assessed defines and documents the software programs and/or applications from which the information system is to validate the information output to ensure the information is consistent with expected content. DoD has determined the software programs and/or applications are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented software programs and/or applications to ensure the organization being inspected/assessed defines the software programs and/or applications from which the information system is to validate the information output to ensure the information is consistent with expected content. DoD has determined the software programs and/or applications are not appropriate to define at the Enterprise level.'),
('002771','draft','2013-07-11','DISA FSO','technical','The information system validates information output from organization-defined software programs and/or applications to ensure that the information is consistent with the expected content.','SI-15.2','The organization being inspected/assessed configures the information system to validate information output from software programs and/or applications defined in SI-15, CCI 2770 to ensure that the information is consistent with the expected content. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2771.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to validate information output from software programs and/or applications defined in SI-15, CCI 2770 to ensure that the information is consistent with the expected content. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2771.'),
('002772','deprecated','2013-07-11','DISA FSO','policy','The organization defines the security safeguards to be implemented to protect the information system^s memory from unauthorized code execution.',NULL,NULL,NULL),
('002773','draft','2013-07-11','DISA FSO','policy','The organization defines the fail-safe procedures to be implemented by the information system when organization-defined failure conditions occur.','SI-17.1','The organization being inspected/assessed defines and documents the fail-safe procedures to be implemented by the information system when organization-defined failure conditions occur. DoD has determined the fail-safe procedures are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented fail-safe procedures to ensure the organization being inspected/assessed defines the fail-safe procedures to be implemented by the information system when organization-defined failure conditions occur. DoD has determined the fail-safe procedures are not appropriate to define at the Enterprise level.'),
('002774','draft','2013-07-11','DISA FSO','policy','The organization defines the failure conditions which, when they occur, will result in the information system implementing organization-defined fail-safe procedures.','SI-17.2','The organization being inspected/assessed defines and documents the failure conditions which, when they occur, will result in the information system implementing organization-defined fail-safe procedures. DoD has determined the failure conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented failure conditions to ensure the organization being inspected/assessed defines the failure conditions which, when they occur, will result in the information system implementing organization-defined fail-safe procedures. DoD has determined the failure conditions are not appropriate to define at the Enterprise level.'),
('002775','draft','2013-07-11','DISA FSO','technical','The information system implements organization-defined fail-safe procedures when organization-defined failure conditions occur.','SI-17.3','The organization being inspected/assessed configures the information system to implement fail-safe procedures defined in SI-17, CCI 2773 when failure conditions defined in SI-17, CCI 2774 occur. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2775.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement fail-safe procedures defined in SI-17, CCI 2773 when failure conditions defined in SI-17, CCI 2774 occur. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2775.'),
('002776','draft','2013-07-12','DISA FSO','policy','The organization defines the personnel or roles to whom the incident response policy is disseminated.','IR-1.1','DoD has defined the roles as all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.'),
('002777','draft','2013-07-12','DISA FSO','policy','The organization defines the personnel or roles to whom the incident response procedures are disseminated.','IR-1.2','DoD has defined the roles as all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as all personnel identified as stakeholders in the incident response process, as well as the ISSM and ISSO.'),
('002778','draft','2013-07-12','DISA FSO','policy','The organization defines the time period in which information system users who assume an incident response role or responsibility receive incident response training.','IR-2.2','DoD has defined the time period as 30 working days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 30 working days.'),
('002779','draft','2013-07-12','DISA FSO','policy','The organization provides incident response training to information system users consistent with assigned roles and responsibilities when required by information system changes.','IR-2.5','The organization being inspected/assessed documents and implements a process to provide incident response training to information system users, other than general users, consistent with assigned roles and responsibilities when required by information system changes. For general users, DoD components are automatically compliant with the requirement based on DoDD 8570.01 requirements for IA awareness training. The organization must maintain a record of training.','The organization conducting the inspection/assessment obtains and examines the documented process as well as training records for a sampling of information system users to ensure the organization being inspected/assessed provides incident response training to information system users, other than general users, consistent with assigned roles and responsibilities when required by information system changes. For general users, DoD components are automatically compliant with the requirement based on DoDD 8570.01 requirements for IA awareness training. '),
('002780','draft','2013-07-12','DISA FSO','policy','The organization coordinates incident response testing with organizational elements responsible for related plans.','IR-3(2).1','The organization being inspected/assessed documents within their incident response testing plan, the necessary support from all responsible organizational elements for incident response testing.','The organization conducting the inspection/assessment obtains and examines the incident response testing plan to ensure the organization being inspected/assessed coordinates incident response testing with organizational elements responsible for related plans.'),
('002781','draft','2013-07-12','DISA FSO','policy','The organization defines the information system components for dynamic reconfiguration as part of the incident response capability.','IR-4(2).2','The organization being inspected/assessed defines and documents the information system components for dynamic reconfiguration as part of the incident response capability. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components for dynamic reconfiguration as part of the incident response capability.'),
('002782','draft','2013-07-12','DISA FSO','policy','The organization implements an incident handling capability for insider threats.','IR-4(6).1','The organization being inspected/assessed documents within their incident response plan and implements plans to respond to incidents related to insider threats.','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as a sampling of incident after action reports to ensure the organization being inspected/assessed implements incident handling capability for insider threats.'),
('002783','draft','2013-07-12','DISA FSO','policy','The organization coordinates an incident handling capability for insider threats across organization-defined components or elements of the organization.','IR-4(7).1','The organization being inspected/assessed documents within their incident response plan, the responsibilities of each element of the organization defined in IR-4 (7), CCI 2784.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed coordinates incident handling capability for insider threats across components or elements of the organization defined in IR-4 (7), CCI 2784.'),
('002784','draft','2013-07-12','DISA FSO','policy','The organization defines components or elements of the organization across which an incident handling capability for insider threats will be coordinated.','IR-4(7).2','The organization being inspected/assessed defines and documents components or elements of the organization in which incident handling capability for insider threats will be coordinated. DoD has determined the components or elements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented components or elements to ensure the organization being inspected/assessed defines components or elements of the organization in which incident handling capability for insider threats will be coordinated. DoD has determined the components or elements are not appropriate to define at the Enterprise level.'),
('002785','draft','2013-07-12','DISA FSO','policy','The organization coordinates with organization-defined external organizations to correlate and share organization-defined incident information to achieve a cross-organization perspective on incident awareness and more effective incident responses.','IR-4(8).1','The organization being inspected/assessed coordinates with external organizations defined in IR-4 (8), CCI 2786 to correlate and share incident information defined in IR-4 (8), CCI 2787 to achieve a cross-organization perspective on incident awareness and more effective incident responses.','The organization conducting the inspection/assessment obtains and examines reports, meeting minutes, or other evidence that the organization being inspected/assessed is coordinating with external organizations defined in IR-4 (8), CCI 2786 to correlate and share incident information defined in IR-4 (8), CCI 2787 to achieve a cross-organization perspective on incident awareness and more effective incident responses.'),
('002786','draft','2013-07-12','DISA FSO','policy','The organization defines external organizations with which to correlate and share organization-defined incident information.','IR-4(8).2','The organization being inspected/assessed defines and documents external organizations with whom they will correlate and share organization-defined incident information.\n\nDoD has determined the external organizations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented external organizations to ensure the organization being inspected/assessed defines external organizations to correlate and share organization-defined incident information.\n\nDoD has determined the external organizations are not appropriate to define at the Enterprise level.'),
('002787','draft','2013-07-12','DISA FSO','policy','The organization defines incident information to correlate and share with organization-defined external organizations.','IR-4(8).3','The organization being inspected/assessed defines and documents what incident information will be correlated and shared with each external organization defined in IR-4 (8), CCI 2786.\n\nDoD has determined the incident information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented incident information to ensure the organization being inspected/assessed defines what incident information will be correlated and shared with each external organization defined in IR-4 (8), CCI 2786.\n\nDoD has determined the incident information is not appropriate to define at the Enterprise level.'),
('002788','draft','2013-07-12','DISA FSO','policy','The organization employs organization-defined dynamic response capabilities to effectively respond to security incidents.','IR-4(9).1','The organization being inspected/assessed implements at a minimum, the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT) to effectively respond to security incidents. DoD has defined the dynamic response capabilities as at a minimum, the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT). ','The organization conducting the inspection/assessment obtains and examines incident response logs to ensure that they reflect the use of at a minimum, the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT). DoD has defined the dynamic response capabilities as at a minimum, the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT). '),
('002789','draft','2013-07-12','DISA FSO','policy','The organization defines dynamic response capabilities to effectively respond to security incidents.','IR-4(9).2','DoD has defined the dynamic response capabilities as at a minimum, the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the dynamic response capabilities as at a minimum, the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT).'),
('002790','draft','2013-07-12','DISA FSO','policy','The organization coordinates incident handling activities involving supply chain events with other organizations involved in the supply chain.','IR-4(10).1','The organization being inspected/assessed documents and implements a process to coordinate incident handling activities involving supply chain events with other organizations involved in the supply chain.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed coordinates incident handling activities involving supply chain events with other organizations involved in the supply chain.'),
('002791','draft','2013-07-12','DISA FSO','policy','The organization defines authorities to whom security incident information is reported.','IR-6.4','DoD has defined the authorities as the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the authorities as the appropriate CIRT/CERT (such as US-CERT, DoD CERT, IC CERT).'),
('002792','draft','2013-07-12','DISA FSO','policy','The organization defines personnel or roles to whom information system vulnerabilities associated with reported security incident information are reported.','IR-6(2).2','The organization being inspected/assessed defines and documents personnel or roles to whom information system vulnerabilities associated with reported security incident information are reported. The personnel shall be identified IAW CJCSM 6510.01B. DoD has determined the personnel are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel to ensure the organization being inspected/assessed defines personnel or roles to whom information system vulnerabilities associated with reported security incident information are reported IAW CJCSM 6510.01B.'),
('002793','draft','2013-07-12','DISA FSO','policy','The organization provides security incident information to other organizations involved in the supply chain for information systems or information system components related to the incident.','IR-6(3).1','The organization being inspected/assessed documents and implement a process to provide security incident information to other organizations involved in the supply chain for information systems or information system components related to the incident.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides security incident information to other organizations involved in the supply chain for information systems or information system components related to the incident.'),
('002794','draft','2013-07-12','DISA FSO','policy','The organization develops an incident response plan.','IR-8.1','The organization being inspected/assessed develops and documents an incident response plan.','The organization conducting the inspection/assessment obtains and examines the documented incident response plan to ensure the organization being inspected/assessed develops an incident response plan.'),
('002795','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan provides the organization with a roadmap for implementing its incident response capability.','IR-8.2','The organization being inspected/assessed defines and documents within their incident response plan, a roadmap for implementing its incident response capability.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed provides within their plan, a roadmap for implementing its incident response capability.'),
('002796','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan describes the structure and organization of the incident response capability.','IR-8.3','The organization being inspected/assessed defines and documents within their incident response plan, the structure and organization of the incident response capability.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed describes within their plan, the structure and organization of the incident response capability.'),
('002797','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan provides a high-level approach for how the incident response capability fits into the overall organization.','IR-8.4','The organization being inspected/assessed defines and documents within their incident response plan, a high-level approach for how the incident response capability fits into the overall organization.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed provides within their plan, a high-level approach for how the incident response capability fits into the overall organization.'),
('002798','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan meets the unique requirements of the organization, which relate to mission, size, structure, and functions.','IR-8.5','The organization being inspected/assessed will ensure their incident response plan meets the unique requirements of the organization, which relate to mission, size, structure, and functions.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure it meets the unique requirements of the organization being inspected/assessed, which relate to mission, size, structure, and functions.'),
('002799','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan defines reportable incidents.','IR-8.6','The organization being inspected/assessed defines and document within their incident response plan, reportable incidents IAW CJCSM 6510.01B Table B-A-2. ','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed defines reportable incidents IAW CJCSM 6510.01B Table B-A-2. '),
('002800','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan provides metrics for measuring the incident response capability within the organization.','IR-8.7','The organization being inspected/assessed defines and documents within their incident response plan, metrics for measuring the incident response capability within the organization IAW CJCSM 6510.01B, Enclosure A.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed defines metrics for measuring the incident response capability within the organization IAW CJCSM 6510.01B, Enclosure A.'),
('002801','draft','2013-07-12','DISA FSO','policy','The organization^s incident response plan defines the resources and management support needed to effectively maintain and mature an incident response capability.','IR-8.8','The organization being inspected/assessed defines and documents within their incident response plan, the resources and management support needed to effectively maintain and mature an incident response capability.','The organization conducting the inspection/assessment obtains and examines the incident response plan to ensure the organization being inspected/assessed defines within their plan, the resources and management support needed to effectively maintain and mature an incident response capability.'),
('002802','draft','2013-07-12','DISA FSO','policy','The organization defines personnel or roles to review and approve the incident response plan.','IR-8.9','DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.'),
('002803','draft','2013-07-12','DISA FSO','policy','The organization defines incident response personnel (identified by name and/or by role) and organizational elements to whom incident response plan changes will be communicated.','IR-8.17','DoD has defined the incident response personnel as all stakeholders identified in the incident response plan, not later than 30 days after the change is made.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the incident response personnel as all stakeholders identified in the incident response plan, not later than 30 days after the change is made.'),
('002804','draft','2013-07-12','DISA FSO','policy','The organization protects the incident response plan from unauthorized disclosure and modification.','IR-8.18','The organization being inspected/assessed protects the incident response plan from unauthorized disclosure and modification.','The organization conducting the inspection/assessment obtains and examines artifacts which identify how the incident response plan is protected to ensure the organization being inspected/assessed protects the incident response plan from unauthorized disclosure and modification.'),
('002805','draft','2013-07-12','DISA FSO','policy','The organization responds to information spills by identifying the specific information involved in the information system contamination.','IR-9.1','The organization being inspected/assessed documents within their incident response plan, a process to identify the specific information involved in the information system contamination. ','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as after action reports of incidents to ensure that specific information involved in the information system contamination is identified.'),
('002806','draft','2013-07-12','DISA FSO','policy','The organization responds to information spills by alerting organization-defined personnel or roles of the information spill using a method of communication not associated with the spill.','IR-9.2','The organization being inspected/assessed documents within their incident response plan, a process to alert at a minimum, the Originating Classification Authority (OCA), the information owner/originator, the ISSM, the activity security manager, and the responsible computer incident response center of the information spill using a method of communication not associated with the spill.\n\nDoD has defined the personnel or roles as at a minimum, the OCA, the information owner/originator, the ISSM, the activity security manager, and the responsible computer incident response center.','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as after action reports of incidents to ensure that at a minimum, the OCA, the information owner/originator, the ISSM, the activity security manager, and the responsible computer incident response center were alerted of the information spill using a method of communication not associated with the spill.\n\nDoD has defined the personnel or roles as at a minimum, the OCA, the information owner/originator, the ISSM, the activity security\nmanager, and the responsible computer incident response center.'),
('002807','draft','2013-07-12','DISA FSO','policy','The organization defines personnel or roles to be alerted of information spills using a method of communication not associated with the spill.','IR-9.3','DoD has defined the personnel or roles as at a minimum, the OCA, the information owner/originator, the ISSM, the activity security manager, and the responsible computer incident response center. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the OCA, the information owner/originator, the ISSM, the activity security manager, and the responsible computer incident response center. '),
('002808','draft','2013-07-12','DISA FSO','policy','The organization responds to information spills by isolating the contaminated information system or system component.','IR-9.4','The organization being inspected/assessed documents within their incident response plan, a process to isolate the contaminated information system or system component. ','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as after action reports of incidents to ensure that the organization being inspected/assessed isolates contaminated information system or system component.'),
('002809','draft','2013-07-12','DISA FSO','policy','The organization responds to information spills by eradicating the information from the contaminated information system or component.','IR-9.5','The organization being inspected/assessed documents within their incident response plan, a process to eradicate the information from the contaminated information system or component. ','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as after action reports of incidents to ensure that the organization being inspected/assessed eradicates the information from the contaminated information system or component.'),
('002810','draft','2013-07-12','DISA FSO','policy','The organization responds to information spills by identifying other information systems or system components that may have been subsequently contaminated.','IR-9.6','The organization being inspected/assessed documents within their incident response plan, a process to identify other information systems or system components that may have been subsequently contaminated. ','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as after action reports of incidents to ensure that the organization being inspected/assessed identifies other information systems or system components that may have been subsequently contaminated.'),
('002811','draft','2013-07-12','DISA FSO','policy','The organization responds to information spills by performing other organization-defined actions.','IR-9.7','The organization being inspected/assessed documents within their incident response plan, processes to perform actions defined in IR-9, CCI 2812. ','The organization conducting the inspection/assessment obtains and examines the incident response plan as well as after action reports of incidents to ensure that the organization being inspected/assessed performs actions defined in IR-9, CCI 2812.'),
('002812','draft','2013-07-12','DISA FSO','policy','The organization defines other actions required to respond to information spills.','IR-9.8','The organization being inspected/assessed\ndefines and documents additional actions to be taken in response to spillage incidents. The actions must include the following:\n1)consider the information system as classified at the same level as the spilled information until the appropriate remediation processes have been executed and verified;\n2) Include the investigative team members and questions identified in CNSS Instruction 1001 in investigation of the incident;\n3) Protect information regarding the incident from disclosure.\n\nDoD has determined the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented additional actions to ensure the organization being inspected/assessed defines other actions required to respond to information spills. DoD has determined the actions are not appropriate to define at the Enterprise level'),
('002813','draft','2013-07-12','DISA FSO','policy','The organization assigns organization-defined personnel or roles with responsibility for responding to information spills.','IR-9(1).1','The organization being inspected/assessed appoints personnel or roles defined in IR-9 (1), CCI 2815 as having the responsibility for responding to information spills. ','The organization conducting the inspection/assessment obtains and examines appointment letters to ensure the organization being inspected/assessed appoints personnel or roles defined in IR-9 (1), CCI 2815 as having the responsibility for responding to information spills. '),
('002814','deprecated','2013-07-12','DISA FSO','policy','The organization assigns organization-defined personnel or roles with responsibility for responding to information spills.',NULL,NULL,NULL),
('002815','draft','2013-07-12','DISA FSO','policy','The organization defines personnel or roles to whom responsibility for responding to information spills will be assigned.','IR-9(1).2','The organization being inspected/assessed defines and documents personnel or roles to whom responsibility for responding to information spills will be assigned. The personnel must include the ISSO and ISSM. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines personnel or roles to whom responsibility for responding to information spills will be assigned, which must include the ISSO and ISSM. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002816','draft','2013-07-12','DISA FSO','policy','The organization provides information spillage response training according to an organization-defined frequency.','IR-9(2).1','The organization being inspected/assessed documents and implements a process to provide information spillage response training annually. The organization must maintain a record of training. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the training records for a sampling of incident response personnel to ensure the organization being inspected/assessed provides information spillage response training annually. DoD has defined the frequency as annually.'),
('002817','draft','2013-07-12','DISA FSO','policy','The organization defines the frequency with which to provide information spillage response training.','IR-9(2).2','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('002818','draft','2013-07-12','DISA FSO','policy','The organization implements organization-defined procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.','IR-9(3).1','The organization being inspected/assessed implements procedures defined in IR-9 (3), CCI 2819 to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.','The organization conducting the inspection/assessment obtains and examines the documented procedures defined in IR-9 (3), CCI 2819 as well as after action reports of incidents to ensure the organization being inspected/assessed implements procedures defined in IR-9 (3), CCI 2819 to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.'),
('002819','draft','2013-07-12','DISA FSO','policy','The organization defines procedures to implement to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.','IR-9(3).2','The organization being inspected/assessed defines and documents procedures to implement to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions. DoD has determined the procedures are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed defines procedures to implement to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions. DoD has determined the procedures are not appropriate to define at the Enterprise level.'),
('002820','draft','2013-07-12','DISA FSO','policy','The organization employs organization-defined security safeguards for personnel exposed to information not within assigned access authorizations.','IR-9(4).1','The organization being inspected/assessed documents and implements a process to employ security safeguards defined in IR-9 (4), CCI 2821 for personnel exposed to information not within assigned access authorizations. ','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs security safeguards defined in IR-9 (4), CCI 2821 for personnel exposed to information not within assigned access authorizations. '),
('002821','draft','2013-07-12','DISA FSO','policy','The organization defines security safeguards to employ for personnel exposed to information not within assigned access authorizations.','IR-9(4).2','The organization being inspected/assessed defines and documents security safeguards to employ for personnel exposed to information not within assigned access authorizations. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines security safeguards to employ for personnel exposed to information not within assigned access authorizations. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002822','draft','2013-07-12','DISA FSO','policy','The organization establishes an integrated team of forensic/malicious code analysts, tool developers, and real-time operations personnel.','IR-10.1','The organization being inspected/assessed establishes an integrated team of forensic/malicious code analysts, tool developers, and real-time operations personnel. The organization appoints team members and defines and documents roles and responsibilities for each member.','The organization conducting the inspection/assessment obtains and examines appointments to the integrated team as well as the documented roles and responsibilities to ensure the organization being inspected/assessed establishes an integrated team of forensic/malicious code analysts, tool developers, and real-time operations personnel.'),
('002823','draft','2013-07-12','DISA FSO','policy','The organization defines the security safeguards to be implemented to protect the information system^s memory from unauthorized code execution.','SI-16.1','The organization being inspected/assessed defines and documents the security safeguards to be implemented to protect the information system\'s memory from unauthorized code execution. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be implemented to protect the information system\'s memory from unauthorized code execution. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002824','draft','2013-07-12','DISA FSO','technical','The information system implements organization-defined security safeguards to protect its memory from unauthorized code execution.','SI-16.2','The organization being inspected/assessed configures the information system to implement security safeguards defined in SI-16, CCI 2823 to protect its memory from unauthorized code execution. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2824.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement security safeguards defined in SI-16, CCI 2823 to protect its memory from unauthorized code execution. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2824.'),
('002825','draft','2013-07-20','DISA FSO','policy','The organization defines personnel or roles to whom the contingency planning policy is to be disseminated.','CP-1.3','DoD has defined the personnel or roles as all stakeholders identified in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all stakeholders identified in the contingency plan.'),
('002826','draft','2013-07-20','DISA FSO','policy','The organization defines personnel or roles to whom the contingency planning procedures are disseminated.','CP-1.6','DoD has defined the personnel or roles as all stakeholders identified in the contingency plan.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all stakeholders identified in the contingency plan.'),
('002827','draft','2013-07-20','DISA FSO','policy','The organization coordinates its contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.','CP-2(7).1','The organization being inspected/assessed implements service level agreements and/or memorandums of agreement with external service providers necessary for the conduct of contingency plans to ensure that contingency requirements can be satisfied.','The organization conducting the inspection/assessment obtains and examines service level agreements and/or memorandums of agreement with external service providers to ensure the organization being inspected/assessed coordinates with those providers.'),
('002828','draft','2013-07-20','DISA FSO','policy','The organization identifies critical information system assets supporting essential missions.','CP-2(8).1','The organization being inspected/assessed identifies and documents critical information system assets supporting essential missions.','The organization conducting the inspection/assessment obtains and examines the documented list of critical information system assets supporting essential missions to ensure the organization being inspected/assessed identifies those assets.'),
('002829','draft','2013-07-20','DISA FSO','policy','The organization identifies critical information system assets supporting essential business functions.','CP-2(8).2','The organization being inspected/assessed identifies and documents critical information system assets supporting essential business functions.','The organization conducting the inspection/assessment obtains and examines the documented list of critical information system assets supporting essential business functions to ensure the organization being inspected/assessed identifies those assets.'),
('002830','draft','2013-07-20','DISA FSO','policy','The organization defines the personnel or roles who review and approve the contingency plan for the information system.','CP-2.16','DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSM and ISSO.'),
('002831','draft','2013-07-20','DISA FSO','policy','The organization defines a list of key contingency personnel (identified by name and/or by role) and organizational elements to whom contingency plan changes are to be communicated.','CP-2.27','DoD has defined the list as all stakeholders identified in the contingency plan','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the list as all stakeholders identified in the contingency plan'),
('002832','draft','2013-07-20','DISA FSO','policy','The organization protects the contingency plan from unauthorized disclosure and modification.','CP-2.28','The organization being inspected/assessed documents and implements a process to protect the contingency plan from unauthorized disclosure and modification.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed protects the contingency plan from unauthorized disclosure and modification.'),
('002833','draft','2013-07-20','DISA FSO','policy','The organization defines the time period that contingency training is to be provided to information system users consistent with assigned roles and responsibilities within assuming a contingency role or responsibility.','CP-3.2','DoD has defined the time period as at a maximum, 10 working days. ','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as at a maximum, 10 working days. '),
('002834','draft','2013-07-20','DISA FSO','policy','The organization provides contingency training to information system users consistent with assigned roles and responsibilities when required by information system changes.','CP-3.3','The organization being inspected/assessed will update contingency training materials when required by information system changes and provide that training to personnel with contingency roles and responsibilities IAW CP-2, CCI 449. The organization will maintain documentation of the training activity dates, location, and personnel for audit trail purposes and future reference (e.g., scheduling refresher training, etc.).','The organization conducting the inspection/assessment obtains and examines training materials and documentation of training activities to determine whether the materials are accurate in consideration of the state of the information system and content of the contingency plan. The organization ensures that training is provided to users consistent with assigned roles and responsibilities.'),
('002835','draft','2013-07-20','DISA FSO','policy','The organization tests the contingency plan at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations.','CP-4(2).2','The organization being inspected/assessed will perform contingency plan testing at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations. The organization must maintain a record of test results.','The organization conducting the inspection/assessment obtains and examines the test results to ensure the organization being inspected/assessed tests the contingency plan at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations.'),
('002836','draft','2013-07-20','DISA FSO','policy','The organization ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site.','CP-6.2','The organization being inspected/assessed documents the information security safeguards that are in place at both the primary and alternate sites and evidence that the alternate site was approved based on an assessment that security is equivalent at the alternate site.','The organization conducting the inspection/assessment obtains and examines the documentation of the primary/alternate site information security safeguards that are in place as well as evidence that the alternate site was approved based on an assessment that security is equivalent at the alternate site.'),
('002837','draft','2013-07-20','DISA FSO','policy','The organization plans for circumstances that preclude returning to the primary processing site.','CP-7(6).1','The organization being inspected/assessed documents a process to be followed in the event of circumstances that preclude returning to the primary processing site.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed plans for circumstances that preclude returning to the primary processing site.'),
('002838','draft','2013-07-20','DISA FSO','policy','The organization prepares for circumstances that preclude returning to the primary processing site.','CP-7(6).2','The organization being inspected/assessed makes the resources available necessary to implement the plan documented IAW CP-7 (6), CCI 2837.','The organization conducting the inspection/assessment obtains and examines system resource lists or agreements with external support providers to ensure the organization being inspected/assessed prepares for circumstances that preclude returning to the primary processing site.'),
('002839','draft','2013-07-20','DISA FSO','policy','The organization defines information system operations that are permitted to transfer and resume at an alternate processing site for essential missions/business functions when the primary processing capabilities are unavailable.','CP-7.4','The organization being inspected/assessed defines and documents information system operations that are permitted to transfer and resume at an alternate processing sites for essential missions/business functions when the primary processing capabilities are unavailable. DoD has determined the information system operations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system operations to ensure the organization being inspected/assessed defines information system operations that are permitted to transfer and resume at an alternate processing sites for essential missions/business functions when the primary processing capabilities are unavailable. DoD has determined the information system operations are not appropriate to define at the Enterprise level.'),
('002840','draft','2013-07-20','DISA FSO','policy','The organization defines the information system operations to be resumed for essential missions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-8.5','The organization being inspected/assessed defines and documents the information system operations to be resumed for essential missions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites. DoD has determined the information system operations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system operations to ensure the organization being inspected/assessed defines the information system operations to be resumed for essential missions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites. DoD has determined the information system operations are not appropriate to define at the Enterprise level.'),
('002841','draft','2013-07-20','DISA FSO','policy','The organization defines the information system operations to be resumed for essential business functions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-8.6','The organization being inspected/assessed defines and documents the information system operations to be resumed for essential business functions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites. DoD has determined the information system operations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system operations to ensure the organization being inspected/assessed defines the information system operations to be resumed for essential business functions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites. DoD has determined the information system operations are not appropriate to define at the Enterprise level.'),
('002842','draft','2013-07-20','DISA FSO','policy','The organization reviews provider contingency plans to ensure that the plans meet organizational contingency requirements.','CP-8(4).3','The organization being inspected/assessed obtains and examines provider contingency plans to ensure the plans meet organizational contingency requirements. The organization must maintain an audit trail of reviews.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews to ensure the organization being inspected/assessed reviews provider contingency plans to ensure that the plans meet organizational contingency requirements.'),
('002843','draft','2013-07-20','DISA FSO','policy','The organization defines the frequency with which to obtain evidence of contingency testing by providers.','CP-8(4).4','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually.'),
('002844','draft','2013-07-20','DISA FSO','policy','The organization defines the frequency with which to obtain evidence of contingency training by providers.','CP-8(4).5','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at least annually.'),
('002845','draft','2013-07-20','DISA FSO','policy','The organization obtains evidence of contingency testing by providers in accordance with organization-defined frequency.','CP-8(4).6','The organization being inspected/assessed obtains and maintains evidence of contingency testing by providers to ensure that the training is tested at least annually. DoD has defined the frequency as at least annually.','The organization conducting the inspection/assessment obtains and examines the evidence of contingency testing to ensure that the organization being inspected/assessed obtains evidence that contingency testing is conducted by providers at least annually. DoD has defined the frequency as at least annually.'),
('002846','draft','2013-07-20','DISA FSO','policy','The organization obtains evidence of contingency training by providers in accordance with organization-defined frequency.','CP-8(4).7','The organization being inspected/assessed obtains and maintains evidence of contingency training by providers to ensure that the training is provided at least annually. DoD has defined the frequency as at least annually.','The organization conducting the inspection/assessment obtains and examines the evidence of contingency training to ensure that the organization being inspected/assessed obtains evidence that contingency training is conducted by providers at least annually. DoD has defined the frequency as at least annually.'),
('002847','draft','2013-07-20','DISA FSO','policy','The organization defines the frequency with which to test alternate telecommunication services.','CP-8(5).1','DoD has defined the frequency as at least annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level DoD has defined the frequency as at least annually.'),
('002848','draft','2013-07-20','DISA FSO','policy','The organization tests alternate telecommunication services per organization-defined frequency.','CP-8(5).2','The organization being inspected/assessed documents and implements a process to test alternate telecommunication services at least annually. The organization must maintain a record of tests. DoD has defined the frequency as at least annually.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of tests to ensure the organization being inspected/assessed tests alternate telecommunication services at least annually. DoD has defined the frequency as at least annually.'),
('002849','draft','2013-07-20','DISA FSO','policy','The organization defines critical information system software and other security-related information, of which backup copies must be stored in a separate facility or in a fire-rated container.','CP-9(3).1','The organization being inspected/assessed defines and documents critical information system software and other security-related information which backup copies must be stored in a separate facility or in a fire-rated container. DoD has determined the critical information system software and other security-related information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented critical information system software and other security-related information to ensure the organization being inspected/assessed defines critical information system software and other security-related information which backup copies must be stored in a separate facility or in a fire-rated container. DoD has determined the critical information system software and other security-related information is not appropriate to define at the Enterprise level.'),
('002850','draft','2013-07-20','DISA FSO','policy','The organization stores backup copies of organization-defined critical information system software and other security-related information in a separate facility or in a fire-rated container that is not collocated with the operational system.','CP-9(3).2','The organization being inspected/assessed stores backup copies of critical information system software and other security-related information defined in CP-9 (3), CCI 2849 in a separate facility or in a fire-rated container that is not collocated with the operational system. The organization must maintain a record of where software is stored.','The organization conducting the inspection/assessment obtains and examines the record of where software is stored to ensure the organization being inspected/assessed stores backup copies of critical information system software and other security-related information defined in CP-9 (3), CCI 2849 in a separate facility or in a fire-rated container that is not collocated with the operational system.'),
('002851','draft','2013-07-20','DISA FSO','policy','The organization defines the backup information that requires dual authorization for deletion or destruction.','CP-9(7).1','The organization being inspected/assessed defines and documents the backup information that requires dual authorization for deletion or destruction. DoD has determined the backup information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented backup information to ensure the organization being inspected/assessed defines the backup information that requires dual authorization for deletion or destruction. DoD has determined the backup information is not appropriate to define at the Enterprise level.'),
('002852','draft','2013-07-20','DISA FSO','policy','The organization enforces dual authorization for the deletion or destruction of organization-defined backup information.','CP-9(7).2','The organization being inspected/assessed documents and implements a process for dual authorization for the deletion or destruction of backup information defined in CP-9 (7), CCI 2851. The organization must maintain a record of deletion or destruction of information defined in CP-9 (7), CCI 2851.','The organization conducting the inspection/assessment obtains and examines the documented process and record of deletion and destruction to ensure the organization being inspected/assessed enforces dual authorization for the deletion or destruction of backup information defined in CP-9 (7), CCI 2851.'),
('002853','draft','2013-07-20','DISA FSO','technical','The information system provides the capability to employ organization-defined alternative communications protocols in support of maintaining continuity of operations.','CP-11.1','The organization being inspected/assessed configures the information system to provide the capability to employ alternative communications protocols defined in CP-11, CCI 2854 in support of maintaining continuity of operations. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2853.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to provide the capability to employ alternative communications protocols defined in CP-11, CCI 2854 in support of maintaining continuity of operations. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2853.'),
('002854','draft','2013-07-20','DISA FSO','policy','The organization defines the alternative communications protocols the information system must be capable of providing in support of maintaining continuity of operations.','CP-11.2','The organization being inspected/assessed defines and documents the alternative communications protocols the information systems must be capable of providing in support of maintaining continuity of operations. DoD has determined the alternative communications protocols are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented alternative communications protocols to ensure the organization being inspected/assessed defines the alternative communications protocols the information systems must be capable of providing in support of maintaining continuity of operations. DoD has determined the alternative communications protocols are not appropriate to define at the Enterprise level.'),
('002855','draft','2013-07-20','DISA FSO','technical','The information system, when organization-defined conditions are detected, enters a safe mode of operation with organization-defined restrictions of safe mode of operation.','CP-12.1','The organization being inspected/assessed configures the information system to enter a safe mode of operation with restrictions of safe mode of operation defined in CP-12, CCI 2857 when conditions defined in CP-12, CCI 2856 are detected. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2855.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enter a safe mode of operation with restrictions of safe mode of operation defined in CP-12, CCI 2857 when conditions defined in CP-12, CCI 2856 are detected. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2855.'),
('002856','draft','2013-07-20','DISA FSO','policy','The organization defines the conditions that, when detected, the information system enters a safe mode of operation with organization-defined restrictions of safe mode of operation.','CP-12.2','The organization being inspected/assessed defines and documents the conditions, that when detected, the information system enters a safe mode of operation with organization-defined restrictions of safe mode of operation. DoD has determined the conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented conditions to ensure the organization being inspected/assessed defines the conditions, that when detected, the information system enters a safe mode of operation with organization-defined restrictions of safe mode of operation. DoD has determined the conditions are not appropriate to define at the Enterprise level.'),
('002857','draft','2013-07-20','DISA FSO','policy','The organization defines the restrictions of the safe mode of operation that the information system will enter when organization-defined conditions are detected.','CP-12.3','The organization being inspected/assessed defines and documents the restrictions of safe mode of operation that the information system will enter when organization-defined conditions are detected. DoD has determined the restrictions on safe mode of operation are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented restrictions to ensure the organization being inspected/assessed defines the restrictions of safe mode of operation that the information system will enter when organization-defined conditions are detected. DoD has determined the restrictions on safe mode of operation are not appropriate to define at the Enterprise level.'),
('002858','draft','2013-07-20','DISA FSO','policy','The organization employs organization-defined alternative or supplemental security mechanisms for satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised.','CP-13.1','The organization being inspected/assessed documents and implement a process to employ alternative or supplemental security mechanisms defined in CP-13, CCI 2859 for satisfying security functions defined in CP-13, CCI 2860 when the primary means of implementing the security function is unavailable or compromised.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs alternative or supplemental security mechanisms defined in CP-13, CCI 2859 for satisfying security functions defined in CP-13, CCI 2860 when the primary means of implementing the security function is unavailable or compromised.'),
('002859','draft','2013-07-20','DISA FSO','policy','The organization defines the alternative or supplemental security mechanisms that will be employed for satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised.','CP-13.2','The organization being inspected/assessed defines and documents the alternative or supplemental security mechanisms that will be employed for satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised. DoD has determined the alternative or supplemental security mechanisms are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented alternative or supplemental security mechanisms to ensure the organization being inspected/assessed defines the alternative or supplemental security mechanisms that will be employed for satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised. DoD has determined the alternative or supplemental security mechanisms are not appropriate to define at the Enterprise level.'),
('002860','draft','2013-07-20','DISA FSO','policy','The organization defines the security functions that must be satisfied when the primary means of implementing the security function is unavailable or compromised.','CP-13.3','The organization being inspected/assessed defines and documents the security functions that must be satisfied when the primary means of implementing the security function is unavailable or compromised. DoD has determined the security functions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security functions to ensure the organization being inspected/assessed defines the security functions that must be satisfied when the primary means of implementing the security function is unavailable or compromised. DoD has determined the security functions are not appropriate to define at the Enterprise level.'),
('002861','draft','2013-07-22','DISA FSO','policy','The organization defines the personnel or roles to whom a system maintenance policy is disseminated.','MA-1.1','DoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.'),
('002862','draft','2013-07-22','DISA FSO','policy','The organization defines the personnel or roles to whom system maintenance procedures are to be disseminated.','MA-1.2','DoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the SCA, ISSO, and maintenance personnel as needed by role in maintaining the system.'),
('002863','draft','2013-07-22','DISA FSO','policy','The organization employs automated mechanisms to schedule, conduct, and document repairs.','MA-2(2).1','The organization being inspected/assessed documents and implements automated mechanisms to schedule, conduct, and document repairs.','The organization conducting the inspection/assessment obtains and examines the documentation of automated mechanisms to ensure the organization being inspected/assessed employs automated mechanisms to schedule, conduct, and document repairs.'),
('002864','draft','2013-07-22','DISA FSO','policy','The organization produces up-to date, accurate, and complete records of all maintenance requested, scheduled, in process, and completed.','MA-2(2).3','The organization being inspected/assessed produces and maintains up-to date, accurate, and complete records of all maintenance requested, scheduled, in process, and completed.','The organization conducting the inspection/assessment obtains and examines the records of maintenance to ensure the organization being inspected/assessed produces up-to date, accurate, and complete records of all maintenance requested, scheduled, in process, and completed.'),
('002865','draft','2013-07-22','DISA FSO','policy','The organization produces up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed.','MA-2(2).4','The organization being inspected/assessed produces and maintains up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed.','The organization conducting the inspection/assessment obtains and examines the records of repair actions to ensure the organization being inspected/assessed produces up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed.'),
('002866','draft','2013-07-22','DISA FSO','policy','The organization schedules maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.1','The organization being inspected/assessed schedules maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements. The organization must maintain a record of maintenance.','The organization conducting the inspection/assessment obtains and examines the record of maintenance to ensure the organization being inspected/assessed schedules maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002867','draft','2013-07-22','DISA FSO','policy','The organization performs maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.2','The organization being inspected/assessed implements a process to perform maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements. The organization must maintain a record of maintenance procedures followed.','The organization conducting the inspection/assessment obtains and examines the record of maintenance procedures followed to ensure the organization being inspected/assessed performs maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002868','draft','2013-07-22','DISA FSO','policy','The organization documents maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.3','The organization being inspected/assessed documents maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','The organization conducting the inspection/assessment obtains and examines documentation of maintenance to ensure the organization being inspected/assessed documents maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002869','draft','2013-07-22','DISA FSO','policy','The organization reviews records of maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.4','The organization being inspected/assessed documents and implements a process to review records of maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews records of maintenance on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002870','draft','2013-07-22','DISA FSO','policy','The organization schedules repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.5','The organization being inspected/assessed schedules repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements. The organization must maintain a record of repairs.','The organization conducting the inspection/assessment obtains and examines the record of repairs to ensure the organization being inspected/assessed schedules repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002871','draft','2013-07-22','DISA FSO','policy','The organization performs repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.6','The organization being inspected/assessed implements a process to perform repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements. The organization must maintain a record of repair procedures followed.','The organization conducting the inspection/assessment obtains and examines the record of repair procedures followed to ensure the organization being inspected/assessed performs repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002872','draft','2013-07-22','DISA FSO','policy','The organization documents repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.7','The organization being inspected/assessed documents repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','The organization conducting the inspection/assessment obtains and examines documentation of repairs to ensure the organization being inspected/assessed documents repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002873','draft','2013-07-22','DISA FSO','policy','The organization reviews records of repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-2.8','The organization being inspected/assessed documents and implements a process to review records of repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews records of repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002874','draft','2013-07-22','DISA FSO','policy','The organization defines the personnel or roles who can explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs.','MA-2.11','The organization being inspected/assessed defines and documents the personnel or roles who can explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles who can explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002875','draft','2013-07-22','DISA FSO','policy','The organization includes organization-defined maintenance-related information in organizational maintenance records.','MA-2.14','The organization being inspected/assessed includes maintenance-related information defined in MA-2, CCI 2876 in organizational maintenance records.','The organization conducting the inspection/assessment obtains and examines maintenance records to ensure they include maintenance-related information defined in MA-2, CCI 2876.'),
('002876','draft','2013-07-22','DISA FSO','policy','The organization defines the maintenance-related information to include in organizational maintenance records.','MA-2.15','The organization being inspected/assessed defines and documents the maintenance-related information to include in organizational maintenance records. DoD has determined the maintenance-related information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented maintenance-related information to ensure the organization being inspected/assessed defines the maintenance-related information to include in organizational maintenance records. DoD has determined the maintenance-related information is not appropriate to define at the Enterprise level.'),
('002877','deprecated','2013-07-22','DISA FSO','policy','The organization prevents the unauthorized removal of maintenance equipment containing organizational information by verifying that there is no organizational information contained on the equipment.',NULL,NULL,NULL),
('002878','deprecated','2013-07-22','DISA FSO','policy','The organization prevents the unauthorized removal of maintenance equipment containing organizational information by sanitizing or destroying the equipment.',NULL,NULL,NULL),
('002879','deprecated','2013-07-22','DISA FSO','policy','The organization prevents the unauthorized removal of maintenance equipment containing organizational information by retaining the equipment within the facility.',NULL,NULL,NULL),
('002880','deprecated','2013-07-22','DISA FSO','policy','The organization prevents the unauthorized removal of maintenance equipment containing organizational information by retaining the equipment within the facility.',NULL,NULL,NULL),
('002881','deprecated','2013-07-22','DISA FSO','policy','The organization prevents the unauthorized removal of maintenance equipment containing organizational information by obtaining an exemption from organization-defined personnel or roles explicitly authorizing removal of the equipment from the facility.',NULL,NULL,NULL),
('002882','draft','2013-07-22','DISA FSO','policy','The organization defines the personnel or roles who can provide an exemption that explicitly authorizes removal of equipment from the facility.','MA-3(3).2','The organization being inspected/assessed defines and documents the personnel or roles who can provide an exemption that explicitly authorizes removal of equipment from the facility. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles who can provide an exemption that explicitly authorizes removal of equipment from the facility. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002883','draft','2013-07-22','DISA FSO','technical','The information system restricts the use of maintenance tools to authorized personnel only.','MA-3(4).1','The organization being inspected/assessed configures the information system to restrict the use of maintenance tools to authorized personnel only. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2883.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to restrict the use of maintenance tools to authorized personnel only. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2883.'),
('002884','draft','2013-07-22','DISA FSO','technical','The organization audits nonlocal maintenance and diagnostic sessions^ organization-defined audit events.','MA-4(1).1','The organization being inspected/assessed configures the information system to audit nonlocal maintenance and diagnostic sessions\' organization-defined audit events. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2884.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to audit nonlocal maintenance and diagnostic sessions\' organization-defined audit events. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2884.'),
('002885','draft','2013-07-22','DISA FSO','policy','The organization defines the nonlocal maintenance and diagnostic session audit events to audit.','MA-4(1).2','The organization being inspected/assessed defines and documents the nonlocal maintenance and diagnostic session audit events to audit. DoD has determined the audit events are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented audit events to ensure the organization being inspected/assessed defines the nonlocal maintenance and diagnostic session audit events to audit. DoD has determined the audit events are not appropriate to define at the Enterprise level.'),
('002886','draft','2013-07-22','DISA FSO','policy','The organization reviews the records of the nonlocal maintenance and diagnostic sessions.','MA-4(1).3','The organization being inspected/assessed documents and implements a process to review the records of the nonlocal maintenance and diagnostic sessions. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews the records of the nonlocal maintenance and diagnostic sessions.'),
('002887','draft','2013-07-22','DISA FSO','policy','The organization defines the authenticators that are replay resistant which will be employed to protect nonlocal maintenance sessions.','MA-4(4).2','The organization being inspected/assessed defines and documents the authenticators that are replay resistant which will be employed to protect nonlocal maintenance sessions. DoD has determined the authenticators are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented authenticators to ensure the organization being inspected/assessed defines the authenticators that are replay resistant which will be employed to protect nonlocal maintenance sessions. DoD has determined the authenticators are not appropriate to define at the Enterprise level.'),
('002888','draft','2013-07-22','DISA FSO','policy','The organization defines the personnel or roles authorized to approve each nonlocal maintenance session.',NULL,NULL,NULL),
('002889','draft','2013-07-22','DISA FSO','policy','The organization notifies organization-defined personnel or roles of the date and time of planned nonlocal maintenance.','MA-4(5).4','The organization being inspected/assessed documents and implements a process to notify the user base which could be impacted by the maintenance event of the date and time of planned nonlocal maintenance. DoD has defined the personnel or roles as the user base which could be impacted by the maintenance event.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed notifies the user base which could be impacted by the maintenance event of the date and time of planned nonlocal maintenance. DoD has defined the personnel or roles as the user base which could be impacted by the maintenance event.'),
('002890','draft','2013-07-22','DISA FSO','technical','The information system implements cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications.','MA-4(6).1','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2890.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2890.'),
('002891','draft','2013-07-22','DISA FSO','technical','The information system implements remote disconnect verification at the termination of nonlocal maintenance and diagnostic sessions.','MA-4(7).1','The organization being inspected/assessed configures the information system to implement remote disconnect verification at the termination of nonlocal maintenance and diagnostic sessions. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2891.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement remote disconnect verification at the termination of nonlocal maintenance and diagnostic sessions. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2891.'),
('002892','draft','2013-07-22','DISA FSO','policy','The organization develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system.','MA-5(1).4','The organization being inspected/assessed documents and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system.'),
('002893','draft','2013-07-22','DISA FSO','policy','The organization ensures that non-escorted personnel performing maintenance activities not directly associated with the information system but in the physical proximity of the system, have required access authorization.','MA-5(5).1','The organization being inspected/assessed documents and implements a process to ensure that non-escorted personnel performing maintenance activities not directly associated with the information system but in the physical proximity of the system, have required access authorization.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that non-escorted personnel performing maintenance activities not directly associated with the information system but in the physical proximity of the system, have required access authorization.'),
('002894','draft','2013-07-22','DISA FSO','policy','The organization ensures that non-escorted personnel performing maintenance on the information system have required access authorizations.','MA-5.3','The organization being inspected/assessed documents and implements a process to ensure that non-escorted personnel performing maintenance on the information system have required access authorizations. The organization must maintain a record of personnel performing maintenance on the information system.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of personnel performing maintenance on the information system to ensure the organization being inspected/assessed ensures that non-escorted personnel performing maintenance on the information system have required access authorizations.'),
('002895','draft','2013-07-22','DISA FSO','policy','The organization designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.','MA-5.4','The organization being inspected/assessed defines and documents organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.','The organization conducting the inspection/assessment obtains and examines documented organizational personnel to ensure the organization being inspected/assessed designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.'),
('002896','draft','2013-07-22','DISA FSO','policy','The organization defines the information system components for which it obtains maintenance support and/or spare parts.','MA-6.2','The organization being inspected/assessed defines and documents the information system components for which it obtains maintenance support and/or spare parts. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components for which it obtains maintenance support and/or spare parts. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002897','draft','2013-07-22','DISA FSO','policy','The organization defines a time period for obtaining maintenance support and/or spare parts for organization-defined information system components after a failure.','MA-6.3','DoD has defined the time period as within 24 hours (Low and Moderate Availability) or immediately upon failure for (High Availability).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as within 24 hours (Low and Moderate Availability) or immediately upon failure for (High Availability).'),
('002898','draft','2013-07-22','DISA FSO','policy','The organization performs preventive maintenance on organization-defined information system components at organization-defined time intervals.','MA-6(1).1','The organization being inspected/assessed performs preventive maintenance on information system components defined in MA-6 (1), CCI 2899 at time intervals defined in MA-6 (1), CCI 2900. The organization must maintain schedules and records of preventive maintenance.','The organization conducting the inspection/assessment obtains and examines schedules and records of preventive maintenance to ensure the organization being inspected/assessed performs preventive maintenance on information system components defined in MA-6 (1), CCI 2899 at time intervals defined in MA-6 (1), CCI 2900.'),
('002899','draft','2013-07-22','DISA FSO','policy','The organization defines information system components on which to perform preventive maintenance.','MA-6(1).2','The organization being inspected/assessed defines and documents information system components on which to perform preventive maintenance. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines information system components on which to perform preventive maintenance. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002900','draft','2013-07-22','DISA FSO','policy','The organization defines time intervals at which to perform preventive maintenance on organization-defined information system components.','MA-6(1).3','The organization being inspected/assessed defines and documents time intervals to perform preventive maintenance on organization-defined information system components. Time periods must be determined based on methods of determining what preventive (or other) failure management policies to apply include, for example, original equipment manufacturer (OEM) recommendations, statistical failure records, requirements of codes, legislation, or regulations within a jurisdiction, expert opinion, maintenance that has already been conducted on similar equipment, or measured values and performance indications. DoD has determined the time intervals are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time intervals to ensure the organization being inspected/assessed defines time intervals to perform preventive maintenance on organization-defined information system components. DoD has determined the time intervals are not appropriate to define at the Enterprise level.'),
('002901','draft','2013-07-22','DISA FSO','policy','The organization performs predictive maintenance on organization-defined information system components at organization-defined intervals.','MA-6(2).1','The organization being inspected/assessed performs predictive maintenance on information system components defined in MA-6 (2), CCI 2902 at time intervals defined in MA-6 (2), CCI 2903. The organization must maintain schedules and records of predictive maintenance.','The organization conducting the inspection/assessment obtains and examines schedules and records of predictive maintenance to ensure the organization being inspected/assessed performs predictive maintenance on information system components defined in MA-6 (2), CCI 2902 at time intervals defined in MA-6 (2), CCI 2903.'),
('002902','draft','2013-07-22','DISA FSO','policy','The organization defines information system components on which to perform predictive maintenance.','MA-6(2).2','The organization being inspected/assessed defines and documents information system components on which to perform predictive maintenance. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines information system components on which to perform predictive maintenance. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('002903','draft','2013-07-22','DISA FSO','policy','The organization defines time intervals at which to perform predictive maintenance on organization-defined information system components.','MA-6(2).3','The organization being inspected/assessed defines and documents time intervals to perform predictive maintenance on organization-defined information system components. DoD has determined the time intervals are not appropriate to define at the Enterprise level','The organization conducting the inspection/assessment obtains and examines the documented time intervals to ensure the organization being inspected/assessed defines time intervals to perform predictive maintenance on organization-defined information system components. DoD has determined the time intervals are not appropriate to define at the Enterprise level.');
INSERT INTO `cci` VALUES ('002904','draft','2013-07-22','DISA FSO','policy','The organization employs automated mechanisms to transfer predictive maintenance data to a computerized maintenance management system.','MA-6(3).1','The organization being inspected/assessed documents and implements automated mechanisms to transfer predictive maintenance data to a computerized maintenance management system.','The organization conducting the inspection/assessment obtains and examines documentation of automated mechanisms to ensure the organization being inspected/assessed employs automated mechanisms to transfer predictive maintenance data to a computerized maintenance management system.'),
('002905','draft','2013-08-12','DISA FSO','policy','The organization employs automated mechanisms to schedule, conduct, and document maintenance.','MA-2(2).2','The organization being inspected/assessed documents and implements automated mechanisms to schedule, conduct, and document maintenance.','The organization conducting the inspection/assessment obtains and examines the documentation of automated mechanisms to ensure the organization being inspected/assessed employs automated mechanisms to schedule, conduct, and document maintenance.'),
('002906','draft','2013-08-13','DISA FSO','policy','The organization defines the vulnerability scanning activities in which the information system implements privileged access authorization to organization-identified information system components.','RA-5(5).3','The organization being inspected/assessed defines and documents the vulnerability scanning activities in which the information system implements privileged access authorization to organization-identified information system components. DoD has determined the vulnerability scanning activities are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented vulnerability scanning activities to ensure the organization being inspected/assessed defines the vulnerability scanning activities in which the information system implements privileged access authorization to organization-identified information system components. DoD has determined the vulnerability scanning activities are not appropriate to define at the Enterprise level.'),
('002907','draft','2013-08-22','DISA FSO','policy','The organization defines the system mode to be invoked, such as a full system shutdown, a partial system shutdown, or a degraded operational mode with limited mission/business functionality available, in the event of organization-defined audit failures.','AU-5(4).3','The organization being inspected/assessed defines and documents the system mode to be invoked. Possible examples of system modes include a full system shutdown, a partial system shutdown, or a degraded operational mode with limited mission/business functionality available.','The organization conducting the inspection/assessment obtains and examines the documented system mode to ensure the organization being inspected/assessed defines the system mode to be invoked.'),
('002908','draft','2013-08-27','DISA FSO','policy','The organization defines the personnel or roles to whom a physical and environmental protection policy is disseminated.','PE-1.1','DoD has defined the roles as organizational personnel with physical and environmental protection responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as organizational personnel with physical and environmental protection responsibilities.'),
('002909','draft','2013-08-27','DISA FSO','policy','The organization defines the personnel or roles to whom the physical and environmental protection procedures are disseminated.','PE-1.2','DoD has defined the roles as organizational personnel with physical and environmental protection responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as organizational personnel with physical and environmental protection responsibilities.'),
('002910','draft','2013-08-27','DISA FSO','policy','The organization approves a list of individuals with authorized access to the facility where the information system resides.','PE-2.2','The organization being inspected/assessed formally approves a list of individuals currently authorized to access the facility where the information system resides.','The organization conducting the inspection/assessment obtains and examines the list of individuals currently authorized to access the facility where the information system resides and ensures it is formally approved.'),
('002911','draft','2013-08-27','DISA FSO','policy','The organization maintains a list of individuals with authorized access to the facility where the information system resides.','PE-2.3','The organization being inspected/assessed maintains a list of individuals currently authorized to access the facility where the information system resides.','The organization conducting the inspection/assessment obtains and examines the list of individuals to ensure the organization being inspected/assessed maintains a list of individuals currently authorized to access the facility where the information system resides.'),
('002912','draft','2013-08-27','DISA FSO','policy','The organization defines a list of acceptable forms of identification for visitor access to the facility where the information system resides.','PE-2(2).2','The organization being inspected/assessed defines and documents a list of acceptable forms of identification for visitor access to the facility where the information system resides. DoD has determined the list of acceptable forms of identification are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented a list of acceptable forms of identification to ensure the organization being inspected/assessed defines a list of acceptable forms of identification for visitor access to the facility where the information system resides. DoD has determined the list of acceptable forms of identification are not appropriate to define at the Enterprise level.'),
('002913','draft','2013-08-27','DISA FSO','policy','The organization restricts unescorted access to the facility where the information system resides to personnel with one or more of the following: security clearances for all information contained within the system; formal access authorizations for all information contained within the system; need for access to all information contained within the system; organization-defined credentials.','PE-2(3).1','The organization being inspected/assessed defines and documents the requirements that must be met before unescorted access to the facility where the information system resides will be granted. These requirements will be selected from: security clearances for all information contained within the system; formal access authorizations for all information contained within the system; need for access to all information contained within the system; credentials defined in PE-2 (3), CCI 2914. This requirement must be documented within the organization\'s physical security policy.','The organization conducting the inspection/assessment obtains and examines the physical security policy to ensure the organization being inspected/assessed has selected one or more of the physical security requirements that must be met before unescorted access to the facility where the information system resides is granted'),
('002914','draft','2013-08-27','DISA FSO','policy','The organization defines the credentials required for personnel to have unescorted access to the facility where the information system resides.','PE-2(3).2','The organization being inspected/assessed defines and documents the credentials required for personnel to have unescorted access to the facility where the information system resides. DoD has determined the credentials are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented credentials to ensure the organization being inspected/assessed defines the credentials required for personnel to have unescorted access to the facility where the information system resides. DoD has determined the credentials are not appropriate to define at the Enterprise level.'),
('002915','draft','2013-08-27','DISA FSO','policy','The organization defines the entry/exit points to the facility where the information system resides.','PE-3.2','The organization being inspected/assessed defines and documents the entry/exit points to the facility where the information system resides. DoD has determined the entry/exit points are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented entry/exit points and inspects the facility to ensure that all entry/exit points are documented. DoD has determined the entry/exit points are not appropriate to define at the Enterprise level.'),
('002916','draft','2013-08-27','DISA FSO','policy','The organization defines the physical access control systems/devices or guards that control ingress/egress to the facility where the information system resides.','PE-3.5','The organization being inspected/assessed defines and documents the physical access control systems/devices or guards that control ingress/egress to the facility. DoD has determined the physical access control systems/devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented physical access control systems/devices to ensure the organization being inspected/assessed defines the physical access control systems/devices or guards that control ingress/egress to the facility. DoD has determined the physical access control systems/devices are not appropriate to define at the Enterprise level.'),
('002917','draft','2013-08-27','DISA FSO','policy','The organization maintains physical access audit logs for organization-defined entry/exit points to the facility where the information system resides.','PE-3.6','The organization being inspected/assessed maintains physical access audit logs for entry/exit points defined in PE-3, CCI 2918.','The organization conducting the inspection/assessment obtains and examines the physical access audit logs and compares the logged entry with known access to those entry points to ensure the organization being inspected/assessed maintains physical access audit logs for entry/exit points defined in PE-3, CCI 2918. Instances of access that will be compared with the audit logs include, at a minimum, access as part of the inspection/assessment. Comparison of other entry/exit events required elsewhere in system documentation that would have occurred before the inspection/assessment such as daily checks and scheduled maintenance are strongly encouraged and help to establish a history of compliance/non-compliance.'),
('002918','draft','2013-08-27','DISA FSO','policy','The organization defines entry/exit points to the facility where the information system resides that require physical access audit logs be maintained.','PE-3.7','The organization being inspected/assessed defines and documents entry/exit points that require physical access audit logs be maintained. DoD has determined the entry/exit points are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented entry/exit points to ensure the organization being inspected/assessed defines entry/exit points that require physical access audit logs be maintained. DoD has determined the entry/exit points are not appropriate to define at the Enterprise level.'),
('002919','draft','2013-08-27','DISA FSO','policy','The organization provides organization-defined security safeguards to control access to areas within the facility where the information system resides officially designated as publicly accessible.','PE-3.8','The organization being inspected/assessed provides security safeguards defined in PE-3, CCI 2920 to control access to areas within the facility officially designated as publicly accessible. The organization must document which areas are officially designated as publicly accessible.','The organization conducting the inspection/assessment obtains and examines the documentation of areas officially designated as publicly accessible to ensure the organization being inspected/assessed provides security safeguards defined in PE-3, CCI 2920 to control access to areas within the facility officially designated as publicly accessible.'),
('002920','draft','2013-08-27','DISA FSO','policy','The organization defines security safeguards to control access to areas within the facility where the information system resides officially designated as publicly accessible.','PE-3.9','The organization being inspected/assessed defines and documents security safeguards to control access to areas within the facility officially designated as publicly accessible. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines security safeguards to control access to areas within the facility officially designated as publicly accessible. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002921','draft','2013-08-27','DISA FSO','policy','The organization escorts visitors in the facility where the information system resides during organization-defined circumstances requiring visitor escorts.','PE-3.10','The organization being inspected/assessed documents and implements a process to escort visitors during circumstances defined in PE-3, CCI 2922 requiring visitor escorts.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed escorts visitors during circumstances defined in PE-3, CCI 2922 requiring visitor escorts.'),
('002922','draft','2013-08-27','DISA FSO','policy','The organization defines circumstances requiring visitor escorts in the facility where the information system resides.','PE-3.11','The organization being inspected/assessed defines and documents circumstances requiring visitor escorts. DoD has determined the circumstances are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances to ensure the organization being inspected/assessed defines circumstances requiring visitor escorts. DoD has determined the circumstances are not appropriate to define at the Enterprise level.'),
('002923','draft','2013-08-27','DISA FSO','policy','The organization monitors visitor activity in the facility where the information system resides during organization-defined circumstances requiring visitor monitoring.','PE-3.12','The organization being inspected/assessed documents and implements a process to monitor visitor activity during circumstances defined in PE-3, CCI 2924 requiring visitor monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed monitors visitor activity during circumstances defined in PE-3, CCI 2924 requiring visitor monitoring.'),
('002924','draft','2013-08-27','DISA FSO','policy','The organization defines circumstances requiring visitor monitoring in the facility where the information system resides.','PE-3.13','The organization being inspected/assessed defines and documents circumstances requiring visitor monitoring. DoD has determined the circumstances are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented circumstances to ensure the organization being inspected/assessed defines circumstances requiring visitor monitoring. DoD has determined the circumstances are not appropriate to define at the Enterprise level.'),
('002925','draft','2013-08-27','DISA FSO','policy','The organization defines the physical access devices to inventory.','PE-3.17','DoD has defined the physical access devices as minimally keys or any other physical token used to gain access.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the physical access devices as minimally keys or any other physical token used to gain access.'),
('002926','draft','2013-08-27','DISA FSO','policy','The organization defines the physical spaces containing one or more components of the information system that require physical access authorizations and controls at the facility where the information system resides.','PE-3(1).2','The organization being inspected/assessed defines and documents the physical spaces containing one or more components of the information system that require physical access authorizations and controls at the facility. DoD has determined the physical spaces are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented physical spaces to ensure the organization being inspected/assessed defines the physical spaces containing one or more components of the information system that require physical access authorizations and controls at the facility. DoD has determined the physical spaces are not appropriate to define at the Enterprise level.'),
('002927','draft','2013-08-27','DISA FSO','policy','The organization defines the frequency with which to perform security checks at the physical boundary of the facility or information system for unauthorized exfiltration of information or removal of information system components.','PE-3(2).2','DoD has defined the frequency as at a minimum, annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as at a minimum, annually.'),
('002928','draft','2013-08-27','DISA FSO','policy','The organization defines security safeguards to detect and prevent physical tampering or alteration of organization-defined hardware components within the information system.','PE-3(5).2','The organization being inspected/assessed defines and documents security safeguards to detect and prevent physical tampering or alteration of organization-defined hardware components within the information system. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines security safeguards to detect and prevent physical tampering or alteration of organization-defined hardware components within the information system. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002929','draft','2013-08-27','DISA FSO','policy','The organization defines hardware components within the information system for which to employ organization-defined security safeguards to detect and prevent physical tampering or alteration.','PE-3(5).3','The organization being inspected/assessed defines and documents hardware components within the information system to employ organization-defined security safeguards to detect and prevent physical tampering or alteration. DoD has determined the hardware components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented hardware components to ensure the organization being inspected/assessed defines hardware components within the information system to employ organization-defined security safeguards to detect and prevent physical tampering or alteration. DoD has determined the hardware components are not appropriate to define at the Enterprise level.'),
('002930','draft','2013-08-27','DISA FSO','policy','The organization defines information system distribution and transmission lines within organizational facilities to control physical access to using organization-defined security safeguards.','PE-4.2','The organization being inspected/assessed defines and documents information system distribution and transmission lines within organizational facilities to control physical access using organization-defined security safeguards. If transmission lines carry classified information, a protected distribution system (PDS) must be used to transmit unencrypted classified information through an area of lesser classification or control. For additional information, see NSTISSI No. 7003. DoD has determined the information system distribution and transmission lines are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system distribution and transmission lines to ensure the organization being inspected/assessed defines information system distribution and transmission lines within organizational facilities to control physical access using organization-defined security safeguards. DoD has determined the information system distribution and transmission lines are not appropriate to define at the Enterprise level.'),
('002931','draft','2013-08-27','DISA FSO','policy','The organization defines security safeguards to control physical access to organization-defined information system distribution and transmission lines within organizational facilities.','PE-4.3','The organization being inspected/assessed defines and documents security safeguards to control physical access to organization-defined information system distribution and transmission lines within organizational facilities. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines security safeguards to control physical access to organization-defined information system distribution and transmission lines within organizational facilities. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('002932','draft','2013-08-27','DISA FSO','policy','The organization controls physical access to output from organization-defined output devices.','PE-5(1).1','The organization being inspected/assessed documents and implements a process to control physical access to output from output devices defined in PE-5 (1), CCI 2933.','The organization conducting the inspection/assessment obtains and examines the documented process and inspects the physical access controls surrounding a sampling of output devices to ensure the organization being inspected/assessed controls physical access to output from output devices defined in PE-5 (1), CCI 2933.'),
('002933','draft','2013-08-27','DISA FSO','policy','The organization defines output devices for which physical access to output is controlled.','PE-5(1).2','The organization being inspected/assessed defines and documents output devices for which physical access to output is controlled. DoD has determined the output devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented output devices to ensure the organization being inspected/assessed defines output devices for which physical access to output is controlled. DoD has determined the output devices are not appropriate to define at the Enterprise level.'),
('002934','draft','2013-08-27','DISA FSO','policy','The organization ensures that only authorized individuals receive output from organization-defined output devices.','PE-5(1).3','The organization being inspected/assessed documents and implements a process to ensure that only authorized individuals receive output from the output device defined in PE-5 (1), CCI 2933.','The organization conducting the inspection/assessment obtains and examines the documented process and inspects the physical access controls surrounding a sampling of output devices to ensure the organization being inspected/assessed ensures that only authorized individuals receive output from the output device defined in PE-5 (1), CCI 2933.'),
('002935','draft','2013-08-27','DISA FSO','policy','The information system controls physical access to output from organization-defined output devices.','PE-5(2).1','The organization being inspected/assessed configures the information system to control physical access to output from output devices defined in PE-5 (1), CCI 2933. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2935.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to control physical access to output from output devices defined in PE-5 (1), CCI 2933. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2935.'),
('002936','draft','2013-08-27','DISA FSO','policy','The information system links individual identity to receipt of output from organization-defined output devices.','PE-5(2).2','The organization being inspected/assessed configures the information system to link individual identity to receipt of the output from the output device defined in PE-5 (1), CCI 2933. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 2936.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to link individual identity to receipt of the output from the output device defined in PE-5 (1), CCI 2933. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 2936.'),
('002937','draft','2013-08-27','DISA FSO','policy','The organization marks organization-defined information system output devices indicating the appropriate security marking of the information permitted to be output from the device.','PE-5(3).1','The organization being inspected/assessed marks all devices if the organizational facility contains classified information indicating the appropriate security marking of the information permitted to be output from the device. DoD has defined the information system output devices as all devices if the organizational facility contains classified information.','The organization conducting the inspection/assessment inspects a sampling of information system components to ensure the organization being inspected/assessed marks all devices if the organizational facility contains classified information indicating the appropriate security marking of the information permitted to be output from the device. DoD has defined the information system output devices as all devices if the organizational facility contains classified information.'),
('002938','draft','2013-08-27','DISA FSO','policy','The organization defines the information system output devices marked indicating the appropriate security marking of the information permitted to be output from the device.','PE-5(3).2','DoD has defined the information system output devices as all devices if the organizational facility contains classified information.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the information system output devices as all devices if the organizational facility contains classified information.'),
('002939','draft','2013-08-27','DISA FSO','policy','The organization monitors physical access to the facility where the information system resides to detect and respond to physical security incidents.','PE-6.1','The organization being inspected/assessed will implement monitoring procedures to ensure physical access intrusion alarms and surveillance equipment are actively monitored to detect and respond to all physical access security incidents.','The organization conducting the inspection/assessment obtains and examines the inspected organization\'s monitoring procedures addressing physical access monitoring. Organizational personnel with physical access monitoring responsibilities are to be interviewed. The objective of the reviews and interviews is to validate the organization is actively monitoring its physical access intrusion alarms and surveillance equipment to detect and respond to all physical access security incidents.'),
('002940','draft','2013-08-27','DISA FSO','policy','The organization reviews physical access logs upon occurrence of organization-defined events or potential indications of events.','PE-6.2','The organization being inspected/assessed documents and implements a process to review physical access logs upon occurrence of events or potential indications of events defined in PE-6, CCI 2941. The organization must maintain records of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of reviews to ensure the organization being inspected/assessed reviews physical access logs upon occurrence of events or potential indications of events defined in PE-6, CCI 2941.'),
('002941','draft','2013-08-27','DISA FSO','policy','The organization defines events or potential indications of events requiring review of physical access logs.','PE-6.3','The organization being inspected/assessed defines and documents events or potential indications of events requiring review of physical access logs. DoD has determined the events or potential indications of events are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented events or potential indications of events to ensure the organization being inspected/assessed defines events or potential indications of events requiring review of physical access logs. DoD has determined the events or potential indications of events are not appropriate to define at the Enterprise level.'),
('002942','draft','2013-08-27','DISA FSO','policy','The organization employs automated mechanisms to recognize organization-defined classes/types of intrusions.','PE-6(2).1','The organization being inspected/assessed implements automated mechanisms to recognize classes/types of intrusions defined in PE-6 (2), CCI 2943.','The organization conducting the inspection/assessment obtains and examines hardware/software lists and/or any other documentation showing the use of automated intrusion detection systems to ensure the organization being inspected/assessed implements automated mechanisms to recognize classes/types of intrusions defined in PE-6 (2), CCI 2943.'),
('002943','draft','2013-08-27','DISA FSO','policy','The organization defines classes/types of intrusions to recognize using automated mechanisms.','PE-6(2).2','The organization being inspected/assessed defines and documents classes/types of intrusions to recognize using automated mechanisms. DoD has determined the classes/types of intrusions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented classes/types of intrusion to ensure the organization being inspected/assessed defines classes/types of intrusions to recognize using automated mechanisms. DoD has determined the classes/types of intrusions are not appropriate to define at the Enterprise level.'),
('002944','draft','2013-08-27','DISA FSO','policy','The organization employs automated mechanisms to initiate organization-defined response actions to organization-defined classes/types of intrusions.','PE-6(2).3','The organization being inspected/assessed implements automated mechanisms to initiate response actions defined in PE-6 (2), CCI 2945 to classes/types of intrusions defined in PE-6 (2), CCI 2943.','The organization conducting the inspection/assessment obtains and examines hardware/software lists and/or any other documentation showing the use of automated intrusion detection systems to ensure the organization being inspected/assessed implements automated mechanisms to initiate response actions defined in PE-6 (2), CCI 2945 to classes/types of intrusions defined in PE-6 (2), CCI 2943.'),
('002945','draft','2013-08-27','DISA FSO','policy','The organization defines response actions to initiate when organization-defined classes/types of intrusions are recognized.','PE-6(2).4','The organization being inspected/assessed defines and documents response actions to initiate when organization-defined classes/types of intrusions are recognized. DoD has determined the response actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented response actions to ensure the organization being inspected/assessed defines response actions to initiate when organization-defined classes/types of intrusions are recognized. DoD has determined the response actions are not appropriate to define at the Enterprise level.'),
('002946','draft','2013-08-27','DISA FSO','policy','The organization employs video surveillance of organization-defined operational areas.','PE-6(3).1','The organization being inspected/assessed documents and implements video surveillance of operational areas defined in PE-6 (3), CCI 2947.','The organization conducting the inspection/assessment obtains and examines the documentation of video surveillance a sampling of recorded video surveillance to ensure the organization being inspected/assessed employs video surveillance of operational areas defined in PE-6 (3), CCI 2947.'),
('002947','draft','2013-08-27','DISA FSO','policy','The organization defines the operational areas in which to employ video surveillance.','PE-6(3).2','The organization being inspected/assessed defines and documents the operational areas to employ video surveillance. DoD has determined the operational areas are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented operational areas to ensure the organization being inspected/assessed defines the operational areas to employ video surveillance. DoD has determined the operational areas are not appropriate to define at the Enterprise level.'),
('002948','draft','2013-08-27','DISA FSO','policy','The organization retains video surveillance recordings for an organization-defined time period.','PE-6(3).3','The organization being inspected/assessed documents and implements a process to retain video surveillance recordings for at a minimum 90 days. DoD has defined the time period as at a minimum 90 days.','The organization conducting the inspection/assessment obtains and examines the documented process and a sampling of recordings from within 90 days to ensure the organization being inspected/assessed retains video surveillance recordings for at a minimum 90 days. DoD has defined the time period as at a minimum 90 days.'),
('002949','draft','2013-08-27','DISA FSO','policy','The organization defines the time period to retain video surveillance recordings.','PE-6(3).4','DoD has defined the time period as at a minimum 90 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as at a minimum 90 days.'),
('002950','draft','2013-08-27','DISA FSO','policy','The organization monitors physical access to the information system in addition to the physical access monitoring of the facility as organization-defined physical spaces containing one or more components of the information system.','PE-6(4).1','The organization being inspected/assessed documents and implements a process to monitor physical access to the information system in addition to the physical access monitoring of the facility as physical spaces containing one or more components of the information system defined in PE-6 (4), CCI 2951. The organization must maintain records of monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of monitoring to ensure the organization being inspected/assessed monitors physical access to the information system in addition to the physical access monitoring of the facility as physical spaces containing one or more components of the information system defined in PE-6 (4), CCI 2951.'),
('002951','draft','2013-08-27','DISA FSO','policy','The organization defines physical spaces containing one or more components of the information system in which physical access is monitored.','PE-6(4).2','The organization being inspected/assessed defines and documents physical spaces containing one or more components of the information system in which physical access is monitored. DoD has determined the physical spaces are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented physical spaces to ensure the organization being inspected/assessed defines physical spaces containing one or more components of the information system in which physical access is monitored. DoD has determined the physical spaces are not appropriate to define at the Enterprise level.'),
('002952','draft','2013-08-27','DISA FSO','policy','The organization defines the time period to maintain visitor access records to the facility where the information system resides.','PE-8.2','DoD has defined the time period as at least one year.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as at least one year.'),
('002953','draft','2013-08-27','DISA FSO','policy','The organization employs redundant power cabling paths that are physically separated by an organization-defined distance.','PE-9(1).1','The organization being inspected/assessed employs redundant power cabling paths that are physically separated by the distance defined in PE-9 (1), CCI 2954.','The organization conducting the inspection/assessment obtains and examines cabling diagrams or, if unavailable, inspects power cabling configuration to ensure the organization being inspected/assessed employs redundant power cabling paths that are physically separated by the distance defined in PE-9 (1), CCI 2954.'),
('002954','draft','2013-08-27','DISA FSO','policy','The organization defines the distance by which to physically separate redundant power cabling paths.','PE-9(1).2','The organization being inspected/assessed defines and documents the distance to physically separate redundant power cabling paths. DoD has determined the distance is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented distance to ensure the organization being inspected/assessed defines the distance to physically separate redundant power cabling paths. DoD has determined the distance is not appropriate to define at the Enterprise level.'),
('002955','draft','2013-08-29','DISA FSO','policy','The organization provides a short-term uninterruptible power supply to facilitate an orderly shutdown of the information system and/or transition of the information system to long-term alternate power in the event of a primary power source loss.','PE-11.1','The organization being inspected/assessed implements an uninterruptible power supply with sufficient capacity to support orderly shutdown of the system or transition the system to long-term alternate power in the event of a primary power source loss.','The organization conducting the inspection/assessment obtains and examines documentation identifying the capacity of the implemented uninterruptible power supply, documentation identifying the power requirements of the system, and documentation identifying the contingency plan in the event of primary power source loss to ensure the organization being inspected/assessed provides uninterruptible power supply with sufficient capacity to support orderly shutdown of the system or transition the system to long-term alternate power in the event of a primary power source loss.'),
('002956','draft','2013-08-29','DISA FSO','policy','The organization provides a long-term alternate power supply for the information system that is self-contained.','PE-11(2).1','The organization being inspected/assessed implements a long-term alternate power supply for the information system that is self-contained.','The organization conducting the inspection/assessment obtains and examines documentation identifying the implemented alternate power supply to ensure the organization being inspected/assessed implements a long-term alternate power supply for the information system that is self-contained.'),
('002957','draft','2013-08-29','DISA FSO','policy','The organization provides a long-term alternate power supply for the information system that is not reliant on external power generation.','PE-11(2).2','The organization being inspected/assessed implements a long-term alternate power supply for the information system that is not reliant on external power generation.','The organization conducting the inspection/assessment obtains and examines documentation identifying the implemented alternate power supply to ensure the organization being inspected/assessed implements a long-term alternate power supply for the information system that is not reliant on external power generation.'),
('002958','draft','2013-08-29','DISA FSO','policy','The organization provides a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability or full operational capability in the event of an extended loss of the primary power source.','PE-11(2).3','The organization being inspected/assessed implements a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability or full operational capability in the event of an extended loss of the primary power source.','The organization conducting the inspection/assessment obtains and examines documentation identifying the implemented alternate power supply to ensure the organization being inspected/assessed implements a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability or full operational capability in the event of an extended loss of the primary power source.'),
('002959','draft','2013-08-29','DISA FSO','policy','The organization provides emergency lighting for all areas within the facility supporting essential missions.','PE-12(1).1','The organization being inspected/assessed implements emergency lighting for all areas within the facility supporting essential missions.','The organization conducting the inspection/assessment inspects areas within the facility supporting essential missions to ensure emergency lighting is implemented.'),
('002960','draft','2013-08-29','DISA FSO','policy','The organization provides emergency lighting for all areas within the facility supporting essential business functions.','PE-12(1).2','The organization being inspected/assessed implements emergency lighting for all areas within the facility supporting essential business functions.','The organization conducting the inspection/assessment inspects areas within the facility supporting essential business functions to ensure emergency lighting is implemented.'),
('002961','draft','2013-08-29','DISA FSO','policy','The organization employs fire detection devices/systems for the information system that activate automatically.','PE-13(1).1','The organization being inspected/assessed documents and implements fire detection devices/systems for the information system that activate automatically.','The organization conducting the inspection/assessment obtains and examines the documented evidence of fire detection devices/systems to ensure the organization being inspected/assessed employs fire detection devices/systems for the information system that activate automatically.'),
('002962','draft','2013-08-29','DISA FSO','policy','The organization employs fire detection devices/systems for the information system that automatically activate to notify organization-defined personnel or roles and organization-defined emergency responders in the event of a fire.','PE-13(1).2','The organization being inspected/assessed documents and implements fire detection devices/systems for the information system that automatically activate to notify personnel or roles defined in PE-13 (1), CCI 2963 and emergency responders defined in PE-13 (1), CCI 2964 in the event of a fire.','The organization conducting the inspection/assessment obtains and examines the documented evidence of fire detection devices/systems to ensure the organization being inspected/assessed employs fire detection devices/systems for the information system that automatically activate to notify personnel or roles defined in PE-13 (1), CCI 2963 and emergency responders defined in PE-13 (1), CCI 2964 in the event of a fire.'),
('002963','draft','2013-08-29','DISA FSO','policy','The organization defines the personnel or roles to be notified in the event of a fire.','PE-13(1).3','The organization being inspected/assessed defines and documents the personnel or roles to be notified in the event of a fire. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to be notified in the event of a fire. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002964','draft','2013-08-29','DISA FSO','policy','The organization defines the emergency responders to be notified in the event of a fire.','PE-13(1).4','The organization being inspected/assessed defines and documents the emergency responders to be notified in the event of a fire. DoD has determined the emergency responders are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented emergency responders to ensure the organization being inspected/assessed defines the emergency responders to be notified in the event of a fire. DoD has determined the emergency responders are not appropriate to define at the Enterprise level.'),
('002965','draft','2013-08-29','DISA FSO','policy','The organization employs fire suppression devices/systems for the information system that provide automatic notification of any activation to organization-defined personnel or roles and organization-defined emergency responders.','PE-13(2).1','The organization being inspected/assessed documents and implements fire suppression devices/systems for the information system that provide automatic notification of any activation to organization-defined personnel or roles and organization defined emergency responders.','The organization conducting the inspection/assessment obtains and examines the documented evidence of fire detection devices/systems to ensure the organization being inspected/assessed employs fire suppression devices/systems for the information system that provide automatic notification of any activation to organization-defined personnel or roles and organization defined emergency responders.'),
('002966','draft','2013-08-29','DISA FSO','policy','The organization defines the personnel or roles to be automatically notified of any activation of fire suppression devices/systems for the information system.','PE-13(2).2','The organization being inspected/assessed defines and documents the personnel or roles to be automatically notified of any activation of fire suppression devices/systems for the information system. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to be automatically notified of any activation of fire suppression devices/systems for the information system. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002967','draft','2013-08-29','DISA FSO','policy','The organization defines the emergency responders to be automatically notified of any activation of fire suppression devices/systems for the information system.','PE-13(2).3','The organization being inspected/assessed defines and documents the emergency responders to be automatically notified of any activation of fire suppression devices/systems for the information system. DoD has determined the emergency responders are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented emergency responders to ensure the organization being inspected/assessed defines the emergency responders to be automatically notified of any activation of fire suppression devices/systems for the information system. DoD has determined the emergency responders are not appropriate to define at the Enterprise level.'),
('002968','draft','2013-08-29','DISA FSO','policy','The organization ensures that the facility undergoes, on an organization-defined frequency, fire protection inspections by authorized and qualified inspectors.','PE-13(4).1','The organization being inspected/assessed implements a process to undergo fire protection inspections by authorized and qualified inspectors annually. The organization must maintain a record of inspections. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the record of inspections to ensure the organization being inspected/assessed implements a process to undergo fire protection inspections by authorized and qualified inspectors annually. DoD has defined the frequency as annually.'),
('002969','draft','2013-08-29','DISA FSO','policy','The organization defines a frequency with which the facility undergoes fire protection inspections.','PE-13(4).2','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('002970','draft','2013-08-29','DISA FSO','policy','The organization resolves deficiencies identified during facility fire protection inspections within an organization-defined time period.','PE-13(4).3','The organization being inspected/assessed resolves deficiencies identified during facility fire protection inspections within 60 days. DoD has defined the time period as 60 days.','The organization conducting the inspection/assessment obtains and examines past facility fire protection inspection reports and inspects the facility to ensure all deficiencies identified are resolved in 60 days. DoD has defined the time period as 60 days.'),
('002971','draft','2013-08-29','DISA FSO','policy','The organization defines the time period within which to resolve deficiencies identified during facility fire protection inspections.','PE-13(4).4','DoD has defined the time period as 60 days.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as 60 days.'),
('002972','draft','2013-08-29','DISA FSO','policy','The organization employs automated mechanisms to detect the presence of water in the vicinity of the information system and alerts organization-defined personnel or roles.','PE-15(1).1','The organization being inspected/assessed documents and implements automated mechanisms to detect the presence of water in the vicinity of the information system and alerts personnel or roles defined in PE-15 (1), CCI 2973.','The organization conducting the inspection/assessment obtains and examines documentation identifying water detection mechanisms to ensure the organization being inspected/assessed implements automated mechanisms to detect the presence of water in the vicinity of the information system and alerts personnel or roles defined in PE-15 (1), CCI 2973.'),
('002973','draft','2013-08-29','DISA FSO','policy','The organization defines the personnel or roles to be alerted when automated mechanisms detect the presence of water in the vicinity of the information system.','PE-15(1).2','The organization being inspected/assessed defines and documents the personnel or roles to be alerted when automated mechanisms detect the presence of water in the vicinity of the information system. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to be alerted when automated mechanisms detect the presence of water in the vicinity of the information system. DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('002974','draft','2013-08-29','DISA FSO','policy','The organization defines types of information system components to authorize, monitor, and control entering and exiting the facility and to maintain records.','PE-16.5','DoD has defined the types of information system components as all system components.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the types of information system components as all system components.'),
('002975','draft','2013-08-29','DISA FSO','policy','The organization defines security controls to employ at alternate work sites.','PE-17.2','The organization being inspected/assessed defines and documents security controls to employ at alternate work sites, which must include all applicable building and safety codes for the information system\'s environment DoD has determined the security controls are not appropriate to define at the Enterprise level, but must include all applicable building and safety codes for the information system\'s environment.','The organization conducting the inspection/assessment obtains and examines the documented security controls to ensure the organization being inspected/assessed defines security controls to employ at alternate work sites, which must include all applicable building and safety codes for the information system\'s environment. DoD has determined the security controls are not appropriate to define at the Enterprise level, but must include all applicable building and safety codes for the information system\'s environment.'),
('002976','draft','2013-08-29','DISA FSO','policy','The organization defines physical and environmental hazards that could cause potential damage to information system components within the facility.','PE-18.3','The organization being inspected/assessed defines and documents physical and environmental hazards that could cause potential damage to information system components within the facility. DoD has determined the physical and environmental hazards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented physical and environmental hazards to ensure the organization being inspected/assessed defines physical and environmental hazards that could cause potential damage to information system components within the facility. DoD has determined the physical and environmental hazards are not appropriate to define at the Enterprise level.'),
('002977','draft','2013-08-29','DISA FSO','policy','The organization plans the location or site of the facility where the information system resides with regard to physical and environmental hazards.','PE-18(1).1','The organization being inspected/assessed plans the location or site of the facility where the information system resides with regard to physical and environmental hazards. The organization must document the rationale for planning the location or site of the facility.','The organization conducting the inspection/assessment obtains and examines the documented rationale to ensure the organization being inspected/assessed plans the location or site of the facility where the information system resides with regard to physical and environmental hazards.'),
('002978','draft','2013-08-29','DISA FSO','policy','The organization considers the physical and environmental hazards in its risk mitigation strategy for existing facilities.','PE-18(1).2','The organization being inspected/assessed considers the physical and environmental hazards in its risk mitigation strategy for existing facilities. The organization must document the risk assessment.','The organization conducting the inspection/assessment obtains and examines the physical and environmental risk assessment to ensure the organization being inspected/assessed considers the physical and environmental hazards in its risk mitigation strategy for existing facilities.'),
('002979','draft','2013-08-29','DISA FSO','policy','The organization employs organization-defined asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas.','PE-20.1','The organization being inspected/assessed implements asset location technologies defined in PE-20, CCI 2980 to track and monitor the location and movement of assets defined in PE-20, CCI 2981 within controlled areas defined in PE-20, CCI 2982.','The organization conducting the inspection/assessment obtains and examines documentation reflecting asset location technologies in use to ensure the organization being inspected/assessed implements asset location technologies defined in PE-20, CCI 2980 to track and monitor the location and movement of assets defined in PE-20, CCI 2981 within controlled areas defined in PE-20, CCI 2982.'),
('002980','draft','2013-08-29','DISA FSO','policy','The organization defines asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas.','PE-20.2','The organization being inspected/assessed defines and documents asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas. DoD has determined the asset location technologies are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented asset location technologies to ensure the organization being inspected/assessed defines asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas. DoD has determined the asset location technologies are not appropriate to define at the Enterprise level.'),
('002981','draft','2013-08-29','DISA FSO','policy','The organization defines the assets within the organization-defined controlled areas which are to be tracked and monitored for their location and movement.','PE-20.3','The organization being inspected/assessed defines and documents the assets within the organization-defined controlled areas which are to be tracked and monitored for their location and movement. DoD has determined the assets are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented assets to ensure the organization being inspected/assessed defines the assets within the organization-defined controlled areas which are to be tracked and monitored for their location and movement. DoD has determined the assets are not appropriate to define at the Enterprise level.'),
('002982','draft','2013-08-29','DISA FSO','policy','The organization defines controlled areas where the location and movement of organization-defined assets are tracked and monitored.','PE-20.4','The organization being inspected/assessed defines and documents controlled areas that the location and movement of organization-defined assets are tracked and monitored. DoD has determined the controlled areas are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented controlled areas to ensure the organization being inspected/assessed defines controlled areas that the location and movement of organization-defined assets are tracked and monitored. DoD has determined the controlled areas are not appropriate to define at the Enterprise level.'),
('002983','draft','2013-08-29','DISA FSO','policy','The organization ensures that asset location technologies are employed in accordance with applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance.','PE-20.5','The organization being inspected/assessed identifies and documents any federal laws, Executive Orders, directives, regulations, policies, standards, and guidance applicable to the asset location technologies in use. In particular, the organization identifies any requirements to protect the privacy of personnel transporting assets being tracked. The organization documents a process to meet the applicable requirements in their documentation of asset tracking technologies (PE-20, CCI 2980).','The organization conducting the inspection/assessment obtains and examines the documented list of any federal laws, Executive Orders, directives, regulations, policies, standards, and guidance applicable to the asset location technologies in use, as well as the documentation of asset tracking technologies per PE-20, CCI 2980, to ensure that the organization being inspected/assessed identifies any requirements (particularly privacy requirements) applicable to the asset tracking methodologies in use, and to ensure that the organization implements a process to meet those identified requirements.'),
('002984','draft','2013-08-29','DISA FSO','policy','The organization develops an organization-wide information security program plan that reflects coordination among organizational entities responsible for the different aspects of information security (i.e., technical, physical, personnel, cyber-physical).','PM-1.5','DoDI 8500.01 and the Knowledge Service meet the requirement for this CCI; individual organizations and system owners must provide documentation of common control implementation in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002985','draft','2013-08-29','DISA FSO','policy','The organization disseminates an organization-wide information security program plan that provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements.','PM-1.2','DoD disseminates DoDI 8500.01 organization-wide via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) and the Knowledge Service is available via: https://rmfks.osd.mil.\n\nDoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002986','draft','2013-08-29','DISA FSO','policy','The organization disseminates an organization-wide information security program plan that includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PM-1.3','DoD disseminates DoDI 8500.01 organization-wide via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) and the Knowledge Service is available via: https://rmfks.osd.mil.\n\nDoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002987','draft','2013-08-29','DISA FSO','policy','The organization disseminates an organization-wide information security program plan that reflects coordination among organizational entities responsible for the different aspects of information security (i.e., technical, physical, personnel, cyber-physical).','PM-1.6','DoD disseminates DoDI 8500.01 organization-wide via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) and the Knowledge Service is available via: https://rmfks.osd.mil.\n\nDoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002988','draft','2013-08-29','DISA FSO','policy','The organization disseminates an organization-wide information security program plan that is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.','PM-1.7','DoD disseminates DoDI 8500.01 organization-wide via the DoD Issuances website (http://www.dtic.mil/whs/directives/corres/dir.html) and the Knowledge Service is available via: https://rmfks.osd.mil.\n\nDoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002989','draft','2013-08-29','DISA FSO','policy','The organization protects the information security program plan from unauthorized disclosure.','PM-1.12','DoD documents and implements methods to protect the information security program plan from unauthorized disclosure by marking, labeling, and handling to prevent unauthorized disclosure. DoD ensures that all changes to the information security program plan are approved.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002990','draft','2013-08-29','DISA FSO','policy','The organization protects the information security program plan from unauthorized modification.','PM-1.13','DoD documents and implements methods to protect the information security program plan from unauthorized disclosure by marking, labeling, and handling to prevent unauthorized modification. DoD ensures that all changes to the information security program plan are approved.','DoD components are automatically compliant with this CCI as they are covered at the DoD level by DoDI 8500.01 and the Knowledge Service. If the organization or system owner is utilizing common controls they must be documented in their Security Plan.'),
('002991','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that plans of action and milestones for the security program and associated organizational information systems are developed.','PM-4.2','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to develop a process for plans of action and milestones for the security program.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to develop a process for plans of action and milestones for the security program.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.'),
('002992','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that plans of action and milestones for the security program and associated organizational information systems are reported in accordance with OMB FISMA reporting requirements.','PM-4.4','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to implement a process ensuring that the plans of action and milestones for the security program are reported in accordance with OMB FISMA reporting requirements.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.','DoDI 8510.01 and the Knowledge Service meet the DoD requirements to implement a process ensuring that the plans of action and milestones for the security program are reported in accordance with OMB FISMA reporting requirements.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8510.01 and the Knowledge Service.'),
('002993','draft','2013-08-29','DISA FSO','policy','The organization reviews plans of action and milestones for the security program and associated organization information systems for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-4.5','The organization being inspected/assessed documents and implements a process to review plans of action and milestones for the security program and associated organization information systems for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews plans of action and milestones for the security program and associated organization information systems for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.'),
('002994','draft','2013-08-29','DISA FSO','policy','The organization reviews and updates the risk management strategy in accordance with organization-defined frequency or as required, to address organizational changes.','PM-9.3','DoD Risk Management Framework meets the requirement for a comprehensive organizational risk strategy.\n\nDoD components are automatically compliant with this CCI because they are covered by the DoD Risk Management Framework (DoDI 8510.01).','DoD Risk Management Framework meets the requirement for a comprehensive organizational risk strategy.\n\nDoD components are automatically compliant with this CCI because they are covered by DoD Risk Management Framework (DoDI 8510.01).'),
('002995','draft','2013-08-29','DISA FSO','policy','The organization defines the frequency with which to review and update the risk management strategy to address organizational changes.','PM-9.4','DoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as reviewed annually - updated as appropriate but at least within 10 years of date of issuance.'),
('002996','draft','2013-08-29','DISA FSO','policy','The organization implements an insider threat program that includes a cross-discipline insider threat incident handling team.','PM-12.1','The organization being inspected/assessed documents and implements an insider threat program that includes a cross-discipline insider threat incident handling team.','The organization conducting the inspection/assessment obtains and examines the documented insider threat program to ensure the organization being inspected/assessed implements an insider threat program that includes a cross-discipline insider threat incident handling team.'),
('002997','draft','2013-08-29','DISA FSO','policy','The organization establishes an information security workforce development and improvement program.','PM-13.1','DoD 8570.01-M, \"Information Assurance Workforce Improvement Program\" meets the DoD requirement to establish an information security workforce development and improvement program.\n\nDoD components are automatically complaint with this CCI as they are covered at the DoD level, DoDI 8570.01-M.','DoD 8570.01-M meets the DoD requirement to establish an information security workforce development and improvement program.\n\nDoD components are automatically complaint with this CCI as they are covered at the DoD level, DoDI 8570.01-M.'),
('002998','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security testing activities associated with organizational information systems are developed.','PM-14.1','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security testing activities associated with organizational information systems are developed.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security testing activities associated with organizational information systems are developed.'),
('002999','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security testing activities associated with organizational information systems are maintained.','PM-14.2','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security testing activities associated with organizational information systems are maintained.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security testing activities associated with organizational information systems are maintained.'),
('003000','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security training activities associated with organizational information systems are developed.','PM-14.3','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security training activities associated with organizational information systems are developed.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security training activities associated with organizational information systems are developed.'),
('003001','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security training activities associated with organizational information systems are maintained.','PM-14.4','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security training activities associated with organizational information systems are maintained.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security training activities associated with organizational information systems are maintained.'),
('003002','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems are developed.','PM-14.5','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems are developed.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems are developed.'),
('003003','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems are maintained.','PM-14.6','The organization being inspected/assessed documents and implements a process for conducting security monitoring activities associated with organizational information systems are maintained.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems are maintained.'),
('003004','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security testing associated with organizational information systems continue to be executed in a timely manner.','PM-14.7','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security testing associated with organizational information systems continue to be executed in a timely manner. The organization must maintain records of execution.','The organization conducting the inspection/assessment obtains and examines the documented process as well as records of execution to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security testing associated with organizational information systems continue to be executed in a timely manner.'),
('003005','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security training associated with organizational information systems continue to be executed in a timely manner.','PM-14.8','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security training associated with organizational information systems continue to be executed in a timely manner. The organization must maintain records of execution.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of execution to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security training associated with organizational information systems continue to be executed in a timely manner.'),
('003006','draft','2013-08-29','DISA FSO','policy','The organization implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems continue to be executed in a timely manner.','PM-14.9','The organization being inspected/assessed documents and implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems continue to be executed in a timely manner. The organization must maintain records of execution.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of execution to ensure the organization being inspected/assessed implements a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational information systems continue to be executed in a timely manner.'),
('003007','draft','2013-08-29','DISA FSO','policy','The organization reviews testing plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-14.10','The organization being inspected/assessed documents and implements a process to review testing plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews testing plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.'),
('003008','draft','2013-08-29','DISA FSO','policy','The organization reviews training plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-14.11','The organization being inspected/assessed reviews training plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews training plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.'),
('003009','draft','2013-08-29','DISA FSO','policy','The organization reviews monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-14.12','The organization being inspected/assessed reviews monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions. The organization must maintain a record of reviews.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.'),
('003010','draft','2013-08-29','DISA FSO','policy','The organization establishes and institutionalizes contact with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel.','PM-15.1','The organization being inspected/assessed establishes and institutionalizes contact with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel.','The organization conducting the inspection/assessment obtains and examines artifacts showing contact to ensure the organization being inspected/assessed establishes and institutionalizes contact with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel.'),
('003011','draft','2013-08-29','DISA FSO','policy','The organization establishes and institutionalizes contact with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies.','PM-15.2','The organization being inspected/assessed establishes and institutionalizes contact with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies.','The organization conducting the inspection/assessment obtains and examines artifacts showing contact to ensure the organization being inspected/assessed establishes and institutionalizes contact with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies.'),
('003012','draft','2013-08-29','DISA FSO','policy','The organization establishes and institutionalizes contact with selected groups and associations within the security community to share current security-related information including threats, vulnerabilities, and incidents.','PM-15.3','The organization being inspected/assessed establishes and institutionalizes contact with selected groups and associations within the security community to share current security-related information including threats, vulnerabilities, and incidents.','The organization conducting the inspection/assessment obtains and examines artifacts showing contact to ensure the organization being inspected/assessed establishes and institutionalizes contact with selected groups and associations within the security community to share current security-related information including threats, vulnerabilities, and incidents.'),
('003013','draft','2013-08-29','DISA FSO','policy','The organization implements a threat awareness program that includes a cross-organization information-sharing capability.','PM-16.1','The organization being inspected/assessed documents and implements a threat awareness program that includes a cross-organization information-sharing capability.','The organization conducting the inspection/assessment obtains and examines the documented threat awareness program to ensure the organization being inspected/assessed implements a threat awareness program that includes a cross-organization information-sharing capability.'),
('003014','draft','2013-08-30','DISA FSO','technical','The information system enforces organization-defined mandatory access control policies over all subjects and objects.','AC-3(3).11','The organization being inspected/assessed configures the information system to enforce mandatory access control policies defined in AC-3 (3), CCI 2153 over all subjects and objects. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 3014.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to enforce mandatory access control policies defined in AC-3 (3), CCI 2153 over all subjects and objects. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 3014.'),
('003015','draft','2013-08-30','DISA FSO','policy','The mandatory access control policy specifies that organization-defined subjects may explicitly be granted organization-defined privileges such that they are not limited by some or all of the mandatory access control constraints.','AC-3(3).12','The organization being inspected/assessed configures the information system to explicitly grant privileges defined in AC-3 (3), CCI 2162 such that they are not limited by some or all of the mandatory access control constraints. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 3015.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to explicitly grant privileges defined in AC-3 (3), CCI 2162 such that they are not limited by some or all of the mandatory access control constraints. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 3015.'),
('003016','draft','2013-09-12','DISA FSO','policy','The organization, upon termination of individual employment, notifies organization-defined personnel or roles within an organization-defined time period.','PS-4.9','The organization being inspected/assessed notifies at a minimum, the ISSO and personnel responsible for revoking credentials immediately or within 24 hours upon termination of individual employment. The organization must maintain records of termination notification. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials. DoD has defined the time period as immediately or within 24 hours.','The organization conducting the inspection/assessment obtains and examines records of termination notification to ensure the organization being inspected/assessed notifies at a minimum, the ISSO and personnel responsible for revoking credentials immediately or within 24 hours upon termination of individual employment. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials. DoD has defined the time period as immediately or within 24 hours.'),
('003017','draft','2013-09-12','DISA FSO','policy','The organization defines the personnel or roles to whom a personnel security policy is disseminated.','PS-1.1','DoD has defined the roles as organizational personnel with access control responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as organizational personnel with access control responsibilities.'),
('003018','draft','2013-09-12','DISA FSO','policy','The organization defines the personnel or roles to whom the personnel security procedures are disseminated.','PS-1.2','DoD has defined the roles as organizational personnel with access control responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as organizational personnel with access control responsibilities.'),
('003019','draft','2013-09-12','DISA FSO','policy','The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties.','PS-3(3).1','The organization being inspected/assessed documents and implements a process to ensure that individuals accessing an information system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties.','The organization conducting the inspection/assessment obtains and examines the documented process and a sampling of access authorizations to ensure individuals accessing an information system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties.'),
('003020','draft','2013-09-12','DISA FSO','policy','The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection satisfy organization-defined additional personnel screening criteria.','PS-3(3).2','The organization being inspected/assessed documents and implements a process to ensure that individuals accessing an information system processing, storing, or transmitting information requiring special protection satisfy additional personnel screening criteria defined in PS-3 (3), CCI 3021.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process to ensure that individuals accessing an information system processing, storing, or transmitting information requiring special protection satisfy additional personnel screening criteria defined in PS-3 (3), CCI 3021.'),
('003021','draft','2013-09-12','DISA FSO','policy','The organization defines additional personnel screening criteria that individuals accessing an information system processing, storing, or transmitting information requiring protection must satisfy.','PS-3(3).3','The organization being inspected/assessed defines and documents additional personnel screening criteria that individuals accessing an information system processing, storing, or transmitting information requiring protection must satisfy. DoD has determined the additional personnel screening criteria is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented additional personnel screening criteria to ensure the organization being inspected/assessed defines additional personnel screening criteria that individuals accessing an information system processing, storing, or transmitting information requiring protection must satisfy. DoD has determined the additional personnel screening criteria is not appropriate to define at the Enterprise level.'),
('003022','draft','2013-09-12','DISA FSO','policy','The organization defines the time period within which to disable information system access upon termination of individual employment.','PS-4.2','DoD has defined the time period as immediately.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediately.'),
('003023','draft','2013-09-12','DISA FSO','policy','The organization, upon termination of individual employment, terminates/revokes any authenticators/credentials associated with the individual.','PS-4.3','The organization being inspected/assessed documents and implements a process to terminate/revoke any authenticators/credentials associated with the individual upon termination of individual employment. The organization must maintain records of termination/revocation of any authenticators/credentials.','The organization conducting the inspection/assessment obtains and examines the documented process as well as a sampling of records of termination/revocation of any authenticators/credentials to ensure the organization being inspected/assessed terminates/revokes any authenticators/credentials associated with the individual upon termination of individual employment.'),
('003024','draft','2013-09-12','DISA FSO','policy','The organization defines information security topics to be discussed while conducting exit interviews.','PS-4.5','The organization being inspected/assessed defines and documents information security topics to be discussed while conducting exit interviews. DoD has determined the information security topics are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information security topics to ensure the organization being inspected/assessed defines information security topics to be discussed while conducting exit interviews. DoD has determined the information security topics are not appropriate to define at the Enterprise level.'),
('003025','draft','2013-09-12','DISA FSO','policy','The organization defines personnel or roles to notify upon termination of individual employment.','PS-4.10','DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials.'),
('003026','draft','2013-09-12','DISA FSO','policy','The organization defines the time period within which to notify organization-defined personnel or roles upon termination of individual employment.','PS-4.11','DoD has defined the time period as immediately or within 24 hours.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediately or within 24 hours.'),
('003027','draft','2013-09-12','DISA FSO','policy','The organization notifies terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information.','PS-4(1).1','The organization being inspected/assessed notifies terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information. The organization must maintain a record of notifications of post-employment requirements.','The organization conducting the inspection/assessment obtains and examines the record of notifications of post-employment requirements to ensure the organization being inspected/assessed notifies terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information.'),
('003028','draft','2013-09-12','DISA FSO','policy','The organization requires terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.','PS-4(1).2','The organization being inspected/assessed documents within their personnel security procedures the requirement for terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.','The organization conducting the inspection/assessment obtains and examines the personnel security procedures and a sampling of signed acknowledgments of post-employment requirements to ensure the organization being inspected/assessed requires terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.'),
('003029','draft','2013-09-12','DISA FSO','policy','The organization employs automated mechanisms to notify organization-defined personnel or roles upon termination of an individual.','PS-4(2).1','The organization being inspected/assessed implements automated mechanisms to notify at a minimum, the ISSO and personnel responsible for revoking credentials upon termination of an individual. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials.','The organization conducting the inspection/assessment examines the configuration of the automated mechanism and any records of notification sent to ensure the organization being inspected/assessed implements automated mechanisms to notify at a minimum, the ISSO and personnel responsible for revoking credentials upon termination of an individual. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials.'),
('003030','draft','2013-09-12','DISA FSO','policy','The organization defines the personnel or roles to be notified by automated mechanism upon termination of an individual.','PS-4(2).2','DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for revoking credentials.'),
('003031','draft','2013-09-12','DISA FSO','policy','The organization modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer.','PS-5.5','The organization being inspected/assessed documents and implements a process to modify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer.','The organization conducting the inspection/assessment obtains and examines the documented process and a sampling of accounts of users recently transferred or reassigned to ensure the organization being inspected/assessed modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer.'),
('003032','draft','2013-09-12','DISA FSO','policy','The organization notifies organization-defined personnel or roles within an organization-defined time period when individuals are transferred or reassigned to other positions within the organization.','PS-5.6','The organization being inspected/assessed notifies at a minimum, the ISSO and personnel responsible for transferring credentials within 24 hours when individuals are transferred or reassigned to other positions within the organization. The organization must maintain records of transfer/reassignment notifications. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials. DoD has defined the time period as within 24 hours.','The organization conducting the inspection/assessment obtains and examines records of transfer/reassignment notifications to ensure the organization being inspected/assessed notifies at a minimum, the ISSO and personnel responsible for transferring credentials within 24 hours when individuals are transferred or reassigned to other positions within the organization. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials. DoD has defined the time period as within 24 hours.'),
('003033','draft','2013-09-12','DISA FSO','policy','The organization defines personnel or roles to be notified when individuals are transferred or reassigned to other positions within the organization.','PS-5.7','DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials.'),
('003034','draft','2013-09-12','DISA FSO','policy','The organization defines the time period within which organization-defined personnel or roles are to be notified when individuals are transferred or reassigned to other positions within the organization.','PS-5.8','DoD has defined the time period as immediately.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediately.'),
('003035','draft','2013-09-12','DISA FSO','policy','The organization develops and documents access agreements for organizational information systems.','PS-6.1','The organization being inspected/assessed develops and documents access agreements for organizational information systems.','The organization conducting the inspection/assessment obtains and examines the documented access agreements to ensure the organization being inspected/assessed develops and documents access agreements for organizational information systems.'),
('003036','draft','2013-09-12','DISA FSO','policy','The organization ensures that individuals requiring access to organizational information and information systems re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or in accordance with organization-defined frequency.','PS-6.5','The organization being inspected/assessed requires that individuals re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or when there is a change to the user\'s level of access.\n\nDoD has defined the frequency as when there is a change to the user\'s level of access.','The organization conducting the inspection/assessment obtains and examines a sampling of re-signed access agreements to ensure the organization being inspected/assessed requires that individuals re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or when there is a change to the user\'s level of access.\n\nDoD has defined the frequency as when there is a change to the user\'s level of access.'),
('003037','draft','2013-09-12','DISA FSO','policy','The organization defines the frequency for individuals requiring access to organization information and information systems to re-sign access agreements.','PS-6.6','DoD has defined the frequency as when there is a change to the user\'s level of access.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as when there is a change to the user\'s level of access.'),
('003038','draft','2013-09-12','DISA FSO','policy','The organization notifies individuals of applicable, legally binding post-employment requirements for protection of organizational information.','PS-6(3).1','The organization being inspected/assessed notifies individuals of applicable, legally binding post-employment requirements for protection of organizational information. The organization must maintain records of notifications of post-employment requirements for protection of organizational information.','The organization conducting the inspection/assessment obtains and examines the records of notifications of post-employment requirements for protection of organizational information to ensure the organization being inspected/assessed notifies individuals of applicable, legally binding post-employment requirements for protection of organizational information.'),
('003039','draft','2013-09-12','DISA FSO','policy','The organization requires individuals to sign an acknowledgement of legally binding post-employment requirements for protection of organizational information, if applicable, as part of granting initial access to covered information.','PS-6(3).2','The organization being inspected/assessed documents and implements a process to require individuals to sign an acknowledgement of legally binding post-employment requirements for protection of organizational information, if applicable, as part of granting initial access to covered information.','The organization conducting the inspection/assessment obtains and examines the documented process and a sampling of signed acknowledgements to ensure the organization being inspected/assessed requires individuals to sign an acknowledgement of legally binding post-employment requirements for protection of organizational information, if applicable, as part of granting initial access to covered information.'),
('003040','draft','2013-09-12','DISA FSO','policy','The organization requires third-party providers to comply with personnel security policies and procedures established by the organization.','PS-7.2','The organization being inspected/assessed documents and implements a process to require third-party providers to comply with personnel security policies and procedures established by the organization.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires third-party providers to comply with personnel security policies and procedures established by the organization.'),
('003041','draft','2013-09-12','DISA FSO','policy','The organization requires third-party providers to notify organization-defined personnel or roles of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges within an organization-defined time period.','PS-7.4','The organization being inspected/assessed documents and implements a process to require third-party providers to notify at a minimum, the ISSO and personnel responsible for transferring credentials of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges immediately. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials. DoD has defined the time period as immediately.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires third-party providers to notify at a minimum, the ISSO and personnel responsible for transferring credentials of any personnel transfers or terminations of third-party personnel who possess organizational credentials and/or badges, or who have information system privileges immediately. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials. DoD has defined the time period as immediately.'),
('003042','draft','2013-09-12','DISA FSO','policy','The organization defines personnel or roles whom third-party providers are to notify when third-party personnel who possess organizational credentials and /or badges or who have information system privileges are transferred or terminated.','PS-7.5','DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO and personnel responsible for transferring credentials.'),
('003043','draft','2013-09-12','DISA FSO','policy','The organization defines the time period for third-party providers to notify organization-defined personnel or roles when third-party personnel who possess organizational credentials and /or badges or who have information system privileges are transferred or terminated.','PS-7.6','DoD has defined the time period as immediately.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediately.'),
('003044','draft','2013-09-12','DISA FSO','policy','The organization notifies organization-defined personnel or roles within an organization-defined time period when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.','PS-8.3','The organization being inspected/assessed notifies at a minimum, the ISSO immediately when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction. The organization must maintain records of notifications of employee sanctions. DoD has defined the personnel or roles as at a minimum, the ISSO. DoD has defined the time period as immediately.','The organization conducting the inspection/assessment obtains and examines the records of notifications of employee sanctions to ensure the organization being inspected/assessed notifies at a minimum, the ISSO immediately when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction. DoD has defined the personnel or roles as at a minimum, the ISSO. DoD has defined the time period as immediately.'),
('003045','draft','2013-09-12','DISA FSO','policy','The organization defines personnel or roles who are to be notified when a formal employee sanctions process is initiated.','PS-8.4','DoD has defined the personnel or roles as at a minimum, the ISSO.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO.'),
('003046','draft','2013-09-12','DISA FSO','policy','The organization defines the time period within which to notify organization-defined personnel or roles when a formal employee sanctions process is initiated.','PS-8.2','DoD has defined the time period as immediately.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the time period as immediately.'),
('003047','draft','2013-09-23','DISA FSO','policy','The organization defines the personnel or roles to whom a security planning policy is disseminated.','PL-1.1','DoD has defined the roles as all organizational personnel with planning responsibilities or information security responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as all personnel organizational personnel with planning responsibilities or information security responsibilities.'),
('003048','draft','2013-09-23','DISA FSO','policy','The organization defines the personnel or roles to whom the security planning procedures are disseminated.','PL-1.2','DoD has defined the roles as all organizational personnel with planning responsibilities or information security responsibilities.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the roles as all organizational personnel with planning responsibilities or information security responsibilities.'),
('003049','draft','2013-09-23','DISA FSO','policy','The organization develops a security plan for the information system.','PL-2.1','The organization being inspected/assessed develops and documents a security plan for the information system.','The organization conducting the inspection/assessment obtains and examines the documented security plan to ensure the organization being inspected/assessed develops a security plan for the information system.'),
('003050','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system is consistent with the organization^s enterprise architecture.','PL-2.2','The organization being inspected/assessed defines a security plan for the information system which is consistent with the organization\'s enterprise architecture.','The organization conducting the inspection/assessment obtains and examines the security plan and the enterprise architecture to ensure the organization\'s security plan for the information system is consistent with the organization\'s enterprise architecture.'),
('003051','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system explicitly defines the authorization boundary for the system.','PL-2.3','The organization being inspected/assessed explicitly defines within the security plan the authorization boundary for the system.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed explicitly defines within the security plan the authorization boundary for the system.'),
('003052','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system describes the operational context of the information system in terms of missions and business processes.','PL-2.4','The organization being inspected/assessed describes within the security plan the operational context of the information system in terms of missions and business processes.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed describes within the security plan the operational context of the information system in terms of missions and business processes.'),
('003053','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system provides the security categorization of the information system, including supporting rationale.','PL-2.5','The organization being inspected/assessed defines within the security plan the security categorization of the information system including supporting rationale.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed defines within the security plan the security categorization of the information system including supporting rationale.'),
('003054','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system describes the operational environment for the information system and relationships with, or connections to, other information systems.','PL-2.6','The organization being inspected/assessed describes within the security plan the operational environment for the information system and relationships with or connections to other information systems.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed describes within the security plan the operational environment for the information system and relationships with or connections to other information systems.'),
('003055','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system provides an overview of the security requirements for the system.','PL-2.7','The organization being inspected/assessed documents within the security plan, an overview of the security requirements for the system.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed their security plan for the information system provides an overview of the security requirements for the system'),
('003056','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system identifies any relevant overlays, if applicable.','PL-2.8','The organization being inspected/assessed identifies within the security plan any relevant overlays, if applicable.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed identifies within the security plan any relevant overlays, if applicable.'),
('003057','draft','2013-09-23','DISA FSO','policy','The organization^s security plan for the information system describes the security controls in place or planned for meeting those requirements, including a rationale for the tailoring decisions.','PL-2.9','The organization being inspected/assessed describes within the security plan the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplementation decisions.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed describes within the security plan the security controls in place or planned for meeting those requirements including a rationale for the tailoring and supplementation decisions.'),
('003058','deprecated','2013-09-23','DISA FSO','policy','The organization distributes copies of the security plan to organization-defined personnel or roles.',NULL,NULL,NULL),
('003059','draft','2013-09-23','DISA FSO','policy','The organization distributes copies of the security plan to organization-defined personnel or roles.','PL-2.11','The organization being inspected/assessed distributes copies of the security plan to, at a minimum, the ISSO, ISSM and SCA via the organization\'s information sharing portal. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.','The organization conducting the inspection/assessment obtains and examines the security plan via the organization\'s information sharing portal to ensure the organization being inspected/assessed distributes copies of the security plan to at a minimum, the ISSO, ISSM and SCA via the organization\'s information sharing portal. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.'),
('003060','draft','2013-09-23','DISA FSO','policy','The organization defines the personnel or roles to whom copies of the security plan are distributed.','PL-2.12','DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.'),
('003061','draft','2013-09-23','DISA FSO','policy','The organization communicates subsequent changes to the security plan to organization-defined personnel or roles.','PL-2.13','The organization being inspected/assessed distributes changes to the security plan to, at a minimum, the ISSO, ISSM and SCA via the organization\'s information sharing portal. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.','The organization conducting the inspection/assessment examines the organization\'s information sharing portal to ensure at a minimum, the ISSO, ISSM and SCA have been provided changes to the security plan. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.'),
('003062','draft','2013-09-23','DISA FSO','policy','The organization defines the personnel or roles to whom changes to the security plan are communicated.','PL-2.14','DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM and SCA.'),
('003063','draft','2013-09-23','DISA FSO','policy','The organization protects the security plan from unauthorized disclosure.','PL-2.18','The organization being inspected/assessed documents and implements a process to protect the security plan from unauthorized disclosure.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed protects the security plan from unauthorized disclosure.'),
('003064','draft','2013-09-23','DISA FSO','policy','The organization protects the security plan from unauthorized modification.','PL-2.19','The organization being inspected/assessed documents and implements a process to protect the security plan from unauthorized modification.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed protects the security plan from unauthorized modification.'),
('003065','draft','2013-09-23','DISA FSO','policy','The organization plans and coordinates security-related activities affecting the information system with organization-defined individuals or groups before conducting such activities in order to reduce the impact on other organizational entities.','PL-2(3).1','The organization being inspected/assessed defines and documents within the security plan, the planning and coordination of security-related activities affecting the information system with individuals or groups defined in PL-2 (3), CCI 3067 before conducting such activities in order to reduce the impact on other organizational entities.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed plans and coordinates of security-related activities affecting the information system with individuals or groups defined in PL-2 (3), CCI 3067 before conducting such activities in order to reduce the impact on other organizational entities.'),
('003066','deprecated','2013-09-23','DISA FSO','policy','The organization defines the individuals or groups with whom security-related activities are planned and coordinated.',NULL,NULL,NULL),
('003067','draft','2013-09-23','DISA FSO','policy','The organization defines the individuals or groups with whom security-related activities are planned and coordinated.','PL-2(3).2','The organization being inspected/assessed defines and documents the individuals or groups with whom security-related activities are planned and coordinated. DoD has determined the individuals or groups are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented individuals or groups to ensure the organization being inspected/assessed defines the individuals or groups with whom security-related activities are planned and coordinated. DoD has determined the individuals or groups are not appropriate to define at the Enterprise level.'),
('003068','draft','2013-09-23','DISA FSO','policy','The organization reviews and updates the rules of behavior in accordance with organization-defined frequency.','PL-4.4','The organization being inspected/assessed reviews and updates the rules of behavior annually. The organization must maintain an audit trail of reviews and updates. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates the rules of behavior annually. DoD has defined the frequency as annually.'),
('003069','draft','2013-09-23','DISA FSO','policy','The organization defines the frequency with which to review and update the rules of behavior.','PL-4.5','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('003070','draft','2013-09-23','DISA FSO','policy','The organization requires individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated.','PL-4.6','The organization being inspected/assessed documents and implements a process to require individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated. The signed acknowledgment portion of this control may be satisfied by the security awareness training and role-based security training programs conducted by organizations if such training includes rules of behavior.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requires individuals who have signed a previous version of the rules of behavior to read and resign when the rules of behavior are revised/updated.'),
('003071','draft','2013-09-23','DISA FSO','policy','The organization develops a security Concept of Operations (CONOPS) for the information system containing, at a minimum, how the organization intends to operate the system from the perspective of information security.','PL-7.1','The organization being inspected/assessed develops and documents a security Concept of Operations (CONOPS) for the information system containing at a minimum, how the organization intends to operate the system from the perspective of information security.','The organization conducting the inspection/assessment obtains and examines the security CONOPS to ensure the organization being inspected/assessed develops a security CONOPS for the information system containing at a minimum, how the organization intends to operate the system from the perspective of information security.'),
('003072','draft','2013-09-23','DISA FSO','policy','The organization develops an information security architecture for the information system.','PL-8.1','The organization being inspected/assessed develops and documents an information security architecture for the information system.','The organization conducting the inspection/assessment obtains and examines the documented information security architecture to ensure the organization being inspected/assessed develops an information security architecture for the information system.'),
('003073','draft','2013-09-23','DISA FSO','policy','The organization^s information security architecture for the information system describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information.','PL-8.2','The organization being inspected/assessed describes within the information security architecture for the information system, the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information.','The organization conducting the inspection/assessment obtains and examines the information security architecture to ensure the organization being inspected/assessed describes within the information security architecture for the information system, the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information.'),
('003074','draft','2013-09-23','DISA FSO','policy','The organization^s information security architecture for the information system describes how the information security architecture is integrated into and supports the enterprise architecture.','PL-8.3','The organization being inspected/assessed describes within the information security architecture for the information system, how the information security architecture is integrated into and supports the enterprise architecture.','The organization conducting the inspection/assessment obtains and examines the information security architecture to ensure the organization being inspected/assessed describes within the information security architecture for the information system, how the information security architecture is integrated into and supports the enterprise architecture.'),
('003075','draft','2013-09-23','DISA FSO','policy','The organization^s information security architecture for the information system describes any information security assumptions about, and dependencies on, external services.','PL-8.4','The organization being inspected/assessed describes within the information security architecture for the information system, any information security assumptions about, and dependencies on, external services.','The organization conducting the inspection/assessment obtains and examines the information security architecture to ensure the organization being inspected/assessed describes within the information security architecture for the information system, any information security assumptions about, and dependencies on, external services.'),
('003076','draft','2013-09-23','DISA FSO','policy','The organization reviews and updates the information security architecture in accordance with organization-defined frequency to reflect updates in the enterprise architecture.','PL-8.5','The organization being inspected/assessed reviews and updates the information security architecture annually to reflect updates in the enterprise architecture. The organization must maintain an audit trail of reviews and updates. DoD has defined the frequency as annually.','The organization conducting the inspection/assessment obtains and examines the audit trail of reviews and updates to ensure the organization being inspected/assessed reviews and updates the information security architecture annually to reflect updates in the enterprise architecture. DoD has defined the frequency as annually.'),
('003077','draft','2013-09-23','DISA FSO','policy','The organization defines the frequency with which to review and update the information system architecture.','PL-8.6','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as annually.'),
('003078','draft','2013-09-23','DISA FSO','policy','The organization ensures that planned information security architecture changes are reflected in the security plan.','PL-8.7','The organization being inspected/assessed includes planned information security architecture changes in the security plan.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed includes planned information security architecture changes in the security plan.'),
('003079','draft','2013-09-23','DISA FSO','policy','The organization ensures that planned information security architecture changes are reflected in the security Concept of Operations (CONOPS).','PL-8.8','The organization being inspected/assessed includes planned information security architecture changes in the security Concept of Operations (CONOPS).','The organization conducting the inspection/assessment obtains and examines security CONOPS to ensure the organization being inspected/assessed includes planned information security architecture changes in the security CONOPS.'),
('003080','draft','2013-09-23','DISA FSO','policy','The organization ensures that planned information security architecture changes are reflected in organizational procurements/acquisitions.','PL-8.9','The organization being inspected/assessed includes planned information security architecture changes in organizational procurements/acquisitions.','The organization conducting the inspection/assessment obtains and examines a sampling of procurement materials to ensure the organization being inspected/assessed includes planned information security architecture changes in organizational procurements/acquisitions.'),
('003081','draft','2013-09-23','DISA FSO','policy','The organization designs its security architecture using a defense-in-depth approach that allocates organization-defined security safeguards to organization-defined locations.','PL-8(1).1','The organization being inspected/assessed designs and documents its security architecture using a defense-in-depth approach that allocates security safeguards defined in PL-8 (1), CCI 3083 to locations defined in PL-8 (1), CCI 3085.','The organization conducting the inspection/assessment obtains and examines the security architecture to ensure the organization being inspected/assessed designs its security architecture using a defense-in-depth approach that allocates security safeguards defined in PL-8 (1), CCI 3083 to locations defined in PL-8 (1), CCI 3085.'),
('003082','draft','2013-09-23','DISA FSO','policy','The organization designs its security architecture using a defense-in-depth approach that allocates organization-defined security safeguards to organization-defined architectural layers.','PL-8(1).2','The organization being inspected/assessed designs and documents its security architecture using a defense-in-depth approach that allocates security safeguards defined in PL-8 (1), CCI 3084 to architectural layers defined in PL-8 (1), CCI 3086.','The organization conducting the inspection/assessment obtains and examines the security architecture to ensure the organization being inspected/assessed designs its security architecture using a defense-in-depth approach that allocates security safeguards defined in PL-8 (1), CCI 3084 to architectural layers defined in PL-8 (1), CCI 3086.'),
('003083','draft','2013-09-23','DISA FSO','policy','The organization defines the security safeguards to be allocated to organization-defined locations.','PL-8(1).3','The organization being inspected/assessed defines and documents the security safeguards to be allocated to organization-defined locations. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be allocated to organization-defined locations. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003084','draft','2013-09-23','DISA FSO','policy','The organization defines the security safeguards to be allocated to organization-defined architectural layers.','PL-8(1).4','The organization being inspected/assessed defines and documents the security safeguards to be allocated to organization-defined architectural layers. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be allocated to organization-defined architectural layers. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003085','draft','2013-09-23','DISA FSO','policy','The organization defines the locations to which it allocates organization-defined security safeguards in the security architecture.','PL-8(1).5','The organization being inspected/assessed defines and documents the locations to which it allocates organization-defined security safeguards in the security architecture. DoD has determined the locations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented locations to ensure the organization being inspected/assessed defines the locations to which it allocates organization-defined security safeguards in the security architecture. DoD has determined the locations are not appropriate to define at the Enterprise level.'),
('003086','draft','2013-09-23','DISA FSO','policy','The organization defines the architectural layers to which it allocates organization-defined security safeguards in the security architecture.','PL-8(1).6','The organization being inspected/assessed defines and documents the architectural layers to which it allocates organization-defined security safeguards in the security architecture. DoD has determined the architectural layers are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented architectural layers to ensure the organization being inspected/assessed defines the architectural layers to which it allocates organization-defined security safeguards in the security architecture. DoD has determined the architectural layers are not appropriate to define at the Enterprise level.'),
('003087','draft','2013-09-23','DISA FSO','policy','The organization designs its security architecture using a defense-in-depth approach that ensures that the allocated security safeguards operate in a coordinated and mutually reinforcing manner.','PL-8(1).7','The organization being inspected/assessed designs and documents its security architecture using a defense-in-depth approach that ensures that the allocated security safeguards operate in a coordinated and mutually reinforcing manner.','The organization conducting the inspection/assessment obtains and examines security architecture to ensure the organization being inspected/assessed designs its security architecture using a defense-in-depth approach that ensures that the allocated security safeguards operate in a coordinated and mutually reinforcing manner.'),
('003088','draft','2013-09-23','DISA FSO','policy','The organization requires that organization-defined security safeguards allocated to organization-defined locations and architectural layers be obtained from different suppliers.','PL-8(2).1','The organization being inspected/assessed obtains from different suppliers security safeguards defined in PL-8 (1), CCIs 3083 and 3084 allocated to locations and architectural layers defined in PL-8 (1) CCIs 3085 and 3086.','The organization conducting the inspection/assessment obtains and examines procurement records to ensure that different suppliers are used to procure security safeguards defined in PL-8 (1), CCIs 3083 and 3084 allocated to locations and architectural layers defined in PL-8 (1) CCIs 3085 and 3086.'),
('003089','draft','2013-09-23','DISA FSO','policy','The organization defines the personnel or roles to whom the system and services acquisition policy is disseminated.','SA-1.1','DoD has defined the personnel or roles as all personnel.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all personnel.'),
('003090','draft','2013-09-23','DISA FSO','policy','The organization defines the personnel or roles to whom procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are disseminated.','SA-1.2','DoD has defined the personnel or roles as all personnel.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as all personnel.'),
('003091','draft','2013-09-23','DISA FSO','policy','The organization determines information security requirements for the information system or information system service in mission/business process planning.','SA-2.1','The organization being inspected/assessed determines and documents information security requirements for the information system or information system service in mission/business process planning.','The organization conducting the inspection/assessment obtains and examines the documented information security requirements to ensure the organization being inspected/assessed determines information security requirements for the information system or information system service in mission/business process planning.'),
('003092','draft','2013-09-23','DISA FSO','policy','The organization defines a system development life cycle that is used to manage the information system.','SA-3.2','The organization being inspected/assessed defines and documents a system development life cycle that is used to manage the information system. DoD has determined the system development life cycle is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented system development life cycle to ensure the organization being inspected/assessed defines a system development life cycle that is used to manage the information system. DoD has determined the system development life cycle is not appropriate to define at the Enterprise level.'),
('003093','draft','2013-09-23','DISA FSO','policy','The organization integrates the organizational information security risk management process into system development life cycle activities.','SA-3.5','The organization being inspected/assessed documents and implements a process to integrate the organizational information security risk management process into system development life cycle activities.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed integrates the organizational information security risk management process into system development life cycle activities.'),
('003094','draft','2013-09-23','DISA FSO','policy','The organization includes the security functional requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.1','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, the security functional requirements, explicitly or by reference, IAW DoDI 8580.1.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes the security functional requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs including DoDI 8580.1.'),
('003095','draft','2013-09-23','DISA FSO','policy','The organization includes the security strength requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.2','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, the security strength requirements, explicitly or by reference, IAW DoDI 8580.1.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes the security strength requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs including DoDI 8580.1.'),
('003096','draft','2013-09-23','DISA FSO','policy','The organization includes the security assurance requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.3','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, the security assurance requirements, explicitly or by reference, IAW DoDI 8580.1.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes the security assurance requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs including DoDI 8580.1.'),
('003097','draft','2013-09-23','DISA FSO','policy','The organization includes the security-related documentation requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.4','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, the security-related documentation requirements, explicitly or by reference.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes the security-related documentation requirements, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.'),
('003098','draft','2013-09-23','DISA FSO','policy','The organization includes requirements for protecting security-related documentation, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.5','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, requirements for protecting security-related documentation, explicitly or by reference.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes requirements for protecting security-related documentation, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.'),
('003099','draft','2013-09-23','DISA FSO','policy','The organization includes description of the information system development environment and environment in which the system is intended to operate, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.6','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, a description of the information system development environment and environment in which the system is intended to operate, explicitly or by reference.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes a description of the information system development environment and environment in which the system is intended to operate, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.'),
('003100','draft','2013-09-23','DISA FSO','policy','The organization includes acceptance criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.','SA-4.7','The organization being inspected/assessed documents within contracts/agreements for the information system, system component, or information system service, acceptance criteria, explicitly or by reference.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed includes acceptance criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs.'),
('003101','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide design information for the security controls to be employed that includes security-relevant external system interfaces, high-level design, low-level design, source code, hardware schematics, and/or organization-defined design information at an organization-defined level of detail.','SA-4(2).1','The organization being inspected/assessed defines and documents in contracts/agreements, the design information for the security controls that the developer will employ in the information system to include security-relevant external system interfaces, high-level design, low-level design, source code, hardware schematics and/or design/information defined in SA-4 (2), CCI 3103 at the level of detail defined in SA-4 (2), CCI 3105.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires the developer of the information system, system component, or information system service to provide design information for the security controls to be employed that includes security-relevant external system interfaces, high-level design, low-level design, source code and/or hardware schematics and/or design/information defined in SA-4 (2), CCI 3103 at the level of detail defined in SA-4 (2), CCI 3105.'),
('003102','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide implementation information for the security controls to be employed that includes security-relevant external system interfaces, high-level design, low-level design, source code, hardware schematics, and/or organization-defined implementation information at an organization-defined level of detail.','SA-4(2).2','The organization being inspected/assessed defines and documents in contracts/agreements, the implementation information for the security controls that the developer will employ in the information system to include security-relevant external system interfaces, high-level design, low-level design, source code and/or hardware schematics and/or implementation information defined in SA-4 (2), CCI 3104 at the level of detail defined in SA-4 (2), CCI 3106.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires the developer of the information system, system component, or information system service to provide implementation information for the security controls to be employed that includes security-relevant external system interfaces, high-level design, low-level design, source code and/or hardware schematics and/or implementation information defined in SA-4 (2), CCI 3104 at the level of detail defined in SA-4 (2), CCI 3106.'),
('003103','draft','2013-09-23','DISA FSO','policy','The organization defines the design information that the developer of the information system, system component, or information system service is required to provide for the security controls to be employed.','SA-4(2).3','The organization being inspected/assessed defines and documents the design information that the developer of the information system, system component, or information system service is required to provide for the security controls to be employed. DoD has determined the design information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented design information to ensure the organization being inspected/assessed defines the design information that the developer of the information system, system component, or information system service is required to provide for the security controls to be employed. DoD has determined the design information is not appropriate to define at the Enterprise level.'),
('003104','draft','2013-09-23','DISA FSO','policy','The organization defines the implementation information that the developer of the information system, system component, or information system service is required to provide for the security controls to be employed.','SA-4(2).4','The organization being inspected/assessed defines and documents the implementation information that the developer of the information system, system component, or information system service is required to provide for the security controls to be employed. DoD has determined the implementation information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented implementation information to ensure the organization being inspected/assessed defines the implementation information that the developer of the information system, system component, or information system service is required to provide for the security controls to be employed. DoD has determined the implementation information is not appropriate to define at the Enterprise level.'),
('003105','draft','2013-09-23','DISA FSO','policy','The organization defines the level of detail for the design information of the security controls that is required to be provided by the developer of the information system, system component, or information system services.','SA-4(2).5','The organization being inspected/assessed defines and documents the level of detail the design information of the security controls is required to be provided by the developer of the information system, system component, or information system services. DoD has determined the level of detail is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of detail to ensure the organization being inspected/assessed defines the level of detail the design information of the security controls is required to be provided by the developer of the information system, system component, or information system services. DoD has determined the level of detail is not appropriate to define at the Enterprise level.'),
('003106','draft','2013-09-23','DISA FSO','policy','The organization defines the level of detail for the implementation information of the security controls that is required to be provided by the developer of the information system, system component, or information system services.','SA-4(2).6','The organization being inspected/assessed defines and documents the level of detail the implementation information of the security controls is required to be provided by the developer of the information system, system component, or information system services. DoD has determined the level of detail is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of detail to ensure the organization being inspected/assessed defines the level of detail the implementation information of the security controls is required to be provided by the developer of the information system, system component, or information system services. DoD has determined the level of detail is not appropriate to define at the Enterprise level.'),
('003107','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to demonstrate the use of a system development life cycle that includes organization-defined state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes.','SA-4(3).1','The organization being inspected/assessed defines and documents within contracts/agreements, a requirement for the developer to demonstrate the use of a system development life cycle that includes the state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes defined in SA-4 (3), CCI 3108.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires the developer of the information system, system component, or information system service to demonstrate the use of a system development life cycle that includes the state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes defined in SA-4 (3), CCI 3108.'),
('003108','draft','2013-09-23','DISA FSO','policy','The organization defines the state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes that the developer of the information system, system component, or information system service is required to include when demonstrating the use of a system development life cycle.','SA-4(3).2','The organization being inspected/assessed defines and documents within contracts/agreements, the requirement for the developer to provide information regarding the state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed defines the state-of-the-practice system/security engineering methods, software development methods, testing/evaluation/validation techniques, and quality control processes that the developer of the information system, system component, or information system service needs to include when demonstrating the use of a system development life cycle.'),
('003109','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to deliver the system, component, or service with organization-defined security configurations implemented.','SA-4(5).1','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer of the information system, system component, or information system service to deliver the system, component, or service with security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.\n\nDoD has defined the security configurations as security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires he developer of the information system, system component, or information system service to deliver the system, component, or service with security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.\n\nDoD has defined the security configurations as security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.'),
('003110','draft','2013-09-23','DISA FSO','policy','The organization defines the security configurations required to be implemented when the developer delivers the information system, system component, or information system service.','SA-4(5).2','DoD has defined the security configurations as security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the security configurations as security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.'),
('003111','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to use the organization-defined security configurations as the default for any subsequent system, component, or service reinstallation or upgrade.','SA-4(5).3','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer of the information system, system component, or information system service to use the applicable requirements from DoDI 8510.01 and STIGs/SRGs as the default for any subsequent system, component, or service reinstallation or upgrade.\n\nDoD has defined the security configurations as security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires the developer of the information system, system component, or information system service to use the applicable requirements from DoDI 8510.01 and STIGs/SRGs as the default for any subsequent system, component, or service reinstallation or upgrade.\n\nDoD has defined the security configurations as security configurations identified by the applicable requirements from DoDI 8510.01 and STIGs/SRGs.'),
('003112','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce a plan for the continuous monitoring of security control effectiveness that contains an organization-defined level of detail.','SA-4(8).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce a plan for the continuous monitoring of security control effectiveness that contains the level of detail defined in SA-4 (8), CCI 3113.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce a plan for the continuous monitoring of security control effectiveness that contains the level of detail defined in SA-4 (8), CCI 3113.'),
('003113','draft','2013-09-23','DISA FSO','policy','The organization defines the level of detail to be contained in the plan for the continuous monitoring of security control effectiveness that the developer of the information system, system component, or information system services is required to produce.','SA-4(8).2','The organization being inspected/assessed defines and documents the level of detail to be contained in the plan for the continuous monitoring of security control effectiveness that the developer of the information system, system component, or information system services is required to produce. DoD has determined the level of detail is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented level of detail to ensure the organization being inspected/assessed defines the level of detail to be contained in the plan for the continuous monitoring of security control effectiveness that the developer of the information system, system component, or information system services is required to produce. DoD has determined the level of detail is not appropriate to define at the Enterprise level.'),
('003114','draft','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use.','SA-4(9).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use.\n\nPorts identified shall be assessed and planned for in light of DISA\'s PPSM requirements.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use.'),
('003115','deprecated','2013-09-23','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to identify early in the system development life cycle, the functions, ports, protocols, and services intended for organizational use.',NULL,NULL,NULL),
('003116','draft','2013-09-23','DISA FSO','policy','The organization employs only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems.','SA-4(10).1','The organization being inspected/assessed employs DoD approved PKI tokens for identity verification.','The organization conducting the inspection/assessment examines the information system to ensure DoD approved PKI tokens are implemented for identity verification.'),
('003117','draft','2013-09-23','DISA FSO','policy','The organization centrally manages organization-defined security controls and related processes.','PL-9.1','DoDI 8500.01, DoDI 8510.01, and CNSSI 1253 meet the DoD requirements for centrally managing security controls and related processes.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and CNSSI 1253.','DoDI 8500.01, DoDI 8510.01, and CNSSI 1253 meet the DoD requirements for centrally managing security controls and related processes.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DoD level policy, DoDI 8500.01 and CNSSI 1253.'),
('003118','draft','2013-09-23','DISA FSO','policy','The organization defines security controls and related processes to be centrally managed.','PL-9.2','DoD has defined the security controls and related processes to be centrally managed as CNSSI 1253, DoDI 8510.01, and DoDI 8500.01.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the security controls and related processes to be centrally managed as CNSSI 1253, DoDI 8510.01, and DoDI 8500.01.'),
('003119','draft','2013-09-23','DISA FSO','policy','The organization employs a technical surveillance countermeasures survey at organization-defined locations on an organization-defined frequency or when organization-defined events or indicators occur.','RA-6.1','The organization being inspected/assessed documents and implements a process to employ a technical surveillance countermeasures survey at locations defined in RA-6, CCI 3120 on a frequency defined in RA-6, CCI 3121 or when events or indicators defined in RA-6, CCI 3122 occur. The organization must maintain a record of surveys.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of surveys to ensure the organization being inspected/assessed employs a technical surveillance countermeasures survey at locations defined in RA-6, CCI 3120 on a frequency defined in RA-6, CCI 3121 or when events or indicators defined in RA-6, CCI 3122 occur.'),
('003120','draft','2013-09-23','DISA FSO','policy','The organization defines the locations where technical surveillance countermeasures surveys are to be employed.','RA-6.2','The organization being inspected/assessed defines and documents the locations where technical surveillance countermeasures surveys are to be employed. DoD has determined the locations are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented locations to ensure the organization being inspected/assessed defines the locations where technical surveillance countermeasures surveys are to be employed. DoD has determined the locations are not appropriate to define at the Enterprise level.'),
('003121','draft','2013-09-23','DISA FSO','policy','The organization defines the frequency on which to employ technical surveillance countermeasures surveys.','RA-6.3','The organization being inspected/assessed defines and documents the frequency on which to employ technical surveillance countermeasures surveys. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency on which to employ technical surveillance countermeasures surveys. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('003122','draft','2013-09-23','DISA FSO','policy','The organization defines the events or indicators upon which technical surveillance countermeasures surveys are to be employed.','RA-6.4','The organization being inspected/assessed defines and documents the events or indicators upon which technical surveillance countermeasures surveys are to be employed. DoD has determined the events or indicators are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented events or indicators to ensure the organization being inspected/assessed defines the events or indicators upon which technical surveillance countermeasures surveys are to be employed. DoD has determined the events or indicators are not appropriate to define at the Enterprise level.'),
('003123','draft','2013-09-24','DISA FSO','technical','The information system implements cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications.','MA-4(6).2','The organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications. For information system components that have applicable STIGs or SRGs, the organization being inspected/assessed must comply with the STIG/SRG guidance that pertains to CCI 3123.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed configures the information system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications. For information system components that have applicable STIGs or SRGs, the organization conducting the inspection/assessment evaluates the components to ensure that the organization being inspected/assessed has configured the information system in compliance with the applicable STIGs and SRGs pertaining to CCI 3123.'),
('003124','draft','2013-09-30','DISA FSO','policy','The organization obtains administrator documentation for the information system, system component, or information system service that describes secure configuration of the system, component, or service.','SA-5.1','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide administrator documentation for the information system, system component or information system service that describe secure configuration of the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide administrator documentation for the information system, system component or information system service that describe secure configuration of the system, component, or service.'),
('003125','draft','2013-09-30','DISA FSO','policy','The organization obtains administrator documentation for the information system, system component, or information system service that describes secure installation of the system, component, or service.','SA-5.2','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide administrator documentation for the information system, system component or information system service that describe secure installation of the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide administrator documentation for the information system, system component or information system service that describe secure installation of the system, component, or service.'),
('003126','draft','2013-09-30','DISA FSO','policy','The organization obtains administrator documentation for the information system, system component, or information system service that describes secure operation of the system, component, or service.','SA-5.3','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide administrator documentation for the information system, system component or information system service that describe secure operation of the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide administrator documentation for the information system, system component or information system service that describe secure operation of the system, component, or service.'),
('003127','draft','2013-09-30','DISA FSO','policy','The organization obtains administrator documentation for the information system, system component, or information system services that describes effective use and maintenance of security functions/mechanisms.','SA-5.4','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide administrator documentation for the information system, system component or information system service that describe effective use and maintenance of security functions/mechanisms.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide administrator documentation for the information system, system component or information system service that describe effective use and maintenance of security functions/mechanisms.'),
('003128','draft','2013-09-30','DISA FSO','policy','The organization obtains administrator documentation for the information system, system component, or information system service that describes known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions.','SA-5.5','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide administrator documentation for the information system, system component or information system service that describe known vulnerabilities regarding configuration and use of administrative (i.e. privileged) functions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide administrator documentation for the information system, system component or information system service that describe known vulnerabilities regarding configuration and use of administrative (i.e. privileged) functions.'),
('003129','draft','2013-09-30','DISA FSO','policy','The organization obtains user documentation for the information system, system component, or information system service that describes user-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms.','SA-5.6','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide user documentation for the information system, system component or information system service that describes user-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide user documentation for the information system, system component or information system service that describes user-accessible security functions/mechanisms and how to effectively use those security functions/mechanisms.'),
('003130','draft','2013-09-30','DISA FSO','policy','The organization obtains user documentation for the information system, system component, or information system service that describes methods for user interaction which enables individuals to use the system, component, or service in a more secure manner.','SA-5.7','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide user documentation for the information system, system component or information system service that describes methods for user interaction which enables individuals to use the system, component, or service in a more secure manner.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide user documentation for the information system, system component or information system service that describes methods for user interaction which enables individuals to use the system, component, or service in a more secure manner.'),
('003131','draft','2013-09-30','DISA FSO','policy','The organization obtains user documentation for the information system, system component, or information system service that describes user responsibilities in maintaining the security of the system, component, or service.','SA-5.8','The organization being inspected/assessed documents within contracts/agreements, requirements that the developer provide user documentation for the information system, system component or information system service that describes user responsibilities in maintaining the security of the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer provide user documentation for the information system, system component or information system service that describes user responsibilities in maintaining the security of the system, component, or service.'),
('003132','draft','2013-09-30','DISA FSO','policy','The organization takes organization-defined actions in response to attempts to obtain either unavailable or nonexistent documentation for the information system, system component, or information system service.','SA-5.9','The organization being inspected/assessed takes actions defined in SA-5, CCI 3133 in response to attempts to obtain either unavailable or nonexistent documentation for information system, system component, or information system service.\n\nThe organization must maintain a record of actions taken.\n\nDoD has determined the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the record of actions taken to ensure the organization being inspected/assessed takes actions defined in SA-5, CCI 3133 in response to attempts to obtain either unavailable or nonexistent documentation for information system, system component, or information system service.\n\nDoD has determined the actions are not appropriate to define at the Enterprise level.'),
('003133','draft','2013-09-30','DISA FSO','policy','The organization defines actions to be taken in response to attempts to obtain either unavailable or nonexistent documentation for the information system, system component, or information system service.','SA-5.10','The organization being inspected/assessed defines and documents actions to be taken in response to attempts to obtain either unavailable or nonexistent documentation for information system, system component, or information system service.\n\nDoD has determined the actions are not appropriate to define at the Enterprise level.','The organization conducting inspection/assessment obtains and examines the documented actions to ensure the organization being inspected/assessed defines action to be taken in response to attempts to obtain either unavailable or nonexistent documentation for information system, system component, or information system service.\n\nDoD has determined the actions are not appropriate to define at the Enterprise level.'),
('003134','draft','2013-09-30','DISA FSO','policy','The organization protects information system, system component, or information system service documentation as required, in accordance with the risk management strategy.','SA-5.12','The organization being inspected/assessed documents and implements processes to store and handle information system, system component, or information system service documentation as required, in accordance with the risk management strategy.','The organization conducting the inspection/assessment obtains and examines the documented processes to ensure the organization being inspected/assessed stores and handles information system, system component, or information system service documentation as required, in accordance with the risk management strategy.'),
('003135','draft','2013-09-30','DISA FSO','policy','The organization distributes information system, system component, or information system service documentation to organization-defined personnel or roles.','SA-5.13','The organization being inspected/assessed distributes information system, system component, or information system service documentation to at a minimum, the ISSO, ISSM, and SCA, via an information sharing capability. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and SCA.','The organization conducting the inspection/assessment obtains and examines the information system, system component, or information system service documentation via the organization\'s information sharing capability to ensure the organization being inspected/assessed distributes information system, system component, or information system service documentation to at a minimum, the ISSO, ISSM, and SCA. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and SCA.'),
('003136','draft','2013-09-30','DISA FSO','policy','The organization defines the personnel or roles to whom information system, system component, or information system service documentation is to be distributed.','SA-5.14','DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and SCA.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and SCA.'),
('003137','draft','2013-09-30','DISA FSO','policy','The organization defines security controls that providers of external information system services employ in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.','SA-9.3','DoD has defined the security controls as security controls defined by CNSSI 1253.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the security controls as security controls defined by CNSSI 1253.'),
('003138','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined processes, methods, and techniques to monitor security control compliance by external service providers on an ongoing basis.','SA-9.8','The organization being inspected/assessed implements the processes, methods, and techniques defined in SA-9, CCI 3139 to monitor security control compliance by external service providers on an ongoing basis. The organization must maintain records of monitoring.','The organization conducting the inspection/assessment obtains and examines the records of monitoring to ensure the organization being inspected/assessed implements the processes, methods, and techniques defined in SA-9, CCI 3139 to monitor security control compliance by external service providers on an ongoing basis.'),
('003139','draft','2013-09-30','DISA FSO','policy','The organization defines processes, methods, and techniques to employ to monitor security control compliance by external service providers on an ongoing basis.','SA-9.9','The organization being inspected/assessed defines and documents processes, methods, and techniques to employ to monitor security control compliance by external service providers on an ongoing basis. DoD has determined the processes, methods, and techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented processes, methods, and techniques to ensure the organization being inspected/assessed defines processes, methods, and techniques to employ to monitor security control compliance by external service providers on an ongoing basis.'),
('003140','draft','2013-09-30','DISA FSO','policy','The organization conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services.','SA-9(1).1','The organization being inspected/assessed documents and implements a process to conduct an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services. The organization must maintain a record of risk assessment.','The organization conducting the inspection/assessment obtains and examines a list of acquired or outsourced information security services and the record of risk assessment to ensure the organization being inspected/assessed conducts an organizational assessment of risk prior to the acquisition or outsourcing of dedicated information security services.'),
('003141','draft','2013-09-30','DISA FSO','policy','The organization ensures that the acquisition or outsourcing of dedicated information security services is approved by organization-defined personnel or roles.','SA-9(1).2','The organization being inspected/assessed ensures that the acquisition or outsourcing of dedicated information security services is approved by the DoD Component CIO or their delegate(s). The organization must maintain a record of approvals. DoD has defined the personnel or roles the DoD Component CIO or their delegate(s).','The organization conducting the inspection/assessment obtains and examines a list of acquired or outsourced information security services as well as the record of approvals to ensure the organization being inspected/assessed ensures that the acquisition or outsourcing of dedicated information security services is approved by the DoD Component CIO or their delegate(s). DoD has defined the personnel or roles the DoD Component CIO or their delegate(s).'),
('003142','draft','2013-09-30','DISA FSO','policy','The organization defines the personnel or roles authorized to approve the acquisition or outsourcing of dedicated information security services.','SA-9(1).3','DoD has defined the personnel or roles the DoD Component CIO or their delegate(s).','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles the DoD Component CIO or their delegate(s).'),
('003143','draft','2013-09-30','DISA FSO','policy','The organization requires providers of organization-defined external information system services to identify the functions, ports, protocols, and other services required for the use of such services.','SA-9(2).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that providers of all external information system services identify the functions, ports, protocols, and other services required for the use of such services.\n\nDoD has defined the external information system services as all external information system services.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that providers of all external information system services identify the functions, ports, protocols, and other services required for the use of such services.\n\nDoD has defined the external information system services as all external information system services.'),
('003144','draft','2013-09-30','DISA FSO','policy','The organization defines the external information system services for which the providers are required to identify the functions, ports, protocols, and other services required for the use of such services.','SA-9(2).2','DoD has defined the external information system services as all external information system services.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external information system services as all external information system services.'),
('003145','draft','2013-09-30','DISA FSO','policy','The organization establishes trust relationships with external service providers based on organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-9(3).1','The organization being inspected/assessed establishes trust relationships with external service providers based on security requirements, properties, factors, or conditions defining acceptable trust relationship defined in SA-9 (3), CCI 3148.','The organization conducting the inspection/assessment obtains and examines a list of trust relationships with external service providers to ensure those relationships are established based on security requirements, properties, factors, or conditions defining acceptable trust relationship defined in SA-9 (3), CCI 3148.'),
('003146','draft','2013-09-30','DISA FSO','policy','The organization documents trust relationships with external service providers based on organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-9(3).2','The organization being inspected/assessed documents trust relationships with external service providers based on security requirements, properties, factors, or conditions defining acceptable trust relationships defined in SA-9 (3), CCI 3148.','The organization conducting the inspection/assessment obtains and examines the list of trust relationship with external service providers to ensure it is documented.'),
('003147','draft','2013-09-30','DISA FSO','policy','The organization maintains trust relationships with external service providers based on organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-9(3).3','The organization being inspected/assessed maintains trust relationships with external service providers based on security requirements, properties, factors, or conditions defining acceptable trust relationships defined in SA-9 (3), CCI 3148.','The organization conducting the inspection/assessment obtains and examines a list of trust relationships with external service providers to ensure those relationships are maintained based on security requirements, properties, factors, or conditions defining acceptable trust relationship defined in SA-9 (3), CCI 3148.'),
('003148','draft','2013-09-30','DISA FSO','policy','The organization defines security requirements, properties, factors, or conditions defining acceptable trust relationships with external service providers.','SA-9(3).4','The organization being inspected/assessed defines and documents security requirements, properties, factors, or conditions defining acceptable trust relationships with external service providers. DoD has determined the security requirements, properties, factors, or conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security requirements, properties, factors, or conditions to ensure the organization being inspected/assessed defines security requirements, properties, factors, or conditions defining acceptable trust relationships with external service providers. DoD has determined the security requirements, properties, factors, or conditions are not appropriate to define at the Enterprise level.'),
('003149','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined security safeguards to ensure that the interests of organization-defined external service providers are consistent with and reflect organizational interests.','SA-9(4).1','The organization being inspected/assessed employs the security safeguards defined in SA-9 (4), CCI 3150 to ensure that the interests of all external service providers from whom services are solicited are consistent with and reflect organizational interests. The organization must maintain records of safeguard review. DoD has defined the external service providers as all external service providers from whom services are solicited.','The organization conducting the inspection/assessment obtains and examines a list of external service providers as well as records of safeguard review to ensure the organization being inspected/assessed employs the security safeguards defined in SA-9 (4), CCI 3150 to ensure that the interests of all external service providers from whom services are solicited are consistent with and reflect organizational interests. DoD has defined the external service providers as all external service providers from whom services are solicited.'),
('003150','draft','2013-09-30','DISA FSO','policy','The organization defines security safeguards to employ to ensure that the interests of organization-defined external service providers are consistent with and reflect organizational interests.','SA-9(4).2','The organization being inspected/assessed defines and documents security safeguards to employ to ensure that the interests of organization-defined external service providers are consistent with and reflect organizational interests. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines security safeguards to employ to ensure that the interests of organization-defined external service providers are consistent with and reflect organizational interests. DoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003151','draft','2013-09-30','DISA FSO','policy','The organization defines external service providers whose interests are consistent with and reflect organizational interests.','SA-9(4).3','DoD has defined the external service providers as all external service providers from whom services are solicited.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external service providers as all external service providers from whom services are solicited.'),
('003152','draft','2013-09-30','DISA FSO','policy','The organization restricts the location of information processing, information/data, and/or information system services to organization-defined locations based on organization-defined requirements or conditions.','SA-9(5).1','The organization being inspected/assessed restricts the location of information processing, information/data, and/or information system services to locations defined in SA-9 (5), CCI 3153 based on requirements or conditions defined in SA-9 (5), CCI 3154.','The organization conducting the inspection/assessment obtains and examines a list of locations of information processing, information/data, and/or information system services to ensure the organization being inspected/assessed restricts the location of information processing, information/data, and/or information system services to locations defined in SA-9 (5), CCI 3153 based on requirements or conditions defined in SA-9 (5), CCI 3154.'),
('003153','draft','2013-09-30','DISA FSO','policy','The organization defines the locations for which to restrict information processing, information/data, and/or information system services based on organization-defined requirements or conditions.','SA-9(5).2','The organization being inspected/assessed defines and documents the locations to restrict information processing, information/data, and/or information system services based on organization-defined requirements or conditions.\n\nDefinitions should take into account regulatory guidelines in place to protect the data being stored or processed.\n\nDoD has determined the location is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented locations to ensure the organization being inspected/assessed defines the locations to restrict information processing, information/data, and/or information system services based on organization-defined requirements or conditions. DoD has determined the location is not appropriate to define at the Enterprise level.'),
('003154','draft','2013-09-30','DISA FSO','policy','The organization defines the requirements or conditions on which to base restricting the location of information processing, information/data, and/or information system services to organization-defined locations.','SA-9(5).3','The organization being inspected/assessed defines and documents the requirements or conditions on which to base restricting the location of information processing, information/data, and/or information system services to organization-defined locations.\n\nDefinitions should take into account regulatory guidelines in place to protect the data being stored or processed.\n\nDoD has determined the requirements or conditions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented requirements or conditions to ensure the organization being inspected/assessed defines the requirements or conditions on which to base restricting the location of information processing, information/data, and/or information system services to organization-defined locations. DoD has determined the requirements or conditions are not appropriate to define at the Enterprise level.'),
('003155','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform configuration management during system, component, or service design, development, implementation and/or operation.','SA-10.1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service perform configuration management during system, component or service design, development, implementation and/or operation. The configuration management process applies to:\n1. Documentation developed or used in the lifecycle, including requirements and interface specifications;\n2. Elements including design libraries;\n3. Tools including design tools and test tools;\n4. Technical data including test data; and\n5. Information on element and system lifecycle processes','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires the developer of the information system, system component, or information system service perform configuration management during system, component or service design, development, implementation and/or operation.'),
('003156','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to document the integrity of changes to organization-defined configuration items under configuration management.','SA-10.2','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service document the integrity of changes to configuration items under configuration management defined in SA-10, CCI 3159.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the integrity of changes to configuration items under configuration management defined in SA-10, CCI 3159.'),
('003157','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to manage the integrity of changes to organization-defined configuration items under configuration management.','SA-10.3','The organization being inspected/assessed requires within contracts/agreements the requirement that the developer of the information system, system component, or information system service manage the integrity of changes to configuration items under configuration management defined in SA-10, CCI 3159.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service manage the integrity of changes to configuration items under configuration management defined in SA-10, CCI 3159.'),
('003158','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to control the integrity of changes to organization-defined configuration items under configuration management.','SA-10.4','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service control the integrity of changes to configuration items under configuration management defined in SA-10, CCI 3159.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service control the integrity of changes to configuration items under configuration management defined in SA-10, CCI 3159.'),
('003159','draft','2013-09-30','DISA FSO','policy','The organization defines the configuration items under configuration management that require the integrity of changes to be documented, managed and controlled.','SA-10.5','The organization being inspected/assessed defines and documents the configuration items under configuration management that require the integrity of changes to be documented, managed and controlled. DoD has determined the configuration items are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented configuration items to ensure the organization being inspected/assessed defines the configuration items under configuration management that require the integrity of changes to be documented, managed and controlled. DoD has determined the configuration items are not appropriate to define at the Enterprise level.'),
('003160','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to document the potential security impacts of approved changes to the system, component, or service.','SA-10.8','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service document the potential security impacts of approved changes to the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the potential security impacts of approved changes to the system, component, or service.'),
('003161','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to track security flaws within the system, component, or service.','SA-10.9','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service track security flaws within the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service track security flaws within the system, component, or service.'),
('003162','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to track flaw resolution within the system, component, or service.','SA-10.10','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service track flaw resolution within the system, component, or service.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service track flaw resolution within the system, component, or service.'),
('003163','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to report findings of security flaws and flaw resolution within the system, component, or service to organization-defined personnel.','SA-10.11','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service report security flaws and flaw resolution within the system, component, or service findings to at a minimum, the ISSO and ISSM.\n\nDoD has defined the personnel as at a minimum, the ISSO and ISSM.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service report security flaws and flaw resolution within the system, component, or service findings to at a minimum, the ISSO and ISSM.\n\n DoD has defined the personnel as at a minimum, the ISSO and ISSM.'),
('003164','draft','2013-09-30','DISA FSO','policy','The organization defines the personnel to whom security flaw findings and flaw resolution within the system, component, or service are reported.','SA-10.12','DoD has defined the personnel as at a minimum, the ISSO and ISSM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel as at a minimum, the ISSO and ISSM.'),
('003165','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to enable integrity verification of hardware components.','SA-10(3).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service enable integrity verification of hardware components.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service enable integrity verification of hardware components.'),
('003166','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions.','SA-10(4).1','The organization being inspected/assessed documents within contracts/agreements the requirement that the developer of the information system, system component, or information system service employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions.'),
('003167','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to employ tools for comparing newly generated versions of software/firmware source code with previous versions.','SA-10(4).2','The organization being inspected/assessed documents within contracts/agreements the requirement that the developer of the information system, system component, or information system service employ tools for comparing newly generated versions of software/firmware source code with previous versions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service employ tools for comparing newly generated versions of software/firmware source code with previous versions.'),
('003168','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to employ tools for comparing newly generated versions of object code with previous versions.','SA-10(4).3','The organization being inspected/assessed documents within contracts/agreements the requirement that the developer of the information system, system component, or information system service employ tools for comparing newly generated versions of object code with previous versions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service employ tools for comparing newly generated versions of object code with previous versions.'),
('003169','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to maintain the integrity of the mapping between the master build data (hardware drawings and software/firmware code) describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.','SA-10(5).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service maintain the integrity of the mapping between the master build data (hardware drawings and software/firmware code) describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service maintain the integrity of the mapping between the master build data (hardware drawings and software/firmware code) describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.'),
('003170','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.','SA-10(6).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.'),
('003171','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to create a security assessment plan.','SA-11.1','The organization being inspected/assessed requires that the developer create and document a security assessment plan that includes:\n1. The types of analyses, testing, evaluation, and reviews of software and firmware components;\n2. The degree of rigor to be applied; and\n3. The types of artifacts produced during those processes.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service create a security assessment plan.'),
('003172','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to implement a security assessment plan.','SA-11.2','The organization being inspected/assessed requires that the developer implement the security assessment plan developed in SA-11, CCI 003171.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service implement a security assessment plan.'),
('003173','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform unit, integration, system, and/or regression testing/evaluation at an organization-defined depth and coverage.','SA-11.3','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service perform unit, integration, system, and/or regression testing/evaluation at depth and coverage defined in SA-11, CCI 3174.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform unit, integration, system, and/or regression testing/evaluation at depth and coverage defined in SA-11, CCI 3174.'),
('003174','draft','2013-09-30','DISA FSO','policy','The organization defines the depth and coverage at which to perform unit, integration, system, and/or regression testing/evaluation.','SA-11.4','The organization being inspected/assessed defines and documents the depth and coverage to perform unit, integration, system, and/or regression testing/evaluation. Examples of approaches or tool types that could be required are:\n1. Approaches such as static analyses, dynamic analyses, binary analysis, or a hybrid of the three approaches; and\n2. Tools such as web-based application scanners, static analysis tools, binary analyzers.\n\nDoD has determined the depth and coverage are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented depth and coverage to ensure the organization being inspected/assessed defines the depth and coverage to perform unit, integration, system, and/or regression testing/evaluation. DoD has determined the depth and coverage are not appropriate to define at the Enterprise level.'),
('003175','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce evidence of the execution of the security assessment plan.','SA-11.5','The organization being inspected/assessed requires the developer to produce and provide evidence of the execution of the security assessment plan.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce evidence of the execution of the security assessment plan.'),
('003176','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce the results of the security testing/evaluation.','SA-11.6','The organization being inspected/assessed requires the developer to produce and provide results of the security testing/evaluation.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce the results of the security testing/evaluation.'),
('003177','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to implement a verifiable flaw remediation process.','SA-11.7','The organization being inspected/assessed requires the developer to implement a verifiable flaw remediation process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service implement a verifiable flaw remediation process.'),
('003178','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to correct flaws identified during security testing/evaluation.','SA-11.8','The organization being inspected/assessed requires the developer to correct flaws identified during security testing/evaluation and to document and provide evidence that the flaws were corrected.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service correct flaws identified during security testing/evaluation and provide evidence.'),
('003179','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to employ static code analysis tools to identify common flaws.','SA-11(1).1','The organization being inspected/assessed includes the requirement within contracts/agreements that the developer of the information system, system component, or information system service employ static code analysis tools to identify common flaws.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service employ static code analysis tools to identify common flaws.'),
('003180','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to document the results of static code analysis.','SA-11(1).2','The organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the type of static code analysis that was performed and the results (including defects).','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the results of static code analysis.'),
('003181','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform threat and vulnerability analysis.','SA-11(2).1','The organization being inspected/assessed requires the developer to document and perform threat and vulnerability analysis to ensure that design or implementation changes, and resulting vulnerabilities, are accounted for early in the life cycle.\n\nThreat analysis may be performed through the use of open source threat information. Vulnerability analyses should be informed by system design documentation and may include static analyses, dynamic analyses, simulations, and penetration testing. The developer must document the type of vulnerability analysis that was performed, the results (including defects) and any follow on actions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform threat and vulnerability analysis.'),
('003182','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform testing/evaluation of the as-built system, component, or service subsequent to threat and vulnerability analysis.','SA-11(2).2','The organization being inspected/assessed requires within contracts/agreements that the developer the information system, system component, or information system service perform testing/evaluation of the as-built system, component, or service based on threat and vulnerability analysis.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform testing/evaluation of the as-built system, component, or service subsequent to threat and vulnerability analysis.'),
('003183','draft','2013-09-30','DISA FSO','policy','The organization requires an independent agent satisfying organization-defined independence criteria to verify the correct implementation of the developer security assessment plan.','SA-11(3).1','The organization being inspected/assessed requires within contracts/agreements that an independent agent satisfying independence criteria defined in SA-11 (3), CCI 3185 verify the correct implementation of the developer security assessment plan.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that an independent agent satisfying independence criteria defined in SA-11 (3), CCI 3185 verify the correct implementation of the developer security assessment plan.'),
('003184','draft','2013-09-30','DISA FSO','policy','The organization requires an independent agent satisfying organization-defined independence criteria to verify the evidence produced during security testing/evaluation.','SA-11(3).2','The organization being inspected/assessed requires within contracts/agreements that an independent agent satisfying independence criteria defined in SA-11 (3), CCI 3185 verify the evidence produced during security testing/evaluation.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that an independent agent satisfying independence criteria defined in SA-11 (3), CCI 3185 verify the evidence produced during security testing/evaluation.'),
('003185','draft','2013-09-30','DISA FSO','policy','The organization defines the independence criteria the independent agent must satisfy prior to verifying the correct implementation of the developer security assessment plan and the evidence produced during security testing/evaluation.','SA-11(3).3','The organization being inspected/assessed defines and documents the independence criteria the independent agent must satisfy prior to verifying the correct implementation of the developer security assessment plan and the evidence produced during security testing/evaluation. DoD has determined the independence criteria is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented independence criteria to ensure the organization being inspected/assessed defines the independence criteria the independent agent must satisfy prior to verifying the correct implementation of the developer security assessment plan and the evidence produced during security testing/evaluation. DoD has determined the independence criteria is not appropriate to define at the Enterprise level.'),
('003186','draft','2013-09-30','DISA FSO','policy','The organization ensures that the independent agent either is provided with sufficient information to complete the verification process or has been granted the authority to obtain such information.','SA-11(3).4','The organization being inspected/assessed provides the independent agent with sufficient information and access/authority to complete the verification process. The organization must maintain a record of information provided.','The organization conducting the inspection/assessment obtains and examines the record of information provided to ensure the organization being inspected/assessed provides the independent agent with sufficient information and access/authority to complete the verification process.'),
('003187','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform a manual code review of organization-defined specific code using organization-defined processes, procedures, and/or techniques.','SA-11(4).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service perform a manual code review of specific code defined in SA-11 (4), CCI 3188 using processes, procedures, and/or techniques defined in SA-11 (4), CCI 3189.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform a manual code review of specific code defined in SA-11 (4), CCI 3188 using processes, procedures, and/or techniques defined in SA-11 (4), CCI 3189.'),
('003188','draft','2013-09-30','DISA FSO','policy','The organization defines the specific code for which the developer of the information system, system component, or information system service is required to perform a manual code review using organization-defined process, procedures, and/or techniques.','SA-11(4).2','The organization being inspected/assessed defines and documents the specific code that requires the developer of the information system, system component, or information system service to perform a manual code review against using organization-defined process, procedures, and/or techniques.\n\nThe defined code shall include:\n1. random samples; and\n2. critical software and firmware components of information systems.\n\nDoD has determined the specific code is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented specific code to ensure the organization being inspected/assessed defines the specific code that requires the developer of the information system, system component, or information system service to perform a manual code review against using organization-defined process, procedures, and/or techniques. DoD has determined the specific code is not appropriate to define at the Enterprise level.'),
('003189','draft','2013-09-30','DISA FSO','policy','The organization defines the processes, procedures, and/or techniques to be used by the developer of the information system, system component, or information system service to perform a manual code review of organization-defined specific code.','SA-11(4).3','The organization being inspected/assessed requires in contracts/agreements that the developer define and document the processes, procedures, and/or techniques to be used to perform a manual code review of organization-defined specific code.\n\nManual code reviews identify weaknesses which are generally unavailable to more automated analytic tools and techniques such as static or dynamic analysis. Manual code reviews should be performed in conjunction with automated testing, such as static or dynamic analysis, to provide greater levels of analysis.\n\nDoD has determined the processes, procedures, and/or techniques are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented processes, procedures, and/or techniques to ensure the organization being inspected/assessed defines the processes, procedures, and/or techniques to be used by the developer of the information system, system component, or information system service to perform a manual code review of organization-defined specific code. DoD has determined the processes, procedures, and/or techniques are not appropriate to define at the Enterprise level.'),
('003190','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform penetration testing at an organization-defined breadth/depth and with organization-defined constraints.','SA-11(5).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service perform penetration testing at a breadth/depth defined in SA-11 (5), CCI 3191 and with constraints defined in SA-11 (5), CCI 3192.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform penetration testing at a breadth/depth defined in SA-11 (5), CCI 3191 and with constraints defined in SA-11 (5), CCI 3192.'),
('003191','draft','2013-09-30','DISA FSO','policy','The organization defines the breadth/depth at which the developer of the information system, system component, or information system service is required to perform penetration testing.','SA-11(5).2','The organization being inspected/assessed defines and documents the breadth/depth the developer of the information system, system component, or information system service is required to perform penetration testing. DoD has determined the breadth/depth are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented breadth/depth to ensure the organization being inspected/assessed defines the breadth/depth the developer of the information system, system component, or information system service is required to perform penetration testing. DoD has determined the constraints are not appropriate to define at the Enterprise level.'),
('003192','draft','2013-09-30','DISA FSO','policy','The organization defines the constraints on penetration testing performed by the developer of the information system, system component, or information system service.','SA-11(5).3','The organization being inspected/assessed defines and documents the constraints on penetration testing performed by developer of the information system, system component, or information system service.\n\nPenetration testing should use all available information technology product documentation (e.g., product/system design specifications, source code, and administrator/operator manuals) and can include, for example, white, gray, or black box testing to attempt circumventing security features of the information technology product or system. Penetration testing should be performed:\n1. by skilled security professionals working in controlled environments to simulate and execute adversary actions; and\n2. in conjunction with automated and manual code reviews to provide greater levels of analysis than would ordinarily be possible.\n\nDoD has determined the constraints are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented constraints to ensure the organization being inspected/assessed defines the constraints on penetration testing performed by developer of the information system, system component, or information system service. DoD has determined the constraints are not appropriate to define at the Enterprise level.'),
('003193','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform attack surface reviews.','SA-11(6).1','The organization being inspected/assessed requires within contracts/agreements that the developer perform and document attack surface reviews to uncover any accessible areas where weaknesses or deficiencies in the design and functionality of information systems (including the hardware, software, and firmware components) provide opportunities for adversaries to exploit vulnerabilities.\n\nAttack surface reviews may include:\n1. Analyzing both design and implementation changes to information systems;\n2. Testing the system with debug options off, or making the debug capabilities inaccessible to unauthorized users;\n3. Mitigating attack vectors generated as a result of the changes. Correction of identified flaws includes, for example, deprecation of unsafe functions; and\n4. Using configuration documents that describe how to configure OTS elements to limit their functionality or increase their security. These include DISA Security Technical Implementation Guides (STIGs) and NSA Security configuration guides. Perform this as early in the lifecycle as possible, so that unnecessary or dangerous functionality is not depended upon or does not go unnoticed.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform and document attack surface reviews.'),
('003194','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to verify that the scope of security testing/evaluation provides complete coverage of required security controls at an organization-defined depth of testing/evaluation.','SA-11(7).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service verify that the scope of security testing/evaluation provides complete coverage of required security controls at the depth of testing/evaluation defined in SA-11 (7), CCI 3195.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service verify that the scope of security testing/evaluation provides complete coverage of required security controls at the depth of testing/evaluation defined in SA-11 (7), CCI 3195.'),
('003195','draft','2013-09-30','DISA FSO','policy','The organization defines the depth of testing/evaluation to which the developer of the information system, system component, or information system service is required to verify that the scope of security testing/evaluation provides complete coverage of the required security controls.','SA-11(7).2','The organization being inspected/assessed defines and documents the depth of testing/evaluation to which the developer of the information system, system component, or information system service is required to verify that the scope of security testing/evaluation provides complete coverage of the required security controls.\n\n The developer can accomplish scope verification through a variety of analytic techniques that provide an increasing level of assurance corresponding to the degree of formality of the analysis. High levels of assurance can be provided by the use of formal modeling and analysis techniques including theorem provers, model checkers, and correlation between control implementation and corresponding test cases.\n\nDoD has determined the depth of testing/evaluation is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented depth of testing/evaluation to ensure the organization being inspected/assessed defines the depth of testing/evaluation to which the developer of the information system, system component, or information system service is required to verify that the scope of security testing/evaluation provides complete coverage of the required security controls. DoD has determined the depth of testing/evaluation is not appropriate to define at the Enterprise level.'),
('003196','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to employ dynamic code analysis tools to identify common flaws.','SA-11(8).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service employ dynamic code analysis tools to identify common flaws.\n\nDynamic code analysis tools include fuzz testing, using simulation, and white and black box testing. Dynamic code analysis should be performed in conjunction with static code analysis to provide greater levels of analysis.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service employ dynamic code analysis tools to identify common flaws.'),
('003197','draft','2013-09-30','DISA FSO ','policy','The organization requires the developer of the information system, system component, or information system service to document the results of the dynamic code analysis.','SA-11(8).2','The organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the type of dynamic analysis that was performed and the results (including defects).','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the results of the dynamic code analysis.'),
('003198','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined tailored acquisition strategies, contract tools, and procurement methods for the purchase of the information system, system component, or information system service from suppliers.','SA-12(1).1','The organization being inspected/assessed implements IAW the DoDI 5200.44 \"Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN) tailored acquisition strategies, contract tools, and procurement methods defined in SA-12 (1), CCI 3199 as a means to mitigate supply chain risk.\n\nThe organization being inspected/assessed must maintain documentation tracing the strategies, tools, and methods implemented to the organization-defined strategies, tools, and methods.','The organization conducting the inspection/assessment obtains and examines documentation tracing the strategies, tools, and methods implemented to the organization-defined strategies, tools, and methods to ensure that the tailored acquisition strategies, contract tools, and procurement methods identified in SA-12 (1), CCI 3199 have been implemented.'),
('003199','draft','2013-09-30','DISA FSO','policy','The organization defines tailored acquisition strategies, contract tools, and procurement methods to employ for the purchase of the information system, system component, or information system service from suppliers.','SA-12(1).2','The organization being inspected/assessed defines and documents the tailored acquisition strategies, contract tools, and procurement methods IAW DoDI 5200.44, \"Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN).\" Examples include:\n1. Transferring a portion of the risk to the developer or supplier through the use of contract language and incentives;\n2. Using contract language that requires the implementation of SCRM throughout the system lifecycle in applicable contracts and other acquisition and assistance instruments (grants, cooperative agreements, Cooperative Research and Development Agreements (CRADAs),and other transactions) examples include:\na. Language outlined in the Defense Acquisition Guidebook section 13.13. Contracting;\nb. Language requiring the use of protected mechanisms to deliver elements and data about elements, processes, and delivery mechanisms;\nc. Language that articulates that requirements flow down supply chain tiers to sub-prime suppliers.\n3. Incentives for suppliers that:\na. Implement required security safeguards and SCRM best practices;\nb. Promote transparency into their organizational processes and security practices;\nc. Provide additional vetting of the processes and security practices of subordinate suppliers, critical information system components, and services; and\nd. Implement contract to reduce SC risk down the contract stack.\n4. Gaining insight into supplier security practices;\n5. Using contract language and incentives to enable more robust risk management later in the lifecycle;\n6. Using a centralized intermediary or Blind Buy approaches to acquire element(s) to hide actual usage locations from an untrustworthy supplier or adversary;\n7. Exercise the authorities provided in section 806 of the 2011 NDAA, through Public Law 111-383 referenced in the Defense Federal Acquisition Regulation Supplement (DFAR); interim rule part 252.239-7018 Supply Chain Risk.\n\nDoD has determined the tailored acquisition strategies, contract tools, and procurement methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documentation containing the tailored acquisition strategies, contract tools, and procurement methods to ensure they have been defined IAW DoDI 5200.44, \"Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN).\"\n\nDoD has determined the tailored acquisition strategies, contract tools, and procurement methods are not appropriate to define at the Enterprise level.'),
('003200','draft','2013-09-30','DISA FSO','policy','The organization conducts a supplier review prior to entering into a contractual agreement to acquire the information system, system component, or information system service.','SA-12(2).1','The organization being inspected/assessed documents and implements a process to conduct a supplier review prior to entering into a contractual agreement to acquire the information system, system component, or information system service. Examples of items that can be considered in the review are the suppliers:\n1. Organization and process certifications;\n2. Security policies, procedures, and activities across the lifecycle;\n3. Supply chain and the criteria and methodology for selecting/managing their suppliers/service providers;\n4. Financials to determine if the supplier is financially stable;\n5. Foreign Ownership, Control, and Influence;\n6. Past performance and any documented supply chain incidents;\n7. Business relationships; and\n8. Maturity of business processes.\n\nThe organization must maintain a record of supplier review.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of supplier review to ensure the organization being inspected/assessed documents and implements a process to conduct a supplier review prior to entering into a contractual agreement to acquire the information system, system component, or information system service.'),
('003201','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined security safeguards to limit harm from potential adversaries identifying and targeting the organizational supply chain.','SA-12(5).1','The organization being inspected/assessed employs security safeguards defined in SA-12 (5), CCI 3202 to limit harm from potential adversaries identifying and targeting the organizational supply chain.\n\nThe organization must maintain a record of security safeguards employed.','The organization conducting the inspection/assessment obtains and examines the record of security safeguards supplied to ensure the organization being inspected/assessed employs security safeguards defined in SA-12 (5), CCI 3202 to limit harm from potential adversaries identifying and targeting the organizational supply chain.'),
('003202','draft','2013-09-30','DISA FSO','policy','The organization defines security safeguards to employ to limit harm from potential adversaries identifying and targeting the organizational supply chain.','SA-12(5).2','The organization being inspected/assessed defines and documents security safeguards to employ to limit harm from potential adversaries identifying and targeting the organizational supply chain IAW DoDI 5200.44.\n\nExamples of security safeguards that the organization should consider implementing to limit the harm from potential adversaries targeting the organizational supply chain, are:\n1. Using trusted physical delivery mechanisms that do not permit access to the element during delivery (ship via a protected carrier, use cleared/official couriers, or a diplomatic pouch);\n2. Using trusted electronic delivery of products and services (require downloading from approved, verification-enhanced sites);\n3. Avoiding the purchase of custom configurations, where feasible;\n4. Using procurement carve outs (i.e., exclusions to commitments or obligations), where feasible;\n5. Using defensive design approaches;\n6. Employing system OPSEC principles;\n7. Employing a diverse set of suppliers;\n8. Employing approved vendor lists with standing reputations in industry;\n9. Using a centralized intermediary and Blind Buy approaches to acquire element(s) to hide actual usage locations from an untrustworthy supplier or adversary Employing inventory management policies and processes;\n10. Using flexible agreements during each acquisition and procurement phase so that it is possible to meet emerging needs or requirements to address supply chain risk without requiring complete revision or re-competition of an acquisition or procurement;\n11. Using international, national, commercial or government standards to increase potential supply base;\n12. Limiting the disclosure of information that can become publicly available; and\n13. Minimizing the time between purchase decisions and required delivery.\nOrganizations should reference the SCRM Key Practices and Implementation Guide for DoD for additional guidance.\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The conducting the inspection/assessment obtains and examines the documented security safeguards to ensure they have been defined IAW DoDI 5200.44.\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003203','draft','2013-09-30','DISA FSO','policy','The organization conducts an assessment of the information system, system component, or information system service prior to selection, acceptance, or update.','SA-12(7).1','The organization being inspected/assessed or an independent, third-party entity must perform and document assessments that may include static analyses, dynamic analyses, simulations, white, gray, and black box testing, fuzz testing, penetration testing, and ensure that components or services are genuine (e.g., using tags, cryptographic hash verifications, or digital signatures). Where possible, testing should employ threat profiles based on the threats that the system is likely to face in the operational environment.','The organization conducting the inspection/assessment obtains and examines documented assessment(s) that were conducted by the organization prior to selection, acceptance, or update to ensure that the organization being inspected/assessed is assessing information systems, system components, or information system services prior to selection, acceptance, or update.'),
('003204','deprecated','2013-09-30','DISA FSO','policy','The organization conducts an assessment of the information system, system component, or information system service prior to selection, acceptance, or update.',NULL,NULL,NULL),
('003205','draft','2013-09-30','DISA FSO','policy','The organization uses all-source intelligence analysis of suppliers and potential suppliers of the information system, system component, or information system service.','SA-12(8).1','The organization being inspected/assessed documents and implements a process IAW DoDI 5200.44 to use all-source intelligence analysis of suppliers and potential suppliers of the information system, system component, or information system service.\n\nAll-source intelligence of suppliers that the organization may use includes:\n1. Defense Intelligence Agency (DIA) Threat Assessment Center (TAC), the enterprise focal point for supplier threat assessments for the DoD acquisition community risks;\n2. Other U.S. Government resources including:\na. Government Industry Data Exchange Program (GIDEP) Database where government and industry can record issues with suppliers, including counterfeits; and\nb. System for Award Management (SAM) Database of companies that are barred from doing business with the US Government.\n3. Open source and commercial research.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process IAW DoDI 5200.44 to use all-source intelligence analysis of suppliers and potential suppliers of the information system, system component, or information system service.'),
('003206','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined Operations Security (OPSEC) safeguards in accordance with classification guides to protect supply chain-related information for the information system, system component, or information system service.','SA-12(9).1','The organization being inspected/assessed implements Operations Security (OPSEC) safeguards defined in SA-12 (9), CCI 3206 to protect supply chain-related information for the information system, system component, or information system service.','The organization conducting the inspection/assessment obtains and examines any applicable artifacts showing the use of OPSEC safeguards to ensure the organization being inspected/assessed implements OPSEC safeguards defined in SA-12 (9), CCI 3206 to protect supply chain-related information for the information system, system component, or information system service.\n\nDoD has determined the OPSEC safeguards are not appropriate to define at the Enterprise level.'),
('003207','deprecated','2013-09-30','DISA FSO','policy','The organization employs organization-defined tailored acquisition strategies, contract tools, and procurement methods for the purchase of the information system, system component, or information system service from suppliers.',NULL,NULL,NULL),
('003208','deprecated','2013-09-30','DISA FSO','policy','The organization employs organization-defined tailored acquisition strategies, contract tools, and procurement methods for the purchase of the information system, system component, or information system service from suppliers.',NULL,NULL,NULL),
('003209','deprecated','2013-09-30','DISA FSO','policy','The organization employs organization-defined tailored acquisition strategies, contract tools, and procurement methods for the purchase of the information system, system component, or information system service from suppliers.',NULL,NULL,NULL),
('003210','draft','2013-09-30','DISA FSO','policy','The organization defines the Operations Security (OPSEC) safeguards to be employed in accordance with classification guides to protect supply chain-related information for the information system, system component, or information system service.','SA-12(9).2','The organization being inspected/assessed defines and documents Operations Security (OPSEC) safeguards IAW DoDD 5205.02E, DoD Manual 5205.02, and DoDI 5200.44.\n\nOPSEC safeguards may include:\n1. Limiting the disclosure of information needed to design, develop, test, produce, deliver, and support the element for example, supplier identities, supplier processes, potential suppliers, security requirements, design specifications, testing and evaluation result, and system/component configurations, including the use of direct shipping, blind buys, etc.;\n2. Extending supply chain awareness, education, and training for suppliers, intermediate users, and end users;\n3. Extending the range of OPSEC tactics, techniques, and procedures to potential suppliers, contracted suppliers, or sub-prime contractor tier of suppliers; and\n4. Using centralized support and maintenance services to minimize direct interactions between end users and original suppliers.\n\nDoD has determined the OPSEC safeguards are not appropriate to define at the Enterprise level.','The organization being inspected/assessed obtains and examines the documented OPSEC safeguards to ensure they have been defined IAW DoDD 5205.02E, DoD Manual 5205.02, and DoDI 5200.44.\n\nDoD has determined the OPSEC safeguards are not appropriate to define at the Enterprise level.'),
('003211','deprecated','2013-09-30','DISA FSO','policy','The organization defines the Operations Security (OPSEC) safeguards to be employed in accordance with classification guides to protect supply chain-related information for the information system, system component, or information system service.',NULL,NULL,NULL),
('003212','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined security safeguards to validate that the information system or system component received is genuine and has not been altered.','SA-12(10).1','The organization being inspected/assessed employs security safeguards to validate that the information system or system component received is genuine and has not been altered defined in SA-12 (10), CCI 3213. The organization must maintain a record of information system validation. The record must identify what safeguards are applied.\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the record of information system validation to ensure the organization being inspected/assessed employs security safeguards defined in SA-12 (10), CCI 3213 to validate that the information system or system component received is genuine and has not been altered.\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003213','draft','2013-09-30','DISA FSO','policy','The organization defines the security safeguards to be employed to validate that the information system or system component received is genuine and has not been altered.','SA-12(10).2','The organization being inspected/assessed defines and documents security safeguards to validate that the information system or system component received is genuine and has not been altered IAW DoDI 5200.44.\n\nSecurity safeguards may:\n1. Examine for:\na. Evidence of unauthorized tampering/modification, intentional bugging/subversion, or harmful features;\nb. Indicators of weaknesses such as unexpected size/dimensions, substandard workmanship, mismatched serial number or bar code, altered/ unexpected/ counterfeit trademarks or markings, or XRF (x-ray fluorescence); and\nc. Newly manufactured (not refurbished) elements and for valid licensing (including support agreements).\n2. Include:\na. Acceptance testing;\nb. Anti-tamper mechanisms (tamper-resistant and tamper-evident packaging, anti-tamper fence);\nc. Contact angle analysis and chemical surface analysis;\nd. Encryption (in motion and at rest);\ne. Watermarking mechanisms;\nf. Optical/nanotechnology tagging;\ng. Side-channel analysis;\nh. Performance and sub-element baseline; and\ni. Difficult-to-forge marks (such as digital signatures and hologram tags).\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure they have been defined IAW DoDI 5200.44.\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003214','draft','2013-09-30','DISA FSO','policy','The organization employs organizational analysis, independent third-party analysis, organizational penetration testing and/or independent third-party penetration testing of organization-defined supply chain elements, processes, and actors associated with the information system, system component, or information system service.','SA-12(11).1','The organization being inspected/assessed documents and implements processes to employ organizational analysis, independent third-party analysis, organizational penetration testing and/or independent third-party penetration testing of supply chain elements, processes and actors defined in SA-12 (11), CCI 3215 associated with the information system, system component, or information system service.\n\nPenetration testing/analysis should be performed:\n1. On potential system elements before accepting the system;\n2. As a realistic simulation of the active adversarys known adversary tactics, techniques, procedures (TTPs), and tools; and\n3. Throughout the lifecycle on physical and logical systems, elements, and processes.','The organization conducting the inspection/assessment obtains and examines the documented processes to ensure the organization being inspected/assessed employs organizational analysis, independent third-party analysis, organizational penetration testing and/or independent third-party penetration testing of supply chain elements, processes and actors defined in SA-12 (11), CCI 3215 associated with the information system, system component, or information system service.'),
('003215','draft','2013-09-30','DISA FSO','policy','The organization defines the supply chain elements, processes, and actors associated with the information system, system component, or information system service for organizational analysis, independent third-party analysis, organizational penetration testing and/or independent third-party penetration testing.','SA-12(11).2','The organization being inspected/assessed defines and documents the supply chain elements, processes, and actors associated with the information system, system component, or information system service for organizational analysis, independent third-party analysis, organizational penetration testing and/or independent third-party penetration testing.\n\nPenetration testing should be performed throughout the lifecycle on physical and logical systems, elements, and processes including:\n1. Hardware, software, and firmware development processes;\n2. Shipping/handling procedures;\n3. Personnel and physical security programs;\n4. Configuration management tools/measures to maintain provenance; and\n5. Any other programs, processes, or procedures associated with the production/distribution of supply chain elements.\n\nThe elements, processes, and actors must be defined IAW DoDI 5200.44.\n\nDoD has determined the elements, processes, and actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented supply chain elements, processes, and actors to ensure the organization being inspected/assessed defines the supply chain elements, processes, and actors associated with the information system, system component, or information system service for organizational analysis, independent third-party analysis, organizational penetration testing and/or independent third-party penetration testing IAW DoDI 5200.44. DoD has determined the elements, processes, and actions are not appropriate to define at the Enterprise level.'),
('003216','draft','2013-09-30','DISA FSO','policy','The organization establishes inter-organizational agreements with entities involved in the supply chain for the information system, system component, or information system service.','SA-12(12).1','The organization being inspected/assessed establishes and documents inter-organizational agreements with entities involved in the supply chain for the information system, system component, or information system service.','The organization conducting the inspection/assessment obtains and examines the documented inter-organizational agreements to ensure the organization being inspected/assessed establishes inter-organizational agreements with entities involved in the supply chain for the information system, system component, or information system service.'),
('003217','draft','2013-09-30','DISA FSO','policy','The organization establishes inter-organizational procedures with entities involved in the supply chain for the information system, system component, or information system service.','SA-12(12).2','The organization being inspected/assessed establishes and documents inter-organizational procedures with entities involved in the supply chain for the information system, system component, or information system service.','The organization conducting the inspection/assessment obtains and examines the documented inter-organizational procedures to ensure the organization being inspected/assessed establishes inter-organizational procedures with entities involved in the supply chain for the information system, system component, or information system service.'),
('003218','draft','2013-09-30','DISA FSO','policy','The organization employs organization-defined security safeguards to ensure an adequate supply of organization-defined critical information system components.','SA-12(13).1','The organization being inspected/assessed documents and implements a process to employ security safeguards defined in SA-12 (13), CCI 3219 to ensure an adequate supply of critical information system components defined in SA-12 (13), CCI 3220.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs security safeguards defined by SA-12 (13), CCI 3219 to ensure an adequate supply of critical information system components defined in SA-12 (13), CCI 3220.'),
('003219','draft','2013-09-30','DISA FSO','policy','The organization defines the security safeguards to be employed to ensure an adequate supply of organization-defined critical information system components.','SA-12(13).2','The organization being inspected/assessed defines and documents the security safeguards to be employed to ensure an adequate supply of organization-defined critical information system components.\n\nThe organization should employ security safeguards for critical materials, production, assembly, testing, packaging, delivery, and sustainment objects and determine what will be needed and when, and how quickly, for system and system element replacements. Safeguards include:\n1. Storing critical element spares near or with systems so that they can be rapidly replaced;\n2. Stockpiling of spare components to ensure operation during mission-critical times;\n3. Using multiple delivery paths and suppliers;\n4. Having a variety of vetted delivery paths;\n5. Using trusted and cleared contacts and shipping via a protected carrier (such as using cleared/official couriers, or a diplomatic pouch);\n6. Proactively manage the life cycle of their products through Diminishing Manufacturing Sources and Material Shortages (DMSMS). This may involve advance purchase and inventory of spare parts while they are widely available and verifiable.\n\n DoD has determined the security safeguards are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security safeguards to ensure the organization being inspected/assessed defines the security safeguards to be employed to ensure an adequate supply of organization-defined critical information system components.\n\nDoD has determined the security safeguards are not appropriate to define at the Enterprise level.'),
('003220','draft','2013-09-30','DISA FSO','policy','The organization defines the critical information system components for which organization-defined security safeguards are employed to ensure adequate supply.','SA-12(13).3','The organization being inspected/assessed defines and documents the critical information system components for which organization-defined security safeguards are employed to ensure adequate supply. DoD has determined the critical information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented critical information system components to ensure the organization being inspected/assessed defines the critical information system components for which organization-defined security safeguards are employed to ensure adequate supply. DoD has determined the critical information system components are not appropriate to define at the Enterprise level.'),
('003221','draft','2013-09-30','DISA FSO','policy','The organization establishes unique identification of organization-defined supply chain elements, processes, and actors for the information system, system component, or information system service.','SA-12(14).1','The organization being inspected/assessed establishes and documents unique identification of supply chain elements, processes, and actors defined in SA-12 (14), CCI 3223.','The organization conducting the inspection/assessment obtains and examines the documented unique identification of supply chain elements, processes, and actors to ensure the organization being inspected/assessed establishes unique identification of supply chain elements, processes, and actors defined in SA-12 (14), CCI 3223 for the information system, system component, or information system service.'),
('003222','draft','2013-09-30','DISA FSO','policy','The organization retains unique identification of organization-defined supply chain elements, processes, and actors for the information system, system component, or information system service.','SA-12(14).2','The organization being inspected/assessed retains previous versions of the unique identification of supply chain elements, processes, and actors documented IAW SA-12 (14), CCI 3221.','The organization conducting the inspection/assessment obtains and examines previous versions of the identification of supply chain elements, processes, and actors documented IAW SA-12 (14), CCI 3221 to ensure the organization being inspected/assessed retains unique identification of supply chain elements, processes, and actors.'),
('003223','draft','2013-09-30','DISA FSO','policy','The organization defines the supply chain elements, processes, and actors for the information system, system component, or information system service to establish and retain unique identification.','SA-12(14).3','The organization being inspected/assessed defines and documents the supply chain elements, processes, and actors for the information system, system component, or information system service to establish and retain unique identification. The elements, processes, and actors must be defined IAW DoDI 5200.44.\n\nThe organization should consider employing:\n1. Procedures for proposing, evaluating, and justifying relevant changes to system/component provenance for their impact on components, processes, systems, missions, and exposure to supply chain risks;\n2. Procedures for allocating responsibilities for the creation, maintenance, and monitoring of provenance are documented;\n3. Methods for tracking relevant purchasing, shipping, receiving, or transfer activities, including records of reviewer signatures for comparison;\n4. Processes for transferring provenance responsibility for systems or components between organizations across physical and logical boundaries including any approvals required;\n5. Procedures for tracking and documenting chain of custody of the system or component (Labeling (using serial numbers) and tagging (using radio-frequency identification [RFID] tags); and\n6. Security reviews for evaluating and vetting key personnel employed by acquirers or suppliers in any capacity (full-time employee, part-time employee, consultant, contractor, subcontractor, vendor, agent, etc.)\n\nDoD has determined the elements, processes, and actors are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented elements, processes, and actors to ensure the organization being inspected/assessed defines the supply chain elements, processes, and actors for the information system, system component, or information system service to establish and retain unique identification IAW DoDI 5200.44. DoD has determined the elements, processes, and actors are not appropriate to define at the Enterprise level.'),
('003224','draft','2013-09-30','DISA FSO','policy','The organization establishes a process to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.','SA-12(15).1','The organization being inspected/assessed documents and implements a process to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.\n\nThe organization being inspected/assessed will perform follow-on actions to address the weaknesses and deficiencies identified during assessments of supply chain (SC) elements (e.g., penetration testing, audits, verification/validation activities). Follow on actions may include:\n1. Performing failure or forensic analysis on elements and processes to determine the cause of failure. Isolate and diagnose the elements of the component that are not performing properly and assess the origin and mechanisms of the failure. Assess the impact of the failure, ways to detect failures, and mitigating actions (including ways to detect failures and preventing future occurrences);\n2. Initiate a plan to remediate vulnerabilities immediately upon detection which include:\na. Identifying the weakness associated with the vulnerability;\nb. Determining the root cause and context; and\nc. Remediating the vulnerability, depending on the likelihood of its exploitation and the severity of its consequences.\n3. Coordinating SC incident management activities with other organizations to ensure consistent and effective management of SC risk incidents; and\n4. Following established procedures for reporting incidents. If no procedure has been established, determine what information should flow in and out, to who, and in what circumstances;\n5. Establishing and maintain SC risk incident reporting connectivity to local, regional, and national incident management processes where established (e.g., IAVA, CERT/CC, US CERT, FBI, FISMA reporting), and possibly intelligence processes.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes a process to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.'),
('003225','draft','2013-09-30','DISA FSO','policy','The organization describes the trustworthiness required in the organization-defined information system, information system component, or information system service supporting its critical missions/business functions.','SA-13.1','The organization being inspected/assessed documents within its security plan the trustworthiness required in the information system, information system component, or information system service defined in SA-13, CCI 3226 supporting its critical missions/business functions.','The organization conducting the inspection/assessment obtains and examines the security plan to ensure the organization being inspected/assessed documents within its security plan the trustworthiness required in the information system, information system component, or information system service defined in SA-13, CCI 3226 supporting its critical missions/business functions.'),
('003226','draft','2013-09-30','DISA FSO','policy','The organization defines the information system, information system component, or information system service supporting its critical missions/business functions in which the trustworthiness must be described.','SA-13.2','The organization being inspected/assessed defines and documents the information system, information system component, or information system service supporting its critical missions/business functions in which the trustworthiness must be described. DoD has determined the information system, information system component, or information system service is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system, information system component, or information system service to ensure the organization being inspected/assessed defines the information system, information system component, or information system service supporting its critical missions/business functions in which the trustworthiness must be described. DoD has determined the information system, information system component, or information system service is not appropriate to define at the Enterprise level.'),
('003227','draft','2013-09-30','DISA FSO','policy','The organization implements an organization-defined assurance overlay to achieve trustworthiness required to support its critical missions/business functions.','SA-13.3','The organization being inspected/assessed implements an assurance overlay defined in SA-13, CCI 3228 to achieve trustworthiness required to support its critical missions/business functions.','The organization conducting the inspection/assessment examines the information system to ensure the organization being inspected/assessed implements an assurance overlay defined in SA-13, CCI 3228 to achieve trustworthiness required to support its critical missions/business functions.'),
('003228','draft','2013-09-30','DISA FSO','policy','The organization defines an assurance overlay to be implemented to achieve trustworthiness required to support its critical missions/business functions.','SA-13.4','The organization being inspected/assessed defines and documents an assurance overlay to be implemented to achieve trustworthiness required to support its critical missions/business functions. DoD has determined the assurance overlay is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented assurance overlay to ensure the organization being inspected/assessed defines an assurance overlay to be implemented to achieve trustworthiness required to support its critical missions/business functions. DoD has determined the assurance overlay is not appropriate to define at the Enterprise level.'),
('003229','draft','2013-09-30','DISA FSO','policy','The organization identifies critical information system components by performing a criticality analysis for organization-defined information systems, information system components, or information system services at organization-defined decision points in the system development life cycle.','SA-14.1','The organization being inspected/assessed identifies and documents critical information system components by performing a criticality analysis for information systems, information system components, or information system services IAW DoDI 5200.44. Information systems include all DoD Information Technology.\n\nCriticality analysis is the primary method by which a program identifies mission-critical functions and associated components. Criticality analysis includes the following iterative steps:\n1. Identify and group mission threads.\n2. Decompose the mission threads into their mission-critical functions and assign them criticality levels.\n3. Map the mission-critical functions to the system architecture and identify the defined system components (hardware, software, and firmware) that implement those functions (i.e., components that are critical to the mission effectiveness of the system or an interfaced network).\n4. Allocate criticality levels to those components that have been defined.\n\nCriticality levels are determined by assessing the relative impact on the systems ability to complete its mission if the function and associated component fails. Level I is total mission failure, Level II is significant/unacceptable degradation, Level III is partial/acceptable, and Level IV is negligible.\n\nOnce the program has identified critical components through the criticality analysis, the program systems engineers and SSEs can use the results along with the vulnerability assessment and threat assessment to determine the risk.\n\nThe organization should reference the Defense Acquisition Guidebook (DAG) Chapter 13 for more information.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed identifies critical information system components by performing a criticality analysis for information systems, information system components, or information system services IAW DoDI 5200.44.'),
('003230','draft','2013-09-30','DISA FSO','policy','The organization identifies critical information system functions by performing a criticality analysis for organization-defined information systems, information system components, or information system services at organization-defined decision points in the system development life cycle.','SA-14.2','The organization being inspected/assessed identifies and documents critical information system functions by performing a criticality analysis for information systems, information system components, or information system services IAW DoDI 5200.44.\n\nCriticality analysis is the primary method by which a program identifies mission-critical functions and associated components. Criticality analysis includes the following iterative steps:\n1. Identify and group mission threads.\n2. Decompose the mission threads into their mission-critical functions and assign them criticality levels.\n3. Map the mission-critical functions to the system architecture and identify the defined system components (hardware, software, and firmware) that implement those functions (i.e., components that are critical to the mission effectiveness of the system or an interfaced network).\n4. Allocate criticality levels to those components that have been defined.\n\nCriticality levels are determined by assessing the relative impact on the systems ability to complete its mission if the function and associated component fails. Level I is total mission failure, Level II is significant/unacceptable degradation, Level III is partial/acceptable, and Level IV is negligible.\n\nOnce the program has identified critical functions through the criticality analysis, the program systems engineers and SSEs can use the results along with the vulnerability assessment and threat assessment to determine the risk.\n\nThe organization should reference the Defense Acquisition Guidebook (DAG) Chapter 13 for more information.','The organization conducting the inspection/assessment obtains and examines the documented information system functions to ensure the organization being inspected/assessed identifies critical information system functions by performing a criticality analysis for information systems, information system components, or information system services IAW DoDI 5200.44.'),
('003231','draft','2013-09-30','DISA FSO','policy','The organization defines the information systems, information system components, or information system services for which the organization identifies critical information system components and functions for criticality analysis.','SA-14.3','The organization being inspected/assessed defines and documents the information systems, information system components, or information system services for which the organization identifies critical information system components and functions for criticality analysis IAW DoDI 5200.44.\n\nThe organization should perform Criticality Analysis to identify and prioritize mission-critical functions and critical components in accordance with the DoDI 5200.44. The criticality analysis allows a program to focus attention (and resources) on the system capabilities, mission-critical functions that matter most. Mission-critical functions are those functions of the system that, if corrupted or disabled, would likely lead to mission failure or degradation. Mission-critical components are primarily the elements of the system (hardware, software, and firmware) that implement critical functions; however, system components that perform defensive functions to protect inherently critical components and other components with unmediated access to inherently critical components, may themselves be mission critical.\n\nDoD has determined the decision points are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems, information system components, or information system services to ensure they have been defined IAW DoDI 5200.44.\n\nDoD has determined the information systems, information system components, or information system services are not appropriate to define at the Enterprise level.'),
('003232','draft','2013-09-30','DISA FSO','policy','The organization defines the decision points in the system development life cycle at which to perform a criticality analysis to identify critical information system components and functions for organization-defined information systems, information system components, or information system services.','SA-14.4','The organization being inspected/assessed defines and documents the decision points in the system development life cycle at which to perform a criticality analysis to identify critical information system components and functions for organization-defined information systems, information system components , or information system services IAW DoDI 5200.44 and DoDI 5000.2.\n\nCriticality analysis is an iterative process that should be performed whenever an architecture or design is being developed or modified and executed across the acquisition lifecycle, building on growing maturity and updated information, in preparation for acquisition milestone reviews, and at other points in the acquisition lifecycle as defined by the DoDI 5000.2.\n\nA DoD program needs to perform criticality analysis throughout the acquisition life cycle. As a minimum, DoD programs need to perform / update a criticality analysis, along with the threat assessment, vulnerability assessment, risk assessment, cost-benefit trade-off and countermeasure selection, before each technical review.\n\nDoD has determined the decision points are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented decision points to ensure they have been defined IAW DoDI 5200.44 and DoDI 5000.2.\n\n\nDoD has determined the decision points are not appropriate to define at the Enterprise level.'),
('003233','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to follow a documented development process.','SA-15.1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service to follow a documented development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service to follow a documented development process.'),
('003234','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process explicitly addresses security requirements.','SA-15.2','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service explicitly addresses security requirements.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service explicitly addresses security requirements.'),
('003235','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process identifies the standards used in the development process.','SA-15.3','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service identifies the standards used in the development process, for example, programming languages and computer-aided design (CAD) systems.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service identifies the standards used in the development process.'),
('003236','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process identifies the tools used in the development process.','SA-15.4','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service identifies the tools used in the development process, for example, programming languages and computer-aided design (CAD) systems.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service identifies the tools used in the development process.'),
('003237','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process documents the specific tool options and tool configurations used in the development process.','SA-15.5','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service documents the specific tool options and tool configurations used in the development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service documents the specific tool options and tool configurations used in the development process.'),
('003238','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process documents changes to the process and/or tools used in development.','SA-15.6','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service documents changes to the process and/or tools used in development.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service documents changes to the process and/or tools used in development.'),
('003239','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process manages changes to the process and/or tools used in development.','SA-15.7','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service document a process to manage changes to the process and/or tools used in development.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document a process to manage changes to the process and/or tools used in development.'),
('003240','draft','2013-09-30','DISA FSO','policy','The documented information system, system component, or information system service development process ensures the integrity of changes to the process and/or tools used in development.','SA-15.8','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service document the integrity of changes to the process and/or tools used in development.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service document the integrity of changes to the process and/or tools used in development.'),
('003241','draft','2013-09-30','DISA FSO','policy','The organization reviews the development process in accordance with organization-defined frequency to determine if the development process selected and employed can satisfy organization-defined security requirements.','SA-15.9','The organization being inspected/assessed documents and implements a process to review the development process before first use and annually thereafter to determine if the development process selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. Reviews of development processes can include, for example, the use of capability maturity model integration (CMMI) to determine the potential effectiveness of such processes.\n\nThe organization must maintain a record of reviews.\n\nDoD has defined the frequency as before first use and annually thereafter.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews the development process before first use and annually thereafter to determine if the development process selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. DoD has defined the frequency as before first use and annually thereafter.'),
('003242','draft','2013-09-30','DISA FSO','policy','The organization reviews the development standards in accordance with organization-defined frequency to determine if the development standards selected and employed can satisfy organization-defined security requirements.','SA-15.10','The organization being inspected/assessed documents and implements a process to review the development standards before first use and annually thereafter to determine if the development standards selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. The organization must maintain a record of reviews. DoD has defined the frequency as before first use and annually thereafter.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews the development standards before first use and annually thereafter to determine if the development standards selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. DoD has defined the frequency as before first use and annually thereafter.'),
('003243','draft','2013-09-30','DISA FSO','policy','The organization reviews the development tools in accordance with organization-defined frequency to determine if the development tools selected and employed can satisfy organization-defined security requirements.','SA-15.11','The organization being inspected/assessed documents and implements a process to review the development tools before first use and annually thereafter to determine if the development tools selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. The organization must maintain a record of reviews. DoD has defined the frequency as before first use and annually thereafter.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews the development tools before first use and annually thereafter to determine if the development tools selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. DoD has defined the frequency as before first use and annually thereafter.'),
('003244','draft','2013-09-30','DISA FSO','policy','The organization reviews the development tool options/configurations in accordance with organization-defined frequency to determine if the development tool options/configurations selected and employed can satisfy organization-defined security requirements.','SA-15.12','The organization being inspected/assessed documents and implements a process to review the development tool options/configurations before first use and annually thereafter to determine if the development tool options/configurations selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. The organization must maintain a record of reviews. DoD has defined the frequency as before first use and annually thereafter.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reviews to ensure the organization being inspected/assessed reviews the development tool options/configurations before first use and annually thereafter to determine if the development tool options/configurations selected and employed can satisfy the security requirements defined in SA-15, CCI 3246. DoD has defined the frequency as before first use and annually thereafter.'),
('003245','draft','2013-09-30','DISA FSO','policy','The organization defines the frequency on which to review the development process, standards, tools, and tool options/configurations to determine if the process, standards, tools, and tool options/configurations selected and employed can satisfy organization-defined security requirements.','SA-15.13','DoD has defined the frequency as before first use and annually thereafter.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the frequency as before first use and annually thereafter.'),
('003246','draft','2013-09-30','DISA FSO','policy','The organization defines the security requirements that must be satisfied by conducting a review of the development process, standards, tools, and tool options/configurations.','SA-15.14','The organization being inspected/assessed defines and documents the security requirements that must be satisfied by conducting a review of the development process, standards, tools, and tool options/configurations. DoD has determined the security requirements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented security requirements to ensure the organization being inspected/assessed defines the security requirements that must be satisfied by conducting a review of the development process, standards, tools, and tool options/configurations. DoD has determined the security requirements are not appropriate to define at the Enterprise level.'),
('003247','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to define quality metrics at the beginning of the development process.','SA-15(1).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service define quality metrics at the beginning of the development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service define quality metrics at the beginning of the development process.'),
('003248','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide evidence of meeting the quality metrics in accordance with organization-defined frequency, organization-defined program review milestones and/or upon delivery.','SA-15(1).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service provide evidence of meeting the quality metrics in accordance with the frequency defined in SA-15 (1), CCI 3249, at a minimum, program review milestones IAW DoD Memorandum \"Document Streamlining - Program Protection Plan (PPP)\" and/or upon delivery.\n\nDoD has defined the program review milestones as at a minimum, program review milestones IAW DoD Memorandum \"Document Streamlining - Program Protection Plan (PPP).\"','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service provide evidence of meeting the quality metrics in accordance with the frequency defined in SA-15 (1), CCI 3249, at a minimum, program review milestones IAW DoD Memorandum \"Document Streamlining - Program Protection Plan (PPP)\" and/or upon delivery.\n\nDoD has defined the program review milestones as at a minimum, program review milestones IAW DoD Memorandum \"Document Streamlining - Program Protection Plan (PPP).\"'),
('003249','draft','2013-09-30','DISA FSO','policy','The organization defines the frequency on which the developer of the information system, system component, or information system service is required to provide evidence of meeting the quality metrics.','SA-15(1).3','The organization being inspected/assessed defines and documents the frequency that is required by the developer of the information system, system component, or information system service to provide evidence of meeting the quality metrics. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency that is required by the developer of the information system, system component, or information system service to provide evidence of meeting the quality metrics. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('003250','draft','2013-09-30','DISA FSO','policy','The organization defines the program review milestones at which the developer of the information system, system component, or information system service is required to provide evidence of meeting the quality metrics.','SA-15(1).4','DoD has defined the program review milestones as at a minimum, program review milestones IAW DoD Memorandum \"Document Streamlining - Program Protection Plan (PPP).\"','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the program review milestones as at a minimum, program review milestones IAW DoD Memorandum \"Document Streamlining - Program Protection Plan (PPP).\"'),
('003251','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to select a security tracking tool for use during the development process.','SA-15(2).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service select a security tracking tool for use during the development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service select a security tracking tool for use during the development process.'),
('003252','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to employ a security tracking tool for use during the development process.','SA-15(2).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service employ a security tracking tool for use during the development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service employ a security tracking tool for use during the development process.'),
('003253','draft','2013-09-30','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to perform a criticality analysis at an organization-defined breadth/depth and at organization-defined decision points in the system development life cycle.','SA-15(3).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service perform a criticality analysis at the breadth/depth IAW DoDI 5200.44.\n\nThe organization should develop Request for Proposals (RFPs) and other contract language that require contractors to perform Criticality Analyses (CAs) periodically. Developer input into criticality analysis provides detailed design documentation for information system components (e.g., functional specifications, high-level designs, low-level designs, and source code/hardware schematics). Criticality Analysis should be conducted in accordance with the DoDI 5200.44 and the DoDI 5000.2.\n\nOnce the program has identified critical functions through the criticality analysis, the program systems engineers and SSEs can use the results along with the vulnerability assessment and threat assessment to determine the risk.\n\nThe organization should reference the Defense Acquisition Guidebook (DAG) Chapter 13 for more information.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform a criticality analysis at the breadth/depth IAW DoDI 5200.44.'),
('003254','draft','2013-09-30','DISA FSO','policy','The organization defines the breadth/depth at which the developer of the information system, system component, or information system service is required to perform a criticality analysis.','SA-15(3).2','The organization being inspected/assessed defines and documents the breadth/depth the developer of the information system, system component, or information system service is required to perform a criticality analysis IAW DoDI 5200.44.\n\nThe criticality analysis allows a program to focus attention (and resources) on the system capabilities, mission-critical functions that matter most. Mission-critical functions are those functions of the system that, if corrupted or disabled, would likely lead to mission failure or degradation. Mission-critical components are primarily the elements of the system (hardware, software, and firmware) that implement critical functions; however, system components that perform defensive functions to protect inherently critical components and other components with unmediated access to inherently critical components, may themselves be mission critical.\n\nCriticality analysis is the primary method by which a program identifies mission-critical functions and associated components. Criticality analysis includes the following iterative steps:\n1. Identify and group mission threads.\n2. Decompose the mission threads into their mission-critical functions and assign them criticality levels.\n3. Map the mission-critical functions to the system architecture and identify the defined system components (hardware, software, and firmware) that implement those functions (i.e., components that are critical to the mission effectiveness of the system or an interfaced network).\n4. Allocate criticality levels to those components that have been defined.\n\nCriticality levels are determined by assessing the relative impact on the systems ability to complete its mission if the function and associated component fails. Level I is total mission failure, Level II is significant/unacceptable degradation, Level III is partial/acceptable, and Level IV is negligible.\n\nThe organization should reference the Defense Acquisition Guidebook (DAG) Chapter 13 for more information.\n\nDoD has determined the breadth/depth are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented breadth/depth to ensure the organization being inspected/assessed defines the breadth/depth the developer of the information system, system component, or information system service is required to perform a criticality analysis IAW DoDI 5200.44.\n\nDoD has determined the breadth/depth are not appropriate to define at the Enterprise level.'),
('003255','draft','2013-09-30','DISA FSO','policy','The organization defines decision points in the system development life cycle at which the developer of the information system, system component, or information system service is required to perform a criticality analysis.','SA-15(3).3','The organization being inspected/assessed defines and documents decision points in the system development life cycle the developer of the information system, system component, or information system service is required to perform a criticality analysis IAW DoDI 5200.44 and DoDI 5000.2.\n\nCriticality analysis is an iterative process that should be performed whenever an architecture or design is being developed or modified and executed across the acquisition lifecycle, building on growing maturity and updated information.\n\nCriticality analysis is performed throughout the acquisition life cycle. As a minimum, the developer should support the performing and update a criticality analysis, along with the threat assessment, vulnerability assessment, risk assessment, cost-benefit trade-off and countermeasure selection, before each technical review.','The organization conducting the inspection/assessment obtains and examines the documented decision points to ensure the organization being inspected/assessed defines decision points in the system development life cycle the developer of the information system, system component, or information system service is required to perform a criticality analysis IAW DoDI 5200.44 and DoDI 5000.2.\n\nDoD has determined the decision points are not appropriate to define at the Enterprise level.'),
('003256','draft','2013-09-30','DISA FSO','policy','The organization requires that developers perform threat modeling for the information system at an organization-defined breadth/depth.','SA-15(4).1','The organization being inspected/assessed requires within contracts/agreements that the developers perform threat modeling for the information system at the breadth/depth defined in SA-15 (4), CCI 3258.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developers perform threat modeling for the information system at the breadth/depth defined in SA-15 (4), CCI 3258.'),
('003257','draft','2013-09-30','DISA FSO','policy','The organization requires that developers perform a vulnerability analysis for the information system at an organization-defined breadth/depth.','SA-15(4).2','The organization being inspected/assessed requires within contracts/agreements that the developers perform a vulnerability analysis for the information system at the breadth/depth defined in SA-15 (4), CCI 3259 to inform design or implementation changes and resulting vulnerabilities are accounted for during development . Vulnerability analysis should consider a review of system design and may include static analyses, dynamic analyses, simulations, and penetration testing. The developer should document the type of vulnerability analysis that was performed, the results (including defects) and any follow on actions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developers perform a vulnerability analysis for the information system at the breadth/depth defined in SA-15 (4), CCI 3259.'),
('003258','draft','2013-09-30','DISA FSO','policy','The organization defines the breadth/depth at which threat modeling for the information system must be performed by developers.','SA-15(4).3','The organization being inspected/assessed requires within contracts/agreements that the developers perform threat modeling for the information system at the breadth/depth defined in SA-15 (4), CCI 3258.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developers perform threat modeling for the information system at the breadth/depth defined in SA-15 (4), CCI 3258.'),
('003259','draft','2013-09-30','DISA FSO','policy','The organization defines the breadth/depth at which vulnerability analysis for the information system must be performed by developers.','SA-15(4).4','The organization being inspected/assessed requires within contracts/agreements that the developers perform a vulnerability analysis for the information system at the breadth/depth defined in SA-15 (4), CCI 3259 to inform design or implementation changes and resulting vulnerabilities are accounted for during development . Vulnerability analysis should consider a review of system design and may include static analyses, dynamic analyses, simulations, and penetration testing. The developer should document the type of vulnerability analysis that was performed, the results (including defects) and any follow on actions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developers perform a vulnerability analysis for the information system at the breadth/depth defined in SA-15 (4), CCI 3259.'),
('003260','draft','2013-09-30','DISA FSO','policy','Threat modeling performed by the developer for the information system uses organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels.','SA-15(4).5','The organization being inspected/assessed requires within contracts/agreements that the developer\'s threat modeling include the use of information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels defined in SA-15 (4), CCI 3262.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed documents within their contracts/agreements, their requirement that the developer\'s threat modeling include the use of information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels defined in SA-15 (4), CCI 3262.'),
('003261','draft','2013-09-30','DISA FSO','policy','Vulnerability analysis performed by the developer for the information system uses organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels.','SA-15(4).6','The organization being inspected/assessed requires within contracts/agreements that the developer\'s vulnerability analysis include the use of information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels defined in SA-15 (4), CCI 3263. Vulnerability analysis should consider a review of system design and may include static analyses, dynamic analyses, simulations, and penetration testing. The developer should document the type of vulnerability analysis that was performed, the results (including defects) and any follow on actions.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed documents within their contracts/agreements, their requirement that the developer\'s vulnerability analysis include the use of information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels defined in SA-15 (4), CCI 3263.'),
('003262','draft','2013-09-30','DISA FSO','policy','The organization defines information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used to perform threat modeling for the information system by the developer.','SA-15(4).7','The organization being inspected/assessed defines and documents information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used to perform threat modeling for the information system by the developer. DoD has determined the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information to ensure the organization being inspected/assessed defines information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used to perform threat modeling for the information system by the developer. DoD has determined the information is not appropriate to define at the Enterprise level.'),
('003263','draft','2013-09-30','DISA FSO','policy','The organization defines information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used to perform a vulnerability analysis for the information system by the developer.','SA-15(4).8','The organization being inspected/assessed defines and documents information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used to perform a vulnerability analysis for the information system by the developer. DoD has determined the information is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information to ensure the organization being inspected/assessed defines information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used to perform a vulnerability analysis for the information system by the developer. DoD has determined the information is not appropriate to define at the Enterprise level.'),
('003264','draft','2013-09-30','DISA FSO','policy','The organization requires the threat modeling performed by the developers employ organization-defined tools and methods.','SA-15(4).9','The organization being inspected/assessed requires within contracts/agreements that the threat modeling performed by the developers employ the tools and methods defined in SA-15 (4), CCI 3266.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the threat modeling performed by the developers employ the tools and methods defined in SA-15 (4), CCI 3266.'),
('003265','draft','2013-09-30','DISA FSO','policy','The organization requires the vulnerability analysis performed by the developers employ organization-defined tools and methods.','SA-15(4).10','The organization being inspected/assessed requires within contracts/agreements that the vulnerability analysis performed by the developers employ the tools and methods defined in SA-15 (4), CCI 3267.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the vulnerability analysis performed by the developers employ the tools and methods defined in SA-15 (4), CCI 3267.'),
('003266','draft','2013-09-30','DISA FSO','policy','The organization defines tools and methods to be employed to perform threat modeling for the information system by the developer.','SA-15(4).11','The organization being inspected/assessed defines and documents tools and methods to be employed to perform threat modeling for the information system by the developer. DoD has determined the tools and methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented tools and methods to ensure the organization being inspected/assessed defines tools and methods to be employed to perform threat modeling for the information system by the developer. DoD has determined the tools and methods are not appropriate to define at the Enterprise level.'),
('003267','draft','2013-09-30','DISA FSO','policy','The organization defines tools and methods to be employed to perform a vulnerability analysis for the information system by the developer.','SA-15(4).12','The organization being inspected/assessed defines and documents tools and methods to be employed to perform a vulnerability analysis for the information system by the developer. DoD has determined the tools and methods are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented tools and methods to ensure the organization being inspected/assessed defines tools and methods to be employed to perform a vulnerability analysis for the information system by the developer. DoD has determined the tools and methods are not appropriate to define at the Enterprise level.'),
('003268','draft','2013-09-30','DISA FSO','policy','The organization requires that developers performing threat modeling for the information system produce evidence that meets organization-defined acceptance criteria.','SA-15(4).13','The organization being inspected/assessed requires within contracts/agreements that the developers performing threat modeling for the information system produces evidence that meet the acceptance criteria defined in SA-15 (4), CCI 3270.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developers performing threat modeling for the information system produces evidence that meet the acceptance criteria defined in SA-15 (4), CCI 3270.'),
('003269','draft','2013-09-30','DISA FSO','policy','The organization requires that developers performing vulnerability analysis for the information system produce evidence that meets organization-defined acceptance criteria.','SA-15(4).14','The organization being inspected/assessed requires within contracts/agreements that the developers performing vulnerability analysis for the information system produces evidence that meet the acceptance criteria defined in SA-15 (4), CCI 3271.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the vulnerability analysis performed by the developers performing vulnerability analysis for the information system produces evidence that meet the acceptance criteria defined in SA-15 (4), CCI 3271.'),
('003270','draft','2013-09-30','DISA FSO','policy','The organization defines the acceptance criteria that must be met when threat modeling of the information system is performed by the developer.','SA-15(4).15','The organization being inspected/assessed defines and documents the acceptance criteria that must be met when threat modeling of the information system is performed by the developer. DoD has determined the acceptance criteria is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented acceptance criteria to ensure the organization being inspected/assessed defines the acceptance criteria that must be met when threat modeling of the information system is performed by the developer. DoD has determined the acceptance criteria is not appropriate to define at the Enterprise level.'),
('003271','draft','2013-10-03','DISA FSO','policy','The organization defines the acceptance criteria that must be met when vulnerability analysis of the information system is performed by the developer.','SA-15(4).16','The organization being inspected/assessed defines and documents the acceptance criteria that must be met when vulnerability analysis of the information system is performed by the developer. DoD has determined the acceptance criteria is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented acceptance criteria to ensure the organization being inspected/assessed defines the acceptance criteria that must be met when vulnerability analysis of the information system is performed by the developer. DoD has determined the acceptance criteria is not appropriate to define at the Enterprise level.'),
('003272','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to reduce attack surfaces to organization-defined thresholds.','SA-15(5).1','The organization being inspected/assessed requires the developer to perform attack surface reduction activities to reduce risk to organizations by giving attackers less opportunity to exploit weaknesses or vulnerabilities.\n\nAttack surface reduction may include:\n1. Testing and delivering the system with debug options off, or making the debug capabilities inaccessible to unauthorized users;\n2. Applying the principle of least privilege;\n3. Applying the principle of least functionality (i.e., restricting ports, protocols, functions, and services), deprecating unsafe functions, and eliminating application programming interfaces (APIs) that are vulnerable to cyber attacks; and\n4. Employing layered defenses.\n5. Using trusted physical delivery mechanisms that do not permit access to the element during delivery (ship via a protected carrier, use cleared/official couriers, or a diplomatic pouch);\n6. Using trusted logical delivery of products and services (require downloading from approved, verification-enhanced sites);\n7. Avoiding the purchase of custom configurations;\n8. Using procurement carve outs (i.e., exclusions to commitments or obligations);\n9. Using defensive design approaches;\n10. Minimizing the time between purchase decisions and required delivery;\n11. Employing a diverse set of suppliers;\n12. Employing approved vendor lists with standing reputations in industry;\n13. Diversifying and disperse how the product is acquired (e.g. Spot Markets); and\n14. Employing inventory management policies and processes.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service reduce attack surfaces to thresholds defined in SA-15 (5), CCI 3273.'),
('003273','draft','2013-10-03','DISA FSO','policy','The organization defines the thresholds to which the developer of the information system, system component, or information system service is required to reduce attack surfaces.','SA-15(5).2','The organization being inspected/assessed defines and documents the thresholds that the developer of the information system, system component, or information system service is required to reduce attack surfaces. DoD has determined the thresholds are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented thresholds to ensure the organization being inspected/assessed defines the thresholds that the developer of the information system, system component, or information system service is required to reduce attack surfaces. DoD has determined the thresholds are not appropriate to define at the Enterprise level.'),
('003274','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to implement an explicit process to continuously improve the development process.','SA-15(6).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service implement an explicit process to continuously improve the development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service implement an explicit process to continuously improve the development process.'),
('003275','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system services to perform an automated vulnerability analysis using organization-defined tools.','SA-15(7).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service perform an automated vulnerability analysis using the tools defined in SA-15 (7), CCI 3276.\n\nThe organization should require the developer to perform automated vulnerability analysis which may include dynamic analyses, static analyses, and regression testing tools. Automated testing should be performed in conjunction with manual testing to provide greater levels of analysis.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service perform an automated vulnerability analysis using the tools defined in SA-15 (7), CCI 3276.'),
('003276','draft','2013-10-03','DISA FSO','policy','The organization defines the tools the developer of the information system, system component, or information system services uses to perform an automated vulnerability analysis.','SA-15(7).2','The organization being inspected/assessed defines and documents the tools the developer of the information system, system component, or information system services uses to perform an automated vulnerability analysis. DoD has determined the tools are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented tools to ensure the organization being inspected/assessed defines the tools the developer of the information system, system component, or information system services uses to perform an automated vulnerability analysis. DoD has determined the tools are not appropriate to define at the Enterprise level.'),
('003277','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system services to determine the exploitation potential for discovered vulnerabilities.','SA-15(7).3','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service determine the exploitation potential for discovered vulnerabilities.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service determine the exploitation potential for discovered vulnerabilities.'),
('003278','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system services to determine potential risk mitigations for delivered vulnerabilities.','SA-15(7).4','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service determine potential risk mitigations for delivered vulnerabilities.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service determine potential risk mitigations for delivered vulnerabilities.'),
('003279','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system services to deliver the outputs of the tools and results of the vulnerability analysis to organization-defined personnel or roles.','SA-15(7).5','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service deliver the outputs of the tools and results of the vulnerability analysis to the ISSO, ISSM, and PM.\n\nDoD has defined the personnel or roles as the ISSO, ISSM, and PM.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service deliver the outputs of the tools and results of the vulnerability analysis to the ISSO, ISSM, and PM.\n\nDoD has defined the personnel or roles as the ISSO, ISSM, and PM.'),
('003280','draft','2013-10-03','DISA FSO','policy','The organization defines the personnel or roles to whom the outputs of the tools and results of the vulnerability analysis are delivered.','SA-15(7).6','DoD has defined the personnel or roles as the ISSO, ISSM, and PM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as the ISSO, ISSM, and PM.'),
('003281','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to use threat modeling from similar systems, components, or services to inform the current development process.','SA-15(8).1','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service use threat modeling from similar systems, components, or services to inform the current development process.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service use threat modeling from similar systems, components, or services to inform the current development process.'),
('003282','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to use vulnerability analysis from similar systems, components, or services to inform the current development process.','SA-15(8).2','The organization being inspected/assessed requires within contracts/agreements that the developer of the information system, system component, or information system service use vulnerability analysis from similar systems, components, or services to inform the current development process and potential design or implementation issues. Authoritative vulnerability information is available from a variety of public and private sector sources including, for example, the National Vulnerability Database and the Government/Industry Data Exchange Program (GIDEP).','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service use vulnerability analysis from similar systems, components, or services to inform the current development process.'),
('003283','draft','2013-10-03','DISA FSO','policy','The organization approves the use of live data in development environments for the information system, system component, or information system service.','SA-15(9).1','The organization being inspected/assessed documents and implements a process to approve the use of live data in development environments for the information system, system component, or information system service. The organization must maintain a record of approvals.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of approvals to ensure the organization being inspected/assessed approves the use of live data in development environments for the information system, system component, or information system service.'),
('003284','draft','2013-10-03','DISA FSO','policy','The organization approves the use of live data in test environments for the information system, system component, or information system service.','SA-15(9).2','The organization being inspected/assessed documents and implements a process to approve the use of live data in test environments for the information system, system component, or information system service. The organization must maintain a record of approvals.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of approvals to ensure the organization being inspected/assessed approves the use of live data in test environments for the information system, system component, or information system service.'),
('003285','draft','2013-10-03','DISA FSO','policy','The organization documents the use of live data in development environments for the information system, system component, or information system service.','SA-15(9).3','The organization being inspected/assessed documents the use of live data in development environments for the information system, system component, or information system service.','The organization conducting the inspection/assessment obtains and examines the documented use of live data in test environments to ensure the organization being inspected/assessed documents the use of live data in development environments for the information system, system component, or information system service.'),
('003286','draft','2013-10-03','DISA FSO','policy','The organization documents the use of live data in test environments for the information system, system component, or information system service.','SA-15(9).4','The organization being inspected/assessed documents the use of live data in test environments for the information system, system component, or information system service.','The organization conducting the inspection/assessment obtains and examines the documented use of live data in test environments to ensure the organization being inspected/assessed documents the use of live data in test environments for the information system, system component, or information system service.'),
('003287','draft','2013-10-03','DISA FSO','policy','The organization controls the use of live data in development environments for the information system, system component, or information system service.','SA-15(9).5','The organization being inspected/assessed documents and implements a process to control the use of live data in development environments for the information system, system component, or information system service. The Enclave Test and Development STIG identifies requirements for test and development environments.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed controls the use of live data in development environments for the information system, system component, or information system service.'),
('003288','draft','2013-10-03','DISA FSO','policy','The organization controls the use of live data in test environments for the information system, system component, or information system service.','SA-15(9).6','The organization being inspected/assessed documents and implements a process to control the use of live data in test environments for the information system, system component, or information system service. The Enclave Test and Development STIG identifies requirements for test and development environments.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed controls the use of live data in test environments for the information system, system component, or information system service.'),
('003289','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide an incident response plan.','SA-15(10).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service provide an incident response plan.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service provide an incident response plan.'),
('003290','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security review.','SA-15(11).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service be released or delivered together with the corresponding evidence supporting the final security review.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service be released or delivered together with the corresponding evidence supporting the final security review.'),
('003291','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide organization-defined training on the correct use and operation of the implemented security functions, controls, and/or mechanisms.','SA-16.1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service provide training defined in SA-16, CCI 3292 on the correct use and operation of the implemented security functions, controls, and/or mechanisms.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service provide training defined in SA-16, CCI 3292 on the correct use and operation of the implemented security functions, controls, and/or mechanisms.'),
('003292','draft','2013-10-03','DISA FSO','policy','The organization defines the training the developer of the information system, system component, or information system service is required to provide on the correct use and operation of the implemented security functions, controls, and/or mechanisms.','SA-16.2','The organization being inspected/assessed defines and documents the training the developer of the information system, system component, or information system service is required to provide on the correct use and operation of the implemented security functions, controls, and/or mechanisms. DoD has determined the training is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented training to ensure the organization being inspected/assessed defines the training the developer of the information system, system component, or information system service is required to provide on the correct use and operation of the implemented security functions, controls, and/or mechanisms. DoD has determined the training is not appropriate to define at the Enterprise level.'),
('003293','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce a design specification and security architecture.','SA-17.1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce a design specification and security architecture.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce a design specification and security architecture.'),
('003294','draft','2013-10-03','DISA FSO','policy','The design specification and security architecture is consistent with and supportive of the organization^s security architecture which is established within and is an integrated part of the organization^s enterprise architecture.','SA-17.2','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer produce a design specification and security architecture that is consistent with and supportive of the organization\'s security architecture which is established within and is interrogated part of the organization\'s enterprise architecture.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer produce a design specification and security architecture that is consistent with and supportive of the organization\'s security architecture which is established within and is interrogated part of the organization\'s enterprise architecture.'),
('003295','draft','2013-10-03','DISA FSO','policy','The design specification and security architecture accurately and completely describes the required security functionality.','SA-17.3','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer produce a design specification and security architecture that accurately and completely describes the required security functionality.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer produce a design specification and security architecture that accurately and completely describes the required security functionality.'),
('003296','draft','2013-10-03','DISA FSO','policy','The design specification and security architecture accurately and completely describes the allocation of security controls among physical and logical components.','SA-17.4','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer produce a design specification and security architecture that accurately and completely describes the allocation of security controls among physical and logical components.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer produce a design specification and security architecture that accurately and completely describes the allocation of security controls among physical and logical components.'),
('003297','draft','2013-10-03','DISA FSO','policy','The design specification and security architecture expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection.','SA-17.5','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer produce a design specification and security architecture that expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer produce a design specification and security architecture that expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection.'),
('003298','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system to produce, as an integral part of the development process, a formal policy model describing the organization-defined elements of organizational security policy to be enforced.','SA-17(1).1','The organization being inspected/assessed documents within contracts/agreements,, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal policy model describing the elements of organizational security policy defined in SA-17 (1), CCI 3299 to be enforced.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal policy model describing the elements of organizational security policy defined in SA-17 (1), CCI 3299 to be enforced.'),
('003299','draft','2013-10-03','DISA FSO','policy','The organization defines the elements of organization security policy to be described in the formal policy model for enforcement on the information system, system component, or information system service.','SA-17(1).2','The organization being inspected/assessed defines and documents the elements of organization security policy to be described in the formal policy model for enforcement on the information system, system component, or information system service. DoD has determined the elements are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented elements to ensure the organization being inspected/assessed defines the elements of organization security policy to be described in the formal policy model for enforcement on the information system, system component, or information system service. DoD has determined the elements are not appropriate to define at the Enterprise level.'),
('003300','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented.','SA-17(1).3','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements o ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented.'),
('003301','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to define security-relevant hardware.','SA-17(2).1','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service define security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service define security-relevant software.'),
('003302','deprecated','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to define security-relevant hardware.',NULL,NULL,NULL),
('003303','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to define security-relevant software.','SA-17(2).2','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service define security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service define security-relevant software.'),
('003304','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to define security-relevant firmware.','SA-17(2).3','The organization being inspected/assessed documents within contracts/agreements, the requirement that the developer of the information system, system component, or information system service define security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service define security-relevant firmware.'),
('003305','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide a rationale that the definition for security-relevant hardware is complete.','SA-17(2).4','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service provide a rationale that the definition for security-relevant hardware is complete.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service provide a rationale that the definition for security-relevant hardware is complete.'),
('003306','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide a rationale that the definition for security-relevant software is complete.','SA-17(2).5','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service provide a rationale that the definition for security-relevant software is complete.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service provide a rationale that the definition for security-relevant software is complete.'),
('003307','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to provide a rationale that the definition for security-relevant firmware is complete.','SA-17(2).6','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service provide a rationale that the definition for security-relevant firmware is complete.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service provide a rationale that the definition for security-relevant firmware is complete.'),
('003308','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.','SA-17(3).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.'),
('003309','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant software in terms of exceptions, error messages, and effects.','SA-17(3).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant software in terms of exceptions, error messages, and effects.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant software in terms of exceptions, error messages, and effects.'),
('003310','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','SA-17(3).3','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.'),
('003311','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model.','SA-17(3).4','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model.'),
('003312','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware.','SA-17(3).5','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware.'),
('003313','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant software.','SA-17(3).6','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant software.'),
('003314','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant firmware.','SA-17(3).7','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant firmware.'),
('003315','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show that the formal top-level specification is an accurate description of the implemented security-relevant hardware.','SA-17(3).8','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show that the formal top-level specification is an accurate description of the implemented security-relevant hardware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show that the formal top-level specification is an accurate description of the implemented security-relevant hardware.'),
('003316','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show that the formal top-level specification is an accurate description of the implemented security-relevant software.','SA-17(3).9','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show that the formal top-level specification is an accurate description of the implemented security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show that the formal top-level specification is an accurate description of the implemented security-relevant software.'),
('003317','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show that the formal top-level specification is an accurate description of the implemented security-relevant firmware.','SA-17(3).10','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show that the formal top-level specification is an accurate description of the implemented security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show that the formal top-level specification is an accurate description of the implemented security-relevant firmware.'),
('003318','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to describe the security-relevant hardware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware.','SA-17(3).11','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service describe the security-relevant firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service describe the security-relevant firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware.'),
('003319','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to describe the security-relevant software mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant software.','SA-17(3).12','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service describe the security-relevant software mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service describe the security-relevant software mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant software.'),
('003320','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to describe the security-relevant firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant firmware.','SA-17(3).13','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service describe the security-relevant firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service describe the security-relevant firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant firmware.'),
('003321','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.','SA-17(4).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.'),
('003322','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant software in terms of exceptions, error messages, and effects.','SA-17(4).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.'),
('003323','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','SA-17(4).3','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.'),
('003324','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration or convincing argument with formal methods as feasible that the descriptive top-level specification is consistent with the formal policy model.','SA-17(4).4','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration or convincing argument with formal methods as feasible that the descriptive top-level specification is consistent with the formal policy model.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration or convincing argument with formal methods as feasible that the descriptive top-level specification is consistent with the formal policy model.'),
('003325','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware.','SA-17(4).5','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware.'),
('003326','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant software.','SA-17(4).6','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant software.'),
('003327','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant firmware.','SA-17(4).7','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant firmware.'),
('003328','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware.','SA-17(4).8','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware.'),
('003329','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant software.','SA-17(4).9','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant software.'),
('003330','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant firmware.','SA-17(4).10','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant firmware.'),
('003331','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to describe the security-relevant hardware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware.','SA-17(4).11','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service describe the security-relevant hardware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service describe the security-relevant hardware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware.'),
('003332','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to describe the security-relevant software mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant software.','SA-17(4).12','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service describe the security-relevant software mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant software.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service describe the security-relevant software mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant software.'),
('003333','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to describe the security-relevant firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant firmware.','SA-17(4).13','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service describe the security-relevant firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant firmware.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service describe the security-relevant firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant firmware.'),
('003334','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to design and structure the security-relevant hardware to use a complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(5).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service design and structure the security-relevant hardware to use a complete, conceptually simple protection mechanism with precisely defined semantics.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service design and structure the security-relevant hardware to use a complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003335','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to design and structure the security-relevant software to use a complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(5).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service design and structure the security-relevant software to use a complete, conceptually simple protection mechanism with precisely defined semantics.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service design and structure the security-relevant software to use a complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003336','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to design and structure the security-relevant firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(5).3','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service design and structure the security-relevant firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service design and structure the security-relevant firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003337','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to internally structure the security-relevant hardware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(5).4','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service internally structure the security-relevant hardware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service internally structure the security-relevant hardware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003338','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to internally structure the security-relevant software with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(5).5','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service internally structure the security-relevant software with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service internally structure the security-relevant software with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003339','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service to internally structure the security-relevant firmware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(5).6','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service internally structure the security-relevant firmware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service internally structure the security-relevant firmware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003340','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, component, or information system service to structure security-relevant hardware to facilitate testing.','SA-17(6).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service structure security-relevant hardware to facilitate testing.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service structure security-relevant hardware to facilitate testing.'),
('003341','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, component, or information system service to structure security-relevant software to facilitate testing.','SA-17(6).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service structure security-relevant software to facilitate testing.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service structure security-relevant software to facilitate testing.'),
('003342','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, component, or information system service to structure security-relevant firmware to facilitate testing.','SA-17(6).3','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service structure security-relevant firmware to facilitate testing.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service structure security-relevant firmware to facilitate testing.'),
('003343','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, component, or information system service to structure security-relevant hardware to facilitate controlling access with least privilege.','SA-17(7).1','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service structure security-relevant hardware to facilitate controlling access with least privilege.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service structure security-relevant hardware to facilitate controlling access with least privilege.'),
('003344','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, component, or information system service to structure security-relevant software to facilitate controlling access with least privilege.','SA-17(7).2','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service structure security-relevant software to facilitate controlling access with least privilege.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service structure security-relevant software to facilitate controlling access with least privilege.'),
('003345','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, component, or information system service to structure security-relevant firmware to facilitate controlling access with least privilege.','SA-17(7).3','The organization being inspected/assessed documents within the contracts/agreements, the requirement that the developer of the information system, system component, or information system service structure security-relevant firmware to facilitate controlling access with least privilege.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of the information system, system component, or information system service structure security-relevant firmware to facilitate controlling access with least privilege.'),
('003346','draft','2013-10-03','DISA FSO','policy','The organization implements a tamper protection program for the information system, system component, or information system service.','SA-18.1','The organization being inspected/assessed documents and implements a tamper protection program for the information system, system component, or information system service.','The organization conducting the inspection/assessment obtains and examines the documented tamper protection program to ensure the organization being inspected/assessed implements a tamper protection program for the information system, system component, or information system service.'),
('003347','draft','2013-10-03','DISA FSO','policy','The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including design.','SA-18(1).1','The organization being inspected/assessed documents and implements a process to employ anti-tamper technologies and techniques during multiple phases in the system development life cycle including design.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including design.'),
('003348','draft','2013-10-03','DISA FSO','policy','The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including development.','SA-18(1).2','The organization being inspected/assessed documents and implements a process to employ anti-tamper technologies and techniques during multiple phases in the system development life cycle including development.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including development.'),
('003349','draft','2013-10-03','DISA FSO','policy','The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including integration.','SA-18(1).3','The organization being inspected/assessed documents and implements a process to employ anti-tamper technologies and techniques during multiple phases in the system development life cycle including integration.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including integration.'),
('003350','draft','2013-10-03','DISA FSO','policy','The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including operations.','SA-18(1).4','The organization being inspected/assessed documents and implements a process to employ anti-tamper technologies and techniques during multiple phases in the system development life cycle including operations.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including operations.'),
('003351','draft','2013-10-03','DISA FSO','policy','The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including maintenance.','SA-18(1).5','The organization being inspected/assessed documents and implements a process to employ anti-tamper technologies and techniques during multiple phases in the system development life cycle including maintenance.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including maintenance.'),
('003352','draft','2013-10-03','DISA FSO','policy','The organization inspects organization-defined information systems, system components, or devices at random, at an organization-defined frequency, and/or upon organization-defined indications of need for inspection to detect tampering.','SA-18(2).1','The organization being inspected/assessed documents and implements a process to inspect information systems, system components, or devices defined in SA-18 (2), CCI 3353 at random, at a frequency defined in SA-18 (2), CCI 3354, and/or upon indications of need for inspection defined in SA-18 (2), CCI 3355 to detect tampering. The organization must maintain a record of inspections.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of inspections to ensure the organization being inspected/assessed inspects information systems, system components, or devices defined in SA-18 (2), CCI 3353 at random, at a frequency defined in SA-18 (2), CCI 3354, and/or upon indications of need for inspection defined in SA-18 (2), CCI 3355 to detect tampering.'),
('003353','draft','2013-10-03','DISA FSO','policy','The organization defines the information systems, system components, or devices to inspect at random, at an organization-defined frequency, and/or upon organization-defined indications of need for inspection to detect tampering.','SA-18(2).2','The organization being inspected/assessed defines and documents the information systems, system components, or devices to inspect at random, at organization-defined frequency, and/or upon organization-defined indications of need for inspection to detect tampering. DoD has determined the information systems, system components, or devices are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information systems, system components, or devices to ensure the organization being inspected/assessed defines the information systems, system components, or devices to inspect at random, at organization-defined frequency, and/or upon organization-defined indications of need for inspection to detect tampering. DoD has determined the information systems, system components, or devices are not appropriate to define at the Enterprise level.'),
('003354','draft','2013-10-03','DISA FSO','policy','The organization defines the frequency on which to inspect organization-defined information systems, system components, or devices to detect tampering.','SA-18(2).3','The organization being inspected/assessed defines and documents the frequency to inspect organization-defined information systems, system, components, or devices to detect tampering. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency to inspect organization-defined information systems, system, components, or devices to detect tampering. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('003355','draft','2013-10-03','DISA FSO','policy','The organization defines indications of need for inspection to detect tampering during inspections of organization-defined information systems, system components, or devices.','SA-18(2).4','The organization being inspected/assessed defines and documents indications of need for inspection to detect tampering during inspections of organization-defined information systems, system components, or devices. DoD has determined the indications are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented indications to ensure the organization being inspected/assessed defines indications of need for inspection to detect tampering during inspections of organization-defined information systems, system components, or devices. DoD has determined the indications are not appropriate to define at the Enterprise level.'),
('003356','draft','2013-10-03','DISA FSO','policy','The organization develops an anti-counterfeit policy that includes the means to detect counterfeit components from entering the information system.','SA-19.1','The organization being inspected/assessed develops and documents an anti-counterfeit policy that include the means to detect counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the documented anti-counterfeit policy to ensure the organization being inspected/assessed develops an anti-counterfeit policy that include the means to detect counterfeit components from entering the information system.'),
('003357','draft','2013-10-03','DISA FSO','policy','The organization develops an anti-counterfeit policy that includes the means to prevent counterfeit components from entering the information system.','SA-19.2','The organization being inspected/assessed develops and documents an anti-counterfeit policy that include the means to prevent counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the documented anti-counterfeit policy to ensure the organization being inspected/assessed develops an anti-counterfeit policy that include the means to prevent counterfeit components from entering the information system.'),
('003358','draft','2013-10-03','DISA FSO','policy','The organization develops anti-counterfeit procedures that include the means to detect counterfeit components from entering the information system.','SA-19.3','The organization being inspected/assessed develops and documents anti-counterfeit procedures that include the means to detect counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the documented anti-counterfeit procedures to ensure the organization being inspected/assessed develops anti-counterfeit procedures that include the means to detect counterfeit components from entering the information system.'),
('003359','draft','2013-10-03','DISA FSO','policy','The organization develops anti-counterfeit procedures that include the means to prevent counterfeit components from entering the information system.','SA-19.4','The organization being inspected/assessed develops and documents anti-counterfeit procedures that include the means to prevent counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the documented anti-counterfeit procedures to ensure the organization being inspected/assessed develops anti-counterfeit procedures that include the means to prevent counterfeit components from entering the information system.'),
('003360','draft','2013-10-03','DISA FSO','policy','The organization implements an anti-counterfeit policy that includes the means to detect counterfeit components from entering the information system.','SA-19.5','The organization being inspected/assessed implements the policy defined in SA-19, CCIs 3356 that include the means to detect counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the policy defined in SA-19, CCIs 3356 and any artifacts applicable to counterfeit components to ensure the organization being inspected/assessed implements the policy defined in SA-19, CCIs 3356 that include the means to detect counterfeit components from entering the information system.'),
('003361','draft','2013-10-03','DISA FSO','policy','The organization implements an anti-counterfeit policy that includes the means to prevent counterfeit components from entering the information system.','SA-19.6','The organization being inspected/assessed implements the policy defined in SA-19, CCIs 3357 that include the means to prevent counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the policy defined in SA-19, CCIs 3357 and any artifacts applicable to counterfeit components to ensure the organization being inspected/assessed implements the policy defined in SA-19, CCIs 3357 that include the means to detect counterfeit components from entering the information system.'),
('003362','draft','2013-10-03','DISA FSO','policy','The organization implements anti-counterfeit procedures that include the means to detect counterfeit components from entering the information system.','SA-19.7','The organization being inspected/assessed implements the procedures defined in SA-19, CCIs 3358 that include the means to detect counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the procedures defined in SA-19, CCIs 3358 and any artifacts applicable to counterfeit components to ensure the organization being inspected/assessed implements the procedures defined in SA-19, CCIs 3358 that include the means to detect counterfeit components from entering the information system.'),
('003363','draft','2013-10-03','DISA FSO','policy','The organization implements anti-counterfeit procedures that include the means to prevent counterfeit components from entering the information system.','SA-19.8','The organization being inspected/assessed implements the procedures defined in SA-19, CCIs 3359 that include the means to prevent counterfeit components from entering the information system.','The organization conducting the inspection/assessment obtains and examines the procedures defined in SA-19, CCIs 3359 and any artifacts applicable to counterfeit components to ensure the organization being inspected/assessed implements the procedures defined in SA-19, CCIs 3359 that include the means to prevent counterfeit components from entering the information system.'),
('003364','draft','2013-10-03','DISA FSO','policy','The organization reports counterfeit information system components to the source of the counterfeit component, organization-defined external reporting organizations, and/or organization-defined personnel or roles.','SA-19.9','The organization being inspected/assessed documents and implements a process to report counterfeit information system components to source of counterfeit component, at a minimum, USCYBERCOM. And/or at a minimum, the ISSO, ISSM, and PM. The organization must maintain a record of reporting. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and PM. DoD has defined the external reporting organizations as at a minimum, USCYBERCOM.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of reporting to ensure the organization being inspected/assessed reports counterfeit information system components to source of counterfeit component, at a minimum, USCYBERCOM. And/or at a minimum, the ISSO, ISSM, and PM.'),
('003365','draft','2013-10-03','DISA FSO','policy','The organization defines the external reporting organizations to which counterfeit information system components are to be reported.','SA-19.10','DoD has defined the external reporting organizations as at a minimum, USCYBERCOM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the external reporting organizations as at a minimum, USCYBERCOM'),
('003366','draft','2013-10-03','DISA FSO','policy','The organization defines the personnel or roles to whom counterfeit information system components are to be reported.','SA-19.11','DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and PM.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the personnel or roles as at a minimum, the ISSO, ISSM, and PM.'),
('003367','draft','2013-10-03','DISA FSO','policy','The organization trains organization-defined personnel or roles to detect counterfeit information system components (including hardware, software, and firmware).','SA-19(1).1','The organization being inspected/assessed documents and implements a process to train personnel or roles defined in SA-19 (1), CCI 3368 to detect counterfeit information system components (including hardware, software, and firmware). The organization must maintain a record of training.','The organization conducting the inspection/assessment obtains and examines the documented process, the list of personnel responsible for detecting counterfeit information system components, as well as the record of training to ensure the organization being inspected/assessed trains personnel or roles defined in SA-19 (1), CCI 3368 to detect counterfeit information system components (including hardware, software, and firmware).'),
('003368','draft','2013-10-03','DISA FSO','policy','The organization defines the personnel or roles to be trained to detect counterfeit information system components (including hardware, software, and firmware).','SA-19(1).2','The organization being inspected/assessed defines and documents the personnel or roles to be trained to detect counterfeit information system components (including hardware, software, and firmware). DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented personnel or roles to ensure the organization being inspected/assessed defines the personnel or roles to be trained to detect counterfeit information system components (including hardware, software, and firmware). DoD has determined the personnel or roles are not appropriate to define at the Enterprise level.'),
('003369','draft','2013-10-03','DISA FSO','policy','The organization maintains configuration control over organization-defined information system components awaiting service/repair.','SA-19(2).1','The organization being inspected/assessed documents and implements a process to maintain configuration control over information system components defined in SA-19 (2), CCI 3370 awaiting service/repair.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed maintains configuration control l over information system components defined in SA-19 (2), CCI 3370 awaiting service/repair.'),
('003370','draft','2013-10-03','DISA FSO','policy','The organization defines the information system components awaiting service/repair over which configuration control must be maintained.','SA-19(2).2','The organization being inspected/assessed defines and documents the information system components awaiting service/repair in which configuration control must be maintained. DoD has determined the information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system components to ensure the organization being inspected/assessed defines the information system components awaiting service/repair in which configuration control must be maintained. DoD has determined the information system components are not appropriate to define at the Enterprise level.'),
('003371','draft','2013-10-03','DISA FSO','policy','The organization maintains configuration control over serviced/repaired components awaiting return to service.','SA-19(2).3','The organization being inspected/assessed documents and implements a process to maintain configuration control over serviced/repaired components awaiting return to service.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed maintains configuration control over serviced/repaired components awaiting return to service.'),
('003372','draft','2013-10-03','DISA FSO','policy','The organization defines the support from external providers to be provided for unsupported information system components.','SA-22(1).1','The organization being inspected/assessed defines and documents the support from external providers to be provided for unsupported information system components. DoD has determined the support from external providers is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented support to ensure the organization being inspected/assessed defines the support from external providers to be provided for unsupported information system components. DoD has determined the support from external providers is not appropriate to define at the Enterprise level.'),
('003373','draft','2013-10-03','DISA FSO','policy','The organization provides in-house support and/or organization-defined support from external providers for unsupported information system components.','SA-22(1).2','The organization being inspected/assessed documents and implements a process to provide in-house support and/or support from external providers defined in SA-22 (1), CCI 3372 for unsupported information system components.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides in-house support and/or support from external providers defined in SA-22 (1), CCI 3372 for unsupported information system components.'),
('003374','draft','2013-10-03','DISA FSO','policy','The organization documents approval for the continued use of unsupported system components required to satisfy mission/business needs.','SA-22.2','The organization being inspected/assessed documents approval for the continued use of unsupported system components required to satisfy mission/business needs.','The organization conducting the inspection/assessment obtains and examines the hardware and software lists as well as the documented approvals to ensure the organization being inspected/assessed documents approval for the continued use of unsupported system components required to satisfy mission/business needs.'),
('003375','draft','2013-10-03','DISA FSO','policy','The organization provides justification for the continued use of unsupported system components required to satisfy mission/business needs.','SA-22.3','The organization being inspected/assessed documents justification for the continued use of unsupported system components required to satisfy mission/business needs.','The organization conducting the inspection/assessment obtains and examines the documented justification as well as the hardware and software lists to ensure the organization being inspected/assessed provides justification for the continued use of unsupported system components required to satisfy mission/business needs.'),
('003376','draft','2013-10-03','DISA FSO','policy','The organization replaces information system components when support for the components is no longer available from the developer, vendor, or manufacturer.','SA-22.1','The organization being inspected/assessed documents and implements a process to replace information system components when support for the components is no longer available from the developer, vendor, or manufacturer.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the hardware and software lists to ensure the organization being inspected/assessed replaces information system components when support for the components is no longer available from the developer, vendor, or manufacturer.'),
('003377','draft','2013-10-03','DISA FSO','policy','The organization defines the actions the developer of the information system, system component, or information system service must take to ensure the required screening criteria are satisfied.','SA-21(1).1','The organization being inspected/assessed defines and documents the actions the developer of the information system, system component, or information system service must take to ensure the required screening criteria are satisfied. DoD has determined the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented actions to ensure the organization being inspected/assessed defines the actions the developer of the information system, system component, or information system service must take to ensure the required screening criteria are satisfied. DoD has determined the actions are not appropriate to define at the Enterprise level.'),
('003378','draft','2013-10-03','DISA FSO','policy','The organization defines the actions the developer of the information system, system component, or information system service must take to ensure the required access authorizations are satisfied.','SA-21(1).2','The organization being inspected/assessed defines and documents the actions the developer of the information system, system component, or information system service must take to ensure the required access authorizations are satisfied. DoD has determined the actions are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented actions to ensure the organization being inspected/assessed defines the actions the developer of the information system, system component, or information system service must take to ensure the required access authorizations are satisfied. DoD has determined the actions are not appropriate to define at the Enterprise level.'),
('003379','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service take organization-defined actions to ensure the required screening criteria are satisfied.','SA-21(1).3','The organization being inspected/assessed documents within the contracts/agreements the requirement that the developer of information system, system component, or information system service take actions defined in SA-21 (1), CCI 3377 to ensure the required screening criteria are satisfied.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of information system, system component, or information system service take actions defined in SA-21 (1), CCI 3377 to ensure the required screening criteria are satisfied.'),
('003380','draft','2013-10-03','DISA FSO','policy','The organization requires the developer of the information system, system component, or information system service take organization-defined actions to ensure the required access authorizations are satisfied.','SA-21(1).4','The organization being inspected/assessed documents within the contracts/agreements the requirement that the developer of information system, system component, or information system service take actions defined in SA-21 (1), CCI 3378 to ensure the required access authorizations are satisfied.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of information system, system component, or information system service take actions defined in SA-21 (1), CCI 3378 to ensure the required access authorizations are satisfied.'),
('003381','draft','2013-10-03','DISA FSO','policy','The organization defines additional personnel screening criteria that must be satisfied by the developer of an organization-defined information system, system component, or information system service.','SA-21.4','The organization being inspected/assessed defines and documents additional personnel screening criteria that must be satisfied by the developer of organization-defined information system, system component, or information system service.\n\nDoD has determined the additional personnel screening criteria is not appropriate to define at the Enterprise level.\n\nThe organization should ensure that the developer is trustworthy by performing a review of the developer that may include:\n1. Organization and process certifications;\n2. Security policies, procedures, and activities across the lifecycle;\n3. Supply chain and how suppliers select/manage their suppliers/service providers;\n4. Financials to determine if the supplier is financially stable;\n5. Foreign Ownership, Control, and Influence;\n6. Past performance and vulnerabilities;\n7. Business relationships;\n8. Maturity of business processes; and\n9. Developer screening practices that may include::\na. Evaluating and vetting key personnel through security reviews (including clearance, satisfactory background checks, citizenship, and nationality) by acquirers or suppliers in any capacity (full-time employee, part-time employee, consultant, contractor, subcontractor, vendor, agent, etc.);\nb. Reevaluating personnel through security reviews and assessments on a periodic basis or upon occurrence of specific significant events.','The organization conducting the inspection/assessment obtains and examines the documented additional personnel screening criteria to ensure the organization being inspected/assessed defines additional personnel screening criteria that must be satisfied by the developer of organization-defined information system, system component, or information system service. DoD has determined the additional personnel screening criteria is not appropriate to define at the Enterprise level.'),
('003382','draft','2013-10-03','DISA FSO','policy','The organization requires that the developer of an organization-defined information system, system component, or information system service satisfy organization-defined additional personnel screening criteria.','SA-21.5','The organization being inspected/assessed requires within contracts that the developer of information system, system component, or information system service defined in SA-21, CCI 3384 satisfy additional personnel screening criteria defined in SA-21, CCI 3381.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of information system, system component, or information system service defined in SA-21, CCI 3384 satisfy additional personnel screening criteria defined in SA-21, CCI 3381.'),
('003383','draft','2013-10-03','DISA FSO','policy','The organization defines the official government duties to be assigned to the developer of an organization-defined information system, system component, or information system service.','SA-21.2','The organization being inspected/assessed defines and documents the official government duties to be assigned to the developer of organization-defined information system, system component, or information system service. DoD has determined the official government duties are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented official government duties to ensure the organization being inspected/assessed defines the official government duties to be assigned to the developer of organization-defined information system, system component, or information system service. DoD has determined the official government duties are not appropriate to define at the Enterprise level.'),
('003384','draft','2013-10-03','DISA FSO','policy','The organization defines the information system, system component, or information system service which requires the information system developer to have appropriate access authorizations and satisfy additional personnel screening criteria.','SA-21.1','The organization being inspected/assessed defines and documents the information system, system component, or information system service which require the information system developer to have appropriate access authorizations and satisfy additional personnel screening criteria. DoD has determined the information system, system component, or information system service is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information system, system component, or information system service to ensure the organization being inspected/assessed defines the information system, system component, or information system service which require the information system developer to have appropriate access authorizations and satisfy additional personnel screening criteria. DoD has determined the information system, system component, or information system service is not appropriate to define at the Enterprise level.'),
('003385','draft','2013-10-03','DISA FSO','policy','The organization requires that the developer of an organization-defined information system, system component, or information system service have appropriate access authorizations as determined by assigned organization-defined official government duties.','SA-21.3','The organization being inspected/assessed requires within contracts that the developer of information system, system component, or information system service defined in SA-21, CCI 3384 have appropriate access authorizations as determined by assigned official government duties defined in SA-21, CCI 3383.','The organization conducting the inspection/assessment obtains and examines the contracts/agreements to ensure the organization being inspected/assessed requires that the developer of information system, system component, or information system service defined in SA-21, CCI 3384 have appropriate access authorizations as determined by assigned official government duties defined in SA-21, CCI 3383.'),
('003386','draft','2013-10-03','DISA FSO','policy','The organization defines the critical information system components to re-implement or custom develop.','SA-20.1','The organization being inspected/assessed defines and documents the critical information system components to re-implement or custom develop. DoD has determined the critical information system components are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented critical information system components to ensure the organization being inspected/assessed defines the critical information system components to re-implement or custom develop. DoD has determined the critical information system components are not appropriate to define at the Enterprise level.'),
('003387','draft','2013-10-03','DISA FSO','policy','The organization re-implements or custom develops organization-defined critical information system components.','SA-20.2','The organization being inspected/assessed re-implements or custom develops critical information system components defined in SA-20, CCI 3386.','The organization conducting the inspection/assessment obtains and examines hardware and software lists to ensure that no commercial off-the-shelf components are used as critical information system components defined in SA-20, CCI 3386.'),
('003388','draft','2013-10-03','DISA FSO','policy','The organization defines the frequency on which to scan for counterfeit information system components.','SA-19(4).1','The organization being inspected/assessed defines and documents the frequency to scan for counterfeit information system components. DoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines the frequency to scan for counterfeit information system components. DoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('003389','draft','2013-10-03','DISA FSO','policy','The organization scans for counterfeit information system components in accordance with organization-defined frequency.','SA-19(4).2','The organization being inspected/assessed documents and implements a process to scan for counterfeit information system components in accordance with the frequency defined in SA-19 (4), CCI 3388. The organization must maintain a record of scans.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of scans to ensure the organization being inspected/assessed scans for counterfeit information system components in accordance with the frequency defined in SA-19 (4), CCI 3388.'),
('003390','draft','2013-10-03','DISA FSO','policy','The organization defines the techniques and methods used to dispose of information system components.','SA-19(3).1','DoD has defined the techniques and methods as defined IAW DoD Manual 5200.01.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level. DoD has defined the techniques and methods as defined IAW DoD Manual 5200.01.'),
('003391','draft','2013-10-03','DISA FSO','policy','The organization disposes of information system components using organization-defined techniques and methods.','SA-19(3).2','The organization being inspected/assessed documents and implements a process to dispose of information system components using techniques and methods defined IAW DoD Manual 5200.01. The organization must maintain a record of disposal. DoD has defined the techniques and methods as defined IAW DoD Manual 5200.01.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the record of disposal to ensure the organization being inspected/assessed disposes of information system components using techniques and methods defined IAW DoD Manual 5200.01. DoD has defined the techniques and methods as defined IAW DoD Manual 5200.01.'),
('003392','draft','2013-11-07','DISA FSO','policy','The organization determines and documents the legal authority that permits the collection of personally identifiable information (PII), either generally or in support of a specific program or information system need.','AP-1.1','The organization being inspected/assessed identifies and documents in applicable privacy notices and privacy impact assessment, the legal authority applicable to the information system permitting the collection of PII IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, and DoDD 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documented the legal authority that permits the collection of PII, and that such collection is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation.'),
('003393','draft','2013-11-07','DISA FSO','policy','The organization determines and documents the legal authority that permits the use of personally identifiable information (PII), either generally or in support of a specific program or information system need.','AP-1.2','The organization being inspected/assessed identifies and documents in applicable privacy notices and privacy impact assessment, the legal authority applicable to the information system permitting the collection of PII IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, and DoDD 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documented the legal authority that permits the use of PII, and that such use is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation.'),
('003394','draft','2013-11-07','DISA FSO','policy','The organization determines and documents the legal authority that permits the maintenance of personally identifiable information (PII), either generally or in support of a specific program or information system need.','AP-1.3','The organization being inspected/assessed identifies and documents in applicable privacy notices and privacy impact assessment, the legal authority applicable to the information system permitting the collection of PII IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, and DoDD 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documented the legal authority that permits the maintenance of PII, and that such maintenance is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation.'),
('003395','draft','2013-11-07','DISA FSO','policy','The organization determines and documents the legal authority that permits the sharing of personally identifiable information (PII), either generally or in support of a specific program or information system need.','AP-1.4','The organization being inspected/assessed identifies and documents in applicable privacy notices and privacy impact assessment, the legal authority applicable to the information system permitting the collection of PII IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, and DoDD 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documented the legal authority that permits the dissemination or sharing of PII, and that such dissemination or sharing is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation.'),
('003396','draft','2013-11-07','DISA FSO','policy','The organization describes, in its privacy notices, the purpose(s) for which personally identifiable information (PII) is collected.','AP-2.1','The organization being inspected/assessed ensures the PII collected by the specific program or information system is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation, for example, but not limited to, the Privacy Act system of records notice (SORN) or Privacy Impact Assessment (PIA). The privacy documentation shall be IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, Section 208 of the E-Gov Act of 2002 (Public Law 107-347) and DoDI 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy notices and privacy impact assessment to ensure the organization being inspected/assessed describes, in its privacy notices, the purpose(s) for which PII is collected.'),
('003397','draft','2013-11-07','DISA FSO','policy','The organization appoints a Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO) accountable for developing, implementing, and maintaining an organization-wide governance and privacy program to ensure compliance with all applicable laws and regulations regarding the collection, use, maintenance, sharing, and disposal of personally identifiable information (PII) by programs and information systems.','AR-1.1','The Senior Agency Official for Privacy (SAOP) is appointed at the DoD enterprise level. The SAOP is accountable for developing, implementing and maintaining the DoD-enterprise level governance and privacy program, which can be augmented with a Component level guidance and privacy program.\n\n\nThe Component Senior Official for Privacy is accountable for developing, implementing and maintaining the Component level governance and privacy program.\n\nThe organization being inspected/assessed appoints and documents a Component Senior Official for privacy.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has document the appointment of component Senior Official for privacy.'),
('003398','draft','2013-11-07','DISA FSO','policy','The organization describes, in its privacy notices, the purpose(s) for which personally identifiable information (PII) is used.','AP-2.2','The organization being inspected/assessed ensures the PII collected by the specific program or information system is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation, for example, but not limited to, the Privacy Act system of records notice (SORN) or Privacy Impact Assessment (PIA). The privacy documentation shall be IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, Section 208 of the E-Gov Act of 2002 (Public Law 107-347) and DoDI 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy notices and privacy impact assessment to ensure the organization being inspected/assessed describes, in its privacy notices, the purpose(s) for which PII is used.'),
('003399','draft','2013-11-07','DISA FSO','policy','The organization describes, in its privacy notices, the purpose(s) for which personally identifiable information (PII) is maintained.','AP-2.3','The organization being inspected/assessed ensures the PII collected by the specific program or information system is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation, for example, but not limited to, the Privacy Act system of records notice (SORN) or Privacy Impact Assessment (PIA). The privacy documentation shall be IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, Section 208 of the E-Gov Act of 2002 (Public Law 107-347) and DoDI 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy notices and privacy impact assessment to ensure the organization being inspected/assessed describes, in its privacy notices, the purpose(s) for which PII is maintained.'),
('003400','draft','2013-11-07','DISA FSO','policy','The organization describes, in its privacy notices, the purpose(s) for which personally identifiable information (PII) is shared.','AP-2.4','The organization being inspected/assessed ensures the PII collected by the specific program or information system is related to, and compatible with, the purpose and scope of the authority described in the privacy documentation, for example, but not limited to, the Privacy Act system of records notice (SORN) or Privacy Impact Assessment (PIA). The privacy documentation shall be IAW 5 USC 552a, DoDD 5400.11, DoD 5400.11-R, Section 208 of the E-Gov Act of 2002 (Public Law 107-347) and DoDI 5400.16.','The organization conducting the inspection/assessment obtains and examines the applicable privacy notices and privacy impact assessment to ensure the organization being inspected/assessed describes, in its privacy notices, the purpose(s) for which PII is shared.'),
('003401','draft','2013-11-07','DISA FSO','policy','The organization monitors federal privacy laws and policy for changes that affect the privacy program.','AR-1.2','The organization being inspected/assessed documents and implements a repeatable business process by which it monitors federal privacy laws and policy for changes that affect the privacy program.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has a documented repeatable business process by which it monitors federal privacy laws and policy for changes that affect the privacy program.'),
('003402','draft','2013-11-07','DISA FSO','policy','The organization defines the allocation of budget resources sufficient to implement and operate the organization-wide privacy program.','AR-1.3','The organization being inspected/assessed defines and documents the allocation of budget resources sufficient to implement and operate the organization-wide privacy program.\n\nDoD has determined the allocation of budget resources is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented allocation to ensure the organization being inspected/assessed defines the allocation of budget resources sufficient to implement and operate the organization-wide privacy program.\n\nDoD has determined the allocation of budget resources is not appropriate to define at the Enterprise level.'),
('003403','draft','2013-11-07','DISA FSO','policy','The organization defines the allocation of staffing resources sufficient to implement and operate the organization-wide privacy program.','AR-1.4','The organization being inspected/assessed defines and documents the allocation of staffing resources sufficient to implement and operate the organization-wide privacy program.\n\nDoD has determined the allocation of staffing resources is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented allocation to ensure the organization being inspected/assessed defines the allocation of staffing resources sufficient to implement and operate the organization-wide privacy program.\n\nDoD has determined the allocation of staffing resources is not appropriate to define at the Enterprise level.'),
('003404','draft','2013-11-07','DISA FSO','policy','The organization allocates sufficient organization-defined budget resources to implement and operate the organization-wide privacy program.','AR-1.5','The organization being inspected/assessed documents and implements a process for the allocation of sufficient organization-defined budget resources to implement and operate the organization-wide privacy program.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documents which demonstrate allocation of sufficient organization-defined budget resources to implement and operate the organization-wide privacy program.'),
('003405','draft','2013-11-07','DISA FSO','policy','The organization allocates sufficient organization-defined staffing resources to implement and operate the organization-wide privacy program.','AR-1.6','The organization being inspected/assessed documents and implements a process for the allocation of sufficient organization-defined staffing resources to implement and operate the organization-wide privacy program.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documents which demonstrate allocation of sufficient organization-defined staffing resources to implement and operate the organization-wide privacy program.'),
('003406','draft','2013-11-07','DISA FSO','policy','The organization develops a strategic organizational privacy plan for implementing applicable privacy controls, policies, and procedures.','AR-1.7','The organization being inspected/assessed documents and implements a strategic organizational privacy plan for implementing applicable privacy controls, policies, and procedures.\n\nThe DoD has determined that this CCI is not applicable until the policy is issued.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documents which demonstrate a strategic organizational privacy plan for implementing applicable privacy controls, policies, and procedures.\n\nThe DoD has determined that this CCI is not applicable until the policy is issued.'),
('003407','draft','2013-11-07','DISA FSO','policy','The organization develops operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving personally identifiable information (PII).','AR-1.8','The organization being inspected/assessed documents and implements operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.','The organization conducting the inspection/assessment obtains and examines the applicable privacy documentation to ensure the organization being inspected/assessed has documents which demonstrate operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.'),
('003408','draft','2013-11-07','DISA FSO','policy','The organization disseminates operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving personally identifiable information (PII).','AR-1.9','The organization being inspected/assessed disseminates via an information sharing capability, operational privacy policies and procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.','The organization conducting the inspection/assessment obtains and examines the operational privacy policies and procedures via the organization\'s information sharing capability to ensure the organization being inspected/assessed disseminates operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII and procedures which implement these policies.'),
('003409','draft','2013-11-07','DISA FSO','policy','The organization implements operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving personally identifiable information (PII).','AR-1.10','The organization being inspected/assessed documents and implements operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.','The organization conducting the inspection/assessment obtains and examines the operational privacy policies to ensure the organization being inspected/assessed implements operational privacy policies which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.'),
('003410','draft','2013-11-07','DISA FSO','policy','The organization develops operational privacy procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving personally identifiable information (PII).','AR-1.11','The organization being inspected/assessed defines and documents operational privacy procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.','The organization conducting the inspection/assessment obtains and examines the documented operational privacy procedures to ensure the organization being inspected/assessed develops operational privacy procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.'),
('003411','draft','2013-11-07','DISA FSO','policy','The organization disseminates operational privacy procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving personally identifiable information (PII).','AR-1.12','The organization being inspected/assessed disseminates via an information sharing capability, the operational privacy procedures which implement the applicable privacy and security controls for programs, information systems, or technologies involving PII.','The organization conducting the inspection/assessment obtains and examines via the organization\'s information sharing capability the operational privacy procedures to ensure it has been disseminated.'),
('003412','draft','2013-11-07','DISA FSO','policy','The organization implements operational privacy procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving personally identifiable information (PII).','AR-1.13','The organization being inspected/assessed documents and implements operational privacy procedures which implement the applicable privacy and security controls for programs, information systems, or technologies involving PII.','The organization conducting the inspection/assessment obtains and examines the operational privacy procedures to ensure the organization being inspected/assessed implements operational privacy procedures which govern the appropriate privacy and security controls for programs, information systems, or technologies involving PII.'),
('003413','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency, minimally biennially, on which the privacy plan, policies, and procedures are to be updated.','AR-1.14','DoD has defined the frequency as at a minimum, biennially.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as at a minimum, biennially.'),
('003414','draft','2013-11-07','DISA FSO','policy','The organization updates the privacy plan per organization-defined frequency.','AR-1.15','The organization being inspected/assessed updates the privacy plan at a minimum, biennially.\n\nThe organization must maintain records of updates.\n\nDoD has defined the frequency as at a minimum, biennially.','The organization conducting the inspection/assessment obtains and examines records of updates to ensure the organization being inspected/assessed updates the privacy plan at a minimum, biennially.\n\nDoD has defined the frequency as at a minimum, biennially.'),
('003415','draft','2013-11-07','DISA FSO','policy','The organization updates the privacy policies per organization-defined frequency.','AR-1.16','The organization being inspected/assessed updates the privacy policies at a minimum, biennially.\n\nThe organization must maintain records of updates.\n\nDoD has defined the frequency as at a minimum, biennially.','The organization conducting the inspection/assessment obtains and examines records of updates to ensure the organization being inspected/assessed updates the privacy policies at a minimum, biennially.\n\nDoD has defined the frequency as at a minimum, biennially.'),
('003416','draft','2013-11-07','DISA FSO','policy','The organization updates the privacy procedures per organization-defined frequency.','AR-1.17','The organization being inspected/assessed updates privacy procedures at a minimum, biennially.\n\nThe organization must maintain records of updates.\n\nDoD has defined the frequency as at a minimum, biennially.','The organization conducting the inspection/assessment obtains and examines records of updates to ensure the organization being inspected/assessed updates privacy procedures at a minimum, biennially.\n\nDoD has defined the frequency as at a minimum, biennially.'),
('003417','draft','2013-11-07','DISA FSO','policy','The organization documents a privacy risk management process which assesses the privacy risk to individuals.','AR-2.1','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals.','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals.'),
('003418','draft','2013-11-07','DISA FSO','policy','The organization implements a privacy risk management process which assesses the privacy risk to individuals.','AR-2.2','The organization being inspected/assessed implements a privacy risk management process which assesses the privacy risk to individuals.','The organization conducting the inspection/assessment obtains and examines the documents which implement a privacy risk management process which assesses the privacy risk to individuals.'),
('003419','draft','2013-11-07','DISA FSO','policy','The organization^s privacy risk management process assesses the privacy risk to individuals resulting from the collection of personally identifiable information (PII).','AR-2.3','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals resulting from the collection of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals resulting from the collection of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)'),
('003420','draft','2013-11-07','DISA FSO','policy','The organization^s privacy risk management process assesses the privacy risk to individuals resulting from the sharing of personally identifiable information (PII).','AR-2.4','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals resulting from t sharing of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals resulting from the sharing of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)'),
('003421','draft','2013-11-07','DISA FSO','policy','The organization^s privacy risk management process assesses the privacy risk to individuals resulting from the storing of personally identifiable information (PII).','AR-2.5','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals resulting from the storing of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals resulting from the storing of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)'),
('003422','draft','2013-11-07','DISA FSO','policy','The organization^s privacy risk management process assesses the privacy risk to individuals resulting from the transmitting of personally identifiable information (PII).','AR-2.6','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals resulting from the transmitting of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals resulting from the transmitting of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)'),
('003423','draft','2013-11-07','DISA FSO','policy','The organization^s privacy risk management process assesses the privacy risk to individuals resulting from the use of personally identifiable information (PII).','AR-2.7','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals resulting from the use of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals resulting from the use of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)'),
('003424','draft','2013-11-07','DISA FSO','policy','The organization^s privacy risk management process assesses the privacy risk to individuals resulting from the disposal of personally identifiable information (PII).','AR-2.8','The organization being inspected/assessed documents a privacy risk management process which assesses the privacy risk to individuals resulting from the disposal of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)','The organization conducting the inspection/assessment obtains and examines the documented privacy risk management process which assesses the privacy risk to individuals resulting from the disposal of PII. (http://iatraining.disa.mil/eta/piiv2/launchPage.htm)'),
('003425','draft','2013-11-07','DISA FSO','policy','The organization conducts Privacy Impact Assessments (PIAs) for information systems, programs, or other activities that pose a privacy risk in accordance with applicable law, OMB policy, or any existing organizational policies and procedures.','AR-2.9','The organization being inspected/assessed documents and implements a process to conduct Privacy Impact Assessments (PIAs) for information systems, programs, or other activities that pose a privacy risk in accordance with applicable law, OMB policy, or any existing organizational policies and procedures.\n\nOnly applies to non national security systems.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed conducts Privacy Impact Assessments (PIAs) for information systems, programs, or other activities that pose a privacy risk in accordance with applicable law, OMB policy, or any existing organizational policies and procedures.'),
('003426','draft','2013-11-07','DISA FSO','policy','The organization establishes privacy roles for contractors.','AR-3.1','The organization being inspected/assessed establishes and documents privacy roles for contractors.','The organization conducting the inspection/assessment obtains and examines the documented privacy roles for contractors.'),
('003427','draft','2013-11-07','DISA FSO','policy','The organization establishes privacy responsibilities for contractors.','AR-3.2','The organization being inspected/assessed establishes and documents privacy responsibilities for contractors.','The organization conducting the inspection/assessment obtains and examines the documented privacy responsibilities for contractors.'),
('003428','draft','2013-11-07','DISA FSO','policy','The organization establishes access requirements for contractors.','AR-3.3','The organization being inspected/assessed establishes and documents access requirements for contractors.','The organization conducting the inspection/assessment obtains and examines the access requirements for contractors.'),
('003429','draft','2013-11-07','DISA FSO','policy','The organization establishes privacy roles for service providers.','AR-3.4','The organization being inspected/assessed establishes and documents privacy roles for service providers.','The organization conducting the inspection/assessment obtains and examines the privacy roles established for service providers.'),
('003430','draft','2013-11-07','DISA FSO','policy','The organization establishes privacy responsibilities for service providers.','AR-3.5','The organization being inspected/assessed establishes and documents privacy responsibilities for service providers.','The organization conducting the inspection/assessment obtains and examines the privacy responsibilities established for service providers.'),
('003431','draft','2013-11-07','DISA FSO','policy','The organization establishes access requirements for service providers.','AR-3.6','The organization being inspected/assessed establishes and documents access requirements for service providers.','The organization conducting the inspection/assessment obtains and examines the access requirements established for service providers.'),
('003432','draft','2013-11-07','DISA FSO','policy','The organization includes privacy requirements in contracts.','AR-3.7','The organization being inspected/assessed includes the privacy requirements from Federal Acquisition Regulation Subpart 24.1, 48 CFR Part 24 and Part 39.105, and DoDD 5400.11 in contracts.','The organization conducting the inspection/assessment obtains and examines a representative sample and business procedures which ensure all contracts include the privacy requirements from Federal Acquisition Regulation Subpart 24.1, 48 CFR Part 24 and Part 39.105, and DoDD 5400.11.'),
('003433','draft','2013-11-07','DISA FSO','policy','The organization includes privacy requirements in other acquisition-related documents.','AR-3.8','The organization being inspected/assessed includes the privacy requirements from Federal Acquisition Regulation Subpart 24.1, 48 CFR Part 24 and Part 39.105, and DoDD 5400.11 in other acquisition-related documents.','The organization conducting the inspection/assessment obtains and examines the business procedures and a representative sample of the documents to demonstrate all other acquisition-related documents applicable to the information system include the privacy requirements from Federal Acquisition Regulation Subpart 24.1, 48 CFR Part 24 and Part 39.105, and DoDD 5400.11.'),
('003434','deprecated','2013-11-07','DISA FSO','policy','The organization defines the frequency for monitoring privacy controls and internal privacy policy to ensure effective implementation.','AR-4.1','DoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.'),
('003435','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency for auditing privacy controls and internal privacy policy to ensure effective implementation.','AR-4.2','DoD has defined the frequency as every three years or as required by major system change.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as every three years or as required by major system change.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.'),
('003436','draft','2013-11-07','DISA FSO','policy','The organization monitors privacy controls, per organization-defined frequency, to ensure effective implementation.','AR-4.3','The organization being inspected/assessed documents and implements a process to monitor privacy controls to ensure effective implementation.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed monitors privacy controls to ensure effective implementation.'),
('003437','draft','2013-11-07','DISA FSO','policy','The organization monitors internal privacy policy to ensure effective implementation.','AR-4.4','The organization being inspected/assessed documents and implements a process to monitor internal privacy policy to ensure effective implementation.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed monitors internal privacy policy to ensure effective implementation.'),
('003438','draft','2013-11-07','DISA FSO','policy','The organization audits privacy controls, per organization-defined frequency, to ensure effective implementation.','AR-4.5','The organization being inspected/assessed documents and implements a process to audit privacy controls, every three years or as required by major system change, to ensure effective implementation.\n\nThe organization must maintain an audit trail.\n\nDoD has defined the frequency as every three years or as required by major system change.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail to ensure the organization being inspected/assessed audits privacy controls, every three years or as required by major system change, to ensure effective implementation.\n\nDoD has defined the frequency as every three years or as required by major system change.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.'),
('003439','draft','2013-11-07','DISA FSO','policy','The organization audits internal privacy policy, per organization-defined frequency, to ensure effective implementation.','AR-4.6','The organization being inspected/assessed documents and implements a process to audit privacy controls, every three years or as required by major system change, to ensure effective implementation.\n\nThe organization must maintain an audit trail.\n\nDoD has defined the frequency as every three years or as required by major system change.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail to ensure the organization being inspected/assessed audits privacy controls, every three years or as required by major system change, to ensure effective implementation.\n\nDoD has defined the frequency as every three years or as required by major system change.\n\nDoD has defined the frequency as upon a change in the privacy, security or authorization posture of the system and not to exceed every three years.'),
('003440','draft','2013-11-07','DISA FSO','policy','The organization develops a comprehensive training and awareness strategy aimed at ensuring that personnel understand privacy responsibilities and procedures.','AR-5.1','The organization being inspected/assessed documents whether the IASE PII Training provides personnel with the information necessary to understand their roles and responsibilities, or if additional organization-specific training is required. If organization-specific training is required, the organization being inspected/assessed defines and documents the unique privacy needs which must be addressed by training.','The organization conducting the inspection/assessment obtains and examines the documented evidence of a review as to whether the IASE provided PII training provides personnel with the information necessary to understand their roles and responsibilities. If the documented review indicates that organization-specific training is necessary, then the organization conducting the inspection/assessment obtains and examines documentation identifying the unique privacy needs which must be addressed by training to ensure they are identified.'),
('003441','draft','2013-11-07','DISA FSO','policy','The organization implements a comprehensive training and awareness strategy aimed at ensuring that personnel understand privacy responsibilities and procedures.','AR-5.2','If the organization being inspected/assessed identifies IAW AR-5, CCI 3440 that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization being inspected/assessed documents and implements a comprehensive training and awareness strategy aimed at ensuring that personnel understand privacy responsibilities and procedures.','The organization conducting the inspection/assessment obtains and examines the documented results of the review conducted IAW AR-5, CCI 3440. If the review indicates that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization conducting the inspection/assessment obtains and examines the documented training and awareness strategy to ensure that it implements training aimed at ensuring that personnel understand privacy responsibilities and procedures.'),
('003442','draft','2013-11-07','DISA FSO','policy','The organization updates a comprehensive training and awareness strategy aimed at ensuring that personnel understand privacy responsibilities and procedures.','AR-5.3','If the organization being inspected/assessed identifies IAW AR-5, CCI 3440 that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization being inspected/assessed documents and implements a process to update the comprehensive training and awareness strategy.','The organization conducting the inspection/assessment obtains and examines the documented results of the review conducted IAW AR-5, CCI 3440. If the review indicates that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization conducting the inspection/assessment obtains and examines the documented update process for the training and awareness strategy to ensure that the organization being inspected/assessed updates the strategy.'),
('003443','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency, minimally annually, for administering its basic privacy training.','AR-5.4','The organization being inspected/assessed documents whether the IASE PII Training provides personnel with the information necessary to understand their roles and responsibilities, or if additional organization-specific training is required. If organization-specific training is required, the organization being inspected/assessed defines and documents the unique privacy needs which must be addressed by training.','The organization conducting the inspection/assessment obtains and examines the documented evidence of a review as to whether the IASE provided PII training provides personnel with the information necessary to understand their roles and responsibilities. If the documented review indicates that organization-specific training is necessary, then the organization conducting the inspection/assessment obtains and examines documentation identifying the unique privacy needs which must be addressed by training to ensure they are identified.'),
('003444','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency, minimally annually, for administering the targeted, role-based privacy training for personnel having responsibility for personally identifiable information (PII) or for activities that involve PII.','AR-5.5','If the organization being inspected/assessed identifies IAW AR-5, CCI 3440 that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization being inspected/assessed documents and implements a comprehensive training and awareness strategy aimed at ensuring that personnel understand privacy responsibilities and procedures.','The organization conducting the inspection/assessment obtains and examines the documented results of the review conducted IAW AR-5, CCI 3440. If the review indicates that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization conducting the inspection/assessment obtains and examines the documented training and awareness strategy to ensure that it implements training aimed at ensuring that personnel understand privacy responsibilities and procedures.'),
('003445','draft','2013-11-07','DISA FSO','policy','The organization administers basic privacy training per the organization-defined frequency.','AR-5.6','If the organization being inspected/assessed identifies IAW AR-5, CCI 3440 that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization being inspected/assessed documents and implements a process to update the comprehensive training and awareness strategy.','The organization conducting the inspection/assessment obtains and examines the documented results of the review conducted IAW AR-5, CCI 3440. If the review indicates that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization conducting the inspection/assessment obtains and examines the documented update process for the training and awareness strategy to ensure that the organization being inspected/assessed updates the strategy.'),
('003446','draft','2013-11-07','DISA FSO','policy','The organization administers, per organization-defined frequency, targeted, role-based privacy training for personnel having responsibility for personally identifiable information (PII) or for activities that involve PII.','AR-5.7','The organization follows its strategy and plan for administering targeted, role-based privacy training.','The organization conducting the inspection/assessment reviews evidence of the organization being inspected providing annual targeted, role-based privacy training. DoD Components that have determined and documented adequate justification that DoD-wide privacy training and awareness activities provide evidence to demonstrate its personnel are taking this training annually.'),
('003447','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency, minimally annually, on which personnel certify acceptance of responsibilities for privacy requirements.','AR-5.8','DoD has defined the frequency as annually.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as annually.'),
('003448','draft','2013-11-07','DISA FSO','policy','The organization ensures personnel certify (manually or electronically) acceptance of responsibilities for privacy requirements per organization-defined frequency.','AR-5.9','The organization being inspected/assessed must ensure that personnel certify (manually or electronically) acceptance of responsibilities for privacy requirements at least annually. This can be achieved either through inclusion of these requirements within and annually recertifying their existing AUP, or via a separate acceptance method.','The organization conducting the inspection/assessment obtains and examines the documented results of the review conducted IAW AR-5, CCI 3440. If the review indicates that IASE provided PII training meets the needs of the organization then the organization is automatically compliant. Otherwise, the organization conducting the inspection/assessment obtains and examines the documented certification process as well as a representative sample of employee certification records to ensure that the organization being inspected/assessed ensures personnel certify (manually or electronically) acceptance of responsibilities for privacy requirements per organization-defined frequency.'),
('003449','draft','2013-11-07','DISA FSO','policy','The organization develops reports for the Office of Management and Budget (OMB), Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.','AR-6.1','The organization being inspected/assessed documents and implements a process to provide all input required by Defense Privacy and Civil Liberties Office (DPLCO), DA&M and/or the OCIO to support the reporting OMB, Congress and the other oversight bodies.','The organization conducting the inspection/assessment obtains and examines the documented process as well as reports generated to ensure the organization being inspected/assessed provides all input required by Defense Privacy and Civil Liberties Office (DPLCO), DA&M and/or the OCIO to support the reporting OMB, Congress and the other oversight bodies.'),
('003450','draft','2013-11-07','DISA FSO','policy','The organization disseminates reports to the Office of Management and Budget (OMB), Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.','AR-6.2','Only designated officials, such as the Senior Agency Official for Privacy (SAOP), respond to external reporting requirements on behalf of the DoD. The Defense Civil Liberties and Privacy Office (DPCLO) meets the requirement to disseminate reports to the Office of Management and Budget (OMB), Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.\n\nDoD Components are automatically compliant with this control because they are covered by the DPCLO and the action is performed by the DA&M and/or OCIO.','The DPCLO meets the requirement to disseminate reports to the Office of Management and Budget (OMB), Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.\n\nDoD Components are automatically compliant with this control because they are covered by the DPCLO and the action is performed by the DA&M and/or OCIO.'),
('003451','draft','2013-11-07','DISA FSO','policy','The organization updates reports for the Office of Management and Budget (OMB), Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.','AR-6.3','The organization being inspected/assessed provides the necessary inputs to external privacy reports as mandated by the DPCLO and OCIO to ensure the organization being inspected/assessed updates reports for the OMB, Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.','The organization conducting the inspection/assessment reviews evidence of contributions of updated inputs to external privacy reports as mandated by the DPCLO and OCIO to ensure the organization being inspected/assessed updates reports for the OMB, Congress, and other oversight bodies, as appropriate, to demonstrate accountability with specific statutory and regulatory privacy program mandates.'),
('003452','draft','2013-11-07','DISA FSO','policy','The organization develops reports for senior management and other personnel with responsibility for monitoring privacy program progress and compliance.','AR-6.4','The organization being inspected/assessed provides the necessary inputs to support DoD\'s internal privacy reporting requirements. For example, DoD Components are required to report to the Defense Privacy Office the status and metrics for internal periodic Privacy Act System of Records Notices (SORN) reviews. DoD 5400.11-R, sections C8.1-3 establish policy for DoD Component compliance DPCLO requirements for DoD Privacy Reports.','The organization conducting the inspection/assessment reviews evidence of contributions to internal privacy reports as mandated by the DPLCO and OCIO to ensure the organization being inspected/assessed develops reports for senior management and other personnel with responsibility for monitoring privacy program progress and compliance.'),
('003453','draft','2013-11-07','DISA FSO','policy','The organization disseminates reports to senior management and other personnel with responsibility for monitoring privacy program progress and compliance.','AR-6.5','The organization being inspected/assessed provides the necessary inputs to support DoD\'s internal privacy reports to the appropriate personnel in a timely manner.','The organization conducting the inspection/assessment reviews evidence of contributions to internal privacy reports as mandated by the DPCLO and OCIO to ensure the organization being inspected/assessed disseminates reports to senior management and other personnel with responsibility for monitoring privacy program progress and compliance.'),
('003454','draft','2013-11-07','DISA FSO','policy','The organization updates reports for senior management and other personnel with responsibility for monitoring privacy program progress and compliance.','AR-6.6','The organization being inspected/assessed provides the necessary inputs to support any required updates to DoD\'s internal privacy reports.','The organization conducting the inspection/assessment reviews evidence of contributions of updated inputs to internal privacy reports as mandated by the DPCLO and OCIO to ensure the organization being inspected/assessed updates reports for senior management and other personnel with responsibility for monitoring privacy program progress and compliance.'),
('003455','draft','2013-11-07','DISA FSO','policy','The organization designs information systems to support privacy by automating privacy controls.','AR-7.1','To the extent feasible, when designing information systems, the organization being inspected/assessed employs technologies and system capabilities that automate privacy controls on the collection, use, retention, and disclosure of personally identifiable information (PII).\n\nFor example, when sharing records between systems, design the system to only share PII data fields within a record that are relevant to the purpose of sharing rather than sending the entire record (which may contain PII data fields that are not relevant to the purpose for sharing). Privacy requirements and controls should be identified during the concept and requirements development phases of system design, and design decisions should be documented in appropriate system artifacts throughout (e.g. system design documents, system security plans, interconnection security agreements, and Privacy Impact Assessments). By building privacy controls into system design and development, DoD Components mitigate privacy risks to PII, thereby reducing the likelihood of information system breaches and other privacy-related incidents. DoD Components also plan for and conduct periodic reviews of systems to determine the need for updates to maintain compliance with the Privacy Act as well as the DoD\'s and DoD Component\'s privacy policies. Regardless of whether automated privacy controls are employed, DoD Components regularly monitor information system use and sharing of PII to ensure that the use/sharing is consistent with the authorized purposes identified in the Privacy Act and/or in the public notice of organizations (e.g. System of Records Notices), or in a manner compatible with those purposes.','The organization conducting the inspection/assessment :\n1. reviews policies and procedures that govern the organization\'s systems engineering lifecycle to ensure privacy requirements are included in the process.,\n2. obtains and examines system design documents and examines the information system to ensure it includes automated privacy controls,\n3. examines plans for periodic reviews to ensure they are commensurate with the privacy risks identified for the system and that they are occurring based on the planned frequency; and\n4. when available, examines results of reviews and associated action plans to address findings to ensure they are being addressed.'),
('003456','draft','2013-11-07','DISA FSO','policy','The organization, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the date of each disclosure of a record.','AR-8.1','The organization being inspected/assessed documents and implements a process, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, to include the date of each disclosure of a record.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the date of each disclosure of a record.'),
('003457','draft','2013-11-07','DISA FSO','policy','The organization, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the nature of each disclosure of a record.','AR-8.2','The organization being inspected/assessed documents and implements a process, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, to include the nature of each disclosure of a record.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the nature of each disclosure of a record.'),
('003458','draft','2013-11-07','DISA FSO','policy','The organization, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the purpose of each disclosure of a record.','AR-8.3','The organization being inspected/assessed documents and implements a process as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, to include the purpose of each disclosure of a record.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the purpose of each disclosure of a record.'),
('003459','draft','2013-11-07','DISA FSO','policy','The organization keeps an accurate accounting of disclosures of Privacy Act information held in each system of records under its control.','AR-8.4','The organization being inspected/assessed documents and implements a process to keep an accurate accounting of disclosures of Privacy Act information held in each system of records under its control.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed keeps an accurate accounting of disclosures of Privacy Act information held in each system of records under its control.'),
('003460','draft','2013-11-07','DISA FSO','policy','The organization, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the name and address of the person or agency to which the disclosure was made.','AR-8.5','The organization being inspected/assessed documents and implements a process, as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, to include the name and address of the person or agency to which the disclosure was made.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed as part of the accurate accounting of disclosures of Privacy Act information held in each system of records under its control, includes the name and address of the person or agency to which the disclosure was made.'),
('003461','draft','2013-11-07','DISA FSO','policy','The organization retains the accounting of disclosures for the life of the record or five years after the disclosure is made, whichever is longer.','AR-8.6','The organization being inspected/assessed documents and implements a process to retain the accounting of disclosures for the life of the record or five years after the disclosure is made, whichever is longer.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed retains the accounting of disclosures for the life of the record or five years after the disclosure is made, whichever is longer.'),
('003462','draft','2013-11-07','DISA FSO','policy','The organization makes the accounting of disclosures available to the person named in the record upon request.','AR-8.7','The organization being inspected/assessed documents and implements a process to make the accounting of disclosures available to the person named in the record upon request.\n\nNOTE: The system of the record might have an exemption that prevents the accounting of disclosures to the person named in the record. This must be spelled out in the SORN.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed makes the accounting of disclosures available to the person named in the record upon request.\n\nNOTE: The system of the record might have an exemption that prevents the accounting of disclosures to the person named in the record. This must be spelled out in the SORN.'),
('003463','draft','2013-11-07','DISA FSO','policy','The organization confirms to the greatest extent practicable upon collection or creation of personally identifiable information (PII), the accuracy of that information.','DI-1.1','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed confirms to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs.'),
('003464','draft','2013-11-07','DISA FSO','policy','The organization confirms to the greatest extent practicable upon collection or creation of personally identifiable information (PII), the relevancy of that information.','DI-1.2','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable upon collection or creation of PII, the relevancy of that information collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable upon collection or creation of PII, the relevancy of that information collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs'),
('003465','draft','2013-11-07','DISA FSO','policy','The organization confirms to the greatest extent practicable upon collection or creation of personally identifiable information (PII), the timeliness of that information.','DI-1.3','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable upon collection or creation of PII, the timeliness of that information collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable upon collection or creation of PII, the timeliness of that information collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs'),
('003466','draft','2013-11-07','DISA FSO','policy','The organization confirms to the greatest extent practicable upon collection or creation of personally identifiable information (PII), the completeness of that information.','DI-1.4','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable upon collection or creation of PII, the completeness of that information collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs.','The organization being inspected/assessed documents and implements a process to confirm to the greatest extent practicable upon collection or creation of PII, the completeness of that information collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs.'),
('003467','draft','2013-11-07','DISA FSO','policy','The organization collects personally identifiable information (PII) directly from the individual to the greatest extent practicable.','DI-1.5','The organization being inspected/assessed documents and implements a process to collect information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed collects information to the greatest extent practicable directly from the subject individual when the information may result in adverse determinations about an individual\'s rights, benefits, and privileges under Federal programs.'),
('003468','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency on which it will check for, and correct as necessary, inaccurate or outdated personally identifiable information (PII) used by its programs or systems.','DI-1.6','DoD has defined the frequency as when changes warrant corrections.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as when changes warrant corrections.'),
('003469','draft','2013-11-07','DISA FSO','policy','The organization checks for, and corrects as necessary, any inaccurate or outdated personally identifiable information (PII) used by its programs or systems on an organization-defined frequency.','DI-1.7','The organization being inspected/assessed documents and implements a process to checks for, and correct as necessary, any inaccurate or outdated PII used by its programs or systems when changes warrant corrections.\n\nDoD has defined the frequency as when changes warrant corrections.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed checks for, and corrects as necessary, any inaccurate or outdated PII used by its programs or systems when changes warrant corrections.\n\nDoD has defined the frequency as when changes warrant corrections.'),
('003470','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines ensuring the quality of disseminated Privacy Act information.','DI-1.8','The organization being inspected/assessed defines and issues PII quality assurance guidelines IAW DoD 5400.11-R to ensure accuracy, relevance, timeliness, and completion of PII prior to its dissemination. Quality guidelines are tailored as necessary for specific programs or systems.','The organization conducting the inspection/assessment reviews the PII quality guidelines for the organization being inspected/assessed against documentation for the program or system to ensure quality thresholds are being met.'),
('003471','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines ensuring the utility of disseminated Privacy Act information.','DI-1.9','The organization being inspected/assessed defines and issues PII utility guidelines IAW DoD 5400.11-R. Utility guidelines are tailored as necessary for specific programs or systems. Utility of information covered under the Privacy Act is strictly limited to an authorized purpose and need-to-know. When evaluating options for greater PII utility, consult with the DoD Component\'s privacy office.','The organization conducting the inspection/assessment reviews the PII utility guidelines for the organization being inspected/assessed against documentation for the program or system to ensure utility thresholds are being met and that PII is not shared other than as allowed by policy or notice.'),
('003472','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines ensuring the objectivity of disseminated Privacy Act information.','DI-1.10','The organization being inspected/assessed defines and issues PII objectivity guidelines IAW DoD 5400.11-R. Objectivity guidelines are tailored as necessary for specific programs or systems.','The organization conducting the inspection/assessment reviews the PII objectivity guidelines for the organization being inspected/assessed against documentation for the program or system to ensure objectivity thresholds are being met.'),
('003473','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines ensuring the integrity of disseminated Privacy Act information.','DI-1.11','The organization being inspected/assessed defines and issues PII integrity guidelines IAW DoD 5400.11-R. Integrity guidelines are tailored as necessary for specific programs or systems.','The organization conducting the inspection/assessment reviews the PII integrity guidelines for the organization being inspected/assessed against documentation for the program or system to ensure integrity thresholds are being met.'),
('003474','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines maximizing the quality of disseminated Privacy Act information.','DI-1.12','The organization being inspected/assessed defines and issues PII quality guidelines IAW DoD 5400.11-R. Quality guidelines are tailored as necessary for specific programs or systems.','The organization conducting the inspection/assessment reviews the PII quality guidelines for the organization being inspected/assessed against documentation for the program or system to ensure quality thresholds are being met.'),
('003475','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines maximizing the utility of disseminated Privacy Act information.','DI-1.13','The organization being inspected/assessed defines and issues PII utility guidelines IAW DoD 5400.11-R. Utility guidelines are tailored as necessary for specific programs or systems. Utility of information covered under the Privacy Act is strictly limited to an authorized purpose and need-to-know. When evaluating options for greater PII utility, consult with the DoD Component\'s privacy office.','The organization conducting the inspection/assessment reviews the PII utility guidelines for the organization being inspected/assessed against documentation for the program or system to ensure utility thresholds are being met and that PII is not shared other than as allowed by policy or notice.'),
('003476','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines maximizing the objectivity of disseminated Privacy Act information.','DI-1.14','The organization being inspected/assessed defines and issues PII objectivity guidelines IAW DoD 5400.11-R. Objectivity guidelines are tailored as necessary for specific programs or systems.','The organization conducting the inspection/assessment reviews the PII objectivity guidelines for the organization being inspected/assessed against documentation for the program or system to ensure objectivity thresholds are being met.'),
('003477','draft','2013-11-07','DISA FSO','policy','The organization issues guidelines maximizing the integrity of disseminated Privacy Act information.','DI-1.15','The organization being inspected/assessed defines and issues PII integrity guidelines IAW DoD 5400.11-R. Integrity guidelines are tailored as necessary for specific programs or systems.','The organization conducting the inspection/assessment reviews the PII integrity guidelines for the organization being inspected/assessed against documentation for the program or system to ensure integrity thresholds are being met.'),
('003478','draft','2013-11-07','DISA FSO','policy','The organization requests the individual or individual^s authorized representative validate personally identifiable information (PII) during the collection process.','DI-1(1).1','The organization being inspected/assessed documents and implements a process to request the individual or individual\'s authorized representative validate PII during the collection process.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requests the individual or individual\'s authorized representative validate PII during the collection process.'),
('003479','draft','2013-11-07','DISA FSO','policy','The organization defines the frequency on which it will request the individual, or individual^s authorized representative, revalidate that personally identifiable information (PII) collected is still accurate.','DI-1(2).1','The organization being inspected/assessed defines and documents the frequency on which it will request the individual, or individual\'s authorized representative, revalidate that PII collected is still accurate. The frequency should be as often as is necessary to ensure the PII is accurate, relevant, timely, and complete; commensurate with the impact of the determination to an individual\'s rights, benefits, or privileges as determined by the system owner in consultation with the organization\'s privacy office.\n\nDoD has determined the frequency is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented frequency to ensure the organization being inspected/assessed defines and documents the frequency on which it will request the individual, or individual\'s authorized representative, revalidate that PII collected is still accurate.\n\nDoD has determined the frequency is not appropriate to define at the Enterprise level.'),
('003480','draft','2013-11-07','DISA FSO','policy','On an organization-defined frequency, the organization requests the individual, or individual^s authorized representative, revalidate that personally identifiable information (PII) collected is still accurate.','DI-1(2).2','The organization being inspected/assessed documents and implements a process to request the individual, or individual\'s authorized representative, revalidate that PII collected is still accurate, as frequently as is necessary to ensure the PII is accurate, relevant, timely, and complete; commensurate with the impact of the determination to an individual\'s rights, benefits, or privileges as determined by the system owner in consultation with the organization\'s privacy office.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed requests the individual, or individual\'s authorized representative, revalidate that PII collected is still accurate. as frequently as is necessary to ensure the PII is accurate, relevant, timely, and complete; commensurate with the impact of the determination to an individual\'s rights, benefits, or privileges as determined by the system owner in consultation with the organization\'s privacy office.'),
('003481','draft','2013-11-07','DISA FSO','policy','The organization documents processes to ensure the integrity of personally identifiable information (PII) through existing security controls.','DI-2.1','The organization being inspected/assessed documents and implements the necessary security controls to protect the integrity of PII it maintains. Selection of security controls should be documented in relevant security documentation.\n\nNOTE: This applies to the security control for systems involved in computer matching agreements.','The organization conducting the inspection/assessment obtains and examines system documentation that discusses the selection of security controls and their relevance to privacy and confirms controls are in place for systems that maintain PII.\n\nNOTE: This applies to the security control for systems involved in computer matching agreements.'),
('003482','draft','2013-11-07','DISA FSO','policy','The organization, when appropriate, establishes a Data Integrity Board.','DI-2.2','The Defense Privacy and Civil Liberties Office (DPCLO) is responsible for meeting the requirements to establish a Data Integrity Board.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DPCLO.','The DPCLO is responsible for meeting the requirements to establish a Data Integrity Board.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DPCLO.'),
('003483','draft','2013-11-07','DISA FSO','policy','The organization^s Data Integrity Board oversees the organizational Computer Matching Agreements.','DI-2.3','The Defense Privacy and Civil Liberties Office (DPCLO) is responsible for the Data Integrity Board overseeing the organizational Computer Matching Agreements.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DPCLO.','The DPCLO is responsible for the Data Integrity Board overseeing the organizational Computer Matching Agreements.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DPCLO.'),
('003484','draft','2013-11-07','DISA FSO','policy','The organization^s Data Integrity Board ensures the Computer Matching Agreements comply with the computer matching provisions of the Privacy Act.','DI-2.4','The Defense Privacy and Civil Liberties Office (DPCLO) is responsible for the Data Integrity Board ensuring the Computer Matching Agreements comply with the computer matching provisions of the Privacy Act.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DPCLO.','The DPCLO is responsible for the Data Integrity Board ensuring the Computer Matching Agreements comply with the computer matching provisions of the Privacy Act.\n\nDoD Components are automatically compliant with this CCI because they are covered by the DPCLO.'),
('003485','draft','2013-11-07','DISA FSO','policy','The organization publishes Computer Matching Agreements on its public website.','DI-2(1).1','The Defense Privacy and Civil Liberties Office (DPCLO) is responsible for publishing Computer Matching Agreements on its public website.\n\nDoD Components are automatically compliant with this control because they are covered by the DPCLO.','The Defense Privacy and Civil Liberties Office (DPCLO) is responsible for publishing Computer Matching Agreements on its public website.\n\nDoD Components are automatically compliant with this control because they are covered by the DPCLO.'),
('003486','draft','2013-11-08','DISA FSO','policy','The organization identifies the minimum personally identifiable information (PII) elements that are relevant and necessary to accomplish the legally authorized purpose of collection.','DM-1.1','The organization being inspected/assessed documents and implements a process to identify the minimum personally identifiable information (PII) elements that are relevant and necessary to accomplish the legally authorized purpose of collection.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed identifies the minimum personally identifiable information (PII) elements that are relevant and necessary to accomplish the legally authorized purpose of collection.'),
('003487','draft','2013-11-08','DISA FSO','policy','The organization limits the collection and retention of personally identifiable information (PII) to the minimum elements identified for the purposes described in the published privacy notice.','DM-1.2','The organization being inspected/assessed documents and implements a process to limit the collection and retention of PII to the minimum elements identified for the purposes described in the published SORN and Privacy Act Statement.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed limits the collection and retention of PII to the minimum elements identified for the purposes described in the published SORN and Privacy Act Statement.'),
('003488','draft','2013-11-08','DISA FSO','policy','The organization limits the collection and retention of personally identifiable information (PII) to the minimum elements identified for the purposes which the individual has provided consent.','DM-1.3','The organization being inspected/assessed documents and implements a process to limit the collection and retention of PII to the minimum elements identified for the purposes which the individual has provided consent.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed limits the collection and retention of PII to the minimum elements identified for the purposes which the individual has provided consent.'),
('003489','draft','2013-11-08','DISA FSO','policy','The organization defines the frequency, minimally annually, for conducting reviews of its personally identifiable information (PII) holdings.','DM-1.4','DoD has defines the frequency as annually as part of the agency\'s report under FISMA.','DoD has defines the frequency as annually as part of the agency\'s report under FISMA.'),
('003490','draft','2013-11-08','DISA FSO','policy','The organization conducts an initial evaluation of personally identifiable information (PII) holdings.','DM-1.5','The organization being inspected/assessed documents and implements a process to conduct an initial evaluation of PII holdings.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed conducts an initial evaluation of PII holdings'),
('003491','draft','2013-11-08','DISA FSO','policy','The organization establishes a schedule for regularly reviewing the personally identifiable information (PII) holdings on an organization-defined frequency to ensure that only PII identified in the notice is collected and retained.','DM-1.6','The organization being inspected/assessed establishes and documents a schedule for regularly reviewing the PII holdings at least annually as part of the agency\'s report under FISMA to ensure that only PII identified in the notice is collected and retained.\n\nDoD has defined the frequency as at least annually as part of the agency\'s report under FISMA.','The organization conducting the inspection/assessment obtains and examines the documented schedule to ensure the organization being inspected/assessed establishes a schedule for regularly reviewing the PII holdings at least annually as part of the agency\'s report under FISMA to ensure that only PII identified in the notice is collected and retained.\n\nDoD has defined the frequency as at least annually as part of the agency\'s report under FISMA.'),
('003492','draft','2013-11-08','DISA FSO','policy','The organization follows a schedule for regularly reviewing the personally identifiable information (PII) holdings on an organization-defined frequency to ensure that only PII identified in the notice is collected and retained.','DM-1.7','The organization being inspected/assessed documents and implements a process to follow a schedule for regularly reviewing the PII holdings per the frequency defined in DM-1, CCI 3489 to ensure that only PII identified in the notice is collected and retained.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed follows a schedule for regularly reviewing the PII holdings per the frequency defined in DM-1, CCI 3489 to ensure that only PII identified in the notice is collected and retained.'),
('003493','draft','2013-11-08','DISA FSO','policy','The organization establishes a schedule for regularly reviewing the personally identifiable information (PII) holdings on an organization-defined frequency to ensure the PII continues to be necessary to accomplish the legally authorized purpose.','DM-1.8','The organization being inspected/assessed establishes and documents a schedule for regularly reviewing the PII holdings per the frequency defined in DM-1, CCI 3489 to ensure the PII continues to be necessary to accomplish the legally authorized purpose.','The organization conducting the inspection/assessment obtains and examines the documented schedule to ensure the organization being inspected/assessed establishes a schedule for regularly reviewing the PII holdings per the frequency defined in DM-1, CCI 3489 to ensure the PII continues to be necessary to accomplish the legally authorized purpose.'),
('003494','draft','2013-11-08','DISA FSO','policy','The organization follows a schedule for regularly reviewing the personally identifiable information (PII) holdings on an organization-defined frequency to ensure the PII continues to be necessary to accomplish the legally authorized purpose.','DM-1.9','The organization being inspected/assessed documents and implements a process to follow a schedule for regularly reviewing the PII holdings per the frequency defined in DM-1, CCI 3489 to ensure the PII continues to be necessary to accomplish the legally authorized purpose.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed follows a schedule for regularly reviewing the PII holdings per the frequency defined in DM-1, CCI 3489 to ensure the PII continues to be necessary to accomplish the legally authorized purpose.'),
('003495','draft','2013-11-08','DISA FSO','policy','The organization, where feasible and within the limits of technology, locates and removes/redacts specified personally identifiable information (PII).','DM-1(1).1','The organization being inspected/assessed documents and implements a process to locate and remove/redact specified PII, where feasible and within the limits of technology.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed where feasible and within the limits of technology, locates and removes/redacts specified PII.'),
('003496','draft','2013-11-08','DISA FSO','policy','The organization, where feasible and within the limits of technology, uses anonymization and de-identification techniques to permit use of the retained Privacy Act information while reducing its sensitivity and reducing the risk resulting from disclosure.','DM-1(1).2','The organization being inspected/assessed documents and implements a process to use anonymization and de-identification techniques, where feasible and within the limits of technology, to permit use of the retained Privacy Act information while reducing its sensitivity and reducing the risk resulting from disclosure.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed, where feasible and within the limits of technology, uses anonymization and de-identification techniques to permit use of the retained Privacy Act information while reducing its sensitivity and reducing the risk resulting from disclosure.'),
('003497','draft','2013-11-08','DISA FSO','policy','The organization defines the time period for retaining each collection of personally identifiable information (PII) that is required to fulfill the purpose(s) identified in the published privacy notice or required by law.','DM-2.1','The organization being inspected/assessed must define and document the time period IAW the NARA-approved Records Schedule and the Privacy Act System of Records Notice.\n\nDoD has determined the time period is not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented time period to ensure the organization being inspected/assessed define and document the time period IAW the NARA-approved Records Schedule and the Privacy Act System of Records Notice.\n\nDoD has determined the time period is not appropriate to define at the Enterprise level.'),
('003498','draft','2013-11-08','DISA FSO','policy','The organization retains each collection of personally identifiable information (PII) for the organization-defined time period to fulfill the purpose(s) identified in the published privacy notice or as required by law.','DM-2.2','The organization being inspected/assessed documents and implements a process to retain each collection of PII for the time period defined DM-2, CCI 3497 to fulfill the purpose(s) identified in the published SORN and Privacy Act Statement or as required by law.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed retains each collection of PII for the time period defined in DM-2, CCI 3497 to fulfill the purpose(s) identified in the published SORN and Privacy Act Statement or as required by law.'),
('003499','draft','2013-11-08','DISA FSO','policy','The organization disposes of, destroys, erases, and/or anonymizes the personally identifiable information (PII), regardless of the method of storage, in accordance with a NARA-approved record retention schedule.','DM-2.3','The organization being inspected/assessed documents and implements a process to dispose of, destroy, erase, and/or anonymize the PII, regardless of the method of storage, in accordance with a NARA-approved record retention schedule.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed disposes of, destroys, erases, and/or anonymizes the PII, regardless of the method of storage, in accordance with a NARA-approved record retention schedule.'),
('003500','draft','2013-11-08','DISA FSO','policy','The organization disposes of, destroys, erases, and/or anonymizes the personally identifiable information (PII), regardless of the method of storage, in a manner that prevents loss, theft, misuse, or unauthorized access.','DM-2.4','The organization being inspected/assessed documents and implements a process to dispose of, destroy, erase, and/or anonymize the PII, regardless of the method of storage, in a manner that prevents loss, theft, misuse, or unauthorized access.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed disposes of, destroys, erases, and/or anonymizes the PII, regardless of the method of storage, in a manner that prevents loss, theft, misuse, or unauthorized access.'),
('003501','draft','2013-11-08','DISA FSO','policy','The organization defines the techniques or methods to be employed to ensure the secure deletion or destruction of personally identifiable information (PII) (including originals, copies, and archived records).','DM-2.5','DoD has defined the techniques or methods as techniques and methods IAW DoD 5400.11-R.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the techniques or methods as techniques and methods IAW DoD 5400.11-R.'),
('003502','draft','2013-11-08','DISA FSO','policy','The organization uses organization-defined techniques or methods to ensure secure deletion or destruction of personally identifiable information (PII) (including originals, copies, and archived records).','DM-2.6','The organization being inspected/assessed documents and implements a process to use techniques and methods IAW DoD 5400.11-R to ensure secure deletion or destruction of PII (including originals, copies, and archived records).\n\nDoD has defined the techniques or methods as techniques and methods IAW DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed uses techniques and methods IAW DoD 5400.11-R to ensure secure deletion or destruction of PII (including originals, copies, and archived records).\n\nDoD has defined the techniques or methods as techniques and methods IAW DoD 5400.11-R.'),
('003503','draft','2013-11-08','DISA FSO','policy','The organization, where feasible, configures its information systems to record the date personally identifiable information (PII) is collected, created, or updated.','DM-2(1).1','The organization being inspected/assessed documents and implements a process to configure, where feasible, its information systems to record the date PII is collected, created, or updated.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed configures, where feasible, its information systems to record the date PII is collected, created, or updated.'),
('003504','deprecated','2013-11-08','DISA FSO','policy','The organization, where feasible, configures its information systems to record the date personally identifiable information (PII) is created.',NULL,NULL,NULL),
('003505','deprecated','2013-11-08','DISA FSO','policy','The organization, where feasible, configures its information systems to record the date personally identifiable information (PII) is updated.',NULL,NULL,NULL),
('003506','draft','2013-11-08','DISA FSO','policy','The organization, where feasible, configures its information systems to record when personally identifiable information (PII) is to be deleted or archived under an approved record retention schedule.','DM-2(1).2','The organization being inspected/assessed documents and implements a process to configure, where feasible, its information systems to record when PII is to be deleted or archived under a NARA-approved record retention schedule.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed, where feasible, configures its information systems to record when PII is to be deleted or archived under a NARA-approved record retention schedule.'),
('003507','draft','2013-11-08','DISA FSO','policy','The organization develops policies that minimize the use of personally identifiable information (PII) for testing.','DM-3.1','The organization being inspected/assessed develops and documents policies that minimize the use of PII for testing.','The organization conducting the inspection/assessment obtains and examines the documented policies to ensure the organization being inspected/assessed develops policies that minimize the use of PII for testing.'),
('003508','draft','2013-11-08','DISA FSO','policy','The organization develops policies that minimize the use of personally identifiable information (PII) for training.','DM-3.2','The organization being inspected/assessed develops and documents policies that minimize the use of PII for training.','The organization conducting the inspection/assessment obtains and examines the documented policies to ensure the organization being inspected/assessed develops policies that minimize the use of PII for training.'),
('003509','draft','2013-11-08','DISA FSO','policy','The organization develops policies that minimize the use of personally identifiable information (PII) for research.','DM-3.3','The organization being inspected/assessed develops and documents policies that minimize the use of PII for research.','The organization conducting the inspection/assessment obtains and examines the documented policies to ensure the organization being inspected/assessed develops policies that minimize the use of PII for research.'),
('003510','draft','2013-11-08','DISA FSO','policy','The organization develops procedures that minimize the use of personally identifiable information (PII) for testing.','DM-3.4','The organization being inspected/assessed develops and documents procedures that minimize the use of PII for testing.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed develops procedures that minimize the use of PII for testing.'),
('003511','draft','2013-11-08','DISA FSO','policy','The organization develops procedures that minimize the use of personally identifiable information (PII) for training.','DM-3.5','The organization being inspected/assessed develops and documents procedures that minimize the use of PII for training.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed develops procedures that minimize the use of PII for training.'),
('003512','draft','2013-11-08','DISA FSO','policy','The organization develops procedures that minimize the use of personally identifiable information (PII) for research.','DM-3.6','The organization being inspected/assessed develops and documents procedures that minimize the use of PII for research.','The organization conducting the inspection/assessment obtains and examines the documented procedures to ensure the organization being inspected/assessed develops procedures that minimize the use of PII for research.'),
('003513','draft','2013-11-08','DISA FSO','policy','The organization implements controls to protect personally identifiable information (PII) used for testing.','DM-3.7','The organization being inspected/assessed will complete a Privacy Impact Assessment (PIA) for any information system that uses PII for testing and implement the identified controls.','The organization conducting the inspection/assessment obtains and examines the PIA for all information systems using PII for testing to ensure the PIA is completed and approved. The organization conducting the inspection/assessment inspects the information system to ensure the organization being inspected/assessed has properly implemented the controls identified in the PIA to protect PII.'),
('003514','draft','2013-11-08','DISA FSO','policy','The organization implements controls to protect personally identifiable information (PII) used for training.','DM-3.8','The organization being inspected/assessed will complete a Privacy Impact Assessment (PIA) for any information system that uses PII for training and implement the identified controls.','The organization conducting the inspection/assessment obtains and examines the PIA for all information systems using PII for training to ensure the PIA is completed and approved. The organization conducting the inspection/assessment inspects the information system to ensure the organization being inspected/assessed has properly implemented the controls identified in the PIA to protect PII.'),
('003515','draft','2013-11-08','DISA FSO','policy','The organization implements controls to protect personally identifiable information (PII) used for research.','DM-3.9','The organization being inspected/assessed will complete a Privacy Impact Assessment (PIA) for any information system that uses PII for research and implement the identified controls.','The organization conducting the inspection/assessment obtains and examines the PIA for all information systems using PII for research to ensure the PIA is completed and approved. The organization conducting the inspection/assessment inspects the information system to ensure the organization being inspected/assessed has properly implemented the controls identified in the PIA to protect PII.'),
('003516','draft','2013-11-08','DISA FSO','policy','The organization, where feasible, uses techniques to minimize the risk to privacy of using personally identifiable information (PII) for research.','DM-3(1).1','The organization being inspected/assessed documents and implements\ntechniques (such as de-identification or anonymization) to minimize the risk\nto privacy of using PII for research. Where such techniques aren\'t feasible due to the parameters of the research, the organization will document the justification for not implementing such techniques.','The organization conducting the inspection/assessment obtains and examines the documented techniques to minimize the risk to privacy of using PII for research and verifies that these techniques are being used\nor that the justifications for not using them are documented.'),
('003517','draft','2013-11-08','DISA FSO','policy','The organization, where feasible, uses techniques to minimize the risk to privacy of using personally identifiable information (PII) for testing.','DM-3(1).2','The organization being inspected/assessed documents and implements\ntechniques (such as de-identification or anonymization) to minimize the risk\nto privacy of using PII for testing. Where such techniques aren\'t feasible due to the parameters of the testing, the organization will document the justification for not implementing such techniques.','The organization conducting the inspection/assessment obtains and examines the documented techniques to minimize the risk to privacy of using PII for testing and verifies that these techniques are being used\nor that the justifications for not using them are documented.'),
('003518','draft','2013-11-08','DISA FSO','policy','The organization, where feasible, uses techniques to minimize the risk to privacy of using personally identifiable information (PII) for training.','DM-3(1).3','The organization being inspected/assessed documents and implements\ntechniques (such as de-identification or anonymization) to minimize the risk\nto privacy of using PII for training. Where such techniques aren\'t feasible due to the parameters of the training, the organization will document the justification\nfor not implementing such training.','The organization conducting the inspection/assessment obtains and examines the documented techniques to minimize the risk to privacy of using PII for training and verifies that these techniques are being used\nor that the justifications for not using them are documented.'),
('003519','draft','2013-11-08','DISA FSO','policy','The organization provides means, where feasible and appropriate, for individuals to authorize the collection of personally identifiable information (PII) prior to its collection.','IP-1.1','The organization being inspected/assessed documents and implements a procedure for individuals to authorize the collection of personally identifiable\ninformation (PII) prior to its collection. Minimally, where individual\nauthorization is not feasible or appropriate, the organization will notify\nusers that PII is being collected.','The organization conducting the inspection/assessment obtains and examines the documented procedure as well as a sampling of artifacts related to the authorization of collection of PII to ensure the organization being inspected/assessed provides means, where feasible and appropriate, for individuals to authorize the collection of PII prior to its collection. Where authorization is not feasible or appropriate, the organization conducting the inspection/assessment ensures that the organization notifies users that PII is being collected.'),
('003520','draft','2013-11-08','DISA FSO','policy','The organization provides means, where feasible and appropriate, for individuals to authorize the use of personally identifiable information (PII) prior to its collection.','IP-1.2','The organization being inspected/assessed documents and implements a procedure for individuals to authorize the use of personally identifiable\ninformation (PII) prior to its collection. Minimally, where individual\nauthorization is not feasible or appropriate, the organization will notify\nusers that PII is being used.','The organization conducting the inspection/assessment obtains and examines the documented procedure as well as a sampling of artifacts related to the authorization of the use of PII to ensure the organization being inspected/assessed provides means, where feasible and appropriate, for individuals to authorize the use of PII prior to its collection. Where authorization is not feasible or appropriate, the organization conducting the inspection/assessment ensures that the organization notifies users that PII is being used.'),
('003521','draft','2013-11-08','DISA FSO','policy','The organization provides means, where feasible and appropriate, for individuals to authorize the maintaining of personally identifiable information (PII) prior to its collection.','IP-1.3','The organization being inspected/assessed documents and implements a procedure for individuals to authorize the maintaining of personally identifiable\ninformation (PII) prior to its collection. Minimally, where individual\nauthorization is not feasible or appropriate, the organization will notify\nusers that PII is being maintained.','The organization conducting the inspection/assessment obtains and examines the documented procedure as well as a sampling of artifacts related to the authorization of the maintaining of PII to ensure the organization being inspected/assessed provides means, where feasible and appropriate, for individuals to authorize the maintaining of PII prior to its collection. Where authorization is not feasible or appropriate, the organization conducting the inspection/assessment ensures that the organization notifies users that PII is being maintained.'),
('003522','draft','2013-11-08','','policy','The organization provides means, where feasible and appropriate, for individuals to authorize sharing of personally identifiable information (PII) prior to its collection.','IP-1.4','The organization being inspected/assessed documents and implements a procedure for individuals to authorize the sharing of personally identifiable\ninformation (PII) prior to its collection. Minimally, where individual\nauthorization is not feasible or appropriate, the organization will notify\nusers that PII is being shared.','The organization conducting the inspection/assessment obtains and examines the documented procedure as well as a sampling of artifacts related to the authorization of the sharing of PII to ensure the organization being inspected/assessed provides means, where feasible and appropriate, for individuals to authorize the sharing of PII prior to its collection. Where authorization is not feasible or appropriate, the organization conducting the inspection/assessment ensures that the organization notifies users that PII is being shared.'),
('003523','draft','2013-11-08','DISA FSO','policy','The organization provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the collection of personally identifiable information (PII).','IP-1.5','The organization being inspected/assessed documents and implements a procedure for individuals to understand the consequences of decisions to approve or decline the authorization of the collection of PII.','The organization conducting the inspection/assessment obtains and examines the documented procedure to ensure the organization being inspected/assessed provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the collection of PII.'),
('003524','draft','2013-11-08','DISA FSO','policy','The organization provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the use of personally identifiable information (PII).','IP-1.6','The organization being inspected/assessed documents and implements a procedure for individuals to understand the consequences of decisions to approve or decline the authorization of the use of PII.','The organization conducting the inspection/assessment obtains and examines the documented procedure to ensure the organization being inspected/assessed provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the use of PII.'),
('003525','draft','2013-11-08','DISA FSO','policy','The organization provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the dissemination of personally identifiable information (PII).','IP-1.7','The organization being inspected/assessed documents and implements a procedure for individuals to understand the consequences of decisions to approve or decline the authorization of the dissemination of PII.','The organization conducting the inspection/assessment obtains and examines the documented procedure to ensure the organization being inspected/assessed provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the dissemination of PII.'),
('003526','draft','2013-11-08','DISA FSO','policy','The organization provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the retention of personally identifiable information (PII).','IP-1.8','The organization being inspected/assessed documents and implements a procedure for individuals to understand the consequences of decisions to approve or decline the authorization of the retention of PII.','The organization conducting the inspection/assessment obtains and examines the documented procedure to ensure the organization being inspected/assessed provides appropriate means for individuals to understand the consequences of decisions to approve or decline the authorization of the retention of PII.'),
('003527','draft','2013-11-08','DISA FSO','policy','The organization obtains consent, where feasible and appropriate, from individuals prior to any new uses or disclosure of previously collected personally identifiable information (PII).','IP-1.9','The organization being inspected/assessed documents and implements a process to obtain consent, where feasible and appropriate, from individuals prior to any new uses or disclosure of previously collected PII. Minimally, where consent is not feasible or appropriate, the organization will notify users of new uses or disclosure of previously collected PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed obtains consent, where feasible and appropriate, from individuals prior to any new uses or disclosure of previously collected PII. Where consent is not feasible or appropriate, the organization conducting the inspection/assessment ensures that the organization notifies users of new uses or disclosure of previously collected PII.'),
('003528','draft','2013-11-08','DISA FSO','policy','The organization ensures that individuals are aware of all uses of personally identifiable information (PII) not initially described in the public notice that was in effect at the time the organization collected the PII.','IP-1.10','The organization being inspected/assessed documents and implements a process to ensure that individuals are aware of all uses of PII not initially described in the SORN and Privacy Act Statement that was in effect at the time the organization collected the PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that individuals are aware of all uses of PII not initially described in the SORN and Privacy Act Statement that was in effect at the time the organization collected the PII.'),
('003529','draft','2013-11-08','DISA FSO','policy','The organization ensures that individuals, where feasible, consent to all uses of personally identifiable information (PII) not initially described in the public notice that was in effect at the time the organization collected the PII.','IP-1.11','The organization being inspected/assessed documents and implements a process to ensure that individuals, where feasible, consent to all uses of PII not initially described in the SORN and Privacy Act Statement that was in effect at the time the organization collected the PII. Minimally, where consent is not feasible or appropriate, the organization will notify users of all uses of PII not initially described in the SORN and Privacy Act Statement that was in effect at the time the organization collected the PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed ensures that individuals, where feasible, consent to all uses of PII not initially described in the SORN and Privacy Act Statement that was in effect at the time the organization collected the PII. Where consent is not feasible or appropriate, the organization conducting the inspection/assessment ensures that the organization notifies users of PII not initially described in the SORN and Privacy Act Statement that was in effect at the time the organization collected the PII.'),
('003530','draft','2013-11-08','DISA FSO','policy','The organization implements mechanisms to support itemized or tiered consent for specific uses of personally identifiable information (PII) data.','IP-1(1).1','The organization implements mechanisms to support itemized or tiered consent for specific uses of PII data.','The organization conducting the inspection/assessment obtains and examines documentation of the itemized or tiered consent methods used by the organization to ensure the organization being inspected/assessed provides individuals, where feasible, consent to each tier of use requested.'),
('003531','draft','2013-11-08','DISA FSO','policy','The organization provides individuals the ability to have access to their personally identifiable information (PII) maintained in its system(s) of records.','IP-2.1','The organization being inspected/assessed provides for public access to records in systems of records IAW the SORN. PII not included in the Privacy Act System of Records may be accessed through a Freedom of Information Act Request. At a minimum the organization shall provide access to an individuals own PII IAW both DoDD 5400.11 and DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines documentation of how the organization provides an individual with access to his own PII to ensure the organization being inspected/assessed provides individuals access to his own PII IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003532','draft','2013-11-08','DISA FSO','policy','The organization publishes rules and regulations governing how individuals may request access to records maintained in a Privacy Act system of records.','IP-2.2','The organization being inspected/assessed provides for public access to records in systems of records IAW the SORN. PII not included in the Privacy Act System of Records may be accessed through a Freedom of Information Act Request. At a minimum the organization shall provide access to an individuals own PII IAW both DoDD 5400.11 and DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines documentation of how the organization provides an individual with access to his own PII to ensure the organization being inspected/assessed provides individuals access to his own PII IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003533','deprecated','2013-11-08','DISA FSO','policy','The organization publishes regulations governing how individuals may request access to records maintained in a Privacy Act system of records.','IP-2.3','The organization being inspected/assessed provides for public access to records in systems of records IAW the SORN. PII not included in the Privacy Act System of Records may be accessed through a Freedom of Information Act Request. At a minimum the organization shall provide access to an individuals own PII IAW both DoDD 5400.11 and DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines documentation of how the organization provides an individual with access to his own PII to ensure the organization being inspected/assessed provides individuals access to his own PII IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003534','draft','2013-11-08','DISA FSO','policy','The organization publishes access procedures for Privacy Act systems of records in System of Records Notices (SORNs).','IP-2.4','The organization being inspected/assessed provides for public access to records in systems of records IAW the SORN. PII not included in the Privacy Act System of Records may be accessed through a Freedom of Information Act Request. At a minimum the organization shall provide access to an individuals own PII IAW both DoDD 5400.11 and DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines documentation of how the organization provides an individual with access to his own PII to ensure the organization being inspected/assessed provides individuals access to his own PII IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003535','draft','2013-11-08','DISA FSO','policy','The organization adheres to Privacy Act requirements for the proper processing of Privacy Act requests.','IP-2.5','The organization being inspected/assessed provides for public access to records in systems of records IAW the SORN. PII not included in the Privacy Act System of Records may be accessed through a Freedom of Information Act Request. At a minimum the organization shall provide access to an individuals own PII IAW both DoDD 5400.11 and DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines documentation of how the organization provides an individual with access to his own PII to ensure the organization being inspected/assessed provides individuals access to his own PII IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003536','draft','2013-11-08','DISA FSO','policy','The organization adheres to OMB policies and guidance for the proper processing of Privacy Act requests.','IP-2.6','The organization being inspected/assessed provides for public access to records in systems of records IAW the SORN. PII not included in the Privacy Act System of Records may be accessed through a Freedom of Information Act Request. At a minimum the organization shall provide access to an individuals own PII IAW both DoDD 5400.11 and DoD 5400.11-R.','The organization conducting the inspection/assessment obtains and examines documentation of how the organization provides an individual with access to his own PII to ensure the organization being inspected/assessed provides individuals access to his own PII IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003537','draft','2013-11-08','DISA FSO','policy','The organization provides a process for individuals to have inaccurate personally identifiable information (PII) maintained by the organization corrected or amended, as appropriate.','IP-3.1','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R for individuals to have inaccurate PII maintained by the organization corrected or amended, as appropriate.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides a process IAW DoDD 5400.11 and DoD 5400.11-R for individuals to have inaccurate PII maintained by the organization corrected or amended, as appropriate.'),
('003538','draft','2013-11-08','DISA FSO','policy','The organization establishes a process for disseminating corrections or amendments of the personally identifiable information (PII) to other authorized users of the PII, such as external information-sharing partners.','IP-3.2','The organization being inspected/assessed establishes and documents a process IAW DoDD 5400.11 and DoD 5400.11-R for disseminating corrections or amendments of the PII to other authorized users of the PII, such as external information-sharing partners.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes a process IAW DoDD 5400.11 and DoD 5400.11-R for disseminating corrections or amendments of the PII to other authorized users of the PII, such as external information-sharing partners.'),
('003539','draft','2013-11-08','DISA FSO','policy','The organization establishes a process, where feasible and appropriate, to notify affected individuals that their personally identifiable information (PII) information has been corrected or amended.','IP-3.3','The organization being inspected/assessed establishes and documents a process IAW DoDD 5400.11 and DoD 5400.11-R where feasible and appropriate, to notify affected individuals that their PII information has been corrected or amended.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed establishes a process IAW DoDD 5400.11 and DoD 5400.11-R, where feasible and appropriate, to notify affected individuals that their PII information has been corrected or amended.'),
('003540','draft','2013-11-08','DISA FSO','policy','The organization implements a process for receiving complaints, concerns, or questions from individuals about the organizational privacy practices.','IP-4.1','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and for receiving privacy-related complaints, grievances, concerns, or questions from individuals','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process IAW DoD 5400.11-R and OMB Memorandum M-08-09 for receiving complaints, grievances, concerns, or questions from individuals about: (1) organizational privacy process and procedural issues (consent, collection, and appropriate notice); (2) redress issues (non-Privacy Act inquiries seeking resolution of difficulties or concerns about privacy matters); (3) operational issues (inquiries regarding Privacy Act matters not including Privacy Act requests for access and/or corrections); and (4) a complaint or grievance against the organization or one of its employees concerning any right granted by DoD 5400.11-R.'),
('003541','draft','2013-11-08','DISA FSO','policy','The organization implements a process for responding to complaints, concerns, or questions from individuals about the organizational privacy practices.','IP-4.2','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and for responding to privacy-related complaints, grievances, concerns, or questions from individuals','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed implements a process IAW DoD 5400.11-R and OMB Memorandum M-08-09 for processing complaints, grievances, concerns, or questions from individuals about: (1) organizational privacy process and procedural issues (consent, collection, and appropriate notice); (2) redress issues (non-Privacy Act inquiries seeking resolution of difficulties or concerns about privacy matters); (3) operational issues (inquiries regarding Privacy Act matters not including Privacy Act requests for access and/or corrections); and (4) a complaint or grievance against the organization or one of its employees concerning any right granted by DoD 5400.11-R.'),
('003542','draft','2013-11-08','DISA FSO','policy','The organization defines the time period within which it must respond to complaints, concerns, or questions from individuals about the organizational privacy practices.','IP-4(1).1','DoD has defined the time period as 30 days within receipt of the initial complaint.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the time period as 30 days within receipt of the initial complaint.'),
('003543','draft','2013-11-08','DISA FSO','policy','The organization responds to complaints, concerns, or questions from individuals about the organizational privacy practices within the organization-defined time period.','IP-4(1).2','The organization being inspected/assessed documents and implements a process to respond to complaints, concerns, or questions from individuals about the organizational privacy practices within 30 days within receipt of the initial complaint.\n\nDoD has defined the time period as 30 days within receipt of the initial complaint.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed responds to complaints, concerns, or questions from individuals about the organizational privacy practices within 30 days within receipt of the initial complaint.\n\nDoD has defined the time period as 30 days within receipt of the initial complaint.'),
('003544','draft','2013-11-08','DISA FSO','policy','The organization defines the frequency on which it will update the inventory that contains a listing of all programs and information systems identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.1','DoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.'),
('003545','draft','2013-11-08','DISA FSO','policy','The organization establishes an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.2','The organization being inspected/assessed establishes and documents an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing PII.','The organization conducting the inspection/assessment obtains and examines the documented inventory to ensure the organization being inspected/assessed establishes an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing PII.'),
('003546','draft','2013-11-08','DISA FSO','policy','The organization establishes an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.3','The organization being inspected/assessed establishes and documents an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing PII.','The organization conducting the inspection/assessment obtains and examines the documented inventory to ensure the organization being inspected/assessed establishes an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing PII.'),
('003547','draft','2013-11-08','DISA FSO','policy','The organization maintains an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.4','The organization being inspected/assessed documents and implements a process to maintain an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed maintains an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing PII.'),
('003548','draft','2013-11-08','DISA FSO','policy','The organization maintains an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.5','The organization being inspected/assessed documents and implements a process to maintain an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed maintains an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing PII.'),
('003549','draft','2013-11-08','DISA FSO','policy','The organization updates, per organization-defined frequency, an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.6','The organization being inspected/assessed documents and implements a process to update, within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs, an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing PII.\n\nThe organization must maintain an audit trail of updates.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of updates to ensure the organization being inspected/assessed updates, within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs, an inventory that contains a listing of all programs identified as collecting, using, maintaining, or sharing PII.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.'),
('003550','draft','2013-11-08','DISA FSO','policy','The organization updates, per organization-defined frequency, an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing personally identifiable information (PII).','SE-1.7','The organization being inspected/assessed documents and implements a process to update, within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs, an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing PII.\n\nThe organization must maintain an audit trail of updates.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of updates to ensure the organization being inspected/assessed updates, within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs, an inventory that contains a listing of all information systems identified as collecting, using, maintaining, or sharing PII.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.'),
('003551','draft','2013-11-08','DISA FSO','policy','The organization defines the frequency for providing each update of the personally identifiable information (PII) inventory to the CIO or information security official.','SE-1.8','DoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.','The organization being inspected/assessed is automatically compliant with this CCI because they are covered at the DoD level.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.'),
('003552','draft','2013-11-08','DISA FSO','policy','The organization provides each update of the personally identifiable information (PII) inventory to the CIO or information security official, per organization-defined frequency, to support the establishment of information security requirements for all new or modified information systems containing PII.','SE-1.9','The organization being inspected/assessed documents and implements a process to provide each update of the PII inventory to the CIO or information security official, within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs, to support the establishment of information security requirements for all new or modified information systems containing PII.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides each update of the PII inventory to the CIO or information security official, within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs, to support the establishment of information security requirements for all new or modified information systems containing PII.\n\nDoD has defined the frequency as within three years of PIA approval and when a significant system change or a change in privacy or security posture occurs.'),
('003553','draft','2013-11-08','DISA FSO','policy','The organization develops a Privacy Incident Response Plan.','SE-2.1','The organization being inspected/assessed develops and documents a Privacy Incident Response Plan. The revision of DoD 5400.11-R into a manual provides DoD-enterprise-level guidance on breach reporting. Components may decide to augment this with their own incident response plan. The privacy incident response plan may be included as a part of the organization\'s existing response plan.','The organization conducting the inspection/assessment obtains and examines the documented Privacy Incident Response Plan to ensure the organization being inspected/assessed develops a Privacy Incident Response Plan.'),
('003554','draft','2013-11-08','DISA FSO','policy','The organization implements a Privacy Incident Response Plan.','SE-2.2','The organization being inspected/assessed implements a Privacy Incident Response Plan. The revision of DoD 5400.11-R into a manual provides DoD-enterprise-level guidance on breach reporting. Components may decide to augment this with their own incident response plan.','The organization conducting the inspection/assessment obtains and examines the documented Privacy Incident Response Plan to ensure the organization being inspected/assessed implements a Privacy Incident Response Plan.'),
('003555','draft','2013-11-08','DISA FSO','policy','The organization provides an organized and effective response to privacy incidents in accordance with the organizational Privacy Incident Response Plan.','SE-2.3','The organization being inspected/assessed documents and implements a process to provides an organized and effective response to privacy incidents in accordance with the organizational Privacy Incident Response Plan. The revision of DoD 5400.11-R into a manual provides DoD-enterprise-level guidance on breach reporting. Components may decide to augment this with their own incident response plan. The privacy incident response plan, which may be included as a part of your existing response plan.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides an organized and effective response to privacy incidents in accordance with the organizational Privacy Incident Response Plan.'),
('003556','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to the public regarding its activities that impact privacy, including its collection, use, sharing, safeguarding, maintenance, and disposal of personally identifiable information (PII).','TR-1.1','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to the public regarding its activities that impact privacy, including its collection, use, sharing, safeguarding, maintenance, and disposal of personally identifiable information (PII).','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice to the public IAW DoD 5400.11-R and DoDI 5400.16 regarding its activities that impact privacy, including its collection, use, sharing, safeguarding, maintenance, and disposal of personally identifiable information (PII).'),
('003557','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to individuals regarding its activities that impact privacy, including its collection, use, sharing, safeguarding, maintenance, and disposal of personally identifiable information (PII).','TR-1.2','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective information to individuals regarding its activities that impact privacy, including its collection, use, sharing, safeguarding, maintenance, and disposal of PII. The process may include use of the SORN, PIA, or through the Privacy Act Statement on forms used to collect PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to individuals regarding its activities that impact privacy, including its collection, use, sharing, safeguarding, maintenance, and disposal of PII.'),
('003558','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to the public regarding its authority for collecting personally identifiable information (PII).','TR-1.3','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to the public regarding its authority for collecting PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to the public regarding its authority for collecting PII.'),
('003559','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to individuals regarding its authority for collecting personally identifiable information (PII).','TR-1.4','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to individuals regarding its authority for collecting PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAWIAW DoD 5400.11-R and DoDI 5400.16 to individuals regarding its authority for collecting PII.'),
('003560','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to the public regarding the choices, if any, individuals may have regarding how the organization uses personally identifiable information (PII).','TR-1.5','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to the public regarding the choices, if any, individuals may have regarding how the organization uses PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to the public regarding the choices, if any, individuals may have regarding how the organization uses PII.'),
('003561','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to individuals regarding the choices, if any, individuals may have regarding how the organization uses personally identifiable information (PII).','TR-1.6','The organization being inspected/assessed documents and implements a process to provide IAW DoD 5400.11-R and DoDI 5400.16 effective notice to individuals regarding the choices, if any, individuals may have regarding how the organization uses PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to individuals regarding the choices, if any, individuals may have regarding how the organization uses PII.'),
('003562','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to the public regarding the consequences of exercising or not exercising the choices regarding how the organization uses personally identifiable information (PII).','TR-1.7','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to the public regarding the consequences of exercising or not exercising the choices regarding how the organization uses PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to the public regarding the consequences of exercising or not exercising the choices regarding how the organization uses PII.'),
('003563','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to individuals regarding the consequences of exercising or not exercising the choices regarding how the organization uses personally identifiable information (PII).','TR-1.8','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to individuals regarding the consequences of exercising or not exercising the choices regarding how the organization uses PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to individuals regarding the consequences of exercising or not exercising the choices regarding how the organization uses PII.'),
('003564','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to the public regarding the ability of individuals to access personally identifiable information (PII).','TR-1.9','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to the public regarding the ability to access PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to the public regarding the ability to access PII.'),
('003565','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to individuals regarding the ability to access personally identifiable information (PII).','TR-1.10','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to individuals regarding the ability to access PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to individuals regarding the ability to access PII.'),
('003566','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to the public regarding the ability to have personally identifiable information (PII) amended or corrected if necessary.','TR-1.11','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to the public regarding the ability to have PII amended or corrected if necessary.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to the public regarding the ability to have PII amended or corrected if necessary.'),
('003567','draft','2013-11-08','DISA FSO','policy','The organization provides effective notice to individuals regarding the ability to have personally identifiable information (PII) amended or corrected if necessary.','TR-1.12','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to provide effective notice to individuals regarding the ability to have PII amended or corrected if necessary.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides effective notice IAW DoD 5400.11-R and DoDI 5400.16 to individuals regarding the ability to have PII amended or corrected if necessary.'),
('003568','draft','2013-11-08','DISA FSO','policy','The organization describes the personally identifiable information (PII) the organization collects.','TR-1.13','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 the PII the organization collects.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes the PII the organization collects IAW DoD 5400.11-R and DoDI 5400.16'),
('003569','draft','2013-11-08','DISA FSO','policy','The organization describes the purpose(s) for which it collects the personally identifiable information (PII).','TR-1.14','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 the purpose(s) for which it collects the PII information.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes the purpose(s) for which it collects the PII information IAW DoD 5400.11-R and DoDI 5400.16'),
('003570','draft','2013-11-08','DISA FSO','policy','The organization describes how the organization uses personally identifiable information (PII) internally.','TR-1.15','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 how the organization uses PII internally.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes how the organization uses PII internally IAW DoD 5400.11-R and DoDI 5400.16'),
('003571','draft','2013-11-08','DISA FSO','policy','The organization describes whether the organization shares personally identifiable information (PII) with external entities.','TR-1.16','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 whether the organization shares PII with external entities.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes whether the organization shares PII with external entities IAW DoD 5400.11-R and DoDI 5400.16.'),
('003572','draft','2013-11-08','DISA FSO','policy','The organization describes the categories of those external entities with whom personally identifiable information (PII) is shared.','TR-1.17','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 the categories of those external entities with whom PII is shared.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes the categories of those external entities with whom PII is shared IAW DoD 5400.11-R and DoDI 5400.16'),
('003573','draft','2013-11-08','DISA FSO','policy','The organization describes the purposes for sharing personally identifiable information (PII) with external entities.','TR-1.18','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 the purposes for sharing PII with external entities.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes the purposes for sharing PII with external entities IAW DoD 5400.11-R and DoDI 5400.16'),
('003574','draft','2013-11-08','DISA FSO','policy','The organization describes whether individuals have the ability to consent to specific uses or sharing of personally identifiable information (PII).','TR-1.19','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 whether individuals have the ability to consent to specific uses or sharing of PII.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes whether individuals have the ability to consent to specific uses or sharing of PII IAW DoD 5400.11-R and DoDI 5400.16'),
('003575','draft','2013-11-08','DISA FSO','policy','The organization describes how individuals may exercise their consent regarding specific uses or sharing of personally identifiable information (PII).','TR-1.20','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 how individuals may exercise their consent regarding specific uses or sharing of PII.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes how individuals may exercise their consent regarding specific uses or sharing of PII IAW DoD 5400.11-R and DoDI 5400.16.'),
('003576','draft','2013-11-08','DISA FSO','policy','The organization describes how individuals may obtain access to personally identifiable information (PII).','TR-1.21','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 how individuals may obtain access to PII.','The organization being inspected/assessed obtains and examines the documented description to ensure the organization being inspected/assessed describes how individuals may obtain access to PII IAW DoD 5400.11-R and DoDI 5400.16.'),
('003577','draft','2013-11-08','DISA FSO','policy','The organization describes how the personally identifiable information (PII) will be protected.','TR-1.22','The organization being inspected/assessed describes and documents IAW DoD 5400.11-R and DoDI 5400.16 how the PII will be protected.','The organization conducting the inspection/assessment obtains and examines the documented description to ensure the organization being inspected/assessed describes how the PII will be protected IAW DoD 5400.11-R and DoDI 5400.16.'),
('003578','draft','2013-11-08','DISA FSO','policy','The organization revises its public notices to reflect changes in practice or policy that affect personally identifiable information (PII), before or as soon as practicable after the change.','TR-1.23','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to revise its public notices to reflect changes in practice or policy that affect PII, before or as soon as practicable after the change.\n\nThe organization must maintain an audit trail of revisions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of revisions to ensure the organization being inspected/assessed revises its public notices, IAW DoD 5400.11-R and DoDI 5400.16, to reflect changes in practice or policy that affect PII, before or as soon as practicable after the change.'),
('003579','draft','2013-11-08','DISA FSO','policy','The organization revises its public notices to reflect changes in practice or policy that impact privacy, before or as soon as practicable after the change.','TR-1.24','The organization being inspected/assessed documents and implements a process IAW DoD 5400.11-R and DoDI 5400.16 to revise its public notices to reflect changes in practice or policy that impact privacy, before or as soon as practicable after the change.\n\nThe organization must maintain an audit trail of revisions.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of revisions to ensure the organization being inspected/assessed revises its public notices IAW DoD 5400.11-R and DoDI 5400.16 to reflect changes in practice or policy that impact privacy, before or as soon as practicable after the change.'),
('003580','draft','2013-11-08','DISA FSO','policy','The organization provides real-time notice and/or layered notice when it collects personally identifiable information (PII).','TR-1(1).1','The organization being inspected/assessed documents and implements a process to provide real-time notice and/or layered notice when it collects PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed provides real-time notice and/or layered notice when it collects PII.'),
('003581','draft','2013-11-08','DISA FSO','policy','The organization publishes System of Records Notices (SORNs) in the Federal Register, subject to required oversight processes, for systems containing personally identifiable information (PII).','TR-2.1','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to publish System of Records Notices (SORNs) in the Federal Register, subject to required oversight processes, for systems containing PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed publishes IAW DoDD 5400.11 and DoD 5400.11-R System of Records Notices (SORNs) in the Federal Register, subject to required oversight processes, for systems containing PII.'),
('003582','draft','2013-11-08','DISA FSO','policy','The organization keeps System of Records Notices (SORNs) current.','TR-2.2','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to review System of Records Notices (SORNs) every two years and to updated as necessary to keep current.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed keeps System of Records Notices (SORNs) current IAW DoDD 5400.11 and DoD 5400.11-R by reviewing the SORNs every two years and updating as necessary.'),
('003583','draft','2013-11-08','DISA FSO','policy','The organization includes Privacy Act Statements on its forms that collect personally identifiable information (PII), or on separate forms that can be retained by individuals, to provide additional formal notice to individuals from whom the information is being collected.','TR-2.3','The organization being inspected/assesse documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to include Privacy Act Statements on its forms that collect PII, or on separate forms that can be retained by individuals, to provide additional formal notice to individuals from whom the information is being collected.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed, IAW DoDD 5400.11 and DoD 5400.11-R, includes Privacy Act Statements on its forms that collect PII, or on separate forms that can be retained by individuals, to provide additional formal notice to individuals from whom the information is being collected.'),
('003584','draft','2013-11-08','DISA FSO','policy','The organization publishes System of Records Notices (SORNs) on its public website.','TR-2(1).1','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to publish their Component level System of Records Notices (SORNs) on its public website.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed publishes their Component level System of Records Notices (SORNs) on its public websites IAW DoDD 5400.11 and DoD 5400.11-R.'),
('003585','draft','2013-11-08','DISA FSO','policy','The organization ensures the public has access to information about its privacy activities.','TR-3.1','DoDD 5400.11, DoD 5400.11-R, DoDI 5400.16, publication of both Privacy Impact Assessments and System of Records Notices, as well as, if published, Service or DoD Component level privacy regulations, meet this control\'s requirement to make public information about the organizations\' privacy activities.\n\nThe organization being inspected/assessed documents any Service or Component level privacy regulations it has published.','DoDD 5400.11, DoD 5400.11-R, DoDI 5400.16, publication of both Privacy Impact Assessments and System of Records Notices, as well as, if published, Service or DoD Component level privacy regulations, meet this control\'s to make publicly accessible information about the organizations\' privacy activities.\n\nThe organization conducting the inspection/assessment obtains and examines the published Service or Component level privacy regulations to ensure the organization being inspected/assessed, has made those regulations public.'),
('003586','draft','2013-11-08','DISA FSO','policy','The organization ensures the public is able to communicate with its Senior Agency Official for Privacy (SAOP)/Chief Privacy Officer (CPO).','TR-3.2','If the DoD Component has identified a Chief Privacy Officer, the DoD Component shall provide a phone number and e-mail address on its web site to enable the public to communicate with its Chief Privacy Officer. If the DoD Component is serviced by another DoD Component\'s Chief Privacy Officer, the DoD Component will provide a phone number and e-mail address for that Officer.\n\nThe organization being inspected/assessed documents the web site on which it has published a phone number and e-mail address on its web site to enable the public to communicate with its Chief Privacy Officer.','The organization conducting the inspection/assessment obtains and examines the documented web site to ensure the organization being inspected/assessed, has provided a phone number and e-mail address that permits the public to communicate with its Chief Privacy Officer.'),
('003587','draft','2013-11-08','DISA FSO','policy','The organization ensures its privacy practices are publicly available through organizational websites or otherwise.','TR-3.3','If the DoD Component has a Component level Privacy regulation, the DoD Component shall provide public access to that regulation on the Component\'s web site.\n\nThe organization being inspected/assessed documents the web site on which it has published its Component level privacy regulation.','If the DoD Component has a Component level Privacy regulation, the DoD Component shall provide public access to that regulation on the Component\'s web site.\n\nThe organization conducting the inspection/assessment obtains and examines the documented web site to ensure the organization being inspected/assessed, has provided public access to the Component level privacy regulation.'),
('003588','draft','2013-11-08','DISA FSO','policy','The organization uses personally identifiable information (PII) internally only for the authorized purpose(s) identified in the Privacy Act and/or in public notices.','UL-1.1','The organization being inspected/assessed documents and implements a process to use personally identifiable information (PII) internally only for the authorized purpose(s) identified in the Privacy Act and/or in public notices.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed uses personally identifiable information (PII) internally only for the authorized purpose(s) identified in the Privacy Act and/or in public notices.'),
('003589','draft','2013-11-08','DISA FSO','policy','The organization shares personally identifiable information (PII) externally, only for the authorized purposes identified in the Privacy Act and/or described in its notice(s) or for a purpose that is compatible with those purposes.','UL-2.1','The organization being inspected/assessed documents and implements a process to share IAW DoDD 5400.11 and DoD 5400.11-R, PII externally, only for the authorized purposes or for a purpose that is compatible with those purposes. Planned use of PII must be identified and documented as an authorized purposes in the corresponding SORN, PIA, security plan, or other system-specific document.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed shares IAW DoD 5400.11, PII externally, only for the authorized purposes or for a purpose that is compatible with those purposes. Planned use of PII must be identified and documented as an authorized purposes in the corresponding SORN, PIA, security plan, or other system-specific document.'),
('003590','draft','2013-11-08','DISA FSO','policy','The organization, where appropriate, enters into Memoranda of Understanding, Memoranda of Agreement, Letters of Intent, Computer Matching Agreements, or similar agreements, with third parties that specifically describe the personally identifiable information (PII) covered.','UL-2.2','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to enter into Memoranda of Understanding, Memoranda of Agreement, Letters of Intent, Computer Matching Agreements, or similar agreements, where appropriate, with third parties that specifically describe the PII covered.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed, IAW DoDD 5400.11 and DoD 5400.11-R, enters into Memoranda of Understanding, Memoranda of Agreement, Letters of Intent, Computer Matching Agreements, or similar agreements, where appropriate, with third parties that specifically describe the PII covered.'),
('003591','draft','2013-11-08','DISA FSO','policy','The organization, where appropriate, enters into Memoranda of Understanding, Memoranda of Agreement, Letters of Intent, Computer Matching Agreements, or similar agreements, with third parties that specifically enumerate the purposes for which the personally identifiable information (PII) may be used.','UL-2.3','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to enter into Memoranda of Understanding, Memoranda of Agreement, Letters of Intent, Computer Matching Agreements, or similar agreements, where appropriate, with third parties that specifically enumerate the purposes for which the PII may be used.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed, IAW DoDD 5400.11 and DoD 5400.11-R, enters into Memoranda of Understanding, Memoranda of Agreement, Letters of Intent, Computer Matching Agreements, or similar agreements, where appropriate, with third parties that specifically enumerate the purposes for which the PII may be used.'),
('003592','draft','2013-11-08','DISA FSO','policy','The organization monitors its staff on the authorized sharing of personally identifiable information (PII) with third parties.','UL-2.4','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to monitor its staff on the authorized sharing of PII with third parties.\n\nThe organization must maintain an audit trail of monitoring.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the audit trail of monitoring to ensure the organization being inspected/assessed monitors its staff, IAW DoDD 5400.11 and DoD 5400.11-R, on the authorized sharing of PII with third parties.'),
('003593','draft','2013-11-08','DISA FSO','policy','The organization audits its staff on the authorized sharing of personally identifiable information (PII) with third parties.','UL-2.5','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R, to audit its staff on the authorized sharing of PII with third parties.\n\nThe organization must maintain records of audits.','The organization conducting the inspection/assessment obtains and examines the documented process as well as the records of audits to ensure the organization being inspected/assessed audits its staff, IAW DoDD 5400.11 and DoD 5400.11-R, on the authorized sharing of PII with third parties.'),
('003594','draft','2013-11-08','DISA FSO','policy','The organization trains its staff on the authorized sharing of personally identifiable information (PII) with third parties.','UL-2.6','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to train its staff on the authorized sharing of PII with third parties.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed trains its staff, IAW DoDD 5400.11 and DoD 5400.11-R, on the authorized sharing of PII with third parties.'),
('003595','draft','2013-11-08','DISA FSO','policy','The organization trains its staff on the consequences of unauthorized use or sharing of personally identifiable information (PII).','UL-2.7','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to train its staff on the consequences of unauthorized use or sharing of PII.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed trains its staff, IAW DoDD 5400.11 and DoD 5400.11-R, on the consequences of unauthorized use or sharing of PII.'),
('003596','draft','2013-11-08','DISA FSO','policy','The organization evaluates any proposed new instances of sharing personally identifiable information (PII) with third parties to assess whether the sharing is authorized.','UL-2.8','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to evaluate any proposed new instances of sharing PII with third parties to assess whether the sharing is authorized.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed evaluates IAW DoDD 5400.11 and DoD 5400.11-R any proposed new instances of sharing PII with third parties to assess whether the sharing is authorized.'),
('003597','draft','2013-11-08','DISA FSO','policy','The organization evaluates any proposed new instances of sharing personally identifiable information (PII) with third parties to assess whether additional or new public notice is required.','UL-2.9','The organization being inspected/assessed documents and implements a process IAW DoDD 5400.11 and DoD 5400.11-R to evaluate any proposed new instances of sharing PII with third parties to assess whether additional or new public notice is required.','The organization conducting the inspection/assessment obtains and examines the documented process to ensure the organization being inspected/assessed evaluates IAW DoDD 5400.11 and DoD 5400.11-R any proposed new instances of sharing PII with third parties to assess whether additional or new public notice is required.'),
('003599','draft','2016-06-07','DISA FSO','policy','The organization defines the individuals or information systems to be the only recipients of organization-defined information, information system components, or devices, by employing organization-defined security safeguards.','SC-37(1).1','The organization being inspected/assessed defines and documents the individuals or information systems that are the only recipients of organization-defined information, information system components, or devices, and employed organization-defined security safeguards. DoD has determined the individuals or information systems are not appropriate to define at the Enterprise level.','The organization conducting the inspection/assessment obtains and examines the documented information, information system components, or devices to ensure the organization being inspected/assessed defines the individuals or information systems authorized to be recipients of organization-defined information, information system components, or devices, and has employed organization-defined security safeguards. DoD has determined the individuals or information systems are not appropriate to define at the Enterprise level.');
/*!40000 ALTER TABLE `cci` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `cci_reference_map`
--
LOCK TABLES `cci_reference_map` WRITE;
/*!40000 ALTER TABLE `cci_reference_map` DISABLE KEYS */;
INSERT INTO `cci_reference_map` VALUES (21392,'001545','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b 1','AC-1b.1.','AC-1'),
(21393,'001546','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b 2','AC-1b.2.','AC-1'),
(21394,'000001','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1','AC-1a.1.','AC-1'),
(21395,'000004','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 2','AC-1a.2.','AC-1'),
(21396,'000002','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1','AC-1a.1.','AC-1'),
(21397,'000003','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b 1','AC-1b.1.','AC-1'),
(21398,'000005','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 2','AC-1a.2.','AC-1'),
(21399,'000006','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b 2','AC-1b.2.','AC-1'),
(21400,'001547','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 j','AC-2j.','AC-2'),
(21401,'000008','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 c','AC-2c.','AC-2'),
(21402,'000010','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 e','AC-2e.','AC-2'),
(21403,'000011','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f.','AC-2'),
(21404,'000012','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 j','AC-2j.','AC-2'),
(21405,'000015','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (1)','AC-2 (1)','AC-2 (1)'),
(21406,'000016','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2 (2)','AC-2 (2)'),
(21407,'000017','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3)','AC-2 (3)','AC-2 (3)'),
(21408,'000018','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21409,'000019','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (5)','AC-2 (5)','AC-2 (5)'),
(21410,'001361','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2 (2)','AC-2 (2)'),
(21411,'001365','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2 (2)','AC-2 (2)'),
(21412,'000217','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3)','AC-2 (3)','AC-2 (3)'),
(21413,'001403','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21414,'001404','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21415,'001405','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21416,'001406','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (5)','AC-2 (5)','AC-2 (5)'),
(21417,'001407','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (a)','AC-2 (7)(a)','AC-2 (7)'),
(21418,'001358','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (a)','AC-2 (7)(a)','AC-2 (7)'),
(21419,'001360','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (b)','AC-2 (7)(b)','AC-2 (7)'),
(21420,'001682','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2 (2)','AC-2 (2)'),
(21421,'001683','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21422,'001684','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21423,'001685','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21424,'001686','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(21425,'001548','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
(21426,'001549','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
(21427,'001550','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
(21428,'001551','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
(21429,'001553','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (10)','AC-4 (10)','AC-4 (10)'),
(21430,'001554','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (11)','AC-4 (11)','AC-4 (11)'),
(21431,'000026','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (2)','AC-4 (2)','AC-4 (2)'),
(21432,'000027','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (3)','AC-4 (3)','AC-4 (3)'),
(21433,'000028','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (4)','AC-4 (4)','AC-4 (4)'),
(21434,'000029','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (5)','AC-4 (5)','AC-4 (5)'),
(21435,'000030','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (6)','AC-4 (6)','AC-4 (6)'),
(21436,'000031','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (7)','AC-4 (7)','AC-4 (7)'),
(21437,'000032','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8)','AC-4 (8)','AC-4 (8)'),
(21438,'000034','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (10)','AC-4 (10)','AC-4 (10)'),
(21439,'000035','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (11)','AC-4 (11)','AC-4 (11)'),
(21440,'000219','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (13)','AC-4 (13)','AC-4 (13)'),
(21441,'001414','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
(21442,'001415','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (5)','AC-4 (5)','AC-4 (5)'),
(21443,'001416','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (7)','AC-4 (7)','AC-4 (7)'),
(21444,'001417','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8)','AC-4 (8)','AC-4 (8)'),
(21445,'001368','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
(21446,'001371','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (14)','AC-4 (14)','AC-4 (14)'),
(21447,'001372','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (14)','AC-4 (14)','AC-4 (14)'),
(21448,'001373','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4 (15)','AC-4 (15)'),
(21449,'001374','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4 (15)','AC-4 (15)'),
(21450,'001558','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1)','AC-6 (1)','AC-6 (1)'),
(21451,'000039','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (2)','AC-6 (2)','AC-6 (2)'),
(21452,'000041','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6 (3)','AC-6 (3)'),
(21453,'000042','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6 (3)','AC-6 (3)'),
(21454,'000225','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6','AC-6','AC-6'),
(21455,'001419','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (2)','AC-6 (2)','AC-6 (2)'),
(21456,'001420','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6 (3)','AC-6 (3)'),
(21457,'001422','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (6)','AC-6 (6)','AC-6 (6)'),
(21458,'001559','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16 (2)','AC-16 (2)'),
(21459,'001560','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(21460,'001424','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16 (1)','AC-16 (1)'),
(21461,'001425','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16 (2)','AC-16 (2)'),
(21462,'001428','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16 (5)','AC-16 (5)'),
(21463,'001429','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16 (5)','AC-16 (5)'),
(21464,'001430','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16 (5)','AC-16 (5)'),
(21465,'001561','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (3)','AC-17 (3)','AC-17 (3)'),
(21466,'000063','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a.','AC-17'),
(21467,'000065','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 b','AC-17b.','AC-17'),
(21468,'000067','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (1)','AC-17 (1)','AC-17 (1)'),
(21469,'000068','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (2)','AC-17 (2)','AC-17 (2)'),
(21470,'000069','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (3)','AC-17 (3)','AC-17 (3)'),
(21471,'000070','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17 (4)(a)','AC-17 (4)'),
(21472,'000072','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (6)','AC-17 (6)','AC-17 (6)'),
(21473,'001453','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (2)','AC-17 (2)','AC-17 (2)'),
(21474,'001438','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 a','AC-18a.','AC-18'),
(21475,'001439','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 a','AC-18a.','AC-18'),
(21476,'001441','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 b','AC-18b.','AC-18'),
(21477,'001443','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (1)','AC-18 (1)','AC-18 (1)'),
(21478,'001444','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (1)','AC-18 (1)','AC-18 (1)'),
(21479,'001449','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (3)','AC-18 (3)','AC-18 (3)'),
(21480,'001451','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (5)','AC-18 (5)','AC-18 (5)'),
(21481,'001564','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b 1','AT-1b.1.','AT-1'),
(21482,'001565','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b 2','AT-1b.2.','AT-1'),
(21483,'000100','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1','AT-1a.1.','AT-1'),
(21484,'000101','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1','AT-1a.1.','AT-1'),
(21485,'000102','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b 1','AT-1b.1.','AT-1'),
(21486,'000103','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 2','AT-1a.2.','AT-1'),
(21487,'000104','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 2','AT-1a.2.','AT-1'),
(21488,'000105','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b 2','AT-1b.2.','AT-1'),
(21489,'001566','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3 (2)','AT-3 (2)'),
(21490,'001567','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3 (2)','AT-3 (2)'),
(21491,'001568','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3 (2)','AT-3 (2)'),
(21492,'000108','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 a','AT-3a.','AT-3'),
(21493,'000109','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 b','AT-3b.','AT-3'),
(21494,'000110','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 c','AT-3c.','AT-3'),
(21495,'000111','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 c','AT-3c.','AT-3'),
(21496,'001481','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3 (1)','AT-3 (1)'),
(21497,'001482','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3 (1)','AT-3 (1)'),
(21498,'001483','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3 (1)','AT-3 (1)'),
(21499,'001569','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 1','AU-1b.1.','AU-1'),
(21500,'001570','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 2','AU-1b.2.','AU-1'),
(21501,'000117','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1','AU-1a.1.','AU-1'),
(21502,'000119','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 1','AU-1b.1.','AU-1'),
(21503,'000120','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a.2.','AU-1'),
(21504,'000122','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 2','AU-1b.2.','AU-1'),
(21505,'001571','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 a','AU-2a.','AU-2'),
(21506,'000123','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 a','AU-2a.','AU-2'),
(21507,'000124','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 b','AU-2b.','AU-2'),
(21508,'000125','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 c','AU-2c.','AU-2'),
(21509,'000126','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 d','AU-2d.','AU-2'),
(21510,'000127','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 (3)','AU-2 (3)','AU-2 (3)'),
(21511,'001484','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 d','AU-2d.','AU-2'),
(21512,'001485','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 d','AU-2d.','AU-2'),
(21513,'001486','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 (3)','AU-2 (3)','AU-2 (3)'),
(21514,'001572','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 a','AU-5a.','AU-5'),
(21515,'001573','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (3)','AU-5 (3)','AU-5 (3)'),
(21516,'000139','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 a','AU-5a.','AU-5'),
(21517,'000140','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 b','AU-5b.','AU-5'),
(21518,'000145','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (3)','AU-5 (3)','AU-5 (3)'),
(21519,'000147','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5 (2)','AU-5 (2)'),
(21520,'001490','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 b','AU-5b.','AU-5'),
(21521,'001575','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (2)','AU-9 (2)','AU-9 (2)'),
(21522,'000162','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9','AU-9','AU-9'),
(21523,'000163','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9','AU-9','AU-9'),
(21524,'000164','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9','AU-9','AU-9'),
(21525,'000165','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (1)','AU-9 (1)','AU-9 (1)'),
(21526,'001348','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (2)','AU-9 (2)','AU-9 (2)'),
(21527,'001349','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (2)','AU-9 (2)','AU-9 (2)'),
(21528,'001350','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (3)','AU-9 (3)','AU-9 (3)'),
(21529,'001351','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (4)','AU-9 (4)','AU-9 (4)'),
(21530,'001493','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9','AU-9','AU-9'),
(21531,'001494','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9','AU-9','AU-9'),
(21532,'001495','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9','AU-9','AU-9'),
(21533,'001496','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (3)','AU-9 (3)','AU-9 (3)'),
(21534,'001576','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12 (1)','AU-12 (1)'),
(21535,'001577','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12 (1)','AU-12 (1)'),
(21536,'000169','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 a','AU-12a.','AU-12'),
(21537,'000171','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 b','AU-12b.','AU-12'),
(21538,'000172','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 c','AU-12c.','AU-12'),
(21539,'000173','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12 (1)','AU-12 (1)'),
(21540,'000174','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12 (1)','AU-12 (1)'),
(21541,'001459','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 a','AU-12a.','AU-12'),
(21542,'001353','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (2)','AU-12 (2)','AU-12 (2)'),
(21543,'001578','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b 2','CA-1b.2.','CA-1'),
(21544,'000238','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b 1','CA-1b.1.','CA-1'),
(21545,'000239','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1','CA-1a.1.','CA-1'),
(21546,'000240','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1','CA-1a.1.','CA-1'),
(21547,'000240','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1','CA-1a.1.','CA-1'),
(21548,'000241','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b 1','CA-1b.1.','CA-1'),
(21549,'000242','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a.2.','CA-1'),
(21550,'000243','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a.2.','CA-1'),
(21551,'000244','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b 2','CA-1b.2.','CA-1'),
(21552,'000245','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 a','CA-2a.','CA-2'),
(21553,'000246','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 a 1','CA-2a.1.','CA-2'),
(21554,'000247','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 a 2','CA-2a.2.','CA-2'),
(21555,'000248','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 a 3','CA-2a.3.','CA-2'),
(21556,'000251','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 b','CA-2b.','CA-2'),
(21557,'000252','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 b','CA-2b.','CA-2'),
(21558,'000253','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 c','CA-2c.','CA-2'),
(21559,'000254','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 d','CA-2d.','CA-2'),
(21560,'000255','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (1)','CA-2 (1)','CA-2 (1)'),
(21561,'000256','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2 (2)','CA-2 (2)'),
(21562,'000257','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 a','CA-3a.','CA-3'),
(21563,'000258','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 b','CA-3b.','CA-3'),
(21564,'000259','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 b','CA-3b.','CA-3'),
(21565,'000260','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 b','CA-3b.','CA-3'),
(21566,'000262','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (1)','CA-3 (1)','CA-3 (1)'),
(21567,'000263','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (2)','CA-3 (2)','CA-3 (2)'),
(21568,'001581','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g.','CA-7'),
(21569,'001582','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2 (2)','CA-2 (2)'),
(21570,'001583','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2 (2)','CA-2 (2)'),
(21571,'000274','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7','CA-7','CA-7'),
(21572,'000279','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 c','CA-7c.','CA-7'),
(21573,'000280','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g.','CA-7'),
(21574,'000281','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g.','CA-7'),
(21575,'000282','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (1)','CA-7 (1)','CA-7 (1)'),
(21576,'001681','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2 (2)','CA-2 (2)'),
(21577,'001584','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b 2','CM-1b.2.','CM-1'),
(21578,'000286','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b 1','CM-1b.1.','CM-1'),
(21579,'000287','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1','CM-1a.1.','CM-1'),
(21580,'000289','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b 1','CM-1b.1.','CM-1'),
(21581,'000290','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a.2.','CM-1'),
(21582,'000292','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b 2','CM-1b.2.','CM-1'),
(21583,'001585','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (1) (b)','CM-2 (1)(b)','CM-2 (1)'),
(21584,'000293','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2','CM-2','CM-2'),
(21585,'000294','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2','CM-2','CM-2'),
(21586,'000295','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2','CM-2','CM-2'),
(21587,'000296','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (1) (a)','CM-2 (1)(a)','CM-2 (1)'),
(21588,'000297','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (1) (b)','CM-2 (1)(b)','CM-2 (1)'),
(21589,'000298','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (1) (c)','CM-2 (1)(c)','CM-2 (1)'),
(21590,'000299','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (1) (c)','CM-2 (1)(c)','CM-2 (1)'),
(21591,'000300','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2 (2)','CM-2 (2)'),
(21592,'000301','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2 (2)','CM-2 (2)'),
(21593,'000302','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2 (2)','CM-2 (2)'),
(21594,'000303','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2 (2)','CM-2 (2)'),
(21595,'000304','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (3)','CM-2 (3)','CM-2 (3)'),
(21596,'000311','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (6)','CM-2 (6)','CM-2 (6)'),
(21597,'000312','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (6)','CM-2 (6)','CM-2 (6)'),
(21598,'001497','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (1) (a)','CM-2 (1)(a)','CM-2 (1)'),
(21599,'001586','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g.','CM-3'),
(21600,'001586','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3 (4)','CM-3 (4)'),
(21601,'000313','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 a','CM-3a.','CM-3'),
(21602,'000314','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 b','CM-3b.','CM-3'),
(21603,'000316','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 e','CM-3e.','CM-3'),
(21604,'000318','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 f','CM-3f.','CM-3'),
(21605,'000319','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g.','CM-3'),
(21606,'000320','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g.','CM-3'),
(21607,'000321','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g.','CM-3'),
(21608,'000322','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (a)','CM-3 (1)(a)','CM-3 (1)'),
(21609,'000323','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (b)','CM-3 (1)(b)','CM-3 (1)'),
(21610,'000324','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (c)','CM-3 (1)(c)','CM-3 (1)'),
(21611,'000325','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (d)','CM-3 (1)(d)','CM-3 (1)'),
(21612,'000326','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (e)','CM-3 (1)(e)','CM-3 (1)'),
(21613,'000327','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (2)','CM-3 (2)','CM-3 (2)'),
(21614,'000328','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (2)','CM-3 (2)','CM-3 (2)'),
(21615,'000329','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (2)','CM-3 (2)','CM-3 (2)'),
(21616,'000330','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (3)','CM-3 (3)','CM-3 (3)'),
(21617,'000331','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (3)','CM-3 (3)','CM-3 (3)'),
(21618,'000332','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3 (4)','CM-3 (4)'),
(21619,'001498','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (c)','CM-3 (1)(c)','CM-3 (1)'),
(21620,'000333','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-4','CM-4','CM-4'),
(21621,'000335','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4 (2)','CM-4 (2)'),
(21622,'000336','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4 (2)','CM-4 (2)'),
(21623,'000337','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4 (2)','CM-4 (2)'),
(21624,'001588','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 a','CM-6a.','CM-6'),
(21625,'000363','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 a','CM-6a.','CM-6'),
(21626,'000364','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 a','CM-6a.','CM-6'),
(21627,'000365','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 a','CM-6a.','CM-6'),
(21628,'000366','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 b','CM-6b.','CM-6'),
(21629,'000367','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c.','CM-6'),
(21630,'000368','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c.','CM-6'),
(21631,'000369','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c.','CM-6'),
(21632,'000370','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6 (1)','CM-6 (1)'),
(21633,'000371','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6 (1)','CM-6 (1)'),
(21634,'000372','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6 (1)','CM-6 (1)'),
(21635,'001502','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 d','CM-6d.','CM-6'),
(21636,'001503','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 d','CM-6d.','CM-6'),
(21637,'001592','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (2)','CM-7 (2)','CM-7 (2)'),
(21638,'000380','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 b','CM-7b.','CM-7'),
(21639,'000381','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 a','CM-7a.','CM-7'),
(21640,'000382','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 b','CM-7b.','CM-7'),
(21641,'000384','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (a)','CM-7 (1)(a)','CM-7 (1)'),
(21642,'000387','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (3)','CM-7 (3)','CM-7 (3)'),
(21643,'000388','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (3)','CM-7 (3)','CM-7 (3)'),
(21644,'001596','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b 2','CP-1b.2.','CP-1'),
(21645,'001597','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 2','CP-1a.2.','CP-1'),
(21646,'001598','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b 2','CP-1b.2.','CP-1'),
(21647,'000437','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b 1','CP-1b.1.','CP-1'),
(21648,'000438','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1','CP-1a.1.','CP-1'),
(21649,'000439','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1','CP-1a.1.','CP-1'),
(21650,'000440','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b 1','CP-1b.1.','CP-1'),
(21651,'000441','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 2','CP-1a.2.','CP-1'),
(21652,'001599','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2 (5)','CP-2 (5)'),
(21653,'001600','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2 (5)','CP-2 (5)'),
(21654,'001601','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2 (6)','CP-2 (6)'),
(21655,'001602','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2 (6)','CP-2 (6)'),
(21656,'000443','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 1','CP-2a.1.','CP-2'),
(21657,'000444','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 1','CP-2a.1.','CP-2'),
(21658,'000445','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 1','CP-2a.1.','CP-2'),
(21659,'000446','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 2','CP-2a.2.','CP-2'),
(21660,'000447','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 2','CP-2a.2.','CP-2'),
(21661,'000448','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 2','CP-2a.2.','CP-2'),
(21662,'000449','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 3','CP-2a.3.','CP-2'),
(21663,'000450','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a.4.','CP-2'),
(21664,'000451','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a.4.','CP-2'),
(21665,'000452','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a.4.','CP-2'),
(21666,'000453','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a.4.','CP-2'),
(21667,'000454','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a.4.','CP-2'),
(21668,'000455','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a.4.','CP-2'),
(21669,'000456','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 5','CP-2a.5.','CP-2'),
(21670,'000457','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 6','CP-2a.6.','CP-2'),
(21671,'000458','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 b','CP-2b.','CP-2'),
(21672,'000459','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 b','CP-2b.','CP-2'),
(21673,'000460','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 c','CP-2c.','CP-2'),
(21674,'000461','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 d','CP-2d.','CP-2'),
(21675,'000462','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 d','CP-2d.','CP-2'),
(21676,'000463','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e.','CP-2'),
(21677,'000464','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e.','CP-2'),
(21678,'000465','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e.','CP-2'),
(21679,'000466','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e.','CP-2'),
(21680,'000468','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 f','CP-2f.','CP-2'),
(21681,'000469','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (1)','CP-2 (1)','CP-2 (1)'),
(21682,'000470','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (2)','CP-2 (2)','CP-2 (2)'),
(21683,'000471','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (2)','CP-2 (2)','CP-2 (2)'),
(21684,'000472','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (2)','CP-2 (2)','CP-2 (2)'),
(21685,'000473','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2 (3)','CP-2 (3)'),
(21686,'000474','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2 (3)','CP-2 (3)'),
(21687,'000475','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2 (3)','CP-2 (3)'),
(21688,'000476','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2 (3)','CP-2 (3)'),
(21689,'000477','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (4)','CP-2 (4)','CP-2 (4)'),
(21690,'000478','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (4)','CP-2 (4)','CP-2 (4)'),
(21691,'000479','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (4)','CP-2 (4)','CP-2 (4)'),
(21692,'000480','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (4)','CP-2 (4)','CP-2 (4)'),
(21693,'000481','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2 (5)','CP-2 (5)'),
(21694,'000482','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2 (5)','CP-2 (5)'),
(21695,'000483','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2 (6)','CP-2 (6)'),
(21696,'000484','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2 (6)','CP-2 (6)'),
(21697,'001604','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (3)','CP-6 (3)','CP-6 (3)'),
(21698,'000505','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 a','CP-6a.','CP-6'),
(21699,'000507','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (1)','CP-6 (1)','CP-6 (1)'),
(21700,'000508','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (2)','CP-6 (2)','CP-6 (2)'),
(21701,'000509','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (3)','CP-6 (3)','CP-6 (3)'),
(21702,'001606','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (2)','CP-7 (2)','CP-7 (2)'),
(21703,'000510','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a.','CP-7'),
(21704,'000513','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a.','CP-7'),
(21705,'000514','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a.','CP-7'),
(21706,'000515','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 b','CP-7b.','CP-7'),
(21707,'000516','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (1)','CP-7 (1)','CP-7 (1)'),
(21708,'000517','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (2)','CP-7 (2)','CP-7 (2)'),
(21709,'000518','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (3)','CP-7 (3)','CP-7 (3)'),
(21710,'000519','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (4)','CP-7 (4)','CP-7 (4)'),
(21711,'000520','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (4)','CP-7 (4)','CP-7 (4)'),
(21712,'000521','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 c','CP-7c.','CP-7'),
(21713,'000522','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
(21714,'000523','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
(21715,'000524','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
(21716,'000525','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
(21717,'000526','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (a)','CP-8 (1)(a)','CP-8 (1)'),
(21718,'000527','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (a)','CP-8 (1)(a)','CP-8 (1)'),
(21719,'000528','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (b)','CP-8 (1)(b)','CP-8 (1)'),
(21720,'000529','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (b)','CP-8 (1)(b)','CP-8 (1)'),
(21721,'000530','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (2)','CP-8 (2)','CP-8 (2)'),
(21722,'000531','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (3)','CP-8 (3)','CP-8 (3)'),
(21723,'000532','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (a)','CP-8 (4)(a)','CP-8 (4)'),
(21724,'000533','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (a)','CP-8 (4)(a)','CP-8 (4)'),
(21725,'001609','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (6)','CP-9 (6)','CP-9 (6)'),
(21726,'000534','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (a)','CP-9(a)','CP-9'),
(21727,'000535','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (a)','CP-9(a)','CP-9'),
(21728,'000536','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (b)','CP-9(b)','CP-9'),
(21729,'000537','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (b)','CP-9(b)','CP-9'),
(21730,'000538','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (c) ','CP-9(c)','CP-9'),
(21731,'000539','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (c) ','CP-9(c)','CP-9'),
(21732,'000540','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (d)','CP-9(d)','CP-9'),
(21733,'000541','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (1)','CP-9 (1)','CP-9 (1)'),
(21734,'000542','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (1)','CP-9 (1)','CP-9 (1)'),
(21735,'000543','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (2)','CP-9 (2)','CP-9 (2)'),
(21736,'000547','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (5)','CP-9 (5)','CP-9 (5)'),
(21737,'000548','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (5)','CP-9 (5)','CP-9 (5)'),
(21738,'000549','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (6)','CP-9 (6)','CP-9 (6)'),
(21739,'001610','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 g','IA-5g.','IA-5'),
(21740,'001611','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21741,'001612','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21742,'001613','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21743,'001614','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21744,'001615','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (b)','IA-5 (1)(b)','IA-5 (1)'),
(21745,'001616','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (d)','IA-5 (1)(d)','IA-5 (1)'),
(21746,'001617','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (d)','IA-5 (1)(d)','IA-5 (1)'),
(21747,'001618','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (e)','IA-5 (1)(e)','IA-5 (1)'),
(21748,'001619','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21749,'001621','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (8)','IA-5 (8)','IA-5 (8)'),
(21750,'000176','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 b','IA-5b.','IA-5'),
(21751,'000179','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 f','IA-5f.','IA-5'),
(21752,'000180','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 f','IA-5f.','IA-5'),
(21753,'000181','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 f','IA-5f.','IA-5'),
(21754,'000182','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 g','IA-5g.','IA-5'),
(21755,'000183','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 h','IA-5h.','IA-5'),
(21756,'000184','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 i','IA-5i.','IA-5'),
(21757,'000185','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (a)','IA-5 (2)(a)','IA-5 (2)'),
(21758,'000186','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (b)','IA-5 (2)(b)','IA-5 (2)'),
(21759,'000187','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (c)','IA-5 (2)(c)','IA-5 (2)'),
(21760,'000201','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (6)','IA-5 (6)','IA-5 (6)'),
(21761,'000202','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (7)','IA-5 (7)','IA-5 (7)'),
(21762,'000204','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (8)','IA-5 (8)','IA-5 (8)'),
(21763,'000192','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21764,'000193','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21765,'000194','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21766,'000195','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (b)','IA-5 (1)(b)','IA-5 (1)'),
(21767,'000196','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (c)','IA-5 (1)(c)','IA-5 (1)'),
(21768,'000197','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (c)','IA-5 (1)(c)','IA-5 (1)'),
(21769,'000198','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (d)','IA-5 (1)(d)','IA-5 (1)'),
(21770,'000199','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (d)','IA-5 (1)(d)','IA-5 (1)'),
(21771,'000200','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (e)','IA-5 (1)(e)','IA-5 (1)'),
(21772,'000203','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (7)','IA-5 (7)','IA-5 (7)'),
(21773,'000205','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5 (1)(a)','IA-5 (1)'),
(21774,'001544','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 c','IA-5c.','IA-5'),
(21775,'000813','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a','IR-2a.','IR-2'),
(21776,'000814','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 c','IR-2c.','IR-2'),
(21777,'000815','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 c','IR-2c.','IR-2'),
(21778,'000816','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 (1)','IR-2 (1)','IR-2 (1)'),
(21779,'000817','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 (2)','IR-2 (2)','IR-2 (2)'),
(21780,'001624','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
(21781,'000818','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
(21782,'000819','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
(21783,'000820','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
(21784,'000821','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (1)','IR-3 (1)','IR-3 (1)'),
(21785,'001625','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 c','IR-4c.','IR-4'),
(21786,'000822','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 a','IR-4a.','IR-4'),
(21787,'000823','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 b','IR-4b.','IR-4'),
(21788,'000824','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 c','IR-4c.','IR-4'),
(21789,'000825','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (1)','IR-4 (1)','IR-4 (1)'),
(21790,'000826','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (2)','IR-4 (2)','IR-4 (2)'),
(21791,'000827','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (3)','IR-4 (3)','IR-4 (3)'),
(21792,'000828','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (3)','IR-4 (3)','IR-4 (3)'),
(21793,'000829','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (4)','IR-4 (4)','IR-4 (4)'),
(21794,'000830','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (5)','IR-4 (5)','IR-4 (5)'),
(21795,'000831','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (5)','IR-4 (5)','IR-4 (5)'),
(21796,'001626','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5 (1)','IR-5 (1)'),
(21797,'001627','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5 (1)','IR-5 (1)'),
(21798,'000832','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-5','IR-5','IR-5'),
(21799,'000833','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5 (1)','IR-5 (1)'),
(21800,'001628','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b 2','MA-1b.2.','MA-1'),
(21801,'000854','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b 1','MA-1b.1.','MA-1'),
(21802,'000855','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 2','MA-1a.2.','MA-1'),
(21803,'000856','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 2','MA-1a.2.','MA-1'),
(21804,'000857','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b 2','MA-1b.2.','MA-1'),
(21805,'000851','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b 1','MA-1b.1.','MA-1'),
(21806,'000852','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1','MA-1a.1.','MA-1'),
(21807,'000853','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1','MA-1a.1.','MA-1'),
(21808,'000859','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 b','MA-2b.','MA-2'),
(21809,'000860','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 c','MA-2c.','MA-2'),
(21810,'000861','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 d','MA-2d.','MA-2'),
(21811,'000862','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 e','MA-2e.','MA-2'),
(21812,'001631','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (3) (b)','MA-4 (3)(b)','MA-4 (3)'),
(21813,'001632','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (b)','MA-4 (4)(b)','MA-4 (4)'),
(21814,'000873','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 a','MA-4a.','MA-4'),
(21815,'000874','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 a','MA-4a.','MA-4'),
(21816,'000876','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 b','MA-4b.','MA-4'),
(21817,'000877','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 c','MA-4c.','MA-4'),
(21818,'000878','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 d','MA-4d.','MA-4'),
(21819,'000879','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 e','MA-4e.','MA-4'),
(21820,'000881','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (2)','MA-4 (2)','MA-4 (2)'),
(21821,'000882','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (3) (a)','MA-4 (3)(a)','MA-4 (3)'),
(21822,'000883','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (3) (b)','MA-4 (3)(b)','MA-4 (3)'),
(21823,'000884','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (a)','MA-4 (4)(a)','MA-4 (4)'),
(21824,'000886','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (b)','MA-4 (5)(b)','MA-4 (5)'),
(21825,'000887','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (a)','MA-4 (5)(a)','MA-4 (5)'),
(21826,'001010','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 a','MP-3a.','MP-3'),
(21827,'001011','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 b','MP-3b.','MP-3'),
(21828,'001012','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 b','MP-3b.','MP-3'),
(21829,'001013','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 b','MP-3b.','MP-3'),
(21830,'001635','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 d','PE-2d.','PE-2'),
(21831,'000912','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 a','PE-2a.','PE-2'),
(21832,'000913','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 b','PE-2b.','PE-2'),
(21833,'000914','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 c','PE-2c.','PE-2'),
(21834,'000915','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 c','PE-2c.','PE-2'),
(21835,'000916','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (1)','PE-2 (1)','PE-2 (1)'),
(21836,'000917','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (2)','PE-2 (2)','PE-2 (2)'),
(21837,'001636','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 b 1','PL-1b.1.','PL-1'),
(21838,'001637','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 b 1','PL-1b.1.','PL-1'),
(21839,'001638','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 b 2','PL-1b.2.','PL-1'),
(21840,'000563','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1','PL-1a.1.','PL-1'),
(21841,'000564','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1','PL-1a.1.','PL-1'),
(21842,'000566','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 2','PL-1a.2.','PL-1'),
(21843,'000567','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 2','PL-1a.2.','PL-1'),
(21844,'000568','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 b 2','PL-1b.2.','PL-1'),
(21845,'001639','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a.','PL-4'),
(21846,'000592','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a.','PL-4'),
(21847,'000593','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 b','PL-4b.','PL-4'),
(21848,'000594','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 (1)','PL-4 (1)','PL-4 (1)'),
(21849,'000595','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 (1)','PL-4 (1)','PL-4 (1)'),
(21850,'001640','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-8','PM-8','PM-8'),
(21851,'000216','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-8','PM-8','PM-8'),
(21852,'001641','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a.','RA-5'),
(21853,'001643','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a.','RA-5'),
(21854,'001645','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (5)','RA-5 (5)','RA-5 (5)'),
(21855,'001054','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a.','RA-5'),
(21856,'001055','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a.','RA-5'),
(21857,'001056','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a.','RA-5'),
(21858,'001057','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 b','RA-5b.','RA-5'),
(21859,'001058','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 c','RA-5c.','RA-5'),
(21860,'001059','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 d','RA-5d.','RA-5'),
(21861,'001060','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 d','RA-5d.','RA-5'),
(21862,'001061','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 e','RA-5e.','RA-5'),
(21863,'001062','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (1)','RA-5 (1)','RA-5 (1)'),
(21864,'001063','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (2)','RA-5 (2)','RA-5 (2)'),
(21865,'001064','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (2)','RA-5 (2)','RA-5 (2)'),
(21866,'001066','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (4)','RA-5 (4)','RA-5 (4)'),
(21867,'001067','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (5)','RA-5 (5)','RA-5 (5)'),
(21868,'001068','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (6)','RA-5 (6)','RA-5 (6)'),
(21869,'001071','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (8)','RA-5 (8)','RA-5 (8)'),
(21870,'001642','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 b','RA-3b.','RA-3'),
(21871,'001048','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 a','RA-3a.','RA-3'),
(21872,'001049','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 b','RA-3b.','RA-3'),
(21873,'001050','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 c','RA-3c.','RA-3'),
(21874,'001051','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 c','RA-3c.','RA-3'),
(21875,'001052','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 e','RA-3e.','RA-3'),
(21876,'001053','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 e','RA-3e.','RA-3'),
(21877,'000610','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 b','SA-2b.','SA-2'),
(21878,'000611','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 b','SA-2b.','SA-2'),
(21879,'000612','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 b','SA-2b.','SA-2'),
(21880,'000613','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 c','SA-2c.','SA-2'),
(21881,'000614','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 c','SA-2c.','SA-2'),
(21882,'000623','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (1)','SA-4 (1)','SA-4 (1)'),
(21883,'000631','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (6) (a)','SA-4 (6)(a)','SA-4 (6)'),
(21884,'000633','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (6) (b)','SA-4 (6)(b)','SA-4 (6)'),
(21885,'000634','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (7) (a)','SA-4 (7)(a)','SA-4 (7)'),
(21886,'000635','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (7) (b)','SA-4 (7)(b)','SA-4 (7)'),
(21887,'000642','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 c','SA-5c.','SA-5'),
(21888,'000692','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 c','SA-10c.','SA-10'),
(21889,'000694','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 d','SA-10d.','SA-10'),
(21890,'000698','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (1)','SA-10 (1)','SA-10 (1)'),
(21891,'000700','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (2)','SA-10 (2)','SA-10 (2)'),
(21892,'001084','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-3','SC-3','SC-3'),
(21893,'001085','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (1)','SC-3 (1)','SC-3 (1)'),
(21894,'001086','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (2)','SC-3 (2)','SC-3 (2)'),
(21895,'001089','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (5)','SC-3 (5)','SC-3 (5)'),
(21896,'001097','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 a','SC-7a.','SC-7'),
(21897,'001098','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 c','SC-7c.','SC-7'),
(21898,'001101','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (3)','SC-7 (3)','SC-7 (3)'),
(21899,'001102','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (a)','SC-7 (4)(a)','SC-7 (4)'),
(21900,'001103','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (b)','SC-7 (4)(b)','SC-7 (4)'),
(21901,'001105','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (d)','SC-7 (4)(d)','SC-7 (4)'),
(21902,'001106','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (e)','SC-7 (4)(e)','SC-7 (4)'),
(21903,'001107','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (e)','SC-7 (4)(e)','SC-7 (4)'),
(21904,'001108','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (e)','SC-7 (4)(e)','SC-7 (4)'),
(21905,'001109','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (5)','SC-7 (5)','SC-7 (5)'),
(21906,'001112','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (8)','SC-7 (8)','SC-7 (8)'),
(21907,'001113','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (8)','SC-7 (8)','SC-7 (8)'),
(21908,'001114','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (8)','SC-7 (8)','SC-7 (8)'),
(21909,'001116','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (10)','SC-7 (10)','SC-7 (10)'),
(21910,'001119','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (13)','SC-7 (13)','SC-7 (13)'),
(21911,'001120','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (13)','SC-7 (13)','SC-7 (13)'),
(21912,'001121','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (14)','SC-7 (14)','SC-7 (14)'),
(21913,'001122','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (14)','SC-7 (14)','SC-7 (14)'),
(21914,'001123','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (15)','SC-7 (15)','SC-7 (15)'),
(21915,'001124','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (16)','SC-7 (16)','SC-7 (16)'),
(21916,'001125','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (17)','SC-7 (17)','SC-7 (17)'),
(21917,'001126','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (18)','SC-7 (18)','SC-7 (18)'),
(21918,'001661','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-11','SC-11','SC-11'),
(21919,'001135','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-11','SC-11','SC-11'),
(21920,'001662','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18 (1)','SC-18 (1)'),
(21921,'001162','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 b','SC-18b.','SC-18'),
(21922,'001163','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 c','SC-18c.','SC-18'),
(21923,'001164','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 c','SC-18c.','SC-18'),
(21924,'001165','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 c','SC-18c.','SC-18'),
(21925,'001166','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18 (1)','SC-18 (1)'),
(21926,'001167','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18 (2)','SC-18 (2)'),
(21927,'001168','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18 (2)','SC-18 (2)'),
(21928,'001169','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (3)','SC-18 (3)','SC-18 (3)'),
(21929,'001170','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18 (4)','SC-18 (4)'),
(21930,'001171','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18 (4)','SC-18 (4)'),
(21931,'001172','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18 (4)','SC-18 (4)'),
(21932,'001160','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 a','SC-18a.','SC-18'),
(21933,'001161','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 b','SC-18b.','SC-18'),
(21934,'001687','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18 (2)','SC-18 (2)'),
(21935,'001688','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18 (2)','SC-18 (2)'),
(21936,'001695','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (3)','SC-18 (3)','SC-18 (3)'),
(21937,'001663','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 b','SC-20b.','SC-20'),
(21938,'001178','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 a','SC-20a.','SC-20'),
(21939,'001179','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 b','SC-20b.','SC-20'),
(21940,'001664','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (3)','SC-23 (3)','SC-23 (3)'),
(21941,'001184','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23','SC-23','SC-23'),
(21942,'001185','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (1)','SC-23 (1)','SC-23 (1)'),
(21943,'001188','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (3)','SC-23 (3)','SC-23 (3)'),
(21944,'001189','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (3)','SC-23 (3)','SC-23 (3)'),
(21945,'001665','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
(21946,'001190','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
(21947,'001191','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
(21948,'001192','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
(21949,'001193','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
(21950,'001199','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28','SC-28','SC-28'),
(21951,'001225','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 a','SI-2a.','SI-2'),
(21952,'001226','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 a','SI-2a.','SI-2'),
(21953,'001227','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 a','SI-2a.','SI-2'),
(21954,'001228','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b.','SI-2'),
(21955,'001229','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b.','SI-2'),
(21956,'001230','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 d','SI-2d.','SI-2'),
(21957,'001231','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (1)','SI-2 (1)','SI-2 (1)'),
(21958,'001233','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2 (2)','SI-2 (2)'),
(21959,'001234','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2 (2)','SI-2 (2)'),
(21960,'001235','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (3) (a)','SI-2 (3)(a)','SI-2 (3)'),
(21961,'001236','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (3) (b)','SI-2 (3)(b)','SI-2 (3)'),
(21962,'001669','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (a)','SI-3 (6)(a)','SI-3 (6)'),
(21963,'001240','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 b','SI-3b.','SI-3'),
(21964,'001241','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c.1.','SI-3'),
(21965,'001242','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c.1.','SI-3'),
(21966,'001243','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 2','SI-3c.2.','SI-3'),
(21967,'001244','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 2','SI-3c.2.','SI-3'),
(21968,'001245','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 d','SI-3d.','SI-3'),
(21969,'001246','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (1)','SI-3 (1)','SI-3 (1)'),
(21970,'001247','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (2)','SI-3 (2)','SI-3 (2)'),
(21971,'001249','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (4)','SI-3 (4)','SI-3 (4)'),
(21972,'001251','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (a)','SI-3 (6)(a)','SI-3 (6)'),
(21973,'001670','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7)','SI-4 (7)','SI-4 (7)'),
(21974,'001671','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (11)','SI-4 (11)','SI-4 (11)'),
(21975,'001673','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (14)','SI-4 (14)','SI-4 (14)'),
(21976,'001253','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 1','SI-4a.1.','SI-4'),
(21977,'001255','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 c','SI-4c.','SI-4'),
(21978,'001256','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 c','SI-4c.','SI-4'),
(21979,'001257','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 e','SI-4e.','SI-4'),
(21980,'001258','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 f','SI-4f.','SI-4'),
(21981,'001260','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (2)','SI-4 (2)','SI-4 (2)'),
(21982,'001264','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (5)','SI-4 (5)','SI-4 (5)'),
(21983,'001266','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7)','SI-4 (7)','SI-4 (7)'),
(21984,'001267','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7)','SI-4 (7)','SI-4 (7)'),
(21985,'001268','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7)','SI-4 (7)','SI-4 (7)'),
(21986,'001270','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (9)','SI-4 (9)','SI-4 (9)'),
(21987,'001271','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (9)','SI-4 (9)','SI-4 (9)'),
(21988,'001273','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (11)','SI-4 (11)','SI-4 (11)'),
(21989,'001274','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (12)','SI-4 (12)','SI-4 (12)'),
(21990,'001275','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (12)','SI-4 (12)','SI-4 (12)'),
(21991,'001276','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (13) (a)','SI-4 (13)(a)','SI-4 (13)'),
(21992,'001277','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (13) (b)','SI-4 (13)(b)','SI-4 (13)'),
(21993,'001282','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (15)','SI-4 (15)','SI-4 (15)'),
(21994,'001283','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (16)','SI-4 (16)','SI-4 (16)'),
(21995,'001284','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (17)','SI-4 (17)','SI-4 (17)'),
(21996,'001675','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (3)','SI-6 (3)','SI-6 (3)'),
(21997,'001294','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 c','SI-6c.','SI-6'),
(21998,'001295','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (2)','SI-6 (2)','SI-6 (2)'),
(21999,'001296','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (3)','SI-6 (3)','SI-6 (3)'),
(22000,'001306','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 b','SI-8b.','SI-8'),
(22001,'001307','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 (1)','SI-8 (1)','SI-8 (1)'),
(22002,'001308','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 (2)','SI-8 (2)','SI-8 (2)'),
(22003,'001678','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-12','SI-12','SI-12'),
(22004,'001315','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-12','SI-12','SI-12'),
(22005,'001318','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 b','SI-13b.','SI-13'),
(22006,'001319','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (1)','SI-13 (1)','SI-13 (1)'),
(22007,'001320','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (1)','SI-13 (1)','SI-13 (1)'),
(22008,'001321','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (16)','SI-7 (16)','SI-7 (16)'),
(22009,'001322','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (16)','SI-7 (16)','SI-7 (16)'),
(22010,'001323','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (3)','SI-13 (3)','SI-13 (3)'),
(22011,'001324','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (3)','SI-13 (3)','SI-13 (3)'),
(22012,'001325','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (3)','SI-13 (3)','SI-13 (3)'),
(22013,'001326','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (a)','SI-13 (4)(a)','SI-13 (4)'),
(22014,'001327','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (a)','SI-13 (4)(a)','SI-13 (4)'),
(22015,'001328','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (b)','SI-13 (4)(b)','SI-13 (4)'),
(22016,'001329','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (b)','SI-13 (4)(b)','SI-13 (4)'),
(22017,'001680','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 2','PM-1a.2.','PM-1'),
(22018,'000073','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 1','PM-1a.1.','PM-1'),
(22019,'000074','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 4','PM-1a.4.','PM-1'),
(22020,'000075','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 b','PM-1b.','PM-1'),
(22021,'000076','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 b','PM-1b.','PM-1'),
(22022,'000077','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 c','PM-1c.','PM-1'),
(22023,'000021','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (2)','AC-3 (2)','AC-3 (2)'),
(22024,'000024','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (5)','AC-3 (5)','AC-3 (5)'),
(22025,'000213','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3','AC-3','AC-3'),
(22026,'001408','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (2)','AC-3 (2)','AC-3 (2)'),
(22027,'001411','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (5)','AC-3 (5)','AC-3 (5)'),
(22028,'000036','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 a','AC-5a.','AC-5'),
(22029,'001380','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 b','AC-5b.','AC-5'),
(22030,'000043','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7','AC-7','AC-7'),
(22031,'000044','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 a','AC-7a.','AC-7'),
(22032,'001423','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7','AC-7','AC-7'),
(22033,'000048','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a','AC-8a.','AC-8'),
(22034,'000050','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 b','AC-8b.','AC-8'),
(22035,'001384','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 1','AC-8c.1.','AC-8'),
(22036,'001385','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 2','AC-8c.2.','AC-8'),
(22037,'001386','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 2','AC-8c.2.','AC-8'),
(22038,'001387','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 2','AC-8c.2.','AC-8'),
(22039,'001388','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 3','AC-8c.3.','AC-8'),
(22040,'000052','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9','AC-9','AC-9'),
(22041,'000053','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (1)','AC-9 (1)','AC-9 (1)'),
(22042,'001389','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9 (2)','AC-9 (2)'),
(22043,'001390','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9 (2)','AC-9 (2)'),
(22044,'001391','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9 (2)','AC-9 (2)'),
(22045,'001392','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9 (2)','AC-9 (2)'),
(22046,'001393','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (3)','AC-9 (3)','AC-9 (3)'),
(22047,'001394','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (3)','AC-9 (3)','AC-9 (3)'),
(22048,'001395','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (3)','AC-9 (3)','AC-9 (3)'),
(22049,'000054','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
(22050,'000055','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
(22051,'000056','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 b','AC-11b.','AC-11'),
(22052,'000057','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 a','AC-11a.','AC-11'),
(22053,'000058','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 a','AC-11a.','AC-11'),
(22054,'000059','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 a','AC-11a.','AC-11'),
(22055,'000060','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 (1)','AC-11 (1)','AC-11 (1)'),
(22056,'000061','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-14 a','AC-14a.','AC-14'),
(22057,'000232','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-14 b','AC-14b.','AC-14'),
(22058,'000264','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 a','CA-5a.','CA-5'),
(22059,'000265','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 b','CA-5b.','CA-5'),
(22060,'000266','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 b','CA-5b.','CA-5'),
(22061,'000267','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5 (1)','CA-5 (1)'),
(22062,'000268','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5 (1)','CA-5 (1)'),
(22063,'000269','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5 (1)','CA-5 (1)'),
(22064,'000270','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 a','CA-6a.','CA-6'),
(22065,'000271','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 b','CA-6b.','CA-6'),
(22066,'000272','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 c','CA-6c.','CA-6'),
(22067,'000273','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 c','CA-6c.','CA-6'),
(22068,'000082','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a.','AC-19'),
(22069,'000083','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a.','AC-19'),
(22070,'000084','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 b','AC-19b.','AC-19'),
(22071,'001458','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (4)','AC-19 (4)(b)(4)','AC-19 (4)'),
(22072,'001330','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (a)','AC-19 (4)(a)','AC-19 (4)'),
(22073,'001331','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (1)','AC-19 (4)(b)(1)','AC-19 (4)'),
(22074,'001332','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (2)','AC-19 (4)(b)(2)','AC-19 (4)'),
(22075,'001333','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (3)','AC-19 (4)(b)(3)','AC-19 (4)'),
(22076,'001334','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (4)','AC-19 (4)(b)(4)','AC-19 (4)'),
(22077,'001335','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (4)','AC-19 (4)(b)(4)','AC-19 (4)'),
(22078,'000093','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a','AC-20a.','AC-20'),
(22079,'000097','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (2)','AC-20 (2)','AC-20 (2)'),
(22080,'000098','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 a','AC-21a.','AC-21'),
(22081,'000099','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 (1)','AC-21 (1)','AC-21 (1)'),
(22082,'001470','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 a','AC-21a.','AC-21'),
(22083,'001471','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 b','AC-21b.','AC-21'),
(22084,'001472','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 b','AC-21b.','AC-21'),
(22085,'000106','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 a','AT-2a.','AT-2'),
(22086,'000107','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (1)','AT-2 (1)','AT-2 (1)'),
(22087,'000112','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 b','AT-2b.','AT-2'),
(22088,'001479','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 c','AT-2c.','AT-2'),
(22089,'001480','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-2','AT-2','AT-2'),
(22090,'000113','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 a','AT-4a.','AT-4'),
(22091,'000114','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 a','AT-4a.','AT-4'),
(22092,'001336','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 b','AT-4b.','AT-4'),
(22093,'001337','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 b','AT-4b.','AT-4'),
(22094,'000130','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3','AU-3','AU-3'),
(22095,'000131','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3','AU-3','AU-3'),
(22096,'000132','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3','AU-3','AU-3'),
(22097,'000133','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3','AU-3','AU-3'),
(22098,'000134','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3','AU-3','AU-3'),
(22099,'000135','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (1)','AU-3 (1)','AU-3 (1)'),
(22100,'001487','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3','AU-3','AU-3'),
(22101,'001488','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (1)','AU-3 (1)','AU-3 (1)'),
(22102,'000148','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a.','AU-6'),
(22103,'000149','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 b','AU-6b.','AU-6'),
(22104,'000151','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a.','AU-6'),
(22105,'000153','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (3)','AU-6 (3)','AU-6 (3)'),
(22106,'000154','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (4)','AU-6 (4)','AU-6 (4)'),
(22107,'001491','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (6)','AU-6 (6)','AU-6 (6)'),
(22108,'000158','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (1)','AU-7 (1)','AU-7 (1)'),
(22109,'000159','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 a','AU-8a.','AU-8'),
(22110,'000161','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 (1) (a)','AU-8 (1)(a)','AU-8 (1)'),
(22111,'001492','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 (1) (a)','AU-8 (1)(a)','AU-8 (1)'),
(22112,'000166','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10','AU-10','AU-10'),
(22113,'001340','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (3)','AU-10 (3)','AU-10 (3)'),
(22114,'001341','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (a)','AU-10 (4)(a)','AU-10 (4)'),
(22115,'000167','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-11','AU-11','AU-11'),
(22116,'000168','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-11','AU-11','AU-11'),
(22117,'000206','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-6','IA-6','IA-6'),
(22118,'000209','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
(22119,'000210','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
(22120,'000211','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
(22121,'000212','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-7','PM-7','PM-7'),
(22122,'000078','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-2','PM-2','PM-2'),
(22123,'000080','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 a','PM-3a.','PM-3'),
(22124,'000081','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 b','PM-3b.','PM-3'),
(22125,'000141','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 c','PM-3c.','PM-3'),
(22126,'000142','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a.1.','PM-4'),
(22127,'000170','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 2','PM-4a.2.','PM-4'),
(22128,'000207','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-5','PM-5','PM-5'),
(22129,'000227','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 a','PM-9a.','PM-9'),
(22130,'000228','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 b','PM-9b.','PM-9'),
(22131,'000229','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 a','PM-10a.','PM-10'),
(22132,'000230','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 a','PM-10a.','PM-10'),
(22133,'000231','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 a','PM-10a.','PM-10'),
(22134,'000233','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 b','PM-10b.','PM-10'),
(22135,'000234','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 c','PM-10c.','PM-10'),
(22136,'000235','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 a','PM-11a.','PM-11'),
(22137,'000236','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 b','PM-11b.','PM-11'),
(22138,'001460','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-13','AU-13','AU-13'),
(22139,'001461','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-13','AU-13','AU-13'),
(22140,'000338','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22141,'000339','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22142,'000340','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22143,'000341','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22144,'000342','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22145,'000343','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22146,'000344','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22147,'000345','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
(22148,'000348','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (2)','CM-5 (2)','CM-5 (2)'),
(22149,'000349','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (2)','CM-5 (2)','CM-5 (2)'),
(22150,'000350','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (2)','CM-5 (2)','CM-5 (2)'),
(22151,'000353','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5 (4)','CM-5 (4)'),
(22152,'000354','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5 (4)','CM-5 (4)'),
(22153,'001499','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (6)','CM-5 (6)','CM-5 (6)'),
(22154,'000389','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 1','CM-8a.1.','CM-8'),
(22155,'000390','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 1','CM-8a.1.','CM-8'),
(22156,'000392','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 2','CM-8a.2.','CM-8'),
(22157,'000393','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 2','CM-8a.2.','CM-8'),
(22158,'000395','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 3','CM-8a.3.','CM-8'),
(22159,'000396','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 3','CM-8a.3.','CM-8'),
(22160,'000398','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 4','CM-8a.4.','CM-8'),
(22161,'000399','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 4','CM-8a.4.','CM-8'),
(22162,'000400','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 4','CM-8a.4.','CM-8'),
(22163,'000408','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (1)','CM-8 (1)','CM-8 (1)'),
(22164,'000409','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (1)','CM-8 (1)','CM-8 (1)'),
(22165,'000410','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (1)','CM-8 (1)','CM-8 (1)'),
(22166,'000411','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8 (2)','CM-8 (2)'),
(22167,'000412','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8 (2)','CM-8 (2)'),
(22168,'000413','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8 (2)','CM-8 (2)'),
(22169,'000414','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8 (2)','CM-8 (2)'),
(22170,'000415','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (a)','CM-8 (3)(a)','CM-8 (3)'),
(22171,'000416','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (a)','CM-8 (3)(a)','CM-8 (3)'),
(22172,'000418','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (4)','CM-8 (4)','CM-8 (4)'),
(22173,'000419','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (5)','CM-8 (5)','CM-8 (5)'),
(22174,'000420','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (6)','CM-8 (6)','CM-8 (6)'),
(22175,'000421','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 a','CM-9a.','CM-9'),
(22176,'000422','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 a','CM-9a.','CM-9'),
(22177,'000423','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 a','CM-9a.','CM-9'),
(22178,'000424','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c.','CM-9'),
(22179,'000425','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c.','CM-9'),
(22180,'000426','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c.','CM-9'),
(22181,'000436','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 (1)','CM-9 (1)','CM-9 (1)'),
(22182,'000485','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 c','CP-3c.','CP-3'),
(22183,'000486','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a','CP-3a.','CP-3'),
(22184,'000487','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 c','CP-3c.','CP-3'),
(22185,'000488','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 (1)','CP-3 (1)','CP-3 (1)'),
(22186,'000489','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 (2)','CP-3 (2)','CP-3 (2)'),
(22187,'000490','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 a','CP-4a.','CP-4'),
(22188,'000492','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 a','CP-4a.','CP-4'),
(22189,'000494','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 a','CP-4a.','CP-4'),
(22190,'000496','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 b','CP-4b.','CP-4'),
(22191,'000497','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 c','CP-4c.','CP-4'),
(22192,'000498','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (1)','CP-4 (1)','CP-4 (1)'),
(22193,'000500','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (2) (a)','CP-4 (2)(a)','CP-4 (2)'),
(22194,'000502','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (3)','CP-4 (3)','CP-4 (3)'),
(22195,'000504','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (4)4','CP-4 (4)4.','CP-4 (4)'),
(22196,'000968','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (3)','PE-13 (3)','PE-13 (3)'),
(22197,'000965','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13','PE-13','PE-13'),
(22198,'000971','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 a','PE-14a.','PE-14'),
(22199,'000972','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 a','PE-14a.','PE-14'),
(22200,'000973','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 b','PE-14b.','PE-14'),
(22201,'000974','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 b','PE-14b.','PE-14'),
(22202,'000975','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 (1)','PE-14 (1)','PE-14 (1)'),
(22203,'000976','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 (2)','PE-14 (2)','PE-14 (2)'),
(22204,'000977','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-15','PE-15','PE-15'),
(22205,'000978','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-15','PE-15','PE-15'),
(22206,'000979','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-15','PE-15','PE-15'),
(22207,'001182','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-22','SC-22','SC-22'),
(22208,'001183','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-22','SC-22','SC-22'),
(22209,'001173','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-19 a','SC-19a.','SC-19'),
(22210,'001174','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-19 a','SC-19a.','SC-19'),
(22211,'001175','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-19 b','SC-19b.','SC-19'),
(22212,'001176','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-19 b','SC-19b.','SC-19'),
(22213,'001177','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-19 b','SC-19b.','SC-19'),
(22214,'000550','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10','CP-10','CP-10'),
(22215,'000551','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10','CP-10','CP-10'),
(22216,'000552','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10','CP-10','CP-10'),
(22217,'000553','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (2)','CP-10 (2)','CP-10 (2)'),
(22218,'000556','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (4)','CP-10 (4)','CP-10 (4)'),
(22219,'000557','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (4)','CP-10 (4)','CP-10 (4)'),
(22220,'000558','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (5)','SI-13 (5)','SI-13 (5)'),
(22221,'000559','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (5)','SI-13 (5)','SI-13 (5)'),
(22222,'000560','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (6)','CP-10 (6)','CP-10 (6)'),
(22223,'000561','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (6)','CP-10 (6)','CP-10 (6)'),
(22224,'000562','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (6)','CP-10 (6)','CP-10 (6)'),
(22225,'000571','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 9','PL-2a.9.','PL-2'),
(22226,'000572','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 c','PL-2c.','PL-2'),
(22227,'000573','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 c','PL-2c.','PL-2'),
(22228,'000574','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 d','PL-2d.','PL-2'),
(22229,'000577','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 b','PL-7b.','PL-7'),
(22230,'000578','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 b','PL-7b.','PL-7'),
(22231,'001646','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b 2','SA-1b.2.','SA-1'),
(22232,'000601','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b 1','SA-1b.1.','SA-1'),
(22233,'000602','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1','SA-1a.1.','SA-1'),
(22234,'000603','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1','SA-1a.1.','SA-1'),
(22235,'000604','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b 1','SA-1b.1.','SA-1'),
(22236,'000605','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 2','SA-1a.2.','SA-1'),
(22237,'000606','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 2','SA-1a.2.','SA-1'),
(22238,'000607','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b 2','SA-1b.2.','SA-1'),
(22239,'000615','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a.','SA-3'),
(22240,'000616','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 b','SA-3b.','SA-3'),
(22241,'000618','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 c','SA-3c.','SA-3'),
(22242,'000664','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
(22243,'000665','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
(22244,'000666','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
(22245,'000667','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
(22246,'000668','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
(22247,'000669','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 a','SA-9a.','SA-9'),
(22248,'000670','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 a','SA-9a.','SA-9'),
(22249,'000671','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 b','SA-9b.','SA-9'),
(22250,'000672','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 b','SA-9b.','SA-9'),
(22251,'000673','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 b','SA-9b.','SA-9'),
(22252,'000674','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 b','SA-9b.','SA-9'),
(22253,'000722','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12','SA-12','SA-12'),
(22254,'000723','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12','SA-12','SA-12'),
(22255,'000756','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1','IA-1a.1.','IA-1'),
(22256,'000757','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1','IA-1a.1.','IA-1'),
(22257,'000758','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b 1','IA-1b.1.','IA-1'),
(22258,'000759','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b 1','IA-1b.1.','IA-1'),
(22259,'000760','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 2','IA-1a.2.','IA-1'),
(22260,'000761','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 2','IA-1a.2.','IA-1'),
(22261,'000762','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b 2','IA-1b.2.','IA-1'),
(22262,'000763','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b 2','IA-1b.2.','IA-1'),
(22263,'000764','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2','IA-2','IA-2'),
(22264,'000765','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (1)','IA-2 (1)','IA-2 (1)'),
(22265,'000766','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (2)','IA-2 (2)','IA-2 (2)'),
(22266,'000767','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (3)','IA-2 (3)','IA-2 (3)'),
(22267,'000768','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (4)','IA-2 (4)','IA-2 (4)'),
(22268,'000770','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (5)','IA-2 (5)','IA-2 (5)'),
(22269,'000777','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3','IA-3','IA-3'),
(22270,'000778','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3','IA-3','IA-3'),
(22271,'000783','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (b)','IA-3 (3)(b)','IA-3 (3)'),
(22272,'000794','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 e','IA-4e.','IA-4'),
(22273,'000795','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 e','IA-4e.','IA-4'),
(22274,'000796','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (1)','IA-4 (1)','IA-4 (1)'),
(22275,'000799','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (3)','IA-4 (3)','IA-4 (3)'),
(22276,'000800','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (4)','IA-4 (4)','IA-4 (4)'),
(22277,'000801','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (4)','IA-4 (4)','IA-4 (4)'),
(22278,'000803','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-7','IA-7','IA-7'),
(22279,'000804','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8','IA-8','IA-8'),
(22280,'000805','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1','IR-1a.1.','IR-1'),
(22281,'000806','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1','IR-1a.1.','IR-1'),
(22282,'000807','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b 1','IR-1b.1.','IR-1'),
(22283,'000808','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b 1','IR-1b.1.','IR-1'),
(22284,'000809','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 2','IR-1a.2.','IR-1'),
(22285,'000810','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 2','IR-1a.2.','IR-1'),
(22286,'000811','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b 2','IR-1b.2.','IR-1'),
(22287,'000812','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b 2','IR-1b.2.','IR-1'),
(22288,'000834','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 a','IR-6a.','IR-6'),
(22289,'000835','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 a','IR-6a.','IR-6'),
(22290,'000836','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 b','IR-6b.','IR-6'),
(22291,'000837','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (1)','IR-6 (1)','IR-6 (1)'),
(22292,'000838','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (2)','IR-6 (2)','IR-6 (2)'),
(22293,'000839','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-7','IR-7','IR-7'),
(22294,'000840','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-7 (1)','IR-7 (1)','IR-7 (1)'),
(22295,'000841','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-7 (2) (a)','IR-7 (2)(a)','IR-7 (2)'),
(22296,'000842','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-7 (2) (b)','IR-7 (2)(b)','IR-7 (2)'),
(22297,'000844','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 8','IR-8a.8.','IR-8'),
(22298,'000845','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 b','IR-8b.','IR-8'),
(22299,'000846','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 b','IR-8b.','IR-8'),
(22300,'000847','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 c','IR-8c.','IR-8'),
(22301,'000848','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 c','IR-8c.','IR-8'),
(22302,'000849','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 d','IR-8d.','IR-8'),
(22303,'000850','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 e','IR-8e.','IR-8'),
(22304,'000865','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3','MA-3','MA-3'),
(22305,'000866','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3','MA-3','MA-3'),
(22306,'000867','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3','MA-3','MA-3'),
(22307,'000869','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (1)','MA-3 (1)','MA-3 (1)'),
(22308,'000870','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (2)','MA-3 (2)','MA-3 (2)'),
(22309,'000871','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3)','MA-3 (3)','MA-3 (3)'),
(22310,'000890','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 a','MA-5a.','MA-5'),
(22311,'000891','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 a','MA-5a.','MA-5'),
(22312,'000893','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (a)','MA-5 (1)(a)','MA-5 (1)'),
(22313,'000894','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (a) (1)','MA-5 (1)(a)(1)','MA-5 (1)'),
(22314,'000895','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (a) (2)','MA-5 (1)(a)(2)','MA-5 (1)'),
(22315,'000897','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (2)','MA-5 (2)','MA-5 (2)'),
(22316,'000898','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (3)','MA-5 (3)','MA-5 (3)'),
(22317,'000899','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (4) (a)','MA-5 (4)(a)','MA-5 (4)'),
(22318,'000900','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (4) (b)','MA-5 (4)(b)','MA-5 (4)'),
(22319,'000903','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6','MA-6','MA-6'),
(22320,'000904','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1','PE-1a.1.','PE-1'),
(22321,'000905','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1','PE-1a.1.','PE-1'),
(22322,'000906','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b 1','PE-1b.1.','PE-1'),
(22323,'000907','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b 1','PE-1b.1.','PE-1'),
(22324,'000908','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 2','PE-1a.2.','PE-1'),
(22325,'000909','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 2','PE-1a.2.','PE-1'),
(22326,'000910','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b 2','PE-1b.2.','PE-1'),
(22327,'000911','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b 2','PE-1b.2.','PE-1'),
(22328,'000919','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a','PE-3a.','PE-3'),
(22329,'000920','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 1','PE-3a.1.','PE-3'),
(22330,'000921','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 2','PE-3a.2.','PE-3'),
(22331,'000923','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 e','PE-3e.','PE-3'),
(22332,'000924','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 f','PE-3f.','PE-3'),
(22333,'000925','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 f','PE-3f.','PE-3'),
(22334,'000926','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 g','PE-3g.','PE-3'),
(22335,'000927','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 g','PE-3g.','PE-3'),
(22336,'000928','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (1)','PE-3 (1)','PE-3 (1)'),
(22337,'000929','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (2)','PE-3 (2)','PE-3 (2)'),
(22338,'000930','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (3)','PE-3 (3)','PE-3 (3)'),
(22339,'000931','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (4)','PE-3 (4)','PE-3 (4)'),
(22340,'000932','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (4)','PE-3 (4)','PE-3 (4)'),
(22341,'000933','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (5)','PE-3 (5)','PE-3 (5)'),
(22342,'000934','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (6)','PE-3 (6)','PE-3 (6)'),
(22343,'000935','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (6)','PE-3 (6)','PE-3 (6)'),
(22344,'000936','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-4','PE-4','PE-4'),
(22345,'000937','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5','PE-5','PE-5'),
(22346,'000939','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b.','PE-6'),
(22347,'000940','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b.','PE-6'),
(22348,'000941','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 c','PE-6c.','PE-6'),
(22349,'000942','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (1)','PE-6 (1)','PE-6 (1)'),
(22350,'000947','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 a','PE-8a.','PE-8'),
(22351,'000948','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 b','PE-8b.','PE-8'),
(22352,'000949','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 b','PE-8b.','PE-8'),
(22353,'000950','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 (1)','PE-8 (1)','PE-8 (1)'),
(22354,'000952','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-9','PE-9','PE-9'),
(22355,'000954','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (2)','PE-9 (2)','PE-9 (2)'),
(22356,'000955','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (2)','PE-9 (2)','PE-9 (2)'),
(22357,'000956','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 a','PE-10a.','PE-10'),
(22358,'000957','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 b','PE-10b.','PE-10'),
(22359,'000958','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 b','PE-10b.','PE-10'),
(22360,'000959','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 c','PE-10c.','PE-10'),
(22361,'000961','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (1)','PE-11 (1)','PE-11 (1)'),
(22362,'000963','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-12','PE-12','PE-12'),
(22363,'000981','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-16','PE-16','PE-16'),
(22364,'000982','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-16','PE-16','PE-16'),
(22365,'000983','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-16','PE-16','PE-16'),
(22366,'000984','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-16','PE-16','PE-16'),
(22367,'000985','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 a','PE-17a.','PE-17'),
(22368,'000987','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 b','PE-17b.','PE-17'),
(22369,'000988','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 c','PE-17c.','PE-17'),
(22370,'000989','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-18','PE-18','PE-18'),
(22371,'000991','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-18','PE-18','PE-18'),
(22372,'000993','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-19','PE-19','PE-19'),
(22373,'000994','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-19 (1)','PE-19 (1)','PE-19 (1)'),
(22374,'000995','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1','MP-1a.1.','MP-1'),
(22375,'000996','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1','MP-1a.1.','MP-1'),
(22376,'000997','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b 1','MP-1b.1.','MP-1'),
(22377,'000998','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b 1','MP-1b.1.','MP-1'),
(22378,'000999','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 2','MP-1a.2.','MP-1'),
(22379,'001000','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 2','MP-1a.2.','MP-1'),
(22380,'001001','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b 2','MP-1b.2.','MP-1'),
(22381,'001002','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b 2','MP-1b.2.','MP-1'),
(22382,'001003','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-2','MP-2','MP-2'),
(22383,'001004','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-2','MP-2','MP-2'),
(22384,'001005','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-2','MP-2','MP-2'),
(22385,'001007','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 (2)','MP-4 (2)','MP-4 (2)'),
(22386,'001008','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 (2)','MP-4 (2)','MP-4 (2)'),
(22387,'001014','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a.','MP-4'),
(22388,'001015','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a.','MP-4'),
(22389,'001016','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a.','MP-4'),
(22390,'001018','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 b','MP-4b.','MP-4'),
(22391,'001020','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a.','MP-5'),
(22392,'001021','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a.','MP-5'),
(22393,'001022','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a.','MP-5'),
(22394,'001023','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 b','MP-5b.','MP-5'),
(22395,'001024','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 d','MP-5d.','MP-5'),
(22396,'001025','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 c','MP-5c.','MP-5'),
(22397,'001026','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 (3)','MP-5 (3)','MP-5 (3)'),
(22398,'001027','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 (4)','MP-5 (4)','MP-5 (4)'),
(22399,'001028','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 a','MP-6a.','MP-6'),
(22400,'001030','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (2)','MP-6 (2)','MP-6 (2)'),
(22401,'001031','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (2)','MP-6 (2)','MP-6 (2)'),
(22402,'001032','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (3)','MP-6 (3)','MP-6 (3)'),
(22403,'001033','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (3)','MP-6 (3)','MP-6 (3)'),
(22404,'001037','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1','RA-1a.1.','RA-1'),
(22405,'001038','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1','RA-1a.1.','RA-1'),
(22406,'001039','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b 1','RA-1b.1.','RA-1'),
(22407,'001040','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b 1','RA-1b.1.','RA-1'),
(22408,'001041','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 2','RA-1a.2.','RA-1'),
(22409,'001042','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 2','RA-1a.2.','RA-1'),
(22410,'001043','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b 2','RA-1b.2.','RA-1'),
(22411,'001044','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b 2','RA-1b.2.','RA-1'),
(22412,'001045','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 a','RA-2a.','RA-2'),
(22413,'001046','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 b','RA-2b.','RA-2'),
(22414,'001047','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 c','RA-2c.','RA-2'),
(22415,'001074','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1','SC-1a.1.','SC-1'),
(22416,'001075','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1','SC-1a.1.','SC-1'),
(22417,'001076','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b 1','SC-1b.1.','SC-1'),
(22418,'001077','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b 1','SC-1b.1.','SC-1'),
(22419,'001078','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a.2.','SC-1'),
(22420,'001079','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a.2.','SC-1'),
(22421,'001080','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b 2','SC-1b.2.','SC-1'),
(22422,'001081','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b 2','SC-1b.2.','SC-1'),
(22423,'001082','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-2','SC-2','SC-2'),
(22424,'001083','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-2 (1)','SC-2 (1)','SC-2 (1)'),
(22425,'001090','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-4','SC-4','SC-4'),
(22426,'001093','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5','SC-5','SC-5'),
(22427,'001094','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (1)','SC-5 (1)','SC-5 (1)'),
(22428,'001095','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (2)','SC-5 (2)','SC-5 (2)'),
(22429,'001133','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-10','SC-10','SC-10'),
(22430,'001134','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-10','SC-10','SC-10'),
(22431,'001139','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (1)','SC-12 (1)','SC-12 (1)'),
(22432,'001150','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 a','SC-15a.','SC-15'),
(22433,'001151','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 a','SC-15a.','SC-15'),
(22434,'001152','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 b','SC-15b.','SC-15'),
(22435,'001153','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (1)','SC-15 (1)','SC-15 (1)'),
(22436,'001155','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (3)','SC-15 (3)','SC-15 (3)'),
(22437,'001156','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (3)','SC-15 (3)','SC-15 (3)'),
(22438,'001157','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
(22439,'001158','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (1)','SC-16 (1)','SC-16 (1)'),
(22440,'001159','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-17','SC-17','SC-17'),
(22441,'001194','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-25','SC-25','SC-25'),
(22442,'001195','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-26','SC-26','SC-26'),
(22443,'001196','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-35','SC-35','SC-35'),
(22444,'001197','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-27','SC-27','SC-27'),
(22445,'001198','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-27','SC-27','SC-27'),
(22446,'001201','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-29','SC-29','SC-29'),
(22447,'001203','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-29 (1)','SC-29 (1)','SC-29 (1)'),
(22448,'001204','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-29 (1)','SC-29 (1)','SC-29 (1)'),
(22449,'001207','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (1)','SC-31 (1)','SC-31 (1)'),
(22450,'001210','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 a','SC-34a.','SC-34'),
(22451,'001211','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 b','SC-34b.','SC-34'),
(22452,'001212','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34','SC-34','SC-34'),
(22453,'001213','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 b','SC-34b.','SC-34'),
(22454,'001214','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (1)','SC-34 (1)','SC-34 (1)'),
(22455,'001215','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (1)','SC-34 (1)','SC-34 (1)'),
(22456,'001216','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (2)','SC-34 (2)','SC-34 (2)'),
(22457,'001217','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 1','SI-1a.1.','SI-1'),
(22458,'001218','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 1','SI-1a.1.','SI-1'),
(22459,'001219','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b 1','SI-1b.1.','SI-1'),
(22460,'001220','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 2','SI-1a.2.','SI-1'),
(22461,'001221','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 2','SI-1a.2.','SI-1'),
(22462,'001222','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b 2','SI-1b.2.','SI-1'),
(22463,'001223','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b 1','SI-1b.1.','SI-1'),
(22464,'001224','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b 2','SI-1b.2.','SI-1'),
(22465,'001285','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 a','SI-5a.','SI-5'),
(22466,'001286','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 b','SI-5b.','SI-5'),
(22467,'001287','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c.','SI-5'),
(22468,'001288','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c.','SI-5'),
(22469,'001289','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 d','SI-5d.','SI-5'),
(22470,'001290','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 (1)','SI-5 (1)','SI-5 (1)'),
(22471,'001300','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (2)','SI-7 (2)','SI-7 (2)'),
(22472,'001301','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (3)','SI-7 (3)','SI-7 (3)'),
(22473,'001310','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10','SI-10','SI-10'),
(22474,'001312','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-11 a','SI-11a.','SI-11'),
(22475,'001314','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-11 b','SI-11b.','SI-11'),
(22476,'001462','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 (2)','AU-14 (2)','AU-14 (2)'),
(22477,'001464','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 (1)','AU-14 (1)','AU-14 (1)'),
(22478,'001473','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 a','AC-22a.','AC-22'),
(22479,'001474','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 b','AC-22b.','AC-22'),
(22480,'001475','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 c','AC-22c.','AC-22'),
(22481,'001476','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 d','AC-22d.','AC-22'),
(22482,'001477','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 d','AC-22d.','AC-22'),
(22483,'001478','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 d','AC-22d.','AC-22'),
(22484,'001504','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1','PS-1a.1.','PS-1'),
(22485,'001505','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1','PS-1a.1.','PS-1'),
(22486,'001506','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b 2','PS-1b.2.','PS-1'),
(22487,'001507','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b 1','PS-1b.1.','PS-1'),
(22488,'001508','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b 2','PS-1b.2.','PS-1'),
(22489,'001509','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 2','PS-1a.2.','PS-1'),
(22490,'001510','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 2','PS-1a.2.','PS-1'),
(22491,'001511','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b 2','PS-1b.2.','PS-1'),
(22492,'001512','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 a','PS-2a.','PS-2'),
(22493,'001513','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 b','PS-2b.','PS-2'),
(22494,'001514','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 c','PS-2c.','PS-2'),
(22495,'001515','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 c','PS-2c.','PS-2'),
(22496,'001516','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 a','PS-3a.','PS-3'),
(22497,'001517','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 b','PS-3b.','PS-3'),
(22498,'001518','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 b','PS-3b.','PS-3'),
(22499,'001519','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 b','PS-3b.','PS-3'),
(22500,'001520','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (1)','PS-3 (1)','PS-3 (1)'),
(22501,'001521','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (2)','PS-3 (2)','PS-3 (2)'),
(22502,'001522','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 a','PS-4a.','PS-4'),
(22503,'001523','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 c','PS-4c.','PS-4'),
(22504,'001524','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 d','PS-4d.','PS-4'),
(22505,'001525','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 e','PS-4e.','PS-4'),
(22506,'001526','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 e','PS-4e.','PS-4'),
(22507,'001527','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 a','PS-5a.','PS-5'),
(22508,'001528','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 b','PS-5b.','PS-5'),
(22509,'001529','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 b','PS-5b.','PS-5'),
(22510,'001530','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 b','PS-5b.','PS-5'),
(22511,'001531','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 1','PS-6c.1.','PS-6'),
(22512,'001532','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 b','PS-6b.','PS-6'),
(22513,'001533','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 b','PS-6b.','PS-6'),
(22514,'001536','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (2) (a)','PS-6 (2)(a)','PS-6 (2)'),
(22515,'001537','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (2) (b)','PS-6 (2)(b)','PS-6 (2)'),
(22516,'001538','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (2) (c)','PS-6 (2)(c)','PS-6 (2)'),
(22517,'001539','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 a','PS-7a.','PS-7'),
(22518,'001540','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 c','PS-7c.','PS-7'),
(22519,'001541','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 e','PS-7e.','PS-7'),
(22520,'001542','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 a','PS-8a.','PS-8'),
(22521,'002106','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1','AC-1a.1.','AC-1'),
(22522,'002107','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1','AC-1a.1.','AC-1'),
(22523,'002108','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1','AC-1a.1.','AC-1'),
(22524,'002109','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 2','AC-1a.2.','AC-1'),
(22525,'002110','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 a','AC-2a.','AC-2'),
(22526,'002111','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 a','AC-2a.','AC-2'),
(22527,'002112','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 b','AC-2b.','AC-2'),
(22528,'002113','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 c','AC-2c.','AC-2'),
(22529,'002114','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d','AC-2d.','AC-2'),
(22530,'002115','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d','AC-2d.','AC-2'),
(22531,'002116','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d','AC-2d.','AC-2'),
(22532,'002117','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d','AC-2d.','AC-2'),
(22533,'002118','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d','AC-2d.','AC-2'),
(22534,'002119','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d','AC-2d.','AC-2'),
(22535,'002120','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 e','AC-2e.','AC-2'),
(22536,'002121','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f.','AC-2'),
(22537,'002122','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 g','AC-2g.','AC-2'),
(22538,'002123','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h 1','AC-2h.1.','AC-2'),
(22539,'002124','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h 2','AC-2h.2.','AC-2'),
(22540,'002125','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h 3','AC-2h.3.','AC-2'),
(22541,'002126','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 1 ','AC-2i.1 .','AC-2'),
(22542,'002127','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 2 ','AC-2i.2 .','AC-2'),
(22543,'002128','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 3 ','AC-2i.3 .','AC-2'),
(22544,'002129','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 k','AC-2k.','AC-2'),
(22545,'002130','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(22546,'002131','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(22547,'002132','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2 (4)','AC-2 (4)'),
(22548,'002133','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (5)','AC-2 (5)','AC-2 (5)'),
(22549,'002134','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (6)','AC-2 (6)','AC-2 (6)'),
(22550,'002135','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (6)','AC-2 (6)','AC-2 (6)'),
(22551,'002136','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (c)','AC-2 (7)(c)','AC-2 (7)'),
(22552,'002137','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (c)','AC-2 (7)(c)','AC-2 (7)'),
(22553,'002138','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2 (8)','AC-2 (8)'),
(22554,'002139','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2 (8)','AC-2 (8)'),
(22555,'002140','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (9)','AC-2 (9)','AC-2 (9)'),
(22556,'002141','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (9)','AC-2 (9)','AC-2 (9)'),
(22557,'002142','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (10)','AC-2 (10)','AC-2 (10)'),
(22558,'002143','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (11)','AC-2 (11)','AC-2 (11)'),
(22559,'002144','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (11)','AC-2 (11)','AC-2 (11)'),
(22560,'002145','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (11)','AC-2 (11)','AC-2 (11)'),
(22561,'002146','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (a)','AC-2 (12)(a)','AC-2 (12)'),
(22562,'002147','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (a)','AC-2 (12)(a)','AC-2 (12)'),
(22563,'002148','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (b)','AC-2 (12)(b)','AC-2 (12)'),
(22564,'002149','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (b)','AC-2 (12)(b)','AC-2 (12)'),
(22565,'002150','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (13)','AC-2 (13)','AC-2 (13)'),
(22566,'002151','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (13)','AC-2 (13)','AC-2 (13)'),
(22567,'002152','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (2)','AC-3 (2)','AC-3 (2)'),
(22568,'002153','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3)','AC-3 (3)','AC-3 (3)'),
(22569,'002154','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (a)','AC-3 (3)(a)','AC-3 (3)'),
(22570,'002155','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (1)','AC-3 (3)(b)(1)','AC-3 (3)'),
(22571,'002156','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (2)','AC-3 (3)(b)(2)','AC-3 (3)'),
(22572,'002157','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (3)','AC-3 (3)(b)(3)','AC-3 (3)'),
(22573,'002158','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (4)','AC-3 (3)(b)(4)','AC-3 (3)'),
(22574,'002159','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (4)','AC-3 (3)(b)(4)','AC-3 (3)'),
(22575,'002160','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (5)','AC-3 (3)(b)(5)','AC-3 (3)'),
(22576,'002161','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (c)','AC-3 (3)(c)','AC-3 (3)'),
(22577,'002162','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (c)','AC-3 (3)(c)','AC-3 (3)'),
(22578,'002163','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4)','AC-3 (4)','AC-3 (4)'),
(22579,'002164','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4) ','AC-3 (4)','AC-3 (4)'),
(22580,'002165','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4)','AC-3 (4)','AC-3 (4)'),
(22581,'002166','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22582,'002167','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22583,'002168','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22584,'002169','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22585,'002170','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22586,'002171','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22587,'002172','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22588,'002173','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22589,'002174','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22590,'002175','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22591,'002176','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3 (7)','AC-3 (7)'),
(22592,'002177','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (8)','AC-3 (8)','AC-3 (8)'),
(22593,'002178','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (8)','AC-3 (8)','AC-3 (8)'),
(22594,'002179','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (8)','AC-3 (8)','AC-3 (8)'),
(22595,'002180','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (a)','AC-3 (9)(a)','AC-3 (9)'),
(22596,'002181','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (a)','AC-3 (9)(a)','AC-3 (9)'),
(22597,'002182','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (a)','AC-3 (9)(a)','AC-3 (9)'),
(22598,'002183','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (b)','AC-3 (9)(b)','AC-3 (9)'),
(22599,'002184','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (b)','AC-3 (9)(b)','AC-3 (9)'),
(22600,'002185','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (10)','AC-3 (10)','AC-3 (10)'),
(22601,'002186','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (10)','AC-3 (10)','AC-3 (10)'),
(22602,'003014','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3)','AC-3 (3)','AC-3 (3)'),
(22603,'003015','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (c)','AC-3 (3)(c)','AC-3 (3)'),
(22604,'002187','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4 (1)','AC-4 (1)'),
(22605,'002188','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4 (1)','AC-4 (1)'),
(22606,'002189','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4 (1)','AC-4 (1)'),
(22607,'002190','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4 (1)','AC-4 (1)'),
(22608,'002191','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (2)','AC-4 (2)','AC-4 (2)'),
(22609,'002192','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (3)','AC-4 (3)','AC-4 (3)'),
(22610,'002193','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (4)','AC-4 (4)','AC-4 (4)'),
(22611,'002194','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (6)','AC-4 (6)','AC-4 (6)'),
(22612,'002195','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8)','AC-4 (8)','AC-4 (8)'),
(22613,'002196','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (9)','AC-4 (9)','AC-4 (9)'),
(22614,'002197','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (9)','AC-4 (9)','AC-4 (9)'),
(22615,'002198','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (9)','AC-4 (9)','AC-4 (9)'),
(22616,'002199','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (10)','AC-4 (10)','AC-4 (10)'),
(22617,'002200','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (12)','AC-4 (12)','AC-4 (12)'),
(22618,'002201','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (12)','AC-4 (12)','AC-4 (12)'),
(22619,'002202','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (13)','AC-4 (13)','AC-4 (13)'),
(22620,'002203','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4 (15)','AC-4 (15)'),
(22621,'002204','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4 (15)','AC-4 (15)'),
(22622,'002205','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (17)','AC-4 (17)','AC-4 (17)'),
(22623,'002206','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (17)','AC-4 (17)','AC-4 (17)'),
(22624,'002207','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (17)','AC-4 (17)','AC-4 (17)'),
(22625,'002208','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (17)','AC-4 (17)','AC-4 (17)'),
(22626,'002209','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (18)','AC-4 (18)','AC-4 (18)'),
(22627,'002210','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (18)','AC-4 (18)','AC-4 (18)'),
(22628,'002211','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (19)','AC-4 (19)','AC-4 (19)'),
(22629,'002212','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (20)','AC-4 (20)','AC-4 (20)'),
(22630,'002213','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (20)','AC-4 (20)','AC-4 (20)'),
(22631,'002214','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (20)','AC-4 (20)','AC-4 (20)'),
(22632,'002215','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (21)','AC-4 (21)','AC-4 (21)'),
(22633,'002216','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (21)','AC-4 (21)','AC-4 (21)'),
(22634,'002217','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (21)','AC-4 (21)','AC-4 (21)'),
(22635,'002218','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (22)','AC-4 (22)','AC-4 (22)'),
(22636,'002219','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 a','AC-5a.','AC-5'),
(22637,'002220','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 c','AC-5c.','AC-5'),
(22638,'002221','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1)','AC-6 (1)','AC-6 (1)'),
(22639,'002222','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1)','AC-6 (1)','AC-6 (1)'),
(22640,'002223','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1)','AC-6 (1)','AC-6 (1)'),
(22641,'002224','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6 (3)','AC-6 (3)'),
(22642,'002225','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (4)','AC-6 (4)','AC-6 (4)'),
(22643,'002226','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (5)','AC-6 (5)','AC-6 (5)'),
(22644,'002227','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (5)','AC-6 (5)','AC-6 (5)'),
(22645,'002228','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (a)','AC-6 (7)(a)','AC-6 (7)'),
(22646,'002229','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (a)','AC-6 (7)(a)','AC-6 (7)'),
(22647,'002230','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (a)','AC-6 (7)(a)','AC-6 (7)'),
(22648,'002231','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (b)','AC-6 (7)(b)','AC-6 (7)'),
(22649,'002232','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (8)','AC-6 (8)','AC-6 (8)'),
(22650,'002233','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (8)','AC-6 (8)','AC-6 (8)'),
(22651,'002234','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (9)','AC-6 (9)','AC-6 (9)'),
(22652,'002235','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (10)','AC-6 (10)','AC-6 (10)'),
(22653,'002236','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 b','AC-7b.','AC-7'),
(22654,'002237','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 b','AC-7b.','AC-7'),
(22655,'002238','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 b','AC-7b.','AC-7'),
(22656,'002239','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7 (2)','AC-7 (2)'),
(22657,'002240','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7 (2)','AC-7 (2)'),
(22658,'002241','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7 (2)','AC-7 (2)'),
(22659,'002242','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7 (2)','AC-7 (2)'),
(22660,'002243','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 1','AC-8a.1.','AC-8'),
(22661,'002244','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 2','AC-8a.2.','AC-8'),
(22662,'002245','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 3','AC-8a.3.','AC-8'),
(22663,'002246','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 4','AC-8a.4.','AC-8'),
(22664,'002247','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a','AC-8a.','AC-8'),
(22665,'002248','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 1','AC-8c.1.','AC-8'),
(22666,'002249','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (4)','AC-9 (4)','AC-9 (4)'),
(22667,'002250','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (4)','AC-9 (4)','AC-9 (4)'),
(22668,'002251','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (4)','AC-9 (4)','AC-9 (4)'),
(22669,'002252','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
(22670,'002253','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
(22671,'002255','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-14 a','AC-14a.','AC-14'),
(22672,'002256','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22673,'002257','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22674,'002258','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22675,'002259','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22676,'002260','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22677,'002261','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22678,'002262','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22679,'002263','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22680,'002264','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a.','AC-16'),
(22681,'002265','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 b','AC-16b.','AC-16'),
(22682,'002266','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 b','AC-16b.','AC-16'),
(22683,'002267','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c.','AC-16'),
(22684,'002268','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c.','AC-16'),
(22685,'002269','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c.','AC-16'),
(22686,'002270','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 d','AC-16d.','AC-16'),
(22687,'002271','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 d','AC-16d.','AC-16'),
(22688,'002272','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16 (1)','AC-16 (1)'),
(22689,'002273','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16 (1)','AC-16 (1)'),
(22690,'002274','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16 (1)','AC-16 (1)'),
(22691,'002275','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16 (1)','AC-16 (1)'),
(22692,'002276','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16 (2)','AC-16 (2)'),
(22693,'002277','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16 (2)','AC-16 (2)'),
(22694,'002278','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22695,'002279','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22696,'002280','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22697,'002281','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22698,'002282','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22699,'002283','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22700,'002284','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16 (3)','AC-16 (3)'),
(22701,'002285','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(22702,'002286','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(22703,'002287','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(22704,'002288','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(22705,'002289','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(22706,'002290','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16 (4)','AC-16 (4)'),
(22707,'002291','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22708,'002292','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22709,'002293','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22710,'002294','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22711,'002295','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22712,'002296','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22713,'002297','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22714,'002298','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16 (6)','AC-16 (6)'),
(22715,'002299','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (7)','AC-16 (7)','AC-16 (7)'),
(22716,'002300','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16 (8)','AC-16 (8)'),
(22717,'002301','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16 (8)','AC-16 (8)'),
(22718,'002302','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16 (8)','AC-16 (8)'),
(22719,'002303','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (9)','AC-16 (9)','AC-16 (9)'),
(22720,'002304','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (9)','AC-16 (9)','AC-16 (9)'),
(22721,'002305','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16 (10)','AC-16 (10)'),
(22722,'002306','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16 (10)','AC-16 (10)'),
(22723,'002307','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16 (10)','AC-16 (10)'),
(22724,'002308','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16 (10)','AC-16 (10)'),
(22725,'002309','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16 (10)','AC-16 (10)'),
(22726,'002310','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a.','AC-17'),
(22727,'002311','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a.','AC-17'),
(22728,'002312','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a.','AC-17'),
(22729,'002313','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (1)','AC-17 (1)','AC-17 (1)'),
(22730,'002314','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (1)','AC-17 (1)','AC-17 (1)'),
(22731,'002315','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (3)','AC-17 (3)','AC-17 (3)'),
(22732,'002316','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17 (4)(a)','AC-17 (4)'),
(22733,'002317','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17 (4)(a)','AC-17 (4)'),
(22734,'002318','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17 (4)(a)','AC-17 (4)'),
(22735,'002319','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (b)','AC-17 (4)(b)','AC-17 (4)'),
(22736,'002320','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (b)','AC-17 (4)(b)','AC-17 (4)'),
(22737,'002321','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (9)','AC-17 (9)','AC-17 (9)'),
(22738,'002322','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (9)','AC-17 (9)','AC-17 (9)'),
(22739,'002323','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 a','AC-18a.','AC-18'),
(22740,'002324','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (4)','AC-18 (4)','AC-18 (4)'),
(22741,'002325','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a.','AC-19'),
(22742,'002326','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a.','AC-19'),
(22743,'002327','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (c)','AC-19 (4)(c)','AC-19 (4)'),
(22744,'002328','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (c)','AC-19 (4)(c)','AC-19 (4)'),
(22745,'002329','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (5)','AC-19 (5)','AC-19 (5)'),
(22746,'002330','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (5)','AC-19 (5)','AC-19 (5)'),
(22747,'002331','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (5)','AC-19 (5)','AC-19 (5)'),
(22748,'002332','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 b','AC-20b.','AC-20'),
(22749,'002333','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (a)','AC-20 (1)(a)','AC-20 (1)'),
(22750,'002334','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (a)','AC-20 (1)(a)','AC-20 (1)'),
(22751,'002335','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (a)','AC-20 (1)(a)','AC-20 (1)'),
(22752,'002336','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (a)','AC-20 (1)(a)','AC-20 (1)'),
(22753,'002337','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (b)','AC-20 (1)(b)','AC-20 (1)'),
(22754,'002338','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (3)','AC-20 (3)','AC-20 (3)'),
(22755,'002339','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (4)','AC-20 (4)','AC-20 (4)'),
(22756,'002340','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (4)','AC-20 (4)','AC-20 (4)'),
(22757,'002341','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 (2)','AC-21 (2)','AC-21 (2)'),
(22758,'002342','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 (2)','AC-21 (2)','AC-21 (2)'),
(22759,'002343','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
(22760,'002344','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
(22761,'002345','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
(22762,'002346','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
(22763,'002347','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
(22764,'002348','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24','AC-24','AC-24'),
(22765,'002349','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24','AC-24','AC-24'),
(22766,'002350','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24 (1)','AC-24 (1)'),
(22767,'002351','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24 (1)','AC-24 (1)'),
(22768,'002352','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24 (1)','AC-24 (1)'),
(22769,'002353','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24 (1)','AC-24 (1)'),
(22770,'002354','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (2)','AC-24 (2)','AC-24 (2)'),
(22771,'002355','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (2)','AC-24 (2)','AC-24 (2)'),
(22772,'002356','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
(22773,'002357','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
(22774,'002358','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
(22775,'002359','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
(22776,'002048','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1','AT-1a.1.','AT-1'),
(22777,'002049','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 2','AT-1a.2.','AT-1'),
(22778,'002055','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (2)','AT-2 (2)','AT-2 (2)'),
(22779,'002050','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3 (1)','AT-3 (1)'),
(22780,'002051','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3 (2)','AT-3 (2)'),
(22781,'002052','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (3)','AT-3 (3)','AT-3 (3)'),
(22782,'002053','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (4)','AT-3 (4)','AT-3 (4)'),
(22783,'002054','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (4)','AT-3 (4)','AT-3 (4)'),
(22784,'001831','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1','AU-1a.1.','AU-1'),
(22785,'001832','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1','AU-1a.1.','AU-1'),
(22786,'001833','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a.2.','AU-1'),
(22787,'001834','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a.2.','AU-1'),
(22788,'001835','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 1','AU-1b.1.','AU-1'),
(22789,'001836','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 1','AU-1b.1.','AU-1'),
(22790,'001837','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 1','AU-1b.1.','AU-1'),
(22791,'001838','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 1','AU-1b.1.','AU-1'),
(22792,'001839','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 2','AU-1b.2.','AU-1'),
(22793,'001840','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 2','AU-1b.2.','AU-1'),
(22794,'001841','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 2','AU-1b.2.','AU-1'),
(22795,'001842','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b 2','AU-1b.2.','AU-1'),
(22796,'001930','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1','AU-1a.1.','AU-1'),
(22797,'001931','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a.2.','AU-1'),
(22798,'001843','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 (3)','AU-2 (3)','AU-2 (3)'),
(22799,'001844','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (2)','AU-3 (2)','AU-3 (2)'),
(22800,'001845','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (2)','AU-3 (2)','AU-3 (2)'),
(22801,'001846','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (2)','AU-3 (2)','AU-3 (2)'),
(22802,'001847','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (2)','AU-3 (2)','AU-3 (2)'),
(22803,'001848','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-4','AU-4','AU-4'),
(22804,'001849','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-4','AU-4','AU-4'),
(22805,'001850','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-4 (1)','AU-4 (1)','AU-4 (1)'),
(22806,'001851','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-4 (1)','AU-4 (1)','AU-4 (1)'),
(22807,'001852','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5 (1)','AU-5 (1)'),
(22808,'001853','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5 (1)','AU-5 (1)'),
(22809,'001854','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5 (1)','AU-5 (1)'),
(22810,'001855','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5 (1)','AU-5 (1)'),
(22811,'001856','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5 (2)','AU-5 (2)'),
(22812,'001857','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5 (2)','AU-5 (2)'),
(22813,'001858','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5 (2)','AU-5 (2)'),
(22814,'001859','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (3)','AU-5 (3)','AU-5 (3)'),
(22815,'001860','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (4)','AU-5 (4)','AU-5 (4)'),
(22816,'001861','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (4)','AU-5 (4)','AU-5 (4)'),
(22817,'002907','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (4)','AU-5 (4)','AU-5 (4)'),
(22818,'001862','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a.','AU-6'),
(22819,'001863','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 b','AU-6b.','AU-6'),
(22820,'001864','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (1)','AU-6 (1)','AU-6 (1)'),
(22821,'001865','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (1)','AU-6 (1)','AU-6 (1)'),
(22822,'001866','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (5)','AU-6 (5)','AU-6 (5)'),
(22823,'001867','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (5)','AU-6 (5)','AU-6 (5)'),
(22824,'001868','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (7)','AU-6 (7)','AU-6 (7)'),
(22825,'001869','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (7)','AU-6 (7)','AU-6 (7)'),
(22826,'001870','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (8)','AU-6 (8)','AU-6 (8)'),
(22827,'001871','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (9)','AU-6 (9)','AU-6 (9)'),
(22828,'001872','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (10)','AU-6 (10)','AU-6 (10)'),
(22829,'001873','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (10)','AU-6 (10)','AU-6 (10)'),
(22830,'001874','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (10)','AU-6 (10)','AU-6 (10)'),
(22831,'001875','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a.','AU-7'),
(22832,'001876','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a.','AU-7'),
(22833,'001877','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a.','AU-7'),
(22834,'001878','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a.','AU-7'),
(22835,'001879','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a.','AU-7'),
(22836,'001880','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a.','AU-7'),
(22837,'001881','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 b','AU-7b.','AU-7'),
(22838,'001882','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 b','AU-7b.','AU-7'),
(22839,'001883','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (1)','AU-7 (1)','AU-7 (1)'),
(22840,'001884','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (2)','AU-7 (2)','AU-7 (2)'),
(22841,'001885','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (2)','AU-7 (2)','AU-7 (2)'),
(22842,'001886','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (2)','AU-7 (2)','AU-7 (2)'),
(22843,'001887','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (2)','AU-7 (2)','AU-7 (2)'),
(22844,'001888','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 b','AU-8b.','AU-8'),
(22845,'001889','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 b','AU-8b.','AU-8'),
(22846,'001890','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 b','AU-8b.','AU-8'),
(22847,'001891','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 (1) (a)','AU-8 (1)(a)','AU-8 (1)'),
(22848,'001892','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 (1) (b)','AU-8 (1)(b)','AU-8 (1)'),
(22849,'001893','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 (2)','AU-8 (2)','AU-8 (2)'),
(22850,'002046','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 (1) (b)','AU-8 (1)(b)','AU-8 (1)'),
(22851,'001894','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (4)','AU-9 (4)','AU-9 (4)'),
(22852,'001895','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (5)','AU-9 (5)','AU-9 (5)'),
(22853,'001896','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (5)','AU-9 (5)','AU-9 (5)'),
(22854,'001897','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (6)','AU-9 (6)','AU-9 (6)'),
(22855,'001898','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (6)','AU-9 (6)','AU-9 (6)'),
(22856,'001899','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10','AU-10','AU-10'),
(22857,'001900','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (1) (a)','AU-10 (1)(a)','AU-10 (1)'),
(22858,'001901','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (1) (a)','AU-10 (1)(a)','AU-10 (1)'),
(22859,'001902','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (1) (b)','AU-10 (1)(b)','AU-10 (1)'),
(22860,'001903','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (a)','AU-10 (2)(a)','AU-10 (2)'),
(22861,'001904','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (a)','AU-10 (2)(a)','AU-10 (2)'),
(22862,'001905','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (b)','AU-10 (2)(b)','AU-10 (2)'),
(22863,'001906','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (b)','AU-10 (2)(b)','AU-10 (2)'),
(22864,'001907','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (a)','AU-10 (4)(a)','AU-10 (4)'),
(22865,'001908','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (b)','AU-10 (4)(b)','AU-10 (4)'),
(22866,'001909','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (b)','AU-10 (4)(b)','AU-10 (4)'),
(22867,'002044','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-11 (1)','AU-11 (1)','AU-11 (1)'),
(22868,'002045','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-11 (1)','AU-11 (1)','AU-11 (1)'),
(22869,'001910','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 b','AU-12b.','AU-12'),
(22870,'001911','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12 (3)','AU-12 (3)'),
(22871,'001912','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12 (3)','AU-12 (3)'),
(22872,'001913','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12 (3)','AU-12 (3)'),
(22873,'001914','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12 (3)','AU-12 (3)'),
(22874,'002047','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12 (3)','AU-12 (3)'),
(22875,'001915','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-13','AU-13','AU-13'),
(22876,'001916','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (1)','AU-13 (1)','AU-13 (1)'),
(22877,'001917','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (2)','AU-13 (2)','AU-13 (2)'),
(22878,'001918','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (2)','AU-13 (2)','AU-13 (2)'),
(22879,'001919','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-14','AU-14','AU-14'),
(22880,'001920','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 (3)','AU-14 (3)','AU-14 (3)'),
(22881,'001921','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-15','AU-15','AU-15'),
(22882,'001922','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-15','AU-15','AU-15'),
(22883,'001923','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16','AU-16','AU-16'),
(22884,'001924','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16','AU-16','AU-16'),
(22885,'001925','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16','AU-16','AU-16'),
(22886,'001926','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (1)','AU-16 (1)','AU-16 (1)'),
(22887,'001927','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (2)','AU-16 (2)','AU-16 (2)'),
(22888,'001928','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (2)','AU-16 (2)','AU-16 (2)'),
(22889,'001929','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (2)','AU-16 (2)','AU-16 (2)'),
(22890,'002060','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1','CA-1a.1.','CA-1'),
(22891,'002061','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1','CA-1a.1.','CA-1'),
(22892,'002062','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a.2.','CA-1'),
(22893,'002063','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (1)','CA-2 (1)','CA-2 (1)'),
(22894,'002064','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2 (2)','CA-2 (2)'),
(22895,'002065','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2 (2)','CA-2 (2)'),
(22896,'002066','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2 (3)','CA-2 (3)'),
(22897,'002067','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2 (3)','CA-2 (3)'),
(22898,'002068','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2 (3)','CA-2 (3)'),
(22899,'002069','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2 (3)','CA-2 (3)'),
(22900,'002070','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 a 3','CA-2a.3.','CA-2'),
(22901,'002071','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 d','CA-2d.','CA-2'),
(22902,'002072','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (1)','CA-3 (1)','CA-3 (1)'),
(22903,'002073','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (1)','CA-3 (1)','CA-3 (1)'),
(22904,'002074','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (2)','CA-3 (2)','CA-3 (2)'),
(22905,'002075','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (3)','CA-3 (3)','CA-3 (3)'),
(22906,'002076','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (3)','CA-3 (3)','CA-3 (3)'),
(22907,'002077','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (3)','CA-3 (3)','CA-3 (3)'),
(22908,'002078','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (4)','CA-3 (4)','CA-3 (4)'),
(22909,'002079','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (4)','CA-3 (4)','CA-3 (4)'),
(22910,'002080','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (5)','CA-3 (5)','CA-3 (5)'),
(22911,'002081','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (5)','CA-3 (5)','CA-3 (5)'),
(22912,'002082','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (5)','CA-3 (5)','CA-3 (5)'),
(22913,'002083','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 c','CA-3c.','CA-3'),
(22914,'002084','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 c','CA-3c.','CA-3'),
(22915,'002085','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (1)','CA-7 (1)','CA-7 (1)'),
(22916,'002086','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (3)','CA-7 (3)','CA-7 (3)'),
(22917,'002087','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 a','CA-7a.','CA-7'),
(22918,'002088','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 b','CA-7b.','CA-7'),
(22919,'002089','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 b','CA-7b.','CA-7'),
(22920,'002090','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 d','CA-7d.','CA-7'),
(22921,'002091','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 e','CA-7e.','CA-7'),
(22922,'002092','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 f','CA-7f.','CA-7'),
(22923,'002093','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8','CA-8','CA-8'),
(22924,'002094','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8','CA-8','CA-8'),
(22925,'002095','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8','CA-8','CA-8'),
(22926,'002096','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (1)','CA-8 (1)','CA-8 (1)'),
(22927,'002097','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (2)','CA-8 (2)','CA-8 (2)'),
(22928,'002098','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (2)','CA-8 (2)','CA-8 (2)'),
(22929,'002099','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (2)','CA-8 (2)','CA-8 (2)'),
(22930,'002100','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (1)','CA-9 (1)','CA-9 (1)'),
(22931,'002101','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (a)','CA-9(a)','CA-9'),
(22932,'002102','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (a)','CA-9(a)','CA-9'),
(22933,'002103','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
(22934,'002104','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
(22935,'002105','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
(22936,'001820','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1','CM-1a.1.','CM-1'),
(22937,'001821','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1','CM-1a.1.','CM-1'),
(22938,'001822','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1','CM-1a.1.','CM-1'),
(22939,'001823','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a.2.','CM-1'),
(22940,'001824','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a.2.','CM-1'),
(22941,'001825','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a.2.','CM-1'),
(22942,'001736','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (3)','CM-2 (3)','CM-2 (3)'),
(22943,'001737','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (a)','CM-2 (7)(a)','CM-2 (7)'),
(22944,'001738','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (a)','CM-2 (7)(a)','CM-2 (7)'),
(22945,'001739','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (a)','CM-2 (7)(a)','CM-2 (7)'),
(22946,'001815','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (b)','CM-2 (7)(b)','CM-2 (7)'),
(22947,'001816','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (b)','CM-2 (7)(b)','CM-2 (7)'),
(22948,'001740','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 b','CM-3b.','CM-3'),
(22949,'001741','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 c','CM-3c.','CM-3'),
(22950,'001742','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (b)','CM-3 (1)(b)','CM-3 (1)'),
(22951,'001743','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (5)','CM-3 (5)','CM-3 (5)'),
(22952,'001744','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (5)','CM-3 (5)','CM-3 (5)'),
(22953,'001745','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (6)','CM-3 (6)','CM-3 (6)'),
(22954,'001746','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (6)','CM-3 (6)','CM-3 (6)'),
(22955,'001819','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 d','CM-3d.','CM-3'),
(22956,'002056','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 e','CM-3e.','CM-3'),
(22957,'002057','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (f)','CM-3 (1)(f)','CM-3 (1)'),
(22958,'002058','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (f)','CM-3 (1)(f)','CM-3 (1)'),
(22959,'001817','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (1)','CM-4 (1)','CM-4 (1)'),
(22960,'001818','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (1)','CM-4 (1)','CM-4 (1)'),
(22961,'001747','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (3)','CM-5 (3)','CM-5 (3)'),
(22962,'001748','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (3)','CM-5 (3)','CM-5 (3)'),
(22963,'001749','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (3)','CM-5 (3)','CM-5 (3)'),
(22964,'001750','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (3)','CM-5 (3)','CM-5 (3)'),
(22965,'001751','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5 (4)','CM-5 (4)'),
(22966,'001752','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5 (4)','CM-5 (4)'),
(22967,'001753','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (a)','CM-5 (5)(a)','CM-5 (5)'),
(22968,'001754','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (a)','CM-5 (5)(a)','CM-5 (5)'),
(22969,'001813','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (1)','CM-5 (1)','CM-5 (1)'),
(22970,'001814','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (1)','CM-5 (1)','CM-5 (1)'),
(22971,'001826','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (2)','CM-5 (2)','CM-5 (2)'),
(22972,'001827','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (b)','CM-5 (5)(b)','CM-5 (5)'),
(22973,'001828','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (b)','CM-5 (5)(b)','CM-5 (5)'),
(22974,'001829','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (b)','CM-5 (5)(b)','CM-5 (5)'),
(22975,'001830','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (b)','CM-5 (5)(b)','CM-5 (5)'),
(22976,'001755','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c.','CM-6'),
(22977,'001756','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c.','CM-6'),
(22978,'001757','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (2)','CM-6 (2)','CM-6 (2)'),
(22979,'001758','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (2)','CM-6 (2)','CM-6 (2)'),
(22980,'001759','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (2)','CM-6 (2)','CM-6 (2)'),
(22981,'002059','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6 (1)','CM-6 (1)'),
(22982,'001760','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (a)','CM-7 (1)(a)','CM-7 (1)'),
(22983,'001761','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (b)','CM-7 (1)(b)','CM-7 (1)'),
(22984,'001762','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (b)','CM-7 (1)(b)','CM-7 (1)'),
(22985,'001763','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (2)','CM-7 (2)','CM-7 (2)'),
(22986,'001764','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (2)','CM-7 (2)','CM-7 (2)'),
(22987,'001765','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (a)','CM-7 (4)(a)','CM-7 (4)'),
(22988,'001766','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (a)','CM-7 (4)(a)','CM-7 (4)'),
(22989,'001767','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (b)','CM-7 (4)(b)','CM-7 (4)'),
(22990,'001768','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (c)','CM-7 (4)(c)','CM-7 (4)'),
(22991,'001769','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (c)','CM-7 (4)(c)','CM-7 (4)'),
(22992,'001770','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (c)','CM-7 (4)(c)','CM-7 (4)'),
(22993,'001771','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (c)','CM-7 (4)(c)','CM-7 (4)'),
(22994,'001772','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (a)','CM-7 (5)(a)','CM-7 (5)'),
(22995,'001773','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (a)','CM-7 (5)(a)','CM-7 (5)'),
(22996,'001774','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (b)','CM-7 (5)(b)','CM-7 (5)'),
(22997,'001775','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (c)','CM-7 (5)(c)','CM-7 (5)'),
(22998,'001776','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (c)','CM-7 (5)(c)','CM-7 (5)'),
(22999,'001777','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (c)','CM-7 (5)(c)','CM-7 (5)'),
(23000,'001778','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (c)','CM-7 (5)(c)','CM-7 (5)'),
(23001,'001779','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 b','CM-8b.','CM-8'),
(23002,'001780','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 b','CM-8b.','CM-8'),
(23003,'001781','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 b','CM-8b.','CM-8'),
(23004,'001782','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 b','CM-8b.','CM-8'),
(23005,'001783','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (b)','CM-8 (3)(b)','CM-8 (3)'),
(23006,'001784','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (b)','CM-8 (3)(b)','CM-8 (3)'),
(23007,'001785','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (7)','CM-8 (7)','CM-8 (7)'),
(23008,'001786','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (8)','CM-8 (8)','CM-8 (8)'),
(23009,'001787','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (9) (a)','CM-8 (9)(a)','CM-8 (9)'),
(23010,'001788','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (9) (a)','CM-8 (9)(a)','CM-8 (9)'),
(23011,'001789','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (9) (b)','CM-8 (9)(b)','CM-8 (9)'),
(23012,'001790','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b.','CM-9'),
(23013,'001791','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b.','CM-9'),
(23014,'001792','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b.','CM-9'),
(23015,'001793','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b.','CM-9'),
(23016,'001794','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b.','CM-9'),
(23017,'001795','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b.','CM-9'),
(23018,'001796','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c.','CM-9'),
(23019,'001797','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c.','CM-9'),
(23020,'001798','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c.','CM-9'),
(23021,'001799','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 d','CM-9d.','CM-9'),
(23022,'001800','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 d','CM-9d.','CM-9'),
(23023,'001801','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 d','CM-9d.','CM-9'),
(23024,'001726','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a.','CM-10'),
(23025,'001727','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a.','CM-10'),
(23026,'001728','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a.','CM-10'),
(23027,'001729','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a.','CM-10'),
(23028,'001730','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b.','CM-10'),
(23029,'001731','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b.','CM-10'),
(23030,'001732','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 c','CM-10c.','CM-10'),
(23031,'001733','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 c','CM-10c.','CM-10'),
(23032,'001734','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 (1)','CM-10 (1)','CM-10 (1)'),
(23033,'001735','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 (1)','CM-10 (1)','CM-10 (1)'),
(23034,'001802','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b.','CM-10'),
(23035,'001803','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b.','CM-10'),
(23036,'001804','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 a','CM-11a.','CM-11'),
(23037,'001805','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 a','CM-11a.','CM-11'),
(23038,'001806','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 b','CM-11b.','CM-11'),
(23039,'001807','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 b','CM-11b.','CM-11'),
(23040,'001808','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 c','CM-11c.','CM-11'),
(23041,'001809','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 c','CM-11c.','CM-11'),
(23042,'001810','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 (1)','CM-11 (1)','CM-11 (1)'),
(23043,'001811','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 (1)','CM-11 (1)','CM-11 (1)'),
(23044,'001812','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 (2)','CM-11 (2)','CM-11 (2)'),
(23045,'002825','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1','CP-1a.1.','CP-1'),
(23046,'002826','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 2','CP-1a.2.','CP-1'),
(23047,'002827','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (7)','CP-2 (7)','CP-2 (7)'),
(23048,'002828','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (8)','CP-2 (8)','CP-2 (8)'),
(23049,'002829','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (8)','CP-2 (8)','CP-2 (8)'),
(23050,'002830','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 6','CP-2a.6.','CP-2'),
(23051,'002831','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 f','CP-2f.','CP-2'),
(23052,'002832','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 g','CP-2g.','CP-2'),
(23053,'002833','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a','CP-3a.','CP-3'),
(23054,'002834','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 b','CP-3b.','CP-3'),
(23055,'002835','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (2) (b)','CP-4 (2)(b)','CP-4 (2)'),
(23056,'002836','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 b','CP-6b.','CP-6'),
(23057,'002837','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (6)','CP-7 (6)','CP-7 (6)'),
(23058,'002838','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (6)','CP-7 (6)','CP-7 (6)'),
(23059,'002839','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a.','CP-7'),
(23060,'002840','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
(23061,'002841','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
(23062,'002842','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (b)','CP-8 (4)(b)','CP-8 (4)'),
(23063,'002843','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c) ','CP-8 (4)(c)','CP-8 (4)'),
(23064,'002844','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c) ','CP-8 (4)(c)','CP-8 (4)'),
(23065,'002845','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c) ','CP-8 (4)(c)','CP-8 (4)'),
(23066,'002846','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c) ','CP-8 (4)(c)','CP-8 (4)'),
(23067,'002847','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (5)','CP-8 (5)','CP-8 (5)'),
(23068,'002848','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (5)','CP-8 (5)','CP-8 (5)'),
(23069,'002849','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (3)','CP-9 (3)','CP-9 (3)'),
(23070,'002850','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (3)','CP-9 (3)','CP-9 (3)'),
(23071,'002851','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (7)','CP-9 (7)','CP-9 (7)'),
(23072,'002852','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (7)','CP-9 (7)','CP-9 (7)'),
(23073,'002853','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-11','CP-11','CP-11'),
(23074,'002854','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-11','CP-11','CP-11'),
(23075,'002855','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-12','CP-12','CP-12'),
(23076,'002856','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-12','CP-12','CP-12'),
(23077,'002857','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-12','CP-12','CP-12'),
(23078,'002858','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-13','CP-13','CP-13'),
(23079,'002859','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-13','CP-13','CP-13'),
(23080,'002860','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','CP-13','CP-13','CP-13'),
(23081,'001932','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1','IA-1a.1.','IA-1'),
(23082,'001933','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1','IA-1a.1.','IA-1'),
(23083,'001934','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 2','IA-1a.2.','IA-1'),
(23084,'001935','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (6)','IA-2 (6)','IA-2 (6)'),
(23085,'001936','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (6)','IA-2 (6)','IA-2 (6)'),
(23086,'001937','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (6)','IA-2 (6)','IA-2 (6)'),
(23087,'001938','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (7)','IA-2 (7)','IA-2 (7)'),
(23088,'001939','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (7)','IA-2 (7)','IA-2 (7)'),
(23089,'001940','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (7)','IA-2 (7)','IA-2 (7)'),
(23090,'001941','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (8)','IA-2 (8)','IA-2 (8)'),
(23091,'001942','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (9)','IA-2 (9)','IA-2 (9)'),
(23092,'001943','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2 (10)','IA-2 (10)'),
(23093,'001944','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2 (10)','IA-2 (10)'),
(23094,'001945','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2 (10)','IA-2 (10)'),
(23095,'001946','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2 (10)','IA-2 (10)'),
(23096,'001947','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (11)','IA-2 (11)','IA-2 (11)'),
(23097,'001948','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (11)','IA-2 (11)','IA-2 (11)'),
(23098,'001949','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (11)','IA-2 (11)','IA-2 (11)'),
(23099,'001950','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (11)','IA-2 (11)','IA-2 (11)'),
(23100,'001951','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (11)','IA-2 (11)','IA-2 (11)'),
(23101,'001952','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (11)','IA-2 (11)','IA-2 (11)'),
(23102,'001953','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (12)','IA-2 (12)','IA-2 (12)'),
(23103,'001954','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (12)','IA-2 (12)','IA-2 (12)'),
(23104,'001955','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (13)','IA-2 (13)','IA-2 (13)'),
(23105,'001956','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (13)','IA-2 (13)','IA-2 (13)'),
(23106,'001957','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (13)','IA-2 (13)','IA-2 (13)'),
(23107,'001958','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3','IA-3','IA-3'),
(23108,'001959','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (1)','IA-3 (1)','IA-3 (1)'),
(23109,'001960','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3 (3)(a)','IA-3 (3)'),
(23110,'001961','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3 (3)(a)','IA-3 (3)'),
(23111,'001962','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3 (3)(a)','IA-3 (3)'),
(23112,'001963','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3 (3)(a)','IA-3 (3)'),
(23113,'001964','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3 (4)','IA-3 (4)'),
(23114,'001965','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3 (4)','IA-3 (4)'),
(23115,'001966','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3 (4)','IA-3 (4)'),
(23116,'001967','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (1)','IA-3 (1)','IA-3 (1)'),
(23117,'001968','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3 (4)','IA-3 (4)'),
(23118,'001969','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3 (4)','IA-3 (4)'),
(23119,'001970','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 a','IA-4a.','IA-4'),
(23120,'001971','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 a','IA-4a.','IA-4'),
(23121,'001972','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 b','IA-4b.','IA-4'),
(23122,'001973','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 c','IA-4c.','IA-4'),
(23123,'001974','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 d','IA-4d.','IA-4'),
(23124,'001975','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 d','IA-4d.','IA-4'),
(23125,'001976','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (5)','IA-4 (5)','IA-4 (5)'),
(23126,'001977','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (6)','IA-4 (6)','IA-4 (6)'),
(23127,'001978','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (6)','IA-4 (6)','IA-4 (6)'),
(23128,'001979','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (7)','IA-4 (7)','IA-4 (7)'),
(23129,'002040','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (2)','IA-4 (2)','IA-4 (2)'),
(23130,'001980','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 a','IA-5a.','IA-5'),
(23131,'001981','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23132,'001982','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23133,'001983','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23134,'001984','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23135,'001985','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23136,'001986','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23137,'001987','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23138,'001988','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d.','IA-5'),
(23139,'001989','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 e','IA-5e.','IA-5'),
(23140,'001990','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 j','IA-5j.','IA-5'),
(23141,'001991','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (d)','IA-5 (2)(d)','IA-5 (2)'),
(23142,'001992','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (3)','IA-5 (3)','IA-5 (3)'),
(23143,'001993','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (3)','IA-5 (3)','IA-5 (3)'),
(23144,'001994','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (3)','IA-5 (3)','IA-5 (3)'),
(23145,'001995','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (3)','IA-5 (3)','IA-5 (3)'),
(23146,'001996','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (4)','IA-5 (4)','IA-5 (4)'),
(23147,'001997','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (4)','IA-5 (4)','IA-5 (4)'),
(23148,'001998','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (5)','IA-5 (5)','IA-5 (5)'),
(23149,'001999','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (9)','IA-5 (9)','IA-5 (9)'),
(23150,'002000','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (9)','IA-5 (9)','IA-5 (9)'),
(23151,'002001','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (10)','IA-5 (10)','IA-5 (10)'),
(23152,'002002','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (11)','IA-5 (11)','IA-5 (11)'),
(23153,'002003','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (11)','IA-5 (11)','IA-5 (11)'),
(23154,'002004','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (12)','IA-5 (12)','IA-5 (12)'),
(23155,'002005','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (12)','IA-5 (12)','IA-5 (12)'),
(23156,'002006','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (13)','IA-5 (13)','IA-5 (13)'),
(23157,'002007','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (13)','IA-5 (13)','IA-5 (13)'),
(23158,'002008','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (14)','IA-5 (14)','IA-5 (14)'),
(23159,'002041','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (f)','IA-5 (1)(f)','IA-5 (1)'),
(23160,'002042','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 h','IA-5h.','IA-5'),
(23161,'002043','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (15)','IA-5 (15)','IA-5 (15)'),
(23162,'002365','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 i','IA-5i.','IA-5'),
(23163,'002366','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 i','IA-5i.','IA-5'),
(23164,'002367','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (7)','IA-5 (7)','IA-5 (7)'),
(23165,'002009','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (1)','IA-8 (1)','IA-8 (1)'),
(23166,'002010','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (1)','IA-8 (1)','IA-8 (1)'),
(23167,'002011','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (2)','IA-8 (2)','IA-8 (2)'),
(23168,'002012','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (3)','IA-8 (3)','IA-8 (3)'),
(23169,'002013','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (3)','IA-8 (3)','IA-8 (3)'),
(23170,'002014','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (4)','IA-8 (4)','IA-8 (4)'),
(23171,'002015','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (5)','IA-8 (5)','IA-8 (5)'),
(23172,'002016','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (5)','IA-8 (5)','IA-8 (5)'),
(23173,'002017','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
(23174,'002018','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
(23175,'002019','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
(23176,'002020','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
(23177,'002021','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
(23178,'002022','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
(23179,'002023','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (1)','IA-9 (1)','IA-9 (1)'),
(23180,'002024','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (1)','IA-9 (1)','IA-9 (1)'),
(23181,'002025','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (1)','IA-9 (1)','IA-9 (1)'),
(23182,'002026','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (1)','IA-9 (1)','IA-9 (1)'),
(23183,'002027','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (1)','IA-9 (1)','IA-9 (1)'),
(23184,'002028','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (1)','IA-9 (1)','IA-9 (1)'),
(23185,'002029','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (2)','IA-9 (2)','IA-9 (2)'),
(23186,'002030','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (2)','IA-9 (2)','IA-9 (2)'),
(23187,'002031','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (2)','IA-9 (2)','IA-9 (2)'),
(23188,'002032','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-9 (2)','IA-9 (2)','IA-9 (2)'),
(23189,'002033','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-10','IA-10','IA-10'),
(23190,'002034','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-10','IA-10','IA-10'),
(23191,'002035','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-10','IA-10','IA-10'),
(23192,'002036','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-11','IA-11','IA-11'),
(23193,'002037','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-11','IA-11','IA-11'),
(23194,'002038','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-11','IA-11','IA-11'),
(23195,'002039','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IA-11','IA-11','IA-11'),
(23196,'002776','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1','IR-1a.1.','IR-1'),
(23197,'002777','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 2','IR-1a.2.','IR-1'),
(23198,'002778','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a','IR-2a.','IR-2'),
(23199,'002779','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 b','IR-2b.','IR-2'),
(23200,'002780','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (2)','IR-3 (2)','IR-3 (2)'),
(23201,'002781','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (2)','IR-4 (2)','IR-4 (2)'),
(23202,'002782','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (6)','IR-4 (6)','IR-4 (6)'),
(23203,'002783','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (7)','IR-4 (7)','IR-4 (7)'),
(23204,'002784','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (7)','IR-4 (7)','IR-4 (7)'),
(23205,'002785','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (8)','IR-4 (8)','IR-4 (8)'),
(23206,'002786','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (8)','IR-4 (8)','IR-4 (8)'),
(23207,'002787','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (8)','IR-4 (8)','IR-4 (8)'),
(23208,'002788','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (9)','IR-4 (9)','IR-4 (9)'),
(23209,'002789','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (9)','IR-4 (9)','IR-4 (9)'),
(23210,'002790','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (10)','IR-4 (10)','IR-4 (10)'),
(23211,'002791','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 b','IR-6b.','IR-6'),
(23212,'002792','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (2)','IR-6 (2)','IR-6 (2)'),
(23213,'002793','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (3)','IR-6 (3)','IR-6 (3)'),
(23214,'002794','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a','IR-8a.','IR-8'),
(23215,'002795','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 1','IR-8a.1.','IR-8'),
(23216,'002796','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 2','IR-8a.2.','IR-8'),
(23217,'002797','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 3','IR-8a.3.','IR-8'),
(23218,'002798','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 4','IR-8a.4.','IR-8'),
(23219,'002799','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 5','IR-8a.5.','IR-8'),
(23220,'002800','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 6','IR-8a.6.','IR-8'),
(23221,'002801','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 7','IR-8a.7.','IR-8'),
(23222,'002802','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 8','IR-8a.8.','IR-8'),
(23223,'002803','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 e','IR-8e.','IR-8'),
(23224,'002804','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 f','IR-8f.','IR-8'),
(23225,'002805','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 a','IR-9a.','IR-9'),
(23226,'002806','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 b','IR-9b.','IR-9'),
(23227,'002807','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 b','IR-9b.','IR-9'),
(23228,'002808','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 c','IR-9c.','IR-9'),
(23229,'002809','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 d','IR-9d.','IR-9'),
(23230,'002810','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 e','IR-9e.','IR-9'),
(23231,'002811','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 f','IR-9f.','IR-9'),
(23232,'002812','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 f','IR-9f.','IR-9'),
(23233,'002813','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (1)','IR-9 (1)','IR-9 (1)'),
(23234,'002814','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (1)','IR-9 (1)','IR-9 (1)'),
(23235,'002815','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (1)','IR-9 (1)','IR-9 (1)'),
(23236,'002816','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (2)','IR-9 (2)','IR-9 (2)'),
(23237,'002817','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (2)','IR-9 (2)','IR-9 (2)'),
(23238,'002818','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (3)','IR-9 (3)','IR-9 (3)'),
(23239,'002819','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (3)','IR-9 (3)','IR-9 (3)'),
(23240,'002820','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (4)','IR-9 (4)','IR-9 (4)'),
(23241,'002821','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (4)','IR-9 (4)','IR-9 (4)'),
(23242,'002822','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IR-10','IR-10','IR-10'),
(23243,'002861','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1','MA-1a.1.','MA-1'),
(23244,'002862','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 2','MA-1a.2.','MA-1'),
(23245,'002863','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (a)','MA-2 (2)(a)','MA-2 (2)'),
(23246,'002864','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (b)','MA-2 (2)(b)','MA-2 (2)'),
(23247,'002865','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (b)','MA-2 (2)(b)','MA-2 (2)'),
(23248,'002866','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23249,'002867','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a ','MA-2a..','MA-2'),
(23250,'002868','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23251,'002869','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23252,'002870','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23253,'002871','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23254,'002872','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23255,'002873','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a.','MA-2'),
(23256,'002874','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 c','MA-2c.','MA-2'),
(23257,'002875','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 f','MA-2f.','MA-2'),
(23258,'002876','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 f','MA-2f.','MA-2'),
(23259,'002905','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (a)','MA-2 (2)(a)','MA-2 (2)'),
(23260,'002877','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (a)','MA-3 (3)(a)','MA-3 (3)'),
(23261,'002878','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (b)','MA-3 (3)(b)','MA-3 (3)'),
(23262,'002879','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (c)','MA-3 (3)(c)','MA-3 (3)'),
(23263,'002880','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (c)','MA-3 (3)(c)','MA-3 (3)'),
(23264,'002881','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (d)','MA-3 (3)(d)','MA-3 (3)'),
(23265,'002882','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (d)','MA-3 (3)(d)','MA-3 (3)'),
(23266,'002883','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (4)','MA-3 (4)','MA-3 (4)'),
(23267,'002884','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (1) (a)','MA-4 (1)(a)','MA-4 (1)'),
(23268,'002885','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (1) (a)','MA-4 (1)(a)','MA-4 (1)'),
(23269,'002886','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (1) (b)','MA-4 (1)(b)','MA-4 (1)'),
(23270,'002887','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (a)','MA-4 (4)(a)','MA-4 (4)'),
(23271,'002888','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (a)','MA-4 (5)(a)','MA-4 (5)'),
(23272,'002889','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (b)','MA-4 (5)(b)','MA-4 (5)'),
(23273,'002890','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (6)','MA-4 (6)','MA-4 (6)'),
(23274,'002891','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (7)','MA-4 (7)','MA-4 (7)'),
(23275,'003123','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (6)','MA-4 (6)','MA-4 (6)'),
(23276,'002892','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (b)','MA-5 (1)(b)','MA-5 (1)'),
(23277,'002893','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (5)','MA-5 (5)','MA-5 (5)'),
(23278,'002894','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 b','MA-5b.','MA-5'),
(23279,'002895','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 c','MA-5c.','MA-5'),
(23280,'002896','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6','MA-6','MA-6'),
(23281,'002897','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6','MA-6','MA-6'),
(23282,'002898','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (1)','MA-6 (1)','MA-6 (1)'),
(23283,'002899','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (1)','MA-6 (1)','MA-6 (1)'),
(23284,'002900','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (1)','MA-6 (1)','MA-6 (1)'),
(23285,'002901','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (2)','MA-6 (2)','MA-6 (2)'),
(23286,'002902','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (2)','MA-6 (2)','MA-6 (2)'),
(23287,'002903','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (2)','MA-6 (2)','MA-6 (2)'),
(23288,'002904','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (3)','MA-6 (3)','MA-6 (3)'),
(23289,'002566','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1','MP-1a.1.','MP-1'),
(23290,'002567','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6 (1)','MP-6 (1)'),
(23291,'002568','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6 (1)','MP-6 (1)'),
(23292,'002569','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6 (1)','MP-6 (1)'),
(23293,'002570','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6 (1)','MP-6 (1)'),
(23294,'002571','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6 (1)','MP-6 (1)'),
(23295,'002572','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6 (1)','MP-6 (1)'),
(23296,'002573','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (7)','MP-6 (7)','MP-6 (7)'),
(23297,'002574','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (7)','MP-6 (7)','MP-6 (7)'),
(23298,'002575','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (8)','MP-6 (8)','MP-6 (8)'),
(23299,'002576','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (8)','MP-6 (8)','MP-6 (8)'),
(23300,'002577','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (8)','MP-6 (8)','MP-6 (8)'),
(23301,'002578','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 a','MP-6a.','MP-6'),
(23302,'002579','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 a','MP-6a.','MP-6'),
(23303,'002580','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 b','MP-6b.','MP-6'),
(23304,'002581','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-7','MP-7','MP-7'),
(23305,'002582','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-7','MP-7','MP-7'),
(23306,'002583','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-7','MP-7','MP-7'),
(23307,'002584','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-7','MP-7','MP-7'),
(23308,'002585','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (1)','MP-7 (1)','MP-7 (1)'),
(23309,'002586','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (2)','MP-7 (2)','MP-7 (2)'),
(23310,'002587','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (1)','MP-8 (1)','MP-8 (1)'),
(23311,'002588','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8 (2)','MP-8 (2)'),
(23312,'002589','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8 (2)','MP-8 (2)'),
(23313,'002590','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8 (2)','MP-8 (2)'),
(23314,'002591','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8 (2)','MP-8 (2)'),
(23315,'002592','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (3)','MP-8 (3)','MP-8 (3)'),
(23316,'002593','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (3)','MP-8 (3)','MP-8 (3)'),
(23317,'002594','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (4)','MP-8 (4)','MP-8 (4)'),
(23318,'002595','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 a','MP-8a.','MP-8'),
(23319,'002596','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 a','MP-8a.','MP-8'),
(23320,'002597','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 a','MP-8a.','MP-8'),
(23321,'002598','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 b','MP-8b.','MP-8'),
(23322,'002599','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 c','MP-8c.','MP-8'),
(23323,'002600','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 d','MP-8d.','MP-8'),
(23324,'002908','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1','PE-1a.1.','PE-1'),
(23325,'002909','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 2','PE-1a.2.','PE-1'),
(23326,'002910','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 a','PE-2a.','PE-2'),
(23327,'002911','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 a','PE-2a.','PE-2'),
(23328,'002912','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (2)','PE-2 (2)','PE-2 (2)'),
(23329,'002913','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (3)','PE-2 (3)','PE-2 (3)'),
(23330,'002914','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (3)','PE-2 (3)','PE-2 (3)'),
(23331,'002915','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a','PE-3a.','PE-3'),
(23332,'002916','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 2','PE-3a.2.','PE-3'),
(23333,'002917','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 b','PE-3b.','PE-3'),
(23334,'002918','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 b','PE-3b.','PE-3'),
(23335,'002919','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 c','PE-3c.','PE-3'),
(23336,'002920','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 c','PE-3c.','PE-3'),
(23337,'002921','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d.','PE-3'),
(23338,'002922','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d.','PE-3'),
(23339,'002923','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d.','PE-3'),
(23340,'002924','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d.','PE-3'),
(23341,'002925','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 f','PE-3f.','PE-3'),
(23342,'002926','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (1)','PE-3 (1)','PE-3 (1)'),
(23343,'002927','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (2)','PE-3 (2)','PE-3 (2)'),
(23344,'002928','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (5)','PE-3 (5)','PE-3 (5)'),
(23345,'002929','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (5)','PE-3 (5)','PE-3 (5)'),
(23346,'002930','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-4','PE-4','PE-4'),
(23347,'002931','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-4','PE-4','PE-4'),
(23348,'002932','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (1) (a)','PE-5 (1)(a)','PE-5 (1)'),
(23349,'002933','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (1) (a)','PE-5 (1)(a)','PE-5 (1)'),
(23350,'002934','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (1) (b)','PE-5 (1)(b)','PE-5 (1)'),
(23351,'002935','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (2) (a)','PE-5 (2)(a)','PE-5 (2)'),
(23352,'002936','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (2) (b)','PE-5 (2)(b)','PE-5 (2)'),
(23353,'002937','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (3)','PE-5 (3)','PE-5 (3)'),
(23354,'002938','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (3)','PE-5 (3)','PE-5 (3)'),
(23355,'002939','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 a','PE-6a.','PE-6'),
(23356,'002940','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b.','PE-6'),
(23357,'002941','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b.','PE-6'),
(23358,'002942','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6 (2)','PE-6 (2)'),
(23359,'002943','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6 (2)','PE-6 (2)'),
(23360,'002944','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6 (2)','PE-6 (2)'),
(23361,'002945','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6 (2)','PE-6 (2)'),
(23362,'002946','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3)','PE-6 (3)','PE-6 (3)'),
(23363,'002947','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3)','PE-6 (3)','PE-6 (3)'),
(23364,'002948','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3)','PE-6 (3)','PE-6 (3)'),
(23365,'002949','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3)','PE-6 (3)','PE-6 (3)'),
(23366,'002950','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (4)','PE-6 (4)','PE-6 (4)'),
(23367,'002951','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (4)','PE-6 (4)','PE-6 (4)'),
(23368,'002952','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 a','PE-8a.','PE-8'),
(23369,'002953','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (1)','PE-9 (1)','PE-9 (1)'),
(23370,'002954','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (1)','PE-9 (1)','PE-9 (1)'),
(23371,'002955','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-11','PE-11','PE-11'),
(23372,'002956','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (2) (a)','PE-11 (2)(a)','PE-11 (2)'),
(23373,'002957','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (2) (b)','PE-11 (2)(b)','PE-11 (2)'),
(23374,'002958','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (2) (c)','PE-11 (2)(c)','PE-11 (2)'),
(23375,'002959','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-12 (1)','PE-12 (1)','PE-12 (1)'),
(23376,'002960','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-12 (1)','PE-12 (1)','PE-12 (1)'),
(23377,'002961','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13 (1)','PE-13 (1)'),
(23378,'002962','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13 (1)','PE-13 (1)'),
(23379,'002963','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13 (1)','PE-13 (1)'),
(23380,'002964','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13 (1)','PE-13 (1)'),
(23381,'002965','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2)','PE-13 (2)','PE-13 (2)'),
(23382,'002966','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2)','PE-13 (2)','PE-13 (2)'),
(23383,'002967','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2)','PE-13 (2)','PE-13 (2)'),
(23384,'002968','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13 (4)','PE-13 (4)'),
(23385,'002969','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13 (4)','PE-13 (4)'),
(23386,'002970','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13 (4)','PE-13 (4)'),
(23387,'002971','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13 (4)','PE-13 (4)'),
(23388,'002972','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-15 (1)','PE-15 (1)','PE-15 (1)'),
(23389,'002973','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-15 (1)','PE-15 (1)','PE-15 (1)'),
(23390,'002974','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-16','PE-16','PE-16'),
(23391,'002975','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 a','PE-17a.','PE-17'),
(23392,'002976','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-18','PE-18','PE-18'),
(23393,'002977','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-18 (1)','PE-18 (1)','PE-18 (1)'),
(23394,'002978','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-18 (1)','PE-18 (1)','PE-18 (1)'),
(23395,'003047','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1','PL-1a.1.','PL-1'),
(23396,'003048','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 2','PL-1a.2.','PL-1'),
(23397,'003049','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a','PL-2a.','PL-2'),
(23398,'003050','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 1','PL-2a.1.','PL-2'),
(23399,'003051','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 2','PL-2a.2.','PL-2'),
(23400,'003052','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 3','PL-2a.3.','PL-2'),
(23401,'003053','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 4','PL-2a.4.','PL-2'),
(23402,'003054','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 5','PL-2a.5.','PL-2'),
(23403,'003055','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 6','PL-2a.6.','PL-2'),
(23404,'003056','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 7','PL-2a.7.','PL-2'),
(23405,'003057','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 8','PL-2a.8.','PL-2'),
(23406,'003058','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b.','PL-2'),
(23407,'003059','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b.','PL-2'),
(23408,'003060','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b.','PL-2'),
(23409,'003061','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b.','PL-2'),
(23410,'003062','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b.','PL-2'),
(23411,'003063','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 e','PL-2e.','PL-2'),
(23412,'003064','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 e','PL-2e.','PL-2'),
(23413,'003065','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 (3)','PL-2 (3)','PL-2 (3)'),
(23414,'003066','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 (3)','PL-2 (3)','PL-2 (3)'),
(23415,'003067','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 (3)','PL-2 (3)','PL-2 (3)'),
(23416,'003068','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 c','PL-4c.','PL-4'),
(23417,'003069','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 c','PL-4c.','PL-4'),
(23418,'003070','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 d','PL-4d.','PL-4'),
(23419,'003071','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 a','PL-7a.','PL-7'),
(23420,'003072','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a','PL-8a.','PL-8'),
(23421,'003073','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 1','PL-8a.1.','PL-8'),
(23422,'003074','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 2','PL-8a.2.','PL-8'),
(23423,'003075','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 3','PL-8a.3.','PL-8'),
(23424,'003076','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 b','PL-8b.','PL-8'),
(23425,'003077','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 b','PL-8b.','PL-8'),
(23426,'003078','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c.','PL-8'),
(23427,'003079','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c.','PL-8'),
(23428,'003080','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c.','PL-8'),
(23429,'003081','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8 (1)(a)','PL-8 (1)'),
(23430,'003082','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8 (1)(a)','PL-8 (1)'),
(23431,'003083','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8 (1)(a)','PL-8 (1)'),
(23432,'003084','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8 (1)(a)','PL-8 (1)'),
(23433,'003085','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8 (1)(a)','PL-8 (1)'),
(23434,'003086','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8 (1)(a)','PL-8 (1)'),
(23435,'003087','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (b)','PL-8 (1)(b)','PL-8 (1)'),
(23436,'003088','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (2)','PL-8 (2)','PL-8 (2)'),
(23437,'003017','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1','PS-1a.1.','PS-1'),
(23438,'003018','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 2','PS-1a.2.','PS-1'),
(23439,'003019','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (3) (a)','PS-3 (3)(a)','PS-3 (3)'),
(23440,'003020','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (3) (b)','PS-3 (3)(b)','PS-3 (3)'),
(23441,'003021','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (3) (b)','PS-3 (3)(b)','PS-3 (3)'),
(23442,'003016','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 f','PS-4f.','PS-4'),
(23443,'003022','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 a','PS-4a.','PS-4'),
(23444,'003023','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 b','PS-4b.','PS-4'),
(23445,'003024','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 c','PS-4c.','PS-4'),
(23446,'003025','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 f','PS-4f.','PS-4'),
(23447,'003026','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 f','PS-4f.','PS-4'),
(23448,'003027','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (1) (a)','PS-4 (1)(a)','PS-4 (1)'),
(23449,'003028','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (1) (b)','PS-4 (1)(b)','PS-4 (1)'),
(23450,'003029','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (2)','PS-4 (2)','PS-4 (2)'),
(23451,'003030','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (2)','PS-4 (2)','PS-4 (2)'),
(23452,'003031','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 c','PS-5c.','PS-5'),
(23453,'003032','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 d','PS-5d.','PS-5'),
(23454,'003033','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 d','PS-5d.','PS-5'),
(23455,'003034','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 d','PS-5d.','PS-5'),
(23456,'003035','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 a','PS-6a.','PS-6'),
(23457,'003036','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 2','PS-6c.2.','PS-6'),
(23458,'003037','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 2','PS-6c.2.','PS-6'),
(23459,'003038','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (3) (a)','PS-6 (3)(a)','PS-6 (3)'),
(23460,'003039','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (3) (b)','PS-6 (3)(b)','PS-6 (3)'),
(23461,'003040','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 b','PS-7b.','PS-7'),
(23462,'003041','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 d','PS-7d.','PS-7'),
(23463,'003042','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 d','PS-7d.','PS-7'),
(23464,'003043','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 d','PS-7d.','PS-7'),
(23465,'003044','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 b','PS-8b.','PS-8'),
(23466,'003045','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 b','PS-8b.','PS-8'),
(23467,'003046','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 b','PS-8b.','PS-8'),
(23468,'002368','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1','RA-1a.1.','RA-1'),
(23469,'002369','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 2','RA-1a.2.','RA-1'),
(23470,'002370','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 d','RA-3d.','RA-3'),
(23471,'002371','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 d','RA-3d.','RA-3'),
(23472,'002372','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (10)','RA-5 (10)','RA-5 (10)'),
(23473,'002373','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (3)','RA-5 (3)','RA-5 (3)'),
(23474,'002374','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (4)','RA-5 (4)','RA-5 (4)'),
(23475,'002375','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (4)','RA-5 (4)','RA-5 (4)'),
(23476,'002376','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 e','RA-5e.','RA-5'),
(23477,'002906','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (5)','RA-5 (5)','RA-5 (5)'),
(23478,'003119','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
(23479,'003120','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
(23480,'003121','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
(23481,'003122','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
(23482,'003089','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1','SA-1a.1.','SA-1'),
(23483,'003090','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 2','SA-1a.2.','SA-1'),
(23484,'003091','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 a ','SA-2a..','SA-2'),
(23485,'003092','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a.','SA-3'),
(23486,'003093','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 d','SA-3d.','SA-3'),
(23487,'003094','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 a','SA-4a.','SA-4'),
(23488,'003095','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 b','SA-4b.','SA-4'),
(23489,'003096','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 c','SA-4c.','SA-4'),
(23490,'003097','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 d','SA-4d.','SA-4'),
(23491,'003098','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 e','SA-4e.','SA-4'),
(23492,'003099','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 f','SA-4f.','SA-4'),
(23493,'003100','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 g','SA-4g.','SA-4'),
(23494,'003101','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4 (2)','SA-4 (2)'),
(23495,'003102','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4 (2)','SA-4 (2)'),
(23496,'003103','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4 (2)','SA-4 (2)'),
(23497,'003104','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4 (2)','SA-4 (2)'),
(23498,'003105','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4 (2)','SA-4 (2)'),
(23499,'003106','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4 (2)','SA-4 (2)'),
(23500,'003107','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3)','SA-4 (3)','SA-4 (3)'),
(23501,'003108','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3)','SA-4 (3)','SA-4 (3)'),
(23502,'003109','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (5) (a)','SA-4 (5)(a)','SA-4 (5)'),
(23503,'003110','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (5) (a)','SA-4 (5)(a)','SA-4 (5)'),
(23504,'003111','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (5) (b)','SA-4 (5)(b)','SA-4 (5)'),
(23505,'003112','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (8)','SA-4 (8)','SA-4 (8)'),
(23506,'003113','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (8)','SA-4 (8)','SA-4 (8)'),
(23507,'003114','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (9)','SA-4 (9)','SA-4 (9)'),
(23508,'003115','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (9)','SA-4 (9)','SA-4 (9)'),
(23509,'003116','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (10)','SA-4 (10)','SA-4 (10)'),
(23510,'003124','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 1','SA-5a.1.','SA-5'),
(23511,'003125','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 1','SA-5a.1.','SA-5'),
(23512,'003126','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 1','SA-5a.1.','SA-5'),
(23513,'003127','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 2','SA-5a.2.','SA-5'),
(23514,'003128','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 3','SA-5a.3.','SA-5'),
(23515,'003129','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 1','SA-5b.1.','SA-5'),
(23516,'003130','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 2','SA-5b.2.','SA-5'),
(23517,'003131','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 3','SA-5b.3.','SA-5'),
(23518,'003132','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 c','SA-5c.','SA-5'),
(23519,'003133','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 c','SA-5c.','SA-5'),
(23520,'003134','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 d','SA-5d.','SA-5'),
(23521,'003135','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 e','SA-5e.','SA-5'),
(23522,'003136','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 e','SA-5e.','SA-5'),
(23523,'003137','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 a','SA-9a.','SA-9'),
(23524,'003138','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 c','SA-9c.','SA-9'),
(23525,'003139','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 c','SA-9c.','SA-9'),
(23526,'003140','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (1) (a)','SA-9(1)(a)','SA-9'),
(23527,'003141','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (1) (b)','SA-9 (1)(b)','SA-9 (1)'),
(23528,'003142','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (1) (b)','SA-9 (1)(b)','SA-9 (1)'),
(23529,'003143','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (2)','SA-9 (2)','SA-9 (2)'),
(23530,'003144','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (2)','SA-9 (2)','SA-9 (2)'),
(23531,'003145','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9 (3)','SA-9 (3)'),
(23532,'003146','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9 (3)','SA-9 (3)'),
(23533,'003147','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9 (3)','SA-9 (3)'),
(23534,'003148','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9 (3)','SA-9 (3)'),
(23535,'003149','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (4)','SA-9 (4)','SA-9 (4)'),
(23536,'003150','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (4)','SA-9 (4)','SA-9 (4)'),
(23537,'003151','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (4)','SA-9 (4)','SA-9 (4)'),
(23538,'003152','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (5)','SA-9 (5)','SA-9 (5)'),
(23539,'003153','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (5)','SA-9 (5)','SA-9 (5)'),
(23540,'003154','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (5)','SA-9 (5)','SA-9 (5)'),
(23541,'003155','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 a','SA-10a.','SA-10'),
(23542,'003156','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b.','SA-10'),
(23543,'003157','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b.','SA-10'),
(23544,'003158','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b.','SA-10'),
(23545,'003159','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b.','SA-10'),
(23546,'003160','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 d','SA-10d.','SA-10'),
(23547,'003161','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e.','SA-10'),
(23548,'003162','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e.','SA-10'),
(23549,'003163','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e.','SA-10'),
(23550,'003164','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e.','SA-10'),
(23551,'003165','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (3)','SA-10 (3)','SA-10 (3)'),
(23552,'003166','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (4)','SA-10 (4)','SA-10 (4)'),
(23553,'003167','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (4)','SA-10 (4)','SA-10 (4)'),
(23554,'003168','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (4)','SA-10 (4)','SA-10 (4)'),
(23555,'003169','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (5)','SA-10 (5)','SA-10 (5)'),
(23556,'003170','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (6)','SA-10 (6)','SA-10 (6)'),
(23557,'003171','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 a','SA-11a.','SA-11'),
(23558,'003172','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 a','SA-11a.','SA-11'),
(23559,'003173','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 b','SA-11b.','SA-11'),
(23560,'003174','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 b','SA-11b.','SA-11'),
(23561,'003175','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 c','SA-11c.','SA-11'),
(23562,'003176','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 c','SA-11c.','SA-11'),
(23563,'003177','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 d','SA-11d.','SA-11'),
(23564,'003178','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 e','SA-11e.','SA-11'),
(23565,'003179','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (1)','SA-11 (1)','SA-11 (1)'),
(23566,'003180','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (1)','SA-11 (1)','SA-11 (1)'),
(23567,'003181','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2)','SA-11 (2)','SA-11 (2)'),
(23568,'003182','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2)','SA-11 (2)','SA-11 (2)'),
(23569,'003183','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11 (3)(a)','SA-11 (3)'),
(23570,'003184','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11 (3)(a)','SA-11 (3)'),
(23571,'003185','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11 (3)(a)','SA-11 (3)'),
(23572,'003186','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (b)','SA-11 (3)(b)','SA-11 (3)'),
(23573,'003187','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (4)','SA-11 (4)','SA-11 (4)'),
(23574,'003188','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (4)','SA-11 (4)','SA-11 (4)'),
(23575,'003189','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (4)','SA-11 (4)','SA-11 (4)'),
(23576,'003190','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5)','SA-11 (5)','SA-11 (5)'),
(23577,'003191','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5)','SA-11 (5)','SA-11 (5)'),
(23578,'003192','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5)','SA-11 (5)','SA-11 (5)'),
(23579,'003193','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (6)','SA-11 (6)','SA-11 (6)'),
(23580,'003194','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (7)','SA-11 (7)','SA-11 (7)'),
(23581,'003195','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (7)','SA-11 (7)','SA-11 (7)'),
(23582,'003196','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (8)','SA-11 (8)','SA-11 (8)'),
(23583,'003197','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (8)','SA-11 (8)','SA-11 (8)'),
(23584,'003198','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (1)','SA-12 (1)','SA-12 (1)'),
(23585,'003199','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (1)','SA-12 (1)','SA-12 (1)'),
(23586,'003200','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (2)','SA-12 (2)','SA-12 (2)'),
(23587,'003201','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (5)','SA-12 (5)','SA-12 (5)'),
(23588,'003202','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (5)','SA-12 (5)','SA-12 (5)'),
(23589,'003203','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (7)','SA-12 (7)','SA-12 (7)'),
(23590,'003204','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (7)','SA-12 (7)','SA-12 (7)'),
(23591,'003205','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (8)','SA-12 (8)','SA-12 (8)'),
(23592,'003206','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (9)','SA-12 (9)','SA-12 (9)'),
(23593,'003207','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (1)','SA-12 (1)','SA-12 (1)'),
(23594,'003208','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (1)','SA-12 (1)','SA-12 (1)'),
(23595,'003209','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (1)','SA-12 (1)','SA-12 (1)'),
(23596,'003210','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (9)','SA-12 (9)','SA-12 (9)'),
(23597,'003211','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (9)','SA-12 (9)','SA-12 (9)'),
(23598,'003212','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (10)','SA-12 (10)','SA-12 (10)'),
(23599,'003213','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (10)','SA-12 (10)','SA-12 (10)'),
(23600,'003214','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (11)','SA-12 (11)','SA-12 (11)'),
(23601,'003215','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (11)','SA-12 (11)','SA-12 (11)'),
(23602,'003216','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (12)','SA-12 (12)','SA-12 (12)'),
(23603,'003217','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (12)','SA-12 (12)','SA-12 (12)'),
(23604,'003218','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (13)','SA-12 (13)','SA-12 (13)'),
(23605,'003219','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (13)','SA-12 (13)','SA-12 (13)'),
(23606,'003220','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (13)','SA-12 (13)','SA-12 (13)'),
(23607,'003221','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (14)','SA-12 (14)','SA-12 (14)'),
(23608,'003222','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (14)','SA-12 (14)','SA-12 (14)'),
(23609,'003223','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (14)','SA-12 (14)','SA-12 (14)'),
(23610,'003224','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-12 (15)','SA-12 (15)','SA-12 (15)'),
(23611,'003225','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-13 a','SA-13a.','SA-13'),
(23612,'003226','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-13 a','SA-13a.','SA-13'),
(23613,'003227','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-13 b','SA-13b.','SA-13'),
(23614,'003228','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-13 b','SA-13b.','SA-13'),
(23615,'003229','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-14','SA-14','SA-14'),
(23616,'003230','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-14','SA-14','SA-14'),
(23617,'003231','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-14','SA-14','SA-14'),
(23618,'003232','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-14','SA-14','SA-14'),
(23619,'003233','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15','SA-15','SA-15'),
(23620,'003234','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 1','SA-15a.1.','SA-15'),
(23621,'003235','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 2','SA-15a.2.','SA-15'),
(23622,'003236','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 2','SA-15a.2.','SA-15'),
(23623,'003237','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 3','SA-15a.3.','SA-15'),
(23624,'003238','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 4','SA-15a.4.','SA-15'),
(23625,'003239','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 4','SA-15a.4.','SA-15'),
(23626,'003240','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 4','SA-15a.4.','SA-15'),
(23627,'003241','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b.','SA-15'),
(23628,'003242','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b.','SA-15'),
(23629,'003243','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b.','SA-15'),
(23630,'003244','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b.','SA-15'),
(23631,'003245','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b.','SA-15'),
(23632,'003246','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b.','SA-15'),
(23633,'003247','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (a)','SA-15 (1)(a)','SA-15 (1)'),
(23634,'003248','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (b)','SA-15 (1)(b)','SA-15 (1)'),
(23635,'003249','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (b)','SA-15 (1)(b)','SA-15 (1)'),
(23636,'003250','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (b)','SA-15 (1)(b)','SA-15 (1)'),
(23637,'003251','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (2)','SA-15 (2)','SA-15 (2)'),
(23638,'003252','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (2)','SA-15 (2)','SA-15 (2)'),
(23639,'003253','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3)','SA-15 (3)','SA-15 (3)'),
(23640,'003254','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3)','SA-15 (3)','SA-15 (3)'),
(23641,'003255','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3)','SA-15 (3)','SA-15 (3)'),
(23642,'003256','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4)','SA-15 (4)','SA-15 (4)'),
(23643,'003257','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4)','SA-15 (4)','SA-15 (4)'),
(23644,'003258','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4)','SA-15 (4)','SA-15 (4)'),
(23645,'003259','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4)','SA-15 (4)','SA-15 (4)'),
(23646,'003260','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (a)','SA-15 (4)(a)','SA-15 (4)'),
(23647,'003261','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (a)','SA-15 (4)(a)','SA-15 (4)'),
(23648,'003262','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (a)','SA-15 (4)(a)','SA-15 (4)'),
(23649,'003263','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (a)','SA-15 (4)(a)','SA-15 (4)'),
(23650,'003264','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (b)','SA-15 (4)(b)','SA-15 (4)'),
(23651,'003265','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (b)','SA-15 (4)(b)','SA-15 (4)'),
(23652,'003266','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (b)','SA-15 (4)(b)','SA-15 (4)'),
(23653,'003267','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (b)','SA-15 (4)(b)','SA-15 (4)'),
(23654,'003268','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (c)','SA-15 (4)(c)','SA-15 (4)'),
(23655,'003269','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (c)','SA-15 (4)(c)','SA-15 (4)'),
(23656,'003270','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (c)','SA-15 (4)(c)','SA-15 (4)'),
(23657,'003271','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (4) (c)','SA-15 (4)(c)','SA-15 (4)'),
(23658,'003272','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (5)','SA-15 (5)','SA-15 (5)'),
(23659,'003273','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (5)','SA-15 (5)','SA-15 (5)'),
(23660,'003274','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (6)','SA-15 (6)','SA-15 (6)'),
(23661,'003275','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (a)','SA-15 (7)(a)','SA-15 (7)'),
(23662,'003276','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (a)','SA-15 (7)(a)','SA-15 (7)'),
(23663,'003277','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (b)','SA-15 (7)(b)','SA-15 (7)'),
(23664,'003278','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (c)','SA-15 (7)(c)','SA-15 (7)'),
(23665,'003279','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (d)','SA-15 (7)(d)','SA-15 (7)'),
(23666,'003280','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (d)','SA-15 (7)(d)','SA-15 (7)'),
(23667,'003281','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (8)','SA-15 (8)','SA-15 (8)'),
(23668,'003282','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (8)','SA-15 (8)','SA-15 (8)'),
(23669,'003283','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (9)','SA-15 (9)','SA-15 (9)'),
(23670,'003284','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (9)','SA-15 (9)','SA-15 (9)'),
(23671,'003285','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (9)','SA-15 (9)','SA-15 (9)'),
(23672,'003286','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (9)','SA-15 (9)','SA-15 (9)'),
(23673,'003287','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (9)','SA-15 (9)','SA-15 (9)'),
(23674,'003288','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (9)','SA-15 (9)','SA-15 (9)'),
(23675,'003289','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (10)','SA-15 (10)','SA-15 (10)'),
(23676,'003290','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (11)','SA-15 (11)','SA-15 (11)'),
(23677,'003291','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-16','SA-16','SA-16'),
(23678,'003292','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-16','SA-16','SA-16'),
(23679,'003293','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17','SA-17','SA-17'),
(23680,'003294','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 a','SA-17a.','SA-17'),
(23681,'003295','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 b','SA-17b.','SA-17'),
(23682,'003296','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 b','SA-17b.','SA-17'),
(23683,'003297','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 c','SA-17c.','SA-17'),
(23684,'003298','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (a)','SA-17 (1)(a)','SA-17 (1)'),
(23685,'003299','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (a)','SA-17 (1)(a)','SA-17 (1)'),
(23686,'003300','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (b)','SA-17 (1)(b)','SA-17 (1)'),
(23687,'003301','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17 (2)(a)','SA-17 (2)'),
(23688,'003302','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17 (2)(a)','SA-17 (2)'),
(23689,'003303','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17 (2)(a)','SA-17 (2)'),
(23690,'003304','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17 (2)(a)','SA-17 (2)'),
(23691,'003305','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17 (2)(a)','SA-17 (2)'),
(23692,'003306','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (b)','SA-17 (2)(b)','SA-17 (2)'),
(23693,'003307','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (b)','SA-17 (2)(b)','SA-17 (2)'),
(23694,'003308','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (a)','SA-17 (3)(a)','SA-17 (3)'),
(23695,'003309','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (a)','SA-17 (3)(a)','SA-17 (3)'),
(23696,'003310','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (a)','SA-17 (3)(a)','SA-17 (3)'),
(23697,'003311','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (b)','SA-17 (3)(b)','SA-17 (3)'),
(23698,'003312','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (c)','SA-17 (3)(c)','SA-17 (3)'),
(23699,'003313','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (c)','SA-17 (3)(c)','SA-17 (3)'),
(23700,'003314','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (c)','SA-17 (3)(c)','SA-17 (3)'),
(23701,'003315','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (d)','SA-17 (3)(d)','SA-17 (3)'),
(23702,'003316','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (d)','SA-17 (3)(d)','SA-17 (3)'),
(23703,'003317','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (d)','SA-17 (3)(d)','SA-17 (3)'),
(23704,'003318','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (e)','SA-17 (3)(e)','SA-17 (3)'),
(23705,'003319','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (e)','SA-17 (3)(e)','SA-17 (3)'),
(23706,'003320','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (e)','SA-17 (3)(e)','SA-17 (3)'),
(23707,'003321','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (a)','SA-17 (4)(a)','SA-17 (4)'),
(23708,'003322','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (a)','SA-17 (4)(a)','SA-17 (4)'),
(23709,'003323','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (a)','SA-17 (4)(a)','SA-17 (4)'),
(23710,'003324','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (b)','SA-17 (4)(b)','SA-17 (4)'),
(23711,'003325','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (c)','SA-17 (4)(c)','SA-17 (4)'),
(23712,'003326','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (c)','SA-17 (4)(c)','SA-17 (4)'),
(23713,'003327','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (c)','SA-17 (4)(c)','SA-17 (4)'),
(23714,'003328','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (d)','SA-17 (4)(d)','SA-17 (4)'),
(23715,'003329','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (d)','SA-17 (4)(d)','SA-17 (4)'),
(23716,'003330','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (d)','SA-17 (4)(d)','SA-17 (4)'),
(23717,'003331','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (e)','SA-17 (4)(e)','SA-17 (4)'),
(23718,'003332','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (e)','SA-17 (4)(e)','SA-17 (4)'),
(23719,'003333','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (e)','SA-17 (4)(e)','SA-17 (4)'),
(23720,'003334','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (a)','SA-17 (5)(a)','SA-17 (5)'),
(23721,'003335','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (a)','SA-17 (5)(a)','SA-17 (5)'),
(23722,'003336','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (a)','SA-17 (5)(a)','SA-17 (5)'),
(23723,'003337','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (b)','SA-17 (5)(b)','SA-17 (5)'),
(23724,'003338','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (b)','SA-17 (5)(b)','SA-17 (5)'),
(23725,'003339','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (b)','SA-17 (5)(b)','SA-17 (5)'),
(23726,'003340','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (6)','SA-17 (6)','SA-17 (6)'),
(23727,'003341','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (6)','SA-17 (6)','SA-17 (6)'),
(23728,'003342','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (6)','SA-17 (6)','SA-17 (6)'),
(23729,'003343','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (7)','SA-17 (7)','SA-17 (7)'),
(23730,'003344','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (7)','SA-17 (7)','SA-17 (7)'),
(23731,'003345','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (7)','SA-17 (7)','SA-17 (7)'),
(23732,'003346','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18','SA-18','SA-18'),
(23733,'003347','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (1)','SA-18 (1)','SA-18 (1)'),
(23734,'003348','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (1)','SA-18 (1)','SA-18 (1)'),
(23735,'003349','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (1)','SA-18 (1)','SA-18 (1)'),
(23736,'003350','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (1)','SA-18 (1)','SA-18 (1)'),
(23737,'003351','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (1)','SA-18 (1)','SA-18 (1)'),
(23738,'003352','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (2)','SA-18 (2)','SA-18 (2)'),
(23739,'003353','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (2)','SA-18 (2)','SA-18 (2)'),
(23740,'003354','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (2)','SA-18 (2)','SA-18 (2)'),
(23741,'003355','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-18 (2)','SA-18 (2)','SA-18 (2)'),
(23742,'003356','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23743,'003357','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23744,'003358','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23745,'003359','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23746,'003360','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23747,'003361','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23748,'003362','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23749,'003363','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 a','SA-19a.','SA-19'),
(23750,'003364','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 b','SA-19b.','SA-19'),
(23751,'003365','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 b','SA-19b.','SA-19'),
(23752,'003366','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 b','SA-19b.','SA-19'),
(23753,'003367','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (1)','SA-19 (1)','SA-19 (1)'),
(23754,'003368','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (1)','SA-19 (1)','SA-19 (1)'),
(23755,'003369','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (2)','SA-19 (2)','SA-19 (2)'),
(23756,'003370','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (2)','SA-19 (2)','SA-19 (2)'),
(23757,'003371','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (2)','SA-19 (2)','SA-19 (2)'),
(23758,'003388','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (4)','SA-19 (4)','SA-19 (4)'),
(23759,'003389','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (4)','SA-19 (4)','SA-19 (4)'),
(23760,'003390','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (3)','SA-19 (3)','SA-19 (3)'),
(23761,'003391','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-19 (3)','SA-19 (3)','SA-19 (3)'),
(23762,'003386','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-20','SA-20','SA-20'),
(23763,'003387','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-20','SA-20','SA-20'),
(23764,'003377','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 (1)','SA-21 (1)','SA-21 (1)'),
(23765,'003378','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 (1)','SA-21 (1)','SA-21 (1)'),
(23766,'003379','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 (1)','SA-21 (1)','SA-21 (1)'),
(23767,'003380','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 (1)','SA-21 (1)','SA-21 (1)'),
(23768,'003381','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 b','SA-21b.','SA-21'),
(23769,'003382','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 b','SA-21b.','SA-21'),
(23770,'003383','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 a','SA-21a.','SA-21'),
(23771,'003384','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 ','SA-21','SA-21'),
(23772,'003385','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 a','SA-21a.','SA-21'),
(23773,'002377','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1','SC-1a.1.','SC-1'),
(23774,'002378','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1','SC-1a.1.','SC-1'),
(23775,'002379','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a.2.','SC-1'),
(23776,'002380','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a.2.','SC-1'),
(23777,'002381','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (3)','SC-3 (3)','SC-3 (3)'),
(23778,'002382','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (4)','SC-3 (4)','SC-3 (4)'),
(23779,'002383','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-4 (2)','SC-4 (2)','SC-4 (2)'),
(23780,'002384','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-4 (2)','SC-4 (2)','SC-4 (2)'),
(23781,'002385','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5','SC-5','SC-5'),
(23782,'002386','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5','SC-5','SC-5'),
(23783,'002387','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (1)','SC-5 (1)','SC-5 (1)'),
(23784,'002388','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (a)','SC-5 (3)(a)','SC-5 (3)'),
(23785,'002389','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (a)','SC-5 (3)(a)','SC-5 (3)'),
(23786,'002390','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (b)','SC-5 (3)(b)','SC-5 (3)'),
(23787,'002391','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (b)','SC-5 (3)(b)','SC-5 (3)'),
(23788,'002392','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-6','SC-6','SC-6'),
(23789,'002393','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-6','SC-6','SC-6'),
(23790,'002394','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-6','SC-6','SC-6'),
(23791,'002395','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 b','SC-7b.','SC-7'),
(23792,'002396','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (c)','SC-7 (4)(c)','SC-7 (4)'),
(23793,'002397','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (7)','SC-7 (7)','SC-7 (7)'),
(23794,'002398','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (9) (a)','SC-7 (9)(a)','SC-7 (9)'),
(23795,'002399','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (9) (a)','SC-7 (9)(a)','SC-7 (9)'),
(23796,'002400','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (9) (b)','SC-7 (9)(b)','SC-7 (9)'),
(23797,'002401','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (11)','SC-7 (11)','SC-7 (11)'),
(23798,'002402','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (11)','SC-7 (11)','SC-7 (11)'),
(23799,'002403','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (11)','SC-7 (11)','SC-7 (11)'),
(23800,'002404','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (12)','SC-7 (12)','SC-7 (12)'),
(23801,'002405','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (12)','SC-7 (12)','SC-7 (12)'),
(23802,'002406','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (12)','SC-7 (12)','SC-7 (12)'),
(23803,'002407','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (14)','SC-7 (14)','SC-7 (14)'),
(23804,'002408','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (19)','SC-7 (19)','SC-7 (19)'),
(23805,'002409','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (19)','SC-7 (19)','SC-7 (19)'),
(23806,'002410','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (20)','SC-7 (20)','SC-7 (20)'),
(23807,'002411','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (20)','SC-7 (20)','SC-7 (20)'),
(23808,'002412','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7 (21)','SC-7 (21)'),
(23809,'002413','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7 (21)','SC-7 (21)'),
(23810,'002414','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7 (21)','SC-7 (21)'),
(23811,'002415','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7 (21)','SC-7 (21)'),
(23812,'002416','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (22)','SC-7 (22)','SC-7 (22)'),
(23813,'002417','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (23)','SC-7 (23)','SC-7 (23)'),
(23814,'002418','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8','SC-8','SC-8'),
(23815,'002419','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (1)','SC-8 (1)','SC-8 (1)'),
(23816,'002420','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (2)','SC-8 (2)','SC-8 (2)'),
(23817,'002421','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (1)','SC-8 (1)','SC-8 (1)'),
(23818,'002422','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (2)','SC-8 (2)','SC-8 (2)'),
(23819,'002423','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (3)','SC-8 (3)','SC-8 (3)'),
(23820,'002424','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (4)','SC-8 (4)','SC-8 (4)'),
(23821,'002425','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (4)','SC-8 (4)','SC-8 (4)'),
(23822,'002427','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (3)','SC-8 (3)','SC-8 (3)'),
(23823,'002426','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 (1)','SC-11 (1)','SC-11 (1)'),
(23824,'002428','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23825,'002429','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23826,'002430','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23827,'002431','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23828,'002432','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23829,'002433','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23830,'002434','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23831,'002435','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23832,'002436','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23833,'002437','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23834,'002438','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23835,'002439','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23836,'002440','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23837,'002441','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23838,'002442','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
(23839,'002443','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (2)','SC-12 (2)','SC-12 (2)'),
(23840,'002444','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (2)','SC-12 (2)','SC-12 (2)'),
(23841,'002445','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (2)','SC-12 (2)','SC-12 (2)'),
(23842,'002446','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12 (3)','SC-12 (3)'),
(23843,'002447','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12 (3)','SC-12 (3)'),
(23844,'002448','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12 (3)','SC-12 (3)'),
(23845,'002449','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-13','SC-13','SC-13'),
(23846,'002450','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-13','SC-13','SC-13'),
(23847,'002451','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (3)','SC-15 (3)','SC-15 (3)'),
(23848,'002452','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (4)','SC-15 (4)','SC-15 (4)'),
(23849,'002453','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (4)','SC-15 (4)','SC-15 (4)'),
(23850,'002454','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
(23851,'002455','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
(23852,'002456','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-17','SC-17','SC-17'),
(23853,'002457','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18 (1)','SC-18 (1)'),
(23854,'002458','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18 (1)','SC-18 (1)'),
(23855,'002459','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (3)','SC-18 (3)','SC-18 (3)'),
(23856,'002460','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18 (4)','SC-18 (4)'),
(23857,'002461','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (5)','SC-18 (5)','SC-18 (5)'),
(23858,'002462','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 a','SC-20a.','SC-20'),
(23859,'002463','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 (2)','SC-20 (2)','SC-20 (2)'),
(23860,'002464','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 (2)','SC-20 (2)','SC-20 (2)'),
(23861,'002465','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
(23862,'002466','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
(23863,'002467','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
(23864,'002468','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
(23865,'002469','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (5)','SC-23 (5)','SC-23 (5)'),
(23866,'002470','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (5)','SC-23 (5)','SC-23 (5)'),
(23867,'002471','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-25','SC-25','SC-25'),
(23868,'002472','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28','SC-28','SC-28'),
(23869,'002473','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28 (1)','SC-28 (1)'),
(23870,'002474','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28 (1)','SC-28 (1)'),
(23871,'002475','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28 (1)','SC-28 (1)'),
(23872,'002476','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28 (1)','SC-28 (1)'),
(23873,'002477','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (2)','SC-28 (2)','SC-28 (2)'),
(23874,'002478','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (2)','SC-28 (2)','SC-28 (2)'),
(23875,'002479','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (2)','SC-28 (2)','SC-28 (2)'),
(23876,'002480','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-29','SC-29','SC-29'),
(23877,'002481','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-29 (1)','SC-29 (1)','SC-29 (1)'),
(23878,'002482','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
(23879,'002483','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
(23880,'002484','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
(23881,'002485','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
(23882,'002486','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (2)','SC-30 (2)','SC-30 (2)'),
(23883,'002487','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (2)','SC-30 (2)','SC-30 (2)'),
(23884,'002488','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (2)','SC-30 (2)','SC-30 (2)'),
(23885,'002489','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30 (3)','SC-30 (3)'),
(23886,'002490','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30 (3)','SC-30 (3)'),
(23887,'002491','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30 (3)','SC-30 (3)'),
(23888,'002492','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30 (3)','SC-30 (3)'),
(23889,'002493','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (4)','SC-30 (4)','SC-30 (4)'),
(23890,'002494','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (4)','SC-30 (4)','SC-30 (4)'),
(23891,'002495','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (5)','SC-30 (5)','SC-30 (5)'),
(23892,'002496','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (5)','SC-30 (5)','SC-30 (5)'),
(23893,'002497','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (5)','SC-30 (5)','SC-30 (5)'),
(23894,'002498','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 a','SC-31a.','SC-31'),
(23895,'002499','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 b','SC-31b.','SC-31'),
(23896,'002500','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (2)','SC-31 (2)','SC-31 (2)'),
(23897,'002501','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (2)','SC-31 (2)','SC-31 (2)'),
(23898,'002502','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (3)','SC-31 (3)','SC-31 (3)'),
(23899,'002503','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (3)','SC-31 (3)','SC-31 (3)'),
(23900,'002504','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-32','SC-32','SC-32'),
(23901,'002505','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-32','SC-32','SC-32'),
(23902,'002506','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-32','SC-32','SC-32'),
(23903,'002507','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (2)','SC-34 (2)','SC-34 (2)'),
(23904,'002508','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (3) (a)','SC-34 (3)(a)','SC-34 (3)'),
(23905,'002509','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (3) (a)','SC-34 (3)(a)','SC-34 (3)'),
(23906,'002510','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (3) (b)','SC-34 (3)(b)','SC-34 (3)'),
(23907,'002511','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (3) (b)','SC-34 (3)(b)','SC-34 (3)'),
(23908,'002512','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (3) (b)','SC-34 (3)(b)','SC-34 (3)'),
(23909,'002513','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
(23910,'002514','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
(23911,'002515','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
(23912,'002516','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
(23913,'002517','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1)','SC-36 (1)','SC-36 (1)'),
(23914,'002518','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1)','SC-36 (1)','SC-36 (1)'),
(23915,'002519','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1)','SC-36 (1)','SC-36 (1)'),
(23916,'002520','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1)','SC-36 (1)','SC-36 (1)'),
(23917,'002521','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
(23918,'002522','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
(23919,'002523','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
(23920,'002524','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
(23921,'002525','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37 (1)','SC-37 (1)'),
(23922,'002526','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37 (1)','SC-37 (1)'),
(23923,'002527','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37 (1)','SC-37 (1)'),
(23924,'003599','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37 (1)','SC-37 (1)'),
(23925,'002528','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-38','SC-38','SC-38'),
(23926,'002529','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-38','SC-38','SC-38'),
(23927,'002530','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-39','SC-39','SC-39'),
(23928,'002531','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-39 (1)','SC-39 (1)','SC-39 (1)'),
(23929,'002532','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-39 (2)','SC-39 (2)','SC-39 (2)'),
(23930,'002533','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-39 (2)','SC-39 (2)','SC-39 (2)'),
(23931,'002534','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40','SC-40','SC-40'),
(23932,'002535','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40','SC-40','SC-40'),
(23933,'002536','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40','SC-40','SC-40'),
(23934,'002537','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (1)','SC-40 (1)','SC-40 (1)'),
(23935,'002538','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (1)','SC-40 (1)','SC-40 (1)'),
(23936,'002539','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (2)','SC-40 (2)','SC-40 (2)'),
(23937,'002540','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (2)','SC-40 (2)','SC-40 (2)'),
(23938,'002541','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (3)','SC-40 (3)','SC-40 (3)'),
(23939,'002542','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (4)','SC-40 (4)','SC-40 (4)'),
(23940,'002543','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (4)','SC-40 (4)','SC-40 (4)'),
(23941,'002544','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-41','SC-41','SC-41'),
(23942,'002545','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-41','SC-41','SC-41'),
(23943,'002546','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-41','SC-41','SC-41'),
(23944,'002547','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 a','SC-42a.','SC-42'),
(23945,'002548','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 a','SC-42a.','SC-42'),
(23946,'002549','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 b','SC-42b.','SC-42'),
(23947,'002550','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 b','SC-42b.','SC-42'),
(23948,'002551','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (1)','SC-42 (1)','SC-42 (1)'),
(23949,'002552','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (1)','SC-42 (1)','SC-42 (1)'),
(23950,'002553','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (2)','SC-42 (2)','SC-42 (2)'),
(23951,'002554','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (2)','SC-42 (2)','SC-42 (2)'),
(23952,'002555','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (2)','SC-42 (2)','SC-42 (2)'),
(23953,'002556','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (3)','SC-42 (3)','SC-42 (3)'),
(23954,'002557','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (3)','SC-42 (3)','SC-42 (3)'),
(23955,'002558','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (3)','SC-42 (3)','SC-42 (3)'),
(23956,'002559','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 a','SC-43a.','SC-43'),
(23957,'002560','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 a','SC-43a.','SC-43'),
(23958,'002561','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 b','SC-43b.','SC-43'),
(23959,'002562','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 b','SC-43b.','SC-43'),
(23960,'002563','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 b','SC-43b.','SC-43'),
(23961,'002564','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-44','SC-44','SC-44'),
(23962,'002565','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SC-44','SC-44','SC-44'),
(23963,'002601','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a','SI-1a.','SI-1'),
(23964,'002602','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b.','SI-2'),
(23965,'002603','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b.','SI-2'),
(23966,'002604','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c.','SI-2'),
(23967,'002605','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c.','SI-2'),
(23968,'002606','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c.','SI-2'),
(23969,'002607','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c.','SI-2'),
(23970,'002608','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (3) (b)','SI-2 (3)(b)','SI-2 (3)'),
(23971,'002609','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2 (5)','SI-2 (5)'),
(23972,'002610','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2 (5)','SI-2 (5)'),
(23973,'002611','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2 (5)','SI-2 (5)'),
(23974,'002612','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2 (5)','SI-2 (5)'),
(23975,'002613','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2 (5)','SI-2 (5)'),
(23976,'002614','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2 (5)','SI-2 (5)'),
(23977,'002615','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2 (6)','SI-2 (6)'),
(23978,'002616','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2 (6)','SI-2 (6)'),
(23979,'002617','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2 (6)','SI-2 (6)'),
(23980,'002618','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2 (6)','SI-2 (6)'),
(23981,'002619','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 a','SI-3a.','SI-3'),
(23982,'002620','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 a','SI-3a.','SI-3'),
(23983,'002621','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 a','SI-3a.','SI-3'),
(23984,'002622','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 a','SI-3a.','SI-3'),
(23985,'002623','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c.1.','SI-3'),
(23986,'002624','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c.1.','SI-3'),
(23987,'002625','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (b)','SI-3 (6)(b)','SI-3 (6)'),
(23988,'002626','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (b)','SI-3 (6)(b)','SI-3 (6)'),
(23989,'002627','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (7)','SI-3 (7)','SI-3 (7)'),
(23990,'002628','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8)','SI-3 (8)','SI-3 (8)'),
(23991,'002629','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8)','SI-3 (8)','SI-3 (8)'),
(23992,'002630','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8)','SI-3 (8)','SI-3 (8)'),
(23993,'002631','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8)','SI-3 (8)','SI-3 (8)'),
(23994,'002632','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (9)','SI-3 (9)','SI-3 (9)'),
(23995,'002633','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (9)','SI-3 (9)','SI-3 (9)'),
(23996,'002634','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3 (10)(a)','SI-3 (10)'),
(23997,'002635','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3 (10)(a)','SI-3 (10)'),
(23998,'002636','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3 (10)(a)','SI-3 (10)'),
(23999,'002637','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (9)','SI-3 (9)','SI-3 (9)'),
(24000,'002638','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3 (10)(a)','SI-3 (10)'),
(24001,'002639','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (b)','SI-3 (10)(b)','SI-3 (10)'),
(24002,'002640','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (b)','SI-3 (10)(b)','SI-3 (10)'),
(24003,'002641','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 1','SI-4a.1.','SI-4'),
(24004,'002642','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 2','SI-4a.2.','SI-4'),
(24005,'002643','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 2','SI-4a.2.','SI-4'),
(24006,'002644','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 2','SI-4a.2.','SI-4'),
(24007,'002645','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 b','SI-4b.','SI-4'),
(24008,'002646','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 b','SI-4b.','SI-4'),
(24009,'002647','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 d','SI-4d.','SI-4'),
(24010,'002648','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 d','SI-4d.','SI-4'),
(24011,'002649','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 d','SI-4d.','SI-4'),
(24012,'002650','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g.','SI-4'),
(24013,'002651','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g.','SI-4'),
(24014,'002652','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g.','SI-4'),
(24015,'002653','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4','SI-4','SI-4'),
(24016,'002654','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g.','SI-4'),
(24017,'002655','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (1)','SI-4 (1)','SI-4 (1)'),
(24018,'002656','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (1)','SI-4 (1)','SI-4 (1)'),
(24019,'002657','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (3)','SI-4 (3)','SI-4 (3)'),
(24020,'002658','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (3)','SI-4 (3)','SI-4 (3)'),
(24021,'002659','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4)','SI-4 (4)','SI-4 (4)'),
(24022,'002660','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4)','SI-4 (4)','SI-4 (4)'),
(24023,'002661','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4)','SI-4 (4)','SI-4 (4)'),
(24024,'002662','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4)','SI-4 (4)','SI-4 (4)'),
(24025,'002663','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (5)','SI-4 (5)','SI-4 (5)'),
(24026,'002664','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (5)','SI-4 (5)','SI-4 (5)'),
(24027,'002665','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4 (10)','SI-4 (10)'),
(24028,'002666','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4 (10)','SI-4 (10)'),
(24029,'002667','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4 (10)','SI-4 (10)'),
(24030,'002668','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (11)','SI-4 (11)','SI-4 (11)'),
(24031,'002669','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (13) (c)','SI-4 (13)(c)','SI-4 (13)'),
(24032,'002670','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (18)','SI-4 (18)','SI-4 (18)'),
(24033,'002671','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (18)','SI-4 (18)','SI-4 (18)'),
(24034,'002672','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (18)','SI-4 (18)','SI-4 (18)'),
(24035,'002673','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (19)','SI-4 (19)','SI-4 (19)'),
(24036,'002674','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (19)','SI-4 (19)','SI-4 (19)'),
(24037,'002675','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (19)','SI-4 (19)','SI-4 (19)'),
(24038,'002676','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (20)','SI-4 (20)','SI-4 (20)'),
(24039,'002677','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (20)','SI-4 (20)','SI-4 (20)'),
(24040,'002678','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (21)','SI-4 (21)','SI-4 (21)'),
(24041,'002679','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (21)','SI-4 (21)','SI-4 (21)'),
(24042,'002680','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (21)','SI-4 (21)','SI-4 (21)'),
(24043,'002681','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22)','SI-4 (22)','SI-4 (22)'),
(24044,'002682','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22)','SI-4 (22)','SI-4 (22)'),
(24045,'002683','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22)','SI-4 (22)','SI-4 (22)'),
(24046,'002684','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22)','SI-4 (22)','SI-4 (22)'),
(24047,'002685','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (23)','SI-4 (23)','SI-4 (23)'),
(24048,'002686','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (23)','SI-4 (23)','SI-4 (23)'),
(24049,'002687','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (23)','SI-4 (23)','SI-4 (23)'),
(24050,'002688','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4 (24)','SI-4 (24)'),
(24051,'002689','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4 (24)','SI-4 (24)'),
(24052,'002690','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4 (24)','SI-4 (24)'),
(24053,'002691','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4 (24)','SI-4 (24)'),
(24054,'002692','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 a','SI-5a.','SI-5'),
(24055,'002693','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c.','SI-5'),
(24056,'002694','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c.','SI-5'),
(24057,'002695','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 a','SI-6a.','SI-6'),
(24058,'002696','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 a','SI-6a.','SI-6'),
(24059,'002697','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b.','SI-6'),
(24060,'002698','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b.','SI-6'),
(24061,'002699','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b.','SI-6'),
(24062,'002700','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 c','SI-6c.','SI-6'),
(24063,'002701','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 d','SI-6d.','SI-6'),
(24064,'002702','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 d','SI-6d.','SI-6'),
(24065,'002703','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7','SI-7','SI-7'),
(24066,'002704','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7','SI-7','SI-7'),
(24067,'002705','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24068,'002706','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24069,'002707','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24070,'002708','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24071,'002709','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24072,'002710','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24073,'002711','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24074,'002712','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7 (1)','SI-7 (1)'),
(24075,'002713','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (2)','SI-7 (2)','SI-7 (2)'),
(24076,'002714','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (5)','SI-7 (5)','SI-7 (5)'),
(24077,'002715','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (5)','SI-7 (5)','SI-7 (5)'),
(24078,'002716','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (6)','SI-7 (6)','SI-7 (6)'),
(24079,'002717','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (6)','SI-7 (6)','SI-7 (6)'),
(24080,'002718','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (6)','SI-7 (6)','SI-7 (6)'),
(24081,'002719','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (7)','SI-7 (7)','SI-7 (7)'),
(24082,'002720','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (7)','SI-7 (7)','SI-7 (7)'),
(24083,'002721','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7 (8)','SI-7 (8)'),
(24084,'002722','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7 (8)','SI-7 (8)'),
(24085,'002723','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7 (8)','SI-7 (8)'),
(24086,'002724','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7 (8)','SI-7 (8)'),
(24087,'002725','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (9)','SI-7 (9)','SI-7 (9)'),
(24088,'002726','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (9)','SI-7 (9)','SI-7 (9)'),
(24089,'002727','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (10)','SI-7 (10)','SI-7 (10)'),
(24090,'002728','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (10)','SI-7 (10)','SI-7 (10)'),
(24091,'002729','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (10)','SI-7 (10)','SI-7 (10)'),
(24092,'002730','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (11)','SI-7 (11)','SI-7 (11)'),
(24093,'002731','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (11)','SI-7 (11)','SI-7 (11)'),
(24094,'002732','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (12)','SI-7 (12)','SI-7 (12)'),
(24095,'002733','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (12)','SI-7 (12)','SI-7 (12)'),
(24096,'002734','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (13)','SI-7 (13)','SI-7 (13)'),
(24097,'002735','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (13)','SI-7 (13)','SI-7 (13)'),
(24098,'002736','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (13)','SI-7 (13)','SI-7 (13)'),
(24099,'002737','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (14) (a)','SI-7 (14)(a)','SI-7 (14)'),
(24100,'002738','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (14) (b)','SI-7 (14)(b)','SI-7 (14)'),
(24101,'002739','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (15)','SI-7 (15)','SI-7 (15)'),
(24102,'002740','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (15)','SI-7 (15)','SI-7 (15)'),
(24103,'002741','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 a','SI-8a.','SI-8'),
(24104,'002742','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 a','SI-8a.','SI-8'),
(24105,'002743','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 (3)','SI-8 (3)','SI-8 (3)'),
(24106,'002744','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10','SI-10','SI-10'),
(24107,'002745','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (a)','SI-10 (1)(a)','SI-10 (1)'),
(24108,'002746','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (a)','SI-10 (1)(a)','SI-10 (1)'),
(24109,'002747','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (b)','SI-10 (1)(b)','SI-10 (1)'),
(24110,'002748','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (b)','SI-10 (1)(b)','SI-10 (1)'),
(24111,'002749','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (c)','SI-10 (1)(c)','SI-10 (1)'),
(24112,'002750','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10 (2)','SI-10 (2)'),
(24113,'002751','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10 (2)','SI-10 (2)'),
(24114,'002752','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10 (2)','SI-10 (2)'),
(24115,'002753','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10 (2)','SI-10 (2)'),
(24116,'002754','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (3)','SI-10 (3)','SI-10 (3)'),
(24117,'002755','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (4)','SI-10 (4)','SI-10 (4)'),
(24118,'002756','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (5)','SI-10 (5)','SI-10 (5)'),
(24119,'002757','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (5)','SI-10 (5)','SI-10 (5)'),
(24120,'002758','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (5)','SI-10 (5)','SI-10 (5)'),
(24121,'002759','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-11 b','SI-11b.','SI-11'),
(24122,'002760','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 a','SI-13a.','SI-13'),
(24123,'002761','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 a','SI-13a.','SI-13'),
(24124,'002762','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 b','SI-13b.','SI-13'),
(24125,'002763','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 b','SI-13b.','SI-13'),
(24126,'002764','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
(24127,'002765','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
(24128,'002766','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
(24129,'002767','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
(24130,'002768','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (1)','SI-14 (1)','SI-14 (1)'),
(24131,'002769','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (1)','SI-14 (1)','SI-14 (1)'),
(24132,'002770','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-15','SI-15','SI-15'),
(24133,'002771','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-15','SI-15','SI-15'),
(24134,'002772','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-15','SI-15','SI-15'),
(24135,'002984','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 3','PM-1a.3.','PM-1'),
(24136,'002985','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 1','PM-1a.1.','PM-1'),
(24137,'002986','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 2','PM-1a.2.','PM-1'),
(24138,'002987','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 3','PM-1a.3.','PM-1'),
(24139,'002988','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 4','PM-1a.4.','PM-1'),
(24140,'002989','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 d','PM-1d.','PM-1'),
(24141,'002990','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 d','PM-1d.','PM-1'),
(24142,'002991','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a.1.','PM-4'),
(24143,'002992','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 3','PM-4a.3.','PM-4'),
(24144,'002993','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 b','PM-4b.','PM-4'),
(24145,'002994','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 c','PM-9c.','PM-9'),
(24146,'002995','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 c','PM-9c.','PM-9'),
(24147,'002996','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-12','PM-12','PM-12'),
(24148,'002997','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-13','PM-13','PM-13'),
(24149,'002998','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a.1.','PM-14'),
(24150,'002999','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a.1.','PM-14'),
(24151,'003000','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a.1.','PM-14'),
(24152,'003001','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a.1.','PM-14'),
(24153,'003002','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a.1.','PM-14'),
(24154,'003003','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a.1.','PM-14'),
(24155,'003004','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a.2.','PM-14'),
(24156,'003005','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a.2.','PM-14'),
(24157,'003006','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a.2.','PM-14'),
(24158,'003007','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 b','PM-14b.','PM-14'),
(24159,'003008','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 b','PM-14b.','PM-14'),
(24160,'003009','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 b','PM-14b.','PM-14'),
(24161,'003010','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 a','PM-15a.','PM-15'),
(24162,'003011','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 b','PM-15b.','PM-15'),
(24163,'003012','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 c','PM-15c.','PM-15'),
(24164,'003013','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PM-16','PM-16','PM-16'),
(24165,'003392','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-1','AP-1','AP-1'),
(24166,'003393','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-1','AP-1','AP-1'),
(24167,'003394','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-1','AP-1','AP-1'),
(24168,'003395','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-1','AP-1','AP-1'),
(24169,'003396','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-2','AP-2','AP-2'),
(24170,'003398','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-2','AP-2','AP-2'),
(24171,'003399','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-2','AP-2','AP-2'),
(24172,'003400','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AP-2','AP-2','AP-2'),
(24173,'003397','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 a','AR-1a.','AR-1'),
(24174,'003401','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 b','AR-1b.','AR-1'),
(24175,'003402','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 c','AR-1c.','AR-1'),
(24176,'003403','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 c','AR-1c.','AR-1'),
(24177,'003404','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 c','AR-1c.','AR-1'),
(24178,'003405','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 c','AR-1c.','AR-1'),
(24179,'003406','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 d','AR-1d.','AR-1'),
(24180,'003407','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 e','AR-1e.','AR-1'),
(24181,'003408','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 e','AR-1e.','AR-1'),
(24182,'003409','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 e','AR-1e.','AR-1'),
(24183,'003410','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 e','AR-1e.','AR-1'),
(24184,'003411','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 e','AR-1e.','AR-1'),
(24185,'003412','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 e','AR-1e.','AR-1'),
(24186,'003413','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 f','AR-1f.','AR-1'),
(24187,'003414','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 f','AR-1f.','AR-1'),
(24188,'003415','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 f','AR-1f.','AR-1'),
(24189,'003416','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-1 f','AR-1f.','AR-1'),
(24190,'003417','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24191,'003418','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24192,'003419','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24193,'003420','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24194,'003421','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24195,'003422','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24196,'003423','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24197,'003424','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 a','AR-2a.','AR-2'),
(24198,'003425','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-2 b','AR-2b.','AR-2'),
(24199,'003426','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 a','AR-3a.','AR-3'),
(24200,'003427','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 a','AR-3a.','AR-3'),
(24201,'003428','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 a','AR-3a.','AR-3'),
(24202,'003429','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 a','AR-3a.','AR-3'),
(24203,'003430','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 a','AR-3a.','AR-3'),
(24204,'003431','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 a','AR-3a.','AR-3'),
(24205,'003432','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 b','AR-3b.','AR-3'),
(24206,'003433','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-3 b','AR-3b.','AR-3'),
(24207,'003434','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-4','AR-4','AR-4'),
(24208,'003435','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-4','AR-4','AR-4'),
(24209,'003436','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-4','AR-4','AR-4'),
(24210,'003437','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-4','AR-4','AR-4'),
(24211,'003438','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-4','AR-4','AR-4'),
(24212,'003439','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-4','AR-4','AR-4'),
(24213,'003440','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 a','AR-5a.','AR-5'),
(24214,'003441','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 a','AR-5a.','AR-5'),
(24215,'003442','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 a','AR-5a.','AR-5'),
(24216,'003443','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 b','AR-5b.','AR-5'),
(24217,'003444','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 b','AR-5b.','AR-5'),
(24218,'003445','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 b','AR-5b.','AR-5'),
(24219,'003446','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 b','AR-5b.','AR-5'),
(24220,'003447','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 c','AR-5c.','AR-5'),
(24221,'003448','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-5 c','AR-5c.','AR-5'),
(24222,'003449','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-6','AR-6','AR-6'),
(24223,'003450','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-6','AR-6','AR-6'),
(24224,'003451','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-6','AR-6','AR-6'),
(24225,'003452','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-6','AR-6','AR-6'),
(24226,'003453','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-6','AR-6','AR-6'),
(24227,'003454','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-6','AR-6','AR-6'),
(24228,'003455','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-7','AR-7','AR-7'),
(24229,'003456','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 a (1)','AR-8a(1)','AR-8'),
(24230,'003457','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 a (1)','AR-8a(1)','AR-8'),
(24231,'003458','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 a (1)','AR-8a(1)','AR-8'),
(24232,'003459','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 a (1)','AR-8a(1)','AR-8'),
(24233,'003460','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 a (2)','AR-8a(2)','AR-8'),
(24234,'003461','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 b','AR-8b.','AR-8'),
(24235,'003462','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AR-8 c','AR-8c.','AR-8'),
(24236,'003463','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 a','DI-1a.','DI-1'),
(24237,'003464','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 a','DI-1a.','DI-1'),
(24238,'003465','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 a','DI-1a.','DI-1'),
(24239,'003466','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 a','DI-1a.','DI-1'),
(24240,'003467','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 b','DI-1b.','DI-1'),
(24241,'003468','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 c','DI-1c.','DI-1'),
(24242,'003469','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 c','DI-1c.','DI-1'),
(24243,'003470','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24244,'003471','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24245,'003472','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24246,'003473','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24247,'003474','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24248,'003475','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24249,'003476','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24250,'003477','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 d','DI-1d.','DI-1'),
(24251,'003478','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 (1)','DI-1 (1)','DI-1 (1)'),
(24252,'003479','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 (2)','DI-1 (2)','DI-1 (2)'),
(24253,'003480','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-1 (2)','DI-1 (2)','DI-1 (2)'),
(24254,'003481','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-2 a','DI-2a.','DI-2'),
(24255,'003482','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-2 b','DI-2b.','DI-2'),
(24256,'003483','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-2 b','DI-2b.','DI-2'),
(24257,'003484','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-2 b','DI-2b.','DI-2'),
(24258,'003485','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DI-2 (1)','DI-2 (1)','DI-2 (1)'),
(24259,'003486','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 a','DM-1a.','DM-1'),
(24260,'003487','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 b','DM-1b.','DM-1'),
(24261,'003488','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 b','DM-1b.','DM-1'),
(24262,'003489','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 c','DM-1c.','DM-1'),
(24263,'003490','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 c','DM-1c.','DM-1'),
(24264,'003491','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 c','DM-1c.','DM-1'),
(24265,'003492','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 c','DM-1c.','DM-1'),
(24266,'003493','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 c','DM-1c.','DM-1'),
(24267,'003494','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 c','DM-1c.','DM-1'),
(24268,'003495','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 (1)','DM-1 (1)','DM-1 (1)'),
(24269,'003496','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-1 (1)','DM-1 (1)','DM-1 (1)'),
(24270,'003497','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 a','DM-2a.','DM-2'),
(24271,'003498','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 a','DM-2a.','DM-2'),
(24272,'003499','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 b','DM-2b.','DM-2'),
(24273,'003500','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 b','DM-2b.','DM-2'),
(24274,'003501','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 c','DM-2c.','DM-2'),
(24275,'003502','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 c','DM-2c.','DM-2'),
(24276,'003503','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 (1)','DM-2 (1)','DM-2 (1)'),
(24277,'003504','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 (1)','DM-2 (1)','DM-2 (1)'),
(24278,'003505','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 (1)','DM-2 (1)','DM-2 (1)'),
(24279,'003506','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-2 (1)','DM-2 (1)','DM-2 (1)'),
(24280,'003507','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 a','DM-3a.','DM-3'),
(24281,'003508','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 a','DM-3a.','DM-3'),
(24282,'003509','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 a','DM-3a.','DM-3'),
(24283,'003510','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 a','DM-3a.','DM-3'),
(24284,'003511','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 a','DM-3a.','DM-3'),
(24285,'003512','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 a','DM-3a.','DM-3'),
(24286,'003513','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 b','DM-3b.','DM-3'),
(24287,'003514','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 b','DM-3b.','DM-3'),
(24288,'003515','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 b','DM-3b.','DM-3'),
(24289,'003516','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 (1)','DM-3 (1)','DM-3 (1)'),
(24290,'003517','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 (1)','DM-3 (1)','DM-3 (1)'),
(24291,'003518','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','DM-3 (1)','DM-3 (1)','DM-3 (1)'),
(24292,'003519','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 a','IP-1a.','IP-1'),
(24293,'003520','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 a','IP-1a.','IP-1'),
(24294,'003521','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 a','IP-1a.','IP-1'),
(24295,'003522','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 a','IP-1a.','IP-1'),
(24296,'003523','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 b','IP-1b.','IP-1'),
(24297,'003524','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 b','IP-1b.','IP-1'),
(24298,'003525','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 b','IP-1b.','IP-1'),
(24299,'003526','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 b','IP-1b.','IP-1'),
(24300,'003527','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 c','IP-1c.','IP-1'),
(24301,'003528','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 d','IP-1d.','IP-1'),
(24302,'003529','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 d','IP-1d.','IP-1'),
(24303,'003530','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-1 (1)','IP-1 (1)','IP-1 (1)'),
(24304,'003531','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-2 a','IP-2a.','IP-2'),
(24305,'003532','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-2 b','IP-2b.','IP-2'),
(24306,'003533','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-2 b','IP-2b.','IP-2'),
(24307,'003534','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-2 c','IP-2c.','IP-2'),
(24308,'003535','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-2 d','IP-2d.','IP-2'),
(24309,'003536','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-2 d','IP-2d.','IP-2'),
(24310,'003537','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-3 a','IP-3a.','IP-3'),
(24311,'003538','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-3 b','IP-3b.','IP-3'),
(24312,'003539','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-3 b','IP-3b.','IP-3'),
(24313,'003540','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-4','IP-4','IP-4'),
(24314,'003541','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-4','IP-4','IP-4'),
(24315,'003542','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-4 (1)','IP-4 (1)','IP-4 (1)'),
(24316,'003543','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','IP-4 (1)','IP-4 (1)','IP-4 (1)'),
(24317,'003544','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24318,'003545','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24319,'003546','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24320,'003547','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24321,'003548','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24322,'003549','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24323,'003550','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 a','SE-1a.','SE-1'),
(24324,'003551','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 b','SE-1b.','SE-1'),
(24325,'003552','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-1 b','SE-1b.','SE-1'),
(24326,'003553','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-2 a','SE-2a.','SE-2'),
(24327,'003554','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-2 a','SE-2a.','SE-2'),
(24328,'003555','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SE-2 b','SE-2b.','SE-2'),
(24329,'003556','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24330,'003557','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24331,'003558','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24332,'003559','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24333,'003560','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24334,'003561','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24335,'003562','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24336,'003563','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24337,'003564','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24338,'003565','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24339,'003566','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24340,'003567','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 a','TR-1a.','TR-1'),
(24341,'003568','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24342,'003569','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24343,'003570','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24344,'003571','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24345,'003572','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24346,'003573','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24347,'003574','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24348,'003575','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24349,'003576','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24350,'003577','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 b','TR-1b.','TR-1'),
(24351,'003578','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 c','TR-1c.','TR-1'),
(24352,'003579','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 c','TR-1c.','TR-1'),
(24353,'003580','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-1 (1)','TR-1 (1)','TR-1 (1)'),
(24354,'003581','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-2 a','TR-2a.','TR-2'),
(24355,'003582','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-2 b','TR-2b.','TR-2'),
(24356,'003583','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-2 c','TR-2c.','TR-2'),
(24357,'003584','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-2 (1)','TR-2 (1)','TR-2 (1)'),
(24358,'003585','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-3 a','TR-3a.','TR-3'),
(24359,'003586','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-3 a','TR-3a.','TR-3'),
(24360,'003587','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','TR-3 b','TR-3b.','TR-3'),
(24361,'003588','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-1','UL-1','UL-1'),
(24362,'003589','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 a','UL-2a.','UL-2'),
(24363,'003590','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 b','UL-2b.','UL-2'),
(24364,'003591','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 b','UL-2b.','UL-2'),
(24365,'003592','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 c','UL-2c.','UL-2'),
(24366,'003593','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 c','UL-2c.','UL-2'),
(24367,'003594','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 c','UL-2c.','UL-2'),
(24368,'003595','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 c','UL-2c.','UL-2'),
(24369,'003596','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 d','UL-2d.','UL-2'),
(24370,'003597','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','UL-2 d','UL-2d.','UL-2'),
(24371,'002254','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-12','AC-12','AC-12'),
(24372,'002360','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-12','AC-12','AC-12'),
(24373,'002361','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-12','AC-12','AC-12'),
(24374,'002362','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (1)','AC-12 (1)','AC-12 (1)'),
(24375,'002363','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (1)','AC-12 (1)','AC-12 (1)'),
(24376,'002364','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (1)','AC-12 (1)','AC-12 (1)'),
(24377,'002979','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-20 a','PE-20a.','PE-20'),
(24378,'002980','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-20 a','PE-20a.','PE-20'),
(24379,'002981','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-20 a','PE-20a.','PE-20'),
(24380,'002982','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-20 a','PE-20a.','PE-20'),
(24381,'002983','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PE-20 b','PE-20b.','PE-20'),
(24382,'003372','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 (1)','SA-22 (1)','SA-22 (1)'),
(24383,'003373','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 (1)','SA-22 (1)','SA-22 (1)'),
(24384,'003374','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 b','SA-22b.','SA-22'),
(24385,'003375','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 b','SA-22b.','SA-22'),
(24386,'003376','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 a','SA-22a.','SA-22'),
(24387,'002773','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-17','SI-17','SI-17'),
(24388,'002774','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-17','SI-17','SI-17'),
(24389,'002775','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-17','SI-17','SI-17'),
(24390,'002823','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-16','SI-16','SI-16'),
(24391,'002824','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','SI-16','SI-16','SI-16'),
(24392,'003117','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-9','PL-9','PL-9'),
(24393,'003118','NIST','NIST SP 800-53 Revision 4','4','http://csrc.nist.gov/publications/PubsSPs.html','PL-9','PL-9','PL-9');
/*!40000 ALTER TABLE `cci_reference_map` ENABLE KEYS */;
UNLOCK TABLES;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2020-05-20 20:35:08
================================================
FILE: api/source/service/migrations/sql/0001/down/10-collection-created.sql
================================================
ALTER TABLE `collection`
DROP COLUMN `created`;
================================================
FILE: api/source/service/migrations/sql/0001/up/10-collection-created.sql
================================================
ALTER TABLE `collection`
ADD COLUMN `created` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP AFTER `metadata`;
================================================
FILE: api/source/service/migrations/sql/0002/down/10-collection-description.sql
================================================
ALTER TABLE `collection`
DROP COLUMN `description`;
================================================
FILE: api/source/service/migrations/sql/0002/up/10-collection-description.sql
================================================
ALTER TABLE `collection`
ADD COLUMN `description` VARCHAR(255) NULL AFTER `name`;
================================================
FILE: api/source/service/migrations/sql/0003/up/10-asset-mac-fqdn.sql
================================================
ALTER TABLE `asset`
ADD COLUMN `mac` VARCHAR(17) NULL AFTER `ip`;
ALTER TABLE `asset`
ADD COLUMN `fqdn` VARCHAR(255) NULL AFTER `name`;
================================================
FILE: api/source/service/migrations/sql/0004/up/10-user-data.sql
================================================
ALTER TABLE `user_data`
DROP COLUMN `display`,
DROP COLUMN `email`,
DROP COLUMN `globalAccess`,
DROP COLUMN `canCreateCollection`,
DROP COLUMN `canAdmin`,
DROP COLUMN `metadata`,
DROP COLUMN `disabled`;
ALTER TABLE `user_data` ADD COLUMN `lastClaims` json DEFAULT ('{}');
================================================
FILE: api/source/service/migrations/sql/0005/down/10-v-current-rev.sql
================================================
ALTER VIEW `v_current_rev` AS
select
`rr`.`revId` AS `revId`,`rr`.`benchmarkId` AS `benchmarkId`,`rr`.`version` AS `version`,`rr`.`release` AS `release`,`rr`.`benchmarkDate` AS `benchmarkDate`,`rr`.`benchmarkDateSql` AS `benchmarkDateSql`,`rr`.`status` AS `status`,`rr`.`statusDate` AS `statusDate`,`rr`.`description` AS `description`,`rr`.`active` AS `active`,`rr`.`groupCount` AS `groupCount`,`rr`.`ruleCount` AS `ruleCount`,`rr`.`checkCount` AS `checkCount`,`rr`.`fixCount` AS `fixCount`,`rr`.`ovalCount` AS `ovalCount` from (select `r`.`revId` AS `revId`,`r`.`benchmarkId` AS `benchmarkId`,`r`.`version` AS `version`,`r`.`release` AS `release`,`r`.`benchmarkDate` AS `benchmarkDate`,`r`.`benchmarkDateSql` AS `benchmarkDateSql`,`r`.`status` AS `status`,`r`.`statusDate` AS `statusDate`,`r`.`description` AS `description`,`r`.`active` AS `active`,`r`.`groupCount` AS `groupCount`,`r`.`ruleCount` AS `ruleCount`,`r`.`checkCount` AS `checkCount`,`r`.`fixCount` AS `fixCount`,(select count(`rule_oval_map`.`roId`) from `rule_oval_map` where (`rule_oval_map`.`benchmarkId` = `r`.`benchmarkId`)) AS `ovalCount`,row_number() OVER (PARTITION BY `r`.`benchmarkId` ORDER BY (`r`.`version` + 0) desc,(`r`.`release` + 0) desc ) AS `rn` from `revision` `r` where (`r`.`status` = 'accepted')) `rr` where (`rr`.`rn` = 1);
DELETE from current_rev;
INSERT INTO current_rev (
revId,
benchmarkId,
`version`,
`release`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
ruleCount,
checkCount,
fixCount,
ovalCount)
SELECT
revId,
benchmarkId,
`version`,
`release`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
ruleCount,
checkCount,
fixCount,
ovalCount
FROM
v_current_rev;
DELETE FROM current_group_rule;
INSERT INTO current_group_rule (groupId, ruleId, benchmarkId)
SELECT rg.groupId,
rgr.ruleId,
cr.benchmarkId
from
current_rev cr
left join rev_group_map rg on rg.revId=cr.revId
left join rev_group_rule_map rgr on rgr.rgId=rg.rgId
order by
rg.groupId,rgr.ruleId,cr.benchmarkId;
================================================
FILE: api/source/service/migrations/sql/0005/up/10-v-current-rev.sql
================================================
ALTER VIEW `v_current_rev` AS
select
`rr`.`revId` AS `revId`,
`rr`.`benchmarkId` AS `benchmarkId`,
`rr`.`version` AS `version`,
`rr`.`release` AS `release`,
`rr`.`benchmarkDate` AS `benchmarkDate`,
`rr`.`benchmarkDateSql` AS `benchmarkDateSql`,
`rr`.`status` AS `status`,
`rr`.`statusDate` AS `statusDate`,
`rr`.`description` AS `description`,
`rr`.`active` AS `active`,
`rr`.`groupCount` AS `groupCount`,
`rr`.`ruleCount` AS `ruleCount`,
`rr`.`checkCount` AS `checkCount`,
`rr`.`fixCount` AS `fixCount`,
`rr`.`ovalCount` AS `ovalCount`
from (
select
`r`.`revId` AS `revId`,
`r`.`benchmarkId` AS `benchmarkId`,
`r`.`version` AS `version`,
`r`.`release` AS `release`,
`r`.`benchmarkDate` AS `benchmarkDate`,
`r`.`benchmarkDateSql` AS `benchmarkDateSql`,
`r`.`status` AS `status`,
`r`.`statusDate` AS `statusDate`,
`r`.`description` AS `description`,
`r`.`active` AS `active`,
`r`.`groupCount` AS `groupCount`,
`r`.`ruleCount` AS `ruleCount`,
`r`.`checkCount` AS `checkCount`,
`r`.`fixCount` AS `fixCount`,
(select count(`rule_oval_map`.`roId`) from `rule_oval_map` where (`rule_oval_map`.`benchmarkId` = `r`.`benchmarkId`)) AS `ovalCount`,
row_number() OVER (
PARTITION BY `r`.`benchmarkId`
ORDER BY
FIELD(status, 'draft', 'accepted') desc,
(`r`.`version` + 0) desc,
(`r`.`release` + 0) desc ) AS `rn`
from
`revision` `r`) `rr` where (`rr`.`rn` = 1);
DELETE from current_rev;
INSERT INTO current_rev (
revId,
benchmarkId,
`version`,
`release`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
ruleCount,
checkCount,
fixCount,
ovalCount)
SELECT
revId,
benchmarkId,
`version`,
`release`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
ruleCount,
checkCount,
fixCount,
ovalCount
FROM
v_current_rev;
DELETE FROM current_group_rule;
INSERT INTO current_group_rule (groupId, ruleId, benchmarkId)
SELECT rg.groupId,
rgr.ruleId,
cr.benchmarkId
from
current_rev cr
left join rev_group_map rg on rg.revId=cr.revId
left join rev_group_rule_map rgr on rgr.rgId=rg.rgId
order by
rg.groupId,rgr.ruleId,cr.benchmarkId;
================================================
FILE: api/source/service/migrations/sql/0006/up/10-v-current-rev.sql
================================================
ALTER VIEW `v_current_rev` AS
select
`rr`.`revId` AS `revId`,
`rr`.`benchmarkId` AS `benchmarkId`,
`rr`.`version` AS `version`,
`rr`.`release` AS `release`,
`rr`.`benchmarkDate` AS `benchmarkDate`,
`rr`.`benchmarkDateSql` AS `benchmarkDateSql`,
`rr`.`status` AS `status`,
`rr`.`statusDate` AS `statusDate`,
`rr`.`description` AS `description`,
`rr`.`active` AS `active`,
`rr`.`groupCount` AS `groupCount`,
`rr`.`ruleCount` AS `ruleCount`,
`rr`.`checkCount` AS `checkCount`,
`rr`.`fixCount` AS `fixCount`,
`rr`.`ovalCount` AS `ovalCount`
from (
select
`r`.`revId` AS `revId`,
`r`.`benchmarkId` AS `benchmarkId`,
`r`.`version` AS `version`,
`r`.`release` AS `release`,
`r`.`benchmarkDate` AS `benchmarkDate`,
`r`.`benchmarkDateSql` AS `benchmarkDateSql`,
`r`.`status` AS `status`,
`r`.`statusDate` AS `statusDate`,
`r`.`description` AS `description`,
`r`.`active` AS `active`,
`r`.`groupCount` AS `groupCount`,
`r`.`ruleCount` AS `ruleCount`,
`r`.`checkCount` AS `checkCount`,
`r`.`fixCount` AS `fixCount`,
(select count(distinct `ro`.`ruleId`) from `rule_oval_map` `ro` where `ro`.`ruleId` IN (
SELECT `rgr`.`ruleId` from `rev_group_map` `rg` inner join `rev_group_rule_map` `rgr` on `rg`.`rgId` = `rgr`.`rgId` WHERE `rg`.`revId` = `r`.`revId`)) AS `ovalCount`,
row_number() OVER (
PARTITION BY `r`.`benchmarkId`
ORDER BY
FIELD(status, 'draft', 'accepted') desc,
(`r`.`version` + 0) desc,
(`r`.`release` + 0) desc ) AS `rn`
from
`revision` `r`) `rr` where (`rr`.`rn` = 1);
DELETE from current_rev;
INSERT INTO current_rev (
revId,
benchmarkId,
`version`,
`release`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
ruleCount,
checkCount,
fixCount,
ovalCount)
SELECT
revId,
benchmarkId,
`version`,
`release`,
benchmarkDate,
benchmarkDateSql,
status,
statusDate,
description,
active,
groupCount,
ruleCount,
checkCount,
fixCount,
ovalCount
FROM
v_current_rev;
DELETE FROM current_group_rule;
INSERT INTO current_group_rule (groupId, ruleId, benchmarkId)
SELECT rg.groupId,
rgr.ruleId,
cr.benchmarkId
from
current_rev cr
left join rev_group_map rg on rg.revId=cr.revId
left join rev_group_rule_map rgr on rgr.rgId=rg.rgId
order by
rg.groupId,rgr.ruleId,cr.benchmarkId;
================================================
FILE: api/source/service/migrations/sql/current/10-stigman-tables.sql
================================================
-- MySQL dump 10.13 Distrib 8.0.44, for Linux (x86_64)
--
-- Host: 127.0.0.1 Database: stigman
-- ------------------------------------------------------
-- Server version 8.0.44
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `_migrations`
--
DROP TABLE IF EXISTS `_migrations`;
CREATE TABLE `_migrations` (
`createdAt` datetime DEFAULT CURRENT_TIMESTAMP,
`updatedAt` datetime DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP,
`name` varchar(128) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `asset`
--
DROP TABLE IF EXISTS `asset`;
CREATE TABLE `asset` (
`assetId` int NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`fqdn` varchar(255) DEFAULT NULL,
`collectionId` int NOT NULL,
`ip` varchar(255) DEFAULT NULL,
`mac` varchar(255) DEFAULT NULL,
`description` varchar(255) DEFAULT NULL,
`noncomputing` bit(1) NOT NULL DEFAULT b'0',
`metadata` json NOT NULL,
`state` enum('enabled','disabled') NOT NULL,
`stateDate` datetime DEFAULT NULL,
`stateUserId` int DEFAULT NULL,
`isEnabled` tinyint GENERATED ALWAYS AS ((case when (`state` = _utf8mb4'enabled') then 1 else NULL end)) STORED,
PRIMARY KEY (`assetId`),
UNIQUE KEY `INDEX_NAME_COLLECTION_ENABLED` (`name`,`collectionId`,`isEnabled`),
KEY `INDEX_COMPUTING` (`noncomputing`),
KEY `INDEX_COLLECTIONID` (`collectionId`),
KEY `idx_state` (`state`),
CONSTRAINT `FK_ASSET_2` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `cci`
--
DROP TABLE IF EXISTS `cci`;
CREATE TABLE `cci` (
`cci` varchar(20) NOT NULL,
`status` varchar(20) NOT NULL,
`publishdate` date NOT NULL,
`contributor` varchar(255) NOT NULL,
`type` varchar(20) NOT NULL,
`definition` text NOT NULL,
`apAcronym` varchar(20) DEFAULT NULL,
`implementation` text,
`assessmentProcedure` text,
PRIMARY KEY (`cci`),
KEY `ap` (`apAcronym`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `cci_reference_map`
--
DROP TABLE IF EXISTS `cci_reference_map`;
CREATE TABLE `cci_reference_map` (
`cciRefId` int NOT NULL AUTO_INCREMENT,
`cci` varchar(20) NOT NULL,
`creator` varchar(255) NOT NULL,
`title` varchar(255) NOT NULL,
`version` varchar(255) NOT NULL,
`location` varchar(255) NOT NULL,
`indexDisa` varchar(255) NOT NULL,
`textRefNist` varchar(255) NOT NULL,
`parentControl` varchar(255) NOT NULL,
PRIMARY KEY (`cciRefId`),
KEY `cci` (`cci`),
KEY `textRefNist` (`textRefNist`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `check_content`
--
DROP TABLE IF EXISTS `check_content`;
CREATE TABLE `check_content` (
`ccId` int NOT NULL AUTO_INCREMENT,
`digest` binary(32) GENERATED ALWAYS AS (unhex(sha2(`content`,256))) STORED,
`content` text NOT NULL,
PRIMARY KEY (`ccId`),
UNIQUE KEY `digest_UNIQUE` (`digest`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection`
--
DROP TABLE IF EXISTS `collection`;
CREATE TABLE `collection` (
`collectionId` int NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
`description` varchar(255) DEFAULT NULL,
`settings` json NOT NULL,
`metadata` json NOT NULL,
`created` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
`state` enum('enabled','disabled','cloning') NOT NULL,
`createdUserId` int DEFAULT NULL,
`stateDate` datetime DEFAULT NULL,
`stateUserId` int DEFAULT NULL,
`isNameUnavailable` tinyint GENERATED ALWAYS AS ((case when ((`state` = _utf8mb4'cloning') or (`state` = _utf8mb4'enabled')) then 1 else NULL end)) VIRTUAL,
`isEnabled` tinyint GENERATED ALWAYS AS ((case when (`state` = _utf8mb4'enabled') then 1 else NULL end)) STORED,
PRIMARY KEY (`collectionId`),
UNIQUE KEY `index2` (`name`,`isEnabled`),
UNIQUE KEY `index3` (`name`,`isNameUnavailable`),
KEY `idx_state` (`state`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection_grant`
--
DROP TABLE IF EXISTS `collection_grant`;
CREATE TABLE `collection_grant` (
`grantId` int NOT NULL AUTO_INCREMENT,
`collectionId` int NOT NULL,
`userId` int DEFAULT NULL,
`userGroupId` int DEFAULT NULL,
`roleId` int NOT NULL,
PRIMARY KEY (`grantId`),
UNIQUE KEY `INDEX_USER` (`userId`,`collectionId`),
UNIQUE KEY `INDEX_USER_GROUP` (`userGroupId`,`collectionId`),
KEY `INDEX_COLLECTION` (`collectionId`,`roleId`),
CONSTRAINT `fk_collection_grant_1` FOREIGN KEY (`userId`) REFERENCES `user_data` (`userId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_2` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_3` FOREIGN KEY (`userGroupId`) REFERENCES `user_group` (`userGroupId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection_grant_acl`
--
DROP TABLE IF EXISTS `collection_grant_acl`;
CREATE TABLE `collection_grant_acl` (
`cgAclId` int NOT NULL AUTO_INCREMENT,
`grantId` int NOT NULL,
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs DEFAULT NULL,
`assetId` int DEFAULT NULL,
`clId` int DEFAULT NULL,
`access` enum('none','r','rw') NOT NULL,
`modifiedUserId` int DEFAULT NULL,
`modifiedDate` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`cgAclId`),
KEY `fk_collection_grant_acl_1` (`grantId`),
KEY `fk_collection_grant_acl_2` (`assetId`,`benchmarkId`),
KEY `fk_collection_grant_acl_3` (`benchmarkId`,`assetId`),
KEY `fk_collection_grant_acl_4` (`clId`,`benchmarkId`),
CONSTRAINT `fk_collection_grant_acl_1` FOREIGN KEY (`grantId`) REFERENCES `collection_grant` (`grantId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_acl_2` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_acl_3` FOREIGN KEY (`benchmarkId`) REFERENCES `stig` (`benchmarkId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_acl_4` FOREIGN KEY (`clId`) REFERENCES `collection_label` (`clId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_grant_acl_5` FOREIGN KEY (`benchmarkId`, `assetId`) REFERENCES `stig_asset_map` (`benchmarkId`, `assetId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection_label`
--
DROP TABLE IF EXISTS `collection_label`;
CREATE TABLE `collection_label` (
`clId` int NOT NULL AUTO_INCREMENT,
`collectionId` int NOT NULL,
`name` varchar(36) NOT NULL,
`description` varchar(45) DEFAULT NULL,
`color` varchar(6) NOT NULL,
`uuid` binary(16) NOT NULL,
PRIMARY KEY (`clId`),
UNIQUE KEY `colname` (`collectionId`,`name`),
KEY `index4` (`uuid`),
CONSTRAINT `fk_collection_label_1` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection_label_asset_map`
--
DROP TABLE IF EXISTS `collection_label_asset_map`;
CREATE TABLE `collection_label_asset_map` (
`claId` int NOT NULL AUTO_INCREMENT,
`assetId` int NOT NULL,
`clId` int NOT NULL,
PRIMARY KEY (`claId`),
UNIQUE KEY `index4` (`assetId`,`clId`),
KEY `fk_collection_label_asset_map_2` (`clId`),
CONSTRAINT `fk_collection_label_asset_map_1` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_collection_label_asset_map_2` FOREIGN KEY (`clId`) REFERENCES `collection_label` (`clId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `collection_rev_map`
--
DROP TABLE IF EXISTS `collection_rev_map`;
CREATE TABLE `collection_rev_map` (
`crId` int NOT NULL AUTO_INCREMENT,
`collectionId` int NOT NULL,
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs DEFAULT NULL,
`revId` varchar(255) NOT NULL,
PRIMARY KEY (`crId`),
UNIQUE KEY `index_collection_benchmark` (`collectionId`,`benchmarkId`),
KEY `index_revId` (`revId`),
CONSTRAINT `fk_collection_rev_map_1` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `config`
--
DROP TABLE IF EXISTS `config`;
CREATE TABLE `config` (
`key` varchar(45) NOT NULL,
`value` varchar(255) NOT NULL,
PRIMARY KEY (`key`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `current_rev`
--
DROP TABLE IF EXISTS `current_rev`;
CREATE TABLE `current_rev` (
`revId` varchar(255) NOT NULL,
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs DEFAULT NULL,
`version` int NOT NULL,
`release` varchar(45) NOT NULL,
`benchmarkDate` varchar(45) DEFAULT NULL,
`benchmarkDateSql` date DEFAULT NULL,
`status` varchar(45) DEFAULT NULL,
`statusDate` varchar(45) DEFAULT NULL,
`marking` varchar(10) DEFAULT NULL,
`description` varchar(4000) DEFAULT NULL,
`active` tinyint DEFAULT NULL,
`groupCount` int NOT NULL DEFAULT '0',
`ruleCount` int GENERATED ALWAYS AS (((`highCount` + `mediumCount`) + `lowCount`)) STORED,
`checkCount` int NOT NULL DEFAULT '0',
`fixCount` int NOT NULL DEFAULT '0',
`lowCount` int NOT NULL DEFAULT '0',
`mediumCount` int NOT NULL DEFAULT '0',
`highCount` int NOT NULL DEFAULT '0',
PRIMARY KEY (`revId`),
UNIQUE KEY `index2` (`benchmarkId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `default_rev`
--
DROP TABLE IF EXISTS `default_rev`;
CREATE TABLE `default_rev` (
`vdId` int NOT NULL AUTO_INCREMENT,
`collectionId` int NOT NULL,
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs NOT NULL,
`revId` varchar(255) NOT NULL,
`revisionPinned` tinyint NOT NULL,
PRIMARY KEY (`vdId`),
UNIQUE KEY `index2` (`collectionId`,`benchmarkId`),
KEY `index3` (`benchmarkId`),
KEY `index4` (`revId`),
CONSTRAINT `fk_default_rev_2` FOREIGN KEY (`collectionId`) REFERENCES `collection` (`collectionId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Temporary view structure for view `enabled_asset`
--
DROP TABLE IF EXISTS `enabled_asset`;
/*!50001 DROP VIEW IF EXISTS `enabled_asset`*/;
/*!50001 CREATE VIEW `enabled_asset` AS SELECT
1 AS `assetId`,
1 AS `name`,
1 AS `fqdn`,
1 AS `collectionId`,
1 AS `ip`,
1 AS `mac`,
1 AS `description`,
1 AS `noncomputing`,
1 AS `metadata`,
1 AS `state`,
1 AS `stateDate`,
1 AS `stateUserId`,
1 AS `isEnabled`*/;
--
-- Temporary view structure for view `enabled_collection`
--
DROP TABLE IF EXISTS `enabled_collection`;
/*!50001 DROP VIEW IF EXISTS `enabled_collection`*/;
/*!50001 CREATE VIEW `enabled_collection` AS SELECT
1 AS `collectionId`,
1 AS `name`,
1 AS `description`,
1 AS `settings`,
1 AS `metadata`,
1 AS `created`,
1 AS `state`,
1 AS `createdUserId`,
1 AS `stateDate`,
1 AS `stateUserId`,
1 AS `isNameUnavailable`,
1 AS `isEnabled`*/;
--
-- Table structure for table `fix_text`
--
DROP TABLE IF EXISTS `fix_text`;
CREATE TABLE `fix_text` (
`ftId` int NOT NULL AUTO_INCREMENT,
`digest` binary(32) GENERATED ALWAYS AS (unhex(sha2(`text`,256))) STORED,
`text` text NOT NULL,
PRIMARY KEY (`ftId`),
UNIQUE KEY `digest_UNIQUE` (`digest`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `job`
--
DROP TABLE IF EXISTS `job`;
CREATE TABLE `job` (
`jobId` int NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
`description` varchar(255) DEFAULT NULL,
`createdBy` int DEFAULT NULL,
`updatedBy` int DEFAULT NULL,
`created` timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
`updated` timestamp(3) NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP(3),
PRIMARY KEY (`jobId`),
UNIQUE KEY `idx_job_name` (`name`),
KEY `fk_job_updatedBy` (`updatedBy`),
KEY `fk_job_createdBy` (`createdBy`),
CONSTRAINT `fk_job_createdBy` FOREIGN KEY (`createdBy`) REFERENCES `user_data` (`userId`) ON DELETE RESTRICT,
CONSTRAINT `fk_job_updatedBy` FOREIGN KEY (`updatedBy`) REFERENCES `user_data` (`userId`) ON DELETE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `job_run`
--
DROP TABLE IF EXISTS `job_run`;
CREATE TABLE `job_run` (
`jrId` int NOT NULL AUTO_INCREMENT,
`jobId` int NOT NULL,
`runId` binary(16) NOT NULL,
`state` varchar(255) DEFAULT NULL,
`created` timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
`updated` timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) ON UPDATE CURRENT_TIMESTAMP(3),
PRIMARY KEY (`jrId`),
UNIQUE KEY `idx_job_run_runId` (`runId`),
KEY `fk_job_run_jobId` (`jobId`),
CONSTRAINT `fk_job_run_jobId` FOREIGN KEY (`jobId`) REFERENCES `job` (`jobId`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `job_task_map`
--
DROP TABLE IF EXISTS `job_task_map`;
CREATE TABLE `job_task_map` (
`jtId` int NOT NULL AUTO_INCREMENT,
`jobId` int NOT NULL,
`taskId` int NOT NULL,
`created` timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
`updated` timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) ON UPDATE CURRENT_TIMESTAMP(3),
PRIMARY KEY (`jtId`),
KEY `fk_job_task_jobId` (`jobId`),
KEY `fk_job_task_taskId` (`taskId`),
CONSTRAINT `fk_job_task_jobId` FOREIGN KEY (`jobId`) REFERENCES `job` (`jobId`) ON DELETE CASCADE,
CONSTRAINT `fk_job_task_taskId` FOREIGN KEY (`taskId`) REFERENCES `task` (`taskId`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `result`
--
DROP TABLE IF EXISTS `result`;
CREATE TABLE `result` (
`resultId` int NOT NULL AUTO_INCREMENT,
`api` varchar(32) NOT NULL,
`ckl` varchar(32) NOT NULL,
`cklb` varchar(32) NOT NULL,
`abbr` varchar(2) NOT NULL,
`en` varchar(64) NOT NULL,
PRIMARY KEY (`resultId`),
UNIQUE KEY `RESULT_API` (`api`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_group_rule_cci_map`
--
DROP TABLE IF EXISTS `rev_group_rule_cci_map`;
CREATE TABLE `rev_group_rule_cci_map` (
`rgrccId` int NOT NULL AUTO_INCREMENT,
`rgrId` int NOT NULL,
`cci` varchar(20) NOT NULL,
PRIMARY KEY (`rgrccId`),
UNIQUE KEY `index2` (`rgrId`,`cci`),
KEY `index3` (`cci`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rev_group_rule_map`
--
DROP TABLE IF EXISTS `rev_group_rule_map`;
CREATE TABLE `rev_group_rule_map` (
`rgrId` int NOT NULL AUTO_INCREMENT,
`revId` varchar(255) DEFAULT NULL,
`groupId` varchar(45) DEFAULT NULL,
`groupTitle` varchar(255) DEFAULT NULL,
`groupSeverity` varchar(45) DEFAULT NULL,
`ruleId` varchar(255) DEFAULT NULL,
`version` varchar(45) DEFAULT NULL,
`title` varchar(1000) DEFAULT NULL,
`severity` varchar(45) DEFAULT NULL,
`weight` varchar(45) DEFAULT NULL,
`vulnDiscussion` text,
`falsePositives` text,
`falseNegatives` text,
`documentable` varchar(45) DEFAULT NULL,
`mitigations` text,
`severityOverrideGuidance` text,
`potentialImpacts` text,
`thirdPartyTools` text,
`mitigationControl` text,
`responsibility` varchar(255) DEFAULT NULL,
`iaControls` varchar(255) DEFAULT NULL,
`checkSystem` varchar(255) DEFAULT NULL,
`checkDigest` binary(32) DEFAULT NULL,
`fixref` varchar(255) DEFAULT NULL,
`fixDigest` binary(32) DEFAULT NULL,
PRIMARY KEY (`rgrId`),
UNIQUE KEY `rev_group_rule_UNIQUE` (`revId`,`groupId`,`ruleId`),
KEY `idx_rgrm_ruleId` (`ruleId`),
KEY `index5` (`fixDigest`),
KEY `idx_version_check_digest` (`version`,`checkDigest`),
CONSTRAINT `fk_rev_group_rule_map_1` FOREIGN KEY (`revId`) REFERENCES `revision` (`revId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `review`
--
DROP TABLE IF EXISTS `review`;
CREATE TABLE `review` (
`reviewId` int NOT NULL AUTO_INCREMENT,
`assetId` int DEFAULT NULL,
`ruleId` varchar(45) DEFAULT NULL,
`resultId` int DEFAULT NULL,
`detail` mediumtext,
`comment` mediumtext,
`autoResult` bit(1) DEFAULT b'0',
`ts` datetime NOT NULL,
`userId` int DEFAULT NULL,
`statusId` int NOT NULL,
`statusText` varchar(512) DEFAULT NULL,
`statusUserId` int DEFAULT NULL,
`statusTs` datetime DEFAULT NULL,
`metadata` json NOT NULL DEFAULT (json_object()),
`touchTs` datetime GENERATED ALWAYS AS (greatest(`ts`,`statusTs`)) STORED,
`resultEngine` json DEFAULT NULL,
`reProduct` varchar(255) GENERATED ALWAYS AS (json_unquote(json_extract(`resultEngine`,_utf8mb4'$.product'))) VIRTUAL,
`reType` varchar(255) GENERATED ALWAYS AS (json_unquote(json_extract(`resultEngine`,_utf8mb4'$.type'))) VIRTUAL,
`reAuthority` varchar(255) GENERATED ALWAYS AS (json_unquote(json_extract(`resultEngine`,_utf8mb4'$.overrides[0].authority'))) VIRTUAL,
`version` varchar(45) NOT NULL,
`checkDigest` binary(32) NOT NULL,
PRIMARY KEY (`reviewId`),
KEY `INDEX_RESULTID` (`resultId`),
KEY `INDEX_RULEID` (`ruleId`),
KEY `INDEX_STATUSID` (`statusId`),
KEY `idx_vcd` (`version`,`checkDigest`),
KEY `idx_asset_vcd` (`assetId`,`version`,`checkDigest`),
KEY `idx_reProduct` (`reProduct`),
KEY `idx_reType` (`reType`),
KEY `idx_reAuthority` (`reAuthority`),
CONSTRAINT `FK_REVIEWS_1` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `review_history`
--
DROP TABLE IF EXISTS `review_history`;
CREATE TABLE `review_history` (
`historyId` bigint unsigned NOT NULL AUTO_INCREMENT,
`reviewId` int NOT NULL,
`resultId` int NOT NULL,
`detail` mediumtext,
`comment` mediumtext,
`autoResult` bit(1) DEFAULT NULL,
`ts` datetime NOT NULL,
`userId` int DEFAULT NULL,
`statusId` int NOT NULL,
`statusText` varchar(512) DEFAULT NULL,
`statusUserId` int DEFAULT NULL,
`statusTs` datetime DEFAULT NULL,
`touchTs` datetime DEFAULT NULL,
`resultEngine` json DEFAULT NULL,
`reProduct` varchar(255) GENERATED ALWAYS AS (json_unquote(json_extract(`resultEngine`,_utf8mb4'$.product'))) VIRTUAL,
`reType` varchar(255) GENERATED ALWAYS AS (json_unquote(json_extract(`resultEngine`,_utf8mb4'$.type'))) VIRTUAL,
`reAuthority` varchar(255) GENERATED ALWAYS AS (json_unquote(json_extract(`resultEngine`,_utf8mb4'$.overrides[0].authority'))) VIRTUAL,
`ruleId` varchar(45) DEFAULT NULL,
PRIMARY KEY (`historyId`),
KEY `index_reviewId` (`reviewId`),
KEY `idx_reProduct` (`reProduct`),
KEY `idx_reType` (`reType`),
KEY `idx_reAuthority` (`reAuthority`),
CONSTRAINT `fk_review_history_1` FOREIGN KEY (`reviewId`) REFERENCES `review` (`reviewId`) ON DELETE CASCADE ON UPDATE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `revision`
--
DROP TABLE IF EXISTS `revision`;
CREATE TABLE `revision` (
`revId` varchar(255) NOT NULL,
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs DEFAULT NULL,
`version` int NOT NULL,
`release` varchar(45) NOT NULL,
`revisionStr` varchar(45) GENERATED ALWAYS AS (concat(_utf8mb4'V',`version`,_utf8mb4'R',`release`)) VIRTUAL,
`benchmarkDate` varchar(45) DEFAULT NULL,
`benchmarkDateSql` date DEFAULT NULL,
`status` varchar(45) DEFAULT NULL,
`statusDate` varchar(45) DEFAULT NULL,
`marking` varchar(10) DEFAULT NULL,
`description` varchar(4000) DEFAULT NULL,
`active` tinyint DEFAULT '1',
`groupCount` int NOT NULL DEFAULT '0',
`ruleCount` int GENERATED ALWAYS AS (((`highCount` + `mediumCount`) + `lowCount`)) STORED,
`checkCount` int NOT NULL DEFAULT '0',
`fixCount` int NOT NULL DEFAULT '0',
`lowCount` int NOT NULL DEFAULT '0',
`mediumCount` int NOT NULL DEFAULT '0',
`highCount` int NOT NULL DEFAULT '0',
PRIMARY KEY (`revId`),
UNIQUE KEY `uidx_revision_benchmarkId_version_release` (`benchmarkId`,`version`,`release`),
KEY `idx_revision_benchmark_revisionStr` (`benchmarkId`,`revisionStr`),
CONSTRAINT `FK_REVISION_1` FOREIGN KEY (`benchmarkId`) REFERENCES `stig` (`benchmarkId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `rule_version_check_digest`
--
DROP TABLE IF EXISTS `rule_version_check_digest`;
CREATE TABLE `rule_version_check_digest` (
`ruleId` varchar(255) NOT NULL,
`version` varchar(45) NOT NULL,
`checkDigest` binary(32) NOT NULL,
PRIMARY KEY (`ruleId`),
KEY `index_vcd` (`version`,`checkDigest`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `severity_cat_map`
--
DROP TABLE IF EXISTS `severity_cat_map`;
CREATE TABLE `severity_cat_map` (
`id` int NOT NULL AUTO_INCREMENT,
`severity` varchar(45) NOT NULL,
`cat` int NOT NULL,
`roman` varchar(45) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_scm_severity` (`severity`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `status`
--
DROP TABLE IF EXISTS `status`;
CREATE TABLE `status` (
`statusId` int NOT NULL,
`api` varchar(16) NOT NULL,
`en` varchar(16) NOT NULL,
PRIMARY KEY (`statusId`),
UNIQUE KEY `IDX_API` (`api`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `stig`
--
DROP TABLE IF EXISTS `stig`;
CREATE TABLE `stig` (
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs NOT NULL,
`title` varchar(255) NOT NULL,
PRIMARY KEY (`benchmarkId`),
KEY `idx_benchmark_title` (`title`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `stig_asset_map`
--
DROP TABLE IF EXISTS `stig_asset_map`;
CREATE TABLE `stig_asset_map` (
`saId` int NOT NULL AUTO_INCREMENT,
`benchmarkId` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs DEFAULT NULL,
`assetId` int NOT NULL,
`userIds` json DEFAULT NULL,
`minTs` datetime DEFAULT NULL,
`maxTs` datetime DEFAULT NULL,
`saved` int DEFAULT NULL,
`savedResultEngine` int DEFAULT NULL,
`submitted` int DEFAULT NULL,
`submittedResultEngine` int DEFAULT NULL,
`rejected` int DEFAULT NULL,
`rejectedResultEngine` int DEFAULT NULL,
`accepted` int DEFAULT NULL,
`acceptedResultEngine` int DEFAULT NULL,
`highCount` int DEFAULT NULL,
`mediumCount` int DEFAULT NULL,
`lowCount` int DEFAULT NULL,
`notchecked` int DEFAULT NULL,
`notcheckedResultEngine` int DEFAULT NULL,
`notapplicable` int DEFAULT NULL,
`notapplicableResultEngine` int DEFAULT NULL,
`pass` int DEFAULT NULL,
`passResultEngine` int DEFAULT NULL,
`fail` int DEFAULT NULL,
`failResultEngine` int DEFAULT NULL,
`unknown` int DEFAULT NULL,
`unknownResultEngine` int DEFAULT NULL,
`error` int DEFAULT NULL,
`errorResultEngine` int DEFAULT NULL,
`notselected` int DEFAULT NULL,
`notselectedResultEngine` int DEFAULT NULL,
`informational` int DEFAULT NULL,
`informationalResultEngine` int DEFAULT NULL,
`fixed` int DEFAULT NULL,
`fixedResultEngine` int DEFAULT NULL,
`maxTouchTs` datetime DEFAULT NULL,
`assessedHighCount` int DEFAULT NULL,
`assessedMediumCount` int DEFAULT NULL,
`assessedLowCount` int DEFAULT NULL,
PRIMARY KEY (`saId`),
UNIQUE KEY `IDX_BAID` (`benchmarkId`,`assetId`),
KEY `IDX_ASSETID` (`assetId`),
CONSTRAINT `FK_STIG_ASSET_MAP_1` FOREIGN KEY (`assetId`) REFERENCES `asset` (`assetId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `FK_STIG_ASSET_MAP_2` FOREIGN KEY (`benchmarkId`) REFERENCES `stig` (`benchmarkId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `task`
--
DROP TABLE IF EXISTS `task`;
CREATE TABLE `task` (
`taskId` int NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
`description` varchar(255) DEFAULT NULL,
`command` varchar(255) NOT NULL,
PRIMARY KEY (`taskId`),
UNIQUE KEY `idx_task_name` (`name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `task_output`
--
DROP TABLE IF EXISTS `task_output`;
CREATE TABLE `task_output` (
`seq` int NOT NULL AUTO_INCREMENT,
`ts` timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
`runId` binary(16) DEFAULT NULL,
`taskId` int DEFAULT NULL,
`type` varchar(45) NOT NULL,
`message` varchar(255) NOT NULL,
PRIMARY KEY (`seq`),
KEY `fk_task_output_runId` (`runId`),
KEY `fk_task_output_taskId` (`taskId`),
CONSTRAINT `fk_task_output_runId` FOREIGN KEY (`runId`) REFERENCES `job_run` (`runId`) ON DELETE CASCADE,
CONSTRAINT `fk_task_output_taskId` FOREIGN KEY (`taskId`) REFERENCES `task` (`taskId`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `user_data`
--
DROP TABLE IF EXISTS `user_data`;
CREATE TABLE `user_data` (
`userId` int NOT NULL AUTO_INCREMENT,
`username` varchar(255) NOT NULL,
`created` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
`lastAccess` int DEFAULT NULL,
`lastClaims` json DEFAULT (_utf8mb4'{}'),
`status` enum('available','unavailable') NOT NULL DEFAULT 'available',
`statusDate` datetime NOT NULL DEFAULT (`created`),
`statusUser` int DEFAULT NULL,
`webPreferences` json NOT NULL DEFAULT (_utf8mb4'{"darkMode": true, "lastWhatsNew": "2000-01-01"}'),
PRIMARY KEY (`userId`),
UNIQUE KEY `INDEX_username` (`username`),
KEY `INDEX_status` (`status`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `user_group`
--
DROP TABLE IF EXISTS `user_group`;
CREATE TABLE `user_group` (
`userGroupId` int NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`description` varchar(255) DEFAULT NULL,
`createdUserId` int NOT NULL,
`createdDate` datetime DEFAULT CURRENT_TIMESTAMP,
`modifiedUserId` int NOT NULL,
`modifiedDate` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`userGroupId`),
UNIQUE KEY `idx_name` (`name`),
KEY `fk_user_group_1_idx` (`createdUserId`),
KEY `fk_user_group_2_idx` (`modifiedUserId`),
CONSTRAINT `fk_user_group_1` FOREIGN KEY (`createdUserId`) REFERENCES `user_data` (`userId`) ON DELETE RESTRICT ON UPDATE RESTRICT,
CONSTRAINT `fk_user_group_2` FOREIGN KEY (`modifiedUserId`) REFERENCES `user_data` (`userId`) ON DELETE RESTRICT ON UPDATE RESTRICT
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Table structure for table `user_group_user_map`
--
DROP TABLE IF EXISTS `user_group_user_map`;
CREATE TABLE `user_group_user_map` (
`ugumId` int NOT NULL AUTO_INCREMENT,
`userGroupId` int NOT NULL,
`userId` int NOT NULL,
PRIMARY KEY (`ugumId`),
UNIQUE KEY `INDEX_UG_USER` (`userGroupId`,`userId`),
KEY `fk_user_group_map_2_idx` (`userId`),
CONSTRAINT `fk_user_group_map_1` FOREIGN KEY (`userGroupId`) REFERENCES `user_group` (`userGroupId`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `fk_user_group_map_2` FOREIGN KEY (`userId`) REFERENCES `user_data` (`userId`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
--
-- Temporary view structure for view `v_current_rev`
--
DROP TABLE IF EXISTS `v_current_rev`;
/*!50001 DROP VIEW IF EXISTS `v_current_rev`*/;
/*!50001 CREATE VIEW `v_current_rev` AS SELECT
1 AS `revId`,
1 AS `benchmarkId`,
1 AS `version`,
1 AS `release`,
1 AS `benchmarkDate`,
1 AS `benchmarkDateSql`,
1 AS `status`,
1 AS `statusDate`,
1 AS `marking`,
1 AS `description`,
1 AS `active`,
1 AS `groupCount`,
1 AS `ruleCount`,
1 AS `lowCount`,
1 AS `mediumCount`,
1 AS `highCount`,
1 AS `checkCount`,
1 AS `fixCount`*/;
--
-- Temporary view structure for view `v_default_rev`
--
DROP TABLE IF EXISTS `v_default_rev`;
/*!50001 DROP VIEW IF EXISTS `v_default_rev`*/;
/*!50001 CREATE VIEW `v_default_rev` AS SELECT
1 AS `collectionId`,
1 AS `benchmarkId`,
1 AS `revId`,
1 AS `revisionPinned`*/;
--
-- Temporary view structure for view `v_latest_rev`
--
DROP TABLE IF EXISTS `v_latest_rev`;
/*!50001 DROP VIEW IF EXISTS `v_latest_rev`*/;
/*!50001 CREATE VIEW `v_latest_rev` AS SELECT
1 AS `revId`,
1 AS `benchmarkId`,
1 AS `revisionStr`*/;
--
-- Dumping events for database 'stigman'
--
/*!50106 SET @save_time_zone= @@TIME_ZONE */ ;
/*!50106 DROP EVENT IF EXISTS `job-1-stigman` */;
DELIMITER $
/*!50003 SET @saved_col_connection = @@collation_connection */ $
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ $
/*!50003 SET @saved_sql_mode = @@sql_mode */ $
/*!50003 SET sql_mode = 'IGNORE_SPACE,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION' */ $
/*!50003 SET @saved_time_zone = @@time_zone */ $
/*!50003 SET time_zone = 'SYSTEM' */ $
/*!50106 CREATE*/ /*!50117 */ /*!50106 EVENT `job-1-stigman` ON SCHEDULE EVERY 1 DAY STARTS '2025-10-01 05:00:00' ON COMPLETION NOT PRESERVE DISABLE DO CALL run_job(1, NULL) */ $
/*!50003 SET time_zone = @saved_time_zone */ $
/*!50003 SET sql_mode = @saved_sql_mode */ $
/*!50003 SET collation_connection = @saved_col_connection */ $
DELIMITER ;
/*!50106 SET TIME_ZONE= @save_time_zone */ ;
--
-- Dumping routines for database 'stigman'
--
/*!50003 DROP PROCEDURE IF EXISTS `analyze_tables` */;
/*!50003 SET @saved_col_connection = @@collation_connection */ ;
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ ;
/*!50003 SET @saved_sql_mode = @@sql_mode */ ;
/*!50003 SET sql_mode = 'IGNORE_SPACE,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION' */ ;
DELIMITER $
CREATE PROCEDURE `analyze_tables`(IN in_tables JSON)
BEGIN
DECLARE v_itemCount INT;
DECLARE v_currentCount INT;
DECLARE v_table VARCHAR(255);
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1
err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
IF err_msg = NULL THEN
SET err_msg = '';
END IF;
CALL task_output('error',concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info', 'task started');
select JSON_LENGTH(in_tables) INTO v_itemCount;
SET v_currentCount = 0;
WHILE v_currentCount < v_itemCount DO
SET v_table = json_unquote(json_extract(in_tables, concat('$[', v_currentCount, ']')));
CALL task_output('info', concat('analyze table: ', v_table));
SET @sql = CONCAT('ANALYZE TABLE ', v_table);
PREPARE stmt_analyze_tables FROM @sql;
EXECUTE stmt_analyze_tables;
DEALLOCATE PREPARE stmt_analyze_tables;
SET v_currentCount = v_currentCount + 1;
END WHILE;
CALL task_output('info', 'task finished');
END $
DELIMITER ;
/*!50003 SET sql_mode = @saved_sql_mode */ ;
/*!50003 SET collation_connection = @saved_col_connection */ ;
/*!50003 DROP PROCEDURE IF EXISTS `delete_disabled` */;
/*!50003 SET @saved_col_connection = @@collation_connection */ ;
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ ;
/*!50003 SET @saved_sql_mode = @@sql_mode */ ;
/*!50003 SET sql_mode = 'IGNORE_SPACE,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION' */ ;
DELIMITER $
CREATE PROCEDURE `delete_disabled`()
BEGIN
DECLARE v_incrementValue INT DEFAULT 10000;
DECLARE v_curMinId BIGINT DEFAULT 1;
DECLARE v_curMaxId BIGINT DEFAULT v_incrementValue + 1;
DECLARE v_numCollectionIds INT;
DECLARE v_numAssetIds INT;
DECLARE v_numReviewIds INT;
DECLARE v_numHistoryIds INT;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1 err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error', concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info','task started');
drop temporary table if exists t_collectionIds;
create temporary table t_collectionIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select collectionId from collection where isEnabled is null;
select max(seq) into v_numCollectionIds from t_collectionIds;
CALL task_output('info', concat('found ', ifnull(v_numCollectionIds, 0), ' collections to delete'));
drop temporary table if exists t_assetIds;
create temporary table t_assetIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select assetId from asset where isEnabled is null or collectionId in (select collectionId from t_collectionIds);
select max(seq) into v_numAssetIds from t_assetIds;
CALL task_output('info', concat('found ', ifnull(v_numAssetIds, 0), ' assets to delete'));
drop temporary table if exists t_reviewIds;
create temporary table t_reviewIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select reviewId from review where assetId in (select assetId from t_assetIds);
select max(seq) into v_numReviewIds from t_reviewIds;
CALL task_output('info', concat('found ', ifnull(v_numReviewIds, 0), ' reviews to delete'));
drop temporary table if exists t_historyIds;
create temporary table t_historyIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select historyId from review_history where reviewId in (select reviewId from t_reviewIds);
select max(seq) into v_numHistoryIds from t_historyIds;
CALL task_output('info', concat('found ', ifnull(v_numHistoryIds, 0), ' history records to delete'));
IF v_numHistoryIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numHistoryIds, ' history records'));
REPEAT
delete from review_history where historyId IN (
select historyId from t_historyIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_historyIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numReviewIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numReviewIds, ' reviews'));
REPEAT
delete from review where reviewId IN (
select reviewId from t_reviewIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_reviewIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numAssetIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numAssetIds, ' assets'));
REPEAT
delete from asset where assetId IN (
select assetId from t_assetIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_assetIds;
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
IF v_numCollectionIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numCollectionIds, ' collections'));
REPEAT
delete from collection where collectionId IN (
select collectionId from t_collectionIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
drop temporary table if exists t_collectionIds;
CALL task_output('info', 'task finished');
END $
DELIMITER ;
/*!50003 SET sql_mode = @saved_sql_mode */ ;
/*!50003 SET collation_connection = @saved_col_connection */ ;
/*!50003 DROP PROCEDURE IF EXISTS `delete_unmapped` */;
/*!50003 SET @saved_col_connection = @@collation_connection */ ;
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ ;
/*!50003 SET @saved_sql_mode = @@sql_mode */ ;
/*!50003 SET sql_mode = 'IGNORE_SPACE,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION' */ ;
DELIMITER $
CREATE PROCEDURE `delete_unmapped`(IN in_context VARCHAR(255))
BEGIN
DECLARE v_numReviewIds INT;
DECLARE v_numHistoryIds INT;
DECLARE v_incrementValue INT DEFAULT 10000;
DECLARE v_curMinId BIGINT DEFAULT 1;
DECLARE v_curMaxId BIGINT DEFAULT v_incrementValue + 1;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1
err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error',concat('code: ', err_code, ' message: ', err_msg));
RESIGNAL;
END;
-- Runtime context is available via user variables (null if running outside a job)
CALL task_output('info', 'task started');
drop temporary table if exists t_reviewIds;
create temporary table t_reviewIds (seq INT AUTO_INCREMENT PRIMARY KEY, reviewId INT);
-- Context-specific logic
IF in_context = 'system' THEN
INSERT into t_reviewIds (reviewId)
select r.reviewId from review r
left join rev_group_rule_map rgr on (r.version = rgr.version and r.checkDigest = rgr.checkDigest)
where rgr.rgrId is null;
ELSEIF in_context = 'asset' THEN
INSERT into t_reviewIds (reviewId)
select
r.reviewId
from
review r
left join rev_group_rule_map rgr on (r.version = rgr.version and r.checkDigest = rgr.checkDigest)
left join revision on (rgr.revId = revision.revId)
left join stig_asset_map sa on (r.assetId = sa.assetId and revision.benchmarkId = sa.benchmarkId)
group by
r.reviewId
having
count(sa.saId) = 0;
END IF;
select max(seq) into v_numReviewIds from t_reviewIds;
CALL task_output('info', concat('found ', ifnull(v_numReviewIds, 0), ' reviews to delete'));
IF v_numReviewIds > 0 THEN
drop temporary table if exists t_historyIds;
create temporary table t_historyIds (seq INT AUTO_INCREMENT PRIMARY KEY)
select historyId from review_history where reviewId in (select reviewId from t_reviewIds);
select max(seq) into v_numHistoryIds from t_historyIds;
CALL task_output('info', concat('found ', ifnull(v_numHistoryIds, 0), ' history records to delete'));
IF v_numHistoryIds > 0 THEN
CALL task_output('info', concat('deleting ', v_numHistoryIds, ' history records'));
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
REPEAT
delete from review_history where historyId IN (
select historyId from t_historyIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
CALL task_output('info', concat('deleting ', v_numReviewIds, ' reviews'));
SET v_curMinId = 1;
SET v_curMaxId = v_curMinId + v_incrementValue;
REPEAT
delete from review where reviewId IN (
select reviewId from t_reviewIds where seq >= v_curMinId and seq < v_curMaxId
);
SET v_curMinId = v_curMinId + v_incrementValue;
SET v_curMaxId = v_curMaxId + v_incrementValue;
UNTIL ROW_COUNT() = 0 END REPEAT;
END IF;
CALL task_output('info', 'task finished');
END $
DELIMITER ;
/*!50003 SET sql_mode = @saved_sql_mode */ ;
/*!50003 SET collation_connection = @saved_col_connection */ ;
/*!50003 DROP PROCEDURE IF EXISTS `run_job` */;
/*!50003 SET @saved_col_connection = @@collation_connection */ ;
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ ;
/*!50003 SET @saved_sql_mode = @@sql_mode */ ;
/*!50003 SET sql_mode = 'IGNORE_SPACE,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION' */ ;
DELIMITER $
CREATE PROCEDURE `run_job`(
IN in_jobId INT,
IN in_runIdStr VARCHAR(36)
)
main:BEGIN
DECLARE v_done INT DEFAULT FALSE;
DECLARE v_jrId INT;
DECLARE v_numTasks INT;
DECLARE v_currentTaskId INT;
DECLARE v_currentTaskName VARCHAR(255);
DECLARE v_currentCommand VARCHAR(255);
DECLARE v_currentTaskNum INT DEFAULT 0;
DECLARE v_param_string TEXT;
DECLARE cur CURSOR FOR
SELECT
jt.taskId,
t.name,
t.command
FROM
job_task_map jt
inner join task t on (jt.taskId = t.taskId)
WHERE
jobId = in_jobId
ORDER BY jtId ASC;
DECLARE CONTINUE HANDLER FOR NOT FOUND SET v_done = TRUE;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
BEGIN
DECLARE err_code INT;
DECLARE err_msg TEXT;
GET STACKED DIAGNOSTICS CONDITION 1 err_code = MYSQL_ERRNO, err_msg = MESSAGE_TEXT;
CALL task_output('error', concat('code: ', err_code, ' message: ', err_msg));
UPDATE job_run SET state = 'failed' WHERE runId = @runId;
END;
-- setup runtime context (null if running outside a job)
IF in_runIdStr IS NOT NULL AND in_runIdStr REGEXP '^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$' THEN
SET @runId = UUID_TO_BIN(in_runIdStr, 1);
ELSE
SET @runId = UUID_TO_BIN(UUID(), 1);
END IF;
SET @taskId = NULL;
INSERT INTO job_run(jobId, runId, state) VALUES (in_jobId, @runId, 'running');
CALL task_output('info', concat('run started for jobId ', in_jobId));
-- Get the number of tasks for the job
SELECT COUNT(*) INTO v_numTasks FROM job_task_map WHERE jobId = in_jobId;
IF v_numTasks = 0 THEN
CALL task_output('error', 'no tasks to run');
UPDATE job_run SET state = 'failed' WHERE runId = @runId AND state = 'running';
LEAVE main; -- No tasks to run, exit the procedure
END IF;
OPEN cur;
read_loop: LOOP
FETCH cur INTO v_currentTaskId, v_currentTaskName, v_currentCommand;
IF v_done THEN
LEAVE read_loop;
END IF;
SET v_currentTaskNum = v_currentTaskNum + 1;
SET @sql = CONCAT('CALL ', v_currentCommand);
PREPARE stmt_run_job FROM @sql;
CALL task_output('info', concat('Beginning task ', v_currentTaskName, ' (', v_currentTaskNum, '/', v_numTasks, ')'));
SET @taskId = v_currentTaskId;
EXECUTE stmt_run_job;
DEALLOCATE PREPARE stmt_run_job;
SET @taskId = NULL;
CALL task_output('info', concat('Ended task ', v_currentTaskName, ' (', v_currentTaskNum, '/', v_numTasks, ')'));
END LOOP;
CLOSE cur;
-- === Post-task-loop logic ===
UPDATE job_run SET state = 'completed' WHERE runId = @runId AND state = 'running';
CALL task_output('info', concat('run completed for jobId ', in_jobId));
END $
DELIMITER ;
/*!50003 SET sql_mode = @saved_sql_mode */ ;
/*!50003 SET collation_connection = @saved_col_connection */ ;
/*!50003 DROP PROCEDURE IF EXISTS `task_output` */;
/*!50003 SET @saved_col_connection = @@collation_connection */ ;
/*!50003 SET collation_connection = utf8mb4_0900_ai_ci */ ;
/*!50003 SET @saved_sql_mode = @@sql_mode */ ;
/*!50003 SET sql_mode = 'IGNORE_SPACE,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION' */ ;
DELIMITER $
CREATE PROCEDURE `task_output`(
IN in_type VARCHAR(45),
IN in_message VARCHAR(255)
)
BEGIN
IF in_message IS NULL THEN SET in_message = ''; END IF;
insert into task_output (runId, taskId, type, message) values (@runId, @taskId, in_type, in_message);
END $
DELIMITER ;
/*!50003 SET sql_mode = @saved_sql_mode */ ;
/*!50003 SET collation_connection = @saved_col_connection */ ;
--
-- Final view structure for view `enabled_asset`
--
/*!50001 DROP VIEW IF EXISTS `enabled_asset`*/;
/*!50001 SET @saved_col_connection = @@collation_connection */;
/*!50001 SET collation_connection = utf8mb4_0900_ai_ci */;
/*!50001 CREATE ALGORITHM=UNDEFINED */
/*!50001 VIEW `enabled_asset` AS select `asset`.`assetId` AS `assetId`,`asset`.`name` AS `name`,`asset`.`fqdn` AS `fqdn`,`asset`.`collectionId` AS `collectionId`,`asset`.`ip` AS `ip`,`asset`.`mac` AS `mac`,`asset`.`description` AS `description`,`asset`.`noncomputing` AS `noncomputing`,`asset`.`metadata` AS `metadata`,`asset`.`state` AS `state`,`asset`.`stateDate` AS `stateDate`,`asset`.`stateUserId` AS `stateUserId`,`asset`.`isEnabled` AS `isEnabled` from `asset` where (`asset`.`state` = 'enabled') */;
/*!50001 SET collation_connection = @saved_col_connection */;
--
-- Final view structure for view `enabled_collection`
--
/*!50001 DROP VIEW IF EXISTS `enabled_collection`*/;
/*!50001 SET @saved_col_connection = @@collation_connection */;
/*!50001 SET collation_connection = utf8mb4_0900_ai_ci */;
/*!50001 CREATE ALGORITHM=UNDEFINED */
/*!50001 VIEW `enabled_collection` AS select `collection`.`collectionId` AS `collectionId`,`collection`.`name` AS `name`,`collection`.`description` AS `description`,`collection`.`settings` AS `settings`,`collection`.`metadata` AS `metadata`,`collection`.`created` AS `created`,`collection`.`state` AS `state`,`collection`.`createdUserId` AS `createdUserId`,`collection`.`stateDate` AS `stateDate`,`collection`.`stateUserId` AS `stateUserId`,`collection`.`isNameUnavailable` AS `isNameUnavailable`,`collection`.`isEnabled` AS `isEnabled` from `collection` where (`collection`.`state` = 'enabled') */;
/*!50001 SET collation_connection = @saved_col_connection */;
--
-- Final view structure for view `v_current_rev`
--
/*!50001 DROP VIEW IF EXISTS `v_current_rev`*/;
/*!50001 SET @saved_col_connection = @@collation_connection */;
/*!50001 SET collation_connection = utf8mb4_0900_ai_ci */;
/*!50001 CREATE ALGORITHM=UNDEFINED */
/*!50001 VIEW `v_current_rev` AS select `rr`.`revId` AS `revId`,`rr`.`benchmarkId` AS `benchmarkId`,`rr`.`version` AS `version`,`rr`.`release` AS `release`,`rr`.`benchmarkDate` AS `benchmarkDate`,`rr`.`benchmarkDateSql` AS `benchmarkDateSql`,`rr`.`status` AS `status`,`rr`.`statusDate` AS `statusDate`,`rr`.`marking` AS `marking`,`rr`.`description` AS `description`,`rr`.`active` AS `active`,`rr`.`groupCount` AS `groupCount`,`rr`.`ruleCount` AS `ruleCount`,`rr`.`lowCount` AS `lowCount`,`rr`.`mediumCount` AS `mediumCount`,`rr`.`highCount` AS `highCount`,`rr`.`checkCount` AS `checkCount`,`rr`.`fixCount` AS `fixCount` from (select `r`.`revId` AS `revId`,`r`.`benchmarkId` AS `benchmarkId`,`r`.`version` AS `version`,`r`.`release` AS `release`,`r`.`benchmarkDate` AS `benchmarkDate`,`r`.`benchmarkDateSql` AS `benchmarkDateSql`,`r`.`status` AS `status`,`r`.`statusDate` AS `statusDate`,`r`.`marking` AS `marking`,`r`.`description` AS `description`,`r`.`active` AS `active`,`r`.`groupCount` AS `groupCount`,`r`.`ruleCount` AS `ruleCount`,`r`.`lowCount` AS `lowCount`,`r`.`mediumCount` AS `mediumCount`,`r`.`highCount` AS `highCount`,`r`.`checkCount` AS `checkCount`,`r`.`fixCount` AS `fixCount`,row_number() OVER (PARTITION BY `r`.`benchmarkId` ORDER BY field(`r`.`status`,'draft','accepted') desc,(`r`.`version` + 0) desc,(`r`.`release` + 0) desc ) AS `rn` from `revision` `r`) `rr` where (`rr`.`rn` = 1) */;
/*!50001 SET collation_connection = @saved_col_connection */;
--
-- Final view structure for view `v_default_rev`
--
/*!50001 DROP VIEW IF EXISTS `v_default_rev`*/;
/*!50001 SET @saved_col_connection = @@collation_connection */;
/*!50001 SET collation_connection = utf8mb4_0900_ai_ci */;
/*!50001 CREATE ALGORITHM=UNDEFINED */
/*!50001 VIEW `v_default_rev` AS select distinct `a`.`collectionId` AS `collectionId`,`sa`.`benchmarkId` AS `benchmarkId`,(case when (`crm`.`revId` is not null) then `crm`.`revId` else `cr`.`revId` end) AS `revId`,(case when (`crm`.`revId` is not null) then 1 else 0 end) AS `revisionPinned` from (((`asset` `a` join `stig_asset_map` `sa` on((`a`.`assetId` = `sa`.`assetId`))) left join `current_rev` `cr` on((`sa`.`benchmarkId` = `cr`.`benchmarkId`))) left join `collection_rev_map` `crm` on(((`sa`.`benchmarkId` = `crm`.`benchmarkId`) and (`a`.`collectionId` = `crm`.`collectionId`)))) */;
/*!50001 SET collation_connection = @saved_col_connection */;
--
-- Final view structure for view `v_latest_rev`
--
/*!50001 DROP VIEW IF EXISTS `v_latest_rev`*/;
/*!50001 SET @saved_col_connection = @@collation_connection */;
/*!50001 SET collation_connection = utf8mb4_0900_ai_ci */;
/*!50001 CREATE ALGORITHM=UNDEFINED */
/*!50001 VIEW `v_latest_rev` AS select `rr`.`revId` AS `revId`,`rr`.`benchmarkId` AS `benchmarkId`,concat('V',`rr`.`version`,'R',`rr`.`release`) AS `revisionStr` from (select `r`.`revId` AS `revId`,`r`.`benchmarkId` AS `benchmarkId`,`r`.`version` AS `version`,`r`.`release` AS `release`,row_number() OVER (PARTITION BY `r`.`benchmarkId` ORDER BY field(`r`.`status`,'draft','accepted') desc,(`r`.`version` + 0) desc,(`r`.`release` + 0) desc ) AS `rn` from `revision` `r`) `rr` where (`rr`.`rn` = 1) */;
/*!50001 SET collation_connection = @saved_col_connection */;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2026-03-09 22:40:40
================================================
FILE: api/source/service/migrations/sql/current/20-stigman-static.sql
================================================
-- MySQL dump 10.13 Distrib 8.0.44, for Linux (x86_64)
--
-- Host: 127.0.0.1 Database: stigman
-- ------------------------------------------------------
-- Server version 8.0.44
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Dumping data for table `result`
--
LOCK TABLES `result` WRITE;
/*!40000 ALTER TABLE `result` DISABLE KEYS */;
INSERT INTO `result` VALUES (1,'notchecked','Not_Reviewed','not_reviewed','NR','Not checked'),(2,'notapplicable','Not_Applicable','not_applicable','NA','Not Applicable'),(3,'pass','NotAFinding','not_a_finding','NF','Not a Finding'),(4,'fail','Open','open','O','Open'),(5,'unknown','Not_Reviewed','not_reviewed','U','Unknown'),(6,'error','Not_Reviewed','not_reviewed','E','Error'),(7,'notselected','Not_Reviewed','not_reviewed','NS','Not selected'),(8,'informational','Not_Reviewed','not_reviewed','I','Informational'),(9,'fixed','NotAFinding','not_a_finding','NF','Fixed');
/*!40000 ALTER TABLE `result` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `status`
--
LOCK TABLES `status` WRITE;
/*!40000 ALTER TABLE `status` DISABLE KEYS */;
INSERT INTO `status` VALUES (0,'saved','Saved'),(1,'submitted','Submitted'),(2,'rejected','Rejected'),(3,'accepted','Accepted');
/*!40000 ALTER TABLE `status` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `_migrations`
--
LOCK TABLES `_migrations` WRITE;
/*!40000 ALTER TABLE `_migrations` DISABLE KEYS */;
INSERT INTO `_migrations` VALUES ('2023-03-09 16:11:04',NULL,'0000.js'),('2023-03-09 16:11:04',NULL,'0001.js'),('2023-03-09 16:11:04',NULL,'0002.js'),('2023-03-09 16:11:04',NULL,'0003.js'),('2023-03-09 16:11:04',NULL,'0004.js'),('2023-03-09 16:11:04',NULL,'0005.js'),('2023-03-09 16:11:04',NULL,'0006.js'),('2023-03-09 16:11:05',NULL,'0007.js'),('2023-03-09 16:11:06',NULL,'0008.js'),('2023-03-09 16:11:06',NULL,'0009.js'),('2023-03-09 16:11:06',NULL,'0010.js'),('2023-03-09 16:11:07',NULL,'0011.js'),('2023-03-09 16:11:07',NULL,'0012.js'),('2023-03-09 16:11:07',NULL,'0013.js'),('2023-03-09 16:11:07',NULL,'0014.js'),('2023-03-09 16:11:07',NULL,'0015.js'),('2023-03-09 16:11:08',NULL,'0016.js'),('2023-03-09 16:11:08',NULL,'0017.js'),('2023-03-09 16:11:08',NULL,'0018.js'),('2023-03-09 16:11:09',NULL,'0019.js'),('2023-03-09 16:11:10',NULL,'0020.js'),('2023-04-11 14:14:58',NULL,'0021.js'),('2023-04-26 13:06:02',NULL,'0022.js'),('2023-07-18 14:50:40',NULL,'0023.js'),('2023-09-05 14:19:13',NULL,'0024.js'),('2023-09-05 14:19:14',NULL,'0025.js'),('2023-09-05 14:19:14',NULL,'0026.js'),('2023-09-05 14:19:14',NULL,'0027.js'),('2024-03-26 12:40:20',NULL,'0028.js'),('2024-05-14 21:39:38',NULL,'0029.js'),('2024-05-14 21:40:06',NULL,'0031.js'),('2024-07-24 14:40:24',NULL,'0032.js'),('2025-02-05 17:47:29',NULL,'0033.js'),('2025-02-05 17:47:29',NULL,'0034.js'),('2025-02-05 17:48:18',NULL,'0035.js'),('2025-02-05 17:48:18',NULL,'0036.js'),('2025-05-13 22:25:35',NULL,'0037.js'),('2025-05-13 22:25:45',NULL,'0038.js'),('2025-05-13 22:25:45',NULL,'0039.js'),('2025-05-13 22:25:45',NULL,'0040.js'),('2025-10-04 20:54:44',NULL,'0041.js'),('2025-10-04 20:54:44',NULL,'0042.js'),('2025-10-04 20:54:44',NULL,'0043.js'),('2025-10-04 20:54:45',NULL,'0044.js'),('2025-10-04 20:54:45',NULL,'0045.js'),('2026-03-09 22:40:20',NULL,'0046.js');
/*!40000 ALTER TABLE `_migrations` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `task`
--
LOCK TABLES `task` WRITE;
/*!40000 ALTER TABLE `task` DISABLE KEYS */;
INSERT INTO `task` VALUES (1,'WipeDeletedObjects','Wipe deleted collections and assets and their associated reviews','delete_disabled()'),(2,'DeleteUnmappedReviews','Delete reviews that no longer match any rule in the system','delete_unmapped(\"system\")'),(3,'DeleteUnmappedAssetReviews','Delete reviews that no longer match an asset\'s assigned rules','delete_unmapped(\"asset\")'),(4,'AnalyzeReviewTables','Analyze database tables for performance','analyze_tables(JSON_ARRAY(\"reviews\", \"review_history\"))');
/*!40000 ALTER TABLE `task` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `job`
--
LOCK TABLES `job` WRITE;
/*!40000 ALTER TABLE `job` DISABLE KEYS */;
INSERT INTO `job` VALUES (1,'Cleanup Database','Wipe deleted collections and assets and their associated reviews',NULL,NULL,'2025-10-04 20:54:45.057',NULL),(2,'Delete Unmapped Reviews','Delete reviews that no longer match any rule in the system',NULL,NULL,'2025-10-04 20:54:45.057',NULL),(3,'Delete Unmapped Asset Reviews','Delete reviews that no longer match an asset\'s assigned rules',NULL,NULL,'2025-10-04 20:54:45.057',NULL);
/*!40000 ALTER TABLE `job` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Dumping data for table `job_task_map`
--
LOCK TABLES `job_task_map` WRITE;
/*!40000 ALTER TABLE `job_task_map` DISABLE KEYS */;
INSERT INTO `job_task_map` VALUES (1,1,1,'2025-10-04 20:54:45.079','2025-10-04 20:54:45.079'),(2,1,4,'2025-10-04 20:54:45.079','2025-10-04 20:54:45.079'),(3,2,2,'2025-10-04 20:54:45.079','2025-10-04 20:54:45.079'),(4,2,4,'2025-10-04 20:54:45.079','2025-10-04 20:54:45.079'),(5,3,3,'2025-10-04 20:54:45.079','2025-10-04 20:54:45.079'),(6,3,4,'2025-10-04 20:54:45.079','2025-10-04 20:54:45.079');
/*!40000 ALTER TABLE `job_task_map` ENABLE KEYS */;
UNLOCK TABLES;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2026-03-09 22:40:40
ALTER TABLE job AUTO_INCREMENT=100;
ALTER TABLE job_task_map AUTO_INCREMENT=1000;
================================================
FILE: api/source/service/migrations/sql/current/31-rev5-cci-data.sql
================================================
--
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Data for table `cci`
--
LOCK TABLES `cci` WRITE;
/*!40000 ALTER TABLE `cci` DISABLE KEYS */;
INSERT INTO `cci` VALUES ('000002','draft','2009-09-14','DISA FSO','policy','Disseminate the organization-level; mission/business process-level; and/or system-level access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance to organization-defined personnel or roles.','AC-01a.','N/A','Determine if: - an access control policy is developed and documented. - the access control policy is disseminated to [AC-01_ODP[01]; personnel or roles to whom the access control policy is to be disseminated is/are defined].'),
('000003','draft','2009-09-14','DISA FSO','policy','Review and update the current access control policy on an organization-defined frequency.','AC-01c.01','N/A','Determine if: - the current access control policy is reviewed and updated [AC-01_ODP[05]; the frequency at which the current access control policy is reviewed and updated is defined]. - the current access control policy is reviewed and updated following [AC-01_ODP[06]; events that would require the current access control policy to be reviewed and updated are defined].'),
('000005','draft','2009-09-14','DISA FSO','policy','Disseminate procedures to facilitate the implementation of the organization-level; mission/business process-level; and/or system-level access control policy and associated access controls to the organization-defined personnel or roles.','AC-01a.02','N/A','Determine if: - access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented. - the access control procedures are disseminated to [AC-01_ODP[02]; personnel or roles to whom the access control procedures are to be disseminated is/are defined].'),
('000006','draft','2009-09-14','DISA FSO','policy','Review and update the current access control procedures on an organization-defined frequency.','AC-01c.02','N/A','Determine if: - the current access control procedures are reviewed and updated [AC-01_ODP[07]; the frequency at which the current access control procedures are reviewed and updated is defined;]. - the current access control procedures are reviewed and updated following [AC-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('000010','draft','2009-05-13','DISA FSO','policy','Require approvals by organization-defined personnel or roles for requests to create accounts.','AC-02e.','N/A','Determine if approvals are required by [AC-02_ODP[03]; personnel or roles required to approve requests to create accounts is/are defined] for requests to create accounts.'),
('000011','draft','2009-05-13','DISA FSO','policy','Create, enable, modify, disable, and remove system accounts in accordance with organization-defined procedures.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('000012','draft','2009-09-14','DISA FSO','policy','Review accounts for compliance with account management requirements per organization-defined frequency.','AC-02j.','N/A','Determine if accounts are reviewed for compliance with account management requirements [AC-02_ODP[10]; the frequency of account review is defined].'),
('000015','draft','2009-05-13','DISA FSO','technical','Support the management of system accounts using organization-defined automated mechanisms.','AC-02(01)','N/A','Determine if the management of system accounts is supported using [AC-02(01)_ODP; automated mechanisms used to support the management of system accounts are defined].'),
('000016','draft','2009-05-13','DISA FSO','technical','Automatically remove or disable temporary and emergency accounts after an organization-defined time-period for each type of account.','AC-02(02)','N/A','Determine if temporary and emergency accounts are automatically [AC-02(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {remove; disable}] after [AC-02(02)_ODP[02]; the time period after which to automatically remove or disable temporary or emergency accounts is defined].'),
('000017','draft','2009-05-13','DISA FSO','technical','Disable accounts when the accounts have been inactive for the organization-defined time-period.','AC-02(03)(d)','N/A','Determine if accounts are disabled within [AC-02(03)_ODP[01]; time period within which to disable accounts is defined] when the accounts have been inactive for [AC-02(03)_ODP[02]; time period for account inactivity before disabling is defined].'),
('000018','draft','2009-05-13','DISA FSO','technical','Automatically audit account creation actions.','AC-02(04)','N/A','Determine if: - account creation is automatically audited. - account modification is automatically audited. - account enabling is automatically audited. - account disabling is automatically audited. - account removal actions are automatically audited.'),
('000019','draft','2009-09-14','DISA FSO','policy','Require that users log out in accordance with the organization-defined time-period of expected inactivity or description of when to log out.','AC-02(05)','N/A','Determine if users are required to log out when [AC-02(05)_ODP; the time period of expected inactivity or description of when to log out is defined].'),
('000021','draft','2009-05-13','DISA FSO','technical','Enforce dual authorization for organization-defined privileged commands and/or other organization-defined actions.','AC-03(02)','N/A','Determine if dual authorization is enforced for [AC-03(02)_ODP; privileged commands and/or other actions requiring dual authorization are defined].'),
('000024','draft','2009-09-14','DISA FSO','technical','Prevent access to organization-defined security-relevant information except during secure, non-operable system states.','AC-03(05)','N/A','Determine if access to [AC-03(05)_ODP; security-relevant information to which access is prevented except during secure, non-operable system states is defined] is prevented except during secure, non-operable system states.'),
('000026','draft','2009-05-13','DISA FSO','technical','Use protected processing domains to enforce organization-defined information flow control policies as a basis for flow control decisions.','AC-04(02)','N/A','Determine if protected processing domains are used to enforce [AC-04(02)_ODP; information flow control policies to be enforced by use of protected processing domains are defined] as a basis for flow control decisions.'),
('000027','draft','2009-05-13','DISA FSO','technical','Enforce organization-defined information flow control policies.','AC-04(03)','N/A','Determine if [AC-04(03)_ODP; information flow control policies to be enforced are defined] are enforced.'),
('000028','draft','2009-05-13','DISA FSO','policy','Prevent encrypted information from bypassing organization-defined flow control mechanisms by employing organization-defined procedures or methods.','AC-04(04)','N/A','Determine if encrypted information is prevented from bypassing [AC-04(04)_ODP[01]; information flow control mechanisms that encrypted information is prevented from bypassing are defined] by [AC-04(04)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [AC-04(04)_ODP[03]; the organization-defined procedure or method used to prevent encrypted information from bypassing information flow control mechanisms is defined (if selected)]].'),
('000029','draft','2009-05-13','DISA FSO','technical','Enforce organization-defined limitations on embedding data types within other data types.','AC-04(05)','N/A','Determine if [AC-04(05)_ODP; limitations on embedding data types within other data types are defined] are enforced on embedding data types within other data types.'),
('000030','draft','2009-05-13','DISA FSO','technical','Enforce information flow control based on organization-defined metadata.','AC-04(06)','N/A','Determine if information flow control enforcement is based on [AC-04(06)_ODP; metadata on which to base enforcement of information flow control is defined].'),
('000031','draft','2009-05-13','DISA FSO','technical','Enforce one-way information flows using hardware-based flow control mechanisms.','AC-04(07)','N/A','Determine if one-way information flows are enforced through hardware-based flow control mechanisms.'),
('000032','draft','2009-09-14','DISA FSO','technical','Enforce information flow control using organization-defined security policy filters as a basis for flow control decisions for organization-defined information flows.','AC-04(08)(a)','N/A','Determine if: - information flow control is enforced using [AC-04(08)_ODP[01]; security policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[03]; information flows for which information flow control is enforced by security filters are defined]. - information flow control is enforced using [AC-04(08)_ODP[02]; privacy policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[04]; information flows for which information flow control is enforced by privacy filters are defined].'),
('000034','draft','2009-05-13','DISA FSO','technical','Provide the capability for privileged administrators to enable and disable organization-defined security or privacy filters under organization-defined conditions.','AC-04(10)','N/A','Determine if: - capability is provided for privileged administrators to enable and disable [AC-04(10)_ODP[01]; security policy filters that privileged administrators have the capability to enable and disable are defined] under [AC-04(10)_ODP[03]; conditions under which privileged administrators have the capability to enable and disable security policy filters are defined]. - capability is provided for privileged administrators to enable and disable [AC-04(10)_ODP[02]; privacy policy filters that privileged administrators have the capability to enable and disable are defined] under [AC-04(10)_ODP[04]; conditions under which privileged administrators have the capability to enable and disable privacy policy filters are defined].'),
('000035','draft','2009-09-14','DISA FSO','technical','Provide the capability for privileged administrators to configure the organization-defined security or privacy policy filters to support different security or privacy policies.','AC-04(11)','N/A','Determine if: - capability is provided for privileged administrators to configure [AC-04(11)_ODP[01]; security policy filters that privileged administrators have the capability to configure to support different security and privacy policies are defined] to support different security or privacy policies. - capability is provided for privileged administrators to configure [AC-04(11)_ODP[02]; privacy policy filters that privileged administrators have the capability to configure to support different security and privacy policies are defined] to support different security or privacy policies.'),
('000039','draft','2009-09-14','DISA FSO','policy','Require that users of system accounts, or roles, with access to organization-defined security functions or security-relevant information, use non-privileged accounts or roles, when accessing nonsecurity functions.','AC-06(02)','N/A','Determine if users of system accounts (or roles) with access to [AC-06(02)_ODP; security functions or security-relevant information, the access to which requires users to use non-privileged accounts to access non-security functions, are defined] are required to use non-privileged accounts or roles when accessing non-security functions.'),
('000041','draft','2009-05-19','DISA FSO','policy','Authorize network access to organization-defined privileged commands only for organization-defined compelling operational needs.','AC-06(03)','N/A','Determine if: - network access to [AC-06(03)_ODP[01]; privileged commands to which network access is to be authorized only for compelling operational needs are defined] is authorized only for [AC-06(03)_ODP[02]; compelling operational needs necessitating network access to privileged commands are defined]. - the rationale for authorizing network access to privileged commands is documented in the security plan for the system.'),
('000042','draft','2009-05-19','DISA FSO','policy','Document the rationale for authorized network access to organization-defined privileged commands in the security plan for the system.','AC-06(03)','N/A','Determine if: - network access to [AC-06(03)_ODP[01]; privileged commands to which network access is to be authorized only for compelling operational needs are defined] is authorized only for [AC-06(03)_ODP[02]; compelling operational needs necessitating network access to privileged commands are defined]. - the rationale for authorizing network access to privileged commands is documented in the security plan for the system.'),
('000043','draft','2009-05-19','DISA FSO','policy','Defines the maximum number of consecutive invalid logon attempts to the information system by a user during an organization-defined time period.','AC-07a.','N/A','Determine if a limit of [AC-07_ODP[01]; the number of consecutive invalid logon attempts by a user allowed during a time period is defined] consecutive invalid logon attempts by a user during [AC-07_ODP[02]; the time period to which the number of consecutive invalid logon attempts by a user is limited is defined] is enforced.'),
('000044','draft','2009-09-14','DISA FSO','technical','Enforce the organization-defined limit of consecutive invalid logon attempts by a user during the organization-defined time period.','AC-07a.','N/A','Determine if a limit of [AC-07_ODP[01]; the number of consecutive invalid logon attempts by a user allowed during a time period is defined] consecutive invalid logon attempts by a user during [AC-07_ODP[02]; the time period to which the number of consecutive invalid logon attempts by a user is limited is defined] is enforced.'),
('000048','draft','2009-05-19','DISA FSO','technical','Display an organization-defined system use notification message or banner to users before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidelines.','AC-08a.','N/A','Determine if [AC-08_ODP[01]; system use notification message or banner to be displayed by the system to users before granting access to the system is defined] is displayed to users before granting access to the system that provides privacy and security notices consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('000050','draft','2009-09-14','DISA FSO','technical','Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system.','AC-08b.','N/A','Determine if the notification message or banner is retained on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system.'),
('000052','draft','2009-09-14','DISA FSO','technical','Notify the user, upon successful logon (access) to the system, of the date and time of the last logon (access).','AC-09','N/A','Determine if the user is notified, upon successful logon to the system, of the date and time of the last logon.'),
('000053','draft','2009-09-14','DISA FSO','technical','Notify the user, upon successful logon/access, of the number of unsuccessful logon/access attempts since the last successful logon/access.','AC-09(01)','N/A','Determine if the user is notified, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.'),
('000054','draft','2009-05-19','DISA FSO','technical','Limit the number of concurrent sessions for each organization-defined account and/or account type to an organization-defined number.','AC-10','N/A','Determine if the number of concurrent sessions for each [AC-10_ODP[01]; accounts and/or account types for which to limit the number of concurrent sessions is defined] is limited to [AC-10_ODP[02]; the number of concurrent sessions to be allowed for each account and/or account type is defined].'),
('000055','draft','2009-05-19','DISA FSO','policy','Defines the maximum number of concurrent sessions to be allowed for each organization-defined account and/or account type.','AC-10','N/A','Determine if the number of concurrent sessions for each [AC-10_ODP[01]; accounts and/or account types for which to limit the number of concurrent sessions is defined] is limited to [AC-10_ODP[02]; the number of concurrent sessions to be allowed for each account and/or account type is defined].'),
('000056','draft','2009-09-14','DISA FSO','technical','Retain the device lock until the user reestablishes access using established identification and authentication procedures.','AC-11b.','N/A','Determine if device lock is retained until the user re-establishes access using established identification and authentication procedures.'),
('000057','draft','2009-05-19','DISA FSO','technical','Prevent further access to the system by initiating a device lock after organization-defined time period of inactivity; and/or requiring the user to initiate a device lock before leaving the system unattended.','AC-11a.','N/A','Determine if further access to the system is prevented by [AC-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {initiating a device lock after [AC-11_ODP[02]; time period of inactivity after which a device lock is initiated is defined (if selected)] of inactivity; requiring the user to initiate a device lock before leaving the system unattended}].'),
('000059','draft','2009-09-14','DISA FSO','policy','Defines the time-period of inactivity after which the system initiates a device lock.','AC-11a.','N/A','Determine if further access to the system is prevented by [AC-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {initiating a device lock after [AC-11_ODP[02]; time period of inactivity after which a device lock is initiated is defined (if selected)] of inactivity; requiring the user to initiate a device lock before leaving the system unattended}].'),
('000060','draft','2009-05-19','DISA FSO','technical','Conceal, via the device lock, information previously visible on the display with a publicly viewable image.','AC-11(01)','N/A','Determine if information previously visible on the display is concealed, via device lock, with a publicly viewable image.'),
('000061','draft','2009-09-14','DISA FSO','policy','Identify organization-defined user actions that can be performed on the system without identification or authentication consistent with organizational missions/business functions.','AC-14a.','N/A','Determine if [AC-14_ODP; user actions that can be performed on the system without identification or authentication are defined] that can be performed on the system without identification or authentication consistent with organizational mission and business functions are identified.'),
('000065','draft','2009-09-14','DISA FSO','policy','Authorize remote access to the system prior to allowing such connections.','AC-17b.','N/A','Determine if each type of remote access to the system is authorized prior to allowing such connections.'),
('000067','draft','2009-09-14','DISA FSO','technical','Employ automated mechanisms to monitor remote access methods.','AC-17(01)','N/A','Determine if: - automated mechanisms are employed to monitor remote access methods. - automated mechanisms are employed to control remote access methods.'),
('000068','draft','2009-09-14','DISA FSO','technical','Implement cryptographic mechanisms to protect the confidentiality of remote access sessions.','AC-17(02)','N/A','Determine if cryptographic mechanisms are implemented to protect the confidentiality and integrity of remote access sessions.'),
('000069','draft','2009-05-19','DISA FSO','policy','Route all remote accesses through authorized and managed network access control points.','AC-17(03)','N/A','Determine if remote accesses are routed through authorized and managed network access control points.'),
('000070','draft','2009-05-19','DISA FSO','policy','Authorize the execution of privileged commands via remote access only in a format that provides assessable evidence for organization-defined needs.','AC-17(04)(a)','N/A','Determine if: - the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence. - access to security-relevant information via remote access is authorized only in a format that provides assessable evidence. - the execution of privileged commands via remote access is authorized only for the following needs: [AC-17(04)_ODP[01]; needs requiring execution of privileged commands via remote access are defined]. - access to security-relevant information via remote access is authorized only for the following needs: [AC-17(04)_ODP[02]; needs requiring access to security-relevant information via remote access are defined].'),
('000072','draft','2009-09-25','DISA FSO','policy','Protect information about remote access mechanisms from unauthorized use and disclosure.','AC-17(06)','N/A','Determine if information about remote access mechanisms is protected from unauthorized use and disclosure.'),
('000073','draft','2009-11-03','DISA FSO','policy','Develop an organization-wide information security program plan that provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements.','PM-01a.01','N/A','Determine if: - the information security program plan provides an overview of the requirements for the security program. - the information security program plan provides a description of the security program management controls in place or planned for meeting those requirements. - the information security program plan provides a description of the common controls in place or planned for meeting those requirements.'),
('000074','draft','2009-11-03','DISA FSO','policy','Develop an organization-wide information security program plan that is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.','PM-01a.04','N/A','Determine if the information security program plan is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.'),
('000075','draft','2009-11-03','DISA FSO','policy','Review and update the organization-wide information security program plan on an organization-defined frequency.','PM-01b.','N/A','Determine if: - the information security program plan is reviewed and updated [PM-01_ODP[01]; the frequency at which to review and update the organization-wide information security program plan is defined]. - the information security program plan is reviewed and updated following [PM-01_ODP[02]; events that trigger the review and update of the organization-wide information security program plan are defined].'),
('000076','draft','2009-11-03','DISA FSO','policy','Defines the frequency with which to review and update the organization-wide information security program plan.','PM-01b.','N/A','Determine if: - the information security program plan is reviewed and updated [PM-01_ODP[01]; the frequency at which to review and update the organization-wide information security program plan is defined]. - the information security program plan is reviewed and updated following [PM-01_ODP[02]; events that trigger the review and update of the organization-wide information security program plan are defined].'),
('000078','draft','2009-11-03','DISA FSO','policy','Appoint a Senior Information Security Officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program.','PM-02','N/A','Determine if: - a senior agency information security officer is appointed. - the senior agency information security officer is provided with the mission and resources to coordinate an organization-wide information security program. - the senior agency information security officer is provided with the mission and resources to develop an organization-wide information security program. - the senior agency information security officer is provided with the mission and resources to implement an organization-wide information security program. - the senior agency information security officer is provided with the mission and resources to maintain an organization-wide information security program.'),
('000080','draft','2009-11-03','DISA FSO','policy','Include the resources needed to implement the information security programs in capital planning and investment requests and document all exceptions to this requirement.','PM-03a.','N/A','Determine if: - the resources needed to implement the information security program are included in capital planning and investment requests, and all exceptions are documented. - the resources needed to implement the privacy program are included in capital planning and investment requests, and all exceptions are documented.'),
('000083','draft','2009-05-19','DISA FSO','policy','Establish implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas.','AC-19a.','N/A','Determine if: - configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area. - connection requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area. - implementation guidance is established for organization-controlled mobile devices, including when such devices are outside of the controlled area.'),
('000084','draft','2009-09-14','DISA FSO','policy','Authorize connection of mobile devices to organizational systems.','AC-19b.','N/A','Determine if the connection of mobile devices to organizational systems is authorized.'),
('000093','draft','2009-09-14','DISA FSO','policy','Establish organization-defined terms and conditions, and/or identify organization-defined controls asserted to be implemented on external systems, consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from the external systems.','AC-20a.01','N/A','Determine if [AC-20_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish [AC-20_ODP[02]; terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]; identify [AC-20_ODP[03]; controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]}]]] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable).'),
('000097','draft','2009-09-14','DISA FSO','policy','Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using organization-defined restrictions.','AC-20(02)','N/A','Determine if the use of organization-controlled portable storage devices by authorized individuals is restricted on external systems using [AC-20(02)_ODP; restrictions on the use of organization-controlled portable storage devices by authorized individuals on external systems are defined].'),
('000098','draft','2009-05-19','DISA FSO','policy','Enable authorized users to determine whether access authorizations assigned to the sharing partner match the information''s access and use restrictions for organization-defined information sharing circumstances where user discretion is required.','AC-21a.','N/A','Determine if authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information''s access and use restrictions for [AC-21_ODP[01]; information-sharing circumstances where user discretion is required to determine whether access authorizations assigned to a sharing partner match the information''s access and use restrictions are defined].'),
('000099','draft','2009-05-19','DISA FSO','policy','Employ organization-defined automated mechanisms to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.','AC-21(01)','N/A','Determine if [AC-21(01)_ODP; automated mechanisms employed to enforce information-sharing decisions by authorized users are defined] are employed to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.'),
('000100','draft','2009-05-20','DISA FSO','policy','Develop and document an organization level, mission/business process-level, or system-level awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','AT-01a.01(a)','N/A','Determine if: - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy addresses purpose. - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy addresses scope. - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy addresses roles. - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy addresses responsibilities. - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy addresses management commitment. - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy addresses coordination among organizational entities. - the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level} awareness and training policy addresses compliance.'),
('000101','draft','2009-05-20','DISA FSO','policy','Disseminate an organization level, mission/business process-level, or system-level awareness and training policy to organization-defined personnel or roles.','AT-01a.','N/A','Determine if: - an awareness and training policy is developed and documented. - the awareness and training policy is disseminated to [AT-01_ODP[01]; personnel or roles to whom the awareness and training policy is to be disseminated is/are defined].'),
('000102','draft','2009-05-20','DISA FSO','policy','Review and update the current security awareness and training policy in accordance with organization-defined frequency.','AT-01c.01','N/A','Determine if: - the current awareness and training policy is reviewed and updated [AT-01_ODP[05]; the frequency at which the current awareness and training policy is reviewed and updated is defined]. - the current awareness and training policy is reviewed and updated following [AT-01_ODP[06]; events that would require the current awareness and training policy to be reviewed and updated are defined].'),
('000103','draft','2009-05-20','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the awareness and training policy and associated awareness and training controls.','AT-01a.02','N/A','Determine if: - awareness and training procedures to facilitate the implementation of the awareness and training policy and associated access controls are developed and documented. - the awareness and training procedures are disseminated to [AT-01_ODP[02]; personnel or roles to whom the awareness and training procedures are to be disseminated is/are defined].'),
('000104','draft','2009-05-20','DISA FSO','policy','Disseminate organization-level; mission/business process-level; or system-level awareness and training procedures to organization-defined personnel or roles.','AT-01a.02','N/A','Determine if: - awareness and training procedures to facilitate the implementation of the awareness and training policy and associated access controls are developed and documented. - the awareness and training procedures are disseminated to [AT-01_ODP[02]; personnel or roles to whom the awareness and training procedures are to be disseminated is/are defined].'),
('000105','draft','2009-05-20','DISA FSO','policy','Review and update the current security awareness and training procedures in accordance with an organization-defined frequency.','AT-01c.02','N/A','Determine if: - the current awareness and training procedures are reviewed and updated [AT-01_ODP[07]; the frequency at which the current awareness and training procedures are reviewed and updated is defined]. - the current awareness and training procedures are reviewed and updated following [AT-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('000106','draft','2009-09-14','DISA FSO','policy','Provide basic security literacy training to system users (including managers, senior executives, and contractors) as part of initial training for new users.','AT-02a.01','N/A','Determine if: - security literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users. - privacy literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users. - security literacy training is provided to system users (including managers, senior executives, and contractors) [AT-02_ODP[01]; the frequency at which to provide security literacy training to system users (including managers, senior executives, and contractors) after initial training is defined] thereafter. - privacy literacy training is provided to system users (including managers, senior executives, and contractors) [AT-02_ODP[02]; the frequency at which to provide privacy literacy training to system users (including managers, senior executives, and contractors) after initial training is defined] thereafter.'),
('000107','draft','2009-05-20','DISA FSO','policy','Provide practical exercises in literacy training that simulate events and incidents.','AT-02(01)','N/A','Determine if practical exercises in literacy training that simulate events and incidents are provided.'),
('000108','draft','2009-05-20','DISA FSO','policy','Provide role-based security training to personnel with organization-defined roles and responsibilities before authorizing access to the system, information, or performing assigned duties.','AT-03a.01','N/A','Determine if: - role-based security training is provided to [AT-03_ODP[01]; roles and responsibilities for role-based security training are defined] before authorizing access to the system, information, or performing assigned duties. - role-based privacy training is provided to [AT-03_ODP[02]; roles and responsibilities for role-based privacy training are defined] before authorizing access to the system, information, or performing assigned duties. - role-based security training is provided to [AT-03_ODP[01]; roles and responsibilities for role-based security training are defined] [AT-03_ODP[03]; the frequency at which to provide role-based security and privacy training to assigned personnel after initial training is defined] thereafter. - role-based privacy training is provided to [AT-03_ODP[02]; roles and responsibilities for role-based privacy training are defined] [AT-03_ODP[03]; the frequency at which to provide role-based security and privacy training to assigned personnel after initial training is defined] thereafter.'),
('000109','draft','2009-05-20','DISA FSO','policy','Provide role-based security training to personnel with organization-defined roles and responsibilities when required by system changes.','AT-03a.02','N/A','Determine if: - role-based security training is provided to personnel with assigned security roles and responsibilities when required by system changes. - role-based privacy training is provided to personnel with assigned security roles and responsibilities when required by system changes.'),
('000112','draft','2009-05-20','DISA FSO','policy','Provide basic security awareness training to system users (including managers, senior executives, and contractors) when required by system changes or following organization-defined events.','AT-02a.02','N/A','Determine if: - security literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following [AT-02_ODP[03]; events that require security literacy training for system users are defined]. - privacy literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following [AT-02_ODP[04]; events that require privacy literacy training for system users are defined].'),
('000113','draft','2009-09-14','DISA FSO','policy','Document individual security training activities, including security awareness training and specific system security training.','AT-04a.','N/A','Determine if: - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented. - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are monitored.'),
('000114','draft','2009-09-14','DISA FSO','policy','Monitor individual information security training activities, including security awareness training and specific security training.','AT-04a.','N/A','Determine if: - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented. - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are monitored.'),
('000117','draft','2009-05-20','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','AU-01a.01(a)','N/A','Determine if: - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses purpose. - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses scope. - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses roles. - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses responsibilities. - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses management commitment. - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses coordination among organizational entities. - the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy addresses compliance.'),
('000119','draft','2009-05-20','DISA FSO','policy','Review and update the current audit and accountability policy on an organization-defined frequency.','AU-01c.01','N/A','Determine if: - the current audit and accountability policy is reviewed and updated [AU-01_ODP[05]; the frequency at which the current audit and accountability policy is reviewed and updated is defined]. - the current audit and accountability policy is reviewed and updated following [AU-01_ODP[06]; events that would require the current audit and accountability policy to be reviewed and updated are defined.]'),
('000120','draft','2009-05-20','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.','AU-01a.02','N/A','Determine if: - audit and accountability procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls are developed and documented. - the audit and accountability procedures are disseminated to [AU-01_ODP[02]; personnel or roles to whom the audit and accountability procedures are to be disseminated is/are defined].'),
('000122','draft','2009-05-20','DISA FSO','policy','Review and update the current audit and accountability procedures on an organization-defined frequency.','AU-01c.02','N/A','Determine if: - the current audit and accountability procedures are reviewed and updated [AU-01_ODP[07]; the frequency at which the current audit and accountability procedures are reviewed and updated is defined]. - the current audit and accountability procedures are reviewed and updated following [AU-01_ODP[08]; events that would require audit and accountability procedures to be reviewed and updated are defined].'),
('000123','draft','2009-09-15','DISA FSO','policy','Identify the organization-defined event types that the system is capable of logging in support of the audit function.','AU-02a.','N/A','Determine if [AU-02_ODP[01]; the event types that the system is capable of logging in support of the audit function are defined] that the system is capable of logging are identified in support of the audit logging function.'),
('000124','draft','2009-09-15','DISA FSO','policy','Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged.','AU-02b.','N/A','Determine if the event logging function is coordinated with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged.'),
('000125','draft','2009-09-15','DISA FSO','policy','Provide a rationale for why the event types selected for logging are deemed to be adequate for support after-the-fact investigations of incidents.','AU-02d.','N/A','Determine if a rationale is provided for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents.'),
('000126','draft','2009-09-15','DISA FSO','policy','Specify the organization-defined event types (subset of the event types defined in AU-2a) along with the frequency of (or situation requiring logging for each identified event type.','AU-02c.','N/A','Determine if: - [AU-02_ODP[02]; the event types (subset of AU-02_ODP[01]) for logging within the system are defined] are specified for logging within the system. - the specified event types are logged within the system [AU-02_ODP[03]; the frequency or situation requiring logging for each specified event type is defined].'),
('000130','draft','2009-05-20','DISA FSO','technical','Ensure that audit records contain information that establishes what type of event occurred.','AU-03a.','N/A','Determine if audit records contain information that establishes what type of event occurred.'),
('000131','draft','2009-05-20','DISA FSO','technical','Ensure that audit records containing information that establishes when the event occurred.','AU-03b.','N/A','Determine if audit records contain information that establishes when the event occurred.'),
('000132','draft','2009-05-20','DISA FSO','technical','Ensure that audit records containing information that establishes where the event occurred.','AU-03c.','N/A','Determine if audit records contain information that establishes where the event occurred.'),
('000133','draft','2009-05-20','DISA FSO','technical','Ensure that audit records containing information that establishes the source of the event.','AU-03d.','N/A','Determine if audit records contain information that establishes the source of the event.'),
('000134','draft','2009-05-20','DISA FSO','technical','Ensure that audit records containing information that establishes the outcome of the event.','AU-03e.','N/A','Determine if audit records contain information that establishes the outcome of the event.'),
('000135','draft','2009-05-20','DISA FSO','technical','Generate audit records containing the organization-defined additional information that is to be included in the audit records.','AU-03(01)','N/A','Determine if generated audit records contain the following [AU-03(01)_ODP; additional information to be included in audit records is defined].'),
('000139','draft','2009-09-15','DISA FSO','technical','Alert organization-defined personnel or roles within an organization-defined time period in the event of an audit logging process failure.','AU-05a.','N/A','Determine if [AU-05_ODP[01]; personnel or roles receiving audit logging process failure alerts are defined] are alerted in the event of an audit logging process failure within [AU-05_ODP[02]; time period for personnel or roles receiving audit logging process failure alerts is defined].'),
('000140','draft','2009-05-20','DISA FSO','technical','Take organization-defined actions upon audit failure include, shutting down the system, overwriting oldest audit records, and stopping the generation of audit records.','AU-05b.','N/A','Determine if [AU-05_ODP[03]; additional actions to be taken in the event of an audit logging process failure are defined] are taken in the event of an audit logging process failure.'),
('000141','draft','2009-11-03','DISA FSO','policy','Make available for expenditure, the planned information security resources.','PM-03c.','N/A','Determine if: - information security resources are made available for expenditure as planned. - privacy resources are made available for expenditure as planned.'),
('000142','draft','2009-11-03','DISA FSO','policy','Implement a process to ensure that plans of action and milestones for the information security program and the associated organizational systems are maintained.','PM-04a.01','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained.'),
('000145','draft','2009-05-20','DISA FSO','policy','Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity by delaying or rejecting network traffic above those organization-defined thresholds.','AU-05(03)','N/A','Determine if: - configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity are enforced. - network traffic is [AU-05(03)_ODP; one or more of the following PARAMETER VALUES is/are selected: {reject; delay}] if network traffic volume is above configured thresholds.'),
('000147','draft','2009-05-22','DISA FSO','policy','Defines the audit logging failure events requiring real-time alerts.','AU-05(02)','N/A','Determine if an alert is provided within [AU-05(02)_ODP[01]; real-time period requiring alerts when audit failure events (defined in AU-05(02)_ODP[03]) occur is defined] to [AU-05(02)_ODP[02]; personnel, roles, and/or locations to be alerted in real time when audit failure events (defined in AU-05(02)_ODP[03]) occur is/are defined] when [AU-05(02)_ODP[03]; audit logging failure events requiring real-time alerts are defined] occur.'),
('000148','draft','2009-05-22','DISA FSO','policy','Review and analyze system audit records on an organization-defined frequency for indications of organization-defined inappropriate or unusual activity.','AU-06a.','N/A','Determine if system audit records are reviewed and analyzed [AU-06_ODP[01]; frequency at which system audit records are reviewed and analyzed is defined] for indications of [AU-06_ODP[02]; inappropriate or unusual activity is defined] and the potential impact of the inappropriate or unusual activity.'),
('000149','draft','2009-05-22','DISA FSO','policy','Report any findings to organization-defined personnel or roles for indications of organization-defined inappropriate or unusual activity.','AU-06b.','N/A','Determine if findings are reported to [AU-06_ODP[03]; personnel or roles to receive findings from reviews and analyses of system records is/are defined].'),
('000151','draft','2009-09-15','DISA FSO','policy','Defines the frequency for the review and analysis of system audit records for organization-defined inappropriate or unusual activity.','AU-06a.','N/A','Determine if system audit records are reviewed and analyzed [AU-06_ODP[01]; frequency at which system audit records are reviewed and analyzed is defined] for indications of [AU-06_ODP[02]; inappropriate or unusual activity is defined] and the potential impact of the inappropriate or unusual activity.'),
('000153','draft','2009-05-22','DISA FSO','policy','Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.','AU-06(03)','N/A','Determine if audit records across different repositories are analyzed and correlated to gain organization-wide situational awareness.'),
('000154','draft','2009-05-22','DISA FSO','technical','Provide the capability to centrally review and analyze audit records from multiple components within the system.','AU-06(04)','N/A','Determine if: - the capability to centrally review and analyze audit records from multiple components within the system is provided. - the capability to centrally review and analyze audit records from multiple components within the system is implemented.'),
('000158','draft','2009-05-22','DISA FSO','technical','Provide the capability to process, sort, and search audit records for events of interest based on organization-defined audit fields within audit records.','AU-07(01)','N/A','Determine if: - the capability to process, sort, and search audit records for events of interest based on [AU-07(01)_ODP; fields within audit records that can be processed, sorted, or searched are defined] are provided. - the capability to process, sort, and search audit records for events of interest based on [AU-07(01)_ODP; fields within audit records that can be processed, sorted, or searched are defined] are implemented.'),
('000159','draft','2009-05-22','DISA FSO','technical','Use internal system clocks to generate time stamps for audit records.','AU-08a.','N/A','Determine if internal system clocks are used to generate timestamps for audit records.'),
('000162','draft','2009-05-22','DISA FSO','technical','Protect audit information from unauthorized access.','AU-09a.','N/A','Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion.'),
('000163','draft','2009-05-22','DISA FSO','technical','Protect audit information from unauthorized modification.','AU-09a.','N/A','Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion.'),
('000164','draft','2009-05-22','DISA FSO','technical','Protect audit information from unauthorized deletion.','AU-09a.','N/A','Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion.'),
('000165','draft','2009-05-22','DISA FSO','policy','Write audit records to hardware-enforced, write-once media.','AU-09(01)','N/A','Determine if audit trails are written to hardware-enforced, write-once media.'),
('000166','draft','2009-05-22','DISA FSO','technical','Provide irrefutable evidence that an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.','AU-10','N/A','Determine if irrefutable evidence is provided that an individual (or process acting on behalf of an individual) has performed [AU-10_ODP; actions to be covered by non-repudiation are defined].'),
('000167','draft','2009-05-22','DISA FSO','policy','Retain audit records for an organization-defined time period to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.','AU-11','N/A','Determine if audit records are retained for [AU-11_ODP; a time period to retain audit records that is consistent with the records retention policy is defined] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.'),
('000168','draft','2009-09-15','DISA FSO','policy','Defines the time period for retention of audit records, which is consistent with its records retention policy, to provide support for after-the-fact investigations of incidents and meet regulatory and organizational information retention requirements.','AU-11','N/A','Determine if audit records are retained for [AU-11_ODP; a time period to retain audit records that is consistent with the records retention policy is defined] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.'),
('000169','draft','2009-05-22','DISA FSO','technical','Provide audit record generation capability for the event types the system is capable of auditing as defined in AU-2 a on organization-defined information system components.','AU-12a.','N/A','Determine if audit record generation capability for the event types the system is capable of auditing (defined in AU-02_ODP[01]) is provided by [AU-12_ODP[01]; system components that provide an audit record generation capability for the events types (defined in AU-02_ODP[02]) are defined].'),
('000170','draft','2009-11-03','DISA FSO','policy','Implement a process to ensure that plans of action and milestones for the security program and associated organizational systems document the remedial information security actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation.','PM-04a.02','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems document remedial information security risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems document remedial privacy risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems document remedial supply chain risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation.'),
('000171','draft','2009-09-15','DISA FSO','technical','Allow organization-defined personnel or roles to select the event types that are to be logged by specific components of the system.','AU-12b.','N/A','Determine if [AU-12_ODP[02]; personnel or roles allowed to select the event types that are to be logged by specific components of the system is/are defined] is/are allowed to select the event types that are to be logged by specific components of the system.'),
('000172','draft','2009-09-15','DISA FSO','technical','Generate audit records for the event types defined in AU-2 c that include the audit record content defined in AU-3.','AU-12c.','N/A','Determine if audit records for the event types defined in AU-02_ODP[02] that include the audit record content defined in AU-03 are generated.'),
('000173','draft','2009-09-15','DISA FSO','policy','Defines the level of tolerance for relationship between time stamps of individual records in the audit trail that will be used for correlation.','AU-12(01)','N/A','Determine if audit records from [AU-12(01)_ODP[01]; system components from which audit records are to be compiled into a system-wide (logical or physical) audit trail are defined] are compiled into a system-wide (logical or physical) audit trail that is time-correlated to within [AU-12(01)_ODP[02]; level of tolerance for the relationship between timestamps of individual records in the audit trail is defined].'),
('000174','draft','2009-05-22','DISA FSO','technical','Compile audit records from organization-defined information system components into a system-wide (logical or physical) audit trail that is time-correlated to within an organization-defined level of tolerance for relationship between time stamps of individual records in the audit trail.','AU-12(01)','N/A','Determine if audit records from [AU-12(01)_ODP[01]; system components from which audit records are to be compiled into a system-wide (logical or physical) audit trail are defined] are compiled into a system-wide (logical or physical) audit trail that is time-correlated to within [AU-12(01)_ODP[02]; level of tolerance for the relationship between timestamps of individual records in the audit trail is defined].'),
('000176','draft','2009-05-22','DISA FSO','policy','Manage system authenticators by establishing initial authenticator content for authenticators issued by the organization.','IA-05b.','N/A','Determine if system authenticators are managed through the establishment of initial authenticator content for any authenticators issued by the organization.'),
('000182','draft','2009-05-22','DISA FSO','policy','Manage system authenticators by changing or refreshing authenticators in accordance with the organization-defined time period by authenticator type or when organization-defined events occur.','IA-05f.','N/A','Determine if system authenticators are managed through the change or refreshment of authenticators [IA-05_ODP[01]; a time period for changing or refreshing authenticators by authenticator type is defined] or when [IA-05_ODP[02]; events that trigger the change or refreshment of authenticators are defined] occur.'),
('000183','draft','2009-05-22','DISA FSO','policy','Manage system authenticators by protecting authenticator content from unauthorized disclosure.','IA-05g.','N/A','Determine if system authenticators are managed through the protection of authenticator content from unauthorized disclosure and modification.'),
('000184','draft','2009-05-22','DISA FSO','policy','Manage system authenticators by requiring individuals to take, and having devices implement, specific security controls to protect authenticators.','IA-05h.','N/A','Determine if: - system authenticators are managed through the requirement for individuals to take specific controls to protect authenticators. - system authenticators are managed through the requirement for devices to implement specific controls to protect authenticators.'),
('000185','draft','2009-09-15','DISA FSO','technical','For public key-based authentication, validate certificates by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information.','IA-05(02)(b)(01)','N/A','Determine if when public key infrastructure (PKI) is used, certificates are validated by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information.'),
('000186','draft','2009-09-15','DISA FSO','technical','For public key-based authentication, enforce authorized access to the corresponding private key.','IA-05(02)(a)(01)','N/A','Determine if authorized access to the corresponding private key is enforced for public key-based authentication.'),
('000187','draft','2009-09-15','DISA FSO','technical','For public key-based authentication, map the authenticated identity to the account of the individual or group.','IA-05(02)(a)(02)','N/A','Determine if the authenticated identity is mapped to the account of the individual or group for public key-based authentication.'),
('000197','draft','2009-09-15','DISA FSO','technical','For password-based authentication, transmit passwords only over cryptographically-protected channels.','IA-05(01)(c)','N/A','Determine if for password-based authentication, passwords are only transmitted over cryptographically protected channels.'),
('000201','draft','2009-05-22','DISA FSO','policy','Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.','IA-05(06)','N/A','Determine if authenticators are protected commensurate with the security category of the information to which use of the authenticator permits access.'),
('000204','draft','2009-05-22','DISA FSO','policy','Defines the security controls required to manage the risk of compromise due to individuals having accounts on multiple systems.','IA-05(08)','N/A','Determine if [IA-05(08)_ODP; security controls implemented to manage the risk of compromise due to individuals having accounts on multiple systems are defined] are implemented to manage the risk of compromise due to individuals having accounts on multiple systems.'),
('000206','draft','2009-05-22','DISA FSO','technical','Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.','IA-06','N/A','Determine if the feedback of authentication information is obscured during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.'),
('000209','draft','2009-11-03','DISA FSO','policy','Develop the results of information security measures of performance.','PM-06','N/A','Determine if: - information security measures of performance are developed. - information security measures of performance are monitored. - the results of information security measures of performance are reported. - privacy measures of performance are developed. - privacy measures of performance are monitored. - the results of privacy measures of performance are reported.'),
('000210','draft','2009-11-03','DISA FSO','policy','Monitor the results of information security measures of performance.','PM-06','N/A','Determine if: - information security measures of performance are developed. - information security measures of performance are monitored. - the results of information security measures of performance are reported. - privacy measures of performance are developed. - privacy measures of performance are monitored. - the results of privacy measures of performance are reported.'),
('000211','draft','2009-11-03','DISA FSO','policy','Report on the results of information security measures of performance.','PM-06','N/A','Determine if: - information security measures of performance are developed. - information security measures of performance are monitored. - the results of information security measures of performance are reported. - privacy measures of performance are developed. - privacy measures of performance are monitored. - the results of privacy measures of performance are reported.'),
('000212','draft','2009-11-03','DISA FSO','policy','Develop an enterprise architecture with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-07','N/A','Determine if: - an enterprise architecture is developed with consideration for information security. - an enterprise architecture is maintained with consideration for information security. - an enterprise architecture is developed with consideration for privacy. - an enterprise architecture is maintained with consideration for privacy. - an enterprise architecture is developed with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation. - an enterprise architecture is maintained with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.'),
('000213','draft','2009-09-14','DISA FSO','technical','Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.','AC-03','N/A','Determine if approved authorizations for logical access to information and system resources are enforced in accordance with applicable access control policies.'),
('000216','draft','2009-11-03','DISA FSO','policy','Address information security issues in the development and documentation of a critical infrastructure and key resources protection plan.','PM-08','N/A','Determine if: - information security issues are addressed in the development of a critical infrastructure and key resources protection plan. - information security issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - information security issues are addressed in the update of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the development of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the update of a critical infrastructure and key resources protection plan.'),
('000217','draft','2009-09-24','DISA FSO','policy','Defines a time period after which inactive accounts are automatically disabled.',NULL,'N/A',NULL),
('000219','draft','2009-09-14','DISA FSO','technical','When transferring information between different security domains, decompose information into organization-defined policy-relevant subcomponents for submission to policy enforcement mechanisms.','AC-04(13)','N/A','Determine if when transferring information between different security domains, information is decomposed into [AC-04(13)_ODP; policy-relevant subcomponents into which to decompose information for submission to policy enforcement mechanisms are defined] for submission to policy enforcement mechanisms.'),
('000225','draft','2009-09-14','DISA FSO','policy','Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned organizational tasks.','AC-06','N/A','Determine if the principle of least privilege is employed, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.'),
('000227','draft','2009-11-03','DISA FSO','policy','Develop a comprehensive strategy to manage security risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of information systems.','PM-09a.01','N/A','Determine if a comprehensive strategy is developed to manage security risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of organizational systems.'),
('000228','draft','2009-11-03','DISA FSO','policy','Implement the risk management strategy consistently across the organization.','PM-09b.','N/A','Determine if the risk management strategy is implemented consistently across the organization.'),
('000232','draft','2009-09-14','DISA FSO','policy','Document and provide supporting rationale in the security plan for the system, user actions not requiring identification and authentication.','AC-14b.','N/A','Determine if: - user actions not requiring identification or authentication are documented in the security plan for the system. - a rationale for user actions not requiring identification or authentication is provided in the security plan for the system.'),
('000233','draft','2009-11-03','DISA FSO','policy','Designate individuals to fulfill specific roles and responsibilities within the organizational risk management process.','PM-10b.','N/A','Determine if individuals are designated to fulfill specific roles and responsibilities within the organizational risk management process.'),
('000234','draft','2009-11-03','DISA FSO','policy','Integrate the authorization processes into an organization-wide risk management program.','PM-10c.','N/A','Determine if the authorization processes are integrated into an organization-wide risk management program.'),
('000235','draft','2009-11-04','DISA FSO','policy','Define organizational mission and business processes with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-11a.','N/A','Determine if: - organizational mission and business processes are defined with consideration for information security. - organizational mission and business processes are defined with consideration for privacy. - organizational mission and business processes are defined with consideration for the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.'),
('000236','draft','2009-11-04','DISA FSO','policy','Determine information protection needs arising from the defined mission and business processes.','PM-11b.','N/A','Determine if: - information protection needs arising from the defined mission and business processes are determined. - personally identifiable information processing needs arising from the defined mission and business processes are determined.'),
('000238','draft','2009-09-15','DISA FSO','policy','Defines the frequency to review and update the current assessment, authorization, and monitoring policy.','CA-01c.01','N/A','Determine if: - the current assessment, authorization, and monitoring policy is reviewed and updated [CA-01_ODP[05]; the frequency at which the current assessment, authorization, and monitoring policy is reviewed and updated is defined]. - the current assessment, authorization, and monitoring policy is reviewed and updated following [CA-01_ODP[06]; events that would require the current assessment, authorization, and monitoring policy to be reviewed and updated are defined].'),
('000239','draft','2009-09-15','DISA FSO','policy','Develop and document an organization-level; mission/business process; system-level assessment, authorization, and monitoring policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','CA-01a.01(a)','N/A','Determine if: - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy addresses purpose. - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy addresses scope. - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level};] assessment, authorization, and monitoring policy addresses roles. - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy addresses responsibilities. - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy addresses management commitment. - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy addresses coordination among organizational entities. - the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy addresses compliance.'),
('000240','draft','2009-09-15','DISA FSO','policy','Disseminates to organization-defined personnel or roles an organization-level; mission/business process; system-level assessment, authorization, and monitoring policy.','CA-01a.','N/A','Determine if: - an assessment, authorization, and monitoring policy is developed and documented. - the assessment, authorization, and monitoring policy is disseminated to [CA-01_ODP[01]; personnel or roles to whom the assessment, authorization, and monitoring policy is to be disseminated is/are defined].'),
('000241','draft','2009-09-15','DISA FSO','policy','Review and update the current assessment, authorization, and monitoring policy on an organization-defined frequency.','CA-01c.01','N/A','Determine if: - the current assessment, authorization, and monitoring policy is reviewed and updated [CA-01_ODP[05]; the frequency at which the current assessment, authorization, and monitoring policy is reviewed and updated is defined]. - the current assessment, authorization, and monitoring policy is reviewed and updated following [CA-01_ODP[06]; events that would require the current assessment, authorization, and monitoring policy to be reviewed and updated are defined].'),
('000242','draft','2009-09-15','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls.','CA-01a.02','N/A','Determine if: - assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented. - the assessment, authorization, and monitoring procedures are disseminated to [CA-01_ODP[02]; personnel or roles to whom the assessment, authorization, and monitoring procedures are to be disseminated is/are defined].'),
('000243','draft','2009-09-15','DISA FSO','policy','Disseminate to organization-defined personnel or roles procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls.','CA-01a.02','N/A','Determine if: - assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented. - the assessment, authorization, and monitoring procedures are disseminated to [CA-01_ODP[02]; personnel or roles to whom the assessment, authorization, and monitoring procedures are to be disseminated is/are defined].'),
('000244','draft','2009-09-15','DISA FSO','policy','Review and update the current assessment, authorization, and monitoring procedures on an organization-defined frequency.','CA-01c.02','N/A','Determine if: - the current assessment, authorization, and monitoring procedures are reviewed and updated [CA-01_ODP[07]; the frequency at which the current assessment, authorization, and monitoring procedures are reviewed and updated is defined]. - the current assessment, authorization, and monitoring procedures are reviewed and updated following [CA-01_ODP[08]; events that would require assessment, authorization, and monitoring procedures to be reviewed and updated are defined].'),
('000246','draft','2009-09-15','DISA FSO','policy','Develop a control assessment plan that describes the scope of the assessment including controls and control enhancements under assessment.','CA-02b.01','N/A','Determine if a control assessment plan is developed that describes the scope of the assessment, including controls and control enhancements under assessment.'),
('000247','draft','2009-09-15','DISA FSO','policy','Develop a control assessment plan that describes the scope of the assessment including assessment procedures to be used to determine control effectiveness.','CA-02b.02','N/A','Determine if a control assessment plan is developed that describes the scope of the assessment, including assessment procedures to be used to determine control effectiveness.'),
('000248','draft','2009-09-15','DISA FSO','policy','Develop a control assessment plan that describes the scope of the assessment including assessment environment.','CA-02b.03','N/A','Determine if: - a control assessment plan is developed that describes the scope of the assessment, including the assessment environment. - a control assessment plan is developed that describes the scope of the assessment, including the assessment team. - a control assessment plan is developed that describes the scope of the assessment, including assessment roles and responsibilities.'),
('000251','draft','2009-09-15','DISA FSO','policy','Assess the controls in the systems and its environment of operation on an organization-defined frequency, to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements.','CA-02d.','N/A','Determine if: - controls are assessed in the system and its environment of operation [CA-02_ODP[01]; the frequency at which to assess controls in the system and its environment of operation is defined] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements. - controls are assessed in the system and its environment of operation [CA-02_ODP[01]; the frequency at which to assess controls in the system and its environment of operation is defined] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established privacy requirements.'),
('000252','draft','2009-09-15','DISA FSO','policy','Defines the frequency on which the security controls in the system and its environment of operation are assessed.','CA-02d.','N/A','Determine if: - controls are assessed in the system and its environment of operation [CA-02_ODP[01]; the frequency at which to assess controls in the system and its environment of operation is defined] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements. - controls are assessed in the system and its environment of operation [CA-02_ODP[01]; the frequency at which to assess controls in the system and its environment of operation is defined] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established privacy requirements.'),
('000253','draft','2009-09-15','DISA FSO','policy','Produce a control assessment report that document the results of the assessment.',NULL,'N/A',NULL),
('000254','draft','2009-09-15','DISA FSO','policy','Provide the results of the control assessment to organization-defined individuals or roles.','CA-02f.','N/A','Determine if the results of the control assessment are provided to [CA-02_ODP[02]; individuals or roles to whom control assessment results are to be provided are defined].'),
('000255','draft','2009-09-15','DISA FSO','policy','Employ independent assessors or assessment teams to conduct control assessments.','CA-02(01)','N/A','Determine if independent assessors or assessment teams are employed to conduct control assessments.'),
('000256','draft','2009-09-15','DISA FSO','policy','Include as part of the control assessments, announced or unannounced, on an organization-defined frequency, in-depth monitoring; security instrumentation; automated security test cases; vulnerability scanning; malicious user testing; insider threat assessment; performance and load testing; data leakage or data loss assessment; and/or organization-defined other forms of assessment.','CA-02(02)','N/A','Determine if [CA-02(02)_ODP[01]; frequency at which to include specialized assessments as part of the control assessment is defined] [CA-02(02)_ODP[02]; one of the following PARAMETER VALUES is selected: {announced; unannounced}] [CA-02(02)_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {in-depth monitoring; security instrumentation; automated security test cases; vulnerability scanning; malicious user testing; insider threat assessment; performance and load testing; data leakage or data loss assessment; [CA-02(02)_ODP[04]; other forms of assessment are defined (if selected)]}] are included as part of control assessments.'),
('000258','draft','2009-09-15','DISA FSO','policy','Document, as part of each exchange agreement, the interface characteristics.','CA-03b.','N/A','Determine if: - the interface characteristics are documented as part of each exchange agreement. - security requirements are documented as part of each exchange agreement. - privacy requirements are documented as part of each exchange agreement. - controls are documented as part of each exchange agreement. - responsibilities for each system are documented as part of each exchange agreement. - the impact level of the information communicated is documented as part of each exchange agreement.'),
('000259','draft','2009-09-15','DISA FSO','policy','Document, as part of each exchange agreement, the security requirements, controls and responsibilities for each system, and the impact level of the information communicated.','CA-03b.','N/A','Determine if: - the interface characteristics are documented as part of each exchange agreement. - security requirements are documented as part of each exchange agreement. - privacy requirements are documented as part of each exchange agreement. - controls are documented as part of each exchange agreement. - responsibilities for each system are documented as part of each exchange agreement. - the impact level of the information communicated is documented as part of each exchange agreement.'),
('000264','draft','2009-09-15','DISA FSO','policy','Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system.','CA-05a.','N/A','Determine if a plan of action and milestones for the system is developed to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system.'),
('000265','draft','2009-09-15','DISA FSO','policy','Defines the frequency with which to update the existing plan of action and milestones for the system.','CA-05b.','N/A','Determine if existing plan of action and milestones are updated [CA-05_ODP; the frequency at which to update an existing plan of action and milestones based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities is defined] based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.'),
('000266','draft','2009-09-15','DISA FSO','policy','Update, on an organization-defined frequency, the existing plan of action and milestones based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.','CA-05b.','N/A','Determine if existing plan of action and milestones are updated [CA-05_ODP; the frequency at which to update an existing plan of action and milestones based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities is defined] based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.'),
('000267','draft','2009-09-15','DISA FSO','policy','Ensure the accuracy of the plan of action and milestones for the system using organization-defined automated mechanisms.','CA-05(01)','N/A','Determine if [CA-05(01)_ODP; automated mechanisms used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system are defined] are used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system.'),
('000268','draft','2009-09-15','DISA FSO','policy','Ensure the currency of the plan of action and milestones for the system using organization-defined automated mechanisms.','CA-05(01)','N/A','Determine if [CA-05(01)_ODP; automated mechanisms used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system are defined] are used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system.'),
('000269','draft','2009-09-15','DISA FSO','policy','Ensure the availability of the plan of action and milestones for the system using organization-defined automated mechanisms.','CA-05(01)','N/A','Determine if [CA-05(01)_ODP; automated mechanisms used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system are defined] are used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system.'),
('000270','draft','2009-09-15','DISA FSO','policy','Assign a senior official as the authorizing official for the system.','CA-06a.','N/A','Determine if a senior official is assigned as the authorizing official for the system.'),
('000271','draft','2009-09-15','DISA FSO','policy','Ensure the authorizing official for the system authorizes the system to operate before commencing operations.','CA-06c.02','N/A','Determine if before commencing operations, the authorizing official for the system authorizes the system to operate.'),
('000272','draft','2009-09-15','DISA FSO','policy','Update the authorization on an organization-defined frequency.','CA-06e.','N/A','Determine if the authorizations are updated [CA-06_ODP; frequency at which to update the authorizations is defined].'),
('000273','draft','2009-09-15','DISA FSO','policy','Defines the frequency with which to update the authorizations.','CA-06e.','N/A','Determine if the authorizations are updated [CA-06_ODP; frequency at which to update the authorizations is defined].'),
('000274','draft','2009-09-15','DISA FSO','policy','Develop a continuous monitoring strategy.','CA-07','N/A','Determine if: - a system-level continuous monitoring strategy is developed. - system-level continuous monitoring is implemented in accordance with the organization-level continuous monitoring strategy.'),
('000279','draft','2009-09-15','DISA FSO','policy','Implement ongoing control assessments in accordance with the continuous monitoring strategy.','CA-07c.','N/A','Determine if system-level continuous monitoring includes ongoing control assessments in accordance with the continuous monitoring strategy.'),
('000280','draft','2009-09-15','DISA FSO','policy','Implement a continuous monitoring program that includes reporting the security status to organization-defined personnel or roles on an organization-defined frequency.','CA-07g.','N/A','Determine if: - system-level continuous monitoring includes reporting the security status of the system to [CA-07_ODP[04]; personnel or roles to whom the security status of the system is reported are defined] [CA-07_ODP[05]; frequency at which the security status of the system is reported is defined]. - system-level continuous monitoring includes reporting the privacy status of the system to [CA-07_ODP[06]; personnel or roles to whom the privacy status of the system is reported are defined] [CA-07_ODP[07]; frequency at which the privacy status of the system is reported is defined].'),
('000281','draft','2009-09-15','DISA FSO','policy','Defines the frequency with which to report the security status to organization-defined personnel or roles.','CA-07g.','N/A','Determine if: - system-level continuous monitoring includes reporting the security status of the system to [CA-07_ODP[04]; personnel or roles to whom the security status of the system is reported are defined] [CA-07_ODP[05]; frequency at which the security status of the system is reported is defined]. - system-level continuous monitoring includes reporting the privacy status of the system to [CA-07_ODP[06]; personnel or roles to whom the privacy status of the system is reported are defined] [CA-07_ODP[07]; frequency at which the privacy status of the system is reported is defined].'),
('000282','draft','2009-09-15','DISA FSO','policy','Employ independent assessors or assessment teams to monitor the controls in the system on an ongoing basis.','CA-07(01)','N/A','Determine if independent assessors or assessment teams are employed to monitor the controls in the system on an ongoing basis.'),
('000286','draft','2009-09-17','DISA FSO','policy','Defines the frequency with which to review and update the configuration management policies.','CM-01c.01','N/A','Determine if: - the current configuration management policy is reviewed and updated [CM-01_ODP[05]; the frequency at which the current configuration management policy is reviewed and updated is defined]. - the current configuration management policy is reviewed and updated following [CM-01_ODP[06]; events that would require the current configuration management policy to be reviewed and updated are defined].'),
('000287','draft','2009-09-17','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','CM-01a.01(a)','N/A','Determine if: - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses purpose. - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses scope. - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses roles. - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses responsibilities. - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses management commitment. - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses coordination among organizational entities. - the [CM-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the configuration management policy addresses compliance.'),
('000289','draft','2009-09-17','DISA FSO','policy','Review and update, on an organization-defined frequency, the configuration management policy.','CM-01c.01','N/A','Determine if: - the current configuration management policy is reviewed and updated [CM-01_ODP[05]; the frequency at which the current configuration management policy is reviewed and updated is defined]. - the current configuration management policy is reviewed and updated following [CM-01_ODP[06]; events that would require the current configuration management policy to be reviewed and updated are defined].'),
('000290','draft','2009-09-17','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the organization-level; mission/business process-level; and/or system-level configuration management policy and the associated configuration management controls.','CM-01a.02','N/A','Determine if: - configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented. - the configuration management procedures are disseminated to [CM-01_ODP[02]; personnel or roles to whom the configuration management procedures are to be disseminated is/are defined].'),
('000292','draft','2009-09-17','DISA FSO','policy','Review and update, on an organization-defined frequency, the procedures to facilitate the implementation of the organization-level; mission/business process-level; and/or system-level configuration management policy and associated configuration management controls.','CM-01a.02','N/A','Determine if: - configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented. - the configuration management procedures are disseminated to [CM-01_ODP[02]; personnel or roles to whom the configuration management procedures are to be disseminated is/are defined].'),
('000295','draft','2009-09-17','DISA FSO','policy','Maintain, under configuration control, a current baseline configuration of the system.','CM-02a.','N/A','Determine if: - a current baseline configuration of the system is developed and documented. - a current baseline configuration of the system is maintained under configuration control.'),
('000296','draft','2009-09-17','DISA FSO','policy','Review and update the baseline configuration of the system on an organization-defined frequency.','CM-02b.01','N/A','Determine if the baseline configuration of the system is reviewed and updated [CM-02_ODP[01]; the frequency of baseline configuration review and update is defined].'),
('000297','draft','2009-09-17','DISA FSO','policy','Review and update the baseline configuration of the system when required due to organization-defined circumstances.','CM-02b.02','N/A','Determine if the baseline configuration of the system is reviewed and updated when required due to [CM-02_ODP[02]; the circumstances requiring baseline configuration review and update are defined].'),
('000300','draft','2009-09-17','DISA FSO','policy','Maintain complete configuration of the system using organization-defined automated mechanisms.','CM-02(02)','N/A','Determine if: - the currency of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the completeness of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the accuracy of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the availability of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined].'),
('000301','draft','2009-09-17','DISA FSO','policy','Maintain current configuration of the system using organization-defined automated mechanisms.','CM-02(02)','N/A','Determine if: - the currency of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the completeness of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the accuracy of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the availability of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined].'),
('000302','draft','2009-09-17','DISA FSO','policy','Maintain accurate configuration of the system using organization-defined automated mechanisms.','CM-02(02)','N/A','Determine if: - the currency of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the completeness of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the accuracy of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the availability of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined].'),
('000303','draft','2009-09-17','DISA FSO','policy','Maintain available configuration of the system using organization-defined automated mechanisms.','CM-02(02)','N/A','Determine if: - the currency of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the completeness of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the accuracy of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the availability of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined].'),
('000304','draft','2009-09-17','DISA FSO','policy','Retain organization-defined number of previous versions of baseline configurations of the system to support rollback.','CM-02(03)','N/A','Determine if [CM-02(03)_ODP; the number of previous baseline configuration versions to be retained is defined] of previous baseline configuration version(s) of the system is/are retained to support rollback.'),
('000311','draft','2009-09-17','DISA FSO','policy','Maintain a baseline configuration for system development environments that is managed separately from the operational baseline configuration.','CM-02(06)','N/A','Determine if: - a baseline configuration for system development environments that is managed separately from the operational baseline configuration is maintained. - a baseline configuration for test environments that is managed separately from the operational baseline configuration is maintained.'),
('000312','draft','2009-09-17','DISA FSO','policy','Maintain a baseline configuration for system test environments that is managed separately from the operational baseline configuration.','CM-02(06)','N/A','Determine if: - a baseline configuration for system development environments that is managed separately from the operational baseline configuration is maintained. - a baseline configuration for test environments that is managed separately from the operational baseline configuration is maintained.'),
('000313','draft','2009-09-17','DISA FSO','policy','Determine and document the types of changes to the system that are configuration-controlled.','CM-03a.','N/A','Determine if the types of changes to the system that are configuration-controlled are determined and documented.'),
('000314','draft','2009-09-17','DISA FSO','policy','Approve or disapprove configuration-controlled changes to the system, with explicit consideration for security impact analyses.','CM-03b.','N/A','Determine if: - proposed configuration-controlled changes to the system are reviewed. - proposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security and privacy impact analyses.'),
('000316','draft','2009-09-17','DISA FSO','policy','Retain records of configuration-controlled changes to the system for an organization-defined time period.','CM-03e.','N/A','Determine if records of configuration-controlled changes to the system are retained for [CM-03_ODP[01]; the time period to retain records of configuration-controlled changes is defined].'),
('000318','draft','2009-09-17','DISA FSO','policy','Monitor and review activities associated with configuration-controlled changes to the system.','CM-03f.','N/A','Determine if: - activities associated with configuration-controlled changes to the system are monitored. - activities associated with configuration-controlled changes to the system are reviewed.'),
('000319','draft','2009-09-17','DISA FSO','policy','Coordinate and provides oversight for configuration change control activities through an organization-defined configuration change control element that convenes at the organization-defined frequency, and/or for any organization-defined configuration change conditions.','CM-03g.','N/A','Determine if: - configuration change control activities are coordinated and overseen by [CM-03_ODP[02]; the configuration change control element responsible for coordinating and overseeing change control activities is defined]. - the configuration control element convenes [CM-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[CM-03_ODP[04]; the frequency at which the configuration control element convenes is defined (if selected)]; when [CM-03_ODP[05]; configuration change conditions that prompt the configuration control element to convene are defined (if selected)]}]].'),
('000320','draft','2009-09-17','DISA FSO','policy','Defines the frequency with which to convene the configuration change control element.','CM-03g.','N/A','Determine if: - configuration change control activities are coordinated and overseen by [CM-03_ODP[02]; the configuration change control element responsible for coordinating and overseeing change control activities is defined]. - the configuration control element convenes [CM-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[CM-03_ODP[04]; the frequency at which the configuration control element convenes is defined (if selected)]; when [CM-03_ODP[05]; configuration change conditions that prompt the configuration control element to convene are defined (if selected)]}]].'),
('000321','draft','2009-09-17','DISA FSO','policy','Defines configuration change conditions that prompt the configuration change control element to convene.','CM-03g.','N/A','Determine if: - configuration change control activities are coordinated and overseen by [CM-03_ODP[02]; the configuration change control element responsible for coordinating and overseeing change control activities is defined]. - the configuration control element convenes [CM-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[CM-03_ODP[04]; the frequency at which the configuration control element convenes is defined (if selected)]; when [CM-03_ODP[05]; configuration change conditions that prompt the configuration control element to convene are defined (if selected)]}]].'),
('000322','draft','2009-09-17','DISA FSO','policy','Use organization-defined automated mechanisms to document proposed changes to the system.','CM-03(01)(a)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to document proposed changes to the system.'),
('000323','draft','2009-09-17','DISA FSO','policy','Use organization-defined automated mechanisms to notify organization-defined approval authorities of proposed changes to the system and request change approval.','CM-03(01)(b)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to notify [CM-03(01)_ODP[02]; approval authorities to be notified of and request approval for proposed changes to the system are defined] of proposed changes to the system and request change approval.'),
('000324','draft','2009-09-17','DISA FSO','policy','Use organization-defined automated mechanisms to highlight proposed changes to the system that have not been approved or disapproved by an organization-defined time period.','CM-03(01)(c)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to highlight proposed changes to the system that have not been approved or disapproved within [CM-03(01)_ODP[03]l the time period after which to highlight changes that have not been approved or disapproved is defined].'),
('000325','draft','2009-09-17','DISA FSO','policy','Use organization-defined automated mechanisms to prohibit changes to the system until designated approvals are received.','CM-03(01)(d)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to prohibit changes to the system until designated approvals are received.'),
('000326','draft','2009-09-17','DISA FSO','policy','Use organization-defined automated mechanisms to document all changes to the system.','CM-03(01)(e)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to document all changes to the system.'),
('000327','draft','2009-09-17','DISA FSO','policy','Tests changes to the system before finalizing the implementation of the changes.','CM-03(02)','N/A','Determine if: - changes to the system are tested before finalizing the implementation of the changes. - changes to the system are validated before finalizing the implementation of the changes. - changes to the system are documented before finalizing the implementation of the changes.'),
('000328','draft','2009-09-17','DISA FSO','policy','Validate changes to the system before finalizing the implementation of the changes.','CM-03(02)','N/A','Determine if: - changes to the system are tested before finalizing the implementation of the changes. - changes to the system are validated before finalizing the implementation of the changes. - changes to the system are documented before finalizing the implementation of the changes.'),
('000329','draft','2009-09-17','DISA FSO','policy','Document changes to the system before finalizing the implementation of the changes.','CM-03(02)','N/A','Determine if: - changes to the system are tested before finalizing the implementation of the changes. - changes to the system are validated before finalizing the implementation of the changes. - changes to the system are documented before finalizing the implementation of the changes.'),
('000330','draft','2009-09-17','DISA FSO','policy','Implement changes to the current system baseline using organization-defined automated mechanisms.','CM-03(03)','N/A','Determine if: - changes to the current system baseline are implemented using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined]. - the updated baseline is deployed across the installed base using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined].'),
('000331','draft','2009-09-17','DISA FSO','policy','Deploy the updated system baseline across the installed base using organization-defined automated mechanism.','CM-03(03)','N/A','Determine if: - changes to the current system baseline are implemented using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined]. - the updated baseline is deployed across the installed base using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined].'),
('000332','draft','2009-09-17','DISA FSO','policy','Require an organization-defined security representative to be a member of the organization-defined configuration change control element.','CM-03(04)','N/A','Determine if: - [CM-03(04)_ODP[01]; security representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined]. - [CM-03(04)_ODP[02]; privacy representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined].'),
('000333','draft','2009-09-18','DISA FSO','policy','Analyze changes to the system to determine potential security impacts prior to change implementation.','CM-04','N/A','Determine if: - changes to the system are analyzed to determine potential security impacts prior to change implementation. - changes to the system are analyzed to determine potential privacy impacts prior to change implementation.'),
('000335','draft','2009-09-18','DISA FSO','policy','After system changes, verify that the impacted controls are implemented correctly, meeting the security requirements for the system.','CM-04(02)','N/A','Determine if: - the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes. - the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.'),
('000336','draft','2009-09-18','DISA FSO','policy','After system changes, verify that the impacted controls are operating as intended, meeting the security requirements for the system.','CM-04(02)','N/A','Determine if: - the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes. - the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.'),
('000337','draft','2009-09-18','DISA FSO','policy','After system changes, verify that the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system.','CM-04(02)','N/A','Determine if: - the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes. - the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.'),
('000340','draft','2009-09-18','DISA FSO','policy','Approve physical access restrictions associated with changes to the system.','CM-05','N/A','Determine if: - physical access restrictions associated with changes to the system are defined and documented. - physical access restrictions associated with changes to the system are approved. - physical access restrictions associated with changes to the system are enforced. - logical access restrictions associated with changes to the system are defined and documented. - logical access restrictions associated with changes to the system are approved. - logical access restrictions associated with changes to the system are enforced.'),
('000341','draft','2009-09-18','DISA FSO','policy','Enforce physical access restrictions associated with changes to the system.','CM-05','N/A','Determine if: - physical access restrictions associated with changes to the system are defined and documented. - physical access restrictions associated with changes to the system are approved. - physical access restrictions associated with changes to the system are enforced. - logical access restrictions associated with changes to the system are defined and documented. - logical access restrictions associated with changes to the system are approved. - logical access restrictions associated with changes to the system are enforced.'),
('000344','draft','2009-09-18','DISA FSO','policy','Approve logical access restrictions associated with changes to the system.','CM-05','N/A','Determine if: - physical access restrictions associated with changes to the system are defined and documented. - physical access restrictions associated with changes to the system are approved. - physical access restrictions associated with changes to the system are enforced. - logical access restrictions associated with changes to the system are defined and documented. - logical access restrictions associated with changes to the system are approved. - logical access restrictions associated with changes to the system are enforced.'),
('000345','draft','2009-09-18','DISA FSO','policy','Enforce logical access restrictions associated with changes to the system.','CM-05','N/A','Determine if: - physical access restrictions associated with changes to the system are defined and documented. - physical access restrictions associated with changes to the system are approved. - physical access restrictions associated with changes to the system are enforced. - logical access restrictions associated with changes to the system are defined and documented. - logical access restrictions associated with changes to the system are approved. - logical access restrictions associated with changes to the system are enforced.'),
('000353','draft','2009-09-18','DISA FSO','policy','Defines system components requiring enforcement of a dual authorization for system changes.','CM-05(04)','N/A','Determine if: - dual authorization for implementing changes to [CM-05(04)_ODP[01]; system components requiring dual authorization for changes are defined] is enforced. - dual authorization for implementing changes to [CM-05(04)_ODP[02]; system-level information requiring dual authorization for changes is defined] is enforced.'),
('000354','draft','2009-09-18','DISA FSO','policy','Enforce dual authorization for implementing changes to organization-defined system components.','CM-05(04)','N/A','Determine if: - dual authorization for implementing changes to [CM-05(04)_ODP[01]; system components requiring dual authorization for changes are defined] is enforced. - dual authorization for implementing changes to [CM-05(04)_ODP[02]; system-level information requiring dual authorization for changes is defined] is enforced.'),
('000366','draft','2009-09-18','DISA FSO','policy','Implement the security configuration settings.','CM-06b.','N/A','Determine if the configuration settings documented in CM-06a are implemented.'),
('000367','draft','2009-09-18','DISA FSO','policy','Identify any deviations from the established configuration settings for organization-defined system components based on organization-defined operational requirements.','CM-06c.','N/A','Determine if: - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are identified and documented based on [CM-06_ODP[03]; operational requirements necessitating approval of deviations are defined]. - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are approved.'),
('000368','draft','2009-09-18','DISA FSO','policy','Document any deviations from the established configuration settings for organization-defined system components based on organization-defined operational requirements.','CM-06c.','N/A','Determine if: - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are identified and documented based on [CM-06_ODP[03]; operational requirements necessitating approval of deviations are defined]. - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are approved.'),
('000369','draft','2009-09-18','DISA FSO','policy','Approve any deviations from the established configuration settings for organization-defined system components based on organization-defined operational requirements.','CM-06c.','N/A','Determine if: - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are identified and documented based on [CM-06_ODP[03]; operational requirements necessitating approval of deviations are defined]. - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are approved.'),
('000370','draft','2009-09-18','DISA FSO','policy','Manage configuration settings for organization-defined system components using organization-defined automated mechanisms.','CM-06(01)','N/A','Determine if: - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are managed using [CM-06(01)_ODP[02]; automated mechanisms to manage configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are applied using [CM-06(01)_ODP[03]; automated mechanisms to apply configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are verified using [CM-06(01)_ODP[04]; automated mechanisms to verify configuration settings are defined].'),
('000371','draft','2009-09-18','DISA FSO','policy','Apply configuration settings for organization-defined system components using organization-defined automated mechanisms.','CM-06(01)','N/A','Determine if: - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are managed using [CM-06(01)_ODP[02]; automated mechanisms to manage configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are applied using [CM-06(01)_ODP[03]; automated mechanisms to apply configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are verified using [CM-06(01)_ODP[04]; automated mechanisms to verify configuration settings are defined].'),
('000372','draft','2009-09-18','DISA FSO','policy','Verify configuration settings for organization-defined system components using organization-defined automated mechanisms.','CM-06(01)','N/A','Determine if: - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are managed using [CM-06(01)_ODP[02]; automated mechanisms to manage configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are applied using [CM-06(01)_ODP[03]; automated mechanisms to apply configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are verified using [CM-06(01)_ODP[04]; automated mechanisms to verify configuration settings are defined].'),
('000380','draft','2009-09-18','DISA FSO','policy','Defines prohibited or restricted functions, system ports, protocols, software and/or services for the system.','CM-07b.','N/A','Determine if: - the use of [CM-07_ODP[02]; functions to be prohibited or restricted are defined] is prohibited or restricted. - the use of [CM-07_ODP[03]; ports to be prohibited or restricted are defined] is prohibited or restricted. - the use of [CM-07_ODP[04]; protocols to be prohibited or restricted are defined] is prohibited or restricted. - the use of [CM-07_ODP[05]; software to be prohibited or restricted is defined] is prohibited or restricted. - the use of [CM-07_ODP[06]; services to be prohibited or restricted are defined] is prohibited or restricted.'),
('000381','draft','2009-09-18','DISA FSO','technical','Configure the system to provide only organization-defined mission essential capabilities.','CM-07a.','N/A','Determine if the system is configured to provide only [CM-07_ODP[01]; mission-essential capabilities for the system are defined].'),
('000382','draft','2009-09-18','DISA FSO','technical','Configure the system to prohibit or restrict the use of organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services.','CM-07b.','N/A','Determine if: - the use of [CM-07_ODP[02]; functions to be prohibited or restricted are defined] is prohibited or restricted. - the use of [CM-07_ODP[03]; ports to be prohibited or restricted are defined] is prohibited or restricted. - the use of [CM-07_ODP[04]; protocols to be prohibited or restricted are defined] is prohibited or restricted. - the use of [CM-07_ODP[05]; software to be prohibited or restricted is defined] is prohibited or restricted. - the use of [CM-07_ODP[06]; services to be prohibited or restricted are defined] is prohibited or restricted.'),
('000384','draft','2009-09-18','DISA FSO','policy','Review the system per organization-defined frequency to identify unnecessary and nonsecure functions, ports, protocols, software, and services.','CM-07(01)(a)','N/A','Determine if the system is reviewed [CM-07(01)_ODP[01]; the frequency at which to review the system to identify unnecessary and/or non-secure functions, ports, protocols, software, and/or services is defined] to identify unnecessary and/or non-secure functions, ports, protocols, software, and services.'),
('000387','draft','2009-09-18','DISA FSO','policy','Defines registration requirements for functions, ports, protocols, and services.','CM-07(03)','N/A','Determine if [CM-07(03)_ODP; registration requirements for functions, ports, protocols, and services are defined] are complied with.'),
('000388','draft','2009-09-18','DISA FSO','policy','Ensure compliance with organization-defined registration requirements for functions, ports, protocols, and services.','CM-07(03)','N/A','Determine if [CM-07(03)_ODP; registration requirements for functions, ports, protocols, and services are defined] are complied with.'),
('000398','draft','2009-09-18','DISA FSO','policy','Defines information deemed necessary to achieve effective system component accountability.','CM-08a.05','N/A','Determine if an inventory of system components that includes [CM-08_ODP[01]; information deemed necessary to achieve effective system component accountability is defined] is developed and documented.'),
('000408','draft','2009-09-18','DISA FSO','policy','Update the inventory of system components as part of component installations.','CM-08(01)','N/A','Determine if: - the inventory of system components is updated as part of component installations. - the inventory of system components is updated as part of component removals. - the inventory of system components is updated as part of system updates.'),
('000409','draft','2009-09-18','DISA FSO','policy','Update the inventory of system components as part of component removals.','CM-08(01)','N/A','Determine if: - the inventory of system components is updated as part of component installations. - the inventory of system components is updated as part of component removals. - the inventory of system components is updated as part of system updates.'),
('000410','draft','2009-09-18','DISA FSO','policy','Update the inventory of system components as part of system updates.','CM-08(01)','N/A','Determine if: - the inventory of system components is updated as part of component installations. - the inventory of system components is updated as part of component removals. - the inventory of system components is updated as part of system updates.'),
('000411','draft','2009-09-18','DISA FSO','policy','Maintain the currency of the inventory of system components using organization-defined automated mechanisms.','CM-08(02)','N/A','Determine if: - [CM-08(02)_ODP[01]; automated mechanisms used to maintain the currency of the system component inventory are defined] are used to maintain the currency of the system component inventory. - [CM-08(02)_ODP[02]; automated mechanisms used to maintain the completeness of the system component inventory are defined] are used to maintain the completeness of the system component inventory. - [CM-08(02)_ODP[03]; automated mechanisms used to maintain the accuracy of the system component inventory are defined] are used to maintain the accuracy of the system component inventory. - [CM-08(02)_ODP[04]; automated mechanisms used to maintain the availability of the system component inventory are defined] are used to maintain the availability of the system component inventory.'),
('000412','draft','2009-09-18','DISA FSO','policy','Maintain the completeness of the inventory of system components using organization-defined automated mechanisms.','CM-08(02)','N/A','Determine if: - [CM-08(02)_ODP[01]; automated mechanisms used to maintain the currency of the system component inventory are defined] are used to maintain the currency of the system component inventory. - [CM-08(02)_ODP[02]; automated mechanisms used to maintain the completeness of the system component inventory are defined] are used to maintain the completeness of the system component inventory. - [CM-08(02)_ODP[03]; automated mechanisms used to maintain the accuracy of the system component inventory are defined] are used to maintain the accuracy of the system component inventory. - [CM-08(02)_ODP[04]; automated mechanisms used to maintain the availability of the system component inventory are defined] are used to maintain the availability of the system component inventory.'),
('000413','draft','2009-09-18','DISA FSO','policy','Maintain the accuracy of the inventory of system components using organization-defined automated mechanisms.','CM-08(02)','N/A','Determine if: - [CM-08(02)_ODP[01]; automated mechanisms used to maintain the currency of the system component inventory are defined] are used to maintain the currency of the system component inventory. - [CM-08(02)_ODP[02]; automated mechanisms used to maintain the completeness of the system component inventory are defined] are used to maintain the completeness of the system component inventory. - [CM-08(02)_ODP[03]; automated mechanisms used to maintain the accuracy of the system component inventory are defined] are used to maintain the accuracy of the system component inventory. - [CM-08(02)_ODP[04]; automated mechanisms used to maintain the availability of the system component inventory are defined] are used to maintain the availability of the system component inventory.'),
('000414','draft','2009-09-18','DISA FSO','policy','Maintain the availability of the inventory of system components using organization-defined automated mechanisms.','CM-08(02)','N/A','Determine if: - [CM-08(02)_ODP[01]; automated mechanisms used to maintain the currency of the system component inventory are defined] are used to maintain the currency of the system component inventory. - [CM-08(02)_ODP[02]; automated mechanisms used to maintain the completeness of the system component inventory are defined] are used to maintain the completeness of the system component inventory. - [CM-08(02)_ODP[03]; automated mechanisms used to maintain the accuracy of the system component inventory are defined] are used to maintain the accuracy of the system component inventory. - [CM-08(02)_ODP[04]; automated mechanisms used to maintain the availability of the system component inventory are defined] are used to maintain the availability of the system component inventory.'),
('000415','draft','2009-09-18','DISA FSO','policy','Defines the frequency of employing automated mechanisms to detect the presence of unauthorized hardware, software, and firmware components within the system.','CM-08(03)(a)','N/A','Determine if: - the presence of unauthorized hardware within the system is detected using [CM-08(03)_ODP[01]; automated mechanisms used to detect the presence of unauthorized hardware within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined]. - the presence of unauthorized software within the system is detected using [CM-08(03)_ODP[02]; automated mechanisms used to detect the presence of unauthorized software within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined;]. - the presence of unauthorized firmware within the system is detected using [CM-08(03)_ODP[03]; automated mechanisms used to detect the presence of unauthorized firmware within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined].'),
('000416','draft','2009-09-18','DISA FSO','policy','Detect the presence of unauthorized hardware, software, and firmware components within the system using organization-defined automated mechanisms, on an organization-defined frequency.','CM-08(03)(a)','N/A','Determine if: - the presence of unauthorized hardware within the system is detected using [CM-08(03)_ODP[01]; automated mechanisms used to detect the presence of unauthorized hardware within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined]. - the presence of unauthorized software within the system is detected using [CM-08(03)_ODP[02]; automated mechanisms used to detect the presence of unauthorized software within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined;]. - the presence of unauthorized firmware within the system is detected using [CM-08(03)_ODP[03]; automated mechanisms used to detect the presence of unauthorized firmware within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined].'),
('000418','draft','2009-09-18','DISA FSO','policy','Include in the system component inventory information, a means for identifying by name, position, and/or role, individuals responsible and accountable for administering those components.','CM-08(04)','N/A','Determine if individuals responsible and accountable for administering system components are identified by [CM-08(04)_ODP; one or more of the following PARAMETER VALUES is/are selected: {name; position; role}] in the system component inventory.'),
('000420','draft','2009-09-18','DISA FSO','policy','Include assessed component configurations and any approved deviations to current deployed configurations in the system component inventory.','CM-08(06)','N/A','Determine if: - assessed component configurations are included in the system component inventory. - any approved deviations to current deployed configurations are included in the system component inventory.'),
('000423','draft','2009-09-18','DISA FSO','policy','Implement a configuration management plan for the system that addresses roles, responsibilities, and configuration management processes and procedures.','CM-09a.','N/A','Determine if: - the configuration management plan addresses roles. - the configuration management plan addresses responsibilities. - the configuration management plan addresses configuration management processes and procedures.'),
('000426','draft','2009-09-18','DISA FSO','policy','Implement a configuration management plan for the system that defines the configuration items for the system.','CM-09c.','N/A','Determine if: - the configuration management plan defines the configuration items for the system. - the configuration management plan places the configuration items under configuration management.'),
('000436','draft','2009-09-18','DISA FSO','policy','Assign responsibility for developing the configuration management process to organizational personnel that are not directly involved in system development.','CM-09(01)','N/A','Determine if the responsibility for developing the configuration management process is assigned to organizational personnel who are not directly involved in system development.'),
('000437','draft','2009-09-18','DISA FSO','policy','Defines the frequency with which to review and update the current contingency planning policy.','CP-01c.01','N/A','Determine if: - the current contingency planning policy is reviewed and updated [CP-01_ODP[05]; the frequency at which the current contingency planning policy is reviewed and updated is defined]. - the current contingency planning policy is reviewed and updated following [CP-01_ODP[06]; events that would require the current contingency planning policy to be reviewed and updated are defined].'),
('000438','draft','2009-09-18','DISA FSO','policy','Develop and document an organizational-level; mission/business process-level; and/or system-level contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','CP-01a.01(a)','N/A','Determine if: - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses purpose. - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses scope. - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses roles. - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses responsibilities. - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses management commitment. - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses coordination among organizational entities. - the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy addresses compliance.'),
('000439','draft','2009-09-18','DISA FSO','policy','Disseminate an organizational-level; mission/business process-level; and/or system-level contingency planning policy to organization-defined personnel or roles.','CP-01a.','N/A','Determine if: - a contingency planning policy is developed and documented. - the contingency planning policy is disseminated to [CP-01_ODP[01]; personnel or roles to whom the contingency planning policy is to be disseminated is/are defined].'),
('000440','draft','2009-09-18','DISA FSO','policy','Review and update the current contingency planning policy in accordance with an organization-defined frequency.','CP-01c.01','N/A','Determine if: - the current contingency planning policy is reviewed and updated [CP-01_ODP[05]; the frequency at which the current contingency planning policy is reviewed and updated is defined]. - the current contingency planning policy is reviewed and updated following [CP-01_ODP[06]; events that would require the current contingency planning policy to be reviewed and updated are defined].'),
('000441','draft','2009-09-18','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls.','CP-01a.02','N/A','Determine if: - contingency planning procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls are developed and documented. - the contingency planning procedures are disseminated to [CP-01_ODP[02]; personnel or roles to whom the contingency planning procedures are to be disseminated is/are defined].'),
('000443','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that identifies essential missions.','CP-02a.01','N/A','Determine if a contingency plan for the system is developed that identifies essential mission and business functions and associated contingency requirements.'),
('000444','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that identifies essential business functions.','CP-02a.01','N/A','Determine if a contingency plan for the system is developed that identifies essential mission and business functions and associated contingency requirements.'),
('000445','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that identifies associated contingency requirements.','CP-02a.01','N/A','Determine if a contingency plan for the system is developed that identifies essential mission and business functions and associated contingency requirements.'),
('000446','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that provides recovery objectives.','CP-02a.02','N/A','Determine if: - a contingency plan for the system is developed that provides recovery objectives. - a contingency plan for the system is developed that provides restoration priorities. - a contingency plan for the system is developed that provides metrics.'),
('000447','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that provides restoration priorities.','CP-02a.02','N/A','Determine if: - a contingency plan for the system is developed that provides recovery objectives. - a contingency plan for the system is developed that provides restoration priorities. - a contingency plan for the system is developed that provides metrics.'),
('000448','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that provides metrics.','CP-02a.02','N/A','Determine if: - a contingency plan for the system is developed that provides recovery objectives. - a contingency plan for the system is developed that provides restoration priorities. - a contingency plan for the system is developed that provides metrics.'),
('000449','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that addresses contingency roles, responsibilities, assigned individuals with contact information.','CP-02a.03','N/A','Determine if: - a contingency plan for the system is developed that addresses contingency roles. - a contingency plan for the system is developed that addresses contingency responsibilities. - a contingency plan for the system is developed that addresses assigned individuals with contact information.'),
('000456','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that addresses eventual, full system restoration without deterioration of the controls originally planned and implemented.','CP-02a.05','N/A','Determine if a contingency plan for the system is developed that addresses eventual, full-system restoration without deterioration of the controls originally planned and implemented.'),
('000457','draft','2009-09-18','DISA FSO','policy','Develop a contingency plan for the system that is reviewed and approved by organization-defined personnel or roles.','CP-02a.07','N/A','Determine if: - a contingency plan for the system is developed that is reviewed by [CP-02_ODP[01]; personnel or roles to review a contingency plan is/are defined]. - a contingency plan for the system is developed that is approved by [CP-02_ODP[02]; personnel or roles to approve a contingency plan is/are defined].'),
('000458','draft','2009-09-18','DISA FSO','policy','Defines the key contingency personnel (identified by name and/or by role) and organizational elements designated to receive copies of the contingency plan.','CP-02b.','N/A','Determine if: - copies of the contingency plan are distributed to [CP-02_ODP[03]; key contingency personnel (identified by name and/or by role) to whom copies of the contingency plan are distributed are defined]. - copies of the contingency plan are distributed to [CP-02_ODP[04]; key contingency organizational elements to which copies of the contingency plan are distributed are defined].'),
('000459','draft','2009-09-18','DISA FSO','policy','Distributes copies of the contingency plan to an organization-defined list of key contingency personnel (identified by name and/or by role) and organizational elements.','CP-02b.','N/A','Determine if: - copies of the contingency plan are distributed to [CP-02_ODP[03]; key contingency personnel (identified by name and/or by role) to whom copies of the contingency plan are distributed are defined]. - copies of the contingency plan are distributed to [CP-02_ODP[04]; key contingency organizational elements to which copies of the contingency plan are distributed are defined].'),
('000460','draft','2009-09-18','DISA FSO','policy','Coordinate contingency planning activities with incident handling activities.','CP-02c.','N/A','Determine if contingency planning activities are coordinated with incident handling activities.'),
('000461','draft','2009-09-18','DISA FSO','policy','Defines the frequency with which to review the contingency plan for the system.','CP-02d.','N/A','Determine if the contingency plan for the system is reviewed [CP-02_ODP[05]; frequency of contingency plan review is defined].'),
('000462','draft','2009-09-18','DISA FSO','policy','Reviews the contingency plan for the system in accordance with organization-defined frequency.','CP-02d.','N/A','Determine if the contingency plan for the system is reviewed [CP-02_ODP[05]; frequency of contingency plan review is defined].'),
('000463','draft','2009-09-18','DISA FSO','policy','Updates the contingency plan to address changes to the organization.','CP-02e.','N/A','Determine if: - the contingency plan is updated to address changes to the organization, system, or environment of operation. - the contingency plan is updated to address problems encountered during contingency plan implementation, execution, or testing.'),
('000464','draft','2009-09-18','DISA FSO','policy','Updates the contingency plan to address changes to the system.','CP-02e.','N/A','Determine if: - the contingency plan is updated to address changes to the organization, system, or environment of operation. - the contingency plan is updated to address problems encountered during contingency plan implementation, execution, or testing.'),
('000465','draft','2009-09-18','DISA FSO','policy','Updates the contingency plan to address changes to the environment of operation.','CP-02e.','N/A','Determine if: - the contingency plan is updated to address changes to the organization, system, or environment of operation. - the contingency plan is updated to address problems encountered during contingency plan implementation, execution, or testing.'),
('000466','draft','2009-09-18','DISA FSO','policy','Updates the contingency plan to address problems encountered during contingency plan implementation, execution, or testing.','CP-02e.','N/A','Determine if: - the contingency plan is updated to address changes to the organization, system, or environment of operation. - the contingency plan is updated to address problems encountered during contingency plan implementation, execution, or testing.'),
('000468','draft','2009-09-18','DISA FSO','policy','Communicates contingency plan changes to an organization-defined list of key contingency personnel (identified by name and/or by role) and organizational elements.','CP-02f.','N/A','Determine if: - contingency plan changes are communicated to [CP-02_ODP[06]; key contingency personnel (identified by name and/or by role) to communicate changes to are defined]. - contingency plan changes are communicated to [CP-02_ODP[07]; key contingency organizational elements to communicate changes to are defined].'),
('000469','draft','2009-09-18','DISA FSO','policy','Coordinate contingency plan development with organizational elements responsible for related plans.','CP-02(01)','N/A','Determine if contingency plan development is coordinated with organizational elements responsible for related plans.'),
('000470','draft','2009-09-18','DISA FSO','policy','Conduct capacity planning so that necessary capacity for information processing exists during contingency operations.','CP-02(02)','N/A','Determine if: - capacity planning is conducted so that the necessary capacity exists during contingency operations for information processing. - capacity planning is conducted so that the necessary capacity exists during contingency operations for telecommunications. - capacity planning is conducted so that the necessary capacity exists during contingency operations for environmental support.'),
('000471','draft','2009-09-18','DISA FSO','policy','Conduct capacity planning so that necessary capacity for telecommunications exists during contingency operations.','CP-02(02)','N/A','Determine if: - capacity planning is conducted so that the necessary capacity exists during contingency operations for information processing. - capacity planning is conducted so that the necessary capacity exists during contingency operations for telecommunications. - capacity planning is conducted so that the necessary capacity exists during contingency operations for environmental support.'),
('000472','draft','2009-09-18','DISA FSO','policy','Conduct capacity planning so that necessary capacity for environmental support exists during contingency operations.','CP-02(02)','N/A','Determine if: - capacity planning is conducted so that the necessary capacity exists during contingency operations for information processing. - capacity planning is conducted so that the necessary capacity exists during contingency operations for telecommunications. - capacity planning is conducted so that the necessary capacity exists during contingency operations for environmental support.'),
('000473','draft','2009-09-18','DISA FSO','policy','Defines the time period for planning the resumption of essential missions as a result of contingency plan activation.','CP-02(03)','N/A','Determine if the resumption of [CP-02(03)_ODP[01]; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions are planned for within [CP-02(03)_ODP[02]; the contingency plan activation time period within which to resume mission and business functions is defined] of contingency plan activation.'),
('000474','draft','2009-09-18','DISA FSO','policy','Defines the time period for planning the resumption of essential business functions as a result of contingency plan activation.','CP-02(03)','N/A','Determine if the resumption of [CP-02(03)_ODP[01]; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions are planned for within [CP-02(03)_ODP[02]; the contingency plan activation time period within which to resume mission and business functions is defined] of contingency plan activation.'),
('000475','draft','2009-09-18','DISA FSO','policy','Plan for the resumption of all or essential mission functions within the organization-defined time period of contingency plan activation.','CP-02(03)','N/A','Determine if the resumption of [CP-02(03)_ODP[01]; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions are planned for within [CP-02(03)_ODP[02]; the contingency plan activation time period within which to resume mission and business functions is defined] of contingency plan activation.'),
('000476','draft','2009-09-18','DISA FSO','policy','Plan for the resumption of all or essential business functions within the organization-defined time period of contingency plan activation.','CP-02(03)','N/A','Determine if the resumption of [CP-02(03)_ODP[01]; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions are planned for within [CP-02(03)_ODP[02]; the contingency plan activation time period within which to resume mission and business functions is defined] of contingency plan activation.'),
('000481','draft','2009-09-18','DISA FSO','policy','Plan for the continuance of all or essential missions with little or no loss of operational continuity.','CP-02(05)','N/A','Determine if: - the continuance of [CP-02(05)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions with minimal or no loss of operational continuity is planned for. - continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('000482','draft','2009-09-18','DISA FSO','policy','Plan for the continuance of all or essential business functions with little or no loss of operational continuity.','CP-02(05)','N/A','Determine if: - the continuance of [CP-02(05)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions with minimal or no loss of operational continuity is planned for. - continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('000483','draft','2009-09-18','DISA FSO','policy','Plan for the transfer of all or essential mission functions to alternate processing and/or storage sites with minimal or no loss of operational continuity.','CP-02(06)','N/A','Determine if: - the transfer of [CP-02(06)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity is planned for. - operational continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('000484','draft','2009-09-18','DISA FSO','policy','Plan for the transfer of all or essential business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity.','CP-02(06)','N/A','Determine if: - the transfer of [CP-02(06)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity is planned for. - operational continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('000485','draft','2009-09-21','DISA FSO','policy','Defines the frequency of contingency training to system users.','CP-03a.03','N/A','Determine if contingency training is provided to system users consistent with assigned roles and responsibilities [CP-03_ODP[02]; frequency at which to provide training to system users with a contingency role or responsibility is defined] thereafter.'),
('000486','draft','2009-09-21','DISA FSO','policy','Provide contingency training to system users consistent with assigned roles and responsibilities within an organization-defined time period of assuming a contingency role or responsibility.','CP-03a.01','N/A','Determine if contingency training is provided to system users consistent with assigned roles and responsibilities within [CP-03_ODP[01]; the time period within which to provide contingency training after assuming a contingency role or responsibility is defined] of assuming a contingency role or responsibility.'),
('000487','draft','2009-09-21','DISA FSO','policy','Provide contingency training to system users consistent with assigned roles and responsibilities in accordance with organization-defined frequency.','CP-03a.03','N/A','Determine if contingency training is provided to system users consistent with assigned roles and responsibilities [CP-03_ODP[02]; frequency at which to provide training to system users with a contingency role or responsibility is defined] thereafter.'),
('000488','draft','2009-09-21','DISA FSO','policy','Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations.','CP-03(01)','N/A','Determine if simulated events are incorporated into contingency training to facilitate effective response by personnel in crisis situations.'),
('000489','draft','2009-09-21','DISA FSO','policy','Employ mechanisms used in operations to provide a more thorough and realistic contingency training environment.','CP-03(02)','N/A','Determine if mechanisms used in operations are employed to provide a more thorough and realistic contingency training environment.'),
('000490','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to test the contingency plan for the system.','CP-04a.','N/A','Determine if: - the contingency plan for the system is tested [CP-04_ODP[01]; frequency of testing the contingency plan for the system is defined]. - [CP-04_ODP[02]; tests for determining the effectiveness of the contingency plan are defined] are used to determine the effectiveness of the plan. - [CP-04_ODP[03]; tests for determining readiness to execute the contingency plan are defined] are used to determine the readiness to execute the plan.'),
('000492','draft','2009-09-21','DISA FSO','policy','Defines the contingency plan tests to be conducted for the system.','CP-04a.','N/A','Determine if: - the contingency plan for the system is tested [CP-04_ODP[01]; frequency of testing the contingency plan for the system is defined]. - [CP-04_ODP[02]; tests for determining the effectiveness of the contingency plan are defined] are used to determine the effectiveness of the plan. - [CP-04_ODP[03]; tests for determining readiness to execute the contingency plan are defined] are used to determine the readiness to execute the plan.'),
('000494','draft','2009-09-21','DISA FSO','policy','Test the contingency plan for the system in accordance with organization-defined frequency using organization-defined tests to determine the effectiveness of the plan and the organizational readiness to execute the plan.','CP-04a.','N/A','Determine if: - the contingency plan for the system is tested [CP-04_ODP[01]; frequency of testing the contingency plan for the system is defined]. - [CP-04_ODP[02]; tests for determining the effectiveness of the contingency plan are defined] are used to determine the effectiveness of the plan. - [CP-04_ODP[03]; tests for determining readiness to execute the contingency plan are defined] are used to determine the readiness to execute the plan.'),
('000496','draft','2009-09-21','DISA FSO','policy','Review the contingency plan test results.','CP-04b.','N/A','Determine if the contingency plan test results are reviewed.'),
('000497','draft','2009-09-21','DISA FSO','policy','Initiate corrective actions, if needed, after reviewing the contingency plan test results.','CP-04c.','N/A','Determine if corrective actions are initiated, if needed.'),
('000498','draft','2009-09-21','DISA FSO','policy','Coordinate contingency plan testing with organizational elements responsible for related plans.','CP-04(01)','N/A','Determine if contingency plan testing is coordinated with organizational elements responsible for related plans.'),
('000500','draft','2009-09-21','DISA FSO','policy','Test the contingency plan at the alternate processing site to familiarize contingency personnel with the facility and available resources.','CP-04(02)(a)','N/A','Determine if the contingency plan is tested at the alternate processing site to familiarize contingency personnel with the facility and available resources.'),
('000502','draft','2009-09-21','DISA FSO','policy','Test the contingency plan using organization-defined automated mechanisms.','CP-04(03)','N/A','Determine if the contingency plan is tested using [CP-04(03)_ODP; automated mechanisms for contingency plan testing are defined].'),
('000504','draft','2009-09-21','DISA FSO','policy','Include a full recovery and reconstitution of the system to a known state as part of contingency plan testing.','CP-04(04)','N/A','Determine if: - a full recovery of the system to a known state is included as part of contingency plan testing. - a full reconstitution of the system to a known state is included as part of contingency plan testing.'),
('000505','draft','2009-09-21','DISA FSO','policy','Establish an alternate storage site, including necessary agreements to permit the storage of system backup information.','CP-06a.','N/A','Determine if: - an alternate storage site is established. - establishment of the alternate storage site includes necessary agreements to permit the storage and retrieval of system backup information.'),
('000507','draft','2009-09-21','DISA FSO','policy','Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats.','CP-06(01)','N/A','Determine if an alternate storage site that is sufficiently separated from the primary storage site is identified to reduce susceptibility to the same threats.'),
('000508','draft','2009-09-21','DISA FSO','policy','Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives.','CP-06(02)','N/A','Determine if: - the alternate storage site is configured to facilitate recovery operations in accordance with recovery time objectives. - the alternate storage site is configured to facilitate recovery operations in accordance with recovery point objectives.'),
('000509','draft','2009-09-21','DISA FSO','policy','Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster.','CP-06(03)','N/A','Determine if: - potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster are identified. - explicit mitigation actions to address identified accessibility problems are outlined.'),
('000510','draft','2009-09-21','DISA FSO','policy','Defines the time-period consistent with recovery time and recovery point objectives for essential missions/business functions to permit the transfer and resumption of organization-defined system operations at an alternate processing site when the primary processing capabilities are unavailable.','CP-07a.','N/A','Determine if an alternate processing site, including necessary agreements to permit the transfer and resumption of [CP-07_ODP[01]; system operations for essential mission and business functions are defined] for essential mission and business functions, is established within [CP-07_ODP[02]; time period consistent with recovery time and recovery point objectives is defined] when the primary processing capabilities are unavailable.'),
('000513','draft','2009-09-21','DISA FSO','policy','Establish an alternate processing site including necessary agreements to permit the transfer and resumption of organization-defined system operations for essential mission functions within an organization-defined time period consistent with recovery time and recovery point objectives when the primary processing capabilities are unavailable.','CP-07a.','N/A','Determine if an alternate processing site, including necessary agreements to permit the transfer and resumption of [CP-07_ODP[01]; system operations for essential mission and business functions are defined] for essential mission and business functions, is established within [CP-07_ODP[02]; time period consistent with recovery time and recovery point objectives is defined] when the primary processing capabilities are unavailable.'),
('000514','draft','2009-09-21','DISA FSO','policy','Establish an alternate processing site including necessary agreements to permit the transfer and resumption of organization-defined system operations for essential business functions within an organization-defined time period consistent with recovery time and recovery point objectives when the primary processing capabilities are unavailable.','CP-07a.','N/A','Determine if an alternate processing site, including necessary agreements to permit the transfer and resumption of [CP-07_ODP[01]; system operations for essential mission and business functions are defined] for essential mission and business functions, is established within [CP-07_ODP[02]; time period consistent with recovery time and recovery point objectives is defined] when the primary processing capabilities are unavailable.'),
('000515','draft','2009-09-21','DISA FSO','policy','Make available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site within the organization-defined time period for transfer and resumption.','CP-07b.','N/A','Determine if: - the equipment and supplies required to transfer operations are made available at the alternate processing site or if contracts are in place to support delivery to the site within [CP-07_ODP[02]; time period consistent with recovery time and recovery point objectives is defined] for transfer. - the equipment and supplies required to resume operations are made available at the alternate processing site or if contracts are in place to support delivery to the site within [CP-07_ODP[02]; time period consistent with recovery time and recovery point objectives is defined] for resumption.'),
('000516','draft','2009-09-21','DISA FSO','policy','Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats.','CP-07(01)','N/A','Determine if an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats is identified.'),
('000517','draft','2009-09-21','DISA FSO','policy','Identify potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster.','CP-07(02)','N/A','Determine if: - potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster are identified. - explicit mitigation actions to address identified accessibility problems are outlined.'),
('000518','draft','2009-09-21','DISA FSO','policy','Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).','CP-07(03)','N/A','Determine if alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed.'),
('000519','draft','2009-09-21','DISA FSO','policy','Prepare the alternate processing site so that the site can serve as the operational site supporting essential missions.','CP-07(04)','N/A','Determine if the alternate processing site is prepared so that the site can serve as the operational site supporting essential mission and business functions.'),
('000520','draft','2009-09-21','DISA FSO','policy','Prepare the alternate processing site so that the site can serve as the operational site supporting essential business functions.','CP-07(04)','N/A','Determine if the alternate processing site is prepared so that the site can serve as the operational site supporting essential mission and business functions.'),
('000521','draft','2009-09-21','DISA FSO','policy','Provide controls at the alternate processing site that are equivalent to those at the primary site.','CP-07c.','N/A','Determine if controls provided at the alternate processing site are equivalent to those at the primary site.'),
('000522','draft','2009-09-21','DISA FSO','policy','Defines the time-period within which to permit the resumption of organization-defined system operations for essential mission functions when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-08','N/A','Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [CP-08_ODP[01]; system operations to be resumed for essential mission and business functions are defined], are established for essential mission and business functions within [CP-08_ODP[02]; time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.'),
('000523','draft','2009-09-21','DISA FSO','policy','Defines the time-period within which to permit the resumption of organization-defined system operations for essential business functions when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-08','N/A','Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [CP-08_ODP[01]; system operations to be resumed for essential mission and business functions are defined], are established for essential mission and business functions within [CP-08_ODP[02]; time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.'),
('000524','draft','2009-09-21','DISA FSO','policy','Establish alternate telecommunication services, including necessary agreements to permit the resumption of organization-defined system operations for essential mission functions within an organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-08','N/A','Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [CP-08_ODP[01]; system operations to be resumed for essential mission and business functions are defined], are established for essential mission and business functions within [CP-08_ODP[02]; time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.'),
('000525','draft','2009-09-21','DISA FSO','policy','Establish alternate telecommunication services, including necessary agreements to permit the resumption of organization-defined system operations for essential business functions within an organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-08','N/A','Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [CP-08_ODP[01]; system operations to be resumed for essential mission and business functions are defined], are established for essential mission and business functions within [CP-08_ODP[02]; time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.'),
('000526','draft','2009-09-21','DISA FSO','policy','Develop primary telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).','CP-08(01)(a)','N/A','Determine if: - primary telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed. - alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed.'),
('000527','draft','2009-09-21','DISA FSO','policy','Develop alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).','CP-08(01)(a)','N/A','Determine if: - primary telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed. - alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed.'),
('000530','draft','2009-09-21','DISA FSO','policy','Obtain alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services.','CP-08(02)','N/A','Determine if alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services are obtained.'),
('000531','draft','2009-09-21','DISA FSO','policy','Obtain alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats.','CP-08(03)','N/A','Determine if alternate telecommunications services from providers that are separated from primary service providers are obtained to reduce susceptibility to the same threats.'),
('000532','draft','2009-09-21','DISA FSO','policy','Require primary telecommunications service providers to have contingency plans.','CP-08(04)(a)','N/A','Determine if: - primary telecommunications service providers are required to have contingency plans. - alternate telecommunications service providers are required to have contingency plans.'),
('000533','draft','2009-09-21','DISA FSO','policy','Require alternate telecommunications service providers to have contingency plans.','CP-08(04)(a)','N/A','Determine if: - primary telecommunications service providers are required to have contingency plans. - alternate telecommunications service providers are required to have contingency plans.'),
('000534','draft','2009-09-21','DISA FSO','policy','Defines the frequency of conducting user-level information backups to support recovery time objectives and recovery point objectives.','CP-09a.','N/A','Determine if backups of user-level information contained in [CP-09_ODP[01]; system components for which to conduct backups of user-level information is defined] are conducted [CP-09_ODP[02]; frequency at which to conduct backups of user-level information consistent with recovery time and recovery point objectives is defined].'),
('000535','draft','2009-09-21','DISA FSO','policy','Conduct backups of user-level information contained in organization-defined system components per organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-09a.','N/A','Determine if backups of user-level information contained in [CP-09_ODP[01]; system components for which to conduct backups of user-level information is defined] are conducted [CP-09_ODP[02]; frequency at which to conduct backups of user-level information consistent with recovery time and recovery point objectives is defined].'),
('000536','draft','2009-09-21','DISA FSO','policy','Defines the frequency of conducting system-level information backups to support recovery time objectives and recovery point objectives.','CP-09b.','N/A','Determine if backups of system-level information contained in the system are conducted [CP-09_ODP[03]; frequency at which to conduct backups of system-level information consistent with recovery time and recovery point objectives is defined].'),
('000537','draft','2009-09-21','DISA FSO','policy','Conduct backups of system-level information contained in the system per organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-09b.','N/A','Determine if backups of system-level information contained in the system are conducted [CP-09_ODP[03]; frequency at which to conduct backups of system-level information consistent with recovery time and recovery point objectives is defined].'),
('000538','draft','2009-09-21','DISA FSO','policy','Defines the frequency of conducting system documentation backups, including security-related documentation, to support recovery time objectives and recovery point objectives.','CP-09c.','N/A','Determine if backups of system documentation, including security- and privacy-related documentation are conducted [CP-09_ODP[04]; frequency at which to conduct backups of system documentation consistent with recovery time and recovery point objectives is defined].'),
('000539','draft','2009-09-21','DISA FSO','policy','Conduct backups of system documentation, including security-related documentation, per an organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-09c.','N/A','Determine if backups of system documentation, including security- and privacy-related documentation are conducted [CP-09_ODP[04]; frequency at which to conduct backups of system documentation consistent with recovery time and recovery point objectives is defined].'),
('000541','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to test backup information to verify media reliability and information integrity.','CP-09(01)','N/A','Determine if: - backup information is tested [CP-09(01)_ODP[01]; frequency at which to test backup information for media reliability is defined] to verify media reliability. - backup information is tested [CP-09(01)_ODP[02]; frequency at which to test backup information for information integrity is defined] to verify information integrity.'),
('000542','draft','2009-09-21','DISA FSO','policy','Test backup information per an organization-defined frequency to verify media reliability and information integrity.','CP-09(01)','N/A','Determine if: - backup information is tested [CP-09(01)_ODP[01]; frequency at which to test backup information for media reliability is defined] to verify media reliability. - backup information is tested [CP-09(01)_ODP[02]; frequency at which to test backup information for information integrity is defined] to verify information integrity.'),
('000543','draft','2009-09-21','DISA FSO','policy','Use a sample of backup information in the restoration of selected system functions as part of contingency plan testing.','CP-09(02)','N/A','Determine if a sample of backup information in the restoration of selected system functions is used as part of contingency plan testing.'),
('000547','draft','2009-09-21','DISA FSO','policy','Defines the time-period and transfer rate of the system backup information to the alternate storage site consistent with the recovery time and recovery point objectives.','CP-09(05)','N/A','Determine if: - system backup information is transferred to the alternate storage site for [CP-09(05)_ODP[01]; time period consistent with recovery time and recovery point objectives is defined]. - system backup information is transferred to the alternate storage site [CP-09(05)_ODP[02]; transfer rate consistent with recovery time and recovery point objectives is defined].'),
('000548','draft','2009-09-21','DISA FSO','policy','Transfer system backup information to the alternate storage site in accordance with the organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives.','CP-09(05)','N/A','Determine if: - system backup information is transferred to the alternate storage site for [CP-09(05)_ODP[01]; time period consistent with recovery time and recovery point objectives is defined]. - system backup information is transferred to the alternate storage site [CP-09(05)_ODP[02]; transfer rate consistent with recovery time and recovery point objectives is defined].'),
('000549','draft','2009-09-21','DISA FSO','policy','Maintain a redundant secondary system that is not collocated with the primary system.','CP-09(06)','N/A','Determine if: - system backup is conducted by maintaining a redundant secondary system that is not collocated with the primary system. - system backup is conducted by maintaining a redundant secondary system that can be activated without loss of information or disruption to operations.'),
('000553','draft','2009-09-21','DISA FSO','policy','Implement transaction recovery for systems that are transaction-based.','CP-10(02)','N/A','Determine if transaction recovery is implemented for systems that are transaction-based.'),
('000556','draft','2009-09-21','DISA FSO','policy','Defines restoration time periods within which to restore system components from configuration-controlled and integrity-protected information representing a known, operational state for the components.','CP-10(04)','N/A','Determine if the capability to restore system components within [CP-10(04)_ODP; restoration time period within which to restore system components to a known, operational state is defined] from configuration-controlled and integrity-protected information representing a known, operational state for the components is provided.'),
('000557','draft','2009-09-21','DISA FSO','policy','Provide the capability to restore information system components within organization-defined restoration time periods from configuration-controlled and integrity-protected information representing a known, operational state for the components.','CP-10(04)','N/A','Determine if the capability to restore system components within [CP-10(04)_ODP; restoration time period within which to restore system components to a known, operational state is defined] from configuration-controlled and integrity-protected information representing a known, operational state for the components is provided.'),
('000558','draft','2009-09-21','DISA FSO','policy','Defines the real-time or near-real-time failover capability to be provided for the system.','SI-13(05)','N/A','Determine if [SI-13(05)_ODP[01]; one of the following PARAMETER VALUES is selected: {real-time; near real-time}] [SI-13(05)_ODP[02]; a failover capability for the system has been defined] is provided for the system.'),
('000559','draft','2009-09-21','DISA FSO','policy','Provide real-time or near-real-time organization-defined failover capability for the system.','SI-13(05)','N/A','Determine if [SI-13(05)_ODP[01]; one of the following PARAMETER VALUES is selected: {real-time; near real-time}] [SI-13(05)_ODP[02]; a failover capability for the system has been defined] is provided for the system.'),
('000563','draft','2009-09-21','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and or system-level planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PL-01a.01(a)','N/A','Determine if: - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses purpose. - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses scope. - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses roles. - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses responsibilities. - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses management commitment. - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses coordination among organizational entities. - the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy addresses compliance.'),
('000564','draft','2009-09-21','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; and or system-level planning policy to organization-defined personnel or roles.','PL-01a.','N/A','Determine if: - a planning policy is developed and documented. - the planning policy is disseminated to [PL-01_ODP[01]; personnel or roles to whom the planning policy is to be disseminated is/are defined].'),
('000566','draft','2009-09-21','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the planning policy and associated planning controls.','PL-01a.02','N/A','Determine if: - planning procedures to facilitate the implementation of the planning policy and associated planning controls are developed and documented. - the planning procedures are disseminated to [PL-01_ODP[02]; personnel or roles to whom the planning procedures are to be disseminated is/are defined].'),
('000567','draft','2009-09-21','DISA FSO','policy','Disseminates planning procedures to organization-defined personnel or roles.','PL-01a.02','N/A','Determine if: - planning procedures to facilitate the implementation of the planning policy and associated planning controls are developed and documented. - the planning procedures are disseminated to [PL-01_ODP[02]; personnel or roles to whom the planning procedures are to be disseminated is/are defined].'),
('000568','draft','2009-09-21','DISA FSO','policy','Review and update the current planning procedures in accordance with organization-defined frequency.','PL-01c.02','N/A','Determine if: - the current planning procedures are reviewed and updated [PL-01_ODP[07]; the frequency with which the current planning procedures are reviewed and updated is defined]. - the current planning procedures are reviewed and updated following [PL-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('000571','draft','2009-09-21','DISA FSO','policy','Develop security and privacy plans for the system that are reviewed and approved by the authorizing official or designated representative prior to plan implementation.','PL-02a.15','N/A','Determine if: - a security plan for the system is developed that is reviewed and approved by the authorizing official or designated representative prior to plan implementation. - a privacy plan for the system is developed that is reviewed and approved by the authorizing official or designated representative prior to plan implementation.'),
('000572','draft','2009-09-21','DISA FSO','policy','Defines the frequency for reviewing the plans for the system.','PL-02c.','N/A','Determine if plans are reviewed [PL-02_ODP[03]; frequency to review system security and privacy plans is defined].'),
('000573','draft','2009-09-21','DISA FSO','policy','Review the plans in accordance with organization-defined frequency.','PL-02c.','N/A','Determine if plans are reviewed [PL-02_ODP[03]; frequency to review system security and privacy plans is defined].'),
('000574','draft','2009-09-21','DISA FSO','policy','Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments.','PL-02d.','N/A','Determine if: - plans are updated to address changes to the system and environment of operations. - plans are updated to address problems identified during the plan implementation. - plans are updated to address problems identified during control assessments.'),
('000577','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review and update the CONOPS.','PL-07b.','N/A','Determine if the CONOPS is reviewed and updated [PL-07_ODP; frequency for review and update of the Concept of Operations (CONOPS) is defined].'),
('000578','draft','2009-09-21','DISA FSO','policy','Review and update the CONOPS in accordance with organization-defined frequency.','PL-07b.','N/A','Determine if the CONOPS is reviewed and updated [PL-07_ODP; frequency for review and update of the Concept of Operations (CONOPS) is defined].'),
('000592','draft','2009-09-21','DISA FSO','policy','Establish the rules that describe their responsibilities and expected behavior, for information and system usage, for individuals requiring access to the system.','PL-04a.','N/A','Determine if: - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system. - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system.'),
('000593','draft','2009-09-21','DISA FSO','policy','Receive a documented acknowledgement from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the system.','PL-04b.','N/A','Determine if before authorizing access to information and the system, a documented acknowledgement from such individuals indicating that they have read, understand, and agree to abide by the rules of behavior is received.'),
('000594','draft','2009-09-21','DISA FSO','policy','Include in the rules of behavior, restrictions on the use of social media, social networking sites, and external sites/applications.','PL-04(01)(a)','N/A','Determine if the rules of behavior include restrictions on the use of social media, social networking sites, and external sites/applications.'),
('000595','draft','2009-09-21','DISA FSO','policy','Include in the rules of behavior, restrictions on posting organizational information on public websites.','PL-04(01)(b)','N/A','Determine if the rules of behavior include restrictions on posting organizational information on public websites.'),
('000601','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review and update the current system and services acquisition policy.','SA-01c.01','N/A','Determine if: - the system and services acquisition policy is reviewed and updated [SA-01_ODP[05]; the frequency at which the current system and services acquisition policy is reviewed and updated is defined]. - the current system and services acquisition policy is reviewed and updated following [SA-01_ODP[06]; events that would require the current system and services acquisition policy to be reviewed and updated are defined].'),
('000602','draft','2009-09-21','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SA-01a.01(a)','N/A','Determine if: - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses purpose. - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses scope. - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses roles. - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses responsibilities. - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses management commitment. - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses coordination among organizational entities. - the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy addresses compliance.'),
('000603','draft','2009-09-21','DISA FSO','policy','Disseminate to organization-defined personnel or roles an organization-level; mission/business process-level; and/or system-level system and services acquisition policy.','SA-01a.','N/A','Determine if: - a system and services acquisition policy is developed and documented. - the system and services acquisition policy is disseminated to [SA-01_ODP[01]; personnel or roles to whom the system and services acquisition policy is to be disseminated is/are defined].'),
('000604','draft','2009-09-21','DISA FSO','policy','Review and update the current system and services acquisition policy in accordance with organization-defined frequency.','SA-01c.01','N/A','Determine if: - the system and services acquisition policy is reviewed and updated [SA-01_ODP[05]; the frequency at which the current system and services acquisition policy is reviewed and updated is defined]. - the current system and services acquisition policy is reviewed and updated following [SA-01_ODP[06]; events that would require the current system and services acquisition policy to be reviewed and updated are defined].'),
('000605','draft','2009-09-21','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls.','SA-01a.02','N/A','Determine if: - system and services acquisition procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are developed and documented. - the system and services acquisition procedures are disseminated to [SA-01_ODP[02]; personnel or roles to whom the system and services acquisition procedures are to be disseminated is/are defined].'),
('000606','draft','2009-09-21','DISA FSO','policy','Disseminate to organization-defined personnel or roles procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls.','SA-01a.02','N/A','Determine if: - system and services acquisition procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are developed and documented. - the system and services acquisition procedures are disseminated to [SA-01_ODP[02]; personnel or roles to whom the system and services acquisition procedures are to be disseminated is/are defined].'),
('000607','draft','2009-09-21','DISA FSO','policy','Review and update the current system and services acquisition procedures in accordance with organization-defined frequency.','SA-01c.02','N/A','Determine if: - the current system and services acquisition procedures are reviewed and updated [SA-01_ODP[07]; the frequency at which the current system and services acquisition procedures are reviewed and updated is defined]. - the current system and services acquisition procedures are reviewed and updated following [SA-01_ODP[08]; events that would require the system and services acquisition procedures to be reviewed and updated are defined].'),
('000610','draft','2009-09-21','DISA FSO','policy','Determine the resources required to protect the system or system service as part of the organizational capital planning and investment control process.','SA-02b.','N/A','Determine if: - the resources required to protect the system or system service are determined and documented as part of the organizational capital planning and investment control process. - the resources required to protect the system or system service are allocated as part of the organizational capital planning and investment control process.'),
('000611','draft','2009-09-21','DISA FSO','policy','Document the resources required to protect the system or system service as part of the organizational capital planning and investment control process.','SA-02b.','N/A','Determine if: - the resources required to protect the system or system service are determined and documented as part of the organizational capital planning and investment control process. - the resources required to protect the system or system service are allocated as part of the organizational capital planning and investment control process.'),
('000612','draft','2009-09-21','DISA FSO','policy','Allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process.','SA-02b.','N/A','Determine if: - the resources required to protect the system or system service are determined and documented as part of the organizational capital planning and investment control process. - the resources required to protect the system or system service are allocated as part of the organizational capital planning and investment control process.'),
('000613','draft','2009-09-21','DISA FSO','policy','Establish a discrete line item for information security in organizational programming documentation.','SA-02c.','N/A','Determine if: - a discrete line item for information security is established in organizational programming and budgeting documentation. - a discrete line item for privacy is established in organizational programming and budgeting documentation.'),
('000614','draft','2009-09-21','DISA FSO','policy','Establish a discrete line item for information security in organizational budgeting documentation.','SA-02c.','N/A','Determine if: - a discrete line item for information security is established in organizational programming and budgeting documentation. - a discrete line item for privacy is established in organizational programming and budgeting documentation.'),
('000615','draft','2009-09-21','DISA FSO','policy','Manage the system using an organization-defined system development life cycle that incorporates information security considerations.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('000616','draft','2009-09-21','DISA FSO','policy','Define and document information system security roles and responsibilities throughout the system development life cycle.','SA-03b.','N/A','Determine if: - information security roles and responsibilities are defined and documented throughout the system development life cycle. - privacy roles and responsibilities are defined and documented throughout the system development life cycle.'),
('000618','draft','2009-09-21','DISA FSO','policy','Identify individuals having information system security roles and responsibilities.','SA-03c.','N/A','Determine if: - individuals with information security roles and responsibilities are identified. - individuals with privacy roles and responsibilities are identified.'),
('000623','draft','2009-09-21','DISA FSO','policy','Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented.','SA-04(01)','N/A','Determine if the developer of the system, system component, or system service is required to provide a description of the functional properties of the controls to be implemented.'),
('000631','draft','2009-09-21','DISA FSO','policy','Employ only government off-the-shelf or commercial off-the-shelf information assurance and information assurance-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted.','SA-04(06)(a)','N/A','Determine if only government off-the-shelf or commercial off-the-shelf information assurance and information assurance-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted are employed.'),
('000633','draft','2009-09-21','DISA FSO','policy','Ensure that government off-the-shelf or commercial-off-the-shelf information assurance and information assurance-enabled information technology products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures.','SA-04(06)(b)','N/A','Determine if these products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures.'),
('000634','draft','2009-09-21','DISA FSO','policy','Limit the use of commercially provided information assurance and information assurance-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists.','SA-04(07)(a)','N/A','Determine if the use of commercially provided information assurance and information assurance-enabled information technology products is limited to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists.'),
('000635','draft','2009-09-21','DISA FSO','policy','Require, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated or NSA-approved.','SA-04(07)(b)','N/A','Determine if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that cryptographic module is required to be FIPS-validated or NSA-approved.'),
('000642','draft','2009-09-21','DISA FSO','policy','Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent.','SA-05c.','N/A','Determine if: - attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent is documented. - after attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent, [SA-05_ODP[01]; actions to take when system, system component, or system service documentation is either unavailable or nonexistent are defined] are taken in response.'),
('000664','draft','2009-09-21','DISA FSO','policy','Apply organization-defined systems security and privacy engineering principles in the specification of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('000665','draft','2009-09-21','DISA FSO','policy','Apply organization-defined systems security and privacy engineering principles in the design of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('000666','draft','2009-09-21','DISA FSO','policy','Apply organization-defined systems security and privacy engineering principles in the development of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('000667','draft','2009-09-21','DISA FSO','policy','Apply organization-defined systems security and privacy engineering principles in the implementation of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('000668','draft','2009-09-21','DISA FSO','policy','Apply organization-defined systems security and privacy engineering principles in the modification of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('000669','draft','2009-09-21','DISA FSO','policy','Require that providers of external system services comply with organizational security requirements.',NULL,'N/A',NULL),
('000692','draft','2009-09-22','DISA FSO','policy','Require the developer of the system, system component, or system service to implement only organization-approved changes to the system, component, or service.','SA-10c.','N/A','Determine if the developer of the system, system component, or system service is required to implement only organization-approved changes to the system, component, or service.'),
('000694','draft','2009-09-22','DISA FSO','policy','Require the developer of the system, system component, or system service to document approved changes to the system, component, or service.','SA-10d.','N/A','Determine if: - the developer of the system, system component, or system service is required to document approved changes to the system, component, or service. - the developer of the system, system component, or system service is required to document the potential security impacts of approved changes. - the developer of the system, system component, or system service is required to document the potential privacy impacts of approved changes.'),
('000698','draft','2009-09-22','DISA FSO','policy','Require the developer of the system, system component, or system service to enable integrity verification of software and firmware components.','SA-10(01)','N/A','Determine if the developer of the system, system component, or system service is required to enable integrity verification of software and firmware components.'),
('000700','draft','2009-09-22','DISA FSO','policy','Provide an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team.','SA-10(02)','N/A','Determine if an alternate configuration management process has been provided using organizational personnel in the absence of a dedicated developer configuration management team.'),
('000757','draft','2009-09-17','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; and/or system-level identification and authentication policy to organization-defined personnel.','IA-01a.','N/A','Determine if: - an identification and authentication policy is developed and documented. - the identification and authentication policy is disseminated to [IA-01_ODP[01]; personnel or roles to whom the identification and authentication policy is to be disseminated are defined].'),
('000758','draft','2009-09-17','DISA FSO','policy','Review and update the current identification and authentication policy in accordance with the organization-defined frequency.','IA-01c.01','N/A','Determine if: - the current identification and authentication policy is reviewed and updated [IA-01_ODP[05]; the frequency at which the current identification and authentication policy is reviewed and updated is defined]. - the current identification and authentication policy is reviewed and updated following [IA-01_ODP[06]; events that would require the current identification and authentication policy to be reviewed and updated are defined].'),
('000759','draft','2009-09-17','DISA FSO','policy','Defines a frequency for reviewing and updating the identification and authentication policy.','IA-01c.01','N/A','Determine if: - the current identification and authentication policy is reviewed and updated [IA-01_ODP[05]; the frequency at which the current identification and authentication policy is reviewed and updated is defined]. - the current identification and authentication policy is reviewed and updated following [IA-01_ODP[06]; events that would require the current identification and authentication policy to be reviewed and updated are defined].'),
('000762','draft','2009-09-17','DISA FSO','policy','Review and update the current identification and authentication procedures in accordance with the organization-defined frequency.','IA-01c.02','N/A','Determine if: - the current identification and authentication procedures are reviewed and updated [IA-01_ODP[07]; the frequency at which the current identification and authentication procedures are reviewed and updated is defined]. - the current identification and authentication procedures are reviewed and updated following [IA-01_ODP[08]; events that would require identification and authentication procedures to be reviewed and updated are defined].'),
('000763','draft','2009-09-17','DISA FSO','policy','Defines a frequency for reviewing and updating the identification and authentication procedures.','IA-01c.02','N/A','Determine if: - the current identification and authentication procedures are reviewed and updated [IA-01_ODP[07]; the frequency at which the current identification and authentication procedures are reviewed and updated is defined]. - the current identification and authentication procedures are reviewed and updated following [IA-01_ODP[08]; events that would require identification and authentication procedures to be reviewed and updated are defined].'),
('000764','draft','2009-09-17','DISA FSO','technical','Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.','IA-02','N/A','Determine if: - organizational users are uniquely identified and authenticated. - the unique identification of authenticated organizational users is associated with processes acting on behalf of those users.'),
('000765','draft','2009-09-17','DISA FSO','technical','Implement multifactor authentication for access to privileged accounts.','IA-02(01)','N/A','Determine if multi-factor authentication is implemented for access to privileged accounts.'),
('000766','draft','2009-09-17','DISA FSO','technical','Implement multifactor authentication for access to non-privileged accounts.','IA-02(02)','N/A','Determine if multi-factor authentication for access to non-privileged accounts is implemented.'),
('000777','draft','2009-09-17','DISA FSO','policy','Defines devices and/or types of devices for which identification and authentication is required before establishing a connection.','IA-03','N/A','Determine if [IA-03_ODP[01]; devices and/or types of devices to be uniquely identified and authenticated before establishing a connection are defined] are uniquely identified and authenticated before establishing a [IA-03_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {local; remote; network}] connection.'),
('000778','draft','2009-09-17','DISA FSO','technical','Uniquely identify organization-defined devices and/or types of devices before establishing a local, remote, and/or network connection.','IA-03','N/A','Determine if [IA-03_ODP[01]; devices and/or types of devices to be uniquely identified and authenticated before establishing a connection are defined] are uniquely identified and authenticated before establishing a [IA-03_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {local; remote; network}] connection.'),
('000783','draft','2009-09-17','DISA FSO','technical','Audit lease information when assigned to a device.','IA-03(03)(b)','N/A','Determine if lease information is audited when assigned to a device.'),
('000796','draft','2009-09-17','DISA FSO','policy','Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts.','IA-04(01)','N/A','Determine if the use of system account identifiers that are the same as public identifiers is prohibited for individual accounts.'),
('000800','draft','2009-09-17','DISA FSO','policy','Defines characteristics for identifying individual status.','IA-04(04)','N/A','Determine if individual identifiers are managed by uniquely identifying each individual as [IA-04(04)_ODP; characteristics used to identify individual status is defined].'),
('000801','draft','2009-09-17','DISA FSO','policy','Manage individual identifiers by uniquely identifying each individual as organization-defined characteristics identifying individual status.','IA-04(04)','N/A','Determine if individual identifiers are managed by uniquely identifying each individual as [IA-04(04)_ODP; characteristics used to identify individual status is defined].'),
('000803','draft','2009-09-17','DISA FSO','technical','Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.','IA-07','N/A','Determine if mechanisms for authentication to a cryptographic module are implemented that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.'),
('000804','draft','2009-09-17','DISA FSO','technical','Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users.','IA-08','N/A','Determine if non-organizational users or processes acting on behalf of non-organizational users are uniquely identified and authenticated.'),
('000805','draft','2009-09-17','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','IR-01a.01(a)','N/A','Determine if: - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses purpose. - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses scope. - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses roles. - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses responsibilities. - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses management commitment. - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses coordination among organizational entities. - the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy addresses compliance.'),
('000806','draft','2009-09-17','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; and/or system-level incident response policy to organization-defined personnel or roles.','IR-01a.','N/A','Determine if: - an incident response policy is developed and documented. - the incident response policy is disseminated to [IR-01_ODP[01]; personnel or roles to whom the incident response policy is to be disseminated is/are defined].'),
('000807','draft','2009-09-17','DISA FSO','policy','Review and update the current incident response policy in accordance with organization-defined frequency.','IR-01c.01','N/A','Determine if: - the current incident response policy is reviewed and updated [IR-01_ODP[05]; the frequency at which the current incident response policy is reviewed and updated is defined]. - the current incident response policy is reviewed and updated following [IR-01_ODP[06]; events that would require the current incident response policy to be reviewed and updated are defined].'),
('000808','draft','2009-09-17','DISA FSO','policy','Defines the frequency with which to review and update the current incident response policy.','IR-01c.01','N/A','Determine if: - the current incident response policy is reviewed and updated [IR-01_ODP[05]; the frequency at which the current incident response policy is reviewed and updated is defined]. - the current incident response policy is reviewed and updated following [IR-01_ODP[06]; events that would require the current incident response policy to be reviewed and updated are defined].'),
('000809','draft','2009-09-17','DISA FSO','policy','Develop and document procedures to facilitate the implementation of incident response policy and associated incident response controls.','IR-01a.02','N/A','Determine if: - incident response procedures to facilitate the implementation of the incident response policy and associated incident response controls are developed and documented. - the incident response procedures are disseminated to [IR-01_ODP[02]; personnel or roles to whom the incident response procedures are to be disseminated is/are defined].'),
('000810','draft','2009-09-17','DISA FSO','policy','Disseminate the incident response procedures to organization-defined personnel or roles.','IR-01a.02','N/A','Determine if: - incident response procedures to facilitate the implementation of the incident response policy and associated incident response controls are developed and documented. - the incident response procedures are disseminated to [IR-01_ODP[02]; personnel or roles to whom the incident response procedures are to be disseminated is/are defined].'),
('000811','draft','2009-09-17','DISA FSO','policy','Review and update the current incident response procedures in accordance with organization-defined frequency.','IR-01c.02','N/A','Determine if: - the current incident response procedures are reviewed and updated [IR-01_ODP[07]; the frequency at which the current incident response procedures are reviewed and updated is defined]. - the current incident response procedures are reviewed and updated following [IR-01_ODP[08]; events that would require the incident response procedures to be reviewed and updated are defined].'),
('000812','draft','2009-09-17','DISA FSO','policy','Defines the frequency with which to review and update the current incident response procedures.','IR-01c.02','N/A','Determine if: - the current incident response procedures are reviewed and updated [IR-01_ODP[07]; the frequency at which the current incident response procedures are reviewed and updated is defined]. - the current incident response procedures are reviewed and updated following [IR-01_ODP[08]; events that would require the incident response procedures to be reviewed and updated are defined].'),
('000813','draft','2009-09-17','DISA FSO','policy','Provide incident response training to system users consistent with assigned roles and responsibilities within an organization-defined time period of assuming an incident response role or responsibility.','IR-02a.01','N/A','Determine if incident response training is provided to system users consistent with assigned roles and responsibilities within [IR-02_ODP[01]; a time period within which incident response training is to be provided to system users assuming an incident response role or responsibility is defined] of assuming an incident response role or responsibility or acquiring system access.'),
('000814','draft','2009-09-17','DISA FSO','policy','Provide incident response training in accordance with organization-defined frequency.','IR-02a.03','N/A','Determine if incident response training is provided to system users consistent with assigned roles and responsibilities [IR-02_ODP[02]; frequency at which to provide incident response training to users is defined] thereafter.'),
('000815','draft','2009-09-17','DISA FSO','policy','Defines a frequency for incident response training.',NULL,'N/A',NULL),
('000816','draft','2009-09-17','DISA FSO','policy','Incorporate simulated events into incident response training to facilitate effective response by personnel in crisis situations.','IR-02(01)','N/A','Determine if simulated events are incorporated into incident response training to facilitate the required response by personnel in crisis situations.'),
('000817','draft','2009-09-17','DISA FSO','policy','Provide an incident response training environment using organization-defined automated mechanisms.','IR-02(02)','N/A','Determine if an incident response training environment is provided using [IR-02(02)_ODP; automated mechanisms used in an incident response training environment are defined].'),
('000818','draft','2009-09-17','DISA FSO','policy','Test the effectiveness of the incident response capability for the system on an organization-defined frequency using organization-defined tests.','IR-03','N/A','Determine if the effectiveness of the incident response capability for the system is tested [IR-03_ODP[01]; frequency at which to test the effectiveness of the incident response capability for the system is defined] using [IR-03_ODP[02]; tests used to test the effectiveness of the incident response capability for the system are defined].'),
('000819','draft','2009-09-17','DISA FSO','policy','Defines a frequency for incident response tests.','IR-03','N/A','Determine if the effectiveness of the incident response capability for the system is tested [IR-03_ODP[01]; frequency at which to test the effectiveness of the incident response capability for the system is defined] using [IR-03_ODP[02]; tests used to test the effectiveness of the incident response capability for the system are defined].'),
('000820','draft','2009-09-17','DISA FSO','policy','Defines tests for incident response.','IR-03','N/A','Determine if the effectiveness of the incident response capability for the system is tested [IR-03_ODP[01]; frequency at which to test the effectiveness of the incident response capability for the system is defined] using [IR-03_ODP[02]; tests used to test the effectiveness of the incident response capability for the system are defined].'),
('000821','draft','2009-09-17','DISA FSO','policy','Test the incident response capability using organization-defined automated mechanisms.','IR-03(01)','N/A','Determine if the incident response capability is tested using [IR-03(01)_ODP; automated mechanisms used to test the incident response capability are defined].'),
('000822','draft','2009-09-18','DISA FSO','policy','Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery.','IR-04a.','N/A','Determine if: - an incident handling capability for incidents is implemented that is consistent with the incident response plan. - the incident handling capability for incidents includes preparation. - the incident handling capability for incidents includes detection and analysis. - the incident handling capability for incidents includes containment. - the incident handling capability for incidents includes eradication. - the incident handling capability for incidents includes recovery.'),
('000823','draft','2009-09-18','DISA FSO','policy','Coordinate incident handling activities with contingency planning activities.','IR-04b.','N/A','Determine if incident handling activities are coordinated with contingency planning activities.'),
('000825','draft','2009-09-18','DISA FSO','policy','Support the incident handling process using organization-defined automated mechanisms.','IR-04(01)','N/A','Determine if the incident handling process is supported using [IR-04(01)_ODP; automated mechanisms used to support the incident handling process are defined].'),
('000826','draft','2009-09-18','DISA FSO','policy','Include organization-defined types of dynamic reconfiguration for organization-defined system components as part of the incident response capability.','IR-04(02)','N/A','Determine if [IR-04(02)_ODP[01]; types of dynamic reconfiguration for system components are defined] for [IR-04(02)_ODP[02]; system components that require dynamic reconfiguration are defined] are included as part of the incident response capability.'),
('000827','draft','2009-09-18','DISA FSO','policy','Identify organization-defined classes of incidents for which organization-defined actions are to be taken to ensure continuation of organizational mission and business functions.','IR-04(03)','N/A','Determine if: - [IR-04(03)_ODP[01]; classes of incidents requiring an organization-defined action (defined in IR-04(03)_ODP[02]) to be taken are defined] are identified. - [IR-04(03)_ODP[02]; actions to be taken in response to organization-defined classes of incidents are defined] are taken in response to those incidents (defined in IR-04(03)_ODP[01]) to ensure the continuation of organizational mission and business functions.'),
('000828','draft','2009-09-18','DISA FSO','policy','Identify actions to take in response to organization-defined classes of incidents to ensure continuation of organizational missions and business functions.','IR-04(03)','N/A','Determine if: - [IR-04(03)_ODP[01]; classes of incidents requiring an organization-defined action (defined in IR-04(03)_ODP[02]) to be taken are defined] are identified. - [IR-04(03)_ODP[02]; actions to be taken in response to organization-defined classes of incidents are defined] are taken in response to those incidents (defined in IR-04(03)_ODP[01]) to ensure the continuation of organizational mission and business functions.'),
('000829','draft','2009-09-18','DISA FSO','policy','Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response.','IR-04(04)','N/A','Determine if incident information and individual incident responses are correlated to achieve an organization-wide perspective on incident awareness and response.'),
('000830','draft','2009-09-18','DISA FSO','policy','Defines security violations that, if detected, initiate a configurable capability to automatically disable the system.','IR-04(05)','N/A','Determine if a configurable capability is implemented to automatically disable the system if [IR-04(05)_ODP; security violations that automatically disable a system are defined] are detected.'),
('000831','draft','2009-09-18','DISA FSO','technical','Implement a configurable capability to automatically disable the system if organization-defined security violations are detected.','IR-04(05)','N/A','Determine if a configurable capability is implemented to automatically disable the system if [IR-04(05)_ODP; security violations that automatically disable a system are defined] are detected.'),
('000832','draft','2009-09-18','DISA FSO','policy','Track and document incidents.','IR-05','N/A','Determine if: - incidents are tracked. - incidents are documented.'),
('000834','draft','2009-09-18','DISA FSO','policy','Defines a time period for personnel to report suspected incidents to the organizational incident response capability.','IR-06a.','N/A','Determine if personnel is/are required to report suspected incidents to the organizational incident response capability within [IR-06_ODP[01]; time period for personnel to report suspected incidents to the organizational incident response capability is defined].'),
('000835','draft','2009-09-18','DISA FSO','policy','Require personnel to report suspected incidents to the organizational incident response capability within the organization-defined time period.','IR-06a.','N/A','Determine if personnel is/are required to report suspected incidents to the organizational incident response capability within [IR-06_ODP[01]; time period for personnel to report suspected incidents to the organizational incident response capability is defined].'),
('000836','draft','2009-09-18','DISA FSO','policy','Report incident information to organization-defined authorities.','IR-06b.','N/A','Determine if incident information is reported to [IR-06_ODP[02]; authorities to whom incident information is to be reported are defined].'),
('000837','draft','2009-09-18','DISA FSO','policy','Report incidents using organization-defined automated mechanisms.','IR-06(01)','N/A','Determine if incidents are reported using [IR-06(01)_ODP; automated mechanisms used for reporting incidents are defined].'),
('000838','draft','2009-09-18','DISA FSO','policy','Report system vulnerabilities associated with reported incidents to organization-defined personnel or roles.','IR-06(02)','N/A','Determine if system vulnerabilities associated with reported incidents are reported to [IR-06(02)_ODP; personnel or roles to whom system vulnerabilities associated with reported incidents are reported to is/are defined].'),
('000839','draft','2009-09-18','DISA FSO','policy','Provide an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the system for the handling and reporting of incidents.','IR-07','N/A','Determine if: - an incident response support resource, integral to the organizational incident response capability, is provided. - the incident response support resource offers advice and assistance to users of the system for the response and reporting of incidents.'),
('000841','draft','2009-09-18','DISA FSO','policy','Establish a direct, cooperative relationship between its incident response capability and external providers of system protection capability.','IR-07(02)(a)','N/A','Determine if a direct, cooperative relationship is established between its incident response capability and external providers of the system protection capability.'),
('000842','draft','2009-09-18','DISA FSO','policy','Identify organizational incident response team members to the external providers.','IR-07(02)(b)','N/A','Determine if organizational incident response team members are identified to the external providers.'),
('000844','draft','2009-09-18','DISA FSO','policy','Develop an incident response plan that is reviewed and approved by organization-defined personnel or roles on an organization-defined frequency.','IR-08a.09','N/A','Determine if an incident response plan is developed that is reviewed and approved by [IR-08_ODP[01]; personnel or roles that review and approve the incident response plan is/are identified] [IR-08_ODP[02]; the frequency at which to review and approve the incident response plan is defined].'),
('000845','draft','2009-09-18','DISA FSO','policy','Defines incident response personnel (identified by name and/or by role) and organizational elements to whom copies of the incident response plan are distributed.','IR-08b.','N/A','Determine if: - copies of the incident response plan are distributed to [IR-08_ODP[04]; incident response personnel (identified by name and/or by role) to whom copies of the incident response plan are to be distributed is/are defined]. - copies of the incident response plan are distributed to [IR-08_ODP[05]; organizational elements to which copies of the incident response plan are to be distributed are defined].'),
('000846','draft','2009-09-18','DISA FSO','policy','Distributes copies of the incident response plan to organization-defined incident response personnel (identified by name and/or by role) and organizational elements.','IR-08b.','N/A','Determine if: - copies of the incident response plan are distributed to [IR-08_ODP[04]; incident response personnel (identified by name and/or by role) to whom copies of the incident response plan are to be distributed is/are defined]. - copies of the incident response plan are distributed to [IR-08_ODP[05]; organizational elements to which copies of the incident response plan are to be distributed are defined].'),
('000849','draft','2009-09-18','DISA FSO','policy','Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing.','IR-08c.','N/A','Determine if the incident response plan is updated to address system and organizational changes or problems encountered during plan implementation, execution, or testing.'),
('000850','draft','2009-09-18','DISA FSO','policy','Communicate incident response plan changes to organization-defined incident response personnel (identified by name and/or by role) and organizational elements.','IR-08d.','N/A','Determine if: - incident response plan changes are communicated to [IR-08_ODP[06]; incident response personnel (identified by name and/or by role) to whom changes to the incident response plan is/are communicated are defined]. - incident response plan changes are communicated to [IR-08_ODP[07]; organizational elements to which changes to the incident response plan are communicated are defined].'),
('000851','draft','2009-09-18','DISA FSO','policy','Defines the frequency with which to review and update the current system maintenance policy.','MA-01c.01','N/A','Determine if: - the current maintenance policy is reviewed and updated [MA-01_ODP[05]; the frequency with which the current maintenance policy is reviewed and updated is defined]. - the current maintenance policy is reviewed and updated following [MA-01_ODP[06]; events that would require the current maintenance policy to be reviewed and updated are defined].'),
('000852','draft','2009-09-18','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','MA-01a.01(a)','N/A','Determine if: - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses purpose. - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses scope. - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses roles. - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses responsibilities. - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses management commitment. - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses coordination among organizational entities. - the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy addresses compliance.'),
('000853','draft','2009-09-18','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; and/or system-level maintenance policy to organization-defined personnel or roles.','MA-01a.','N/A','Determine if: - a maintenance policy is developed and documented. - the maintenance policy is disseminated to [MA-01_ODP[01]; personnel or roles to whom the maintenance policy is to be disseminated is/are defined].'),
('000854','draft','2009-09-18','DISA FSO','policy','Review and update the current maintenance policy in accordance with organization-defined frequency.','MA-01c.01','N/A','Determine if: - the current maintenance policy is reviewed and updated [MA-01_ODP[05]; the frequency with which the current maintenance policy is reviewed and updated is defined]. - the current maintenance policy is reviewed and updated following [MA-01_ODP[06]; events that would require the current maintenance policy to be reviewed and updated are defined].'),
('000855','draft','2009-09-18','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls.','MA-01a.02','N/A','Determine if: - maintenance procedures to facilitate the implementation of the maintenance policy and associated maintenance controls are developed and documented. - Determine if the maintenance procedures are disseminated to [MA-01_ODP[02]; personnel or roles to whom the maintenance procedures are to be disseminated is/are defined].'),
('000856','draft','2009-09-18','DISA FSO','policy','Disseminate procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls to organization-defined personnel or roles.','MA-01a.02','N/A','Determine if: - maintenance procedures to facilitate the implementation of the maintenance policy and associated maintenance controls are developed and documented. - Determine if the maintenance procedures are disseminated to [MA-01_ODP[02]; personnel or roles to whom the maintenance procedures are to be disseminated is/are defined].'),
('000857','draft','2009-09-18','DISA FSO','policy','Review and update the current maintenance procedures in accordance with organization-defined frequency.','MA-01c.02','N/A','Determine if: - the current maintenance procedures are reviewed and updated [MA-01_ODP[07]; the frequency with which the current maintenance procedures are reviewed and updated is defined]. - the current maintenance procedures are reviewed and updated following [MA-01_ODP[08]; events that would require the maintenance procedures to be reviewed and updated are defined].'),
('000860','draft','2009-09-18','DISA FSO','policy','Require that organization-defines personnel or roles explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement.','MA-02c.','N/A','Determine if [MA-02_ODP[01]; personnel or roles required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance or repairs is/are defined] is/are required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement.'),
('000861','draft','2009-09-18','DISA FSO','policy','Sanitize equipment to remove organization-defined information from associated media prior to removal from organizational facilities for off-site maintenance, repairs or replacement.','MA-02d.','N/A','Determine if equipment is sanitized to remove [MA-02_ODP[02]; information to be removed from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement is defined] from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement.'),
('000862','draft','2009-09-18','DISA FSO','policy','Check all potentially impacted controls to verify that the controls are still functioning properly following maintenance, repair or replacement actions.','MA-02e.','N/A','Determine if all potentially impacted controls are checked to verify that the controls are still functioning properly following maintenance, repair, or replacement actions.'),
('000865','draft','2009-09-18','DISA FSO','policy','Approve the use of system maintenance tools.',NULL,'N/A',NULL),
('000866','draft','2009-09-18','DISA FSO','policy','Control the use of system maintenance tools.',NULL,'N/A',NULL),
('000867','draft','2009-09-18','DISA FSO','policy','Monitor the use of system maintenance tools.','MA-03a.','N/A','Determine if: - the use of system maintenance tools is approved. - the use of system maintenance tools is controlled. - the use of system maintenance tools is monitored.'),
('000869','draft','2009-09-18','DISA FSO','policy','Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.','MA-03(01)','N/A','Determine if maintenance tools used by maintenance personnel are inspected for improper or unauthorized modifications.'),
('000870','draft','2009-09-18','DISA FSO','policy','Check media containing diagnostic and test programs for malicious code before the media are used in the system.','MA-03(02)','N/A','Determine if media containing diagnostic and test programs are checked for malicious code before the media are used in the system.'),
('000871','draft','2009-09-18','DISA FSO','policy','Prevent the unauthorized removal of maintenance equipment containing organizational information by: (a) verifying that there is no organizational information contained on the equipment; (b) sanitizing or destroying the equipment; (c) retaining the equipment within the facility; or (d) obtaining an exemption from organization-defined personnel or roles explicitly authorizing removal of the equipment from the facility.','MA-03(03)(a)','N/A','Determine if the removal of maintenance equipment containing organizational information is prevented by verifying that there is no organizational information contained on the equipment.'),
('000873','draft','2009-09-18','DISA FSO','policy','Approve nonlocal maintenance and diagnostic activities.','MA-04a.','N/A','Determine if: - nonlocal maintenance and diagnostic activities are approved. - nonlocal maintenance and diagnostic activities are monitored.'),
('000874','draft','2009-09-18','DISA FSO','policy','Monitor nonlocal maintenance and diagnostic activities.','MA-04a.','N/A','Determine if: - nonlocal maintenance and diagnostic activities are approved. - nonlocal maintenance and diagnostic activities are monitored.'),
('000876','draft','2009-09-18','DISA FSO','policy','Allow the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the system.','MA-04b.','N/A','Determine if: - the use of nonlocal maintenance and diagnostic tools are allowed only as consistent with organizational policy. - the use of nonlocal maintenance and diagnostic tools are documented in the security plan for the system.'),
('000877','draft','2009-09-18','DISA FSO','technical','Employ strong authentication in the establishment of nonlocal maintenance and diagnostic sessions.','MA-04c.','N/A','Determine if strong authentication is employed in the establishment of nonlocal maintenance and diagnostic sessions.'),
('000878','draft','2009-09-18','DISA FSO','policy','Maintain records for nonlocal maintenance and diagnostic activities.','MA-04d.','N/A','Determine if records for nonlocal maintenance and diagnostic activities are maintained.'),
('000882','draft','2009-09-18','DISA FSO','policy','Require that nonlocal maintenance and diagnostic services be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced.','MA-04(03)(a)','N/A','Determine if: - nonlocal maintenance services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced. - nonlocal diagnostic services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced.'),
('000883','draft','2009-09-18','DISA FSO','policy','Remove the component to be serviced from the system prior to nonlocal maintenance or diagnostic services; sanitize the component (for organizational information).','MA-04(03)(b)','N/A','Determine if: - the component to be serviced is removed from the system prior to nonlocal maintenance or diagnostic services. - the component to be serviced is sanitized (for organizational information). - the component is inspected and sanitized (for potentially malicious software) after the service is performed and before reconnecting the component to the system.'),
('000884','draft','2009-09-18','DISA FSO','technical','Protect nonlocal maintenance sessions by employing organization-defined authenticators that are replay resistant.','MA-04(04)(a)','N/A','Determine if nonlocal maintenance sessions are protected by employing [MA-04(04)_ODP; authenticators that are replay resistant are defined].'),
('000886','draft','2009-09-18','DISA FSO','policy','Defines the personnel or roles to be notified of the date and time of planned nonlocal maintenance.','MA-04(05)(b)','N/A','Determine if [MA-04(05)_ODP[02]; personnel and roles to be notified of the date and time of planned nonlocal maintenance is/are defined] is/are notified of the date and time of planned nonlocal maintenance.'),
('000887','draft','2009-09-18','DISA FSO','policy','Require the approval of each nonlocal maintenance session by organization-defined personnel or roles.','MA-04(05)(a)','N/A','Determine if the approval of each nonlocal maintenance session is required by [MA-04(05)_ODP[01]; personnel or roles required to approve each nonlocal maintenance session is/are defined].'),
('000890','draft','2009-09-18','DISA FSO','policy','Establish a process for maintenance personnel authorization.','MA-05a.','N/A','Determine if: - a process for maintenance personnel authorization is established. - a list of authorized maintenance organizations or personnel is maintained.'),
('000891','draft','2009-09-18','DISA FSO','policy','Maintain a list of authorized maintenance organizations or personnel.','MA-05a.','N/A','Determine if: - a process for maintenance personnel authorization is established. - a list of authorized maintenance organizations or personnel is maintained.'),
('000893','draft','2009-09-18','DISA FSO','policy','Implement procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens.',NULL,'N/A',NULL),
('000894','draft','2009-09-18','DISA FSO','policy','Requires maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals to be escorted and supervised during the performance of maintenance and diagnostic activities on the system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified.','MA-05(01)(a)(01)','N/A','Determine if procedures for the use of maintenance personnel who lack appropriate security clearances or are not U.S. citizens are implemented and include approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified escorting and supervising maintenance personnel without the needed access authorization during the performance of maintenance and diagnostic activities.'),
('000895','draft','2009-09-18','DISA FSO','policy','Require that, prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the system be sanitized and all nonvolatile storage media be removed or physically disconnected from the system and secured.','MA-05(01)(a)(02)','N/A','Determine if procedures for the use of maintenance personnel who lack appropriate security clearances or are not U.S. citizens are implemented and include all volatile information storage components within the system being sanitized and all non-volatile storage media being removed or physically disconnected from the system and secured prior to initiating maintenance or diagnostic activities.'),
('000897','draft','2009-09-18','DISA FSO','policy','Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for all compartments of information on the system.','MA-05(02)','N/A','Determine if: - personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances for at least the highest classification level and for compartments of information on the system. - personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess formal access approvals for at least the highest classification level and for compartments of information on the system.'),
('000898','draft','2009-09-18','DISA FSO','policy','Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are U.S. citizens.','MA-05(03)','N/A','Determine if personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are U.S. citizens.'),
('000899','draft','2009-09-18','DISA FSO','policy','Ensure that cleared foreign nationals with appropriate security clearances are used to conduct maintenance and diagnostic activities on classified systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments.','MA-05(04)(a)','N/A','Determine if foreign nationals with appropriate security clearances are used to conduct maintenance and diagnostic activities on classified systems only when the systems are jointly owned and operated by the United States and foreign allied governments or owned and operated solely by foreign allied governments.'),
('000900','draft','2009-09-18','DISA FSO','policy','Ensure that that approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements.','MA-05(04)(b)','N/A','Determine if: - approvals regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements. - consents regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements. - detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements.'),
('000903','draft','2009-09-18','DISA FSO','policy','Obtain maintenance support and/or spare parts for organization-defined system components within an organization-defined time period of failure.','MA-06','N/A','Determine if maintenance support and/or spare parts are obtained for [MA-06_ODP[01]; system components for which maintenance support and/or spare parts are obtained are defined] within [MA-06_ODP[02]; time period within which maintenance support and/or spare parts are to be obtained after a failure are defined] of failure.'),
('000904','draft','2009-09-21','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PE-01a.01(a)','N/A','Determine if: - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses purpose. - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses scope. - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses roles. - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses responsibilities. - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses management commitment. - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses coordination among organizational entities. - the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy addresses compliance.'),
('000905','draft','2009-09-21','DISA FSO','policy','Disseminate a physical and environmental protection policy to organization-defined personnel or roles.','PE-01a.','N/A','Determine if: - a physical and environmental protection policy is developed and documented. - the physical and environmental protection policy is disseminated to [PE-01_ODP[01]; personnel or roles to whom the physical and environmental protection policy is to be disseminated is/are defined].'),
('000906','draft','2009-09-21','DISA FSO','policy','Review and update the current physical and environmental protection policy in accordance with organization-defined frequency.','PE-01c.01','N/A','Determine if: - the current physical and environmental protection policy is reviewed and updated [PE-01_ODP[05]; the frequency at which the current physical and environmental protection policy is reviewed and updated is defined]. - the current physical and environmental protection policy is reviewed and updated following [PE-01_ODP[06]; events that would require the current physical and environmental protection policy to be reviewed and updated are defined].'),
('000907','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review and update the physical and environmental protection policy.','PE-01c.01','N/A','Determine if: - the current physical and environmental protection policy is reviewed and updated [PE-01_ODP[05]; the frequency at which the current physical and environmental protection policy is reviewed and updated is defined]. - the current physical and environmental protection policy is reviewed and updated following [PE-01_ODP[06]; events that would require the current physical and environmental protection policy to be reviewed and updated are defined].'),
('000908','draft','2009-09-21','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls.','PE-01a.02','N/A','Determine if: - physical and environmental protection procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls are developed and documented. - the physical and environmental protection procedures are disseminated to [PE-01_ODP[02]; personnel or roles to whom the physical and environmental protection procedures are to be disseminated is/are defined].'),
('000909','draft','2009-09-21','DISA FSO','policy','Disseminate physical and environmental protection procedures to organization-defined personnel or roles.','PE-01a.02','N/A','Determine if: - physical and environmental protection procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls are developed and documented. - the physical and environmental protection procedures are disseminated to [PE-01_ODP[02]; personnel or roles to whom the physical and environmental protection procedures are to be disseminated is/are defined].'),
('000910','draft','2009-09-21','DISA FSO','policy','Review and update the current physical and environmental protection procedures in accordance with organization-defined frequency.','PE-01c.02','N/A','Determine if: - the current physical and environmental protection procedures are reviewed and updated [PE-01_ODP[07]; the frequency at which the current physical and environmental protection procedures are reviewed and updated is defined]. - the current physical and environmental protection procedures are reviewed and updated following [PE-01_ODP[08]; events that would require the physical and environmental protection procedures to be reviewed and updated are defined].'),
('000911','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review and update the physical and environmental protection procedures.','PE-01c.02','N/A','Determine if: - the current physical and environmental protection procedures are reviewed and updated [PE-01_ODP[07]; the frequency at which the current physical and environmental protection procedures are reviewed and updated is defined]. - the current physical and environmental protection procedures are reviewed and updated following [PE-01_ODP[08]; events that would require the physical and environmental protection procedures to be reviewed and updated are defined].'),
('000912','draft','2009-09-21','DISA FSO','policy','Develop a list of individuals with authorized access to the facility where the system resides.','PE-02a.','N/A','Determine if: - a list of individuals with authorized access to the facility where the system resides has been developed. - the list of individuals with authorized access to the facility where the system resides has been approved. - the list of individuals with authorized access to the facility where the system resides has been maintained.'),
('000913','draft','2009-09-21','DISA FSO','policy','Issue authorization credentials for facility access.','PE-02b.','N/A','Determine if authorization credentials are issued for facility access.'),
('000914','draft','2009-09-21','DISA FSO','policy','Review the access list detailing authorized facility access by individuals in accordance with organization-defined frequency.','PE-02c.','N/A','Determine if the access list detailing authorized facility access by individuals is reviewed [PE-02_ODP; frequency at which to review the access list detailing authorized facility access by individuals is defined].'),
('000915','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review the access list detailing authorized facility access by individuals.','PE-02c.','N/A','Determine if the access list detailing authorized facility access by individuals is reviewed [PE-02_ODP; frequency at which to review the access list detailing authorized facility access by individuals is defined].'),
('000916','draft','2009-09-21','DISA FSO','policy','Authorize physical access to the facility where the system resides based on position or role.','PE-02(01)','N/A','Determine if physical access to the facility where the system resides is authorized based on position or role.'),
('000917','draft','2009-09-21','DISA FSO','policy','Require two forms of identification from an organization-defined list of acceptable forms of identification for visitor access to the facility where the system resides.','PE-02(02)','N/A','Determine if two forms of identification are required from [PE-02(02)_ODP; a list of acceptable forms of identification for visitor access to the facility where the system resides is defined] for visitor access to the facility where the system resides.'),
('000920','draft','2009-09-21','DISA FSO','policy','Verify individual access authorizations before granting access to the facility.','PE-03a.01','N/A','Determine if physical access authorizations are enforced at [PE-03_ODP[01]; entry and exit points to the facility in which the system resides are defined] by verifying individual access authorizations before granting access to the facility.'),
('000923','draft','2009-09-21','DISA FSO','policy','Secure keys, combinations, and other physical access devices.','PE-03e.','N/A','Determine if: - keys are secured. - combinations are secured. - other physical access devices are secured.'),
('000924','draft','2009-09-21','DISA FSO','policy','Inventory organization-defined physical access devices on an organization-defined frequency.','PE-03f.','N/A','Determine if [PE-03_ODP[07]; physical access devices to be inventoried are defined] are inventoried [PE-03_ODP[08]; frequency at which to inventory physical access devices is defined].'),
('000925','draft','2009-09-21','DISA FSO','policy','Defines the frequency for conducting inventories of organization-defined physical access devices.','PE-03f.','N/A','Determine if [PE-03_ODP[07]; physical access devices to be inventoried are defined] are inventoried [PE-03_ODP[08]; frequency at which to inventory physical access devices is defined].'),
('000926','draft','2009-09-21','DISA FSO','policy','Change combinations and keys in accordance with organization-defined frequency and/or when keys are lost, combinations are compromised, or when individuals possessing the keys or combinations are transferred or terminated.','PE-03g.','N/A','Determine if: - combinations are changed [PE-03_ODP[09]; frequency at which to change combinations is defined], when combinations are compromised, or when individuals possessing the combinations are transferred or terminated. - keys are changed [PE-03_ODP[10]; frequency at which to change keys is defined], when keys are lost, or when individuals possessing the keys are transferred or terminated.'),
('000927','draft','2009-09-21','DISA FSO','policy','Defines a frequency for changing combinations and keys.','PE-03g.','N/A','Determine if: - combinations are changed [PE-03_ODP[09]; frequency at which to change combinations is defined], when combinations are compromised, or when individuals possessing the combinations are transferred or terminated. - keys are changed [PE-03_ODP[10]; frequency at which to change keys is defined], when keys are lost, or when individuals possessing the keys are transferred or terminated.'),
('000928','draft','2009-09-21','DISA FSO','policy','Enforce physical access authorizations to the system in addition to the physical access controls for the facility where the system resides at organization-defined physical spaces containing one or more components of the system.','PE-03(01)','N/A','Determine if: - physical access authorizations to the system are enforced. - physical access controls are enforced for the facility at [PE-03(01)_ODP; physical spaces containing one or more components of the system are defined].'),
('000929','draft','2009-09-21','DISA FSO','policy','Perform security checks in accordance with organization-defined frequency at the physical boundary of the facility or system for unauthorized exfiltration of information or removal of system components.','PE-03(02)','N/A','Determine if security checks are performed [PE-03(02)_ODP; the frequency at which to perform security checks at the physical perimeter of the facility or system for exfiltration of information or removal of system components is defined] at the physical perimeter of the facility or system for exfiltration of information or removal of system components.'),
('000930','draft','2009-09-21','DISA FSO','policy','Employ guards to control every physical access point to the facility where the system resides 24 hours per day, 7 days per week.','PE-03(03)','N/A','Determine if guards are employed to control [PE-03(03)_ODP; physical access points to the facility where the system resides are defined] to the facility where the system resides 24 hours per day, 7 days per week.'),
('000931','draft','2009-09-21','DISA FSO','policy','Use lockable physical casings to protect organization-defined system components from unauthorized physical access.','PE-03(04)','N/A','Determine if lockable physical casings are used to protect [PE-03(04)_ODP; system components to be protected from unauthorized physical access are defined] from unauthorized access.'),
('000932','draft','2009-09-21','DISA FSO','policy','Defines system components to be protected from unauthorized physical access using lockable physical casings.','PE-03(04)','N/A','Determine if lockable physical casings are used to protect [PE-03(04)_ODP; system components to be protected from unauthorized physical access are defined] from unauthorized access.'),
('000933','draft','2009-09-21','DISA FSO','policy','Employ organization-defined anti-tamper technologies to deter and/or prevent physical tampering or alteration of organization-defined hardware components within the system.','PE-03(05)','N/A','Determine if [PE-03(05)_ODP[01]; anti-tamper technologies to be employed are defined] are employed to [PE-03(05)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {detect; prevent}] physical tampering or alteration of [PE-03(05)_ODP[03]; hardware components to be protected from physical tampering or alteration are defined] within the system.'),
('000936','draft','2009-09-21','DISA FSO','policy','Control physical access to organization-defined system distribution and transmission lines within organizational facilities using organization-defined security controls.','PE-04','N/A','Determine if physical access to [PE-04_ODP[01]; system distribution and transmission lines requiring physical access controls are defined] within organizational facilities is controlled using [PE-04_ODP[02]; security controls to be implemented to control physical access to system distribution and transmission lines within the organizational facility are defined].'),
('000937','draft','2009-09-21','DISA FSO','policy','Control physical access to output from organization-defined output devices to prevent unauthorized individuals from obtaining the output.','PE-05','N/A','Determine if physical access to output from [PE-05_ODP; output devices that require physical access control to output are defined] is controlled to prevent unauthorized individuals from obtaining the output.'),
('000939','draft','2009-09-21','DISA FSO','policy','Review physical access logs in accordance with organization-defined frequency.','PE-06b.','N/A','Determine if: - physical access logs are reviewed [PE-06_ODP[01]; the frequency at which to review physical access logs is defined]. - physical access logs are reviewed upon occurrence of [PE-06_ODP[02]; events or potential indication of events requiring physical access logs to be reviewed are defined].'),
('000940','draft','2009-09-21','DISA FSO','policy','Defines a frequency for reviewing physical access logs.','PE-06b.','N/A','Determine if: - physical access logs are reviewed [PE-06_ODP[01]; the frequency at which to review physical access logs is defined]. - physical access logs are reviewed upon occurrence of [PE-06_ODP[02]; events or potential indication of events requiring physical access logs to be reviewed are defined].'),
('000941','draft','2009-09-21','DISA FSO','policy','Coordinate results of reviews and investigations with the organization''s incident response capability.','PE-06c.','N/A','Determine if: - results of reviews are coordinated with organizational incident response capabilities. - results of investigations are coordinated with organizational incident response capabilities.'),
('000942','draft','2009-09-21','DISA FSO','policy','Monitor physical access to the facility where the system resides using physical intrusion alarms and surveillance equipment.','PE-06(01)','N/A','Determine if: - physical access to the facility where the system resides is monitored using physical intrusion alarms. - physical access to the facility where the system resides is monitored using physical surveillance equipment.'),
('000947','draft','2009-09-21','DISA FSO','policy','Maintain visitor access records to the facility where the system resides for an organization-defined time period.','PE-08a.','N/A','Determine if visitor access records for the facility where the system resides are maintained for [PE-08_ODP[01]; time period for which to maintain visitor access records for the facility where the system resides is defined].'),
('000948','draft','2009-09-21','DISA FSO','policy','Review visitor access records in accordance with organization-defined frequency.','PE-08b.','N/A','Determine if visitor access records are reviewed [PE-08_ODP[02]; the frequency at which to review visitor access records is defined].'),
('000949','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review the visitor access records for the facility where the system resides.','PE-08b.','N/A','Determine if visitor access records are reviewed [PE-08_ODP[02]; the frequency at which to review visitor access records is defined].'),
('000950','draft','2009-09-21','DISA FSO','policy','Maintain and review visitor access records using organization-defined automated mechanisms.','PE-08(01)','N/A','Determine if: - visitor access records are maintained using [PE-08(01)_ODP[01]; automated mechanisms used to maintain visitor access records are defined]. - visitor access records are reviewed using [PE-08(01)_ODP[02]; automated mechanisms used to review visitor access records are defined].'),
('000952','draft','2009-09-21','DISA FSO','policy','Protect power equipment and power cabling for the system from damage and destruction.','PE-09','N/A','Determine if: - power equipment for the system is protected from damage and destruction. - power cabling for the system is protected from damage and destruction.'),
('000954','draft','2009-09-21','DISA FSO','policy','Employ automatic voltage controls for organization-defined critical system components.','PE-09(02)','N/A','Determine if automatic voltage controls for [PE-09(02)_ODP; the critical system components that require automatic voltage controls are defined] are employed.'),
('000955','draft','2009-09-21','DISA FSO','policy','Defines critical system components that require automatic voltage controls.','PE-09(02)','N/A','Determine if automatic voltage controls for [PE-09(02)_ODP; the critical system components that require automatic voltage controls are defined] are employed.'),
('000956','draft','2009-09-21','DISA FSO','policy','Provides the capability of shutting off power to the organization-defined system or individual system components in emergency situations.','PE-10a.','N/A','Determine if the capability to shut off power to [PE-10_ODP[01]; system or individual system components that require the capability to shut off power in emergency situations is/are defined] in emergency situations is provided.'),
('000957','draft','2009-09-21','DISA FSO','policy','Place emergency shutoff switches or devices in an organization-defined location by system or system component to facilitate access for authorized personnel.','PE-10b.','N/A','Determine if emergency shutoff switches or devices are placed in [PE-10_ODP[02]; location of emergency shutoff switches or devices by system or system component is defined] to facilitate access for authorized personnel.'),
('000958','draft','2009-09-21','DISA FSO','policy','Defines a location for emergency shutoff switches or devices by system or system component.','PE-10b.','N/A','Determine if emergency shutoff switches or devices are placed in [PE-10_ODP[02]; location of emergency shutoff switches or devices by system or system component is defined] to facilitate access for authorized personnel.'),
('000959','draft','2009-09-21','DISA FSO','policy','Protect emergency power shutoff capability from unauthorized activation.','PE-10c.','N/A','Determine if the emergency power shutoff capability is protected from unauthorized activation.'),
('000961','draft','2009-09-21','DISA FSO','policy','Provide an alternate power supply for the system that is activated manually or automatically and that can maintain minimally required operational capability in the event of an extended loss of the primary power source.','PE-11(01)','N/A','Determine if: - an alternate power supply provided for the system is activated [PE-11(01)_ODP; one of the following PARAMETER VALUES is selected: {manually; automatically}]. - the alternate power supply provided for the system can maintain minimally required operational capability in the event of an extended loss of the primary power source.'),
('000963','draft','2009-09-21','DISA FSO','policy','Employ and maintains automatic emergency lighting for the information system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility.','PE-12','N/A','Determine if: - automatic emergency lighting that activates in the event of a power outage or disruption is employed for the system. - automatic emergency lighting that activates in the event of a power outage or disruption is maintained for the system. - automatic emergency lighting for the system covers emergency exits within the facility. - automatic emergency lighting for the system covers evacuation routes within the facility.'),
('000965','draft','2009-09-21','DISA FSO','policy','Employ and maintain fire detection and suppression systems that are supported by an independent energy source.','PE-13','N/A','Determine if: - fire detection systems are employed. - employed fire detection systems are supported by an independent energy source. - employed fire detection systems are maintained. - fire suppression systems are employed. - employed fire suppression systems are supported by an independent energy source. - employed fire suppression systems are maintained.'),
('000968','draft','2009-09-21','DISA FSO','policy','Employ an automatic fire suppression capability for the system when the facility is not staffed on a continuous basis.','PE-13(02)(b)','N/A','Determine if an automatic fire suppression capability is employed when the facility is not staffed on a continuous basis.'),
('000971','draft','2009-09-21','DISA FSO','policy','Maintain temperature; humidity; pressure; radiation; and/or organization-defined environmental control levels within the facility where the system resides at organization-defined acceptable levels.','PE-14a.','N/A','Determine if [PE-14_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {temperature; humidity; pressure; radiation; [PE-14_ODP[02]; environmental control(s) for which to maintain a specified level in the facility where the system resides are defined (if selected)]}] levels are maintained at [PE-14_ODP[03]; acceptable levels for environmental controls are defined] within the facility where the system resides.'),
('000972','draft','2009-09-21','DISA FSO','policy','Defines acceptable temperature, humidity, pressure, radiation, and/or organization-defined environmental control levels to be maintained within the facility where the system resides.','PE-14a.','N/A','Determine if [PE-14_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {temperature; humidity; pressure; radiation; [PE-14_ODP[02]; environmental control(s) for which to maintain a specified level in the facility where the system resides are defined (if selected)]}] levels are maintained at [PE-14_ODP[03]; acceptable levels for environmental controls are defined] within the facility where the system resides.'),
('000973','draft','2009-09-21','DISA FSO','policy','Monitor environmental control levels in accordance with organization-defined frequency.','PE-14b.','N/A','Determine if environmental control levels are monitored [PE-14_ODP[04]; frequency at which to monitor environmental control levels is defined].'),
('000974','draft','2009-09-21','DISA FSO','policy','Defines a frequency for monitoring environmental control levels.','PE-14b.','N/A','Determine if environmental control levels are monitored [PE-14_ODP[04]; frequency at which to monitor environmental control levels is defined].'),
('000975','draft','2009-09-21','DISA FSO','policy','Employ organization-defined automatic environmental controls in the facility to prevent fluctuations potentially harmful to the system.','PE-14(01)','N/A','Determine if [PE-14(01)_ODP; automatic environmental controls to prevent fluctuations that are potentially harmful to the system are defined] are employed in the facility to prevent fluctuations that are potentially harmful to the system.'),
('000976','draft','2009-09-21','DISA FSO','policy','Employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment to organization-defined personnel or roles.','PE-14(02)','N/A','Determine if: - environmental control monitoring is employed. - the environmental control monitoring capability provides an alarm or notification to [PE-14(02)_ODP; personnel or roles to be notified by environmental control monitoring when environmental changes are potentially harmful to personnel or equipment is/are defined] when changes are potentially harmful to personnel or equipment.'),
('000977','draft','2009-09-21','DISA FSO','policy','Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible.','PE-15','N/A','Determine if: - the system is protected from damage resulting from water leakage by providing master shutoff or isolation valves. - the master shutoff or isolation valves are accessible. - the master shutoff or isolation valves are working properly. - the master shutoff or isolation valves are known to key personnel.'),
('000978','draft','2009-09-21','DISA FSO','policy','Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are working properly.','PE-15','N/A','Determine if: - the system is protected from damage resulting from water leakage by providing master shutoff or isolation valves. - the master shutoff or isolation valves are accessible. - the master shutoff or isolation valves are working properly. - the master shutoff or isolation valves are known to key personnel.'),
('000979','draft','2009-09-21','DISA FSO','policy','Key personnel have knowledge of the master water shutoff or isolation valves.','PE-15','N/A','Determine if: - the system is protected from damage resulting from water leakage by providing master shutoff or isolation valves. - the master shutoff or isolation valves are accessible. - the master shutoff or isolation valves are working properly. - the master shutoff or isolation valves are known to key personnel.'),
('000981','draft','2009-09-21','DISA FSO','policy','Authorize organization-defined types of system components entering and exiting the facility.','PE-16a.','N/A','Determine if: - [PE-16_ODP[01]; types of system components to be authorized and controlled when entering the facility are defined] are authorized when entering the facility. - [PE-16_ODP[01]; types of system components to be authorized and controlled when entering the facility are defined] are controlled when entering the facility. - [PE-16_ODP[02]; types of system components to be authorized and controlled when exiting the facility are defined] are authorized when exiting the facility. - [PE-16_ODP[02]; types of system components to be authorized and controlled when exiting the facility are defined] are controlled when exiting the facility.'),
('000983','draft','2009-09-21','DISA FSO','policy','Control organization-defined types of system components entering and exiting the facility.','PE-16a.','N/A','Determine if: - [PE-16_ODP[01]; types of system components to be authorized and controlled when entering the facility are defined] are authorized when entering the facility. - [PE-16_ODP[01]; types of system components to be authorized and controlled when entering the facility are defined] are controlled when entering the facility. - [PE-16_ODP[02]; types of system components to be authorized and controlled when exiting the facility are defined] are authorized when exiting the facility. - [PE-16_ODP[02]; types of system components to be authorized and controlled when exiting the facility are defined] are controlled when exiting the facility.'),
('000984','draft','2009-09-21','DISA FSO','policy','Maintain records of system components.','PE-16b.','N/A','Determine if records of the system components are maintained.'),
('000985','draft','2009-09-21','DISA FSO','policy','Employ organization-defined controls at alternate work sites.','PE-17b.','N/A','Determine if [PE-17_ODP[02]; controls to be employed at alternate work sites are defined] are employed at alternate work sites.'),
('000987','draft','2009-09-21','DISA FSO','policy','Assess as feasible, the effectiveness of controls at alternate work sites.','PE-17c.','N/A','Determine if the effectiveness of controls at alternate work sites is assessed.'),
('000988','draft','2009-09-21','DISA FSO','policy','Provide a means for employees to communicate with information security personnel in case of incidents.','PE-17d.','N/A','Determine if a means for employees to communicate with information security and privacy personnel in case of incidents is provided.'),
('000989','draft','2009-09-21','DISA FSO','policy','Position system components within the facility to minimize potential damage from organization-defined physical and environmental hazards.','PE-18','N/A','Determine if system components are positioned within the facility to minimize potential damage from [PE-18_ODP; physical and environmental hazards that could result in potential damage to system components within the facility are defined] and to minimize the opportunity for unauthorized access.'),
('000991','draft','2009-09-21','DISA FSO','policy','Position system components within the facility to minimize the opportunity for unauthorized access.','PE-18','N/A','Determine if system components are positioned within the facility to minimize potential damage from [PE-18_ODP; physical and environmental hazards that could result in potential damage to system components within the facility are defined] and to minimize the opportunity for unauthorized access.'),
('000993','draft','2009-09-21','DISA FSO','policy','Protect the system from information leakage due to electromagnetic signals emanations.','PE-19','N/A','Determine if the system is protected from information leakage due to electromagnetic signal emanations.'),
('000995','draft','2009-09-21','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','MP-01a.01(a)','N/A','Determine if: - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy addresses purpose. - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy addresses scope. - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy addresses roles. - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy addresses responsibilities. - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy addresses management commitment. - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy addresses coordination among organizational entities. - the [MP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] media protection policy compliance.'),
('000996','draft','2009-09-21','DISA FSO','policy','Disseminates a media protection policy to organization-defined personnel or roles.','MP-01a.','N/A','Determine if: - a media protection policy is developed and documented. - the media protection policy is disseminated to [MP-01_ODP[01]; personnel or roles to whom the media protection policy is to be disseminated is/are defined].'),
('000997','draft','2009-09-21','DISA FSO','policy','Review and update the current media protection policy in accordance with organization-defined frequency.','MP-01c.01','N/A','Determine if: - the current media protection policy is reviewed and updated [MP-01_ODP[05]; the frequency with which the current media protection policy is reviewed and updated is defined]. - the current media protection policy is reviewed and updated following [MP-01_ODP[06]; events that would require the current media protection policy to be reviewed and updated are defined].'),
('000998','draft','2009-09-21','DISA FSO','policy','Defines a frequency for reviewing and updating the current media protection policy.','MP-01c.01','N/A','Determine if: - the current media protection policy is reviewed and updated [MP-01_ODP[05]; the frequency with which the current media protection policy is reviewed and updated is defined]. - the current media protection policy is reviewed and updated following [MP-01_ODP[06]; events that would require the current media protection policy to be reviewed and updated are defined].'),
('000999','draft','2009-09-21','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the media protection policy and associated media protection controls.','MP-01a.02','N/A','Determine if: - media protection procedures to facilitate the implementation of the media protection policy and associated media protection controls are developed and documented. - the media protection procedures are disseminated to [MP-01_ODP[02]; personnel or roles to whom the media protection procedures are to be disseminated is/are defined].'),
('001000','draft','2009-09-21','DISA FSO','policy','Disseminate to organization-defined personnel or roles procedures to facilitate the implementation of the media protection policy and associated media protection controls.','MP-01a.02','N/A','Determine if: - media protection procedures to facilitate the implementation of the media protection policy and associated media protection controls are developed and documented. - the media protection procedures are disseminated to [MP-01_ODP[02]; personnel or roles to whom the media protection procedures are to be disseminated is/are defined].'),
('001001','draft','2009-09-21','DISA FSO','policy','Review and update the current media protection procedures in accordance with organization-defined frequency.','MP-01c.02','N/A','Determine if: - the current media protection procedures are reviewed and updated [MP-01_ODP[07]; the frequency with which the current media protection procedures are reviewed and updated is defined]. - the current media protection procedures are reviewed and updated following [MP-01_ODP[08]; events that would require media protection procedures to be reviewed and updated are defined].'),
('001002','draft','2009-09-21','DISA FSO','policy','Defines a frequency for reviewing and updating the current media protection procedures.','MP-01c.02','N/A','Determine if: - the current media protection procedures are reviewed and updated [MP-01_ODP[07]; the frequency with which the current media protection procedures are reviewed and updated is defined]. - the current media protection procedures are reviewed and updated following [MP-01_ODP[08]; events that would require media protection procedures to be reviewed and updated are defined].'),
('001003','draft','2009-09-21','DISA FSO','policy','Restrict access to organization-defined types of digital and/or non-digital media to organization-defined personnel or roles.','MP-02','N/A','Determine if: - access to [MP-02_ODP[01]; types of digital media to which access is restricted are defined] is restricted to [MP-02_ODP[02]; personnel or roles authorized to access digital media is/are defined]. - access to [MP-02_ODP[03]; types of non-digital media to which access is restricted are defined] is restricted to [MP-02_ODP[04]; personnel or roles authorized to access non-digital media is/are defined].'),
('001004','draft','2009-09-21','DISA FSO','policy','Defines types of digital and/or non-digital media for which the organization restricts access.','MP-02','N/A','Determine if: - access to [MP-02_ODP[01]; types of digital media to which access is restricted are defined] is restricted to [MP-02_ODP[02]; personnel or roles authorized to access digital media is/are defined]. - access to [MP-02_ODP[03]; types of non-digital media to which access is restricted are defined] is restricted to [MP-02_ODP[04]; personnel or roles authorized to access non-digital media is/are defined].'),
('001005','draft','2009-09-21','DISA FSO','policy','Defines personnel or roles from which to restrict access to organization-defined types of digital and/or non-digital media.','MP-02','N/A','Determine if: - access to [MP-02_ODP[01]; types of digital media to which access is restricted are defined] is restricted to [MP-02_ODP[02]; personnel or roles authorized to access digital media is/are defined]. - access to [MP-02_ODP[03]; types of non-digital media to which access is restricted are defined] is restricted to [MP-02_ODP[04]; personnel or roles authorized to access non-digital media is/are defined].'),
('001007','draft','2009-09-21','DISA FSO','policy','Restrict access to media storage areas using organization-defined automated mechanisms.','MP-04(02)','N/A','Determine if: - access to media storage areas is restricted using [MP-04(02)_ODP[01]; automated mechanisms to restrict access to media storage areas are defined]. - access attempts to media storage areas are logged using [MP-04(02)_ODP[02]; automated mechanisms to log access attempts to media storage areas are defined]. - access granted to media storage areas is logged using [MP-04(02)_ODP[03]; automated mechanisms to log access granted to media storage areas are defined].'),
('001008','draft','2009-09-21','DISA FSO','policy','Log access attempts and access granted using organization-defined automated mechanisms.','MP-04(02)','N/A','Determine if: - access to media storage areas is restricted using [MP-04(02)_ODP[01]; automated mechanisms to restrict access to media storage areas are defined]. - access attempts to media storage areas are logged using [MP-04(02)_ODP[02]; automated mechanisms to log access attempts to media storage areas are defined]. - access granted to media storage areas is logged using [MP-04(02)_ODP[03]; automated mechanisms to log access granted to media storage areas are defined].'),
('001010','draft','2009-09-21','DISA FSO','policy','Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information.','MP-03a.','N/A','Determine if system media is marked to indicate distribution limitations, handling caveats, and applicable security markings (if any) of the information.'),
('001011','draft','2009-09-21','DISA FSO','policy','Exempt organization-defined types of system media from marking as long as the media remain within organization-defined controlled areas.','MP-03b.','N/A','Determine if [MP-03_ODP[01]; types of system media exempt from marking when remaining in controlled areas are defined] remain within [MP-03_ODP[02]; controlled areas where media is exempt from marking are defined].'),
('001012','draft','2009-09-21','DISA FSO','policy','Defines types of system media to exempt from marking as long as the media remain within organization-defined controlled areas.','MP-03b.','N/A','Determine if [MP-03_ODP[01]; types of system media exempt from marking when remaining in controlled areas are defined] remain within [MP-03_ODP[02]; controlled areas where media is exempt from marking are defined].'),
('001013','draft','2009-09-21','DISA FSO','policy','Defines controlled areas where organization-defined types of system media are exempt from being marked.','MP-03b.','N/A','Determine if [MP-03_ODP[01]; types of system media exempt from marking when remaining in controlled areas are defined] remain within [MP-03_ODP[02]; controlled areas where media is exempt from marking are defined].'),
('001015','draft','2009-09-21','DISA FSO','policy','Defines types of digital and/or non-digital media to physically control and securely store within organization-defined controlled areas.','MP-04a.','N/A','Determine if: - [MP-04_ODP[01]; types of digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[02]; types of non-digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[03]; types of digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[05]; controlled areas within which to securely store digital media are defined]. - [MP-04_ODP[04]; types of non-digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[06]; controlled areas within which to securely store non-digital media are defined].'),
('001016','draft','2009-09-21','DISA FSO','policy','Defines controlled areas where organization-defined types of digital and/or non-digital media are physically controlled and securely stored.','MP-04a.','N/A','Determine if: - [MP-04_ODP[01]; types of digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[02]; types of non-digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[03]; types of digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[05]; controlled areas within which to securely store digital media are defined]. - [MP-04_ODP[04]; types of non-digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[06]; controlled areas within which to securely store non-digital media are defined].'),
('001021','draft','2009-09-21','DISA FSO','policy','Defines types of system media protected and controlled during transport outside of controlled areas.','MP-05a.','N/A','Determine if: - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are protected during transport outside of controlled areas using [MP-05_ODP[02]; controls used to protect system media outside of controlled areas are defined]. - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are controlled during transport outside of controlled areas using [MP-05_ODP[03]; controls used to control system media outside of controlled areas are defined].'),
('001022','draft','2009-09-21','DISA FSO','policy','Defines controls to be used to protect and control organization-defined types of system media during transport outside of controlled areas.','MP-05a.','N/A','Determine if: - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are protected during transport outside of controlled areas using [MP-05_ODP[02]; controls used to protect system media outside of controlled areas are defined]. - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are controlled during transport outside of controlled areas using [MP-05_ODP[03]; controls used to control system media outside of controlled areas are defined].'),
('001023','draft','2009-09-21','DISA FSO','policy','Maintain accountability for system media during transport outside of controlled areas.','MP-05b.','N/A','Determine if accountability for system media is maintained during transport outside of controlled areas.'),
('001024','draft','2009-09-21','DISA FSO','policy','Restrict the activities associated with the transport of system media to authorized personnel.','MP-05d.','N/A','Determine if: - personnel authorized to conduct media transport activities is/are identified. - activities associated with the transport of system media are restricted to identified authorized personnel.'),
('001025','draft','2009-09-21','DISA FSO','policy','Document activities associated with the transport of system media.','MP-05c.','N/A','Determine if activities associated with the transport of system media are documented.'),
('001026','draft','2009-09-21','DISA FSO','policy','Employ an identified custodian during transport of system media outside of controlled areas.','MP-05(03)','N/A','Determine if: - a custodian to transport system media outside of controlled areas is identified. - the identified custodian is employed during the transport of system media outside of controlled areas.'),
('001028','draft','2009-09-21','DISA FSO','policy','Sanitize organization-defined system media prior to disposal, release out of organizational control, or release for reuse using organization-defined sanitization techniques and procedures.','MP-06a.','N/A','Determine if: - [MP-06_ODP[01]; system media to be sanitized prior to disposal is defined] is sanitized using [MP-06_ODP[04]; sanitization techniques and procedures to be used for sanitization prior to disposal are defined] prior to disposal. - [MP-06_ODP[02]; system media to be sanitized prior to release from organizational control is defined] is sanitized using [MP-06_ODP[05]; sanitization techniques and procedures to be used for sanitization prior to release from organizational control are defined] prior to release from organizational control. - [MP-06_ODP[03]; system media to be sanitized prior to release for reuse is defined] is sanitized using [MP-06_ODP[06]; sanitization techniques and procedures to be used for sanitization prior to release for reuse are defined] prior to release for reuse.'),
('001031','draft','2009-09-21','DISA FSO','policy','Defines a frequency for testing sanitization equipment and procedures to ensure that the intended sanitization is being achieved.','MP-06(02)','N/A','Determine if: - sanitization equipment is tested [MP-06(02)_ODP[01]; frequency with which to test sanitization equipment is defined] to ensure that the intended sanitization is being achieved. - sanitization procedures are tested [MP-06(02)_ODP[02]; frequency with which to test sanitization procedures is defined] to ensure that the intended sanitization is being achieved.'),
('001032','draft','2009-09-21','DISA FSO','policy','Apply nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the system in accordance with organization-defined circumstances requiring sanitization of portable storage devices.','MP-06(03)','N/A','Determine if non-destructive sanitization techniques are applied to portable storage devices prior to connecting such devices to the system under [MP-06(03)_ODP; circumstances requiring sanitization of portable storage devices are defined].'),
('001033','draft','2009-09-21','DISA FSO','policy','Defines circumstances requiring sanitization of portable storage devices prior to connecting such devices to the system.','MP-06(03)','N/A','Determine if non-destructive sanitization techniques are applied to portable storage devices prior to connecting such devices to the system under [MP-06(03)_ODP; circumstances requiring sanitization of portable storage devices are defined].'),
('001037','draft','2009-09-21','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; system-level risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','RA-01a.01(a)','N/A','Determine if: - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses purpose. - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses scope. - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses roles. - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses responsibilities. - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses management commitment. - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses coordination among organizational entities. - the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy addresses compliance.'),
('001038','draft','2009-09-21','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; system-level risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance to organization-defined personnel or roles.','RA-01a.','N/A','Determine if: - a risk assessment policy is developed and documented. - the risk assessment policy is disseminated to [RA-01_ODP[01; personnel or roles to whom the risk assessment policy is to be disseminated is/are defined].'),
('001039','draft','2009-09-21','DISA FSO','policy','Review and update the current risk assessment policy in accordance with organization-defined frequency.','RA-01c.01','N/A','Determine if: - the current risk assessment policy is reviewed and updated [RA-01_ODP[05]; the frequency at which the current risk assessment policy is reviewed and updated is defined]. - the current risk assessment policy is reviewed and updated following [RA-01_ODP[06]; events that would require the current risk assessment policy to be reviewed and updated are defined].'),
('001040','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review and update the current risk assessment policy.','RA-01c.01','N/A','Determine if: - the current risk assessment policy is reviewed and updated [RA-01_ODP[05]; the frequency at which the current risk assessment policy is reviewed and updated is defined]. - the current risk assessment policy is reviewed and updated following [RA-01_ODP[06]; events that would require the current risk assessment policy to be reviewed and updated are defined].'),
('001041','draft','2009-09-21','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls.','RA-01a.02','N/A','Determine if: - risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls are developed and documented. - the risk assessment procedures are disseminated to [RA-01_ODP[02]; personnel or roles to whom the risk assessment procedures are to be disseminated is/are defined].'),
('001042','draft','2009-09-21','DISA FSO','policy','Disseminate risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls to organization-defined personnel or roles.','RA-01a.02','N/A','Determine if: - risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls are developed and documented. - the risk assessment procedures are disseminated to [RA-01_ODP[02]; personnel or roles to whom the risk assessment procedures are to be disseminated is/are defined].'),
('001043','draft','2009-09-21','DISA FSO','policy','Review and update the current risk assessment procedures in accordance with organization-defined frequency.','RA-01c.02','N/A','Determine if: - the current risk assessment procedures are reviewed and updated [RA-01_ODP[07]; the frequency at which the current risk assessment procedures are reviewed and updated is defined]. - the current risk assessment procedures are reviewed and updated following [RA-01_ODP[08]; events that would require risk assessment procedures to be reviewed and updated are defined].'),
('001044','draft','2009-09-21','DISA FSO','policy','Defines the frequency with which to review and update the current risk assessment procedures.','RA-01c.02','N/A','Determine if: - the current risk assessment procedures are reviewed and updated [RA-01_ODP[07]; the frequency at which the current risk assessment procedures are reviewed and updated is defined]. - the current risk assessment procedures are reviewed and updated following [RA-01_ODP[08]; events that would require risk assessment procedures to be reviewed and updated are defined].'),
('001046','draft','2009-09-21','DISA FSO','policy','Document the security categorization results including supporting rationale in the security plan for the system.','RA-02b.','N/A','Determine if the security categorization results, including supporting rationale, are documented in the security plan for the system.'),
('001047','draft','2009-09-21','DISA FSO','policy','Verify the security categorization decision is reviewed and approved by the authorizing official or authorizing official designated representative.','RA-02c.','N/A','Determine if the authorizing official or authorizing official designated representative reviews and approves the security categorization decision.'),
('001048','draft','2009-09-21','DISA FSO','policy','Conduct a risk assessment, including determining the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, stores, or transmits, and any related information.','RA-03a.02','N/A','Determine if a risk assessment is conducted to determine the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system; the information it processes, stores, or transmits; and any related information.'),
('001049','draft','2009-09-21','DISA FSO','policy','Document risk assessment results in the organization-defined document.','RA-03c.','N/A','Determine if risk assessment results are documented in [RA-03_ODP[01]; one of the following PARAMETER VALUES is selected: {security and privacy plans; risk assessment report; [RA-03_ODP[02]; a document in which risk assessment results are to be documented (if not documented in the security and privacy plans or risk assessment report) is defined (if selected)]}].'),
('001050','draft','2009-09-21','DISA FSO','policy','Review risk assessment results on an organization-defined frequency.','RA-03d.','N/A','Determine if risk assessment results are reviewed [RA-03_ODP[03]; the frequency to review risk assessment results is defined].'),
('001051','draft','2009-09-21','DISA FSO','policy','Defines a frequency for reviewing risk assessment results.','RA-03d.','N/A','Determine if risk assessment results are reviewed [RA-03_ODP[03]; the frequency to review risk assessment results is defined].'),
('001052','draft','2009-09-21','DISA FSO','policy','Update the risk assessment on an organization-defined frequency or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.','RA-03f.','N/A','Determine if the risk assessment is updated [RA-03_ODP[05]; the frequency to update the risk assessment is defined] or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.'),
('001053','draft','2009-09-21','DISA FSO','policy','Defines a frequency for updating the risk assessment.','RA-03f.','N/A','Determine if the risk assessment is updated [RA-03_ODP[05]; the frequency to update the risk assessment is defined] or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.'),
('001054','draft','2009-09-21','DISA FSO','policy','Monitor and scan for vulnerabilities in the system and hosted applications on an organization-defined frequency and/or randomly in accordance with organization-defined process.','RA-05a.','N/A','Determine if: - systems and hosted applications are monitored for vulnerabilities [RA-05_ODP[01]; frequency for monitoring systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported. - systems and hosted applications are scanned for vulnerabilities [RA-05_ODP[02]; frequency for scanning systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported.'),
('001055','draft','2009-09-21','DISA FSO','policy','Defines a frequency for scanning for vulnerabilities in the system and hosted applications, and/or randomly in accordance with organization-defined process.','RA-05a.','N/A','Determine if: - systems and hosted applications are monitored for vulnerabilities [RA-05_ODP[01]; frequency for monitoring systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported. - systems and hosted applications are scanned for vulnerabilities [RA-05_ODP[02]; frequency for scanning systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported.'),
('001056','draft','2009-09-21','DISA FSO','policy','Monitor and scan for vulnerabilities in the system and hosted applications when new vulnerabilities potentially affecting the system/applications are identified and reported.','RA-05a.','N/A','Determine if: - systems and hosted applications are monitored for vulnerabilities [RA-05_ODP[01]; frequency for monitoring systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported. - systems and hosted applications are scanned for vulnerabilities [RA-05_ODP[02]; frequency for scanning systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported.'),
('001057','draft','2009-09-21','DISA FSO','policy','Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: enumerating platforms, software flaws, and improper configurations.','RA-05b.01','N/A','Determine if vulnerability monitoring tools and techniques are employed to automate parts of the vulnerability management process by using standards for enumerating platforms, software flaws, and improper configurations.'),
('001058','draft','2009-09-21','DISA FSO','policy','Analyze vulnerability scan reports and results from vulnerability monitoring.','RA-05c.','N/A','Determine if vulnerability scan reports and results from vulnerability monitoring are analyzed.'),
('001059','draft','2009-09-21','DISA FSO','policy','Remediate legitimate vulnerabilities in organization-defined response times in accordance with an organizational assessment risk.','RA-05d.','N/A','Determine if legitimate vulnerabilities are remediated [RA-05_ODP[03]; response times to remediate legitimate vulnerabilities in accordance with an organizational assessment of risk are defined] in accordance with an organizational assessment of risk.'),
('001060','draft','2009-09-21','DISA FSO','policy','Defines response times for remediating legitimate vulnerabilities in accordance with an organization assessment of risk.','RA-05d.','N/A','Determine if legitimate vulnerabilities are remediated [RA-05_ODP[03]; response times to remediate legitimate vulnerabilities in accordance with an organizational assessment of risk are defined] in accordance with an organizational assessment of risk.'),
('001061','draft','2009-09-21','DISA FSO','policy','Share information obtained from the vulnerability monitoring process and control assessments with organization-defined personnel or roles to help eliminate similar vulnerabilities in other systems.','RA-05e.','N/A','Determine if information obtained from the vulnerability monitoring process and control assessments is shared with [RA-05_ODP[04]; personnel or roles with whom information obtained from the vulnerability scanning process and control assessments is to be shared] to help eliminate similar vulnerabilities in other systems.'),
('001063','draft','2009-09-21','DISA FSO','policy','Update the system vulnerabilities scanned on an organization-defined frequency, prior to a new scan, and/or when new vulnerabilities are identified and reported.','RA-05(02)','N/A','Determine if the system vulnerabilities to be scanned are updated [RA-05(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[RA-05(02)_ODP[02]; the frequency for updating the system vulnerabilities to be scanned is defined (if selected)]; prior to a new scan; when new vulnerabilities are identified and reported}].'),
('001064','draft','2009-09-21','DISA FSO','policy','Defines a frequency for updating the system vulnerabilities scanned.','RA-05(02)','N/A','Determine if the system vulnerabilities to be scanned are updated [RA-05(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[RA-05(02)_ODP[02]; the frequency for updating the system vulnerabilities to be scanned is defined (if selected)]; prior to a new scan; when new vulnerabilities are identified and reported}].'),
('001066','draft','2009-09-21','DISA FSO','policy','Determine information about the system that is discoverable.','RA-05(04)','N/A','Determine if: - information about the system is discoverable. - [RA-05(04)_ODP; corrective actions to be taken if information about the system is discoverable are defined] are taken when information about the system is confirmed as discoverable.'),
('001067','draft','2009-09-21','DISA FSO','technical','Implement privileged access authorization to organization-identified system components for organization-defined vulnerability scanning activities.','RA-05(05)','N/A','Determine if privileged access authorization is implemented to [RA-05(05)_ODP[01]; system components to which privileged access is authorized for selected vulnerability scanning activities are defined] for [RA-05(05)_ODP[02]; vulnerability scanning activities selected for privileged access authorization to system components are defined].'),
('001068','draft','2009-09-21','DISA FSO','policy','Compare the results of multiple vulnerability scans using organization-defined automated mechanisms.','RA-05(06)','N/A','Determine if the results of multiple vulnerability scans are compared using [RA-05(06)_ODP; automated mechanisms to compare the results of multiple vulnerability scans are defined].'),
('001071','draft','2009-09-21','DISA FSO','policy','Review historic audit logs to determine if a vulnerability identified in the organization-defined system has been previously exploited within an organization-defined time period.','RA-05(08)','N/A','Determine if historic audit logs are reviewed to determine if a vulnerability identified in a [RA-05(08)_ODP[01]; a system whose historic audit logs are to be reviewed is defined] has been previously exploited within [RA-05(08)_ODP[02]; a time period for a potential previous exploit of a system is defined].'),
('001075','draft','2009-09-21','DISA FSO','policy','Disseminates to organization-defined personnel or roles the organization-level; mission/business process-level; and/or system-level system and communications protection policy.','SC-01a.','N/A','Determine if: - a system and communications protection policy is developed and documented. - the system and communications protection policy is disseminated to [SC-01_ODP[01]; personnel or roles to whom the system and communications protection policy is to be disseminated is/are defined].'),
('001076','draft','2009-09-21','DISA FSO','policy','Review and update the current system and communications protection policy in accordance with organization-defined frequency.','SC-01c.01','N/A','Determine if: - the current system and communications protection policy is reviewed and updated [SC-01_ODP[05]; the frequency at which the current system and communications protection policy is reviewed and updated is defined]. - the current system and communications protection policy is reviewed and updated following [SC-01_ODP[06]; events that would require the current system and communications protection policy to be reviewed and updated are defined].'),
('001077','draft','2009-09-21','DISA FSO','policy','Defines the frequency for reviewing and updating the current system and communications protection policy.','SC-01c.01','N/A','Determine if: - the current system and communications protection policy is reviewed and updated [SC-01_ODP[05]; the frequency at which the current system and communications protection policy is reviewed and updated is defined]. - the current system and communications protection policy is reviewed and updated following [SC-01_ODP[06]; events that would require the current system and communications protection policy to be reviewed and updated are defined].'),
('001079','draft','2009-09-21','DISA FSO','policy','Disseminates to organization-defined personnel or roles the procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','SC-01a.02','N/A','Determine if: - system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls are developed and documented. - the system and communications protection procedures are disseminated to [SC-01_ODP[02]; personnel or roles to whom the system and communications protection procedures are to be disseminated is/are defined].'),
('001080','draft','2009-09-21','DISA FSO','policy','Review and update the current system and communications protection procedures in accordance with organization-defined frequency.','SC-01c.02','N/A','Determine if: - the current system and communications protection procedures are reviewed and updated [SC-01_ODP[07]; the frequency at which the current system and communications protection procedures are reviewed and updated is defined]. - the current system and communications protection procedures are reviewed and updated following [SC-01_ODP[08]; events that would require the system and communications protection procedures to be reviewed and updated are defined].'),
('001081','draft','2009-09-21','DISA FSO','policy','Defines the frequency for reviewing and updating the current system and communications protection procedures.','SC-01c.02','N/A','Determine if: - the current system and communications protection procedures are reviewed and updated [SC-01_ODP[07]; the frequency at which the current system and communications protection procedures are reviewed and updated is defined]. - the current system and communications protection procedures are reviewed and updated following [SC-01_ODP[08]; events that would require the system and communications protection procedures to be reviewed and updated are defined].'),
('001082','draft','2009-09-21','DISA FSO','technical','Separate user functionality, including user interface services, from system management functionality.','SC-02','N/A','Determine if user functionality, including user interface services, is separated from system management functionality.'),
('001083','draft','2009-09-21','DISA FSO','technical','Prevent the presentation of system management functionality at an interface for non-privileged users.','SC-02(01)','N/A','Determine if the presentation of system management functionality is prevented at interfaces to non-privileged users.'),
('001084','draft','2009-09-21','DISA FSO','technical','Isolate security functions from nonsecurity functions.','SC-03','N/A','Determine if security functions are isolated from non-security functions.'),
('001085','draft','2009-09-21','DISA FSO','technical','Employ hardware separation mechanisms to implement security function isolation.','SC-03(01)','N/A','Determine if hardware separation mechanisms are employed to implement security function isolation.'),
('001086','draft','2009-09-21','DISA FSO','technical','Isolate security functions enforcing access and information flow control from both nonsecurity functions and from other security functions.','SC-03(02)','N/A','Determine if: - security functions enforcing access control are isolated from non-security functions. - security functions enforcing access control are isolated from other security functions. - security functions enforcing information flow control are isolated from non-security functions. - security functions enforcing information flow control are isolated from other security functions.'),
('001089','draft','2009-09-21','DISA FSO','technical','Implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.','SC-03(05)','N/A','Determine if security functions are implemented as a layered structure, minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.'),
('001090','draft','2009-09-21','DISA FSO','technical','Prevent unauthorized and unintended information transfer via shared system resources.','SC-04','N/A','Determine if: - unauthorized information transfer via shared system resources is prevented. - unintended information transfer via shared system resources is prevented.'),
('001093','draft','2009-09-21','DISA FSO','policy','Defines the types of denial-of-service events for protecting against or limiting the effects of the denial-of-service events.','SC-05a.','N/A','Determine if the effects of [SC-05_ODP[01]; types of denial-of-service events to be protected against or limited are defined] are [SC-05_ODP[02]; one of the following PARAMETER VALUES is selected: {protect against; limit}].'),
('001094','draft','2009-09-21','DISA FSO','technical','Restrict the ability of individuals to launch organization-defined denial of service attacks against other systems.','SC-05(01)','N/A','Determine if the ability of individuals to launch [SC-05(01)_ODP; denial-of-service attacks for which to restrict the ability of individuals to launch are defined] against other systems is restricted.'),
('001095','draft','2009-09-21','DISA FSO','technical','Manage capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial-of-service attacks.','SC-05(02)','N/A','Determine if capacity, bandwidth, or other redundancies to limit the effects of information flooding denial-of-service attacks are managed.'),
('001097','draft','2009-09-21','DISA FSO','policy','Monitor and control communications at the external managed interfaces to the system and at key managed interfaces within the system.','SC-07a.','N/A','Determine if: - communications at external managed interfaces to the system are monitored. - communications at external managed interfaces to the system are controlled. - communications at key internal managed interfaces within the system are monitored. - communications at key internal managed interfaces within the system are controlled.'),
('001098','draft','2009-09-21','DISA FSO','policy','Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture.','SC-07c.','N/A','Determine if external networks or systems are only connected to through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.'),
('001101','draft','2009-09-21','DISA FSO','policy','Limit the number of external network connections to the system.','SC-07(03)','N/A','Determine if the number of external network connections to the system is limited.'),
('001102','draft','2009-09-21','DISA FSO','policy','Implement a managed interface for each external telecommunication service.','SC-07(04)(a)','N/A','Determine if a managed interface is implemented for each external telecommunication service.'),
('001103','draft','2009-09-21','DISA FSO','policy','Establish a traffic flow policy for each managed interface for each external telecommunication service.','SC-07(04)(b)','N/A','Determine if a traffic flow policy is established for each managed interface.'),
('001105','draft','2009-09-21','DISA FSO','policy','Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need.','SC-07(04)(d)','N/A','Determine if each exception to the traffic flow policy is documented with a supporting mission or business need and duration of that need.'),
('001106','draft','2009-09-21','DISA FSO','policy','Review exceptions to the traffic flow policy on an organization-defined frequency for each external telecommunication service.','SC-07(04)(e)','N/A','Determine if: - exceptions to the traffic flow policy are reviewed [SC-07(04)_ODP; the frequency at which to review exceptions to traffic flow policy is defined]. - exceptions to the traffic flow policy that are no longer supported by an explicit mission or business need are removed.'),
('001107','draft','2009-09-21','DISA FSO','policy','Defines a frequency for the review of exceptions to the traffic flow policy for each external telecommunication service.','SC-07(04)(e)','N/A','Determine if: - exceptions to the traffic flow policy are reviewed [SC-07(04)_ODP; the frequency at which to review exceptions to traffic flow policy is defined]. - exceptions to the traffic flow policy that are no longer supported by an explicit mission or business need are removed.'),
('001108','draft','2009-09-21','DISA FSO','policy','Remove traffic flow policy exceptions that are no longer supported by an explicit mission or business need for each external telecommunication service.','SC-07(04)(e)','N/A','Determine if: - exceptions to the traffic flow policy are reviewed [SC-07(04)_ODP; the frequency at which to review exceptions to traffic flow policy is defined]. - exceptions to the traffic flow policy that are no longer supported by an explicit mission or business need are removed.'),
('001109','draft','2009-09-21','DISA FSO','technical','Deny network communications traffic by default and allow network communications traffic by exception at managed interfaces; and/or for organization-defined systems.','SC-07(05)','N/A','Determine if: - network communications traffic is denied by default [SC-07(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {at managed interfaces; for [SC-07(05)_ODP[02]; systems for which network communications traffic is denied by default and network communications traffic is allowed by exception are defined (if selected)]}]. - network communications traffic is allowed by exception [SC-07(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {at managed interfaces; for [SC-07(05)_ODP[02]; systems for which network communications traffic is denied by default and network communications traffic is allowed by exception are defined (if selected)]}].'),
('001112','draft','2009-09-21','DISA FSO','policy','Route organization-defined internal communications traffic to organization-defined external networks through authenticated proxy servers at managed interfaces.','SC-07(08)','N/A','Determine if [SC-07(08)_ODP[01]; internal communications traffic to be routed to external networks is defined] is routed to [SC-07(08)_ODP[02]; external networks to which internal communications traffic is to be routed are defined] through authenticated proxy servers at managed interfaces.'),
('001113','draft','2009-09-21','DISA FSO','policy','Defines the internal communications traffic to be routed to external networks.','SC-07(08)','N/A','Determine if [SC-07(08)_ODP[01]; internal communications traffic to be routed to external networks is defined] is routed to [SC-07(08)_ODP[02]; external networks to which internal communications traffic is to be routed are defined] through authenticated proxy servers at managed interfaces.'),
('001114','draft','2009-09-21','DISA FSO','policy','Defines the external networks to which organization-defined internal communications traffic should be routed.','SC-07(08)','N/A','Determine if [SC-07(08)_ODP[01]; internal communications traffic to be routed to external networks is defined] is routed to [SC-07(08)_ODP[02]; external networks to which internal communications traffic is to be routed are defined] through authenticated proxy servers at managed interfaces.'),
('001116','draft','2009-09-21','DISA FSO','policy','Prevent the exfiltration of information.','SC-07(10)(a)','N/A','Determine if the exfiltration of information is prevented.'),
('001119','draft','2009-09-21','DISA FSO','policy','Isolate organization-defined information security tools, mechanisms, and support components from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.','SC-07(13)','N/A','Determine if [SC-07(13)_ODP; information security tools, mechanisms, and support components to be isolated from other internal system components are defined] are isolated from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.'),
('001120','draft','2009-09-21','DISA FSO','policy','Defines the information security tools, mechanisms, and support components to be isolated.','SC-07(13)','N/A','Determine if [SC-07(13)_ODP; information security tools, mechanisms, and support components to be isolated from other internal system components are defined] are isolated from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.'),
('001121','draft','2009-09-21','DISA FSO','policy','Protect against unauthorized physical connections at organization-defined managed interfaces.','SC-07(14)','N/A','Determine if [SC-07(14)_ODP; managed interfaces to be protected against unauthorized physical connections are defined] are protected against unauthorized physical connections.'),
('001123','draft','2009-09-21','DISA FSO','policy','Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.','SC-07(15)','N/A','Determine if: - networked, privileged accesses are routed through a dedicated, managed interface for purposes of access control. - networked, privileged accesses are routed through a dedicated, managed interface for purposes of auditing.'),
('001124','draft','2009-09-21','DISA FSO','technical','Prevent discovery of specific system components that represent a managed interface.','SC-07(16)','N/A','Determine if the discovery of specific system components that represent a managed interface is prevented.'),
('001125','draft','2009-09-21','DISA FSO','technical','Enforce adherence to protocol formats.','SC-07(17)','N/A','Determine if adherence to protocol formats is enforced.'),
('001126','draft','2009-09-21','DISA FSO','technical','Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device.','SC-07(18)','N/A','Determine if systems are prevented from entering unsecure states in the event of an operational failure of a boundary protection device.'),
('001133','draft','2009-09-21','DISA FSO','technical','Terminate the network connection associated with a communications session at the end of the session or after an organization-defined time period of inactivity.','SC-10','N/A','Determine if the network connection associated with a communication session is terminated at the end of the session or after [SC-10_ODP; a time period of inactivity after which the system terminates a network connection associated with a communication session is defined] of inactivity.'),
('001134','draft','2009-09-21','DISA FSO','policy','Defines the time period of inactivity after which the system terminates a network connection associated with a communications session.','SC-10','N/A','Determine if the network connection associated with a communication session is terminated at the end of the session or after [SC-10_ODP; a time period of inactivity after which the system terminates a network connection associated with a communication session is defined] of inactivity.'),
('001135','draft','2009-09-21','DISA FSO','policy','Provide a physically or logically isolated trusted communication path for communication between the user and the trusted components of the system.','SC-11a.','N/A','Determine if a [SC-11_ODP[01]; one of the following PARAMETER VALUES is selected: {physically; logically}] isolated trusted communication path is provided for communications between the user and the trusted components of the system.'),
('001139','draft','2009-09-21','DISA FSO','policy','Maintain availability of information in the event of the loss of cryptographic keys by users.','SC-12(01)','N/A','Determine if information availability is maintained in the event of the loss of cryptographic keys by users.'),
('001150','draft','2009-09-21','DISA FSO','technical','Prohibit remote activation of collaborative computing devices and applications, excluding the organization-defined exceptions where remote activation is to be allowed.','SC-15a.','N/A','Determine if remote activation of collaborative computing devices and applications is prohibited except [SC-15_ODP; exceptions where remote activation is to be allowed are defined].'),
('001151','draft','2009-09-21','DISA FSO','policy','Defines exceptions to the prohibition of collaborative computing devices where remote activation is to be allowed.','SC-15a.','N/A','Determine if remote activation of collaborative computing devices and applications is prohibited except [SC-15_ODP; exceptions where remote activation is to be allowed are defined].'),
('001152','draft','2009-09-21','DISA FSO','technical','Provide an explicit indication of use to users physically present at collaborative computing devices.','SC-15b.','N/A','Determine if an explicit indication of use is provided to users physically present at the devices.'),
('001153','draft','2009-09-21','DISA FSO','technical','Provide physical or logical disconnect of collaborative computing devices in a manner that supports ease of use.','SC-15(01)','N/A','Determine if the [SC-15(01)_ODP; one or more of the following PARAMETER VALUES is/are selected: {physical; logical}] disconnect of collaborative computing devices is/are provided in a manner that supports ease of use.'),
('001155','draft','2009-09-21','DISA FSO','policy','Disable or remove collaborative computing devices and applications from organization-defined systems or system components in organization-defined secure work areas.','SC-15(03)','N/A','Determine if collaborative computing devices and applications are disabled or removed from [SC-15(03)_ODP[01]; systems or system components from which collaborative computing devices are to be disabled or removed are defined] in [SC-15(03)_ODP[02]; secure work areas where collaborative computing devices are to be disabled or removed from systems or system components are defined].'),
('001156','draft','2009-09-21','DISA FSO','policy','Defines secure work areas where collaborative computing devices and applications are to be disabled or removed.','SC-15(03)','N/A','Determine if collaborative computing devices and applications are disabled or removed from [SC-15(03)_ODP[01]; systems or system components from which collaborative computing devices are to be disabled or removed are defined] in [SC-15(03)_ODP[02]; secure work areas where collaborative computing devices are to be disabled or removed from systems or system components are defined].'),
('001157','draft','2009-09-21','DISA FSO','policy','Associate organization-defined security attributes with information exchanged between systems.','SC-16','N/A','Determine if: - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between system components. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between system components.'),
('001158','draft','2009-09-21','DISA FSO','technical','Verify the integrity of transmitted security attributes.','SC-16(01)','N/A','Determine if: - the integrity of transmitted security attributes is verified. - the integrity of transmitted privacy attributes is verified.'),
('001159','draft','2009-09-21','DISA FSO','policy','Issue public key certificates under an organization-defined certificate policy or obtain public key certificates from an approved service provider.','SC-17a.','N/A','Determine if public key certificates are issued under [SC-17_ODP; a certificate policy for issuing public key certificates is defined], or public key certificates are obtained from an approved service provider.'),
('001160','draft','2009-09-21','DISA FSO','policy','Defines acceptable and unacceptable mobile code and mobile code technologies.','SC-18a.','N/A','Determine if: - acceptable mobile code is defined. - unacceptable mobile code is defined. - acceptable mobile code technologies are defined. - unacceptable mobile code technologies are defined.'),
('001163','draft','2009-09-21','DISA FSO','policy','Authorize the use of mobile code within the system.','SC-18b.','N/A','Determine if: - the use of mobile code is authorized within the system. - the use of mobile code is monitored within the system. - the use of mobile code is controlled within the system.'),
('001164','draft','2009-09-21','DISA FSO','policy','Monitor the use of mobile code within the system.','SC-18b.','N/A','Determine if: - the use of mobile code is authorized within the system. - the use of mobile code is monitored within the system. - the use of mobile code is controlled within the system.'),
('001165','draft','2009-09-21','DISA FSO','policy','Control the use of mobile code within the system.','SC-18b.','N/A','Determine if: - the use of mobile code is authorized within the system. - the use of mobile code is monitored within the system. - the use of mobile code is controlled within the system.'),
('001166','draft','2009-09-21','DISA FSO','technical','Identify organization-defined unacceptable mobile code.','SC-18(01)','N/A','Determine if: - [SC-18(01)_ODP[01]; unacceptable mobile code to be identified is defined] is identified. - [SC-18(01)_ODP[02]; corrective actions to be taken when unacceptable mobile code is identified are defined] are taken if unacceptable mobile code is identified.'),
('001167','draft','2009-09-21','DISA FSO','policy','Verify that the development of mobile code to be deployed in information systems meets organization-defined mobile code requirements.','SC-18(02)','N/A','Determine if: - the acquisition of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the development of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the use of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined].'),
('001168','draft','2009-09-21','DISA FSO','policy','Defines mobile code requirements for the acquisition, development, and use of mobile code.','SC-18(02)','N/A','Determine if: - the acquisition of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the development of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the use of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined].'),
('001169','draft','2009-09-21','DISA FSO','technical','Prevent the download of organization-defined unacceptable mobile code.','SC-18(03)','N/A','Determine if: - the download of [SC-18(03)_ODP; unacceptable mobile code to be prevented from downloading and executing is defined] is prevented. - the execution of [SC-18(03)_ODP; unacceptable mobile code to be prevented from downloading and executing is defined] is prevented.'),
('001170','draft','2009-09-21','DISA FSO','technical','Prevents the automatic execution of mobile code in organization-defined software applications.','SC-18(04)','N/A','Determine if: - the automatic execution of mobile code in [SC-18(04)_ODP[01]; software applications in which the automatic execution of mobile code is to be prevented are defined] is prevented. - [SC-18(04)_ODP[02]; actions to be enforced by the system prior to executing mobile code are defined] are enforced prior to executing mobile code.'),
('001171','draft','2009-09-21','DISA FSO','policy','Defines software applications in which automatic mobile code execution is to be prohibited.','SC-18(04)','N/A','Determine if: - the automatic execution of mobile code in [SC-18(04)_ODP[01]; software applications in which the automatic execution of mobile code is to be prevented are defined] is prevented. - [SC-18(04)_ODP[02]; actions to be enforced by the system prior to executing mobile code are defined] are enforced prior to executing mobile code.'),
('001172','draft','2009-09-21','DISA FSO','policy','Defines actions to be enforced before executing mobile code.','SC-18(04)','N/A','Determine if: - the automatic execution of mobile code in [SC-18(04)_ODP[01]; software applications in which the automatic execution of mobile code is to be prevented are defined] is prevented. - [SC-18(04)_ODP[02]; actions to be enforced by the system prior to executing mobile code are defined] are enforced prior to executing mobile code.'),
('001178','draft','2009-09-21','DISA FSO','technical','Provide additional data origin authentication artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries.','SC-20a.','N/A','Determine if: - additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries. - integrity verification artifacts are provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries.'),
('001179','draft','2009-09-21','DISA FSO','technical','Provides the means to indicate the security status of child zones, when operating as part of a distributed, hierarchical namespace.','SC-20b.','N/A','Determine if: - the means to indicate the security status of child zones (and if the child supports secure resolution services) is provided when operating as part of a distributed, hierarchical namespace. - the means to enable verification of a chain of trust among parent and child domains when operating as part of a distributed, hierarchical namespace is provided.'),
('001182','draft','2009-09-21','DISA FSO','policy','Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant.','SC-22','N/A','Determine if: - the systems that collectively provide name/address resolution services for an organization are fault-tolerant. - the systems that collectively provide name/address resolution services for an organization implement internal role separation. - the systems that collectively provide name/address resolution services for an organization implement external role separation.'),
('001183','draft','2009-09-21','DISA FSO','policy','Ensure the systems that collectively provide name/address resolution service for an organization implement internal/external role separation.','SC-22','N/A','Determine if: - the systems that collectively provide name/address resolution services for an organization are fault-tolerant. - the systems that collectively provide name/address resolution services for an organization implement internal role separation. - the systems that collectively provide name/address resolution services for an organization implement external role separation.'),
('001184','draft','2009-09-21','DISA FSO','technical','Protect the authenticity of communications sessions.','SC-23','N/A','Determine if the authenticity of communication sessions is protected.'),
('001185','draft','2009-09-21','DISA FSO','technical','Invalidate session identifiers upon user logout or other session termination.','SC-23(01)','N/A','Determine if session identifiers are invalidated upon user logout or other session termination.'),
('001188','draft','2009-09-21','DISA FSO','technical','Generate a unique session identifier for each session with organization-defined randomness requirements.','SC-23(03)','N/A','Determine if: - a unique session identifier is generated for each session with [SC-23(03)_ODP; randomness requirements for generating a unique session identifier for each session are defined]. - only system-generated session identifiers are recognized.'),
('001189','draft','2009-09-21','DISA FSO','policy','Defines randomness requirements for generating unique session identifiers.','SC-23(03)','N/A','Determine if: - a unique session identifier is generated for each session with [SC-23(03)_ODP; randomness requirements for generating a unique session identifier for each session are defined]. - only system-generated session identifiers are recognized.'),
('001190','draft','2009-09-21','DISA FSO','technical','Fail to an organization-defined known-system state for the list of organization-defined types of system failures on organization-defined system components on the indicated components while preserving organization-defined system state information in failure.','SC-24','N/A','Determine if [SC-24_ODP[01]; types of system failures for which the system components fail to a known state are defined] fail to a [SC-24_ODP[02]; known system state to which system components fail in the event of a system failure is defined] while preserving [SC-24_ODP[03]; system state information to be preserved in the event of a system failure is defined] in failure.'),
('001191','draft','2009-09-21','DISA FSO','policy','Defines the known system state the system should fail to in the event of an organization-defined system failure.','SC-24','N/A','Determine if [SC-24_ODP[01]; types of system failures for which the system components fail to a known state are defined] fail to a [SC-24_ODP[02]; known system state to which system components fail in the event of a system failure is defined] while preserving [SC-24_ODP[03]; system state information to be preserved in the event of a system failure is defined] in failure.'),
('001192','draft','2009-09-21','DISA FSO','policy','Defines types of system failures for which should fail to an organization-defined known system state.','SC-24','N/A','Determine if [SC-24_ODP[01]; types of system failures for which the system components fail to a known state are defined] fail to a [SC-24_ODP[02]; known system state to which system components fail in the event of a system failure is defined] while preserving [SC-24_ODP[03]; system state information to be preserved in the event of a system failure is defined] in failure.'),
('001193','draft','2009-09-21','DISA FSO','policy','Defines system state information that should be preserved in the event of a system failure.','SC-24','N/A','Determine if [SC-24_ODP[01]; types of system failures for which the system components fail to a known state are defined] fail to a [SC-24_ODP[02]; known system state to which system components fail in the event of a system failure is defined] while preserving [SC-24_ODP[03]; system state information to be preserved in the event of a system failure is defined] in failure.'),
('001194','draft','2009-09-21','DISA FSO','policy','Employ minimal functionality and information storage on organization-defined information system components.','SC-25','N/A','Determine if: - minimal functionality for [SC-25_ODP; system components to be employed with minimal functionality and information storage are defined] is employed. - minimal information storage on [SC-25_ODP; system components to be employed with minimal functionality and information storage are defined] is allocated.'),
('001195','draft','2009-09-21','DISA FSO','policy','Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.','SC-26','N/A','Determine if: - components within organizational systems specifically designed to be the target of malicious attacks are included to detect such attacks. - components within organizational systems specifically designed to be the target of malicious attacks are included to deflect such attacks. - components within organizational systems specifically designed to be the target of malicious attacks are included to analyze such attacks.'),
('001196','draft','2009-09-21','DISA FSO','policy','Include system components that proactively seek to identify network-based malicious code or malicious websites.','SC-35','N/A','Determine if system components that proactively seek to identify network-based malicious code or malicious websites are included.'),
('001197','draft','2009-09-21','DISA FSO','policy','Include within organizational systems organization-defined platform-independent applications.','SC-27','N/A','Determine if [SC-27_ODP; platform-independent applications to be included within organizational systems are defined] are included within organizational systems.'),
('001198','draft','2009-09-21','DISA FSO','policy','Defines applications that are platform independent.','SC-27','N/A','Determine if [SC-27_ODP; platform-independent applications to be included within organizational systems are defined] are included within organizational systems.'),
('001199','draft','2009-09-21','DISA FSO','technical','Protects the confidentiality and/or integrity of organization-defined information at rest.','SC-28','N/A','Determine if the [SC-28_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] of [SC-28_ODP[02]; information at rest requiring protection is defined] is/are protected.'),
('001201','draft','2009-09-21','DISA FSO','policy','Employ a diverse set of information technologies for organization-defined system components in the implementation of the system.','SC-29','N/A','Determine if a diverse set of information technologies is employed for [SC-29_ODP; system components requiring a diverse set of information technologies to be employed in the implementation of the system are defined] in the implementation of the system.'),
('001203','draft','2009-09-21','DISA FSO','policy','Employ virtualization techniques to support the deployment of a diversity of operating systems that are changed on an organization-defined frequency.','SC-29(01)','N/A','Determine if virtualization techniques are employed to support the deployment of a diverse range of operating systems and applications that are changed [SC-29(01)_ODP; the frequency at which to change the diversity of operating systems and applications deployed using virtualization techniques is defined].'),
('001204','draft','2009-09-21','DISA FSO','policy','Defines the frequency of changes to operating systems and applications to support a diversity of deployments.','SC-29(01)','N/A','Determine if virtualization techniques are employed to support the deployment of a diverse range of operating systems and applications that are changed [SC-29(01)_ODP; the frequency at which to change the diversity of operating systems and applications deployed using virtualization techniques is defined].'),
('001207','draft','2009-09-21','DISA FSO','policy','Test a subset of the identified covert channels to determine which channels are exploitable.','SC-31(01)','N/A','Determine if a subset of the identified covert channels is tested to determine the channels that are exploitable.'),
('001210','draft','2009-09-21','DISA FSO','technical','For organization-defined system components, load and execute the operating environment from hardware-enforced, read-only media.','SC-34a.','N/A','Determine if the operating environment for [SC-34_ODP[01]; system components for which the operating environment and applications are to be loaded and executed from hardware-enforced, read-only media are defined] is loaded and executed from hardware-enforced, read-only media.'),
('001211','draft','2009-09-21','DISA FSO','technical','For organization-defined system components, load and execute organization-defined applications from hardware-enforced, read-only media.','SC-34b.','N/A','Determine if [SC-34_ODP[02]; applications to be loaded and executed from hardware-enforced, read-only media are defined] for [SC-34_ODP[01]; system components for which the operating environment and applications are to be loaded and executed from hardware-enforced, read-only media are defined] are loaded and executed from hardware-enforced, read-only media.'),
('001212','draft','2009-09-21','DISA FSO','policy','Defines system components on which the operating environment and organization-defined applications are loaded and executed from hardware-enforced, read-only media.',NULL,'N/A',NULL),
('001213','draft','2009-09-21','DISA FSO','policy','Defines applications that will be loaded and executed from hardware-enforced, read-only media.','SC-34b.','N/A','Determine if [SC-34_ODP[02]; applications to be loaded and executed from hardware-enforced, read-only media are defined] for [SC-34_ODP[01]; system components for which the operating environment and applications are to be loaded and executed from hardware-enforced, read-only media are defined] are loaded and executed from hardware-enforced, read-only media.'),
('001214','draft','2009-09-21','DISA FSO','policy','Employ organization-defined system components with no writeable storage that is persistent across component restart or power on/off.','SC-34(01)','N/A','Determine if [SC-34(01)_ODP; system components to be employed with no writeable storage are defined] are employed with no writeable storage that is persistent across component restart or power on/off.'),
('001215','draft','2009-09-21','DISA FSO','policy','Defines the system components to be employed with no writeable storage.','SC-34(01)','N/A','Determine if [SC-34(01)_ODP; system components to be employed with no writeable storage are defined] are employed with no writeable storage that is persistent across component restart or power on/off.'),
('001216','draft','2009-09-21','DISA FSO','policy','Protect the integrity of information prior to storage on read-only media.','SC-34(02)','N/A','Determine if: - the integrity of information is protected prior to storage on read-only media. - the media is controlled after such information has been recorded onto the media.'),
('001217','draft','2009-09-22','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system level system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SC-34(02)','N/A','Determine if: - the integrity of information is protected prior to storage on read-only media. - the media is controlled after such information has been recorded onto the media.'),
('001218','draft','2009-09-22','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; and/or system level system and information integrity policy to organization-defined personnel or roles.','SI-01a.','N/A','Determine if: - a system and information integrity policy is developed and documented. - the system and information integrity policy is disseminated to [SI-01_ODP[01]; personnel or roles to whom the system and information integrity policy is to be disseminated is/are defined].'),
('001219','draft','2009-09-22','DISA FSO','policy','Review and update the current system and information integrity policy in accordance with organization-defined frequency.','SI-01c.01','N/A','Determine if: - the current system and information integrity policy is reviewed and updated [SI-01_ODP[05]; the frequency at which the current system and information integrity policy is reviewed and updated is defined]. - the current system and information integrity policy is reviewed and updated following [SI-01_ODP[06]; events that would require the current system and information integrity policy to be reviewed and updated are defined].'),
('001220','draft','2009-09-22','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the organization-level; mission/business process-level; and/or system level system and information integrity policy and associated system integrity controls.','SI-01a.02','N/A','Determine if: - system and information integrity procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls are developed and documented. - the system and information integrity procedures are disseminated to [SI-01_ODP[02]; personnel or roles to whom the system and information integrity procedures are to be disseminated is/are defined].'),
('001221','draft','2009-09-22','DISA FSO','policy','Disseminate to organization-defined personnel or roles procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls.','SI-01a.02','N/A','Determine if: - system and information integrity procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls are developed and documented. - the system and information integrity procedures are disseminated to [SI-01_ODP[02]; personnel or roles to whom the system and information integrity procedures are to be disseminated is/are defined].'),
('001222','draft','2009-09-22','DISA FSO','policy','Review and update the current system and information integrity procedures in accordance with organization-defined frequency.','SI-01c.02','N/A','Determine if: - the current system and information integrity procedures are reviewed and updated [SI-01_ODP[07]; the frequency at which the current system and information integrity procedures are reviewed and updated is defined]. - the current system and information integrity procedures are reviewed and updated following [SI-01_ODP[08]; events that would require the system and information integrity procedures to be reviewed and updated are defined].'),
('001223','draft','2009-09-22','DISA FSO','policy','Defines the frequency for reviewing and updating the current system and information integrity policy.','SI-01c.01','N/A','Determine if: - the current system and information integrity policy is reviewed and updated [SI-01_ODP[05]; the frequency at which the current system and information integrity policy is reviewed and updated is defined]. - the current system and information integrity policy is reviewed and updated following [SI-01_ODP[06]; events that would require the current system and information integrity policy to be reviewed and updated are defined].'),
('001224','draft','2009-09-22','DISA FSO','policy','Defines the frequency for reviewing and updating the current system and information integrity procedures.','SI-01c.02','N/A','Determine if: - the current system and information integrity procedures are reviewed and updated [SI-01_ODP[07]; the frequency at which the current system and information integrity procedures are reviewed and updated is defined]. - the current system and information integrity procedures are reviewed and updated following [SI-01_ODP[08]; events that would require the system and information integrity procedures to be reviewed and updated are defined].'),
('001225','draft','2009-09-22','DISA FSO','policy','Identify system flaws.','SI-02a.','N/A','Determine if: - system flaws are identified. - system flaws are reported. - system flaws are corrected.'),
('001226','draft','2009-09-22','DISA FSO','policy','Report system flaws.','SI-02a.','N/A','Determine if: - system flaws are identified. - system flaws are reported. - system flaws are corrected.'),
('001227','draft','2009-09-22','DISA FSO','policy','Correct system flaws.','SI-02a.','N/A','Determine if: - system flaws are identified. - system flaws are reported. - system flaws are corrected.'),
('001228','draft','2009-09-22','DISA FSO','policy','Test software updates related to flaw remediation for effectiveness before installation.','SI-02b.','N/A','Determine if: - software updates related to flaw remediation are tested for effectiveness before installation. - software updates related to flaw remediation are tested for potential side effects before installation. - firmware updates related to flaw remediation are tested for effectiveness before installation. - firmware updates related to flaw remediation are tested for potential side effects before installation.'),
('001229','draft','2009-09-22','DISA FSO','policy','Test software updates related to flaw remediation for potential side effects before installation.','SI-02b.','N/A','Determine if: - software updates related to flaw remediation are tested for effectiveness before installation. - software updates related to flaw remediation are tested for potential side effects before installation. - firmware updates related to flaw remediation are tested for effectiveness before installation. - firmware updates related to flaw remediation are tested for potential side effects before installation.'),
('001230','draft','2009-09-22','DISA FSO','policy','Incorporate flaw remediation into the organizational configuration management process.','SI-02d.','N/A','Determine if flaw remediation is incorporated into the organizational configuration management process.'),
('001235','draft','2009-09-22','DISA FSO','policy','Measure the time between flaw identification and flaw remediation.','SI-02(03)(a)','N/A','Determine if the time between flaw identification and flaw remediation is measured.'),
('001236','draft','2009-09-22','DISA FSO','policy','Defines benchmarks for the time taken to apply corrective actions after flaw identification.','SI-02(03)(b)','N/A','Determine if [SI-02(03)_ODP; the benchmarks for taking corrective actions are defined] for taking corrective actions have been established.'),
('001241','draft','2009-09-22','DISA FSO','technical','Configure malicious code protection mechanisms to perform periodic scans of the system on an organization-defined frequency.','SI-03c.01','N/A','Determine if: - malicious code protection mechanisms are configured to perform periodic scans of the system [SI-03_ODP[02]; the frequency at which malicious code protection mechanisms perform scans is defined]. - malicious code protection mechanisms are configured to perform real-time scans of files from external sources at [SI-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {endpoint; network entry and exit points}] as the files are downloaded, opened, or executed in accordance with organizational policy.'),
('001243','draft','2009-09-22','DISA FSO','technical','Configure malicious code protection mechanisms to block malicious code; quarantine malicious code; and/or take organization-defined action(s) in response to malicious code detection.','SI-03c.02','N/A','Determine if: - malicious code protection mechanisms are configured to [SI-03_ODP[04]; one or more of the following PARAMETER VALUES is/are selected: {block malicious code; quarantine malicious code; take [SI-03_ODP[05]; action to be taken in response to malicious code detection are defined (if selected)}] in response to malicious code detection. - malicious code protection mechanisms are configured to send alerts to [SI-03_ODP[06]; personnel or roles to be alerted when malicious code is detected is/are defined] in response to malicious code detection.'),
('001244','draft','2009-09-22','DISA FSO','policy','Defines one or more actions to perform in response to malicious code detection, such as blocking malicious code, quarantining malicious code, or sending alerts to administrators.','SI-03c.02','N/A','Determine if: - malicious code protection mechanisms are configured to [SI-03_ODP[04]; one or more of the following PARAMETER VALUES is/are selected: {block malicious code; quarantine malicious code; take [SI-03_ODP[05]; action to be taken in response to malicious code detection are defined (if selected)}] in response to malicious code detection. - malicious code protection mechanisms are configured to send alerts to [SI-03_ODP[06]; personnel or roles to be alerted when malicious code is detected is/are defined] in response to malicious code detection.'),
('001245','draft','2009-09-22','DISA FSO','policy','Address the receipt of false positives during malicious code detection and eradication, and the resulting potential impact on the availability of the system.','SI-03d.','N/A','Determine if the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system are addressed.'),
('001249','draft','2009-09-22','DISA FSO','technical','Update malicious code protection mechanisms only when directed by a privileged user.','SI-03(04)','N/A','Determine if malicious code protection mechanisms are updated only when directed by a privileged user.'),
('001251','draft','2009-09-22','DISA FSO','policy','Test malicious code protection mechanisms on an organization-defined frequency by introducing a known benign code into the system.','SI-03(06)(a)','N/A','Determine if malicious code protection mechanisms are tested [SI-03(06)_ODP; the frequency at which to test malicious code protection mechanisms is defined] by introducing known benign code into the system.'),
('001253','draft','2009-09-22','DISA FSO','policy','Defines the objectives of monitoring for attacks and indicators of potential attacks on the system.','SI-04a.01','N/A','Determine if the system is monitored to detect attacks and indicators of potential attacks in accordance with [SI-04_ODP[01]; monitoring objectives to detect attacks and indicators of potential attacks on the system are defined].'),
('001255','draft','2009-09-22','DISA FSO','policy','Invoke internal monitoring capabilities or deploy monitoring devices strategically within the system to collect organization-determined essential information.','SI-04c.01','N/A','Determine if internal monitoring capabilities are invoked or monitoring devices are deployed strategically within the system to collect organization-determined essential information.'),
('001256','draft','2009-09-22','DISA FSO','policy','Invoke internal monitoring capabilities or deploy monitoring devices at ad hoc locations within the system to track specific types of transactions of interest to the organization.','SI-04c.02','N/A','Determine if internal monitoring capabilities are invoked or monitoring devices are deployed at ad hoc locations within the system to track specific types of transactions of interest to the organization.'),
('001257','draft','2009-09-22','DISA FSO','policy','Adjust the level of system monitoring activity when there is a change in increased risk to organizational operations and assets, individuals, other organizations, or the Nation.','SI-04e.','N/A','Determine if the level of system monitoring activity is adjusted when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation.'),
('001258','draft','2009-09-22','DISA FSO','policy','Obtain legal opinion with regard to system monitoring activities.','SI-04f.','N/A','Determine if a legal opinion regarding system monitoring activities is obtained.'),
('001260','draft','2009-09-22','DISA FSO','policy','Employ automated tools to support near real-time analysis of events.','SI-04(02)','N/A','Determine if automated tools and mechanisms are employed to support a near real-time analysis of events.'),
('001264','draft','2009-09-22','DISA FSO','policy','Defines the indicators of compromise or potential compromise which will result in system alerts being provided to organization-defined personnel or roles.','SI-04(05)','N/A','Determine if [SI-04(05)_ODP[01]; personnel or roles to be alerted when indications of compromise or potential compromise occur is/are defined] are alerted when system-generated [SI-04(05)_ODP[02]; compromise indicators are defined] occur.'),
('001266','draft','2009-09-22','DISA FSO','technical','Notify an organization-defined incident response personnel (identified by name and/or by role) of detected suspicious events.','SI-04(07)(a)','N/A','Determine if [SI-04(07)_ODP[01]; incident response personnel (identified by name and/or by role) to be notified of detected suspicious events is/are defined] are notified of detected suspicious events.'),
('001267','draft','2009-09-22','DISA FSO','policy','Defines incident response personnel (identified by name and/or by role) to be notified of detected suspicious events.','SI-04(07)(a)','N/A','Determine if [SI-04(07)_ODP[01]; incident response personnel (identified by name and/or by role) to be notified of detected suspicious events is/are defined] are notified of detected suspicious events.'),
('001268','draft','2009-09-22','DISA FSO','policy','Defines the least-disruptive actions to be taken by system to terminate suspicious events.','SI-04(07)(b)','N/A','Determine if [SI-04(07)_ODP[02]; least-disruptive actions to terminate suspicious events are defined] are taken upon the detection of suspicious events.'),
('001270','draft','2009-09-22','DISA FSO','policy','Test intrusion monitoring tools at an organization-defined frequency.','SI-04(09)','N/A','Determine if intrusion-monitoring tools and mechanisms are tested [SI-04(09)_ODP; a frequency at which to test intrusion-monitoring tools and mechanisms is defined].'),
('001271','draft','2009-09-22','DISA FSO','policy','Defines the frequency for testing intrusion monitoring tools.','SI-04(09)','N/A','Determine if intrusion-monitoring tools and mechanisms are tested [SI-04(09)_ODP; a frequency at which to test intrusion-monitoring tools and mechanisms is defined].'),
('001273','draft','2009-09-22','DISA FSO','policy','Analyze outbound communications traffic at the external interfaces to the system to discover anomalies.','SI-04(11)','N/A','Determine if: - outbound communications traffic at the external interfaces to the system is analyzed to discover anomalies. - outbound communications traffic at [SI-04(11)_ODP; interior points within the system where communications traffic is to be analyzed are defined] is analyzed to discover anomalies. '),
('001274','draft','2009-09-22','DISA FSO','policy','Alert organization-defined personnel or roles using organization-defined automated mechanisms when inappropriate or unusual activities with security or privacy implications.','SI-04(12)','N/A','Determine if [SI-04(12)_ODP[01]; personnel or roles to be alerted when indications of inappropriate or unusual activity with security or privacy implications occur is/are defined] is/are alerted using [SI-04(12)_ODP[02]; automated mechanisms used to alert personnel or roles are defined] when [SI-04(12)_ODP[03]; activities that trigger alerts to personnel or are defined] indicate inappropriate or unusual activities with security or privacy implications.'),
('001275','draft','2009-09-22','DISA FSO','policy','Defines the activities which will trigger alerts to security personnel of inappropriate or unusual activities.','SI-04(12)','N/A','Determine if [SI-04(12)_ODP[01]; personnel or roles to be alerted when indications of inappropriate or unusual activity with security or privacy implications occur is/are defined] is/are alerted using [SI-04(12)_ODP[02]; automated mechanisms used to alert personnel or roles are defined] when [SI-04(12)_ODP[03]; activities that trigger alerts to personnel or are defined] indicate inappropriate or unusual activities with security or privacy implications.'),
('001276','draft','2009-09-22','DISA FSO','policy','Analyze communications traffic and event patterns for the system.','SI-04(13)(a)','N/A','Determine if: - communications traffic for the system is analyzed. - event patterns for the system are analyzed.'),
('001277','draft','2009-09-22','DISA FSO','policy','Develop profiles representing common traffic and event patterns.','SI-04(13)(b)','N/A','Determine if: - profiles representing common traffic are developed. - profiles representing event patterns are developed.'),
('001282','draft','2009-09-22','DISA FSO','policy','Employ an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.','SI-04(15)','N/A','Determine if an intrusion detection system is employed to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.'),
('001283','draft','2009-09-22','DISA FSO','policy','Correlate information from monitoring tools employed throughout the system.','SI-04(16)','N/A','Determine if information from monitoring tools and mechanisms employed throughout the system is correlated.'),
('001284','draft','2009-09-22','DISA FSO','policy','Correlate information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.','SI-04(17)','N/A','Determine if information from monitoring physical, cyber, and supply chain activities are correlated to achieve integrated, organization-wide situational awareness.'),
('001285','draft','2009-09-22','DISA FSO','policy','Receive system security alerts, advisories, and directives from organization-defined external organizations on an ongoing basis.','SI-05a.','N/A','Determine if system security alerts, advisories, and directives are received from [SI-05_ODP[01]; external organizations from whom system security alerts, advisories, and directives are to be received on an ongoing basis are defined] on an ongoing basis.'),
('001286','draft','2009-09-22','DISA FSO','policy','Generate internal security alerts, advisories, and directives as deemed necessary.','SI-05b.','N/A','Determine if internal security alerts, advisories, and directives are generated as deemed necessary.'),
('001287','draft','2009-09-22','DISA FSO','policy','Disseminate security alerts, advisories, and directives to organization-defined personnel or roles, organization-defined elements within the organization, and/or organization-defined external organizations.','SI-05c.','N/A','Determine if security alerts, advisories, and directives are disseminated to [SI-05_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[SI-05_ODP[03]; personnel or roles to whom security alerts, advisories, and directives are to be disseminated is/are defined (if selected)]; [SI-05_ODP[04]; elements within the organization to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]; [SI-05_ODP[05]; external organizations to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]}].'),
('001288','draft','2009-09-22','DISA FSO','policy','Defines the personnel or roles to whom the organization will disseminate security alerts, advisories, and directives.','SI-05c.','N/A','Determine if security alerts, advisories, and directives are disseminated to [SI-05_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[SI-05_ODP[03]; personnel or roles to whom security alerts, advisories, and directives are to be disseminated is/are defined (if selected)]; [SI-05_ODP[04]; elements within the organization to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]; [SI-05_ODP[05]; external organizations to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]}].'),
('001289','draft','2009-09-22','DISA FSO','policy','Implement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance.','SI-05d.','N/A','Determine if security directives are implemented in accordance with established time frames or if the issuing organization is notified of the degree of noncompliance.'),
('001290','draft','2009-09-22','DISA FSO','policy','Broadcast security alert and advisory information throughout the organization using organization-defined automated mechanisms.','SI-05(01)','N/A','Determine if [SI-05(01)_ODP; automated mechanisms used to broadcast security alert and advisory information throughout the organization are defined] are used to broadcast security alert and advisory information throughout the organization.'),
('001294','draft','2009-09-22','DISA FSO','technical','Alert organization-defined personnel or roles of failed security verification tests.','SI-06c.','N/A','Determine if: - [SI-06_ODP[06]; personnel or roles to be alerted of failed security and privacy verification tests is/are defined] is/are alerted to failed security verification tests. - [SI-06_ODP[06]; personnel or roles to be alerted of failed security and privacy verification tests is/are defined] is/are alerted to failed privacy verification tests.'),
('001295','draft','2009-09-22','DISA FSO','technical','Implement automated mechanisms to support the management of distributed security function testing.','SI-06(02)','N/A','Determine if: - automated mechanisms are implemented to support the management of distributed security function testing. - automated mechanisms are implemented to support the management of distributed privacy function testing.'),
('001296','draft','2009-09-22','DISA FSO','policy','Report the results of security function verification to organization-defined personnel or roles.','SI-06(03)','N/A','Determine if: - the results of security function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined]. - the results of privacy function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined].'),
('001300','draft','2009-09-22','DISA FSO','policy','Employ automated tools that provide notification to organization-defined personnel or roles upon discovering discrepancies during integrity verification.','SI-07(02)','N/A','Determine if automated tools that provide notification to [SI-07(02)_ODP; personnel or roles to whom notification is to be provided upon discovering discrepancies during integrity verification is/are defined] upon discovering discrepancies during integrity verification are employed.'),
('001301','draft','2009-09-22','DISA FSO','policy','Employ centrally managed integrity verification tools.','SI-07(03)','N/A','Determine if centrally managed integrity verification tools are employed.'),
('001308','draft','2009-09-22','DISA FSO','technical','Automatically update spam protection mechanisms on an organization-defined frequency.','SI-08(02)','N/A','Determine if spam protection mechanisms are automatically updated [SI-08(02)_ODP; the frequency at which to automatically update spam protection mechanisms is defined].'),
('001310','draft','2009-09-22','DISA FSO','technical','Checks the validity of organization-defined information inputs to the system.','SI-10','N/A','Determine if the validity of the [SI-10_ODP; information inputs to the system requiring validity checks are defined] is checked.'),
('001312','draft','2009-09-22','DISA FSO','technical','Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited.','SI-11a.','N/A','Determine if error messages that provide the information necessary for corrective actions are generated without revealing information that could be exploited.'),
('001314','draft','2009-09-22','DISA FSO','technical','Reveal error messages only to organization-defined personnel or roles.','SI-11b.','N/A','Determine if error messages are revealed only to [SI-11_ODP; personnel or roles to whom error messages are to be revealed is/are defined].'),
('001315','draft','2009-09-22','DISA FSO','policy','Manage information within the system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','SI-12','N/A','Determine if: - information within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements. - information within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements. - information output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements. - information output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.'),
('001318','draft','2009-09-22','DISA FSO','policy','Provide substitute system components.','SI-13b.','N/A','Determine if substitute system components and a means to exchange active and standby components are provided in accordance with [SI-13_ODP[02]; mean time to failure (MTTF) substitution criteria to be used as a means to exchange active and standby components are defined].'),
('001319','draft','2009-09-22','DISA FSO','policy','Take system components out of service by transferring component responsibilities to a substitute component no later than an organization-defined fraction or percentage of mean time to failure (MTTF).','SI-13(01)','N/A','Determine if system components are taken out of service by transferring component responsibilities to substitute components no later than [SI-13(01)_ODP; the fraction or percentage of mean time to failure within which to transfer the responsibilities of a system component to a substitute component is defined] of mean time to failure.'),
('001320','draft','2009-09-22','DISA FSO','policy','Defines the maximum fraction or percentage of mean time to failure (MTTF) used to determine when system components are taken out of service by transferring component responsibilities to substitute components.','SI-13(01)','N/A','Determine if system components are taken out of service by transferring component responsibilities to substitute components no later than [SI-13(01)_ODP; the fraction or percentage of mean time to failure within which to transfer the responsibilities of a system component to a substitute component is defined] of mean time to failure.'),
('001321','draft','2009-09-22','DISA FSO','policy','Prohibit processes from executing without supervision for more than an organization-defined time period.','SI-07(16)','N/A','Determine if processes are prohibited from executing without supervision for more than [SI-07(16)_ODP; the maximum time period permitted for processes to execute without supervision is defined].'),
('001322','draft','2009-09-22','DISA FSO','policy','Defines a time period that is the longest a process is allowed to execute without supervision.','SI-07(16)','N/A','Determine if processes are prohibited from executing without supervision for more than [SI-07(16)_ODP; the maximum time period permitted for processes to execute without supervision is defined].'),
('001323','draft','2009-09-22','DISA FSO','policy','Manually initiate transfers between active and standby system components when the use of the active component reaches an organization-defined percentage of the mean time to failure.','SI-13(03)','N/A','Determine if transfers are initiated manually between active and standby system components when the use of the active component reaches [SI-13(03)_ODP; the percentage of the mean time to failure for transfers to be manually initiated is defined] of the mean time to failure.'),
('001326','draft','2009-09-22','DISA FSO','policy','If system component failures are detected, ensure standby components are successfully and transparently installed within an organization-defined time period.','SI-13(04)(a)','N/A','Determine if the standby components are successfully and transparently installed within [SI-13(04)_ODP[01]; time period for standby components to be installed is defined] if system component failures are detected.'),
('001327','draft','2009-09-22','DISA FSO','policy','Defines a time period for a standby system component to be successfully and transparently installed for the system component that has failed.','SI-13(04)(a)','N/A','Determine if the standby components are successfully and transparently installed within [SI-13(04)_ODP[01]; time period for standby components to be installed is defined] if system component failures are detected.'),
('001328','draft','2009-09-22','DISA FSO','technical','If system component failures are detected, activate an organization-defined alarm, automatically shut down the system, and/or organization-defined action.','SI-13(04)(b)','N/A','Determine if [SI-13(04)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {activate [SI-13(04)_ODP[03]; alarm to be activated when system component failures are detected is defined (if selected)]; automatically shut down the system; [SI-13(04)_ODP[04]; action to be taken when system component failures are detected is defined (if selected)]}] are performed if system component failures are detected.'),
('001329','draft','2009-09-22','DISA FSO','policy','Defines the alarm to be activated when a system component failure is detected.','SI-13(04)(b)','N/A','Determine if [SI-13(04)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {activate [SI-13(04)_ODP[03]; alarm to be activated when system component failures are detected is defined (if selected)]; automatically shut down the system; [SI-13(04)_ODP[04]; action to be taken when system component failures are detected is defined (if selected)]}] are performed if system component failures are detected.'),
('001330','draft','2009-09-22','DISA FSO','policy','Prohibit the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official.','AC-19(04)(a)','N/A','Determine if the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information is prohibited unless specifically permitted by the authorizing official.'),
('001331','draft','2009-09-22','DISA FSO','policy','Prohibit the connection of unclassified mobile devices to classified systems.','AC-19(04)(b)(01)','N/A','Determine if prohibition of the connection of unclassified mobile devices to classified systems is enforced on individuals permitted by an authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information.'),
('001332','draft','2009-09-22','DISA FSO','policy','Connection of unclassified mobile devices to unclassified systems requires approval from the authorizing official.','AC-19(04)(b)(02)','N/A','Determine if approval by the authorizing official for the connection of unclassified mobile devices to unclassified systems is enforced on individuals permitted to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information.'),
('001333','draft','2009-09-22','DISA FSO','policy','Use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited.','AC-19(04)(b)(03)','N/A','Determine if prohibition of the use of internal or external modems or wireless interfaces within unclassified mobile devices is enforced on individuals permitted by an authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information.'),
('001334','draft','2009-09-22','DISA FSO','policy','Require unclassified mobile devices used in facilities containing systems processing, storing, or transmitting classified information and the information stored on those devices be subject to random reviews and inspections by organization-defined security officials.','AC-19(04)(b)(04)','N/A','Determine if: - random review and inspection of unclassified mobile devices and the information stored on those devices by [AC-19(04)_ODP[01]; security officials responsible for the review and inspection of unclassified mobile devices and the information stored on those devices are defined] are enforced. - following of the incident handling policy is enforced if classified information is found during a random review and inspection of unclassified mobile devices.'),
('001335','draft','2009-09-22','DISA FSO','policy','Defines security officials to perform reviews and inspections of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information.','AC-19(04)(b)(04)','N/A','Determine if: - random review and inspection of unclassified mobile devices and the information stored on those devices by [AC-19(04)_ODP[01]; security officials responsible for the review and inspection of unclassified mobile devices and the information stored on those devices are defined] are enforced. - following of the incident handling policy is enforced if classified information is found during a random review and inspection of unclassified mobile devices.'),
('001336','draft','2009-09-22','DISA FSO','policy','Retain individual training records for an organization-defined time-period.','AT-04b.','N/A','Determine if individual training records are retained for [AT-04_ODP; time period for retaining individual training records is defined].'),
('001337','draft','2009-09-22','DISA FSO','policy','Defines the time period for retaining individual training records.','AT-04b.','N/A','Determine if individual training records are retained for [AT-04_ODP; time period for retaining individual training records is defined].'),
('001340','draft','2009-09-22','DISA FSO','technical','Maintain reviewer or releaser identity and credentials within the established chain of custody for all information reviewed or released.','AU-10(03)','N/A','Determine if reviewer or releaser credentials are maintained within the established chain of custody for information reviewed or released.'),
('001341','draft','2009-09-22','DISA FSO','technical','Validate the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between organization-defined security domains.','AU-10(04)(a)','N/A','Determine if the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between [AU-10(04)_ODP[01]; security domains for which the binding of the information reviewer identity to the information is to be validated at transfer or release are defined].'),
('001348','draft','2009-09-22','DISA FSO','technical','Store audit records on an organization-defined frequency in a repository that is part of a physically different system or system component than the system or component being audited.','AU-09(02)','N/A','Determine if audit records are stored [AU-09(02)_ODP; the frequency of storing audit records in a repository is defined] in a repository that is part of a physically different system or system component than the system or component being audited.'),
('001349','draft','2009-09-22','DISA FSO','policy','Defines a frequency for storing audit records in a repository that is part of a physically different system or system component than the system or component being audited.','AU-09(02)','N/A','Determine if audit records are stored [AU-09(02)_ODP; the frequency of storing audit records in a repository is defined] in a repository that is part of a physically different system or system component than the system or component being audited.'),
('001350','draft','2009-09-22','DISA FSO','technical','Implement cryptographic mechanisms to protect the integrity of audit information.','AU-09(03)','N/A','Determine if cryptographic mechanisms to protect the integrity of audit information and audit tools are implemented.'),
('001351','draft','2009-09-22','DISA FSO','policy','Authorize access to management of audit logging functionality to only an organization-defined subset of privileged users or roles.','AU-09(04)','N/A','Determine if access to management of audit logging functionality is authorized only to [AU-09(04)_ODP; a subset of privileged users or roles authorized to access management of audit logging functionality is defined].'),
('001353','draft','2009-09-22','DISA FSO','technical','Produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format.','AU-12(02)','N/A','Determine if a system-wide (logical or physical) audit trail composed of audit records is produced in a standardized format.'),
('001358','draft','2009-09-22','DISA FSO','policy','Establish privileged user accounts in accordance with a role-based access scheme; or an attribute-based access scheme.','AC-02(07)(a)','N/A','Determine if privileged user accounts are established and administered in accordance with [AC-02(07)_ODP; one of the following PARAMETER VALUES is selected: {a role-based access scheme; an attribute-based access scheme}].'),
('001360','draft','2009-09-22','DISA FSO','policy','Monitor privileged role assignments.','AC-02(07)(b)','N/A','Determine if privileged role or attribute assignments are monitored.'),
('001361','draft','2009-09-24','DISA FSO','policy','Defines a time period after which temporary accounts are automatically terminated.','AC-02(02)','N/A','Determine if temporary and emergency accounts are automatically [AC-02(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {remove; disable}] after [AC-02(02)_ODP[02]; the time period after which to automatically remove or disable temporary or emergency accounts is defined].'),
('001365','draft','2009-09-24','DISA FSO','policy','Defines a time period after which emergency accounts are automatically terminated.','AC-02(02)','N/A','Determine if temporary and emergency accounts are automatically [AC-02(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {remove; disable}] after [AC-02(02)_ODP[02]; the time period after which to automatically remove or disable temporary or emergency accounts is defined].'),
('001368','draft','2009-09-22','DISA FSO','technical','Enforce approved authorizations for controlling the flow of information within the system based on organization-defined information flow control policies.','AC-04','N/A','Determine if approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on [AC-04_ODP; information flow control policies within the system and between connected systems are defined].'),
('001371','draft','2009-09-22','DISA FSO','policy','Defines security or privacy policy filters requiring fully enumerated formats which are to be implemented when transferring information between different security domains.','AC-04(14)','N/A','Determine if: - when transferring information between different security domains, implemented [AC-04(14)_ODP[01]; security policy filters to be implemented that require fully enumerated formats restricting data structure and content have been defined] require fully enumerated formats that restrict data structure and content. - when transferring information between different security domains, implemented [AC-04(14)_ODP[02]; privacy policy filters to be implemented that require fully enumerated formats restricting data structure and content are defined] require fully enumerated formats that restrict data structure and content.'),
('001372','draft','2009-09-22','DISA FSO','technical','When transferring information between different security domains, implement organization-defined security or privacy policy filters requiring fully enumerated formats that restrict data structure and content.','AC-04(14)','N/A','Determine if: - when transferring information between different security domains, implemented [AC-04(14)_ODP[01]; security policy filters to be implemented that require fully enumerated formats restricting data structure and content have been defined] require fully enumerated formats that restrict data structure and content. - when transferring information between different security domains, implemented [AC-04(14)_ODP[02]; privacy policy filters to be implemented that require fully enumerated formats restricting data structure and content are defined] require fully enumerated formats that restrict data structure and content.'),
('001373','draft','2009-09-22','DISA FSO','technical','When transferring information between different security domains, examine the information for the presence of organization-defined unsanctioned information.','AC-04(15)','N/A','Determine if: - when transferring information between different security domains, information is examined for the presence of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[02]; security policy that requires the transfer of unsanctioned information between different security domains to be prohibited is defined (if selected)]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[03]; privacy policy that requires the transfer of organization-defined unsanctioned information between different security domains to be prohibited is defined (if selected)].'),
('001374','draft','2009-09-22','DISA FSO','technical','When transferring information between different security domains, prohibit the transfer of such information in accordance with the organization-defined security or privacy policy.','AC-04(15)','N/A','Determine if: - when transferring information between different security domains, information is examined for the presence of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[02]; security policy that requires the transfer of unsanctioned information between different security domains to be prohibited is defined (if selected)]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[03]; privacy policy that requires the transfer of organization-defined unsanctioned information between different security domains to be prohibited is defined (if selected)].'),
('001384','draft','2009-09-22','DISA FSO','technical','For publicly accessible systems, display system use information with organization-defined conditions before granting further access to the publicly accessible system.','AC-08c.01','N/A','Determine if for publicly accessible systems, system use information [AC-08_ODP[02]; conditions for system use to be displayed by the system before granting further access are defined] is displayed before granting further access to the publicly accessible system.'),
('001385','draft','2009-09-22','DISA FSO','technical','For publicly accessible systems, displays references, if any, to monitoring that are consistent with privacy accommodations for such systems that generally prohibit those activities.','AC-08c.02','N/A','Determine if for publicly accessible systems, any references to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities are displayed.'),
('001386','draft','2009-09-22','DISA FSO','technical','For publicly accessible systems, displays references, if any, to recording that are consistent with privacy accommodations for such systems that generally prohibit those activities.','AC-08c.02','N/A','Determine if for publicly accessible systems, any references to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities are displayed.'),
('001387','draft','2009-09-22','DISA FSO','technical','For publicly accessible systems, displays references, if any, to auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities.','AC-08c.02','N/A','Determine if for publicly accessible systems, any references to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities are displayed.'),
('001388','draft','2009-09-22','DISA FSO','technical','For publicly accessible systems, includes a description of the authorized uses of the system.','AC-08c.03','N/A','Determine if for publicly accessible systems, a description of the authorized uses of the system is included.'),
('001389','draft','2009-09-22','DISA FSO','policy','Defines the time period that the system notifies the user of the number of successful logon/access attempts.','AC-09(02)','N/A','Determine if the user is notified, upon successful logon, of the number of [AC-09(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {successful logons; unsuccessful logon attempts; both}] during [AC-09(02)_ODP[02]; the time period for which the system notifies the user of the number of successful logons, unsuccessful logon attempts, or both is defined].'),
('001390','draft','2009-09-22','DISA FSO','policy','Defines the time period that the system notifies the user of the number of unsuccessful logon/access attempts.','AC-09(02)','N/A','Determine if the user is notified, upon successful logon, of the number of [AC-09(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {successful logons; unsuccessful logon attempts; both}] during [AC-09(02)_ODP[02]; the time period for which the system notifies the user of the number of successful logons, unsuccessful logon attempts, or both is defined].'),
('001391','draft','2009-09-22','DISA FSO','technical','Notify the user, upon successful logon, of the number of successful logons/accesses during the organization-defined time period.','AC-09(02)','N/A','Determine if the user is notified, upon successful logon, of the number of [AC-09(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {successful logons; unsuccessful logon attempts; both}] during [AC-09(02)_ODP[02]; the time period for which the system notifies the user of the number of successful logons, unsuccessful logon attempts, or both is defined].'),
('001392','draft','2009-09-22','DISA FSO','technical','Notify the user, upon successful logon, of the number of unsuccessful logon/access attempts during the organization-defined time period.','AC-09(02)','N/A','Determine if the user is notified, upon successful logon, of the number of [AC-09(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {successful logons; unsuccessful logon attempts; both}] during [AC-09(02)_ODP[02]; the time period for which the system notifies the user of the number of successful logons, unsuccessful logon attempts, or both is defined].'),
('001393','draft','2009-09-22','DISA FSO','policy','Defines the security-related characteristics/parameters of the user''s account which, when changed, will result in a notification being provided to the user during the organization-defined time period.','AC-09(03)','N/A','Determine if the user is notified, upon successful logon, of changes to [AC-09(03)_ODP[01]; changes to security-related characteristics or parameters of the user''s account that require notification are defined] during [AC-09(03)_ODP[02]; the time period for which the system notifies the user of changes to security-related characteristics or parameters of the user''s account is defined].'),
('001394','draft','2009-09-22','DISA FSO','policy','Defines the time period during which organization-defined security-related changes to the user''s account are to be tracked.','AC-09(03)','N/A','Determine if the user is notified, upon successful logon, of changes to [AC-09(03)_ODP[01]; changes to security-related characteristics or parameters of the user''s account that require notification are defined] during [AC-09(03)_ODP[02]; the time period for which the system notifies the user of changes to security-related characteristics or parameters of the user''s account is defined].'),
('001395','draft','2009-09-22','DISA FSO','technical','Notify the user, upon successful logon, of changes to organization-defined security-related characteristics/parameters of the user''s account during the organization-defined time-period.','AC-09(03)','N/A','Determine if the user is notified, upon successful logon, of changes to [AC-09(03)_ODP[01]; changes to security-related characteristics or parameters of the user''s account that require notification are defined] during [AC-09(03)_ODP[02]; the time period for which the system notifies the user of changes to security-related characteristics or parameters of the user''s account is defined].'),
('001403','draft','2009-09-24','DISA FSO','technical','Automatically audit account modification actions.','AC-02(04)','N/A','Determine if: - account creation is automatically audited. - account modification is automatically audited. - account enabling is automatically audited. - account disabling is automatically audited. - account removal actions are automatically audited.'),
('001404','draft','2009-09-24','DISA FSO','technical','Automatically audit account disabling actions.','AC-02(04)','N/A','Determine if: - account creation is automatically audited. - account modification is automatically audited. - account enabling is automatically audited. - account disabling is automatically audited. - account removal actions are automatically audited.'),
('001405','draft','2009-09-24','DISA FSO','technical','Automatically audit account removal actions.','AC-02(04)','N/A','Determine if: - account creation is automatically audited. - account modification is automatically audited. - account enabling is automatically audited. - account disabling is automatically audited. - account removal actions are automatically audited.'),
('001406','draft','2009-09-24','DISA FSO','policy','Defines a time period of expected inactivity when users are required to log out.','AC-02(05)','N/A','Determine if users are required to log out when [AC-02(05)_ODP; the time period of expected inactivity or description of when to log out is defined].'),
('001407','draft','2009-09-24','DISA FSO','policy','Administer privileged user accounts in accordance with a role-based access scheme; or an attribute-based access scheme.','AC-02(07)(a)','N/A','Determine if privileged user accounts are established and administered in accordance with [AC-02(07)_ODP; one of the following PARAMETER VALUES is selected: {a role-based access scheme; an attribute-based access scheme}].'),
('001408','draft','2009-09-24','DISA FSO','policy','Defines privileged commands for which dual authorization is to be enforced.','AC-03(02)','N/A','Determine if dual authorization is enforced for [AC-03(02)_ODP; privileged commands and/or other actions requiring dual authorization are defined].'),
('001411','draft','2009-09-24','DISA FSO','policy','Defines security-relevant information to which the system prevents access except during secure, non-operable system states.','AC-03(05)','N/A','Determine if access to [AC-03(05)_ODP; security-relevant information to which access is prevented except during secure, non-operable system states is defined] is prevented except during secure, non-operable system states.'),
('001414','draft','2009-09-24','DISA FSO','technical','Enforce approved authorizations for controlling the flow of information between connected systems based on organization-defined information flow control policies.','AC-04','N/A','Determine if approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on [AC-04_ODP; information flow control policies within the system and between connected systems are defined].'),
('001415','draft','2009-09-24','DISA FSO','policy','Defines limitations for the embedding of data types within other data types.','AC-04(05)','N/A','Determine if [AC-04(05)_ODP; limitations on embedding data types within other data types are defined] are enforced on embedding data types within other data types.'),
('001417','draft','2009-09-24','DISA FSO','policy','Defines security policy filters to be enforced and used as a basis for flow control decisions.','AC-04(08)(a)','N/A','Determine if: - information flow control is enforced using [AC-04(08)_ODP[01]; security policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[03]; information flows for which information flow control is enforced by security filters are defined]. - information flow control is enforced using [AC-04(08)_ODP[02]; privacy policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[04]; information flows for which information flow control is enforced by privacy filters are defined].'),
('001419','draft','2009-09-25','DISA FSO','policy','Defines the security functions or security-relevant information to which users of system accounts, or roles, have access.','AC-06(02)','N/A','Determine if users of system accounts (or roles) with access to [AC-06(02)_ODP; security functions or security-relevant information, the access to which requires users to use non-privileged accounts to access non-security functions, are defined] are required to use non-privileged accounts or roles when accessing non-security functions.'),
('001420','draft','2009-09-25','DISA FSO','policy','Defines the privileged commands to which network access is to be authorized only for organization-defined compelling operational needs.','AC-06(03)','N/A','Determine if: - network access to [AC-06(03)_ODP[01]; privileged commands to which network access is to be authorized only for compelling operational needs are defined] is authorized only for [AC-06(03)_ODP[02]; compelling operational needs necessitating network access to privileged commands are defined]. - the rationale for authorizing network access to privileged commands is documented in the security plan for the system.'),
('001422','draft','2009-09-25','DISA FSO','policy','Prohibit privileged access to the system by non-organizational users.','AC-06(06)','N/A','Determine if privileged access to the system by non-organizational users is prohibited.'),
('001423','draft','2009-09-25','DISA FSO','policy','Defines the time period in which the organization-defined maximum number of consecutive invalid logon attempts occur.','AC-07a.','N/A','Determine if a limit of [AC-07_ODP[01]; the number of consecutive invalid logon attempts by a user allowed during a time period is defined] consecutive invalid logon attempts by a user during [AC-07_ODP[02]; the time period to which the number of consecutive invalid logon attempts by a user is limited is defined] is enforced.'),
('001424','draft','2009-09-25','DISA FSO','technical','Dynamically associate security attributes with organization-defined subjects in accordance with organization-defined security policies as information is created and combined.',NULL,'N/A',NULL),
('001425','draft','2009-09-25','DISA FSO','technical','Provides authorized individuals (or processes acting on behalf of individuals) the capability to change the value of associated security attributes.',NULL,'N/A',NULL),
('001428','draft','2009-09-25','DISA FSO','technical','Display security attributes in human-readable form on each object that the system transmits to output devices to identify organization-identified special dissemination, handling, or distribution instructions using organization-identified human-readable, standard naming conventions.','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('001429','draft','2009-09-25','DISA FSO','policy','Identify special dissemination, handling, or distribution instructions for identifying security attributes on output.','AC-16(05)','N/A','Determine if: - security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined]. - privacy attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined].'),
('001430','draft','2009-09-25','DISA FSO','policy','Identify human-readable, standard naming conventions for identifying security attributes on output.','AC-16(05)','N/A','Determine if: - security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined]. - privacy attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined].'),
('001439','draft','2009-09-25','DISA FSO','policy','Establish implementation guidance for wireless access.','AC-18a.','N/A','Determine if: - configuration requirements are established for each type of wireless access. - connection requirements are established for each type of wireless access. - implementation guidance is established for each type of wireless access.'),
('001441','draft','2009-09-25','DISA FSO','policy','Authorize each type of wireless access to the system prior to allowing such connections.','AC-18b.','N/A','Determine if each type of wireless access to the system is authorized prior to allowing such connections.'),
('001443','draft','2009-09-25','DISA FSO','technical','Protect wireless access to the system using authentication of users and/or devices.','AC-18(01)','N/A','Determine if: - wireless access to the system is protected using authentication of [AC-18(01)_ODP; one or more of the following PARAMETER VALUES is/are selected: {users; devices}]. - wireless access to the system is protected using encryption.'),
('001444','draft','2009-09-25','DISA FSO','technical','Protect wireless access to the system using encryption.','AC-18(01)','N/A','Determine if: - wireless access to the system is protected using authentication of [AC-18(01)_ODP; one or more of the following PARAMETER VALUES is/are selected: {users; devices}]. - wireless access to the system is protected using encryption.'),
('001449','draft','2009-09-25','DISA FSO','policy','Disable, when not intended for use, wireless networking capabilities internally embedded within system components prior to issuance and deployment.','AC-18(03)','N/A','Determine if when not intended for use, wireless networking capabilities embedded within system components are disabled prior to issuance and deployment.'),
('001451','draft','2009-09-25','DISA FSO','policy','Select radio antennas and calibrate transmission power levels to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries.','AC-18(05)','N/A','Determine if: - radio antennas are selected to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries. - transmission power levels are calibrated to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries.'),
('001453','draft','2009-09-29','DISA FSO','technical','Implement cryptographic mechanisms to protect the integrity of remote access sessions.','AC-17(02)','N/A','Determine if cryptographic mechanisms are implemented to protect the confidentiality and integrity of remote access sessions.'),
('001458','draft','2009-09-29','DISA FSO','policy','If classified information is found on mobile devices, the incident handling policy is to be followed.','AC-19(04)(b)(04)','N/A','Determine if: - random review and inspection of unclassified mobile devices and the information stored on those devices by [AC-19(04)_ODP[01]; security officials responsible for the review and inspection of unclassified mobile devices and the information stored on those devices are defined] are enforced. - following of the incident handling policy is enforced if classified information is found during a random review and inspection of unclassified mobile devices.'),
('001459','draft','2009-09-29','DISA FSO','policy','Defines system components that provide audit record generation capability.','AU-12a.','N/A','Determine if audit record generation capability for the event types the system is capable of auditing (defined in AU-02_ODP[01]) is provided by [AU-12_ODP[01]; system components that provide an audit record generation capability for the events types (defined in AU-02_ODP[02]) are defined].'),
('001460','draft','2009-09-29','DISA FSO','policy','Monitor organization-defined open source information and/or information sites per organization-defined frequency for evidence of unauthorized disclosure of organizational information.','AU-13a.','N/A','Determine if [AU-13_ODP[01]; open-source information and/or information sites to be monitored for evidence of unauthorized disclosure of organizational information is/are defined] is/are monitored [AU-13_ODP[02]; the frequency with which open-source information and/or information sites are monitored for evidence of unauthorized disclosure of organizational information is defined] for evidence of unauthorized disclosure of organizational information.'),
('001461','draft','2009-09-29','DISA FSO','policy','Defines a frequency for monitoring open source information and/or information sites for evidence of unauthorized exfiltration or disclosure of organizational information.','AU-13a.','N/A','Determine if [AU-13_ODP[01]; open-source information and/or information sites to be monitored for evidence of unauthorized disclosure of organizational information is/are defined] is/are monitored [AU-13_ODP[02]; the frequency with which open-source information and/or information sites are monitored for evidence of unauthorized disclosure of organizational information is defined] for evidence of unauthorized disclosure of organizational information.'),
('001464','draft','2009-09-29','DISA FSO','technical','Initiates session audits automatically at system start-up.','AU-14(01)','N/A','Determine if session audits are initiated automatically at system start-up.'),
('001470','draft','2009-09-29','DISA FSO','policy','Defines information sharing circumstances where user discretion is required.','AC-21a.','N/A','Determine if authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information''s access and use restrictions for [AC-21_ODP[01]; information-sharing circumstances where user discretion is required to determine whether access authorizations assigned to a sharing partner match the information''s access and use restrictions are defined].'),
('001471','draft','2009-09-29','DISA FSO','policy','Employ organization-defined automated mechanisms or manual processes required to assist users in making information sharing/collaboration decisions.','AC-21b.','N/A','Determine if [AC-21_ODP[02]; automated mechanisms or manual processes that assist users in making information-sharing and collaboration decisions are defined] are employed to assist users in making information-sharing and collaboration decisions.'),
('001472','draft','2009-09-29','DISA FSO','policy','Defines the automated mechanisms or manual processes required to assist users in making information sharing/collaboration decisions.','AC-21b.','N/A','Determine if [AC-21_ODP[02]; automated mechanisms or manual processes that assist users in making information-sharing and collaboration decisions are defined] are employed to assist users in making information-sharing and collaboration decisions.'),
('001473','draft','2009-09-29','DISA FSO','policy','Designate individuals authorized to post information onto a publicly accessible system.','AC-22a.','N/A','Determine if designated individuals are authorized to make information publicly accessible.'),
('001474','draft','2009-09-29','DISA FSO','policy','Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information.','AC-22b.','N/A','Determine if authorized individuals are trained to ensure that publicly accessible information does not contain non-public information.'),
('001475','draft','2009-09-29','DISA FSO','policy','Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included.','AC-22c.','N/A','Determine if the proposed content of information is reviewed prior to posting onto the publicly accessible system to ensure that non-public information is not included.'),
('001476','draft','2009-09-29','DISA FSO','policy','Review the content on the publicly accessible system for nonpublic information on an organization-defined frequency.','AC-22d.','N/A','Determine if: - the content on the publicly accessible system is reviewed for non-public information [AC-22_ODP; the frequency at which to review the content on the publicly accessible system for non-public information is defined]. - non-public information is removed from the publicly accessible system, if discovered.'),
('001477','draft','2009-09-29','DISA FSO','policy','Defines a frequency for reviewing the content on the publicly accessible system for nonpublic information.','AC-22d.','N/A','Determine if: - the content on the publicly accessible system is reviewed for non-public information [AC-22_ODP; the frequency at which to review the content on the publicly accessible system for non-public information is defined]. - non-public information is removed from the publicly accessible system, if discovered.'),
('001478','draft','2009-09-29','DISA FSO','policy','Remove nonpublic information from the publicly accessible system, if discovered.','AC-22d.','N/A','Determine if: - the content on the publicly accessible system is reviewed for non-public information [AC-22_ODP; the frequency at which to review the content on the publicly accessible system for non-public information is defined]. - non-public information is removed from the publicly accessible system, if discovered.'),
('001481','draft','2009-09-29','DISA FSO','policy','Provide organization-defined personnel or roles with initial training in the employment and operation of environmental controls.','AT-03(01)','N/A','Determine if [AT-03(01)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of environmental controls are defined] are provided with initial and refresher training [AT-03(01)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of environmental controls is defined] in the employment and operation of environmental controls.'),
('001482','draft','2009-09-29','DISA FSO','policy','Provide organization-defined personnel or roles with refresher training in the employment and operation of environmental controls in accordance with the organization-defined frequency.','AT-03(01)','N/A','Determine if [AT-03(01)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of environmental controls are defined] are provided with initial and refresher training [AT-03(01)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of environmental controls is defined] in the employment and operation of environmental controls.'),
('001483','draft','2009-09-29','DISA FSO','policy','Defines a frequency for providing employees with refresher training in the employment and operation of environmental controls.','AT-03(01)','N/A','Determine if [AT-03(01)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of environmental controls are defined] are provided with initial and refresher training [AT-03(01)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of environmental controls is defined] in the employment and operation of environmental controls.'),
('001484','draft','2009-09-29','DISA FSO','policy','Defines the frequency of (or situation requiring) logging for each identified event.','AU-02c.','N/A','Determine if: - [AU-02_ODP[02]; the event types (subset of AU-02_ODP[01]) for logging within the system are defined] are specified for logging within the system. - the specified event types are logged within the system [AU-02_ODP[03]; the frequency or situation requiring logging for each specified event type is defined].'),
('001485','draft','2009-09-29','DISA FSO','policy','Defines the event types for logging within the system.','AU-02c.','N/A','Determine if: - [AU-02_ODP[02]; the event types (subset of AU-02_ODP[01]) for logging within the system are defined] are specified for logging within the system. - the specified event types are logged within the system [AU-02_ODP[03]; the frequency or situation requiring logging for each specified event type is defined].'),
('001487','draft','2009-09-29','DISA FSO','technical','Ensure that audit records containing information that establishes the identity of any individuals, subjects, or objects/entities associated with the event.','AU-03f.','N/A','Determine if audit records contain information that establishes the identity of any individuals, subjects, or objects/entities associated with the event.'),
('001488','draft','2009-09-29','DISA FSO','policy','Defines the additional information to be included in the audit records.','AU-03(01)','N/A','Determine if generated audit records contain the following [AU-03(01)_ODP; additional information to be included in audit records is defined].'),
('001490','draft','2009-09-29','DISA FSO','policy','Defines the actions to be taken by the system upon audit failure, including shutting down the system, overwriting oldest audit records, and stopping the generation of audit records.','AU-05b.','N/A','Determine if [AU-05_ODP[03]; additional actions to be taken in the event of an audit logging process failure are defined] are taken in the event of an audit logging process failure.'),
('001491','draft','2009-09-29','DISA FSO','policy','Correlate information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.','AU-06(06)','N/A','Determine if information from audit records is correlated with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.'),
('001493','draft','2009-09-29','DISA FSO','technical','Protect audit tools from unauthorized access.','AU-09a.','N/A','Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion.'),
('001494','draft','2009-09-29','DISA FSO','technical','Protect audit tools from unauthorized modification.','AU-09a.','N/A','Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion.'),
('001495','draft','2009-09-29','DISA FSO','technical','Protect audit tools from unauthorized deletion.','AU-09a.','N/A','Determine if audit information and audit logging tools are protected from unauthorized access, modification, and deletion.'),
('001496','draft','2009-09-29','DISA FSO','technical','Implement cryptographic mechanisms to protect the integrity of audit tools.','AU-09(03)','N/A','Determine if cryptographic mechanisms to protect the integrity of audit information and audit tools are implemented.'),
('001497','draft','2009-09-29','DISA FSO','policy','Defines a frequency for the review and update to the baseline configuration of the system.','CM-02b.01','N/A','Determine if the baseline configuration of the system is reviewed and updated [CM-02_ODP[01]; the frequency of baseline configuration review and update is defined].'),
('001498','draft','2009-09-29','DISA FSO','policy','Defines a time period after which proposed changes to the system that have not been approved or disapproved are highlighted.','CM-03(01)(c)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to highlight proposed changes to the system that have not been approved or disapproved within [CM-03(01)_ODP[03]l the time period after which to highlight changes that have not been approved or disapproved is defined].'),
('001499','draft','2009-09-29','DISA FSO','technical','Limit privileges to change software resident within software libraries.','CM-05(06)','N/A','Determine if privileges to change software resident within software libraries are limited.'),
('001504','draft','2009-11-02','DISA FSO','policy','Develop and document an organization-level; mission/business process-level; and/or system-level personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PS-01a.01(a)','N/A','Determine if: - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses purpose. - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses scope. - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses roles. - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses responsibilities. - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses management commitment. - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses coordination among organizational entities. - the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy addresses compliance.'),
('001505','draft','2009-11-02','DISA FSO','policy','Disseminate an organization-level; mission/business process-level; and/or system-level personnel security policy to organization-defined personnel or roles.','PS-01a.','N/A','Determine if: - a personnel security policy is developed and documented. - the personnel security policy is disseminated to [PS-01_ODP[01]; personnel or roles to whom the personnel security policy is to be disseminated is/are defined].'),
('001506','draft','2009-11-02','DISA FSO','policy','Review and update the current personnel security policy in accordance with organization-defined frequency.','PS-01c.01','N/A','Determine if: - the current personnel security policy is reviewed and updated [PS-01_ODP[05]; the frequency at which the current personnel security policy is reviewed and updated is defined]. - the current personnel security policy is reviewed and updated following [PS-01_ODP[06]; events that would require the current personnel security policy to be reviewed and updated are defined].'),
('001507','draft','2009-11-02','DISA FSO','policy','Defines the frequency with which to review and update the current personnel security policy.','PS-01c.01','N/A','Determine if: - the current personnel security policy is reviewed and updated [PS-01_ODP[05]; the frequency at which the current personnel security policy is reviewed and updated is defined]. - the current personnel security policy is reviewed and updated following [PS-01_ODP[06]; events that would require the current personnel security policy to be reviewed and updated are defined].'),
('001508','draft','2009-11-02','DISA FSO','policy','Defines the frequency with which to review and update the current personnel security procedures.','PS-01c.02','N/A','Determine if: - the current personnel security procedures are reviewed and updated [PS-01_ODP[07]; the frequency at which the current personnel security procedures are reviewed and updated is defined]. - the current personnel security procedures are reviewed and updated following [PS-01_ODP[08]; events that would require the personnel security procedures to be reviewed and updated are defined].'),
('001509','draft','2009-11-02','DISA FSO','policy','Develop and document procedures to facilitate the implementation of the personnel security policy and associated personnel security controls.','PS-01a.02','N/A','Determine if: - Determine if personnel security procedures to facilitate the implementation of the personnel security policy and associated personnel security controls are developed and documented. - the personnel security procedures are disseminated to [PS-01_ODP[02]; personnel or roles to whom the personnel security procedures are to be disseminated is/are defined].'),
('001510','draft','2009-11-02','DISA FSO','policy','Disseminate personnel security procedures to organization-defined personnel or roles.','PS-01a.02','N/A','Determine if: - Determine if personnel security procedures to facilitate the implementation of the personnel security policy and associated personnel security controls are developed and documented. - the personnel security procedures are disseminated to [PS-01_ODP[02]; personnel or roles to whom the personnel security procedures are to be disseminated is/are defined].'),
('001511','draft','2009-11-02','DISA FSO','policy','Review and update the current personnel security procedures in accordance with organization-defined frequency.',NULL,'N/A',NULL),
('001512','draft','2009-11-02','DISA FSO','policy','Assign a risk designation to all organizational positions.','PS-02a.','N/A','Determine if a risk designation is assigned to all organizational positions.'),
('001513','draft','2009-11-02','DISA FSO','policy','Establish screening criteria for individuals filling organizational positions.','PS-02b.','N/A','Determine if screening criteria are established for individuals filling organizational positions.'),
('001514','draft','2009-11-02','DISA FSO','policy','Review and update position risk designations in accordance with organization-defined frequency.','PS-02c.','N/A','Determine if position risk designations are reviewed and updated [PS-02_ODP; the frequency at which to review and update position risk designations is defined].'),
('001515','draft','2009-11-02','DISA FSO','policy','Defines the frequency with which to review and update position risk designations.','PS-02c.','N/A','Determine if position risk designations are reviewed and updated [PS-02_ODP; the frequency at which to review and update position risk designations is defined].'),
('001516','draft','2009-11-02','DISA FSO','policy','Screen individuals prior to authorizing access to the system.','PS-03a.','N/A','Determine if individuals are screened prior to authorizing access to the system.'),
('001517','draft','2009-11-02','DISA FSO','policy','Rescreen individuals with authorized access to the system in accordance with organization-defined conditions requiring rescreening, and where rescreening is so indicated, on the organization-defined frequency of rescreening.','PS-03b.','N/A','Determine if: - individuals are rescreened in accordance with [PS-03_ODP[01]; conditions requiring rescreening of individuals are defined]. - where rescreening is so indicated, individuals are rescreened [PS-03_ODP[02]; the frequency of rescreening individuals where it is so indicated is defined].'),
('001518','draft','2009-11-02','DISA FSO','policy','Defines the conditions requiring rescreening of individuals with authorized access to the system.','PS-03b.','N/A','Determine if: - individuals are rescreened in accordance with [PS-03_ODP[01]; conditions requiring rescreening of individuals are defined]. - where rescreening is so indicated, individuals are rescreened [PS-03_ODP[02]; the frequency of rescreening individuals where it is so indicated is defined].'),
('001519','draft','2009-11-02','DISA FSO','policy','Defines the frequency for rescreening individuals with authorized access to the information system when organization-defined conditions requiring rescreening are met.','PS-03b.','N/A','Determine if: - individuals are rescreened in accordance with [PS-03_ODP[01]; conditions requiring rescreening of individuals are defined]. - where rescreening is so indicated, individuals are rescreened [PS-03_ODP[02]; the frequency of rescreening individuals where it is so indicated is defined].'),
('001520','draft','2009-11-02','DISA FSO','policy','Verify that individuals accessing a system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the information to which they have access on the system.','PS-03(01)','N/A','Determine if: - individuals accessing a system processing, storing, or transmitting classified information are cleared. - individuals accessing a system processing, storing, or transmitting classified information are indoctrinated to the highest classification level of the information to which they have access on the system.'),
('001521','draft','2009-11-02','DISA FSO','policy','Verify that individuals accessing a system processing, storing, or transmitting types of classified information which require formal indoctrination, are formally indoctrinated for all of the relevant types of information to which they have access on the system.','PS-03(02)','N/A','Determine if individuals accessing a system processing, storing, or transmitting types of classified information that require formal indoctrination are formally indoctrinated for all of the relevant types of information to which they have access on the system.'),
('001522','draft','2009-11-02','DISA FSO','policy','Upon termination of individual employment, disable system access within an organization-defined time period.','PS-04a.','N/A','Determine if upon termination of individual employment, system access is disabled within [PS-04_ODP[01]; a time period within which to disable system access is defined].'),
('001523','draft','2009-11-02','DISA FSO','policy','Upon termination of individual employment, conduct exit interviews that include a discussion of organization-defined information security topics.','PS-04c.','N/A','Determine if upon termination of individual employment, exit interviews that include a discussion of [PS-04_ODP[02]; information security topics to be discussed when conducting exit interviews are defined] are conducted.'),
('001524','draft','2009-11-02','DISA FSO','policy','Upon termination of individual employment, retrieve all security-related organizational system-related property.','PS-04d.','N/A','Determine if upon termination of individual employment, all security-related organizational system-related property is retrieved.'),
('001525','draft','2009-11-02','DISA FSO','policy','Upon termination of individual employment, retain access to organizational information formerly controlled by the terminated individual.','PS-04e.','N/A','Determine if upon termination of individual employment, access to organizational information and systems formerly controlled by the terminated individual are retained.'),
('001526','draft','2009-11-02','DISA FSO','policy','Upon termination of individual employment, retain access to organizational systems formerly controlled by the terminated individual.','PS-04e.','N/A','Determine if upon termination of individual employment, access to organizational information and systems formerly controlled by the terminated individual are retained.'),
('001527','draft','2009-11-03','DISA FSO','policy','Review and confirm the ongoing operational need for current logical and physical access authorizations to systems and facilities when individuals are reassigned or transferred to other positions within the organization.','PS-05a.','N/A','Determine if the ongoing operational need for current logical and physical access authorizations to systems and facilities are reviewed and confirmed when individuals are reassigned or transferred to other positions within the organization.'),
('001528','draft','2009-11-03','DISA FSO','policy','Initiate organization-defined transfer or reassignment actions within an organization-defined time period following the formal personnel transfer action.','PS-05b.','N/A','Determine if [PS-05_ODP[01]; transfer or reassignment actions to be initiated following transfer or reassignment are defined] are initiated within [PS-05_ODP[02]; the time period within which transfer or reassignment actions must occur following transfer or reassignment is defined].'),
('001529','draft','2009-11-03','DISA FSO','policy','Defines transfer or reassignment actions to initiate within an organization-defined time period following the formal personnel transfer action.','PS-05b.','N/A','Determine if [PS-05_ODP[01]; transfer or reassignment actions to be initiated following transfer or reassignment are defined] are initiated within [PS-05_ODP[02]; the time period within which transfer or reassignment actions must occur following transfer or reassignment is defined].'),
('001530','draft','2009-11-03','DISA FSO','policy','Defines the time period within which the organization initiates organization-defined transfer or reassignment actions following the formal personnel transfer action.','PS-05b.','N/A','Determine if [PS-05_ODP[01]; transfer or reassignment actions to be initiated following transfer or reassignment are defined] are initiated within [PS-05_ODP[02]; the time period within which transfer or reassignment actions must occur following transfer or reassignment is defined].'),
('001532','draft','2009-11-03','DISA FSO','policy','Review and update the access agreements for organizational systems in accordance with organization-defined frequency.','PS-06b.','N/A','Determine if the access agreements are reviewed and updated [PS-06_ODP[01]; the frequency at which to review and update access agreements is defined].'),
('001533','draft','2009-11-03','DISA FSO','policy','Defines the frequency with which to review and update access agreements for organizational systems.','PS-06b.','N/A','Determine if the access agreements are reviewed and updated [PS-06_ODP[01]; the frequency at which to review and update access agreements is defined].'),
('001536','draft','2009-11-03','DISA FSO','policy','Verify that access to classified information requiring special protection is granted only to individuals who have a valid access authorization that is demonstrated by assigned official government duties.','PS-06(02)(a)','N/A','Determine if access to classified information requiring special protection is granted only to individuals who have a valid access authorization that is demonstrated by assigned official government duties.'),
('001537','draft','2009-11-03','DISA FSO','policy','Verify that access to classified information requiring special protection is granted only to individuals who satisfy associated personnel security criteria.','PS-06(02)(b)','N/A','Determine if access to classified information requiring special protection is granted only to individuals who satisfy associated personnel security criteria.'),
('001538','draft','2009-11-03','DISA FSO','policy','Verify that access to classified information requiring special protection is granted only to individuals who have read, understood, and signed a nondisclosure agreement.','PS-06(02)(c)','N/A','Determine if access to classified information requiring special protection is granted only to individuals who have read, understood, and signed a non-disclosure agreement.'),
('001539','draft','2009-11-03','DISA FSO','policy','Establish personnel security requirements including security roles and responsibilities for external providers.','PS-07a.','N/A','Determine if personnel security requirements are established, including security roles and responsibilities for external providers.'),
('001540','draft','2009-11-03','DISA FSO','policy','Document personnel security requirements.','PS-07c.','N/A','Determine if personnel security requirements are documented.'),
('001541','draft','2009-11-03','DISA FSO','policy','Monitor provider compliance with personnel security requirements.','PS-07e.','N/A','Determine if provider compliance with personnel security requirements is monitored.'),
('001544','draft','2009-11-30','DISA FSO','policy','Manage system authenticators by ensuring that authenticators have sufficient strength of mechanism for their intended use.','IA-05c.','N/A','Determine if system authenticators are managed to ensure that authenticators have sufficient strength of mechanism for their intended use.'),
('001545','draft','2010-05-11','DISA FSO','policy','Defines a frequency for reviewing and updating the access control policy.','AC-01c.01','N/A','Determine if: - the current access control policy is reviewed and updated [AC-01_ODP[05]; the frequency at which the current access control policy is reviewed and updated is defined]. - the current access control policy is reviewed and updated following [AC-01_ODP[06]; events that would require the current access control policy to be reviewed and updated are defined].'),
('001546','draft','2010-05-11','DISA FSO','policy','Defines a frequency for reviewing and updating the access control procedures.','AC-01c.02','N/A','Determine if: - the current access control procedures are reviewed and updated [AC-01_ODP[07]; the frequency at which the current access control procedures are reviewed and updated is defined;]. - the current access control procedures are reviewed and updated following [AC-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('001547','draft','2010-05-11','DISA FSO','policy','Defines the frequency on which it will review information system accounts for compliance with account management requirements.','AC-02j.','N/A','Determine if accounts are reviewed for compliance with account management requirements [AC-02_ODP[10]; the frequency of account review is defined].'),
('001548','draft','2010-05-11','DISA FSO','policy','Defines the information flow control policies for controlling the flow of information within the system.','AC-04','N/A','Determine if approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on [AC-04_ODP; information flow control policies within the system and between connected systems are defined].'),
('001549','draft','2010-05-11','DISA FSO','policy','Defines the information flow control policies for controlling the flow of information between interconnected systems.','AC-04','N/A','Determine if approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on [AC-04_ODP; information flow control policies within the system and between connected systems are defined].'),
('001553','draft','2010-05-11','DISA FSO','policy','Defines security or privacy policy filters that privileged administrators have the capability to enable and disable.','AC-04(10)','N/A','Determine if: - capability is provided for privileged administrators to enable and disable [AC-04(10)_ODP[01]; security policy filters that privileged administrators have the capability to enable and disable are defined] under [AC-04(10)_ODP[03]; conditions under which privileged administrators have the capability to enable and disable security policy filters are defined]. - capability is provided for privileged administrators to enable and disable [AC-04(10)_ODP[02]; privacy policy filters that privileged administrators have the capability to enable and disable are defined] under [AC-04(10)_ODP[04]; conditions under which privileged administrators have the capability to enable and disable privacy policy filters are defined].'),
('001554','draft','2010-05-11','DISA FSO','policy','Defines the security or privacy policy filters that privileged administrators have the capability to configure.','AC-04(11)','N/A','Determine if: - capability is provided for privileged administrators to configure [AC-04(11)_ODP[01]; security policy filters that privileged administrators have the capability to configure to support different security and privacy policies are defined] to support different security or privacy policies. - capability is provided for privileged administrators to configure [AC-04(11)_ODP[02]; privacy policy filters that privileged administrators have the capability to configure to support different security and privacy policies are defined] to support different security or privacy policies.'),
('001558','draft','2010-05-11','DISA FSO','policy','Defines the security functions (deployed in hardware, software, and firmware) for which access must be authorized.','AC-06(01)(a)','N/A','Determine if: - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[02]; security functions (deployed in hardware) for authorized access are defined]. - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[03]; security functions (deployed in software) for authorized access are defined]. - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[04]; security functions (deployed in firmware) for authorized access are defined].'),
('001564','draft','2010-05-11','DISA FSO','policy','Defines the frequency of security awareness and training policy reviews and updates.','AT-01c.01','N/A','Determine if: - the current awareness and training policy is reviewed and updated [AT-01_ODP[05]; the frequency at which the current awareness and training policy is reviewed and updated is defined]. - the current awareness and training policy is reviewed and updated following [AT-01_ODP[06]; events that would require the current awareness and training policy to be reviewed and updated are defined].'),
('001565','draft','2010-05-11','DISA FSO','policy','Defines the frequency of security awareness and training procedure reviews and updates.','AT-01c.02','N/A','Determine if: - the current awareness and training procedures are reviewed and updated [AT-01_ODP[07]; the frequency at which the current awareness and training procedures are reviewed and updated is defined]. - the current awareness and training procedures are reviewed and updated following [AT-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('001566','draft','2010-05-11','DISA FSO','policy','Provide organization-defined personnel or roles with initial training in the employment and operation of physical security controls.','AT-03(02)','N/A','Determine if [AT-03(02)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of physical security controls is/are defined] is/are provided with initial and refresher training [AT-03(02)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of physical security controls is defined] in the employment and operation of physical security controls.'),
('001567','draft','2010-05-11','DISA FSO','policy','Provide organization-defined personnel or roles with refresher training, thereafter, in the employment and operation of physical security controls in accordance with the organization-defined frequency.','AT-03(02)','N/A','Determine if [AT-03(02)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of physical security controls is/are defined] is/are provided with initial and refresher training [AT-03(02)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of physical security controls is defined] in the employment and operation of physical security controls.'),
('001568','draft','2010-05-11','DISA FSO','policy','Defines a frequency for providing employees with refresher training in the employment and operation of physical security controls.','AT-03(02)','N/A','Determine if [AT-03(02)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of physical security controls is/are defined] is/are provided with initial and refresher training [AT-03(02)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of physical security controls is defined] in the employment and operation of physical security controls.'),
('001569','draft','2010-05-11','DISA FSO','policy','Defines the frequency on which the current audit and accountability policy will be reviewed and updated.','AU-01c.01','N/A','Determine if: - the current audit and accountability policy is reviewed and updated [AU-01_ODP[05]; the frequency at which the current audit and accountability policy is reviewed and updated is defined]. - the current audit and accountability policy is reviewed and updated following [AU-01_ODP[06]; events that would require the current audit and accountability policy to be reviewed and updated are defined.]'),
('001570','draft','2010-05-11','DISA FSO','policy','Defines the frequency on which the current audit and accountability procedures will be reviewed and updated.','AU-01c.02','N/A','Determine if: - the current audit and accountability procedures are reviewed and updated [AU-01_ODP[07]; the frequency at which the current audit and accountability procedures are reviewed and updated is defined]. - the current audit and accountability procedures are reviewed and updated following [AU-01_ODP[08]; events that would require audit and accountability procedures to be reviewed and updated are defined].'),
('001571','draft','2010-05-11','DISA FSO','policy','Defines the event types that the system is capable of logging in support of the audit function.','AU-02a.','N/A','Determine if [AU-02_ODP[01]; the event types that the system is capable of logging in support of the audit function are defined] that the system is capable of logging are identified in support of the audit logging function.'),
('001572','draft','2010-05-11','DISA FSO','policy','Defines the personnel or roles to be alerted in the event of an audit logging process failure.','AU-05a.','N/A','Determine if [AU-05_ODP[01]; personnel or roles receiving audit logging process failure alerts are defined] are alerted in the event of an audit logging process failure within [AU-05_ODP[02]; time period for personnel or roles receiving audit logging process failure alerts is defined].'),
('001573','draft','2010-05-11','DISA FSO','policy','Defines whether to reject or delay network traffic that exceeds organization-defined thresholds.','AU-05(03)','N/A','Determine if: - configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity are enforced. - network traffic is [AU-05(03)_ODP; one or more of the following PARAMETER VALUES is/are selected: {reject; delay}] if network traffic volume is above configured thresholds.'),
('001577','draft','2010-05-11','DISA FSO','policy','Defines the system components from which audit records are to be compiled into the system-wide audit trail.','AU-12(01)','N/A','Determine if audit records from [AU-12(01)_ODP[01]; system components from which audit records are to be compiled into a system-wide (logical or physical) audit trail are defined] are compiled into a system-wide (logical or physical) audit trail that is time-correlated to within [AU-12(01)_ODP[02]; level of tolerance for the relationship between timestamps of individual records in the audit trail is defined].'),
('001578','draft','2010-05-11','DISA FSO','policy','Defines the frequency to review and update the current assessment, authorization, and monitoring procedures.','CA-01c.02','N/A','Determine if: - the current assessment, authorization, and monitoring procedures are reviewed and updated [CA-01_ODP[07]; the frequency at which the current assessment, authorization, and monitoring procedures are reviewed and updated is defined]. - the current assessment, authorization, and monitoring procedures are reviewed and updated following [CA-01_ODP[08]; events that would require assessment, authorization, and monitoring procedures to be reviewed and updated are defined].'),
('001582','draft','2010-05-11','DISA FSO','policy','Defines other forms of control assessments other than in-depth monitoring; security instrumentation; automated security test cases; vulnerability scanning; malicious user testing; insider threat assessment; performance and load testing; data leakage or data loss assessment that should be included as part of the control assessments.','CA-02(02)','N/A','Determine if [CA-02(02)_ODP[01]; frequency at which to include specialized assessments as part of the control assessment is defined] [CA-02(02)_ODP[02]; one of the following PARAMETER VALUES is selected: {announced; unannounced}] [CA-02(02)_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {in-depth monitoring; security instrumentation; automated security test cases; vulnerability scanning; malicious user testing; insider threat assessment; performance and load testing; data leakage or data loss assessment; [CA-02(02)_ODP[04]; other forms of assessment are defined (if selected)]}] are included as part of control assessments.'),
('001584','draft','2010-05-11','DISA FSO','policy','Defines the frequency with which to review and update configuration management procedures.','CM-01c.02','N/A','Determine if: - the current configuration management procedures are reviewed and updated [CM-01_ODP[07]; the frequency at which the current configuration management procedures are reviewed and updated is defined]. - the current configuration management procedures are reviewed and updated following [CM-01_ODP[08]; events that would require configuration management procedures to be reviewed and updated are defined].'),
('001585','draft','2010-05-12','DISA FSO','policy','Defines the circumstances that require reviews and updates to the baseline configuration of the system.','CM-02b.02','N/A','Determine if the baseline configuration of the system is reviewed and updated when required due to [CM-02_ODP[02]; the circumstances requiring baseline configuration review and update are defined].'),
('001586','draft','2010-05-12','DISA FSO','policy','Defines the configuration change control element responsible for coordinating and providing oversight for configuration change control activities.','CM-03g.','N/A','Determine if: - configuration change control activities are coordinated and overseen by [CM-03_ODP[02]; the configuration change control element responsible for coordinating and overseeing change control activities is defined]. - the configuration control element convenes [CM-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[CM-03_ODP[04]; the frequency at which the configuration control element convenes is defined (if selected)]; when [CM-03_ODP[05]; configuration change conditions that prompt the configuration control element to convene are defined (if selected)]}]].'),
('001592','draft','2010-05-12','DISA FSO','policy','Defines the rules authorizing the terms and conditions of software program usage on the system.','CM-07(02)','N/A','Determine if program execution is prevented in accordance with [CM-07(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[CM-07(02)_ODP[02]; policies, rules of behavior, and/or access agreements regarding software program usage and restrictions are defined (if selected)]; rules authorizing the terms and conditions of software program usage}].'),
('001596','draft','2010-05-12','DISA FSO','policy','Defines the frequency with which to review and update the current contingency planning procedures.','CP-01c.02','N/A','Determine if: - the current contingency planning procedures are reviewed and updated [CP-01_ODP[07]; the frequency at which the current contingency planning procedures are reviewed and updated is defined]. - the current contingency planning procedures are reviewed and updated following [CP-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('001597','draft','2010-05-12','DISA FSO','policy','Disseminate contingency planning procedures to organization-defined personnel or roles.','CP-01a.02','N/A','Determine if: - contingency planning procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls are developed and documented. - the contingency planning procedures are disseminated to [CP-01_ODP[02]; personnel or roles to whom the contingency planning procedures are to be disseminated is/are defined].'),
('001598','draft','2010-05-12','DISA FSO','policy','Review and update the current contingency planning procedures in accordance with the organization-defined frequency.','CP-01c.02','N/A','Determine if: - the current contingency planning procedures are reviewed and updated [CP-01_ODP[07]; the frequency at which the current contingency planning procedures are reviewed and updated is defined]. - the current contingency planning procedures are reviewed and updated following [CP-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('001599','draft','2010-05-12','DISA FSO','policy','Sustain operational continuity of essential missions until full system restoration at primary processing and/or storage sites.','CP-02(05)','N/A','Determine if: - the continuance of [CP-02(05)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions with minimal or no loss of operational continuity is planned for. - continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('001600','draft','2010-05-12','DISA FSO','policy','Sustains operational continuity of essential business functions until full system restoration at primary processing and/or storage sites.','CP-02(05)','N/A','Determine if: - the continuance of [CP-02(05)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions with minimal or no loss of operational continuity is planned for. - continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('001601','draft','2010-05-12','DISA FSO','policy','Sustain operational continuity of essential mission functions at alternate processing and/or storage sites until system restoration to primary processing and/or storage sites.','CP-02(06)','N/A','Determine if: - the transfer of [CP-02(06)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity is planned for. - operational continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('001602','draft','2010-05-12','DISA FSO','policy','Sustain operational continuity of essential business functions at alternate processing and/or storage sites until system restoration at primary processing and/or storage sites.','CP-02(06)','N/A','Determine if: - the transfer of [CP-02(06)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity is planned for. - operational continuity is sustained until full system restoration at primary processing and/or storage sites.'),
('001604','draft','2010-05-12','DISA FSO','policy','Outline explicit mitigation actions for potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster.','CP-06(03)','N/A','Determine if: - potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster are identified. - explicit mitigation actions to address identified accessibility problems are outlined.'),
('001606','draft','2010-05-12','DISA FSO','policy','Identify potential accessibility problems to outline explicit mitigation actions.','CP-07(02)','N/A','Determine if: - potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster are identified. - explicit mitigation actions to address identified accessibility problems are outlined.'),
('001609','draft','2010-05-12','DISA FSO','policy','Activate the redundant secondary system that is not collocated with the primary system without loss of information or disruption to operations.','CP-09(06)','N/A','Determine if: - system backup is conducted by maintaining a redundant secondary system that is not collocated with the primary system. - system backup is conducted by maintaining a redundant secondary system that can be activated without loss of information or disruption to operations.'),
('001610','draft','2010-05-12','DISA FSO','policy','Defines the time-period (by authenticator type) for changing/refreshing authenticators.','IA-05f.','N/A','Determine if system authenticators are managed through the change or refreshment of authenticators [IA-05_ODP[01]; a time period for changing or refreshing authenticators by authenticator type is defined] or when [IA-05_ODP[02]; events that trigger the change or refreshment of authenticators are defined] occur.'),
('001621','draft','2010-05-12','DISA FSO','policy','Implement organization-defined security controls to manage the risk of compromise due to individuals having accounts on multiple systems.','IA-05(08)','N/A','Determine if [IA-05(08)_ODP; security controls implemented to manage the risk of compromise due to individuals having accounts on multiple systems are defined] are implemented to manage the risk of compromise due to individuals having accounts on multiple systems.'),
('001625','draft','2010-05-12','DISA FSO','policy','Implement the resulting incident handling activity changes to incident response procedures, training, and testing accordingly.','IR-04c.','N/A','Determine if: - lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing. - the changes resulting from the incorporated lessons learned are implemented accordingly.'),
('001628','draft','2010-05-12','DISA FSO','policy','Defines a frequency with which to review and update the current maintenance procedures.','MA-01c.02','N/A','Determine if: - the current maintenance procedures are reviewed and updated [MA-01_ODP[07]; the frequency with which the current maintenance procedures are reviewed and updated is defined]. - the current maintenance procedures are reviewed and updated following [MA-01_ODP[08]; events that would require the maintenance procedures to be reviewed and updated are defined].'),
('001631','draft','2010-05-12','DISA FSO','policy','After the service is performed, inspect and sanitize the component (for potentially malicious software) before reconnecting the component to the system.','MA-04(03)(b)','N/A','Determine if: - the component to be serviced is removed from the system prior to nonlocal maintenance or diagnostic services. - the component to be serviced is sanitized (for organizational information). - the component is inspected and sanitized (for potentially malicious software) after the service is performed and before reconnecting the component to the system.'),
('001632','draft','2010-05-12','DISA FSO','technical','Protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by either physically separated communications paths or logically separated communications paths based upon encryption.','MA-04(04)(b)(01)','N/A','Determine if nonlocal maintenance sessions are protected by separating maintenance sessions from other network sessions with the system by physically separated communication paths.'),
('001635','draft','2010-05-12','DISA FSO','policy','Remove individuals from the facility access list when access is no longer required.','PE-02d.','N/A','Determine if individuals are removed from the facility access list when access is no longer required.'),
('001636','draft','2010-05-12','DISA FSO','policy','Defines the frequency with which to review and update the current planning policy.','PL-01c.01','N/A','Determine if: - the current planning policy is reviewed and updated [PL-01_ODP[05]; the frequency with which the current planning policy is reviewed and updated is defined]. - the current planning policy is reviewed and updated following [PL-01_ODP[06]; events that would require the current planning policy to be reviewed and updated are defined].'),
('001637','draft','2010-05-12','DISA FSO','policy','Review and update the current planning policy in accordance with organization-defined frequency.','PL-01c.01','N/A','Determine if: - the current planning policy is reviewed and updated [PL-01_ODP[05]; the frequency with which the current planning policy is reviewed and updated is defined]. - the current planning policy is reviewed and updated following [PL-01_ODP[06]; events that would require the current planning policy to be reviewed and updated are defined].'),
('001638','draft','2010-05-12','DISA FSO','policy','Defines the frequency with which to review and update the current planning procedures.','PL-01c.02','N/A','Determine if: - the current planning procedures are reviewed and updated [PL-01_ODP[07]; the frequency with which the current planning procedures are reviewed and updated is defined]. - the current planning procedures are reviewed and updated following [PL-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('001640','draft','2010-05-12','DISA FSO','policy','Address information security issues in the updating of a critical infrastructure and key resources protection plan.','PM-08','N/A','Determine if: - information security issues are addressed in the development of a critical infrastructure and key resources protection plan. - information security issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - information security issues are addressed in the update of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the development of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the update of a critical infrastructure and key resources protection plan.'),
('001641','draft','2010-05-12','DISA FSO','policy','Defines the process for conducting random vulnerability scans on the system and hosted applications.','RA-05a.','N/A','Determine if: - systems and hosted applications are monitored for vulnerabilities [RA-05_ODP[01]; frequency for monitoring systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported. - systems and hosted applications are scanned for vulnerabilities [RA-05_ODP[02]; frequency for scanning systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported.'),
('001642','draft','2010-05-12','DISA FSO','policy','Defines the organizational document in which risk assessment results are documented (e.g., security plan, privacy plan; risk assessment report).',NULL,'N/A',NULL),
('001643','draft','2010-05-12','DISA FSO','policy','Monitor and scan for vulnerabilities in the system and hosted applications in accordance with the organization-defined process for random scans.','RA-05a.','N/A','Determine if: - systems and hosted applications are monitored for vulnerabilities [RA-05_ODP[01]; frequency for monitoring systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported. - systems and hosted applications are scanned for vulnerabilities [RA-05_ODP[02]; frequency for scanning systems and hosted applications for vulnerabilities is defined] and when new vulnerabilities potentially affecting the system are identified and reported.'),
('001645','draft','2010-05-12','DISA FSO','policy','The organization identifies the information system components to which privileged access is authorized for selected organization-defined vulnerability scanning activities.','RA-05(05)','N/A','Determine if privileged access authorization is implemented to [RA-05(05)_ODP[01]; system components to which privileged access is authorized for selected vulnerability scanning activities are defined] for [RA-05(05)_ODP[02]; vulnerability scanning activities selected for privileged access authorization to system components are defined].'),
('001646','draft','2010-05-12','DISA FSO','policy','Defines the frequency with which to review and update the current system and services acquisition procedures.','SA-01c.02','N/A','Determine if: - the current system and services acquisition procedures are reviewed and updated [SA-01_ODP[07]; the frequency at which the current system and services acquisition procedures are reviewed and updated is defined]. - the current system and services acquisition procedures are reviewed and updated following [SA-01_ODP[08]; events that would require the system and services acquisition procedures to be reviewed and updated are defined].'),
('001661','draft','2010-05-12','DISA FSO','policy','Defines the security functions, to at a minimum, include system authentication and re-authentication, for permitting users to invoke the trusted communications path.','SC-11b.','N/A','Determine if users are permitted to invoke the trusted communication path for communications between the user and the [SC-11_ODP[02]; security functions of the system are defined] of the system, including authentication and re-authentication, at a minimum.'),
('001662','draft','2010-05-12','DISA FSO','technical','Take organization-defined corrective action when organization-defined unacceptable mobile code is identified.','SC-18(01)','N/A','Determine if: - [SC-18(01)_ODP[01]; unacceptable mobile code to be identified is defined] is identified. - [SC-18(01)_ODP[02]; corrective actions to be taken when unacceptable mobile code is identified are defined] are taken if unacceptable mobile code is identified.'),
('001663','draft','2010-05-12','DISA FSO','technical','The information system, when operating as part of a distributed, hierarchical namespace, provides the means to enable verification of a chain of trust among parent and child domains (if the child supports secure resolution services).','SC-20b.','N/A','Determine if: - the means to indicate the security status of child zones (and if the child supports secure resolution services) is provided when operating as part of a distributed, hierarchical namespace. - the means to enable verification of a chain of trust among parent and child domains when operating as part of a distributed, hierarchical namespace is provided.'),
('001664','draft','2010-05-12','DISA FSO','technical','Recognize only session identifiers that are system-generated.','SC-23(03)','N/A','Determine if: - a unique session identifier is generated for each session with [SC-23(03)_ODP; randomness requirements for generating a unique session identifier for each session are defined]. - only system-generated session identifiers are recognized.'),
('001665','draft','2010-05-12','DISA FSO','technical','Preserve organization-defined system state information in the event of a system failure.','SC-24','N/A','Determine if [SC-24_ODP[01]; types of system failures for which the system components fail to a known state are defined] fail to a [SC-24_ODP[02]; known system state to which system components fail in the event of a system failure is defined] while preserving [SC-24_ODP[03]; system state information to be preserved in the event of a system failure is defined] in failure.'),
('001669','draft','2010-05-12','DISA FSO','policy','Defines the frequency of testing malicious code protection mechanisms.','SI-03(06)(a)','N/A','Determine if malicious code protection mechanisms are tested [SI-03(06)_ODP; the frequency at which to test malicious code protection mechanisms is defined] by introducing known benign code into the system.'),
('001670','draft','2010-05-12','DISA FSO','technical','Take organization-defined least-disruptive actions to terminate suspicious events.','SI-04(07)(b)','N/A','Determine if [SI-04(07)_ODP[02]; least-disruptive actions to terminate suspicious events are defined] are taken upon the detection of suspicious events.'),
('001671','draft','2010-05-12','DISA FSO','policy','Analyze outbound communications traffic at selected organization-defined interior points within the system to discover anomalies.','SI-04(11)','N/A','Determine if: - outbound communications traffic at the external interfaces to the system is analyzed to discover anomalies. - outbound communications traffic at [SI-04(11)_ODP; interior points within the system where communications traffic is to be analyzed are defined] is analyzed to discover anomalies. '),
('001673','draft','2010-05-12','DISA FSO','policy','Employ a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises or breaches to the system.','SI-04(14)','N/A','Determine if: - a wireless intrusion detection system is employed to identify rogue wireless devices. - a wireless intrusion detection system is employed to detect attack attempts on the system. - a wireless intrusion detection system is employed to detect potential compromises or breaches to the system.'),
('001675','draft','2010-05-12','DISA FSO','policy','Defines the personnel or roles that are to receive reports on the results of security function verification.','SI-06(03)','N/A','Determine if: - the results of security function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined]. - the results of privacy function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined].'),
('001678','draft','2010-05-12','DISA FSO','policy','Retain information within the system and information output from the system in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','SI-12','N/A','Determine if: - information within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements. - information within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements. - information output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements. - information output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.'),
('001680','draft','2010-06-09','DISA FSO','policy','Develop an organization-wide information security program plan that includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PM-01a.02','N/A','Determine if: - the information security program plan includes the identification and assignment of roles. - the information security program plan includes the identification and assignment of responsibilities. - the information security program plan addresses management commitment. - the information security program plan addresses coordination among organizational entities. - the information security program plan addresses compliance.'),
('001682','draft','2011-05-03','DISA FSO','technical','Automatically remove or disable emergency accounts after an organization-defined time period for each type of account.','AC-02(02)','N/A','Determine if temporary and emergency accounts are automatically [AC-02(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {remove; disable}] after [AC-02(02)_ODP[02]; the time period after which to automatically remove or disable temporary or emergency accounts is defined].'),
('001687','draft','2011-05-03','DISA FSO','policy','Verify that the use of mobile code deployed in system meets organization-defined mobile code requirements.','SC-18(02)','N/A','Determine if: - the acquisition of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the development of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the use of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined].'),
('001688','draft','2011-05-03','DISA FSO','policy','Verify the acquisition of mobile code deployed in the system meets organization-defined mobile code requirements.','SC-18(02)','N/A','Determine if: - the acquisition of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the development of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined]. - the use of mobile code to be deployed in the system meets [SC-18(02)_ODP; mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined].'),
('001695','draft','2011-10-07','DISA FSO','technical','Prevent the execution of organization-defined unacceptable mobile code.','SC-18(03)','N/A','Determine if: - the download of [SC-18(03)_ODP; unacceptable mobile code to be prevented from downloading and executing is defined] is prevented. - the execution of [SC-18(03)_ODP; unacceptable mobile code to be prevented from downloading and executing is defined] is prevented.'),
('001726','draft','2013-02-28','DISA FSO','policy','Use software in accordance with contract agreements.','CM-10a.','N/A','Determine if software and associated documentation are used in accordance with contract agreements and copyright laws.'),
('001727','draft','2013-02-28','DISA FSO','policy','Use software documentation in accordance with contract agreements.','CM-10a.','N/A','Determine if software and associated documentation are used in accordance with contract agreements and copyright laws.'),
('001728','draft','2013-02-28','DISA FSO','policy','Use software in accordance with copyright laws.','CM-10a.','N/A','Determine if software and associated documentation are used in accordance with contract agreements and copyright laws.'),
('001729','draft','2013-02-28','DISA FSO','policy','Use software documentation in accordance with copyright laws.','CM-10a.','N/A','Determine if software and associated documentation are used in accordance with contract agreements and copyright laws.'),
('001730','draft','2013-02-28','DISA FSO','policy','Track the use of software protected by quantity licenses to control copying of the software.','CM-10b.','N/A','Determine if the use of software and associated documentation protected by quantity licenses is tracked to control copying and distribution.'),
('001731','draft','2013-02-28','DISA FSO','policy','Track the use of software documentation protected by quantity licenses to control distribution of the software documentation.','CM-10b.','N/A','Determine if the use of software and associated documentation protected by quantity licenses is tracked to control copying and distribution.'),
('001732','draft','2013-02-28','DISA FSO','policy','Control the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.','CM-10c.','N/A','Determine if the use of peer-to-peer file sharing technology is controlled and documented to ensure that peer-to-peer file sharing is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.'),
('001733','draft','2013-02-28','DISA FSO','policy','Document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.','CM-10c.','N/A','Determine if the use of peer-to-peer file sharing technology is controlled and documented to ensure that peer-to-peer file sharing is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.'),
('001734','draft','2013-02-28','DISA FSO','policy','Defines the restrictions to be followed on the use of open source software.','CM-10(01)','N/A','Determine if [CM-10(01)_ODP; restrictions on the use of open-source software are defined] are established for the use of open-source software.'),
('001735','draft','2013-02-28','DISA FSO','policy','Establish organization-defined restrictions on the use of open source software.','CM-10(01)','N/A','Determine if [CM-10(01)_ODP; restrictions on the use of open-source software are defined] are established for the use of open-source software.'),
('001736','draft','2013-02-28','DISA FSO','policy','Defines the number of previous versions of the baseline configuration of the system required to support rollback.','CM-02(03)','N/A','Determine if [CM-02(03)_ODP; the number of previous baseline configuration versions to be retained is defined] of previous baseline configuration version(s) of the system is/are retained to support rollback.'),
('001737','draft','2013-02-28','DISA FSO','policy','Defines the systems or system components that are to have organization-defined configurations applied when located in areas of significant risk.','CM-02(07)(a)','N/A','Determine if [CM-02(07)_ODP[01]; the systems or system components to be issued when individuals travel to high-risk areas are defined] with [CM-02(07)_ODP[02]; configurations for systems or system components to be issued when individuals travel to high-risk areas are defined] are issued to individuals traveling to locations that the organization deems to be of significant risk.'),
('001738','draft','2013-02-28','DISA FSO','policy','Defines the configurations to be implemented on systems and system components when they are located in areas of significant risk.','CM-02(07)(a)','N/A','Determine if [CM-02(07)_ODP[01]; the systems or system components to be issued when individuals travel to high-risk areas are defined] with [CM-02(07)_ODP[02]; configurations for systems or system components to be issued when individuals travel to high-risk areas are defined] are issued to individuals traveling to locations that the organization deems to be of significant risk.'),
('001739','draft','2013-02-28','DISA FSO','policy','Issue organization-defined systems or system components with organization-defined configurations to individuals traveling to locations the organization deems to be of significant risk.','CM-02(07)(a)','N/A','Determine if [CM-02(07)_ODP[01]; the systems or system components to be issued when individuals travel to high-risk areas are defined] with [CM-02(07)_ODP[02]; configurations for systems or system components to be issued when individuals travel to high-risk areas are defined] are issued to individuals traveling to locations that the organization deems to be of significant risk.'),
('001740','draft','2013-02-28','DISA FSO','policy','Review proposed configuration-controlled changes to the system.','CM-03b.','N/A','Determine if: - proposed configuration-controlled changes to the system are reviewed. - proposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security and privacy impact analyses.'),
('001741','draft','2013-02-28','DISA FSO','policy','Document configuration change decisions associated with the system.','CM-03c.','N/A','Determine if configuration change decisions associated with the system are documented.'),
('001742','draft','2013-02-28','DISA FSO','policy','Defines the approval authorities to be notified when proposed changes to the system are received.','CM-03(01)(b)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to notify [CM-03(01)_ODP[02]; approval authorities to be notified of and request approval for proposed changes to the system are defined] of proposed changes to the system and request change approval.'),
('001743','draft','2013-02-28','DISA FSO','policy','Defines the security responses to be automatically implemented if baseline configurations are changed in an unauthorized manner.','CM-03(05)','N/A','Determine if [CM-03(05)_ODP; security responses to be automatically implemented are defined] are automatically implemented if baseline configurations are changed in an unauthorized manner.'),
('001744','draft','2013-02-28','DISA FSO','technical','Implement organization-defined security responses automatically if baseline configurations are changed in an unauthorized manner.','CM-03(05)','N/A','Determine if [CM-03(05)_ODP; security responses to be automatically implemented are defined] are automatically implemented if baseline configurations are changed in an unauthorized manner.'),
('001745','draft','2013-02-28','DISA FSO','policy','Defines the controls that are to be provided by the cryptographic mechanisms are under configuration management.','CM-03(06)','N/A','Determine if cryptographic mechanisms used to provide [CM-03(06)_ODP; controls provided by cryptographic mechanisms that are to be under configuration management are defined] are under configuration management.'),
('001746','draft','2013-02-28','DISA FSO','policy','Ensure that cryptographic mechanisms used to provide organization-defined control are under configuration management.','CM-03(06)','N/A','Determine if cryptographic mechanisms used to provide [CM-03(06)_ODP; controls provided by cryptographic mechanisms that are to be under configuration management are defined] are under configuration management.'),
('001751','draft','2013-02-28','DISA FSO','policy','Defines system-level information requiring enforcement of a dual authorization for system changes.','CM-05(04)','N/A','Determine if: - dual authorization for implementing changes to [CM-05(04)_ODP[01]; system components requiring dual authorization for changes are defined] is enforced. - dual authorization for implementing changes to [CM-05(04)_ODP[02]; system-level information requiring dual authorization for changes is defined] is enforced.'),
('001752','draft','2013-02-28','DISA FSO','policy','Enforce dual authorization for implementing changes to organization-defined system-level information.','CM-05(04)','N/A','Determine if: - dual authorization for implementing changes to [CM-05(04)_ODP[01]; system components requiring dual authorization for changes are defined] is enforced. - dual authorization for implementing changes to [CM-05(04)_ODP[02]; system-level information requiring dual authorization for changes is defined] is enforced.'),
('001753','draft','2013-02-28','DISA FSO','policy','Limit privileges to change system components within a production or operational environment.','CM-05(05)(a)','N/A','Determine if: - privileges to change system components within a production or operational environment are limited. - privileges to change system-related information within a production or operational environment are limited.'),
('001754','draft','2013-02-28','DISA FSO','policy','Limit privileges to change system-related information within a production or operational environment.','CM-05(05)(a)','N/A','Determine if: - privileges to change system components within a production or operational environment are limited. - privileges to change system-related information within a production or operational environment are limited.'),
('001755','draft','2013-02-28','DISA FSO','policy','Defines the system components for which any deviation from the established configuration settings are to be identified, documented, and approved.','CM-06c.','N/A','Determine if: - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are identified and documented based on [CM-06_ODP[03]; operational requirements necessitating approval of deviations are defined]. - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are approved.'),
('001756','draft','2013-02-28','DISA FSO','policy','Defines the operational requirements on which the configuration settings for the organization-defined system components are to be based.','CM-06c.','N/A','Determine if: - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are identified and documented based on [CM-06_ODP[03]; operational requirements necessitating approval of deviations are defined]. - any deviations from established configuration settings for [CM-06_ODP[02]; system components for which approval of deviations is needed are defined] are approved.'),
('001757','draft','2013-02-28','DISA FSO','policy','Defines the actions to employ when responding to unauthorized changes to the organization-defined configuration settings.','CM-06(02)','N/A','Determine if [CM-06(02)_ODP[01]; actions to be taken upon an unauthorized change are defined] are taken in response to unauthorized changes to [CM-06(02)_ODP[02]; configuration settings requiring action upon an unauthorized change are defined].'),
('001758','draft','2013-02-28','DISA FSO','policy','Defines the configuration settings for which to employ organization-defined actions in response to unauthorized changes.','CM-06(02)','N/A','Determine if [CM-06(02)_ODP[01]; actions to be taken upon an unauthorized change are defined] are taken in response to unauthorized changes to [CM-06(02)_ODP[02]; configuration settings requiring action upon an unauthorized change are defined].'),
('001759','draft','2013-02-28','DISA FSO','policy','Take organization-defined actions in response to unauthorized changes to organization-defined configuration settings.','CM-06(02)','N/A','Determine if [CM-06(02)_ODP[01]; actions to be taken upon an unauthorized change are defined] are taken in response to unauthorized changes to [CM-06(02)_ODP[02]; configuration settings requiring action upon an unauthorized change are defined].'),
('001760','draft','2013-02-28','DISA FSO','policy','Defines the frequency of system reviews to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services.','CM-07(01)(a)','N/A','Determine if the system is reviewed [CM-07(01)_ODP[01]; the frequency at which to review the system to identify unnecessary and/or non-secure functions, ports, protocols, software, and/or services is defined] to identify unnecessary and/or non-secure functions, ports, protocols, software, and services.'),
('001761','draft','2013-02-28','DISA FSO','policy','Defines the functions, ports, protocols, software, and services within the information system that are to be disabled or removed when deemed unnecessary and/or nonsecure.','CM-07(01)(b)','N/A','Determine if: - [CM-07(01)_ODP[02]; functions to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed. - [CM-07(01)_ODP[03]; ports to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed. - [CM-07(01)_ODP[04]; protocols to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed. - [CM-07(01)_ODP[05]; software to be disabled or removed when deemed unnecessary or non-secure is defined] deemed to be unnecessary and/or non-secure is disabled or removed. - [CM-07(01)_ODP[06]; services to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed.'),
('001762','draft','2013-02-28','DISA FSO','technical','Disable or remove organization-defined functions, ports, protocols, software, and services within the system deemed to be unnecessary and/or nonsecure.','CM-07(01)(b)','N/A','Determine if: - [CM-07(01)_ODP[02]; functions to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed. - [CM-07(01)_ODP[03]; ports to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed. - [CM-07(01)_ODP[04]; protocols to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed. - [CM-07(01)_ODP[05]; software to be disabled or removed when deemed unnecessary or non-secure is defined] deemed to be unnecessary and/or non-secure is disabled or removed. - [CM-07(01)_ODP[06]; services to be disabled or removed when deemed unnecessary or non-secure are defined] deemed to be unnecessary and/or non-secure are disabled or removed.'),
('001763','draft','2013-02-28','DISA FSO','policy','Defines the policies regarding software program usage and restrictions.','CM-07(02)','N/A','Determine if program execution is prevented in accordance with [CM-07(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[CM-07(02)_ODP[02]; policies, rules of behavior, and/or access agreements regarding software program usage and restrictions are defined (if selected)]; rules authorizing the terms and conditions of software program usage}].'),
('001764','draft','2013-02-28','DISA FSO','technical','Prevent program execution in accordance with organization-defined policies, rules of behavior, and/or access agreements regarding software program usage and restrictions; rules authorizing the terms and conditions of software program usage.','CM-07(02)','N/A','Determine if program execution is prevented in accordance with [CM-07(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[CM-07(02)_ODP[02]; policies, rules of behavior, and/or access agreements regarding software program usage and restrictions are defined (if selected)]; rules authorizing the terms and conditions of software program usage}].'),
('001765','draft','2013-02-28','DISA FSO','policy','Defines the software programs not authorized to execute on the system.','CM-07(04)(a)','N/A','Determine if [CM-07(04)_ODP[01]; software programs not authorized to execute on the system are defined] are identified.'),
('001766','draft','2013-02-28','DISA FSO','policy','Identify the organization-defined software programs not authorized to execute on the system.','CM-07(04)(a)','N/A','Determine if [CM-07(04)_ODP[01]; software programs not authorized to execute on the system are defined] are identified.'),
('001767','draft','2013-02-28','DISA FSO','technical','Employ an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the system.','CM-07(04)(b)','N/A','Determine if an allow-all, deny-by-exception policy is employed to prohibit the execution of unauthorized software programs on the system.'),
('001768','draft','2013-02-28','DISA FSO','policy','Defines the frequency on which the list of unauthorized software programs will be reviewed and updated.','CM-07(04)(c)','N/A','Determine if the list of unauthorized software programs is reviewed and updated [CM-07(04)_ODP[02]; frequency at which to review and update the list of unauthorized software programs is defined].'),
('001770','draft','2013-02-28','DISA FSO','policy','Review and update the list of unauthorized software programs per organization-defined frequency.','CM-07(04)(c)','N/A','Determine if the list of unauthorized software programs is reviewed and updated [CM-07(04)_ODP[02]; frequency at which to review and update the list of unauthorized software programs is defined].'),
('001772','draft','2013-02-28','DISA FSO','policy','Defines the software programs authorized to execute on the system.','CM-07(05)(a)','N/A','Determine if [CM-07(05)_ODP[01]; software programs authorized to execute on the system are defined] are identified.'),
('001773','draft','2013-02-28','DISA FSO','policy','Identify the organization-defined software programs authorized to execute on the system.','CM-07(05)(a)','N/A','Determine if [CM-07(05)_ODP[01]; software programs authorized to execute on the system are defined] are identified.'),
('001774','draft','2013-02-28','DISA FSO','technical','Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system.','CM-07(05)(b)','N/A','Determine if a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system is employed.'),
('001775','draft','2013-02-28','DISA FSO','policy','Defines the frequency on which the list of authorized software programs will be reviewed and updated.','CM-07(05)(c)','N/A','Determine if the list of authorized software programs is reviewed and updated [CM-07(05)_ODP[02]; frequency at which to review and update the list of authorized software programs is defined].'),
('001777','draft','2013-02-28','DISA FSO','policy','Review and update the list of authorized software programs per organization-defined frequency.','CM-07(05)(c)','N/A','Determine if the list of authorized software programs is reviewed and updated [CM-07(05)_ODP[02]; frequency at which to review and update the list of authorized software programs is defined].'),
('001779','draft','2013-02-28','DISA FSO','policy','Defines the frequency on which the system component inventory is to be reviewed and updated.','CM-08b.','N/A','Determine if the system component inventory is reviewed and updated [CM-08_ODP[02]; frequency at which to review and update the system component inventory is defined].'),
('001780','draft','2013-02-28','DISA FSO','policy','Review and update the system component inventory per organization-defined frequency.','CM-08b.','N/A','Determine if the system component inventory is reviewed and updated [CM-08_ODP[02]; frequency at which to review and update the system component inventory is defined].'),
('001783','draft','2013-03-01','DISA FSO','policy','Defines the personnel or roles to be notified when unauthorized hardware, software, and firmware components are detected within the system.','CM-08(03)(b)','N/A','Determine if: - [CM-08(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {disable network access by unauthorized components; isolate unauthorized components; notify [CM-08(03)_ODP[06]; personnel or roles to be notified when unauthorized components are detected is/are defined (if selected)]}] are taken when unauthorized hardware is detected. - [CM-08(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {disable network access by unauthorized components; isolate unauthorized components; notify [CM-08(03)_ODP[06]; personnel or roles to be notified when unauthorized components are detected is/are defined (if selected)]}] are taken when unauthorized software is detected. - [CM-08(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {disable network access by unauthorized components; isolate unauthorized components; notify [CM-08(03)_ODP[06]; personnel or roles to be notified when unauthorized components are detected is/are defined (if selected)]}] are taken when unauthorized software is detected.'),
('001784','draft','2013-03-01','DISA FSO','policy','When unauthorized hardware, software, and firmware components are detected within the system, the organization takes action to disable network access by such components, isolates the components, and/or notifies organization-defined personnel or roles.','CM-08(03)(b)','N/A','Determine if: - [CM-08(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {disable network access by unauthorized components; isolate unauthorized components; notify [CM-08(03)_ODP[06]; personnel or roles to be notified when unauthorized components are detected is/are defined (if selected)]}] are taken when unauthorized hardware is detected. - [CM-08(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {disable network access by unauthorized components; isolate unauthorized components; notify [CM-08(03)_ODP[06]; personnel or roles to be notified when unauthorized components are detected is/are defined (if selected)]}] are taken when unauthorized software is detected. - [CM-08(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {disable network access by unauthorized components; isolate unauthorized components; notify [CM-08(03)_ODP[06]; personnel or roles to be notified when unauthorized components are detected is/are defined (if selected)]}] are taken when unauthorized software is detected.'),
('001785','draft','2013-03-01','DISA FSO','policy','Provide a centralized repository for the inventory of system components.','CM-08(07)','N/A','Determine if a centralized repository for the system component inventory is provided.'),
('001786','draft','2013-03-01','DISA FSO','policy','Support the tracking of system components by geographic location using organization-defined automated mechanisms.','CM-08(08)','N/A','Determine if [CM-08(08)_ODP; automated mechanisms for tracking components are defined] are used to support the tracking of system components by geographic location.'),
('001788','draft','2013-03-01','DISA FSO','policy','Assign system components to a system.','CM-08(09)(a)','N/A','Determine if system components are assigned to a system.'),
('001789','draft','2013-03-01','DISA FSO','policy','Receive an acknowledgement from organization-defined personnel or roles of the acquired system components to a system.','CM-08(09)(b)','N/A','Determine if an acknowledgement of the component assignment is received from [CM-08(09)_ODP; personnel or roles from which to receive an acknowledgement is/are defined].'),
('001792','draft','2013-03-01','DISA FSO','policy','Implement a configuration management plan for the system that establishes a process for identifying configuration items throughout the system development life cycle.','CM-09b.','N/A','Determine if: - the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle. - the configuration management plan establishes a process for managing the configuration of the configuration items.'),
('001795','draft','2013-03-01','DISA FSO','policy','Implement a configuration management plan for the system that establishes a process for managing the configuration of the configuration items.','CM-09b.','N/A','Determine if: - the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle. - the configuration management plan establishes a process for managing the configuration of the configuration items.'),
('001798','draft','2013-03-01','DISA FSO','policy','Implement a configuration management plan for the system that places the configuration items under configuration management.','CM-09c.','N/A','Determine if: - the configuration management plan defines the configuration items for the system. - the configuration management plan places the configuration items under configuration management.'),
('001799','draft','2013-03-01','DISA FSO','policy','Develop and document a configuration management plan for the system that protects the configuration management plan from unauthorized disclosure and modification.','CM-09e.','N/A','Determine if: - the configuration management plan is protected from unauthorized disclosure. - the configuration management plan is protected from unauthorized modification.'),
('001801','draft','2013-03-01','DISA FSO','policy','Implement a configuration management plan for the system that protects the configuration management plan from unauthorized disclosure and modification.','CM-09e.','N/A','Determine if: - the configuration management plan is protected from unauthorized disclosure. - the configuration management plan is protected from unauthorized modification.'),
('001802','draft','2013-03-01','DISA FSO','policy','Track the use of software documentation protected by quantity licenses to control copying of the software documentation.','CM-10b.','N/A','Determine if the use of software and associated documentation protected by quantity licenses is tracked to control copying and distribution.'),
('001803','draft','2013-03-01','DISA FSO','policy','Track the use of software protected by quantity licenses to control distribution of the software.','CM-10b.','N/A','Determine if the use of software and associated documentation protected by quantity licenses is tracked to control copying and distribution.'),
('001804','draft','2013-03-01','DISA FSO','policy','Defines the policies for governing the installation of software by users.','CM-11a.','N/A','Determine if [CM-11_ODP[01]; policies governing the installation of software by users are defined] governing the installation of software by users are established.'),
('001805','draft','2013-03-01','DISA FSO','policy','Establish organization-defined policies governing the installation of software by users.','CM-11a.','N/A','Determine if [CM-11_ODP[01]; policies governing the installation of software by users are defined] governing the installation of software by users are established.'),
('001806','draft','2013-03-01','DISA FSO','policy','Defines methods to be employed to enforce the software installation policies.','CM-11b.','N/A','Determine if software installation policies are enforced through [CM-11_ODP[02]; methods used to enforce software installation policies are defined].'),
('001807','draft','2013-03-01','DISA FSO','policy','Enforce software installation policies through organization-defined methods.','CM-11b.','N/A','Determine if software installation policies are enforced through [CM-11_ODP[02]; methods used to enforce software installation policies are defined].'),
('001808','draft','2013-03-01','DISA FSO','policy','Defines the frequency on which it will monitor software installation policy compliance.','CM-11c.','N/A','Determine if compliance with [CM-11_ODP[01]; policies governing the installation of software by users are defined] is monitored [CM-11_ODP[03]; frequency with which to monitor compliance is defined].'),
('001809','draft','2013-03-01','DISA FSO','policy','Monitor software installation policy compliance per an organization-defined frequency.','CM-11c.','N/A','Determine if compliance with [CM-11_ODP[01]; policies governing the installation of software by users are defined] is monitored [CM-11_ODP[03]; frequency with which to monitor compliance is defined].'),
('001813','draft','2013-03-01','DISA FSO','technical','Enforce access restrictions using organization-defined mechanisms.','CM-05(01)(a)','N/A','Determine if access restrictions for change are enforced using [CM-05(01)_ODP; mechanisms used to automate the enforcement of access restrictions are defined].'),
('001815','draft','2013-03-01','DISA FSO','policy','Defines the controls to be applied to devices when individuals return from areas of significant risk.','CM-02(07)(b)','N/A','Determine if [CM-02(07)_ODP[03]; the controls to be applied when the individuals return from travel are defined] are applied to the systems or system components when the individuals return from travel.'),
('001816','draft','2013-03-01','DISA FSO','policy','Apply organization-defined controls to the systems or components when the individuals return from travel.','CM-02(07)(b)','N/A','Determine if [CM-02(07)_ODP[03]; the controls to be applied when the individuals return from travel are defined] are applied to the systems or system components when the individuals return from travel.'),
('001817','draft','2013-03-01','DISA FSO','policy','When analyzing changes to the system, looks for privacy impacts due to flaws, weaknesses, incompatibility, or intentional malice.','CM-04(01)','N/A','Determine if: - changes to the system are analyzed in a separate test environment before implementation in an operational environment. - changes to the system are analyzed for security impacts due to flaws. - changes to the system are analyzed for privacy impacts due to flaws. - changes to the system are analyzed for security impacts due to weaknesses. - changes to the system are analyzed for privacy impacts due to weaknesses. - changes to the system are analyzed for privacy impacts due to incompatibility. - changes to the system are analyzed for privacy impacts due to incompatibility. - changes to the system are analyzed for security impacts due to intentional malice. - changes to the system are analyzed for privacy impacts due to intentional malice.'),
('001818','draft','2013-03-01','DISA FSO','policy','Analyze changes to the system in a separate test environment before installation in an operational environment.','CM-04(01)','N/A','Determine if: - changes to the system are analyzed in a separate test environment before implementation in an operational environment. - changes to the system are analyzed for security impacts due to flaws. - changes to the system are analyzed for privacy impacts due to flaws. - changes to the system are analyzed for security impacts due to weaknesses. - changes to the system are analyzed for privacy impacts due to weaknesses. - changes to the system are analyzed for privacy impacts due to incompatibility. - changes to the system are analyzed for privacy impacts due to incompatibility. - changes to the system are analyzed for security impacts due to intentional malice. - changes to the system are analyzed for privacy impacts due to intentional malice.'),
('001819','draft','2013-03-01','DISA FSO','policy','Implement approved configuration-controlled changes to the system.','CM-03d.','N/A','Determine if approved configuration-controlled changes to the system are implemented.'),
('001821','draft','2013-03-01','DISA FSO','policy','Defines the organizational personnel or roles to whom the organization-level; mission/business process-level; and/or system-level configuration management policy is to be disseminated.','CM-01a.','N/A','Determine if: - a configuration management policy is developed and documented. - the configuration management policy is disseminated to [CM-01_ODP[01]; personnel or roles to whom the configuration management policy is to be disseminated is/are defined].'),
('001822','draft','2013-03-01','DISA FSO','policy','Disseminate the organization-level; mission/business process-level; and/or system-level configuration management policy to organization-defined personnel or roles.','CM-01a.','N/A','Determine if: - a configuration management policy is developed and documented. - the configuration management policy is disseminated to [CM-01_ODP[01]; personnel or roles to whom the configuration management policy is to be disseminated is/are defined].'),
('001824','draft','2013-03-01','DISA FSO','policy','Defines the organizational personnel or roles to whom the organization-level; mission/business process-level; and/or system-level configuration management procedures are to be disseminated.','CM-01a.02','N/A','Determine if: - configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented. - the configuration management procedures are disseminated to [CM-01_ODP[02]; personnel or roles to whom the configuration management procedures are to be disseminated is/are defined].'),
('001825','draft','2013-03-01','DISA FSO','policy','Disseminate to organization-defined personnel or roles the procedures to facilitate the implementation of the organization-level; mission/business process-level; and/or system-level configuration management policy and associated configuration management controls.','CM-01a.02','N/A','Determine if: - configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented. - the configuration management procedures are disseminated to [CM-01_ODP[02]; personnel or roles to whom the configuration management procedures are to be disseminated is/are defined].'),
('001832','draft','2013-03-14','DISA FSO','policy','Disseminate the organization-level; mission/business process-level; and/or system-level audit and accountability policy to organization-defined personnel or roles.','AU-01a.','N/A','Determine if: - an audit and accountability policy is developed and documented. - the audit and accountability policy is disseminated to [AU-01_ODP[01]; personnel or roles to whom the audit and accountability policy is to be disseminated is/are defined].'),
('001834','draft','2013-03-14','DISA FSO','policy','Disseminate to organization-defined personnel or roles procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.','AU-01a.02','N/A','Determine if: - audit and accountability procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls are developed and documented. - the audit and accountability procedures are disseminated to [AU-01_ODP[02]; personnel or roles to whom the audit and accountability procedures are to be disseminated is/are defined].'),
('001848','draft','2013-03-14','DISA FSO','policy','Defines the audit log retention requirements for allocating audit log storage capacity.','AU-04','N/A','Determine if audit log storage capacity is allocated to accommodate [AU-04_ODP; audit log retention requirements are defined].'),
('001849','draft','2013-03-14','DISA FSO','technical','Allocate audit log storage capacity to accommodate organization-defined audit log retention requirements.','AU-04','N/A','Determine if audit log storage capacity is allocated to accommodate [AU-04_ODP; audit log retention requirements are defined].'),
('001850','draft','2013-03-14','DISA FSO','policy','Defines the frequency to off-load audit records onto a different system or media than the system being audited.','AU-04(01)','N/A','Determine if audit logs are transferred [AU-04(01)_ODP; the frequency of audit logs transferred to a different system, system component, or media other than the system or system component conducting the logging is defined] to a different system, system component, or media other than the system or system component conducting the logging.'),
('001851','draft','2013-03-14','DISA FSO','technical','Transfer audit logs per organization-defined frequency to a different system, system component, or media than the system or system component conducting the logging.','AU-04(01)','N/A','Determine if audit logs are transferred [AU-04(01)_ODP; the frequency of audit logs transferred to a different system, system component, or media other than the system or system component conducting the logging is defined] to a different system, system component, or media other than the system or system component conducting the logging.'),
('001852','draft','2013-03-14','DISA FSO','policy','Defines the personnel, roles and/or locations to receive a warning when allocated audit log storage volume reaches a defined percentage of maximum audit log storage capacity.','AU-05(01)','N/A','Determine if a warning is provided to [AU-05(01)_ODP[01]; personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity] within [AU-05(01)_ODP[02]; time period for defined personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity is defined] when allocated audit log storage volume reaches [AU-05(01)_ODP[03]; percentage of repository maximum audit log storage capacity is defined] of repository maximum audit log storage capacity.'),
('001853','draft','2013-03-14','DISA FSO','policy','Defines the time period within which organization-defined personnel, roles, and/or locations are to receive warnings when allocated audit log storage volume reaches an organization-defined percentage of maximum audit log storage capacity.','AU-05(01)','N/A','Determine if a warning is provided to [AU-05(01)_ODP[01]; personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity] within [AU-05(01)_ODP[02]; time period for defined personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity is defined] when allocated audit log storage volume reaches [AU-05(01)_ODP[03]; percentage of repository maximum audit log storage capacity is defined] of repository maximum audit log storage capacity.'),
('001854','draft','2013-03-14','DISA FSO','policy','Defines the percentage of maximum audit log storage capacity that is to be reached, at which time the system will provide a warning to organization-defined personnel, roles, and/or locations.','AU-05(01)','N/A','Determine if a warning is provided to [AU-05(01)_ODP[01]; personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity] within [AU-05(01)_ODP[02]; time period for defined personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity is defined] when allocated audit log storage volume reaches [AU-05(01)_ODP[03]; percentage of repository maximum audit log storage capacity is defined] of repository maximum audit log storage capacity.'),
('001855','draft','2013-03-14','DISA FSO','technical','Provide a warning to organization-defined personnel, roles, and/or locations within an organization-defined time period when allocated audit log storage volume reaches an organization-defined percentage of repository maximum audit log storage capacity.','AU-05(01)','N/A','Determine if a warning is provided to [AU-05(01)_ODP[01]; personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity] within [AU-05(01)_ODP[02]; time period for defined personnel, roles, and/or locations to be warned when allocated audit log storage volume reaches a percentage of repository maximum audit log storage capacity is defined] when allocated audit log storage volume reaches [AU-05(01)_ODP[03]; percentage of repository maximum audit log storage capacity is defined] of repository maximum audit log storage capacity.'),
('001856','draft','2013-03-14','DISA FSO','policy','Defines the real-time period in which to provide an alert when organization-defined audit failure events occur.','AU-05(02)','N/A','Determine if an alert is provided within [AU-05(02)_ODP[01]; real-time period requiring alerts when audit failure events (defined in AU-05(02)_ODP[03]) occur is defined] to [AU-05(02)_ODP[02]; personnel, roles, and/or locations to be alerted in real time when audit failure events (defined in AU-05(02)_ODP[03]) occur is/are defined] when [AU-05(02)_ODP[03]; audit logging failure events requiring real-time alerts are defined] occur.'),
('001857','draft','2013-03-14','DISA FSO','policy','Defines the personnel, roles, and/or locations to receive alerts when organization-defined audit failure events occur.','AU-05(02)','N/A','Determine if an alert is provided within [AU-05(02)_ODP[01]; real-time period requiring alerts when audit failure events (defined in AU-05(02)_ODP[03]) occur is defined] to [AU-05(02)_ODP[02]; personnel, roles, and/or locations to be alerted in real time when audit failure events (defined in AU-05(02)_ODP[03]) occur is/are defined] when [AU-05(02)_ODP[03]; audit logging failure events requiring real-time alerts are defined] occur.'),
('001858','draft','2013-03-14','DISA FSO','technical','Provide an alert in an organization-defined real-time-period to organization-defined personnel, roles, and/or locations when organization-defined audit failure events requiring real-time alerts occur.','AU-05(02)','N/A','Determine if an alert is provided within [AU-05(02)_ODP[01]; real-time period requiring alerts when audit failure events (defined in AU-05(02)_ODP[03]) occur is defined] to [AU-05(02)_ODP[02]; personnel, roles, and/or locations to be alerted in real time when audit failure events (defined in AU-05(02)_ODP[03]) occur is/are defined] when [AU-05(02)_ODP[03]; audit logging failure events requiring real-time alerts are defined] occur.'),
('001859','draft','2013-03-14','DISA FSO','policy','Defines the network communication traffic volume thresholds reflecting limits on auditing capacity, specifying when the information system will reject or delay network traffic that exceed those thresholds.','AU-05(03)','N/A','Determine if: - configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity are enforced. - network traffic is [AU-05(03)_ODP; one or more of the following PARAMETER VALUES is/are selected: {reject; delay}] if network traffic volume is above configured thresholds.'),
('001860','draft','2013-03-14','DISA FSO','policy','Defines the audit logging failures which, should they occur, will invoke an organization-defined system mode.','AU-05(04)','N/A','Determine if [AU-05(04)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available}] is/are invoked in the event of [AU-05(04)_ODP[02]; audit logging failures that trigger a change in operational mode are defined], unless an alternate audit logging capability exists.'),
('001861','draft','2013-03-14','DISA FSO','technical','Invoke a full system shutdown, partial system shutdown, or degraded operational mode with limited mission or business functionality available in the event of organization-defined audit logging failures, unless an alternate audit logging capability exists.','AU-05(04)','N/A','Determine if [AU-05(04)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available}] is/are invoked in the event of [AU-05(04)_ODP[02]; audit logging failures that trigger a change in operational mode are defined], unless an alternate audit logging capability exists.'),
('001862','draft','2013-03-15','DISA FSO','policy','Defines the types of inappropriate or unusual activity to be reviewed and analyzed in the audit records.','AU-06a.','N/A','Determine if system audit records are reviewed and analyzed [AU-06_ODP[01]; frequency at which system audit records are reviewed and analyzed is defined] for indications of [AU-06_ODP[02]; inappropriate or unusual activity is defined] and the potential impact of the inappropriate or unusual activity.'),
('001863','draft','2013-03-15','DISA FSO','policy','Defines the personnel or roles to receive the reports of organization-defined inappropriate or unusual activity.','AU-06b.','N/A','Determine if findings are reported to [AU-06_ODP[03]; personnel or roles to receive findings from reviews and analyses of system records is/are defined].'),
('001864','draft','2013-03-15','DISA FSO','policy','Integrate audit review and analysis using organization-defined automated mechanisms.','AU-06(01)','N/A','Determine if audit record review, analysis, and reporting processes are integrated using [AU-06(01)_ODP; automated mechanisms used for integrating audit record review, analysis, and reporting processes are defined].'),
('001865','draft','2013-03-15','DISA FSO','policy','Integrate reporting processes using organization-defined automated mechanisms.','AU-06(01)','N/A','Determine if audit record review, analysis, and reporting processes are integrated using [AU-06(01)_ODP; automated mechanisms used for integrating audit record review, analysis, and reporting processes are defined].'),
('001866','draft','2013-03-15','DISA FSO','policy','Defines the data/information to be collected from other sources to enhance its ability to identify inappropriate or unusual activity.','AU-06(05)','N/A','Determine if analysis of audit records is integrated with analysis of [AU-06(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {vulnerability scanning information; performance data; system monitoring information; [AU-06(05)_ODP[02]; data/information collected from other sources to be analyzed is defined (if selected)}]] to further enhance the ability to identify inappropriate or unusual activity.'),
('001867','draft','2013-03-15','DISA FSO','policy','Integrate analysis of audit records with analysis of vulnerability scanning information, performance data, system monitoring information, and/or organization-defined data/information collected from other sources to further enhance the ability to identify inappropriate or unusual activity.','AU-06(05)','N/A','Determine if analysis of audit records is integrated with analysis of [AU-06(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {vulnerability scanning information; performance data; system monitoring information; [AU-06(05)_ODP[02]; data/information collected from other sources to be analyzed is defined (if selected)}]] to further enhance the ability to identify inappropriate or unusual activity.'),
('001868','draft','2013-03-15','DISA FSO','policy','Specify the permitted actions for each information system process, role, and/or user associated with the review and analysis of audit information.','AU-06(07)','N/A','Determine if the permitted actions for each [AU-06(07)_ODP; one or more of the following PARAMETER VALUES is/are selected: {system process; role; user}] associated with the review, analysis, and reporting of audit record information are specified.'),
('001869','draft','2013-03-15','DISA FSO','policy','Specify the permitted actions for each information system process, role, and/or user associated with the reporting of audit information.','AU-06(07)','N/A','Determine if the permitted actions for each [AU-06(07)_ODP; one or more of the following PARAMETER VALUES is/are selected: {system process; role; user}] associated with the review, analysis, and reporting of audit record information are specified.'),
('001870','draft','2013-03-15','DISA FSO','policy','Perform a full-text analysis of logged privileged commands in a physically-distinct component or subsystem of the system, or other system that is dedicated to that analysis.','AU-06(08)','N/A','Determine if a full text analysis of logged privileged commands in a physically distinct component or subsystem of the system or other system that is dedicated to that analysis is performed.'),
('001871','draft','2013-03-15','DISA FSO','policy','Correlate information from non-technical sources with audit record information to enhance organization-wide situational awareness.','AU-06(09)','N/A','Determine if information from non-technical sources is correlated with audit record information to enhance organization-wide situational awareness.'),
('001875','draft','2013-03-15','DISA FSO','technical','Provide an audit reduction capability that supports on-demand audit review and analysis.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('001876','draft','2013-03-15','DISA FSO','technical','Provide an audit reduction capability that supports on-demand reporting requirements.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('001877','draft','2013-03-15','DISA FSO','technical','Provide an audit reduction capability that supports after-the-fact investigations of incidents.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('001878','draft','2013-03-15','DISA FSO','technical','Provide a report generation capability that supports on-demand audit review and analysis.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('001879','draft','2013-03-15','DISA FSO','policy','Provide a report generation capability that supports on-demand reporting requirements.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('001880','draft','2013-03-15','DISA FSO','technical','Provide a report generation capability that supports after-the-fact investigations of security incidents.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('001881','draft','2013-03-15','DISA FSO','technical','Provide an audit reduction capability that does not alter original content or time ordering of audit records.','AU-07b.','N/A','Determine if: - an audit record reduction and report generation capability is provided that does not alter the original content or time ordering of audit records. - an audit record reduction and report generation capability is implemented that does not alter the original content or time ordering of audit records.'),
('001882','draft','2013-03-15','DISA FSO','technical','Provide a report generation capability that does not alter original content or time ordering of audit records.','AU-07b.','N/A','Determine if: - an audit record reduction and report generation capability is provided that does not alter the original content or time ordering of audit records. - an audit record reduction and report generation capability is implemented that does not alter the original content or time ordering of audit records.'),
('001883','draft','2013-03-15','DISA FSO','policy','Defines the audit fields within audit records to be processed, sorted, and searched for events of interest by the system.','AU-07(01)','N/A','Determine if: - the capability to process, sort, and search audit records for events of interest based on [AU-07(01)_ODP; fields within audit records that can be processed, sorted, or searched are defined] are provided. - the capability to process, sort, and search audit records for events of interest based on [AU-07(01)_ODP; fields within audit records that can be processed, sorted, or searched are defined] are implemented.'),
('001888','draft','2013-03-15','DISA FSO','policy','Defines the granularity of time measurement for time stamps generated for audit records.','AU-08b.','N/A','Determine if timestamps are recorded for audit records that meet [AU-08_ODP; granularity of time measurement for audit record timestamps is defined] and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or include the local time offset as part of the timestamp.'),
('001889','draft','2013-03-15','DISA FSO','technical','Record time stamps for audit records that meet organization-defined granularity of time measurement.','AU-08b.','N/A','Determine if timestamps are recorded for audit records that meet [AU-08_ODP; granularity of time measurement for audit record timestamps is defined] and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or include the local time offset as part of the timestamp.'),
('001890','draft','2013-03-15','DISA FSO','technical','Record time stamps for audit records that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or that include the local time offset as part of the time stamp.','AU-08b.','N/A','Determine if timestamps are recorded for audit records that meet [AU-08_ODP; granularity of time measurement for audit record timestamps is defined] and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or include the local time offset as part of the timestamp.'),
('001894','draft','2013-03-15','DISA FSO','policy','Defines the subset of privileged users who will be authorized access to the management of audit functionality.','AU-09(04)','N/A','Determine if access to management of audit logging functionality is authorized only to [AU-09(04)_ODP; a subset of privileged users or roles authorized to access management of audit logging functionality is defined].'),
('001895','draft','2013-03-15','DISA FSO','policy','Defines the audit information requiring dual authorization for movement or deletion actions.','AU-09(05)','N/A','Determine if dual authorization is enforced for the [AU-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {movement; deletion}] of [AU-09(05)_ODP[02]; audit information for which dual authorization is to be enforced is defined].'),
('001896','draft','2013-03-15','DISA FSO','technical','Enforce dual authorization for movement and/or deletion of organization-defined audit information.','AU-09(05)','N/A','Determine if dual authorization is enforced for the [AU-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {movement; deletion}] of [AU-09(05)_ODP[02]; audit information for which dual authorization is to be enforced is defined].'),
('001897','draft','2013-03-15','DISA FSO','policy','Defines the subset of privileged users or roles who will be authorized read-only access to audit information.','AU-09(06)','N/A','Determine if read-only access to audit information is authorized to [AU-09(06)_ODP; a subset of privileged users or roles with authorized read-only access to audit information is defined].'),
('001898','draft','2013-03-15','DISA FSO','policy','Authorize read-only access to audit information to an organization-defined subset of privileged users or roles.','AU-09(06)','N/A','Determine if read-only access to audit information is authorized to [AU-09(06)_ODP; a subset of privileged users or roles with authorized read-only access to audit information is defined].'),
('001899','draft','2013-03-15','DISA FSO','policy','Defines the actions to be covered by non-repudiation.','AU-10','N/A','Determine if irrefutable evidence is provided that an individual (or process acting on behalf of an individual) has performed [AU-10_ODP; actions to be covered by non-repudiation are defined].'),
('001900','draft','2013-03-15','DISA FSO','policy','Defines the strength of binding to be applied to the binding of the identity of the information producer with the information.','AU-10(01)(a)','N/A','Determine if the identity of the information producer is bound with the information to [AU-10(01)_ODP; the strength of binding between the identity of the information producer and the information is defined].'),
('001901','draft','2013-03-15','DISA FSO','technical','Bind the identity of the information producer with the information to an organization-defined strength of binding.','AU-10(01)(a)','N/A','Determine if the identity of the information producer is bound with the information to [AU-10(01)_ODP; the strength of binding between the identity of the information producer and the information is defined].'),
('001902','draft','2013-03-15','DISA FSO','technical','Provide the means for authorized individuals to determine the identity of the producer of the information.','AU-10(01)(b)','N/A','Determine if the means for authorized individuals to determine the identity of the producer of the information is provided.'),
('001903','draft','2013-03-15','DISA FSO','policy','Defines the frequency on which the system is to validate the binding of the information producer identity to the information.','AU-10(02)(a)','N/A','Determine if the binding of the information producer identity to the information is validated at [AU-10(02)_ODP[01]; the frequency at which to validate the binding of the information producer identity to the information is defined].'),
('001904','draft','2013-03-15','DISA FSO','technical','Validate the binding of the information producer identity to the information at an organization-defined frequency.','AU-10(02)(a)','N/A','Determine if the binding of the information producer identity to the information is validated at [AU-10(02)_ODP[01]; the frequency at which to validate the binding of the information producer identity to the information is defined].'),
('001905','draft','2013-03-15','DISA FSO','policy','Defines the actions to be performed in the event of an error when validating the binding of the information producer identity to the information.','AU-10(02)(b)','N/A','Determine if [AU-10(02)_ODP[02]; the actions to be performed in the event of a validation error are defined] in the event of a validation error are performed.'),
('001906','draft','2013-03-15','DISA FSO','technical','Perform organization-defined actions in the event of an error when validating the binding of the information producer identity to the information.','AU-10(02)(b)','N/A','Determine if [AU-10(02)_ODP[02]; the actions to be performed in the event of a validation error are defined] in the event of a validation error are performed.'),
('001907','draft','2013-03-15','DISA FSO','policy','Defines the security domains which will require the system validate the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer.','AU-10(04)(a)','N/A','Determine if the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between [AU-10(04)_ODP[01]; security domains for which the binding of the information reviewer identity to the information is to be validated at transfer or release are defined].'),
('001908','draft','2013-03-15','DISA FSO','policy','Defines the action the system is to perform in the event of an information reviewer identity binding validation error.',NULL,'N/A',NULL),
('001909','draft','2013-03-15','DISA FSO','technical','Perform organization-defined actions in the event of an information reviewer identity binding validation error.','AU-10(04)(b)','N/A','Determine if [AU-10(04)_ODP[02]; actions to be performed in the event of a validation error are defined] are performed in the event of a validation error.'),
('001910','draft','2013-03-15','DISA FSO','policy','Defines the personnel or roles allowed to select which event types are to be logged by specific components of the system.','AU-12b.','N/A','Determine if [AU-12_ODP[02]; personnel or roles allowed to select the event types that are to be logged by specific components of the system is/are defined] is/are allowed to select the event types that are to be logged by specific components of the system.'),
('001911','draft','2013-03-15','DISA FSO','policy','Defines the selectable event criteria to be used as the basis for changes to the auditing to be performed on organization-defined system components, by organization-defined individuals or roles, within organization-defined time thresholds.','AU-12(03)','N/A','Determine if: - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is provided. - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is implemented.'),
('001912','draft','2013-03-15','DISA FSO','policy','Defines the time thresholds for organization-defined individuals or roles to change the auditing to be performed based on organization-defined selectable event criteria.','AU-12(03)','N/A','Determine if: - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is provided. - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is implemented.'),
('001913','draft','2013-03-15','DISA FSO','policy','Defines the individuals or roles that are to be provided the capability to change the auditing to be performed based on organization-defined selectable event criteria, within organization-defined time thresholds.','AU-12(03)','N/A','Determine if: - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is provided. - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is implemented.'),
('001914','draft','2013-03-15','DISA FSO','technical','Provide the capability for organization-defined individuals or roles to change the logging to be performed on organization-defined system components based on organization-defined selectable event criteria within organization-defined time thresholds.','AU-12(03)','N/A','Determine if: - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is provided. - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is implemented.'),
('001915','draft','2013-03-15','DISA FSO','policy','Defines the open source information and/or information sites to be monitored for evidence of unauthorized exfiltration or disclosure of organizational information.',NULL,'N/A',NULL),
('001917','draft','2013-03-15','DISA FSO','policy','Defines the frequency for reviewing the open source information sites being monitored.','AU-13(02)','N/A','Determine if the list of open-source information sites being monitored is reviewed [AU-13(02)_ODP; the frequency at which to review the open-source information sites being monitored is defined].'),
('001918','draft','2013-03-15','DISA FSO','policy','Review the open source information sites being monitored per organization-defined frequency.','AU-13(02)','N/A','Determine if the list of open-source information sites being monitored is reviewed [AU-13(02)_ODP; the frequency at which to review the open-source information sites being monitored is defined].'),
('001919','draft','2013-03-15','DISA FSO','technical','Provide the capability for organization-defined users or roles to select a user session to record; view; hear; or log the content of a user session under organization-defined circumstances.','AU-14a.','N/A','Determine if: - [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] are provided with the capability to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined]. - the capability for [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined] is implemented.'),
('001920','draft','2013-03-15','DISA FSO','technical','Provide the capability for authorized users to remotely view and hear content related to an established user session in real time.','AU-14(03)','N/A','Determine if: - the capability for authorized users to remotely view and hear content related to an established user session in real time is provided. - the capability for authorized users to remotely view and hear content related to an established user session in real time is implemented.'),
('001923','draft','2013-03-15','DISA FSO','policy','Defines the audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries.','AU-16','N/A','Determine if [AU-16_ODP[01]; methods for coordinating audit information among external organizations when audit information is transmitted across organizational boundaries are defined] for coordinating [AU-16_ODP[02]; audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries is defined] among external organizations when audit information is transmitted across organizational boundaries are employed.'),
('001924','draft','2013-03-15','DISA FSO','policy','Defines the methods to be employed when coordinating audit information among external organizations when audit information is transmitted across organizational boundaries.','AU-16','N/A','Determine if [AU-16_ODP[01]; methods for coordinating audit information among external organizations when audit information is transmitted across organizational boundaries are defined] for coordinating [AU-16_ODP[02]; audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries is defined] among external organizations when audit information is transmitted across organizational boundaries are employed.'),
('001925','draft','2013-03-15','DISA FSO','policy','Employ organization-defined methods for coordinating organization-defined audit information among external organizations when audit information is transmitted across organizational boundaries.','AU-16','N/A','Determine if [AU-16_ODP[01]; methods for coordinating audit information among external organizations when audit information is transmitted across organizational boundaries are defined] for coordinating [AU-16_ODP[02]; audit information to be coordinated among external organizations when audit information is transmitted across organizational boundaries is defined] among external organizations when audit information is transmitted across organizational boundaries are employed.'),
('001926','draft','2013-03-15','DISA FSO','policy','Preserve the identity of individuals in cross-organizational audit trails.','AU-16(01)','N/A','Determine if the identity of individuals in cross-organizational audit trails is preserved.'),
('001927','draft','2013-03-15','DISA FSO','policy','Defines the organizations that will be provided cross-organizational audit information.','AU-16(02)','N/A','Determine if cross-organizational audit information is provided to [AU-16(02)_ODP[01]; organizations with which cross-organizational audit information is to be shared are defined] based on [AU-16(02)_ODP[02]; cross-organizational sharing agreements to be used when providing cross-organizational audit information to organizations are defined].'),
('001928','draft','2013-03-15','DISA FSO','policy','Defines the cross-organizational sharing agreements to be established with organization-defined organizations authorized to be provided cross-organizational sharing of audit information.','AU-16(02)','N/A','Determine if cross-organizational audit information is provided to [AU-16(02)_ODP[01]; organizations with which cross-organizational audit information is to be shared are defined] based on [AU-16(02)_ODP[02]; cross-organizational sharing agreements to be used when providing cross-organizational audit information to organizations are defined].'),
('001929','draft','2013-03-15','DISA FSO','policy','Provide cross-organizational audit information to organization-defined organizations based on organization-defined cross organizational sharing agreements.','AU-16(02)','N/A','Determine if cross-organizational audit information is provided to [AU-16(02)_ODP[01]; organizations with which cross-organizational audit information is to be shared are defined] based on [AU-16(02)_ODP[02]; cross-organizational sharing agreements to be used when providing cross-organizational audit information to organizations are defined].'),
('001930','draft','2013-04-08','DISA FSO','policy','Defines the personnel or roles to whom the organization-level; mission/business process-level; and/or system-level audit and accountability policy is to be disseminated.','AU-01a.','N/A','Determine if: - an audit and accountability policy is developed and documented. - the audit and accountability policy is disseminated to [AU-01_ODP[01]; personnel or roles to whom the audit and accountability policy is to be disseminated is/are defined].'),
('001931','draft','2013-04-08','DISA FSO','policy','Defines the personnel or roles to whom the audit and accountability procedures are to be disseminated.','AU-01a.02','N/A','Determine if: - audit and accountability procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls are developed and documented. - the audit and accountability procedures are disseminated to [AU-01_ODP[02]; personnel or roles to whom the audit and accountability procedures are to be disseminated is/are defined].'),
('001941','draft','2013-05-03','DISA FSO','technical','Implement replay-resistant authentication mechanisms for access to privileged accounts and/or non-privileged accounts.','IA-02(08)','N/A','Determine if replay-resistant authentication mechanisms for access to [IA-02(08)_ODP; one or more of the following PARAMETER VALUES is/are selected: {privileged accounts; non-privileged accounts}] are implemented.'),
('001943','draft','2013-05-03','DISA FSO','policy','Defines the system accounts for which single sign-on capability will be provided.','IA-02(10)','N/A','Determine if a single sign-on capability is provided for [IA-02(10)_ODP; system accounts and services for which a single sign-on capability must be provided are defined].'),
('001944','draft','2013-05-03','DISA FSO','policy','Defines the system services for which single sign-on capability will be provided.','IA-02(10)','N/A','Determine if a single sign-on capability is provided for [IA-02(10)_ODP; system accounts and services for which a single sign-on capability must be provided are defined].'),
('001945','draft','2013-05-03','DISA FSO','technical','Provide a single sign-on capability for organization-defined system accounts.','IA-02(10)','N/A','Determine if a single sign-on capability is provided for [IA-02(10)_ODP; system accounts and services for which a single sign-on capability must be provided are defined].'),
('001946','draft','2013-05-03','DISA FSO','technical','Provide a single sign-on capability for organization-defined system services.','IA-02(10)','N/A','Determine if a single sign-on capability is provided for [IA-02(10)_ODP; system accounts and services for which a single sign-on capability must be provided are defined].'),
('001953','draft','2013-05-03','DISA FSO','technical','Accept Personal Identity Verification-compliant credentials.','IA-02(12)','N/A','Determine if Personal Identity Verification-compliant credentials are accepted and electronically verified.'),
('001954','draft','2013-05-03','DISA FSO','technical','Electronically verify Personal Identity Verification-compliant credentials.','IA-02(12)','N/A','Determine if Personal Identity Verification-compliant credentials are accepted and electronically verified.'),
('001955','draft','2013-05-03','DISA FSO','policy','Defines the out-of-band authentication to be implemented under organization-defined conditions.','IA-02(13)','N/A','Determine if [IA-02(13)_ODP[01]; out-of-band authentication mechanisms to be implemented are defined] mechanisms are implemented under [IA-02(13)_ODP[02]; conditions under which out-of-band authentication is to be implemented are defined].'),
('001956','draft','2013-05-03','DISA FSO','policy','Defines the conditions for implementing organization-defined out-of-band authentication.','IA-02(13)','N/A','Determine if [IA-02(13)_ODP[01]; out-of-band authentication mechanisms to be implemented are defined] mechanisms are implemented under [IA-02(13)_ODP[02]; conditions under which out-of-band authentication is to be implemented are defined].'),
('001957','draft','2013-05-03','DISA FSO','technical','Implement organization-defined out-of-band authentication mechanisms under organization-defined conditions.','IA-02(13)','N/A','Determine if [IA-02(13)_ODP[01]; out-of-band authentication mechanisms to be implemented are defined] mechanisms are implemented under [IA-02(13)_ODP[02]; conditions under which out-of-band authentication is to be implemented are defined].'),
('001958','draft','2013-05-03','DISA FSO','technical','Authenticate organization-defined devices and/or types of devices before establishing a local, remote, and/or network connection.','IA-03','N/A','Determine if [IA-03_ODP[01]; devices and/or types of devices to be uniquely identified and authenticated before establishing a connection are defined] are uniquely identified and authenticated before establishing a [IA-03_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {local; remote; network}] connection.'),
('001959','draft','2013-05-03','DISA FSO','policy','Defines the devices and/or types of devices the system is to authenticate before establishing a connection.','IA-03(01)','N/A','Determine if [IA-03(01)_ODP[01]; devices and/or types of devices requiring use of cryptographically based, bidirectional authentication to authenticate before establishing one or more connections are defined] are authenticated before establishing [IA-03(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {local; remote; network}] connection using bidirectional authentication that is cryptographically based.'),
('001960','draft','2013-05-03','DISA FSO','policy','Defines the lease information to be assigned to devices.','IA-03(03)(a)','N/A','Determine if: - dynamic address allocation lease information assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[01]; lease information to be employed to standardize dynamic address allocation for devices is defined]. - dynamic address allocation lease duration assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[02]; lease duration to be employed to standardize dynamic address allocation for devices is defined].'),
('001961','draft','2013-05-03','DISA FSO','policy','Defines the lease duration to be assigned to devices.','IA-03(03)(a)','N/A','Determine if: - dynamic address allocation lease information assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[01]; lease information to be employed to standardize dynamic address allocation for devices is defined]. - dynamic address allocation lease duration assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[02]; lease duration to be employed to standardize dynamic address allocation for devices is defined].'),
('001962','draft','2013-05-03','DISA FSO','technical','Where addresses are allocated dynamically, standardize dynamic address allocation lease information assigned to devices in accordance with organization-defined lease information.','IA-03(03)(a)','N/A','Determine if: - dynamic address allocation lease information assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[01]; lease information to be employed to standardize dynamic address allocation for devices is defined]. - dynamic address allocation lease duration assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[02]; lease duration to be employed to standardize dynamic address allocation for devices is defined].'),
('001963','draft','2013-05-03','DISA FSO','technical','Where addresses are allocated dynamically, standardize dynamic address allocation lease duration assigned to devices in accordance with organization-defined lease duration.','IA-03(03)(a)','N/A','Determine if: - dynamic address allocation lease information assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[01]; lease information to be employed to standardize dynamic address allocation for devices is defined]. - dynamic address allocation lease duration assigned to devices where addresses are allocated dynamically are standardized in accordance with [IA-03(03)_ODP[02]; lease duration to be employed to standardize dynamic address allocation for devices is defined].'),
('001965','draft','2013-05-03','DISA FSO','policy','Defines the configuration management process that is to handle the device authentication procedures.','IA-03(04)','N/A','Determine if device identification and authentication are handled based on attestation by [IA-03(04)_ODP; configuration management process to be employed to handle device identification and authentication based on attestation is defined].'),
('001966','draft','2013-05-03','DISA FSO','policy','Handle device identification based on attestation is handled by the organization-defined configuration management process.','IA-03(04)','N/A','Determine if device identification and authentication are handled based on attestation by [IA-03(04)_ODP; configuration management process to be employed to handle device identification and authentication based on attestation is defined].'),
('001967','draft','2013-05-03','DISA FSO','technical','Authenticate organization-defined devices and/or types of devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.','IA-03(01)','N/A','Determine if [IA-03(01)_ODP[01]; devices and/or types of devices requiring use of cryptographically based, bidirectional authentication to authenticate before establishing one or more connections are defined] are authenticated before establishing [IA-03(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {local; remote; network}] connection using bidirectional authentication that is cryptographically based.'),
('001968','draft','2013-05-03','DISA FSO','policy','Defines the configuration management process that is to handle the device identification procedures.','IA-03(04)','N/A','Determine if device identification and authentication are handled based on attestation by [IA-03(04)_ODP; configuration management process to be employed to handle device identification and authentication based on attestation is defined].'),
('001969','draft','2013-05-03','DISA FSO','policy','Handle device authentication based on attestation is handled by the organization-defined configuration management process.','IA-03(04)','N/A','Determine if device identification and authentication are handled based on attestation by [IA-03(04)_ODP; configuration management process to be employed to handle device identification and authentication based on attestation is defined].'),
('001970','draft','2013-05-03','DISA FSO','policy','Defines the personnel or roles that authorize the assignment of individual, group, role, and device identifiers.','IA-04a.','N/A','Determine if system identifiers are managed by receiving authorization from [IA-04_ODP[01]; personnel or roles from whom authorization must be received to assign an identifier are defined] to assign to an individual, group, role, or device identifier.'),
('001971','draft','2013-05-03','DISA FSO','policy','Manage system identifiers by receiving authorization from organization-defined personnel or roles to assign an individual, group, role, or device identifier.','IA-04a.','N/A','Determine if system identifiers are managed by receiving authorization from [IA-04_ODP[01]; personnel or roles from whom authorization must be received to assign an identifier are defined] to assign to an individual, group, role, or device identifier.'),
('001972','draft','2013-05-03','DISA FSO','policy','Manage system identifiers by selecting an identifier that identifies an individual, group, role, or device.','IA-04b.','N/A','Determine if system identifiers are managed by selecting an identifier that identifies an individual, group, role, service, or device.'),
('001973','draft','2013-05-03','DISA FSO','policy','Manage system identifiers by assigning the identifier to the intended individual, group, role, or device.','IA-04c.','N/A','Determine if system identifiers are managed by assigning the identifier to the intended individual, group, role, service, or device.'),
('001974','draft','2013-05-03','DISA FSO','policy','Defines the time period for which the reuse of identifiers is prohibited.','IA-04d.','N/A','Determine if system identifiers are managed by preventing reuse of identifiers for [IA-04_ODP[02]; a time period for preventing reuse of identifiers is defined].'),
('001975','draft','2013-05-03','DISA FSO','policy','Manage system identifiers by preventing reuse of identifiers for an organization-defined time period.','IA-04d.','N/A','Determine if system identifiers are managed by preventing reuse of identifiers for [IA-04_ODP[02]; a time period for preventing reuse of identifiers is defined].'),
('001976','draft','2013-05-03','DISA FSO','technical','Manage individual identifiers dynamically in accordance with organization-defined identifier policy.','IA-04(05)','N/A','Determine if individual identifiers are dynamically managed in accordance with [IA-04(05)_ODP; a dynamic identifier policy for managing individual identifiers is defined].'),
('001977','draft','2013-05-03','DISA FSO','policy','Defines the external organizations with which it will coordinate for cross-management of identifiers.','IA-04(06)','N/A','Determine if cross-organization management of identifiers is coordinated with [IA-04(06)_ODP; external organizations with whom to coordinate the cross-organization management of identifiers are defined].'),
('001978','draft','2013-05-03','DISA FSO','policy','Coordinate with organization-defined external organizations for cross-organization management of identifiers.','IA-04(06)','N/A','Determine if cross-organization management of identifiers is coordinated with [IA-04(06)_ODP; external organizations with whom to coordinate the cross-organization management of identifiers are defined].'),
('001980','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator.','IA-05a.','N/A','Determine if system authenticators are managed through the verification of the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution.'),
('001981','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by establishing administrative procedures for initial authenticator distribution.','IA-05d.','N/A','Determine if system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators.'),
('001984','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by establishing administrative procedures for revoking authenticators.','IA-05d.','N/A','Determine if system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators.'),
('001985','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by implementing administrative procedures for initial authenticator distribution.','IA-05d.','N/A','Determine if system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators.'),
('001988','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by implementing administrative procedures for revoking authenticators.','IA-05d.','N/A','Determine if system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators.'),
('001990','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by changing authenticators for group or role accounts when membership to those accounts changes.','IA-05i.','N/A','Determine if system authenticators are managed through the change of authenticators for group or role accounts when membership to those accounts changes.'),
('001998','draft','2013-05-03','DISA FSO','policy','Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.','IA-05(05)','N/A','Determine if developers and installers of system components are required to provide unique authenticators or change default authenticators prior to delivery and installation.'),
('002001','draft','2013-05-03','DISA FSO','technical','Bind identities and authenticators dynamically using organization-defined binding rules.','IA-05(10)','N/A','Determine if identities and authenticators are dynamically bound using [IA-05(10)_ODP; rules for dynamically binding identities and authenticators are defined].'),
('002004','draft','2013-05-03','DISA FSO','policy','Defines the biometric quality requirements to be employed by the mechanisms for biometric-based authentication.','IA-05(12)','N/A','Determine if mechanisms that satisfy [IA-05(12)_ODP; biometric quality requirements for biometric-based authentication are defined] are employed for biometric-based authentication.'),
('002005','draft','2013-05-03','DISA FSO','technical','For biometric-based authentication, employ mechanisms that satisfy organization-defined biometric quality requirements.','IA-05(12)','N/A','Determine if mechanisms that satisfy [IA-05(12)_ODP; biometric quality requirements for biometric-based authentication are defined] are employed for biometric-based authentication.'),
('002006','draft','2013-05-03','DISA FSO','policy','Defines the time period after which the use of cached authenticators is prohibited.','IA-05(13)','N/A','Determine if the use of cached authenticators is prohibited after [IA-05(13)_ODP; the time period after which the use of cached authenticators is prohibited is defined].'),
('002007','draft','2013-05-03','DISA FSO','technical','Prohibit the use of cached authenticators after an organization-defined time period.','IA-05(13)','N/A','Determine if the use of cached authenticators is prohibited after [IA-05(13)_ODP; the time period after which the use of cached authenticators is prohibited is defined].'),
('002008','draft','2013-05-03','DISA FSO','policy','For PKI-based authentication, employs an organization-wide methodology for managing the content of PKI trust stores installed across all platforms including networks, operating systems, browsers, and applications.','IA-05(14)','N/A','Determine if an organization-wide methodology for managing the content of PKI trust stores is employed across all platforms, including networks, operating systems, browsers, and applications for PKI-based authentication.'),
('002009','draft','2013-05-03','DISA FSO','technical','Accept Personal Identity Verification-compliant credentials from other federal agencies.','IA-08(01)','N/A','Determine if: - Personal Identity Verification-compliant credentials from other federal agencies are accepted. - Personal Identity Verification-compliant credentials from other federal agencies are electronically verified.'),
('002010','draft','2013-05-03','DISA FSO','technical','Electronically verify Personal Identity Verification-compliant credentials from other federal agencies.','IA-08(01)','N/A','Determine if: - Personal Identity Verification-compliant credentials from other federal agencies are accepted. - Personal Identity Verification-compliant credentials from other federal agencies are electronically verified.'),
('002015','draft','2013-05-03','DISA FSO','technical','Accept federated or PKI credentials that meet organization-defined policy.',NULL,'N/A',NULL),
('002016','draft','2013-05-03','DISA FSO','technical','Verify federated PKI credentials that meet organization-defined policy.',NULL,'N/A',NULL),
('002018','draft','2013-05-03','DISA FSO','policy','Defines the system services and applications requiring authentication.','IA-09','N/A','Determine if [IA-09_ODP; system services and applications to be uniquely identified and authenticated are defined] are uniquely identified and authenticated before establishing communications with devices, users, or other services or applications.'),
('002021','draft','2013-05-03','DISA FSO','policy','Uniquely identify organization-defined system services and applications before establishing communications with devices, users, or other services or applications.','IA-09','N/A','Determine if [IA-09_ODP; system services and applications to be uniquely identified and authenticated are defined] are uniquely identified and authenticated before establishing communications with devices, users, or other services or applications.'),
('002022','draft','2013-05-03','DISA FSO','policy','Uniquely authenticate organization-defined system services and applications before establishing communications with devices, users, or other services or applications.','IA-09','N/A','Determine if [IA-09_ODP; system services and applications to be uniquely identified and authenticated are defined] are uniquely identified and authenticated before establishing communications with devices, users, or other services or applications.'),
('002033','draft','2013-05-03','DISA FSO','policy','Defines the specific circumstances or situations when individuals accessing the system employ organization-defined supplemental authentication techniques or mechanisms.','IA-10','N/A','Determine if individuals accessing the system are required to employ [IA-10_ODP[01]; supplemental authentication techniques or mechanisms to be employed when accessing the system under specific circumstances or situations are defined] under specific [IA-10_ODP[02]; circumstances or situations that require individuals accessing the system to employ supplemental authentication techniques or mechanisms are defined].'),
('002034','draft','2013-05-03','DISA FSO','policy','Defines the supplemental authentication techniques or mechanisms to be employed in specific organization-defined circumstances or situations by individuals accessing the system.','IA-10','N/A','Determine if individuals accessing the system are required to employ [IA-10_ODP[01]; supplemental authentication techniques or mechanisms to be employed when accessing the system under specific circumstances or situations are defined] under specific [IA-10_ODP[02]; circumstances or situations that require individuals accessing the system to employ supplemental authentication techniques or mechanisms are defined].'),
('002035','draft','2013-05-03','DISA FSO','policy','Require individuals accessing the system employ organization-defined supplemental authentication techniques or mechanisms under specific organization-defined circumstances or situations.','IA-10','N/A','Determine if individuals accessing the system are required to employ [IA-10_ODP[01]; supplemental authentication techniques or mechanisms to be employed when accessing the system under specific circumstances or situations are defined] under specific [IA-10_ODP[02]; circumstances or situations that require individuals accessing the system to employ supplemental authentication techniques or mechanisms are defined].'),
('002036','draft','2013-05-03','DISA FSO','policy','Defines the circumstances or situations under which users will be required to reauthenticate.','IA-11','N/A','Determine if users are required to re-authenticate when [IA-11_ODP; circumstances or situations requiring re-authentication are defined].'),
('002038','draft','2013-05-03','DISA FSO','technical','The organization requires users to reauthenticate upon organization-defined circumstances or situations requiring reauthentication.',NULL,'N/A',NULL),
('002042','draft','2013-05-03','DISA FSO','policy','Manage system authenticators by protecting authenticator content from unauthorized modification.','IA-05g.','N/A','Determine if system authenticators are managed through the protection of authenticator content from unauthorized disclosure and modification.'),
('002044','draft','2013-05-29','DISA FSO','policy','Defines measures to be employed to ensure that long-term audit records generated by the system can be retrieved.','AU-11(01)','N/A','Determine if [AU-11(01)_ODP; measures to be employed to ensure that long-term audit records generated by the system can be retrieved are defined] are employed to ensure that long-term audit records generated by the system can be retrieved.'),
('002045','draft','2013-05-29','DISA FSO','policy','Employ organization-defined measures to ensure that long-term audit records generated by the information system can be retrieved.','AU-11(01)','N/A','Determine if [AU-11(01)_ODP; measures to be employed to ensure that long-term audit records generated by the system can be retrieved are defined] are employed to ensure that long-term audit records generated by the system can be retrieved.'),
('002047','draft','2013-05-29','DISA FSO','policy','Defines the system components on which the auditing that is to be performed can be changed by organization-defined individuals or roles.','AU-12(03)','N/A','Determine if: - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is provided. - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is implemented.'),
('002048','draft','2013-06-05','DISA FSO','policy','Defines the personnel or roles to whom the awareness and training policy is disseminated.','AT-01a.','N/A','Determine if: - an awareness and training policy is developed and documented. - the awareness and training policy is disseminated to [AT-01_ODP[01]; personnel or roles to whom the awareness and training policy is to be disseminated is/are defined].'),
('002049','draft','2013-06-05','DISA FSO','policy','Defines the personnel or roles to whom the organization-level; mission/business process-level; system-level awareness and training procedures are disseminated.','AT-01a.02','N/A','Determine if: - awareness and training procedures to facilitate the implementation of the awareness and training policy and associated access controls are developed and documented. - the awareness and training procedures are disseminated to [AT-01_ODP[02]; personnel or roles to whom the awareness and training procedures are to be disseminated is/are defined].'),
('002050','draft','2013-06-05','DISA FSO','policy','Defines the personnel or roles to whom initial and refresher training in the employment and operation of environmental controls is to be provided.','AT-03(01)','N/A','Determine if [AT-03(01)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of environmental controls are defined] are provided with initial and refresher training [AT-03(01)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of environmental controls is defined] in the employment and operation of environmental controls.'),
('002051','draft','2013-06-05','DISA FSO','policy','Defines the personnel or roles to whom initial and refresher training in the employment and operation of physical security controls is to be provided.','AT-03(02)','N/A','Determine if [AT-03(02)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of physical security controls is/are defined] is/are provided with initial and refresher training [AT-03(02)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of physical security controls is defined] in the employment and operation of physical security controls.'),
('002052','draft','2013-06-05','DISA FSO','policy','Provide practical exercises in security training that reinforce training objectives.','AT-03(03)','N/A','Determine if: - practical exercises in security training that reinforce training objectives are provided. - practical exercises in privacy training that reinforce training objectives are provided.'),
('002055','draft','2013-06-05','DISA FSO','policy','Provide literacy training on recognizing and reporting potential indicators of insider threat.','AT-02(02)','N/A','Determine if: - literacy training on recognizing potential indicators of insider threat is provided. - literacy training on reporting potential indicators of insider threat is provided.'),
('002056','draft','2013-06-11','DISA FSO','policy','Defines the time period the records of configuration-controlled changes are to be retained.','CM-03d.','N/A','Determine if approved configuration-controlled changes to the system are implemented.'),
('002057','draft','2013-06-11','DISA FSO','policy','Defines the personnel to be notified when approved changes to the system are completed.','CM-03(01)(f)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to notify [CM-03(01)_ODP[04]; personnel to be notified when approved changes are complete is/are defined] when approved changes to the system are completed.'),
('002058','draft','2013-06-11','DISA FSO','policy','Employ automated mechanisms to notify organization-defined personnel when approved changes to the system are completed.','CM-03(01)(f)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to notify [CM-03(01)_ODP[04]; personnel to be notified when approved changes are complete is/are defined] when approved changes to the system are completed.'),
('002059','draft','2013-06-11','DISA FSO','policy','Defines the system components for which the organization will employ automated mechanisms to centrally manage, apply, and verify configuration settings.','CM-06(01)','N/A','Determine if: - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are managed using [CM-06(01)_ODP[02]; automated mechanisms to manage configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are applied using [CM-06(01)_ODP[03]; automated mechanisms to apply configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are verified using [CM-06(01)_ODP[04]; automated mechanisms to verify configuration settings are defined].'),
('002061','draft','2013-06-21','DISA FSO','policy','Defines the personnel or roles to whom the organization-level; mission/business process; system-level assessment, authorization, and monitoring policy is to be disseminated.','CA-01a.','N/A','Determine if: - an assessment, authorization, and monitoring policy is developed and documented. - the assessment, authorization, and monitoring policy is disseminated to [CA-01_ODP[01]; personnel or roles to whom the assessment, authorization, and monitoring policy is to be disseminated is/are defined].'),
('002062','draft','2013-06-21','DISA FSO','policy','Defines the personnel or roles to whom the assessment, authorization, monitoring procedures are to be disseminated.','CA-01a.02','N/A','Determine if: - assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented. - the assessment, authorization, and monitoring procedures are disseminated to [CA-01_ODP[02]; personnel or roles to whom the assessment, authorization, and monitoring procedures are to be disseminated is/are defined].'),
('002065','draft','2013-06-21','DISA FSO','policy','Defines the frequency at which to conduct control assessments.','CA-02(02)','N/A','Determine if [CA-02(02)_ODP[01]; frequency at which to include specialized assessments as part of the control assessment is defined] [CA-02(02)_ODP[02]; one of the following PARAMETER VALUES is selected: {announced; unannounced}] [CA-02(02)_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {in-depth monitoring; security instrumentation; automated security test cases; vulnerability scanning; malicious user testing; insider threat assessment; performance and load testing; data leakage or data loss assessment; [CA-02(02)_ODP[04]; other forms of assessment are defined (if selected)]}] are included as part of control assessments.'),
('002066','draft','2013-06-21','DISA FSO','policy','Leverage the results of control assessments of the organization-defined system performed by an organization-defined external organization when the assessment meets organization-defined requirements.','CA-02(03)','N/A','Determine if the results of control assessments performed by [CA-02(03)_ODP[01]; external organizations from which the results of control assessments are leveraged are defined] on [CA-02(03)_ODP[02]; system on which a control assessment was performed by an external organization is defined] are leveraged when the assessment meets [CA-02(03)_ODP[03]; requirements to be met by the control assessment performed by an external organization on the system are defined].'),
('002067','draft','2013-06-21','DISA FSO','policy','Defines the system for which the results of control assessments will be leveraged.',NULL,'N/A',NULL),
('002068','draft','2013-06-21','DISA FSO','policy','Defines the external organizations from which control assessment results for organization-defined systems will be accepted.','CA-02(03)','N/A','Determine if the results of control assessments performed by [CA-02(03)_ODP[01]; external organizations from which the results of control assessments are leveraged are defined] on [CA-02(03)_ODP[02]; system on which a control assessment was performed by an external organization is defined] are leveraged when the assessment meets [CA-02(03)_ODP[03]; requirements to be met by the control assessment performed by an external organization on the system are defined].'),
('002069','draft','2013-06-21','DISA FSO','policy','Defines the requirements the control assessments for organization-defined systems from organization-defined external organizations must meet.','CA-02(03)','N/A','Determine if the results of control assessments performed by [CA-02(03)_ODP[01]; external organizations from which the results of control assessments are leveraged are defined] on [CA-02(03)_ODP[02]; system on which a control assessment was performed by an external organization is defined] are leveraged when the assessment meets [CA-02(03)_ODP[03]; requirements to be met by the control assessment performed by an external organization on the system are defined].'),
('002070','draft','2013-06-21','DISA FSO','policy','Develop a control assessment plan that describes the scope of the assessment including assessment team, and assessment roles and responsibilities.','CA-02b.03','N/A','Determine if: - a control assessment plan is developed that describes the scope of the assessment, including the assessment environment. - a control assessment plan is developed that describes the scope of the assessment, including the assessment team. - a control assessment plan is developed that describes the scope of the assessment, including assessment roles and responsibilities.'),
('002071','draft','2013-06-21','DISA FSO','policy','Defines the individuals or roles to whom the results of the control assessment are to be provided.','CA-02f.','N/A','Determine if the results of the control assessment are provided to [CA-02_ODP[02]; individuals or roles to whom control assessment results are to be provided are defined].'),
('002083','draft','2013-06-21','DISA FSO','policy','Review and update the agreements on an organization-defined frequency.','CA-03c.','N/A','Determine if agreements are reviewed and updated [CA-03_ODP[03]; the frequency at which to review and update agreements is defined].'),
('002084','draft','2013-06-21','DISA FSO','policy','Defines the frequency at which reviews and updates to the agreements must be conducted.','CA-03c.','N/A','Determine if agreements are reviewed and updated [CA-03_ODP[03]; the frequency at which to review and update agreements is defined].'),
('002086','draft','2013-06-21','DISA FSO','policy','Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring process need to be modified based on empirical data.','CA-07(03)','N/A','Determine if: - trend analysis is employed to determine if control implementations used in the continuous monitoring process need to be modified based on empirical data. - trend analysis is employed to determine if the frequency of continuous monitoring activities used in the continuous monitoring process needs to be modified based on empirical data. - trend analysis is employed to determine if the types of activities used in the continuous monitoring process need to be modified based on empirical data.'),
('002087','draft','2013-06-21','DISA FSO','policy','Establish organization-defined system-level metrics to be monitored.','CA-07a.','N/A','Determine if system-level continuous monitoring includes establishment of the following system-level metrics to be monitored: [CA-07_ODP[01]; system-level metrics to be monitored are defined].'),
('002088','draft','2013-06-21','DISA FSO','policy','Establish organization-defined frequencies for monitoring.','CA-07b.','N/A','Determine if: - system-level continuous monitoring includes established [CA-07_ODP[02]; frequencies at which to monitor control effectiveness are defined] for monitoring. - system-level continuous monitoring includes established [CA-07_ODP[03]; frequencies at which to assess control effectiveness are defined] for assessment of control effectiveness.'),
('002090','draft','2013-06-21','DISA FSO','policy','Implement ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy.','CA-07d.','N/A','Determine if system-level continuous monitoring includes ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy.'),
('002091','draft','2013-06-21','DISA FSO','policy','Implement a continuous monitoring program that includes correlation and analysis of information generated by assessments and monitoring.','CA-07e.','N/A','Determine if system-level continuous monitoring includes correlation and analysis of information generated by control assessments and monitoring.'),
('002092','draft','2013-06-21','DISA FSO','policy','Implement a continuous monitoring program that includes response actions to address results of the analysis of control assessment and monitoring information.','CA-07f.','N/A','Determine if system-level continuous monitoring includes response actions to address the results of the analysis of control assessment and monitoring information.'),
('002093','draft','2013-06-21','DISA FSO','policy','Conduct penetration testing in accordance with organization-defined frequency on organization-defined systems or system components.','CA-08','N/A','Determine if penetration testing is conducted [CA-08_ODP[01]; frequency at which to conduct penetration testing on systems or system components is defined] on [CA-08_ODP[02]; systems or system components on which penetration testing is to be conducted are defined].'),
('002094','draft','2013-06-21','DISA FSO','policy','Defines the frequency for conducting penetration testing on organization-defined systems or system components.','CA-08','N/A','Determine if penetration testing is conducted [CA-08_ODP[01]; frequency at which to conduct penetration testing on systems or system components is defined] on [CA-08_ODP[02]; systems or system components on which penetration testing is to be conducted are defined].'),
('002095','draft','2013-06-21','DISA FSO','policy','Defines the systems or system components on which penetration testing will be conducted.','CA-08','N/A','Determine if penetration testing is conducted [CA-08_ODP[01]; frequency at which to conduct penetration testing on systems or system components is defined] on [CA-08_ODP[02]; systems or system components on which penetration testing is to be conducted are defined].'),
('002096','draft','2013-06-21','DISA FSO','policy','Employ an independent penetration agent or penetration team to perform penetration testing on the system or system components.','CA-08(01)','N/A','Determine if an independent penetration testing agent or team is employed to perform penetration testing on the system or system components.'),
('002097','draft','2013-06-21','DISA FSP','policy','Defines red team exercises to simulate attempts by adversaries to compromise organizational systems.','CA-08(02)','N/A','Determine if [CA-08(02)_ODP; red team exercises to simulate attempts by adversaries to compromise organizational systems are defined] are employed to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement.'),
('002099','draft','2013-06-21','DISA FSO','policy','Employ organization-defined red team exercises to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement.','CA-08(02)','N/A','Determine if [CA-08(02)_ODP; red team exercises to simulate attempts by adversaries to compromise organizational systems are defined] are employed to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement.'),
('002100','draft','2013-06-21','DISA FSO','policy','Perform security compliance checks on constituent components prior to the establishment of the internal connection.','CA-09(01)','N/A','Determine if: - security compliance checks are performed on constituent system components prior to the establishment of the internal connection. - privacy compliance checks are performed on constituent system components prior to the establishment of the internal connection.'),
('002101','draft','2013-06-21','DISA FSO','policy','Authorizes internal connections of organization-defined system components or classes of components to the system.','CA-09a.','N/A','Determine if internal connections of [CA-09_ODP[01]; system components or classes of components requiring internal connections to the system are defined] to the system are authorized.'),
('002102','draft','2013-06-21','DISA FSO','policy','Defines the system components or classes of components that are authorized internal connections to the system.','CA-09a.','N/A','Determine if internal connections of [CA-09_ODP[01]; system components or classes of components requiring internal connections to the system are defined] to the system are authorized.'),
('002103','draft','2013-06-21','DISA FSO','policy','Document, for each internal connection, the interface characteristics.','CA-09b.','N/A','Determine if: - for each internal connection, the interface characteristics are documented. - for each internal connection, the security requirements are documented. - for each internal connection, the privacy requirements are documented. - for each internal connection, the nature of the information communicated is documented.'),
('002104','draft','2013-06-21','DISA FSO','policy','Document, for each internal connection, the security requirements.','CA-09b.','N/A','Determine if: - for each internal connection, the interface characteristics are documented. - for each internal connection, the security requirements are documented. - for each internal connection, the privacy requirements are documented. - for each internal connection, the nature of the information communicated is documented.'),
('002105','draft','2013-06-21','DISA FSO','policy','Document, for each internal connection, the nature of the information communicated.','CA-09b.','N/A','Determine if: - for each internal connection, the interface characteristics are documented. - for each internal connection, the security requirements are documented. - for each internal connection, the privacy requirements are documented. - for each internal connection, the nature of the information communicated is documented.'),
('002107','draft','2013-06-24','DISA FSO','policy','Defines the personnel or roles to be recipients of the organization-level; mission/business process-level; and/or system-level access control policy necessary to facilitate the implementation of the access control policy and associated access controls.','AC-01a.','N/A','Determine if: - an access control policy is developed and documented. - the access control policy is disseminated to [AC-01_ODP[01]; personnel or roles to whom the access control policy is to be disseminated is/are defined].'),
('002108','draft','2013-06-24','DISA FSO','policy','Defines the personnel or roles to be recipients of the procedures necessary to facilitate the implementation of the organization-level; mission/business process-level; and/or system-level access control policy and associated access controls.','AC-01a.02','N/A','Determine if: - access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented. - the access control procedures are disseminated to [AC-01_ODP[02]; personnel or roles to whom the access control procedures are to be disseminated is/are defined].'),
('002112','draft','2013-06-24','DISA FSO','policy','Assign account managers.','AC-02b.','N/A','Determine if account managers are assigned.'),
('002115','draft','2013-06-24','DISA FSO','policy','Specify authorized users of the system.','AC-02d.01','N/A','Determine if authorized users of the system are specified.'),
('002116','draft','2013-06-24','DISA FSO','policy','Specify authorized users of the group.','AC-02d.02','N/A','Determine if group and role membership are specified.'),
('002117','draft','2013-06-24','DISA FSO','policy','Specify authorized users of the role membership.','AC-02d.02','N/A','Determine if group and role membership are specified.'),
('002118','draft','2013-06-24','DISA FSO','policy','Specify authorized access authorizations (i.e., privileges) for each account.','AC-02d.03','N/A','Determine if: - access authorizations (i.e., privileges) are specified for each account. - [AC-02_ODP[02]; attributes (as required) for each account are defined] are specified for each account. '),
('002119','draft','2013-06-24','DISA FSO','policy','Specify organization-attributes (as required) for each account on the system.','AC-02d.03','N/A','Determine if: - access authorizations (i.e., privileges) are specified for each account. - [AC-02_ODP[02]; attributes (as required) for each account are defined] are specified for each account. '),
('002120','draft','2013-06-24','DISA FSO','policy','Defines the personnel or roles authorized to approve the creation of accounts.','AC-02e.','N/A','Determine if approvals are required by [AC-02_ODP[03]; personnel or roles required to approve requests to create accounts is/are defined] for requests to create accounts.'),
('002121','draft','2013-06-24','DISA FSO','policy','Defines the procedures to be employed when creating, enabling, modifying, disabling, and removing information system accounts.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('002122','draft','2013-06-24','DISA FSO','policy','Monitor the use of accounts.','AC-02g.','N/A','Determine if the use of accounts is monitored.'),
('002123','draft','2013-06-24','DISA FSO','policy','Notify account managers and organization-defined personnel or roles within an organization-defined time-period when accounts are no longer required.','AC-02h.01','N/A','Determine if account managers and [AC-02_ODP[05]; personnel or roles to be notified is/are defined] are notified within [AC-02_ODP[06]; time period within which to notify account managers when accounts are no longer required is defined] when accounts are no longer required.'),
('002124','draft','2013-06-24','DISA FSO','policy','Notify account managers and organization-defined personnel or roles within an organization-defined time-period when users are terminated or transferred.','AC-02h.02','N/A','Determine if account managers and [AC-02_ODP[05]; personnel or roles to be notified is/are defined] are notified within [AC-02_ODP[07]; time period within which to notify account managers when users are terminated or transferred is defined] when users are terminated or transferred.'),
('002125','draft','2013-06-24','DISA FSO','policy','Notify account managers and organization-defined personnel or roles within an organization-defined time-period when system usage or need-to-know changes for an individual.','AC-02h.03','N/A','Determine if account managers and [AC-02_ODP[05]; personnel or roles to be notified is/are defined] are notified within [AC-02_ODP[08]; time period within which to notify account managers when system usage or the need to know changes for an individual is defined] when system usage or the need to know changes for an individual.'),
('002126','draft','2013-06-24','DISA FSO','policy','Authorize access to the system based on a valid access authorization.','AC-02i.01','N/A','Determine if access to the system is authorized based on a valid access authorization.'),
('002127','draft','2013-06-24','DISA FSO','policy','Authorize access to the system based on intended system usage.','AC-02i.02','N/A','Determine if access to the system is authorized based on intended system usage.'),
('002128','draft','2013-06-24','DISA FSO','policy','Authorize access to the system based on organization-defined attributes (as required).','AC-02i.03','N/A','Determine if access to the system is authorized based on [AC-02_ODP[09]; attributes needed to authorize system access (as required) are defined].'),
('002129','draft','2013-06-24','DISA FSO','policy','Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group.','AC-02k.','N/A','Determine if: - a process is established for changing shared or group account authenticators (if deployed) when individuals are removed from the group. - a process is implemented for changing shared or group account authenticators (if deployed) when individuals are removed from the group.'),
('002130','draft','2013-06-24','DISA FSO','technical','Automatically audit account enabling actions.','AC-02(04)','N/A','Determine if: - account creation is automatically audited. - account modification is automatically audited. - account enabling is automatically audited. - account disabling is automatically audited. - account removal actions are automatically audited.'),
('002133','draft','2013-06-24','DISA FSO ','policy','Defines other conditions when users are required to log out.','AC-02(05)','N/A','Determine if users are required to log out when [AC-02(05)_ODP; the time period of expected inactivity or description of when to log out is defined].'),
('002134','draft','2013-06-24','DISA FSO','policy','Defines a list of dynamic privilege management capabilities to be implemented.','AC-02(06)','N/A','Determine if [AC-02(06)_ODP; dynamic privilege management capabilities are defined] are implemented.'),
('002135','draft','2013-06-24','DISA FSO','technical','Implement the organization-defined list of dynamic privilege management capabilities.','AC-02(06)','N/A','Determine if [AC-02(06)_ODP; dynamic privilege management capabilities are defined] are implemented.'),
('002137','draft','2013-06-24','DISA FSO','policy','Revoke access when privileged role or attribute assignments are no longer appropriate.','AC-02(07)(d)','N/A','Determine if access is revoked when privileged role or attribute assignments are no longer appropriate.'),
('002138','draft','2013-06-24','DISA FSO','policy','Defines the system accounts that can be dynamically created.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('002139','draft','2013-06-24','DISA FSO','technical','Create organization-defined system accounts dynamically.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('002140','draft','2013-06-24','DISA FSO ','policy','Defines the conditions for establishing shared/group accounts.','AC-02(09)','N/A','Determine if the use of shared and group accounts is only permitted if [AC-02(09)_ODP; conditions for establishing shared and group accounts are defined] are met.'),
('002141','draft','2013-06-24','DISA FSO','policy','Only permit the use of shared and group accounts that meet organization-defined conditions for establishing shared and group accounts.','AC-02(09)','N/A','Determine if the use of shared and group accounts is only permitted if [AC-02(09)_ODP; conditions for establishing shared and group accounts are defined] are met.'),
('002143','draft','2013-06-24','DISA FSO','policy','Defines the circumstances and/or usage conditions that are to be enforced for organization-defined information system accounts.','AC-02(11)','N/A','Determine if [AC-02(11)_ODP[01]; circumstances and/or usage conditions to be enforced for system accounts are defined] for [AC-02(11)_ODP[02]; system accounts subject to enforcement of circumstances and/or usage conditions are defined] are enforced.'),
('002144','draft','2013-06-24','DISA FSO ','policy','Defines the system accounts that are to be subject to the enforcement of organization-defined circumstances and/or usage conditions.','AC-02(11)','N/A','Determine if [AC-02(11)_ODP[01]; circumstances and/or usage conditions to be enforced for system accounts are defined] for [AC-02(11)_ODP[02]; system accounts subject to enforcement of circumstances and/or usage conditions are defined] are enforced.'),
('002145','draft','2013-06-24','DISA FSO','technical','Enforce organization-defined circumstances and/or usage conditions for organization-defined system accounts.','AC-02(11)','N/A','Determine if [AC-02(11)_ODP[01]; circumstances and/or usage conditions to be enforced for system accounts are defined] for [AC-02(11)_ODP[02]; system accounts subject to enforcement of circumstances and/or usage conditions are defined] are enforced.'),
('002146','draft','2013-06-24','DISA FSO','policy','Defines atypical usage for which the system accounts are to be monitored.','AC-02(12)(a)','N/A','Determine if system accounts are monitored for [AC-02(12)_ODP[01]; atypical usage for which to monitor system accounts is defined].'),
('002147','draft','2013-06-24','DISA FSO','policy','Monitor system accounts for organization-defined atypical usage.','AC-02(12)(a)','N/A','Determine if system accounts are monitored for [AC-02(12)_ODP[01]; atypical usage for which to monitor system accounts is defined].'),
('002148','draft','2013-06-24','DISA FSO','policy','Defines the personnel or roles to whom atypical usage of system accounts are to be reported.','AC-02(12)(b)','N/A','Determine if atypical usage of system accounts is reported to [AC-02(12)_ODP[02]; personnel or roles to report atypical usage is/are defined].'),
('002149','draft','2013-06-24','DISA FSO','policy','Report atypical usage of system accounts to organization-defined personnel or roles.','AC-02(12)(b)','N/A','Determine if atypical usage of system accounts is reported to [AC-02(12)_ODP[02]; personnel or roles to report atypical usage is/are defined].'),
('002150','draft','2013-06-24','DISA FSO','policy','Defines the time period within which the accounts of users posing a significant risk are to be disabled after discovery of the risk.','AC-02(13)','N/A','Determine if accounts of individuals are disabled within [AC-02(13)_ODP[01]; time period within which to disable accounts of individuals who are discovered to pose significant risk is defined] of discovery of [AC-02(13)_ODP[02]; significant risks leading to disabling accounts are defined].'),
('002151','draft','2013-06-24','DISA FSO','policy','Disable accounts of individuals within an organization-defined time-period of discovery of organization-defined significant risk.','AC-02(13)','N/A','Determine if accounts of individuals are disabled within [AC-02(13)_ODP[01]; time period within which to disable accounts of individuals who are discovered to pose significant risk is defined] of discovery of [AC-02(13)_ODP[02]; significant risks leading to disabling accounts are defined].'),
('002152','draft','2013-06-24','DISA FSO','policy','Defines other actions necessary for which dual authorization is to be enforced.','AC-03(02)','N/A','Determine if dual authorization is enforced for [AC-03(02)_ODP; privileged commands and/or other actions requiring dual authorization are defined].'),
('002153','draft','2013-06-24','DISA FSO','policy','Defines the mandatory access control policies that are to be enforced over all subjects and objects.','AC-03(03)','N/A','Determine if: - [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] is enforced over the set of covered objects specified in the policy.'),
('002154','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy is uniformly enforced across the covered subjects and objects within the system.','AC-03(03)(a)','N/A','Determine if: - [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] is uniformly enforced across the covered subjects within the system. - [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] is uniformly enforced across the covered objects within the system.'),
('002155','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information is constrained from passing the information to unauthorized subjects or objects.','AC-03(03)(b)(01)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that a subject that has been granted access to information is constrained from passing the information to unauthorized subjects or objects are enforced.'),
('002156','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information is constrained from granting its privileges to other subjects.','AC-03(03)(b)(02)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that a subject that has been granted access to information is constrained from granting its privileges to other subjects are enforced.'),
('002157','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information is constrained from changing one or more security attributes on subjects, objects, the system, or system components.','AC-03(03)(b)(03)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that a subject that has been granted access to information is constrained from changing one of more security attributes (specified by the policy) on subjects, objects, the system, or system components are enforced.'),
('002158','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information is constrained from choosing the security attributes to be associated with newly created or modified objects.','AC-03(03)(b)(04)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that a subject that has been granted access to information is constrained from choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects are enforced.'),
('002159','draft','2013-06-24','DISA FSO ','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information is constrained from choosing the attribute values to be associated with newly created or modified objects.','AC-03(03)(b)(04)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that a subject that has been granted access to information is constrained from choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects are enforced.'),
('002160','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information is constrained from changing the rules governing access control.','AC-03(03)(b)(05)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that a subject that has been granted access to information is constrained from changing the rules governing access control are enforced.'),
('002161','draft','2013-06-24','DISA FSO','policy','Defines subjects which may explicitly be granted organization-defined privileges such that they are not limited by any of the mandatory access control constraints.','AC-03(03)(c)','N/A','Determine if [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] and [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] specifying that [AC-03(03)_ODP[03]; subjects to be explicitly granted privileges are defined] may explicitly be granted [AC-03(03)_ODP[04]; privileges to be explicitly granted to subjects are defined] such that they are not limited by any defined subset (or all) of the above constraints are enforced.'),
('002162','draft','2013-06-24','DISA FSO','policy','Defines the privileges that may explicitly be granted to organization-defined subjects such that they are not limited by any of the mandatory access control constraints.','AC-03(04)','N/A','Determine if: - [AC-03(04)_ODP[01]; discretionary access control policy enforced over the set of covered subjects is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(04)_ODP[02]; discretionary access control policy enforced over the set of covered objects is defined] is enforced over the set of covered objects specified in the policy.'),
('002163','draft','2013-06-24','DISA FSO','policy','Defines the discretionary access control policies the information system is to enforce over subjects and objects.',NULL,'N/A',NULL),
('002164','draft','2013-06-24','DISA FSO','policy','Enforce organization-defined discretionary access control policy that over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following: pass the information to any other subjects or objects; grant its privileges to other subjects; change security attributes on subjects, objects, the system, or the system''s components; choose the security attributes to be associated with newly created or revised objects; and/or change the rules governing access control.',NULL,'N/A',NULL),
('002165','draft','2013-06-24','DISA FSO','technical','Enforce organization-defined discretionary access control policies over defined subjects and objects.',NULL,'N/A',NULL),
('002166','draft','2013-06-24','DISA FSO','policy','Defines the role-based access control policies to enforce over all subjects and objects.','AC-03(07)','N/A','Determine if: - a role-based access control policy is enforced over defined subjects. - a role-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(07)_ODP[01]; roles upon which to base control of access are defined] and [AC-03(07)_ODP[02]; users authorized to assume roles (defined in AC-03(07)_ODP[01]) are defined.]'),
('002169','draft','2013-06-24','DISA FSO','technical','Enforce a role-based access control policy over defined subjects and objects based upon organization-defined roles and users authorized to assume such roles.','AC-03(07)','N/A','Determine if: - a role-based access control policy is enforced over defined subjects. - a role-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(07)_ODP[01]; roles upon which to base control of access are defined] and [AC-03(07)_ODP[02]; users authorized to assume roles (defined in AC-03(07)_ODP[01]) are defined.]'),
('002170','draft','2013-06-24','DISA FSO','policy','Control access based upon organization-defined roles and users authorized to assume such roles.','AC-03(07)','N/A','Determine if: - a role-based access control policy is enforced over defined subjects. - a role-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(07)_ODP[01]; roles upon which to base control of access are defined] and [AC-03(07)_ODP[02]; users authorized to assume roles (defined in AC-03(07)_ODP[01]) are defined.]'),
('002173','draft','2013-06-24','DISA FSO','policy','Defines the roles authorized to control access based upon the role-based access control policy.','AC-03(07)','N/A','Determine if: - a role-based access control policy is enforced over defined subjects. - a role-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(07)_ODP[01]; roles upon which to base control of access are defined] and [AC-03(07)_ODP[02]; users authorized to assume roles (defined in AC-03(07)_ODP[01]) are defined.]'),
('002174','draft','2013-06-24','DISA FSO','policy','Defines the users authorized to control access based upon the role-based access control policy.','AC-03(07)','N/A','Determine if: - a role-based access control policy is enforced over defined subjects. - a role-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(07)_ODP[01]; roles upon which to base control of access are defined] and [AC-03(07)_ODP[02]; users authorized to assume roles (defined in AC-03(07)_ODP[01]) are defined.]'),
('002177','draft','2013-06-24','DISA FSO','policy','Defines the rules governing the timing of revocation of access authorizations.','AC-03(08)','N/A','Determine if: - revocation of access authorizations is enforced, resulting from changes to the security attributes of subjects based on [AC-03(08)_ODP; rules governing the timing of revocations of access authorizations are defined]. - revocation of access authorizations is enforced resulting from changes to the security attributes of objects based on [AC-03(08)_ODP; rules governing the timing of revocations of access authorizations are defined].'),
('002178','draft','2013-06-24','DISA FSO','technical','Enforce the revocation of access authorizations resulting from changes to the security attributes of subjects based on organization-defined rules governing the timing of revocations of access authorizations.','AC-03(08)','N/A','Determine if: - revocation of access authorizations is enforced, resulting from changes to the security attributes of subjects based on [AC-03(08)_ODP; rules governing the timing of revocations of access authorizations are defined]. - revocation of access authorizations is enforced resulting from changes to the security attributes of objects based on [AC-03(08)_ODP; rules governing the timing of revocations of access authorizations are defined].'),
('002179','draft','2013-06-24','DISA FSO','technical','Enforce the revocation of access authorizations resulting from changes to the security attributes of objects based on organization-defined rules governing the timing of revocations of access authorizations.','AC-03(08)','N/A','Determine if: - revocation of access authorizations is enforced, resulting from changes to the security attributes of subjects based on [AC-03(08)_ODP; rules governing the timing of revocations of access authorizations are defined]. - revocation of access authorizations is enforced resulting from changes to the security attributes of objects based on [AC-03(08)_ODP; rules governing the timing of revocations of access authorizations are defined].'),
('002180','draft','2013-06-24','DISA FSO','policy','Defines the controls the organization-defined system or system component is to provide to protect information released outside the established system boundary.','AC-03(09)(a)','N/A','Determine if information is released outside of the system only if the receiving [AC-03(09)_ODP[01]; the outside system or system component to which to release information is defined] provides [AC-03(09)_ODP[02]; controls to be provided by the outside system or system component (defined in AC-03(09)_ODP[01]) are defined].'),
('002181','draft','2013-06-24','DISA FSO','policy','Defines system or system components that are to provide organization-defined controls to protect information received outside the established system boundary.','AC-03(09)(a)','N/A','Determine if information is released outside of the system only if the receiving [AC-03(09)_ODP[01]; the outside system or system component to which to release information is defined] provides [AC-03(09)_ODP[02]; controls to be provided by the outside system or system component (defined in AC-03(09)_ODP[01]) are defined].'),
('002182','draft','2013-06-24','DISA FSO','policy','Release information outside of the established system boundary only if organization-defined system or system components provides organization-defined controls.','AC-03(09)(a)','N/A','Determine if information is released outside of the system only if the receiving [AC-03(09)_ODP[01]; the outside system or system component to which to release information is defined] provides [AC-03(09)_ODP[02]; controls to be provided by the outside system or system component (defined in AC-03(09)_ODP[01]) are defined].'),
('002183','draft','2013-06-24','DISA FSO ','policy','Defines the controls to be used to validate the appropriateness of the information designated for release.','AC-03(09)(b)','N/A','Determine if information is released outside of the system only if [AC-03(09)_ODP[03]; controls used to validate appropriateness of information to be released are defined] are used to validate the appropriateness of the information designated for release.'),
('002184','draft','2013-06-24','DISA FSO','policy','Release information outside of the established system boundary only if organization-defined controls are used to validate the appropriateness of the information designated for release.','AC-03(09)(b)','N/A','Determine if information is released outside of the system only if [AC-03(09)_ODP[03]; controls used to validate appropriateness of information to be released are defined] are used to validate the appropriateness of the information designated for release.'),
('002185','draft','2013-06-24','DISA FSO','policy','Defines the conditions on which it will employ an audited override of automated access control mechanisms.','AC-03(10)','N/A','Determine if an audited override of automated access control mechanisms is employed under [AC-03(10)_ODP[01]; conditions under which to employ an audited override of automated access control mechanisms are defined] by [AC-03(10)_ODP[02]; roles allowed to employ an audited override of automated access control mechanisms are defined].'),
('002186','draft','2013-06-24','DISA FSO','technical','Employ an audited override of automated access control mechanisms under organization-defined conditions by organization-defined roles.','AC-03(10)','N/A','Determine if an audited override of automated access control mechanisms is employed under [AC-03(10)_ODP[01]; conditions under which to employ an audited override of automated access control mechanisms are defined] by [AC-03(10)_ODP[02]; roles allowed to employ an audited override of automated access control mechanisms are defined].'),
('002187','draft','2013-06-24','DISA FSO','policy','Defines the security attributes to be used to enforce organization-defined information flow control policies.','AC-04(01)','N/A','Determine if: - [AC-04(01)_ODP[01]; security attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[03]; information objects to be associated with information security attributes are defined], [AC-04(01)_ODP[05]; source objects to be associated with information security attributes are defined], and [AC-04(01)_ODP[07]; destination objects to be associated with information security attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions. - [AC-04(01)_ODP[02]; privacy attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[04]; information objects to be associated with privacy attributes are defined], [AC-04(01)_ODP[06]; source objects to be associated with privacy attributes are defined], and [AC-04(01)_ODP[08]; destination objects to be associated with privacy attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions.'),
('002188','draft','2013-06-24','DISA FSO','policy','Defines the information, source, and destination objects with which the organization-defined security attributes are to be associated.','AC-04(01)','N/A','Determine if: - [AC-04(01)_ODP[01]; security attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[03]; information objects to be associated with information security attributes are defined], [AC-04(01)_ODP[05]; source objects to be associated with information security attributes are defined], and [AC-04(01)_ODP[07]; destination objects to be associated with information security attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions. - [AC-04(01)_ODP[02]; privacy attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[04]; information objects to be associated with privacy attributes are defined], [AC-04(01)_ODP[06]; source objects to be associated with privacy attributes are defined], and [AC-04(01)_ODP[08]; destination objects to be associated with privacy attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions.'),
('002189','draft','2013-06-24','DISA FSO','policy','Defines the information flow control policies to be enforced for flow control decisions.','AC-04(01)','N/A','Determine if: - [AC-04(01)_ODP[01]; security attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[03]; information objects to be associated with information security attributes are defined], [AC-04(01)_ODP[05]; source objects to be associated with information security attributes are defined], and [AC-04(01)_ODP[07]; destination objects to be associated with information security attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions. - [AC-04(01)_ODP[02]; privacy attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[04]; information objects to be associated with privacy attributes are defined], [AC-04(01)_ODP[06]; source objects to be associated with privacy attributes are defined], and [AC-04(01)_ODP[08]; destination objects to be associated with privacy attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions.'),
('002190','draft','2013-06-24','DISA FSO','technical','Use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions.','AC-04(01)','N/A','Determine if: - [AC-04(01)_ODP[01]; security attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[03]; information objects to be associated with information security attributes are defined], [AC-04(01)_ODP[05]; source objects to be associated with information security attributes are defined], and [AC-04(01)_ODP[07]; destination objects to be associated with information security attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions. - [AC-04(01)_ODP[02]; privacy attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[04]; information objects to be associated with privacy attributes are defined], [AC-04(01)_ODP[06]; source objects to be associated with privacy attributes are defined], and [AC-04(01)_ODP[08]; destination objects to be associated with privacy attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions.'),
('002191','draft','2013-06-24','DISA FSO','policy','Defines the information flow control policies to be enforced by the information system using protected processing domains.','AC-04(02)','N/A','Determine if protected processing domains are used to enforce [AC-04(02)_ODP; information flow control policies to be enforced by use of protected processing domains are defined] as a basis for flow control decisions.'),
('002192','draft','2013-06-24','DISA FSO','policy','Defines the policies to enforce dynamic information flow control.','AC-04(03)','N/A','Determine if [AC-04(03)_ODP; information flow control policies to be enforced are defined] are enforced.'),
('002193','draft','2013-06-24','DISA FSO','policy','Defines procedures or methods to be employed to prevent encrypted information from bypassing flow control mechanisms, such as decrypting the information, blocking the flow of the encrypted information, and/or terminating communications sessions attempting to pass encrypted information.','AC-04(04)','N/A','Determine if encrypted information is prevented from bypassing [AC-04(04)_ODP[01]; information flow control mechanisms that encrypted information is prevented from bypassing are defined] by [AC-04(04)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [AC-04(04)_ODP[03]; the organization-defined procedure or method used to prevent encrypted information from bypassing information flow control mechanisms is defined (if selected)]].'),
('002194','draft','2013-06-24','DISA FSO','policy','Defines the metadata the information system uses to enforce information flow control.','AC-04(06)','N/A','Determine if information flow control enforcement is based on [AC-04(06)_ODP; metadata on which to base enforcement of information flow control is defined].'),
('002195','draft','2013-06-24','DISA FSO','policy','Defines the information flows against which the organization-defined security or privacy policy filters are to be enforced.','AC-04(08)(a)','N/A','Determine if: - information flow control is enforced using [AC-04(08)_ODP[01]; security policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[03]; information flows for which information flow control is enforced by security filters are defined]. - information flow control is enforced using [AC-04(08)_ODP[02]; privacy policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[04]; information flows for which information flow control is enforced by privacy filters are defined].'),
('002196','draft','2013-06-24','DISA FSO','policy','Defines the information flows for which will enforce the use of human reviews under organization-defined conditions.','AC-04(09)','N/A','Determine if human reviews are used for [AC-04(09)_ODP[01]; information flows requiring the use of human reviews are defined] under [AC-04(09)_ODP[02]; conditions under which the use of human reviews for information flows are to be enforced are defined].'),
('002197','draft','2013-06-24','DISA FSO','policy','Defines the conditions which will require the use of human reviews of organization-defined information flows.','AC-04(09)','N/A','Determine if human reviews are used for [AC-04(09)_ODP[01]; information flows requiring the use of human reviews are defined] under [AC-04(09)_ODP[02]; conditions under which the use of human reviews for information flows are to be enforced are defined].'),
('002198','draft','2013-06-24','DISA FSO','policy','Enforce the use of human reviews for organization-defined information flows under organization-defined conditions.','AC-04(09)','N/A','Determine if human reviews are used for [AC-04(09)_ODP[01]; information flows requiring the use of human reviews are defined] under [AC-04(09)_ODP[02]; conditions under which the use of human reviews for information flows are to be enforced are defined].'),
('002199','draft','2013-06-24','DISA FSO','policy','Defines the conditions that provides the capability for privileged administrators to enable and disable organization-defined security policy filters.','AC-04(10)','N/A','Determine if: - capability is provided for privileged administrators to enable and disable [AC-04(10)_ODP[01]; security policy filters that privileged administrators have the capability to enable and disable are defined] under [AC-04(10)_ODP[03]; conditions under which privileged administrators have the capability to enable and disable security policy filters are defined]. - capability is provided for privileged administrators to enable and disable [AC-04(10)_ODP[02]; privacy policy filters that privileged administrators have the capability to enable and disable are defined] under [AC-04(10)_ODP[04]; conditions under which privileged administrators have the capability to enable and disable privacy policy filters are defined].'),
('002200','draft','2013-06-24','DISA FSO','policy','Defines the data type identifiers to be used to validate data being transferred between different security domains.','AC-04(12)','N/A','Determine if when transferring information between different security domains, [AC-04(12)_ODP; data type identifiers to be used to validate data essential for information flow decisions are defined] are used to validate data essential for information flow decisions.'),
('002201','draft','2013-06-24','DISA FSO','technical','When transferring information between different security domains, use organization-defined data type identifiers to validate data essential for information flow decisions.','AC-04(12)','N/A','Determine if when transferring information between different security domains, [AC-04(12)_ODP; data type identifiers to be used to validate data essential for information flow decisions are defined] are used to validate data essential for information flow decisions.'),
('002202','draft','2013-06-24','DISA FSO','policy','Defines the policy-relevant subcomponents into which information being transferred between different security domains is to be decomposed for submission to policy enforcement mechanisms.','AC-04(13)','N/A','Determine if when transferring information between different security domains, information is decomposed into [AC-04(13)_ODP; policy-relevant subcomponents into which to decompose information for submission to policy enforcement mechanisms are defined] for submission to policy enforcement mechanisms.'),
('002203','draft','2013-06-24','DISA FSO ','policy','Defines the unsanctioned information when transferring information between different security domains.','AC-04(15)','N/A','Determine if: - when transferring information between different security domains, information is examined for the presence of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[02]; security policy that requires the transfer of unsanctioned information between different security domains to be prohibited is defined (if selected)]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[03]; privacy policy that requires the transfer of organization-defined unsanctioned information between different security domains to be prohibited is defined (if selected)].'),
('002204','draft','2013-06-24','DISA FSO ','policy','Defines the security or privacy policy which prohibits the transfer of unsanctioned information between different security domains.','AC-04(15)','N/A','Determine if: - when transferring information between different security domains, information is examined for the presence of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[02]; security policy that requires the transfer of unsanctioned information between different security domains to be prohibited is defined (if selected)]. - when transferring information between different security domains, transfer of [AC-04(15)_ODP[01]; unsanctioned information to be detected is defined] is prohibited in accordance with the [AC-04(15)_ODP[03]; privacy policy that requires the transfer of organization-defined unsanctioned information between different security domains to be prohibited is defined (if selected)].'),
('002205','draft','2013-06-24','DISA FSO ','technical','Uniquely identify and authenticate source by organization, system, application, service, and/or individual for information transfer.','AC-04(17)','N/A','Determine if source and destination points are uniquely identified and authenticated by [AC-04(17)_ODP; one or more of the following PARAMETER VALUES is/are selected: {organization, system, application, service, individual}] for information transfer.'),
('002207','draft','2013-06-24','DISA FSO ','technical','Uniquely identify and authenticate destination points by organization, system, application, service, and/or individual for information transfer.','AC-04(17)','N/A','Determine if source and destination points are uniquely identified and authenticated by [AC-04(17)_ODP; one or more of the following PARAMETER VALUES is/are selected: {organization, system, application, service, individual}] for information transfer.'),
('002211','draft','2013-06-24','DISA FSO ','technical','When transferring information between different security domains, implement organization-defined security or privacy filters on metadata.','AC-04(19)','N/A','Determine if: - when transferring information between different security domains, [AC-04(19)_ODP[01]; security policy filters to be implemented on metadata are defined (if selected)] are implemented on metadata. - when transferring information between different security domains, [AC-04(19)_ODP[02]; privacy policy filters to be implemented on metadata are defined (if selected)] are implemented on metadata.'),
('002212','draft','2013-06-24','DISA FSO ','policy','Defines the solutions in approved configurations to be employed to control the flow of organization-defined information across security domains.','AC-04(20)','N/A','Determine if [AC-04(20)_ODP[01]; solutions in approved configurations to control the flow of information across security domains are defined] are employed to control the flow of [AC-04(20)_ODP[02]; information to be controlled when it flows across security domains is defined] across security domains.'),
('002213','draft','2013-06-24','DISA FSO','policy','Defines the information to be subjected to flow control across security domains.','AC-04(20)','N/A','Determine if [AC-04(20)_ODP[01]; solutions in approved configurations to control the flow of information across security domains are defined] are employed to control the flow of [AC-04(20)_ODP[02]; information to be controlled when it flows across security domains is defined] across security domains.'),
('002214','draft','2013-06-24','DISA FSO ','policy','Employ organization-defined solutions in approved configurations to control the flow of organization-defined information across security domains.','AC-04(20)','N/A','Determine if [AC-04(20)_ODP[01]; solutions in approved configurations to control the flow of information across security domains are defined] are employed to control the flow of [AC-04(20)_ODP[02]; information to be controlled when it flows across security domains is defined] across security domains.'),
('002215','draft','2013-06-24','DISA FSO','policy','Defines the mechanisms and/or techniques to be used to logically or physically separate information flows.','AC-04(21)','N/A','Determine if: - information flows are separated logically using [AC-04(21)_ODP[01]; mechanisms and/or techniques used to logically separate information flows are defined (if selected)] to accomplish [AC-04(21)_ODP[03]; required separations by types of information are defined]. - information flows are separated physically using [AC-04(21)_ODP[02]; mechanisms and/or techniques used to physically separate information flows are defined (if selected)] to accomplish [AC-04(21)_ODP[03]; required separations by types of information are defined].'),
('002216','draft','2013-06-24','DISA FSO','policy','Defines the types of information required to accomplish logical or physical separation of information flows.','AC-04(21)','N/A','Determine if: - information flows are separated logically using [AC-04(21)_ODP[01]; mechanisms and/or techniques used to logically separate information flows are defined (if selected)] to accomplish [AC-04(21)_ODP[03]; required separations by types of information are defined]. - information flows are separated physically using [AC-04(21)_ODP[02]; mechanisms and/or techniques used to physically separate information flows are defined (if selected)] to accomplish [AC-04(21)_ODP[03]; required separations by types of information are defined].'),
('002217','draft','2013-06-24','DISA FSO','policy','Separate information flows logically or physically using organization-defined mechanisms and/or techniques to accomplish organization-defined required separations by types of information.','AC-04(21)','N/A','Determine if: - information flows are separated logically using [AC-04(21)_ODP[01]; mechanisms and/or techniques used to logically separate information flows are defined (if selected)] to accomplish [AC-04(21)_ODP[03]; required separations by types of information are defined]. - information flows are separated physically using [AC-04(21)_ODP[02]; mechanisms and/or techniques used to physically separate information flows are defined (if selected)] to accomplish [AC-04(21)_ODP[03]; required separations by types of information are defined].'),
('002218','draft','2013-06-24','DISA FSO','technical','Provide access from a single device to computing platforms, applications, or data residing on multiple different security domains, while preventing any information flow between the different security domains.','AC-04(22)','N/A','Determine if access is provided from a single device to computing platforms, applications, or data that reside in multiple different security domains while preventing information flow between the different security domains.'),
('002219','draft','2013-06-24','DISA FSO','policy','Defines the duties of individuals requiring separation.','AC-05a.','N/A','Determine if [AC-05_ODP; duties of individuals requiring separation are defined] are identified and documented.'),
('002220','draft','2013-06-24','DISA FSO','policy','Define system access authorizations to support separation of duties.','AC-05a.','N/A','Determine if [AC-05_ODP; duties of individuals requiring separation are defined] are identified and documented.'),
('002221','draft','2013-06-24','DISA FSO','policy','Defines the security-relevant information for which access must be explicitly authorized.','AC-06(01)(b)','N/A','Determine if access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[05]; security-relevant information for authorized access is defined].'),
('002222','draft','2013-06-24','DISA FSO','policy','Authorize access for organization-defined individuals or roles to organization-defined security functions (deployed in hardware, software, and firmware).','AC-06(01)(a)','N/A','Determine if: - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[02]; security functions (deployed in hardware) for authorized access are defined]. - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[03]; security functions (deployed in software) for authorized access are defined]. - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[04]; security functions (deployed in firmware) for authorized access are defined].'),
('002223','draft','2013-06-24','DISA FSO','policy','Authorize access for organization-defined individuals or roles to organization-defined security-relevant information.','AC-06(01)(b)','N/A','Determine if access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[05]; security-relevant information for authorized access is defined].'),
('002224','draft','2013-06-24','DISA FSO','policy','Defines the compelling operational needs that must be met in order to be authorized network access to organization-defined privileged commands.','AC-06(03)','N/A','Determine if: - network access to [AC-06(03)_ODP[01]; privileged commands to which network access is to be authorized only for compelling operational needs are defined] is authorized only for [AC-06(03)_ODP[02]; compelling operational needs necessitating network access to privileged commands are defined]. - the rationale for authorizing network access to privileged commands is documented in the security plan for the system.'),
('002225','draft','2013-06-24','DISA FSO ','policy','Provide separate processing domains to enable finer-grained allocation of user privileges.','AC-06(04)','N/A','Determine if separate processing domains are provided to enable finer-grain allocation of user privileges.'),
('002226','draft','2013-06-24','DISA FSO','policy','Defines the personnel or roles to whom privileged accounts are to be restricted on the information system.','AC-06(05)','N/A','Determine if privileged accounts on the system are restricted to [AC-06(05)_ODP; personnel or roles to which privileged accounts on the system are to be restricted is/are defined].'),
('002227','draft','2013-06-24','DISA FSO','policy','Restrict privileged accounts on the system to organization-defined personnel or roles.','AC-06(05)','N/A','Determine if privileged accounts on the system are restricted to [AC-06(05)_ODP; personnel or roles to which privileged accounts on the system are to be restricted is/are defined].'),
('002228','draft','2013-06-24','DISA FSO','policy','Defines the frequency on which it conducts reviews of the privileges assigned to organization-defined roles or classes of users.','AC-06(07)(a)','N/A','Determine if privileges assigned to [AC-06(07)_ODP[02]; roles or classes of users to which privileges are assigned are defined] are reviewed [AC-06(07)_ODP[01]; the frequency at which to review the privileges assigned to roles or classes of users is defined] to validate the need for such privileges.'),
('002229','draft','2013-06-24','DISA FSO','policy','Defines the roles or classes of users that are to have their privileges reviewed on an organization-defined frequency.','AC-06(07)(a)','N/A','Determine if privileges assigned to [AC-06(07)_ODP[02]; roles or classes of users to which privileges are assigned are defined] are reviewed [AC-06(07)_ODP[01]; the frequency at which to review the privileges assigned to roles or classes of users is defined] to validate the need for such privileges.'),
('002230','draft','2013-06-24','DISA FSO','policy','Review, on an organization-defined frequency, the privileges assigned to organization-defined roles or classes of users to validate the need for such privileges.','AC-06(07)(a)','N/A','Determine if privileges assigned to [AC-06(07)_ODP[02]; roles or classes of users to which privileges are assigned are defined] are reviewed [AC-06(07)_ODP[01]; the frequency at which to review the privileges assigned to roles or classes of users is defined] to validate the need for such privileges.'),
('002231','draft','2013-06-24','DISA FSO','policy','Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.','AC-06(07)(b)','N/A','Determine if privileges are reassigned or removed, if necessary, to correctly reflect organizational mission and business needs.'),
('002232','draft','2013-06-24','DISA FSO','policy','Defines the software that is prevented from executing at a higher privilege than users executing the software.','AC-06(08)','N/A','Determine if [AC-06(08)_ODP; software to be prevented from executing at higher privilege levels than users executing the software is defined] is prevented from executing at higher privilege levels than users executing the software.'),
('002233','draft','2013-06-24','DISA FSO','technical','Prevent the organization-defined software from executing at higher privilege levels than users executing the software.','AC-06(08)','N/A','Determine if [AC-06(08)_ODP; software to be prevented from executing at higher privilege levels than users executing the software is defined] is prevented from executing at higher privilege levels than users executing the software.'),
('002234','draft','2013-06-24','DISA FSO','technical','Log the execution of privileged functions.','AC-06(09)','N/A','Determine if the execution of privileged functions is logged.'),
('002235','draft','2013-06-24','DISA FSO','technical','Prevent non-privileged users from executing privileged functions.','AC-06(10)','N/A','Determine if non-privileged users are prevented from executing privileged functions.'),
('002236','draft','2013-06-24','DISA FSO','policy','Defines the time period the information system will automatically lock the account or node when the maximum number of unsuccessful logon attempts is exceeded.','AC-07b.','N/A','Determine if automatically [AC-07_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {lock the account or node for [AC-07_ODP[04]; time period for an account or node to be locked is defined (if selected);]; lock the account or node until released by an administrator; delay next logon prompt per [AC-07_ODP[05]; delay algorithm for the next logon prompt is defined (if selected)]; notify system administrator; take other [AC-07_ODP[06]; other action to be taken when the maximum number of unsuccessful attempts is exceeded is defined (if selected)]]]] when the maximum number of unsuccessful attempts is exceeded.'),
('002237','draft','2013-06-24','DISA FSO','policy','Defines the delay algorithm to delay the next logon prompt when the maximum number of unsuccessful logon attempts is exceeded.','AC-07b.','N/A','Determine if automatically [AC-07_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {lock the account or node for [AC-07_ODP[04]; time period for an account or node to be locked is defined (if selected);]; lock the account or node until released by an administrator; delay next logon prompt per [AC-07_ODP[05]; delay algorithm for the next logon prompt is defined (if selected)]; notify system administrator; take other [AC-07_ODP[06]; other action to be taken when the maximum number of unsuccessful attempts is exceeded is defined (if selected)]]]] when the maximum number of unsuccessful attempts is exceeded.'),
('002238','draft','2013-06-24','DISA FSO','technical','Automatically lock the account or node for either an organization-defined time period, until the locked account or node is released by an administrator, or delays the next logon prompt according to the organization-defined delay algorithm when the maximum number of unsuccessful logon attempts is exceeded.','AC-07b.','N/A','Determine if automatically [AC-07_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {lock the account or node for [AC-07_ODP[04]; time period for an account or node to be locked is defined (if selected);]; lock the account or node until released by an administrator; delay next logon prompt per [AC-07_ODP[05]; delay algorithm for the next logon prompt is defined (if selected)]; notify system administrator; take other [AC-07_ODP[06]; other action to be taken when the maximum number of unsuccessful attempts is exceeded is defined (if selected)]]]] when the maximum number of unsuccessful attempts is exceeded.'),
('002239','draft','2013-06-24','DISA FSO','policy','Defines the mobile devices that are to be purged or wiped after an organization-defined number of consecutive, unsuccessful device logon attempts.','AC-07(02)','N/A','Determine if information is purged or wiped from [AC-07(02)_ODP[01]; mobile devices to be purged or wiped of information are defined] based on [AC-07(02)_ODP[02]; purging or wiping requirements and techniques to be used when mobile devices are purged or wiped of information are defined] after [AC-07(02)_ODP[03]; the number of consecutive, unsuccessful logon attempts before the information is purged or wiped from mobile devices is defined] consecutive, unsuccessful device logon attempts.'),
('002240','draft','2013-06-24','DISA FSO','policy','Defines the purging or wiping requirements and techniques to be used on organization-defined mobile devices after an organization-defined number of consecutive, unsuccessful device logon attempts.','AC-07(02)','N/A','Determine if information is purged or wiped from [AC-07(02)_ODP[01]; mobile devices to be purged or wiped of information are defined] based on [AC-07(02)_ODP[02]; purging or wiping requirements and techniques to be used when mobile devices are purged or wiped of information are defined] after [AC-07(02)_ODP[03]; the number of consecutive, unsuccessful logon attempts before the information is purged or wiped from mobile devices is defined] consecutive, unsuccessful device logon attempts.'),
('002241','draft','2013-06-24','DISA FSO','policy','Defines the number of consecutive, unsuccessful device logon attempts after which the organization-defined mobile devices will be purged or wiped.','AC-07(02)','N/A','Determine if information is purged or wiped from [AC-07(02)_ODP[01]; mobile devices to be purged or wiped of information are defined] based on [AC-07(02)_ODP[02]; purging or wiping requirements and techniques to be used when mobile devices are purged or wiped of information are defined] after [AC-07(02)_ODP[03]; the number of consecutive, unsuccessful logon attempts before the information is purged or wiped from mobile devices is defined] consecutive, unsuccessful device logon attempts.'),
('002242','draft','2013-06-24','DISA FSO','technical','Purge or wipe information from organization-defined mobile devices based on organization-defined purging or wiping requirements and techniques after an organization-defined number of consecutive, unsuccessful device logon attempts.','AC-07(02)','N/A','Determine if information is purged or wiped from [AC-07(02)_ODP[01]; mobile devices to be purged or wiped of information are defined] based on [AC-07(02)_ODP[02]; purging or wiping requirements and techniques to be used when mobile devices are purged or wiped of information are defined] after [AC-07(02)_ODP[03]; the number of consecutive, unsuccessful logon attempts before the information is purged or wiped from mobile devices is defined] consecutive, unsuccessful device logon attempts.'),
('002243','draft','2013-06-24','DISA FSO','policy','Organization-defined system use notification message or banner is to state that users are accessing a U.S. Government system.','AC-08a.01','N/A','Determine if the system use notification states that users are accessing a U.S. Government system.'),
('002244','draft','2013-06-24','DISA FSO','policy','Organization-defined system use notification message or banner is to state that system usage may be monitored, recorded, and subject to audit.','AC-08a.02','N/A','Determine if the system use notification states that system usage may be monitored, recorded, and subject to audit.'),
('002245','draft','2013-06-24','DISA FSO','policy','Organization-defined system use notification message or banner is to state that unauthorized use of the system is prohibited and subject to criminal and civil penalties.','AC-08a.03','N/A','Determine if the system use notification states that unauthorized use of the system is prohibited and subject to criminal and civil penalties.'),
('002246','draft','2013-06-24','DISA FSO','policy','Organization-defined system use notification message or banner is to state that use of the system indicates consent to monitoring and recording.','AC-08a.04','N/A','Determine if the system use notification states that use of the system indicates consent to monitoring and recording.'),
('002247','draft','2013-06-24','DISA FSO','policy','Defines the use notification message or banner the system displays to users before granting access to the system.','AC-08a.','N/A','Determine if [AC-08_ODP[01]; system use notification message or banner to be displayed by the system to users before granting access to the system is defined] is displayed to users before granting access to the system that provides privacy and security notices consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('002248','draft','2013-06-24','DISA FSO','policy','Defines the conditions of use which are to be displayed to users of the system before granting further access.','AC-08c.01','N/A','Determine if for publicly accessible systems, system use information [AC-08_ODP[02]; conditions for system use to be displayed by the system before granting further access are defined] is displayed before granting further access to the publicly accessible system.'),
('002249','draft','2013-06-24','DISA FSO','policy','Defines the additional information to be included in the notification to the user upon successful logon.','AC-09(04)','N/A','Determine if the user is notified, upon successful logon, of [AC-09(04)_ODP; additional information about which to notify the user is defined].'),
('002250','draft','2013-06-24','DISA FSO','technical','Notify the user, upon successful logon, of the following additional information: organization-defined additional information.','AC-09(04)','N/A','Determine if the user is notified, upon successful logon, of [AC-09(04)_ODP; additional information about which to notify the user is defined].'),
('002252','draft','2013-06-24','DISA FSO','policy','Defines the accounts and/or account types for which will limit the number of concurrent sessions.','AC-10','N/A','Determine if the number of concurrent sessions for each [AC-10_ODP[01]; accounts and/or account types for which to limit the number of concurrent sessions is defined] is limited to [AC-10_ODP[02]; the number of concurrent sessions to be allowed for each account and/or account type is defined].'),
('002256','draft','2013-06-24','DISA FSO','policy','Defines security attributes having organization-defined types of security attribute values which are associated with information in storage.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002257','draft','2013-06-24','DISA FSO','policy','Defines security attributes having organization-defined types of security attribute values which are associated with information in process.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002258','draft','2013-06-24','DISA FSO','policy','Defines security attributes, having organization-defined types of security attribute values, which are associated with information in transmission.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002259','draft','2013-06-24','DISA FSO','policy','Defines security attribute values associated with organization-defined types of security attributes for information in storage.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002260','draft','2013-06-24','DISA FSO','policy','Defines security attribute values associated with organization-defined types of security attributes for information in process.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002261','draft','2013-06-24','DISA FSO','policy','Defines security attribute values associated with organization-defined types of security attributes for information in transmission.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002262','draft','2013-06-24','DISA FSO','technical','Provide the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in storage.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002263','draft','2013-06-24','DISA FSO','technical','Provide the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in process.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002264','draft','2013-06-24','DISA FSO','technical','Provide the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('002265','draft','2013-06-24','DISA FSO','policy','Ensure that the attribute associations are made and retained with the information.','AC-16b.','N/A','Determine if: - attribute associations are made. - attribute associations are retained with the information.'),
('002266','draft','2013-06-24','DISA FSO','policy','Ensure that the security attribute associations are retained with the information.','AC-16b.','N/A','Determine if: - attribute associations are made. - attribute associations are retained with the information.'),
('002267','draft','2013-06-24','DISA FSO','policy','Defines the security attributes that are permitted for organization-defined systems.','AC-16c.','N/A','Determine if: - the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for [AC-16_ODP[05]; systems for which permitted security attributes are to be established are defined]: [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined]. - the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for [AC-16_ODP[06]; systems for which permitted privacy attributes are to be established are defined]: [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined].'),
('002268','draft','2013-06-24','DISA FSO','policy','Defines the systems for which permitted organization-defined attributes are to be established.','AC-16c.','N/A','Determine if: - the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for [AC-16_ODP[05]; systems for which permitted security attributes are to be established are defined]: [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined]. - the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for [AC-16_ODP[06]; systems for which permitted privacy attributes are to be established are defined]: [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined].'),
('002269','draft','2013-06-24','DISA FSO','policy','Establish the following permitted organization-defined security attributes in AC-16a for organization-defined systems.','AC-16c.','N/A','Determine if: - the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for [AC-16_ODP[05]; systems for which permitted security attributes are to be established are defined]: [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined]. - the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for [AC-16_ODP[06]; systems for which permitted privacy attributes are to be established are defined]: [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined].'),
('002270','draft','2013-06-24','DISA FSO','policy','Defines the attribute values or ranges permitted for each of the established security attributes.','AC-16d.','N/A','Determine if the following permitted attribute values or ranges for each of the established attributes are determined: [AC-16_ODP[09]; attribute values or ranges for established attributes are defined].'),
('002271','draft','2013-06-24','DISA FSO','policy','Determine organization-defined attribute values or ranges for each of the established attributes.','AC-16d.','N/A','Determine if the following permitted attribute values or ranges for each of the established attributes are determined: [AC-16_ODP[09]; attribute values or ranges for established attributes are defined].'),
('002272','draft','2013-06-24','DISA FSO','technical','Dynamically associate security attributes with organization-defined objects in accordance with organization-defined security policies as information is created and combined.',NULL,'N/A',NULL),
('002273','draft','2013-06-24','DISA FSO','policy','Defines the security policies to adhere to when dynamically associating security attributes with organization-defined subjects and objects.',NULL,'N/A',NULL),
('002274','draft','2013-06-24','DISA FSO','policy','Defines the subjects with which the system is to dynamically associate security attributes as information is created and combined.',NULL,'N/A',NULL),
('002275','draft','2013-06-24','DISA FSO','policy','Defines the objects with which the system is to dynamically associate security attributes as information is created and combined.',NULL,'N/A',NULL),
('002277','draft','2013-06-24','DISA FSO','technical','Provides authorized individuals (or processes acting on behalf of individuals) the capability to define the value of associated security attributes.','AC-16(02)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated security attributes. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated privacy attributes.'),
('002278','draft','2013-06-24','DISA FSO','policy','Defines the security attributes for which the association and integrity to organization-defined subjects and objects is maintained.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002279','draft','2013-06-24','DISA FSO','policy','Defines the subjects for which the association and integrity of organization-defined security attributes is maintained.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002280','draft','2013-06-24','DISA FSO','policy','Defines the objects for which the association and integrity of organization-defined security attributes is maintained.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002281','draft','2013-06-24','DISA FSO','technical','Maintain the association of organization-defined security attributes to organization-defined subjects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002282','draft','2013-06-24','DISA FSO','technical','Maintain the association of organization-defined security attributes to organization-defined objects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002283','draft','2013-06-24','DISA FSO','technical','Maintain the integrity of organization-defined security attributes associated with organization-defined subjects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002284','draft','2013-06-24','DISA FSO','technical','Maintain the integrity of organization-defined security attributes associated with organization-defined objects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('002286','draft','2013-06-24','DISA FSO','policy','Defines the subjects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('002287','draft','2013-06-24','DISA FSO','policy','Defines the objects with which organization-defined security attributes may be associated by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('002288','draft','2013-06-24','DISA FSO','policy','Defines the security attributes authorized individuals (or processes acting on behalf of individuals) are permitted to associate with organization-defined subjects and objects.','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('002289','draft','2013-06-24','DISA FSO','technical','Provide the capability to associate organization-defined security attributes with organization-defined subjects by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('002290','draft','2013-06-24','DISA FSO','technical','Provide the capability to associate organization-defined security attributes with organization-defined objects by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('002291','draft','2013-06-24','DISA FSO','policy','Defines the security policies to be followed by personnel when associating organization-defined security attributes with organization-defined subjects and objects.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002292','draft','2013-06-24','DISA FSO','policy','Defines the security attributes which are to be associated with organization-defined subjects and objects.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002293','draft','2013-06-24','DISA FSO','policy','Defines the subjects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002294','draft','2013-06-24','DISA FSO','policy','Defines the objects to be associated, and that association maintained, with organization-defined security attributes in accordance with organization-defined security policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002295','draft','2013-06-24','DISA FSO','policy','Require personnel to associate organization-defined security attributes with organization-defined subjects in accordance with organization-defined security policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002296','draft','2013-06-24','DISA FSO','policy','Require personnel to associate organization-defined security attributes with organization-defined objects in accordance with organization-defined security policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002297','draft','2013-06-24','DISA FSO','policy','Require personnel to maintain the association of organization-defined security attributes with organization-defined subjects in accordance with organization-defined security policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002298','draft','2013-06-24','DISA FSO','policy','Require personnel to maintain the association of organization-defined security attributes with organization-defined objects in accordance with organization-defined security policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('002299','draft','2013-06-24','DISA FSO','policy','Provide a consistent interpretation of security attributes transmitted between distributed system components.','AC-16(07)','N/A','Determine if: - a consistent interpretation of security attributes transmitted between distributed system components is provided. - Determine if a consistent interpretation of privacy attributes transmitted between distributed system components is provided.'),
('002300','draft','2013-06-24','DISA FSO','policy','Defines the techniques and technologies to be implemented when associating security attributes with information.','AC-16(08)','N/A','Determine if: - [AC-16(08)_ODP[01]; techniques and technologies to be implemented in associating security attributes to information are defined] are implemented in associating security attributes to information. - [AC-16(08)_ODP[02]; techniques and technologies to be implemented in associating privacy attributes to information are defined] are implemented in associating privacy attributes to information.'),
('002301','draft','2013-06-24','DISA FSO','policy','Defines the level of assurance to be provided when implementing organization-defined techniques and technologies in associating security attributes to information.','AC-16(08)','N/A','Determine if: - [AC-16(08)_ODP[01]; techniques and technologies to be implemented in associating security attributes to information are defined] are implemented in associating security attributes to information. - [AC-16(08)_ODP[02]; techniques and technologies to be implemented in associating privacy attributes to information are defined] are implemented in associating privacy attributes to information.'),
('002302','draft','2013-06-24','DISA FSO','technical','Implement organization-defined techniques and technologies with an organization-defined level of assurance in associating security attributes to information.','AC-16(08)','N/A','Determine if: - [AC-16(08)_ODP[01]; techniques and technologies to be implemented in associating security attributes to information are defined] are implemented in associating security attributes to information. - [AC-16(08)_ODP[02]; techniques and technologies to be implemented in associating privacy attributes to information are defined] are implemented in associating privacy attributes to information.'),
('002303','draft','2013-06-24','DISA FSO ','policy','Defines the techniques or procedures to be employed to validate re-grading mechanisms.','AC-16(09)','N/A','Determine if: - security attributes associated with information are changed only via regrading mechanisms validated using [AC-16(09)_ODP[01]; techniques or procedures used to validate regrading mechanisms for security attributes are defined]. - privacy attributes associated with information are changed only via regrading mechanisms validated using [AC-16(09)_ODP[02]; techniques or procedures used to validate regrading mechanisms for privacy attributes are defined].'),
('002304','draft','2013-06-24','DISA FSO','policy','Change security attributes associated with information are reassigned only via re-grading mechanisms validated using organization-defined techniques or procedures.','AC-16(09)','N/A','Determine if: - security attributes associated with information are changed only via regrading mechanisms validated using [AC-16(09)_ODP[01]; techniques or procedures used to validate regrading mechanisms for security attributes are defined]. - privacy attributes associated with information are changed only via regrading mechanisms validated using [AC-16(09)_ODP[02]; techniques or procedures used to validate regrading mechanisms for privacy attributes are defined].'),
('002306','draft','2013-06-24','DISA FSO','technical','Provide authorized individuals the capability to define or change the type of security attributes available for association with subjects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('002307','draft','2013-06-24','DISA FSO','technical','Provide authorized individuals the capability to define or change the value of security attributes available for association with subjects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('002308','draft','2013-06-24','DISA FSO','technical','Provide authorized individuals the capability to define or change the type of security attributes available for association with objects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('002309','draft','2013-06-24','DISA FSO','technical','Provide authorized individuals the capability to define or change the value of security attributes available for association with objects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('002310','draft','2013-06-24','DISA FSO','policy','Establish and document usage restrictions for each type of remote access allowed.','AC-17a.','N/A','Determine if: - usage restrictions are established and documented for each type of remote access allowed. - configuration/connection requirements are established and documented for each type of remote access allowed. - implementation guidance is established and documented for each type of remote access allowed.'),
('002311','draft','2013-06-24','DISA FSO','policy','Establish and document configuration/connection requirements for each type of remote access allowed.','AC-17a.','N/A','Determine if: - usage restrictions are established and documented for each type of remote access allowed. - configuration/connection requirements are established and documented for each type of remote access allowed. - implementation guidance is established and documented for each type of remote access allowed.'),
('002312','draft','2013-06-24','DISA FSO','policy','Establish and document implementation guidance for each type of remote access allowed.','AC-17a.','N/A','Determine if: - usage restrictions are established and documented for each type of remote access allowed. - configuration/connection requirements are established and documented for each type of remote access allowed. - implementation guidance is established and documented for each type of remote access allowed.'),
('002314','draft','2013-06-24','DISA FSO','technical','Employ automated mechanisms to control remote access methods.','AC-17(01)','N/A','Determine if: - automated mechanisms are employed to monitor remote access methods. - automated mechanisms are employed to control remote access methods.'),
('002316','draft','2013-06-24','DISA FSO','policy','Authorize access to security-relevant information via remote access only in a format that provides assessable evidence for organization-defined needs.','AC-17(04)(a)','N/A','Determine if: - the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence. - access to security-relevant information via remote access is authorized only in a format that provides assessable evidence. - the execution of privileged commands via remote access is authorized only for the following needs: [AC-17(04)_ODP[01]; needs requiring execution of privileged commands via remote access are defined]. - access to security-relevant information via remote access is authorized only for the following needs: [AC-17(04)_ODP[02]; needs requiring access to security-relevant information via remote access are defined].'),
('002317','draft','2013-06-24','DISA FSO','policy','Defines the needs for when the execution of privileged commands via remote access is to be authorized.','AC-17(04)(a)','N/A','Determine if: - the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence. - access to security-relevant information via remote access is authorized only in a format that provides assessable evidence. - the execution of privileged commands via remote access is authorized only for the following needs: [AC-17(04)_ODP[01]; needs requiring execution of privileged commands via remote access are defined]. - access to security-relevant information via remote access is authorized only for the following needs: [AC-17(04)_ODP[02]; needs requiring access to security-relevant information via remote access are defined].'),
('002318','draft','2013-06-24','DISA FSO','policy','Defines the needs for when access to security-relevant information via remote access is to be authorized.','AC-17(04)(a)','N/A','Determine if: - the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence. - access to security-relevant information via remote access is authorized only in a format that provides assessable evidence. - the execution of privileged commands via remote access is authorized only for the following needs: [AC-17(04)_ODP[01]; needs requiring execution of privileged commands via remote access are defined]. - access to security-relevant information via remote access is authorized only for the following needs: [AC-17(04)_ODP[02]; needs requiring access to security-relevant information via remote access are defined].'),
('002319','draft','2013-06-24','DISA FSO','policy','Document the rationale for authorization of the execution of privilege commands via remote access.','AC-17(04)(b)','N/A','Determine if the rationale for remote access is documented in the security plan for the system.'),
('002320','draft','2013-06-24','DISA FSO','policy','Document the rationale for authorization of access to security-relevant information via remote access.','AC-17(04)(b)','N/A','Determine if the rationale for remote access is documented in the security plan for the system.'),
('002321','draft','2013-06-24','DISA FSO','policy','Defines the time-period within which it disconnects or disables remote access to the system.','AC-17(09)','N/A','Determine if the capability to disconnect or disable remote access to the system within [AC-17(09)_ODP; the time period within which to disconnect or disable remote access to the system is defined] is provided.'),
('002322','draft','2013-06-24','DISA FSO','technical','Provide the capability to disconnect or disable remote access to the system within the organization-defined time period.','AC-17(09)','N/A','Determine if the capability to disconnect or disable remote access to the system within [AC-17(09)_ODP; the time period within which to disconnect or disable remote access to the system is defined] is provided.'),
('002323','draft','2013-06-24','DISA FSO','policy','Establish configuration requirements and connection requirements for wireless access.','AC-18a.','N/A','Determine if: - configuration requirements are established for each type of wireless access. - connection requirements are established for each type of wireless access. - implementation guidance is established for each type of wireless access.'),
('002324','draft','2013-06-24','DISA FSO','policy','Identify and explicitly authorize users allowed to independently configure wireless networking capabilities.','AC-18(04)','N/A','Determine if: - users allowed to independently configure wireless networking capabilities are identified. - users allowed to independently configure wireless networking capabilities are explicitly authorized.'),
('002325','draft','2013-06-24','DISA FSO','policy','Establish configuration requirements for organization-controlled mobile devices, to include when such devices are outside of controlled areas.','AC-19a.','N/A','Determine if: - configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area. - connection requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area. - implementation guidance is established for organization-controlled mobile devices, including when such devices are outside of the controlled area.'),
('002326','draft','2013-06-24','DISA FSO','policy','Establish connection requirements for organization-controlled mobile devices, to include when such devices are outside of controlled areas.','AC-19a.','N/A','Determine if: - configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area. - connection requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area. - implementation guidance is established for organization-controlled mobile devices, including when such devices are outside of the controlled area.'),
('002327','draft','2013-06-24','DISA FSO','policy','Defines the security policies which restrict the connection of classified mobile devices to classified systems.','AC-19(04)(c)','N/A','Determine if the connection of classified mobile devices to classified systems is restricted in accordance with [AC-19(04)_ODP[02]; security policies restricting the connection of classified mobile devices to classified systems are defined].'),
('002328','draft','2013-06-24','DISA FSO','policy','Restrict the connection of classified mobile devices to classified systems in accordance with organization-defined security policies.','AC-19(04)(c)','N/A','Determine if the connection of classified mobile devices to classified systems is restricted in accordance with [AC-19(04)_ODP[02]; security policies restricting the connection of classified mobile devices to classified systems are defined].'),
('002329','draft','2013-06-24','DISA FSO','policy','Defines the mobile devices that are to employ full-device or container encryption to protect the confidentiality and integrity of the information on the device.','AC-19(05)','N/A','Determine if [AC-19(05)_ODP[01]; one of the following PARAMETER VALUES is selected: {full-device encryption; container-based encryption}] is employed to protect the confidentiality and integrity of information on [AC-19(05)_ODP[02]; mobile devices on which to employ encryption are defined].'),
('002330','draft','2013-06-24','DISA FSO','policy','Employ full-device encryption or container encryption to protect the confidentiality of information on organization-defined mobile devices.','AC-19(05)','N/A','Determine if [AC-19(05)_ODP[01]; one of the following PARAMETER VALUES is selected: {full-device encryption; container-based encryption}] is employed to protect the confidentiality and integrity of information on [AC-19(05)_ODP[02]; mobile devices on which to employ encryption are defined].'),
('002331','draft','2013-06-24','DISA FSO','policy','Employ full-device encryption or container encryption to protect the integrity of information on organization-defined mobile devices.','AC-19(05)','N/A','Determine if [AC-19(05)_ODP[01]; one of the following PARAMETER VALUES is selected: {full-device encryption; container-based encryption}] is employed to protect the confidentiality and integrity of information on [AC-19(05)_ODP[02]; mobile devices on which to employ encryption are defined].'),
('002332','draft','2013-06-24','DISA FSO','policy','Establish organization-defined terms and conditions, and/or identify organization-defined controls asserted to be implemented on external systems, consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using the external systems.','AC-20a.02','N/A','Determine if [AC-20_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish [AC-20_ODP[02]; terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]; identify [AC-20_ODP[03]; controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]}]]] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using external systems (if applicable).'),
('002337','draft','2013-06-24','DISA FSO','policy','Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after the system retains approved system connection or processing agreements with the organizational entity hosting the external system.','AC-20(01)(b)','N/A','Determine if authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after retention of approved system connection or processing agreements with the organizational entity hosting the external system (if applicable).'),
('002338','draft','2013-06-24','DISA FSO','policy','Restrict the use of non-organizationally owned systems or system components to process, store, or transmit organizational information using organization-defined restrictions.','AC-20(03)','N/A','Determine if the use of non-organizationally owned systems or system components to process, store, or transmit organizational information is restricted using [AC-20(03)_ODP; restrictions on the use of non-organizationally owned systems or system components to process, store, or transmit organizational information are defined].'),
('002339','draft','2013-06-24','DISA FSO','policy','Defines the network accessible storage devices that are to be prohibited from being used in external systems.','AC-20(04)','N/A','Determine if the use of [AC-20(04)_ODP; network-accessible storage devices prohibited from use in external systems are defined] is prohibited in external systems.'),
('002340','draft','2013-06-24','DISA FSO','policy','Prohibit the use of organization-defined network accessible storage devices in external systems.','AC-20(04)','N/A','Determine if the use of [AC-20(04)_ODP; network-accessible storage devices prohibited from use in external systems are defined] is prohibited in external systems.'),
('002341','draft','2013-06-25','DISA FSO','policy','Defines the information sharing restrictions to be enforced when implementing information search and retrieval services.','AC-21(02)','N/A','Determine if information search and retrieval services that enforce [AC-21(02)_ODP; information-sharing restrictions to be enforced by information search and retrieval services are defined] are implemented.'),
('002342','draft','2013-06-25','DISA FSO','technical','Implement information search and retrieval services that enforce organization-defined information sharing restrictions.','AC-21(02)','N/A','Determine if information search and retrieval services that enforce [AC-21(02)_ODP; information-sharing restrictions to be enforced by information search and retrieval services are defined] are implemented.'),
('002343','draft','2013-06-25','DISA FSO','policy','Defines the data mining prevention techniques to be employed to protect organization-defined data storage objects against data mining.','AC-23','N/A','Determine if [AC-23_ODP[01]; data mining prevention and detection techniques are defined] are employed for [AC-23_ODP[02]; data storage objects to be protected against unauthorized data mining are defined] to detect and protect against unauthorized data mining.'),
('002344','draft','2013-06-25','DISA FSO','policy','Defines the data mining detection techniques to be employed to detect data mining attempts against organization-defined data storage objects.','AC-23','N/A','Determine if [AC-23_ODP[01]; data mining prevention and detection techniques are defined] are employed for [AC-23_ODP[02]; data storage objects to be protected against unauthorized data mining are defined] to detect and protect against unauthorized data mining.'),
('002345','draft','2013-06-25','DISA FSO','policy','Defines the data storage objects that are to be protected against data mining attempts.','AC-23','N/A','Determine if [AC-23_ODP[01]; data mining prevention and detection techniques are defined] are employed for [AC-23_ODP[02]; data storage objects to be protected against unauthorized data mining are defined] to detect and protect against unauthorized data mining.'),
('002346','draft','2013-06-25','DISA FSO','technical','Employ organization-defined data mining prevention techniques for organization-defined data storage objects to protect against unauthorized data mining.','AC-23','N/A','Determine if [AC-23_ODP[01]; data mining prevention and detection techniques are defined] are employed for [AC-23_ODP[02]; data storage objects to be protected against unauthorized data mining are defined] to detect and protect against unauthorized data mining.'),
('002347','draft','2013-06-25','DISA FSO','technical','Employ organization-defined data mining detection techniques for organization-defined data storage objects to detect data mining attempts.','AC-23','N/A','Determine if [AC-23_ODP[01]; data mining prevention and detection techniques are defined] are employed for [AC-23_ODP[02]; data storage objects to be protected against unauthorized data mining are defined] to detect and protect against unauthorized data mining.'),
('002348','draft','2013-06-25','DISA FSO','policy','Defines the access control decisions that are to be applied to each access request prior to access enforcement.','AC-24','N/A','Determine if [AC-24_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish procedures; implement mechanisms}] are taken to ensure that [AC-24_ODP[02]; access control decisions applied to each access request prior to access enforcement are defined] are applied to each access request prior to access enforcement.'),
('002349','draft','2013-06-25','DISA FSO','policy','Establish procedures or implement mechanisms to ensure organization-defined access control decisions are applied to each access request prior to access enforcement.','AC-24','N/A','Determine if [AC-24_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish procedures; implement mechanisms}] are taken to ensure that [AC-24_ODP[02]; access control decisions applied to each access request prior to access enforcement are defined] are applied to each access request prior to access enforcement.'),
('002350','draft','2013-06-25','DISA FSO','policy','Defines the access authorization information that is to be transmitted using organization-defined security safeguards to organization-defined systems that enforce access control decisions.','AC-24(01)','N/A','Determine if [AC-24(01)_ODP[01]; access authorization information transmitted to systems that enforce access control decisions is defined] is transmitted using [AC-24(01)_ODP[02]; controls to be used when authorization information is transmitted to systems that enforce access control decisions are defined] to [AC-24(01)_ODP[03]; systems that enforce access control decisions are defined] that enforce access control decisions.'),
('002351','draft','2013-06-25','DISA FSO','policy','Defines the controls to be employed when transmitting organization-defined access authorization information to organization-defined systems that enforce access control decisions.','AC-24(01)','N/A','Determine if [AC-24(01)_ODP[01]; access authorization information transmitted to systems that enforce access control decisions is defined] is transmitted using [AC-24(01)_ODP[02]; controls to be used when authorization information is transmitted to systems that enforce access control decisions are defined] to [AC-24(01)_ODP[03]; systems that enforce access control decisions are defined] that enforce access control decisions.'),
('002352','draft','2013-06-25','DISA FSO','policy','Defines the systems that are to be recipients of organization-defined access authorization information using organization-defined security safeguards.','AC-24(01)','N/A','Determine if [AC-24(01)_ODP[01]; access authorization information transmitted to systems that enforce access control decisions is defined] is transmitted using [AC-24(01)_ODP[02]; controls to be used when authorization information is transmitted to systems that enforce access control decisions are defined] to [AC-24(01)_ODP[03]; systems that enforce access control decisions are defined] that enforce access control decisions.'),
('002353','draft','2013-06-25','DISA FSO','technical','Transmit organization-defined access authorization information using organization-defined controls to organization-defined systems that enforce access control decisions.','AC-24(01)','N/A','Determine if [AC-24(01)_ODP[01]; access authorization information transmitted to systems that enforce access control decisions is defined] is transmitted using [AC-24(01)_ODP[02]; controls to be used when authorization information is transmitted to systems that enforce access control decisions are defined] to [AC-24(01)_ODP[03]; systems that enforce access control decisions are defined] that enforce access control decisions.'),
('002354','draft','2013-06-25','DISA FSO','policy','Defines the security attributes, not to include the identity of the user or process acting on behalf of the user, to be used as the basis for enforcing access control decisions.','AC-24(02)','N/A','Determine if: - access control decisions are enforced based on [AC-24(02)_ODP[01]; security attributes that do not include the identity of the user or process acting on behalf of the user are defined (if selected)] that do not include the identity of the user or process acting on behalf of the user (if selected). - access control decisions are enforced based on [AC-24(02)_ODP[02]; privacy attributes that do not include the identity of the user or process acting on behalf of the user are defined (if selected)] that do not include the identity of the user or process acting on behalf of the user (if selected).'),
('002355','draft','2013-06-25','DISA FSO','technical','Enforce access control decisions based on organization-defined security or privacy attributes that do not include the identity of the user or process acting on behalf of the user.','AC-24(02)','N/A','Determine if: - access control decisions are enforced based on [AC-24(02)_ODP[01]; security attributes that do not include the identity of the user or process acting on behalf of the user are defined (if selected)] that do not include the identity of the user or process acting on behalf of the user (if selected). - access control decisions are enforced based on [AC-24(02)_ODP[02]; privacy attributes that do not include the identity of the user or process acting on behalf of the user are defined (if selected)] that do not include the identity of the user or process acting on behalf of the user (if selected).'),
('002356','draft','2013-06-25','DISA FSO','policy','Defines the access control policies to be implemented by the reference monitor.','AC-25','N/A','Determine if a reference monitor is implemented for [AC-25_ODP; access control policies for which a reference monitor is implemented are defined] that is tamper-proof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.'),
('002357','draft','2013-06-25','DISA FSO','technical','Implement a reference monitor for organization-defined access control policies that is tamperproof.','AC-25','N/A','Determine if a reference monitor is implemented for [AC-25_ODP; access control policies for which a reference monitor is implemented are defined] that is tamper-proof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.'),
('002358','draft','2013-06-25','DISA FSO','technical','Implement a reference monitor for organization-defined access control policies that is always invoked.','AC-25','N/A','Determine if a reference monitor is implemented for [AC-25_ODP; access control policies for which a reference monitor is implemented are defined] that is tamper-proof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.'),
('002359','draft','2013-06-25','DISA FSO','technical','Implement a reference monitor for organization-defined access control policies that is small enough to be subject to analysis and testing, the completeness of which can be assured.','AC-25','N/A','Determine if a reference monitor is implemented for [AC-25_ODP; access control policies for which a reference monitor is implemented are defined] that is tamper-proof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.'),
('002360','draft','2013-06-26','DISA FSO','policy','Defines the conditions or trigger events requiring session disconnect when automatically terminating a user session.','AC-12','N/A','Determine if a user session is automatically terminated after [AC-12_ODP; conditions or trigger events requiring session disconnect are defined].'),
('002361','draft','2013-06-26','DISA FSO','technical','Automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.','AC-12','N/A','Determine if a user session is automatically terminated after [AC-12_ODP; conditions or trigger events requiring session disconnect are defined].'),
('002362','draft','2013-06-26','DISA FSO','policy','Defines the information resources requiring authentication in order to gain access.','AC-12(01)','N/A','Determine if a logout capability is provided for user-initiated communications sessions whenever authentication is used to gain access to [AC-12(01)_ODP; information resources for which a logout capability for user-initiated communications sessions is required are defined].'),
('002363','draft','2013-06-26','DISA FSO','technical','Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to organization-defined information resources.','AC-12(01)','N/A','Determine if a logout capability is provided for user-initiated communications sessions whenever authentication is used to gain access to [AC-12(01)_ODP; information resources for which a logout capability for user-initiated communications sessions is required are defined].'),
('002364','draft','2013-06-26','DISA FSO','technical','Display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.','AC-12(02)','N/A','Determine if an explicit logout message is displayed to users indicating the termination of authenticated communication sessions.'),
('002368','draft','2013-07-01','DISA FSO','policy','Defines the personnel or roles to whom the organization-level; mission/business process-level; system-level risk assessment policy is disseminated.','RA-01a.','N/A','Determine if: - a risk assessment policy is developed and documented. - the risk assessment policy is disseminated to [RA-01_ODP[01; personnel or roles to whom the risk assessment policy is to be disseminated is/are defined].'),
('002369','draft','2013-07-01','DISA FSO','policy','Defines the personnel or roles to whom the risk assessment procedures are disseminated.','RA-01a.02','N/A','Determine if: - risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls are developed and documented. - the risk assessment procedures are disseminated to [RA-01_ODP[02]; personnel or roles to whom the risk assessment procedures are to be disseminated is/are defined].'),
('002370','draft','2013-07-01','DISA FSO','policy','Disseminate risk assessment results to organization-defined personnel or roles.','RA-03e.','N/A','Determine if risk assessment results are disseminated to [RA-03_ODP[04]; personnel or roles to whom risk assessment results are to be disseminated is/are defined].'),
('002371','draft','2013-07-01','DISA FSO','policy','Defines the personnel or roles to whom the risk assessment results will be disseminated.','RA-03e.','N/A','Determine if risk assessment results are disseminated to [RA-03_ODP[04]; personnel or roles to whom risk assessment results are to be disseminated is/are defined].'),
('002372','draft','2013-07-01','DISA FSO','policy','Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors.','RA-05(10)','N/A','Determine if the output from vulnerability scanning tools is correlated to determine the presence of multi-vulnerability and multi-hop attack vectors.'),
('002373','draft','2013-07-01','DISA FSO','policy','Define the breadth and depth of vulnerability scanning coverage (i.e., information system components scanned and vulnerabilities checked).','RA-05(03)','N/A','Determine if the breadth and depth of vulnerability scanning coverage are defined.'),
('002374','draft','2013-07-01','DISA FSO','policy','Defines the corrective actions if unintended information about the system is discovered.','RA-05(04)','N/A','Determine if: - information about the system is discoverable. - [RA-05(04)_ODP; corrective actions to be taken if information about the system is discoverable are defined] are taken when information about the system is confirmed as discoverable.'),
('002375','draft','2013-07-02','DISA FSO','policy','Take organization-defined corrective actions if information about the system is discovered.','RA-05(04)','N/A','Determine if: - information about the system is discoverable. - [RA-05(04)_ODP; corrective actions to be taken if information about the system is discoverable are defined] are taken when information about the system is confirmed as discoverable.'),
('002376','draft','2013-07-02','DISA FSO','policy','Defines the personnel or roles with whom the information obtained from the vulnerability monitoring process and control assessments will be shared.','RA-05e.','N/A','Determine if information obtained from the vulnerability monitoring process and control assessments is shared with [RA-05_ODP[04]; personnel or roles with whom information obtained from the vulnerability scanning process and control assessments is to be shared] to help eliminate similar vulnerabilities in other systems.'),
('002378','draft','2013-07-02','DISA FSO','policy','Defines the personnel or roles to be recipients of the organization-level; mission/business process-level; and/or system-level system and communications protection policy.','SC-01a.','N/A','Determine if: - a system and communications protection policy is developed and documented. - the system and communications protection policy is disseminated to [SC-01_ODP[01]; personnel or roles to whom the system and communications protection policy is to be disseminated is/are defined].'),
('002380','draft','2013-07-02','DISA FSO','policy','Defines the personnel or roles to be recipients of the procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','SC-01a.02','N/A','Determine if: - system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls are developed and documented. - the system and communications protection procedures are disseminated to [SC-01_ODP[02]; personnel or roles to whom the system and communications protection procedures are to be disseminated is/are defined].'),
('002381','draft','2013-07-02','DISA FSO','technical','Minimize the number of nonsecurity functions included within the isolation boundary containing security functions.','SC-03(03)','N/A','Determine if the number of non-security functions included within the isolation boundary containing security functions is minimized.'),
('002382','draft','2013-07-02','DISA FSO','technical','Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.','SC-03(04)','N/A','Determine if: - security functions are implemented as largely independent modules that maximize internal cohesiveness within modules. - security functions are implemented as largely independent modules that minimize coupling between modules.'),
('002383','draft','2013-07-02','DISA FSO','policy','Defines the procedures to be employed to prevent unauthorized information transfer via shared resources when system processing explicitly switches between different information classification levels or security categories.','SC-04(02)','N/A','Determine if unauthorized information transfer via shared resources is prevented in accordance with [SC-04(02)_ODP; procedures to prevent unauthorized information transfer via shared resources are defined] when system processing explicitly switches between different information classification levels or security categories.'),
('002384','draft','2013-07-02','DISA FSO','technical','Prevent unauthorized information transfer via shared resources in accordance with organization-defined procedures when system processing explicitly switches between different information classification levels or security categories.','SC-04(02)','N/A','Determine if unauthorized information transfer via shared resources is prevented in accordance with [SC-04(02)_ODP; procedures to prevent unauthorized information transfer via shared resources are defined] when system processing explicitly switches between different information classification levels or security categories.'),
('002385','draft','2013-07-02','DISA FSO','technical','Protect against or limit the effects of organization-defined types of denial-of-service events.','SC-05a.','N/A','Determine if the effects of [SC-05_ODP[01]; types of denial-of-service events to be protected against or limited are defined] are [SC-05_ODP[02]; one of the following PARAMETER VALUES is selected: {protect against; limit}].'),
('002387','draft','2013-07-02','DISA FSO','policy','Defines the denial of service attacks against other systems that the system is to restrict the ability of individuals to launch.','SC-05(01)','N/A','Determine if the ability of individuals to launch [SC-05(01)_ODP; denial-of-service attacks for which to restrict the ability of individuals to launch are defined] against other systems is restricted.'),
('002388','draft','2013-07-02','DISA FSO','policy','Defines the monitoring tools to be employed to detect indicators of denial-of-service attacks against the system.',NULL,'N/A',NULL),
('002389','draft','2013-07-02','DISA FSO','policy','Employ organization-defined monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system.',NULL,'N/A',NULL),
('002390','draft','2013-07-02','DISA FSO','policy','Defines the system resources to be monitored to determine if sufficient resources exist to prevent effective denial-of-service attacks.',NULL,'N/A',NULL),
('002391','draft','2013-07-02','DISA FSO','policy','Monitor organization-defined system resources to determine if sufficient resources exist to prevent effective denial-of-service attacks.',NULL,'N/A',NULL),
('002392','draft','2013-07-02','DISA FSO','policy','Defines the resources to be allocated to protect the availability of system resources.','SC-06','N/A','Determine if the availability of resources is protected by allocating [SC-06_ODP[01]; resources to be allocated to protect the availability of resources are defined] by [SC-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {priority; quota; [SC-06_ODP[03]; controls to protect the availability of resources are defined (if selected)]}].'),
('002393','draft','2013-07-02','DISA FSO','policy','Defines the controls to be employed to protect the availability of system resources.','SC-06','N/A','Determine if the availability of resources is protected by allocating [SC-06_ODP[01]; resources to be allocated to protect the availability of resources are defined] by [SC-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {priority; quota; [SC-06_ODP[03]; controls to protect the availability of resources are defined (if selected)]}].'),
('002394','draft','2013-07-02','DISA FSO','technical','Protect the availability of resources by allocating organization-defined resources based on priority, quota, and/or organization-defined controls.','SC-06','N/A','Determine if the availability of resources is protected by allocating [SC-06_ODP[01]; resources to be allocated to protect the availability of resources are defined] by [SC-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {priority; quota; [SC-06_ODP[03]; controls to protect the availability of resources are defined (if selected)]}].'),
('002395','draft','2013-07-02','DISA FSO','policy','Implement subnetworks for publicly accessible system components that are physically and/or logically separated from internal organizational networks.','SC-07b.','N/A','Determine if subnetworks for publicly accessible system components are [SC-07_ODP; one of the following PARAMETER VALUES is selected: {physically; logically}] separated from internal organizational networks.'),
('002396','draft','2013-07-02','DISA FSO','policy','Protect the confidentiality and integrity of the information being transmitted across each interface for each external telecommunication service.','SC-07(04)(c)','N/A','Determine if: - the confidentiality of the information being transmitted across each interface is protected. - the integrity of the information being transmitted across each interface is protected.'),
('002397','draft','2013-07-02','DISA FSO','technical','Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using organization-defined safeguards.','SC-07(07)','N/A','Determine if split tunneling is prevented for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using [SC-07(07)_ODP; safeguards to securely provision split tunneling are defined].'),
('002398','draft','2013-07-02','DISA FSO','policy','Detect outgoing communications traffic posing a threat to external systems.','SC-07(09)(a)','N/A','Determine if: - outgoing communications traffic posing a threat to external systems is detected. - outgoing communications traffic posing a threat to external systems is denied. '),
('002399','draft','2013-07-02','DISA FSO','policy','Deny outgoing communications traffic posing a threat to external systems.','SC-07(09)(a)','N/A','Determine if: - outgoing communications traffic posing a threat to external systems is detected. - outgoing communications traffic posing a threat to external systems is denied. '),
('002400','draft','2013-07-02','DISA FSO','technical','Audit the identity of internal users associated with denied outgoing communications traffic posing a threat to external systems.','SC-07(09)(b)','N/A','Determine if the identity of internal users associated with denied communications is audited.'),
('002401','draft','2013-07-02','DISA FSO','policy','Defines the authorized sources from which the system will allow incoming communications.','SC-07(11)','N/A','Determine if only incoming communications from [SC-07(11)_ODP[01]; authorized sources of incoming communications to be routed are defined] are allowed to be routed to [SC-07(11)_ODP[02]; authorized destinations to which incoming communications from authorized sources may be routed are defined].'),
('002402','draft','2013-07-02','DISA FSO','policy','Defines the authorized destinations for routing inbound communications.','SC-07(11)','N/A','Determine if only incoming communications from [SC-07(11)_ODP[01]; authorized sources of incoming communications to be routed are defined] are allowed to be routed to [SC-07(11)_ODP[02]; authorized destinations to which incoming communications from authorized sources may be routed are defined].'),
('002403','draft','2013-07-02','DISA FSO','technical','Only allow incoming communications from organization-defined authorized sources routed to organization-defined authorized destinations.','SC-07(11)','N/A','Determine if only incoming communications from [SC-07(11)_ODP[01]; authorized sources of incoming communications to be routed are defined] are allowed to be routed to [SC-07(11)_ODP[02]; authorized destinations to which incoming communications from authorized sources may be routed are defined].'),
('002404','draft','2013-07-02','DISA FSO','policy','Defines the host-based boundary protection mechanisms that are to be implemented at organization-defined system components.','SC-07(12)','N/A','Determine if [SC-07(12)_ODP[01]; host-based boundary protection mechanisms to be implemented are defined] are implemented at [SC-07(12)_ODP[02]; system components where host-based boundary protection mechanisms are to be implemented are defined].'),
('002405','draft','2013-07-02','DISA FSO','policy','Defines the system components at which organization-defined host-based boundary protection mechanisms will be implemented.','SC-07(12)','N/A','Determine if [SC-07(12)_ODP[01]; host-based boundary protection mechanisms to be implemented are defined] are implemented at [SC-07(12)_ODP[02]; system components where host-based boundary protection mechanisms are to be implemented are defined].'),
('002406','draft','2013-07-02','DISA FSO','policy','Implement organization-defined host-based boundary protection mechanisms at organization-defined system components.','SC-07(12)','N/A','Determine if [SC-07(12)_ODP[01]; host-based boundary protection mechanisms to be implemented are defined] are implemented at [SC-07(12)_ODP[02]; system components where host-based boundary protection mechanisms are to be implemented are defined].'),
('002407','draft','2013-07-02','DISA FSO','policy','Defines the managed interfaces at which protect against unauthorized physical connections.','SC-07(14)','N/A','Determine if [SC-07(14)_ODP; managed interfaces to be protected against unauthorized physical connections are defined] are protected against unauthorized physical connections.'),
('002408','draft','2013-07-02','DISA FSO','policy','Defines the communication clients that are independently configured by end users and external service providers which will block both inbound and outbound communications traffic.','SC-07(19)','N/A','Determine if: - inbound communications traffic is blocked between [SC-07(19)_ODP; communication clients that are independently configured by end users and external service providers are defined] that are independently configured by end users and external service providers. - outbound communications traffic is blocked between [SC-07(19)_ODP; communication clients that are independently configured by end users and external service providers are defined] that are independently configured by end users and external service providers.'),
('002409','draft','2013-07-02','DISA FSO','technical','Block inbound and outbound communications traffic between organization-defined communication clients that are independently configured by end users and external service providers.','SC-07(19)','N/A','Determine if: - inbound communications traffic is blocked between [SC-07(19)_ODP; communication clients that are independently configured by end users and external service providers are defined] that are independently configured by end users and external service providers. - outbound communications traffic is blocked between [SC-07(19)_ODP; communication clients that are independently configured by end users and external service providers are defined] that are independently configured by end users and external service providers.'),
('002410','draft','2013-07-02','DISA FSO','policy','Defines system components that are to be dynamically isolated from other system components.','SC-07(20)','N/A','Determine if the capability to dynamically isolate [SC-07(20)_ODP; system components to be dynamically isolated from other system components are defined] from other system components is provided.'),
('002411','draft','2013-07-02','DISA FSO','technical','Provide the capability to dynamically isolate organization-defined system components from other system components.','SC-07(20)','N/A','Determine if the capability to dynamically isolate [SC-07(20)_ODP; system components to be dynamically isolated from other system components are defined] from other system components is provided.'),
('002413','draft','2013-07-02','DISA FSO','policy','Defines the system components supporting organization-defined missions and/or business functions that are to be isolated using boundary protection mechanisms.','SC-07(21)','N/A','Determine if boundary protection mechanisms are employed to isolate [SC-07(21)_ODP[01]; system components to be isolated by boundary protection mechanisms are defined] supporting [SC-07(21)_ODP[02]; missions and/or business functions to be supported by system components isolated by boundary protection mechanisms are defined].'),
('002414','draft','2013-07-02','DISA FSO','policy','Defines the missions and/or business functions for which boundary protection mechanisms will be employed to isolate the supporting organization-defined system components.','SC-07(21)','N/A','Determine if boundary protection mechanisms are employed to isolate [SC-07(21)_ODP[01]; system components to be isolated by boundary protection mechanisms are defined] supporting [SC-07(21)_ODP[02]; missions and/or business functions to be supported by system components isolated by boundary protection mechanisms are defined].'),
('002415','draft','2013-07-02','DISA FSO','policy','Employ boundary protection mechanisms to isolate organization-defined system components supporting organization-defined missions and/or business functions.','SC-07(21)','N/A','Determine if boundary protection mechanisms are employed to isolate [SC-07(21)_ODP[01]; system components to be isolated by boundary protection mechanisms are defined] supporting [SC-07(21)_ODP[02]; missions and/or business functions to be supported by system components isolated by boundary protection mechanisms are defined].'),
('002416','draft','2013-07-02','DISA FSO','policy','Implement separate network addresses to connect to systems in different security domains.','SC-07(22)','N/A','Determine if separate network addresses are implemented to connect to systems in different security domains.'),
('002417','draft','2013-07-02','DISA FSO','technical','Disable feedback to senders on protocol format validation failure.','SC-07(23)','N/A','Determine if feedback to senders is disabled on protocol format validation failure.'),
('002418','draft','2013-07-02','DISA FSO','policy','Protect the confidentiality and/or integrity of transmitted information.','SC-08','N/A','Determine if the [SC-08_ODP; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] of transmitted information is/are protected.'),
('002420','draft','2013-07-02','DISA FSO','technical','Maintain the confidentiality and/or integrity of information during preparation for transmission.','SC-08(02)','N/A','Determine if: - information [SC-08(02)_ODP; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] is/are maintained during preparation for transmission. - information [SC-08(02)_ODP; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] is/are maintained during reception.'),
('002421','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission.','SC-08(01)','N/A','Determine if cryptographic mechanisms are implemented to [SC-08(01)_ODP; one or more of the following PARAMETER VALUES is/are selected: {prevent unauthorized disclosure of information; detect changes to information}] during transmission.'),
('002422','draft','2013-07-02','DISA FSO','technical','Maintain the confidentiality and/or integrity of information during reception.','SC-08(02)','N/A','Determine if: - information [SC-08(02)_ODP; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] is/are maintained during preparation for transmission. - information [SC-08(02)_ODP; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] is/are maintained during reception.'),
('002423','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to protect message externals unless otherwise protected by organization-defined alternative physical controls.','SC-08(03)','N/A','Determine if cryptographic mechanisms are implemented to protect message externals unless otherwise protected by [SC-08(03)_ODP; alternative physical controls to protect message externals are defined].'),
('002424','draft','2013-07-02','DISA FSO','policy','Defines the alternative physical controls to be employed when cryptographic mechanisms to conceal or randomize communication patterns are not implemented.','SC-08(04)','N/A','Determine if cryptographic mechanisms are implemented to conceal or randomize communication patterns unless otherwise protected by [SC-08(04)_ODP; alternative physical controls to protect against unauthorized disclosure of communication patterns are defined].'),
('002425','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by organization-defined alternative physical controls.','SC-08(04)','N/A','Determine if cryptographic mechanisms are implemented to conceal or randomize communication patterns unless otherwise protected by [SC-08(04)_ODP; alternative physical controls to protect against unauthorized disclosure of communication patterns are defined].'),
('002426','draft','2013-07-02','DISA FSO','technical','Provide a trusted communications path that is irrefutably distinguishable from other communications paths.','SC-11(01)(a)','N/A','Determine if a trusted communication path that is irrefutably distinguishable from other communication paths is provided.'),
('002427','draft','2013-07-02','DISA FSO','policy','Defines the alternative physical controls to be employed to protect message externals when cryptographic mechanisms are not implemented.','SC-08(03)','N/A','Determine if cryptographic mechanisms are implemented to protect message externals unless otherwise protected by [SC-08(03)_ODP; alternative physical controls to protect message externals are defined].'),
('002428','draft','2013-07-02','DISA FSO','policy','Defines the requirements for cryptographic key generation to be employed within the system.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002429','draft','2013-07-02','DISA FSO','policy','Defines the requirements for cryptographic key distribution to be employed within the system.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002430','draft','2013-07-02','DISA FSO','policy','Defines the requirements for cryptographic key storage to be employed within the system.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002431','draft','2013-07-02','DISA FSO','policy','Defines the requirements for cryptographic key access to be employed within the system.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002432','draft','2013-07-02','DISA FSO','policy','Defines the requirements for cryptographic key destruction to be employed within the system.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002433','draft','2013-07-02','DISA FSO','policy','Establish cryptographic keys when cryptography is employed within the system in accordance with organization-defined requirements for key generation.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002434','draft','2013-07-02','DISA FSO','policy','Establish cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key distribution.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002435','draft','2013-07-02','DISA FSO','policy','Establish cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key storage.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002436','draft','2013-07-02','DISA FSO','policy','Establish cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key access.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002437','draft','2013-07-02','DISA FSO','policy','Establish cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key destruction.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002438','draft','2013-07-02','DISA FSO','policy','Manage cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key generation.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002439','draft','2013-07-02','DISA FSO','policy','Manage cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key distribution.',NULL,'N/A',NULL),
('002440','draft','2013-07-02','DISA FSO','policy','Manage cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key storage.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002441','draft','2013-07-02','DISA FSO','policy','Manage cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key access.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002442','draft','2013-07-02','DISA FSO','policy','Manage cryptographic keys when cryptography employed within the system in accordance with organization-defined requirements for key destruction.','SC-12','N/A','Determine if: - cryptographic keys are established when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined]. - cryptographic keys are managed when cryptography is employed within the system in accordance with [SC-12_ODP; requirements for key generation, distribution, storage, access, and destruction are defined].'),
('002443','draft','2013-07-02','DISA FSO','policy','Produce symmetric cryptographic keys using NIST FIPS-validated or NSA-approved key management technology and processes.','SC-12(02)','N/A','Determine if: - symmetric cryptographic keys are produced using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes. - symmetric cryptographic keys are controlled using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes. - symmetric cryptographic keys are distributed using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes.'),
('002444','draft','2013-07-02','DISA FSO','policy','Control symmetric cryptographic keys using NIST FIPS-validated or NSA-approved key management technology and processes.','SC-12(02)','N/A','Determine if: - symmetric cryptographic keys are produced using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes. - symmetric cryptographic keys are controlled using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes. - symmetric cryptographic keys are distributed using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes.'),
('002445','draft','2013-07-02','DISA FSO','policy','Distribute symmetric cryptographic keys using NIST FIPS-validated or NSA-approved key management technology and processes.','SC-12(02)','N/A','Determine if: - symmetric cryptographic keys are produced using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes. - symmetric cryptographic keys are controlled using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes. - symmetric cryptographic keys are distributed using [SC-12(02)_ODP; one of the following PARAMETER VALUES is selected: {NIST FIPS-validated; NSA-approved}] key management technology and processes.'),
('002446','draft','2013-07-02','DISA FSO','policy','Produce asymmetric cryptographic keys using: NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; or certificates issued in accordance with organization-defined requirements.','SC-12(03)','N/A','Determine if: - asymmetric cryptographic keys are produced using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are controlled using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are distributed using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}].'),
('002447','draft','2013-07-02','DISA FSO','policy','Control asymmetric cryptographic keys using: NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; or certificates issued in accordance with organization-defined requirements.','SC-12(03)','N/A','Determine if: - asymmetric cryptographic keys are produced using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are controlled using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are distributed using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}].'),
('002448','draft','2013-07-02','DISA FSO','policy','Distribute asymmetric cryptographic keys using: NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; or certificates issued in accordance with organization-defined requirements.','SC-12(03)','N/A','Determine if: - asymmetric cryptographic keys are produced using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are controlled using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are distributed using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}].'),
('002449','draft','2013-07-02','DISA FSO','policy','Defines the cryptographic uses, and type of cryptography required for each use, to be implemented by the system.',NULL,'N/A',NULL),
('002450','draft','2013-07-02','DISA FSO','technical','Implement organization-defined types of cryptography for each specified cryptography use.','SC-13a.','N/A','Determine if [SC-13_ODP[01]; cryptographic uses are defined] are identified.'),
('002451','draft','2013-07-02','DISA FSO','policy','Defines the systems or system components from which collaborative computing devices and applications in organization-defined secure work areas are to be disabled or removed.','SC-15(03)','N/A','Determine if collaborative computing devices and applications are disabled or removed from [SC-15(03)_ODP[01]; systems or system components from which collaborative computing devices are to be disabled or removed are defined] in [SC-15(03)_ODP[02]; secure work areas where collaborative computing devices are to be disabled or removed from systems or system components are defined].'),
('002452','draft','2013-07-02','DISA FSO','policy','Defines the online meetings and teleconferences for which the system provides an explicit indication of current participants.','SC-15(04)','N/A','Determine if an explicit indication of current participants in [SC-15(04)_ODP; online meetings and teleconferences for which an explicit indication of current participants is to be provided are defined] is provided.'),
('002453','draft','2013-07-02','DISA FSO','technical','Provide an explicit indication of current participants in organization-defined online meetings and teleconferences.',NULL,'N/A',NULL),
('002454','draft','2013-07-02','DISA FSO','policy','Defines the security attributes to associate with the information being exchanged between systems and between system components.','SC-16','N/A','Determine if: - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between system components. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between system components.'),
('002455','draft','2013-07-02','DISA FSO','technical','Associate organization-defined security attributes with information exchanged between system components.','SC-16','N/A','Determine if: - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between system components. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between system components.'),
('002456','draft','2013-07-02','DISA FSO','policy','Defines the certificate policy employed to issue public key certificates.','SC-15(04)','N/A','Determine if an explicit indication of current participants in [SC-15(04)_ODP; online meetings and teleconferences for which an explicit indication of current participants is to be provided are defined] is provided.'),
('002457','draft','2013-07-02','DISA FSO','policy','Defines the corrective actions to be taken when organization-defined unacceptable mobile code is identified.','SC-18(01)','N/A','Determine if: - [SC-18(01)_ODP[01]; unacceptable mobile code to be identified is defined] is identified. - [SC-18(01)_ODP[02]; corrective actions to be taken when unacceptable mobile code is identified are defined] are taken if unacceptable mobile code is identified.'),
('002458','draft','2013-07-02','DISA FSO','policy','Defines what constitutes unacceptable mobile code by using corrective actions.','SC-18(01)','N/A','Determine if: - [SC-18(01)_ODP[01]; unacceptable mobile code to be identified is defined] is identified. - [SC-18(01)_ODP[02]; corrective actions to be taken when unacceptable mobile code is identified are defined] are taken if unacceptable mobile code is identified.'),
('002459','draft','2013-07-02','DISA FSO','policy','Defines the unacceptable mobile code to prevent download and execution.','SC-18(03)','N/A','Determine if: - the download of [SC-18(03)_ODP; unacceptable mobile code to be prevented from downloading and executing is defined] is prevented. - the execution of [SC-18(03)_ODP; unacceptable mobile code to be prevented from downloading and executing is defined] is prevented.'),
('002460','draft','2013-07-02','DISA FSO','technical','Enforce organization-defined actions prior to executing mobile code.','SC-18(04)','N/A','Determine if: - the automatic execution of mobile code in [SC-18(04)_ODP[01]; software applications in which the automatic execution of mobile code is to be prevented are defined] is prevented. - [SC-18(04)_ODP[02]; actions to be enforced by the system prior to executing mobile code are defined] are enforced prior to executing mobile code.'),
('002461','draft','2013-07-02','DISA FSO','policy','Allow execution of permitted mobile code only in confined virtual machine environments.','SC-18(05)','N/A','Determine if execution of permitted mobile code is allowed only in confined virtual machine environments.'),
('002462','draft','2013-07-02','DISA FSO','technical','Provide additional data integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries.','SC-20a.','N/A','Determine if: - additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries. - integrity verification artifacts are provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries.'),
('002463','draft','2013-07-02','DISA FSO','technical','Provide data origin artifacts for internal name/address resolution queries.','SC-20(02)','N/A','Determine if: - data origin artifacts are provided for internal name/address resolution queries. - integrity protection artifacts are provided for internal name/address resolution queries.'),
('002464','draft','2013-07-02','DISA FSO','technical','Provide data integrity protection artifacts for internal name/address resolution queries.','SC-20(02)','N/A','Determine if: - data origin artifacts are provided for internal name/address resolution queries. - integrity protection artifacts are provided for internal name/address resolution queries.'),
('002465','draft','2013-07-02','DISA FSO','technical','Request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.','SC-21','N/A','Determine if: - data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources. - data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.'),
('002466','draft','2013-07-02','DISA FSO','technical','Request data integrity verification on the name/address resolution responses the system receives from authoritative sources.','SC-21','N/A','Determine if: - data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources. - data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.'),
('002467','draft','2013-07-02','DISA FSO','technical','Perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.','SC-21','N/A','Determine if: - data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources. - data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.'),
('002468','draft','2013-07-02','DISA FSO','technical','Perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.','SC-21','N/A','Determine if: - data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources. - data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources. - data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.'),
('002469','draft','2013-07-02','DISA FSO','policy','Defines the certificate authorities allowed to be used for verification of the establishment of protected sessions.','SC-23(05)','N/A','Determine if only the use of [SC-23(05)_ODP; certificate authorities to be allowed for verification of the establishment of protected sessions are defined] for verification of the establishment of protected sessions is allowed.'),
('002470','draft','2013-07-02','DISA FSO','technical','Only allow the use of organization-defined certificate authorities for verification of the establishment of protected sessions.','SC-23(05)','N/A','Determine if only the use of [SC-23(05)_ODP; certificate authorities to be allowed for verification of the establishment of protected sessions are defined] for verification of the establishment of protected sessions is allowed.'),
('002471','draft','2013-07-02','DISA FSO','policy','Defines the system components, with minimal functionality and information storage, to be employed.','SC-25','N/A','Determine if: - minimal functionality for [SC-25_ODP; system components to be employed with minimal functionality and information storage are defined] is employed. - minimal information storage on [SC-25_ODP; system components to be employed with minimal functionality and information storage are defined] is allocated.'),
('002472','draft','2013-07-02','DISA FSO','policy','Defines the information at rest that is to be protected.','SC-28','N/A','Determine if the [SC-28_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {confidentiality; integrity}] of [SC-28_ODP[02]; information at rest requiring protection is defined] is/are protected.'),
('002473','draft','2013-07-02','DISA FSO','policy','Defines the information at rest for which cryptographic mechanisms will be implemented.','SC-28(01)','N/A','Determine if: - cryptographic mechanisms are implemented to prevent unauthorized disclosure of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02]; system components or media requiring cryptographic protection is/are defined]. - cryptographic mechanisms are implemented to prevent unauthorized modification of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02; system components or media requiring cryptographic protection is/are defined].'),
('002474','draft','2013-07-02','DISA FSO','policy','Defines the system components which require the implementation of cryptographic mechanisms to prevent unauthorized disclosure and modification of organization-defined information at rest.','SC-28(01)','N/A','Determine if: - cryptographic mechanisms are implemented to prevent unauthorized disclosure of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02]; system components or media requiring cryptographic protection is/are defined]. - cryptographic mechanisms are implemented to prevent unauthorized modification of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02; system components or media requiring cryptographic protection is/are defined].'),
('002475','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined system components.','SC-28(01)','N/A','Determine if: - cryptographic mechanisms are implemented to prevent unauthorized disclosure of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02]; system components or media requiring cryptographic protection is/are defined]. - cryptographic mechanisms are implemented to prevent unauthorized modification of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02; system components or media requiring cryptographic protection is/are defined].'),
('002476','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined system components.','SC-28(01)','N/A','Determine if: - cryptographic mechanisms are implemented to prevent unauthorized disclosure of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02]; system components or media requiring cryptographic protection is/are defined]. - cryptographic mechanisms are implemented to prevent unauthorized modification of [SC-28(01)_ODP[01]; information requiring cryptographic protection is defined] at rest on [SC-28(01)_ODP[02; system components or media requiring cryptographic protection is/are defined].'),
('002477','draft','2013-07-02','DISA FSO','policy','Defines the information to be removed from online storage and stored in an offline secure location.','SC-28(02)','N/A','Determine if: - [SC-28(02)_ODP; information to be removed from online storage and stored offline in a secure location is defined] is removed from online storage. - [SC-28(02)_ODP; information to be removed from online storage and stored offline in a secure location is defined] is stored offline in a secure location.'),
('002478','draft','2013-07-02','DISA FSO','policy','Remove organization-defined information from online storage.','SC-28(02)','N/A','Determine if: - [SC-28(02)_ODP; information to be removed from online storage and stored offline in a secure location is defined] is removed from online storage. - [SC-28(02)_ODP; information to be removed from online storage and stored offline in a secure location is defined] is stored offline in a secure location.'),
('002479','draft','2013-07-02','DISA FSO','policy','Store organization-defined information in an offline secure location.','SC-28(02)','N/A','Determine if: - [SC-28(02)_ODP; information to be removed from online storage and stored offline in a secure location is defined] is removed from online storage. - [SC-28(02)_ODP; information to be removed from online storage and stored offline in a secure location is defined] is stored offline in a secure location.'),
('002480','draft','2013-07-02','DISA FSO','policy','Defines the system components for which a diverse set of information technologies are to be employed.','SC-29','N/A','Determine if a diverse set of information technologies is employed for [SC-29_ODP; system components requiring a diverse set of information technologies to be employed in the implementation of the system are defined] in the implementation of the system.'),
('002481','draft','2013-07-02','DISA FSP','policy','Employ virtualization techniques to support the deployment of a diversity of applications that are changed per organization-defined frequency.','SC-29(01)','N/A','Determine if virtualization techniques are employed to support the deployment of a diverse range of operating systems and applications that are changed [SC-29(01)_ODP; the frequency at which to change the diversity of operating systems and applications deployed using virtualization techniques is defined].'),
('002482','draft','2013-07-02','DISA FSO','policy','Defines the concealment and misdirection techniques employed for organization-defined systems to confuse and mislead adversaries.','SC-30','N/A','Determine if [SC-30_ODP[01]; concealment and misdirection techniques to be employed to confuse and mislead adversaries potentially targeting systems are defined] are employed for [SC-30_ODP[02]; systems for which concealment and misdirection techniques are to be employed are defined] for [SC-30_ODP[03]; time periods to employ concealment and misdirection techniques for systems are defined] to confuse and mislead adversaries.'),
('002483','draft','2013-07-02','DISA FSO','policy','Defines the systems for which organization-defined concealment and misdirection techniques are to be employed.','SC-30','N/A','Determine if [SC-30_ODP[01]; concealment and misdirection techniques to be employed to confuse and mislead adversaries potentially targeting systems are defined] are employed for [SC-30_ODP[02]; systems for which concealment and misdirection techniques are to be employed are defined] for [SC-30_ODP[03]; time periods to employ concealment and misdirection techniques for systems are defined] to confuse and mislead adversaries.'),
('002484','draft','2013-07-02','DISA FSO','policy','Defines the time periods at which to employ organization-defined concealment and misdirection techniques on organization-defined systems.','SC-30','N/A','Determine if [SC-30_ODP[01]; concealment and misdirection techniques to be employed to confuse and mislead adversaries potentially targeting systems are defined] are employed for [SC-30_ODP[02]; systems for which concealment and misdirection techniques are to be employed are defined] for [SC-30_ODP[03]; time periods to employ concealment and misdirection techniques for systems are defined] to confuse and mislead adversaries.'),
('002485','draft','2013-07-02','DISA FSO','policy','Employ organization-defined concealment and misdirection techniques for organization-defined systems at organization-defined time periods to confuse and mislead adversaries.','SC-30','N/A','Determine if [SC-30_ODP[01]; concealment and misdirection techniques to be employed to confuse and mislead adversaries potentially targeting systems are defined] are employed for [SC-30_ODP[02]; systems for which concealment and misdirection techniques are to be employed are defined] for [SC-30_ODP[03]; time periods to employ concealment and misdirection techniques for systems are defined] to confuse and mislead adversaries.'),
('002486','draft','2013-07-02','DISA FSO','policy','Defines the techniques to be employed to introduce randomness into organizational operations and assets.','SC-30(02)','N/A','Determine if [SC-30(02)_ODP; techniques employed to introduce randomness into organizational operations and assets are defined] are employed to introduce randomness into organizational operations and assets.'),
('002487','draft','2013-07-02','DISA FSO','policy','Employ organization-defined techniques to introduce randomness into organizational operations.','SC-30(02)','N/A','Determine if [SC-30(02)_ODP; techniques employed to introduce randomness into organizational operations and assets are defined] are employed to introduce randomness into organizational operations and assets.'),
('002488','draft','2013-07-02','DISA FSO','policy','Employ organization-defined techniques to introduce randomness into organizational assets.','SC-30(02)','N/A','Determine if [SC-30(02)_ODP; techniques employed to introduce randomness into organizational operations and assets are defined] are employed to introduce randomness into organizational operations and assets.'),
('002489','draft','2013-07-02','DISA FSO','policy','Defines the processing and/or storage locations to be changed at random intervals or at an organization-defined frequency.','SC-30(03)','N/A','Determine if the location of [SC-30(03)_ODP[01]; processing and/or storage locations to be changed are defined] is changed [SC-30(03)_ODP[02]; one of the following PARAMETER VALUES is selected: {[SC-30(03)_ODP[03]; time frequency at which to change the location of processing and/or storage is defined (if selected)]; random time intervals}].'),
('002490','draft','2013-07-02','DISA FSO','policy','Defines the frequency at which the location of organization-defined processing and/or storage changes.','SC-30(03)','N/A','Determine if the location of [SC-30(03)_ODP[01]; processing and/or storage locations to be changed are defined] is changed [SC-30(03)_ODP[02]; one of the following PARAMETER VALUES is selected: {[SC-30(03)_ODP[03]; time frequency at which to change the location of processing and/or storage is defined (if selected)]; random time intervals}].'),
('002492','draft','2013-07-02','DISA FSO','policy','Change the location of organization-defined processing and/or storage at an organization-defined time frequency or at random time intervals.','SC-30(03)','N/A','Determine if the location of [SC-30(03)_ODP[01]; processing and/or storage locations to be changed are defined] is changed [SC-30(03)_ODP[02]; one of the following PARAMETER VALUES is selected: {[SC-30(03)_ODP[03]; time frequency at which to change the location of processing and/or storage is defined (if selected)]; random time intervals}].'),
('002493','draft','2013-07-02','DISA FSO','policy','Defines the system components in which it will employ realistic but misleading information regarding its security state or posture.','SC-30(04)','N/A','Determine if realistic but misleading information about the security state or posture of [SC-30(04)_ODP; system components for which realistic but misleading information about their security state or posture is employed are defined] is employed.'),
('002494','draft','2013-07-02','DISA FSO','policy','Employ realistic, but misleading, information in organization-defined system components about its security state or posture.','SC-30(04)','N/A','Determine if realistic but misleading information about the security state or posture of [SC-30(04)_ODP; system components for which realistic but misleading information about their security state or posture is employed are defined] is employed.'),
('002495','draft','2013-07-02','DISA FSO','policy','Defines the techniques to be employed to hide or conceal organization-defined system components.','SC-30(05)','N/A','Determine if [SC-30(05)_ODP[01]; techniques to be employed to hide or conceal system components are defined] are employed to hide or conceal [SC-30(05)_ODP[02]; system components to be hidden or concealed using techniques (defined in SC-30(05)_ODP[01]) are defined].'),
('002496','draft','2013-07-02','DISA FSO','policy','Defines the system components to be hidden or concealed.','SC-30(05)','N/A','Determine if [SC-30(05)_ODP[01]; techniques to be employed to hide or conceal system components are defined] are employed to hide or conceal [SC-30(05)_ODP[02]; system components to be hidden or concealed using techniques (defined in SC-30(05)_ODP[01]) are defined].'),
('002497','draft','2013-07-02','DISA FSO','policy','Employ organization-defined techniques to hide or conceal organization-defined system components.','SC-30(05)','N/A','Determine if [SC-30(05)_ODP[01]; techniques to be employed to hide or conceal system components are defined] are employed to hide or conceal [SC-30(05)_ODP[02]; system components to be hidden or concealed using techniques (defined in SC-30(05)_ODP[01]) are defined].'),
('002498','draft','2013-07-02','DISA FSO','policy','Perform a covert channel analysis to identify those aspects of communications within the system that are potential avenues for covert storage and/or timing channels.','SC-31a.','N/A','Determine if a covert channel analysis is performed to identify those aspects of communications within the system that are potential avenues for covert [SC-31_ODP; one or more of the following PARAMETER VALUES is/are selected: {storage; timing}] channels.'),
('002499','draft','2013-07-02','DISA FSO','policy','Estimate the maximum bandwidth of the covert storage and timing channels.','SC-31b.','N/A','Determine if the maximum bandwidth of those channels is estimated.'),
('002500','draft','2013-07-02','DISA FSO','policy','Defines the maximum bandwidth values to which covert storage and/or timing channels are to be reduced.','SC-31(02)','N/A','Determine if the maximum bandwidth for identified covert [SC-31(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {storage; timing}] channels is reduced to [SC-31(02)_ODP[02]; values for the maximum bandwidth for identified covert channels are defined].'),
('002501','draft','2013-07-02','DISA FSO','policy','Reduce the maximum bandwidth for identified covert storage and/or timing channels to organization-defined values.','SC-31(02)','N/A','Determine if the maximum bandwidth for identified covert [SC-31(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {storage; timing}] channels is reduced to [SC-31(02)_ODP[02]; values for the maximum bandwidth for identified covert channels are defined].'),
('002502','draft','2013-07-02','DISA FSO','policy','Defines the subset of identified covert channels in the operational environment of the system that are to have the bandwidth measured.','SC-31(03)','N/A','Determine if the bandwidth of [SC-31(03)_ODP; subset of identified covert channels whose bandwidth is to be measured in the operational environment of the system is defined] is measured in the operational environment of the system.'),
('002503','draft','2013-07-02','DISA FSO','policy','Measure the bandwidth of an organization-defined subset of identified covert channels in the operational environment of the information system.','SC-31(03)','N/A','Determine if the bandwidth of [SC-31(03)_ODP; subset of identified covert channels whose bandwidth is to be measured in the operational environment of the system is defined] is measured in the operational environment of the system.'),
('002504','draft','2013-07-02','DISA FSO','policy','Defines the system components into which the system is partitioned.','SC-32','N/A','Determine if the system is partitioned into [SC-32_ODP[01]; system components to reside in separate physical or logical domains or environments based on circumstances for the physical or logical separation of components are defined] residing in separate [SC-32_ODP[02]; one of the following PARAMETER VALUES is selected: {physical; logical}] domains or environments based on [SC-32_ODP[03]; circumstances for the physical or logical separation of components are defined].'),
('002505','draft','2013-07-02','DISA FSO','policy','Defines the circumstances under which the system components are to be physically or logically separated to support partitioning.','SC-32','N/A','Determine if the system is partitioned into [SC-32_ODP[01]; system components to reside in separate physical or logical domains or environments based on circumstances for the physical or logical separation of components are defined] residing in separate [SC-32_ODP[02]; one of the following PARAMETER VALUES is selected: {physical; logical}] domains or environments based on [SC-32_ODP[03]; circumstances for the physical or logical separation of components are defined].'),
('002506','draft','2013-07-02','DISA FSO','policy','Partition the system into organization-defined system components residing in separate physical or logical domains or environments based on organization-defined circumstances for physical or logical separation of components.','SC-32','N/A','Determine if the system is partitioned into [SC-32_ODP[01]; system components to reside in separate physical or logical domains or environments based on circumstances for the physical or logical separation of components are defined] residing in separate [SC-32_ODP[02]; one of the following PARAMETER VALUES is selected: {physical; logical}] domains or environments based on [SC-32_ODP[03]; circumstances for the physical or logical separation of components are defined].'),
('002507','draft','2013-07-02','DISA FSO','policy','Control read-only media after information has been recorded onto the media.',NULL,'N/A',NULL),
('002508','draft','2013-07-02','DISA FSO','policy','Defines the system firmware components for which hardware-based, write-protect is employed.','SC-51a.','N/A','Determine if hardware-based write-protect for [SC-51_ODP[01]; system firmware components requiring hardware-based write-protect are defined] is employed.'),
('002509','draft','2013-07-02','DISA FSO','policy','Employ hardware-based, write-protect for organization-defined information system firmware components.','SC-51a.','N/A','Determine if hardware-based write-protect for [SC-51_ODP[01]; system firmware components requiring hardware-based write-protect are defined] is employed.'),
('002510','draft','2013-07-02','DISA FSO','policy','Defines the individuals authorized to manually disable hardware-based, write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode.','SC-51b.','N/A','Determine if: - specific procedures are implemented for [SC-51_ODP[02]; authorized individuals requiring procedures for disabling and re-enabling hardware write-protect are defined] to manually disable hardware write-protect for firmware modifications. - specific procedures are implemented for [SC-51_ODP[02]; authorized individuals requiring procedures for disabling and re-enabling hardware write-protect are defined] to re-enable the write-protect prior to returning to operational mode.'),
('002511','draft','2013-07-02','DISA FSO','policy','Implement specific procedures for organization-defined authorized individuals to manually disable hardware-based, write-protect for firmware modifications.','SC-51b.','N/A','Determine if: - specific procedures are implemented for [SC-51_ODP[02]; authorized individuals requiring procedures for disabling and re-enabling hardware write-protect are defined] to manually disable hardware write-protect for firmware modifications. - specific procedures are implemented for [SC-51_ODP[02]; authorized individuals requiring procedures for disabling and re-enabling hardware write-protect are defined] to re-enable the write-protect prior to returning to operational mode.'),
('002512','draft','2013-07-02','DISA FSO','policy','Implement specific procedures for organization-defined authorized individuals to manually re-enable hardware write-protect prior to returning to operational mode.','SC-51b.','N/A','Determine if: - specific procedures are implemented for [SC-51_ODP[02]; authorized individuals requiring procedures for disabling and re-enabling hardware write-protect are defined] to manually disable hardware write-protect for firmware modifications. - specific procedures are implemented for [SC-51_ODP[02]; authorized individuals requiring procedures for disabling and re-enabling hardware write-protect are defined] to re-enable the write-protect prior to returning to operational mode.'),
('002513','draft','2013-07-02','DISA FSO','policy','Defines the processing that is to be distributed across multiple physical locations or logical domains.','SC-36','N/A','Determine if: - [SC-36_ODP[01]; processing components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[02]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}]. - [SC-36_ODP[03]; storage components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[04]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}].'),
('002514','draft','2013-07-02','DISA FSO','policy','Defines the storage components that is to be distributed across multiple physical locations or logical domains.','SC-36','N/A','Determine if: - [SC-36_ODP[01]; processing components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[02]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}]. - [SC-36_ODP[03]; storage components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[04]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}].'),
('002515','draft','2013-07-02','DISA FSO','policy','Distributes organization-defined processing across multiple physical locations or logical domains.','SC-36','N/A','Determine if: - [SC-36_ODP[01]; processing components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[02]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}]. - [SC-36_ODP[03]; storage components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[04]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}].'),
('002516','draft','2013-07-02','DISA FSO','policy','Distributes organization-defined storage components across multiple physical locations or logical domains.','SC-36','N/A','Determine if: - [SC-36_ODP[01]; processing components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[02]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}]. - [SC-36_ODP[03]; storage components to be distributed across multiple locations/domains are defined] are distributed across [SC-36_ODP[04]; one of the following PARAMETER VALUES is selected: {physical locations; logical domains}].'),
('002517','draft','2013-07-02','DISA FSO','policy','Defines the distributed processing components that are to be polled to identify potential faults, errors, or compromises.','SC-36(01)(a)','N/A','Determine if polling techniques are employed to identify potential faults, errors, or compromises to [SC-36(01)_ODP[01]; distributed processing and storage components for which polling techniques are to be employed to identify potential faults, errors, or compromises are defined].'),
('002518','draft','2013-07-02','DISA FSO','policy','Defines the distributed storage components that are to be polled to identify potential faults, errors, or compromises.','SC-36(01)(a)','N/A','Determine if polling techniques are employed to identify potential faults, errors, or compromises to [SC-36(01)_ODP[01]; distributed processing and storage components for which polling techniques are to be employed to identify potential faults, errors, or compromises are defined].'),
('002519','draft','2013-07-02','DISA FSO','policy','Employ polling techniques to identify potential faults, errors, or compromises to organization-defined distributed processing components.','SC-36(01)(a)','N/A','Determine if polling techniques are employed to identify potential faults, errors, or compromises to [SC-36(01)_ODP[01]; distributed processing and storage components for which polling techniques are to be employed to identify potential faults, errors, or compromises are defined].'),
('002520','draft','2013-07-02','DISA FSO','policy','Employ polling techniques to identify potential faults, errors, or compromises to organization-defined distributed storage components.','SC-36(01)(a)','N/A','Determine if polling techniques are employed to identify potential faults, errors, or compromises to [SC-36(01)_ODP[01]; distributed processing and storage components for which polling techniques are to be employed to identify potential faults, errors, or compromises are defined].'),
('002521','draft','2013-07-02','DISA FSO','policy','Defines the out-of-band channels to be employed for the physical delivery or electronic transmission of organization-defined information, system components, or devices.','SC-37','N/A','Determine if [SC-37_ODP[01]; out-of-band channels to be employed for the physical delivery or electronic transmission of information, system components, or devices to individuals or the system are defined] are employed for the physical delivery or electronic transmission of [SC-37_ODP[02]; information, system components, or devices to employ out-of-band-channels for physical delivery or electronic transmission are defined] to [SC-37_ODP[03]; individuals or systems to which physical delivery or electronic transmission of information, system components, or devices is to be achieved via the employment of out-of-band channels are defined].'),
('002522','draft','2013-07-02','DISA FSO','policy','Defines the information, system components, or devices that are to be electronically transmitted or physically delivered via organization-defined out-of-band channels.','SC-37','N/A','Determine if [SC-37_ODP[01]; out-of-band channels to be employed for the physical delivery or electronic transmission of information, system components, or devices to individuals or the system are defined] are employed for the physical delivery or electronic transmission of [SC-37_ODP[02]; information, system components, or devices to employ out-of-band-channels for physical delivery or electronic transmission are defined] to [SC-37_ODP[03]; individuals or systems to which physical delivery or electronic transmission of information, system components, or devices is to be achieved via the employment of out-of-band channels are defined].'),
('002523','draft','2013-07-02','DISA FSO','policy','Defines the individuals or systems authorized to be recipients of organization-defined information, system components, or devices to be delivered by employing organization-defined out-of-band channels for electronic transmission or physical delivery.','SC-37','N/A','Determine if [SC-37_ODP[01]; out-of-band channels to be employed for the physical delivery or electronic transmission of information, system components, or devices to individuals or the system are defined] are employed for the physical delivery or electronic transmission of [SC-37_ODP[02]; information, system components, or devices to employ out-of-band-channels for physical delivery or electronic transmission are defined] to [SC-37_ODP[03]; individuals or systems to which physical delivery or electronic transmission of information, system components, or devices is to be achieved via the employment of out-of-band channels are defined].'),
('002524','draft','2013-07-02','DISA FSO','policy','Employ organization-defined out-of-band channels for the physical delivery or electronic transmission of organization-defined information, system components, or devices to organization-defined individuals or systems.','SC-37','N/A','Determine if [SC-37_ODP[01]; out-of-band channels to be employed for the physical delivery or electronic transmission of information, system components, or devices to individuals or the system are defined] are employed for the physical delivery or electronic transmission of [SC-37_ODP[02]; information, system components, or devices to employ out-of-band-channels for physical delivery or electronic transmission are defined] to [SC-37_ODP[03]; individuals or systems to which physical delivery or electronic transmission of information, system components, or devices is to be achieved via the employment of out-of-band channels are defined].'),
('002525','draft','2013-07-02','DISA FSO','policy','Defines the controls to be employed to ensure only organization-defined individuals or systems receive organization-defined information, system components, or devices.','SC-37(01)','N/A','Determine if [SC-37(01)_ODP[01]; controls to be employed to ensure that only designated individuals or systems receive specific information, system components, or devices are defined] are employed to ensure that only [SC-37(01)_ODP[02]; individuals or systems designated to receive specific information, system components, or devices are defined] receive [SC-37(01)_ODP[03]; information, system components, or devices that only individuals or systems are designated to receive are defined].'),
('002526','draft','2013-07-02','DISA FSO','policy','Defines the information, system components, or devices which are to be received only by organization-defined individuals or systems.','SC-37(01)','N/A','Determine if [SC-37(01)_ODP[01]; controls to be employed to ensure that only designated individuals or systems receive specific information, system components, or devices are defined] are employed to ensure that only [SC-37(01)_ODP[02]; individuals or systems designated to receive specific information, system components, or devices are defined] receive [SC-37(01)_ODP[03]; information, system components, or devices that only individuals or systems are designated to receive are defined].'),
('002527','draft','2013-07-02','DISA FSO','policy','Employ organization-defined controls to ensure only organization-defined individuals or systems receive the organization-defined information, system components, or devices.','SC-37(01)','N/A','Determine if [SC-37(01)_ODP[01]; controls to be employed to ensure that only designated individuals or systems receive specific information, system components, or devices are defined] are employed to ensure that only [SC-37(01)_ODP[02]; individuals or systems designated to receive specific information, system components, or devices are defined] receive [SC-37(01)_ODP[03]; information, system components, or devices that only individuals or systems are designated to receive are defined].'),
('002528','draft','2013-07-02','DISA FSO','policy','Defines the operations security controls to be employed to protect key organizational information throughout the system development life cycle.','SC-38','N/A','Determine if [SC-38_ODP; operations security controls to be employed to protect key organizational information throughout the system development life cycle are defined] are employed to protect key organizational information throughout the system development life cycle.'),
('002529','draft','2013-07-02','DISA FSO','policy','Employ organization-defined operations security controls to protect key organizational information throughout the system development life cycle.','SC-38','N/A','Determine if [SC-38_ODP; operations security controls to be employed to protect key organizational information throughout the system development life cycle are defined] are employed to protect key organizational information throughout the system development life cycle.'),
('002530','draft','2013-07-02','DISA FSO','technical','Maintain a separate execution domain for each executing system process.','SC-39','N/A','Determine if a separate execution domain is maintained for each executing system process.'),
('002531','draft','2013-07-02','DISA FSO','technical','Implement hardware separation mechanisms to facilitate process isolation.','SC-39(01)','N/A','Determine if hardware separation is implemented to facilitate process isolation.'),
('002532','draft','2013-07-02','DISA FSO','policy','Defines the multi-threaded processing in which a separate execution domain is maintained by the system for each thread.','SC-39(02)','N/A','Determine if a separate execution domain is maintained for each thread in [SC-39(02)_ODP; multi-thread processing for which a separate execution domain is to be maintained for each thread is defined].'),
('002533','draft','2013-07-02','DISA FSO','technical','Maintain a separate execution domain for each thread in organization-defined multi-threaded processing.','SC-39(02)','N/A','Determine if a separate execution domain is maintained for each thread in [SC-39(02)_ODP; multi-thread processing for which a separate execution domain is to be maintained for each thread is defined].'),
('002534','draft','2013-07-02','DISA FSO','policy','Defines types of signal parameter attacks or references to sources for such attacks from which the system protects organization-defined wireless links.','SC-40','N/A','Determine if: - external [SC-40_ODP[01]; external wireless links to be protected from particular types of signal parameter attacks are defined] are protected from [SC-40_ODP[02]; types of signal parameter attacks or references to sources for such attacks from which to protect external wireless links are defined]. - internal [SC-40_ODP[03]; internal wireless links to be protected from particular types of signal parameter attacks are defined] are protected from [SC-40_ODP[04]; types of signal parameter attacks or references to sources for such attacks from which to protect internal wireless links are defined].'),
('002535','draft','2013-07-02','DISA FSO','policy','Defines the external and internal wireless links the system is to protect from organization-defined types of signal parameter attacks or references to sources for such attacks.','SC-40','N/A','Determine if: - external [SC-40_ODP[01]; external wireless links to be protected from particular types of signal parameter attacks are defined] are protected from [SC-40_ODP[02]; types of signal parameter attacks or references to sources for such attacks from which to protect external wireless links are defined]. - internal [SC-40_ODP[03]; internal wireless links to be protected from particular types of signal parameter attacks are defined] are protected from [SC-40_ODP[04]; types of signal parameter attacks or references to sources for such attacks from which to protect internal wireless links are defined].'),
('002536','draft','2013-07-02','DISA FSO','technical','Protect organization-defined external and internal wireless links from organization-defined types of signal parameter attacks or references to sources for such attacks.','SC-40','N/A','Determine if: - external [SC-40_ODP[01]; external wireless links to be protected from particular types of signal parameter attacks are defined] are protected from [SC-40_ODP[02]; types of signal parameter attacks or references to sources for such attacks from which to protect external wireless links are defined]. - internal [SC-40_ODP[03]; internal wireless links to be protected from particular types of signal parameter attacks are defined] are protected from [SC-40_ODP[04]; types of signal parameter attacks or references to sources for such attacks from which to protect internal wireless links are defined].'),
('002537','draft','2013-07-02','DISA FSO','policy','Defines the level of protection against the effects of intentional electromagnetic interference to be achieved by implemented cryptographic mechanisms.','SC-40(01)','N/A','Determine if cryptographic mechanisms that achieve [SC-40(01)_ODP; level of protection to be employed against the effects of intentional electromagnetic interference is defined] against the effects of intentional electromagnetic interference are implemented.'),
('002538','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms that achieve an organization-defined level of protection against the effects of intentional electromagnetic interference.','SC-40(01)','N/A','Determine if cryptographic mechanisms that achieve [SC-40(01)_ODP; level of protection to be employed against the effects of intentional electromagnetic interference is defined] against the effects of intentional electromagnetic interference are implemented.'),
('002539','draft','2013-07-02','DISA FSO','policy','Defines the level of reduction the system is to implement to reduce the detection potential of wireless links.','SC-40(02)','N/A','Determine if cryptographic mechanisms to reduce the detection potential of wireless links to [SC-40(02)_ODP; the level of reduction to be achieved to reduce the detection potential of wireless links is defined] are implemented.'),
('002540','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to reduce the detection potential of wireless links to an organization-defined level of reduction.','SC-40(02)','N/A','Determine if cryptographic mechanisms to reduce the detection potential of wireless links to [SC-40(02)_ODP; the level of reduction to be achieved to reduce the detection potential of wireless links is defined] are implemented.'),
('002541','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.','SC-40(03)','N/A','Determine if cryptographic mechanisms are implemented to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.'),
('002542','draft','2013-07-02','DISA FSO','policy','Defines the wireless transmitters that are to have cryptographic mechanisms implemented to prevent the identification of the wireless transmitters.','SC-40(04)','N/A','Determine if cryptographic mechanisms are implemented to prevent the identification of [SC-40(04)_ODP; wireless transmitters for which cryptographic mechanisms are to be implemented are defined] by using the transmitter signal parameters.'),
('002543','draft','2013-07-02','DISA FSO','technical','Implement cryptographic mechanisms to prevent the identification of organization-defined wireless transmitters by using the transmitter signal parameters.','SC-40(04)','N/A','Determine if cryptographic mechanisms are implemented to prevent the identification of [SC-40(04)_ODP; wireless transmitters for which cryptographic mechanisms are to be implemented are defined] by using the transmitter signal parameters.'),
('002544','draft','2013-07-02','DISA FSO','policy','Defines the systems or system components on which organization-defined connection ports or input/output devices are to be physically or logically disabled or removed.','SC-41','N/A','Determine if [SC-41_ODP[01]; connection ports or input/output devices to be disabled or removed are defined] are [SC-41_ODP[02]; one of the following PARAMETER VALUES is selected: {physically; logically}] disabled or removed on [SC-41_ODP[03]; systems or system components with connection ports or input/output devices to be disabled or removed are defined].'),
('002545','draft','2013-07-02','DISA FSO','policy','Defines the connection ports or input/output devices that are to be physically or logically disabled or removed from organization-defined systems or system components.','SC-41','N/A','Determine if [SC-41_ODP[01]; connection ports or input/output devices to be disabled or removed are defined] are [SC-41_ODP[02]; one of the following PARAMETER VALUES is selected: {physically; logically}] disabled or removed on [SC-41_ODP[03]; systems or system components with connection ports or input/output devices to be disabled or removed are defined].'),
('002546','draft','2013-07-02','DISA FSO','technical','Physically or logically disable or remove organization-defined connection ports or input/output devices on organization-defined systems or system components.','SC-41','N/A','Determine if [SC-41_ODP[01]; connection ports or input/output devices to be disabled or removed are defined] are [SC-41_ODP[02]; one of the following PARAMETER VALUES is selected: {physically; logically}] disabled or removed on [SC-41_ODP[03]; systems or system components with connection ports or input/output devices to be disabled or removed are defined].'),
('002547','draft','2013-07-02','DISA FSO','policy','Defines the exceptions where remote activation of sensors is allowed.','SC-42a.','N/A','Determine if [SC-42_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {the use of devices possessing [SC-42_ODP[02]; environmental sensing capabilities in devices are defined (if selected)] in [SC-42_ODP[03]; facilities, areas, or systems where the use of devices possessing environmental sensing capabilities is prohibited are defined (if selected)]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [SC-42_ODP[04]; exceptions where remote activation of sensors is allowed are defined (if selected)]}] is/are prohibited.'),
('002548','draft','2013-07-02','DISA FSO','technical','Prohibit the use of devices possessing organization-defined environmental sensing capabilities in organization-defined facilities, areas, or systems; and/or the remote activation of environmental sensing capabilities on organizational systems or system components except for the organization-defined exceptions where remote activation of sensors is allowed.','SC-42a.','N/A','Determine if [SC-42_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {the use of devices possessing [SC-42_ODP[02]; environmental sensing capabilities in devices are defined (if selected)] in [SC-42_ODP[03]; facilities, areas, or systems where the use of devices possessing environmental sensing capabilities is prohibited are defined (if selected)]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [SC-42_ODP[04]; exceptions where remote activation of sensors is allowed are defined (if selected)]}] is/are prohibited.'),
('002549','draft','2013-07-02','DISA FSO','policy','Defines the class of users to receive explicit indication of sensor use.','SC-42b.','N/A','Determine if an explicit indication of sensor use is provided to [SC-42_ODP[05]; group of users to whom an explicit indication of sensor use is to be provided is defined].'),
('002550','draft','2013-07-02','DISA FSO','technical','Provide an explicit indication of sensor use to the organization-defined class of users.','SC-42b.','N/A','Determine if an explicit indication of sensor use is provided to [SC-42_ODP[05]; group of users to whom an explicit indication of sensor use is to be provided is defined].'),
('002551','draft','2013-07-02','DISA FSO','policy','Defines the sensors to be configured so that collected data or information is reported only to authorized individuals or roles.','SC-42(01)','N/A','Determine if the system is configured so that data or information collected by the [SC-42(01)_ODP; sensors to be used to collect data or information are defined] is only reported to authorized individuals or roles.'),
('002552','draft','2013-07-02','DISA FSO','policy','Verify that the system is configured so that data or information collected by the organization-defined sensors is only reported to authorized individuals or roles.','SC-42(01)','N/A','Determine if the system is configured so that data or information collected by the [SC-42(01)_ODP; sensors to be used to collect data or information are defined] is only reported to authorized individuals or roles.'),
('002553','draft','2013-07-02','DISA FSO','policy','Defines the measures to be employed to ensure data or information collected by organization-defined sensors is used only for authorized purposes.','SC-42(02)','N/A','Determine if [SC-42(02)_ODP; measures to be employed so that data or information collected by sensors is only used for authorized purposes are defined] are employed so that data or information collected by [SC-42(01)_ODP; sensors to be used to collect data or information are defined] is only used for authorized purposes.'),
('002554','draft','2013-07-02','DISA FSO','policy','Defines the sensors that are to collect data or information for authorized purposes.','SC-42(02)','N/A','Determine if [SC-42(02)_ODP; measures to be employed so that data or information collected by sensors is only used for authorized purposes are defined] are employed so that data or information collected by [SC-42(01)_ODP; sensors to be used to collect data or information are defined] is only used for authorized purposes.'),
('002555','draft','2013-07-02','DISA FSO','policy','Employ organization-defined measures, so that data or information collected by organization-defined sensors is only used for authorized purposes.','SC-42(02)','N/A','Determine if [SC-42(02)_ODP; measures to be employed so that data or information collected by sensors is only used for authorized purposes are defined] are employed so that data or information collected by [SC-42(01)_ODP; sensors to be used to collect data or information are defined] is only used for authorized purposes.'),
('002556','draft','2013-07-02','DISA FSO','policy','Defines the environmental sensing capabilities prohibited on devices used in organization-defined facilities, areas, or systems.','SC-42a.','N/A','Determine if [SC-42_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {the use of devices possessing [SC-42_ODP[02]; environmental sensing capabilities in devices are defined (if selected)] in [SC-42_ODP[03]; facilities, areas, or systems where the use of devices possessing environmental sensing capabilities is prohibited are defined (if selected)]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [SC-42_ODP[04]; exceptions where remote activation of sensors is allowed are defined (if selected)]}] is/are prohibited.'),
('002557','draft','2013-07-02','DISA FSO','policy','Defines the facilities, areas, or systems where devices processing organization-defined environmental sensing capabilities are prohibited.','SC-42a.','N/A','Determine if [SC-42_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {the use of devices possessing [SC-42_ODP[02]; environmental sensing capabilities in devices are defined (if selected)] in [SC-42_ODP[03]; facilities, areas, or systems where the use of devices possessing environmental sensing capabilities is prohibited are defined (if selected)]; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: [SC-42_ODP[04]; exceptions where remote activation of sensors is allowed are defined (if selected)]}] is/are prohibited.'),
('002559','draft','2013-07-02','DISA FSO','policy','Defines the system components for which usage restrictions and implementation guidance are to be established.','SC-43a.','N/A','Determine if usage restrictions and implementation guidelines are established for [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined].'),
('002560','draft','2013-07-02','DISA FSO','policy','Establish usage restrictions and implementation guidance for organization-defined system components based on the potential to cause damage to the system if used maliciously.','SC-43a.','N/A','Determine if usage restrictions and implementation guidelines are established for [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined].'),
('002561','draft','2013-07-02','DISA FSO','policy','Authorize the use of organization-defined system components which have the potential to cause damage to the system if used maliciously.','SC-43b.','N/A','Determine if: - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is authorized within the system. - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is monitored within the system. - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is controlled within the system.'),
('002562','draft','2013-07-02','DISA FSO','policy','Monitor the use of organization-defined system components which have the potential to cause damage to the system if used maliciously.','SC-43b.','N/A','Determine if: - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is authorized within the system. - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is monitored within the system. - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is controlled within the system.'),
('002563','draft','2013-07-02','DISA FSO','policy','Control the use of organization-defined system components which have the potential to cause damage to the system if used maliciously.','SC-43b.','N/A','Determine if: - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is authorized within the system. - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is monitored within the system. - the use of [SC-43_ODP; the components for which usage restrictions and implementation guidance are to be established are defined] is controlled within the system.'),
('002564','draft','2013-07-02','DISA FSO','policy','Defines the system, system component, or location where a detonation chamber capability is employed.','SC-44','N/A','Determine if a detonation chamber capability is employed within the [SC-44_ODP; the system, system component, or location where a detonation chamber capability is to be employed is defined].'),
('002565','draft','2013-07-02','DISA FSO','policy','Employ a detonation chamber capability within an organization-defined system, system component, or location.','SC-44','N/A','Determine if a detonation chamber capability is employed within the [SC-44_ODP; the system, system component, or location where a detonation chamber capability is to be employed is defined].'),
('002566','draft','2013-07-09','DISA FSO','policy','Defines personnel or roles to whom a media protection policy and procedures will be disseminated.','MP-01a.','N/A','Determine if: - a media protection policy is developed and documented. - the media protection policy is disseminated to [MP-01_ODP[01]; personnel or roles to whom the media protection policy is to be disseminated is/are defined].'),
('002567','draft','2013-07-09','DISA FSO','policy','Review and approve media sanitization.','MP-06(01)','N/A','Determine if: - media sanitization and disposal actions are reviewed. - media sanitization and disposal actions are approved. - media sanitization and disposal actions are tracked. - media sanitization and disposal actions are documented. - media sanitization and disposal actions are verified.'),
('002568','draft','2013-07-09','DISA FSO','policy','Track and document media sanitization.','MP-06(01)','N/A','Determine if: - media sanitization and disposal actions are reviewed. - media sanitization and disposal actions are approved. - media sanitization and disposal actions are tracked. - media sanitization and disposal actions are documented. - media sanitization and disposal actions are verified.'),
('002569','draft','2013-07-09','DISA FSO','policy','Verify media sanitization.','MP-06(01)','N/A','Determine if: - media sanitization and disposal actions are reviewed. - media sanitization and disposal actions are approved. - media sanitization and disposal actions are tracked. - media sanitization and disposal actions are documented. - media sanitization and disposal actions are verified.'),
('002570','draft','2013-07-09','DISA FSO','policy','Review and approve media disposal actions.','MP-06(01)','N/A','Determine if: - media sanitization and disposal actions are reviewed. - media sanitization and disposal actions are approved. - media sanitization and disposal actions are tracked. - media sanitization and disposal actions are documented. - media sanitization and disposal actions are verified.'),
('002571','draft','2013-07-09','DISA FSO','policy','Track and document media disposal actions.','MP-06(01)','N/A','Determine if: - media sanitization and disposal actions are reviewed. - media sanitization and disposal actions are approved. - media sanitization and disposal actions are tracked. - media sanitization and disposal actions are documented. - media sanitization and disposal actions are verified.'),
('002572','draft','2013-07-09','DISA FSO','policy','Verify media disposal actions.','MP-06(01)','N/A','Determine if: - media sanitization and disposal actions are reviewed. - media sanitization and disposal actions are approved. - media sanitization and disposal actions are tracked. - media sanitization and disposal actions are documented. - media sanitization and disposal actions are verified.'),
('002573','draft','2013-07-09','DISA FSO','policy','Enforce dual authorization for the sanitization of organization-defined system media.','MP-06(07)','N/A','Determine if dual authorization for sanitization of [MP-06(07)_ODP; system media to be sanitized using dual authorization is defined] is enforced.'),
('002574','draft','2013-07-09','DISA FSO','policy','Defines the system media that dual authorization is enforced for sanitization.','MP-06(07)','N/A','Determine if dual authorization for sanitization of [MP-06(07)_ODP; system media to be sanitized using dual authorization is defined] is enforced.'),
('002575','draft','2013-07-09','DISA FSO','policy','Defines systems or system components from which information is purged or wiped, either remotely or under the organization-defined conditions.','MP-06(08)','N/A','Determine if the capability to purge or wipe information from [MP-06(08)_ODP[01]; systems or system components to purge or wipe information either remotely or under specific conditions are defined] [MP-06(08)_ODP[02]; one of the following PARAMETER VALUES is selected: {remotely; under [MP-06(08)_ODP[03]; conditions under which information is to be purged or wiped are defined (if selected)]}] is provided.'),
('002576','draft','2013-07-09','DISA FSO','policy','Defines conditions under which information from organization-defined systems or system components are to be purged or wiped.','MP-06(08)','N/A','Determine if the capability to purge or wipe information from [MP-06(08)_ODP[01]; systems or system components to purge or wipe information either remotely or under specific conditions are defined] [MP-06(08)_ODP[02]; one of the following PARAMETER VALUES is selected: {remotely; under [MP-06(08)_ODP[03]; conditions under which information is to be purged or wiped are defined (if selected)]}] is provided.'),
('002577','draft','2013-07-09','DISA FSO','policy','Provide the capability to purge or wipe information from organization-defined systems, system components either remotely or under organization-defined conditions.','MP-06(08)','N/A','Determine if the capability to purge or wipe information from [MP-06(08)_ODP[01]; systems or system components to purge or wipe information either remotely or under specific conditions are defined] [MP-06(08)_ODP[02]; one of the following PARAMETER VALUES is selected: {remotely; under [MP-06(08)_ODP[03]; conditions under which information is to be purged or wiped are defined (if selected)]}] is provided.'),
('002578','draft','2013-07-09','DISA FSO','policy','Defines system media to sanitize prior to disposal, release out of organizational control, or release for reuse using organization-defined sanitization techniques and procedures.','MP-06a.','N/A','Determine if: - [MP-06_ODP[01]; system media to be sanitized prior to disposal is defined] is sanitized using [MP-06_ODP[04]; sanitization techniques and procedures to be used for sanitization prior to disposal are defined] prior to disposal. - [MP-06_ODP[02]; system media to be sanitized prior to release from organizational control is defined] is sanitized using [MP-06_ODP[05]; sanitization techniques and procedures to be used for sanitization prior to release from organizational control are defined] prior to release from organizational control. - [MP-06_ODP[03]; system media to be sanitized prior to release for reuse is defined] is sanitized using [MP-06_ODP[06]; sanitization techniques and procedures to be used for sanitization prior to release for reuse are defined] prior to release for reuse.'),
('002579','draft','2013-07-09','DISA FSO','policy','Defines the sanitization techniques and procedures to be used to sanitize organization-defined system media prior to disposal, release out of organizational control, or release for reuse.','MP-06a.','N/A','Determine if: - [MP-06_ODP[01]; system media to be sanitized prior to disposal is defined] is sanitized using [MP-06_ODP[04]; sanitization techniques and procedures to be used for sanitization prior to disposal are defined] prior to disposal. - [MP-06_ODP[02]; system media to be sanitized prior to release from organizational control is defined] is sanitized using [MP-06_ODP[05]; sanitization techniques and procedures to be used for sanitization prior to release from organizational control are defined] prior to release from organizational control. - [MP-06_ODP[03]; system media to be sanitized prior to release for reuse is defined] is sanitized using [MP-06_ODP[06]; sanitization techniques and procedures to be used for sanitization prior to release for reuse are defined] prior to release for reuse.'),
('002580','draft','2013-07-09','DISA FSO','policy','Employ sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information.','MP-06b.','N/A','Determine if sanitization mechanisms with strength and integrity commensurate with the security category or classification of the information are employed.'),
('002581','draft','2013-07-09','DISA FSO','policy','Defines the types of system media to restrict or prohibit on organization-defined systems or system components using organization-defined controls.','MP-07a.','N/A','Determine if the use of [MP-07_ODP[01]; types of system media to be restricted or prohibited from use on systems or system components are defined] is [MP-07_ODP[02]; one of the following PARAMETER VALUES is selected: {restrict; prohibit}] on [MP-07_ODP[03]; systems or system components on which the use of specific types of system media to be restricted or prohibited are defined] using [MP-07_ODP[04]; controls to restrict or prohibit the use of specific types of system media on systems or system components are defined].'),
('002582','draft','2013-07-09','DISA FSO','policy','Defines the systems or system components on which to restrict or prohibit the use of organization-defined types of system media using organization-defined controls.','MP-07a.','N/A','Determine if the use of [MP-07_ODP[01]; types of system media to be restricted or prohibited from use on systems or system components are defined] is [MP-07_ODP[02]; one of the following PARAMETER VALUES is selected: {restrict; prohibit}] on [MP-07_ODP[03]; systems or system components on which the use of specific types of system media to be restricted or prohibited are defined] using [MP-07_ODP[04]; controls to restrict or prohibit the use of specific types of system media on systems or system components are defined].'),
('002583','draft','2013-07-09','DISA FSO','policy','Defines the controls to use for restricting or prohibiting the use of organization-defined types of system media on organization-defined systems or system components.','MP-07a.','N/A','Determine if the use of [MP-07_ODP[01]; types of system media to be restricted or prohibited from use on systems or system components are defined] is [MP-07_ODP[02]; one of the following PARAMETER VALUES is selected: {restrict; prohibit}] on [MP-07_ODP[03]; systems or system components on which the use of specific types of system media to be restricted or prohibited are defined] using [MP-07_ODP[04]; controls to restrict or prohibit the use of specific types of system media on systems or system components are defined].'),
('002584','draft','2013-07-09','DISA FSO','policy','Restrict or prohibit the use of organization-defined types of system media on organization-defined systems or system components using organization-defined controls.','MP-07a.','N/A','Determine if the use of [MP-07_ODP[01]; types of system media to be restricted or prohibited from use on systems or system components are defined] is [MP-07_ODP[02]; one of the following PARAMETER VALUES is selected: {restrict; prohibit}] on [MP-07_ODP[03]; systems or system components on which the use of specific types of system media to be restricted or prohibited are defined] using [MP-07_ODP[04]; controls to restrict or prohibit the use of specific types of system media on systems or system components are defined].'),
('002585','draft','2013-07-09','DISA FSO','policy','Prohibit the use of portable storage devices in organizational systems when such devices have no identifiable owner.','MP-07b.','N/A','Determine if the use of portable storage devices in organizational systems is prohibited when such devices have no identifiable owner.'),
('002586','draft','2013-07-09','DISA FSO','policy','Prohibit the use of sanitization-resistant media in organizational systems.','MP-07(02)','N/A','Determine if: - sanitization-resistant media is identified. - the use of sanitization-resistant media in organizational systems is prohibited.'),
('002587','draft','2013-07-09','DISA FSO','policy','Document system media downgrading actions.','MP-08(01)','N/A','Determine if system media downgrading actions are documented.'),
('002591','draft','2013-07-09','DISA FSO','policy','Defines the frequency with which to test downgrading equipment and procedures to ensure correct performance.','MP-08(02)','N/A','Determine if: - downgrading equipment is tested [MP-08(02)_ODP[01]; the frequency with which to test downgrading equipment is defined] to ensure that downgrading actions are being achieved. - downgrading procedures are tested [MP-08(02)_ODP[02]; the frequency with which to test downgrading procedures is defined] to ensure that downgrading actions are being achieved.'),
('002593','draft','2013-07-09','DISA FSO','policy','Downgrade system media containing Controlled Unclassified Information (CUI) prior to public release.','MP-08(03)','N/A','Determine if: - system media containing controlled unclassified information is identified. - system media containing controlled unclassified information is downgraded prior to public release.'),
('002594','draft','2013-07-09','DISA FSO','policy','Downgrade system media containing classified information prior to release to individuals without required access authorizations.','MP-08(04)','N/A','Determine if: - system media containing classified information is identified. - system media containing classified information is downgraded prior to release to individuals without required access authorizations.'),
('002600','draft','2013-07-09','DISA FSO','policy','Downgrade the identified system media using the established process.','MP-08d.','N/A','Determine if the identified system media is downgraded using the [MP-08_ODP[01]; a system media downgrading process is defined].'),
('002601','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles to whom the system and information integrity policy and procedures are to be disseminated.','SI-01a.','N/A','Determine if: - a system and information integrity policy is developed and documented. - the system and information integrity policy is disseminated to [SI-01_ODP[01]; personnel or roles to whom the system and information integrity policy is to be disseminated is/are defined].'),
('002602','draft','2013-07-11','DISA FSO','policy','Test firmware updates related to flaw remediation for effectiveness before installation.','SI-02b.','N/A','Determine if: - software updates related to flaw remediation are tested for effectiveness before installation. - software updates related to flaw remediation are tested for potential side effects before installation. - firmware updates related to flaw remediation are tested for effectiveness before installation. - firmware updates related to flaw remediation are tested for potential side effects before installation.'),
('002603','draft','2013-07-11','DISA FSO','policy','Test firmware updates related to flaw remediation for potential side effects before installation.','SI-02b.','N/A','Determine if: - software updates related to flaw remediation are tested for effectiveness before installation. - software updates related to flaw remediation are tested for potential side effects before installation. - firmware updates related to flaw remediation are tested for effectiveness before installation. - firmware updates related to flaw remediation are tested for potential side effects before installation.'),
('002604','draft','2013-07-11','DISA FSO','policy','Defines the time period following the release of updates within which security-related software updates are to be installed.','SI-02c.','N/A','Determine if: - security-relevant software updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates. - security-relevant firmware updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates.'),
('002605','draft','2013-07-11','DISA FSO','technical','Install security-relevant software updates within an organization-defined time period of the release of the updates.','SI-02c.','N/A','Determine if: - security-relevant software updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates. - security-relevant firmware updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates.'),
('002606','draft','2013-07-11','DISA FSO','policy','Defines the time period following the release of updates within which security-related firmware updates are to be installed.','SI-02c.','N/A','Determine if: - security-relevant software updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates. - security-relevant firmware updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates.'),
('002607','draft','2013-07-11','DISA FSO','technical','Install security-relevant firmware updates within an organization-defined time period of the release of the updates.','SI-02c.','N/A','Determine if: - security-relevant software updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates. - security-relevant firmware updates are installed within [SI-02_ODP; time period within which to install security-relevant software updates after the release of the updates is defined] of the release of the updates.'),
('002608','draft','2013-07-11','DISA FSO','policy','Establish organization-defined benchmarks for the time taken to apply corrective actions after flaw identification.','SI-02(03)(b)','N/A','Determine if [SI-02(03)_ODP; the benchmarks for taking corrective actions are defined] for taking corrective actions have been established.'),
('002609','draft','2013-07-11','DISA FSO','policy','Defines the system components on which organization-defined security-relevant software updates will be automatically installed.','SI-02(05)','N/A','Determine if [SI-02(05)_ODP[01]; security-relevant software and firmware updates to be automatically installed to system components are defined] are installed automatically to [SI-02(05)_ODP[02]; system components requiring security-relevant software updates to be automatically installed are defined].'),
('002610','draft','2013-07-11','DISA FSO','policy','Defines the system components on which organization-defined security-relevant firmware updates will be automatically installed.','SI-02(05)','N/A','Determine if [SI-02(05)_ODP[01]; security-relevant software and firmware updates to be automatically installed to system components are defined] are installed automatically to [SI-02(05)_ODP[02]; system components requiring security-relevant software updates to be automatically installed are defined].'),
('002611','draft','2013-07-11','DISA FSO','policy','Defines the security-relevant software updates to be automatically installed on organization-defined system components.','SI-02(05)','N/A','Determine if [SI-02(05)_ODP[01]; security-relevant software and firmware updates to be automatically installed to system components are defined] are installed automatically to [SI-02(05)_ODP[02]; system components requiring security-relevant software updates to be automatically installed are defined].'),
('002612','draft','2013-07-11','DISA FSO','policy','Defines the security-relevant firmware updates to be automatically installed on organization-defined system components.','SI-02(05)','N/A','Determine if [SI-02(05)_ODP[01]; security-relevant software and firmware updates to be automatically installed to system components are defined] are installed automatically to [SI-02(05)_ODP[02]; system components requiring security-relevant software updates to be automatically installed are defined].'),
('002613','draft','2013-07-11','DISA FSO','technical','Install organization-defined security-relevant software updates automatically to organization-defined system components.','SI-02(05)','N/A','Determine if [SI-02(05)_ODP[01]; security-relevant software and firmware updates to be automatically installed to system components are defined] are installed automatically to [SI-02(05)_ODP[02]; system components requiring security-relevant software updates to be automatically installed are defined].'),
('002614','draft','2013-07-11','DISA FSO','technical','Install organization-defined security-relevant firmware updates automatically to organization-defined system components.','SI-02(05)','N/A','Determine if [SI-02(05)_ODP[01]; security-relevant software and firmware updates to be automatically installed to system components are defined] are installed automatically to [SI-02(05)_ODP[02]; system components requiring security-relevant software updates to be automatically installed are defined].'),
('002615','draft','2013-07-11','DISA FSO','policy','Defines the software components to remove previous versions after updated versions have been installed.','SI-02(06)','N/A','Determine if previous versions of [SI-02(06)_ODP; software and firmware components to be removed after updated versions have been installed are defined] are removed after updated versions have been installed.'),
('002616','draft','2013-07-11','DISA FSO','policy','Defines the firmware components to remove previous versions after updated versions have been installed.','SI-02(06)','N/A','Determine if previous versions of [SI-02(06)_ODP; software and firmware components to be removed after updated versions have been installed are defined] are removed after updated versions have been installed.'),
('002617','draft','2013-07-11','DISA FSO','technical','Remove previous versions of organization-defined software components after updated versions have been installed.','SI-02(06)','N/A','Determine if previous versions of [SI-02(06)_ODP; software and firmware components to be removed after updated versions have been installed are defined] are removed after updated versions have been installed.'),
('002618','draft','2013-07-11','DISA FSO','technical','Remove previous versions of organization-defined firmware components after updated versions have been installed.','SI-02(06)','N/A','Determine if previous versions of [SI-02(06)_ODP; software and firmware components to be removed after updated versions have been installed are defined] are removed after updated versions have been installed.'),
('002623','draft','2013-07-11','DISA FSO','policy','Defines the frequency for performing periodic scans of the system for malicious code.','SI-03c.01','N/A','Determine if: - malicious code protection mechanisms are configured to perform periodic scans of the system [SI-03_ODP[02]; the frequency at which malicious code protection mechanisms perform scans is defined]. - malicious code protection mechanisms are configured to perform real-time scans of files from external sources at [SI-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {endpoint; network entry and exit points}] as the files are downloaded, opened, or executed in accordance with organizational policy.'),
('002624','draft','2013-07-11','DISA FSO','technical','Configure malicious code protection mechanisms to perform real-time scans of files from external sources at endpoint; and/or network entry and exit points as the files are downloaded, opened, or executed in accordance with organizational policy.','SI-03c.01','N/A','Determine if: - malicious code protection mechanisms are configured to perform periodic scans of the system [SI-03_ODP[02]; the frequency at which malicious code protection mechanisms perform scans is defined]. - malicious code protection mechanisms are configured to perform real-time scans of files from external sources at [SI-03_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {endpoint; network entry and exit points}] as the files are downloaded, opened, or executed in accordance with organizational policy.'),
('002625','draft','2013-07-11','DISA FSO','policy','When testing malicious code protection mechanisms, verify the detection of the code.','SI-03(06)(b)','N/A','Determine if: - the detection of (benign test) code occurs. - the associated incident reporting occurs.'),
('002626','draft','2013-07-11','DISA FSO','policy','When testing malicious code protection mechanisms, verify the associated incident reporting of the code occurs.','SI-03(06)(b)','N/A','Determine if: - the detection of (benign test) code occurs. - the associated incident reporting occurs.'),
('002628','draft','2013-07-11','DISA FSO','policy','Defines the unauthorized operating system commands that are to be detected through the kernel application programming interface on organization-defined system hardware components.','SI-03(08)(a)','N/A','Determine if [SI-03(08)_ODP[01]; system hardware components for which unauthorized operating system commands are to be detected through the kernel application programming interface are defined] are detected through the kernel application programming interface on [SI-03(08)_ODP[02]; unauthorized operating system commands to be detected are defined].'),
('002629','draft','2013-07-11','DISA FSO','policy','Defines the system hardware components that are to detect organization-defined unauthorized operating system commands through the kernel programming application interface.','SI-03(08)(a)','N/A','Determine if [SI-03(08)_ODP[01]; system hardware components for which unauthorized operating system commands are to be detected through the kernel application programming interface are defined] are detected through the kernel application programming interface on [SI-03(08)_ODP[02]; unauthorized operating system commands to be detected are defined].'),
('002630','draft','2013-07-11','DISA FSO','technical','Detect organization-defined unauthorized operating system commands through the kernel application programming interface at organization-defined system hardware components.','SI-03(08)(a)','N/A','Determine if [SI-03(08)_ODP[01]; system hardware components for which unauthorized operating system commands are to be detected through the kernel application programming interface are defined] are detected through the kernel application programming interface on [SI-03(08)_ODP[02]; unauthorized operating system commands to be detected are defined].'),
('002631','draft','2013-07-11','DISA FSO','technical','Issue a warning; audit the command execution; and/or prevent the execution of the command when organization-defined unauthorized operating system commands are detected.','SI-03(08)(b)','N/A','Determine if [SI-03(08)_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {issue a warning; audit the command execution; prevent the execution of the command}] is/are performed.'),
('002634','draft','2013-07-11','DISA FSO','policy','Defines the tools to be employed to analyze the characteristics and behavior of malicious code.','SI-03(10)(a)','N/A','Determine if [SI-03(10)_ODP; tools and techniques to be employed to analyze the characteristics and behavior of malicious code are defined] are employed to analyze the characteristics and behavior of malicious code.'),
('002635','draft','2013-07-11','DISA FSO','policy','Defines the techniques to be employed to analyze the characteristics and behavior of malicious code.','SI-03(10)(a)','N/A','Determine if [SI-03(10)_ODP; tools and techniques to be employed to analyze the characteristics and behavior of malicious code are defined] are employed to analyze the characteristics and behavior of malicious code.'),
('002636','draft','2013-07-11','DISA FSO','policy','Employ organization-defined tools to analyze the characteristics and behavior of malicious code.','SI-03(10)(a)','N/A','Determine if [SI-03(10)_ODP; tools and techniques to be employed to analyze the characteristics and behavior of malicious code are defined] are employed to analyze the characteristics and behavior of malicious code.'),
('002638','draft','2013-07-11','DISA FSO','policy','Employ organization-defined techniques to analyze the characteristics and behavior of malicious code.','SI-03(10)(a)','N/A','Determine if [SI-03(10)_ODP; tools and techniques to be employed to analyze the characteristics and behavior of malicious code are defined] are employed to analyze the characteristics and behavior of malicious code.'),
('002639','draft','2013-07-11','DISA FSO','policy','Incorporate the results from malicious code analysis into organizational incident response processes.','SI-03(10)(b)','N/A','Determine if: - the results from malicious code analysis are incorporated into organizational incident response processes. - the results from malicious code analysis are incorporated into organizational flaw remediation processes.'),
('002640','draft','2013-07-11','DISA FSO','policy','Incorporate the results from malicious code analysis into organizational flaw remediation processes.','SI-03(10)(b)','N/A','Determine if: - the results from malicious code analysis are incorporated into organizational incident response processes. - the results from malicious code analysis are incorporated into organizational flaw remediation processes.'),
('002641','draft','2013-07-11','DISA FSO','policy','Monitor the system to detect attacks and indicators of potential attacks in accordance with organization-defined monitoring objectives.','SI-04a.01','N/A','Determine if the system is monitored to detect attacks and indicators of potential attacks in accordance with [SI-04_ODP[01]; monitoring objectives to detect attacks and indicators of potential attacks on the system are defined].'),
('002642','draft','2013-07-11','DISA FSO','policy','Monitor the system to detect unauthorized local connections.','SI-04a.02','N/A','Determine if: - the system is monitored to detect unauthorized local connections. - the system is monitored to detect unauthorized network connections. - the system is monitored to detect unauthorized remote connections.'),
('002643','draft','2013-07-11','DISA FSO','policy','Monitor the system to detect unauthorized network connections.','SI-04a.02','N/A','Determine if: - the system is monitored to detect unauthorized local connections. - the system is monitored to detect unauthorized network connections. - the system is monitored to detect unauthorized remote connections.'),
('002644','draft','2013-07-11','DISA FSO','policy','Monitor the system to detect unauthorized remote connections.','SI-04a.02','N/A','Determine if: - the system is monitored to detect unauthorized local connections. - the system is monitored to detect unauthorized network connections. - the system is monitored to detect unauthorized remote connections.'),
('002645','draft','2013-07-11','DISA FSO','policy','Defines the techniques and methods to be used to identify unauthorized use of the system.','SI-04b.','N/A','Determine if unauthorized use of the system is identified through [SI-04_ODP[02]; techniques and methods used to identify unauthorized use of the system are defined].'),
('002646','draft','2013-07-11','DISA FSO','policy','Identify unauthorized use of the system through organization-defined techniques and methods.','SI-04b.','N/A','Determine if unauthorized use of the system is identified through [SI-04_ODP[02]; techniques and methods used to identify unauthorized use of the system are defined].'),
('002650','draft','2013-07-11','DISA FSO','policy','Defines the system monitoring information that is to be provided the organization-defined personnel or roles.','SI-04g.','N/A','Determine if [SI-04_ODP[03]; system monitoring information to be provided to personnel or roles is defined] is provided to [SI-04_ODP[04]; personnel or roles to whom system monitoring information is to be provided is/are defined] [SI-04_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {as needed; [SI-04_ODP[06]; a frequency for providing system monitoring to personnel or roles is defined (if selected)]}].'),
('002651','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles that are to be provided organization-defined system monitoring information.','SI-04g.','N/A','Determine if [SI-04_ODP[03]; system monitoring information to be provided to personnel or roles is defined] is provided to [SI-04_ODP[04]; personnel or roles to whom system monitoring information is to be provided is/are defined] [SI-04_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {as needed; [SI-04_ODP[06]; a frequency for providing system monitoring to personnel or roles is defined (if selected)]}].'),
('002652','draft','2013-07-11','DISA FSO','policy','Defines the frequency at which the organization will provide the organization-defined system monitoring information to organization-defined personnel or roles.','SI-04g.','N/A','Determine if [SI-04_ODP[03]; system monitoring information to be provided to personnel or roles is defined] is provided to [SI-04_ODP[04]; personnel or roles to whom system monitoring information is to be provided is/are defined] [SI-04_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {as needed; [SI-04_ODP[06]; a frequency for providing system monitoring to personnel or roles is defined (if selected)]}].'),
('002654','draft','2013-07-11','DISA FSO','policy','Provide organization-defined system monitoring information to organization-defined personnel or roles as needed, and/or per organization-defined frequency.','SI-04g.','N/A','Determine if [SI-04_ODP[03]; system monitoring information to be provided to personnel or roles is defined] is provided to [SI-04_ODP[04]; personnel or roles to whom system monitoring information is to be provided is/are defined] [SI-04_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {as needed; [SI-04_ODP[06]; a frequency for providing system monitoring to personnel or roles is defined (if selected)]}].'),
('002655','draft','2013-07-11','DISA FSO','policy','Connect individual intrusion detection tools into a system-wide intrusion detection system.','SI-04(01)','N/A','Determine if: - individual intrusion detection tools are connected to a system-wide intrusion detection system. - individual intrusion detection tools are configured into a system-wide intrusion detection system.'),
('002656','draft','2013-07-11','DISA FSO','technical','Configure individual intrusion detection tools into a system-wide intrusion detection system.','SI-04(01)','N/A','Determine if: - individual intrusion detection tools are connected to a system-wide intrusion detection system. - individual intrusion detection tools are configured into a system-wide intrusion detection system.'),
('002657','draft','2013-07-11','DISA FSO','policy','Employ automated tools to integrate intrusion detection tools into access control mechanisms.','SI-04(03)','N/A','Determine if: - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into access control mechanisms. - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into flow control mechanisms.'),
('002658','draft','2013-07-11','DISA FSO','policy','Employ automated tools to integrate intrusion detection tools into flow control mechanisms.','SI-04(03)','N/A','Determine if: - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into access control mechanisms. - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into flow control mechanisms.'),
('002659','draft','2013-07-11','DISA FSO','policy','Defines the frequency on which it will monitor inbound communications for unusual or unauthorized activities or conditions.','SI-04(04)(b)','N/A','Determine if: - inbound communications traffic is monitored [SI-04(04)_ODP[01]; the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[02]; unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined]. - outbound communications traffic is monitored [SI-04(04)_ODP[03]; the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[04]; unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined].'),
('002660','draft','2013-07-11','DISA FSO','policy','Defines the frequency on which it will monitor outbound communications for unusual or unauthorized activities or conditions.','SI-04(04)(b)','N/A','Determine if: - inbound communications traffic is monitored [SI-04(04)_ODP[01]; the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[02]; unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined]. - outbound communications traffic is monitored [SI-04(04)_ODP[03]; the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[04]; unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined].'),
('002661','draft','2013-07-11','DISA FSO','technical','Monitor inbound communications traffic per organization-defined frequency for organization-defined unusual or unauthorized activities or conditions.','SI-04(04)(b)','N/A','Determine if: - inbound communications traffic is monitored [SI-04(04)_ODP[01]; the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[02]; unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined]. - outbound communications traffic is monitored [SI-04(04)_ODP[03]; the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[04]; unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined].'),
('002662','draft','2013-07-11','DISA FSO','technical','Monitor outbound communications traffic per organization-defined frequency for organization-defined unusual or unauthorized activities or conditions.','SI-04(04)(b)','N/A','Determine if: - inbound communications traffic is monitored [SI-04(04)_ODP[01]; the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[02]; unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined]. - outbound communications traffic is monitored [SI-04(04)_ODP[03]; the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[04]; unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined].'),
('002663','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles to receive alerts when organization-defined indicators of compromise or potential compromise occur.','SI-04(05)','N/A','Determine if [SI-04(05)_ODP[01]; personnel or roles to be alerted when indications of compromise or potential compromise occur is/are defined] are alerted when system-generated [SI-04(05)_ODP[02]; compromise indicators are defined] occur.'),
('002664','draft','2013-07-11','DISA FSO','technical','Alert organization-defined personnel or roles when organization-defined compromise indicators generate the occurrence of a compromise or a potential compromise.','SI-04(05)','N/A','Determine if [SI-04(05)_ODP[01]; personnel or roles to be alerted when indications of compromise or potential compromise occur is/are defined] are alerted when system-generated [SI-04(05)_ODP[02]; compromise indicators are defined] occur.'),
('002665','draft','2013-07-11','DISA FSO','policy','Defines the encrypted communications traffic that is to be visible to organization-defined system monitoring tools.','SI-04(10)','N/A','Determine if provisions are made so that [SI-04(10)_ODP[01]; encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined] is visible to [SI-04(10)_ODP[02]; system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined].'),
('002666','draft','2013-07-11','DISA FSO','policy','Defines the system monitoring tools that will have visibility into organization-defined encrypted communications traffic.','SI-04(10)','N/A','Determine if provisions are made so that [SI-04(10)_ODP[01]; encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined] is visible to [SI-04(10)_ODP[02]; system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined].'),
('002667','draft','2013-07-11','DISA FSO','policy','Make provisions so that organization-defined encrypted communications traffic is visible to organization-defined system monitoring tools.','SI-04(10)','N/A','Determine if provisions are made so that [SI-04(10)_ODP[01]; encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined] is visible to [SI-04(10)_ODP[02]; system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined].'),
('002668','draft','2013-07-11','DISA FSO','policy','Defines the interior points within the system where outbound communications will be analyzed to discover anomalies.','SI-04(11)','N/A','Determine if: - outbound communications traffic at the external interfaces to the system is analyzed to discover anomalies. - outbound communications traffic at [SI-04(11)_ODP; interior points within the system where communications traffic is to be analyzed are defined] is analyzed to discover anomalies. '),
('002669','draft','2013-07-11','DISA FSO','policy','Use the traffic and event profiles in tuning system-monitoring devices.','SI-04(13)(c)','N/A','Determine if: - traffic profiles are used in tuning system-monitoring devices. - event profiles are used in tuning system-monitoring devices.'),
('002670','draft','2013-07-11','DISA FSO','policy','Defines the interior points within the system where outbound communications will be analyzed to detect covert exfiltration of information.','SI-04(18)','N/A','Determine if: - outbound communications traffic is analyzed at interfaces external to the system to detect covert exfiltration of information. - outbound communications traffic is analyzed at [SI-04(18)_ODP; interior points within the system where communications traffic is to be analyzed are defined] to detect covert exfiltration of information.'),
('002671','draft','2013-07-11','DISA FSO','policy','Analyze outbound communications traffic at the external interfaces of the system to detect covert exfiltration of information.','SI-04(18)','N/A','Determine if: - outbound communications traffic is analyzed at interfaces external to the system to detect covert exfiltration of information. - outbound communications traffic is analyzed at [SI-04(18)_ODP; interior points within the system where communications traffic is to be analyzed are defined] to detect covert exfiltration of information.'),
('002672','draft','2013-07-11','DISA FSO','policy','Analyze outbound communications traffic at organization-defined interior points within the system to detect covert exfiltration of information.','SI-04(18)','N/A','Determine if: - outbound communications traffic is analyzed at interfaces external to the system to detect covert exfiltration of information. - outbound communications traffic is analyzed at [SI-04(18)_ODP; interior points within the system where communications traffic is to be analyzed are defined] to detect covert exfiltration of information.'),
('002673','draft','2013-07-11','DISA FSO','policy','Defines the additional monitoring to be implemented for individuals identified as posing an increased level of risk.','SI-04(19)','N/A','Determine if [SI-04(19)_ODP[01]; additional monitoring of individuals who have been identified as posing an increased level of risk is defined] is implemented on individuals who have been identified by [SI-04(19)_ODP[02]; sources that identify individuals who pose an increased level of risk are defined] as posing an increased level of risk.'),
('002674','draft','2013-07-11','DISA FSO','policy','Defines the sources that may be used to identify individuals who pose an increased level of risk.','SI-04(19)','N/A','Determine if [SI-04(19)_ODP[01]; additional monitoring of individuals who have been identified as posing an increased level of risk is defined] is implemented on individuals who have been identified by [SI-04(19)_ODP[02]; sources that identify individuals who pose an increased level of risk are defined] as posing an increased level of risk.'),
('002675','draft','2013-07-11','DISA FSO','policy','Implement organization-defined additional monitoring of individuals who have been identified by organization-defined sources as posing an increased level of risk.','SI-04(19)','N/A','Determine if [SI-04(19)_ODP[01]; additional monitoring of individuals who have been identified as posing an increased level of risk is defined] is implemented on individuals who have been identified by [SI-04(19)_ODP[02]; sources that identify individuals who pose an increased level of risk are defined] as posing an increased level of risk.'),
('002676','draft','2013-07-11','DISA FSO','policy','Defines additional monitoring to be implemented for privileged users.','SI-04(20)','N/A','Determine if [SI-04(20)_ODP; additional monitoring of privileged users is defined] of privileged users is implemented.'),
('002677','draft','2013-07-11','DISA FSO','policy','Implement organization-defined additional monitoring of privileged users.','SI-04(20)','N/A','Determine if [SI-04(20)_ODP; additional monitoring of privileged users is defined] of privileged users is implemented.'),
('002678','draft','2013-07-11','DISA FSO','policy','Defines additional monitoring to be implemented for individuals during an organization-defined probationary period.','SI-04(21)','N/A','Determine if [SI-04(21)_ODP[01]; additional monitoring to be implemented on individuals during probationary periods is defined] of individuals is implemented during [SI-04(21)_ODP[02]; the probationary period of individuals is defined].'),
('002679','draft','2013-07-11','DISA FSO','policy','Defines the probationary period during which additional monitoring will be implemented for individuals.','SI-04(21)','N/A','Determine if [SI-04(21)_ODP[01]; additional monitoring to be implemented on individuals during probationary periods is defined] of individuals is implemented during [SI-04(21)_ODP[02]; the probationary period of individuals is defined].'),
('002680','draft','2013-07-11','DISA FSO','policy','Implement organization-defined additional monitoring of individuals during an organization-defined probationary period.','SI-04(21)','N/A','Determine if [SI-04(21)_ODP[01]; additional monitoring to be implemented on individuals during probationary periods is defined] of individuals is implemented during [SI-04(21)_ODP[02]; the probationary period of individuals is defined].'),
('002681','draft','2013-07-11','DISA FSO','policy','Defines the authorization or approval process for network services.','SI-04(22)(a)','N/A','Determine if network services that have not been authorized or approved by [SI-04(22)_ODP[01]; authorization or approval processes for network services are defined] are detected.'),
('002682','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles to be alerted when unauthorized or unapproved network services are detected.','SI-04(22)(a)','N/A','Determine if network services that have not been authorized or approved by [SI-04(22)_ODP[01]; authorization or approval processes for network services are defined] are detected.'),
('002683','draft','2013-07-11','DISA FSO','policy','Detect network services that have not been authorized or approved by the organization-defined authorization or approval processes.','SI-04(22)(a)','N/A','Determine if network services that have not been authorized or approved by [SI-04(22)_ODP[01]; authorization or approval processes for network services are defined] are detected.'),
('002684','draft','2013-07-11','DISA FSO','technical','Audit and/or alert organization-defined personnel when unauthorized network services are detected.','SI-04(22)(b)','N/A','Determine if [SI-04(22)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {audit; alert [SI-04(22)_ODP[03]; personnel or roles to be alerted upon the detection of network services that have not been authorized or approved by authorization or approval processes is/are defined (if selected)]}] is/are initiated when network services that have not been authorized or approved by authorization or approval processes are detected.'),
('002685','draft','2013-07-11','DISA FSO','policy','Defines the host-based monitoring mechanisms to be implemented at organization-defined system components.','SI-04(23)','N/A','Determine if [SI-04(23)_ODP[01]; host-based monitoring mechanisms to be implemented on system components are defined] are implemented on [SI-04(23)_ODP[02]; system components where host-based monitoring is to be implemented are defined].'),
('002686','draft','2013-07-11','DISA FSO','policy','Defines the system components at which organization-defined host-based monitoring mechanisms are to be implemented.','SI-04(23)','N/A','Determine if [SI-04(23)_ODP[01]; host-based monitoring mechanisms to be implemented on system components are defined] are implemented on [SI-04(23)_ODP[02]; system components where host-based monitoring is to be implemented are defined].'),
('002687','draft','2013-07-11','DISA FSO','policy','Implement organization-defined host-based monitoring mechanisms at organization-defined system components.','SI-04(23)','N/A','Determine if [SI-04(23)_ODP[01]; host-based monitoring mechanisms to be implemented on system components are defined] are implemented on [SI-04(23)_ODP[02]; system components where host-based monitoring is to be implemented are defined].'),
('002688','draft','2013-07-11','DISA FSO','technical','Discover indicators of compromise.','SI-04(24)','N/A','Determine if: - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are discovered. - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are collected. - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are distributed to [SI-04(24)_ODP[02]; personnel or roles to whom indicators of compromise are to be distributed is/are defined].'),
('002689','draft','2013-07-11','DISA FSO','technical','Collect indicators of compromise.','SI-04(24)','N/A','Determine if: - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are discovered. - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are collected. - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are distributed to [SI-04(24)_ODP[02]; personnel or roles to whom indicators of compromise are to be distributed is/are defined].'),
('002690','draft','2013-07-11','DISA FSO','technical','Distribute indicators of compromise provided by organization-defined sources, to organization-defined personnel or roles.','SI-04(24)','N/A','Determine if: - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are discovered. - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are collected. - indicators of compromise provided by [SI-04(24)_ODP[01]; sources that provide indicators of compromise are defined] are distributed to [SI-04(24)_ODP[02]; personnel or roles to whom indicators of compromise are to be distributed is/are defined].'),
('002692','draft','2013-07-11','DISA FSO','policy','Defines the external organizations from which it receives information system security alerts, advisories, and directives.','SI-05a.','N/A','Determine if system security alerts, advisories, and directives are received from [SI-05_ODP[01]; external organizations from whom system security alerts, advisories, and directives are to be received on an ongoing basis are defined] on an ongoing basis.'),
('002693','draft','2013-07-11','DISA FSO','policy','Defines the elements within the organization to whom the organization will disseminate security alerts, advisories, and directives.','SI-05c.','N/A','Determine if security alerts, advisories, and directives are disseminated to [SI-05_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[SI-05_ODP[03]; personnel or roles to whom security alerts, advisories, and directives are to be disseminated is/are defined (if selected)]; [SI-05_ODP[04]; elements within the organization to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]; [SI-05_ODP[05]; external organizations to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]}].'),
('002694','draft','2013-07-11','DISA FSO','policy','Defines the external organizations to which the organization will disseminate security alerts, advisories, and directives.','SI-05c.','N/A','Determine if security alerts, advisories, and directives are disseminated to [SI-05_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[SI-05_ODP[03]; personnel or roles to whom security alerts, advisories, and directives are to be disseminated is/are defined (if selected)]; [SI-05_ODP[04]; elements within the organization to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]; [SI-05_ODP[05]; external organizations to whom security alerts, advisories, and directives are to be disseminated are defined (if selected)]}].'),
('002695','draft','2013-07-11','DISA FSO','policy','Defines the security functions that require verification of correct operation.','SI-06a.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified to be operating correctly. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified to be operating correctly.'),
('002696','draft','2013-07-11','DISA FSO','technical','Verify correct operation of organization-defined security functions.','SI-06a.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified to be operating correctly. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified to be operating correctly.'),
('002697','draft','2013-07-11','DISA FSO','policy','Defines the frequency at which it will verify correct operation of organization-defined security functions.','SI-06b.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}]. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}].'),
('002698','draft','2013-07-11','DISA FSO','policy','Defines the system transitional states when the system will verify correct operation of organization-defined security functions.','SI-06b.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}]. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}].'),
('002699','draft','2013-07-11','DISA FSO','technical','Perform verification of the correct operation of organization-defined security functions: when the system is in an organization-defined transitional state; upon command by a user with appropriate privileges; and/or on an organization-defined frequency.',NULL,'N/A',NULL),
('002700','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles to be notified when security verification tests fail.','SI-06c.','N/A','Determine if: - [SI-06_ODP[06]; personnel or roles to be alerted of failed security and privacy verification tests is/are defined] is/are alerted to failed security verification tests. - [SI-06_ODP[06]; personnel or roles to be alerted of failed security and privacy verification tests is/are defined] is/are alerted to failed privacy verification tests.'),
('002701','draft','2013-07-11','DISA FSO','policy','Defines alternative action(s) to be taken when anomalies in the operation of organization-defined security functions are discovered.','SI-06d.','N/A','Determine if [SI-06_ODP[07]; one or more of the following PARAMETER VALUES is/are selected: {shut the system down; restart the system; [SI-06_ODP[08]; alternative action(s) to be performed when anomalies are discovered are defined (if selected)]}] is/are initiated when anomalies are discovered.'),
('002702','draft','2013-07-11','DISA FSO','technical','Shut the system down, restart the system, and/or initiate organization-defined alternative action(s) when anomalies in the operation of the organization-defined security functions are discovered.','SI-06d.','N/A','Determine if [SI-06_ODP[07]; one or more of the following PARAMETER VALUES is/are selected: {shut the system down; restart the system; [SI-06_ODP[08]; alternative action(s) to be performed when anomalies are discovered are defined (if selected)]}] is/are initiated when anomalies are discovered.'),
('002703','draft','2013-07-11','DISA FSO','policy','Defines the software, firmware, and information which will be subjected to integrity verification tools to detect unauthorized changes.',NULL,'N/A',NULL),
('002704','draft','2013-07-11','DISA FSO','policy','Employ integrity verification tools to detect unauthorized changes to organization-defined software, firmware, and information.','SI-07a.','N/A','Determine if: - integrity verification tools are employed to detect unauthorized changes to [SI-07_ODP[01]; software requiring integrity verification tools to be employed to detect unauthorized changes is defined]. - integrity verification tools are employed to detect unauthorized changes to [SI-07_ODP[02]; firmware requiring integrity verification tools to be employed to detect unauthorized changes is defined]. - integrity verification tools are employed to detect unauthorized changes to [SI-07_ODP[03]; information requiring integrity verification tools to be employed to detect unauthorized changes is defined].'),
('002705','draft','2013-07-11','DISA FSO','policy','Defines the software on which integrity checks will be performed.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002706','draft','2013-07-11','DISA FSO','policy','Defines the firmware on which integrity checks will be performed.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002707','draft','2013-07-11','DISA FSO','policy','Defines the information on which integrity checks will be performed.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002708','draft','2013-07-11','DISA FSO','policy','Defines the transitional state or security-relevant events when performing integrity checks on software, firmware, and information.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002709','draft','2013-07-11','DISA FSO','policy','Defines the frequency at which integrity checks of software, firmware, and information will be performed.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002710','draft','2013-07-11','DISA FSO','technical','Perform an integrity check of organization-defined software at startup, at organization-defined transitional states or security-relevant events, or on an organization-defined frequency.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002711','draft','2013-07-11','DISA FSO','technical','Perform an integrity check of organization-defined firmware at startup, at organization-defined transitional states or security-relevant events, or on an organization-defined frequency.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002712','draft','2013-07-11','DISA FSO','technical','Perform an integrity check of organization-defined information at startup, at organization-defined transitional states or security-relevant events, or on an organization-defined frequency.','SI-07(01)','N/A','Determine if: - an integrity check of [SI-07(01)_ODP[01]; software on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[03]; transitional states or security-relevant events requiring integrity checks (on software) are defined (if selected)]; [SI-07(01)_ODP[04]; frequency with which to perform an integrity check (on software) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[05]; firmware on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[06]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[07]; transitional states or security-relevant events requiring integrity checks (on firmware) are defined (if selected)]; [SI-07(01)_ODP[08]; frequency with which to perform an integrity check (on firmware) is defined (if selected)]}]. - an integrity check of [SI-07(01)_ODP[09]; information on which an integrity check is to be performed is defined] is performed [SI-07(01)_ODP[10]; one or more of the following PARAMETER VALUES is/are selected: {at startup; at [SI-07(01)_ODP[11]; transitional states or security-relevant events requiring integrity checks (of information) are defined (if selected)]; [SI-07(01)_ODP[12]; frequency with which to perform an integrity check (of information) is defined (if selected)]}].'),
('002713','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles to be notified when discrepancies are discovered during integrity verification.','SI-07(02)','N/A','Determine if automated tools that provide notification to [SI-07(02)_ODP; personnel or roles to whom notification is to be provided upon discovering discrepancies during integrity verification is/are defined] upon discovering discrepancies during integrity verification are employed.'),
('002714','draft','2013-07-11','DISA FSO','policy','Defines the controls that are to be employed when integrity violations are discovered.','SI-07(05)','N/A','Determine if [SI-07(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {shut down the system; restart the system; implement [SI-07(05)_ODP[02]; controls to be implemented automatically when integrity violations are discovered are defined (if selected)]}] are automatically performed when integrity violations are discovered.'),
('002715','draft','2013-07-11','DISA FSO','technical','Automatically shut the system down, restart the system, and/or implement organization-defined controls when integrity violations are discovered.','SI-07(05)','N/A','Determine if [SI-07(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {shut down the system; restart the system; implement [SI-07(05)_ODP[02]; controls to be implemented automatically when integrity violations are discovered are defined (if selected)]}] are automatically performed when integrity violations are discovered.'),
('002716','draft','2013-07-11','DISA FSO','technical','Implement cryptographic mechanisms to detect unauthorized changes to software.','SI-07(06)','N/A','Determine if: - cryptographic mechanisms are implemented to detect unauthorized changes to software. - cryptographic mechanisms are implemented to detect unauthorized changes to firmware. - cryptographic mechanisms are implemented to detect unauthorized changes to information.'),
('002717','draft','2013-07-11','DISA FSO','technical','Implement cryptographic mechanisms to detect unauthorized changes to firmware.','SI-07(06)','N/A','Determine if: - cryptographic mechanisms are implemented to detect unauthorized changes to software. - cryptographic mechanisms are implemented to detect unauthorized changes to firmware. - cryptographic mechanisms are implemented to detect unauthorized changes to information.'),
('002718','draft','2013-07-11','DISA FSO','technical','Implement cryptographic mechanisms to detect unauthorized changes to information.','SI-07(06)','N/A','Determine if: - cryptographic mechanisms are implemented to detect unauthorized changes to software. - cryptographic mechanisms are implemented to detect unauthorized changes to firmware. - cryptographic mechanisms are implemented to detect unauthorized changes to information.'),
('002719','draft','2013-07-11','DISA FSO','policy','Defines the unauthorized security-relevant changes to the system that are to be incorporated into the organizational incident response capability.','SI-07(07)','N/A','Determine if the detection of [SI-07(07)_ODP; security-relevant changes to the system are defined] are incorporated into the organizational incident response capability.'),
('002720','draft','2013-07-11','DISA FSO','policy','Incorporate the detection of organization-defined security-relevant unauthorized changes into the organizational incident response capability.','SI-07(07)','N/A','Determine if the detection of [SI-07(07)_ODP; security-relevant changes to the system are defined] are incorporated into the organizational incident response capability.'),
('002721','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles that are to be alerted when a potential integrity violation is detected.','SI-07(08)','N/A','Determine if: - the capability to audit an event upon the detection of a potential integrity violation is provided. - [SI-07(08)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {generate an audit record; alert current user; alert [SI-07(08)_ODP[02]; personnel or roles to be alerted upon the detection of a potential integrity violation is/are defined (if selected)]; [SI-07(08)_ODP[03]; other actions to be taken upon the detection of a potential integrity violation are defined (if selected)]}] is/are initiated upon the detection of a potential integrity violation.'),
('002722','draft','2013-07-11','DISA FSO','policy','Defines other actions that can be taken when a potential integrity violation is detected.','SI-07(08)','N/A','Determine if: - the capability to audit an event upon the detection of a potential integrity violation is provided. - [SI-07(08)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {generate an audit record; alert current user; alert [SI-07(08)_ODP[02]; personnel or roles to be alerted upon the detection of a potential integrity violation is/are defined (if selected)]; [SI-07(08)_ODP[03]; other actions to be taken upon the detection of a potential integrity violation are defined (if selected)]}] is/are initiated upon the detection of a potential integrity violation.'),
('002723','draft','2013-07-11','DISA FSO','technical','Upon detection of a potential integrity violation, provides the capability to audit the event.','SI-07(08)','N/A','Determine if: - the capability to audit an event upon the detection of a potential integrity violation is provided. - [SI-07(08)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {generate an audit record; alert current user; alert [SI-07(08)_ODP[02]; personnel or roles to be alerted upon the detection of a potential integrity violation is/are defined (if selected)]; [SI-07(08)_ODP[03]; other actions to be taken upon the detection of a potential integrity violation are defined (if selected)]}] is/are initiated upon the detection of a potential integrity violation.'),
('002724','draft','2013-07-11','DISA FSO','technical','Upon detection of a potential integrity violation, initiate one or more of the following actions: generate an audit record; alert the current user; alert organization-defined personnel or roles; and/or organization-defined other actions.','SI-07(08)','N/A','Determine if: - the capability to audit an event upon the detection of a potential integrity violation is provided. - [SI-07(08)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {generate an audit record; alert current user; alert [SI-07(08)_ODP[02]; personnel or roles to be alerted upon the detection of a potential integrity violation is/are defined (if selected)]; [SI-07(08)_ODP[03]; other actions to be taken upon the detection of a potential integrity violation are defined (if selected)]}] is/are initiated upon the detection of a potential integrity violation.'),
('002725','draft','2013-07-11','DISA FSO','policy','Defines the system component which will have the integrity of the boot process verified.','SI-07(09)','N/A','Determine if the integrity of the boot process of [SI-07(09)_ODP; system components requiring integrity verification of the boot process are defined] is verified.'),
('002726','draft','2013-07-11','DISA FSO','technical','Verify the integrity of the boot process of organization-defined system components.','SI-07(09)','N/A','Determine if the integrity of the boot process of [SI-07(09)_ODP; system components requiring integrity verification of the boot process are defined] is verified.'),
('002727','draft','2013-07-11','DISA FSO','policy','Defines the mechanisms to be implemented to protect the integrity of the boot firmware in organization-defined system components.','SI-07(10)','N/A','Determine if [SI-07(10)_ODP[01]; mechanisms to be implemented to protect the integrity of boot firmware in system components are defined] are implemented to protect the integrity of boot firmware in [SI-07(10)_ODP[02]; system components requiring mechanisms to protect the integrity of boot firmware are defined].'),
('002728','draft','2013-07-11','DISA FSO','policy','Defines the system components on which organization-defined mechanisms will be implemented to protect the integrity of the boot firmware.','SI-07(10)','N/A','Determine if [SI-07(10)_ODP[01]; mechanisms to be implemented to protect the integrity of boot firmware in system components are defined] are implemented to protect the integrity of boot firmware in [SI-07(10)_ODP[02]; system components requiring mechanisms to protect the integrity of boot firmware are defined].'),
('002729','draft','2013-07-11','DISA FSO','technical','Implement organization-defined mechanisms to protect the integrity of boot firmware in organization-defined system components.','SI-07(10)','N/A','Determine if [SI-07(10)_ODP[01]; mechanisms to be implemented to protect the integrity of boot firmware in system components are defined] are implemented to protect the integrity of boot firmware in [SI-07(10)_ODP[02]; system components requiring mechanisms to protect the integrity of boot firmware are defined].'),
('002732','draft','2013-07-11','DISA FSO','policy','Defines the user-installed software that is to have its integrity verified prior to execution.','SI-07(12)','N/A','Determine if the integrity of [SI-07(12)_ODP; user-installed software requiring integrity verification prior to execution is defined] is verified prior to execution.'),
('002733','draft','2013-07-11','DISA FSO','policy','Require that the integrity of organization-defined user-installed software be verified prior to execution.','SI-07(12)','N/A','Determine if the integrity of [SI-07(12)_ODP; user-installed software requiring integrity verification prior to execution is defined] is verified prior to execution.'),
('002739','draft','2013-07-11','DISA FSO','policy','Defines the software or firmware components on which cryptographic mechanisms are to be implemented to support authentication prior to installation.','SI-07(15)','N/A','Determine if cryptographic mechanisms are implemented to authenticate [SI-07(15)_ODP; software or firmware components to be authenticated by cryptographic mechanisms prior to installation are defined] prior to installation.'),
('002740','draft','2013-07-11','DISA FSO','technical','Implement cryptographic mechanisms to authenticate organization-defined software or firmware components prior to installation.','SI-07(15)','N/A','Determine if cryptographic mechanisms are implemented to authenticate [SI-07(15)_ODP; software or firmware components to be authenticated by cryptographic mechanisms prior to installation are defined] prior to installation.'),
('002741','draft','2013-07-11','DISA FSO','policy','Employ spam protection mechanisms at system entry points to detect and take action on unsolicited messages.','SI-08a.','N/A','Determine if: - spam protection mechanisms are employed at system entry points to detect unsolicited messages. - spam protection mechanisms are employed at system exit points to detect unsolicited messages. - spam protection mechanisms are employed at system entry points to act on unsolicited messages. - spam protection mechanisms are employed at system exit points to act on unsolicited messages.'),
('002742','draft','2013-07-11','DISA FSO','policy','Employ spam protection mechanisms at system exit points to detect and take action on unsolicited messages.','SI-08a.','N/A','Determine if: - spam protection mechanisms are employed at system entry points to detect unsolicited messages. - spam protection mechanisms are employed at system exit points to detect unsolicited messages. - spam protection mechanisms are employed at system entry points to act on unsolicited messages. - spam protection mechanisms are employed at system exit points to act on unsolicited messages.'),
('002743','draft','2013-07-11','DISA FSO','technical','Implement spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic.','SI-08(03)','N/A','Determine if spam protection mechanisms with a learning capability are implemented to more effectively identify legitimate communications traffic.'),
('002744','draft','2013-07-11','DISA FSO','policy','Defines the inputs on which the system is to conduct validity checks.','SI-10','N/A','Determine if the validity of the [SI-10_ODP; information inputs to the system requiring validity checks are defined] is checked.'),
('002745','draft','2013-07-11','DISA FSO','policy','Defines the inputs defined in base control (SI-10), which provide a manual override capability for input validation.','SI-10(01)(a)','N/A','Determine if a manual override capability for the validation of [SI-10_ODP; information inputs to the system requiring validity checks are defined] is provided.'),
('002746','draft','2013-07-11','DISA FSO','technical','Provide a manual override capability for input validation of organization-defined inputs defined in base control (SI-10).','SI-10(01)(a)','N/A','Determine if a manual override capability for the validation of [SI-10_ODP; information inputs to the system requiring validity checks are defined] is provided.'),
('002747','draft','2013-07-11','DISA FSO','policy','Defines the individuals who have the authorization to use the manual override capability for input validation.','SI-10(01)(b)','N/A','Determine if the use of the manual override capability is restricted to only [SI-10(01)_ODP; authorized individuals who can use the manual override capability are defined].'),
('002748','draft','2013-07-11','DISA FSO','technical','Restrict the use of the manual override capability to only organization-defined authorized individuals.','SI-10(01)(b)','N/A','Determine if the use of the manual override capability is restricted to only [SI-10(01)_ODP; authorized individuals who can use the manual override capability are defined].'),
('002749','draft','2013-07-11','DISA FSO','technical','Audit the use of the manual override capability.','SI-10(01)(c)','N/A','Determine if the use of the manual override capability is audited.'),
('002750','draft','2013-07-11','DISA FSO','policy','Defines the time-period within which input validation errors are to be reviewed.','SI-10(02)','N/A','Determine if: - input validation errors are reviewed within [SI-10(02)_ODP[01]; the time period within which input validation errors are to be reviewed is defined]. - input validation errors are resolved within [SI-10(02)_ODP[02]; the time period within which input validation errors are to be resolved is defined].'),
('002751','draft','2013-07-11','DISA FSO','policy','Defines the time-period within which input validation errors are to be resolved.','SI-10(02)','N/A','Determine if: - input validation errors are reviewed within [SI-10(02)_ODP[01]; the time period within which input validation errors are to be reviewed is defined]. - input validation errors are resolved within [SI-10(02)_ODP[02]; the time period within which input validation errors are to be resolved is defined].'),
('002752','draft','2013-07-11','DISA FSO','policy','Review input validation errors within an organization-defined time period.','SI-10(02)','N/A','Determine if: - input validation errors are reviewed within [SI-10(02)_ODP[01]; the time period within which input validation errors are to be reviewed is defined]. - input validation errors are resolved within [SI-10(02)_ODP[02]; the time period within which input validation errors are to be resolved is defined].'),
('002753','draft','2013-07-11','DISA FSO','policy','Resolve input validation errors within an organization-defined time period.','SI-10(02)','N/A','Determine if: - input validation errors are reviewed within [SI-10(02)_ODP[01]; the time period within which input validation errors are to be reviewed is defined]. - input validation errors are resolved within [SI-10(02)_ODP[02]; the time period within which input validation errors are to be resolved is defined].'),
('002754','draft','2013-07-11','DISA FSO','policy','Verify that the system behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.','SI-10(03)','N/A','Determine if: - the system behaves in a predictable manner when invalid inputs are received. - the system behaves in a documented manner when invalid inputs are received.'),
('002755','draft','2013-07-11','DISA FSO','policy','Account for timing interactions among system components in determining appropriate responses for invalid inputs.','SI-10(04)','N/A','Determine if timing interactions among system components are accounted for in determining appropriate responses for invalid inputs.'),
('002756','draft','2013-07-11','DISA FSO','policy','Defines the trusted sources to which the usage of information inputs will be restricted (e.g., whitelisting).','SI-10(05)','N/A','Determine if the use of information inputs is restricted to [SI-10(05)_ODP[01]; trusted sources to which the use of information inputs is to be restricted are defined] and/or [SI-10(05)_ODP[02]; formats to which the use of information inputs is to be restricted are defined].'),
('002757','draft','2013-07-11','DISA FSO','policy','Defines the acceptable formats to which information inputs are restricted.','SI-10(05)','N/A','Determine if the use of information inputs is restricted to [SI-10(05)_ODP[01]; trusted sources to which the use of information inputs is to be restricted are defined] and/or [SI-10(05)_ODP[02]; formats to which the use of information inputs is to be restricted are defined].'),
('002758','draft','2013-07-11','DISA FSO','policy','Restrict the use of information inputs to organization-defined trusted sources and/or organization-defined formats.','SI-10(05)','N/A','Determine if the use of information inputs is restricted to [SI-10(05)_ODP[01]; trusted sources to which the use of information inputs is to be restricted are defined] and/or [SI-10(05)_ODP[02]; formats to which the use of information inputs is to be restricted are defined].'),
('002759','draft','2013-07-11','DISA FSO','policy','Defines the personnel or roles to whom error messages are to be revealed.','SI-11b.','N/A','Determine if error messages are revealed only to [SI-11_ODP; personnel or roles to whom error messages are to be revealed is/are defined].'),
('002760','draft','2013-07-11','DISA FSO','policy','Determines mean time to failure (MTTF) for organization-defined system components in specific environments of operation.','SI-13a.','N/A','Determine if mean time to failure (MTTF) is determined for [SI-13_ODP[01]; system components for which mean time to failure (MTTF) should be determined are defined] in specific environments of operation.'),
('002761','draft','2013-07-11','DISA FSO','policy','Defines the system components in specific environments of operation for which the mean time to failure (MTTF) is to be determined.','SI-13a.','N/A','Determine if mean time to failure (MTTF) is determined for [SI-13_ODP[01]; system components for which mean time to failure (MTTF) should be determined are defined] in specific environments of operation.'),
('002762','draft','2013-07-11','DISA FSO','policy','Defines the mean time to failure (MTTF) substitution criteria to be employed as a means to determine the need to exchange active and standby components.','SI-13b.','N/A','Determine if substitute system components and a means to exchange active and standby components are provided in accordance with [SI-13_ODP[02]; mean time to failure (MTTF) substitution criteria to be used as a means to exchange active and standby components are defined].'),
('002763','draft','2013-07-11','DISA FSO','policy','Provide a means to exchange active and standby components in accordance with the organization-defined mean time to failure (MTTF) substitution criteria.','SI-13b.','N/A','Determine if substitute system components and a means to exchange active and standby components are provided in accordance with [SI-13_ODP[02]; mean time to failure (MTTF) substitution criteria to be used as a means to exchange active and standby components are defined].'),
('002764','draft','2013-07-11','DISA FSO','policy','Defines non-persistent system components and services to be implemented.','SI-14','N/A','Determine if: - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] that are initiated in a known state are implemented. - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] are terminated [SI-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {upon end of session of use; [SI-14_ODP[03]; the frequency at which to terminate non-persistent components and services that are initiated in a known state is defined (if selected)]}].'),
('002765','draft','2013-07-11','DISA FSO','policy','Defines the frequency at which the organization-defined non-persistent system components and services will be terminated.','SI-14','N/A','Determine if: - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] that are initiated in a known state are implemented. - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] are terminated [SI-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {upon end of session of use; [SI-14_ODP[03]; the frequency at which to terminate non-persistent components and services that are initiated in a known state is defined (if selected)]}].'),
('002766','draft','2013-07-11','DISA FSO','policy','Implement organization-defined non-persistence system components and services that are initiated in a known state.','SI-14','N/A','Determine if: - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] that are initiated in a known state are implemented. - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] are terminated [SI-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {upon end of session of use; [SI-14_ODP[03]; the frequency at which to terminate non-persistent components and services that are initiated in a known state is defined (if selected)]}].'),
('002767','draft','2013-07-11','DISA FSO','policy','Implement organization-defined non-persistence system components and services that are terminated upon end of session of use and/or periodically at an organization-defined frequency.','SI-14','N/A','Determine if: - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] that are initiated in a known state are implemented. - non-persistent [SI-14_ODP[01]; non-persistent system components and services to be implemented are defined] are terminated [SI-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {upon end of session of use; [SI-14_ODP[03]; the frequency at which to terminate non-persistent components and services that are initiated in a known state is defined (if selected)]}].'),
('002768','draft','2013-07-11','DISA FSO','policy','Defines the trusted sources from which it obtains software and data employed during the refreshing of non-persistent system components and services.','SI-14(01)','N/A','Determine if the software and data employed during system component and service refreshes are obtained from [SI-14(01)_ODP; trusted sources to obtain software and data for system component and service refreshes are defined].'),
('002769','draft','2013-07-11','DISA FSO','policy','Obtain software and data employed during non-persistent system component and service refreshes are obtained from organization-defined trusted sources.','SI-14(01)','N/A','Determine if the software and data employed during system component and service refreshes are obtained from [SI-14(01)_ODP; trusted sources to obtain software and data for system component and service refreshes are defined].'),
('002770','draft','2013-07-11','DISA FSO','policy','Defines the software programs and/or applications from which the system is to validate the information output to ensure the information is consistent with expected content.','SI-15','N/A','Determine if information output from [SI-15_ODP; software programs and/or applications whose information output requires validation are defined] is validated to ensure that the information is consistent with the expected content.'),
('002771','draft','2013-07-11','DISA FSO','technical','Validate information output from organization-defined software programs and/or applications to ensure that the information is consistent with the expected content.','SI-15','N/A','Determine if information output from [SI-15_ODP; software programs and/or applications whose information output requires validation are defined] is validated to ensure that the information is consistent with the expected content.'),
('002773','draft','2013-07-11','DISA FSO','policy','Defines the fail-safe procedures to be implemented when organization-defined failure conditions occur.','SI-17','N/A','Determine if [SI-17_ODP[01]; fail-safe procedures associated with failure conditions are defined] are implemented when [SI-17_ODP[02]; a list of failure conditions requiring fail-safe procedures is defined] occur.'),
('002774','draft','2013-07-11','DISA FSO','policy','Defines the failure conditions which, when they occur, will result in the information system implementing organization-defined fail-safe procedures.','SI-17','N/A','Determine if [SI-17_ODP[01]; fail-safe procedures associated with failure conditions are defined] are implemented when [SI-17_ODP[02]; a list of failure conditions requiring fail-safe procedures is defined] occur.'),
('002775','draft','2013-07-11','DISA FSO','technical','Implement organization-defined fail-safe procedures when organization-defined failure conditions occur.','SI-17','N/A','Determine if [SI-17_ODP[01]; fail-safe procedures associated with failure conditions are defined] are implemented when [SI-17_ODP[02]; a list of failure conditions requiring fail-safe procedures is defined] occur.'),
('002776','draft','2013-07-12','DISA FSO','policy','Defines the personnel or roles to whom the organization-level; mission/business process-level; and/or system-level incident response policy is disseminated.','IR-01a.','N/A','Determine if: - an incident response policy is developed and documented. - the incident response policy is disseminated to [IR-01_ODP[01]; personnel or roles to whom the incident response policy is to be disseminated is/are defined].'),
('002777','draft','2013-07-12','DISA FSO','policy','Defines the personnel or roles to whom the incident response procedures are disseminated.','IR-01a.02','N/A','Determine if: - incident response procedures to facilitate the implementation of the incident response policy and associated incident response controls are developed and documented. - the incident response procedures are disseminated to [IR-01_ODP[02]; personnel or roles to whom the incident response procedures are to be disseminated is/are defined].'),
('002778','draft','2013-07-12','DISA FSO','policy','Defines the time period in which system users who assume an incident response role or responsibility receive incident response training.','IR-02a.01','N/A','Determine if incident response training is provided to system users consistent with assigned roles and responsibilities within [IR-02_ODP[01]; a time period within which incident response training is to be provided to system users assuming an incident response role or responsibility is defined] of assuming an incident response role or responsibility or acquiring system access.'),
('002779','draft','2013-07-12','DISA FSO','policy','Provide incident response training to system users consistent with assigned roles and responsibilities when required by system changes.','IR-02a.02','N/A','Determine if incident response training is provided to system users consistent with assigned roles and responsibilities when required by system changes.'),
('002780','draft','2013-07-12','DISA FSO','policy','Coordinate incident response testing with organizational elements responsible for related plans.','IR-03(02)','N/A','Determine if incident response testing is coordinated with organizational elements responsible for related plans.'),
('002781','draft','2013-07-12','DISA FSO','policy','Defines the system components for dynamic reconfiguration as part of the incident response capability.','IR-04(02)','N/A','Determine if [IR-04(02)_ODP[01]; types of dynamic reconfiguration for system components are defined] for [IR-04(02)_ODP[02]; system components that require dynamic reconfiguration are defined] are included as part of the incident response capability.'),
('002782','draft','2013-07-12','DISA FSO','policy','Implement an incident handling capability for incidents involving insider threats.','IR-04(06)','N/A','Determine if an incident handling capability is implemented for incidents involving insider threats.'),
('002785','draft','2013-07-12','DISA FSO','policy','Coordinate with organization-defined external organizations to correlate and share organization-defined incident information to achieve a cross-organization perspective on incident awareness and more effective incident responses.','IR-04(08)','N/A','Determine if there is coordination with [IR-04(08)_ODP[01]; external organizations with whom organizational incident information is to be coordinated and shared are defined] to correlate and share [IR-04(08)_ODP[02]; incident information to be correlated and shared with organization-defined external organizations are defined] to achieve a cross-organization perspective on incident awareness and more effective incident responses.'),
('002786','draft','2013-07-12','DISA FSO','policy','Defines external organizations with which to correlate and share organization-defined incident information.','IR-04(08)','N/A','Determine if there is coordination with [IR-04(08)_ODP[01]; external organizations with whom organizational incident information is to be coordinated and shared are defined] to correlate and share [IR-04(08)_ODP[02]; incident information to be correlated and shared with organization-defined external organizations are defined] to achieve a cross-organization perspective on incident awareness and more effective incident responses.'),
('002787','draft','2013-07-12','DISA FSO','policy','Defines incident information to correlate and share with organization-defined external organizations.','IR-04(08)','N/A','Determine if there is coordination with [IR-04(08)_ODP[01]; external organizations with whom organizational incident information is to be coordinated and shared are defined] to correlate and share [IR-04(08)_ODP[02]; incident information to be correlated and shared with organization-defined external organizations are defined] to achieve a cross-organization perspective on incident awareness and more effective incident responses.'),
('002788','draft','2013-07-12','DISA FSO','policy','Employ organization-defined dynamic response capabilities to effectively respond to incidents.','IR-04(09)','N/A','Determine if [IR-04(09)_ODP; dynamic response capabilities to be employed to respond to incidents are defined] are employed to respond to incidents.'),
('002789','draft','2013-07-12','DISA FSO','policy','Defines dynamic response capabilities to effectively respond to incidents.','IR-04(09)','N/A','Determine if [IR-04(09)_ODP; dynamic response capabilities to be employed to respond to incidents are defined] are employed to respond to incidents.'),
('002790','draft','2013-07-12','DISA FSO','policy','Coordinate incident handling activities involving supply chain events with other organizations involved in the supply chain.','IR-04(10)','N/A','Determine if incident handling activities involving supply chain events are coordinated with other organizations involved in the supply chain.'),
('002791','draft','2013-07-12','DISA FSO','policy','Defines authorities to whom incident information is reported.','IR-06b.','N/A','Determine if incident information is reported to [IR-06_ODP[02]; authorities to whom incident information is to be reported are defined].'),
('002792','draft','2013-07-12','DISA FSO','policy','Defines personnel or roles to whom system vulnerabilities associated with reported incident information are reported.','IR-06(02)','N/A','Determine if system vulnerabilities associated with reported incidents are reported to [IR-06(02)_ODP; personnel or roles to whom system vulnerabilities associated with reported incidents are reported to is/are defined].'),
('002793','draft','2013-07-12','DISA FSO','policy','Provide incident information to other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.','IR-06(03)','N/A','Determine if incident information is provided to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.'),
('002794','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan.',NULL,'N/A',NULL),
('002795','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that provides the organization with a roadmap for implementing its incident response capability.','IR-08a.01','N/A','Determine if an incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability.'),
('002796','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that describes the structure and organization of the incident response capability.','IR-08a.02','N/A','Determine if an incident response plan is developed that describes the structure and organization of the incident response capability.'),
('002797','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that provides a high-level approach for how the incident response capability fits into the overall organization.','IR-08a.03','N/A','Determine if an incident response plan is developed that provides a high-level approach for how the incident response capability fits into the overall organization.'),
('002798','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that meets the unique requirements of the organization, which relate to mission, size, structure, and functions.','IR-08a.04','N/A','Determine if an incident response plan is developed that meets the unique requirements of the organization with regard to mission, size, structure, and functions.'),
('002799','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that defines reportable incidents.','IR-08a.05','N/A','Determine if an incident response plan is developed that defines reportable incidents.'),
('002800','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that provides metrics for measuring the incident response capability within the organization.','IR-08a.06','N/A','Determine if an incident response plan is developed that provides metrics for measuring the incident response capability within the organization.'),
('002801','draft','2013-07-12','DISA FSO','policy','Develop an incident response plan that defines the resources and management support needed to effectively maintain and mature an incident response capability.','IR-08a.07','N/A','Determine if an incident response plan is developed that defines the resources and management support needed to effectively maintain and mature an incident response capability.'),
('002802','draft','2013-07-12','DISA FSO','policy','Defines personnel or roles to review and approve the incident response plan.','IR-08a.09','N/A','Determine if an incident response plan is developed that is reviewed and approved by [IR-08_ODP[01]; personnel or roles that review and approve the incident response plan is/are identified] [IR-08_ODP[02]; the frequency at which to review and approve the incident response plan is defined].'),
('002803','draft','2013-07-12','DISA FSO','policy','Defines incident response personnel (identified by name and/or by role) and organizational elements to whom incident response plan changes will be communicated.','IR-08d.','N/A','Determine if: - incident response plan changes are communicated to [IR-08_ODP[06]; incident response personnel (identified by name and/or by role) to whom changes to the incident response plan is/are communicated are defined]. - incident response plan changes are communicated to [IR-08_ODP[07]; organizational elements to which changes to the incident response plan are communicated are defined].'),
('002804','draft','2013-07-12','DISA FSO','policy','Protect the incident response plan from unauthorized disclosure and modification.','IR-08e.','N/A','Determine if: - the incident response plan is protected from unauthorized disclosure. - the incident response plan is protected from unauthorized modification.'),
('002805','draft','2013-07-12','DISA FSO','policy','Respond to information spills by identifying the specific information involved in the system contamination.','IR-09b.','N/A','Determine if the specific information involved in the system contamination is identified in response to information spills.'),
('002806','draft','2013-07-12','DISA FSO','policy','Respond to information spills by alerting organization-defined personnel or roles of the information spill using a method of communication not associated with the spill.','IR-09c.','N/A','Determine if [IR-09_ODP[02]; personnel or roles to be alerted of the information spill using a method of communication not associated with the spill is/are defined] is/are alerted of the information spill using a method of communication not associated with the spill.'),
('002807','draft','2013-07-12','DISA FSO','policy','Defines the personnel or roles to be alerted of information spills using a method of communication not associated with the spill.','IR-09c.','N/A','Determine if [IR-09_ODP[02]; personnel or roles to be alerted of the information spill using a method of communication not associated with the spill is/are defined] is/are alerted of the information spill using a method of communication not associated with the spill.'),
('002808','draft','2013-07-12','DISA FSO','policy','Respond to information spills by isolating the contaminated system or system component.','IR-09c.','N/A','Determine if [IR-09_ODP[02]; personnel or roles to be alerted of the information spill using a method of communication not associated with the spill is/are defined] is/are alerted of the information spill using a method of communication not associated with the spill.'),
('002809','draft','2013-07-12','DISA FSO','policy','Respond to information spills by eradicating the information from the contaminated system or component.','IR-09e.','N/A','Determine if the information is eradicated from the contaminated system or component in response to information spills.'),
('002810','draft','2013-07-12','DISA FSO','policy','Respond to information spills by identifying other systems or system components that may have been subsequently contaminated.','IR-09f.','N/A','Determine if other systems or system components that may have been subsequently contaminated are identified in response to information spills.'),
('002811','draft','2013-07-12','DISA FSO','policy','Respond to information spills by performing additional organization-defined actions.','IR-09g.','N/A','Determine if [IR-09_ODP[03]; actions to be performed are defined] are performed in response to information spills.'),
('002812','draft','2013-07-12','DISA FSO','policy','Defines additional actions required to respond to information spills.','IR-09g.','N/A','Determine if [IR-09_ODP[03]; actions to be performed are defined] are performed in response to information spills.'),
('002816','draft','2013-07-12','DISA FSO','policy','Provide information spillage response training according to an organization-defined frequency.','IR-09(02)','N/A','Determine if information spillage response training is provided [IR-09(02)_ODP; frequency at which to provide information spillage response training is defined].'),
('002817','draft','2013-07-12','DISA FSO','policy','Defines the frequency with which to provide information spillage response training.','IR-09(02)','N/A','Determine if information spillage response training is provided [IR-09(02)_ODP; frequency at which to provide information spillage response training is defined].'),
('002818','draft','2013-07-12','DISA FSO','policy','Implement organization-defined procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.','IR-09(03)','N/A','Determine if [IR-09(03)_ODP; procedures to be implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions are defined] are implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.'),
('002819','draft','2013-07-12','DISA FSO','policy','Defines the procedures to be implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.','IR-09(03)','N/A','Determine if [IR-09(03)_ODP; procedures to be implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions are defined] are implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.'),
('002820','draft','2013-07-12','DISA FSO','policy','Employ organization-defined controls for personnel exposed to information not within assigned access authorizations.','IR-09(04)','N/A','Determine if [IR-09(04)_ODP; controls employed for personnel exposed to information not within assigned access authorizations are defined] are employed for personnel exposed to information not within assigned access authorizations.'),
('002821','draft','2013-07-12','DISA FSO','policy','Defines the controls to be employed for personnel exposed to information not within assigned access authorizations.','IR-09(04)','N/A','Determine if [IR-09(04)_ODP; controls employed for personnel exposed to information not within assigned access authorizations are defined] are employed for personnel exposed to information not within assigned access authorizations.'),
('002823','draft','2013-07-12','DISA FSO','policy','Defines the controls to be implemented to protect the system memory from unauthorized code execution.','SI-16','N/A','Determine if [SI-16_ODP; controls to be implemented to protect the system memory from unauthorized code execution are defined] are implemented to protect the system memory from unauthorized code execution.'),
('002824','draft','2013-07-12','DISA FSO','technical','Implement organization-defined controls to protect the system memory from unauthorized code execution.','SI-16','N/A','Determine if [SI-16_ODP; controls to be implemented to protect the system memory from unauthorized code execution are defined] are implemented to protect the system memory from unauthorized code execution.'),
('002825','draft','2013-07-20','DISA FSO','policy','Defines the personnel or roles to whom the organizational-level; mission/business process-level; and/or system-level contingency planning policy is to be disseminated.','CP-01a.','N/A','Determine if: - a contingency planning policy is developed and documented. - the contingency planning policy is disseminated to [CP-01_ODP[01]; personnel or roles to whom the contingency planning policy is to be disseminated is/are defined].'),
('002826','draft','2013-07-20','DISA FSO','policy','Defines personnel or roles to whom the contingency planning procedures are disseminated.','CP-01a.02','N/A','Determine if: - contingency planning procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls are developed and documented. - the contingency planning procedures are disseminated to [CP-01_ODP[02]; personnel or roles to whom the contingency planning procedures are to be disseminated is/are defined].'),
('002827','draft','2013-07-20','DISA FSO','policy','Coordinate the contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.','CP-02(07)','N/A','Determine if the contingency plan is coordinated with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.'),
('002828','draft','2013-07-20','DISA FSO','policy','Identify critical system assets supporting all or essential mission functions.','CP-02(08)','N/A','Determine if critical system assets supporting [CP-02(08)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions are identified.'),
('002829','draft','2013-07-20','DISA FSO','policy','Identify critical system assets supporting all or essential business functions.','CP-02(08)','N/A','Determine if critical system assets supporting [CP-02(08)_ODP; one of the following PARAMETER VALUES is selected: {all; essential}] mission and business functions are identified.'),
('002830','draft','2013-07-20','DISA FSO','policy','Defines the personnel or roles who review and approve the contingency plan for the system.','CP-02a.07','N/A','Determine if: - a contingency plan for the system is developed that is reviewed by [CP-02_ODP[01]; personnel or roles to review a contingency plan is/are defined]. - a contingency plan for the system is developed that is approved by [CP-02_ODP[02]; personnel or roles to approve a contingency plan is/are defined].'),
('002831','draft','2013-07-20','DISA FSO','policy','Defines a list of key contingency personnel (identified by name and/or by role) and organizational elements to whom contingency plan changes are to be communicated.','CP-02f.','N/A','Determine if: - contingency plan changes are communicated to [CP-02_ODP[06]; key contingency personnel (identified by name and/or by role) to communicate changes to are defined]. - contingency plan changes are communicated to [CP-02_ODP[07]; key contingency organizational elements to communicate changes to are defined].'),
('002832','draft','2013-07-20','DISA FSO','policy','Protects the contingency plan from unauthorized disclosure and modification.','CP-02h.','N/A','Determine if: - the contingency plan is protected from unauthorized disclosure. - the contingency plan is protected from unauthorized modification.'),
('002833','draft','2013-07-20','DISA FSO','policy','Defines the time period that contingency training is to be provided to system users consistent with assigned roles and responsibilities within assuming a contingency role or responsibility.','CP-03a.01','N/A','Determine if contingency training is provided to system users consistent with assigned roles and responsibilities within [CP-03_ODP[01]; the time period within which to provide contingency training after assuming a contingency role or responsibility is defined] of assuming a contingency role or responsibility.'),
('002834','draft','2013-07-20','DISA FSO','policy','Provide contingency training to system users consistent with assigned roles and responsibilities when required by system changes.','CP-03a.02','N/A','Determine if contingency training is provided to system users consistent with assigned roles and responsibilities when required by system changes.'),
('002835','draft','2013-07-20','DISA FSO','policy','Test the contingency plan at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations.','CP-04(02)(b)','N/A','Determine if the contingency plan is tested at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations.'),
('002836','draft','2013-07-20','DISA FSO','policy','Ensure that the alternate storage site provides security controls equivalent to that of the primary site.','CP-06b.','N/A','Determine if the alternate storage site provides controls equivalent to that of the primary site.'),
('002837','draft','2013-07-20','DISA FSO','policy','Plan for circumstances that preclude returning to the primary processing site.','CP-07(06)','N/A','Determine if: - circumstances that preclude returning to the primary processing site are planned for. - circumstances that preclude returning to the primary processing site are prepared for.'),
('002838','draft','2013-07-20','DISA FSO','policy','Prepare for circumstances that preclude returning to the primary processing site.','CP-07(06)','N/A','Determine if: - circumstances that preclude returning to the primary processing site are planned for. - circumstances that preclude returning to the primary processing site are prepared for.'),
('002839','draft','2013-07-20','DISA FSO','policy','Defines system operations that are permitted to transfer and resume at an alternate processing site for essential missions/business functions when the primary processing capabilities are unavailable.','CP-07a.','N/A','Determine if an alternate processing site, including necessary agreements to permit the transfer and resumption of [CP-07_ODP[01]; system operations for essential mission and business functions are defined] for essential mission and business functions, is established within [CP-07_ODP[02]; time period consistent with recovery time and recovery point objectives is defined] when the primary processing capabilities are unavailable.'),
('002840','draft','2013-07-20','DISA FSO','policy','Defines the system operations to be resumed for essential mission functions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-08','N/A','Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [CP-08_ODP[01]; system operations to be resumed for essential mission and business functions are defined], are established for essential mission and business functions within [CP-08_ODP[02]; time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.'),
('002841','draft','2013-07-20','DISA FSO','policy','Defines the system operations to be resumed for essential business functions within the organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.','CP-08','N/A','Determine if alternate telecommunications services, including necessary agreements to permit the resumption of [CP-08_ODP[01]; system operations to be resumed for essential mission and business functions are defined], are established for essential mission and business functions within [CP-08_ODP[02]; time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.'),
('002842','draft','2013-07-20','DISA FSO','policy','Review provider contingency plans to ensure that the plans meet organizational contingency requirements.','CP-08(04)(b)','N/A','Determine if provider contingency plans are reviewed to ensure that the plans meet organizational contingency requirements.'),
('002843','draft','2013-07-20','DISA FSO','policy','Defines the frequency with which to obtain evidence of contingency testing by providers.','CP-08(04)(c)','N/A','Determine if: - evidence of contingency testing by providers is obtained [CP-08(04)_ODP[01]; frequency at which to obtain evidence of contingency testing by providers is defined]. - evidence of contingency training by providers is obtained [CP-08(04)_ODP[02]; frequency at which to obtain evidence of contingency training by providers is defined].'),
('002844','draft','2013-07-20','DISA FSO','policy','Defines the frequency with which to obtain evidence of contingency training by providers.','CP-08(04)(c)','N/A','Determine if: - evidence of contingency testing by providers is obtained [CP-08(04)_ODP[01]; frequency at which to obtain evidence of contingency testing by providers is defined]. - evidence of contingency training by providers is obtained [CP-08(04)_ODP[02]; frequency at which to obtain evidence of contingency training by providers is defined].'),
('002845','draft','2013-07-20','DISA FSO','policy','Obtain evidence of contingency testing by providers in accordance with organization-defined frequency.','CP-08(04)(c)','N/A','Determine if: - evidence of contingency testing by providers is obtained [CP-08(04)_ODP[01]; frequency at which to obtain evidence of contingency testing by providers is defined]. - evidence of contingency training by providers is obtained [CP-08(04)_ODP[02]; frequency at which to obtain evidence of contingency training by providers is defined].'),
('002846','draft','2013-07-20','DISA FSO','policy','Obtain evidence of contingency training by providers in accordance with organization-defined frequency.','CP-08(04)(c)','N/A','Determine if: - evidence of contingency testing by providers is obtained [CP-08(04)_ODP[01]; frequency at which to obtain evidence of contingency testing by providers is defined]. - evidence of contingency training by providers is obtained [CP-08(04)_ODP[02]; frequency at which to obtain evidence of contingency training by providers is defined].'),
('002847','draft','2013-07-20','DISA FSO','policy','Defines the frequency with which to test alternate telecommunication services.','CP-08(05)','N/A','Determine if alternate telecommunications services are tested [CP-08(05)_ODP; frequency at which alternate telecommunications services are tested is defined].'),
('002848','draft','2013-07-20','DISA FSO','policy','Test alternate telecommunication services per organization-defined frequency.','CP-08(05)','N/A','Determine if alternate telecommunications services are tested [CP-08(05)_ODP; frequency at which alternate telecommunications services are tested is defined].'),
('002849','draft','2013-07-20','DISA FSO','policy','Defines critical system software and other security-related information, of which backup copies must be stored in a separate facility or in a fire-rated container.','CP-09(03)','N/A','Determine if backup copies of [CP-09(03)_ODP; critical system software and other security-related information backups to be stored in a separate facility are defined] are stored in a separate facility or in a fire rated container that is not collocated with the operational system.'),
('002850','draft','2013-07-20','DISA FSO','policy','Store backup copies of organization-defined critical system software and other security-related information in a separate facility or in a fire-rated container that is not collocated with the operational system.','CP-09(03)','N/A','Determine if backup copies of [CP-09(03)_ODP; critical system software and other security-related information backups to be stored in a separate facility are defined] are stored in a separate facility or in a fire rated container that is not collocated with the operational system.'),
('002851','draft','2013-07-20','DISA FSO','policy','Defines the backup information that requires dual authorization for deletion or destruction.','CP-09(07)','N/A','Determine if dual authorization for the deletion or destruction of [CP-09(07)_ODP; backup information for which to enforce dual authorization in order to delete or destroy is defined] is enforced.'),
('002852','draft','2013-07-20','DISA FSO','policy','Enforce dual authorization for the deletion or destruction of organization-defined backup information.','CP-09(07)','N/A','Determine if dual authorization for the deletion or destruction of [CP-09(07)_ODP; backup information for which to enforce dual authorization in order to delete or destroy is defined] is enforced.'),
('002853','draft','2013-07-20','DISA FSO','technical','Provide the capability to employ organization-defined alternative communications protocols in support of maintaining continuity of operations.','CP-11','N/A','Determine if the capability to employ [CP-11_ODP; alternative communications protocols in support of maintaining continuity of operations are defined] are provided in support of maintaining continuity of operations.'),
('002854','draft','2013-07-20','DISA FSO','policy','Defines the alternative communications protocols the system must be capable of providing in support of maintaining continuity of operations.','CP-11','N/A','Determine if the capability to employ [CP-11_ODP; alternative communications protocols in support of maintaining continuity of operations are defined] are provided in support of maintaining continuity of operations.'),
('002855','draft','2013-07-20','DISA FSO','technical','When organization-defined conditions are detected, enters a safe mode of operation with organization-defined restrictions of safe mode of operation.','CP-12','N/A','Determine if a safe mode of operation is entered with [CP-12_ODP[01]; restrictions for safe mode of operation are defined] when [CP-12_ODP[02]; conditions detected to enter a safe mode of operation are defined] are detected.'),
('002856','draft','2013-07-20','DISA FSO','policy','Defines the conditions that, when detected, the system enters a safe mode of operation with organization-defined restrictions of safe mode of operation.','CP-12','N/A','Determine if a safe mode of operation is entered with [CP-12_ODP[01]; restrictions for safe mode of operation are defined] when [CP-12_ODP[02]; conditions detected to enter a safe mode of operation are defined] are detected.'),
('002857','draft','2013-07-20','DISA FSO','policy','Defines the restrictions of the safe mode of operation that the system will enter when organization-defined conditions are detected.','CP-12','N/A','Determine if a safe mode of operation is entered with [CP-12_ODP[01]; restrictions for safe mode of operation are defined] when [CP-12_ODP[02]; conditions detected to enter a safe mode of operation are defined] are detected.'),
('002858','draft','2013-07-20','DISA FSO','policy','Employ organization-defined alternative or supplemental security mechanisms for satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised.','CP-13','N/A','Determine if [CP-13_ODP[01]; alternative or supplemental security mechanisms are defined] are employed for satisfying [CP-13_ODP[02]; security functions are defined] when the primary means of implementing the security function is unavailable or compromised.'),
('002859','draft','2013-07-20','DISA FSO','policy','Defines the alternative or supplemental security mechanisms that will be employed for satisfying organization-defined security functions when the primary means of implementing the security function is unavailable or compromised.','CP-13','N/A','Determine if [CP-13_ODP[01]; alternative or supplemental security mechanisms are defined] are employed for satisfying [CP-13_ODP[02]; security functions are defined] when the primary means of implementing the security function is unavailable or compromised.'),
('002860','draft','2013-07-20','DISA FSO','policy','Defines the security functions that must be satisfied when the primary means of implementing the security function is unavailable or compromised.','CP-13','N/A','Determine if [CP-13_ODP[01]; alternative or supplemental security mechanisms are defined] are employed for satisfying [CP-13_ODP[02]; security functions are defined] when the primary means of implementing the security function is unavailable or compromised.'),
('002861','draft','2013-07-22','DISA FSO','policy','Defines the personnel or roles to whom an organization-level; mission/business process-level; and/or system-level maintenance policy is disseminated.','MA-01a.','N/A','Determine if: - a maintenance policy is developed and documented. - the maintenance policy is disseminated to [MA-01_ODP[01]; personnel or roles to whom the maintenance policy is to be disseminated is/are defined].'),
('002862','draft','2013-07-22','DISA FSO','policy','Defines the personnel or roles to whom system maintenance procedures are to be disseminated.','MA-01a.02','N/A','Determine if: - maintenance procedures to facilitate the implementation of the maintenance policy and associated maintenance controls are developed and documented. - Determine if the maintenance procedures are disseminated to [MA-01_ODP[02]; personnel or roles to whom the maintenance procedures are to be disseminated is/are defined].'),
('002864','draft','2013-07-22','DISA FSO','policy','Produce up-to date, accurate, and complete records of all maintenance requested, scheduled, in process, and completed.','MA-02(02)(b)','N/A','Determine if: - up-to date, accurate, and complete records of all maintenance actions requested, scheduled, in process, and completed are produced. - up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed are produced. - up-to date, accurate, and complete records of all replacement actions requested, scheduled, in process, and completed are produced.'),
('002865','draft','2013-07-22','DISA FSO','policy','Produce up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed.','MA-02(02)(b)','N/A','Determine if: - up-to date, accurate, and complete records of all maintenance actions requested, scheduled, in process, and completed are produced. - up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed are produced. - up-to date, accurate, and complete records of all replacement actions requested, scheduled, in process, and completed are produced.'),
('002866','draft','2013-07-22','DISA FSO','policy','Schedule maintenance on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002868','draft','2013-07-22','DISA FSO','policy','Document records of maintenance on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002869','draft','2013-07-22','DISA FSO','policy','Review records of maintenance on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002870','draft','2013-07-22','DISA FSO','policy','Schedule repair on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002872','draft','2013-07-22','DISA FSO','policy','Document repair on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002873','draft','2013-07-22','DISA FSO','policy','Review records of repairs on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('002874','draft','2013-07-22','DISA FSO','policy','Defines the personnel or roles who can explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repairs or replacement.','MA-02c.','N/A','Determine if [MA-02_ODP[01]; personnel or roles required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance or repairs is/are defined] is/are required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement.'),
('002875','draft','2013-07-22','DISA FSO','policy','Include organization-defined information in organizational maintenance records.','MA-02f.','N/A','Determine if [MA-02_ODP[03]; information to be included in organizational maintenance records is defined] is included in organizational maintenance records.'),
('002876','draft','2013-07-22','DISA FSO','policy','Defines the information to include in organizational maintenance records.','MA-02f.','N/A','Determine if [MA-02_ODP[03]; information to be included in organizational maintenance records is defined] is included in organizational maintenance records.'),
('002882','draft','2013-07-22','DISA FSO','policy','Defines the personnel or roles who can provide an exemption that explicitly authorizes removal of equipment from the facility.','MA-03(03)(d)','N/A','Determine if the removal of maintenance equipment containing organizational information is prevented by obtaining an exemption from [MA-03(03)_ODP; personnel or roles who can authorize removal of equipment from the facility is/are defined] explicitly authorizing removal of the equipment from the facility.'),
('002883','draft','2013-07-22','DISA FSO','technical','Restrict the use of maintenance tools to authorized personnel only.','MA-03(04)','N/A','Determine if the use of maintenance tools is restricted to authorized personnel only.'),
('002884','draft','2013-07-22','DISA FSO','technical','Log organization-defined audit events for nonlocal maintenance and diagnostic sessions.','MA-04(01)(a)','N/A','Determine if: - [MA-04(01)_ODP[01]; audit events to be logged for nonlocal maintenance are defined] are logged for nonlocal maintenance sessions. - [MA-04(01)_ODP[02]; audit events to be logged for diagnostic sessions are defined] are logged for nonlocal diagnostic sessions.'),
('002885','draft','2013-07-22','DISA FSO','policy','Defines the audit events for logged for nonlocal maintenance and diagnostic sessions.','MA-04(01)(a)','N/A','Determine if: - [MA-04(01)_ODP[01]; audit events to be logged for nonlocal maintenance are defined] are logged for nonlocal maintenance sessions. - [MA-04(01)_ODP[02]; audit events to be logged for diagnostic sessions are defined] are logged for nonlocal diagnostic sessions.'),
('002886','draft','2013-07-22','DISA FSO','policy','Review the audit records of the maintenance and diagnostic sessions to detect anomalous behavior.','MA-04(01)(b)','N/A','Determine if: - the audit records of the maintenance sessions are reviewed to detect anomalous behavior. - the audit records of the diagnostic sessions are reviewed to detect anomalous behavior.'),
('002887','draft','2013-07-22','DISA FSO','policy','Defines the authenticators that are replay resistant which will be employed to protect nonlocal maintenance sessions.','MA-04(04)(a)','N/A','Determine if nonlocal maintenance sessions are protected by employing [MA-04(04)_ODP; authenticators that are replay resistant are defined].'),
('002888','draft','2013-07-22','DISA FSO','policy','Defines the personnel or roles authorized to approve each nonlocal maintenance session.','MA-04(05)(a)','N/A','Determine if the approval of each nonlocal maintenance session is required by [MA-04(05)_ODP[01]; personnel or roles required to approve each nonlocal maintenance session is/are defined].'),
('002889','draft','2013-07-22','DISA FSO','policy','Notify organization-defined personnel or roles of the date and time of planned nonlocal maintenance.','MA-04(05)(b)','N/A','Determine if [MA-04(05)_ODP[02]; personnel and roles to be notified of the date and time of planned nonlocal maintenance is/are defined] is/are notified of the date and time of planned nonlocal maintenance.'),
('002890','draft','2013-07-22','DISA FSO','technical','Implement organization-defined cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications.','MA-04(06)','N/A','Determine if: - [MA-04(06)_ODP; cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined] are implemented to protect the integrity of nonlocal maintenance and diagnostic communications. - [MA-04(06)_ODP; cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined] are implemented to protect the confidentiality of nonlocal maintenance and diagnostic communications.'),
('002891','draft','2013-07-22','DISA FSO','technical','Verify session and network connection termination after the completion of nonlocal maintenance and diagnostic sessions.','MA-04(07)','N/A','Determine if: - session connection termination is verified after the completion of nonlocal maintenance and diagnostic sessions. - network connection termination is verified after the completion of nonlocal maintenance and diagnostic sessions.'),
('002893','draft','2013-07-22','DISA FSO','policy','Ensure that non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system, have required access authorization.','MA-05(05)','N/A','Determine if non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system have required access authorizations.'),
('002894','draft','2013-07-22','DISA FSO','policy','Verify that non-escorted personnel performing maintenance on the system possess the required access authorizations.','MA-05b.','N/A','Determine if non-escorted personnel performing maintenance on the system possess the required access authorizations.'),
('002895','draft','2013-07-22','DISA FSO','policy','Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.','MA-05c.','N/A','Determine if organizational personnel with required access authorizations and technical competence is/are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.'),
('002896','draft','2013-07-22','DISA FSO','policy','Defines the system components for which it obtains maintenance support and/or spare parts.','MA-06','N/A','Determine if maintenance support and/or spare parts are obtained for [MA-06_ODP[01]; system components for which maintenance support and/or spare parts are obtained are defined] within [MA-06_ODP[02]; time period within which maintenance support and/or spare parts are to be obtained after a failure are defined] of failure.'),
('002897','draft','2013-07-22','DISA FSO','policy','Defines a time period for obtaining maintenance support and/or spare parts for organization-defined system components after a failure.','MA-06','N/A','Determine if maintenance support and/or spare parts are obtained for [MA-06_ODP[01]; system components for which maintenance support and/or spare parts are obtained are defined] within [MA-06_ODP[02]; time period within which maintenance support and/or spare parts are to be obtained after a failure are defined] of failure.'),
('002898','draft','2013-07-22','DISA FSO','policy','Perform preventive maintenance on organization-defined information system components at organization-defined time intervals.','MA-06(01)','N/A','Determine if preventive maintenance is performed on [MA-06(01)_ODP[01]; system components on which preventive maintenance is to be performed are defined] at [MA-06(01)_ODP[02]; time intervals within which preventive maintenance is to be performed on system components are defined].'),
('002899','draft','2013-07-22','DISA FSO','policy','Defines system components on which to perform preventive maintenance.','MA-06(01)','N/A','Determine if preventive maintenance is performed on [MA-06(01)_ODP[01]; system components on which preventive maintenance is to be performed are defined] at [MA-06(01)_ODP[02]; time intervals within which preventive maintenance is to be performed on system components are defined].'),
('002900','draft','2013-07-22','DISA FSO','policy','Defines time intervals at which to perform preventive maintenance on organization-defined system components.','MA-06(01)','N/A','Determine if preventive maintenance is performed on [MA-06(01)_ODP[01]; system components on which preventive maintenance is to be performed are defined] at [MA-06(01)_ODP[02]; time intervals within which preventive maintenance is to be performed on system components are defined].'),
('002901','draft','2013-07-22','DISA FSO','policy','Perform predictive maintenance on organization-defined system components at organization-defined intervals.','MA-06(02)','N/A','Determine if predictive maintenance is performed on [MA-06(02)_ODP[01]; system components on which predictive maintenance is to be performed are defined] at [MA-06(02)_ODP[02]; time intervals within which predictive maintenance is to be performed are defined].'),
('002902','draft','2013-07-22','DISA FSO','policy','Defines system components on which to perform predictive maintenance.','MA-06(02)','N/A','Determine if predictive maintenance is performed on [MA-06(02)_ODP[01]; system components on which predictive maintenance is to be performed are defined] at [MA-06(02)_ODP[02]; time intervals within which predictive maintenance is to be performed are defined].'),
('002903','draft','2013-07-22','DISA FSO','policy','Defines time intervals at which to perform predictive maintenance on organization-defined system components.','MA-06(02)','N/A','Determine if predictive maintenance is performed on [MA-06(02)_ODP[01]; system components on which predictive maintenance is to be performed are defined] at [MA-06(02)_ODP[02]; time intervals within which predictive maintenance is to be performed are defined].'),
('002904','draft','2013-07-22','DISA FSO','policy','Transfer predictive maintenance data to a maintenance management system using organization-defined automated mechanisms.','MA-06(03)','N/A','Determine if predictive maintenance data is transferred to a maintenance management system using [MA-06(03)_ODP; automated mechanisms used to transfer predictive maintenance data to a maintenance management system are defined].'),
('002906','draft','2013-08-13','DISA FSO','policy','Defines the vulnerability scanning activities in which the system implements privileged access authorization to organization-identified system components.','RA-05(05)','N/A','Determine if privileged access authorization is implemented to [RA-05(05)_ODP[01]; system components to which privileged access is authorized for selected vulnerability scanning activities are defined] for [RA-05(05)_ODP[02]; vulnerability scanning activities selected for privileged access authorization to system components are defined].'),
('002907','draft','2013-08-22','DISA FSO','policy','Defines the system mode to be invoked, such as a full system shutdown, a partial system shutdown, or a degraded operational mode with limited mission or business functionality available, in the event of organization-defined audit logging failures.','AU-05(04)','N/A','Determine if [AU-05(04)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available}] is/are invoked in the event of [AU-05(04)_ODP[02]; audit logging failures that trigger a change in operational mode are defined], unless an alternate audit logging capability exists.'),
('002908','draft','2013-08-27','DISA FSO','policy','Defines the personnel or roles to whom an organization-level; mission/business process-level; and/or system-level physical and environmental protection policy is disseminated.','PE-01a.','N/A','Determine if: - a physical and environmental protection policy is developed and documented. - the physical and environmental protection policy is disseminated to [PE-01_ODP[01]; personnel or roles to whom the physical and environmental protection policy is to be disseminated is/are defined].'),
('002909','draft','2013-08-27','DISA FSO','policy','Defines the personnel or roles to whom the physical and environmental protection procedures are disseminated.','PE-01a.02','N/A','Determine if: - physical and environmental protection procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls are developed and documented. - the physical and environmental protection procedures are disseminated to [PE-01_ODP[02]; personnel or roles to whom the physical and environmental protection procedures are to be disseminated is/are defined].'),
('002910','draft','2013-08-27','DISA FSO','policy','Approve a list of individuals with authorized access to the facility where the system resides.','PE-02a.','N/A','Determine if: - a list of individuals with authorized access to the facility where the system resides has been developed. - the list of individuals with authorized access to the facility where the system resides has been approved. - the list of individuals with authorized access to the facility where the system resides has been maintained.'),
('002911','draft','2013-08-27','DISA FSO','policy','Maintain a list of individuals with authorized access to the facility where the system resides.','PE-02a.','N/A','Determine if: - a list of individuals with authorized access to the facility where the system resides has been developed. - the list of individuals with authorized access to the facility where the system resides has been approved. - the list of individuals with authorized access to the facility where the system resides has been maintained.'),
('002912','draft','2013-08-27','DISA FSO','policy','Defines a list of acceptable forms of identification for visitor access to the facility where the system resides.','PE-02(02)','N/A','Determine if two forms of identification are required from [PE-02(02)_ODP; a list of acceptable forms of identification for visitor access to the facility where the system resides is defined] for visitor access to the facility where the system resides.'),
('002913','draft','2013-08-27','DISA FSO','policy','Restrict unescorted access to the facility where the system resides to personnel with one or more of the following: security clearances for all information contained within the system; formal access authorizations for all information contained within the system; need for access to all information contained within the system; organization-defined physical access authorizations.','PE-02(03)','N/A','Determine if unescorted access to the facility where the system resides is restricted to personnel with [PE-02(03)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security clearances for all information contained within the system; formal access authorizations for all information contained within the system; need for access to all information contained within the system; [PE-02(03)_ODP[02]; physical access authorizations for unescorted access to the facility where the system resides are defined (if selected)]}].'),
('002914','draft','2013-08-27','DISA FSO','policy','Defines the credentials required for personnel to have unescorted access to the facility where the system resides.','PE-02(03)','N/A','Determine if unescorted access to the facility where the system resides is restricted to personnel with [PE-02(03)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security clearances for all information contained within the system; formal access authorizations for all information contained within the system; need for access to all information contained within the system; [PE-02(03)_ODP[02]; physical access authorizations for unescorted access to the facility where the system resides are defined (if selected)]}].'),
('002915','draft','2013-08-27','DISA FSO','policy','Defines the entry and exit points to the facility where the system resides.',NULL,'N/A',NULL),
('002916','draft','2013-08-27','DISA FSO','policy','Defines the physical access control systems or devices or guards that control ingress and egress to the facility where the system resides.','PE-03a.02','N/A','Determine if physical access authorizations are enforced at [PE-03_ODP[01]; entry and exit points to the facility in which the system resides are defined] by controlling ingress and egress to the facility using [PE-03_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[PE-03_ODP[03]; physical access control systems or devices used to control ingress and egress to the facility are defined (if selected)]; guards}].'),
('002917','draft','2013-08-27','DISA FSO','policy','Maintain physical access audit logs for organization-defined entry/exit points to the facility where the system resides.','PE-03b.','N/A','Determine if physical access audit logs are maintained for [PE-03_ODP[04]; entry or exit points for which physical access logs are maintained are defined].'),
('002918','draft','2013-08-27','DISA FSO','policy','Defines entry and exit points to the facility where the system resides that require physical access audit logs be maintained.','PE-03b.','N/A','Determine if physical access audit logs are maintained for [PE-03_ODP[04]; entry or exit points for which physical access logs are maintained are defined].'),
('002919','draft','2013-08-27','DISA FSO','policy','Control access to areas within the facility designated as publicly accessible by implementing organization-defined access controls.','PE-03c.','N/A','Determine if access to areas within the facility designated as publicly accessible are maintained by implementing [PE-03_ODP[05]; physical access controls to control access to areas within the facility designated as publicly accessible are defined].'),
('002920','draft','2013-08-27','DISA FSO','policy','Defines physical access controls to control access to areas within the facility designated as publicly accessible.','PE-03c.','N/A','Determine if access to areas within the facility designated as publicly accessible are maintained by implementing [PE-03_ODP[05]; physical access controls to control access to areas within the facility designated as publicly accessible are defined].'),
('002921','draft','2013-08-27','DISA FSO','policy','Escort visitors in the facility where the system resides during organization-defined circumstances requiring visitor escorts.','PE-03d.','N/A','Determine if: - visitors are escorted. - visitor activity is controlled [PE-03_ODP[06]; circumstances requiring visitor escorts and control of visitor activity are defined].'),
('002922','draft','2013-08-27','DISA FSO','policy','Defines circumstances requiring visitor escorts in the facility where the system resides.','PE-03d.','N/A','Determine if: - visitors are escorted. - visitor activity is controlled [PE-03_ODP[06]; circumstances requiring visitor escorts and control of visitor activity are defined].'),
('002923','draft','2013-08-27','DISA FSO','policy','Monitor visitor activity in the facility where the system resides during organization-defined circumstances requiring visitor monitoring.','PE-03d.','N/A','Determine if: - visitors are escorted. - visitor activity is controlled [PE-03_ODP[06]; circumstances requiring visitor escorts and control of visitor activity are defined].'),
('002924','draft','2013-08-27','DISA FSO','policy','Define circumstances requiring visitor monitoring in the facility where the system resides.','PE-03d.','N/A','Determine if: - visitors are escorted. - visitor activity is controlled [PE-03_ODP[06]; circumstances requiring visitor escorts and control of visitor activity are defined].'),
('002925','draft','2013-08-27','DISA FSO','policy','Defines the physical access devices to inventory.','PE-03f.','N/A','Determine if [PE-03_ODP[07]; physical access devices to be inventoried are defined] are inventoried [PE-03_ODP[08]; frequency at which to inventory physical access devices is defined].'),
('002926','draft','2013-08-27','DISA FSO','policy','Defines the physical spaces containing one or more components of the system that require physical access authorizations and controls at the facility where the system resides.','PE-03(01)','N/A','Determine if: - physical access authorizations to the system are enforced. - physical access controls are enforced for the facility at [PE-03(01)_ODP; physical spaces containing one or more components of the system are defined].'),
('002927','draft','2013-08-27','DISA FSO','policy','Defines the frequency with which to perform security checks at the physical boundary of the facility or system for exfiltration of information or removal of system components.','PE-03(02)','N/A','Determine if security checks are performed [PE-03(02)_ODP; the frequency at which to perform security checks at the physical perimeter of the facility or system for exfiltration of information or removal of system components is defined] at the physical perimeter of the facility or system for exfiltration of information or removal of system components.'),
('002928','draft','2013-08-27','DISA FSO','policy','Defines anti-tamper technologies to detect and prevent physical tampering or alteration of organization-defined hardware components within the system.','PE-03(05)','N/A','Determine if [PE-03(05)_ODP[01]; anti-tamper technologies to be employed are defined] are employed to [PE-03(05)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {detect; prevent}] physical tampering or alteration of [PE-03(05)_ODP[03]; hardware components to be protected from physical tampering or alteration are defined] within the system.'),
('002929','draft','2013-08-27','DISA FSO','policy','Defines hardware components within the system for which to employ organization-defined security safeguards to detect and prevent physical tampering or alteration.','PE-03(05)','N/A','Determine if [PE-03(05)_ODP[01]; anti-tamper technologies to be employed are defined] are employed to [PE-03(05)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {detect; prevent}] physical tampering or alteration of [PE-03(05)_ODP[03]; hardware components to be protected from physical tampering or alteration are defined] within the system.'),
('002930','draft','2013-08-27','DISA FSO','policy','Defines system distribution and transmission lines within organizational facilities to control physical access to using organization-defined security controls.','PE-04','N/A','Determine if physical access to [PE-04_ODP[01]; system distribution and transmission lines requiring physical access controls are defined] within organizational facilities is controlled using [PE-04_ODP[02]; security controls to be implemented to control physical access to system distribution and transmission lines within the organizational facility are defined].'),
('002931','draft','2013-08-27','DISA FSO','policy','Defines security controls to control physical access to organization-defined system distribution and transmission lines within organizational facilities.','PE-04','N/A','Determine if physical access to [PE-04_ODP[01]; system distribution and transmission lines requiring physical access controls are defined] within organizational facilities is controlled using [PE-04_ODP[02]; security controls to be implemented to control physical access to system distribution and transmission lines within the organizational facility are defined].'),
('002939','draft','2013-08-27','DISA FSO','policy','Monitor physical access to the facility where the system resides to detect and respond to physical security incidents.','PE-06a.','N/A','Determine if physical access to the facility where the system resides is monitored to detect and respond to physical security incidents.'),
('002940','draft','2013-08-27','DISA FSO','policy','Review physical access logs upon occurrence of organization-defined events or potential indications of events.','PE-06b.','N/A','Determine if: - physical access logs are reviewed [PE-06_ODP[01]; the frequency at which to review physical access logs is defined]. - physical access logs are reviewed upon occurrence of [PE-06_ODP[02]; events or potential indication of events requiring physical access logs to be reviewed are defined].'),
('002941','draft','2013-08-27','DISA FSO','policy','Defines events or potential indications of events requiring review of physical access logs.','PE-06b.','N/A','Determine if: - physical access logs are reviewed [PE-06_ODP[01]; the frequency at which to review physical access logs is defined]. - physical access logs are reviewed upon occurrence of [PE-06_ODP[02]; events or potential indication of events requiring physical access logs to be reviewed are defined].'),
('002942','draft','2013-08-27','DISA FSO','policy','Recognize organization-defined classes or types of intrusions, using organization-defined automated mechanisms.','PE-06(02)','N/A','Determine if: - [PE-06(02)_ODP[01]; classes or types of intrusions to be recognized by automated mechanisms are defined] are recognized. - [PE-06(02)_ODP[02]; response actions to be initiated by automated mechanisms when organization-defined classes or types of intrusions are recognized are defined] are initiated using [PE-06(02)_ODP[03]; automated mechanisms used to recognize classes or types of intrusions and initiate response actions (defined in PE-06(02)_ODP) are defined].'),
('002943','draft','2013-08-27','DISA FSO','policy','Defines the classes or types of intrusions to recognize using automated mechanisms.','PE-06(02)','N/A','Determine if: - [PE-06(02)_ODP[01]; classes or types of intrusions to be recognized by automated mechanisms are defined] are recognized. - [PE-06(02)_ODP[02]; response actions to be initiated by automated mechanisms when organization-defined classes or types of intrusions are recognized are defined] are initiated using [PE-06(02)_ODP[03]; automated mechanisms used to recognize classes or types of intrusions and initiate response actions (defined in PE-06(02)_ODP) are defined].'),
('002944','draft','2013-08-27','DISA FSO','policy','Initiate organization-defined response actions to organization-defined classes or types of intrusions, using organization-defined automated mechanisms.','PE-06(02)','N/A','Determine if: - [PE-06(02)_ODP[01]; classes or types of intrusions to be recognized by automated mechanisms are defined] are recognized. - [PE-06(02)_ODP[02]; response actions to be initiated by automated mechanisms when organization-defined classes or types of intrusions are recognized are defined] are initiated using [PE-06(02)_ODP[03]; automated mechanisms used to recognize classes or types of intrusions and initiate response actions (defined in PE-06(02)_ODP) are defined].'),
('002945','draft','2013-08-27','DISA FSO','policy','Defines the response actions to initiate when organization-defined classes or types of intrusions are recognized.','PE-06(02)','N/A','Determine if: - [PE-06(02)_ODP[01]; classes or types of intrusions to be recognized by automated mechanisms are defined] are recognized. - [PE-06(02)_ODP[02]; response actions to be initiated by automated mechanisms when organization-defined classes or types of intrusions are recognized are defined] are initiated using [PE-06(02)_ODP[03]; automated mechanisms used to recognize classes or types of intrusions and initiate response actions (defined in PE-06(02)_ODP) are defined].'),
('002946','draft','2013-08-27','DISA FSO','policy','Employ video surveillance of organization-defined operational areas.','PE-06(03)(a)','N/A','Determine if video surveillance of [PE-06(03)_ODP[01]; operational areas where video surveillance is to be employed are defined] is employed.'),
('002947','draft','2013-08-27','DISA FSO','policy','Defines the operational areas in which to employ video surveillance.','PE-06(03)(a)','N/A','Determine if video surveillance of [PE-06(03)_ODP[01]; operational areas where video surveillance is to be employed are defined] is employed.'),
('002948','draft','2013-08-27','DISA FSO','policy','Retain video surveillance recordings for an organization-defined time period.','PE-06(03)(c)','N/A','Determine if video recordings are retained for [PE-06(03)_ODP[03]; time period for which to retain video recordings is defined].'),
('002949','draft','2013-08-27','DISA FSO','policy','Defines the time period to retain video surveillance recordings.','PE-06(03)(c)','N/A','Determine if video recordings are retained for [PE-06(03)_ODP[03]; time period for which to retain video recordings is defined].'),
('002950','draft','2013-08-27','DISA FSO','policy','Monitor physical access to the system in addition to the physical access monitoring of the facility as organization-defined physical spaces containing one or more components of the system.','PE-06(04)','N/A','Determine if physical access to the system is monitored in addition to the physical access monitoring of the facility at [PE-06(04)_ODP; physical spaces containing one or more components of the system are defined].'),
('002951','draft','2013-08-27','DISA FSO','policy','Defines physical spaces containing one or more components of the system in which physical access is monitored.','PE-06(04)','N/A','Determine if physical access to the system is monitored in addition to the physical access monitoring of the facility at [PE-06(04)_ODP; physical spaces containing one or more components of the system are defined].'),
('002952','draft','2013-08-27','DISA FSO','policy','Defines the time period to maintain visitor access records to the facility where the system resides.','PE-08a.','N/A','Determine if visitor access records for the facility where the system resides are maintained for [PE-08_ODP[01]; time period for which to maintain visitor access records for the facility where the system resides is defined].'),
('002953','draft','2013-08-27','DISA FSO','policy','Employ redundant power cabling paths that are physically separated by an organization-defined distance.','PE-09(01)','N/A','Determine if redundant power cabling paths that are physically separated by [PE-09(01)_ODP; distance by which redundant power cabling paths are to be physically separated is defined] are employed.'),
('002954','draft','2013-08-27','DISA FSO','policy','Defines the distance by which to physically separate redundant power cabling paths.','PE-09(01)','N/A','Determine if redundant power cabling paths that are physically separated by [PE-09(01)_ODP; distance by which redundant power cabling paths are to be physically separated is defined] are employed.'),
('002955','draft','2013-08-29','DISA FSO','policy','Provide an uninterruptible power supply to facilitate an orderly shutdown of the system, and/or transition of the system to long-term alternate power in the event of a primary power source loss.','PE-11','N/A','Determine if an uninterruptible power supply is provided to facilitate [PE-11_ODP; one of the following PARAMETER VALUES is selected: {an orderly shutdown of the system; transition of the system to long-term alternate power}] in the event of a primary power source loss.'),
('002956','draft','2013-08-29','DISA FSO','policy','Provide an alternate power supply for the system that is activated manually or automatically and that is self-contained.','PE-11(02)(a)','N/A','Determine if the alternate power supply provided for the system is self-contained.'),
('002957','draft','2013-08-29','DISA FSO','policy','Provide an alternate power supply for the system that is activated manually or automatically and that is not reliant on external power generation.','PE-11(02)(b)','N/A','Determine if the alternate power supply provided for the system is not reliant on external power generation.'),
('002958','draft','2013-08-29','DISA FSO','policy','Provide an alternate power supply for the system that is activated manually or automatically and that is capable of maintaining minimally required operational capability or full operational capability in the event of an extended loss of the primary power source.','PE-11(02)(c)','N/A','Determine if the alternate power supply provided for the system is capable of maintaining [PE-11(02)_ODP[02]; one of the following PARAMETER VALUES is selected: {minimally required operational capability; full operational capability}] in the event of an extended loss of the primary power source.'),
('002959','draft','2013-08-29','DISA FSO','policy','Provide emergency lighting for all areas within the facility supporting essential mission functions.','PE-12(01)','N/A','Determine if emergency lighting is provided for all areas within the facility supporting essential mission and business functions.'),
('002960','draft','2013-08-29','DISA FSO','policy','Provide emergency lighting for all areas within the facility supporting essential business functions.','PE-12(01)','N/A','Determine if emergency lighting is provided for all areas within the facility supporting essential mission and business functions.'),
('002961','draft','2013-08-29','DISA FSO','policy','Employ fire detection systems for the system that activate automatically.','PE-13(01)','N/A','Determine if: - fire detection systems that activate automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed in the event of a fire.'),
('002962','draft','2013-08-29','DISA FSO','policy','Employ fire detection systems for the system that automatically activate to notify organization-defined personnel or roles and organization-defined emergency responders in the event of a fire.','PE-13(01)','N/A','Determine if: - fire detection systems that activate automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed in the event of a fire.'),
('002963','draft','2013-08-29','DISA FSO','policy','Defines the personnel or roles to be notified in the event of a fire.','PE-13(01)','N/A','Determine if: - fire detection systems that activate automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed in the event of a fire.'),
('002964','draft','2013-08-29','DISA FSO','policy','Defines the emergency responders to be notified in the event of a fire.','PE-13(01)','N/A','Determine if: - fire detection systems that activate automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed in the event of a fire. - fire detection systems that notify [PE-13(01)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed in the event of a fire.'),
('002965','draft','2013-08-29','DISA FSO','policy','Employ fire suppression systems that activate automatically and notify organization-defined personnel or roles and organization-defined emergency responders.','PE-13(02)(a)','N/A','Determine if: - fire suppression systems that activate automatically are employed. - fire suppression systems that notify [PE-13(02)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed. - fire suppression systems that notify [PE-13(02)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed.'),
('002966','draft','2013-08-29','DISA FSO','policy','Defines the personnel or roles to be automatically notified of any activation of fire suppression systems.','PE-13(02)(a)','N/A','Determine if: - fire suppression systems that activate automatically are employed. - fire suppression systems that notify [PE-13(02)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed. - fire suppression systems that notify [PE-13(02)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed.'),
('002967','draft','2013-08-29','DISA FSO','policy','Defines the emergency responders to be automatically notified of any activation of fire suppression systems.','PE-13(02)(a)','N/A','Determine if: - fire suppression systems that activate automatically are employed. - fire suppression systems that notify [PE-13(02)_ODP[01]; personnel or roles to be notified in the event of a fire is/are defined] automatically are employed. - fire suppression systems that notify [PE-13(02)_ODP[02]; emergency responders to be notified in the event of a fire are defined] automatically are employed.'),
('002968','draft','2013-08-29','DISA FSO','policy','Ensure that the facility undergoes, on an organization-defined frequency, fire protection inspections by authorized and qualified inspectors.','PE-13(04)','N/A','Determine if: - the facility undergoes fire protection inspections [PE-13(04)_ODP[01]; the frequency for conducting fire protection inspections on the facility is defined] by authorized and qualified inspectors. - the identified deficiencies from fire protection inspections are resolved within [PE-13(04)_ODP[02]; a time period for resolving deficiencies identified by fire protection inspections is defined].'),
('002969','draft','2013-08-29','DISA FSO','policy','Defines a frequency with which the facility undergoes fire protection inspections.','PE-13(04)','N/A','Determine if: - the facility undergoes fire protection inspections [PE-13(04)_ODP[01]; the frequency for conducting fire protection inspections on the facility is defined] by authorized and qualified inspectors. - the identified deficiencies from fire protection inspections are resolved within [PE-13(04)_ODP[02]; a time period for resolving deficiencies identified by fire protection inspections is defined].'),
('002970','draft','2013-08-29','DISA FSO','policy','Ensure the identified deficiencies are resolved within an organization-defined time period.','PE-13(04)','N/A','Determine if: - the facility undergoes fire protection inspections [PE-13(04)_ODP[01]; the frequency for conducting fire protection inspections on the facility is defined] by authorized and qualified inspectors. - the identified deficiencies from fire protection inspections are resolved within [PE-13(04)_ODP[02]; a time period for resolving deficiencies identified by fire protection inspections is defined].'),
('002971','draft','2013-08-29','DISA FSO','policy','Defines the time period within which to resolve deficiencies identified during facility fire protection inspections.','PE-13(04)','N/A','Determine if: - the facility undergoes fire protection inspections [PE-13(04)_ODP[01]; the frequency for conducting fire protection inspections on the facility is defined] by authorized and qualified inspectors. - the identified deficiencies from fire protection inspections are resolved within [PE-13(04)_ODP[02]; a time period for resolving deficiencies identified by fire protection inspections is defined].'),
('002973','draft','2013-08-29','DISA FSO','policy','Defines the personnel or roles to be alerted when automated mechanisms detect the presence of water near the system.','PE-15(01)','N/A','Determine if: - the presence of water near the system can be detected automatically. - [PE-15(01)_ODP[01]; personnel or roles to be alerted when the presence of water is detected near the system is/are defined] is/are alerted using [PE-15(01)_ODP[02]; automated mechanisms used to detect the presence of water near the system are defined].'),
('002974','draft','2013-08-29','DISA FSO','policy','Defines types of system components to authorize and control entering and exiting the facility and to maintain records.','PE-16a.','N/A','Determine if: - [PE-16_ODP[01]; types of system components to be authorized and controlled when entering the facility are defined] are authorized when entering the facility. - [PE-16_ODP[01]; types of system components to be authorized and controlled when entering the facility are defined] are controlled when entering the facility. - [PE-16_ODP[02]; types of system components to be authorized and controlled when exiting the facility are defined] are authorized when exiting the facility. - [PE-16_ODP[02]; types of system components to be authorized and controlled when exiting the facility are defined] are controlled when exiting the facility.'),
('002975','draft','2013-08-29','DISA FSO','policy','Defines controls to employ at alternate work sites.','PE-17b.','N/A','Determine if [PE-17_ODP[02]; controls to be employed at alternate work sites are defined] are employed at alternate work sites.'),
('002976','draft','2013-08-29','DISA FSO','policy','Defines physical and environmental hazards that could cause potential damage to system components within the facility.','PE-18','N/A','Determine if system components are positioned within the facility to minimize potential damage from [PE-18_ODP; physical and environmental hazards that could result in potential damage to system components within the facility are defined] and to minimize the opportunity for unauthorized access.'),
('002979','draft','2013-08-29','DISA FSO','policy','Employ organization-defined asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas.','PE-20','N/A','Determine if [PE-20_ODP[01]; asset location technologies to be employed to track and monitor the location and movement of assets is defined] are employed to track and monitor the location and movement of [PE-20_ODP[02]; assets whose location and movement are to be tracked and monitored are defined] within [PE-20_ODP[03]; controlled areas within which asset location and movement are to be tracked and monitored are defined].'),
('002980','draft','2013-08-29','DISA FSO','policy','Defines asset location technologies to track and monitor the location and movement of organization-defined assets within organization-defined controlled areas.','PE-20','N/A','Determine if [PE-20_ODP[01]; asset location technologies to be employed to track and monitor the location and movement of assets is defined] are employed to track and monitor the location and movement of [PE-20_ODP[02]; assets whose location and movement are to be tracked and monitored are defined] within [PE-20_ODP[03]; controlled areas within which asset location and movement are to be tracked and monitored are defined].'),
('002981','draft','2013-08-29','DISA FSO','policy','Defines the assets within the organization-defined controlled areas which are to be tracked and monitored for their location and movement.','PE-20','N/A','Determine if [PE-20_ODP[01]; asset location technologies to be employed to track and monitor the location and movement of assets is defined] are employed to track and monitor the location and movement of [PE-20_ODP[02]; assets whose location and movement are to be tracked and monitored are defined] within [PE-20_ODP[03]; controlled areas within which asset location and movement are to be tracked and monitored are defined].'),
('002982','draft','2013-08-29','DISA FSO','policy','Defines controlled areas where the location and movement of organization-defined assets are tracked and monitored.','PE-20','N/A','Determine if [PE-20_ODP[01]; asset location technologies to be employed to track and monitor the location and movement of assets is defined] are employed to track and monitor the location and movement of [PE-20_ODP[02]; assets whose location and movement are to be tracked and monitored are defined] within [PE-20_ODP[03]; controlled areas within which asset location and movement are to be tracked and monitored are defined].'),
('002984','draft','2013-08-29','DISA FSO','policy','Develop an organization-wide information security program plan that reflects the coordination among organizational entities responsible for information security.','PM-01a.03','N/A','Determine if the information security program plan reflects the coordination among the organizational entities responsible for information security.'),
('002985','draft','2013-08-29','DISA FSO','policy','Disseminate an organization-wide information security program plan that provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements.','PM-01a.','N/A','Determine if: - an organization-wide information security program plan is developed. - the information security program plan is disseminated.'),
('002986','draft','2013-08-29','DISA FSO','policy','Disseminate an organization-wide information security program plan that includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PM-01a.02','N/A','Determine if: - the information security program plan includes the identification and assignment of roles. - the information security program plan includes the identification and assignment of responsibilities. - the information security program plan addresses management commitment. - the information security program plan addresses coordination among organizational entities. - the information security program plan addresses compliance.'),
('002987','draft','2013-08-29','DISA FSO','policy','Disseminate an organization-wide information security plan that reflects the coordination among organizational entities responsible for information security.','PM-01a.','N/A','Determine if: - an organization-wide information security program plan is developed. - the information security program plan is disseminated.'),
('002988','draft','2013-08-29','DISA FSO','policy','Disseminate an organization-wide information security program plan that is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.','PM-01a.','N/A','Determine if: - an organization-wide information security program plan is developed. - the information security program plan is disseminated.'),
('002989','draft','2013-08-29','DISA FSO','policy','Protect the information security program plan from unauthorized disclosure.','PM-01c.','N/A','Determine if: - the information security program plan is protected from unauthorized disclosure. - the information security program plan is protected from unauthorized modification.'),
('002990','draft','2013-08-29','DISA FSO','policy','Protect the information security program plan from unauthorized modification.','PM-01c.','N/A','Determine if: - the information security program plan is protected from unauthorized disclosure. - the information security program plan is protected from unauthorized modification.'),
('002991','draft','2013-08-29','DISA FSO','policy','Implement a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed.','PM-04a.01','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained.'),
('002993','draft','2013-08-29','DISA FSO','policy','Review plans of action and milestones for the security program and associated organization systems for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-04b.','N/A','Determine if: - plans of action and milestones are reviewed for consistency with the organizational risk management strategy. - plans of action and milestones are reviewed for consistency with organization-wide priorities for risk response actions.'),
('002994','draft','2013-08-29','DISA FSO','policy','Review and update the risk management strategy in accordance with organization-defined frequency or as required, to address organizational changes.','PM-09c.','N/A','Determine if the risk management strategy is reviewed and updated [PM-09_ODP; the frequency at which to review and update the risk management strategy is defined] or as required to address organizational changes.'),
('002995','draft','2013-08-29','DISA FSO','policy','Defines the frequency with which to review and update the risk management strategy to address organizational changes.','PM-09c.','N/A','Determine if the risk management strategy is reviewed and updated [PM-09_ODP; the frequency at which to review and update the risk management strategy is defined] or as required to address organizational changes.'),
('002996','draft','2013-08-29','DISA FSO','policy','Implement an insider threat program that includes a cross-discipline insider threat incident handling team.','PM-12','N/A','Determine if an insider threat program that includes a cross-discipline insider threat incident handling team is implemented.'),
('002997','draft','2013-08-29','DISA FSO','policy','Establish a security workforce development and improvement program.','PM-13','N/A','Determine if: - a security workforce development and improvement program is established. - privacy workforce development and improvement program is established.'),
('002998','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security testing activities associated with organizational systems are developed.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('002999','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security testing activities associated with organizational systems are maintained.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('003000','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security training activities associated with organizational systems are developed.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('003001','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security training activities associated with organizational systems are maintained.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('003002','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational systems are developed.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('003003','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational systems are maintained.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('003004','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security testing associated with organizational systems continue to be executed.','PM-14a.02','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed.'),
('003005','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security training associated with organizational systems continue to be executed.','PM-14a.02','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed.'),
('003006','draft','2013-08-29','DISA FSO','policy','Implement a process for ensuring that organizational plans for conducting security monitoring activities associated with organizational systems continue to be executed.','PM-14a.02','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed.'),
('003007','draft','2013-08-29','DISA FSO','policy','Review testing plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-14b.','N/A','Determine if: - testing plans are reviewed for consistency with the organizational risk management strategy. - training plans are reviewed for consistency with the organizational risk management strategy. - monitoring plans are reviewed for consistency with the organizational risk management strategy. - testing plans are reviewed for consistency with organization-wide priorities for risk response actions. - training plans are reviewed for consistency with organization-wide priorities for risk response actions. - monitoring plans are reviewed for consistency with organization-wide priorities for risk response actions.'),
('003008','draft','2013-08-29','DISA FSO','policy','Review training plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-14b.','N/A','Determine if: - testing plans are reviewed for consistency with the organizational risk management strategy. - training plans are reviewed for consistency with the organizational risk management strategy. - monitoring plans are reviewed for consistency with the organizational risk management strategy. - testing plans are reviewed for consistency with organization-wide priorities for risk response actions. - training plans are reviewed for consistency with organization-wide priorities for risk response actions. - monitoring plans are reviewed for consistency with organization-wide priorities for risk response actions.'),
('003009','draft','2013-08-29','DISA FSO','policy','Review monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.','PM-14b.','N/A','Determine if: - testing plans are reviewed for consistency with the organizational risk management strategy. - training plans are reviewed for consistency with the organizational risk management strategy. - monitoring plans are reviewed for consistency with the organizational risk management strategy. - testing plans are reviewed for consistency with organization-wide priorities for risk response actions. - training plans are reviewed for consistency with organization-wide priorities for risk response actions. - monitoring plans are reviewed for consistency with organization-wide priorities for risk response actions.'),
('003010','draft','2013-08-29','DISA FSO','policy','Establish and institutionalize contact with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel.','PM-15a.','N/A','Determine if: - contact is established and institutionalized with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel. - contact is established and institutionalized with selected groups and associations within the privacy community to facilitate ongoing privacy education and training for organizational personnel.'),
('003011','draft','2013-08-29','DISA FSO','policy','Establish and institutionalize contact with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies.','PM-15b.','N/A','Determine if: - contact is established and institutionalized with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies. - contact is established and institutionalized with selected groups and associations within the privacy community to maintain currency with recommended privacy practices, techniques, and technologies.'),
('003012','draft','2013-08-29','DISA FSO','policy','Establish and institutionalize contact with selected groups and associations within the security community to share current security information including threats, vulnerabilities, and incidents.','PM-15c.','N/A','Determine if: - contact is established and institutionalized with selected groups and associations within the security community to share current security information, including threats, vulnerabilities, and incidents. - contact is established and institutionalized with selected groups and associations within the privacy community to share current privacy information, including threats, vulnerabilities, and incidents.'),
('003013','draft','2013-08-29','DISA FSO','policy','Implement a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence.','PM-16','N/A','Determine if a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence is implemented.'),
('003014','draft','2013-08-30','DISA FSO','technical','Enforce organization-defined mandatory access control policies over all subjects and objects.','AC-03(03)','N/A','Determine if: - [AC-03(03)_ODP[01]; mandatory access control policy enforced over the set of covered subjects is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(03)_ODP[02]; mandatory access control policy enforced over the set of covered objects is defined] is enforced over the set of covered objects specified in the policy.'),
('003015','draft','2013-08-30','DISA FSO','policy','Specifies that organization-defined subjects may explicitly be granted organization-defined privileges such that they are not limited by any defined subset (or all) of the above constraints.',NULL,'N/A',NULL),
('003017','draft','2013-09-12','DISA FSO','policy','Defines the personnel or roles to whom an organization-level; mission/business process-level; and/or system-level personnel security policy is disseminated.','PS-01a.','N/A','Determine if: - a personnel security policy is developed and documented. - the personnel security policy is disseminated to [PS-01_ODP[01]; personnel or roles to whom the personnel security policy is to be disseminated is/are defined].'),
('003018','draft','2013-09-12','DISA FSO','policy','Defines the personnel or roles to whom the personnel security procedures are disseminated.','PS-01a.02','N/A','Determine if: - Determine if personnel security procedures to facilitate the implementation of the personnel security policy and associated personnel security controls are developed and documented. - the personnel security procedures are disseminated to [PS-01_ODP[02]; personnel or roles to whom the personnel security procedures are to be disseminated is/are defined].'),
('003019','draft','2013-09-12','DISA FSO','policy','Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties.','PS-03(03)(a)','N/A','Determine if individuals accessing a system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties.'),
('003020','draft','2013-09-12','DISA FSO','policy','Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection satisfy organization-defined additional personnel screening criteria.','PS-03(03)(b)','N/A','Determine if individuals accessing a system processing, storing, or transmitting information requiring special protection satisfy [PS-03(03)_ODP; additional personnel screening criteria to be satisfied for individuals accessing a system processing, storing, or transmitting information requiring special protection are defined].'),
('003021','draft','2013-09-12','DISA FSO','policy','Defines additional personnel screening criteria that individuals accessing a system processing, storing, or transmitting information requiring protection must satisfy.','PS-03(03)(b)','N/A','Determine if individuals accessing a system processing, storing, or transmitting information requiring special protection satisfy [PS-03(03)_ODP; additional personnel screening criteria to be satisfied for individuals accessing a system processing, storing, or transmitting information requiring special protection are defined].'),
('003022','draft','2013-09-12','DISA FSO','policy','Defines the time period within which to disable system access upon termination of individual employment.','PS-04a.','N/A','Determine if upon termination of individual employment, system access is disabled within [PS-04_ODP[01]; a time period within which to disable system access is defined].'),
('003023','draft','2013-09-12','DISA FSO','policy','Upon termination of individual employment, terminate or revoke any authenticators and credentials associated with the individual.','PS-04b.','N/A','Determine if upon termination of individual employment, any authenticators and credentials are terminated or revoked.'),
('003024','draft','2013-09-12','DISA FSO','policy','Defines information security topics to be discussed while conducting exit interviews.','PS-04c.','N/A','Determine if upon termination of individual employment, exit interviews that include a discussion of [PS-04_ODP[02]; information security topics to be discussed when conducting exit interviews are defined] are conducted.'),
('003027','draft','2013-09-12','DISA FSO','policy','Notify terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information.','PS-04(01)(a)','N/A','Determine if terminated individuals are notified of applicable, legally binding post-employment requirements for the protection of organizational information.'),
('003028','draft','2013-09-12','DISA FSO','policy','Require terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.','PS-04(01)(b)','N/A','Determine if terminated individuals are required to sign an acknowledgement of post-employment requirements as part of the organizational termination process.'),
('003029','draft','2013-09-12','DISA FSO','policy','Use organization-defined automated mechanisms to notify organization-defined personnel or roles of individual termination actions; and/or disable access to system resources.','PS-04(02)','N/A','Determine if [PS-04(02)_ODP[01]; automated mechanisms to notify personnel or roles of individual termination actions and/or to disable access to system resources are defined] are used to [PS-04(02)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {notify [PS-04(02)_ODP[03]; personnel or roles to be notified upon termination of an individual is/are defined (if selected)] of individual termination actions; disable access to system resources}].'),
('003030','draft','2013-09-12','DISA FSO','policy','Defines the personnel or roles to be notified by automated mechanism of individual termination actions, and/or disable access to system resources.','PS-04(02)','N/A','Determine if [PS-04(02)_ODP[01]; automated mechanisms to notify personnel or roles of individual termination actions and/or to disable access to system resources are defined] are used to [PS-04(02)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {notify [PS-04(02)_ODP[03]; personnel or roles to be notified upon termination of an individual is/are defined (if selected)] of individual termination actions; disable access to system resources}].'),
('003031','draft','2013-09-12','DISA FSO','policy','Modify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer.','PS-05c.','N/A','Determine if access authorization is modified as needed to correspond with any changes in operational need due to reassignment or transfer.'),
('003032','draft','2013-09-12','DISA FSO','policy','Notify organization-defined personnel or roles within an organization-defined time period when individuals are transferred or reassigned to other positions within the organization.','PS-05d.','N/A','Determine if [PS-05_ODP[03]; personnel or roles to be notified when individuals are reassigned or transferred to other positions within the organization is/are defined] are notified within [PS-05_ODP[04]; time period within which to notify organization-defined personnel or roles when individuals are reassigned or transferred to other positions within the organization is defined].'),
('003033','draft','2013-09-12','DISA FSO','policy','Defines personnel or roles to be notified when individuals are transferred or reassigned to other positions within the organization.','PS-05d.','N/A','Determine if [PS-05_ODP[03]; personnel or roles to be notified when individuals are reassigned or transferred to other positions within the organization is/are defined] are notified within [PS-05_ODP[04]; time period within which to notify organization-defined personnel or roles when individuals are reassigned or transferred to other positions within the organization is defined].'),
('003034','draft','2013-09-12','DISA FSO','policy','Defines the time period within which organization-defined personnel or roles are to be notified when individuals are transferred or reassigned to other positions within the organization.','PS-05d.','N/A','Determine if [PS-05_ODP[03]; personnel or roles to be notified when individuals are reassigned or transferred to other positions within the organization is/are defined] are notified within [PS-05_ODP[04]; time period within which to notify organization-defined personnel or roles when individuals are reassigned or transferred to other positions within the organization is defined].'),
('003035','draft','2013-09-12','DISA FSO','policy','Develop and document access agreements for organizational systems.','PS-06a.','N/A','Determine if access agreements are developed and documented for organizational systems.'),
('003038','draft','2013-09-12','DISA FSO','policy','Notify individuals of applicable, legally binding post-employment requirements for protection of organizational information.','PS-06(03)(a)','N/A','Determine if individuals are notified of applicable, legally binding post-employment requirements for the protection of organizational information.'),
('003039','draft','2013-09-12','DISA FSO','policy','Require individuals to sign an acknowledgement of legally binding post-employment requirements for protection of organizational information, if applicable, as part of granting initial access to covered information.','PS-06(03)(b)','N/A','Determine if individuals are required to sign an acknowledgement of applicable, legally binding post-employment requirements as part of being granted initial access to covered information.'),
('003041','draft','2013-09-12','DISA FSO','policy','Require external providers to notify organization-defined personnel or roles of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges, or who have system privileges within an organization-defined time period.','PS-07d.','N/A','Determine if external providers are required to notify [PS-07_ODP[01]; personnel or roles to be notified of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is/are defined] of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges within [PS-07_ODP[02]; time period within which third-party providers are required to notify organization-defined personnel or roles of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is defined].'),
('003042','draft','2013-09-12','DISA FSO','policy','Defines personnel or roles whom external providers are to notify when external personnel who possess organizational credentials and /or badges or who have system privileges are transferred or terminated.','PS-07d.','N/A','Determine if external providers are required to notify [PS-07_ODP[01]; personnel or roles to be notified of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is/are defined] of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges within [PS-07_ODP[02]; time period within which third-party providers are required to notify organization-defined personnel or roles of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is defined].'),
('003043','draft','2013-09-12','DISA FSO','policy','Defines the time period for external providers to notify organization-defined personnel or roles when external personnel who possess organizational credentials and/or badges, or who have system privileges are transferred or terminated.','PS-07d.','N/A','Determine if external providers are required to notify [PS-07_ODP[01]; personnel or roles to be notified of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is/are defined] of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges within [PS-07_ODP[02]; time period within which third-party providers are required to notify organization-defined personnel or roles of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges is defined].'),
('003044','draft','2013-09-12','DISA FSO','policy','Notify organization-defined personnel or roles within an organization-defined time period when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.','PS-08b.','N/A','Determine if [PS-08_ODP[01]; personnel or roles to be notified when a formal employee sanctions process is initiated is/are defined] is/are notified within [PS-08_ODP[02]; the time period within which organization-defined personnel or roles must be notified when a formal employee sanctions process is initiated is defined] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.'),
('003045','draft','2013-09-12','DISA FSO','policy','Defines personnel or roles who are to be notified when a formal employee sanctions process is initiated.','PS-08b.','N/A','Determine if [PS-08_ODP[01]; personnel or roles to be notified when a formal employee sanctions process is initiated is/are defined] is/are notified within [PS-08_ODP[02]; the time period within which organization-defined personnel or roles must be notified when a formal employee sanctions process is initiated is defined] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.'),
('003046','draft','2013-09-12','DISA FSO','policy','Defines the time period within which to notify organization-defined personnel or roles when a formal employee sanctions process is initiated.','PS-08b.','N/A','Determine if [PS-08_ODP[01]; personnel or roles to be notified when a formal employee sanctions process is initiated is/are defined] is/are notified within [PS-08_ODP[02]; the time period within which organization-defined personnel or roles must be notified when a formal employee sanctions process is initiated is defined] when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.'),
('003047','draft','2013-09-23','DISA FSO','policy','Defines the personnel or roles to whom the planning policy is disseminated.','PL-01a.','N/A','Determine if: - a planning policy is developed and documented. - the planning policy is disseminated to [PL-01_ODP[01]; personnel or roles to whom the planning policy is to be disseminated is/are defined].'),
('003048','draft','2013-09-23','DISA FSO','policy','Defines the personnel or roles to whom the planning procedures are disseminated.','PL-01a.02','N/A','Determine if: - planning procedures to facilitate the implementation of the planning policy and associated planning controls are developed and documented. - the planning procedures are disseminated to [PL-01_ODP[02]; personnel or roles to whom the planning procedures are to be disseminated is/are defined].'),
('003049','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system.',NULL,'N/A',NULL),
('003050','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that are consistent with the organization''s enterprise architecture.','PL-02a.01','N/A','Determine if: - a security plan for the system is developed that is consistent with the organization''s enterprise architecture. - a privacy plan for the system is developed that is consistent with the organization''s enterprise architecture.'),
('003051','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that explicitly defines the authorization boundary for the system.','PL-02a.02','N/A','Determine if: - a security plan for the system is developed that explicitly defines the constituent system components. - a privacy plan for the system is developed that explicitly defines the constituent system components.'),
('003052','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that describes the operational context of the system in terms of missions and business processes.','PL-02a.03','N/A','Determine if: - a security plan for the system is developed that describes the operational context of the system in terms of mission and business processes. - a privacy plan for the system is developed that describes the operational context of the system in terms of mission and business processes.'),
('003053','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that provide the security categorization of the system, including supporting rationale.','PL-02a.06','N/A','Determine if: - a security plan for the system is developed that provides the security categorization of the system, including supporting rationale. - a privacy plan for the system is developed that provides the security categorization of the system, including supporting rationale.'),
('003054','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that describe the operational environment for the system and any dependencies on or connections to, other systems or system components.','PL-02a.09','N/A','Determine if: - a security plan for the system is developed that describes the operational environment for the system and any dependencies on or connections to other systems or system components. - a privacy plan for the system is developed that describes the operational environment for the system and any dependencies on or connections to other systems or system components.'),
('003055','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that provide an overview of the security and privacy requirements for the system.','PL-02a.10','N/A','Determine if: - a security plan for the system is developed that provides an overview of the security requirements for the system. - a privacy plan for the system is developed that provides an overview of the privacy requirements for the system.'),
('003056','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that identify any relevant control baselines or overlays, if applicable.','PL-02a.11','N/A','Determine if: - a security plan for the system is developed that identifies any relevant control baselines or overlays, if applicable. - a privacy plan for the system is developed that identifies any relevant control baselines or overlays, if applicable.'),
('003057','draft','2013-09-23','DISA FSO','policy','Develop security and privacy plans for the system that describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions.','PL-02a.12','N/A','Determine if: - a security plan for the system is developed that describes the controls in place or planned for meeting the security requirements, including rationale for any tailoring decisions. - a privacy plan for the system is developed that describes the controls in place or planned for meeting the privacy requirements, including rationale for any tailoring decisions.'),
('003059','draft','2013-09-23','DISA FSO','policy','Distribute copies of the plans to organization-defined personnel or roles.','PL-02b.','N/A','Determine if: - copies of the plans are distributed to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned]. - subsequent changes to the plans are communicated to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned].'),
('003060','draft','2013-09-23','DISA FSO','policy','Defines the personnel or roles to whom copies of the plans are distributed.','PL-02b.','N/A','Determine if: - copies of the plans are distributed to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned]. - subsequent changes to the plans are communicated to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned].'),
('003061','draft','2013-09-23','DISA FSO','policy','Communicate subsequent changes to the plans to organization-defined personnel or roles.','PL-02b.','N/A','Determine if: - copies of the plans are distributed to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned]. - subsequent changes to the plans are communicated to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned].'),
('003062','draft','2013-09-23','DISA FSO','policy','Defines the personnel or roles to whom changes to the plans are communicated.','PL-02b.','N/A','Determine if: - copies of the plans are distributed to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned]. - subsequent changes to the plans are communicated to [PL-02_ODP[02]; personnel or roles to receive distributed copies of the system security and privacy plans is/are assigned].'),
('003063','draft','2013-09-23','DISA FSO','policy','Protect the plans from unauthorized disclosure.','PL-02e.','N/A','Determine if: - plans are protected from unauthorized disclosure. - plans are protected from unauthorized modification.'),
('003064','draft','2013-09-23','DISA FSO','policy','Protect the plans from unauthorized modification.','PL-02e.','N/A','Determine if: - plans are protected from unauthorized disclosure. - plans are protected from unauthorized modification.'),
('003068','draft','2013-09-23','DISA FSO','policy','Review and update the rules of behavior in accordance with organization-defined frequency.','PL-04c.','N/A','Determine if rules of behavior are reviewed and updated [PL-04_ODP[01]; frequency for reviewing and updating the rules of behavior is defined].'),
('003069','draft','2013-09-23','DISA FSO','policy','Defines the frequency with which to review and update the rules of behavior.','PL-04c.','N/A','Determine if rules of behavior are reviewed and updated [PL-04_ODP[01]; frequency for reviewing and updating the rules of behavior is defined].'),
('003070','draft','2013-09-23','DISA FSO','policy','Require individuals who have acknowledged a previous version of the rules of behavior to read and re-acknowledge, on an organization-defined frequency, and/or when the rules of behavior are revised or updated.','PL-04d.','N/A','Determine if individuals who have acknowledged a previous version of the rules of behavior are required to read and reacknowledge [PL-04_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[PL-04_ODP[03]; frequency for individuals to read and re-acknowledge the rules of behavior is defined (if selected)]; when the rules are revised or updated}].'),
('003071','draft','2013-09-23','DISA FSO','policy','Develop a security Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security.','PL-07a.','N/A','Determine if a CONOPS for the system describing how the organization intends to operate the system from the perspective of information security and privacy is developed.'),
('003072','draft','2013-09-23','DISA FSO','policy','Develop security architectures for the system.',NULL,'N/A',NULL),
('003073','draft','2013-09-23','DISA FSO','policy','Develop security architectures for the system that describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information.','PL-08a.01','N/A','Determine if a security architecture for the system describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information.'),
('003074','draft','2013-09-23','DISA FSO','policy','Develop security architectures for the system that describe how the architectures are integrated into and support the enterprise architecture.','PL-08a.03','N/A','Determine if: - a security architecture for the system describes how the architecture is integrated into and supports the enterprise architecture. - a privacy architecture for the system describes how the architecture is integrated into and supports the enterprise architecture.'),
('003075','draft','2013-09-23','DISA FSO','policy','Develop security architectures for the system that describe any assumptions about, and dependencies on, external systems and services.','PL-08a.04','N/A','Determine if: - a security architecture for the system describes any assumptions about and dependencies on external systems and services. - a privacy architecture for the system describes any assumptions about and dependencies on external systems and services.'),
('003076','draft','2013-09-23','DISA FSO','policy','Review and update the architectures in accordance with organization-defined frequency to reflect updates in the enterprise architecture.','PL-08b.','N/A','Determine if changes in the enterprise architecture are reviewed and updated [PL-08_ODP; frequency for review and update to reflect changes in the enterprise architecture] to reflect changes in the enterprise architecture.'),
('003077','draft','2013-09-23','DISA FSO','policy','Defines the frequency with which to review and update the system architecture.','PL-08b.','N/A','Determine if changes in the enterprise architecture are reviewed and updated [PL-08_ODP; frequency for review and update to reflect changes in the enterprise architecture] to reflect changes in the enterprise architecture.'),
('003078','draft','2013-09-23','DISA FSO','policy','Reflect planned security architecture changes in the security plans.','PL-08c.','N/A','Determine if: - planned architecture changes are reflected in the security plan. - planned architecture changes are reflected in the privacy plan. - planned architecture changes are reflected in the Concept of Operations (CONOPS). - planned architecture changes are reflected in criticality analysis. - planned architecture changes are reflected in organizational procedures. - planned architecture changes are reflected in procurements and acquisitions.'),
('003079','draft','2013-09-23','DISA FSO','policy','Reflect planned security architecture changes in the security Concept of Operations (CONOPS).','PL-08c.','N/A','Determine if: - planned architecture changes are reflected in the security plan. - planned architecture changes are reflected in the privacy plan. - planned architecture changes are reflected in the Concept of Operations (CONOPS). - planned architecture changes are reflected in criticality analysis. - planned architecture changes are reflected in organizational procedures. - planned architecture changes are reflected in procurements and acquisitions.'),
('003080','draft','2013-09-23','DISA FSO','policy','Reflect planned security architecture changes in the security organizational procurements and acquisitions.','PL-08c.','N/A','Determine if: - planned architecture changes are reflected in the security plan. - planned architecture changes are reflected in the privacy plan. - planned architecture changes are reflected in the Concept of Operations (CONOPS). - planned architecture changes are reflected in criticality analysis. - planned architecture changes are reflected in organizational procedures. - planned architecture changes are reflected in procurements and acquisitions.'),
('003081','draft','2013-09-23','DISA FSO','policy','Design the security architecture for the system using a defense-in-depth approach that allocates organization-defined controls to organization-defined locations.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('003082','draft','2013-09-23','DISA FSO','policy','Design the security architecture for the system using a defense-in-depth approach that allocates organization-defined controls to organization-defined architectural layers.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('003083','draft','2013-09-23','DISA FSO','policy','Defines the controls to be allocated to organization-defined locations for the security architecture.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('003084','draft','2013-09-23','DISA FSO','policy','Defines the controls to be allocated to organization-defined architectural layers.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('003085','draft','2013-09-23','DISA FSO','policy','Defines the locations to which the system allocates organization-defined controls in the security architecture.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('003086','draft','2013-09-23','DISA FSO','policy','Defines the architectural layers to which the system allocates organization-defined controls in the security architecture.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('003087','draft','2013-09-23','DISA FSO','policy','Design the security architecture for the system using a defense-in-depth approach that ensures that the allocated controls operate in a coordinated and mutually reinforcing manner.','PL-08(01)(b)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that ensures the allocated controls operate in a coordinated and mutually reinforcing manner. - the privacy architecture for the system is designed using a defense-in-depth approach that ensures the allocated controls operate in a coordinated and mutually reinforcing manner.'),
('003088','draft','2013-09-23','DISA FSO','policy','Require that organization-defined controls allocated to organization-defined locations and architectural layers be obtained from different suppliers.','PL-08(02)','N/A','Determine if [PL-08(02)_ODP[01]; controls to be allocated are defined] that are allocated to [PL-08(02)_ODP[02]; locations and architectural layers are defined] are required to be obtained from different suppliers.'),
('003089','draft','2013-09-23','DISA FSO','policy','Defines the personnel or roles to whom the organization-level; mission/business process-level; and/or system-level system and services acquisition policy is disseminated.','SA-01a.','N/A','Determine if: - a system and services acquisition policy is developed and documented. - the system and services acquisition policy is disseminated to [SA-01_ODP[01]; personnel or roles to whom the system and services acquisition policy is to be disseminated is/are defined].'),
('003090','draft','2013-09-23','DISA FSO','policy','Defines the personnel or roles to whom procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are disseminated.','SA-01a.02','N/A','Determine if: - system and services acquisition procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are developed and documented. - the system and services acquisition procedures are disseminated to [SA-01_ODP[02]; personnel or roles to whom the system and services acquisition procedures are to be disseminated is/are defined].'),
('003091','draft','2013-09-23','DISA FSO','policy','Determine the high-level information security requirements for the system or system service in mission and business process planning.','SA-02a.','N/A','Determine if: - the high-level information security requirements for the system or system service are determined in mission and business process planning. - the high-level privacy requirements for the system or system service are determined in mission and business process planning.'),
('003092','draft','2013-09-23','DISA FSO','policy','Defines a system development life cycle that is used to manage the system.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('003093','draft','2013-09-23','DISA FSO','policy','Integrate the organizational information security risk management process into system development life cycle activities.','SA-03d.','N/A','Determine if: - organizational information security risk management processes are integrated into system development life cycle activities. - organizational privacy risk management processes are integrated into system development life cycle activities.'),
('003094','draft','2013-09-23','DISA FSO','policy','Include the security functional requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the system, system component, or system service.','SA-04a.','N/A','Determine if: - security functional requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - privacy functional requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003095','draft','2013-09-23','DISA FSO','policy','Include the strength of mechanism requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04b.','N/A','Determine if strength of mechanism requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003096','draft','2013-09-23','DISA FSO','policy','Include the security assurance requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04c.','N/A','Determine if: - security assurance requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - privacy assurance requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003097','draft','2013-09-23','DISA FSO','policy','Include the security documentation requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04e.','N/A','Determine if: - security documentation requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - privacy documentation requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003098','draft','2013-09-23','DISA FSO','policy','Include the requirements for protecting security documentation, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04f.','N/A','Determine if: - requirements for protecting security documentation, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - requirements for protecting privacy documentation, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003099','draft','2013-09-23','DISA FSO','policy','Include the description of the system development environment and environment in which the system is intended to operate, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04g.','N/A','Determine if the description of the system development environment and environment in which the system is intended to operate, requirements, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003100','draft','2013-09-23','DISA FSO','policy','Include the acceptance criteria, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04i.','N/A','Determine if acceptance criteria requirements and descriptions are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('003101','draft','2013-09-23','DISA FSO','policy','Require the developer of the system, system component, or system service to provide design information for the controls that includes security-relevant external system interfaces, high-level design, low-level design, source code, hardware schematics, and/or organization-defined design information at an organization-defined level of detail.','SA-04(02)','N/A','Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SA-04(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [SA-04(02)_ODP[02]; design and implementation information is defined (if selected)]}] at [SA-04(02)_ODP[03]; level of detail is defined].'),
('003102','draft','2013-09-23','DISA FSO','policy','Require the developer of the system, system component, or system service to provide implementation information for the controls that includes security-relevant external system interfaces, high-level design, low-level design, source code, hardware schematics, and/or organization-defined implementation information at an organization-defined level of detail.','SA-04(02)','N/A','Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SA-04(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [SA-04(02)_ODP[02]; design and implementation information is defined (if selected)]}] at [SA-04(02)_ODP[03]; level of detail is defined].'),
('003103','draft','2013-09-23','DISA FSO','policy','Defines the design information that the developer of the system, system component, or system service is required to provide for the controls to be designed.','SA-04(02)','N/A','Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SA-04(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [SA-04(02)_ODP[02]; design and implementation information is defined (if selected)]}] at [SA-04(02)_ODP[03]; level of detail is defined].'),
('003104','draft','2013-09-23','DISA FSO','policy','Defines the implementation information that the developer of the system, system component, or system service is required to provide for the security controls to be implemented.','SA-04(02)','N/A','Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SA-04(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [SA-04(02)_ODP[02]; design and implementation information is defined (if selected)]}] at [SA-04(02)_ODP[03]; level of detail is defined].'),
('003105','draft','2013-09-23','DISA FSO','policy','Defines the level of detail for the design information of the controls that is required to be provided by the developer of the information system, system component, or information system services.','SA-04(02)','N/A','Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SA-04(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [SA-04(02)_ODP[02]; design and implementation information is defined (if selected)]}] at [SA-04(02)_ODP[03]; level of detail is defined].'),
('003106','draft','2013-09-23','DISA FSO','policy','Defines the level of detail for the implementation information of the security controls that is required to be provided by the developer of the information system, system component, or information system services.','SA-04(02)','N/A','Determine if the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using [SA-04(02)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; [SA-04(02)_ODP[02]; design and implementation information is defined (if selected)]}] at [SA-04(02)_ODP[03]; level of detail is defined].'),
('003109','draft','2013-09-23','DISA FSO','policy','Require the developer of the system, system component, or system service to deliver the system, component, or service with organization-defined security configurations implemented.','SA-04(05)(a)','N/A','Determine if the developer of the system, system component, or system service is required to deliver the system, component, or service with [SA-04(05)_ODP; security configurations for the system, component, or service are defined] implemented.'),
('003110','draft','2013-09-23','DISA FSO','policy','Defines the security configurations required to be implemented when the developer delivers the system, system component, or system service.','SA-04(05)(a)','N/A','Determine if the developer of the system, system component, or system service is required to deliver the system, component, or service with [SA-04(05)_ODP; security configurations for the system, component, or service are defined] implemented.'),
('003111','draft','2013-09-23','DISA FSO','policy','Requires the developer of the system, system component, or system service to use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade.','SA-04(05)(b)','N/A','Determine if the configurations are used as the default for any subsequent system, component, or service reinstallation or upgrade.'),
('003112','draft','2013-09-23','DISA FSO','policy','Require the developer of the system, system component, or system service to produce a plan for the continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization.','SA-04(08)','N/A','Determine if the developer of the system, system component, or system service is required to produce a plan for the continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization.'),
('003114','draft','2013-09-23','DISA FSO','policy','Require the developer of the system, system component, or system service to identify the functions, ports, protocols, and services intended for organizational use.','SA-04(09)','N/A','Determine if: - the developer of the system, system component, or system service is required to identify the functions intended for organizational use. - the developer of the system, system component, or system service is required to identify the ports intended for organizational use. - the developer of the system, system component, or system service is required to identify the protocols intended for organizational use. - the developer of the system, system component, or system service is required to identify the services intended for organizational use.'),
('003116','draft','2013-09-23','DISA FSO','policy','Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems.','SA-04(10)','N/A','Determine if only information technology products on the FIPS 201-approved products list for the Personal Identity Verification (PIV) capability implemented within organizational systems are employed.'),
('003117','draft','2013-09-23','DISA FSO','policy','Centrally manage organization-defined controls and related processes.','PL-09','N/A','Determine if [PL-09_ODP; security and privacy controls and related processes to be centrally managed are defined] are centrally managed.'),
('003118','draft','2013-09-23','DISA FSO','policy','Defines the controls and related processes to be centrally managed.','PL-09','N/A','Determine if [PL-09_ODP; security and privacy controls and related processes to be centrally managed are defined] are centrally managed.'),
('003119','draft','2013-09-23','DISA FSO','policy','Employ a technical surveillance countermeasures survey at organization-defined locations on an organization-defined frequency or when organization-defined events or indicators occur.','RA-06','N/A','Determine if a technical surveillance countermeasures survey is employed at [RA-06_ODP[01]; locations to employ technical surveillance countermeasure surveys are defined] [RA-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[RA-06_ODP[03]; the frequency at which to employ technical surveillance countermeasure surveys is defined (if selected)]; when [RA-06_ODP[04]; events or indicators which, if they occur, trigger a technical surveillance countermeasures survey are defined (if selected)]}].'),
('003120','draft','2013-09-23','DISA FSO','policy','Defines the locations where technical surveillance countermeasures surveys are to be employed.','RA-06','N/A','Determine if a technical surveillance countermeasures survey is employed at [RA-06_ODP[01]; locations to employ technical surveillance countermeasure surveys are defined] [RA-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[RA-06_ODP[03]; the frequency at which to employ technical surveillance countermeasure surveys is defined (if selected)]; when [RA-06_ODP[04]; events or indicators which, if they occur, trigger a technical surveillance countermeasures survey are defined (if selected)]}].'),
('003121','draft','2013-09-23','DISA FSO','policy','Defines the frequency on which to employ technical surveillance countermeasures surveys.','RA-06','N/A','Determine if a technical surveillance countermeasures survey is employed at [RA-06_ODP[01]; locations to employ technical surveillance countermeasure surveys are defined] [RA-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[RA-06_ODP[03]; the frequency at which to employ technical surveillance countermeasure surveys is defined (if selected)]; when [RA-06_ODP[04]; events or indicators which, if they occur, trigger a technical surveillance countermeasures survey are defined (if selected)]}].'),
('003122','draft','2013-09-23','DISA FSO','policy','Defines the events or indicators upon which technical surveillance countermeasures surveys are to be employed.','RA-06','N/A','Determine if a technical surveillance countermeasures survey is employed at [RA-06_ODP[01]; locations to employ technical surveillance countermeasure surveys are defined] [RA-06_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[RA-06_ODP[03]; the frequency at which to employ technical surveillance countermeasure surveys is defined (if selected)]; when [RA-06_ODP[04]; events or indicators which, if they occur, trigger a technical surveillance countermeasures survey are defined (if selected)]}].'),
('003123','draft','2013-09-24','DISA FSO','technical','Implement organization-defined cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications.','MA-04(06)','N/A','Determine if: - [MA-04(06)_ODP; cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined] are implemented to protect the integrity of nonlocal maintenance and diagnostic communications. - [MA-04(06)_ODP; cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined] are implemented to protect the confidentiality of nonlocal maintenance and diagnostic communications.'),
('003124','draft','2013-09-30','DISA FSO','policy','Obtain or develop administrator documentation for the system, system component, or system service that describes secure configuration of the system, component, or service.','SA-05a.01','N/A','Determine if: - administrator documentation for the system, system component, or system service that describes the secure configuration of the system, component, or service is obtained or developed. - administrator documentation for the system, system component, or system service that describes the secure installation of the system, component, or service is obtained or developed. - administrator documentation for the system, system component, or system service that describes the secure operation of the system, component, or service is obtained or developed.'),
('003125','draft','2013-09-30','DISA FSO','policy','Obtain or develop administrator documentation for the system, system component, or system service that describes secure installation of the system, component, or service.','SA-05a.01','N/A','Determine if: - administrator documentation for the system, system component, or system service that describes the secure configuration of the system, component, or service is obtained or developed. - administrator documentation for the system, system component, or system service that describes the secure installation of the system, component, or service is obtained or developed. - administrator documentation for the system, system component, or system service that describes the secure operation of the system, component, or service is obtained or developed.'),
('003126','draft','2013-09-30','DISA FSO','policy','Obtain or develop administrator documentation for the system, system component, or system service that describes secure operation of the system, component, or service.','SA-05a.01','N/A','Determine if: - administrator documentation for the system, system component, or system service that describes the secure configuration of the system, component, or service is obtained or developed. - administrator documentation for the system, system component, or system service that describes the secure installation of the system, component, or service is obtained or developed. - administrator documentation for the system, system component, or system service that describes the secure operation of the system, component, or service is obtained or developed.'),
('003127','draft','2013-09-30','DISA FSO','policy','Obtain or develop administrator documentation for the system, system component, or system services that describes effective use and maintenance of security functions and mechanisms.','SA-05a.02','N/A','Determine if: - administrator documentation for the system, system component, or system service that describes the effective use of security functions and mechanisms is obtained or developed. - administrator documentation for the system, system component, or system service that describes the effective maintenance of security functions and mechanisms is obtained or developed. - administrator documentation for the system, system component, or system service that describes the effective use of privacy functions and mechanisms is obtained or developed. - administrator documentation for the system, system component, or system service that describes the effective maintenance of privacy functions and mechanisms is obtained or developed.'),
('003128','draft','2013-09-30','DISA FSO','policy','Obtain or develop administrator documentation for the system, system component, or system service that describes known vulnerabilities regarding configuration and use of administrative or privileged functions.','SA-05a.03','N/A','Determine if: - administrator documentation for the system, system component, or system service that describes known vulnerabilities regarding the configuration of administrative or privileged functions is obtained or developed. - administrator documentation for the system, system component, or system service that describes known vulnerabilities regarding the use of administrative or privileged functions is obtained or developed.'),
('003129','draft','2013-09-30','DISA FSO','policy','Obtain or develop user documentation for the system, system component, or system service that describes user-accessible security functions and mechanisms and how to effectively use those functions and mechanisms.','SA-05b.01','N/A','Determine if: - user documentation for the system, system component, or system service that describes user-accessible security functions and mechanisms is obtained or developed. - user documentation for the system, system component, or system service that describes how to effectively use those (user-accessible security) functions and mechanisms is obtained or developed. - user documentation for the system, system component, or system service that describes user-accessible privacy functions and mechanisms is obtained or developed. - user documentation for the system, system component, or system service that describes how to effectively use those (user-accessible privacy) functions and mechanisms is obtained or developed.'),
('003130','draft','2013-09-30','DISA FSO','policy','Obtain or develop user documentation for the system, system component, or system service that describes methods for user interaction which enables individuals to use the system, component, or service in a more secure manner.','SA-05b.02','N/A','Determine if: - user documentation for the system, system component, or system service that describes methods for user interaction, which enable individuals to use the system, component, or service in a more secure manner is obtained or developed. - user documentation for the system, system component, or system service that describes methods for user interaction, which enable individuals to use the system, component, or service to protect individual privacy is obtained or developed.'),
('003131','draft','2013-09-30','DISA FSO','policy','Obtain or develop user documentation for the system, system component, or system service that describes user responsibilities in maintaining the security of the system, component, or service.','SA-05b.03','N/A','Determine if: - user documentation for the system, system component, or system service that describes user responsibilities for maintaining the security of the system, component, or service is obtained or developed. - user documentation for the system, system component, or system service that describes user responsibilities for maintaining the privacy of individuals is obtained or developed.'),
('003132','draft','2013-09-30','DISA FSO','policy','Take organization-defined actions in response to attempts to obtain either unavailable or nonexistent documentation for the system, system component, or system service.','SA-05c.','N/A','Determine if: - attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent is documented. - after attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent, [SA-05_ODP[01]; actions to take when system, system component, or system service documentation is either unavailable or nonexistent are defined] are taken in response.'),
('003133','draft','2013-09-30','DISA FSO','policy','Defines actions to be taken in response to attempts to obtain either unavailable or nonexistent documentation for the system, system component, or system service.','SA-05c.','N/A','Determine if: - attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent is documented. - after attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent, [SA-05_ODP[01]; actions to take when system, system component, or system service documentation is either unavailable or nonexistent are defined] are taken in response.'),
('003135','draft','2013-09-30','DISA FSO','policy','Distribute system, system component, or system service documentation to organization-defined personnel or roles.','SA-05d.','N/A','Determine if documentation is distributed to [SA-05_ODP[02]; personnel or roles to distribute system documentation to is/are defined].'),
('003136','draft','2013-09-30','DISA FSO','policy','Defines the personnel or roles to whom system, system component, or system service documentation is to be distributed.','SA-05d.','N/A','Determine if documentation is distributed to [SA-05_ODP[02]; personnel or roles to distribute system documentation to is/are defined].'),
('003138','draft','2013-09-30','DISA FSO','policy','Employ organization-defined processes, methods, and techniques to monitor control compliance by external service providers on an ongoing basis.','SA-09c.','N/A','Determine if [SA-09_ODP[02]; processes, methods, and techniques employed to monitor control compliance by external service providers are defined] are employed to monitor control compliance by external service providers on an ongoing basis.'),
('003139','draft','2013-09-30','DISA FSO','policy','Defines processes, methods, and techniques to employ to monitor control compliance by external service providers on an ongoing basis.','SA-09c.','N/A','Determine if [SA-09_ODP[02]; processes, methods, and techniques employed to monitor control compliance by external service providers are defined] are employed to monitor control compliance by external service providers on an ongoing basis.'),
('003140','draft','2013-09-30','DISA FSO','policy','Conduct an organizational assessment of risk prior to the acquisition or outsourcing of information security services.','SA-09(01)(a)','N/A','Determine if an organizational assessment of risk is conducted prior to the acquisition or outsourcing of information security services.'),
('003141','draft','2013-09-30','DISA FSO','policy','Verify that the acquisition or outsourcing of dedicated information security services is approved by organization-defined personnel or roles.','SA-09(01)(b)','N/A','Determine if [SA-09(01)_ODP; personnel or roles that approve the acquisition or outsourcing of dedicated information security services is/are defined] approve the acquisition or outsourcing of dedicated information security services.'),
('003142','draft','2013-09-30','DISA FSO','policy','Defines the personnel or roles authorized to approve the acquisition or outsourcing of dedicated information security services.','SA-09(01)(b)','N/A','Determine if [SA-09(01)_ODP; personnel or roles that approve the acquisition or outsourcing of dedicated information security services is/are defined] approve the acquisition or outsourcing of dedicated information security services.'),
('003143','draft','2013-09-30','DISA FSO','policy','Require providers of organization-defined external system services to identify the functions, ports, protocols, and other services required for the use of such services.','SA-09(02)','N/A','Determine if providers of [SA-09(02)_ODP; external system services that require the identification of functions, ports, protocols, and other services are defined] are required to identify the functions, ports, protocols, and other services required for the use of such services.'),
('003144','draft','2013-09-30','DISA FSO','policy','Defines the external system services for which the providers are required to identify the functions, ports, protocols, and other services required for the use of such services.','SA-09(02)','N/A','Determine if providers of [SA-09(02)_ODP; external system services that require the identification of functions, ports, protocols, and other services are defined] are required to identify the functions, ports, protocols, and other services required for the use of such services.'),
('003145','draft','2013-09-30','DISA FSO','policy','Establish trust relationships with external service providers based on organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('003146','draft','2013-09-30','DISA FSO','policy','Document trust relationships with external service providers based on organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('003147','draft','2013-09-30','DISA FSO','policy','Maintain trust relationships with external service providers based on organization-defined security requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('003148','draft','2013-09-30','DISA FSO','policy','Defines security requirements, properties, factors, or conditions defining acceptable trust relationships with external service providers.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('003149','draft','2013-09-30','DISA FSO','policy','Take organization-defined actions to verify that the interests of organization-defined external service providers are consistent with and reflect organizational interests.','SA-09(04)','N/A','Determine if [SA-09(04)_ODP[02]; actions to be taken to verify that the interests of external service providers are consistent with and reflect organizational interests are defined] are taken to verify that the interests of [SA-09(04)_ODP[01]; external service providers are defined] are consistent with and reflect organizational interests.'),
('003150','draft','2013-09-30','DISA FSO','policy','Defines the actions taken to verify that the interests of organization-defined external service providers are consistent with and reflect organizational interests.','SA-09(04)','N/A','Determine if [SA-09(04)_ODP[02]; actions to be taken to verify that the interests of external service providers are consistent with and reflect organizational interests are defined] are taken to verify that the interests of [SA-09(04)_ODP[01]; external service providers are defined] are consistent with and reflect organizational interests.'),
('003151','draft','2013-09-30','DISA FSO','policy','Defines external service providers whose interests are consistent with and reflect organizational interests.','SA-09(04)','N/A','Determine if [SA-09(04)_ODP[02]; actions to be taken to verify that the interests of external service providers are consistent with and reflect organizational interests are defined] are taken to verify that the interests of [SA-09(04)_ODP[01]; external service providers are defined] are consistent with and reflect organizational interests.'),
('003152','draft','2013-09-30','DISA FSO','policy','Restrict the location of information processing, information or data, and/or system services to organization-defined locations based on organization-defined requirements or conditions.','SA-09(05)','N/A','Determine if based on [SA-09(05)_ODP[03]; requirements or conditions for restricting the location of [SA-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {information processing; information or data; system services}] are defined] is/are restricted to [SA-09(05)_ODP[02]; locations where [SA-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {information processing; information or data; system services}] is/are to be restricted are defined].'),
('003153','draft','2013-09-30','DISA FSO','policy','Defines the locations for which to restrict information processing, information or data, and/or system services based on organization-defined requirements or conditions.','SA-09(05)','N/A','Determine if based on [SA-09(05)_ODP[03]; requirements or conditions for restricting the location of [SA-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {information processing; information or data; system services}] are defined] is/are restricted to [SA-09(05)_ODP[02]; locations where [SA-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {information processing; information or data; system services}] is/are to be restricted are defined].'),
('003154','draft','2013-09-30','DISA FSO','policy','Defines the requirements or conditions on which to base restricting the location of information processing, information or data, and/or system services to organization-defined locations.','SA-09(05)','N/A','Determine if based on [SA-09(05)_ODP[03]; requirements or conditions for restricting the location of [SA-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {information processing; information or data; system services}] are defined] is/are restricted to [SA-09(05)_ODP[02]; locations where [SA-09(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {information processing; information or data; system services}] is/are to be restricted are defined].'),
('003155','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to perform configuration management during system, component, or service design, development, implementation, operation and/or disposal.','SA-10a.','N/A','Determine if the developer of the system, system component, or system service is required to perform configuration management during system, component, or service [SA-10_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {design; development; implementation; operation; disposal}].'),
('003156','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to document the integrity of changes to organization-defined configuration items under configuration management.','SA-10b.','N/A','Determine if: - the developer of the system, system component, or system service is required to document the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to manage the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to control the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined].'),
('003157','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to manage the integrity of changes to organization-defined configuration items under configuration management.','SA-10b.','N/A','Determine if: - the developer of the system, system component, or system service is required to document the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to manage the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to control the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined].'),
('003158','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to control the integrity of changes to organization-defined configuration items under configuration management.','SA-10b.','N/A','Determine if: - the developer of the system, system component, or system service is required to document the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to manage the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to control the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined].'),
('003159','draft','2013-09-30','DISA FSO','policy','Defines the configuration items under configuration management that require the integrity of changes to be documented, managed and controlled.','SA-10b.','N/A','Determine if: - the developer of the system, system component, or system service is required to document the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to manage the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined]. - the developer of the system, system component, or system service is required to control the integrity of changes to [SA-10_ODP[02]; configuration items under configuration management are defined].'),
('003160','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to document the potential security impacts of approved changes to the system, component, or service.','SA-10d.','N/A','Determine if: - the developer of the system, system component, or system service is required to document approved changes to the system, component, or service. - the developer of the system, system component, or system service is required to document the potential security impacts of approved changes. - the developer of the system, system component, or system service is required to document the potential privacy impacts of approved changes.'),
('003161','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to track security flaws within the system, component, or service.','SA-10e.','N/A','Determine if: - the developer of the system, system component, or system service is required to track security flaws within the system, component, or service. - the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service. - the developer of the system, system component, or system service is required to report findings to [SA-10_ODP[03]; personnel to whom security flaws and flaw resolutions within the system, component, or service are reported is/are defined].'),
('003162','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to track flaw resolution within the system, component, or service.','SA-10e.','N/A','Determine if: - the developer of the system, system component, or system service is required to track security flaws within the system, component, or service. - the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service. - the developer of the system, system component, or system service is required to report findings to [SA-10_ODP[03]; personnel to whom security flaws and flaw resolutions within the system, component, or service are reported is/are defined].'),
('003163','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to report findings of security flaws and flaw resolution within the system, component, or service to organization-defined personnel.','SA-10e.','N/A','Determine if: - the developer of the system, system component, or system service is required to track security flaws within the system, component, or service. - the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service. - the developer of the system, system component, or system service is required to report findings to [SA-10_ODP[03]; personnel to whom security flaws and flaw resolutions within the system, component, or service are reported is/are defined].'),
('003164','draft','2013-09-30','DISA FSO','policy','Defines the personnel to whom security flaw findings and flaw resolution within the system, component, or service are reported.','SA-10e.','N/A','Determine if: - the developer of the system, system component, or system service is required to track security flaws within the system, component, or service. - the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service. - the developer of the system, system component, or system service is required to report findings to [SA-10_ODP[03]; personnel to whom security flaws and flaw resolutions within the system, component, or service are reported is/are defined].'),
('003165','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to enable integrity verification of hardware components.','SA-10(03)','N/A','Determine if the developer of the system, system component, or system service is required to enable integrity verification of hardware components.'),
('003166','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions.','SA-10(04)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions. - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of source code with previous versions. - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of object code with previous versions. '),
('003167','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of source code with previous versions.','SA-10(04)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions. - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of source code with previous versions. - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of object code with previous versions. '),
('003168','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of object code with previous versions.','SA-10(04)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions. - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of source code with previous versions. - the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of object code with previous versions. '),
('003169','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.','SA-10(05)','N/A','Determine if the developer of the system, system component, or system service is required to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.'),
('003170','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.','SA-10(06)','N/A','Determine if the developer of the system, system component, or system service is required to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.'),
('003171','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to develop a plan for ongoing security control assessment.','SA-11a.','N/A','Determine if: - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments.'),
('003172','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to implement a plan for ongoing security control assessment.','SA-11a.','N/A','Determine if: - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments.'),
('003173','draft','2013-09-30','DISA FSO','policy','Requires the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to perform unit, integration, system, and/or regression testing/evaluation on an organization-defined frequency, at an organization-defined depth and coverage.','SA-11b.','N/A','Determine if the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to perform [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation [SA-11_ODP[02]; frequency at which to conduct [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation is defined] at [SA-11_ODP[03]; depth and coverage of [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation is defined].'),
('003174','draft','2013-09-30','DISA FSO','policy','Defines the depth and coverage at which to perform unit, integration, system, and/or regression testing/evaluation on an organization-defined frequency.','SA-11b.','N/A','Determine if the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to perform [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation [SA-11_ODP[02]; frequency at which to conduct [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation is defined] at [SA-11_ODP[03]; depth and coverage of [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation is defined].'),
('003175','draft','2013-09-30','DISA FSO','policy','Requires the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to produce evidence of the execution of the assessment plan.','SA-11c.','N/A','Determine if: - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce evidence of the execution of the assessment plan. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce the results of the testing and evaluation.'),
('003176','draft','2013-09-30','DISA FSO','policy','Requires the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to produce the results of the testing and evaluation.','SA-11c.','N/A','Determine if: - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce evidence of the execution of the assessment plan. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce the results of the testing and evaluation.'),
('003177','draft','2013-09-30','DISA FSO','policy','Requires the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to implement a verifiable flaw remediation process.','SA-11d.','N/A','Determine if the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a verifiable flaw remediation process.'),
('003178','draft','2013-09-30','DISA FSO','policy','Requires the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to correct flaws identified during testing/evaluation.','SA-11e.','N/A','Determine if the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to correct flaws identified during testing and evaluation.'),
('003179','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws.','SA-11(01)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ static code analysis tools to identify common flaws. - the developer of the system, system component, or system service is required to employ static code analysis tools to document the results of the analysis.'),
('003180','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to document the results of static code analysis.','SA-11(01)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ static code analysis tools to identify common flaws. - the developer of the system, system component, or system service is required to employ static code analysis tools to document the results of the analysis.'),
('003181','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development.',NULL,'N/A',NULL),
('003182','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analysis during subsequent testing and evaluation of the system, component, or service.',NULL,'N/A',NULL),
('003183','draft','2013-09-30','DISA FSO','policy','Require an independent agent satisfying organization-defined independence criteria to verify the correct implementation of the developer security assessment plan.','SA-11(03)(a)','N/A','Determine if: - an independent agent is required to satisfy [SA-11(03)_ODP; independence criteria to be satisfied by an independent agent are defined] to verify the correct implementation of the developer security assessment plan and the evidence produced during testing and evaluation. - an independent agent is required to satisfy [SA-11(03)_ODP; independence criteria to be satisfied by an independent agent are defined] to verify the correct implementation of the developer privacy assessment plan and the evidence produced during testing and evaluation.'),
('003184','draft','2013-09-30','DISA FSO','policy','Require an independent agent satisfying organization-defined independence criteria to verify the evidence produced during security testing and evaluation.','SA-11(03)(a)','N/A','Determine if: - an independent agent is required to satisfy [SA-11(03)_ODP; independence criteria to be satisfied by an independent agent are defined] to verify the correct implementation of the developer security assessment plan and the evidence produced during testing and evaluation. - an independent agent is required to satisfy [SA-11(03)_ODP; independence criteria to be satisfied by an independent agent are defined] to verify the correct implementation of the developer privacy assessment plan and the evidence produced during testing and evaluation.'),
('003185','draft','2013-09-30','DISA FSO','policy','Defines the independence criteria the independent agent must satisfy prior to verifying the correct implementation of the developer security assessment plan and the evidence produced during security testing and evaluation.','SA-11(03)(a)','N/A','Determine if: - an independent agent is required to satisfy [SA-11(03)_ODP; independence criteria to be satisfied by an independent agent are defined] to verify the correct implementation of the developer security assessment plan and the evidence produced during testing and evaluation. - an independent agent is required to satisfy [SA-11(03)_ODP; independence criteria to be satisfied by an independent agent are defined] to verify the correct implementation of the developer privacy assessment plan and the evidence produced during testing and evaluation.'),
('003186','draft','2013-09-30','DISA FSO','policy','Verify that the independent agent either is provided with sufficient information to complete the verification process or has been granted the authority to obtain such information.','SA-11(03)(b)','N/A','Determine if the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information.'),
('003187','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to perform a manual code review of organization-defined specific code using organization-defined processes, procedures, and/or techniques.','SA-11(04)','N/A','Determine if the developer of the system, system component, or system service is required to perform a manual code review of [SA-11(04)_ODP[01]; specific code requiring manual code review is defined] using [SA-11(04)_ODP[02]; processes, procedures, and/or techniques used for manual code reviews are defined].'),
('003188','draft','2013-09-30','DISA FSO','policy','Defines the specific code for which the developer of the system, system component, or system service is required to perform a manual code review using organization-defined process, procedures, and/or techniques.','SA-11(04)','N/A','Determine if the developer of the system, system component, or system service is required to perform a manual code review of [SA-11(04)_ODP[01]; specific code requiring manual code review is defined] using [SA-11(04)_ODP[02]; processes, procedures, and/or techniques used for manual code reviews are defined].'),
('003189','draft','2013-09-30','DISA FSO','policy','Defines the processes, procedures, and/or techniques to be used by the developer of the system, system component, or system service to perform a manual code review of organization-defined specific code.','SA-11(04)','N/A','Determine if the developer of the system, system component, or system service is required to perform a manual code review of [SA-11(04)_ODP[01]; specific code requiring manual code review is defined] using [SA-11(04)_ODP[02]; processes, procedures, and/or techniques used for manual code reviews are defined].'),
('003191','draft','2013-09-30','DISA FSO','policy','Defines the breadth and depth at which the developer of the system, system component, or system service is required to perform penetration testing.','SA-11(05)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: [SA-11(05)_ODP[01]; the breadth of penetration testing is defined]. - the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: [SA-11(05)_ODP[02]; the depth of penetration testing is defined].'),
('003192','draft','2013-09-30','DISA FSO','policy','Defines the constraints on penetration testing performed by the developer of the system, system component, or system service.','SA-11(05)(b)','N/A','Determine if the developer of the system, system component, or system service is required to perform penetration testing under [SA-11(05)_ODP[03]; constraints of penetration testing are defined].'),
('003193','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to perform attack surface reviews.','SA-11(06)','N/A','Determine if the developer of the system, system component, or system service is required to perform attack surface reviews.'),
('003194','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to verify that the scope of testing and evaluation provides complete coverage of required controls at an organization-defined depth of testing and evaluation.','SA-11(07)','N/A','Determine if: - the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at [SA-11(07)_ODP[01]; the breadth of testing and evaluation of required controls is defined]. - the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at [SA-11(07)_ODP[02]; the depth of testing and evaluation of required controls is defined].'),
('003195','draft','2013-09-30','DISA FSO','policy','Defines the depth of testing and evaluation to which the developer of the system, system component, or system service is required to verify that the scope of security testing and evaluation provides complete coverage of the required controls.','SA-11(07)','N/A','Determine if: - the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at [SA-11(07)_ODP[01]; the breadth of testing and evaluation of required controls is defined]. - the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at [SA-11(07)_ODP[02]; the depth of testing and evaluation of required controls is defined].'),
('003196','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws.','SA-11(08)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ dynamic code analysis tools to identify common flaws. - the developer of the system, system component, or system service is required to document the results of the analysis.'),
('003197','draft','2013-09-30','DISA FSO ','policy','Require the developer of the system, system component, or system service to document the results of the dynamic code analysis.','SA-11(08)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ dynamic code analysis tools to identify common flaws. - the developer of the system, system component, or system service is required to document the results of the analysis.'),
('003233','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process.',NULL,'N/A',NULL),
('003234','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that explicitly addresses security requirements.','SA-15a.01','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses security requirements. - the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses privacy requirements.'),
('003235','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that identifies the standards used in the development process.','SA-15a.02','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process that identifies the standards used in the development process. - the developer of the system, system component, or system service is required to follow a documented development process that identifies the tools used in the development process.'),
('003236','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that identifies the tools used in the development process.','SA-15a.02','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process that identifies the standards used in the development process. - the developer of the system, system component, or system service is required to follow a documented development process that identifies the tools used in the development process.'),
('003237','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that documents the specific tool options and tool configurations used in the development process.','SA-15a.03','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process that documents the specific tool used in the development process. - the developer of the system, system component, or system service is required to follow a documented development process that documents the specific tool configurations used in the development process.'),
('003238','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that documents changes to the process and/or tools used in development.','SA-15a.04','N/A','Determine if the developer of the system, system component, or system service is required to follow a documented development process that documents, manages, and ensures the integrity of changes to the process and/or tools used in development.'),
('003239','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that manages changes to the process and/or tools used in development.','SA-15a.04','N/A','Determine if the developer of the system, system component, or system service is required to follow a documented development process that documents, manages, and ensures the integrity of changes to the process and/or tools used in development.'),
('003240','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to follow a documented development process that ensures the integrity of changes to the process and/or tools used in development.','SA-15a.04','N/A','Determine if the developer of the system, system component, or system service is required to follow a documented development process that documents, manages, and ensures the integrity of changes to the process and/or tools used in development.'),
('003241','draft','2013-09-30','DISA FSO','policy','Review the development process in accordance with organization-defined frequency to determine if the development process selected and employed can satisfy organization-defined security requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('003242','draft','2013-09-30','DISA FSO','policy','Review the development standards in accordance with organization-defined frequency to determine if the development standards selected and employed can satisfy organization-defined security requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('003243','draft','2013-09-30','DISA FSO','policy','Review the development tools in accordance with organization-defined frequency to determine if the development tools selected and employed can satisfy organization-defined security requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('003244','draft','2013-09-30','DISA FSO','policy','Review the development tool options/configurations in accordance with organization-defined frequency to determine if the development tool options and tool configurations selected and employed can satisfy organization-defined security requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('003245','draft','2013-09-30','DISA FSO','policy','Defines the frequency on which to review the development process, standards, tools, and tool options/configurations to determine if the process, standards, tools, and tool options and tool configurations selected and employed can satisfy organization-defined security requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('003246','draft','2013-09-30','DISA FSO','policy','Defines the security requirements that must be satisfied by conducting a review of the development process, standards, tools, and tool options and tool configurations.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('003247','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to define quality metrics at the beginning of the development process.','SA-15(01)(a)','N/A','Determine if the developer of the system, system component, or system service is required to define quality metrics at the beginning of the development process.'),
('003248','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to provide evidence of meeting the quality metrics in accordance with organization-defined frequency, organization-defined program review milestones, and/or upon delivery.','SA-15(01)(b)','N/A','Determine if the developer of the system, system component, or system service is required to provide evidence of meeting the quality metrics [SA-15(01)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[SA-15(01)_ODP[02]; frequency at which to provide evidence of meeting the quality metrics is defined (if selected)]; [SA-15(01)_ODP[03]; program review milestones are defined (if selected)]; upon delivery}].'),
('003249','draft','2013-09-30','DISA FSO','policy','Defines the frequency on which the developer of the system, system component, or system service is required to provide evidence of meeting the quality metrics.','SA-15(01)(b)','N/A','Determine if the developer of the system, system component, or system service is required to provide evidence of meeting the quality metrics [SA-15(01)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[SA-15(01)_ODP[02]; frequency at which to provide evidence of meeting the quality metrics is defined (if selected)]; [SA-15(01)_ODP[03]; program review milestones are defined (if selected)]; upon delivery}].'),
('003250','draft','2013-09-30','DISA FSO','policy','Defines the program review milestones at which the developer of the information system, system component, or information system service is required to provide evidence of meeting the quality metrics.','SA-15(01)(b)','N/A','Determine if the developer of the system, system component, or system service is required to provide evidence of meeting the quality metrics [SA-15(01)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {[SA-15(01)_ODP[02]; frequency at which to provide evidence of meeting the quality metrics is defined (if selected)]; [SA-15(01)_ODP[03]; program review milestones are defined (if selected)]; upon delivery}].'),
('003251','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to select a security tracking tool for use during the development process.','SA-15(02)','N/A','Determine if: - the developer of the system, system component, or system service is required to select and employ security tracking tools for use during the development process. - the developer of the system, system component, or system service is required to select and employ privacy tracking tools for use during the development process.'),
('003252','draft','2013-09-30','DISA FSO','policy','Require the developer of the system, system component, or system service to employ a security tracking tool for use during the development process.','SA-15(02)','N/A','Determine if: - the developer of the system, system component, or system service is required to select and employ security tracking tools for use during the development process. - the developer of the system, system component, or system service is required to select and employ privacy tracking tools for use during the development process.'),
('003254','draft','2013-09-30','DISA FSO','policy','Defines the breadth/depth of criticality analysis at which the developer of the system, system component, or system service is required to perform a criticality analysis.','SA-15(03)(b)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: [SA-15(03)_ODP[02]; the breadth of criticality analysis is defined]. - the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: [SA-15(03)_ODP[03]; the depth of criticality analysis is defined].'),
('003255','draft','2013-09-30','DISA FSO','policy','Defines decision points in the system development life cycle at which the developer of the system, system component, or system service is required to perform a criticality analysis.','SA-15(03)(a)','N/A','Determine if the developer of the system, system component, or system service is required to perform a criticality analysis at [SA-15(03)_ODP[01]; decision points in the system development life cycle are defined] in the system development life cycle.'),
('003272','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to reduce attack surfaces to organization-defined thresholds.','SA-15(05)','N/A','Determine if the developer of the system, system component, or system service is required to reduce attack surfaces to [SA-15(05)_ODP; thresholds to which attack surfaces are to be reduced are defined].'),
('003273','draft','2013-10-03','DISA FSO','policy','Defines the thresholds to which the developer of the system, system component, or system service is required to reduce attack surfaces.','SA-15(05)','N/A','Determine if the developer of the system, system component, or system service is required to reduce attack surfaces to [SA-15(05)_ODP; thresholds to which attack surfaces are to be reduced are defined].'),
('003274','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to implement an explicit process to continuously improve the development process.','SA-15(06)','N/A','Determine if the developer of the system, system component, or system service is required to implement an explicit process to continuously improve the development process.'),
('003275','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system services, on an organization-defined frequency, to perform an automated vulnerability analysis using organization-defined tools.','SA-15(07)(a)','N/A','Determine if the developer of the system, system component, or system service is required to perform automated vulnerability analysis [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] using [SA-15(07)_ODP[02]; tools used to perform automated vulnerability analysis are defined].'),
('003276','draft','2013-10-03','DISA FSO','policy','Defines the tools the developer of the system, system component, or system services uses to perform an automated vulnerability analysis.','SA-15(07)(a)','N/A','Determine if the developer of the system, system component, or system service is required to perform automated vulnerability analysis [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] using [SA-15(07)_ODP[02]; tools used to perform automated vulnerability analysis are defined].'),
('003277','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system services, on an organization-defined frequency, to determine the exploitation potential for discovered vulnerabilities.','SA-15(07)(b)','N/A','Determine if the developer of the system, system component, or system service is required to determine the exploitation potential for discovered vulnerabilities [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined].'),
('003278','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system services, on an organization-defined frequency, to determine potential risk mitigations for delivered vulnerabilities.','SA-15(07)(c)','N/A','Determine if the developer of the system, system component, or system service is required to determine potential risk mitigations [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] for delivered vulnerabilities.'),
('003279','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system services, on an organization-defined frequency, to deliver the outputs of the tools and results of the vulnerability analysis to organization-defined personnel or roles.','SA-15(07)(d)','N/A','Determine if the developer of the system, system component, or system service is required to deliver the outputs of the tools and results of the analysis [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] to [SA-15(07)_ODP[03]; personnel or roles to whom the outputs of tools and results of the analysis are to be delivered is/are defined].'),
('003280','draft','2013-10-03','DISA FSO','policy','Defines the personnel or roles to whom the outputs of the tools and results of the vulnerability analysis are delivered.','SA-15(07)(d)','N/A','Determine if the developer of the system, system component, or system service is required to deliver the outputs of the tools and results of the analysis [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] to [SA-15(07)_ODP[03]; personnel or roles to whom the outputs of tools and results of the analysis are to be delivered is/are defined].'),
('003281','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to use threat modeling from similar systems, components, or services to inform the current development process.','SA-15(08)','N/A','Determine if: - the developer of the system, system component, or system service is required to use threat modeling from similar systems, components, or services to inform the current development process. - the developer of the system, system component, or system service is required to use vulnerability analyses from similar systems, components, or services to inform the current development process.'),
('003282','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to use vulnerability analysis from similar systems, components, or services to inform the current development process.','SA-15(08)','N/A','Determine if: - the developer of the system, system component, or system service is required to use threat modeling from similar systems, components, or services to inform the current development process. - the developer of the system, system component, or system service is required to use vulnerability analyses from similar systems, components, or services to inform the current development process.'),
('003289','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to provide an incident response plan.','SA-15(10)','N/A','Determine if: - the developer of the system, system component, or system service is required to provide an incident response plan. - the developer of the system, system component, or system service is required to implement an incident response plan. - the developer of the system, system component, or system service is required to test an incident response plan.'),
('003290','draft','2013-10-03','DISA FSO','policy','Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security review.','SA-15(11)','N/A','Determine if the developer of the system or system component is required to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.'),
('003291','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to provide organization-defined training on the correct use and operation of the implemented security functions, controls, and/or mechanisms.','SA-16','N/A','Determine if the developer of the system, system component, or system service is required to provide [SA-16_ODP; training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms provided by the developer of the system, system component, or system service is defined] on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.'),
('003292','draft','2013-10-03','DISA FSO','policy','Defines the training the developer of the system, system component, or system service is required to provide on the correct use and operation of the implemented security functions, controls, and/or mechanisms.','SA-16','N/A','Determine if the developer of the system, system component, or system service is required to provide [SA-16_ODP; training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms provided by the developer of the system, system component, or system service is defined] on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.'),
('003293','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce a design specification and security architecture.',NULL,'N/A',NULL),
('003294','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce a design specification and security architecture that is consistent with and supportive of the organization''s security architecture which is established within and is an integrated part of the organization''s enterprise architecture.','SA-17a.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that are consistent with the organization''s security architecture, which is an integral part the organization''s enterprise architecture. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that are consistent with the organization''s privacy architecture, which is an integral part the organization''s enterprise architecture.'),
('003295','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce a design specification and security architecture that accurately and completely describes the required security functionality.','SA-17b.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that accurately and completely describe the required security functionality and the allocation of controls among physical and logical components. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that accurately and completely describe the required privacy functionality and the allocation of controls among physical and logical components.'),
('003296','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce a design specification and security architecture that accurately and completely describes the allocation of security controls among physical and logical components.','SA-17b.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that accurately and completely describe the required security functionality and the allocation of controls among physical and logical components. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that accurately and completely describe the required privacy functionality and the allocation of controls among physical and logical components.'),
('003297','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce a design specification and security architecture that expresses how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection.','SA-17c.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that express how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that express how individual privacy functions, mechanisms, and services work together to provide required privacy capabilities and a unified approach to protection.'),
('003298','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system to produce, as an integral part of the development process, a formal policy model describing the organization-defined elements of organizational security policy to be enforced.','SA-17(01)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[01]; organizational security policy to be enforced is defined] to be enforced. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[02]; organizational privacy policy to be enforced is defined] to be enforced.'),
('003299','draft','2013-10-03','DISA FSO','policy','Defines the elements of organizational security policy to be described in the formal policy model for enforcement on the system, system component, or system service.','SA-17(01)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[01]; organizational security policy to be enforced is defined] to be enforced. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[02]; organizational privacy policy to be enforced is defined] to be enforced.'),
('003300','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented.','SA-17(01)(b)','N/A','Determine if: - the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented. - the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational privacy policy when implemented.'),
('003301','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to define security-relevant hardware.','SA-17(02)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to define security-relevant hardware. - the developer of the system, system component, or system service is required to define security-relevant software. - the developer of the system, system component, or system service is required to define security-relevant firmware. '),
('003303','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to define security-relevant software.','SA-17(02)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to define security-relevant hardware. - the developer of the system, system component, or system service is required to define security-relevant software. - the developer of the system, system component, or system service is required to define security-relevant firmware. '),
('003304','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to define security-relevant firmware.','SA-17(02)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to define security-relevant hardware. - the developer of the system, system component, or system service is required to define security-relevant software. - the developer of the system, system component, or system service is required to define security-relevant firmware. '),
('003305','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to provide a rationale that the definition for security-relevant hardware is complete.','SA-17(02)(b)','N/A','Determine if the developer of the system, system component, or system service is required to provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.'),
('003306','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to provide a rationale that the definition for security-relevant software is complete.','SA-17(02)(b)','N/A','Determine if the developer of the system, system component, or system service is required to provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.'),
('003307','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to provide a rationale that the definition for security-relevant firmware is complete.','SA-17(02)(b)','N/A','Determine if the developer of the system, system component, or system service is required to provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.'),
('003308','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.','SA-17(03)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects.'),
('003309','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant software in terms of exceptions, error messages, and effects.','SA-17(03)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects.'),
('003310','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','SA-17(03)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects.'),
('003311','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model.','SA-17(03)(b)','N/A','Determine if the developer of the system, system component, or system service is required to show proof that the formal top-level specification is consistent with the formal policy model to the extent feasible with additional informal demonstration as necessary.'),
('003312','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware.','SA-17(03)(c)','N/A','Determine if the developer of the system, system component, or system service is required to show via informal demonstration that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware.'),
('003313','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant software.','SA-17(03)(c)','N/A','Determine if the developer of the system, system component, or system service is required to show via informal demonstration that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware.'),
('003314','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant firmware.','SA-17(03)(c)','N/A','Determine if the developer of the system, system component, or system service is required to show via informal demonstration that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware.'),
('003315','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show that the formal top-level specification is an accurate description of the implemented security-relevant hardware.','SA-17(03)(d)','N/A','Determine if the developer of the system, system component, or system service is required to show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware.'),
('003316','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show that the formal top-level specification is an accurate description of the implemented security-relevant software.','SA-17(03)(d)','N/A','Determine if the developer of the system, system component, or system service is required to show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware.'),
('003317','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show that the formal top-level specification is an accurate description of the implemented security-relevant firmware.','SA-17(03)(d)','N/A','Determine if the developer of the system, system component, or system service is required to show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware.'),
('003318','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to describe the security-relevant hardware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware.','SA-17(03)(e)','N/A','Determine if the developer of the system, system component, or system service is required to describe the security-relevant hardware, software, and firmware mechanisms that are not addressed in the formal top-level specification but are strictly internal to the security-relevant hardware, software, and firmware.'),
('003319','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to describe the security-relevant software mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant software.','SA-17(03)(e)','N/A','Determine if the developer of the system, system component, or system service is required to describe the security-relevant hardware, software, and firmware mechanisms that are not addressed in the formal top-level specification but are strictly internal to the security-relevant hardware, software, and firmware.'),
('003320','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to describe the security-relevant firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant firmware.','SA-17(03)(e)','N/A','Determine if the developer of the system, system component, or system service is required to describe the security-relevant hardware, software, and firmware mechanisms that are not addressed in the formal top-level specification but are strictly internal to the security-relevant hardware, software, and firmware.'),
('003321','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware in terms of exceptions, error messages, and effects.','SA-17(04)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects.'),
('003322','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant software in terms of exceptions, error messages, and effects.','SA-17(04)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects.'),
('003323','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant firmware in terms of exceptions, error messages, and effects.','SA-17(04)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects.'),
('003324','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration or convincing argument with formal methods as feasible that the descriptive top-level specification is consistent with the formal policy model.','SA-17(04)(b)','N/A','Determine if the developer of the system, system component, or system service is required to show via [SA-17(04)_ODP; one of the following PARAMETER VALUES is selected: {informal demonstration, convincing argument with formal methods as feasible}] that the descriptive top-level specification is consistent with the formal policy model.'),
('003325','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware.','SA-17(04)(c)','N/A','Determine if the developer of the system, system component, or system service is required to show via informal demonstration that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware.'),
('003326','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant software.','SA-17(04)(c)','N/A','Determine if the developer of the system, system component, or system service is required to show via informal demonstration that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware.'),
('003327','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant firmware.','SA-17(04)(c)','N/A','Determine if the developer of the system, system component, or system service is required to show via informal demonstration that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware.'),
('003328','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware.','SA-17(04)(d)','N/A','Determine if the developer of the system, system component, or system service is required to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware.'),
('003329','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant software.','SA-17(04)(d)','N/A','Determine if the developer of the system, system component, or system service is required to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware.'),
('003330','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant firmware.','SA-17(04)(d)','N/A','Determine if the developer of the system, system component, or system service is required to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware.'),
('003331','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to describe the security-relevant hardware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware.','SA-17(04)(e)','N/A','Determine if the developer of the system, system component, or system service is required to describe the security-relevant hardware, software, and firmware mechanisms that are not addressed in the descriptive top-level specification but are strictly internal to the security-relevant hardware, software, and firmware.'),
('003332','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to describe the security-relevant software mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant software.','SA-17(04)(e)','N/A','Determine if the developer of the system, system component, or system service is required to describe the security-relevant hardware, software, and firmware mechanisms that are not addressed in the descriptive top-level specification but are strictly internal to the security-relevant hardware, software, and firmware.'),
('003333','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to describe the security-relevant firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant firmware.','SA-17(04)(e)','N/A','Determine if the developer of the system, system component, or system service is required to describe the security-relevant hardware, software, and firmware mechanisms that are not addressed in the descriptive top-level specification but are strictly internal to the security-relevant hardware, software, and firmware.'),
('003334','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to design and structure the security-relevant hardware to use a complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(05)(a)','N/A','Determine if the developer of the system, system component, or system service is required to design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003335','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to design and structure the security-relevant software to use a complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(05)(a)','N/A','Determine if the developer of the system, system component, or system service is required to design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003336','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to design and structure the security-relevant firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(05)(a)','N/A','Determine if the developer of the system, system component, or system service is required to design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics.'),
('003337','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to internally structure the security-relevant hardware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(05)(b)','N/A','Determine if the developer of the system, system component, or system service is required to internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.'),
('003338','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to internally structure the security-relevant software with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(05)(b)','N/A','Determine if the developer of the system, system component, or system service is required to internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.'),
('003339','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, system component, or system service to internally structure the security-relevant firmware with specific regard for the complete, conceptually simple protection mechanism with precisely defined semantics.','SA-17(05)(b)','N/A','Determine if the developer of the system, system component, or system service is required to internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.'),
('003340','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, component, or system service to structure security-relevant hardware to facilitate testing.','SA-17(06)','N/A','Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate testing.'),
('003341','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, component, or system service to structure security-relevant software to facilitate testing.','SA-17(06)','N/A','Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate testing.'),
('003342','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, component, or system service to structure security-relevant firmware to facilitate testing.','SA-17(06)','N/A','Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate testing.'),
('003343','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, component, or system service to structure security-relevant hardware to facilitate controlling access with least privilege.','SA-17(07)','N/A','Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.'),
('003344','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, component, or system service to structure security-relevant software to facilitate controlling access with least privilege.','SA-17(07)','N/A','Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.'),
('003345','draft','2013-10-03','DISA FSO','policy','Require the developer of the system, component, or system service to structure security-relevant firmware to facilitate controlling access with least privilege.','SA-17(07)','N/A','Determine if the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.'),
('003372','draft','2013-10-03','DISA FSO','policy','Define the support from external providers to be provided for alternative sources for continued support for unsupported system components.','SA-22b.','N/A','Determine if [SA-22_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {in-house support; [SA-22_ODP[02]; support from external providers is defined (if selected)]}] provide options for alternative sources for continued support for unsupported components.'),
('003373','draft','2013-10-03','DISA FSO','policy','Provide in-house support and/or organization-defined support from external providers for alternative sources for continued support for unsupported components.','SA-22b.','N/A','Determine if [SA-22_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {in-house support; [SA-22_ODP[02]; support from external providers is defined (if selected)]}] provide options for alternative sources for continued support for unsupported components.'),
('003376','draft','2013-10-03','DISA FSO','policy','Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer.','SA-22a.','N/A','Determine if system components are replaced when support for the components is no longer available from the developer, vendor, or manufacturer.'),
('003381','draft','2013-10-03','DISA FSO','policy','Defines additional personnel screening criteria that must be satisfied by the developer of an organization-defined system, system component, or system service.','SA-21b.','N/A','Determine if the developer of [SA-21_ODP[01]; the system, systems component, or system service that the developer has access to is/are defined] is required to satisfy [SA-21_ODP[03]; additional personnel screening criteria for the developer are defined].'),
('003382','draft','2013-10-03','DISA FSO','policy','Require that the developer of an organization-defined system, system component, or system service satisfies organization-defined additional personnel screening criteria.','SA-21b.','N/A','Determine if the developer of [SA-21_ODP[01]; the system, systems component, or system service that the developer has access to is/are defined] is required to satisfy [SA-21_ODP[03]; additional personnel screening criteria for the developer are defined].'),
('003383','draft','2013-10-03','DISA FSO','policy','Defines the official government duties to be assigned to the developer of an organization-defined system, system component, or system service.','SA-21a.','N/A','Determine if the developer of [SA-21_ODP[01]; the system, systems component, or system service that the developer has access to is/are defined] is required to have appropriate access authorizations as determined by assigned [SA-21_ODP[02]; official government duties assigned to the developer are defined].'),
('003384','draft','2013-10-03','DISA FSO','policy','Defines the system, system component, or system service which requires the system developer to have appropriate access authorizations, satisfy additional personnel screening criteria, and provide information that the access authorizations and screening criteria are satisfied.',NULL,'N/A',NULL),
('003385','draft','2013-10-03','DISA FSO','policy','Require that the developer of an organization-defined system, system component, or system service has appropriate access authorizations as determined by assigned organization-defined official government duties.','SA-21a.','N/A','Determine if the developer of [SA-21_ODP[01]; the system, systems component, or system service that the developer has access to is/are defined] is required to have appropriate access authorizations as determined by assigned [SA-21_ODP[02]; official government duties assigned to the developer are defined].'),
('003386','draft','2013-10-03','DISA FSO','policy','Defines the critical system components to re-implement or custom develop.','SA-20','N/A','Determine if [SA-20_ODP; critical system components to be reimplemented or custom-developed are defined] are reimplemented or custom-developed.'),
('003387','draft','2013-10-03','DISA FSO','policy','Re-implement or custom develops organization-defined critical system components.','SA-20','N/A','Determine if [SA-20_ODP; critical system components to be reimplemented or custom-developed are defined] are reimplemented or custom-developed.'),
('003601','draft','2022-03-01','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level access control policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','AC-01a.01(b)','N/A','Determine if the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('003602','draft','2022-03-01','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','AC-01a.01(a)','N/A','Determine if: - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses purpose. - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses scope. - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses roles. - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses responsibilities. - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses management commitment. - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses coordination among organizational entities. - the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy addresses compliance.'),
('003603','draft','2022-03-01','DISA','policy','Disseminate the organization-level; mission/business process-level; and/or system-level access control policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines to organization-defined personnel or roles.','AC-01a.01(b)','N/A','Determine if the [AC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] access control policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('003604','draft','2022-03-01','DISA','policy','Develop and document procedures to facilitate the implementation of the organization-level; mission/business process-level; and/or system-level access control policy and the associated access control.','AC-01a.02','N/A','Determine if: - access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented. - the access control procedures are disseminated to [AC-01_ODP[02]; personnel or roles to whom the access control procedures are to be disseminated is/are defined].'),
('003605','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the development and documentation of the access control policy and procedures.','AC-01b.','N/A','Determine if the [AC-01_ODP[04]; an official to manage the access control policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the access control policy and procedures.'),
('003606','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the dissemination of the access control policy and procedures.','AC-01b.','N/A','Determine if the [AC-01_ODP[04]; an official to manage the access control policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the access control policy and procedures.'),
('003607','draft','2022-03-01','DISA','policy','Defines the official designated to manage the development, documentation, and dissemination of the access control policy and procedures.','AC-01b.','N/A','Determine if the [AC-01_ODP[04]; an official to manage the access control policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the access control policy and procedures.'),
('003608','draft','2022-03-01','DISA','policy','Review and update the current access control policy following organization-defined events.','AC-01c.01','N/A','Determine if: - the current access control policy is reviewed and updated [AC-01_ODP[05]; the frequency at which the current access control policy is reviewed and updated is defined]. - the current access control policy is reviewed and updated following [AC-01_ODP[06]; events that would require the current access control policy to be reviewed and updated are defined].'),
('003609','draft','2022-03-01','DISA','policy','Defines the events following reviewing and updating the current access control policy.','AC-01c.01','N/A','Determine if: - the current access control policy is reviewed and updated [AC-01_ODP[05]; the frequency at which the current access control policy is reviewed and updated is defined]. - the current access control policy is reviewed and updated following [AC-01_ODP[06]; events that would require the current access control policy to be reviewed and updated are defined].'),
('003610','draft','2022-03-01','DISA','policy','Review and update the current access control procedures following organization-defined events.','AC-01c.02','N/A','Determine if: - the current access control procedures are reviewed and updated [AC-01_ODP[07]; the frequency at which the current access control procedures are reviewed and updated is defined;]. - the current access control procedures are reviewed and updated following [AC-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('003611','draft','2022-03-01','DISA','policy','Defines the events following reviewing and updating the current access control procedures.','AC-01c.02','N/A','Determine if: - the current access control procedures are reviewed and updated [AC-01_ODP[07]; the frequency at which the current access control procedures are reviewed and updated is defined;]. - the current access control procedures are reviewed and updated following [AC-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('003612','draft','2022-03-01','DISA','policy','Define and document the types of accounts allowed and specifically prohibited for use within the system.','AC-02a.','N/A','Determine if: - account types allowed for use within the system are defined and documented. - account types specifically prohibited for use within the system are defined and documented.'),
('003613','draft','2022-03-01','DISA','policy','Require organization-defined prerequisites and criteria for group membership.','AC-02c.','N/A','Determine if [AC-02_ODP[01]; prerequisites and criteria for group and role membership are defined] for group and role membership are required.'),
('003614','draft','2022-03-01','DISA','policy','Require organization-defined prerequisites and criteria for role membership.','AC-02c.','N/A','Determine if [AC-02_ODP[01]; prerequisites and criteria for group and role membership are defined] for group and role membership are required.'),
('003615','draft','2022-03-01','DISA','policy','Defines the prerequisites and criteria for group and role membership.','AC-02c.','N/A','Determine if [AC-02_ODP[01]; prerequisites and criteria for group and role membership are defined] for group and role membership are required.'),
('003616','draft','2022-03-01','DISA','policy','Defines the attributes (as required) for each account.','AC-02d.03','N/A','Determine if: - access authorizations (i.e., privileges) are specified for each account. - [AC-02_ODP[02]; attributes (as required) for each account are defined] are specified for each account. '),
('003617','draft','2022-03-01','DISA','policy','Create, enable, modify, disable, and remove system accounts in accordance with organization-defined policy.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('003618','draft','2022-03-01','DISA','policy','Create, enable, modify, disable, and remove system accounts in accordance with organization-defined criteria.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('003619','draft','2022-03-01','DISA','policy','Create, enable, modify, disable, and remove system accounts in accordance with organization-defined prerequisites.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('003620','draft','2022-03-01','DISA','policy','Defines the policy to be employed when creating, enabling, modifying, disabling, and removing information system accounts.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('003621','draft','2022-03-01','DISA','policy','Defines the prerequisites to be employed when creating, enabling, modifying, disabling, and removing information system accounts.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('003622','draft','2022-03-01','DISA','policy','Defines the criteria to be employed when creating, enabling, modifying, disabling, and removing information system accounts.','AC-02f.','N/A','Determine if: - accounts are created in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are enabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are modified in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are disabled in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined]. - accounts are removed in accordance with [AC-02_ODP[04]; policy, procedures, prerequisites, and criteria for account creation, enabling, modification, disabling, and removal are defined].'),
('003623','draft','2022-03-01','DISA','policy','Defines the personnel or roles of whom to notify when accounts are no longer required; when users are terminated or transferred; and when system usage or need-to-know changes for an individual.',NULL,'N/A',NULL),
('003624','draft','2022-03-01','DISA','policy','Defines the time period of when to notify account managers for each situation.',NULL,'N/A',NULL),
('003625','draft','2022-03-01','DISA','policy','Defines the attributes (as required) for authorizing access to the system.','AC-02i.03','N/A','Determine if access to the system is authorized based on [AC-02_ODP[09]; attributes needed to authorize system access (as required) are defined].'),
('003626','draft','2022-03-01','DISA','policy','Align account management processes with personnel termination and transfer processes.','AC-02l.','N/A','Determine if: - account management processes are aligned with personnel termination processes. - account management processes are aligned with personnel transfer processes.'),
('003627','draft','2022-03-01','DISA','technical','Disable accounts when the accounts have expired.','AC-02(03)(a)','N/A','Determine if accounts are disabled within [AC-02(03)_ODP[01]; time period within which to disable accounts is defined] when the accounts have expired.'),
('003628','draft','2022-03-01','DISA','technical','Disable accounts when the accounts are no longer associated to a user.','AC-02(03)(b)','N/A','Determine if accounts are disabled within [AC-02(03)_ODP[01]; time period within which to disable accounts is defined] when the accounts are no longer associated with a user or individual.'),
('003629','draft','2022-03-01','DISA','technical','Disable accounts when the accounts are in violation of organizational policy.','AC-02(03)(c)','N/A','Determine if accounts are disabled within [AC-02(03)_ODP[01]; time period within which to disable accounts is defined] when the accounts are in violation of organizational policy.'),
('003630','draft','2022-03-01','DISA','policy','Monitor changes to roles or attributes.','AC-02(07)(c)','N/A','Determine if changes to roles or attributes are monitored.'),
('003631','draft','2022-03-01','DISA','technical','Defines the system accounts that can be dynamically activated.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('003632','draft','2022-03-01','DISA','technical','Activate organization-defined system accounts dynamically.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('003633','draft','2022-03-01','DISA','technical','Defines the system accounts that can be dynamically managed.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('003634','draft','2022-03-01','DISA','technical','Manage organization-defined system accounts dynamically.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('003635','draft','2022-03-01','DISA','technical','Defines the system accounts that can be dynamically deactivated.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('003636','draft','2022-03-01','DISA','technical','Deactivate organization-defined system accounts dynamically.','AC-02(08)','N/A','Determine if: - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are created dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are activated dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are managed dynamically. - [AC-02(08)_ODP; system accounts that are dynamically created, activated, managed, and deactivated are defined] are deactivated dynamically.'),
('003637','draft','2022-03-01','DISA','policy','Defines the significant risks that may be discovered requiring disabled accounts of individuals.','AC-02(13)','N/A','Determine if accounts of individuals are disabled within [AC-02(13)_ODP[01]; time period within which to disable accounts of individuals who are discovered to pose significant risk is defined] of discovery of [AC-02(13)_ODP[02]; significant risks leading to disabling accounts are defined].'),
('003638','draft','2022-03-01','DISA','technical','Enforce organization-defined discretionary access control policies over defined subjects and objects where the policy specifies that a subject that has been granted access to information can pass the information to any other subjects or objects.','AC-03(04)(a)','N/A','Determine if [AC-03(04)_ODP[01]; discretionary access control policy enforced over the set of covered subjects is defined] and [AC-03(04)_ODP[02]; discretionary access control policy enforced over the set of covered objects is defined] are enforced where the policy specifies that a subject that has been granted access to information can pass the information to any other subjects or objects.'),
('003639','draft','2022-03-01','DISA','technical','Enforce organization-defined discretionary access control policies over defined subjects and objects where the policy specifies that a subject that has been granted access to information can grant its privileges to other subjects.','AC-03(04)(b)','N/A','Determine if [AC-03(04)_ODP[01]; discretionary access control policy enforced over the set of covered subjects is defined] and [AC-03(04)_ODP[02]; discretionary access control policy enforced over the set of covered objects is defined] are enforced where the policy specifies that a subject that has been granted access to information can grant its privileges to other subjects.'),
('003640','draft','2022-03-01','DISA','technical','Enforce organization-defined discretionary access control policies over defined subjects and objects where the policy specifies that a subject that has been granted access to information can change security attributes on subjects, objects, the system, or the system''s components.','AC-03(04)(c)','N/A','Determine if [AC-03(04)_ODP[01]; discretionary access control policy enforced over the set of covered subjects is defined] and [AC-03(04)_ODP[02]; discretionary access control policy enforced over the set of covered objects is defined] are enforced where the policy specifies that a subject that has been granted access to information can change security attributes on subjects, objects, the system, or the system''s components.'),
('003641','draft','2022-03-01','DISA','technical','Enforce organization-defined discretionary access control policies over defined subjects and objects where the policy specifies that a subject that has been granted access to information can choose the security attributes to be associated with newly created or revised objects.','AC-03(04)(d)','N/A','Determine if [AC-03(04)_ODP[01]; discretionary access control policy enforced over the set of covered subjects is defined] and [AC-03(04)_ODP[02]; discretionary access control policy enforced over the set of covered objects is defined] are enforced where the policy specifies that a subject that has been granted access to information can choose the security attributes to be associated with newly created or revised objects.'),
('003642','draft','2022-03-01','DISA','technical','Enforce organization-defined discretionary access control policies over defined subjects and objects where the policy specifies that a subject that has been granted access to information can change the rules governing access control.','AC-03(04)(e)','N/A','Determine if [AC-03(04)_ODP[01]; discretionary access control policy enforced over the set of covered subjects is defined] and [AC-03(04)_ODP[02]; discretionary access control policy enforced over the set of covered objects is defined] are enforced where the policy specifies that a subject that has been granted access to information can change the rules governing access control.'),
('003643','draft','2022-03-01','DISA','policy','Defines the organization-defined roles for which it will employ an audited override of automated access control mechanisms.','AC-03(10)','N/A','Determine if an audited override of automated access control mechanisms is employed under [AC-03(10)_ODP[01]; conditions under which to employ an audited override of automated access control mechanisms are defined] by [AC-03(10)_ODP[02]; roles allowed to employ an audited override of automated access control mechanisms are defined].'),
('003644','draft','2022-03-01','DISA','technical','Restrict direct access to data repositories containing organization-defined information types.','AC-03(11)','N/A','Determine if access to data repositories containing [AC-03(11)_ODP; information types requiring restricted access to data repositories are defined] is restricted.'),
('003645','draft','2022-03-01','DISA','technical','Defines the information types of which to restrict direct access to data repositories.','AC-03(11)','N/A','Determine if access to data repositories containing [AC-03(11)_ODP; information types requiring restricted access to data repositories are defined] is restricted.'),
('003646','draft','2022-03-01','DISA','technical','Require applications to assert, as part of the installation process, the access needed to the organization-defined system applications and functions.','AC-03(12)(a)','N/A','Determine if as part of the installation process, applications are required to assert the access needed to the following system applications and functions: [AC-03(12)_ODP; system applications and functions requiring access assertion are defined].'),
('003647','draft','2022-03-01','DISA','technical','Defines the organization-defined system applications and functions as required of the applications as part of the installation process.','AC-03(12)(a)','N/A','Determine if as part of the installation process, applications are required to assert the access needed to the following system applications and functions: [AC-03(12)_ODP; system applications and functions requiring access assertion are defined].'),
('003648','draft','2022-03-01','DISA','technical','Require applications to provide an enforcement mechanism to prevent other-than-asserted access.','AC-03(12)(b)','N/A','Determine if an enforcement mechanism to prevent unauthorized access is provided.'),
('003649','draft','2022-03-01','DISA','technical','Approve access changed after initial installations of the application.','AC-03(12)(c)','N/A','Determine if access changes after initial installation of the application are approved.'),
('003650','draft','2022-03-01','DISA','technical','Enforce attribute-based access control policy over defined subjects and objects based upon organization-defined attributes to assume access permissions.','AC-03(13)','N/A','Determine if: - the attribute-based access control policy is enforced over defined subjects. - the attribute-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(13)_ODP; attributes to assume access permissions are defined].'),
('003651','draft','2022-03-01','DISA','technical','Defines the attributes to assume access permissions for enforcing attribute-based access control policy.','AC-03(13)','N/A','Determine if: - the attribute-based access control policy is enforced over defined subjects. - the attribute-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(13)_ODP; attributes to assume access permissions are defined].'),
('003652','draft','2022-03-01','DISA','technical','Enforce attribute-based control access over defined subjects and objects based upon organization-defined attributes to assume access permissions.','AC-03(13)','N/A','Determine if: - the attribute-based access control policy is enforced over defined subjects. - the attribute-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(13)_ODP; attributes to assume access permissions are defined].'),
('003653','draft','2022-03-01','DISA','technical','Defines the attributes to assume access permissions for enforcing attribute-based control access.','AC-03(13)','N/A','Determine if: - the attribute-based access control policy is enforced over defined subjects. - the attribute-based access control policy is enforced over defined objects. - access is controlled based on [AC-03(13)_ODP; attributes to assume access permissions are defined].'),
('003654','draft','2022-03-01','DISA','technical','Provide organization-defined mechanisms to enable individuals to have access to the following elements of their personally identifiable information: organization-defined elements.','AC-03(14)','N/A','Determine if [AC-03(14)_ODP[01]; mechanisms enabling individuals to have access to elements of their personally identifiable information are defined] are provided to enable individuals to have access to [AC-03(14)_ODP[02]; elements of personally identifiable information to which individuals have access are defined] of their personally identifiable information.'),
('003655','draft','2022-03-01','DISA','technical','Defines the mechanisms to be provided for access to elements of personally identifiable information.','AC-03(14)','N/A','Determine if [AC-03(14)_ODP[01]; mechanisms enabling individuals to have access to elements of their personally identifiable information are defined] are provided to enable individuals to have access to [AC-03(14)_ODP[02]; elements of personally identifiable information to which individuals have access are defined] of their personally identifiable information.'),
('003656','draft','2022-03-01','DISA','technical','Defines the elements of personally identifiable information.','AC-03(14)','N/A','Determine if [AC-03(14)_ODP[01]; mechanisms enabling individuals to have access to elements of their personally identifiable information are defined] are provided to enable individuals to have access to [AC-03(14)_ODP[02]; elements of personally identifiable information to which individuals have access are defined] of their personally identifiable information.'),
('003657','draft','2022-03-01','DISA','technical','Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy.','AC-03(15)(a)','N/A','Determine if: - [AC-03(15)_ODP[01]; a mandatory access control policy enforced over the set of covered subjects specified in the policy is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(15)_ODP[02]; a mandatory access control policy enforced over the set of covered objects specified in the policy is defined] is enforced over the set of covered objects specified in the policy.'),
('003658','deprecated','2022-03-01','DISA','technical','Defines the mandatory access control policies that are to be enforced over all subjects and objects.','AC-03(15)(a)','N/A','Determine if: - [AC-03(15)_ODP[01]; a mandatory access control policy enforced over the set of covered subjects specified in the policy is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(15)_ODP[02]; a mandatory access control policy enforced over the set of covered objects specified in the policy is defined] is enforced over the set of covered objects specified in the policy.'),
('003659','draft','2022-03-01','DISA','technical','Enforce organization-defined discretionary access control policy over the set of covered subjects and objects specified in the policy.','AC-03(15)(b)','N/A','Determine if: - [AC-03(15)_ODP[03]; a discretionary access control policy enforced over the set of covered subjects specified in the policy is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(15)_ODP[04]; a discretionary access control policy enforced over the set of covered objects specified in the policy is defined] is enforced over the set of covered objects specified in the policy.'),
('003660','draft','2022-03-01','DISA','technical','Defines the discretionary access control policies the system is to enforce over subjects and objects.','AC-03(15)(b)','N/A','Determine if: - [AC-03(15)_ODP[03]; a discretionary access control policy enforced over the set of covered subjects specified in the policy is defined] is enforced over the set of covered subjects specified in the policy. - [AC-03(15)_ODP[04]; a discretionary access control policy enforced over the set of covered objects specified in the policy is defined] is enforced over the set of covered objects specified in the policy.'),
('003661','draft','2022-03-01','DISA','technical','Defines the privacy attributes to be used to enforce organization-defined information flow control policies.','AC-04(01)','N/A','Determine if: - [AC-04(01)_ODP[01]; security attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[03]; information objects to be associated with information security attributes are defined], [AC-04(01)_ODP[05]; source objects to be associated with information security attributes are defined], and [AC-04(01)_ODP[07]; destination objects to be associated with information security attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions. - [AC-04(01)_ODP[02]; privacy attributes to be associated with information, source, and destination objects are defined] associated with [AC-04(01)_ODP[04]; information objects to be associated with privacy attributes are defined], [AC-04(01)_ODP[06]; source objects to be associated with privacy attributes are defined], and [AC-04(01)_ODP[08]; destination objects to be associated with privacy attributes are defined] are used to enforce [AC-04(01)_ODP[09]; information flow control policies as a basis for enforcement of flow control decisions are defined] as a basis for flow control decisions.'),
('003662','draft','2022-03-01','DISA','policy','Defines the information flow control mechanisms to prevent the bypassing of encrypted information.','AC-04(04)','N/A','Determine if encrypted information is prevented from bypassing [AC-04(04)_ODP[01]; information flow control mechanisms that encrypted information is prevented from bypassing are defined] by [AC-04(04)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [AC-04(04)_ODP[03]; the organization-defined procedure or method used to prevent encrypted information from bypassing information flow control mechanisms is defined (if selected)]].'),
('003663','draft','2022-03-01','DISA','technical','Enforce information flow control using organization-defined privacy policy filters as a basis for flow control decisions for organization-defined information flows.','AC-04(08)(a)','N/A','Determine if: - information flow control is enforced using [AC-04(08)_ODP[01]; security policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[03]; information flows for which information flow control is enforced by security filters are defined]. - information flow control is enforced using [AC-04(08)_ODP[02]; privacy policy filters to be used as a basis for enforcing information flow control are defined] as a basis for flow control decisions for [AC-04(08)_ODP[04]; information flows for which information flow control is enforced by privacy filters are defined].'),
('003664','draft','2022-03-01','DISA','technical','Enforce information flow control using block; strip; modify and/or quarantine data after a filter processing failure in accordance with organization-defined security or privacy policy.','AC-04(08)(b)','N/A','Determine if [AC-04(08)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {block; strip; modify; quarantine}] data after a filter processing failure in accordance with [AC-04(08)_ODP[06]; security policy identifying actions to be taken after a filter processing failure are defined]; [AC-04(08)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {block; strip; modify; quarantine}] data after a filter processing failure in accordance with [AC-04(08)_ODP[07]; privacy policy identifying actions to be taken after a filter processing failure are defined].'),
('003665','draft','2022-03-01','DISA','technical','Defines the security or privacy policy to be enforced using block; strip; modify and/or quarantine data after a filter processing failure.','AC-04(08)(b)','N/A','Determine if [AC-04(08)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {block; strip; modify; quarantine}] data after a filter processing failure in accordance with [AC-04(08)_ODP[06]; security policy identifying actions to be taken after a filter processing failure are defined]; [AC-04(08)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {block; strip; modify; quarantine}] data after a filter processing failure in accordance with [AC-04(08)_ODP[07]; privacy policy identifying actions to be taken after a filter processing failure are defined].'),
('003666','draft','2022-03-01','DISA','technical','Defines the security or privacy policy filters implemented when transferring information between security domains.','AC-04(19)','N/A','Determine if: - when transferring information between different security domains, [AC-04(19)_ODP[01]; security policy filters to be implemented on metadata are defined (if selected)] are implemented on metadata. - when transferring information between different security domains, [AC-04(19)_ODP[02]; privacy policy filters to be implemented on metadata are defined (if selected)] are implemented on metadata.'),
('003667','draft','2022-03-01','DISA','policy','When transferring information between security domains, modify non-releasable information by implementing organization-defined modification action.','AC-04(23)','N/A','Determine if when transferring information between security domains, non-releasable information is modified by implementing [AC-04(23)_ODP; modification action implemented on non-releasable information is defined].'),
('003668','draft','2022-03-01','DISA','policy','Defines the modification action when transferring information between different security domains.','AC-04(23)','N/A','Determine if when transferring information between security domains, non-releasable information is modified by implementing [AC-04(23)_ODP; modification action implemented on non-releasable information is defined].'),
('003669','draft','2022-03-01','DISA','technical','When transferring information between different security domains, parse incoming data into an internal normalized format.','AC-04(24)','N/A','Determine if: - when transferring information between different security domains, incoming data is parsed into an internal, normalized format. - when transferring information between different security domains, the data is regenerated to be consistent with its intended specification.'),
('003670','draft','2022-03-01','DISA','technical','When transferring information between different security domains, regenerate the data to be consistent with its intended specification.','AC-04(24)','N/A','Determine if: - when transferring information between different security domains, incoming data is parsed into an internal, normalized format. - when transferring information between different security domains, the data is regenerated to be consistent with its intended specification.'),
('003671','draft','2022-03-01','DISA','technical','When transferring information between different security domains, sanitize data to minimize delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography encoded data; spillage of sensitive information in accordance with organization-defined policy.','AC-04(25)','N/A','Determine if when transferring information between different security domains, data is sanitized to minimize [AC-04(25)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography-encoded data; spillage of sensitive information}] in accordance with [AC-04(25)_ODP[02]; policy for sanitizing data is defined].'),
('003672','draft','2022-03-01','DISA','technical','Defines the policy when transferring information between different security domains.','AC-04(25)','N/A','Determine if when transferring information between different security domains, data is sanitized to minimize [AC-04(25)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography-encoded data; spillage of sensitive information}] in accordance with [AC-04(25)_ODP[02]; policy for sanitizing data is defined].'),
('003673','draft','2022-03-01','DISA','policy','When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered.','AC-04(26)','N/A','Determine if: - when transferring information between different security domains, content-filtering actions are recorded and audited. - when transferring information between different security domains, results for the information being filtered are recorded and audited.'),
('003674','draft','2022-03-01','DISA','technical','When transferring information between different security domains, implement content filtering solutions that provide redundant and independent filtering mechanisms for each data type.','AC-04(27)','N/A','Determine if when transferring information between security domains, implemented content filtering solutions provide redundant and independent filtering mechanisms for each data type.'),
('003675','draft','2022-03-01','DISA','technical','When transferring information between different security domains, implement a linear content filter pipeline that is enforced with discretionary and mandatory access controls.','AC-04(28)','N/A','Determine if when transferring information between security domains, a linear content filter pipeline is implemented that is enforced with discretionary and mandatory access controls.'),
('003676','draft','2022-03-01','DISA','policy','When transferring information between different security domains, employ content filter orchestration engines to ensure that content filtering mechanisms successfully complete execution without errors.','AC-04(29)(a)','N/A','Determine if when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering mechanisms successfully complete execution without errors.'),
('003677','draft','2022-03-01','DISA','policy','When transferring information between different security domains, employ content filter orchestration engines to ensure that content filtering actions occur in the correct order and comply with organization-defined policy.','AC-04(29)(b)','N/A','Determine if: - when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering actions occur in the correct order. - when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering actions comply with [AC-04(29)_ODP; policy for content-filtering actions is defined].'),
('003678','draft','2022-03-01','DISA','technical','When transferring information between different security domains, implement content filtering mechanisms using multiple processes.','AC-04(30)','N/A','Determine if when transferring information between security domains, content-filtering mechanisms using multiple processes are implemented.'),
('003679','draft','2022-03-01','DISA','technical','When transferring information between different security domains, prevent the transfer of failed content to the receiving domain.','AC-04(31)','N/A','Determine if when transferring information between different security domains, the transfer of failed content to the receiving domain is prevented.'),
('003680','draft','2022-03-01','DISA','technical','When transferring information between different security domains, the process that transfers information between filter pipelines does not filter message content.','AC-04(32)(a)','N/A','Determine if when transferring information between different security domains, the process that transfers information between filter pipelines does not filter message content.'),
('003681','draft','2022-03-01','DISA','technical','When transferring information between different security domains, the process that transfers information between filter pipelines validates filtering metadata.','AC-04(32)(b)','N/A','Determine if when transferring information between different security domains, the process that transfers information between filter pipelines validates filtering metadata.'),
('003682','draft','2022-03-01','DISA','technical','When transferring information between different security domains, the process that transfers information between filter pipelines ensures the content associated with the filtering metadata has successfully completed filtering.','AC-04(32)(c)','N/A','Determine if when transferring information between different security domains, the process that transfers information between filter pipelines ensures that the content with the filtering metadata has successfully completed filtering.'),
('003683','draft','2022-03-01','DISA','technical','When transferring information between different security domains, the process that transfers information between filter pipelines transfers the content to the destination filter pipeline.','AC-04(32)(d)','N/A','Determine if when transferring information between different security domains, the process that transfers information between filter pipelines transfers the content to the destination filter pipeline.'),
('003684','draft','2022-03-01','DISA','policy','Identify and document organization-defined duties of individuals requiring separation.','AC-05b.','N/A','Determine if system access authorizations to support separation of duties are defined.'),
('003685','draft','2022-03-01','DISA','policy','Defines the individuals or roles who authorize access to organization-defined security functions.','AC-06(01)(a)','N/A','Determine if: - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[02]; security functions (deployed in hardware) for authorized access are defined]. - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[03]; security functions (deployed in software) for authorized access are defined]. - access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[04]; security functions (deployed in firmware) for authorized access are defined].'),
('003686','draft','2022-03-01','DISA','policy','Defines the individuals or roles who authorize access to organization-defined security-relevant information.','AC-06(01)(b)','N/A','Determine if access is authorized for [AC-06(01)_ODP[01]; individuals and roles with authorized access to security functions and security-relevant information are defined] to [AC-06(01)_ODP[05]; security-relevant information for authorized access is defined].'),
('003687','draft','2022-03-01','DISA','policy','Limit the number of unsuccessful biometric logon attempts to an organization-defined number.','AC-07(03)','N/A','Determine if unsuccessful biometric logon attempts are limited to [AC-07(03)_ODP; the number of unsuccessful biometric logon attempts is defined].'),
('003688','draft','2022-03-01','DISA','policy','Defines the number of allowed unsuccessful biometric logon attempts.','AC-07(03)','N/A','Determine if unsuccessful biometric logon attempts are limited to [AC-07(03)_ODP; the number of unsuccessful biometric logon attempts is defined].'),
('003689','draft','2022-03-01','DISA','policy','Allow the use of organization-defined authentication factors that are different from the primary authentication factors after the number of organization-defined consecutive invalid logon attempts have been exceeded.','AC-07(04)(a)','N/A','Determine if [AC-07(04)_ODP[01]; authentication factors allowed to be used that are different from the primary authentication factors are defined] that are different from the primary authentication factors are allowed to be used after the number of organization-defined consecutive invalid logon attempts have been exceeded.'),
('003690','draft','2022-03-01','DISA','policy','Defines the authentication factors after a number of organization-defined consecutive invalid logon attempts have been executed.','AC-07(04)(a)','N/A','Determine if [AC-07(04)_ODP[01]; authentication factors allowed to be used that are different from the primary authentication factors are defined] that are different from the primary authentication factors are allowed to be used after the number of organization-defined consecutive invalid logon attempts have been exceeded.'),
('003691','draft','2022-03-01','DISA','policy','Enforce a limit of organization-defined number consecutive invalid logon attempts through use of the alternative factors by a user during a organization-defined time period.','AC-07(04)(b)','N/A','Determine if a limit of [AC-07(04)_ODP[02]; the number of consecutive, invalid logon attempts through the use of alternative factors for which to enforce a limit by a user is defined] consecutive invalid logon attempts through the use of the alternative factors by the user during a [AC-07(04)_ODP[03]; time period during which a user can attempt logons through alternative factors is defined] is enforced.'),
('003692','draft','2022-03-01','DISA','policy','Defines the number enforced for logon attempts.','AC-07(04)(b)','N/A','Determine if a limit of [AC-07(04)_ODP[02]; the number of consecutive, invalid logon attempts through the use of alternative factors for which to enforce a limit by a user is defined] consecutive invalid logon attempts through the use of the alternative factors by the user during a [AC-07(04)_ODP[03]; time period during which a user can attempt logons through alternative factors is defined] is enforced.'),
('003693','draft','2022-03-01','DISA','technical','Display an explicit message to users indicating that the session will end at an organization-defined time until end of session.','AC-12(03)','N/A','Determine if an explicit message to users is displayed indicating that the session will end in [AC-12(03)_ODP; time until the end of session for display to users is defined].'),
('003694','draft','2022-03-01','DISA','technical','Defines the time until end of session, indicating the session will end.','AC-12(03)','N/A','Determine if an explicit message to users is displayed indicating that the session will end in [AC-12(03)_ODP; time until the end of session for display to users is defined].'),
('003695','draft','2022-03-01','DISA','policy','Defines the user actions that can be performed on the system without identification or authentication consistent with organizational missions/business functions.','AC-14a.','N/A','Determine if [AC-14_ODP; user actions that can be performed on the system without identification or authentication are defined] that can be performed on the system without identification or authentication consistent with organizational mission and business functions are identified.'),
('003696','draft','2022-03-01','DISA','policy','Defines privacy attributes having organization-defined types of privacy attribute values which are associated with information in storage.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('003697','draft','2022-03-01','DISA','policy','Defines privacy attributes having organization-defined types of privacy attribute values which are associated with information in process.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('003698','draft','2022-03-01','DISA','policy','Defines privacy attributes, having organization-defined types of privacy attribute values, which are associated with information in transmission.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('003699','draft','2022-03-01','DISA','policy','Defines privacy attribute values associated with organization-defined types of privacy attributes for information in storage.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('003700','draft','2022-03-01','DISA','policy','Defines privacy attribute values associated with organization-defined types of privacy attributes for information in process.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('003701','draft','2022-03-01','DISA','policy','Defines privacy attribute values associated with organization-defined types of privacy attributes for information in transmission.','AC-16a.','N/A','Determine if: - the means to associate [AC-16_ODP[01]; types of security attributes to be associated with information security attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[03]; security attribute values for types of security attributes are defined] for information in storage, in process, and/or in transmission are provided. - the means to associate [AC-16_ODP[02]; types of privacy attributes to be associated with privacy attribute values for information in storage, in process, and/or in transmission are defined] with [AC-16_ODP[04]; privacy attribute values for types of privacy attributes are defined] for information in storage, in process, and/or in transmission are provided.'),
('003702','draft','2022-03-01','DISA','policy','Ensure that the privacy attribute associations are made with the information.','AC-16b.','N/A','Determine if: - attribute associations are made. - attribute associations are retained with the information.'),
('003703','draft','2022-03-01','DISA','policy','Ensure that the privacy attribute associations are restrained with the information.','AC-16b.','N/A','Determine if: - attribute associations are made. - attribute associations are retained with the information.'),
('003704','draft','2022-03-01','DISA','policy','Establish the following permitted organization-defined privacy attributes defined in AC-16a for organization-defined systems.','AC-16c.','N/A','Determine if: - the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for [AC-16_ODP[05]; systems for which permitted security attributes are to be established are defined]: [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined]. - the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for [AC-16_ODP[06]; systems for which permitted privacy attributes are to be established are defined]: [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined].'),
('003705','draft','2022-03-01','DISA','policy','Defines the privacy attributes that are permitted for organization-defined systems.','AC-16c.','N/A','Determine if: - the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for [AC-16_ODP[05]; systems for which permitted security attributes are to be established are defined]: [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined]. - the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for [AC-16_ODP[06]; systems for which permitted privacy attributes are to be established are defined]: [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined].'),
('003706','draft','2022-03-01','DISA','policy','Defines the attribute values or ranges permitted for each of the established privacy attributes.','AC-16d.','N/A','Determine if the following permitted attribute values or ranges for each of the established attributes are determined: [AC-16_ODP[09]; attribute values or ranges for established attributes are defined].'),
('003707','draft','2022-03-01','DISA','policy','Audit changes to the attributes.','AC-16e.','N/A','Determine if changes to attributes are audited.'),
('003708','draft','2022-03-01','DISA','policy','Review organization-defined security attributes for applicability on an organization-defined frequency.','AC-16f.','N/A','Determine if: - [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[10]; the frequency at which to review security attributes for applicability is defined]. - [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[11]; the frequency at which to review privacy attributes for applicability is defined].'),
('003709','draft','2022-03-01','DISA','policy','Review organization-defined privacy attributes for applicability on an organization-defined frequency.','AC-16f.','N/A','Determine if: - [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[10]; the frequency at which to review security attributes for applicability is defined]. - [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[11]; the frequency at which to review privacy attributes for applicability is defined].'),
('003710','draft','2022-03-01','DISA','policy','Defines the security and privacy attributes to be reviewed for applicability.','AC-16f.','N/A','Determine if: - [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[10]; the frequency at which to review security attributes for applicability is defined]. - [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[11]; the frequency at which to review privacy attributes for applicability is defined].'),
('003711','draft','2022-03-01','DISA','policy','Defines the frequency of which the security and privacy attributes will be reviewed.','AC-16f.','N/A','Determine if: - [AC-16_ODP[07]; security attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[10]; the frequency at which to review security attributes for applicability is defined]. - [AC-16_ODP[08]; privacy attributes defined as part of AC-16a that are permitted for systems are defined] are reviewed for applicability [AC-16_ODP[11]; the frequency at which to review privacy attributes for applicability is defined].'),
('003712','draft','2022-03-01','DISA','technical','Dynamically associate privacy attributes with organization-defined subjects in accordance with organization-defined privacy policies as information is created and combined.','AC-16(01)','N/A','Determine if: - security attributes are dynamically associated with [AC-16(01)_ODP[01]; subjects with which security attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following security policies as information is created and combined: [AC-16(01)_ODP[05]; security policies requiring dynamic association of security attributes with subjects and objects are defined]. - security attributes are dynamically associated with [AC-16(01)_ODP[02]; objects with which security attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following security policies as information is created and combined: [AC-16(01)_ODP[05]; security policies requiring dynamic association of security attributes with subjects and objects are defined]. - privacy attributes are dynamically associated with [AC-16(01)_ODP[03]; subjects with which privacy attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following privacy policies as information is created and combined: [AC-16(01)_ODP[06]; privacy policies requiring dynamic association of privacy attributes with subjects and objects are defined.] - privacy attributes are dynamically associated with [AC-16(01)_ODP[04]; objects with which privacy attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following privacy policies as information is created and combined: [AC-16(01)_ODP[06]; privacy policies requiring dynamic association of privacy attributes with subjects and objects are defined].'),
('003713','draft','2022-03-01','DISA','technical','Dynamically associate privacy attributes with organization-defined objects in accordance with organization-defined privacy policies as information is created and combined.','AC-16(01)','N/A','Determine if: - security attributes are dynamically associated with [AC-16(01)_ODP[01]; subjects with which security attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following security policies as information is created and combined: [AC-16(01)_ODP[05]; security policies requiring dynamic association of security attributes with subjects and objects are defined]. - security attributes are dynamically associated with [AC-16(01)_ODP[02]; objects with which security attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following security policies as information is created and combined: [AC-16(01)_ODP[05]; security policies requiring dynamic association of security attributes with subjects and objects are defined]. - privacy attributes are dynamically associated with [AC-16(01)_ODP[03]; subjects with which privacy attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following privacy policies as information is created and combined: [AC-16(01)_ODP[06]; privacy policies requiring dynamic association of privacy attributes with subjects and objects are defined.] - privacy attributes are dynamically associated with [AC-16(01)_ODP[04]; objects with which privacy attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following privacy policies as information is created and combined: [AC-16(01)_ODP[06]; privacy policies requiring dynamic association of privacy attributes with subjects and objects are defined].'),
('003714','draft','2022-03-01','DISA','technical','Defines the privacy policies to adhere to when dynamically associating security attributes with organization-defined subjects and objects.','AC-16(01)','N/A','Determine if: - security attributes are dynamically associated with [AC-16(01)_ODP[01]; subjects with which security attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following security policies as information is created and combined: [AC-16(01)_ODP[05]; security policies requiring dynamic association of security attributes with subjects and objects are defined]. - security attributes are dynamically associated with [AC-16(01)_ODP[02]; objects with which security attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following security policies as information is created and combined: [AC-16(01)_ODP[05]; security policies requiring dynamic association of security attributes with subjects and objects are defined]. - privacy attributes are dynamically associated with [AC-16(01)_ODP[03]; subjects with which privacy attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following privacy policies as information is created and combined: [AC-16(01)_ODP[06]; privacy policies requiring dynamic association of privacy attributes with subjects and objects are defined.] - privacy attributes are dynamically associated with [AC-16(01)_ODP[04]; objects with which privacy attributes are to be dynamically associated as information is created and combined are defined] in accordance with the following privacy policies as information is created and combined: [AC-16(01)_ODP[06]; privacy policies requiring dynamic association of privacy attributes with subjects and objects are defined].'),
('003715','draft','2022-03-01','DISA','technical','Provides authorized individuals (or processes acting on behalf of individuals) the capability to change the value of associated privacy attributes.','AC-16(02)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated security attributes. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated privacy attributes.'),
('003716','draft','2022-03-01','DISA','technical','Provides authorized individuals (or processes acting on behalf of individuals) the capability to define the value of associated privacy attributes.','AC-16(02)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated security attributes. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated privacy attributes.'),
('003717','draft','2022-03-01','DISA','technical','Defines the privacy attributes for which the association and integrity to organization-defined subjects and objects is maintained.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('003718','draft','2022-03-01','DISA','technical','Maintain the association of organization-defined privacy attributes to organization-defined subjects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('003719','draft','2022-03-01','DISA','technical','Maintain the association of organization-defined privacy attributes to organization-defined objects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('003720','draft','2022-03-01','DISA','technical','Maintain the integrity of organization-defined privacy attributes associated with organization-defined subjects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('003721','draft','2022-03-01','DISA','technical','Maintain the integrity of organization-defined privacy attributes associated with organization-defined objects.','AC-16(03)','N/A','Determine if: - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[03]; subjects requiring the association and integrity of security attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[01]; security attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[04]; objects requiring the association and integrity of security attributes to such objects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[05]; subjects requiring the association and integrity of privacy attributes to such subjects to be maintained are defined] is maintained. - the association and integrity of [AC-16(03)_ODP[02]; privacy attributes that require association and integrity maintenance are defined] to [AC-16(03)_ODP[06]; objects requiring the association and integrity of privacy attributes to such objects to be maintained are defined] is maintained.'),
('003722','draft','2022-03-01','DISA','technical','Defines the subjects with which organization-defined privacy attributes may be associated by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('003723','draft','2022-03-01','DISA','technical','Defines the objects with which organization-defined privacy attributes may be associated by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('003724','draft','2022-03-01','DISA','technical','Defines the privacy attributes authorized individuals (or processes acting on behalf of individuals) are permitted to associate with organization-defined subjects and objects.','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('003725','draft','2022-03-01','DISA','technical','Provide the capability to associate organization-defined privacy attributes with organization-defined subjects by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('003726','draft','2022-03-01','DISA','technical','Provide the capability to associate organization-defined privacy attributes with organization-defined objects by authorized individuals (or processes acting on behalf of individuals).','AC-16(04)','N/A','Determine if: - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[01]; security attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[05]; subjects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[02]; security attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[06]; objects requiring the association of security attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[03]; privacy attributes to be associated with subjects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[07]; subjects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined]. - authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate [AC-16(04)_ODP[04]; privacy attributes to be associated with objects by authorized individuals (or processes acting on behalf of individuals) are defined] with [AC-16(04)_ODP[08]; objects requiring the association of privacy attributes by authorized individuals (or processes acting on behalf of individuals) are defined].'),
('003727','draft','2022-03-01','DISA','technical','Displays privacy attributes in human-readable form on each object that the system transmits to output devices to identify organization-identified special dissemination, handling, or distribution instructions using organization-identified human-readable, standard naming conventions.','AC-16(05)','N/A','Determine if: - security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined]. - privacy attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined].'),
('003728','draft','2022-03-01','DISA','technical','Identifies special dissemination, handling, or distribution instructions for identifying privacy attributes on output.','AC-16(05)','N/A','Determine if: - security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined]. - privacy attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined].'),
('003729','draft','2022-03-01','DISA','technical','Identifies human-readable, standard naming conventions for identifying privacy attributes on output.','AC-16(05)','N/A','Determine if: - security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined]. - privacy attributes are displayed in human-readable form on each object that the system transmits to output devices to identify [AC-16(05)_ODP[01]; special dissemination, handling, or distribution instructions to be used for each object that the system transmits to output devices are defined] using [AC-16(05)_ODP[02]; human-readable, standard naming conventions for the security and privacy attributes to be displayed in human-readable form on each object that the system transmits to output devices are defined].'),
('003730','draft','2022-03-01','DISA','policy','Defines the privacy policies to be followed by personnel when associating organization-defined privacy attributes with organization-defined subjects and objects.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003731','draft','2022-03-01','DISA','policy','Defines the privacy attributes which are to be associated with organization-defined subjects and objects.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003732','draft','2022-03-01','DISA','policy','Defines the subjects to be associated, and that association maintained, with organization-defined privacy attributes in accordance with organization-defined privacy policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003733','draft','2022-03-01','DISA','policy','Defines the objects to be associated, and that association maintained, with organization-defined privacy attributes in accordance with organization-defined privacy policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003734','draft','2022-03-01','DISA','policy','Require personnel to associate organization-defined privacy attributes with organization-defined subjects in accordance with organization-defined privacy policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003735','draft','2022-03-01','DISA','policy','Require personnel to associate organization-defined privacy attributes with organization-defined objects in accordance with organization-defined privacy policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003736','draft','2022-03-01','DISA','policy','Require personnel to maintain the association of organization-defined privacy attributes with organization-defined subjects in accordance with organization-defined privacy policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003737','draft','2022-03-01','DISA','policy','Require personnel to maintain the association of organization-defined privacy attributes with organization-defined objects in accordance with organization-defined privacy policies.','AC-16(06)','N/A','Determine if: - personnel are required to associate and maintain the association of [AC-16(06)_ODP[01]; security attributes to be associated with subjects are defined] with [AC-16(06)_ODP[05]; subjects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[02]; security attributes to be associated with objects are defined] with [AC-16(06)_ODP[06]; objects to be associated with information security attributes are defined] in accordance with [AC-16(06)_ODP[09]; security policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[03]; privacy attributes to be associated with subjects are defined] with [AC-16(06)_ODP[07]; subjects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects]. - personnel are required to associate and maintain the association of [AC-16(06)_ODP[04]; privacy attributes to be associated with objects are defined] with [AC-16(06)_ODP[08]; objects to be associated with privacy attributes are defined] in accordance with [AC-16(06)_ODP[10]; privacy policies that require personnel to associate and maintain the association of security and privacy attributes with subjects and objects].'),
('003738','draft','2022-03-01','DISA','policy','Provide a consistent interpretation of privacy attributes transmitted between distributed system components.','AC-16(07)','N/A','Determine if: - a consistent interpretation of security attributes transmitted between distributed system components is provided. - Determine if a consistent interpretation of privacy attributes transmitted between distributed system components is provided.'),
('003739','draft','2022-03-01','DISA','technical','Defines the techniques and technologies to be implemented when associating security attributes to information.','AC-16(08)','N/A','Determine if: - [AC-16(08)_ODP[01]; techniques and technologies to be implemented in associating security attributes to information are defined] are implemented in associating security attributes to information. - [AC-16(08)_ODP[02]; techniques and technologies to be implemented in associating privacy attributes to information are defined] are implemented in associating privacy attributes to information.'),
('003740','draft','2022-03-01','DISA','technical','Defines the level of assurance to be provided when implementing organization-defined techniques and technologies in associating privacy attributes to information.','AC-16(08)','N/A','Determine if: - [AC-16(08)_ODP[01]; techniques and technologies to be implemented in associating security attributes to information are defined] are implemented in associating security attributes to information. - [AC-16(08)_ODP[02]; techniques and technologies to be implemented in associating privacy attributes to information are defined] are implemented in associating privacy attributes to information.'),
('003741','draft','2022-03-01','DISA','technical','Implement organization-defined techniques and technologies with an organization-defined level of assurance in associating privacy attributes to information.','AC-16(08)','N/A','Determine if: - [AC-16(08)_ODP[01]; techniques and technologies to be implemented in associating security attributes to information are defined] are implemented in associating security attributes to information. - [AC-16(08)_ODP[02]; techniques and technologies to be implemented in associating privacy attributes to information are defined] are implemented in associating privacy attributes to information.'),
('003742','draft','2022-03-01','DISA','policy','Change privacy attributes associated with information are reassigned only via re-grading mechanisms validated using organization-defined techniques or procedures.','AC-16(09)','N/A','Determine if: - security attributes associated with information are changed only via regrading mechanisms validated using [AC-16(09)_ODP[01]; techniques or procedures used to validate regrading mechanisms for security attributes are defined]. - privacy attributes associated with information are changed only via regrading mechanisms validated using [AC-16(09)_ODP[02]; techniques or procedures used to validate regrading mechanisms for privacy attributes are defined].'),
('003743','draft','2022-03-01','DISA','policy','Provide authorized individuals the capability to define or change the type of privacy attributes available for association with subjects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('003744','draft','2022-03-01','DISA','policy','Provide authorized individuals the capability to define or change the value of privacy attributes available for association with subjects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('003745','draft','2022-03-01','DISA','policy','Provide authorized individuals the capability to define or change the type of privacy attributes available for association with objects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('003746','draft','2022-03-01','DISA','policy','Provide authorized individuals the capability to define or change the value of privacy attributes available for association with objects.','AC-16(10)','N/A','Determine if: - authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects. - authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.'),
('003747','draft','2022-03-01','DISA','technical','Implement organization-defined mechanisms to authenticate organization-defined remote commands.','AC-17(10)','N/A','Determine if [AC-17(10)_ODP[01]; mechanisms implemented to authenticate remote commands are defined] are implemented to authenticate [AC-17(10)_ODP[02]; remote commands to be authenticated by mechanisms are defined].'),
('003748','draft','2022-03-01','DISA','technical','Defines the mechanisms used to authenticate organization-defined remote commands.','AC-17(10)','N/A','Determine if [AC-17(10)_ODP[01]; mechanisms implemented to authenticate remote commands are defined] are implemented to authenticate [AC-17(10)_ODP[02]; remote commands to be authenticated by mechanisms are defined].'),
('003749','draft','2022-03-01','DISA','technical','Defines the remote commands used for implementing organization-defined mechanisms.','AC-17(10)','N/A','Determine if [AC-17(10)_ODP[01]; mechanisms implemented to authenticate remote commands are defined] are implemented to authenticate [AC-17(10)_ODP[02]; remote commands to be authenticated by mechanisms are defined].'),
('003750','draft','2022-03-01','DISA','policy','Defines the terms and conditions for accessing the system from external systems.','AC-20a.01','N/A','Determine if [AC-20_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish [AC-20_ODP[02]; terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]; identify [AC-20_ODP[03]; controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]}]]] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable).'),
('003751','draft','2022-03-01','DISA','policy','Defines the controls asserted to be implemented on external systems allowing individuals to access the system from external systems.','AC-20a.01','N/A','Determine if [AC-20_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish [AC-20_ODP[02]; terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]; identify [AC-20_ODP[03]; controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]}]]] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable).'),
('003752','draft','2022-03-01','DISA','policy','Defines the terms and conditions for processing, storing, or transmitting organization-controlled information using external systems.','AC-20a.02','N/A','Determine if [AC-20_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish [AC-20_ODP[02]; terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]; identify [AC-20_ODP[03]; controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]}]]] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using external systems (if applicable).'),
('003753','draft','2022-03-01','DISA','policy','Defines the controls asserted to be implemented on external systems allowing individuals to process, store, or transmit organization-controlled information using external systems.','AC-20a.02','N/A','Determine if [AC-20_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {establish [AC-20_ODP[02]; terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]; identify [AC-20_ODP[03]; controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined (if selected)]}]]] is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using external systems (if applicable).'),
('003754','draft','2022-03-01','DISA','policy','Prohibit the use of organizationally-defined types of external systems.','AC-20b.','N/A','Determine if the use of [AC-20_ODP[04]; types of external systems prohibited from use are defined] is prohibited (if applicable).'),
('003755','draft','2022-03-01','DISA','policy','Defines the types of external systems that are prohibited.','AC-20b.','N/A','Determine if the use of [AC-20_ODP[04]; types of external systems prohibited from use are defined] is prohibited (if applicable).'),
('003756','draft','2022-03-01','DISA','policy','Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after verification of the implementation of controls on the external system as specified in the organization''s security policy and security plan.','AC-20(01)(a)','N/A','Determine if authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after verification of the implementation of controls on the external system as specified in the organization''s security and privacy policies and security and privacy plans (if applicable).'),
('003757','draft','2022-03-01','DISA','policy','Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after verification of the implementation of controls on the external system as specified in the organization''s privacy policy and privacy plan.','AC-20(01)(a)','N/A','Determine if authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after verification of the implementation of controls on the external system as specified in the organization''s security and privacy policies and security and privacy plans (if applicable).'),
('003758','draft','2022-03-01','DISA','policy','Defines the restrictions for the use of organization-controlled portable storage devices.','AC-20(02)','N/A','Determine if the use of organization-controlled portable storage devices by authorized individuals is restricted on external systems using [AC-20(02)_ODP; restrictions on the use of organization-controlled portable storage devices by authorized individuals on external systems are defined].'),
('003759','draft','2022-03-01','DISA','policy','Prohibit the use of organization-controlled portable storage devices by authorized individuals on external systems.','AC-20(05)','N/A','Determine if the use of organization-controlled portable storage devices by authorized individuals is prohibited on external systems.'),
('003760','draft','2022-03-01','DISA','technical','Defines the privacy attributes, not to include the identity of the user or process acting on behalf of the user, to be used as the basis for enforcing access control decisions.','AC-24(02)','N/A','Determine if: - access control decisions are enforced based on [AC-24(02)_ODP[01]; security attributes that do not include the identity of the user or process acting on behalf of the user are defined (if selected)] that do not include the identity of the user or process acting on behalf of the user (if selected). - access control decisions are enforced based on [AC-24(02)_ODP[02]; privacy attributes that do not include the identity of the user or process acting on behalf of the user are defined (if selected)] that do not include the identity of the user or process acting on behalf of the user (if selected).'),
('003761','draft','2022-03-01','DISA','policy','Develop and document an organization level, mission/business process-level, or system-level awareness and training policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','AT-01a.01(b)','N/A','Determine if the [AT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] awareness and training policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('003762','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the development and documentation of the awareness and training policy.','AT-01b.','N/A','Determine if the [AT-01_ODP[04]; an official to manage the awareness and training policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the awareness and training policy and procedures.'),
('003763','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the dissemination of the awareness and training policy.','AT-01b.','N/A','Determine if the [AT-01_ODP[04]; an official to manage the awareness and training policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the awareness and training policy and procedures.'),
('003764','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the development and documentation of the awareness and training procedures.','AT-01b.','N/A','Determine if the [AT-01_ODP[04]; an official to manage the awareness and training policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the awareness and training policy and procedures.'),
('003765','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the dissemination of the awareness and training procedures.','AT-01b.','N/A','Determine if the [AT-01_ODP[04]; an official to manage the awareness and training policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the awareness and training policy and procedures.'),
('003766','draft','2022-03-01','DISA','policy','Provide basic privacy awareness training to system users (including managers, senior executives, and contractors) when required by system changes or following organization-defined events.','AT-02a.02','N/A','Determine if: - security literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following [AT-02_ODP[03]; events that require security literacy training for system users are defined]. - privacy literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following [AT-02_ODP[04]; events that require privacy literacy training for system users are defined].'),
('003767','draft','2022-03-01','DISA','policy','Employ organization-defined awareness techniques to increase the security awareness of system users.','AT-02b.','N/A','Determine if [AT-02_ODP[05]; techniques to be employed to increase the security and privacy awareness of system users are defined] are employed to increase the security and privacy awareness of system users.'),
('003768','draft','2022-03-01','DISA','policy','Employ organization-defined awareness techniques to increase the privacy awareness of system users.','AT-02b.','N/A','Determine if [AT-02_ODP[05]; techniques to be employed to increase the security and privacy awareness of system users are defined] are employed to increase the security and privacy awareness of system users.'),
('003769','draft','2022-03-01','DISA','policy','Defines the awareness techniques for to increase security and privacy awareness of system uses.','AT-02b.','N/A','Determine if [AT-02_ODP[05]; techniques to be employed to increase the security and privacy awareness of system users are defined] are employed to increase the security and privacy awareness of system users.'),
('003770','draft','2022-03-01','DISA','policy','Update literacy training and awareness content on an organization-defined frequency.','AT-02c.','N/A','Determine if: - literacy training and awareness content is updated [AT-02_ODP[06]; the frequency at which to update literacy training and awareness content is defined]. - literacy training and awareness content is updated following [AT-02_ODP[07]; events that would require literacy training and awareness content to be updated are defined].'),
('003771','draft','2022-03-01','DISA','policy','Update literacy training and awareness content following organization-defined event.','AT-02c.','N/A','Determine if: - literacy training and awareness content is updated [AT-02_ODP[06]; the frequency at which to update literacy training and awareness content is defined]. - literacy training and awareness content is updated following [AT-02_ODP[07]; events that would require literacy training and awareness content to be updated are defined].'),
('003772','draft','2022-03-01','DISA','policy','Defines the frequency for updating literacy training and awareness content.','AT-02c.','N/A','Determine if: - literacy training and awareness content is updated [AT-02_ODP[06]; the frequency at which to update literacy training and awareness content is defined]. - literacy training and awareness content is updated following [AT-02_ODP[07]; events that would require literacy training and awareness content to be updated are defined].'),
('003773','draft','2022-03-01','DISA','policy','Defines the events following updating literacy training and awareness content.','AT-02c.','N/A','Determine if: - literacy training and awareness content is updated [AT-02_ODP[06]; the frequency at which to update literacy training and awareness content is defined]. - literacy training and awareness content is updated following [AT-02_ODP[07]; events that would require literacy training and awareness content to be updated are defined].'),
('003774','draft','2022-03-01','DISA','policy','Incorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques.','AT-02d.','N/A','Determine if lessons learned from internal or external security incidents or breaches are incorporated into literacy training and awareness techniques.'),
('003775','draft','2022-03-01','DISA','policy','Provide literacy training on recognizing and reporting potential and actual instances of social engineering.','AT-02(03)','N/A','Determine if: - literacy training on recognizing potential and actual instances of social engineering is provided. - literacy training on reporting potential and actual instances of social engineering is provided. - literacy training on recognizing potential and actual instances of social mining is provided. - literacy training on reporting potential and actual instances of social mining is provided.'),
('003776','draft','2022-03-01','DISA','policy','Provide literacy training on recognizing and reporting potential and actual instances of social mining.','AT-02(03)','N/A','Determine if: - literacy training on recognizing potential and actual instances of social engineering is provided. - literacy training on reporting potential and actual instances of social engineering is provided. - literacy training on recognizing potential and actual instances of social mining is provided. - literacy training on reporting potential and actual instances of social mining is provided.'),
('003777','draft','2022-03-01','DISA','policy','Provide literacy training on recognize suspicious communications and anomalous behavior in organizational systems using organization-defined indicators of malicious code.','AT-02(04)','N/A','Determine if literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using [AT-02(04)_ODP; indicators of malicious code are defined] is provided.'),
('003778','draft','2022-03-01','DISA','policy','Defines the indicators of malicious code used to recognize suspicious communications and anomalous behavior in organizational systems.','AT-02(04)','N/A','Determine if literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using [AT-02(04)_ODP; indicators of malicious code are defined] is provided.'),
('003779','draft','2022-03-01','DISA','policy','Provide literacy training on the advanced persistent threat.','AT-02(05)','N/A','Determine if literacy training on the advanced persistent threat is provided.'),
('003780','draft','2022-03-01','DISA','policy','Provide literacy training on the cyber threat environment.','AT-02(06)(a)','N/A','Determine if literacy training on the cyber threat environment is provided.'),
('003781','draft','2022-03-01','DISA','policy','Reflect current cyber threat information in system operations.','AT-02(06)(b)','N/A','Determine if system operations reflects current cyber threat information.'),
('003782','draft','2022-03-01','DISA','policy','Defines the roles and responsibilities of the personnel providing role-based security and privacy training.',NULL,'N/A',NULL),
('003783','draft','2022-03-01','DISA','policy','Provide role-based privacy training to personnel with organization-defined roles and responsibilities before authorizing access to the system, information, or performing assigned duties.','AT-03a.01','N/A','Determine if: - role-based security training is provided to [AT-03_ODP[01]; roles and responsibilities for role-based security training are defined] before authorizing access to the system, information, or performing assigned duties. - role-based privacy training is provided to [AT-03_ODP[02]; roles and responsibilities for role-based privacy training are defined] before authorizing access to the system, information, or performing assigned duties. - role-based security training is provided to [AT-03_ODP[01]; roles and responsibilities for role-based security training are defined] [AT-03_ODP[03]; the frequency at which to provide role-based security and privacy training to assigned personnel after initial training is defined] thereafter. - role-based privacy training is provided to [AT-03_ODP[02]; roles and responsibilities for role-based privacy training are defined] [AT-03_ODP[03]; the frequency at which to provide role-based security and privacy training to assigned personnel after initial training is defined] thereafter.'),
('003784','draft','2022-03-01','DISA','policy','Provide role-based privacy training to personnel with organization-defined roles and responsibilities when required by system changes.','AT-03a.02','N/A','Determine if: - role-based security training is provided to personnel with assigned security roles and responsibilities when required by system changes. - role-based privacy training is provided to personnel with assigned security roles and responsibilities when required by system changes.'),
('003785','draft','2022-03-01','DISA','policy','Update role-based training content on an organization-defined frequency.','AT-03b.','N/A','Determine if: - role-based training content is updated [AT-03_ODP[04]; the frequency at which to update role-based training content is defined]. - role-based training content is updated following [AT-03_ODP[05]; events that require role-based training content to be updated are defined].'),
('003786','draft','2022-03-01','DISA','policy','Defines the frequency of which the role-based training content is updated.','AT-03b.','N/A','Determine if: - role-based training content is updated [AT-03_ODP[04]; the frequency at which to update role-based training content is defined]. - role-based training content is updated following [AT-03_ODP[05]; events that require role-based training content to be updated are defined].'),
('003787','draft','2022-03-01','DISA','policy','Update role-based training content following organization-defined events.','AT-03b.','N/A','Determine if: - role-based training content is updated [AT-03_ODP[04]; the frequency at which to update role-based training content is defined]. - role-based training content is updated following [AT-03_ODP[05]; events that require role-based training content to be updated are defined].'),
('003788','draft','2022-03-01','DISA','policy','Defines the events following updating role-based training content.','AT-03b.','N/A','Determine if: - role-based training content is updated [AT-03_ODP[04]; the frequency at which to update role-based training content is defined]. - role-based training content is updated following [AT-03_ODP[05]; events that require role-based training content to be updated are defined].'),
('003789','draft','2022-03-01','DISA','policy','Incorporate lessons learned from internal or external security incidents or breaches into role-based training.','AT-03c.','N/A','Determine if lessons learned from internal or external security incidents or breaches are incorporated into role-based training.'),
('003790','draft','2022-03-01','DISA','policy','Provide practical exercises in privacy training that reinforce training objectives.','AT-03(03)','N/A','Determine if: - practical exercises in security training that reinforce training objectives are provided. - practical exercises in privacy training that reinforce training objectives are provided.'),
('003791','draft','2022-03-01','DISA','policy','Defines the frequency for providing training in the employment and operation of personally identifiable information processing and transparency controls to personnel or roles.','AT-03(05)','N/A','Determine if [AT-03(05)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of personally identifiable information processing and transparency controls is/are defined] are provided with initial and refresher training [AT-03(05)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of personally identifiable information processing and transparency controls is defined] in the employment and operation of personally identifiable information processing and transparency controls.'),
('003792','draft','2022-03-01','DISA','policy','Provide organization-defined personnel or roles with initial training in the employment and operation of personally identifiable information processing and transparency controls.','AT-03(05)','N/A','Determine if [AT-03(05)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of personally identifiable information processing and transparency controls is/are defined] are provided with initial and refresher training [AT-03(05)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of personally identifiable information processing and transparency controls is defined] in the employment and operation of personally identifiable information processing and transparency controls.'),
('003793','draft','2022-03-01','DISA','policy','Defines the personnel or roles who are to be provided training in the employment and operation of personally identifiable information processing and transparency controls.','AT-03(05)','N/A','Determine if [AT-03(05)_ODP[01]; personnel or roles to be provided with initial and refresher training in the employment and operation of personally identifiable information processing and transparency controls is/are defined] are provided with initial and refresher training [AT-03(05)_ODP[02]; the frequency at which to provide refresher training in the employment and operation of personally identifiable information processing and transparency controls is defined] in the employment and operation of personally identifiable information processing and transparency controls.'),
('003794','draft','2022-03-01','DISA','policy','Document individual privacy training activities, including privacy awareness training and specific system privacy training.','AT-04a.','N/A','Determine if: - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented. - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are monitored.'),
('003795','draft','2022-03-01','DISA','policy','Monitor individual information privacy training activities, including privacy awareness training and specific privacy training.','AT-04a.','N/A','Determine if: - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented. - information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are monitored.'),
('003796','draft','2022-03-01','DISA','policy','Provide feedback on organizational training results to organization-defined personnel on an organization-defined frequency.','AT-06','N/A','Determine if feedback on organizational training results is provided [AT-06_ODP[01]; frequency at which to provide feedback on organizational training results is defined] to [AT-06_ODP[02]; personnel to whom feedback on organizational training results will be provided is/are assigned].'),
('003797','draft','2022-03-01','DISA','policy','Defines the frequency of which feedback is provided on organizational training results.','AT-06','N/A','Determine if feedback on organizational training results is provided [AT-06_ODP[01]; frequency at which to provide feedback on organizational training results is defined] to [AT-06_ODP[02]; personnel to whom feedback on organizational training results will be provided is/are assigned].'),
('003798','draft','2022-03-01','DISA','policy','Defines the organizational personnel or roles who provide feedback on organizational training results.','AT-06','N/A','Determine if feedback on organizational training results is provided [AT-06_ODP[01]; frequency at which to provide feedback on organizational training results is defined] to [AT-06_ODP[02]; personnel to whom feedback on organizational training results will be provided is/are assigned].'),
('003799','draft','2022-03-01','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level audit and accountability policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','AU-01a.01(b)','N/A','Determine if the [AU-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] of the audit and accountability policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.'),
('003800','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the development and documentation of the audit and accountability policy.','AU-01b.','N/A','Determine if the [AU-01_ODP[04]; an official to manage the audit and accountability policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures.'),
('003801','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the dissemination of the audit and accountability policy.','AU-01b.','N/A','Determine if the [AU-01_ODP[04]; an official to manage the audit and accountability policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures.'),
('003802','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the development and documentation of the audit and accountability procedures.','AU-01b.','N/A','Determine if the [AU-01_ODP[04]; an official to manage the audit and accountability policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures.'),
('003803','draft','2022-03-01','DISA','policy','Designate an organization-defined official to manage the dissemination of the audit and accountability procedures.','AU-01b.','N/A','Determine if the [AU-01_ODP[04]; an official to manage the audit and accountability policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures.'),
('003804','draft','2022-03-01','DISA','policy','Defines the official designated for managing the development, documentation, and dissemination of the audit and accountability policy.','AU-01b.','N/A','Determine if the [AU-01_ODP[04]; an official to manage the audit and accountability policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures.'),
('003805','draft','2022-03-01','DISA','policy','Defines the official designated for managing the development, documentation, and dissemination of the audit and accountability procedures.','AU-01b.','N/A','Determine if the [AU-01_ODP[04]; an official to manage the audit and accountability policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the audit and accountability policy and procedures.'),
('003806','draft','2022-03-02','DISA','policy','Review and update the current audit and accountability policy following organization-defined events.','AU-01c.01','N/A','Determine if: - the current audit and accountability policy is reviewed and updated [AU-01_ODP[05]; the frequency at which the current audit and accountability policy is reviewed and updated is defined]. - the current audit and accountability policy is reviewed and updated following [AU-01_ODP[06]; events that would require the current audit and accountability policy to be reviewed and updated are defined.]'),
('003807','draft','2022-03-02','DISA','policy','Defines the events following reviewing and updating the current audit and accountability policy.','AU-01c.01','N/A','Determine if: - the current audit and accountability policy is reviewed and updated [AU-01_ODP[05]; the frequency at which the current audit and accountability policy is reviewed and updated is defined]. - the current audit and accountability policy is reviewed and updated following [AU-01_ODP[06]; events that would require the current audit and accountability policy to be reviewed and updated are defined.]'),
('003808','draft','2022-03-02','DISA','policy','Review and update the current audit and accountability procedures following organization-defined events.','AU-01c.02','N/A','Determine if: - the current audit and accountability procedures are reviewed and updated [AU-01_ODP[07]; the frequency at which the current audit and accountability procedures are reviewed and updated is defined]. - the current audit and accountability procedures are reviewed and updated following [AU-01_ODP[08]; events that would require audit and accountability procedures to be reviewed and updated are defined].'),
('003809','draft','2022-03-02','DISA','policy','Defines the events following reviewing and updating the current audit and accountability procedures.','AU-01c.02','N/A','Determine if: - the current audit and accountability procedures are reviewed and updated [AU-01_ODP[07]; the frequency at which the current audit and accountability procedures are reviewed and updated is defined]. - the current audit and accountability procedures are reviewed and updated following [AU-01_ODP[08]; events that would require audit and accountability procedures to be reviewed and updated are defined].'),
('003810','draft','2022-03-02','DISA','policy','Review and update the event types selected for logging on an organization-defined frequency.','AU-02e.','N/A','Determine if the event types selected for logging are reviewed and updated [AU-02_ODP[04]; the frequency of event types selected for logging are reviewed and updated].'),
('003811','draft','2022-03-02','DISA','policy','Defines the frequency at which the event types selected for logging will be reviewed and updated.','AU-02e.','N/A','Determine if the event types selected for logging are reviewed and updated [AU-02_ODP[04]; the frequency of event types selected for logging are reviewed and updated].'),
('003812','draft','2022-03-02','DISA','policy','Limit personally identifiable information contained in audit records to organization-defined elements identified in the privacy risk assessment.','AU-03(03)','N/A','Determine if personally identifiable information contained in audit records is limited to [AU-03(03)_ODP; elements identified in the privacy risk assessment are defined] identified in the privacy risk assessment.'),
('003813','draft','2022-03-02','DISA','policy','Defines the elements identified in the privacy risk assessment for limiting personally identifiable information contained in audit records.','AU-03(03)','N/A','Determine if personally identifiable information contained in audit records is limited to [AU-03(03)_ODP; elements identified in the privacy risk assessment are defined] identified in the privacy risk assessment.'),
('003814','draft','2022-03-02','DISA','policy','Defines the time-period for the alert in the event of an audit process failure.','AU-05a.','N/A','Determine if [AU-05_ODP[01]; personnel or roles receiving audit logging process failure alerts are defined] are alerted in the event of an audit logging process failure within [AU-05_ODP[02]; time period for personnel or roles receiving audit logging process failure alerts is defined].'),
('003815','draft','2022-03-02','DISA','policy','Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements organization-defined alternate audit logging functionality.','AU-05(05)','N/A','Determine if an alternate audit logging capability is provided in the event of a failure in primary audit logging capability that implements [AU-05(05)_ODP; an alternate audit logging functionality in the event of a failure in primary audit logging capability is defined].'),
('003816','draft','2022-03-02','DISA','policy','Defines the alternate audit logging functionality in the event of a failure in primary audit logging capability.','AU-05(05)','N/A','Determine if an alternate audit logging capability is provided in the event of a failure in primary audit logging capability that implements [AU-05(05)_ODP; an alternate audit logging functionality in the event of a failure in primary audit logging capability is defined].'),
('003817','draft','2022-03-02','DISA','policy','Review and analyze the potential impact of the organization-defined inappropriate or unusual activity.','AU-06a.','N/A','Determine if system audit records are reviewed and analyzed [AU-06_ODP[01]; frequency at which system audit records are reviewed and analyzed is defined] for indications of [AU-06_ODP[02]; inappropriate or unusual activity is defined] and the potential impact of the inappropriate or unusual activity.'),
('003818','draft','2022-03-02','DISA','policy','Adjust the level of audit review and analysis within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.','AU-06c.','N/A','Determine if the level of audit record review, analysis, and reporting within the system is adjusted when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.'),
('003819','draft','2022-03-02','DISA','policy','Adjust the level of audit reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.','AU-06c.','N/A','Determine if the level of audit record review, analysis, and reporting within the system is adjusted when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.'),
('003820','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for integrating audit record review, analysis, and reporting processes.','AU-06(01)','N/A','Determine if audit record review, analysis, and reporting processes are integrated using [AU-06(01)_ODP; automated mechanisms used for integrating audit record review, analysis, and reporting processes are defined].'),
('003821','draft','2022-03-02','DISA','technical','Implement the capability to centrally review and analyze audit records from multiple components within the system.','AU-06(04)','N/A','Determine if: - the capability to centrally review and analyze audit records from multiple components within the system is provided. - the capability to centrally review and analyze audit records from multiple components within the system is implemented.'),
('003822','draft','2022-03-02','DISA','technical','Implement an audit reduction capability that supports on-demand audit review and analysis.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('003823','draft','2022-03-02','DISA','technical','Implement an audit reduction capability that supports on-demand reporting requirements.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('003824','draft','2022-03-02','DISA','technical','Implement an audit reduction capability that supports after-the-fact investigations of incidents.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('003825','draft','2022-03-02','DISA','technical','Implement a report generation capability that supports on-demand audit review and analysis.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('003826','draft','2022-03-02','DISA','technical','Implement a report generation capability that supports on-demand reporting requirements.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('003827','draft','2022-03-02','DISA','technical','Implement a report generation capability that supports after-the-fact investigations of incidents.','AU-07a.','N/A','Determine if: - an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents. - if an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents.'),
('003828','draft','2022-03-02','DISA','technical','Implement an audit reduction capability that does not alter original content or time ordering of audit records.','AU-07b.','N/A','Determine if: - an audit record reduction and report generation capability is provided that does not alter the original content or time ordering of audit records. - an audit record reduction and report generation capability is implemented that does not alter the original content or time ordering of audit records.'),
('003829','draft','2022-03-02','DISA','technical','Implement a report generation capability that does not alter original content or time ordering of audit records.','AU-07b.','N/A','Determine if: - an audit record reduction and report generation capability is provided that does not alter the original content or time ordering of audit records. - an audit record reduction and report generation capability is implemented that does not alter the original content or time ordering of audit records.'),
('003830','draft','2022-03-02','DISA','technical','Implement the capability to process, sort, and search audit records for events of interest based on organization-defined audit fields within audit records.','AU-07(01)','N/A','Determine if: - the capability to process, sort, and search audit records for events of interest based on [AU-07(01)_ODP; fields within audit records that can be processed, sorted, or searched are defined] are provided. - the capability to process, sort, and search audit records for events of interest based on [AU-07(01)_ODP; fields within audit records that can be processed, sorted, or searched are defined] are implemented.'),
('003831','draft','2022-03-02','DISA','technical','Alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.','AU-09b.','N/A','Determine if [AU-09_ODP; personnel or roles to be alerted upon detection of unauthorized access, modification, or deletion of audit information is/are defined] are alerted upon detection of unauthorized access, modification, or deletion of audit information.'),
('003832','draft','2022-03-02','DISA','technical','Defines the personnel or roles to be alerted upon detection of unauthorized access, modification, or deletion of audit information.','AU-09b.','N/A','Determine if [AU-09_ODP; personnel or roles to be alerted upon detection of unauthorized access, modification, or deletion of audit information is/are defined] are alerted upon detection of unauthorized access, modification, or deletion of audit information.'),
('003833','draft','2022-03-02','DISA','policy','Store audit information on a component running a different operating system than the system component being audited.','AU-09(07)','N/A','Determine if audit information is stored on a component running a different operating system than the system or component being audited.'),
('003834','draft','2022-03-02','DISA','technical','Implement the capability for organization-defined individuals or roles to change the auditing to be performed on organization-defined system components based on organization-defined selectable event criteria within organization-defined time thresholds.','AU-12(03)','N/A','Determine if: - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is provided. - the capability for [AU-12(03)_ODP[01]; individuals or roles authorized to change the logging on system components are defined] to change the logging to be performed on [AU-12(03)_ODP[02]; system components on which logging is to be performed are defined] based on [AU-12(03)_ODP[03]; selectable event criteria with which change logging is to be performed are defined] within [AU-12(03)_ODP[04]; time thresholds in which logging actions are to change is defined] is implemented.'),
('003835','draft','2022-03-02','DISA','technical','Provide the capability for auditing the parameters of user query events for data sets containing personally identifiable information.','AU-12(04)','N/A','Determine if: - the capability to audit the parameters of user query events for data sets containing personally identifiable information is provided. - the capability to audit the parameters of user query events for data sets containing personally identifiable information is implemented.'),
('003836','draft','2022-03-02','DISA','technical','Implement the capability for auditing the parameters of user query events for data sets containing personally identifiable information.','AU-12(04)','N/A','Determine if: - the capability to audit the parameters of user query events for data sets containing personally identifiable information is provided. - the capability to audit the parameters of user query events for data sets containing personally identifiable information is implemented.'),
('003837','draft','2022-03-02','DISA','policy','If an information disclosure is discovered, notify organization-defined personnel or roles.','AU-13b.01','N/A','Determine if [AU-13_ODP[03]; personnel or roles to be notified if an information disclosure is discovered is/are defined] are notified if an information disclosure is discovered.'),
('003838','draft','2022-03-02','DISA','policy','Defines the personnel or roles to be notified if an information disclosure is discovered.','AU-13b.01','N/A','Determine if [AU-13_ODP[03]; personnel or roles to be notified if an information disclosure is discovered is/are defined] are notified if an information disclosure is discovered.'),
('003839','draft','2022-03-02','DISA','policy','If an information disclosure is discovered, take organization-defined additional actions.','AU-13b.02','N/A','Determine if [AU-13_ODP[04]; additional actions to be taken if an information disclosure is discovered are defined] are taken if an information disclosure is discovered.'),
('003840','draft','2022-03-02','DISA','policy','Defines the additional actions to be taken if an information disclosure is discovered.','AU-13b.02','N/A','Determine if [AU-13_ODP[04]; additional actions to be taken if an information disclosure is discovered are defined] are taken if an information disclosure is discovered.'),
('003841','draft','2022-03-02','DISA','policy','Monitor open-source information and information sites using organization-defined automated mechanisms.','AU-13(01)','N/A','Determine if open-source information and information sites are monitored using [AU-13(01)_ODP; automated mechanisms for monitoring open-source information and information sites are defined].'),
('003842','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for monitoring open-source information.','AU-13(01)','N/A','Determine if open-source information and information sites are monitored using [AU-13(01)_ODP; automated mechanisms for monitoring open-source information and information sites are defined].'),
('003843','draft','2022-03-02','DISA','policy','Employ discovery techniques, processes, and tools to determine if external entities are replicating organizational information in an unauthorized manner.','AU-13(03)','N/A','Determine if discovery techniques, processes, and tools are employed to determine if external entities are replicating organizational information in an unauthorized manner.'),
('003844','draft','2022-03-02','DISA','technical','Implement the capability for organization-defined users or roles to select a user session to record; view; hear; and/or log the content of a user session under organization-defined circumstances.','AU-14a.','N/A','Determine if: - [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] are provided with the capability to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined]. - the capability for [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined] is implemented.'),
('003845','draft','2022-03-02','DISA','technical','Defines users or roles who will provide and implement the capability to record; view; hear; and/or log the content of a user session under organization-defined circumstances.','AU-14a.','N/A','Determine if: - [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] are provided with the capability to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined]. - the capability for [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined] is implemented.'),
('003846','draft','2022-03-02','DISA','technical','Defines the circumstances to record; view; hear; and/or log the content of a user session.','AU-14a.','N/A','Determine if: - [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] are provided with the capability to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined]. - the capability for [AU-14_ODP[01]; users or roles who can audit the content of a user session are defined] to [AU-14_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {record; view; hear; log}] the content of a user session under [AU-14_ODP[03]; circumstances under which the content of a user session can be audited are defined] is implemented.'),
('003847','draft','2022-03-02','DISA','technical','Develop, integrate, and use session auditing activities in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.','AU-14b.','N/A','Determine if: - session auditing activities are developed in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. - session auditing activities are integrated in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. - session auditing activities are used in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.'),
('003848','draft','2022-03-02','DISA','technical','Implement the capability for authorized users to remotely view and hear content related to an established user session in real time.','AU-14(03)','N/A','Determine if: - the capability for authorized users to remotely view and hear content related to an established user session in real time is provided. - the capability for authorized users to remotely view and hear content related to an established user session in real time is implemented.'),
('003849','draft','2022-03-02','DISA','policy','Disseminate an organization-level; mission/business process; system-level assessment, authorization, and monitoring policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','CA-01a.01(b)','N/A','Determine if the [CA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] assessment, authorization, and monitoring policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.'),
('003850','draft','2022-03-02','DISA','policy','Defines the personnel or roles to whom the assessment, authorization, and monitoring policy is to be disseminated.','CA-01a.02','N/A','Determine if: - assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented. - the assessment, authorization, and monitoring procedures are disseminated to [CA-01_ODP[02]; personnel or roles to whom the assessment, authorization, and monitoring procedures are to be disseminated is/are defined].'),
('003851','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the development and documentation of the assessment, authorization, and monitoring policy.','CA-01b.','N/A','Determine if the [CA-01_ODP[04]; an official to manage the assessment, authorization, and monitoring policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures.'),
('003852','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the development and documentation of the assessment, authorization, and monitoring procedures.','CA-01b.','N/A','Determine if the [CA-01_ODP[04]; an official to manage the assessment, authorization, and monitoring policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures.'),
('003853','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the dissemination of the assessment, authorization, and monitoring policy.','CA-01b.','N/A','Determine if the [CA-01_ODP[04]; an official to manage the assessment, authorization, and monitoring policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures.'),
('003854','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the dissemination of the assessment, authorization, and monitoring procedures.','CA-01b.','N/A','Determine if the [CA-01_ODP[04]; an official to manage the assessment, authorization, and monitoring policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures.'),
('003855','draft','2022-03-02','DISA','policy','Review and update the current assessment, authorization, and monitoring policy following organization-defined events.','CA-01c.01','N/A','Determine if: - the current assessment, authorization, and monitoring policy is reviewed and updated [CA-01_ODP[05]; the frequency at which the current assessment, authorization, and monitoring policy is reviewed and updated is defined]. - the current assessment, authorization, and monitoring policy is reviewed and updated following [CA-01_ODP[06]; events that would require the current assessment, authorization, and monitoring policy to be reviewed and updated are defined].'),
('003856','draft','2022-03-02','DISA','policy','Defines the events following reviewing and updating the current assessment, authorization, and monitoring policy.','CA-01c.01','N/A','Determine if: - the current assessment, authorization, and monitoring policy is reviewed and updated [CA-01_ODP[05]; the frequency at which the current assessment, authorization, and monitoring policy is reviewed and updated is defined]. - the current assessment, authorization, and monitoring policy is reviewed and updated following [CA-01_ODP[06]; events that would require the current assessment, authorization, and monitoring policy to be reviewed and updated are defined].'),
('003857','draft','2022-03-02','DISA','policy','Review and update the current assessment and authorization procedures following organization-defined events.','CA-01c.02','N/A','Determine if: - the current assessment, authorization, and monitoring procedures are reviewed and updated [CA-01_ODP[07]; the frequency at which the current assessment, authorization, and monitoring procedures are reviewed and updated is defined]. - the current assessment, authorization, and monitoring procedures are reviewed and updated following [CA-01_ODP[08]; events that would require assessment, authorization, and monitoring procedures to be reviewed and updated are defined].'),
('003858','draft','2022-03-02','DISA','policy','Defines the events following reviewing and updating the current assessment, authorization, and monitoring procedures.','CA-01c.02','N/A','Determine if: - the current assessment, authorization, and monitoring procedures are reviewed and updated [CA-01_ODP[07]; the frequency at which the current assessment, authorization, and monitoring procedures are reviewed and updated is defined]. - the current assessment, authorization, and monitoring procedures are reviewed and updated following [CA-01_ODP[08]; events that would require assessment, authorization, and monitoring procedures to be reviewed and updated are defined].'),
('003859','draft','2022-03-02','DISA','policy','Select the appropriate assessor or assessment team for the type of assessment to be conducted.','CA-02a.','N/A','Determine if an appropriate assessor or assessment team is selected for the type of assessment to be conducted.'),
('003860','draft','2022-03-02','DISA','policy','Ensure the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment.','CA-02c.','N/A','Determine if the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment.'),
('003861','draft','2022-03-02','DISA','policy','Assess the controls in the systems and its environment of operation on an organization-defined frequency, to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the privacy requirements.','CA-02d.','N/A','Determine if: - controls are assessed in the system and its environment of operation [CA-02_ODP[01]; the frequency at which to assess controls in the system and its environment of operation is defined] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security requirements. - controls are assessed in the system and its environment of operation [CA-02_ODP[01]; the frequency at which to assess controls in the system and its environment of operation is defined] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established privacy requirements.'),
('003862','draft','2022-03-02','DISA','policy','Approve and manage the exchange of information between the system and other systems using interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service level agreements; user agreement; and/or nondisclosure agreements with an organization-defined type of agreement.','CA-03a.','N/A','Determine if the exchange of information between the system and other systems is approved and managed using [CA-03_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service level agreements; user agreements; non-disclosure agreements; [CA-03_ODP[02]; the type of agreement used to approve and manage the exchange of information is defined (if selected)]}].'),
('003863','draft','2022-03-02','DISA','policy','Document, as part of each exchange agreement, the privacy requirements, controls and responsibilities for each system, and the impact level of the information communicated.','CA-03b.','N/A','Determine if: - the interface characteristics are documented as part of each exchange agreement. - security requirements are documented as part of each exchange agreement. - privacy requirements are documented as part of each exchange agreement. - controls are documented as part of each exchange agreement. - responsibilities for each system are documented as part of each exchange agreement. - the impact level of the information communicated is documented as part of each exchange agreement.'),
('003864','draft','2022-03-02','DISA','policy','Verify that individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.','CA-03(06)','N/A','Determine if individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.'),
('003865','draft','2022-03-02','DISA','policy','Identify transitive (downstream) information exchanges with other systems through the systems identified in CA-3a.','CA-03(07)(a)','N/A','Determine if transitive (downstream) information exchanges with other systems through the systems identified in CA-03a are identified.'),
('003866','draft','2022-03-02','DISA','policy','Take measures to ensure that transitive (downstream) information exchanges cease when the controls on identified transitive (downstream) systems cannot be verified or validated.','CA-03(07)(b)','N/A','Determine if measures are taken to ensure that transitive (downstream) information exchanges cease when the controls on identified transitive (downstream) systems cannot be verified or validated.'),
('003867','draft','2022-03-02','DISA','policy','Defines the automated mechanisms to ensure the accuracy, currency, and availability of the plan of actions and milestones.','CA-05(01)','N/A','Determine if [CA-05(01)_ODP; automated mechanisms used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system are defined] are used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system.'),
('003868','draft','2022-03-02','DISA','policy','Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems.','CA-06b.','N/A','Determine if a senior official is assigned as the authorizing official for common controls available for inheritance by organizational systems.'),
('003869','draft','2022-03-02','DISA','policy','Ensure the authorizing official accepts the use of common controls inherited by the system, before commencing operations.','CA-06c.01','N/A','Determine if before commencing operations, the authorizing official for the system accepts the use of common controls inherited by the system.'),
('003870','draft','2022-03-02','DISA','policy','Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems.','CA-06d.','N/A','Determine if the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems.'),
('003871','draft','2022-03-02','DISA','policy','Employ a joint authorization process for the system that includes multiple authorizing officials from the same organization conducting the authorization.','CA-06(01)','N/A','Determine if: - a joint authorization process is employed for the system. - the joint authorization process employed for the system includes multiple authorizing officials from the same organization conducting the authorization.'),
('003872','draft','2022-03-02','DISA','policy','Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization.','CA-06(02)','N/A','Determine if: - a joint authorization process is employed for the system. - the joint authorization process employed for the system includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization.'),
('003873','draft','2022-03-02','DISA','policy','Implement continuous monitoring in accordance with the organization-level continuous monitoring strategy.','CA-07','N/A','Determine if: - a system-level continuous monitoring strategy is developed. - system-level continuous monitoring is implemented in accordance with the organization-level continuous monitoring strategy.'),
('003874','draft','2022-03-02','DISA','policy','Defines the system-level metrics to be monitored.','CA-07a.','N/A','Determine if system-level continuous monitoring includes establishment of the following system-level metrics to be monitored: [CA-07_ODP[01]; system-level metrics to be monitored are defined].'),
('003875','draft','2022-03-02','DISA','policy','Establish organization-defined frequencies for assessment of control effectiveness.','CA-07b.','N/A','Determine if: - system-level continuous monitoring includes established [CA-07_ODP[02]; frequencies at which to monitor control effectiveness are defined] for monitoring. - system-level continuous monitoring includes established [CA-07_ODP[03]; frequencies at which to assess control effectiveness are defined] for assessment of control effectiveness.'),
('003876','draft','2022-03-02','DISA','policy','Defines the frequencies for monitoring of control effectiveness.','CA-07b.','N/A','Determine if: - system-level continuous monitoring includes established [CA-07_ODP[02]; frequencies at which to monitor control effectiveness are defined] for monitoring. - system-level continuous monitoring includes established [CA-07_ODP[03]; frequencies at which to assess control effectiveness are defined] for assessment of control effectiveness.'),
('003877','draft','2022-03-02','DISA','policy','Defines the frequencies for assessment of control effectiveness.','CA-07b.','N/A','Determine if: - system-level continuous monitoring includes established [CA-07_ODP[02]; frequencies at which to monitor control effectiveness are defined] for monitoring. - system-level continuous monitoring includes established [CA-07_ODP[03]; frequencies at which to assess control effectiveness are defined] for assessment of control effectiveness.'),
('003878','draft','2022-03-02','DISA','policy','Develop ongoing control assessments in accordance with the continuous monitoring strategy.','CA-07c.','N/A','Determine if system-level continuous monitoring includes ongoing control assessments in accordance with the continuous monitoring strategy.'),
('003879','draft','2022-03-02','DISA','policy','Implement a continuous monitoring program that includes reporting the privacy status to organization-defined personnel or roles on an organization-defined frequency.','CA-07g.','N/A','Determine if: - system-level continuous monitoring includes reporting the security status of the system to [CA-07_ODP[04]; personnel or roles to whom the security status of the system is reported are defined] [CA-07_ODP[05]; frequency at which the security status of the system is reported is defined]. - system-level continuous monitoring includes reporting the privacy status of the system to [CA-07_ODP[06]; personnel or roles to whom the privacy status of the system is reported are defined] [CA-07_ODP[07]; frequency at which the privacy status of the system is reported is defined].'),
('003880','draft','2022-03-02','DISA','policy','Defines the frequency with which to report the privacy status to organization-defined personnel or roles.','CA-07g.','N/A','Determine if: - system-level continuous monitoring includes reporting the security status of the system to [CA-07_ODP[04]; personnel or roles to whom the security status of the system is reported are defined] [CA-07_ODP[05]; frequency at which the security status of the system is reported is defined]. - system-level continuous monitoring includes reporting the privacy status of the system to [CA-07_ODP[06]; personnel or roles to whom the privacy status of the system is reported are defined] [CA-07_ODP[07]; frequency at which the privacy status of the system is reported is defined].'),
('003881','draft','2022-03-02','DISA','policy','Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes effectiveness monitoring.','CA-07(04)(a)','N/A','Determine if effectiveness monitoring is included in risk monitoring,'),
('003882','draft','2022-03-02','DISA','policy','Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes compliance monitoring.','CA-07(04)(b)','N/A','Determine if compliance monitoring is included in risk monitoring,'),
('003883','draft','2022-03-02','DISA','policy','Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes change monitoring.','CA-07(04)(c)','N/A','Determine if change monitoring is included in risk monitoring.'),
('003884','draft','2022-03-02','DISA','policy','Employ organization-defined actions to validate that policies are established.','CA-07(05)','N/A','Determine if: - [CA-07(05)_ODP[01; actions to validate that policies are established are defined] are employed to validate that policies are established. - [CA-07(05)_ODP[02]; actions to validate that implemented controls are operating in a consistent manner are defined] are employed to validate that implemented controls are operating in a consistent manner.'),
('003885','draft','2022-03-02','DISA','policy','Employ organization-defined actions to validate that implemented controls are operating in a consistent manner.','CA-07(05)','N/A','Determine if: - [CA-07(05)_ODP[01; actions to validate that policies are established are defined] are employed to validate that policies are established. - [CA-07(05)_ODP[02]; actions to validate that implemented controls are operating in a consistent manner are defined] are employed to validate that implemented controls are operating in a consistent manner.'),
('003886','draft','2022-03-02','DISA','policy','Defines the actions used to validate policies.','CA-07(05)','N/A','Determine if: - [CA-07(05)_ODP[01; actions to validate that policies are established are defined] are employed to validate that policies are established. - [CA-07(05)_ODP[02]; actions to validate that implemented controls are operating in a consistent manner are defined] are employed to validate that implemented controls are operating in a consistent manner.'),
('003887','draft','2022-03-02','DISA','policy','Ensure the accuracy, currency, and availability of monitoring results for the system using organization-defined automated mechanisms.','CA-07(06)','N/A','Determine if [CA-07(06)_ODP; automated mechanisms used to ensure the accuracy, currency, and availability of monitoring results for the system are defined] are used to ensure the accuracy, currency, and availability of monitoring results for the system.'),
('003888','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for ensuring accuracy, currency, and availability of monitoring results.','CA-07(06)','N/A','Determine if [CA-07(06)_ODP; automated mechanisms used to ensure the accuracy, currency, and availability of monitoring results for the system are defined] are used to ensure the accuracy, currency, and availability of monitoring results for the system.'),
('003889','draft','2022-03-02','DISA','policy','Employ a penetration testing process, on an organization-defined frequency, that includes announced or unannounced attempts to bypass or circumvent controls associated with physical access points to the facility.','CA-08(03)','N/A','Determine if the penetration testing process includes [CA-08(03)_ODP[01]; frequency at which to employ penetration testing that attempts to bypass or circumvent controls associated with physical access points to the facility is defined] [CA-08(03)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {announced; unannounced}] attempts to bypass or circumvent controls associated with physical access points to facility.'),
('003890','draft','2022-03-02','DISA','policy','Defines the frequency the penetration testing process will be employed.','CA-08(03)','N/A','Determine if the penetration testing process includes [CA-08(03)_ODP[01]; frequency at which to employ penetration testing that attempts to bypass or circumvent controls associated with physical access points to the facility is defined] [CA-08(03)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {announced; unannounced}] attempts to bypass or circumvent controls associated with physical access points to facility.'),
('003891','draft','2022-03-02','DISA','policy','Document, for each internal connection, the privacy requirements.','CA-09b.','N/A','Determine if: - for each internal connection, the interface characteristics are documented. - for each internal connection, the security requirements are documented. - for each internal connection, the privacy requirements are documented. - for each internal connection, the nature of the information communicated is documented.'),
('003892','draft','2022-03-02','DISA','policy','Terminate internal system connections after organization-defined conditions.','CA-09c.','N/A','Determine if internal system connections are terminated after [CA-09_ODP[02]; conditions requiring termination of internal connections are defined].'),
('003893','draft','2022-03-02','DISA','policy','Defines the conditions for terminating internal system connections.','CA-09c.','N/A','Determine if internal system connections are terminated after [CA-09_ODP[02]; conditions requiring termination of internal connections are defined].'),
('003894','draft','2022-03-02','DISA','policy','Review on an organization-defined frequency the continued need for each internal connection.','CA-09d.','N/A','Determine if the continued need for each internal connection is reviewed [CA-09_ODP[03]; frequency at which to review the continued need for each internal connection is defined].'),
('003895','draft','2022-03-02','DISA','policy','Defines the frequency for reviewing each internal connection.','CA-09d.','N/A','Determine if the continued need for each internal connection is reviewed [CA-09_ODP[03]; frequency at which to review the continued need for each internal connection is defined].'),
('003896','draft','2022-03-02','DISA','policy','Perform privacy compliance checks on constituent components prior to the establishment of the internal connection.','CA-09(01)','N/A','Determine if: - security compliance checks are performed on constituent system components prior to the establishment of the internal connection. - privacy compliance checks are performed on constituent system components prior to the establishment of the internal connection.'),
('003897','draft','2022-03-02','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level configuration management policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','CM-01a.01(b)','N/A','Determine if the configuration management policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('003898','draft','2022-03-02','DISA','policy','Defines the official to manage the development, documentation, and dissemination of the configuration management policy.','CM-01b.','N/A','Determine if the [CM-01_ODP[04]; an official to manage the configuration management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures.'),
('003899','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the development and documentation of the configuration management policy.','CM-01b.','N/A','Determine if the [CM-01_ODP[04]; an official to manage the configuration management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures.'),
('003900','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the dissemination of the configuration management policy.','CM-01b.','N/A','Determine if the [CM-01_ODP[04]; an official to manage the configuration management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures.'),
('003901','draft','2022-03-02','DISA','policy','Defines the official to manage the development, documentation, and dissemination of the configuration management procedures.','CM-01b.','N/A','Determine if the [CM-01_ODP[04]; an official to manage the configuration management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures.'),
('003902','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the development and documentation of the configuration management procedures.','CM-01b.','N/A','Determine if the [CM-01_ODP[04]; an official to manage the configuration management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures.'),
('003903','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the dissemination of the configuration management procedures.','CM-01b.','N/A','Determine if the [CM-01_ODP[04]; an official to manage the configuration management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures.'),
('003904','draft','2022-03-02','DISA','policy','Review and update the configuration management policy following organization-defined events.','CM-01c.01','N/A','Determine if: - the current configuration management policy is reviewed and updated [CM-01_ODP[05]; the frequency at which the current configuration management policy is reviewed and updated is defined]. - the current configuration management policy is reviewed and updated following [CM-01_ODP[06]; events that would require the current configuration management policy to be reviewed and updated are defined].'),
('003905','draft','2022-03-02','DISA','policy','Defines the events for when the policy will be reviewed and updated.','CM-01c.01','N/A','Determine if: - the current configuration management policy is reviewed and updated [CM-01_ODP[05]; the frequency at which the current configuration management policy is reviewed and updated is defined]. - the current configuration management policy is reviewed and updated following [CM-01_ODP[06]; events that would require the current configuration management policy to be reviewed and updated are defined].'),
('003906','draft','2022-03-02','DISA','policy','Review and update, on an organization-defined frequency, the current configuration management procedures.','CM-01c.02','N/A','Determine if: - the current configuration management procedures are reviewed and updated [CM-01_ODP[07]; the frequency at which the current configuration management procedures are reviewed and updated is defined]. - the current configuration management procedures are reviewed and updated following [CM-01_ODP[08]; events that would require configuration management procedures to be reviewed and updated are defined].'),
('003907','draft','2022-03-02','DISA','policy','Review and update the configuration management procedures following organization-defined events.','CM-01c.02','N/A','Determine if: - the current configuration management procedures are reviewed and updated [CM-01_ODP[07]; the frequency at which the current configuration management procedures are reviewed and updated is defined]. - the current configuration management procedures are reviewed and updated following [CM-01_ODP[08]; events that would require configuration management procedures to be reviewed and updated are defined].'),
('003908','draft','2022-03-02','DISA','policy','Defines the events for when the procedures will be reviewed and updated.','CM-01c.02','N/A','Determine if: - the current configuration management procedures are reviewed and updated [CM-01_ODP[07]; the frequency at which the current configuration management procedures are reviewed and updated is defined]. - the current configuration management procedures are reviewed and updated following [CM-01_ODP[08]; events that would require configuration management procedures to be reviewed and updated are defined].'),
('003909','draft','2022-03-02','DISA','policy','Develop and document, under configuration control, a current baseline configuration of the system.','CM-02a.','N/A','Determine if: - a current baseline configuration of the system is developed and documented. - a current baseline configuration of the system is maintained under configuration control.'),
('003910','draft','2022-03-02','DISA','policy','Review and update the baseline configuration of the system when system components are installed or upgraded.','CM-02b.03','N/A','Determine if the baseline configuration of the system is reviewed and updated when system components are installed or upgraded.'),
('003911','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for maintaining the currency, completeness, accuracy, and availability of the baseline configuration of the system.','CM-02(02)','N/A','Determine if: - the currency of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the completeness of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the accuracy of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined]. - the availability of the baseline configuration of the system is maintained using [CM-02(02)_ODP; automated mechanisms for maintaining baseline configuration of the system are defined].'),
('003912','draft','2022-03-02','DISA','policy','Approve or disapprove configuration-controlled changes to the system, with explicit consideration for privacy impact analyses.','CM-03b.','N/A','Determine if: - proposed configuration-controlled changes to the system are reviewed. - proposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security and privacy impact analyses.'),
('003913','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for documenting proposed changes to the system.','CM-03(01)(a)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to document proposed changes to the system.'),
('003914','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for notifying approval authorities of proposed changes to the system and request change proposal.','CM-03(01)(b)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to notify [CM-03(01)_ODP[02]; approval authorities to be notified of and request approval for proposed changes to the system are defined] of proposed changes to the system and request change approval.'),
('003915','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for highlighting proposed changes to the system that have not been approved or disapproved within an organization-defined time period.','CM-03(01)(c)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to highlight proposed changes to the system that have not been approved or disapproved within [CM-03(01)_ODP[03]l the time period after which to highlight changes that have not been approved or disapproved is defined].'),
('003916','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for prohibiting changes to the system until designated approvals are received.','CM-03(01)(d)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to prohibit changes to the system until designated approvals are received.'),
('003917','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for documenting all changes to the system.','CM-03(01)(e)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to document all changes to the system.'),
('003918','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for notifying organization-defined personnel when approved changes to the system are completed.','CM-03(01)(f)','N/A','Determine if [CM-03(01)_ODP[01]; mechanisms used to automate configuration change control are defined] are used to notify [CM-03(01)_ODP[04]; personnel to be notified when approved changes are complete is/are defined] when approved changes to the system are completed.'),
('003919','draft','2022-03-02','DISA','policy','Defines the automated mechanisms to implement changes to the current system baseline.','CM-03(03)','N/A','Determine if: - changes to the current system baseline are implemented using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined]. - the updated baseline is deployed across the installed base using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined].'),
('003920','draft','2022-03-02','DISA','policy','Defines the automated mechanisms to deploy the updated baselines across the installed base.','CM-03(03)','N/A','Determine if: - changes to the current system baseline are implemented using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined]. - the updated baseline is deployed across the installed base using [CM-03(03)_ODP; mechanisms used to automate the implementation of changes and deployment of the updated baseline across the installed base are defined].'),
('003921','draft','2022-03-02','DISA','policy','Require an organization-defined privacy representative to be a member of the organization-defined configuration change control element.','CM-03(04)','N/A','Determine if: - [CM-03(04)_ODP[01]; security representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined]. - [CM-03(04)_ODP[02]; privacy representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined].'),
('003922','draft','2022-03-02','DISA','policy','Defines the security representatives required to be members of the configuration change control element.','CM-03(04)','N/A','Determine if: - [CM-03(04)_ODP[01]; security representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined]. - [CM-03(04)_ODP[02]; privacy representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined].'),
('003923','draft','2022-03-02','DISA','policy','Defines the privacy representatives required to be members of the configuration change control element.','CM-03(04)','N/A','Determine if: - [CM-03(04)_ODP[01]; security representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined]. - [CM-03(04)_ODP[02]; privacy representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined].'),
('003924','draft','2022-03-02','DISA','policy','Defines the configuration change control element required for security and privacy representatives.','CM-03(04)','N/A','Determine if: - [CM-03(04)_ODP[01]; security representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined]. - [CM-03(04)_ODP[02]; privacy representatives required to be members of the change control element are defined] are required to be members of the [CM-03(04)_ODP[03]; the configuration change control element of which the security and privacy representatives are to be members is defined].'),
('003925','draft','2022-03-02','DISA','policy','Review changes to the system on an organization-defined frequency or when there are organization-defined circumstances to determine whether unauthorized changes have occurred.','CM-03(07)','N/A','Determine if changes to the system are reviewed [CM-03(07)_ODP[01]; the frequency at which changes are to be reviewed is defined] or when [CM-03(07)_ODP[02]; the circumstances under which changes are to be reviewed are defined] to determine whether unauthorized changes have occurred.'),
('003926','draft','2022-03-02','DISA','policy','Defines the frequency for reviewing changes to the system.','CM-03(07)','N/A','Determine if changes to the system are reviewed [CM-03(07)_ODP[01]; the frequency at which changes are to be reviewed is defined] or when [CM-03(07)_ODP[02]; the circumstances under which changes are to be reviewed are defined] to determine whether unauthorized changes have occurred.'),
('003927','draft','2022-03-02','DISA','policy','Defines the circumstances for determining whether unauthorized changes to the system have occurred.','CM-03(07)','N/A','Determine if changes to the system are reviewed [CM-03(07)_ODP[01]; the frequency at which changes are to be reviewed is defined] or when [CM-03(07)_ODP[02]; the circumstances under which changes are to be reviewed are defined] to determine whether unauthorized changes have occurred.'),
('003928','draft','2022-03-02','DISA','technical','Prevent or restrict changes to the configuration of the system under organization-defined circumstances.','CM-03(08)','N/A','Determine if changes to the configuration of the system are prevented or restricted under [CM-03(08)_ODP; the circumstances under which changes are to be prevented or restricted are defined].'),
('003929','draft','2022-03-02','DISA','technical','Defines the circumstances for preventing or restricting changes to the configuration of the system.','CM-03(08)','N/A','Determine if changes to the configuration of the system are prevented or restricted under [CM-03(08)_ODP; the circumstances under which changes are to be prevented or restricted are defined].'),
('003930','draft','2022-03-02','DISA','policy','Analyze changes to the system to determine potential privacy impacts prior to change implementation.','CM-04','N/A','Determine if: - changes to the system are analyzed to determine potential security impacts prior to change implementation. - changes to the system are analyzed to determine potential privacy impacts prior to change implementation.'),
('003931','draft','2022-03-02','DISA','policy','When analyzing changes to the system, looks for security impacts due to flaws, weaknesses, incompatibility, or intentional malice.','CM-04(01)','N/A','Determine if: - changes to the system are analyzed in a separate test environment before implementation in an operational environment. - changes to the system are analyzed for security impacts due to flaws. - changes to the system are analyzed for privacy impacts due to flaws. - changes to the system are analyzed for security impacts due to weaknesses. - changes to the system are analyzed for privacy impacts due to weaknesses. - changes to the system are analyzed for privacy impacts due to incompatibility. - changes to the system are analyzed for privacy impacts due to incompatibility. - changes to the system are analyzed for security impacts due to intentional malice. - changes to the system are analyzed for privacy impacts due to intentional malice.'),
('003932','draft','2022-03-02','DISA','policy','After system changes, verify that the impacted controls are implemented correctly, meeting the privacy requirements for the system.','CM-04(02)','N/A','Determine if: - the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes. - the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.'),
('003933','draft','2022-03-02','DISA','policy','After system changes, verify that the impacted controls are operating as intended, meeting the privacy requirements for the system.','CM-04(02)','N/A','Determine if: - the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes. - the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.'),
('003934','draft','2022-03-02','DISA','policy','After system changes, verify that the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system.','CM-04(02)','N/A','Determine if: - the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes. - the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes. - the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes. - the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.'),
('003935','draft','2022-03-02','DISA','policy','Define and document physical access restrictions associated with changes to the system.','CM-05','N/A','Determine if: - physical access restrictions associated with changes to the system are defined and documented. - physical access restrictions associated with changes to the system are approved. - physical access restrictions associated with changes to the system are enforced. - logical access restrictions associated with changes to the system are defined and documented. - logical access restrictions associated with changes to the system are approved. - logical access restrictions associated with changes to the system are enforced.'),
('003936','draft','2022-03-02','DISA','policy','Define and document logical access restrictions associated with changes to the system.','CM-05','N/A','Determine if: - physical access restrictions associated with changes to the system are defined and documented. - physical access restrictions associated with changes to the system are approved. - physical access restrictions associated with changes to the system are enforced. - logical access restrictions associated with changes to the system are defined and documented. - logical access restrictions associated with changes to the system are approved. - logical access restrictions associated with changes to the system are enforced.'),
('003937','draft','2022-03-02','DISA','technical','Defines the automated mechanisms to enforce access restrictions.','CM-05(01)(a)','N/A','Determine if access restrictions for change are enforced using [CM-05(01)_ODP; mechanisms used to automate the enforcement of access restrictions are defined].'),
('003938','draft','2022-03-02','DISA','technical','Automatically generate audit records of the enforcement actions.','CM-05(01)(b)','N/A','Determine if audit records of enforcement actions are automatically generated.'),
('003939','draft','2022-03-02','DISA','policy','Defines the frequency with which to review and reevaluate system privileges.','CM-05(05)(b)','N/A','Determine if: - privileges are reviewed [CM-05(05)_ODP[01; frequency at which to review privileges is defined]. - privileges are reevaluated [CM-05(05)_ODP[02]; frequency at which to reevaluate privileges is defined].'),
('003940','draft','2022-03-02','DISA','policy','Review and reevaluate system privileges per an organization-defined frequency.','CM-05(05)(b)','N/A','Determine if: - privileges are reviewed [CM-05(05)_ODP[01; frequency at which to review privileges is defined]. - privileges are reevaluated [CM-05(05)_ODP[02]; frequency at which to reevaluate privileges is defined].'),
('003941','draft','2022-03-02','DISA','policy','Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using organization-defined common secure configurations.','CM-06a.','N/A','Determine if configuration settings that reflect the most restrictive mode consistent with operational requirements are established and documented for components employed within the system using [CM-06_ODP[01]; common secure configurations to establish and document configuration settings for components employed within the system are defined].'),
('003942','draft','2022-03-02','DISA','policy','Defines the common secure configurations for establishing and documenting configuration settings within the system, that reflect the most restrictive mode consistent with operational requirements.','CM-06a.','N/A','Determine if configuration settings that reflect the most restrictive mode consistent with operational requirements are established and documented for components employed within the system using [CM-06_ODP[01]; common secure configurations to establish and document configuration settings for components employed within the system are defined].'),
('003943','draft','2022-03-02','DISA','policy','Monitor changes to the configuration settings in accordance with organizational policies.','CM-06d.','N/A','Determine if: - changes to the configuration settings are monitored in accordance with organizational policies and procedures. - changes to the configuration settings are controlled in accordance with organizational policies and procedures.'),
('003944','draft','2022-03-02','DISA','policy','Monitor changes to the configuration settings in accordance with organizational procedures.','CM-06d.','N/A','Determine if: - changes to the configuration settings are monitored in accordance with organizational policies and procedures. - changes to the configuration settings are controlled in accordance with organizational policies and procedures.'),
('003945','draft','2022-03-02','DISA','policy','Control changes to the configuration settings in accordance with organizational policies.','CM-06d.','N/A','Determine if: - changes to the configuration settings are monitored in accordance with organizational policies and procedures. - changes to the configuration settings are controlled in accordance with organizational policies and procedures.'),
('003946','draft','2022-03-02','DISA','policy','Control changes to the configuration settings in accordance with organizational procedures.','CM-06d.','N/A','Determine if: - changes to the configuration settings are monitored in accordance with organizational policies and procedures. - changes to the configuration settings are controlled in accordance with organizational policies and procedures.'),
('003947','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for managing, applying, and verifying configuration settings.','CM-06(01)','N/A','Determine if: - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are managed using [CM-06(01)_ODP[02]; automated mechanisms to manage configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are applied using [CM-06(01)_ODP[03]; automated mechanisms to apply configuration settings are defined]. - configuration settings for [CM-06(01)_ODP[01]; system components for which to manage, apply, and verify configuration settings are defined] are verified using [CM-06(01)_ODP[04]; automated mechanisms to verify configuration settings are defined].'),
('003948','draft','2022-03-02','DISA','policy','Defines the mission essential capabilities for configuring the system.','CM-07a.','N/A','Determine if the system is configured to provide only [CM-07_ODP[01]; mission-essential capabilities for the system are defined].'),
('003949','draft','2022-03-02','DISA','policy','Require that organization-defined user-installed software in a confined physical or virtual machine environment with limited privileges.','CM-07(06)','N/A','Determine if [CM-07(06)_ODP; user-installed software required to be executed in a confined environment is defined] is required to be executed in a confined physical or virtual machine environment with limited privileges.'),
('003950','draft','2022-03-02','DISA','policy','Defines the user-installed software required for executing in a confined physical or virtual machine environment with limited privileges.','CM-07(06)','N/A','Determine if [CM-07(06)_ODP; user-installed software required to be executed in a confined environment is defined] is required to be executed in a confined physical or virtual machine environment with limited privileges.'),
('003951','draft','2022-03-02','DISA','policy','Allow execution of binary or machine-executable code only in confined physical or virtual machine environments and with the explicit approval of organization-defined personnel or roles when such code is obtained from sources with limited or no warranty.','CM-07(07)(a)','N/A','Determine if the execution of binary or machine-executable code obtained from sources with limited or no warranty is only allowed with the explicit approval of [CM-07(07)_ODP; personnel or roles to explicitly approve execution of binary or machine-executable code is/are defined].'),
('003952','draft','2022-03-02','DISA','policy','Defines the personnel or roles who allow execution of binary or machine-executable code only in confined physical or virtual machine environments when such code is obtained from sources with limited or no warranty.','CM-07(07)(a)','N/A','Determine if the execution of binary or machine-executable code obtained from sources with limited or no warranty is only allowed with the explicit approval of [CM-07(07)_ODP; personnel or roles to explicitly approve execution of binary or machine-executable code is/are defined].'),
('003953','draft','2022-03-02','DISA','policy','Allow execution of binary or machine-executable code only in confined physical or virtual machine environments and with the explicit approval of organization-defined personnel or roles when such code is without the provision of source code.','CM-07(07)(b)','N/A','Determine if the execution of binary or machine-executable code without the provision of source code is only allowed with the explicit approval of [CM-07(07)_ODP; personnel or roles to explicitly approve execution of binary or machine-executable code is/are defined].'),
('003954','draft','2022-03-02','DISA','policy','Defines the personnel or roles who allow execution of binary or machine-executable code only in confined physical or virtual machine environments when such code is without the provision of source code.','CM-07(07)(b)','N/A','Determine if the execution of binary or machine-executable code without the provision of source code is only allowed with the explicit approval of [CM-07(07)_ODP; personnel or roles to explicitly approve execution of binary or machine-executable code is/are defined].'),
('003955','draft','2022-03-02','DISA','policy','Prohibit the use of binary or machine-executable code from sources with limited or no warranty or without the provision of source code.','CM-07(08)(a)','N/A','Determine if the use of binary or machine-executable code is prohibited when it originates from sources with limited or no warranty or without the provision of source code.'),
('003956','draft','2022-03-02','DISA','policy','Allow exceptions only for compelling mission or operational requirements and with the approval of the authorizing official.','CM-07(08)(b)','N/A','Determine if: - exceptions to the prohibition of binary or machine-executable code from sources with limited or no warranty or without the provision of source code are allowed only for compelling mission or operational requirements. - exceptions to the prohibition of binary or machine-executable code from sources with limited or no warranty or without the provision of source code are allowed only with the approval of the authorizing official.'),
('003957','draft','2022-03-02','DISA','policy','Identify organization-defined hardware components authorized for system use.','CM-07(09)(a)','N/A','Determine if [CM-07(09)_ODP[01]; hardware components authorized for system use are defined] are identified.'),
('003958','draft','2022-03-02','DISA','policy','Defines the hardware components to be identified for authorized system use.','CM-07(09)(a)','N/A','Determine if [CM-07(09)_ODP[01]; hardware components authorized for system use are defined] are identified.'),
('003959','draft','2022-03-02','DISA','policy','Prohibit the use or connection of unauthorized hardware components.','CM-07(09)(b)','N/A','Determine if the use or connection of unauthorized hardware components is prohibited.'),
('003960','draft','2022-03-02','DISA','policy','Review and update the list of authorized hardware components on an organization-defined frequency.','CM-07(09)(c)','N/A','Determine if the list of authorized hardware components is reviewed and updated [CM-07(09)_ODP[02]; frequency at which to review and update the list of authorized hardware components is defined].'),
('003961','draft','2022-03-02','DISA','policy','Defines the frequency the hardware components are reviewed and updated.','CM-07(09)(c)','N/A','Determine if the list of authorized hardware components is reviewed and updated [CM-07(09)_ODP[02]; frequency at which to review and update the list of authorized hardware components is defined].'),
('003962','draft','2022-03-02','DISA','policy','Develop and document an inventory of system components that accurately reflects the system.','CM-08a.01','N/A','Determine if an inventory of system components that accurately reflects the system is developed and documented.'),
('003963','draft','2022-03-02','DISA','policy','Develop and document an inventory of system components that includes all components within the system.','CM-08a.02','N/A','Determine if an inventory of system components that includes all components within the system is developed and documented.'),
('003964','draft','2022-03-02','DISA','policy','Develop and document an inventory of system components that does not include duplicate accounting of components or components assigned to any other system.','CM-08a.03','N/A','Determine if an inventory of system components that does not include duplicate accounting of components or components assigned to any other system is developed and documented.'),
('003965','draft','2022-03-02','DISA','policy','Develop and document an inventory of system components that is at the level of granularity deemed necessary for tracking.','CM-08a.04','N/A','Determine if an inventory of system components that is at the level of granularity deemed necessary for tracking and reporting is developed and documented.'),
('003966','draft','2022-03-02','DISA','policy','Develop and document an inventory of system components that is at the level of granularity deemed necessary for reporting.','CM-08a.04','N/A','Determine if an inventory of system components that is at the level of granularity deemed necessary for tracking and reporting is developed and documented.'),
('003967','draft','2022-03-02','DISA','policy','Develop and document an inventory of system components that includes organization-defined information deemed necessary to achieve effective system component accountability.','CM-08a.05','N/A','Determine if an inventory of system components that includes [CM-08_ODP[01]; information deemed necessary to achieve effective system component accountability is defined] is developed and documented.'),
('003968','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for maintaining the currency, completeness, accuracy, and availability of the inventory of the system components.','CM-08(02)','N/A','Determine if: - [CM-08(02)_ODP[01]; automated mechanisms used to maintain the currency of the system component inventory are defined] are used to maintain the currency of the system component inventory. - [CM-08(02)_ODP[02]; automated mechanisms used to maintain the completeness of the system component inventory are defined] are used to maintain the completeness of the system component inventory. - [CM-08(02)_ODP[03]; automated mechanisms used to maintain the accuracy of the system component inventory are defined] are used to maintain the accuracy of the system component inventory. - [CM-08(02)_ODP[04]; automated mechanisms used to maintain the availability of the system component inventory are defined] are used to maintain the availability of the system component inventory.'),
('003969','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for detecting the presence of unauthorized hardware, software, and firmware components within the system.','CM-08(03)(a)','N/A','Determine if: - the presence of unauthorized hardware within the system is detected using [CM-08(03)_ODP[01]; automated mechanisms used to detect the presence of unauthorized hardware within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined]. - the presence of unauthorized software within the system is detected using [CM-08(03)_ODP[02]; automated mechanisms used to detect the presence of unauthorized software within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined;]. - the presence of unauthorized firmware within the system is detected using [CM-08(03)_ODP[03]; automated mechanisms used to detect the presence of unauthorized firmware within the system are defined] [CM-08(03)_ODP[04]; frequency at which automated mechanisms are used to detect the presence of unauthorized system components within the system is defined].'),
('003970','draft','2022-03-02','DISA','policy','Defines the automated mechanisms for supporting the tracking of system components by geographic location.','CM-08(08)','N/A','Determine if [CM-08(08)_ODP; automated mechanisms for tracking components are defined] are used to support the tracking of system components by geographic location.'),
('003971','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that addresses roles, responsibilities, and configuration management processes.','CM-09a.','N/A','Determine if: - the configuration management plan addresses roles. - the configuration management plan addresses responsibilities. - the configuration management plan addresses configuration management processes and procedures.'),
('003972','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that addresses roles, responsibilities, and configuration management procedures.','CM-09a.','N/A','Determine if: - the configuration management plan addresses roles. - the configuration management plan addresses responsibilities. - the configuration management plan addresses configuration management processes and procedures.'),
('003973','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that establishes a process for identifying configuration items throughout the system development life cycle.','CM-09b.','N/A','Determine if: - the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle. - the configuration management plan establishes a process for managing the configuration of the configuration items.'),
('003974','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that establishes a process for managing the configuration of the configuration items.','CM-09b.','N/A','Determine if: - the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle. - the configuration management plan establishes a process for managing the configuration of the configuration items.'),
('003975','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that defines the configuration items for the system.','CM-09c.','N/A','Determine if: - the configuration management plan defines the configuration items for the system. - the configuration management plan places the configuration items under configuration management.'),
('003976','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that places the configuration items under configuration management.','CM-09c.','N/A','Determine if: - the configuration management plan defines the configuration items for the system. - the configuration management plan places the configuration items under configuration management.'),
('003977','draft','2022-03-02','DISA','policy','Develop and document a configuration management plan for the system that is reviewed and approved by organization-defined personnel or roles.','CM-09d.','N/A','Determine if the configuration management plan is reviewed and approved by [CM-09_ODP; personnel or roles to review and approve the configuration management plan is/are defined].'),
('003978','draft','2022-03-02','DISA','policy','Defines the personnel or roles for those who review and approve the configuration management plan.','CM-09d.','N/A','Determine if the configuration management plan is reviewed and approved by [CM-09_ODP; personnel or roles to review and approve the configuration management plan is/are defined].'),
('003979','draft','2022-03-02','DISA','policy','Implement a configuration management plan for the system that is reviewed and approved by organization-defined personnel or roles.','CM-09d.','N/A','Determine if the configuration management plan is reviewed and approved by [CM-09_ODP; personnel or roles to review and approve the configuration management plan is/are defined].'),
('003980','draft','2022-03-02','DISA','technical','Allow user installation of software only with explicit privileged status.','CM-11(02)','N/A','Determine if user installation of software is allowed only with explicit privileged status.'),
('003981','draft','2022-03-02','DISA','technical','Enforce and monitor compliance with software installation policies using organization-defined automated mechanisms.','CM-11(03)','N/A','Determine if: - compliance with software installation policies is enforced using [CM-11(03)_ODP[01]; automated mechanisms used to enforce compliance are defined]. - compliance with software installation policies is monitored using [CM-11(03)_ODP[02]; automated mechanisms used to monitor compliance are defined].'),
('003982','draft','2022-03-02','DISA','policy','Identify and document the location of the organization-defined information on which the information is processed and stored.','CM-12a.','N/A','Determine if: - the location of [CM-12_ODP; information for which the location is to be identified and documented is defined] is identified and documented. - the specific system components on which [CM-12_ODP; information for which the location is to be identified and documented is defined] is processed are identified and documented. - the specific system components on which [CM-12_ODP; information for which the location is to be identified and documented is defined] is stored are identified and documented.'),
('003983','draft','2022-03-02','DISA','policy','Identify and document the specific system components on which the organization-defined information is processed and stored.','CM-12a.','N/A','Determine if: - the location of [CM-12_ODP; information for which the location is to be identified and documented is defined] is identified and documented. - the specific system components on which [CM-12_ODP; information for which the location is to be identified and documented is defined] is processed are identified and documented. - the specific system components on which [CM-12_ODP; information for which the location is to be identified and documented is defined] is stored are identified and documented.'),
('003984','draft','2022-03-02','DISA','policy','Defines the information on which the location and specific system components are processed and stored.','CM-12a.','N/A','Determine if: - the location of [CM-12_ODP; information for which the location is to be identified and documented is defined] is identified and documented. - the specific system components on which [CM-12_ODP; information for which the location is to be identified and documented is defined] is processed are identified and documented. - the specific system components on which [CM-12_ODP; information for which the location is to be identified and documented is defined] is stored are identified and documented.'),
('003985','draft','2022-03-02','DISA','policy','Identify and document the users who have access to the system where the information is processed and stored.','CM-12b.','N/A','Determine if: - the users who have access to the system and system components where [CM-12_ODP; information for which the location is to be identified and documented is defined] is processed are identified and documented. - the users who have access to the system and system components where [CM-12_ODP; information for which the location is to be identified and documented is defined] is stored are identified and documented.'),
('003986','draft','2022-03-02','DISA','policy','Identify and document the users who have access to the system components where the information is processed and stored.','CM-12b.','N/A','Determine if: - the users who have access to the system and system components where [CM-12_ODP; information for which the location is to be identified and documented is defined] is processed are identified and documented. - the users who have access to the system and system components where [CM-12_ODP; information for which the location is to be identified and documented is defined] is stored are identified and documented.'),
('003987','draft','2022-03-02','DISA','policy','Document changes to the location (i.e., system or system components) where the information is processed and stored.','CM-12c.','N/A','Determine if: - changes to the location (i.e., system or system components) where [CM-12_ODP; information for which the location is to be identified and documented is defined] is processed are documented. - changes to the location (i.e., system or system components) where [CM-12_ODP; information for which the location is to be identified and documented is defined] is stored are documented.'),
('003988','draft','2022-03-02','DISA','policy','Use automated tools to identify organization-defined information by information type on organization-defined components to ensure adequate controls are in place to protect organizational information.','CM-12(01)','N/A','Determine if automated tools are used to identify [CM-12(01)_ODP[01]; information to be protected is defined by information type] on [CM-12(01)_ODP[02]; system components where the information is located are defined] to ensure that controls are in place to protect organizational information and individual privacy.'),
('003989','draft','2022-03-02','DISA','policy','Defines the information by information type for identifying automated tools.','CM-12(01)','N/A','Determine if automated tools are used to identify [CM-12(01)_ODP[01]; information to be protected is defined by information type] on [CM-12(01)_ODP[02]; system components where the information is located are defined] to ensure that controls are in place to protect organizational information and individual privacy.'),
('003990','draft','2022-03-02','DISA','policy','Defines the system components used to ensure controls are in place to protect organizational information and individual privacy.','CM-12(01)','N/A','Determine if automated tools are used to identify [CM-12(01)_ODP[01]; information to be protected is defined by information type] on [CM-12(01)_ODP[02]; system components where the information is located are defined] to ensure that controls are in place to protect organizational information and individual privacy.'),
('003991','draft','2022-03-02','DISA','policy','Develop and document a map of system data actions.','CM-13','N/A','Determine if a map of system data actions is developed and documented.'),
('003992','draft','2022-03-02','DISA','policy','Prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization.','CM-14','N/A','Determine if: - the installation of [CM-14_ODP[01]; software components requiring verification of a digitally signed certificate before installation are defined] is prevented unless it is verified that the software has been digitally signed using a certificate recognized and approved by the organization. - the installation of [CM-14_ODP[02]; firmware components requiring verification of a digitally signed certificate before installation are defined] is prevented unless it is verified that the firmware has been digitally signed using a certificate recognized and approved by the organization.'),
('003993','draft','2022-03-02','DISA','policy','Defines the software and firmware for preventing installation without verification that the component has been digitally signed.','CM-14','N/A','Determine if: - the installation of [CM-14_ODP[01]; software components requiring verification of a digitally signed certificate before installation are defined] is prevented unless it is verified that the software has been digitally signed using a certificate recognized and approved by the organization. - the installation of [CM-14_ODP[02]; firmware components requiring verification of a digitally signed certificate before installation are defined] is prevented unless it is verified that the firmware has been digitally signed using a certificate recognized and approved by the organization.'),
('003994','draft','2022-03-02','DISA','policy','Develop and document an organizational-level; mission/business process-level; and/or system-level contingency planning policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','CP-01a.01(b)','N/A','Determine if the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('003995','draft','2022-03-02','DISA','policy','Disseminate an organizational-level; mission/business process-level; and/or system-level contingency planning policy to organization-defined personnel or roles that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','CP-01a.01(b)','N/A','Determine if the [CP-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] contingency planning policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('003996','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage development and documentation of the contingency planning policy.','CP-01b.','N/A','Determine if the [CP-01_ODP[04]; an official to manage the contingency planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the contingency planning policy and procedures.'),
('003997','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage dissemination of the contingency planning policy.','CP-01b.','N/A','Determine if the [CP-01_ODP[04]; an official to manage the contingency planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the contingency planning policy and procedures.'),
('003998','draft','2022-03-02','DISA','policy','Defines the official designated to manage the development, documentation, and dissemination of the contingency policy.','CP-01b.','N/A','Determine if the [CP-01_ODP[04]; an official to manage the contingency planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the contingency planning policy and procedures.'),
('003999','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the development and documentation of the contingency planning procedures.','CP-01b.','N/A','Determine if the [CP-01_ODP[04]; an official to manage the contingency planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the contingency planning policy and procedures.'),
('004000','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage the dissemination of the contingency procedures.',NULL,'N/A',NULL),
('004001','draft','2022-03-02','DISA','policy','Defines the official designated to manage the development, documentation, and dissemination of the contingency procedures.','CP-01b.','N/A','Determine if the [CP-01_ODP[04]; an official to manage the contingency planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the contingency planning policy and procedures.'),
('004002','draft','2022-03-02','DISA','policy','Review and update the current contingency planning policy following organization-defined events.','CP-01c.01','N/A','Determine if: - the current contingency planning policy is reviewed and updated [CP-01_ODP[05]; the frequency at which the current contingency planning policy is reviewed and updated is defined]. - the current contingency planning policy is reviewed and updated following [CP-01_ODP[06]; events that would require the current contingency planning policy to be reviewed and updated are defined].'),
('004003','draft','2022-03-02','DISA','policy','Defines the events with which to review and update the current contingency planning policy.','CP-01c.01','N/A','Determine if: - the current contingency planning policy is reviewed and updated [CP-01_ODP[05]; the frequency at which the current contingency planning policy is reviewed and updated is defined]. - the current contingency planning policy is reviewed and updated following [CP-01_ODP[06]; events that would require the current contingency planning policy to be reviewed and updated are defined].'),
('004004','draft','2022-03-02','DISA','policy','Review and update the current contingency planning procedures following organization-defined events.','CP-01c.02','N/A','Determine if: - the current contingency planning procedures are reviewed and updated [CP-01_ODP[07]; the frequency at which the current contingency planning procedures are reviewed and updated is defined]. - the current contingency planning procedures are reviewed and updated following [CP-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('004005','draft','2022-03-02','DISA','policy','Defines the events with which to review and update the current contingency planning procedures.','CP-01c.02','N/A','Determine if: - the current contingency planning procedures are reviewed and updated [CP-01_ODP[07]; the frequency at which the current contingency planning procedures are reviewed and updated is defined]. - the current contingency planning procedures are reviewed and updated following [CP-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('004006','draft','2022-03-02','DISA','policy','Develop a contingency plan for the system that addresses maintaining essential mission functions despite a system disruption, compromise, or failure.','CP-02a.04','N/A','Determine if a contingency plan for the system is developed that addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure.'),
('004007','draft','2022-03-02','DISA','policy','Develop a contingency plan for the system that addresses maintaining essential business functions despite a system disruption, compromise, or failure.','CP-02a.04','N/A','Determine if a contingency plan for the system is developed that addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure.'),
('004008','draft','2022-03-02','DISA','policy','Develop a contingency plan for the system that addresses the sharing of contingency information.','CP-02a.06','N/A','Determine if a contingency plan for the system is developed that addresses the sharing of contingency information.'),
('004009','draft','2022-03-02','DISA','policy','Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training.','CP-02g.','N/A','Determine if: - lessons learned from contingency plan testing or actual contingency activities are incorporated into contingency testing. - lessons learned from contingency plan training or actual contingency activities are incorporated into contingency testing and training.'),
('004010','draft','2022-03-02','DISA','policy','Review and update contingency training content on an organization-defined frequency.','CP-03b.','N/A','Determine if: - the contingency plan training content is reviewed and updated [CP-03_ODP[03]; frequency at which to review and update contingency training content is defined]. - the contingency plan training content is reviewed and updated following [CP-03_ODP[04]; events necessitating review and update of contingency training are defined].'),
('004011','draft','2022-03-02','DISA','policy','Defines the frequency the contingency training content will be reviewed and updated.','CP-03b.','N/A','Determine if: - the contingency plan training content is reviewed and updated [CP-03_ODP[03]; frequency at which to review and update contingency training content is defined]. - the contingency plan training content is reviewed and updated following [CP-03_ODP[04]; events necessitating review and update of contingency training are defined].'),
('004012','draft','2022-03-02','DISA','policy','Review and update contingency training content following organization-defined events.','CP-03b.','N/A','Determine if: - the contingency plan training content is reviewed and updated [CP-03_ODP[03]; frequency at which to review and update contingency training content is defined]. - the contingency plan training content is reviewed and updated following [CP-03_ODP[04]; events necessitating review and update of contingency training are defined].'),
('004013','draft','2022-03-02','DISA','policy','Defines the events for which the contingency training content will be reviewed and updated.','CP-03b.','N/A','Determine if: - the contingency plan training content is reviewed and updated [CP-03_ODP[03]; frequency at which to review and update contingency training content is defined]. - the contingency plan training content is reviewed and updated following [CP-03_ODP[04]; events necessitating review and update of contingency training are defined].'),
('004014','draft','2022-03-02','DISA','policy','Defines the automated mechanisms to test the contingency plan.','CP-04(03)','N/A','Determine if the contingency plan is tested using [CP-04(03)_ODP; automated mechanisms for contingency plan testing are defined].'),
('004015','draft','2022-03-02','DISA','policy','Employ organization-defined mechanisms to organization-defined system or system component to disrupt and adversely affect the system or system component.','CP-04(05)','N/A','Determine if [CP-04(05)_ODP[01]; mechanisms employed to disrupt and adversely affect the system or system component are defined] are employed to disrupt and adversely affect the [CP-04(05)_ODP[02]; system or system component on which to apply disruption mechanisms are defined].'),
('004016','draft','2022-03-02','DISA','policy','Defines the mechanisms employed to disrupt and adversely affect the system or system component.','CP-04(05)','N/A','Determine if [CP-04(05)_ODP[01]; mechanisms employed to disrupt and adversely affect the system or system component are defined] are employed to disrupt and adversely affect the [CP-04(05)_ODP[02]; system or system component on which to apply disruption mechanisms are defined].'),
('004017','draft','2022-03-02','DISA','policy','Defines the system or system component used to employ organization-defined mechanisms.','CP-04(05)','N/A','Determine if [CP-04(05)_ODP[01]; mechanisms employed to disrupt and adversely affect the system or system component are defined] are employed to disrupt and adversely affect the [CP-04(05)_ODP[02]; system or system component on which to apply disruption mechanisms are defined].'),
('004018','draft','2022-03-02','DISA','policy','Establish an alternate storage site, including necessary agreements to permit the retrieval of system backup information.','CP-06a.','N/A','Determine if: - an alternate storage site is established. - establishment of the alternate storage site includes necessary agreements to permit the storage and retrieval of system backup information.'),
('004019','draft','2022-03-02','DISA','policy','Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness in the event that the primary and/or alternate telecommunications services are provided by a common carrier.','CP-08(01)(b)','N/A','Determine if Telecommunications Service Priority is requested for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier.'),
('004020','draft','2022-03-02','DISA','policy','Defines the system components to conduct backups of user level information.','CP-09a.','N/A','Determine if backups of user-level information contained in [CP-09_ODP[01]; system components for which to conduct backups of user-level information is defined] are conducted [CP-09_ODP[02]; frequency at which to conduct backups of user-level information consistent with recovery time and recovery point objectives is defined].'),
('004021','draft','2022-03-02','DISA','policy','Conduct backups of system documentation, including privacy-related documentation, per an organization-defined frequency that is consistent with recovery time and recovery point objectives.','CP-09c.','N/A','Determine if backups of system documentation, including security- and privacy-related documentation are conducted [CP-09_ODP[04]; frequency at which to conduct backups of system documentation consistent with recovery time and recovery point objectives is defined].'),
('004022','draft','2022-03-02','DISA','policy','Protect the confidentiality of backup information.','CP-09d.','N/A','Determine if: - the confidentiality of backup information is protected. - the integrity of backup information is protected. - the availability of backup information is protected.'),
('004023','draft','2022-03-02','DISA','policy','Protect integrity of backup information.','CP-09d.','N/A','Determine if: - the confidentiality of backup information is protected. - the integrity of backup information is protected. - the availability of backup information is protected.'),
('004024','draft','2022-03-02','DISA','policy','Protect the availability of backup information.','CP-09d.','N/A','Determine if: - the confidentiality of backup information is protected. - the integrity of backup information is protected. - the availability of backup information is protected.'),
('004025','draft','2022-03-02','DISA','policy','Implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined backup information.','CP-09(08)','N/A','Determine if cryptographic mechanisms are implemented to prevent unauthorized disclosure and modification of [CP-09(08)_ODP; backup information to protect against unauthorized disclosure and modification is defined].'),
('004026','draft','2022-03-02','DISA','policy','Implement cryptographic mechanisms to prevent unauthorized modification of organization-defined backup information.','CP-09(08)','N/A','Determine if cryptographic mechanisms are implemented to prevent unauthorized disclosure and modification of [CP-09(08)_ODP; backup information to protect against unauthorized disclosure and modification is defined].'),
('004027','draft','2022-03-02','DISA','policy','Defines the backup information which is protected by cryptographic mechanisms preventing unauthorized disclosure and modification.','CP-09(08)','N/A','Determine if cryptographic mechanisms are implemented to prevent unauthorized disclosure and modification of [CP-09(08)_ODP; backup information to protect against unauthorized disclosure and modification is defined].'),
('004028','draft','2022-03-02','DISA','policy','Provide for the recovery and reconstitution of the system to a known state within an organization-defined time-period consistent with recovery time and recovery point objectives after a disruption, compromise, or failure.','CP-10','N/A','Determine if: - the recovery of the system to a known state is provided within [CP-10_ODP[01]; time period consistent with recovery time and recovery point objectives for the recovery of the system is determined] after a disruption, compromise, or failure. - a reconstitution of the system to a known state is provided within [CP-10_ODP[02]; time period consistent with recovery time and recovery point objectives for the reconstitution of the system is determined] after a disruption, compromise, or failure.'),
('004029','draft','2022-03-02','DISA','policy','Defines the time-period consistent with recovery time and recovery point objectives for the recovery and reconstitution of the system.','CP-10','N/A','Determine if: - the recovery of the system to a known state is provided within [CP-10_ODP[01]; time period consistent with recovery time and recovery point objectives for the recovery of the system is determined] after a disruption, compromise, or failure. - a reconstitution of the system to a known state is provided within [CP-10_ODP[02]; time period consistent with recovery time and recovery point objectives for the reconstitution of the system is determined] after a disruption, compromise, or failure.'),
('004030','draft','2022-03-02','DISA','policy','Protect system components used for recovery and reconstitution.','CP-10(06)','N/A','Determine if system components used for recovery and reconstitution are protected.'),
('004031','draft','2022-03-02','DISA','policy','Defines the personnel or roles the organization-level; mission/business process-level; and/or system-level identification and authorization policy is disseminated to.','IA-01a.','N/A','Determine if: - an identification and authentication policy is developed and documented. - the identification and authentication policy is disseminated to [IA-01_ODP[01]; personnel or roles to whom the identification and authentication policy is to be disseminated are defined].'),
('004032','draft','2022-03-02','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level identification and authorization policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination, among organizational entities, and compliance.','IA-01a.01(a)','N/A','Determine if: - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses purpose. - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses scope. - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses roles. - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses responsibilities. - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses management commitment. - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses coordination among organizational entities. - the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy addresses compliance.'),
('004033','draft','2022-03-02','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level identification and authorization policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','IA-01a.01(b)','N/A','Determine if the [IA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] identification and authentication policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.'),
('004034','draft','2022-03-02','DISA','policy','Develop and document the procedures to facilitate the implementation of the identification and authorization policy and the associated identification and authentication controls.','IA-01a.02','N/A','Determine if: - identification and authentication procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls are developed and documented. - Determine if the identification and authentication procedures are disseminated to [IA-01_ODP[02]; personnel or roles to whom the identification and authentication procedures are to be disseminated is/are defined].'),
('004035','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage development and documentation of the identification and authentication policy.','IA-01b.','N/A','Determine if the [IA-01_ODP[04]; an official to manage the identification and authentication policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures.'),
('004036','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage dissemination of the identification and authentication policy.','IA-01b.','N/A','Determine if the [IA-01_ODP[04]; an official to manage the identification and authentication policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures.'),
('004037','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage development and documentation of the identification and authentication procedures.','IA-01b.','N/A','Determine if the [IA-01_ODP[04]; an official to manage the identification and authentication policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures.'),
('004038','draft','2022-03-02','DISA','policy','Designate an organization-defined official to manage dissemination of the identification and authentication procedures.','IA-01b.','N/A','Determine if the [IA-01_ODP[04]; an official to manage the identification and authentication policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures.'),
('004039','draft','2022-03-02','DISA','policy','Defines the official designated to managing the development, documentation, and dissemination of the identification and authentication policy.','IA-01b.','N/A','Determine if the [IA-01_ODP[04]; an official to manage the identification and authentication policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures.'),
('004040','draft','2022-03-02','DISA','policy','Defines the official designated to managing the development, documentation, and dissemination of the identification and authentication procedures.','IA-01b.','N/A','Determine if the [IA-01_ODP[04]; an official to manage the identification and authentication policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the identification and authentication policy and procedures.'),
('004041','draft','2022-03-02','DISA','policy','Review and update the current identification and authentication policy following organization-defined events.','IA-01c.01','N/A','Determine if: - the current identification and authentication policy is reviewed and updated [IA-01_ODP[05]; the frequency at which the current identification and authentication policy is reviewed and updated is defined]. - the current identification and authentication policy is reviewed and updated following [IA-01_ODP[06]; events that would require the current identification and authentication policy to be reviewed and updated are defined].'),
('004042','draft','2022-03-02','DISA','policy','Defines the events following reviewing and updating the current identification and authentication policy.','IA-01c.01','N/A','Determine if: - the current identification and authentication policy is reviewed and updated [IA-01_ODP[05]; the frequency at which the current identification and authentication policy is reviewed and updated is defined]. - the current identification and authentication policy is reviewed and updated following [IA-01_ODP[06]; events that would require the current identification and authentication policy to be reviewed and updated are defined].'),
('004043','draft','2022-03-02','DISA','policy','Review and update the current identification and authentication procedures following organization-defined events.','IA-01c.02','N/A','Determine if: - the current identification and authentication procedures are reviewed and updated [IA-01_ODP[07]; the frequency at which the current identification and authentication procedures are reviewed and updated is defined]. - the current identification and authentication procedures are reviewed and updated following [IA-01_ODP[08]; events that would require identification and authentication procedures to be reviewed and updated are defined].'),
('004044','draft','2022-03-02','DISA','policy','Defines the events following reviewing and updating the current identification and authentication procedures.','IA-01c.02','N/A','Determine if: - the current identification and authentication procedures are reviewed and updated [IA-01_ODP[07]; the frequency at which the current identification and authentication procedures are reviewed and updated is defined]. - the current identification and authentication procedures are reviewed and updated following [IA-01_ODP[08]; events that would require identification and authentication procedures to be reviewed and updated are defined].'),
('004045','draft','2022-03-02','DISA','policy','Require users to be individually authenticated before granting access to the shared accounts or resources.','IA-02(05)','N/A','Determine if users are required to be individually authenticated before granting access to the shared accounts or resources when shared accounts or authenticators are employed.'),
('004046','draft','2022-03-02','DISA','technical','Implement multi-factor authentication for local; network; and/or remote access to privileged accounts; and/or non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access.','IA-02(06)(a)','N/A','Determine if multi-factor authentication is implemented for [IA-02(06)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {local; network; remote}] access to [IA-02(06)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {privileged accounts; non-privileged accounts}] such that one of the factors is provided by a device separate from the system gaining access.'),
('004047','draft','2022-03-02','DISA','technical','Implement multi-factor authentication for local; network; and/or remote access to privileged accounts; and/or non-privileged accounts such that the device meets organization-defined strength of mechanism requirements.','IA-02(06)(b)','N/A','Determine if multi-factor authentication is implemented for [IA-02(06)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {local; network; remote}] access to [IA-02(06)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {privileged accounts; non-privileged accounts}] such that the device meets [IA-02(06)_ODP[03]; the strength of mechanism requirements to be enforced by a device separate from the system gaining access to accounts is defined].'),
('004048','draft','2022-03-02','DISA','technical','Defines the strength of mechanism requirements for implementing multi-factor authentication.','IA-02(06)(b)','N/A','Determine if multi-factor authentication is implemented for [IA-02(06)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {local; network; remote}] access to [IA-02(06)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {privileged accounts; non-privileged accounts}] such that the device meets [IA-02(06)_ODP[03]; the strength of mechanism requirements to be enforced by a device separate from the system gaining access to accounts is defined].'),
('004049','draft','2022-03-02','DISA','technical','Defines the dynamic identifier policy for managing individual identifiers dynamically.','IA-04(05)','N/A','Determine if individual identifiers are dynamically managed in accordance with [IA-04(05)_ODP; a dynamic identifier policy for managing individual identifiers is defined].'),
('004050','draft','2022-03-02','DISA','policy','Generate pairwise pseudonymous identifiers.','IA-04(08)','N/A','Determine if pairwise pseudonymous identifiers are generated.'),
('004051','draft','2022-03-02','DISA','policy','Maintain the attributes for each uniquely identified individual, device, or service in organization-defined protected central storage.','IA-04(09)','N/A','Determine if the attributes for each uniquely identified individual, device, or service are maintained in [IA-04(09)_ODP; protected central storage used to maintain the attributes for each uniquely identified individual, device, or service is defined].'),
('004052','draft','2022-03-02','DISA','policy','Defines the protected central storage for maintaining the attributes for each uniquely individual, device or service.','IA-04(09)','N/A','Determine if the attributes for each uniquely identified individual, device, or service are maintained in [IA-04(09)_ODP; protected central storage used to maintain the attributes for each uniquely identified individual, device, or service is defined].'),
('004053','draft','2022-03-02','DISA','policy','Manage system authenticators by establishing administrative procedures for lost/compromised or damaged authenticators.','IA-05d.','N/A','Determine if system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators.'),
('004054','draft','2022-03-02','DISA','policy','Manage system authenticators by implementing administrative procedures for lost/compromised or damaged authenticators.','IA-05d.','N/A','Determine if system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators.'),
('004055','draft','2022-03-02','DISA','policy','Manage system authenticators by changing default authenticators prior to first use.','IA-05e.','N/A','Determine if system authenticators are managed through the change of default authenticators prior to first use.'),
('004056','draft','2022-03-02','DISA','policy','Defines the events for when to change or refresh authenticators.','IA-05f.','N/A','Determine if system authenticators are managed through the change or refreshment of authenticators [IA-05_ODP[01]; a time period for changing or refreshing authenticators by authenticator type is defined] or when [IA-05_ODP[02]; events that trigger the change or refreshment of authenticators are defined] occur.'),
('004057','draft','2022-03-02','DISA','policy','Defines the frequency for updating commonly used, expected, or compromised passwords, when they are suspected of being compromised directly or indirectly.','IA-05(01)(a)','N/A','Determine if for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated [IA-05(01)_ODP[01]; the frequency at which to update the list of commonly used, expected, or compromised passwords is defined] and when organizational passwords are suspected to have been compromised directly or indirectly.'),
('004058','draft','2022-03-02','DISA','technical','For password-based authentication, maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency.','IA-05(01)(a)','N/A','Determine if for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated [IA-05(01)_ODP[01]; the frequency at which to update the list of commonly used, expected, or compromised passwords is defined] and when organizational passwords are suspected to have been compromised directly or indirectly.'),
('004059','draft','2022-03-02','DISA','technical','For password-based authentication, update the list of passwords on an organization-defined frequency.','IA-05(01)(a)','N/A','Determine if for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated [IA-05(01)_ODP[01]; the frequency at which to update the list of commonly used, expected, or compromised passwords is defined] and when organizational passwords are suspected to have been compromised directly or indirectly.'),
('004060','draft','2022-03-02','DISA','technical','For password-based authentication, update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly.','IA-05(01)(a)','N/A','Determine if for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated [IA-05(01)_ODP[01]; the frequency at which to update the list of commonly used, expected, or compromised passwords is defined] and when organizational passwords are suspected to have been compromised directly or indirectly.'),
('004061','draft','2022-03-02','DISA','technical','For password-based authentication, verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a).','IA-05(01)(b)','N/A','Determine if for password-based authentication when passwords are created or updated by users, the passwords are verified not to be found on the list of commonly used, expected, or compromised passwords in IA-05(01)(a).'),
('004062','draft','2022-03-02','DISA','technical','For password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash.','IA-05(01)(d)','N/A','Determine if for password-based authentication, passwords are stored using an approved salted key derivation function, preferably using a keyed hash.'),
('004063','draft','2022-03-02','DISA','technical','For password-based authentication, require immediate selection of a new password upon account recovery.','IA-05(01)(e)','N/A','Determine if for password-based authentication, immediate selection of a new password is required upon account recovery.'),
('004064','draft','2022-03-02','DISA','technical','For password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters.','IA-05(01)(f)','N/A','Determine if for password-based authentication, user selection of long passwords and passphrases is allowed, including spaces and all printable characters.'),
('004065','draft','2022-03-02','DISA','technical','For password-based authentication, employ automated tools to assist the user in selecting strong password authenticators.','IA-05(01)(g)','N/A','Determine if for password-based authentication, automated tools are employed to assist the user in selecting strong password authenticators.'),
('004066','draft','2022-03-02','DISA','technical','For password-based authentication, enforce organization-defined composition and complexity rules.','IA-05(01)(h)','N/A','Determine if for password-based authentication, [IA-05(01)_ODP[02]; authenticator composition and complexity rules are defined] are enforced.'),
('004067','draft','2022-03-02','DISA','policy','Defines the composition and complexity rules to be enforced.','IA-05(01)(h)','N/A','Determine if for password-based authentication, [IA-05(01)_ODP[02]; authenticator composition and complexity rules are defined] are enforced.'),
('004068','draft','2022-03-02','DISA','technical','For public key-based authentication, implement a local cache of revocation data to support path discovery and validation.','IA-05(02)(b)(02)','N/A','Determine if when public key infrastructure (PKI) is used, a local cache of revocation data is implemented to support path discovery and validation.'),
('004069','draft','2022-03-02','DISA','policy','Ensure that the unencrypted static authenticators are not embedded in applications or other forms of static storage.','IA-05(07)','N/A','Determine if unencrypted static authenticators are not embedded in applications or other forms of static storage.'),
('004070','draft','2022-03-02','DISA','policy','Use organization-defined external organizations to federate credentials.','IA-05(09)','N/A','Determine if [IA-05(09)_ODP; external organizations to be used for federating credentials are defined] are used to federate credentials.'),
('004071','draft','2022-03-02','DISA','policy','Defines the external organizations used to federate credentials.','IA-05(09)','N/A','Determine if [IA-05(09)_ODP; external organizations to be used for federating credentials are defined] are used to federate credentials.'),
('004072','draft','2022-03-02','DISA','technical','Defines the binding rules for binding identities and authenticators.','IA-05(10)','N/A','Determine if identities and authenticators are dynamically bound using [IA-05(10)_ODP; rules for dynamically binding identities and authenticators are defined].'),
('004073','draft','2022-03-02','DISA','policy','Use only General Services Administration-approved and validated products and services for identity, credential, and access management.','IA-05(15)','N/A','Determine if only General Services Administration-approved products and services are used for identity, credential, and access management.'),
('004074','draft','2022-03-02','DISA','policy','Require that the issuance of organization-defined types of and/or specific authenticators be conducted in person or by a trusted external party before the organization-defined registration authority with authorization by organization-defined personnel or roles.','IA-05(16)','N/A','Determine if the issuance of [IA-05(16)_ODP[01]; types of and/or specific authenticators to be issued are defined] is required to be conducted [IA-05(16)_ODP[02]; one of the following PARAMETER VALUES is selected: {in person; by a trusted external party}] before [IA-05(16)_ODP[03]; the registration authority that issues authenticators is defined] with authorization by [IA-05(16)_ODP[04]; the personnel or roles who authorize the issuance of authenticators are defined].'),
('004075','draft','2022-03-02','DISA','policy','Defines types of and/or specific authenticators to be conducted in person or by a trusted external party before the organization-defined registration authority.','IA-05(16)','N/A','Determine if the issuance of [IA-05(16)_ODP[01]; types of and/or specific authenticators to be issued are defined] is required to be conducted [IA-05(16)_ODP[02]; one of the following PARAMETER VALUES is selected: {in person; by a trusted external party}] before [IA-05(16)_ODP[03]; the registration authority that issues authenticators is defined] with authorization by [IA-05(16)_ODP[04]; the personnel or roles who authorize the issuance of authenticators are defined].'),
('004076','draft','2022-03-02','DISA','policy','Defines the registration authority who conducts the issuance of organization-defined types of and/or specific authenticators.','IA-05(16)','N/A','Determine if the issuance of [IA-05(16)_ODP[01]; types of and/or specific authenticators to be issued are defined] is required to be conducted [IA-05(16)_ODP[02]; one of the following PARAMETER VALUES is selected: {in person; by a trusted external party}] before [IA-05(16)_ODP[03]; the registration authority that issues authenticators is defined] with authorization by [IA-05(16)_ODP[04]; the personnel or roles who authorize the issuance of authenticators are defined].'),
('004077','draft','2022-03-02','DISA','policy','Defines the personnel or roles who authorize the issuance of organization-defined types of and/or specific authenticators.','IA-05(16)','N/A','Determine if the issuance of [IA-05(16)_ODP[01]; types of and/or specific authenticators to be issued are defined] is required to be conducted [IA-05(16)_ODP[02]; one of the following PARAMETER VALUES is selected: {in person; by a trusted external party}] before [IA-05(16)_ODP[03]; the registration authority that issues authenticators is defined] with authorization by [IA-05(16)_ODP[04]; the personnel or roles who authorize the issuance of authenticators are defined].'),
('004078','draft','2022-03-02','DISA','technical','Employ presentation attack detection mechanisms for biometric-based authentication.','IA-05(17)','N/A','Determine if presentation attack detection mechanisms are employed for biometric-based authentication.'),
('004079','draft','2022-03-02','DISA','technical','Employ organization-defined password managers to generate and manage passwords.','IA-05(18)(a)','N/A','Determine if [IA-05(18)_ODP[01]; password managers employed for generating and managing passwords are defined] are employed to generate and manage passwords.'),
('004080','draft','2022-03-02','DISA','technical','Defines the password managers employed to generate and manage passwords.',NULL,'N/A',NULL),
('004081','draft','2022-03-02','DISA','technical','Protect the passwords using organization-defined controls.','IA-05(18)(b)','N/A','Determine if the passwords are protected using [IA-05(18)_ODP[02]; controls for protecting passwords are defined].'),
('004082','draft','2022-03-02','DISA','technical','Defines the controls for protecting the passwords.','IA-05(18)(b)','N/A','Determine if the passwords are protected using [IA-05(18)_ODP[02]; controls for protecting passwords are defined].'),
('004083','draft','2022-03-02','DISA','technical','Accept only external credentials that are NIST compliant.','IA-08(02)(a)','N/A','Determine if only external authenticators that are NIST-compliant are accepted.'),
('004084','draft','2022-03-02','DISA','technical','Document and maintain a list of accepted external authenticators.','IA-08(02)(b)','N/A','Determine if: - a list of accepted external authenticators is documented. - a list of accepted external authenticators is maintained.'),
('004085','draft','2022-03-02','DISA','technical','Conform to organization-defined identity management profiles for identity management.','IA-08(04)','N/A','Determine if there is conformance with [IA-08(04)_ODP; identity management profiles are defined] for identity management.'),
('004086','draft','2022-03-02','DISA','technical','Defines the identity management profiles for conforming to the profiles for identity management.','IA-08(04)','N/A','Determine if there is conformance with [IA-08(04)_ODP; identity management profiles are defined] for identity management.'),
('004087','draft','2022-03-02','DISA','technical','Defines the policy for accepting and verifying federated or PKI credentials.','IA-08(05)','N/A','Determine if: - federated or PKI credentials that meet [IA-08(05)_ODP; a policy for using federated or PKI credentials is defined] are accepted. - federated or PKI credentials that meet [IA-08(05)_ODP; a policy for using federated or PKI credentials is defined] are verified.'),
('004088','draft','2022-03-02','DISA','policy','Implement organization-defined measures to disassociate user attributes or identifier assertion relationships among individuals.','IA-08(06)','N/A','Determine if [IA-08(06)_ODP; disassociability measures are defined] to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties are implemented.'),
('004089','draft','2022-03-02','DISA','policy','Implement organization-defined measures to disassociate user attributes or identifier assertion relationships among credential service providers.','IA-08(06)','N/A','Determine if [IA-08(06)_ODP; disassociability measures are defined] to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties are implemented.'),
('004090','draft','2022-03-02','DISA','policy','Implement organization-defined measures to disassociate user attributes or identifier assertion relationships among relying parties.','IA-05(18)(a)','N/A','Determine if [IA-05(18)_ODP[01]; password managers employed for generating and managing passwords are defined] are employed to generate and manage passwords.'),
('004091','draft','2022-03-02','DISA','policy','Defines the measures to be implemented to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties.',NULL,'N/A',NULL),
('004092','draft','2022-03-02','DISA','policy','Identity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards.','IA-12a.','N/A','Determine if users who require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines are identity proofed.'),
('004093','draft','2022-03-02','DISA','policy','Identity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable guidelines.','IA-12a.','N/A','Determine if users who require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines are identity proofed.'),
('004094','draft','2022-03-02','DISA','policy','Resolve user identities to a unique individual.','IA-12b.','N/A','Determine if user identities are resolved to a unique individual.'),
('004095','draft','2022-03-02','DISA','policy','Collect identity evidence.','IA-12c.','N/A','Determine if: - identity evidence is collected. - identity evidence is validated. - identity evidence is verified.'),
('004096','draft','2022-03-02','DISA','policy','Validate identity evidence.',NULL,'N/A',NULL),
('004097','draft','2022-03-02','DISA','policy','Verify identity evidence.','IA-12c.','N/A','Determine if: - identity evidence is collected. - identity evidence is validated. - identity evidence is verified.'),
('004098','draft','2022-03-02','DISA','policy','Require that the registration process to receive an account for logical access includes supervisor or sponsor authorization.','IA-12c.','N/A','Determine if: - identity evidence is collected. - identity evidence is validated. - identity evidence is verified.'),
('004099','draft','2022-03-02','DISA','policy','Require evidence of individual identification be presented to the registration authority.','IA-12(02)','N/A','Determine if evidence of individual identification is presented to the registration authority.'),
('004100','draft','2022-03-02','DISA','policy','Require that the presented identity evidence be validated through organizational defined methods of validation.','IA-12(03)','N/A','Determine if the presented identity evidence is validated and verified through [IA-12(03)_ODP; methods of validation and verification of identity evidence are defined].'),
('004101','draft','2022-03-02','DISA','policy','Require that the presented identity evidence be verified through organizational defined methods of verification.','IA-12(03)','N/A','Determine if the presented identity evidence is validated and verified through [IA-12(03)_ODP; methods of validation and verification of identity evidence are defined].'),
('004102','draft','2022-03-02','DISA','policy','Defines the methods of validation required for presenting identity evidence.','IA-12(03)','N/A','Determine if the presented identity evidence is validated and verified through [IA-12(03)_ODP; methods of validation and verification of identity evidence are defined].'),
('004103','draft','2022-03-02','DISA','policy','Defines the methods of verification required for presenting identity evidence.','IA-12(03)','N/A','Determine if the presented identity evidence is validated and verified through [IA-12(03)_ODP; methods of validation and verification of identity evidence are defined].'),
('004104','draft','2022-03-02','DISA','policy','Require that the validation of identity evidence be conducted in person before a designated registration authority.','IA-12(04)','N/A','Determine if the validation and verification of identity evidence is conducted in person before a designated registration authority.'),
('004105','draft','2022-03-02','DISA','policy','Require that the verification of identity evidence be conducted in person before a designated registration authority.','IA-12(04)','N/A','Determine if the validation and verification of identity evidence is conducted in person before a designated registration authority.'),
('004106','draft','2022-03-02','DISA','policy','Require that a registration code or notice of proofing be delivered through an out-of-band channel to verify the users address (physical or digital) of record.','IA-12(05)','N/A','Determine if a [IA-12(05)_ODP; one of the following PARAMETER VALUES is selected: {registration code; notice of proofing}] is delivered through an out-of-band channel to verify the user''s address (physical or digital) of record.'),
('004107','draft','2022-03-03','DISA','policy','Accept externally-proofed identities at an organization-defined identity assurance level.','IA-12(06)','N/A','Determine if externally proofed identities are accepted [IA-12(06)_ODP; an identity assurance level for accepting externally proofed identities is defined].'),
('004108','draft','2022-03-03','DISA','policy','Defines the identity assurance level by accepting externally-proofed identities.','IA-12(06)','N/A','Determine if externally proofed identities are accepted [IA-12(06)_ODP; an identity assurance level for accepting externally proofed identities is defined].'),
('004109','draft','2022-03-03','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level incident response policy that is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.','IR-01a.01(b)','N/A','Determine if the [IR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] incident response policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004110','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the incident response policy.','IR-01b.','N/A','Determine if the [IR-01_ODP[04]; an official to manage the incident response policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the incident response policy and procedures.'),
('004111','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the incident response procedures.','IR-01b.','N/A','Determine if the [IR-01_ODP[04]; an official to manage the incident response policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the incident response policy and procedures.'),
('004112','draft','2022-03-03','DISA','policy','Defines the official designated to manage the incident response policy and procedures.','IR-01b.','N/A','Determine if the [IR-01_ODP[04]; an official to manage the incident response policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the incident response policy and procedures.'),
('004113','draft','2022-03-03','DISA','policy','Review and update the current incident response policy following organization-defined events.','IR-01c.01','N/A','Determine if: - the current incident response policy is reviewed and updated [IR-01_ODP[05]; the frequency at which the current incident response policy is reviewed and updated is defined]. - the current incident response policy is reviewed and updated following [IR-01_ODP[06]; events that would require the current incident response policy to be reviewed and updated are defined].'),
('004114','draft','2022-03-03','DISA','policy','Defines the events for reviewing and updating the current incident response policy.','IR-01c.01','N/A','Determine if: - the current incident response policy is reviewed and updated [IR-01_ODP[05]; the frequency at which the current incident response policy is reviewed and updated is defined]. - the current incident response policy is reviewed and updated following [IR-01_ODP[06]; events that would require the current incident response policy to be reviewed and updated are defined].'),
('004115','draft','2022-03-03','DISA','policy','Review and update the current incident response procedures following organization-defined events.','IR-01c.02','N/A','Determine if: - the current incident response procedures are reviewed and updated [IR-01_ODP[07]; the frequency at which the current incident response procedures are reviewed and updated is defined]. - the current incident response procedures are reviewed and updated following [IR-01_ODP[08]; events that would require the incident response procedures to be reviewed and updated are defined].'),
('004116','draft','2022-03-03','DISA','policy','Defines the events for reviewing and updating the current incident response procedures.','IR-01c.02','N/A','Determine if: - the current incident response procedures are reviewed and updated [IR-01_ODP[07]; the frequency at which the current incident response procedures are reviewed and updated is defined]. - the current incident response procedures are reviewed and updated following [IR-01_ODP[08]; events that would require the incident response procedures to be reviewed and updated are defined].'),
('004117','draft','2022-03-03','DISA','policy','Defines the automated mechanisms to provide an incident response training environment.','IR-02(02)','N/A','Determine if an incident response training environment is provided using [IR-02(02)_ODP; automated mechanisms used in an incident response training environment are defined].'),
('004118','draft','2022-03-03','DISA','policy','Provide incident response training on how to identify and respond to a breach, including the organization''s process for reporting a breach.','IR-02(03)','N/A','Determine if: - incident response training on how to identify and respond to a breach is provided. - incident response training on the organization''s process for reporting a breach is provided.'),
('004119','draft','2022-03-03','DISA','policy','Defines the automated mechanisms to test the incident response capability.','IR-03(01)','N/A','Determine if the incident response capability is tested using [IR-03(01)_ODP; automated mechanisms used to test the incident response capability are defined].'),
('004120','draft','2022-03-03','DISA','policy','Use qualitative data from testing to determine the effectiveness of incident response processes.','IR-03(03)(a)','N/A','Determine if: - qualitative data from testing are used to determine the effectiveness of incident response processes. - quantitative data from testing are used to determine the effectiveness of incident response processes.'),
('004121','draft','2022-03-03','DISA','policy','Use quantitative data from testing to determine the effectiveness of incident response processes.','IR-03(03)(a)','N/A','Determine if: - qualitative data from testing are used to determine the effectiveness of incident response processes. - quantitative data from testing are used to determine the effectiveness of incident response processes.'),
('004122','draft','2022-03-03','DISA','policy','Use qualitative data from testing to continuously improve incident response processes.','IR-03(03)(b)','N/A','Determine if: - qualitative data from testing are used to continuously improve incident response processes. - quantitative data from testing are used to continuously improve incident response processes.'),
('004123','draft','2022-03-03','DISA','policy','Use quantitative data from testing to continuously improve incident response processes.','IR-03(03)(b)','N/A','Determine if: - qualitative data from testing are used to continuously improve incident response processes. - quantitative data from testing are used to continuously improve incident response processes.'),
('004124','draft','2022-03-03','DISA','policy','Use qualitative data from testing to provide incident response measures and metrics that are accurate.','IR-03(03)(c)','N/A','Determine if: - qualitative data from testing are used to provide incident response measures and metrics that are accurate. - quantitative data from testing are used to provide incident response measures and metrics that are accurate. - qualitative data from testing are used to provide incident response measures and metrics that are consistent. - quantitative data from testing are used to provide incident response measures and metrics that are consistent. - qualitative data from testing are used to provide incident response measures and metrics in a reproducible format. - quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.'),
('004125','draft','2022-03-03','DISA','policy','Use quantitative data from testing to provide incident response measures and metrics that are accurate.','IR-03(03)(c)','N/A','Determine if: - qualitative data from testing are used to provide incident response measures and metrics that are accurate. - quantitative data from testing are used to provide incident response measures and metrics that are accurate. - qualitative data from testing are used to provide incident response measures and metrics that are consistent. - quantitative data from testing are used to provide incident response measures and metrics that are consistent. - qualitative data from testing are used to provide incident response measures and metrics in a reproducible format. - quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.'),
('004126','draft','2022-03-03','DISA','policy','Use qualitative data from testing to provide incident response measures and metrics that are consistent.','IR-03(03)(c)','N/A','Determine if: - qualitative data from testing are used to provide incident response measures and metrics that are accurate. - quantitative data from testing are used to provide incident response measures and metrics that are accurate. - qualitative data from testing are used to provide incident response measures and metrics that are consistent. - quantitative data from testing are used to provide incident response measures and metrics that are consistent. - qualitative data from testing are used to provide incident response measures and metrics in a reproducible format. - quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.'),
('004127','draft','2022-03-03','DISA','policy','Use quantitative data from testing to provide incident response measures and metrics that are consistent.','IR-03(03)(c)','N/A','Determine if: - qualitative data from testing are used to provide incident response measures and metrics that are accurate. - quantitative data from testing are used to provide incident response measures and metrics that are accurate. - qualitative data from testing are used to provide incident response measures and metrics that are consistent. - quantitative data from testing are used to provide incident response measures and metrics that are consistent. - qualitative data from testing are used to provide incident response measures and metrics in a reproducible format. - quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.'),
('004128','draft','2022-03-03','DISA','policy','Use qualitative data from testing to provide incident response measures and metrics that are in a reproducible format.','IR-03(03)(c)','N/A','Determine if: - qualitative data from testing are used to provide incident response measures and metrics that are accurate. - quantitative data from testing are used to provide incident response measures and metrics that are accurate. - qualitative data from testing are used to provide incident response measures and metrics that are consistent. - quantitative data from testing are used to provide incident response measures and metrics that are consistent. - qualitative data from testing are used to provide incident response measures and metrics in a reproducible format. - quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.'),
('004129','draft','2022-03-03','DISA','policy','Use quantitative data from testing to provide incident response measures and metrics that are in a reproducible format.','IR-03(03)(c)','N/A','Determine if: - qualitative data from testing are used to provide incident response measures and metrics that are accurate. - quantitative data from testing are used to provide incident response measures and metrics that are accurate. - qualitative data from testing are used to provide incident response measures and metrics that are consistent. - quantitative data from testing are used to provide incident response measures and metrics that are consistent. - qualitative data from testing are used to provide incident response measures and metrics in a reproducible format. - quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.'),
('004130','draft','2022-03-03','DISA','policy','Incorporate lessons learned from ongoing incident handling activities into incident response procedures.','IR-04c.','N/A','Determine if: - lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing. - the changes resulting from the incorporated lessons learned are implemented accordingly.'),
('004131','draft','2022-03-03','DISA','policy','Incorporate lessons learned from ongoing incident handling activities into incident response training.','IR-04c.','N/A','Determine if: - lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing. - the changes resulting from the incorporated lessons learned are implemented accordingly.'),
('004132','draft','2022-03-03','DISA','policy','Incorporate lessons learned from ongoing incident handling activities into incident response testing.','IR-04c.','N/A','Determine if: - lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing. - the changes resulting from the incorporated lessons learned are implemented accordingly.'),
('004133','draft','2022-03-03','DISA','policy','Ensure the rigor of incident handling activities are comparable and predictable across the organization.','IR-04d.','N/A','Determine if: - the rigor of incident handling activities is comparable and predictable across the organization. - the intensity of incident handling activities is comparable and predictable across the organization. - the scope of incident handling activities is comparable and predictable across the organization. - the results of incident handling activities are comparable and predictable across the organization.'),
('004134','draft','2022-03-03','DISA','policy','Ensure the intensity of incident handling activities are comparable and predictable across the organization.','IR-04d.','N/A','Determine if: - the rigor of incident handling activities is comparable and predictable across the organization. - the intensity of incident handling activities is comparable and predictable across the organization. - the scope of incident handling activities is comparable and predictable across the organization. - the results of incident handling activities are comparable and predictable across the organization.'),
('004135','draft','2022-03-03','DISA','policy','Ensure the scope of incident handling activities are comparable and predictable across the organization.','IR-04d.','N/A','Determine if: - the rigor of incident handling activities is comparable and predictable across the organization. - the intensity of incident handling activities is comparable and predictable across the organization. - the scope of incident handling activities is comparable and predictable across the organization. - the results of incident handling activities are comparable and predictable across the organization.'),
('004136','draft','2022-03-03','DISA','policy','Ensure the results of incident handling activities are comparable and predictable across the organization.','IR-04d.','N/A','Determine if: - the rigor of incident handling activities is comparable and predictable across the organization. - the intensity of incident handling activities is comparable and predictable across the organization. - the scope of incident handling activities is comparable and predictable across the organization. - the results of incident handling activities are comparable and predictable across the organization.'),
('004137','draft','2022-03-03','DISA','policy','Defines the automated mechanisms for supporting the incident handling process.','IR-04(01)','N/A','Determine if the incident handling process is supported using [IR-04(01)_ODP; automated mechanisms used to support the incident handling process are defined].'),
('004138','draft','2022-03-03','DISA','policy','Defines the types of dynamic reconfiguration for system components.','IR-04(02)','N/A','Determine if [IR-04(02)_ODP[01]; types of dynamic reconfiguration for system components are defined] for [IR-04(02)_ODP[02]; system components that require dynamic reconfiguration are defined] are included as part of the incident response capability.'),
('004139','draft','2022-03-03','DISA','policy','Defines the classes of incidents to identify actions in response to those incidents.','IR-04(03)','N/A','Determine if: - [IR-04(03)_ODP[01]; classes of incidents requiring an organization-defined action (defined in IR-04(03)_ODP[02]) to be taken are defined] are identified. - [IR-04(03)_ODP[02]; actions to be taken in response to organization-defined classes of incidents are defined] are taken in response to those incidents (defined in IR-04(03)_ODP[01]) to ensure the continuation of organizational mission and business functions.'),
('004140','draft','2022-03-03','DISA','policy','Defines the actions to take in response to organization-defined classes of incidents to ensure continuation of organizational mission and business functions.','IR-04(03)','N/A','Determine if: - [IR-04(03)_ODP[01]; classes of incidents requiring an organization-defined action (defined in IR-04(03)_ODP[02]) to be taken are defined] are identified. - [IR-04(03)_ODP[02]; actions to be taken in response to organization-defined classes of incidents are defined] are taken in response to those incidents (defined in IR-04(03)_ODP[01]) to ensure the continuation of organizational mission and business functions.'),
('004141','draft','2022-03-03','DISA','policy','Coordinate an incident handling capability for insider threats that includes organization-defined entities.','IR-04(07)','N/A','Determine if: - an incident handling capability is coordinated for insider threats. - the coordinated incident handling capability includes [IR-04(07)_ODP; entities that require coordination for an incident handling capability for insider threats are defined].'),
('004142','draft','2022-03-03','DISA','policy','Defines the organizational entities for coordinating an incident handling capability for insider threats.','IR-04(07)','N/A','Determine if: - an incident handling capability is coordinated for insider threats. - the coordinated incident handling capability includes [IR-04(07)_ODP; entities that require coordination for an incident handling capability for insider threats are defined].'),
('004143','draft','2022-03-03','DISA','policy','Establish and maintain an integrated incident response team that can be deployed to any location identified by the organization in an organization-defined time period.','IR-04(11)','N/A','Determine if: - an integrated incident response team is established and maintained. - the integrated incident response team can be deployed to any location identified by the organization in [IR-04(11)_ODP; the time period within which an integrated incident response team can be deployed is defined].'),
('004144','draft','2022-03-03','DISA','policy','Defines the time period for establishing and maintaining an integrated incident response team that can be deployed to any location identified by the organization.','IR-04(11)','N/A','Determine if: - an integrated incident response team is established and maintained. - the integrated incident response team can be deployed to any location identified by the organization in [IR-04(11)_ODP; the time period within which an integrated incident response team can be deployed is defined].'),
('004145','draft','2022-03-03','DISA','policy','Analyze malicious code and/or other residual artifacts remaining in the system after the incident.','IR-04(12)','N/A','Determine if: - malicious code remaining in the system is analyzed after the incident. - other residual artifacts remaining in the system (if any) are analyzed after the incident.'),
('004146','draft','2022-03-03','DISA','policy','Analyze anomalous or suspected adversarial behavior in or related to organization-defined environments or resources.','IR-04(13)','N/A','Determine if anomalous or suspected adversarial behavior in or related to [IR-04(13)_ODP; environments or resources which may contain or may be related to anomalous or suspected adversarial behavior are defined] are analyzed.'),
('004147','draft','2022-03-03','DISA','policy','Defines the environments or resources for analyzing anomalous or suspected adversarial behavior.','IR-04(13)','N/A','Determine if anomalous or suspected adversarial behavior in or related to [IR-04(13)_ODP; environments or resources which may contain or may be related to anomalous or suspected adversarial behavior are defined] are analyzed.'),
('004148','draft','2022-03-03','DISA','policy','Establish and maintain a security operations center.','IR-04(14)','N/A','Determine if: - a security operations center is established. - a security operations center is maintained.'),
('004149','draft','2022-03-03','DISA','policy','Manage public relations associated with an incident.','IR-04(15)(a)','N/A','Determine if public relations associated with an incident are managed.'),
('004150','draft','2022-03-03','DISA','policy','Employ measures to repair the reputation of the organization.','IR-04(15)(b)','N/A','Determine if measures are employed to repair the reputation of the organization.'),
('004151','draft','2022-03-03','DISA','policy','Track incidents using organization-defined automated mechanisms.','IR-05(01)','N/A','Determine if: - incidents are tracked using [IR-05(01)_ODP[01]; automated mechanisms used to track incidents are defined]. - incident information is collected using [IR-05(01)_ODP[02]; automated mechanisms used to collect incident information are defined]. - incident information is analyzed using [IR-05(01)_ODP[03]; automated mechanisms used to analyze incident information are defined].'),
('004152','draft','2022-03-03','DISA','policy','Collect incident information using organization-defined automated mechanisms.','IR-05(01)','N/A','Determine if: - incidents are tracked using [IR-05(01)_ODP[01]; automated mechanisms used to track incidents are defined]. - incident information is collected using [IR-05(01)_ODP[02]; automated mechanisms used to collect incident information are defined]. - incident information is analyzed using [IR-05(01)_ODP[03]; automated mechanisms used to analyze incident information are defined].'),
('004153','draft','2022-03-03','DISA','policy','Analyze incident information using organization-defined automated mechanisms.','IR-05(01)','N/A','Determine if: - incidents are tracked using [IR-05(01)_ODP[01]; automated mechanisms used to track incidents are defined]. - incident information is collected using [IR-05(01)_ODP[02]; automated mechanisms used to collect incident information are defined]. - incident information is analyzed using [IR-05(01)_ODP[03]; automated mechanisms used to analyze incident information are defined].'),
('004154','draft','2022-03-03','DISA','policy','Defines the automated mechanisms to track, collect, and analyze incident information.','IR-05(01)','N/A','Determine if: - incidents are tracked using [IR-05(01)_ODP[01]; automated mechanisms used to track incidents are defined]. - incident information is collected using [IR-05(01)_ODP[02]; automated mechanisms used to collect incident information are defined]. - incident information is analyzed using [IR-05(01)_ODP[03]; automated mechanisms used to analyze incident information are defined].'),
('004155','draft','2022-03-03','DISA','policy','Defines the automated mechanisms for reporting incidents.','IR-06(01)','N/A','Determine if incidents are reported using [IR-06(01)_ODP; automated mechanisms used for reporting incidents are defined].'),
('004156','draft','2022-03-03','DISA','policy','Provide incident information to the provider of the product or service.','IR-06(03)','N/A','Determine if incident information is provided to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.'),
('004157','draft','2022-03-03','DISA','policy','Develop an incident response plan that addresses the sharing of incident information.','IR-08a.08','N/A','Determine if an incident response plan is developed that addresses the sharing of incident information.'),
('004158','draft','2022-03-03','DISA','policy','Defines the frequency organization-defined personnel or roles will review and approve the incident response plan.','IR-08a.09','N/A','Determine if an incident response plan is developed that is reviewed and approved by [IR-08_ODP[01]; personnel or roles that review and approve the incident response plan is/are identified] [IR-08_ODP[02]; the frequency at which to review and approve the incident response plan is defined].'),
('004159','draft','2022-03-03','DISA','policy','Develop an incident response plan that explicitly designates responsibility for incident response to organization-defined entities, personnel, or roles.','IR-08a.10','N/A','Determine if an incident response plan is developed that explicitly designates responsibility for incident response to [IR-08_ODP[03]; entities, personnel, or roles with designated responsibility for incident response are defined].'),
('004160','draft','2022-03-03','DISA','policy','Include a process to determine if notice to individuals or other organizations, including oversight organizations, is needed, in the Incident Response Plan for breaches involving Personally Identifiable Information.','IR-08(01)(a)','N/A','Determine if the incident response plan for breaches involving personally identifiable information includes a process to determine if notice to individuals or other organizations, including oversight organizations, is needed.'),
('004161','draft','2022-03-03','DISA','policy','Include an assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms in the Incident Response Plan for breaches involving Personally Identifiable Information.','IR-08(01)(b)','N/A','Determine if the incident response plan for breaches involving personally identifiable information includes an assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms.'),
('004162','draft','2022-03-03','DISA','policy','Include identification of applicable privacy requirements in the Incident Response Plan for breaches involving Personally Identifiable Information.','IR-08(01)(c)','N/A','Determine if the incident response plan for breaches involving personally identifiable information includes the identification of applicable privacy requirements.'),
('004163','draft','2022-03-03','DISA','policy','Respond to information spills by assigning organization-defined personnel or roles with responsibility for responding to information spills.','IR-09a.','N/A','Determine if [IR-09_ODP[01]; personnel or roles assigned the responsibility for responding to information spills is/are defined] is/are assigned the responsibility to respond to information spills.'),
('004164','draft','2022-03-03','DISA','policy','Defines the personnel or roles who will respond to information spills.','IR-09a.','N/A','Determine if [IR-09_ODP[01]; personnel or roles assigned the responsibility for responding to information spills is/are defined] is/are assigned the responsibility to respond to information spills.'),
('004165','draft','2022-03-03','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level maintenance policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','MA-01a.01(b)','N/A','Determine if the [MA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] maintenance policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004166','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the development, documentation, and dissemination of the maintenance policy.','MA-01b.','N/A','Determine if the [MA-01_ODP[04]; an official to manage the maintenance policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the maintenance policy and procedures.'),
('004167','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the development, documentation, and dissemination of the maintenance procedures.','MA-01b.','N/A','Determine if the [MA-01_ODP[04]; an official to manage the maintenance policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the maintenance policy and procedures.'),
('004168','draft','2022-03-03','DISA','policy','Defines the official who will manage the development, documentation, and dissemination of the maintenance policy.','MA-01b.','N/A','Determine if the [MA-01_ODP[04]; an official to manage the maintenance policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the maintenance policy and procedures.'),
('004169','draft','2022-03-03','DISA','policy','Defines the official who will manage the development, documentation, and dissemination of the maintenance procedures.','MA-01b.','N/A','Determine if the [MA-01_ODP[04]; an official to manage the maintenance policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the maintenance policy and procedures.'),
('004170','draft','2022-03-03','DISA','policy','Review and update the current maintenance policy following organization-defined events.','MA-01c.01','N/A','Determine if: - the current maintenance policy is reviewed and updated [MA-01_ODP[05]; the frequency with which the current maintenance policy is reviewed and updated is defined]. - the current maintenance policy is reviewed and updated following [MA-01_ODP[06]; events that would require the current maintenance policy to be reviewed and updated are defined].'),
('004171','draft','2022-03-03','DISA','policy','Defines the events following reviewing and updating the current maintenance policy.','MA-01c.01','N/A','Determine if: - the current maintenance policy is reviewed and updated [MA-01_ODP[05]; the frequency with which the current maintenance policy is reviewed and updated is defined]. - the current maintenance policy is reviewed and updated following [MA-01_ODP[06]; events that would require the current maintenance policy to be reviewed and updated are defined].'),
('004172','draft','2022-03-03','DISA','policy','Review and update the current maintenance procedures following organization-defined events.','MA-01c.02','N/A','Determine if: - the current maintenance procedures are reviewed and updated [MA-01_ODP[07]; the frequency with which the current maintenance procedures are reviewed and updated is defined]. - the current maintenance procedures are reviewed and updated following [MA-01_ODP[08]; events that would require the maintenance procedures to be reviewed and updated are defined].'),
('004173','draft','2022-03-03','DISA','policy','Defines the events following reviewing and updating the current maintenance procedures.','MA-01c.02','N/A','Determine if: - the current maintenance procedures are reviewed and updated [MA-01_ODP[07]; the frequency with which the current maintenance procedures are reviewed and updated is defined]. - the current maintenance procedures are reviewed and updated following [MA-01_ODP[08]; events that would require the maintenance procedures to be reviewed and updated are defined].'),
('004174','draft','2022-03-03','DISA','policy','Schedule replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('004175','draft','2022-03-03','DISA','policy','Document replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('004176','draft','2022-03-03','DISA','policy','Review records of replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements.','MA-02a.','N/A','Determine if: - maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements. - maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements. - records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements.'),
('004177','draft','2022-03-03','DISA','policy','Approve all maintenance activities, whether performed on site or remotely.','MA-02b.','N/A','Determine if: - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are approved. - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are monitored.'),
('004178','draft','2022-03-03','DISA','policy','Monitor all maintenance activities, whether performed on site or remotely.','MA-02b.','N/A','Determine if: - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are approved. - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are monitored.'),
('004179','draft','2022-03-03','DISA','policy','Approve all maintenance activities, whether the system or system components are serviced on site or removed to another location.','MA-02b.','N/A','Determine if: - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are approved. - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are monitored.'),
('004180','draft','2022-03-03','DISA','policy','Monitor all maintenance activities, whether the system or system components are serviced on site or removed to another location.','MA-02b.','N/A','Determine if: - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are approved. - all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are monitored.'),
('004181','draft','2022-03-03','DISA','policy','Defines the information to be removed from associated media.','MA-02d.','N/A','Determine if equipment is sanitized to remove [MA-02_ODP[02]; information to be removed from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement is defined] from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement.'),
('004182','draft','2022-03-03','DISA','policy','Schedule maintenance, repair, and replacement actions for the system using organization-defined automated mechanisms.','MA-02(02)(a)','N/A','Determine if: - [MA-02(02)_ODP[01]; automated mechanisms used to schedule maintenance, repair, and replacement actions for the system are defined] are used to schedule maintenance, repair, and replacement actions for the system. - [MA-02(02)_ODP[02]; automated mechanisms used to conduct maintenance, repair, and replacement actions for the system are defined] are used to conduct maintenance, repair, and replacement actions for the system. - [MA-02(02)_ODP[03]; automated mechanisms used to document maintenance, repair, and replacement actions for the system are defined] are used to document maintenance, repair, and replacement actions for the system.'),
('004183','draft','2022-03-03','DISA','policy','Conduct maintenance, repair, and replacement actions for the system using organization-defined automated mechanisms.','MA-02(02)(a)','N/A','Determine if: - [MA-02(02)_ODP[01]; automated mechanisms used to schedule maintenance, repair, and replacement actions for the system are defined] are used to schedule maintenance, repair, and replacement actions for the system. - [MA-02(02)_ODP[02]; automated mechanisms used to conduct maintenance, repair, and replacement actions for the system are defined] are used to conduct maintenance, repair, and replacement actions for the system. - [MA-02(02)_ODP[03]; automated mechanisms used to document maintenance, repair, and replacement actions for the system are defined] are used to document maintenance, repair, and replacement actions for the system.'),
('004184','draft','2022-03-03','DISA','policy','Document maintenance, repair, and replacement actions for the system using organization-defined automated mechanisms.','MA-02(02)(a)','N/A','Determine if: - [MA-02(02)_ODP[01]; automated mechanisms used to schedule maintenance, repair, and replacement actions for the system are defined] are used to schedule maintenance, repair, and replacement actions for the system. - [MA-02(02)_ODP[02]; automated mechanisms used to conduct maintenance, repair, and replacement actions for the system are defined] are used to conduct maintenance, repair, and replacement actions for the system. - [MA-02(02)_ODP[03]; automated mechanisms used to document maintenance, repair, and replacement actions for the system are defined] are used to document maintenance, repair, and replacement actions for the system.'),
('004185','draft','2022-03-03','DISA','policy','Produce up-to date, accurate, and complete records of all replacement actions requested, scheduled, in process, and completed.','MA-02(02)(b)','N/A','Determine if: - up-to date, accurate, and complete records of all maintenance actions requested, scheduled, in process, and completed are produced. - up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed are produced. - up-to date, accurate, and complete records of all replacement actions requested, scheduled, in process, and completed are produced.'),
('004186','draft','2022-03-03','DISA','policy','Review previously approved system maintenance tools on an organization-defined frequency.','MA-03b.','N/A','Determine if previously approved system maintenance tools are reviewed [MA-03_ODP frequency; frequency at which to review previously approved system maintenance tools is defined].'),
('004187','draft','2022-03-03','DISA','policy','Defines the frequency for reviewing previously approved system maintenance tools.','MA-03b.','N/A','Determine if previously approved system maintenance tools are reviewed [MA-03_ODP frequency; frequency at which to review previously approved system maintenance tools is defined].'),
('004188','draft','2022-03-03','DISA','policy','Monitor the use of maintenance tools that execute with increased privilege.','MA-03(05)','N/A','Determine if the use of maintenance tools that execute with increased privilege is monitored.'),
('004189','draft','2022-03-03','DISA','policy','Inspect the maintenance tools to ensure the latest software updates and patches are installed.','MA-03(06)','N/A','Determine if maintenance tools are inspected to ensure that the latest software updates and patches are installed.'),
('004190','draft','2022-03-03','DISA','policy','Terminate session when nonlocal maintenance is completed.','MA-04e.','N/A','Determine if: - session connections are terminated when nonlocal maintenance is completed. - network connections are terminated when nonlocal maintenance is completed.'),
('004191','draft','2022-03-03','DISA','policy','Terminate network connection when nonlocal maintenance is completed.','MA-04e.','N/A','Determine if: - session connections are terminated when nonlocal maintenance is completed. - network connections are terminated when nonlocal maintenance is completed.'),
('004192','draft','2022-03-03','DISA','technical','Protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths.','MA-04(04)(b)(02)','N/A','Determine if nonlocal maintenance sessions are protected by logically separated communication paths.'),
('004193','draft','2022-03-03','DISA','policy','Defines the cryptographic mechanisms for protecting the integrity and confidentiality of nonlocal maintenance and diagnostic communications.','MA-04(06)','N/A','Determine if: - [MA-04(06)_ODP; cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined] are implemented to protect the integrity of nonlocal maintenance and diagnostic communications. - [MA-04(06)_ODP; cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined] are implemented to protect the confidentiality of nonlocal maintenance and diagnostic communications.'),
('004194','draft','2022-03-03','DISA','policy','Develop organization-defined alternate controls in the event a system component cannot be sanitized, removed, or disconnected from the system.','MA-05(01)(b)','N/A','Determine if [MA-05(01)_ODP; alternate controls to be developed and implemented in the event that a system component cannot be sanitized, removed, or disconnected from the system are defined] are developed and implemented in the event that a system cannot be sanitized, removed, or disconnected from the system.'),
('004195','draft','2022-03-03','DISA','policy','Implement organization-defined alternate controls in the event a system component cannot be sanitized, removed, or disconnected from the system.','MA-05(01)(b)','N/A','Determine if [MA-05(01)_ODP; alternate controls to be developed and implemented in the event that a system component cannot be sanitized, removed, or disconnected from the system are defined] are developed and implemented in the event that a system cannot be sanitized, removed, or disconnected from the system.'),
('004196','draft','2022-03-03','DISA','policy','Defines alternate controls in the event a system component cannot be sanitized, removed, or disconnected from the system.','MA-05(01)(b)','N/A','Determine if [MA-05(01)_ODP; alternate controls to be developed and implemented in the event that a system component cannot be sanitized, removed, or disconnected from the system are defined] are developed and implemented in the event that a system cannot be sanitized, removed, or disconnected from the system.'),
('004197','draft','2022-03-03','DISA','policy','Defines the automated mechanisms for transferring predictive maintenance data to a maintenance system.','MA-06(03)','N/A','Determine if predictive maintenance data is transferred to a maintenance management system using [MA-06(03)_ODP; automated mechanisms used to transfer predictive maintenance data to a maintenance management system are defined].'),
('004198','draft','2022-03-03','DISA','policy','Restrict or prohibit field maintenance on organization-defined systems or system components to organization-defined trusted maintenance facilities.','MA-07','N/A','Determine if field maintenance on [MA-07_ODP[01]; systems or system components on which field maintenance is restricted or prohibited to trusted maintenance facilities are defined] are restricted or prohibited to [MA-07_ODP[02]; trusted maintenance facilities that are not restricted or prohibited from conducting field maintenance are defined].'),
('004199','draft','2022-03-03','DISA','policy','Defines the systems or system components which restrict or prohibit field maintenance.','MA-07','N/A','Determine if field maintenance on [MA-07_ODP[01]; systems or system components on which field maintenance is restricted or prohibited to trusted maintenance facilities are defined] are restricted or prohibited to [MA-07_ODP[02]; trusted maintenance facilities that are not restricted or prohibited from conducting field maintenance are defined].'),
('004200','draft','2022-03-03','DISA','policy','Defines the trusted maintenance facilities which the systems or system components restrict or prohibit field maintenance.','MA-07','N/A','Determine if field maintenance on [MA-07_ODP[01]; systems or system components on which field maintenance is restricted or prohibited to trusted maintenance facilities are defined] are restricted or prohibited to [MA-07_ODP[02]; trusted maintenance facilities that are not restricted or prohibited from conducting field maintenance are defined].'),
('004201','draft','2022-03-03','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level media protection policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','MP-01a.01(b)','N/A','Determine if the media protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004202','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the development and documentation of the media protection policy.','MP-01b.','N/A','Determine if the [MP-01_ODP[04]; an official to manage the media protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the media protection policy and procedures.'),
('004203','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the dissemination of the media protection policy.','MP-01b.','N/A','Determine if the [MP-01_ODP[04]; an official to manage the media protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the media protection policy and procedures.'),
('004204','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage development and documentation of the media protection procedures.','MP-01b.','N/A','Determine if the [MP-01_ODP[04]; an official to manage the media protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the media protection policy and procedures.'),
('004205','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage dissemination of the media protection procedures.','MP-01b.','N/A','Determine if the [MP-01_ODP[04]; an official to manage the media protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the media protection policy and procedures.'),
('004206','draft','2022-03-03','DISA','policy','Defines the official designated to manage the development, documentation, and dissemination of the media protection policy and procedures.','MP-01b.','N/A','Determine if the [MP-01_ODP[04]; an official to manage the media protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the media protection policy and procedures.'),
('004207','draft','2022-03-03','DISA','policy','Review and update the current media protection policy following organization-defined events.','MP-01c.01','N/A','Determine if: - the current media protection policy is reviewed and updated [MP-01_ODP[05]; the frequency with which the current media protection policy is reviewed and updated is defined]. - the current media protection policy is reviewed and updated following [MP-01_ODP[06]; events that would require the current media protection policy to be reviewed and updated are defined].'),
('004208','draft','2022-03-03','DISA','policy','Defines the events following reviewing and updating the current media policy.','MP-01c.01','N/A','Determine if: - the current media protection policy is reviewed and updated [MP-01_ODP[05]; the frequency with which the current media protection policy is reviewed and updated is defined]. - the current media protection policy is reviewed and updated following [MP-01_ODP[06]; events that would require the current media protection policy to be reviewed and updated are defined].'),
('004209','draft','2022-03-03','DISA','policy','Review and update the current media protection procedures following organization-defined events.','MP-01c.02','N/A','Determine if: - the current media protection procedures are reviewed and updated [MP-01_ODP[07]; the frequency with which the current media protection procedures are reviewed and updated is defined]. - the current media protection procedures are reviewed and updated following [MP-01_ODP[08]; events that would require media protection procedures to be reviewed and updated are defined].'),
('004210','draft','2022-03-03','DISA','policy','Defines the events following reviewing and updating the current media procedures.','MP-01c.02','N/A','Determine if: - the current media protection procedures are reviewed and updated [MP-01_ODP[07]; the frequency with which the current media protection procedures are reviewed and updated is defined]. - the current media protection procedures are reviewed and updated following [MP-01_ODP[08]; events that would require media protection procedures to be reviewed and updated are defined].'),
('004211','draft','2022-03-03','DISA','policy','Physically control and securely store organization-defined types of digital and/or non-digital media within organization-defined controlled areas.','MP-04a.','N/A','Determine if: - [MP-04_ODP[01]; types of digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[02]; types of non-digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[03]; types of digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[05]; controlled areas within which to securely store digital media are defined]. - [MP-04_ODP[04]; types of non-digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[06]; controlled areas within which to securely store non-digital media are defined].'),
('004212','draft','2022-03-03','DISA','policy','Securely store organization-defined types of digital and/or non-digital media within organization-defined controlled areas.','MP-04a.','N/A','Determine if: - [MP-04_ODP[01]; types of digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[02]; types of non-digital media to be physically controlled are defined (if selected)] are physically controlled. - [MP-04_ODP[03]; types of digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[05]; controlled areas within which to securely store digital media are defined]. - [MP-04_ODP[04]; types of non-digital media to be securely stored are defined (if selected)] are securely stored within [MP-04_ODP[06]; controlled areas within which to securely store non-digital media are defined].'),
('004213','draft','2022-03-03','DISA','policy','Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved equipment.','MP-04b.','N/A','Determine if system media types (defined in MP-04_ODP[01], MP-04_ODP[02], MP-04_ODP[03], MP-04_ODP[04]) are protected until the media are destroyed or sanitized using approved equipment, techniques, and procedures.'),
('004214','draft','2022-03-03','DISA','policy','Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved techniques.','MP-04b.','N/A','Determine if system media types (defined in MP-04_ODP[01], MP-04_ODP[02], MP-04_ODP[03], MP-04_ODP[04]) are protected until the media are destroyed or sanitized using approved equipment, techniques, and procedures.'),
('004215','draft','2022-03-03','DISA','policy','Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved procedures.','MP-04b.','N/A','Determine if system media types (defined in MP-04_ODP[01], MP-04_ODP[02], MP-04_ODP[03], MP-04_ODP[04]) are protected until the media are destroyed or sanitized using approved equipment, techniques, and procedures.'),
('004216','draft','2022-03-03','DISA','policy','Defines the automated mechanisms which restrict access to media storage areas and log access attempts and access granted.','MP-04(02)','N/A','Determine if: - access to media storage areas is restricted using [MP-04(02)_ODP[01]; automated mechanisms to restrict access to media storage areas are defined]. - access attempts to media storage areas are logged using [MP-04(02)_ODP[02]; automated mechanisms to log access attempts to media storage areas are defined]. - access granted to media storage areas is logged using [MP-04(02)_ODP[03]; automated mechanisms to log access granted to media storage areas are defined].'),
('004217','draft','2022-03-03','DISA','policy','Protect organization-defined types of system media during transport outside of controlled areas using organization-defined controls.','MP-05a.','N/A','Determine if: - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are protected during transport outside of controlled areas using [MP-05_ODP[02]; controls used to protect system media outside of controlled areas are defined]. - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are controlled during transport outside of controlled areas using [MP-05_ODP[03]; controls used to control system media outside of controlled areas are defined].'),
('004218','draft','2022-03-03','DISA','policy','Control organization-defined types of system media during transport outside of controlled areas using organization-defined controls.','MP-05a.','N/A','Determine if: - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are protected during transport outside of controlled areas using [MP-05_ODP[02]; controls used to protect system media outside of controlled areas are defined]. - [MP-05_ODP[01]; types of system media to protect and control during transport outside of controlled areas are defined] are controlled during transport outside of controlled areas using [MP-05_ODP[03]; controls used to control system media outside of controlled areas are defined].'),
('004219','draft','2022-03-03','DISA','policy','Test sanitization equipment in accordance with the organization-defined frequency to ensure that the intended sanitization is being achieved.','MP-06(02)','N/A','Determine if: - sanitization equipment is tested [MP-06(02)_ODP[01]; frequency with which to test sanitization equipment is defined] to ensure that the intended sanitization is being achieved. - sanitization procedures are tested [MP-06(02)_ODP[02]; frequency with which to test sanitization procedures is defined] to ensure that the intended sanitization is being achieved.'),
('004220','draft','2022-03-03','DISA','policy','Test sanitization procedures in accordance with the organization-defined frequency to ensure that the intended sanitization is being achieved.','MP-06(02)','N/A','Determine if: - sanitization equipment is tested [MP-06(02)_ODP[01]; frequency with which to test sanitization equipment is defined] to ensure that the intended sanitization is being achieved. - sanitization procedures are tested [MP-06(02)_ODP[02]; frequency with which to test sanitization procedures is defined] to ensure that the intended sanitization is being achieved.'),
('004221','draft','2022-03-03','DISA','policy','Establish an organization-defined system media downgrading process that includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information.','MP-08a.','N/A','Determine if: - a [MP-08_ODP[01]; a system media downgrading process is defined] is established. - the [MP-08_ODP[01]; a system media downgrading process is defined] includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information.'),
('004222','draft','2022-03-03','DISA','policy','Defines the system media downgrading process that includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information.','MP-08a.','N/A','Determine if: - a [MP-08_ODP[01]; a system media downgrading process is defined] is established. - the [MP-08_ODP[01]; a system media downgrading process is defined] includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information.'),
('004223','draft','2022-03-03','DISA','policy','Verify that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed.','MP-08b.','N/A','Determine if: - there is verification that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed. - there is verification that the system media downgrading process is commensurate with the access authorizations of the potential recipients of the downgraded information.'),
('004224','draft','2022-03-03','DISA','policy','Verify that the system media downgrading process is commensurate with the access authorizations of the potential recipients of the downgraded information.','MP-08b.','N/A','Determine if: - there is verification that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed. - there is verification that the system media downgrading process is commensurate with the access authorizations of the potential recipients of the downgraded information.'),
('004225','draft','2022-03-03','DISA','policy','Identify organization-defined system media requiring downgrading.','MP-08c.','N/A','Determine if [MP-08_ODP[02]; system media requiring downgrading is defined] is identified.'),
('004226','draft','2022-03-03','DISA','policy','Defines the system media requiring downgrading.','MP-08c.','N/A','Determine if [MP-08_ODP[02]; system media requiring downgrading is defined] is identified.'),
('004227','draft','2022-03-03','DISA','policy','Test downgrading equipment on an organization-defined frequency to ensure that intended downgrading actions are being achieved.','MP-08(02)','N/A','Determine if: - downgrading equipment is tested [MP-08(02)_ODP[01]; the frequency with which to test downgrading equipment is defined] to ensure that downgrading actions are being achieved. - downgrading procedures are tested [MP-08(02)_ODP[02]; the frequency with which to test downgrading procedures is defined] to ensure that downgrading actions are being achieved.'),
('004228','draft','2022-03-03','DISA','policy','Test downgrading procedures on an organization-defined frequency to ensure that intended downgrading actions are being achieved.','MP-08(02)','N/A','Determine if: - downgrading equipment is tested [MP-08(02)_ODP[01]; the frequency with which to test downgrading equipment is defined] to ensure that downgrading actions are being achieved. - downgrading procedures are tested [MP-08(02)_ODP[02]; the frequency with which to test downgrading procedures is defined] to ensure that downgrading actions are being achieved.'),
('004229','draft','2022-03-03','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level physical and environmental protection policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','PE-01a.01(b)','N/A','Determine if the [PE-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] physical and environmental protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004230','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the development and documentation of the physical and environmental protection policy.','PE-01b.','N/A','Determine if the [PE-01_ODP[04]; an official to manage the physical and environmental protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures.'),
('004231','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the dissemination of the physical and environmental protection policy.','PE-01b.','N/A','Determine if the [PE-01_ODP[04]; an official to manage the physical and environmental protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures.'),
('004232','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage development and documentation of the physical and environmental protection procedures.','PE-01b.','N/A','Determine if the [PE-01_ODP[04]; an official to manage the physical and environmental protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures.'),
('004233','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage dissemination of the physical and environmental protection procedures.','PE-01b.','N/A','Determine if the [PE-01_ODP[04]; an official to manage the physical and environmental protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures.'),
('004234','draft','2022-03-03','DISA','policy','Defines the official who will manage the physical and environmental policy.','PE-01b.','N/A','Determine if the [PE-01_ODP[04]; an official to manage the physical and environmental protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures.'),
('004235','draft','2022-03-03','DISA','policy','Defines the official who will manage the physical and environmental procedures.','PE-01b.','N/A','Determine if the [PE-01_ODP[04]; an official to manage the physical and environmental protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures.'),
('004236','draft','2022-03-03','DISA','policy','Review and update the current physical and environmental protection policy following organization-defined events.','PE-01c.01','N/A','Determine if: - the current physical and environmental protection policy is reviewed and updated [PE-01_ODP[05]; the frequency at which the current physical and environmental protection policy is reviewed and updated is defined]. - the current physical and environmental protection policy is reviewed and updated following [PE-01_ODP[06]; events that would require the current physical and environmental protection policy to be reviewed and updated are defined].'),
('004237','draft','2022-03-03','DISA','policy','Defines the events following reviewing and updating the current physical and environmental protection policy.','PE-01c.01','N/A','Determine if: - the current physical and environmental protection policy is reviewed and updated [PE-01_ODP[05]; the frequency at which the current physical and environmental protection policy is reviewed and updated is defined]. - the current physical and environmental protection policy is reviewed and updated following [PE-01_ODP[06]; events that would require the current physical and environmental protection policy to be reviewed and updated are defined].'),
('004238','draft','2022-03-03','DISA','policy','Review and update the current physical and environmental protection procedures following organization-defined events.','PE-01c.02','N/A','Determine if: - the current physical and environmental protection procedures are reviewed and updated [PE-01_ODP[07]; the frequency at which the current physical and environmental protection procedures are reviewed and updated is defined]. - the current physical and environmental protection procedures are reviewed and updated following [PE-01_ODP[08]; events that would require the physical and environmental protection procedures to be reviewed and updated are defined].'),
('004239','draft','2022-03-03','DISA','policy','Defines the events following reviewing and updating the current physical and environmental protection procedures.','PE-01c.02','N/A','Determine if: - the current physical and environmental protection procedures are reviewed and updated [PE-01_ODP[07]; the frequency at which the current physical and environmental protection procedures are reviewed and updated is defined]. - the current physical and environmental protection procedures are reviewed and updated following [PE-01_ODP[08]; events that would require the physical and environmental protection procedures to be reviewed and updated are defined].'),
('004240','draft','2022-03-03','DISA','policy','Enforce physical access authorizations at organization-defined entry points to the facility where the system resides.',NULL,'N/A',NULL),
('004241','draft','2022-03-03','DISA','policy','Enforce physical access authorizations at organization-defined exit points to the facility where the system resides.',NULL,'N/A',NULL),
('004242','draft','2022-03-03','DISA','policy','Control ingress to the facility where the information system resides using one or more organization-defined physical access control systems or devices or guards.','PE-03a.02','N/A','Determine if physical access authorizations are enforced at [PE-03_ODP[01]; entry and exit points to the facility in which the system resides are defined] by controlling ingress and egress to the facility using [PE-03_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[PE-03_ODP[03]; physical access control systems or devices used to control ingress and egress to the facility are defined (if selected)]; guards}].'),
('004243','draft','2022-03-03','DISA','policy','Control egress to the facility where the information system resides using one or more organization-defined physical access control systems or devices or guards.','PE-03a.02','N/A','Determine if physical access authorizations are enforced at [PE-03_ODP[01]; entry and exit points to the facility in which the system resides are defined] by controlling ingress and egress to the facility using [PE-03_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[PE-03_ODP[03]; physical access control systems or devices used to control ingress and egress to the facility are defined (if selected)]; guards}].'),
('004244','draft','2022-03-03','DISA','policy','Limit access using physical barriers.','PE-03(07)','N/A','Determine if physical barriers are used to limit access.'),
('004245','draft','2022-03-03','DISA','policy','Employ access control vestibules at organization-defined locations within the facility.','PE-03(08)','N/A','Determine if access control vestibules are employed at [PE-03(08)_ODP; locations within the facility where access control vestibules are to be employed are defined].'),
('004246','draft','2022-03-03','DISA','policy','Defines the locations within the facility where the access control vestibules are employed.','PE-03(08)','N/A','Determine if access control vestibules are employed at [PE-03(08)_ODP; locations within the facility where access control vestibules are to be employed are defined].'),
('004247','draft','2022-03-03','DISA','technical','Link individual identity to receipt of output from output devices.','PE-05(02)','N/A','Determine if individual identity is linked to the receipt of output from output devices.'),
('004248','draft','2022-03-03','DISA','policy','Defines the automated mechanisms for recognizing organization-defined classes or types of intrusions and initiating organization-defined response actions.','PE-06(02)','N/A','Determine if: - [PE-06(02)_ODP[01]; classes or types of intrusions to be recognized by automated mechanisms are defined] are recognized. - [PE-06(02)_ODP[02]; response actions to be initiated by automated mechanisms when organization-defined classes or types of intrusions are recognized are defined] are initiated using [PE-06(02)_ODP[03]; automated mechanisms used to recognize classes or types of intrusions and initiate response actions (defined in PE-06(02)_ODP) are defined].'),
('004249','draft','2022-03-03','DISA','policy','Review video recordings on an organization-defined frequency.','PE-06(03)(b)','N/A','Determine if video recordings are reviewed [PE-06(03)_ODP[02]; frequency at which to review video recordings is defined].'),
('004250','draft','2022-03-03','DISA','policy','Defines the frequency with which to review video recordings.','PE-06(03)(b)','N/A','Determine if video recordings are reviewed [PE-06(03)_ODP[02]; frequency at which to review video recordings is defined].'),
('004251','draft','2022-03-03','DISA','policy','Report anomalies in visitor access records to organization-defined personnel.','PE-08c.','N/A','Determine if visitor access records anomalies are reported to [PE-08_ODP[03]; personnel to whom visitor access records anomalies are reported to is/are defined].'),
('004252','draft','2022-03-03','DISA','policy','Defines the personnel who are to report anomalies in visitor access records.','PE-08c.','N/A','Determine if visitor access records anomalies are reported to [PE-08_ODP[03]; personnel to whom visitor access records anomalies are reported to is/are defined].'),
('004253','draft','2022-03-03','DISA','policy','Defines the automated mechanisms for maintaining and reviewing visitor access records.','PE-08(01)','N/A','Determine if: - visitor access records are maintained using [PE-08(01)_ODP[01]; automated mechanisms used to maintain visitor access records are defined]. - visitor access records are reviewed using [PE-08(01)_ODP[02]; automated mechanisms used to review visitor access records are defined].'),
('004254','draft','2022-03-03','DISA','policy','Limit personally identifiable information contained in visitor access records to the organization-defined elements identified in the privacy risk assessment.','PE-08(03)','N/A','Determine if personally identifiable information contained in visitor access records is limited to [PE-08(03)_ODP; elements identified in the privacy risk assessment to limit personally identifiable information contained in visitor access logs are defined] identified in the privacy risk assessment.'),
('004255','draft','2022-03-03','DISA','policy','Defines the elements identified in the privacy risk assessment for limiting personally identifiable information contained in visitor access records.','PE-08(03)','N/A','Determine if personally identifiable information contained in visitor access records is limited to [PE-08(03)_ODP; elements identified in the privacy risk assessment to limit personally identifiable information contained in visitor access logs are defined] identified in the privacy risk assessment.'),
('004256','draft','2022-03-03','DISA','policy','Defines the system or individual system components that provide the capability of shutting off power in emergency situations.','PE-10a.','N/A','Determine if the capability to shut off power to [PE-10_ODP[01]; system or individual system components that require the capability to shut off power in emergency situations is/are defined] in emergency situations is provided.'),
('004257','draft','2022-03-03','DISA','policy','Defines the automatic environmental controls for preventing potentially harmful fluctuations to the system.','PE-14(01)','N/A','Determine if [PE-14(01)_ODP; automatic environmental controls to prevent fluctuations that are potentially harmful to the system are defined] are employed in the facility to prevent fluctuations that are potentially harmful to the system.'),
('004258','draft','2022-03-03','DISA','policy','Defines the personnel or roles who employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment.','PE-14(02)','N/A','Determine if: - environmental control monitoring is employed. - the environmental control monitoring capability provides an alarm or notification to [PE-14(02)_ODP; personnel or roles to be notified by environmental control monitoring when environmental changes are potentially harmful to personnel or equipment is/are defined] when changes are potentially harmful to personnel or equipment.'),
('004259','draft','2022-03-03','DISA','policy','Detect the presence of water near the system.','PE-15(01)','N/A','Determine if: - the presence of water near the system can be detected automatically. - [PE-15(01)_ODP[01]; personnel or roles to be alerted when the presence of water is detected near the system is/are defined] is/are alerted using [PE-15(01)_ODP[02]; automated mechanisms used to detect the presence of water near the system are defined].'),
('004260','draft','2022-03-03','DISA','policy','Alert organization-defined personnel or roles of the presence of water near the system using organization-defined automated mechanisms.','PE-15(01)','N/A','Determine if: - the presence of water near the system can be detected automatically. - [PE-15(01)_ODP[01]; personnel or roles to be alerted when the presence of water is detected near the system is/are defined] is/are alerted using [PE-15(01)_ODP[02]; automated mechanisms used to detect the presence of water near the system are defined].'),
('004261','draft','2022-03-03','DISA','policy','Defines the automated mechanisms for detecting the presence of water and alerting organization-defined personnel or roles.','PE-15(01)','N/A','Determine if: - the presence of water near the system can be detected automatically. - [PE-15(01)_ODP[01]; personnel or roles to be alerted when the presence of water is detected near the system is/are defined] is/are alerted using [PE-15(01)_ODP[02]; automated mechanisms used to detect the presence of water near the system are defined].'),
('004262','draft','2022-03-03','DISA','policy','Determine and document the organization-defined alternate work sites allowed for use by employees.','PE-17a.','N/A','Determine if [PE-17_ODP[01]; alternate work sites allowed for use by employees are defined] are determined and documented.'),
('004263','draft','2022-03-03','DISA','policy','Provide a means for employees to communicate with information privacy personnel in case of incidents.','PE-17d.','N/A','Determine if a means for employees to communicate with information security and privacy personnel in case of incidents is provided.'),
('004264','draft','2022-03-03','DISA','policy','Protect system components, associated data communications, and networks in accordance with national Emissions Security policies based on the security category or classification of the information.','PE-19(01)','N/A','Determine if: - system components are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information. - associated data communications are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information. - networks are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information.'),
('004265','draft','2022-03-03','DISA','policy','Protect system components, associated data communications, and networks in accordance with national Emissions Security procedures based on the security category or classification of the information.','PE-19(01)','N/A','Determine if: - system components are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information. - associated data communications are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information. - networks are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information.'),
('004266','draft','2022-03-03','DISA','policy','Employ organization-defined protective measures against electromagnetic pulse damage for organization-defined systems and system components.','PE-21','N/A','Determine if [PE-21_ODP[01]; protective measures to be employed against electromagnetic pulse damage are defined] are employed against electromagnetic pulse damage for [PE-21_ODP[02]; system and system components requiring protection against electromagnetic pulse damage are defined].'),
('004267','draft','2022-03-03','DISA','policy','Defines the protective measure employed against electromagnetic pulse damage for organization-defined systems and system components.','PE-21','N/A','Determine if [PE-21_ODP[01]; protective measures to be employed against electromagnetic pulse damage are defined] are employed against electromagnetic pulse damage for [PE-21_ODP[02]; system and system components requiring protection against electromagnetic pulse damage are defined].'),
('004268','draft','2022-03-03','DISA','policy','Defines the systems and system components in which organization-defined protective measures are employed against electromagnetic pulse damage.','PE-21','N/A','Determine if [PE-21_ODP[01]; protective measures to be employed against electromagnetic pulse damage are defined] are employed against electromagnetic pulse damage for [PE-21_ODP[02]; system and system components requiring protection against electromagnetic pulse damage are defined].'),
('004269','draft','2022-03-03','DISA','policy','Mark organization-defined system hardware components indicating the impact or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.','PE-22','N/A','Determine if [PE-22_ODP; system hardware components to be marked indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component are defined] are marked indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.'),
('004270','draft','2022-03-03','DISA','policy','Defines the system hardware components which are marked, indicating the impact or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.','PE-22','N/A','Determine if [PE-22_ODP; system hardware components to be marked indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component are defined] are marked indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.'),
('004271','draft','2022-03-03','DISA','policy','Plan the location or site of the facility where the system resides considering physical and environmental hazards.','PE-23a.','N/A','Determine if the location or site of the facility where the system resides is planned considering physical and environmental hazards.'),
('004272','draft','2022-03-03','DISA','policy','For existing facilities, consider the physical and environmental hazards in the organizational risk management strategy.','PE-23b.','N/A','Determine if for existing facilities, physical and environmental hazards are considered in the organizational risk management strategy.'),
('004273','draft','2022-03-03','DISA','policy','Develop and document an organization-level; mission/business process-level; and or system-level planning policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','PL-01a.01(b)','N/A','Determine if the [PL-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] planning policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004274','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the development and documentation of the planning policy and procedures.','PL-01b.','N/A','Determine if the [PL-01_ODP[04]; an official to manage the planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the planning policy and procedures.'),
('004275','draft','2022-03-03','DISA','policy','Designate an organization-defined official to manage the dissemination of the planning policy and procedures.','PL-01b.','N/A','Determine if the [PL-01_ODP[04]; an official to manage the planning policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the planning policy and procedures.'),
('004276','draft','2022-03-03','DISA','policy','Review and update the current planning policy following organization-defined events.','PL-01c.01','N/A','Determine if: - the current planning policy is reviewed and updated [PL-01_ODP[05]; the frequency with which the current planning policy is reviewed and updated is defined]. - the current planning policy is reviewed and updated following [PL-01_ODP[06]; events that would require the current planning policy to be reviewed and updated are defined].'),
('004277','draft','2022-03-03','DISA','policy','Review and update the current planning procedures following organization-defined events.','PL-01c.02','N/A','Determine if: - the current planning procedures are reviewed and updated [PL-01_ODP[07]; the frequency with which the current planning procedures are reviewed and updated is defined]. - the current planning procedures are reviewed and updated following [PL-01_ODP[08]; events that would require procedures to be reviewed and updated are defined].'),
('004278','draft','2022-03-03','DISA','policy','Develop security and privacy plans for the system that identify the individuals that fulfill system roles and responsibilities.','PL-02a.04','N/A','Determine if: - a security plan for the system is developed that identifies the individuals that fulfill system roles and responsibilities. - a privacy plan for the system is developed that identifies the individuals that fulfill system roles and responsibilities.'),
('004279','draft','2022-03-03','DISA','policy','Develop security and privacy plans for the system that identify the information types processed, stored, and transmitted by the system.','PL-02a.05','N/A','Determine if: - a security plan for the system is developed that identifies the information types processed, stored, and transmitted by the system. - a privacy plan for the system is developed that identifies the information types processed, stored, and transmitted by the system.'),
('004280','draft','2022-03-03','DISA','policy','Develop security and privacy plans for the system that describe any specific threats to the system that are of concern to the organization.','PL-02a.07','N/A','Determine if: - a security plan for the system is developed that describes any specific threats to the system that are of concern to the organization. - a privacy plan for the system is developed that describes any specific threats to the system that are of concern to the organization.'),
('004281','draft','2022-03-03','DISA','policy','Develop security and privacy plans for the system that provide the results of a privacy risk assessment for the systems processing personally identifiable information.','PL-02a.08','N/A','Determine if: - a security plan for the system is developed that provides the results of a privacy risk assessment for systems processing personally identifiable information. - a privacy plan for the system is developed that provides the results of a privacy risk assessment for systems processing personally identifiable information.'),
('004282','draft','2022-03-03','DISA','policy','Develop security and privacy plans for the system that include risk determinations for security and privacy architecture and design decisions.','PL-02a.13','N/A','Determine if: - a security plan for the system is developed that includes risk determinations for security architecture and design decisions. - a privacy plan for the system is developed that includes risk determinations for privacy architecture and design decisions.'),
('004283','draft','2022-03-03','DISA','policy','Develop security and privacy plans for the system that include security- and privacy-related activities affecting the system that require planning and coordination with organization-defined individuals or groups.','PL-02a.14','N/A','Determine if: - a security plan for the system is developed that includes security-related activities affecting the system that require planning and coordination with [PL-02_ODP[01]; individuals or groups with whom security and privacy-related activities affecting the system that require planning and coordination is/are assigned]. - a privacy plan for the system is developed that includes privacy-related activities affecting the system that require planning and coordination with [PL-02_ODP[01]; individuals or groups with whom security and privacy-related activities affecting the system that require planning and coordination is/are assigned].'),
('004284','draft','2022-03-03','DISA','policy','Establish the rules describing the responsibilities and expected behavior, for security, for individuals requiring access to the system.','PL-04a.','N/A','Determine if: - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system. - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system.'),
('004285','draft','2022-03-03','DISA','policy','Establish the rules describing the responsibilities and expected behavior, for privacy, for individuals requiring access to the system.','PL-04a.','N/A','Determine if: - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system. - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system.'),
('004286','draft','2022-03-03','DISA','policy','Provide the rules describing the responsibilities and expected behavior, for information and system usage, for individuals requiring access to the system.','PL-04a.','N/A','Determine if: - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system. - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system.'),
('004287','draft','2022-03-03','DISA','policy','Provide the rules describing the responsibilities and expected behavior, for security, for individuals requiring access to the system.','PL-04a.','N/A','Determine if: - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system. - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system.'),
('004288','draft','2022-03-03','DISA','policy','Provide the rules describing the responsibilities and expected behavior, for privacy, for individuals requiring access to the system.','PL-04a.','N/A','Determine if: - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system. - rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system.'),
('004289','draft','2022-03-03','DISA','policy','Defines the frequency individuals are required to read and re-acknowledge the rules of behavior whenever the rules are revised or updated.','PL-04d.','N/A','Determine if individuals who have acknowledged a previous version of the rules of behavior are required to read and reacknowledge [PL-04_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[PL-04_ODP[03]; frequency for individuals to read and re-acknowledge the rules of behavior is defined (if selected)]; when the rules are revised or updated}].'),
('004290','draft','2022-03-03','DISA','policy','Include in the rules of behavior, restrictions on use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.','PL-04(01)(c)','N/A','Determine if the rules of behavior include restrictions on the use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.'),
('004291','draft','2022-03-03','DISA','policy','Develop a security Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information privacy.','PL-07a.','N/A','Determine if a CONOPS for the system describing how the organization intends to operate the system from the perspective of information security and privacy is developed.'),
('004292','draft','2022-03-03','DISA','policy','Develop privacy architectures for the system.',NULL,'N/A',NULL),
('004293','draft','2022-03-03','DISA','policy','Develop privacy architectures for the system that describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information.','PL-08a.01','N/A','Determine if a security architecture for the system describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information.'),
('004294','draft','2022-03-03','DISA','policy','Develop security architectures for the system that describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals.','PL-08a.02','N/A','Determine if a privacy architecture describes the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals.'),
('004295','draft','2022-03-03','DISA','policy','Develop privacy architectures for the system that describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals.','PL-08a.02','N/A','Determine if a privacy architecture describes the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals.'),
('004296','draft','2022-03-03','DISA','policy','Develop privacy architectures for the system that describe how the architectures are integrated into and support the enterprise architecture.','PL-08a.03','N/A','Determine if: - a security architecture for the system describes how the architecture is integrated into and supports the enterprise architecture. - a privacy architecture for the system describes how the architecture is integrated into and supports the enterprise architecture.'),
('004297','draft','2022-03-03','DISA','policy','Develop privacy architectures for the system that describe any assumptions about, and dependencies on, external systems and services.','PL-08a.04','N/A','Determine if: - a security architecture for the system describes any assumptions about and dependencies on external systems and services. - a privacy architecture for the system describes any assumptions about and dependencies on external systems and services.'),
('004298','draft','2022-03-03','DISA','policy','Reflect planned privacy architecture changes in the privacy plans.','PL-08c.','N/A','Determine if: - planned architecture changes are reflected in the security plan. - planned architecture changes are reflected in the privacy plan. - planned architecture changes are reflected in the Concept of Operations (CONOPS). - planned architecture changes are reflected in criticality analysis. - planned architecture changes are reflected in organizational procedures. - planned architecture changes are reflected in procurements and acquisitions.'),
('004299','draft','2022-03-03','DISA','policy','Reflect planned privacy architecture changes in the privacy Concept of Operations (CONOPS).','PL-08c.','N/A','Determine if: - planned architecture changes are reflected in the security plan. - planned architecture changes are reflected in the privacy plan. - planned architecture changes are reflected in the Concept of Operations (CONOPS). - planned architecture changes are reflected in criticality analysis. - planned architecture changes are reflected in organizational procedures. - planned architecture changes are reflected in procurements and acquisitions.'),
('004300','draft','2022-03-03','DISA','policy','Reflect planned privacy architecture changes in the privacy organizational procurements and acquisitions.','PL-08c.','N/A','Determine if: - planned architecture changes are reflected in the security plan. - planned architecture changes are reflected in the privacy plan. - planned architecture changes are reflected in the Concept of Operations (CONOPS). - planned architecture changes are reflected in criticality analysis. - planned architecture changes are reflected in organizational procedures. - planned architecture changes are reflected in procurements and acquisitions.'),
('004301','draft','2022-03-03','DISA','policy','Design the privacy architecture for the system using a defense-in-depth approach that allocates organization-defined controls to organization-defined locations.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('004302','draft','2022-03-03','DISA','policy','Design the privacy architecture for the system using a defense-in-depth approach that allocates organization-defined controls to organization-defined architectural layers.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('004303','draft','2022-03-03','DISA','policy','Defines the controls to be allocated to organization-defined locations for the privacy architecture.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('004304','draft','2022-03-03','DISA','policy','Defines the controls to be allocated to the organization-defined privacy architectural layers.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('004305','draft','2022-03-03','DISA','policy','Defines the locations to which the system allocates organization-defined controls in the privacy architecture.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('004306','draft','2022-03-03','DISA','policy','Defines the architectural layers to which the system allocates organization-defined controls in the privacy architecture.','PL-08(01)(a)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined]. - the privacy architecture for the system is designed using a defense-in-depth approach that allocates [PL-08(01)_ODP[01]; controls to be allocated are defined] to [PL-08(01)_ODP[02]; locations and architectural layers are defined].'),
('004307','draft','2022-03-03','DISA','policy','Design the privacy architecture for the system using a defense-in-depth approach that ensures that the allocated controls operate in a coordinated and mutually reinforcing manner.','PL-08(01)(b)','N/A','Determine if: - the security architecture for the system is designed using a defense-in-depth approach that ensures the allocated controls operate in a coordinated and mutually reinforcing manner. - the privacy architecture for the system is designed using a defense-in-depth approach that ensures the allocated controls operate in a coordinated and mutually reinforcing manner.'),
('004308','draft','2022-03-03','DISA','policy','Defines the controls that are allocated to the organization-defined locations and architectural layers.','PL-08(02)','N/A','Determine if [PL-08(02)_ODP[01]; controls to be allocated are defined] that are allocated to [PL-08(02)_ODP[02]; locations and architectural layers are defined] are required to be obtained from different suppliers.'),
('004309','draft','2022-03-03','DISA','policy','Defines the locations and architectural layers that are obtained from different suppliers.','PL-08(02)','N/A','Determine if [PL-08(02)_ODP[01]; controls to be allocated are defined] that are allocated to [PL-08(02)_ODP[02]; locations and architectural layers are defined] are required to be obtained from different suppliers.'),
('004310','draft','2022-03-03','DISA','policy','Select a control baseline for the system.','PL-10','N/A','Determine if a control baseline for the system is selected.'),
('004311','draft','2022-03-03','DISA','policy','Tailor the selected control baseline by applying specified tailoring actions.','PL-11','N/A','Determine if the selected control baseline is tailored by applying specified tailoring actions.'),
('004312','draft','2022-03-03','DISA','policy','Review and update the organization-wide information security program plan following organization-defined events.','PM-01b.','N/A','Determine if: - the information security program plan is reviewed and updated [PM-01_ODP[01]; the frequency at which to review and update the organization-wide information security program plan is defined]. - the information security program plan is reviewed and updated following [PM-01_ODP[02]; events that trigger the review and update of the organization-wide information security program plan are defined].'),
('004313','draft','2022-03-03','DISA','policy','Defines the events for reviewing and updating the organization-wide information security program plan.','PM-01b.','N/A','Determine if: - the information security program plan is reviewed and updated [PM-01_ODP[01]; the frequency at which to review and update the organization-wide information security program plan is defined]. - the information security program plan is reviewed and updated following [PM-01_ODP[02]; events that trigger the review and update of the organization-wide information security program plan are defined].'),
('004314','draft','2022-03-03','DISA','policy','Include the resources needed to implement the information security programs in capital planning and investment requests.','PM-03a.','N/A','Determine if: - the resources needed to implement the information security program are included in capital planning and investment requests, and all exceptions are documented. - the resources needed to implement the privacy program are included in capital planning and investment requests, and all exceptions are documented.'),
('004315','draft','2022-03-03','DISA','policy','Include the resources needed to implement the information privacy programs in capital planning and investment requests.',NULL,'N/A',NULL),
('004316','draft','2022-03-03','DISA','policy','Prepare documentation required for addressing information security programs in capital planning and investment requests in accordance with applicable laws, Executive Orders, directives, policies, regulations, and standards.','PM-03a.','N/A','Determine if: - the resources needed to implement the information security program are included in capital planning and investment requests, and all exceptions are documented. - the resources needed to implement the privacy program are included in capital planning and investment requests, and all exceptions are documented.'),
('004317','draft','2022-03-03','DISA','policy','Prepare documentation required for addressing information privacy programs in capital planning and investment requests in accordance with applicable laws, Executive Orders, directives, policies, regulations, and standards.','PM-03b.','N/A','Determine if: - the documentation required for addressing the information security program in capital planning and investment requests is prepared in accordance with applicable laws, executive orders, directives, policies, regulations, standards. - the documentation required for addressing the privacy program in capital planning and investment requests is prepared in accordance with applicable laws, executive orders, directives, policies, regulations, standards.'),
('004318','draft','2022-03-03','DISA','policy','Make available for expenditure, the planned information privacy resources.','PM-03c.','N/A','Determine if: - information security resources are made available for expenditure as planned. - privacy resources are made available for expenditure as planned.'),
('004319','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the privacy program and the associated organizational systems are maintained.','PM-04a.01','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained.'),
('004320','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed.','PM-04a.01','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained.'),
('004321','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the supply chain risk management programs and the associated organizational systems are maintained.','PM-04a.01','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained.'),
('004322','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the supply chain risk management programs and the associated organizational systems are developed.','PM-04a.01','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained.'),
('004323','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the privacy program and associated organizational systems document the remedial information privacy actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation.','PM-04a.02','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems document remedial information security risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems document remedial privacy risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems document remedial supply chain risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation.'),
('004324','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems document the remedial information supply chain risk management actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation.','PM-04a.02','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security program and associated organizational systems document remedial information security risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation. - a process to ensure that plans of action and milestones for the privacy program and associated organizational systems document remedial privacy risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation. - a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems document remedial supply chain risk management actions to adequately respond to risks to organizational operations and assets, individuals, other organizations, and the Nation.'),
('004325','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the security program and associated organizational systems are reported in accordance with established reporting requirements.','PM-04a.03','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security risk management programs and associated organizational systems are reported in accordance with established reporting requirements. - a process to ensure that plans of action and milestones for the privacy risk management programs and associated organizational systems are reported in accordance with established reporting requirements. - a process to ensure that plans of action and milestones for the supply chain risk management programs and associated organizational systems are reported in accordance with established reporting requirements.'),
('004326','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are reported in accordance with established reporting requirements.','PM-04a.03','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security risk management programs and associated organizational systems are reported in accordance with established reporting requirements. - a process to ensure that plans of action and milestones for the privacy risk management programs and associated organizational systems are reported in accordance with established reporting requirements. - a process to ensure that plans of action and milestones for the supply chain risk management programs and associated organizational systems are reported in accordance with established reporting requirements.'),
('004327','draft','2022-03-03','DISA','policy','Implement a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are reported in accordance with established reporting requirements.','PM-04a.03','N/A','Determine if: - a process to ensure that plans of action and milestones for the information security risk management programs and associated organizational systems are reported in accordance with established reporting requirements. - a process to ensure that plans of action and milestones for the privacy risk management programs and associated organizational systems are reported in accordance with established reporting requirements. - a process to ensure that plans of action and milestones for the supply chain risk management programs and associated organizational systems are reported in accordance with established reporting requirements.'),
('004328','draft','2022-03-03','DISA','policy','Develop an inventory of organizational systems.','PM-05','N/A','Determine if: - an inventory of organizational systems is developed. - the inventory of organizational systems is updated [PM-05_ODP; the frequency at which to update the inventory of organizational systems is defined].'),
('004329','draft','2022-03-03','DISA','policy','Update, on an organization-defined frequency, an inventory of organizational systems.','PM-05','N/A','Determine if: - an inventory of organizational systems is developed. - the inventory of organizational systems is updated [PM-05_ODP; the frequency at which to update the inventory of organizational systems is defined].'),
('004330','draft','2022-03-03','DISA','policy','Defines the frequency with which to update the inventory of organizational systems.','PM-05','N/A','Determine if: - an inventory of organizational systems is developed. - the inventory of organizational systems is updated [PM-05_ODP; the frequency at which to update the inventory of organizational systems is defined].'),
('004331','draft','2022-03-03','DISA','policy','Establish an inventory of all systems, applications, and projects that process personally identifiable information.','PM-05(01)','N/A','Determine if: - an inventory of all systems, applications, and projects that process personally identifiable information is established. - an inventory of all systems, applications, and projects that process personally identifiable information is maintained. - an inventory of all systems, applications, and projects that process personally identifiable information is updated [PM-05(01)_ODP; the frequency at which to update the inventory of systems, applications, and projects that process personally identifiable information is defined].'),
('004332','draft','2022-03-03','DISA','policy','Maintain an inventory of all systems, applications, and projects that process personally identifiable information.','PM-05(01)','N/A','Determine if: - an inventory of all systems, applications, and projects that process personally identifiable information is established. - an inventory of all systems, applications, and projects that process personally identifiable information is maintained. - an inventory of all systems, applications, and projects that process personally identifiable information is updated [PM-05(01)_ODP; the frequency at which to update the inventory of systems, applications, and projects that process personally identifiable information is defined].'),
('004333','draft','2022-03-03','DISA','policy','Update on an organization-defined frequency, an inventory of all systems, applications, and projects that process personally identifiable information.','PM-05(01)','N/A','Determine if: - an inventory of all systems, applications, and projects that process personally identifiable information is established. - an inventory of all systems, applications, and projects that process personally identifiable information is maintained. - an inventory of all systems, applications, and projects that process personally identifiable information is updated [PM-05(01)_ODP; the frequency at which to update the inventory of systems, applications, and projects that process personally identifiable information is defined].'),
('004334','draft','2022-03-03','DISA','policy','Defines the frequency of which an inventory of all systems, applications, and projects that process personally identifiable information will be updated.','PM-05(01)','N/A','Determine if: - an inventory of all systems, applications, and projects that process personally identifiable information is established. - an inventory of all systems, applications, and projects that process personally identifiable information is maintained. - an inventory of all systems, applications, and projects that process personally identifiable information is updated [PM-05(01)_ODP; the frequency at which to update the inventory of systems, applications, and projects that process personally identifiable information is defined].'),
('004335','draft','2022-03-03','DISA','policy','Develop the results of information privacy measures of performance.','PM-06','N/A','Determine if: - information security measures of performance are developed. - information security measures of performance are monitored. - the results of information security measures of performance are reported. - privacy measures of performance are developed. - privacy measures of performance are monitored. - the results of privacy measures of performance are reported.'),
('004336','draft','2022-03-03','DISA','policy','Monitor the results of information privacy measures of performance.','PM-06','N/A','Determine if: - information security measures of performance are developed. - information security measures of performance are monitored. - the results of information security measures of performance are reported. - privacy measures of performance are developed. - privacy measures of performance are monitored. - the results of privacy measures of performance are reported.'),
('004337','draft','2022-03-03','DISA','policy','Report on the results of information privacy measures of performance.','PM-06','N/A','Determine if: - information security measures of performance are developed. - information security measures of performance are monitored. - the results of information security measures of performance are reported. - privacy measures of performance are developed. - privacy measures of performance are monitored. - the results of privacy measures of performance are reported.'),
('004338','draft','2022-03-03','DISA','policy','Develop an enterprise architecture with consideration for information privacy and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-07','N/A','Determine if: - an enterprise architecture is developed with consideration for information security. - an enterprise architecture is maintained with consideration for information security. - an enterprise architecture is developed with consideration for privacy. - an enterprise architecture is maintained with consideration for privacy. - an enterprise architecture is developed with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation. - an enterprise architecture is maintained with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.'),
('004339','draft','2022-03-03','DISA','policy','Maintain an enterprise architecture with consideration for information security and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-07','N/A','Determine if: - an enterprise architecture is developed with consideration for information security. - an enterprise architecture is maintained with consideration for information security. - an enterprise architecture is developed with consideration for privacy. - an enterprise architecture is maintained with consideration for privacy. - an enterprise architecture is developed with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation. - an enterprise architecture is maintained with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.'),
('004340','draft','2022-03-03','DISA','policy','Maintain an enterprise architecture with consideration for information privacy and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-07','N/A','Determine if: - an enterprise architecture is developed with consideration for information security. - an enterprise architecture is maintained with consideration for information security. - an enterprise architecture is developed with consideration for privacy. - an enterprise architecture is maintained with consideration for privacy. - an enterprise architecture is developed with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation. - an enterprise architecture is maintained with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.'),
('004341','draft','2022-03-03','DISA','policy','Offload organization-defined non-essential functions or services to other systems, system components, or an external provider.','PM-07(01)','N/A','Determine if [PM-07(01)_ODP; non-essential functions or services to be offloaded are defined] are offloaded to other systems, system components, or an external provider.'),
('004342','draft','2022-03-03','DISA','policy','Defines the non-essential functions or services to be offloaded to other systems, system components, or an external provider.','PM-07(01)','N/A','Determine if [PM-07(01)_ODP; non-essential functions or services to be offloaded are defined] are offloaded to other systems, system components, or an external provider.'),
('004343','draft','2022-03-03','DISA','policy','Address information privacy issues in the development and documentation of a critical infrastructure and key resources protection plan.','PM-08','N/A','Determine if: - information security issues are addressed in the development of a critical infrastructure and key resources protection plan. - information security issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - information security issues are addressed in the update of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the development of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the update of a critical infrastructure and key resources protection plan.'),
('004344','draft','2022-03-03','DISA','policy','Address information privacy issues in the updating of a critical infrastructure and key resources protection plan.','PM-08','N/A','Determine if: - information security issues are addressed in the development of a critical infrastructure and key resources protection plan. - information security issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - information security issues are addressed in the update of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the development of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the documentation of a critical infrastructure and key resources protection plan. - privacy issues are addressed in the update of a critical infrastructure and key resources protection plan.'),
('004345','draft','2022-03-03','DISA','policy','Develop a comprehensive strategy to manage privacy risk to individuals resulting from the authorized processing of personally identifiable information.','PM-09a.02','N/A','Determine if a comprehensive strategy is developed to manage privacy risk to individuals resulting from the authorized processing of personally identifiable information.'),
('004346','draft','2022-03-03','DISA','policy','Manage the security state of organizational systems and the environments in which those systems operate through authorization processes.','PM-10a.','N/A','Determine if: - the security state of organizational systems and the environments in which those systems operate are managed through authorization processes. - the privacy state of organizational systems and the environments in which those systems operate are managed through authorization processes.'),
('004347','draft','2022-03-03','DISA','policy','Manage the privacy state of organizational systems and the environments in which those systems operate through authorization processes.','PM-10a.','N/A','Determine if: - the security state of organizational systems and the environments in which those systems operate are managed through authorization processes. - the privacy state of organizational systems and the environments in which those systems operate are managed through authorization processes.'),
('004348','draft','2022-03-03','DISA','policy','Define organizational mission and business processes with consideration for information privacy and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.','PM-11a.','N/A','Determine if: - organizational mission and business processes are defined with consideration for information security. - organizational mission and business processes are defined with consideration for privacy. - organizational mission and business processes are defined with consideration for the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.'),
('004349','draft','2022-03-03','DISA','policy','Determine personally identifiable information processing needs arising from the defined mission and business processes.','PM-11b.','N/A','Determine if: - information protection needs arising from the defined mission and business processes are determined. - personally identifiable information processing needs arising from the defined mission and business processes are determined.'),
('004350','draft','2022-03-03','DISA','policy','Review and revise the mission and business processes on an organization-defined frequency.','PM-11c.','N/A','Determine if the mission and business processes are reviewed and revised [PM-11_ODP; the frequency at which to review and revise the mission and business processes is defined].'),
('004351','draft','2022-03-03','DISA','policy','Defines the frequency at which the mission and business processes are reviewed and revised.','PM-11c.','N/A','Determine if the mission and business processes are reviewed and revised [PM-11_ODP; the frequency at which to review and revise the mission and business processes is defined].'),
('004352','draft','2022-03-03','DISA','policy','Establish a privacy workforce development and improvement program.','PM-13','N/A','Determine if: - a security workforce development and improvement program is established. - privacy workforce development and improvement program is established.'),
('004353','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy testing activities associated with organizational systems are developed.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('004354','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy testing activities associated with organizational systems are maintained.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('004355','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy training activities associated with organizational systems are developed.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('004356','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy training activities associated with organizational systems are maintained.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('004357','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy monitoring activities associated with organizational systems are developed.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('004358','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy monitoring activities associated with organizational information systems are maintained.','PM-14a.01','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained.'),
('004359','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy testing associated with organizational systems continue to be executed.','PM-14a.02','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed.'),
('004360','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy training associated with organizational systems continue to be executed.','PM-14a.02','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed.'),
('004361','draft','2022-03-03','DISA','policy','Implement a process for ensuring that organizational plans for conducting privacy monitoring activities associated with organizational systems continue to be executed.','PM-14a.02','N/A','Determine if: - a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed. - a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed.'),
('004362','draft','2022-03-03','DISA','policy','Establish and institutionalize contact with selected groups and associations within the privacy community to facilitate ongoing privacy education and training for organizational personnel.','PM-15a.','N/A','Determine if: - contact is established and institutionalized with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel. - contact is established and institutionalized with selected groups and associations within the privacy community to facilitate ongoing privacy education and training for organizational personnel.'),
('004363','draft','2022-03-03','DISA','policy','Establish and institutionalize contact with selected groups and associations within the privacy community to maintain currency with recommended privacy practices, techniques, and technologies.','PM-15b.','N/A','Determine if: - contact is established and institutionalized with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies. - contact is established and institutionalized with selected groups and associations within the privacy community to maintain currency with recommended privacy practices, techniques, and technologies.'),
('004364','draft','2022-03-03','DISA','policy','Establish and institutionalize contact with selected groups and associations within the privacy community to share current privacy information including threats, vulnerabilities, and incidents.','PM-15c.','N/A','Determine if: - contact is established and institutionalized with selected groups and associations within the security community to share current security information, including threats, vulnerabilities, and incidents. - contact is established and institutionalized with selected groups and associations within the privacy community to share current privacy information, including threats, vulnerabilities, and incidents.'),
('004365','draft','2022-03-03','DISA','policy','Employ automated means to maximize the effectiveness of sharing threat intelligence information.','PM-16(01)','N/A','Determine if automated mechanisms are employed to maximize the effectiveness of sharing threat intelligence information.'),
('004366','draft','2022-03-03','DISA','policy','Establish policy to ensure that the requirements for the protection of Controlled Unclassified Information that is processed, stored or transmitted on external systems, are implemented in accordance with applicable laws, Executive Orders, directives, policies, regulations, and standards.','PM-17a.','N/A','Determine if: - policy is established to ensure that requirements for the protection of controlled unclassified information that is processed, stored, or transmitted on external systems are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards. - procedures are established to ensure that requirements for the protection of controlled unclassified information that is processed, stored, or transmitted on external systems are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards.'),
('004367','draft','2022-03-03','DISA','policy','Establish procedures to ensure that the requirements for the protection of Controlled Unclassified Information that is processed, stored or transmitted on external systems, are implemented in accordance with applicable laws, Executive Orders, directives, policies, regulations, and standards.','PM-17a.','N/A','Determine if: - policy is established to ensure that requirements for the protection of controlled unclassified information that is processed, stored, or transmitted on external systems are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards. - procedures are established to ensure that requirements for the protection of controlled unclassified information that is processed, stored, or transmitted on external systems are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards.'),
('004368','draft','2022-03-03','DISA','policy','Review and update the policy for Controlled Unclassified Information on an organization-defined frequency.','PM-17b.','N/A','Determine if: - policy is reviewed and updated [PM-17_ODP[01]; the frequency at which to review and update the policy is defined]. - procedures are reviewed and updated [PM-17_ODP[02]; the frequency at which to review and update the procedures is defined].'),
('004369','draft','2022-03-03','DISA','policy','Defines the frequency in which the policy for Controlled Unclassified information is reviewed and updated.','PM-17b.','N/A','Determine if: - policy is reviewed and updated [PM-17_ODP[01]; the frequency at which to review and update the policy is defined]. - procedures are reviewed and updated [PM-17_ODP[02]; the frequency at which to review and update the procedures is defined].'),
('004370','draft','2022-03-03','DISA','policy','Review and update the procedures for Controlled Unclassified Information on an organization-defined frequency.','PM-17b.','N/A','Determine if: - policy is reviewed and updated [PM-17_ODP[01]; the frequency at which to review and update the policy is defined]. - procedures are reviewed and updated [PM-17_ODP[02]; the frequency at which to review and update the procedures is defined].'),
('004371','draft','2022-03-03','DISA','policy','Defines the frequency in which the procedures for Controlled Unclassified information is reviewed and updated.','PM-17b.','N/A','Determine if: - policy is reviewed and updated [PM-17_ODP[01]; the frequency at which to review and update the policy is defined]. - procedures are reviewed and updated [PM-17_ODP[02]; the frequency at which to review and update the procedures is defined].'),
('004372','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program.','PM-18a.','N/A','Determine if: - an organization-wide privacy program plan that provides an overview of the agency''s privacy program is developed. - the privacy program plan is disseminated.'),
('004373','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program.','PM-18a.','N/A','Determine if: - an organization-wide privacy program plan that provides an overview of the agency''s privacy program is developed. - the privacy program plan is disseminated.'),
('004374','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and includes a description of the structure of the privacy program and the resources dictated to the privacy program.','PM-18a.01','N/A','Determine if: - the privacy program plan includes a description of the structure of the privacy program. - the privacy program plan includes a description of the resources dedicated to the privacy program.'),
('004375','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and includes a description of the structure of the privacy program and the resources dictated to the privacy program.','PM-18a.01','N/A','Determine if: - the privacy program plan includes a description of the structure of the privacy program. - the privacy program plan includes a description of the resources dedicated to the privacy program.'),
('004376','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and provides an overview of the requirements for the privacy program.','PM-18a.02','N/A','Determine if: - the privacy program plan provides an overview of the requirements for the privacy program. - the privacy program plan provides a description of the privacy program management controls in place or planned for meeting the requirements of the privacy program. - the privacy program plan provides a description of common controls in place or planned for meeting the requirements of the privacy program.'),
('004377','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and provides an overview of the requirements for the privacy program.','PM-18a.02','N/A','Determine if: - the privacy program plan provides an overview of the requirements for the privacy program. - the privacy program plan provides a description of the privacy program management controls in place or planned for meeting the requirements of the privacy program. - the privacy program plan provides a description of common controls in place or planned for meeting the requirements of the privacy program.'),
('004378','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and a description of the privacy program management controls and common controls in place or planned for meeting those requirements.','PM-18a.02','N/A','Determine if: - the privacy program plan provides an overview of the requirements for the privacy program. - the privacy program plan provides a description of the privacy program management controls in place or planned for meeting the requirements of the privacy program. - the privacy program plan provides a description of common controls in place or planned for meeting the requirements of the privacy program.'),
('004379','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and a description of the privacy program management controls and common controls in place or planned for meeting those requirements.','PM-18a.02','N/A','Determine if: - the privacy program plan provides an overview of the requirements for the privacy program. - the privacy program plan provides a description of the privacy program management controls in place or planned for meeting the requirements of the privacy program. - the privacy program plan provides a description of common controls in place or planned for meeting the requirements of the privacy program.'),
('004380','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and includes the role of the Senior Agency Official for Privacy and the identification and assignment of the roles of other privacy officials and staff and their responsibilities.','PM-18a.03','N/A','Determine if: - the privacy program plan includes the role of the senior agency official for privacy. - the privacy program plan includes the identification and assignment of the roles of other privacy officials and staff and their responsibilities.'),
('004381','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and includes the role of the Senior Agency Official for Privacy and the identification and assignment of the roles of other privacy officials and staff and their responsibilities.','PM-18a.03','N/A','Determine if: - the privacy program plan includes the role of the senior agency official for privacy. - the privacy program plan includes the identification and assignment of the roles of other privacy officials and staff and their responsibilities.'),
('004382','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and describes management commitment, compliance, and the strategic goals and objectives of the privacy program.','PM-18a.04','N/A','Determine if: - the privacy program plan describes management commitment. - the privacy program plan describes compliance. - the privacy program plan describes the strategic goals and objectives of the privacy program.'),
('004383','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and describes management commitment, compliance, and the strategic goals and objectives of the privacy program.','PM-18a.04','N/A','Determine if: - the privacy program plan describes management commitment. - the privacy program plan describes compliance. - the privacy program plan describes the strategic goals and objectives of the privacy program.'),
('004384','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and reflects coordination among organizational entities responsible for the different aspects of privacy.','PM-18a.05','N/A','Determine if the privacy program plan reflects coordination among organizational entities responsible for the different aspects of privacy.'),
('004385','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and reflects coordination among organizational entities responsible for the different aspects of privacy.','PM-18a.05','N/A','Determine if the privacy program plan reflects coordination among organizational entities responsible for the different aspects of privacy.'),
('004386','draft','2022-03-03','DISA','policy','Develop an organization-wide privacy program plan that provides an overview of the agency''s privacy program and is approved by a senior official with responsibility and accountability for the privacy risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.','PM-18a.06','N/A','Determine if the privacy program plan is approved by a senior official with responsibility and accountability for the privacy risk being incurred by organizational operations (including, mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.'),
('004387','draft','2022-03-03','DISA','policy','Disseminate an organization-wide privacy program plan that provides an overview of the agency''s privacy program and is approved by a senior official with responsibility and accountability for the privacy risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.','PM-18a.06','N/A','Determine if the privacy program plan is approved by a senior official with responsibility and accountability for the privacy risk being incurred by organizational operations (including, mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.'),
('004388','draft','2022-03-03','DISA','policy','Update the plan on an organization-defined frequency.','PM-18a.06','N/A','Determine if the privacy program plan is approved by a senior official with responsibility and accountability for the privacy risk being incurred by organizational operations (including, mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation.'),
('004389','draft','2022-03-03','DISA','policy','Update the plan to address changes in federal privacy laws and policy and organizational changes and problems identified during plan implementation or privacy control assessments.','PM-18b.','N/A','Determine if: - the privacy program plan is updated [PM-18_ODP; the frequency of updates to the privacy program plan is defined]. - the privacy program plan is updated to address changes in federal privacy laws and policies. - the privacy program plan is updated to address organizational changes. - the privacy program plan is updated to address problems identified during plan implementation or privacy control assessments.'),
('004390','draft','2022-03-03','DISA','policy','Appoint a Senior Agency Official for Privacy with the authority, mission, accountability, and resources to coordinate applicable privacy requirements.','PM-19','N/A','Determine if: - a senior agency official for privacy with authority, mission, accountability, and resources is appointed. - the senior agency official for privacy coordinates applicable privacy requirements. - the senior agency official for privacy develops applicable privacy requirements. - the senior agency official for privacy implements applicable privacy requirements. - the senior agency official for privacy manages privacy risks through the organization-wide privacy program.'),
('004391','draft','2022-03-03','DISA','policy','Appoint a Senior Agency Official for Privacy with the authority, mission, accountability, and resources to develop applicable privacy requirements.','PM-19','N/A','Determine if: - a senior agency official for privacy with authority, mission, accountability, and resources is appointed. - the senior agency official for privacy coordinates applicable privacy requirements. - the senior agency official for privacy develops applicable privacy requirements. - the senior agency official for privacy implements applicable privacy requirements. - the senior agency official for privacy manages privacy risks through the organization-wide privacy program.'),
('004392','draft','2022-03-03','DISA','policy','Appoint a Senior Agency Official for Privacy with the authority, mission, accountability, and resources to implement applicable privacy requirements.','PM-19','N/A','Determine if: - a senior agency official for privacy with authority, mission, accountability, and resources is appointed. - the senior agency official for privacy coordinates applicable privacy requirements. - the senior agency official for privacy develops applicable privacy requirements. - the senior agency official for privacy implements applicable privacy requirements. - the senior agency official for privacy manages privacy risks through the organization-wide privacy program.'),
('004393','draft','2022-03-03','DISA','policy','Appoint a Senior Agency Official for Privacy with the authority, mission, accountability, and resources to manage privacy risks through the organization-wide privacy program.','PM-19','N/A','Determine if: - a senior agency official for privacy with authority, mission, accountability, and resources is appointed. - the senior agency official for privacy coordinates applicable privacy requirements. - the senior agency official for privacy develops applicable privacy requirements. - the senior agency official for privacy implements applicable privacy requirements. - the senior agency official for privacy manages privacy risks through the organization-wide privacy program.'),
('004394','draft','2022-03-03','DISA','policy','Maintain a central resource webpage on the organization''s principle public website that serves as a central source of information about the organization''s privacy plan.','PM-20','N/A','Determine if: - a central resource webpage is maintained on the organization''s principal public website. - the webpage serves as a central source of information about the organization''s privacy program.'),
('004395','draft','2022-03-03','DISA','policy','Ensure that the public has access to information about organizational privacy activities.','PM-20a.','N/A','Determine if: - the webpage ensures that the public has access to information about organizational privacy activities. - the webpage ensures that the public can communicate with its senior agency official for privacy.'),
('004396','draft','2022-03-03','DISA','policy','Ensure that the public can communicate with its Senior Agency Official for Privacy.','PM-20a.','N/A','Determine if: - the webpage ensures that the public has access to information about organizational privacy activities. - the webpage ensures that the public can communicate with its senior agency official for privacy.'),
('004397','draft','2022-03-03','DISA','policy','Ensure that organizational privacy practices and reports are publicly available.','PM-20b.','N/A','Determine if: - the webpage ensures that organizational privacy practices are publicly available. - the webpage ensures that organizational privacy reports are publicly available.'),
('004398','draft','2022-03-03','DISA','policy','Employ publicly facing email addresses and/or phone lines to enable the public to provide feedback and/or direct questions to privacy offices regarding privacy practices.','PM-20c.','N/A','Determine if the webpage employs publicly facing email addresses and/or phone numbers to enable the public to provide feedback and/or direct questions to privacy offices regarding privacy practices.'),
('004399','draft','2022-03-03','DISA','policy','Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services that are written in plain language.','PM-20(01)(a)','N/A','Determine if: - the privacy policies are written in plain language. - the privacy policies are organized in a way that is easy to understand and navigate.'),
('004400','draft','2022-03-03','DISA','policy','Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services that are organized in a way that is easy to understand and navigate.','PM-20(01)(a)','N/A','Determine if: - the privacy policies are written in plain language. - the privacy policies are organized in a way that is easy to understand and navigate.'),
('004401','draft','2022-03-03','DISA','policy','Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services that provide information needed by the public to make an informed about whether and how to interact with the organization.','PM-20(01)(b)','N/A','Determine if: - the privacy policies provide the information needed by the public to make an informed decision about whether to interact with the organization. - the privacy policies provide the information needed by the public to make an informed decision about how to interact with the organization.'),
('004402','draft','2022-03-03','DISA','policy','Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services that are updated whenever the organization makes a substantive change to the practices it describes.','PM-20(01)(c)','N/A','Determine if: - the privacy policies are updated whenever the organization makes a substantive change to the practices it describes. - the privacy policies include a time/date stamp to inform the public of the date of the most recent changes.'),
('004403','draft','2022-03-03','DISA','policy','Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services that includes a time/date stamp to inform the public of the date of the most recent changes.','PM-20(01)(c)','N/A','Determine if: - the privacy policies are updated whenever the organization makes a substantive change to the practices it describes. - the privacy policies include a time/date stamp to inform the public of the date of the most recent changes.'),
('004404','draft','2022-03-03','DISA','policy','Develop an accurate accounting of disclosures of personally identifiable information.','PM-21a.','N/A','Determine if an accurate accounting of disclosures of personally identifiable information is developed and maintained.'),
('004405','draft','2022-03-03','DISA','policy','Maintain an accurate accounting of disclosures of personally identifiable information.','PM-21a.','N/A','Determine if an accurate accounting of disclosures of personally identifiable information is developed and maintained.'),
('004406','draft','2022-03-03','DISA','policy','Develop an accurate accounting of disclosures of personally identifiable information, including date, nature, and purpose of each disclosure of a record.','PM-21a.01','N/A','Determine if: - the accounting includes the date of each disclosure. - the accounting includes the nature of each disclosure. - the accounting includes the purpose of each disclosure.'),
('004407','draft','2022-03-03','DISA','policy','Maintain an accurate accounting of disclosures of personally identifiable information, including date, nature, and purpose of each disclosure of a record.','PM-21a.01','N/A','Determine if: - the accounting includes the date of each disclosure. - the accounting includes the nature of each disclosure. - the accounting includes the purpose of each disclosure.'),
('004408','draft','2022-03-03','DISA','policy','Develop an accurate accounting of disclosures of personally identifiable information, including name and address, or other contact information of the individual or organization to which the disclosure was made.','PM-21a.02','N/A','Determine if: - the accounting includes the name of the individual or organization to whom the disclosure was made. - the accounting includes the address or other contact information of the individual or organization to whom the disclosure was made.'),
('004409','draft','2022-03-03','DISA','policy','Maintain an accurate accounting of disclosures of personally identifiable information, including name and address, or other contact information of the individual or organization to which the disclosure was made.','PM-21a.02','N/A','Determine if: - the accounting includes the name of the individual or organization to whom the disclosure was made. - the accounting includes the address or other contact information of the individual or organization to whom the disclosure was made.'),
('004410','draft','2022-03-03','DISA','policy','Retain the accounting of disclosures for the length of the time the personally identifiable information is maintained or five years after the disclosure is made, whichever is longer.','PM-21b.','N/A','Determine if the accounting of disclosures is retained for the length of time that the personally identifiable information is maintained or five years after the disclosure is made, whichever is longer.'),
('004411','draft','2022-03-03','DISA','policy','Make the accounting of disclosures available to the individual to whom the personally identifiable information relates upon request.','PM-21c.','N/A','Determine if the accounting of disclosures is made available to the individual to whom the personally identifiable information relates upon request.'),
('004412','draft','2022-03-03','DISA','policy','Develop and document organization-wide policies for reviewing for the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle.','PM-22a.','N/A','Determine if: - the policies address reviewing the accuracy of personally identifiable information across the information life cycle. - the policies address reviewing the relevance of personally identifiable information across the information life cycle. - the policies address reviewing the timeliness of personally identifiable information across the information life cycle. - the policies address reviewing the completeness of personally identifiable information across the information life cycle. - the procedures address reviewing the accuracy of personally identifiable information across the information life cycle. - the procedures address reviewing the relevance of personally identifiable information across the information life cycle. - the procedures address reviewing the timeliness of personally identifiable information across the information life cycle. - the procedures address reviewing the completeness of personally identifiable information across the information life cycle.'),
('004413','draft','2022-03-03','DISA','policy','Develop and document organization-wide procedures for reviewing for the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle.','PM-22a.','N/A','Determine if: - the policies address reviewing the accuracy of personally identifiable information across the information life cycle. - the policies address reviewing the relevance of personally identifiable information across the information life cycle. - the policies address reviewing the timeliness of personally identifiable information across the information life cycle. - the policies address reviewing the completeness of personally identifiable information across the information life cycle. - the procedures address reviewing the accuracy of personally identifiable information across the information life cycle. - the procedures address reviewing the relevance of personally identifiable information across the information life cycle. - the procedures address reviewing the timeliness of personally identifiable information across the information life cycle. - the procedures address reviewing the completeness of personally identifiable information across the information life cycle.'),
('004414','draft','2022-03-03','DISA','policy','Develop and document organization-wide policies for correcting or deleting inaccurate or outdated personally identifiable information.','PM-22b.','N/A','Determine if: - the policies address correcting or deleting inaccurate or outdated personally identifiable information. - the procedures address correcting or deleting inaccurate or outdated personally identifiable information.'),
('004415','draft','2022-03-03','DISA','policy','Develop and document organization-wide procedures for correcting or deleting inaccurate or outdated personally identifiable information.','PM-22b.','N/A','Determine if: - the policies address correcting or deleting inaccurate or outdated personally identifiable information. - the procedures address correcting or deleting inaccurate or outdated personally identifiable information.'),
('004416','draft','2022-03-03','DISA','policy','Develop and document organization-wide policies for disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities.','PM-22c.','N/A','Determine if: - the policies address disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities. - the procedures address disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities.'),
('004417','draft','2022-03-03','DISA','policy','Develop and document organization-wide procedures for disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities.','PM-22c.','N/A','Determine if: - the policies address disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities. - the procedures address disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities.'),
('004418','draft','2022-03-03','DISA','policy','Develop and document organization-wide policies for appeals of adverse decisions on correction or deletion requests.','PM-22d.','N/A','Determine if: - the policies address appeals of adverse decisions on correction or deletion requests. - the procedures address appeals of adverse decisions on correction or deletion requests.'),
('004419','draft','2022-03-03','DISA','policy','Develop and document organization-wide procedures for appeals of adverse decisions on correction or deletion requests.','PM-22d.','N/A','Determine if: - the policies address appeals of adverse decisions on correction or deletion requests. - the procedures address appeals of adverse decisions on correction or deletion requests.'),
('004420','draft','2022-03-03','DISA','policy','Establish a Data Governance Body consisting of organization-defined roles with organization-defined responsibilities.','PM-23','N/A','Determine if a Data Governance Body consisting of [PM-23_ODP[01]; the roles of a Data Governance Body are defined] with [PM-23_ODP[02]; the responsibilities of a Data Governance Body are defined] is established.'),
('004421','draft','2022-03-03','DISA','policy','Defines the roles that are established by the Data Governance Body.','PM-23','N/A','Determine if a Data Governance Body consisting of [PM-23_ODP[01]; the roles of a Data Governance Body are defined] with [PM-23_ODP[02]; the responsibilities of a Data Governance Body are defined] is established.'),
('004422','draft','2022-03-03','DISA','policy','Defines the responsibilities the Data Governance Body establishes.','PM-23','N/A','Determine if a Data Governance Body consisting of [PM-23_ODP[01]; the roles of a Data Governance Body are defined] with [PM-23_ODP[02]; the responsibilities of a Data Governance Body are defined] is established.'),
('004423','draft','2022-03-03','DISA','policy','Establish a Data Integrity Board to review proposals to conduct or participate in a matching program.','PM-24a.','N/A','Determine if the Data Integrity Board reviews proposals to conduct or participate in a matching program.'),
('004424','draft','2022-03-03','DISA','policy','Establish a Data Integrity Board to conduct an annual review of all matching programs in which the agency has participated.','PM-24b.','N/A','Determine if the Data Integrity Board conducts an annual review of all matching programs in which the agency has participated.'),
('004425','draft','2022-03-03','DISA','policy','Develop and document policies that address the use of personally identifiable information for internal testing, training, and research.','PM-25a.','N/A','Determine if: - policies that address the use of personally identifiable information for internal testing are developed and documented. - policies that address the use of personally identifiable information for internal training are developed and documented. - policies that address the use of personally identifiable information for internal research are developed and documented. - procedures that address the use of personally identifiable information for internal testing are developed and documented. - procedures that address the use of personally identifiable information for internal training are developed and documented. - procedures that address the use of personally identifiable information for internal research are developed and documented. - policies that address the use of personally identifiable information for internal testing are implemented. - policies that address the use of personally identifiable information for training are implemented. - policies that address the use of personally identifiable information for research are implemented. - procedures that address the use of personally identifiable information for internal testing are implemented. - procedures that address the use of personally identifiable information for training are implemented. - procedures that address the use of personally identifiable information for research are implemented.'),
('004426','draft','2022-03-03','DISA','policy','Develop and document procedures that address the use of personally identifiable information for internal testing, training, and research.','PM-25a.','N/A','Determine if: - policies that address the use of personally identifiable information for internal testing are developed and documented. - policies that address the use of personally identifiable information for internal training are developed and documented. - policies that address the use of personally identifiable information for internal research are developed and documented. - procedures that address the use of personally identifiable information for internal testing are developed and documented. - procedures that address the use of personally identifiable information for internal training are developed and documented. - procedures that address the use of personally identifiable information for internal research are developed and documented. - policies that address the use of personally identifiable information for internal testing are implemented. - policies that address the use of personally identifiable information for training are implemented. - policies that address the use of personally identifiable information for research are implemented. - procedures that address the use of personally identifiable information for internal testing are implemented. - procedures that address the use of personally identifiable information for training are implemented. - procedures that address the use of personally identifiable information for research are implemented.'),
('004427','draft','2022-03-03','DISA','policy','Implement policies that address the use of personally identifiable information for internal testing, training, and research.','PM-25a.','N/A','Determine if: - policies that address the use of personally identifiable information for internal testing are developed and documented. - policies that address the use of personally identifiable information for internal training are developed and documented. - policies that address the use of personally identifiable information for internal research are developed and documented. - procedures that address the use of personally identifiable information for internal testing are developed and documented. - procedures that address the use of personally identifiable information for internal training are developed and documented. - procedures that address the use of personally identifiable information for internal research are developed and documented. - policies that address the use of personally identifiable information for internal testing are implemented. - policies that address the use of personally identifiable information for training are implemented. - policies that address the use of personally identifiable information for research are implemented. - procedures that address the use of personally identifiable information for internal testing are implemented. - procedures that address the use of personally identifiable information for training are implemented. - procedures that address the use of personally identifiable information for research are implemented.'),
('004428','draft','2022-03-03','DISA','policy','Implement procedures that address the use of personally identifiable information for internal testing, training, and research.','PM-25a.','N/A','Determine if: - policies that address the use of personally identifiable information for internal testing are developed and documented. - policies that address the use of personally identifiable information for internal training are developed and documented. - policies that address the use of personally identifiable information for internal research are developed and documented. - procedures that address the use of personally identifiable information for internal testing are developed and documented. - procedures that address the use of personally identifiable information for internal training are developed and documented. - procedures that address the use of personally identifiable information for internal research are developed and documented. - policies that address the use of personally identifiable information for internal testing are implemented. - policies that address the use of personally identifiable information for training are implemented. - policies that address the use of personally identifiable information for research are implemented. - procedures that address the use of personally identifiable information for internal testing are implemented. - procedures that address the use of personally identifiable information for training are implemented. - procedures that address the use of personally identifiable information for research are implemented.'),
('004429','draft','2022-03-03','DISA','policy','Limit or minimize the amount of personally identifiable information used for internal testing, training, and research purposes.','PM-25b.','N/A','Determine if: - the amount of personally identifiable information used for internal testing purposes is limited or minimized. - the amount of personally identifiable information used for internal training purposes is limited or minimized. - the amount of personally identifiable information used for internal research purposes is limited or minimized.'),
('004430','draft','2022-03-03','DISA','policy','Authorize the use of personally identifiable information when such information is required for internal testing, training, and research.','PM-25c.','N/A','Determine if: - the required use of personally identifiable information for internal testing is authorized. - the required use of personally identifiable information for internal training is authorized. - the required use of personally identifiable information for internal research is authorized.'),
('004431','draft','2022-03-03','DISA','policy','Review and update policies on an organization-defined frequency.','PM-25d.','N/A','Determine if: - policies are reviewed [PM-25_ODP[01]; the frequency for reviewing policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - policies are updated [PM-25_ODP[02]; the frequency for updating policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are reviewed [PM-25_ODP[03]; the frequency for reviewing procedures that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are updated [PM-25_ODP[04]; the frequency for updating procedures that address the use of personally identifiable information for internal testing, training, and research is defined].'),
('004432','draft','2022-03-03','DISA','policy','Defines the frequency of which the policies should be reviewed and updated.','PM-25d.','N/A','Determine if: - policies are reviewed [PM-25_ODP[01]; the frequency for reviewing policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - policies are updated [PM-25_ODP[02]; the frequency for updating policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are reviewed [PM-25_ODP[03]; the frequency for reviewing procedures that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are updated [PM-25_ODP[04]; the frequency for updating procedures that address the use of personally identifiable information for internal testing, training, and research is defined].'),
('004433','draft','2022-03-04','DISA','policy','Review and update procedures on an organization-defined frequency.','PM-25d.','N/A','Determine if: - policies are reviewed [PM-25_ODP[01]; the frequency for reviewing policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - policies are updated [PM-25_ODP[02]; the frequency for updating policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are reviewed [PM-25_ODP[03]; the frequency for reviewing procedures that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are updated [PM-25_ODP[04]; the frequency for updating procedures that address the use of personally identifiable information for internal testing, training, and research is defined].'),
('004434','draft','2022-03-04','DISA','policy','Defines the frequency of which the procedures should be reviewed and updated.','PM-25d.','N/A','Determine if: - policies are reviewed [PM-25_ODP[01]; the frequency for reviewing policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - policies are updated [PM-25_ODP[02]; the frequency for updating policies that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are reviewed [PM-25_ODP[03]; the frequency for reviewing procedures that address the use of personally identifiable information for internal testing, training, and research is defined]. - procedures are updated [PM-25_ODP[04]; the frequency for updating procedures that address the use of personally identifiable information for internal testing, training, and research is defined].'),
('004435','draft','2022-03-04','DISA','policy','Implement a process for receiving and responding to complaints, concerns or questions from individuals about the organizational security practices.','PM-26','N/A','Determine if: - a process for receiving complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented. - a process for responding to complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented.'),
('004436','draft','2022-03-04','DISA','policy','Implement a process for receiving and responding to complaints, concerns or questions from individuals about the organizational privacy practices.','PM-26','N/A','Determine if: - a process for receiving complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented. - a process for responding to complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented.'),
('004437','draft','2022-03-04','DISA','policy','Implement mechanisms that are easy to use.','PM-26a.','N/A','Determine if: - the complaint management process includes mechanisms that are easy to use by the public. - the complaint management process includes mechanisms that are readily accessible by the public.'),
('004438','draft','2022-03-04','DISA','policy','Implement mechanisms that are readily available by the public.','PM-26a.','N/A','Determine if: - the complaint management process includes mechanisms that are easy to use by the public. - the complaint management process includes mechanisms that are readily accessible by the public.'),
('004439','draft','2022-03-04','DISA','policy','Implement all information necessary for successfully filing complaints.','PM-26b.','N/A','Determine if the complaint management process includes all information necessary for successfully filing complaints.'),
('004440','draft','2022-03-04','DISA','policy','Implement tracking mechanisms to ensure all complaints received are reviewed and appropriately addressed within an organization-defined time period.','PM-26c.','N/A','Determine if: - the complaint management process includes tracking mechanisms to ensure that all complaints are reviewed within [PM-26_ODP[01]; the time period in which complaints (including concerns or questions) from individuals are to be reviewed is defined]. - the complaint management process includes tracking mechanisms to ensure that all complaints are addressed within [PM-26_ODP[02]; the time period in which complaints (including concerns or questions) from individuals are to be addressed is defined].'),
('004441','draft','2022-03-04','DISA','policy','Defines the time period of which the tracking mechanisms to ensure all complaints received are reviewed and addressed.','PM-26c.','N/A','Determine if: - the complaint management process includes tracking mechanisms to ensure that all complaints are reviewed within [PM-26_ODP[01]; the time period in which complaints (including concerns or questions) from individuals are to be reviewed is defined]. - the complaint management process includes tracking mechanisms to ensure that all complaints are addressed within [PM-26_ODP[02]; the time period in which complaints (including concerns or questions) from individuals are to be addressed is defined].'),
('004442','draft','2022-03-04','DISA','policy','Implement acknowledgement of receipt of complaints, concerns, or questions from individuals within an organization-defined time period.','PM-26d.','N/A','Determine if the complaint management process includes acknowledging the receipt of complaints, concerns, or questions from individuals within [PM-26_ODP[03]; the time period for acknowledging the receipt of complaints is defined].'),
('004443','draft','2022-03-04','DISA','policy','Defines the time period for acknowledging the receipt of complaints, concerns, or questions from individuals.','PM-26d.','N/A','Determine if the complaint management process includes acknowledging the receipt of complaints, concerns, or questions from individuals within [PM-26_ODP[03]; the time period for acknowledging the receipt of complaints is defined].'),
('004444','draft','2022-03-04','DISA','policy','Implement response to complaints, concerns, or questions from individuals within an organization-defined time period.','PM-26e.','N/A','Determine if the complaint management process includes responding to complaints, concerns, or questions from individuals within [PM-26_ODP[04]; the time period for responding to complaints is defined].'),
('004445','draft','2022-03-04','DISA','policy','Defines the time period for response to complaints, concerns, or questions from individuals.','PM-26e.','N/A','Determine if the complaint management process includes responding to complaints, concerns, or questions from individuals within [PM-26_ODP[04]; the time period for responding to complaints is defined].'),
('004446','draft','2022-03-04','DISA','policy','Develop organization-defined privacy reports.',NULL,'N/A',NULL),
('004447','draft','2022-03-04','DISA','policy','Defines the privacy reports that are to be developed.',NULL,'N/A',NULL),
('004448','draft','2022-03-04','DISA','policy','Disseminate privacy reports to organization-defined oversight bodies to demonstrate accountability with statutory, regulatory, and policy privacy program mandates.','PM-27a.01','N/A','Determine if the privacy reports are disseminated to [PM-27_ODP[02]; privacy oversight bodies are defined] to demonstrate accountability with statutory, regulatory, and policy privacy mandates.'),
('004449','draft','2022-03-04','DISA','policy','Develop privacy reports for organization-defined officials and other personnel with responsibility for monitoring privacy program progress and compliance.','PM-27a.02','N/A','Determine if: - the privacy reports are disseminated to [PM-27_ODP[03]; officials responsible for monitoring privacy program compliance are defined]. - the privacy reports are disseminated to other personnel responsible for monitoring privacy program compliance.'),
('004450','draft','2022-03-04','DISA','policy','Disseminate privacy reports for organization-defined officials and other personnel with responsibility for monitoring privacy program compliance.','PM-27a.02','N/A','Determine if: - the privacy reports are disseminated to [PM-27_ODP[03]; officials responsible for monitoring privacy program compliance are defined]. - the privacy reports are disseminated to other personnel responsible for monitoring privacy program compliance.'),
('004451','draft','2022-03-04','DISA','policy','Defines the officials responsible for monitoring privacy program compliance.','PM-27a.02','N/A','Determine if: - the privacy reports are disseminated to [PM-27_ODP[03]; officials responsible for monitoring privacy program compliance are defined]. - the privacy reports are disseminated to other personnel responsible for monitoring privacy program compliance.'),
('004452','draft','2022-03-04','DISA','policy','Review and update privacy reports on an organization-defined frequency.','PM-27b.','N/A','Determine if the privacy reports are reviewed and updated [PM-27_ODP[04]; the frequency for reviewing and updating privacy reports is defined].'),
('004453','draft','2022-03-04','DISA','policy','Defines the frequency of which the privacy reports are reviewed and updated.','PM-27b.','N/A','Determine if the privacy reports are reviewed and updated [PM-27_ODP[04]; the frequency for reviewing and updating privacy reports is defined].'),
('004454','draft','2022-03-04','DISA','policy','Identify and document assumptions affecting risk assessments, risk response, and risk monitoring.','PM-28a.01','N/A','Determine if: - assumptions affecting risk assessments are identified and documented. - assumptions affecting risk responses are identified and documented. - assumptions affecting risk monitoring are identified and documented.'),
('004455','draft','2022-03-04','DISA','policy','Identify and document constraints affecting risk assessments, risk response, and risk monitoring.','PM-28a.02','N/A','Determine if: - constraints affecting risk assessments are identified and documented. - constraints affecting risk responses are identified and documented. - constraints affecting risk monitoring are identified and documented.'),
('004456','draft','2022-03-04','DISA','policy','Identify and document priorities and trade-offs considered by the organization for managing risk.','PM-28a.03','N/A','Determine if: - priorities considered by the organization for managing risk are identified and documented. - trade-offs considered by the organization for managing risk are identified and documented.'),
('004457','draft','2022-03-04','DISA','policy','Identify and document the organizational risk tolerance.','PM-28a.04','N/A','Determine if organizational risk tolerance is identified and documented.'),
('004458','draft','2022-03-04','DISA','policy','Distribute the results of risk framing activities to organization-defined personnel.','PM-28b.','N/A','Determine if the results of risk framing activities are distributed to [PM-28_ODP[01]; the personnel to receive the results of risk framing activities is/are defined].'),
('004459','draft','2022-03-04','DISA','policy','Defines the personnel to distribute the results of risk framing activities.','PM-28b.','N/A','Determine if the results of risk framing activities are distributed to [PM-28_ODP[01]; the personnel to receive the results of risk framing activities is/are defined].'),
('004460','draft','2022-03-04','DISA','policy','Review and update risk framing considerations on an organization-defined frequency.','PM-28c.','N/A','Determine if risk framing considerations are reviewed and updated [PM-28_ODP[02]; the frequency for reviewing and updating risk framing considerations is defined].'),
('004461','draft','2022-03-04','DISA','policy','Defines the frequency for reviewing and updating risk framing considerations.','PM-28c.','N/A','Determine if risk framing considerations are reviewed and updated [PM-28_ODP[02]; the frequency for reviewing and updating risk framing considerations is defined].'),
('004462','draft','2022-03-04','DISA','policy','Appoint a Senior Accountable Official for Risk Management to align organizational information security management processes with strategic, operational, and budgetary planning processes.','PM-29a.','N/A','Determine if: - a Senior Accountable Official for Risk Management is appointed. - a Senior Accountable Official for Risk Management aligns information security and privacy management processes with strategic, operational, and budgetary planning processes.'),
('004463','draft','2022-03-04','DISA','policy','Appoint a Senior Accountable Official for Risk Management to align organizational information privacy management processes with strategic, operational, and budgetary planning processes.','PM-29a.','N/A','Determine if: - a Senior Accountable Official for Risk Management is appointed. - a Senior Accountable Official for Risk Management aligns information security and privacy management processes with strategic, operational, and budgetary planning processes.'),
('004464','draft','2022-03-04','DISA','policy','Establish a Risk Executive (function) to view and analyze risk from an organization-wide perspective.','PM-29b.','N/A','Determine if: - a Risk Executive (function) is established. - a Risk Executive (function) views and analyzes risk from an organization-wide perspective. - a Risk Executive (function) ensures that the management of risk is consistent across the organization.'),
('004465','draft','2022-03-04','DISA','policy','Establish a Risk Executive (function) to ensure management of risk is consistent across the organization.','PM-29b.','N/A','Determine if: - a Risk Executive (function) is established. - a Risk Executive (function) views and analyzes risk from an organization-wide perspective. - a Risk Executive (function) ensures that the management of risk is consistent across the organization.'),
('004466','draft','2022-03-04','DISA','policy','Develop an organization-wide strategy for managing supply chain risks associated with the development of systems, system components, and system services.','PM-30a.','N/A','Determine if: - an organization-wide strategy for managing supply chain risks is developed. - the supply chain risk management strategy addresses risks associated with the development of systems. - the supply chain risk management strategy addresses risks associated with the development of system components. - the supply chain risk management strategy addresses risks associated with the development of system services. - the supply chain risk management strategy addresses risks associated with the acquisition of systems. - the supply chain risk management strategy addresses risks associated with the acquisition of system components. - the supply chain risk management strategy addresses risks associated with the acquisition of system services. - the supply chain risk management strategy addresses risks associated with the maintenance of systems. - the supply chain risk management strategy addresses risks associated with the maintenance of system components. - the supply chain risk management strategy addresses risks associated with the maintenance of system services. - the supply chain risk management strategy addresses risks associated with the disposal of systems. - the supply chain risk management strategy addresses risks associated with the disposal of system components. - the supply chain risk management strategy addresses risks associated with the disposal of system services.'),
('004467','draft','2022-03-04','DISA','policy','Develop an organization-wide strategy for managing supply chain risks associated with the acquisition of systems, system components, and system services.','PM-30a.','N/A','Determine if: - an organization-wide strategy for managing supply chain risks is developed. - the supply chain risk management strategy addresses risks associated with the development of systems. - the supply chain risk management strategy addresses risks associated with the development of system components. - the supply chain risk management strategy addresses risks associated with the development of system services. - the supply chain risk management strategy addresses risks associated with the acquisition of systems. - the supply chain risk management strategy addresses risks associated with the acquisition of system components. - the supply chain risk management strategy addresses risks associated with the acquisition of system services. - the supply chain risk management strategy addresses risks associated with the maintenance of systems. - the supply chain risk management strategy addresses risks associated with the maintenance of system components. - the supply chain risk management strategy addresses risks associated with the maintenance of system services. - the supply chain risk management strategy addresses risks associated with the disposal of systems. - the supply chain risk management strategy addresses risks associated with the disposal of system components. - the supply chain risk management strategy addresses risks associated with the disposal of system services.'),
('004468','draft','2022-03-04','DISA','policy','Develop an organization-wide strategy for managing supply chain risks associated with the maintenance of systems, system components, and system services.','PM-30a.','N/A','Determine if: - an organization-wide strategy for managing supply chain risks is developed. - the supply chain risk management strategy addresses risks associated with the development of systems. - the supply chain risk management strategy addresses risks associated with the development of system components. - the supply chain risk management strategy addresses risks associated with the development of system services. - the supply chain risk management strategy addresses risks associated with the acquisition of systems. - the supply chain risk management strategy addresses risks associated with the acquisition of system components. - the supply chain risk management strategy addresses risks associated with the acquisition of system services. - the supply chain risk management strategy addresses risks associated with the maintenance of systems. - the supply chain risk management strategy addresses risks associated with the maintenance of system components. - the supply chain risk management strategy addresses risks associated with the maintenance of system services. - the supply chain risk management strategy addresses risks associated with the disposal of systems. - the supply chain risk management strategy addresses risks associated with the disposal of system components. - the supply chain risk management strategy addresses risks associated with the disposal of system services.'),
('004469','draft','2022-03-04','DISA','policy','Develop an organization-wide strategy for managing supply chain risks associated with the disposal of systems, system components, and system services.','PM-30a.','N/A','Determine if: - an organization-wide strategy for managing supply chain risks is developed. - the supply chain risk management strategy addresses risks associated with the development of systems. - the supply chain risk management strategy addresses risks associated with the development of system components. - the supply chain risk management strategy addresses risks associated with the development of system services. - the supply chain risk management strategy addresses risks associated with the acquisition of systems. - the supply chain risk management strategy addresses risks associated with the acquisition of system components. - the supply chain risk management strategy addresses risks associated with the acquisition of system services. - the supply chain risk management strategy addresses risks associated with the maintenance of systems. - the supply chain risk management strategy addresses risks associated with the maintenance of system components. - the supply chain risk management strategy addresses risks associated with the maintenance of system services. - the supply chain risk management strategy addresses risks associated with the disposal of systems. - the supply chain risk management strategy addresses risks associated with the disposal of system components. - the supply chain risk management strategy addresses risks associated with the disposal of system services.'),
('004470','draft','2022-03-04','DISA','policy','Implement the supply chain risk management strategy consistently across the organization.','PM-30b.','N/A','Determine if the supply chain risk management strategy is implemented consistently across the organization.'),
('004471','draft','2022-03-04','DISA','policy','Review and update the supply chain risk management strategy on an organization-defined frequency or as required, to address organizational changes.','PM-30c.','N/A','Determine if the supply chain risk management strategy is reviewed and updated [PM-30_ODP; the frequency for reviewing and updating the supply chain risk management strategy is defined] or as required to address organizational changes.'),
('004472','draft','2022-03-04','DISA','policy','Defines the frequency of which the supply chain risk management strategy will be reviewed and updated.','PM-30c.','N/A','Determine if the supply chain risk management strategy is reviewed and updated [PM-30_ODP; the frequency for reviewing and updating the supply chain risk management strategy is defined] or as required to address organizational changes.'),
('004473','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy establishing organization-defined metrics to be monitored.','PM-31a.','N/A','Determine if continuous monitoring programs are implemented that include establishing [PM-31_ODP[01]; the metrics for organization-wide continuous monitoring are defined] to be monitored.'),
('004474','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include establishing organization-wide metrics to be monitored.','PM-31a.','N/A','Determine if continuous monitoring programs are implemented that include establishing [PM-31_ODP[01]; the metrics for organization-wide continuous monitoring are defined] to be monitored.'),
('004475','draft','2022-03-04','DISA','policy','Defines the metrics for developing and implementing continuous monitoring programs.','PM-31a.','N/A','Determine if continuous monitoring programs are implemented that include establishing [PM-31_ODP[01]; the metrics for organization-wide continuous monitoring are defined] to be monitored.'),
('004476','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy establishing organization-defined frequencies for monitoring.','PM-31b.','N/A','Determine if: - continuous monitoring programs are implemented that establish [PM-31_ODP[02]; the frequency for monitoring is defined] for monitoring. - continuous monitoring programs are implemented that establish [PM-31_ODP[03]; the frequency for assessing control effectiveness is defined] for assessment of control effectiveness.'),
('004477','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy establishing organization-defined frequencies for assessment of control effectiveness.','PM-31b.','N/A','Determine if: - continuous monitoring programs are implemented that establish [PM-31_ODP[02]; the frequency for monitoring is defined] for monitoring. - continuous monitoring programs are implemented that establish [PM-31_ODP[03]; the frequency for assessing control effectiveness is defined] for assessment of control effectiveness.'),
('004478','draft','2022-03-04','DISA','policy','Defines the frequencies for developing and implementing continuous monitoring programs for monitoring.','PM-31b.','N/A','Determine if: - continuous monitoring programs are implemented that establish [PM-31_ODP[02]; the frequency for monitoring is defined] for monitoring. - continuous monitoring programs are implemented that establish [PM-31_ODP[03]; the frequency for assessing control effectiveness is defined] for assessment of control effectiveness.'),
('004479','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include establishing organization-wide frequencies for monitoring.','PM-31b.','N/A','Determine if: - continuous monitoring programs are implemented that establish [PM-31_ODP[02]; the frequency for monitoring is defined] for monitoring. - continuous monitoring programs are implemented that establish [PM-31_ODP[03]; the frequency for assessing control effectiveness is defined] for assessment of control effectiveness.'),
('004480','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include establishing organization-wide frequencies for assessment of control effectiveness.','PM-31b.','N/A','Determine if: - continuous monitoring programs are implemented that establish [PM-31_ODP[02]; the frequency for monitoring is defined] for monitoring. - continuous monitoring programs are implemented that establish [PM-31_ODP[03]; the frequency for assessing control effectiveness is defined] for assessment of control effectiveness.'),
('004481','draft','2022-03-04','DISA','policy','Defines the frequencies for developing and implementing continuous monitoring programs for assessment of control effectiveness.','PM-31b.','N/A','Determine if: - continuous monitoring programs are implemented that establish [PM-31_ODP[02]; the frequency for monitoring is defined] for monitoring. - continuous monitoring programs are implemented that establish [PM-31_ODP[03]; the frequency for assessing control effectiveness is defined] for assessment of control effectiveness.'),
('004482','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy for ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy.','PM-31c.','N/A','Determine if continuous monitoring programs are implemented that include monitoring [PM-31_ODP[01]; the metrics for organization-wide continuous monitoring are defined] on an ongoing basis in accordance with the continuous monitoring strategy.'),
('004483','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy.','PM-31c.','N/A','Determine if continuous monitoring programs are implemented that include monitoring [PM-31_ODP[01]; the metrics for organization-wide continuous monitoring are defined] on an ongoing basis in accordance with the continuous monitoring strategy.'),
('004484','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy for correlation and analysis of information generated by control assessments and monitoring.','PM-31d.','N/A','Determine if: - continuous monitoring programs are implemented that include correlating information generated by control assessments and monitoring. - continuous monitoring programs are implemented that include analyzing information generated by control assessments and monitoring.'),
('004485','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include correlation and analysis of information generated by control assessments and monitoring.','PM-31d.','N/A','Determine if: - continuous monitoring programs are implemented that include correlating information generated by control assessments and monitoring. - continuous monitoring programs are implemented that include analyzing information generated by control assessments and monitoring.'),
('004486','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy for response actions to address results of the analysis of control assessment and monitoring information.','PM-31e.','N/A','Determine if: - continuous monitoring programs are implemented that include response actions to address the analysis of control assessment information. - continuous monitoring programs are implemented that include response actions to address the analysis of monitoring information.'),
('004487','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include response actions to address results of the analysis of control assessment and monitoring information.','PM-31e.','N/A','Determine if: - continuous monitoring programs are implemented that include response actions to address the analysis of control assessment information. - continuous monitoring programs are implemented that include response actions to address the analysis of monitoring information.'),
('004488','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy for reporting the security status of organizational systems to organization-defined personnel or roles on an organization-defined frequency.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004489','draft','2022-03-04','DISA','policy','Develop an organization-wide continuous monitoring strategy for reporting the privacy status of organizational systems to organization-defined personnel or roles on an organization-defined frequency.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004490','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include reporting the security status of organizational systems to organization-defined personnel or roles on an organization-defined frequency.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004491','draft','2022-03-04','DISA','policy','Implement continuous monitoring programs that include reporting the privacy status of organizational systems to organization-defined personnel or roles on an organization-defined frequency.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004492','draft','2022-03-04','DISA','policy','Defines the personnel or roles for whom to report the security status of organizational systems.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004493','draft','2022-03-04','DISA','policy','Defines the personnel or roles for whom to report the privacy status of organizational systems.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004494','draft','2022-03-04','DISA','policy','Defines the frequency of reporting the security status of organizational systems to organization-defined personnel or roles.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004495','draft','2022-03-04','DISA','policy','Defines the frequency of reporting the privacy status of organizational systems to organization-defined personnel or roles.','PM-31f.','N/A','Determine if: - continuous monitoring programs are implemented that include reporting the security status of organizational systems to [PM-31_ODP[04]; the personnel or roles for reporting the security status of organizational systems to is/are defined] [PM-31_ODP[06]; the frequency at which to report the security status of organizational systems is defined]. - continuous monitoring programs are implemented that include reporting the privacy status of organizational systems to [PM-31_ODP[05]; the personnel or roles for reporting the privacy status of organizational systems to is/are defined] [PM-31_ODP[07]; the frequency at which to report the privacy status of organizational systems is defined].'),
('004496','draft','2022-03-04','DISA','policy','Analyze organization-defined systems or system components supporting mission essential services or functions to ensure that the information resources are being used consistent with their intended purpose.','PM-32','N/A','Determine if [PM-32_ODP; the systems or system components supporting mission-essential services or functions are defined] supporting mission-essential services or functions are analyzed to ensure that the information resources are being used in a manner that is consistent with their intended purpose.'),
('004497','draft','2022-03-04','DISA','policy','Defines the systems or system components that are used to analyze mission essential services or functions.','PM-32','N/A','Determine if [PM-32_ODP; the systems or system components supporting mission-essential services or functions are defined] supporting mission-essential services or functions are analyzed to ensure that the information resources are being used in a manner that is consistent with their intended purpose.'),
('004498','draft','2022-03-04','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level personnel security policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','PS-01a.01(b)','N/A','Determine if the [PS-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personnel security policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004499','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the development and documentation of the personnel security policy.','PS-01b.','N/A','Determine if the [PS-01_ODP[04]; an official to manage the personnel security policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures.'),
('004500','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the dissemination of the personnel security policy.','PS-01b.','N/A','Determine if the [PS-01_ODP[04]; an official to manage the personnel security policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures.'),
('004501','draft','2022-03-04','DISA','policy','Defines the official who will manage the personnel security policy.','PS-01b.','N/A','Determine if the [PS-01_ODP[04]; an official to manage the personnel security policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures.'),
('004502','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage development and documentation of the personnel security procedures.','PS-01b.','N/A','Determine if the [PS-01_ODP[04]; an official to manage the personnel security policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures.'),
('004503','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the dissemination of the personnel security procedures.','PS-01b.','N/A','Determine if the [PS-01_ODP[04]; an official to manage the personnel security policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures.'),
('004504','draft','2022-03-04','DISA','policy','Defines the official who will manage the personnel security procedures.','PS-01b.','N/A','Determine if the [PS-01_ODP[04]; an official to manage the personnel security policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personnel security policy and procedures.'),
('004505','draft','2022-03-04','DISA','policy','Review and update the current personnel security policy following organization-defined events.','PS-01c.01','N/A','Determine if: - the current personnel security policy is reviewed and updated [PS-01_ODP[05]; the frequency at which the current personnel security policy is reviewed and updated is defined]. - the current personnel security policy is reviewed and updated following [PS-01_ODP[06]; events that would require the current personnel security policy to be reviewed and updated are defined].'),
('004506','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current personnel security policy.','PS-01c.01','N/A','Determine if: - the current personnel security policy is reviewed and updated [PS-01_ODP[05]; the frequency at which the current personnel security policy is reviewed and updated is defined]. - the current personnel security policy is reviewed and updated following [PS-01_ODP[06]; events that would require the current personnel security policy to be reviewed and updated are defined].'),
('004507','draft','2022-03-04','DISA','policy','Review and update the current personnel security procedures following organization-defined events.','PS-01c.02','N/A','Determine if: - the current personnel security procedures are reviewed and updated [PS-01_ODP[07]; the frequency at which the current personnel security procedures are reviewed and updated is defined]. - the current personnel security procedures are reviewed and updated following [PS-01_ODP[08]; events that would require the personnel security procedures to be reviewed and updated are defined].'),
('004508','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current personnel security procedures.','PS-01c.02','N/A','Determine if: - the current personnel security procedures are reviewed and updated [PS-01_ODP[07]; the frequency at which the current personnel security procedures are reviewed and updated is defined]. - the current personnel security procedures are reviewed and updated following [PS-01_ODP[08]; events that would require the personnel security procedures to be reviewed and updated are defined].'),
('004509','draft','2022-03-04','DISA','policy','Verify that individuals accessing a system processing, storing, or transmitting organization-defined information types meet organization-defined citizenship requirements.','PS-03(04)','N/A','Determine if individuals accessing a system processing, storing, or transmitting [PS-03(04)_ODP[01]; information types that are processed, stored, or transmitted by a system that require individuals accessing the system to meet PS-03(04)_ODP[02] citizenship requirements are defined] meet [PS-03(04)_ODP[02]; citizenship requirements to be met by individuals to access a system processing, storing, or transmitting information are defined].'),
('004510','draft','2022-03-04','DISA','policy','Defines the information types that meet the organization-defined citizenship requirement.','PS-03(04)','N/A','Determine if individuals accessing a system processing, storing, or transmitting [PS-03(04)_ODP[01]; information types that are processed, stored, or transmitted by a system that require individuals accessing the system to meet PS-03(04)_ODP[02] citizenship requirements are defined] meet [PS-03(04)_ODP[02]; citizenship requirements to be met by individuals to access a system processing, storing, or transmitting information are defined].'),
('004511','draft','2022-03-04','DISA','policy','Defines the citizenship requirements for individuals accessing a system, storing, or transmitting organization-defined information types.','PS-03(04)','N/A','Determine if individuals accessing a system processing, storing, or transmitting [PS-03(04)_ODP[01]; information types that are processed, stored, or transmitted by a system that require individuals accessing the system to meet PS-03(04)_ODP[02] citizenship requirements are defined] meet [PS-03(04)_ODP[02]; citizenship requirements to be met by individuals to access a system processing, storing, or transmitting information are defined].'),
('004512','draft','2022-03-04','DISA','policy','Defines the automated mechanisms for notifying organization-defined personnel or roles of individual termination actions; and/or disable access to system resources.','PS-04(02)','N/A','Determine if [PS-04(02)_ODP[01]; automated mechanisms to notify personnel or roles of individual termination actions and/or to disable access to system resources are defined] are used to [PS-04(02)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {notify [PS-04(02)_ODP[03]; personnel or roles to be notified upon termination of an individual is/are defined (if selected)] of individual termination actions; disable access to system resources}].'),
('004513','draft','2022-03-04','DISA','policy','Verify that individuals requiring access to organizational information sign appropriate access agreements prior to being granted access.','PS-06c.01','N/A','Determine if individuals requiring access to organizational information and systems sign appropriate access agreements prior to being granted access.'),
('004514','draft','2022-03-04','DISA','policy','Verify that individuals requiring access to organizational systems sign appropriate access agreements prior to being granted access.','PS-06c.01','N/A','Determine if individuals requiring access to organizational information and systems sign appropriate access agreements prior to being granted access.'),
('004515','draft','2022-03-04','DISA','policy','Verify that individuals requiring access to organizational information re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or in accordance with organization-defined frequency.','PS-06c.02','N/A','Determine if individuals requiring access to organizational information and systems re-sign access agreements to maintain access to organizational systems when access agreements have been updated or [PS-06_ODP[02]; the frequency at which to re-sign access agreements to maintain access to organizational information is defined].'),
('004516','draft','2022-03-04','DISA','policy','Verify that individuals requiring access to organizational systems re-sign access agreements to maintain access to organizational information systems when access agreements have been updated or in accordance with organization-defined frequency.','PS-06c.02','N/A','Determine if individuals requiring access to organizational information and systems re-sign access agreements to maintain access to organizational systems when access agreements have been updated or [PS-06_ODP[02]; the frequency at which to re-sign access agreements to maintain access to organizational information is defined].'),
('004517','draft','2022-03-04','DISA','policy','Defines the frequency for individuals requiring access to organizational information to re-sign access agreements.','PS-06c.02','N/A','Determine if individuals requiring access to organizational information and systems re-sign access agreements to maintain access to organizational systems when access agreements have been updated or [PS-06_ODP[02]; the frequency at which to re-sign access agreements to maintain access to organizational information is defined].'),
('004518','draft','2022-03-04','DISA','policy','Defines the frequency for individuals requiring access to organizational systems to re-sign access agreements.','PS-06c.02','N/A','Determine if individuals requiring access to organizational information and systems re-sign access agreements to maintain access to organizational systems when access agreements have been updated or [PS-06_ODP[02]; the frequency at which to re-sign access agreements to maintain access to organizational information is defined].'),
('004519','draft','2022-03-04','DISA','policy','Require external providers to comply with personnel security policies established by the organization.','PS-07b.','N/A','Determine if external providers are required to comply with personnel security policies and procedures established by the organization.'),
('004520','draft','2022-03-04','DISA','policy','Require external providers to comply with personnel security procedures established by the organization.','PS-07b.','N/A','Determine if external providers are required to comply with personnel security policies and procedures established by the organization.'),
('004521','draft','2022-03-04','DISA','policy','Employ a formal sanctions process for individuals failing to comply with established information security policies.','PS-08a.','N/A','Determine if a formal sanctions process is employed for individuals failing to comply with established information security and privacy policies and procedures.'),
('004522','draft','2022-03-04','DISA','policy','Employ a formal sanctions process for individuals failing to comply with established information security procedures.','PS-08a.','N/A','Determine if a formal sanctions process is employed for individuals failing to comply with established information security and privacy policies and procedures.'),
('004523','draft','2022-03-04','DISA','policy','Incorporate security roles and responsibilities into organizational position descriptions.','PS-09','N/A','Determine if: - security roles and responsibilities are incorporated into organizational position descriptions. - privacy roles and responsibilities are incorporated into organizational position descriptions.'),
('004524','draft','2022-03-04','DISA','policy','Incorporate privacy roles and responsibilities into organizational position descriptions.','PS-09','N/A','Determine if: - security roles and responsibilities are incorporated into organizational position descriptions. - privacy roles and responsibilities are incorporated into organizational position descriptions.'),
('004525','draft','2022-03-04','DISA','policy','Develop and document organization-level; mission/business process-level; and/or system level personally identifiable information processing and transparency policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','PT-01a.01(a)','N/A','Determine if: - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses purpose. - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses scope. - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses roles. - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses responsibilities. - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses management commitment. - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses coordination among organizational entities. - the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy addresses compliance.'),
('004526','draft','2022-03-04','DISA','policy','Disseminate organization-level; mission/business process-level; and/or system level personally identifiable information processing and transparency policy to organization-defined personnel or roles.','PT-01a.','N/A','Determine if: - a personally identifiable information processing and transparency policy is developed and documented. - the personally identifiable information processing and transparency policy is disseminated to [PT-01_ODP[01]; personnel or roles to whom the personally identifiable information processing and transparency policy is to be disseminated is/are defined].'),
('004527','draft','2022-03-04','DISA','policy','Defines the personnel or roles to whom the organization-level; mission/business process-level; and/or system level personally identifiable information processing and transparency policy is to be disseminated.','PT-01a.','N/A','Determine if: - a personally identifiable information processing and transparency policy is developed and documented. - the personally identifiable information processing and transparency policy is disseminated to [PT-01_ODP[01]; personnel or roles to whom the personally identifiable information processing and transparency policy is to be disseminated is/are defined].'),
('004528','draft','2022-03-04','DISA','policy','Develop and document organization-level; mission/business process-level; and/or system level personally identifiable information processing and transparency policy that is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.','PT-01a.01(b)','N/A','Determine if the [PT-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] personally identifiable information processing and transparency policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004529','draft','2022-03-04','DISA','policy','Develop and document procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and the associated personally identifiable information processing and transparency controls.','PT-01a.02','N/A','Determine if: - personally identifiable information processing and transparency procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and associated personally identifiable information processing and transparency controls are developed and documented. - the personally identifiable information processing and transparency procedures are disseminated to [PT-01_ODP[02]; personnel or roles to whom the personally identifiable information processing and transparency procedures are to be disseminated is/are defined].'),
('004530','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the development and documentation of the personally identifiable information processing and transparency policy.','PT-01b.','N/A','Determine if the [PT-01_ODP[04]; an official to manage the personally identifiable information processing and transparency policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures.'),
('004531','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the development and documentation of the personally identifiable information processing and transparency procedures.','PT-01b.','N/A','Determine if the [PT-01_ODP[04]; an official to manage the personally identifiable information processing and transparency policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures.'),
('004532','draft','2022-03-04','DISA','policy','Defines the official designated to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures.','PT-01b.','N/A','Determine if the [PT-01_ODP[04]; an official to manage the personally identifiable information processing and transparency policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures.'),
('004533','draft','2022-03-04','DISA','policy','Review and update the current personally identifiable information processing and transparency policy on an organization-defined frequency.','PT-01c.01','N/A','Determine if: - the current personally identifiable information processing and transparency policy is reviewed and updated [PT-01_ODP[05]; the frequency at which the current personally identifiable information processing and transparency policy is reviewed and updated is defined]. - the current personally identifiable information processing and transparency policy is reviewed and updated following [PT-01_ODP[06]; events that would require the current personally identifiable information processing and transparency policy to be reviewed and updated are defined].'),
('004534','draft','2022-03-04','DISA','policy','Review and update the current personally identifiable information processing and transparency policy following organization-defined events.','PT-01c.01','N/A','Determine if: - the current personally identifiable information processing and transparency policy is reviewed and updated [PT-01_ODP[05]; the frequency at which the current personally identifiable information processing and transparency policy is reviewed and updated is defined]. - the current personally identifiable information processing and transparency policy is reviewed and updated following [PT-01_ODP[06]; events that would require the current personally identifiable information processing and transparency policy to be reviewed and updated are defined].'),
('004535','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current personally identifiable processing and transparency policy.','PT-01c.01','N/A','Determine if: - the current personally identifiable information processing and transparency policy is reviewed and updated [PT-01_ODP[05]; the frequency at which the current personally identifiable information processing and transparency policy is reviewed and updated is defined]. - the current personally identifiable information processing and transparency policy is reviewed and updated following [PT-01_ODP[06]; events that would require the current personally identifiable information processing and transparency policy to be reviewed and updated are defined].'),
('004536','draft','2022-03-04','DISA','policy','Review and update the current personally identifiable information processing and transparency procedures on an organization-defined frequency.','PT-01c.02','N/A','Determine if: - the current personally identifiable information processing and transparency procedures are reviewed and updated [PT-01_ODP[07]; the frequency at which the current personally identifiable information processing and transparency procedures are reviewed and updated is defined]. - the current personally identifiable information processing and transparency procedures are reviewed and updated following [PT-01_ODP[08]; events that would require the personally identifiable information processing and transparency procedures to be reviewed and updated are defined].'),
('004537','draft','2022-03-04','DISA','policy','Review and update the current personally identifiable information processing and transparency procedures following organization-defined events.','PT-01c.02','N/A','Determine if: - the current personally identifiable information processing and transparency procedures are reviewed and updated [PT-01_ODP[07]; the frequency at which the current personally identifiable information processing and transparency procedures are reviewed and updated is defined]. - the current personally identifiable information processing and transparency procedures are reviewed and updated following [PT-01_ODP[08]; events that would require the personally identifiable information processing and transparency procedures to be reviewed and updated are defined].'),
('004538','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current personally identifiable processing and transparency procedures.','PT-01c.02','N/A','Determine if: - the current personally identifiable information processing and transparency procedures are reviewed and updated [PT-01_ODP[07]; the frequency at which the current personally identifiable information processing and transparency procedures are reviewed and updated is defined]. - the current personally identifiable information processing and transparency procedures are reviewed and updated following [PT-01_ODP[08]; events that would require the personally identifiable information processing and transparency procedures to be reviewed and updated are defined].'),
('004539','draft','2022-03-04','DISA','policy','Determine and document the organization-defined authority that permits the organization-defined processing of personally identifiable information.','PT-02a.','N/A','Determine if the [PT-02_ODP[01]; the authority to permit the processing (defined in PT-02_ODP[02]) of personally identifiable information is defined] that permits the [PT-02_ODP[02]; the type of processing of personally identifiable information is defined] of personally identifiable information is determined and documented.'),
('004540','draft','2022-03-04','DISA','policy','Defines the authority who will permit the organization-defined processing of personally identifiable information.','PT-02a.','N/A','Determine if the [PT-02_ODP[01]; the authority to permit the processing (defined in PT-02_ODP[02]) of personally identifiable information is defined] that permits the [PT-02_ODP[02]; the type of processing of personally identifiable information is defined] of personally identifiable information is determined and documented.'),
('004541','draft','2022-03-04','DISA','policy','Defines the processing of the personally identifiable information.','PT-02a.','N/A','Determine if the [PT-02_ODP[01]; the authority to permit the processing (defined in PT-02_ODP[02]) of personally identifiable information is defined] that permits the [PT-02_ODP[02]; the type of processing of personally identifiable information is defined] of personally identifiable information is determined and documented.'),
('004542','draft','2022-03-04','DISA','policy','Restrict the organization-defined processing of personally identifiable information to only that which is authorized.','PT-02b.','N/A','Determine if the [PT-02_ODP[03]; the type of processing of personally identifiable information to be restricted is defined] of personally identifiable information is restricted to only that which is authorized.'),
('004543','draft','2022-03-04','DISA','policy','Defines the processing of the personally identifiable information to only that which is authorized.','PT-02b.','N/A','Determine if the [PT-02_ODP[03]; the type of processing of personally identifiable information to be restricted is defined] of personally identifiable information is restricted to only that which is authorized.'),
('004544','draft','2022-03-04','DISA','technical','Attach data tags containing organization-defined authorized processing to organization-defined elements of personally identifiable information.','PT-02(01)','N/A','Determine if data tags containing [PT-02(01)_ODP[01]; the authorized processing of personally identifiable information is defined] are attached to [PT-02(01)_ODP[02]; elements of personally identifiable information to be tagged are defined].'),
('004545','draft','2022-03-04','DISA','technical','Defines the authorized processing which will attach data tags to organization-defined elements of personally identifiable information.','PT-02(01)','N/A','Determine if data tags containing [PT-02(01)_ODP[01]; the authorized processing of personally identifiable information is defined] are attached to [PT-02(01)_ODP[02]; elements of personally identifiable information to be tagged are defined].'),
('004546','draft','2022-03-04','DISA','technical','Defines the elements of personally identifiable information containing organization-defined authorized processing.','PT-02(01)','N/A','Determine if data tags containing [PT-02(01)_ODP[01]; the authorized processing of personally identifiable information is defined] are attached to [PT-02(01)_ODP[02]; elements of personally identifiable information to be tagged are defined].'),
('004547','draft','2022-03-04','DISA','policy','Manage enforcement of the authorized processing of personally identifiable information using organization-defined automated mechanisms.','PT-02(02)','N/A','Determine if enforcement of the authorized processing of personally identifiable information is managed using [PT-02(02)_ODP; automated mechanisms used to manage enforcement of the authorized processing of personally identifiable information are defined].'),
('004548','draft','2022-03-04','DISA','policy','Defines the automated mechanisms for managing enforcement of the authorized processing of personally identifiable information.','PT-02(02)','N/A','Determine if enforcement of the authorized processing of personally identifiable information is managed using [PT-02(02)_ODP; automated mechanisms used to manage enforcement of the authorized processing of personally identifiable information are defined].'),
('004549','draft','2022-03-04','DISA','policy','Identify and document the organization-defined purpose(s) for processing personally identifiable information.','PT-03a.','N/A','Determine if the [PT-03_ODP[01]; the purpose(s) for processing personally identifiable information is/are defined] for processing personally identifiable information is/are identified and documented.'),
('004550','draft','2022-03-04','DISA','policy','Defines the purpose(s) of identifying and documenting personally identifiable information.','PT-03a.','N/A','Determine if the [PT-03_ODP[01]; the purpose(s) for processing personally identifiable information is/are defined] for processing personally identifiable information is/are identified and documented.'),
('004551','draft','2022-03-04','DISA','policy','Describe the purpose(s) in the public privacy notices and policies of the organization.','PT-03b.','N/A','Determine if: - the purpose(s) is/are described in the public privacy notices of the organization. - the purpose(s) is/are described in the policies of the organization.'),
('004552','draft','2022-03-04','DISA','policy','Restrict the organization-defined processing of personally identifiable information to only that which is compatible with the identified purpose(s).','PT-03c.','N/A','Determine if the [PT-03_ODP[02]; the processing of personally identifiable information to be restricted is defined] of personally identifiable information are restricted to only that which is compatible with the identified purpose(s).'),
('004553','draft','2022-03-04','DISA','policy','Defines the processing of personally identifiable information to only that which is compatible with the identified purpose(s).','PT-03c.','N/A','Determine if the [PT-03_ODP[02]; the processing of personally identifiable information to be restricted is defined] of personally identifiable information are restricted to only that which is compatible with the identified purpose(s).'),
('004554','draft','2022-03-04','DISA','policy','Monitor changes in processing personally identifiable information.','PT-03d.','N/A','Determine if: - changes in the processing of personally identifiable information are monitored. - [PT-03_ODP[03]; mechanisms to be implemented for ensuring any changes in the processing of personally identifiable information are made in accordance with requirements are defined] are implemented to ensure that any changes are made in accordance with [PT-03_ODP[04]; requirements for changing the processing of personally identifiable information are defined].'),
('004555','draft','2022-03-04','DISA','policy','Implement organization-defined mechanisms to ensure that any changes are made in accordance with organization-defined requirements.','PT-03d.','N/A','Determine if: - changes in the processing of personally identifiable information are monitored. - [PT-03_ODP[03]; mechanisms to be implemented for ensuring any changes in the processing of personally identifiable information are made in accordance with requirements are defined] are implemented to ensure that any changes are made in accordance with [PT-03_ODP[04]; requirements for changing the processing of personally identifiable information are defined].'),
('004556','draft','2022-03-04','DISA','policy','Defines the mechanisms for ensuring any changes are made in accordance with organization-defined requirements.','PT-03d.','N/A','Determine if: - changes in the processing of personally identifiable information are monitored. - [PT-03_ODP[03]; mechanisms to be implemented for ensuring any changes in the processing of personally identifiable information are made in accordance with requirements are defined] are implemented to ensure that any changes are made in accordance with [PT-03_ODP[04]; requirements for changing the processing of personally identifiable information are defined].'),
('004557','draft','2022-03-04','DISA','policy','Defines the requirements for implementing organization-defined mechanisms.','PT-03d.','N/A','Determine if: - changes in the processing of personally identifiable information are monitored. - [PT-03_ODP[03]; mechanisms to be implemented for ensuring any changes in the processing of personally identifiable information are made in accordance with requirements are defined] are implemented to ensure that any changes are made in accordance with [PT-03_ODP[04]; requirements for changing the processing of personally identifiable information are defined].'),
('004558','draft','2022-03-04','DISA','technical','Attach data tags containing organization-defined processing purposes to organization-defined elements of personally identifiable information.','PT-03(01)','N/A','Determine if data tags containing [PT-03(01)_ODP[01]; processing purposes to be contained in data tags are defined] are attached to [PT-03(01)_ODP[02]; elements of personally identifiable information to be tagged are defined].'),
('004559','draft','2022-03-04','DISA','technical','Defines the elements of personally identifiable information containing organization-defined processing purposes.','PT-03(01)','N/A','Determine if data tags containing [PT-03(01)_ODP[01]; processing purposes to be contained in data tags are defined] are attached to [PT-03(01)_ODP[02]; elements of personally identifiable information to be tagged are defined].'),
('004560','draft','2022-03-04','DISA','policy','Track processing purposes of personally identifiable information using organization-defined automated mechanisms.','PT-03(02)','N/A','Determine if the processing purposes of personally identifiable information are tracked using [PT-03(02)_ODP; automated mechanisms for tracking the processing purposes of personally identifiable information are defined].'),
('004561','draft','2022-03-04','DISA','policy','Implement organization-defined tools or mechanisms for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals'' informed decision-making.','PT-04','N/A','Determine if the [PT-04_ODP; the tools or mechanisms to be implemented for individuals to consent to the processing of their personally identifiable information are defined] are implemented for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individual''s informed decision-making.'),
('004562','draft','2022-03-04','DISA','policy','Defines the tools or mechanisms for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals'' informed decision-making.','PT-04','N/A','Determine if the [PT-04_ODP; the tools or mechanisms to be implemented for individuals to consent to the processing of their personally identifiable information are defined] are implemented for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individual''s informed decision-making.'),
('004563','draft','2022-03-04','DISA','policy','Provide organization-defined mechanisms to allow individuals to tailor processing permissions to selected elements of personally identifiable information.','PT-04(01)','N/A','Determine if [PT-04(01)_ODP; tailoring mechanisms for processing selected elements of personally identifiable information permissions are defined] are provided to allow individuals to tailor processing permissions to selected elements of personally identifiable information.'),
('004564','draft','2022-03-04','DISA','policy','Defines the mechanisms for allowing individuals to tailor processing permissions to selected elements of personally identifiable information.','PT-04(01)','N/A','Determine if [PT-04(01)_ODP; tailoring mechanisms for processing selected elements of personally identifiable information permissions are defined] are provided to allow individuals to tailor processing permissions to selected elements of personally identifiable information.'),
('004565','draft','2022-03-04','DISA','policy','Present organization-defined consent mechanisms to individuals at an organization-defined frequency and in conjunction with organization-defined personally identifiable information processing.','PT-04(02)','N/A','Determine if [PT-04(02)_ODP[01]; consent mechanisms to be presented to individuals are defined] are presented to individuals [PT-04(02)_ODP[02]; the frequency at which to present consent mechanisms to individuals is defined] and in conjunction with [PT-04(02)_ODP[03]; personally identifiable information processing to be presented in conjunction with organization-defined consent mechanisms is defined].'),
('004566','draft','2022-03-04','DISA','policy','Defines the frequency for presenting organization-defined consent mechanisms to individuals.','PT-04(02)','N/A','Determine if [PT-04(02)_ODP[01]; consent mechanisms to be presented to individuals are defined] are presented to individuals [PT-04(02)_ODP[02]; the frequency at which to present consent mechanisms to individuals is defined] and in conjunction with [PT-04(02)_ODP[03]; personally identifiable information processing to be presented in conjunction with organization-defined consent mechanisms is defined].'),
('004567','draft','2022-03-04','DISA','policy','Defines the consent mechanisms needed by individuals on an organization-defined frequency, with organization-defined personally identifiable information processing.','PT-04(02)','N/A','Determine if [PT-04(02)_ODP[01]; consent mechanisms to be presented to individuals are defined] are presented to individuals [PT-04(02)_ODP[02]; the frequency at which to present consent mechanisms to individuals is defined] and in conjunction with [PT-04(02)_ODP[03]; personally identifiable information processing to be presented in conjunction with organization-defined consent mechanisms is defined].'),
('004568','draft','2022-03-04','DISA','policy','Defines the personally identifiable information processing needed for presenting organization-defined consent mechanisms to individuals.','PT-04(02)','N/A','Determine if [PT-04(02)_ODP[01]; consent mechanisms to be presented to individuals are defined] are presented to individuals [PT-04(02)_ODP[02]; the frequency at which to present consent mechanisms to individuals is defined] and in conjunction with [PT-04(02)_ODP[03]; personally identifiable information processing to be presented in conjunction with organization-defined consent mechanisms is defined].'),
('004569','draft','2022-03-04','DISA','policy','Implement organization-defined tools or mechanisms for individuals to revoke consent to the processing of their personally identifiable information.','PT-04(03)','N/A','Determine if the [PT-04(03)_ODP; the tools or mechanisms to be implemented for revoking consent to the processing of personally identifiable information are defined] are implemented for individuals to revoke consent to the processing of their personally identifiable information.'),
('004570','draft','2022-03-04','DISA','policy','Defines the tools or mechanisms for individuals to revoke consent to the processing of their personally identifiable information.','PT-04(03)','N/A','Determine if the [PT-04(03)_ODP; the tools or mechanisms to be implemented for revoking consent to the processing of personally identifiable information are defined] are implemented for individuals to revoke consent to the processing of their personally identifiable information.'),
('004571','draft','2022-03-04','DISA','policy','Provide notice to individuals about the processing of personally identifiable information that is available to individuals upon first interacting with an organization, and subsequently at an organization-defined frequency.','PT-05a.','N/A','Determine if: - a notice to individuals about the processing of personally identifiable information is provided such that the notice is available to individuals upon first interacting with an organization. - a notice to individuals about the processing of personally identifiable information is provided such that the notice is subsequently available to individuals [PT-05_ODP[01]; the frequency at which a notice is provided to individuals after initial interaction with an organization is defined].'),
('004572','draft','2022-03-04','DISA','policy','Defines the frequency for providing notice to individuals about the processing of personally identifiable information that is available to individuals upon first interacting with an organization.','PT-05a.','N/A','Determine if: - a notice to individuals about the processing of personally identifiable information is provided such that the notice is available to individuals upon first interacting with an organization. - a notice to individuals about the processing of personally identifiable information is provided such that the notice is subsequently available to individuals [PT-05_ODP[01]; the frequency at which a notice is provided to individuals after initial interaction with an organization is defined].'),
('004573','draft','2022-03-04','DISA','policy','Provide notice to individuals about the processing of personally identifiable information is clear and easy-to-understand, expressing information about personally identifiable information processing in plain language.','PT-05b.','N/A','Determine if a notice to individuals about the processing of personally identifiable information is provided that is clear, easy-to-understand, and expresses information about personally identifiable information processing in plain language.'),
('004574','draft','2022-03-04','DISA','policy','Provide notice to individuals about the processing of personally identifiable information that identifies the authority that authorizes the processing of personally identifiable information.','PT-05c.','N/A','Determine if a notice to individuals about the processing of personally identifiable information that identifies the authority that authorizes the processing of personally identifiable information is provided.'),
('004575','draft','2022-03-04','DISA','policy','Provide notice to individuals about the processing of personally identifiable information that identifies the purposes for which personally identifiable information is to be processes.','PT-05d.','N/A','Determine if a notice to individuals about the processing of personally identifiable information that identifies the purpose for which personally identifiable information is to be processed is provided.'),
('004576','draft','2022-03-04','DISA','policy','Provide notice to individuals about the processing of personally identifiable information that includes organization-defined information.','PT-05e.','N/A','Determine if a notice to individuals about the processing of personally identifiable information which includes [PT-05_ODP[02]; information to be included with the notice about the processing of personally identifiable information is defined] is provided.'),
('004577','draft','2022-03-04','DISA','policy','Defines the information that includes providing notice to individuals about the processing of personally identifiable information.','PT-05e.','N/A','Determine if a notice to individuals about the processing of personally identifiable information which includes [PT-05_ODP[02]; information to be included with the notice about the processing of personally identifiable information is defined] is provided.'),
('004578','draft','2022-03-04','DISA','policy','Present notice of personally identifiable information processing to individuals at a time and location where the individual provides personally identifiable information or in conjunction with a data action or organization-defined frequency.','PT-05(01)','N/A','Determine if a notice of personally identifiable information processing is presented to individuals at a time and location where the individual provides personally identifiable information, in conjunction with a data action, or [PT-05(01)_ODP; the frequency at which to present a notice of personally identifiable information processing is defined].'),
('004579','draft','2022-03-04','DISA','policy','Defines the frequency for presenting notice of personally identifiable information processing to individuals at a time and location where the individual provides personally identifiable information or in conjunction with a data action.','PT-05(01)','N/A','Determine if a notice of personally identifiable information processing is presented to individuals at a time and location where the individual provides personally identifiable information, in conjunction with a data action, or [PT-05(01)_ODP; the frequency at which to present a notice of personally identifiable information processing is defined].'),
('004580','draft','2022-03-04','DISA','policy','Include Privacy Act statements on forms that collect information that will be maintained in a Privacy Act system of records, or provide Privacy Act statements on separate forms that can be retained by individuals.','PT-05(02)','N/A','Determine if Privacy Act statements are included on forms that collect information that will be maintained in a Privacy Act system of records, or Privacy Act statements are provided on separate forms that can be retained by individuals.'),
('004581','draft','2022-03-04','DISA','policy','For systems that process information that will be maintained in a Privacy Act system of records: draft system of records notices in accordance with OMB guidance.','PT-06a.','N/A','Determine if: - system of records notices are drafted in accordance with OMB guidance for systems that process information that will be maintained in a Privacy Act system of records. - new and significantly modified system of records notices are submitted to the OMB and appropriate congressional committees for advance review for systems that process information that will be maintained in a Privacy Act system of records.'),
('004582','draft','2022-03-04','DISA','policy','For systems that process information that will be maintained in a Privacy Act system of records: submit new and significantly modified system of records notices to the OMB and appropriate committees for advance review.','PT-06a.','N/A','Determine if: - system of records notices are drafted in accordance with OMB guidance for systems that process information that will be maintained in a Privacy Act system of records. - new and significantly modified system of records notices are submitted to the OMB and appropriate congressional committees for advance review for systems that process information that will be maintained in a Privacy Act system of records.'),
('004583','draft','2022-03-04','DISA','policy','For systems that process information that will be maintained in a Privacy Act system of records: publish system of records notices in the Federal Register.','PT-06b.','N/A','Determine if system of records notices are published in the Federal Register for systems that process information that will be maintained in a Privacy Act system of records.'),
('004584','draft','2022-03-04','DISA','policy','For systems that process information that will be maintained in a Privacy Act system of records: keep system of records notices accurate, up-to-date, and scoped in accordance with policy.','PT-06c.','N/A','Determine if system of records notices are kept accurate, up-to-date, and scoped in accordance with policy for systems that process information that will be maintained in a Privacy Act system of records.'),
('004585','draft','2022-03-04','DISA','policy','Review all routine uses published in the system of records notice at an organization-defined frequency to ensure continued accuracy.','PT-06(01)','N/A','Determine if all routine uses published in the system of records notice are reviewed [PT-06(01)_ODP; the frequency at which to review all routine uses published in the system of records notice is defined] to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.'),
('004586','draft','2022-03-04','DISA','policy','Defines the frequency for reviewing all routine uses in published in the system of records notice.','PT-06(01)','N/A','Determine if all routine uses published in the system of records notice are reviewed [PT-06(01)_ODP; the frequency at which to review all routine uses published in the system of records notice is defined] to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.'),
('004587','draft','2022-03-04','DISA','policy','Review all routine uses published in the system of records notice at an organization-defined frequency to ensure that routine uses continue to be compatible with the purpose for which the information was collected.','PT-06(01)','N/A','Determine if all routine uses published in the system of records notice are reviewed [PT-06(01)_ODP; the frequency at which to review all routine uses published in the system of records notice is defined] to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.'),
('004588','draft','2022-03-04','DISA','policy','Review all Privacy Act exemptions claimed for the system of records at organization-defined frequency to ensure they remain appropriate and necessary with law.','PT-06(02)','N/A','Determine if: - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they remain appropriate and necessary in accordance with law. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they have been promulgated as regulations. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they are accurately described in the system of records notice.'),
('004589','draft','2022-03-04','DISA','policy','Review all Privacy Act exemptions claimed for the system of records at organization-defined frequency to ensure they have been promulgated as regulations.','PT-06(02)','N/A','Determine if: - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they remain appropriate and necessary in accordance with law. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they have been promulgated as regulations. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they are accurately described in the system of records notice.'),
('004590','draft','2022-03-04','DISA','policy','Review all Privacy Act exemptions claimed for the system of records at organization-defined frequency to ensure that they are accurately described in the system of records notice.','PT-06(02)','N/A','Determine if: - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they remain appropriate and necessary in accordance with law. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they have been promulgated as regulations. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they are accurately described in the system of records notice.'),
('004591','draft','2022-03-04','DISA','policy','Defines the frequency for reviewing all Privacy Act exemptions claimed for the system of records.','PT-06(02)','N/A','Determine if: - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they remain appropriate and necessary in accordance with law. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they have been promulgated as regulations. - all Privacy Act exemptions claimed for the system of records are reviewed [PT-06(02)_ODP; the frequency at which to review all Privacy Act exemptions claimed for the system of records is defined] to ensure that they are accurately described in the system of records notice.'),
('004592','draft','2022-03-04','DISA','policy','Apply organization-defined processing conditions for specific categories of personally identifiable information.','PT-07','N/A','Determine if [PT-07_ODP; processing conditions to be applied for specific categories of personally identifiable information are defined] are applied for specific categories of personally identifiable information.'),
('004593','draft','2022-03-04','DISA','policy','Defines the processing conditions for applying specific categories of personally identifiable information.','PT-07','N/A','Determine if [PT-07_ODP; processing conditions to be applied for specific categories of personally identifiable information are defined] are applied for specific categories of personally identifiable information.'),
('004594','draft','2022-03-04','DISA','policy','When a system processes Social Security numbers: eliminate unnecessary collection, maintenance, and use of Social Security numbers, and explore alternatives to their use as a personal identifier.','PT-07(01)(a)','N/A','Determine if: - when a system processes Social Security numbers, the unnecessary collection, maintenance, and use of Social Security numbers are eliminated. - when a system processes Social Security numbers, alternatives to the use of Social Security Numbers as a personal identifier are explored.'),
('004595','draft','2022-03-04','DISA','policy','When a system processes Social Security numbers: do not deny any individuals any right, benefit, or privilege provided by law because of such individuals'' refusal to disclose his or her Social Security number.','PT-07(01)(b)','N/A','Determine if when a system processes Social Security numbers, individual rights, benefits, or privileges provided by law are not denied because of an individual''s refusal to disclose their Social Security number.'),
('004596','draft','2022-03-04','DISA','policy','When a system processes Social Security numbers: inform any individual who is asked to disclose his or Social Security number whether that disclosure is mandatory or voluntary, by what statutory or other authority such number is solicited, and what uses will be made of it.','PT-07(01)(c)','N/A','Determine if: - when a system processes Social Security numbers, any individual who is asked to disclose their Social Security number is informed whether that disclosure is mandatory or voluntary, by what statutory or other authority such number is solicited, and what uses will be made of it. - when a system processes Social Security numbers, any individual who is asked to disclose their Social Security number is informed by what statutory or other authority the number is solicited. - when a system processes Social Security numbers, any individual who is asked to disclose their Social Security number is informed what uses will be made of it.'),
('004597','draft','2022-03-04','DISA','policy','Prohibit the processing of information describing how any individual exercises rights guaranteed by the First Amendment unless expressly authorized by statue or by the individual or unless pertinent to and within the scope of an authorized law enforcement activity.','PT-07(02)','N/A','Determine if the processing of information describing how any individual exercises rights guaranteed by the First Amendment is prohibited unless expressly authorized by statute or by the individual or unless pertinent to and within the scope of an authorized law enforcement activity.'),
('004598','draft','2022-03-04','DISA','policy','When a system or organization processes information for the purpose of conducting a matching program: obtain approval from the Data Integrity Board to conduct the matching program.','PT-08a.','N/A','Determine if approval to conduct the matching program is obtained from the Data Integrity Board when a system or organization processes information for the purpose of conducting a matching program.'),
('004599','draft','2022-03-04','DISA','policy','When a system or organization processes information for the purpose of conducting a matching program: develop and enter into a computer matching agreement.','PT-08b.','N/A','Determine if: - a computer matching agreement is developed when a system or organization processes information for the purpose of conducting a matching program. - a computer matching agreement is entered into when a system or organization processes information for the purpose of conducting a matching program.'),
('004600','draft','2022-03-04','DISA','policy','When a system or organization processes information for the purpose of conducting a matching program: publish a matching notice in the Federal Register.','PT-08c.','N/A','Determine if a matching notice is published in the Federal Register when a system or organization processes information for the purpose of conducting a matching program.'),
('004601','draft','2022-03-04','DISA','policy','When a system or organization processes information for the purpose of conducting a matching program: independently verify the information produced by the matching program before taking adverse action against an individual, if required.','PT-08d.','N/A','Determine if the information produced by the matching program is independently verified before taking adverse action against an individual, if required, when a system or organization processes information for the purpose of conducting a matching program.'),
('004602','draft','2022-03-04','DISA','policy','When a system or organization processes information for the purpose of conducting a matching program: provide individuals with notice and an opportunity to contest the findings before taking adverse action against an individual.','PT-08e.','N/A','Determine if: - individuals are provided with notice when a system or organization processes information for the purpose of conducting a matching program. - individuals are provided with an opportunity to contest the findings before adverse action is taken against them when a system or organization processes information for the purpose of conducting a matching program.'),
('004603','draft','2022-03-04','DISA','policy','Develop and document an organization-level; mission/business process-level; system-level risk assessment policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','RA-01a.01(b)','N/A','Determine if the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.'),
('004604','draft','2022-03-04','DISA','policy','Disseminate an organization-level; mission/business process-level; system-level risk assessment policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines, to organization-defined personnel or roles.','RA-01a.01(b)','N/A','Determine if the [RA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] risk assessment policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.'),
('004605','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the development and documentation of the risk assessment policy.','RA-01b.','N/A','Determine if the [RA-01_ODP[04]; an official to manage the risk assessment policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures.'),
('004606','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the dissemination of the risk assessment policy.','RA-01b.','N/A','Determine if the [RA-01_ODP[04]; an official to manage the risk assessment policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures.'),
('004607','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage development and documentation of the risk assessment procedures.','RA-01b.','N/A','Determine if the [RA-01_ODP[04]; an official to manage the risk assessment policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures.'),
('004608','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage dissemination of the risk assessment procedures.','RA-01b.','N/A','Determine if the [RA-01_ODP[04]; an official to manage the risk assessment policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures.'),
('004609','draft','2022-03-04','DISA','policy','Defines the official designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures.','RA-01b.','N/A','Determine if the [RA-01_ODP[04]; an official to manage the risk assessment policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the risk assessment policy and procedures.'),
('004610','draft','2022-03-04','DISA','policy','Review and update the current risk assessment policy following organization-defined events.','RA-01c.01','N/A','Determine if: - the current risk assessment policy is reviewed and updated [RA-01_ODP[05]; the frequency at which the current risk assessment policy is reviewed and updated is defined]. - the current risk assessment policy is reviewed and updated following [RA-01_ODP[06]; events that would require the current risk assessment policy to be reviewed and updated are defined].'),
('004611','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current risk assessment policy.','RA-01c.01','N/A','Determine if: - the current risk assessment policy is reviewed and updated [RA-01_ODP[05]; the frequency at which the current risk assessment policy is reviewed and updated is defined]. - the current risk assessment policy is reviewed and updated following [RA-01_ODP[06]; events that would require the current risk assessment policy to be reviewed and updated are defined].'),
('004612','draft','2022-03-04','DISA','policy','Review and update the current risk assessment procedures following organization-defined events.','RA-01c.02','N/A','Determine if: - the current risk assessment procedures are reviewed and updated [RA-01_ODP[07]; the frequency at which the current risk assessment procedures are reviewed and updated is defined]. - the current risk assessment procedures are reviewed and updated following [RA-01_ODP[08]; events that would require risk assessment procedures to be reviewed and updated are defined].'),
('004613','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current risk assessment procedures.','RA-01c.02','N/A','Determine if: - the current risk assessment procedures are reviewed and updated [RA-01_ODP[07]; the frequency at which the current risk assessment procedures are reviewed and updated is defined]. - the current risk assessment procedures are reviewed and updated following [RA-01_ODP[08]; events that would require risk assessment procedures to be reviewed and updated are defined].'),
('004614','draft','2022-03-04','DISA','policy','Categorize the system and information it processes.','RA-02a.','N/A','Determine if the system and the information it processes, stores, and transmits are categorized.'),
('004615','draft','2022-03-04','DISA','policy','Categorize the system and information it stores.','RA-02a.','N/A','Determine if the system and the information it processes, stores, and transmits are categorized.'),
('004616','draft','2022-03-04','DISA','policy','Categorize the system and information it transmits.','RA-02a.','N/A','Determine if the system and the information it processes, stores, and transmits are categorized.'),
('004617','draft','2022-03-04','DISA','policy','Conduct a impact-level categorization of organizational systems to obtain additional granularity on system impact levels.','RA-02(01)','N/A','Determine if an impact-level prioritization of organizational systems is conducted to obtain additional granularity on system impact levels.'),
('004618','draft','2022-03-04','DISA','policy','Conduct a risk assessment, including identifying threats to the system.','RA-03a.01','N/A','Determine if a risk assessment is conducted to identify threats to and vulnerabilities in the system.'),
('004619','draft','2022-03-04','DISA','policy','Conduct a risk assessment, including identifying vulnerabilities in the system.','RA-03a.01','N/A','Determine if a risk assessment is conducted to identify threats to and vulnerabilities in the system.'),
('004620','draft','2022-03-04','DISA','policy','Conduct a risk assessment, including determining the likelihood and impact of adverse effects on individuals arising from the processing of personally-identifiable information.','RA-03a.03','N/A','Determine if a risk assessment is conducted to determine the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information.'),
('004621','draft','2022-03-04','DISA','policy','Integrate risk assessment results from the organization.','RA-03b.','N/A','Determine if risk assessment results and risk management decisions from the organization and mission or business process perspectives are integrated with system-level risk assessments.'),
('004622','draft','2022-03-04','DISA','policy','Integrate risk management decisions from the organization.','RA-03b.','N/A','Determine if risk assessment results and risk management decisions from the organization and mission or business process perspectives are integrated with system-level risk assessments.'),
('004623','draft','2022-03-04','DISA','policy','Integrate mission or business process perspectives with system-level risk assessments.','RA-03b.','N/A','Determine if risk assessment results and risk management decisions from the organization and mission or business process perspectives are integrated with system-level risk assessments.'),
('004624','draft','2022-03-04','DISA','policy','Assess supply chain risks associated with organization-defined systems, system components, and system services.','RA-03(01)(a)','N/A','Determine if supply chain risks associated with [RA-03(01)_ODP[01]; systems, system components, and system services to assess supply chain risks are defined] are assessed.'),
('004625','draft','2022-03-04','DISA','policy','Defines the systems, system-components, and system services for assessing supply chain risks.','RA-03(01)(a)','N/A','Determine if supply chain risks associated with [RA-03(01)_ODP[01]; systems, system components, and system services to assess supply chain risks are defined] are assessed.'),
('004626','draft','2022-03-04','DISA','policy','Update the supply chain risk assessment on an organization-defined frequency when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.','RA-03(01)(b)','N/A','Determine if the supply chain risk assessment is updated [RA-03(01)_ODP[02]; the frequency at which to update the supply chain risk assessment is defined], when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.'),
('004627','draft','2022-03-04','DISA','policy','Defines the frequency for updating the supply chain assessment.','RA-03(01)(b)','N/A','Determine if the supply chain risk assessment is updated [RA-03(01)_ODP[02]; the frequency at which to update the supply chain risk assessment is defined], when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.'),
('004628','draft','2022-03-04','DISA','policy','Use all-source intelligence to assist in the analysis of risk.','RA-03(02)','N/A','Determine if all-source intelligence is used to assist in the analysis of risk.'),
('004629','draft','2022-03-04','DISA','policy','Determine the current cyber threat environment on an ongoing basis using organization-defined means.','RA-03(03)','N/A','Determine if the current cyber threat environment is determined on an ongoing basis using [RA-03(03)_ODP; means to determine the current cyber threat environment on an ongoing basis].'),
('004630','draft','2022-03-04','DISA','policy','Defines the means for determining the current threat environment.','RA-03(03)','N/A','Determine if the current cyber threat environment is determined on an ongoing basis using [RA-03(03)_ODP; means to determine the current cyber threat environment on an ongoing basis].'),
('004631','draft','2022-03-04','DISA','policy','Employ organization-defined advanced automation and analytics capabilities to predict and identify risks to organization-defined systems or system components.','RA-03(03)','N/A','Determine if the current cyber threat environment is determined on an ongoing basis using [RA-03(03)_ODP; means to determine the current cyber threat environment on an ongoing basis].'),
('004632','draft','2022-03-04','DISA','policy','Defines the advanced automation and analytics capabilities for predicting and identifying risks to organization-defined systems or system components.','RA-03(04)','N/A','Determine if: - [RA-03(04)_ODP[01]; advanced automation capabilities to predict and identify risks are defined] are employed to predict and identify risks to [RA-03(04)_ODP[02]; systems or system components where advanced automation and analytics capabilities are to be employed are defined]. - [RA-03(04)_ODP[03]; advanced analytics capabilities to predict and identify risks are defined] are employed to predict and identify risks to [RA-03(04)_ODP[02]; systems or system components where advanced automation and analytics capabilities are to be employed are defined].'),
('004633','draft','2022-03-04','DISA','policy','Defines the systems or system components for employing advanced automation and analytics capabilities.','RA-03(04)','N/A','Determine if: - [RA-03(04)_ODP[01]; advanced automation capabilities to predict and identify risks are defined] are employed to predict and identify risks to [RA-03(04)_ODP[02]; systems or system components where advanced automation and analytics capabilities are to be employed are defined]. - [RA-03(04)_ODP[03]; advanced analytics capabilities to predict and identify risks are defined] are employed to predict and identify risks to [RA-03(04)_ODP[02]; systems or system components where advanced automation and analytics capabilities are to be employed are defined].'),
('004634','draft','2022-03-04','DISA','policy','Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: formatting checklists and test procedures.','RA-05b.02','N/A','Determine if vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for formatting checklists and test procedures.'),
('004635','draft','2022-03-04','DISA','policy','Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: measuring vulnerability impact.','RA-05b.03','N/A','Determine if vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for measuring vulnerability impact.'),
('004636','draft','2022-03-04','DISA','policy','Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned.','RA-05f.','N/A','Determine if vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned are employed.'),
('004637','draft','2022-03-04','DISA','policy','Defines the automated mechanisms for comparing the results of multiple vulnerability scans.','RA-05(06)','N/A','Determine if the results of multiple vulnerability scans are compared using [RA-05(06)_ODP; automated mechanisms to compare the results of multiple vulnerability scans are defined].'),
('004638','draft','2022-03-04','DISA','policy','Defines the system in which will be identified for determining if a vulnerability has been exploited.','RA-05(08)','N/A','Determine if historic audit logs are reviewed to determine if a vulnerability identified in a [RA-05(08)_ODP[01]; a system whose historic audit logs are to be reviewed is defined] has been previously exploited within [RA-05(08)_ODP[02]; a time period for a potential previous exploit of a system is defined].'),
('004639','draft','2022-03-04','DISA','policy','Defines the time period for reviewing historic audit logs to determine if a vulnerability identified has been exploited.','RA-05(08)','N/A','Determine if historic audit logs are reviewed to determine if a vulnerability identified in a [RA-05(08)_ODP[01]; a system whose historic audit logs are to be reviewed is defined] has been previously exploited within [RA-05(08)_ODP[02]; a time period for a potential previous exploit of a system is defined].'),
('004640','draft','2022-03-04','DISA','policy','Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components.','RA-05(11)','N/A','Determine if a public reporting channel is established for receiving reports of vulnerabilities in organizational systems and system components.'),
('004641','draft','2022-03-04','DISA','policy','Respond to findings from security assessments.','RA-07','N/A','Determine if: - findings from security assessments are responded to in accordance with organizational risk tolerance. - findings from privacy assessments are responded to in accordance with organizational risk tolerance. - findings from monitoring are responded to in accordance with organizational risk tolerance. - findings from audits are responded to in accordance with organizational risk tolerance.'),
('004642','draft','2022-03-04','DISA','policy','Respond to findings from privacy assessments.','RA-07','N/A','Determine if: - findings from security assessments are responded to in accordance with organizational risk tolerance. - findings from privacy assessments are responded to in accordance with organizational risk tolerance. - findings from monitoring are responded to in accordance with organizational risk tolerance. - findings from audits are responded to in accordance with organizational risk tolerance.'),
('004643','draft','2022-03-04','DISA','policy','Respond to findings from monitoring.','RA-07','N/A','Determine if: - findings from security assessments are responded to in accordance with organizational risk tolerance. - findings from privacy assessments are responded to in accordance with organizational risk tolerance. - findings from monitoring are responded to in accordance with organizational risk tolerance. - findings from audits are responded to in accordance with organizational risk tolerance.'),
('004644','draft','2022-03-04','DISA','policy','Respond to findings from audits in accordance with organizational risk tolerance.','RA-07','N/A','Determine if: - findings from security assessments are responded to in accordance with organizational risk tolerance. - findings from privacy assessments are responded to in accordance with organizational risk tolerance. - findings from monitoring are responded to in accordance with organizational risk tolerance. - findings from audits are responded to in accordance with organizational risk tolerance.'),
('004645','draft','2022-03-04','DISA','policy','Conduct privacy impact assessments for systems, programs, or other activities before developing or procuring information technology that processes personally identifiable information.','RA-08a.','N/A','Determine if privacy impact assessments are conducted for systems, programs, or other activities before developing or procuring information technology that processes personally identifiable information.'),
('004646','draft','2022-03-04','DISA','policy','Conduct privacy impact assessments for systems, programs, or other activities before initiating a new collection of personally identifiable information that will be processes using information technology.','RA-08b.','N/A','Determine if: - privacy impact assessments are conducted for systems, programs, or other activities before initiating a collection of personally identifiable information that will be processed using information technology. - privacy impact assessments are conducted for systems, programs, or other activities before initiating a collection of personally identifiable information that includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more individuals, other than agencies, instrumentalities, or employees of the federal government.'),
('004647','draft','2022-03-04','DISA','policy','Conduct privacy impact assessments for systems, programs, or other activities before initiating a new collection of personally identifiable information that includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more persons, other than agencies, instrumentalities, or employees of the Federal Government.','RA-08b.','N/A','Determine if: - privacy impact assessments are conducted for systems, programs, or other activities before initiating a collection of personally identifiable information that will be processed using information technology. - privacy impact assessments are conducted for systems, programs, or other activities before initiating a collection of personally identifiable information that includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more individuals, other than agencies, instrumentalities, or employees of the federal government.'),
('004648','draft','2022-03-04','DISA','policy','Identify critical system components and functions by performing a criticality analysis for organization-defined systems, system components, or system services at organization-defined decision points in the system development life cycle.','RA-09','N/A','Determine if critical system components and functions are identified by performing a criticality analysis for [RA-09_ODP[01]; systems, system components, or system services to be analyzed for criticality are defined] at [RA-09_ODP[02]; decision points in the system development life cycle when a criticality analysis is to be performed are defined].'),
('004649','draft','2022-03-04','DISA','policy','Defines the system, system components, or system services to perform a criticality analysis for identifying critical system components and functions.','RA-09','N/A','Determine if critical system components and functions are identified by performing a criticality analysis for [RA-09_ODP[01]; systems, system components, or system services to be analyzed for criticality are defined] at [RA-09_ODP[02]; decision points in the system development life cycle when a criticality analysis is to be performed are defined].'),
('004650','draft','2022-03-04','DISA','policy','Defines the decision points in the system development life cycle at which organization-defined system, system components, or system services to perform a criticality analysis for identifying critical system components and functions.','RA-09','N/A','Determine if critical system components and functions are identified by performing a criticality analysis for [RA-09_ODP[01]; systems, system components, or system services to be analyzed for criticality are defined] at [RA-09_ODP[02]; decision points in the system development life cycle when a criticality analysis is to be performed are defined].'),
('004651','draft','2022-03-04','DISA','policy','Establish and maintain a cyber threat hunting capability to search for indicators of compromise in organizational systems.','RA-10a.01','N/A','Determine if a cyber threat capability is established and maintained to search for indicators of compromise in organizational systems.'),
('004652','draft','2022-03-04','DISA','policy','Establish and maintain a cyber threat hunting capability to detect, track, and disrupt threats that evade existing controls.','RA-10a.02','N/A','Determine if a cyber threat capability is established and maintained to detect, track, and disrupt threats that evade existing controls.'),
('004653','draft','2022-03-04','DISA','policy','Employ the threat hunting capability on an organization-defined frequency.','RA-10b.','N/A','Determine if the threat hunting capability is employed [RA-10_ODP; the frequency at which to employ the threat hunting capability is defined].'),
('004654','draft','2022-03-04','DISA','policy','Defines the frequency for employing the threat hunting capability.','RA-10b.','N/A','Determine if the threat hunting capability is employed [RA-10_ODP; the frequency at which to employ the threat hunting capability is defined].'),
('004655','draft','2022-03-04','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level system and services acquisition policy that is consistent with applicable laws, Executive Orders, directives, regulations, polices, standards, and guidelines.','SA-01a.01(b)','N/A','Determine if the [SA-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and services acquisition policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004656','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage development and documentation of the system and services acquisition policy.','SA-01b.','N/A','Determine if the [SA-01_ODP[04]; an official to manage the system and services acquisition policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures.'),
('004657','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage dissemination of the system and services acquisition policy.','SA-01b.','N/A','Determine if the [SA-01_ODP[04]; an official to manage the system and services acquisition policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures.'),
('004658','draft','2022-03-04','DISA','policy','Defines the official designated to manage development and documentation of the system and services acquisition policy.','SA-01b.','N/A','Determine if the [SA-01_ODP[04]; an official to manage the system and services acquisition policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures.'),
('004659','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the development and documentation of the system and services acquisition procedures.','SA-01b.','N/A','Determine if the [SA-01_ODP[04]; an official to manage the system and services acquisition policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures.'),
('004660','draft','2022-03-04','DISA','policy','Designate an organization-defined official to manage the dissemination of the system and services acquisition procedures.','SA-01b.','N/A','Determine if the [SA-01_ODP[04]; an official to manage the system and services acquisition policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures.'),
('004661','draft','2022-03-04','DISA','policy','Defines the official designated to manage the system and services acquisition procedures.','SA-01b.','N/A','Determine if the [SA-01_ODP[04]; an official to manage the system and services acquisition policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures.'),
('004662','draft','2022-03-04','DISA','policy','Review and update the current system and services acquisition policy following organization-defined events.','SA-01c.01','N/A','Determine if: - the system and services acquisition policy is reviewed and updated [SA-01_ODP[05]; the frequency at which the current system and services acquisition policy is reviewed and updated is defined]. - the current system and services acquisition policy is reviewed and updated following [SA-01_ODP[06]; events that would require the current system and services acquisition policy to be reviewed and updated are defined].'),
('004663','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current system and services acquisition policy.','SA-01c.01','N/A','Determine if: - the system and services acquisition policy is reviewed and updated [SA-01_ODP[05]; the frequency at which the current system and services acquisition policy is reviewed and updated is defined]. - the current system and services acquisition policy is reviewed and updated following [SA-01_ODP[06]; events that would require the current system and services acquisition policy to be reviewed and updated are defined].'),
('004664','draft','2022-03-04','DISA','policy','Review and update the current system and services acquisition procedures following organization-defined events.','SA-01c.02','N/A','Determine if: - the current system and services acquisition procedures are reviewed and updated [SA-01_ODP[07]; the frequency at which the current system and services acquisition procedures are reviewed and updated is defined]. - the current system and services acquisition procedures are reviewed and updated following [SA-01_ODP[08]; events that would require the system and services acquisition procedures to be reviewed and updated are defined].'),
('004665','draft','2022-03-04','DISA','policy','Defines the events following reviewing and updating the current system and services acquisition procedures.','SA-01c.02','N/A','Determine if: - the current system and services acquisition procedures are reviewed and updated [SA-01_ODP[07]; the frequency at which the current system and services acquisition procedures are reviewed and updated is defined]. - the current system and services acquisition procedures are reviewed and updated following [SA-01_ODP[08]; events that would require the system and services acquisition procedures to be reviewed and updated are defined].'),
('004666','draft','2022-03-04','DISA','policy','Determine the high-level information privacy requirements for the system or system service in mission and business process planning.','SA-02a.','N/A','Determine if: - the high-level information security requirements for the system or system service are determined in mission and business process planning. - the high-level privacy requirements for the system or system service are determined in mission and business process planning.'),
('004667','draft','2022-03-04','DISA','policy','Establish a discrete line item for information privacy in organizational programming documentation.','SA-02c.','N/A','Determine if: - a discrete line item for information security is established in organizational programming and budgeting documentation. - a discrete line item for privacy is established in organizational programming and budgeting documentation.'),
('004668','draft','2022-03-04','DISA','policy','Establish a discrete line item for information privacy in organizational budgeting documentation.','SA-02c.','N/A','Determine if: - a discrete line item for information security is established in organizational programming and budgeting documentation. - a discrete line item for privacy is established in organizational programming and budgeting documentation.'),
('004669','draft','2022-03-04','DISA','policy','Acquire the system using an organization-defined system development life cycle that incorporates information security considerations.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004670','draft','2022-03-04','DISA','policy','Acquire the system using an organization-defined system development life cycle that incorporates information privacy considerations.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004671','draft','2022-03-04','DISA','policy','Develop the system using an organization-defined system development life cycle that incorporates information security considerations.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004672','draft','2022-03-04','DISA','policy','Develop the system using an organization-defined system development life cycle that incorporates information privacy considerations.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004673','draft','2022-03-04','DISA','policy','Manage the system using an organization-defined system development life cycle that incorporates information privacy considerations.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004674','draft','2022-03-04','DISA','policy','Defines a system development life cycle that is used to develop the system.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004675','draft','2022-03-04','DISA','policy','Defines a system development life cycle that is used to acquire the system.','SA-03a.','N/A','Determine if: - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates information security considerations. - the system is acquired, developed, and managed using [SA-03_ODP; system development life cycle is defined] that incorporates privacy considerations.'),
('004676','draft','2022-03-04','DISA','policy','Define and document information system privacy roles and responsibilities throughout the system development life cycle.','SA-03b.','N/A','Determine if: - information security roles and responsibilities are defined and documented throughout the system development life cycle. - privacy roles and responsibilities are defined and documented throughout the system development life cycle.'),
('004677','draft','2022-03-04','DISA','policy','Identify individuals having information system privacy roles and responsibilities.','SA-03c.','N/A','Determine if: - individuals with information security roles and responsibilities are identified. - individuals with privacy roles and responsibilities are identified.'),
('004678','draft','2022-03-04','DISA','policy','Integrate the organizational information privacy risk management process into system development life cycle activities.','SA-03d.','N/A','Determine if: - organizational information security risk management processes are integrated into system development life cycle activities. - organizational privacy risk management processes are integrated into system development life cycle activities.'),
('004679','draft','2022-03-04','DISA','policy','Protect system preproduction environments commensurate with risk throughout the system development life cycle for the system, system component, or system service.','SA-03(01)','N/A','Determine if system pre-production environments are protected commensurate with risk throughout the system development life cycle for the system, system component, or system service.'),
('004680','draft','2022-03-04','DISA','policy','Approve the use of live data in preproduction environments for the system, system component, or system service.','SA-03(02)(a)','N/A','Determine if: - the use of live data in pre-production environments is approved for the system, system component, or system service. - the use of live data in pre-production environments is documented for the system, system component, or system service. - the use of live data in pre-production environments is controlled for the system, system component, or system service.'),
('004681','draft','2022-03-04','DISA','policy','Document the use of live data in preproduction environments for the system, system component, or system service.','SA-03(02)(a)','N/A','Determine if: - the use of live data in pre-production environments is approved for the system, system component, or system service. - the use of live data in pre-production environments is documented for the system, system component, or system service. - the use of live data in pre-production environments is controlled for the system, system component, or system service.'),
('004682','draft','2022-03-04','DISA','policy','Control the use of live data in preproduction environments for the system, system component, or system service.','SA-03(02)(a)','N/A','Determine if: - the use of live data in pre-production environments is approved for the system, system component, or system service. - the use of live data in pre-production environments is documented for the system, system component, or system service. - the use of live data in pre-production environments is controlled for the system, system component, or system service.'),
('004683','draft','2022-03-04','DISA','policy','Protect preproduction environments for the system, system component, or system service at the same impact or classification level as any live data in use within the preproduction environments.','SA-03(02)(b)','N/A','Determine if pre-production environments for the system, system component, or system service are protected at the same impact or classification level as any live data in use within the pre-production environments.'),
('004684','draft','2022-03-04','DISA','policy','Plan for a technology refresh schedule to support the system throughout the system development life cycle.','SA-03(03)','N/A','Determine if: - a technology refresh schedule is planned for the system throughout the system development life cycle. - a technology refresh schedule is implemented for the system throughout the system development life cycle.'),
('004685','draft','2022-03-04','DISA','policy','Implement technology refresh schedule to support the system throughout the system development life cycle.','SA-03(03)','N/A','Determine if: - a technology refresh schedule is planned for the system throughout the system development life cycle. - a technology refresh schedule is implemented for the system throughout the system development life cycle.'),
('004686','draft','2022-03-04','DISA','policy','Defines the organization-defined contract language for including the requirements, descriptions, and criteria in the acquisition contract for the system, system component, or system service.',NULL,'N/A',NULL),
('004687','draft','2022-03-04','DISA','policy','Include the privacy functional requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04a.','N/A','Determine if: - security functional requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - privacy functional requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004688','draft','2022-03-04','DISA','policy','Include the privacy assurance requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04c.','N/A','Determine if: - security assurance requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - privacy assurance requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004689','draft','2022-03-04','DISA','policy','Include the controls needed to satisfy security requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04d.','N/A','Determine if: - controls needed to satisfy the security requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - controls needed to satisfy the privacy requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004690','draft','2022-03-04','DISA','policy','Include the controls needed to satisfy privacy requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04d.','N/A','Determine if: - controls needed to satisfy the security requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - controls needed to satisfy the privacy requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004691','draft','2022-03-04','DISA','policy','Include the privacy documentation requirements, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04e.','N/A','Determine if: - security documentation requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - privacy documentation requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004692','deprecated','2022-03-04','DISA','policy','Include the requirements for protecting security documentation, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04f.','N/A','Determine if: - requirements for protecting security documentation, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - requirements for protecting privacy documentation, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004693','draft','2022-03-04','DISA','policy','Include the requirements for protecting privacy documentation, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04f.','N/A','Determine if: - requirements for protecting security documentation, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - requirements for protecting privacy documentation, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service.'),
('004694','draft','2022-03-04','DISA','policy','Include the allocation of responsibility or identification of parties responsible for information security, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04h.','N/A','Determine if: - the allocation of responsibility or identification of parties responsible for information security requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - the allocation of responsibility or identification of parties responsible for privacy requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}]. - the allocation of responsibility or identification of parties responsible for supply chain risk management requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}].'),
('004695','draft','2022-03-04','DISA','policy','Include the allocation of responsibility or identification of parties responsible for information privacy, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04h.','N/A','Determine if: - the allocation of responsibility or identification of parties responsible for information security requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - the allocation of responsibility or identification of parties responsible for privacy requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}]. - the allocation of responsibility or identification of parties responsible for supply chain risk management requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}].'),
('004696','draft','2022-03-04','DISA','policy','Include the allocation of responsibility or identification of parties responsible for supply chain risk management, explicitly or by reference, using standardized contract language; and/or organization-defined contract language in the acquisition contract for the information system, system component, or information system service.','SA-04h.','N/A','Determine if: - the allocation of responsibility or identification of parties responsible for information security requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}] in the acquisition contract for the system, system component, or system service. - the allocation of responsibility or identification of parties responsible for privacy requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}]. - the allocation of responsibility or identification of parties responsible for supply chain risk management requirements, descriptions, and criteria are included explicitly or by reference using [SA-04_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {standardized contract language; [SA-04_ODP[02]; contract language is defined (if selected)]}].'),
('004697','draft','2022-03-04','DISA','policy','Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes organization-defined systems engineering methods.','SA-04(03)(a)','N/A','Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SA-04(03)_ODP[01]; systems engineering methods are defined].'),
('004698','draft','2022-03-04','DISA','policy','Defines the systems engineering methods for demonstrating the use of a system development life cycle process.','SA-04(03)(a)','N/A','Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SA-04(03)_ODP[01]; systems engineering methods are defined].'),
('004699','draft','2022-03-04','DISA','policy','Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes organization-defined system security engineering methods and/or privacy engineering methods.','SA-04(03)(b)','N/A','Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SA-04(03)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[SA-04(03)_ODP[03]; system security engineering methods are defined (if selected)]; [SA-04(03)_ODP[04]; privacy engineering methods are defined (if selected)]}].'),
('004700','draft','2022-03-04','DISA','policy','Defines the system security engineering methods and/or privacy engineering methods for demonstrating the use of a system development life cycle process.','SA-04(03)(b)','N/A','Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SA-04(03)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {[SA-04(03)_ODP[03]; system security engineering methods are defined (if selected)]; [SA-04(03)_ODP[04]; privacy engineering methods are defined (if selected)]}].'),
('004701','draft','2022-03-04','DISA','policy','Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes organization-defined software development methods; testing; evaluation, assessment, verification, and validation methods, and quality control processes.','SA-04(03)(c)','N/A','Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SA-04(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {[SA-04(03)_ODP[06]; software development methods are defined (if selected)]; [SA-04(03)_ODP[07]; testing, evaluation, assessment, verification, and validation methods are defined (if selected)]; [SA-04(03)_ODP[08]; quality control processes are defined (if selected)]}].'),
('004702','draft','2022-03-04','DISA','policy','Defines the software development methods; testing; evaluation, assessment, verification, and validation methods, and quality control processes for demonstrating the use of a system development life cycle process.','SA-04(03)(c)','N/A','Determine if the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes [SA-04(03)_ODP[05]; one or more of the following PARAMETER VALUES is/are selected: {[SA-04(03)_ODP[06]; software development methods are defined (if selected)]; [SA-04(03)_ODP[07]; testing, evaluation, assessment, verification, and validation methods are defined (if selected)]; [SA-04(03)_ODP[08]; quality control processes are defined (if selected)]}].'),
('004703','draft','2022-03-04','DISA','policy','Include organization-defined Privacy Act requirements in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.','SA-04(11)','N/A','Determine if [SA-04(11)_ODP; Privacy Act requirements for the operation of a system of records are defined] are defined in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.'),
('004704','draft','2022-03-04','DISA','policy','Defines the Privacy Act requirements to include in the acquisition contract.','SA-04(11)','N/A','Determine if [SA-04(11)_ODP; Privacy Act requirements for the operation of a system of records are defined] are defined in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.'),
('004705','draft','2022-03-04','DISA','policy','Include organizational data ownership requirements in the acquisition contract.','SA-04(12)(a)','N/A','Determine if organizational data ownership requirements are included in the acquisition contract.'),
('004706','draft','2022-03-04','DISA','policy','Require all data to be removed from the contractor''s system and returned to the organization within an organization-defined time frame.','SA-04(12)(b)','N/A','Determine if all data to be removed from the contractor''s system and returned to the organization is required within [SA-04(12)_ODP; time frame to remove data from a contractor system and return it to the organization is defined].'),
('004707','draft','2022-03-04','DISA','policy','Defines the time frame for returning the data removed from the contractor''s system.','SA-04(12)(b)','N/A','Determine if all data to be removed from the contractor''s system and returned to the organization is required within [SA-04(12)_ODP; time frame to remove data from a contractor system and return it to the organization is defined].'),
('004708','draft','2022-03-04','DISA','policy','Obtain or develop administrator documentation for the system, system component, or system services that describes effective use and maintenance of privacy functions and mechanisms.','SA-05a.02','N/A','Determine if: - administrator documentation for the system, system component, or system service that describes the effective use of security functions and mechanisms is obtained or developed. - administrator documentation for the system, system component, or system service that describes the effective maintenance of security functions and mechanisms is obtained or developed. - administrator documentation for the system, system component, or system service that describes the effective use of privacy functions and mechanisms is obtained or developed. - administrator documentation for the system, system component, or system service that describes the effective maintenance of privacy functions and mechanisms is obtained or developed.'),
('004709','draft','2022-03-04','DISA','policy','Obtain or develop user documentation for the system, system component, or system service that describes user-accessible privacy functions and mechanisms and how to effectively use those functions and mechanisms.','SA-05b.01','N/A','Determine if: - user documentation for the system, system component, or system service that describes user-accessible security functions and mechanisms is obtained or developed. - user documentation for the system, system component, or system service that describes how to effectively use those (user-accessible security) functions and mechanisms is obtained or developed. - user documentation for the system, system component, or system service that describes user-accessible privacy functions and mechanisms is obtained or developed. - user documentation for the system, system component, or system service that describes how to effectively use those (user-accessible privacy) functions and mechanisms is obtained or developed.'),
('004710','draft','2022-03-04','DISA','policy','Obtain or develop user documentation for the system, system component, or system service that describes methods for user interaction which enables individuals to protect individual privacy.','SA-05b.02','N/A','Determine if: - user documentation for the system, system component, or system service that describes methods for user interaction, which enable individuals to use the system, component, or service in a more secure manner is obtained or developed. - user documentation for the system, system component, or system service that describes methods for user interaction, which enable individuals to use the system, component, or service to protect individual privacy is obtained or developed.'),
('004711','draft','2022-03-04','DISA','policy','Obtain or develop user documentation for the system, system component, or system service that describes user responsibilities in maintaining the privacy of individuals.','SA-05b.03','N/A','Determine if: - user documentation for the system, system component, or system service that describes user responsibilities for maintaining the security of the system, component, or service is obtained or developed. - user documentation for the system, system component, or system service that describes user responsibilities for maintaining the privacy of individuals is obtained or developed.'),
('004712','draft','2022-03-04','DISA','policy','Defines the systems security and privacy engineering principles applied to the specification of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('004713','draft','2022-03-04','DISA','policy','Defines the systems security engineering principles applied to the design of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('004714','draft','2022-03-04','DISA','policy','Defines the systems security engineering principles applied to the development of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('004715','draft','2022-03-04','DISA','policy','Defines the systems security engineering principles applied to the implementation of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('004716','draft','2022-03-04','DISA','policy','Defines the systems security engineering principles applied to the modification of the system and system components.','SA-08','N/A','Determine if: - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[01]; systems security engineering principles are defined] are applied in the modification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the specification of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the design of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the development of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the implementation of the system and system components. - [SA-08_ODP[02]; privacy engineering principles are defined] are applied in the modification of the system and system components.'),
('004717','draft','2022-03-04','DISA','policy','Implement the security design principle of clear abstractions.','SA-08(01)','N/A','Determine if the security design principle of clear abstractions is implemented.'),
('004718','draft','2022-03-04','DISA','policy','Implement the security design principle of least common mechanism in organization-defined systems or system components.','SA-08(02)','N/A','Determine if [SA-08(02)_ODP; systems or system components that implement the security design principle of least common mechanism are defined] implement the security design principle of least common mechanism.'),
('004719','draft','2022-03-04','DISA','policy','Defines the systems or system components which will implement the security design principle of least common mechanism.','SA-08(02)','N/A','Determine if [SA-08(02)_ODP; systems or system components that implement the security design principle of least common mechanism are defined] implement the security design principle of least common mechanism.'),
('004720','draft','2022-03-04','DISA','policy','Implement the security design principles of modularity and layering in organization-defined systems or system components.','SA-08(03)','N/A','Determine if: - [SA-08(03)_ODP[01]; systems or system components that implement the security design principle of modularity are defined] implement the security design principle of modularity. - [SA-08(03)_ODP[02]; systems or system components that implement the security design principle of layering are defined] implement the security design principle of layering.'),
('004721','draft','2022-03-04','DISA','policy','Defines the systems or system components which will implement the security design principles of modularity and layering.','SA-08(03)','N/A','Determine if: - [SA-08(03)_ODP[01]; systems or system components that implement the security design principle of modularity are defined] implement the security design principle of modularity. - [SA-08(03)_ODP[02]; systems or system components that implement the security design principle of layering are defined] implement the security design principle of layering.'),
('004722','draft','2022-03-04','DISA','policy','Implement the security design principle of partially ordered dependencies in organization-defined systems or system components.','SA-08(04)','N/A','Determine if [SA-08(04)_ODP; systems or system components that implement the security design principle of partially ordered dependencies are defined] implement the security design principle of partially ordered dependencies.'),
('004723','draft','2022-03-04','DISA','policy','Defines the systems or system components which will implement the security design principle of partially ordered dependencies.','SA-08(04)','N/A','Determine if [SA-08(04)_ODP; systems or system components that implement the security design principle of partially ordered dependencies are defined] implement the security design principle of partially ordered dependencies.'),
('004724','draft','2022-03-04','DISA','policy','Implement the security design principle of efficiently mediated access in organization-defined systems or system components.','SA-08(05)','N/A','Determine if [SA-08(05)_ODP; systems or system components that implement the security design principle of efficiently mediated access are defined] implement the security design principle of efficiently mediated access.'),
('004725','draft','2022-03-04','DISA','policy','Defines the systems or system components which will implement the security design principle of efficiently mediated access.','SA-08(05)','N/A','Determine if [SA-08(05)_ODP; systems or system components that implement the security design principle of efficiently mediated access are defined] implement the security design principle of efficiently mediated access.'),
('004726','draft','2022-03-04','DISA','policy','Implement the security design principle of minimized sharing in organization-defined systems or system components.','SA-08(06)','N/A','Determine if [SA-08(06)_ODP; systems or system components that implement the security design principle of minimized sharing are defined] implement the security design principle of minimized sharing.'),
('004727','draft','2022-03-04','DISA','policy','Defines the systems or system components which will implement the security design principle of minimized sharing.','SA-08(06)','N/A','Determine if [SA-08(06)_ODP; systems or system components that implement the security design principle of minimized sharing are defined] implement the security design principle of minimized sharing.'),
('004728','draft','2022-03-04','DISA','policy','Implement the security design principle of reduced complexity in organization-defined systems or system components.','SA-08(07)','N/A','Determine if [SA-08(07)_ODP; systems or system components that implement the security design principle of reduced complexity are defined] implement the security design principle of reduced complexity.'),
('004729','draft','2022-03-04','DISA','policy','Defines the systems or system components which will implement the security design principle of reduced complexity.','SA-08(07)','N/A','Determine if [SA-08(07)_ODP; systems or system components that implement the security design principle of reduced complexity are defined] implement the security design principle of reduced complexity.'),
('004730','draft','2022-03-04','DISA','policy','Implement the security design principle of secure evolvability in organization-defined systems or system components.','SA-08(08)','N/A','Determine if [SA-08(08)_ODP; systems or system components that implement the security design principle of secure evolvability are defined] implement the security design principle of secure evolvability.'),
('004731','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of secure evolvability.','SA-08(08)','N/A','Determine if [SA-08(08)_ODP; systems or system components that implement the security design principle of secure evolvability are defined] implement the security design principle of secure evolvability.'),
('004732','draft','2022-03-07','DISA','policy','Implement the security design principle of trusted components in organization-defined systems or system components.','SA-08(09)','N/A','Determine if [SA-08(09)_ODP; systems or system components that implement the security design principle of trusted components are defined] implement the security design principle of trusted components.'),
('004733','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of trusted components.','SA-08(09)','N/A','Determine if [SA-08(09)_ODP; systems or system components that implement the security design principle of trusted components are defined] implement the security design principle of trusted components.'),
('004734','draft','2022-03-07','DISA','policy','Implement the security design principle of hierarchical trust in organization-defined systems or system components.','SA-08(10)','N/A','Determine if [SA-08(10)_ODP; systems or system components that implement the security design principle of hierarchical trust are defined] implement the security design principle of hierarchical trust.'),
('004735','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of hierarchical trust.','SA-08(10)','N/A','Determine if [SA-08(10)_ODP; systems or system components that implement the security design principle of hierarchical trust are defined] implement the security design principle of hierarchical trust.'),
('004736','draft','2022-03-07','DISA','policy','Implement the security design principle of inverse modification threshold in organization-defined systems or system components.','SA-08(11)','N/A','Determine if [SA-08(11)_ODP; systems or system components that implement the security design principle of inverse modification threshold are defined] implement the security design principle of inverse modification threshold.'),
('004737','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of inverse modification threshold.','SA-08(11)','N/A','Determine if [SA-08(11)_ODP; systems or system components that implement the security design principle of inverse modification threshold are defined] implement the security design principle of inverse modification threshold.'),
('004738','draft','2022-03-07','DISA','policy','Implement the security design principle of hierarchical protection in organization-defined systems or system components.','SA-08(12)','N/A','Determine if [SA-08(12)_ODP; systems or system components that implement the security design principle of hierarchical protection are defined] implement the security design principle of hierarchical protection.'),
('004739','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of hierarchical protection.','SA-08(12)','N/A','Determine if [SA-08(12)_ODP; systems or system components that implement the security design principle of hierarchical protection are defined] implement the security design principle of hierarchical protection.'),
('004740','draft','2022-03-07','DISA','policy','Implement the security design principle of minimized security elements in organization-defined systems or system components.','SA-08(13)','N/A','Determine if [SA-08(13)_ODP; systems or system components that implement the security design principle of minimized security elements are defined] implement the security design principle of minimized security elements.'),
('004741','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of minimized security elements.','SA-08(13)','N/A','Determine if [SA-08(13)_ODP; systems or system components that implement the security design principle of minimized security elements are defined] implement the security design principle of minimized security elements.'),
('004742','draft','2022-03-07','DISA','policy','Implement the security design principle of least privilege in organization-defined systems or system components.','SA-08(14)','N/A','Determine if [SA-08(14)_ODP; systems or system components that implement the security design principle of least privilege are defined] implement the security design principle of least privilege.'),
('004743','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of least privilege.','SA-08(14)','N/A','Determine if [SA-08(14)_ODP; systems or system components that implement the security design principle of least privilege are defined] implement the security design principle of least privilege.'),
('004744','draft','2022-03-07','DISA','policy','Implement the security design principle of predicate permission in organization-defined systems or system components.','SA-08(15)','N/A','Determine if [SA-08(15)_ODP; systems or system components that implement the security design principle of predicate permission are defined] implement the security design principle of predicate permission.'),
('004745','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of predicate permission.','SA-08(15)','N/A','Determine if [SA-08(15)_ODP; systems or system components that implement the security design principle of predicate permission are defined] implement the security design principle of predicate permission.'),
('004746','draft','2022-03-07','DISA','policy','Implement the security design principle of self-reliant trustworthiness in organization-defined systems or system components.','SA-08(16)','N/A','Determine if [SA-08(16)_ODP; systems or system components that implement the security design principle of self-reliant trustworthiness are defined] implement the security design principle of self-reliant trustworthiness.'),
('004747','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of self-reliant trustworthiness.','SA-08(16)','N/A','Determine if [SA-08(16)_ODP; systems or system components that implement the security design principle of self-reliant trustworthiness are defined] implement the security design principle of self-reliant trustworthiness.'),
('004748','draft','2022-03-07','DISA','policy','Implement the security design principle of secure distributed composition in organization-defined systems or system components.','SA-08(17)','N/A','Determine if [SA-08(17)_ODP; systems or system components that implement the security design principle of secure distributed composition are defined] implement the security design principle of secure distributed composition.'),
('004749','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of secure distributed composition.','SA-08(17)','N/A','Determine if [SA-08(17)_ODP; systems or system components that implement the security design principle of secure distributed composition are defined] implement the security design principle of secure distributed composition.'),
('004750','draft','2022-03-07','DISA','policy','Implement the security design principle of trusted communication channels in organization-defined systems or system components.','SA-08(18)','N/A','Determine if [SA-08(18)_ODP; systems or system components that implement the security design principle of trusted communications channels are defined] implement the security design principle of trusted communications channels.'),
('004751','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of trusted communication channels.','SA-08(18)','N/A','Determine if [SA-08(18)_ODP; systems or system components that implement the security design principle of trusted communications channels are defined] implement the security design principle of trusted communications channels.'),
('004752','draft','2022-03-07','DISA','policy','Implement the security design principle of continuous protection in organization-defined systems or system components.','SA-08(19)','N/A','Determine if [SA-08(19)_ODP; systems or system components that implement the security design principle of continuous protection are defined] implement the security design principle of continuous protection.'),
('004753','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of continuous protection.','SA-08(19)','N/A','Determine if [SA-08(19)_ODP; systems or system components that implement the security design principle of continuous protection are defined] implement the security design principle of continuous protection.'),
('004754','draft','2022-03-07','DISA','policy','Implement the security design principle of secure metadata management in organization-defined systems or system components.','SA-08(20)','N/A','Determine if [SA-08(20)_ODP; systems or system components that implement the security design principle of secure metadata management are defined] implement the security design principle of secure metadata management.'),
('004755','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of secure metadata management.','SA-08(20)','N/A','Determine if [SA-08(20)_ODP; systems or system components that implement the security design principle of secure metadata management are defined] implement the security design principle of secure metadata management.'),
('004756','draft','2022-03-07','DISA','policy','Implement the security design principle of self-analysis in organization-defined systems or system components.','SA-08(21)','N/A','Determine if [SA-08(21)_ODP; systems or system components that implement the security design principle of self-analysis are defined] implement the security design principle of self-analysis.'),
('004757','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of self-analysis.','SA-08(21)','N/A','Determine if [SA-08(21)_ODP; systems or system components that implement the security design principle of self-analysis are defined] implement the security design principle of self-analysis.'),
('004758','draft','2022-03-07','DISA','policy','Implement the security design principle of accountability and traceability in organization-defined systems or system components.','SA-08(22)','N/A','Determine if: - [SA-08(22)_ODP[01]; systems or system components that implement the security design principle of accountability are defined] implement the security design principle of accountability. - [SA-08(22)_ODP[02]; systems or system components that implement the security design principle of traceability are defined] implement the security design principle of traceability.'),
('004759','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of accountability and traceability.','SA-08(22)','N/A','Determine if: - [SA-08(22)_ODP[01]; systems or system components that implement the security design principle of accountability are defined] implement the security design principle of accountability. - [SA-08(22)_ODP[02]; systems or system components that implement the security design principle of traceability are defined] implement the security design principle of traceability.'),
('004760','draft','2022-03-07','DISA','policy','Implement the security design principle of secure defaults in organization-defined systems or system components.','SA-08(23)','N/A','Determine if [SA-08(23)_ODP; systems or system components that implement the security design principle of secure defaults are defined] implement the security design principle of secure defaults.'),
('004761','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of secure defaults.','SA-08(23)','N/A','Determine if [SA-08(23)_ODP; systems or system components that implement the security design principle of secure defaults are defined] implement the security design principle of secure defaults.'),
('004762','draft','2022-03-07','DISA','policy','Implement the security design principle of secure failure and recovery in organization-defined systems or system components.','SA-08(24)','N/A','Determine if: - [SA-08(24)_ODP[01]; systems or system components that implement the security design principle of secure failure are defined] implement the security design principle of secure failure. - [SA-08(24)_ODP[02]; systems or system components that implement the security design principle of secure recovery are defined] implement the security design principle of secure recovery. '),
('004763','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of secure failure and recovery.','SA-08(24)','N/A','Determine if: - [SA-08(24)_ODP[01]; systems or system components that implement the security design principle of secure failure are defined] implement the security design principle of secure failure. - [SA-08(24)_ODP[02]; systems or system components that implement the security design principle of secure recovery are defined] implement the security design principle of secure recovery. '),
('004764','draft','2022-03-07','DISA','policy','Implement the security design principle of economic security in organization-defined systems or system components.','SA-08(25)','N/A','Determine if [SA-08(25)_ODP; systems or system components that implement the security design principle of economic security are defined] implement the security design principle of economic security.'),
('004765','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of economic security.','SA-08(25)','N/A','Determine if [SA-08(25)_ODP; systems or system components that implement the security design principle of economic security are defined] implement the security design principle of economic security.'),
('004766','draft','2022-03-07','DISA','policy','Implement the security design principle of performance security in organization-defined systems or system components.','SA-08(26)','N/A','Determine if [SA-08(26)_ODP; systems or system components that implement the security design principle of performance security are defined] implement the security design principle of performance security.'),
('004767','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of performance security.','SA-08(26)','N/A','Determine if [SA-08(26)_ODP; systems or system components that implement the security design principle of performance security are defined] implement the security design principle of performance security.'),
('004768','draft','2022-03-07','DISA','policy','Implement the security design principle of human factored security in organization-defined systems or system components.','SA-08(27)','N/A','Determine if [SA-08(27)_ODP; systems or system components that implement the security design principle of human factored security are defined] implement the security design principle of human factored security.'),
('004769','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of human factored security.','SA-08(27)','N/A','Determine if [SA-08(27)_ODP; systems or system components that implement the security design principle of human factored security are defined] implement the security design principle of human factored security.'),
('004770','draft','2022-03-07','DISA','policy','Implement the security design principle of acceptable security in organization-defined systems or system components.','SA-08(28)','N/A','Determine if [SA-08(28)_ODP; systems or system components that implement the security design principle of acceptable security are defined] implement the security design principle of acceptable security.'),
('004771','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of acceptable security.','SA-08(28)','N/A','Determine if [SA-08(28)_ODP; systems or system components that implement the security design principle of acceptable security are defined] implement the security design principle of acceptable security.'),
('004772','draft','2022-03-07','DISA','policy','Implement the security design principle of repeatable and documented procedures in organization-defined systems or system components.','SA-08(29)','N/A','Determine if [SA-08(29)_ODP; systems or system components that implement the security design principle of repeatable and documented procedures are defined] implement the security design principle of repeatable and documented procedures.'),
('004773','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of repeatable and documented procedures.','SA-08(29)','N/A','Determine if [SA-08(29)_ODP; systems or system components that implement the security design principle of repeatable and documented procedures are defined] implement the security design principle of repeatable and documented procedures.'),
('004774','draft','2022-03-07','DISA','policy','Implement the security design principle of procedural rigor in organization-defined systems or system components.','SA-08(30)','N/A','Determine if [SA-08(30)_ODP; systems or system components that implement the security design principle of procedural rigor are defined] implement the security design principle of procedural rigor.'),
('004775','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of procedural rigor.','SA-08(30)','N/A','Determine if [SA-08(30)_ODP; systems or system components that implement the security design principle of procedural rigor are defined] implement the security design principle of procedural rigor.'),
('004776','draft','2022-03-07','DISA','policy','Implement the security design principle of secure system modification in organization-defined systems or system components.','SA-08(31)','N/A','Determine if [SA-08(31)_ODP; systems or system components that implement the security design principle of secure system modification are defined] implement the security design principle of secure system modification.'),
('004777','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of secure system modification.','SA-08(31)','N/A','Determine if [SA-08(31)_ODP; systems or system components that implement the security design principle of secure system modification are defined] implement the security design principle of secure system modification.'),
('004778','draft','2022-03-07','DISA','policy','Implement the security design principle of sufficient documentation in organization-defined systems or system components.','SA-08(32)','N/A','Determine if [SA-08(32)_ODP; systems or system components that implement the security design principle of sufficient documentation are defined] implement the security design principle of sufficient documentation.'),
('004779','draft','2022-03-07','DISA','policy','Defines the systems or system components which will implement the security design principle of sufficient documentation.','SA-08(32)','N/A','Determine if [SA-08(32)_ODP; systems or system components that implement the security design principle of sufficient documentation are defined] implement the security design principle of sufficient documentation.'),
('004780','draft','2022-03-07','DISA','policy','Implement the privacy principle of minimization using organization-defined processes.','SA-08(33)','N/A','Determine if the privacy principle of minimization is implemented using [SA-08(33)_ODP; processes that implement the privacy principle of minimization are defined].'),
('004781','draft','2022-03-07','DISA','policy','Defines the processes for implementing the privacy principle of minimization.','SA-08(33)','N/A','Determine if the privacy principle of minimization is implemented using [SA-08(33)_ODP; processes that implement the privacy principle of minimization are defined].'),
('004782','draft','2022-03-07','DISA','policy','Require that providers of external system services comply with organizational privacy requirements.','SA-09a.','N/A','Determine if: - providers of external system services comply with organizational security requirements. - providers of external system services comply with organizational privacy requirements. - providers of external system services employ [SA-09_ODP[01]; controls to be employed by external system service providers are defined].'),
('004783','draft','2022-03-07','DISA','policy','Require that providers of external system services employ organization-defined controls.','SA-09a.','N/A','Determine if: - providers of external system services comply with organizational security requirements. - providers of external system services comply with organizational privacy requirements. - providers of external system services employ [SA-09_ODP[01]; controls to be employed by external system service providers are defined].'),
('004784','draft','2022-03-07','DISA','policy','Defines the controls for complying with organizational security and privacy requirements.','SA-09a.','N/A','Determine if: - providers of external system services comply with organizational security requirements. - providers of external system services comply with organizational privacy requirements. - providers of external system services employ [SA-09_ODP[01]; controls to be employed by external system service providers are defined].'),
('004785','draft','2022-03-07','DISA','policy','Define and document organizational oversight with regard to external system services.','SA-09b.','N/A','Determine if: - organizational oversight with regard to external system services are defined and documented. - user roles and responsibilities with regard to external system services are defined and documented.'),
('004786','draft','2022-03-07','DISA','policy','Define and document user roles and responsibilities with regard to external system services.','SA-09b.','N/A','Determine if: - organizational oversight with regard to external system services are defined and documented. - user roles and responsibilities with regard to external system services are defined and documented.'),
('004787','draft','2022-03-07','DISA','policy','Establish trust relationships with external service providers based on organization-defined privacy requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('004788','draft','2022-03-07','DISA','policy','Document trust relationships with external service providers based on organization-defined privacy requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('004789','draft','2022-03-07','DISA','policy','Maintain trust relationships with external service providers based on organization-defined privacy requirements, properties, factors, or conditions defining acceptable trust relationships.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('004790','draft','2022-03-07','DISA','policy','Defines privacy requirements, properties, factors, or conditions defining acceptable trust relationships with external service providers.','SA-09(03)','N/A','Determine if: - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[01]; security requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are established and documented. - trust relationships with external service provides based on [SA-09(03)_ODP[02]; privacy requirements, properties, factors, or conditions defining acceptable trust relationships on which a trust relationship is maintained are defined] are maintained.'),
('004791','draft','2022-03-07','DISA','policy','Maintain exclusive control of cryptographic keys for encrypted material stored or transmitted through an external system.','SA-09(06)','N/A','Determine if exclusive control of cryptographic keys is maintained for encrypted material stored or transmitted through an external system.'),
('004792','draft','2022-03-07','DISA','policy','Provide the capability to check the integrity of organizational information while it resides in the external system.','SA-09(07)','N/A','Determine if the capability is provided to check the integrity of information while it resides in the external system.'),
('004793','draft','2022-03-07','DISA','policy','Restrict the geographic location of information processing and data storage to facilities located within the legal jurisdictional boundary of the United States.','SA-09(08)','N/A','Determine if the geographic location of information processing and data storage is restricted to facilities located within the legal jurisdictional boundary of the United States.'),
('004794','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to document the potential privacy impacts of approved changes to the system, component, or service.','SA-10d.','N/A','Determine if: - the developer of the system, system component, or system service is required to document approved changes to the system, component, or service. - the developer of the system, system component, or system service is required to document the potential security impacts of approved changes. - the developer of the system, system component, or system service is required to document the potential privacy impacts of approved changes.'),
('004795','draft','2022-03-07','DISA','policy','Require organization-defined security and privacy representatives to be included in the organization-defined configuration change management and control process.','SA-10(07)','N/A','Determine if: - [SA-10(07)_ODP[01]; security representatives to be included in the configuration change management and control process are defined] are required to be included in the [SA-10(07)_ODP[03]; configuration change management and control processes in which security representatives are required to be included are defined]. - [SA-10(07)_ODP[02]; privacy representatives to be included in the configuration change management and control process are defined] are required to be included in the [SA-10(07)_ODP[04]; configuration change management and control processes in which privacy representatives are required to be included are defined].'),
('004796','draft','2022-03-07','DISA','policy','Defines the security and privacy representatives to be included the organization-defined configuration change management and control process.','SA-10(07)','N/A','Determine if: - [SA-10(07)_ODP[01]; security representatives to be included in the configuration change management and control process are defined] are required to be included in the [SA-10(07)_ODP[03]; configuration change management and control processes in which security representatives are required to be included are defined]. - [SA-10(07)_ODP[02]; privacy representatives to be included in the configuration change management and control process are defined] are required to be included in the [SA-10(07)_ODP[04]; configuration change management and control processes in which privacy representatives are required to be included are defined].'),
('004797','draft','2022-03-07','DISA','policy','Defines the configuration change management and control process required for the organization-defined security and privacy representatives.','SA-10(07)','N/A','Determine if: - [SA-10(07)_ODP[01]; security representatives to be included in the configuration change management and control process are defined] are required to be included in the [SA-10(07)_ODP[03]; configuration change management and control processes in which security representatives are required to be included are defined]. - [SA-10(07)_ODP[02]; privacy representatives to be included in the configuration change management and control process are defined] are required to be included in the [SA-10(07)_ODP[04]; configuration change management and control processes in which privacy representatives are required to be included are defined].'),
('004798','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service, at all post-design phases of the system development life cycle, to develop a plan for ongoing privacy control assessment.','SA-11a.','N/A','Determine if: - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments.'),
('004799','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to implement a plan for ongoing privacy control assessment.','SA-11a.','N/A','Determine if: - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments. - the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments.'),
('004800','draft','2022-03-07','DISA','policy','Defines the frequency that the unit, integration, system, and/or regression testing/evaluation is performed at an organization-defined depth and coverage.','SA-11b.','N/A','Determine if the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to perform [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation [SA-11_ODP[02]; frequency at which to conduct [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation is defined] at [SA-11_ODP[03]; depth and coverage of [SA-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {unit; integration; system; regression}] testing/evaluation is defined].'),
('004801','draft','2022-03-07','DISA','policy','Use the following contextual information.','SA-11(02)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined].'),
('004802','draft','2022-03-07','DISA','policy','Defines the information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels.','SA-11(02)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that uses [SA-11(02)_ODP[01]; information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined].'),
('004803','draft','2022-03-07','DISA','policy','Employ the following tools and methods.','SA-11(02)(b)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined].'),
('004804','draft','2022-03-07','DISA','policy','Defines the tools and methods to be employed.','SA-11(02)(b)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that employs [SA-11(02)_ODP[02]; the tools and methods to be employed for threat modeling and vulnerability analyses are defined].'),
('004805','draft','2022-03-07','DISA','policy','Conduct the modeling and analyses as the following level of rigor.','SA-11(02)(c)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling at [SA-11(02)_ODP[03]; the breadth and depth of threat modeling to be conducted is defined] during development of the system, component, or service. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that conducts modeling and analyses at [SA-11(02)_ODP[04]; the breadth and depth of vulnerability analyses to be conducted is defined].'),
('004806','draft','2022-03-07','DISA','policy','Defines the breadth and depth of modeling and analyses the level of rigor will be conducted.','SA-11(02)(c)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling at [SA-11(02)_ODP[03]; the breadth and depth of threat modeling to be conducted is defined] during development of the system, component, or service. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that conducts modeling and analyses at [SA-11(02)_ODP[04]; the breadth and depth of vulnerability analyses to be conducted is defined].'),
('004807','draft','2022-03-07','DISA','policy','Produces evidence that meets the following acceptance criteria.','SA-11(02)(d)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined].'),
('004808','draft','2022-03-07','DISA','policy','Defines the acceptance criteria that meets the requirement for producing evidence.','SA-11(02)(d)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined].'),
('004809','draft','2022-03-07','DISA','policy','Require an independent agent satisfying organization-defined independence criteria to verify the correct implementation of the developer privacy assessment plan.','SA-11(02)(d)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined].'),
('004810','draft','2022-03-07','DISA','policy','Require an independent agent satisfying organization-defined independence criteria to verify the evidence produced during privacy testing and evaluation.','SA-11(02)(d)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined].'),
('004811','draft','2022-03-07','DISA','policy','Defines the independence criteria the independent agent must satisfy prior to verifying the correct implementation of the developer privacy assessment plan and the evidence produced during privacy testing and evaluation.','SA-11(02)(d)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[05]; acceptance criteria to be met by produced evidence for threat modeling are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined]. - the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [SA-11(02)_ODP[06]; acceptance criteria to be met by produced evidence for vulnerability analyses are defined].'),
('004812','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to perform penetration testing at an organization-defined breadth and depth of testing.','SA-11(05)(a)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: [SA-11(05)_ODP[01]; the breadth of penetration testing is defined]. - the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: [SA-11(05)_ODP[02]; the depth of penetration testing is defined].'),
('004813','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to perform penetration testing under organization-defined constraints.','SA-11(05)(b)','N/A','Determine if the developer of the system, system component, or system service is required to perform penetration testing under [SA-11(05)_ODP[03]; constraints of penetration testing are defined].'),
('004814','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws.','SA-11(09)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ interactive application security testing tools to identify flaws. - the developer of the system, system component, or system service is required to document the results of flaw identification.'),
('004815','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to employ interactive application security testing tools to document the results.','SA-11(09)','N/A','Determine if: - the developer of the system, system component, or system service is required to employ interactive application security testing tools to identify flaws. - the developer of the system, system component, or system service is required to document the results of flaw identification.'),
('004816','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to follow a documented development process that explicitly addresses privacy requirements.','SA-15a.01','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses security requirements. - the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses privacy requirements.'),
('004817','draft','2022-03-07','DISA','policy','Review the development process in accordance with organization-defined frequency to determine if the development process selected and employed can satisfy organization-defined privacy requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('004818','draft','2022-03-07','DISA','policy','Review the development standards in accordance with organization-defined frequency to determine if the development standards selected and employed can satisfy organization-defined privacy requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('004819','draft','2022-03-07','DISA','policy','Review the development tools in accordance with organization-defined frequency to determine if the development tools selected and employed can satisfy organization-defined privacy requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('004820','draft','2022-03-07','DISA','policy','Review the development tool options/configurations in accordance with organization-defined frequency to determine if the development tool options and tool configurations selected and employed can satisfy organization-defined privacy requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('004821','draft','2022-03-07','DISA','policy','Defines the frequency on which to review the development process, standards, tools, and tool options/configurations to determine if the process, standards, tools, and tool options and tool configurations selected and employed can satisfy organization-defined privacy requirements.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('004822','draft','2022-03-07','DISA','policy','Defines the privacy requirements that must be satisfied by conducting a review of the development process, standards, tools, and tool options and tool configurations.','SA-15b.','N/A','Determine if: - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[02]; security requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined]. - the developer of the system, system component, or system service is required to follow a documented development process in which the development process, standards, tools, tool options, and tool configurations are reviewed [SA-15_ODP[01]; frequency at which to review the development process, standards, tools, tool options, and tool configurations is defined] to determine that the process, standards, tools, tool options, and tool configurations selected and employed satisfy [SA-15_ODP[03]; privacy requirements to be satisfied by the process, standards, tools, tool options, and tool configurations are defined].'),
('004823','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to select a privacy tracking tool for use during the development process.','SA-15(02)','N/A','Determine if: - the developer of the system, system component, or system service is required to select and employ security tracking tools for use during the development process. - the developer of the system, system component, or system service is required to select and employ privacy tracking tools for use during the development process.'),
('004824','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to employ a privacy tracking tool for use during the development process.','SA-15(02)','N/A','Determine if: - the developer of the system, system component, or system service is required to select and employ security tracking tools for use during the development process. - the developer of the system, system component, or system service is required to select and employ privacy tracking tools for use during the development process.'),
('004825','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to perform a criticality analysis at the organization-defined decision points in the system development life cycle.','SA-15(03)(a)','N/A','Determine if the developer of the system, system component, or system service is required to perform a criticality analysis at [SA-15(03)_ODP[01]; decision points in the system development life cycle are defined] in the system development life cycle.'),
('004826','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to perform a criticality analysis at an organization-defined breadth/depth of criticality analysis.','SA-15(03)(b)','N/A','Determine if: - the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: [SA-15(03)_ODP[02]; the breadth of criticality analysis is defined]. - the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: [SA-15(03)_ODP[03]; the depth of criticality analysis is defined].'),
('004827','draft','2022-03-07','DISA','policy','Defines the frequency for performing an automated vulnerability analysis using organization-defined tools.','SA-15(07)(a)','N/A','Determine if the developer of the system, system component, or system service is required to perform automated vulnerability analysis [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] using [SA-15(07)_ODP[02]; tools used to perform automated vulnerability analysis are defined].'),
('004828','draft','2022-03-07','DISA','policy','Defines the frequency for determining the exploitation potential for discovered vulnerabilities.','SA-15(07)(b)','N/A','Determine if the developer of the system, system component, or system service is required to determine the exploitation potential for discovered vulnerabilities [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined].'),
('004829','draft','2022-03-07','DISA','policy','Defines the frequency for determining potential risk mitigations for delivered vulnerabilities.','SA-15(07)(c)','N/A','Determine if the developer of the system, system component, or system service is required to determine potential risk mitigations [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] for delivered vulnerabilities.'),
('004830','draft','2022-03-07','DISA','policy','Defines the frequency for delivering the outputs of the tools and results of the vulnerability analysis to organization-defined personnel or roles.','SA-15(07)(d)','N/A','Determine if the developer of the system, system component, or system service is required to deliver the outputs of the tools and results of the analysis [SA-15(07)_ODP[01]; frequency at which to conduct vulnerability analysis is defined] to [SA-15(07)_ODP[03]; personnel or roles to whom the outputs of tools and results of the analysis are to be delivered is/are defined].'),
('004831','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to implement an incident response plan.','SA-15(10)','N/A','Determine if: - the developer of the system, system component, or system service is required to provide an incident response plan. - the developer of the system, system component, or system service is required to implement an incident response plan. - the developer of the system, system component, or system service is required to test an incident response plan.'),
('004832','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to test an incident response plan.','SA-15(10)','N/A','Determine if: - the developer of the system, system component, or system service is required to provide an incident response plan. - the developer of the system, system component, or system service is required to implement an incident response plan. - the developer of the system, system component, or system service is required to test an incident response plan.'),
('004833','draft','2022-03-07','DISA','policy','Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final privacy review.','SA-15(11)','N/A','Determine if the developer of the system or system component is required to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.'),
('004834','draft','2022-03-07','DISA','policy','Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.','SA-15(12)','N/A','Determine if the developer of the system or system component is required to minimize the use of personally identifiable information in development and test environments.'),
('004835','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to provide organization-defined training on the correct use and operation of the implemented privacy functions, controls, and/or mechanisms.','SA-16','N/A','Determine if the developer of the system, system component, or system service is required to provide [SA-16_ODP; training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms provided by the developer of the system, system component, or system service is defined] on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.'),
('004836','draft','2022-03-07','DISA','policy','Defines the training the developer of the system, system component, or information system service is required to provide on the correct use and operation of the implemented privacy functions, controls, and/or mechanisms.','SA-16','N/A','Determine if the developer of the system, system component, or system service is required to provide [SA-16_ODP; training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms provided by the developer of the system, system component, or system service is defined] on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.'),
('004837','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to produce a privacy architecture.',NULL,'N/A',NULL),
('004838','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to produce a privacy architecture that is consistent with and supportive of the organization''s privacy architecture which is established within and is an integrated part of the organization''s enterprise architecture.','SA-17a.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that are consistent with the organization''s security architecture, which is an integral part the organization''s enterprise architecture. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that are consistent with the organization''s privacy architecture, which is an integral part the organization''s enterprise architecture.'),
('004839','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to produce a privacy architecture that accurately and completely describes the required privacy functionality.','SA-17b.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that accurately and completely describe the required security functionality and the allocation of controls among physical and logical components. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that accurately and completely describe the required privacy functionality and the allocation of controls among physical and logical components.'),
('004840','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to produce a privacy architecture that accurately and completely describes the allocation of privacy controls among physical and logical components.','SA-17b.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that accurately and completely describe the required security functionality and the allocation of controls among physical and logical components. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that accurately and completely describe the required privacy functionality and the allocation of controls among physical and logical components.'),
('004841','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to produce a privacy architecture that expresses how individual privacy functions, mechanisms, and services work together to provide required privacy capabilities and a unified approach to protection.','SA-17c.','N/A','Determine if: - the developer of the system, system component, or system service is required to produce a design specification and security architecture that express how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection. - the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that express how individual privacy functions, mechanisms, and services work together to provide required privacy capabilities and a unified approach to protection.'),
('004842','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system to produce, as an integral part of the development process, a formal policy model describing the organization-defined elements of organizational privacy policy to be enforced.','SA-17(01)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[01]; organizational security policy to be enforced is defined] to be enforced. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[02]; organizational privacy policy to be enforced is defined] to be enforced.'),
('004843','draft','2022-03-07','DISA','policy','Defines the elements of organizational privacy policy to be described in the formal policy model for enforcement on the system, system component, or system service.','SA-17(01)(a)','N/A','Determine if: - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[01]; organizational security policy to be enforced is defined] to be enforced. - as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the [SA-17(01)_ODP[02]; organizational privacy policy to be enforced is defined] to be enforced.'),
('004844','draft','2022-03-07','DISA','policy','Require the developer of the system, system component, or system service to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational privacy policy when implemented.','SA-17(01)(b)','N/A','Determine if: - the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented. - the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational privacy policy when implemented.'),
('004845','draft','2022-03-07','DISA','policy','Design organization-defined critical systems or system components with coordinated behavior to implement organization-defined capabilities, by system or component.','SA-17(08)','N/A','Determine if [SA-17(08)_ODP[01]; critical systems or system components are defined] are designed with coordinated behavior to implement [SA-17(08)_ODP[02]; capabilities to be implemented by systems or components are defined].'),
('004846','draft','2022-03-07','DISA','policy','Defines the critical systems or system components for implementing organization-defined capabilities, by system or component.','SA-17(08)','N/A','Determine if [SA-17(08)_ODP[01]; critical systems or system components are defined] are designed with coordinated behavior to implement [SA-17(08)_ODP[02]; capabilities to be implemented by systems or components are defined].'),
('004847','draft','2022-03-07','DISA','policy','Defines the capabilities, by system or component, for designing organization-defined critical systems or system components.','SA-17(08)','N/A','Determine if [SA-17(08)_ODP[01]; critical systems or system components are defined] are designed with coordinated behavior to implement [SA-17(08)_ODP[02]; capabilities to be implemented by systems or components are defined].'),
('004848','draft','2022-03-07','DISA','policy','Use different designs for organization-defined critical systems or system components to satisfy a common set of requirements or to provide equivalent functionality.','SA-17(09)','N/A','Determine if different designs are used for [SA-17(09)_ODP; critical systems or system components to be designed differently are defined] to satisfy a common set of requirements or to provide equivalent functionality.'),
('004849','draft','2022-03-07','DISA','policy','Defines the critical systems or system components for satisfying a common set of requirements or to provide equivalent functionality.','SA-17(09)','N/A','Determine if different designs are used for [SA-17(09)_ODP; critical systems or system components to be designed differently are defined] to satisfy a common set of requirements or to provide equivalent functionality.'),
('004850','draft','2022-03-07','DISA','policy','Employ design; modification; augmentation; and/or reconfiguration on organization-defined systems or system components supporting mission essential services or functions to increase the trustworthiness in those systems or components.','SA-23','N/A','Determine if [SA-23_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {design modification; augmentation; reconfiguration}] is employed on [SA-23_ODP[02]; systems or system components supporting mission-essential services or functions are defined] supporting essential services or functions to increase the trustworthiness in those systems or components.'),
('004851','draft','2022-03-07','DISA','policy','Defines the systems or system components for supporting mission essential services or functions.','SA-23','N/A','Determine if [SA-23_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {design modification; augmentation; reconfiguration}] is employed on [SA-23_ODP[02]; systems or system components supporting mission-essential services or functions are defined] supporting essential services or functions to increase the trustworthiness in those systems or components.'),
('004852','draft','2022-03-07','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SC-01a.01(a)','N/A','Determine if: - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses purpose. - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses scope. - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses roles. - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses responsibilities. - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses management commitment. - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses coordination among organizational entities. - the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy addresses compliance.'),
('004853','draft','2022-03-07','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system-level a system and communications protection policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','SC-01a.01(b)','N/A','Determine if the [SC-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business-process-level; system-level}] system and communications protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004854','draft','2022-03-07','DISA','policy','Develop and document system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','SC-01a.02','N/A','Determine if: - system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls are developed and documented. - the system and communications protection procedures are disseminated to [SC-01_ODP[02]; personnel or roles to whom the system and communications protection procedures are to be disseminated is/are defined].'),
('004855','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the development and documentation of the system and communications protection policy.','SC-01b.','N/A','Determine if the [SC-01_ODP[04]; an official to manage the system and communications protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures.'),
('004856','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the development and documentation of the system and communications protection procedures.','SC-01b.','N/A','Determine if the [SC-01_ODP[04]; an official to manage the system and communications protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures.'),
('004857','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the dissemination of the system and communications protection policy.','SC-01b.','N/A','Determine if the [SC-01_ODP[04]; an official to manage the system and communications protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures.'),
('004858','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the dissemination of the system and communications protection procedures.','SC-01b.','N/A','Determine if the [SC-01_ODP[04]; an official to manage the system and communications protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures.'),
('004859','draft','2022-03-07','DISA','policy','Defines the official to manage the development, documentation, and dissemination of the system and communications protection policy.','SC-01b.','N/A','Determine if the [SC-01_ODP[04]; an official to manage the system and communications protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures.'),
('004860','draft','2022-03-07','DISA','policy','Defines the official to manage the development, documentation, and dissemination of the system and communications protection procedures.','SC-01b.','N/A','Determine if the [SC-01_ODP[04]; an official to manage the system and communications protection policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures.'),
('004861','draft','2022-03-07','DISA','policy','Review and update the current system and communications protection policy following organization-defined events.','SC-01c.01','N/A','Determine if: - the current system and communications protection policy is reviewed and updated [SC-01_ODP[05]; the frequency at which the current system and communications protection policy is reviewed and updated is defined]. - the current system and communications protection policy is reviewed and updated following [SC-01_ODP[06]; events that would require the current system and communications protection policy to be reviewed and updated are defined].'),
('004862','draft','2022-03-07','DISA','policy','Defines the events following reviewing and updating the current system and communications protection policy.','SC-01c.01','N/A','Determine if: - the current system and communications protection policy is reviewed and updated [SC-01_ODP[05]; the frequency at which the current system and communications protection policy is reviewed and updated is defined]. - the current system and communications protection policy is reviewed and updated following [SC-01_ODP[06]; events that would require the current system and communications protection policy to be reviewed and updated are defined].'),
('004863','draft','2022-03-07','DISA','policy','Review and update the current system and communications protection procedures following organization-defined events.','SC-01c.02','N/A','Determine if: - the current system and communications protection procedures are reviewed and updated [SC-01_ODP[07]; the frequency at which the current system and communications protection procedures are reviewed and updated is defined]. - the current system and communications protection procedures are reviewed and updated following [SC-01_ODP[08]; events that would require the system and communications protection procedures to be reviewed and updated are defined].'),
('004864','draft','2022-03-07','DISA','policy','Defines the events following reviewing and updating the current system and communications protection procedures.','SC-01c.02','N/A','Determine if: - the current system and communications protection procedures are reviewed and updated [SC-01_ODP[07]; the frequency at which the current system and communications protection procedures are reviewed and updated is defined]. - the current system and communications protection procedures are reviewed and updated following [SC-01_ODP[08]; events that would require the system and communications protection procedures to be reviewed and updated are defined].'),
('004865','draft','2022-03-07','DISA','technical','Store state information from applications and software separately.','SC-02(02)','N/A','Determine if state information is stored separately from applications and software.'),
('004866','draft','2022-03-07','DISA','technical','Employ organization-defined controls by type of denial-of-service to achieve the denial-of-service objective.','SC-05b.','N/A','Determine if [SC-05_ODP[03]; controls to achieve the denial-of-service objective by type of denial-of-service event are defined] are employed to achieve the denial-of-service protection objective.'),
('004867','draft','2022-03-07','DISA','technical','Defines the controls by type of denial-of-service event by employing the controls to achieve the denial-of-service objective.','SC-05b.','N/A','Determine if [SC-05_ODP[03]; controls to achieve the denial-of-service objective by type of denial-of-service event are defined] are employed to achieve the denial-of-service protection objective.'),
('004868','draft','2022-03-07','DISA','technical','Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational privacy architecture.','SC-07c.','N/A','Determine if external networks or systems are only connected to through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.'),
('004869','draft','2022-03-07','DISA','policy','Prevent unauthorized exchange of control plane traffic with external networks.','SC-07(04)(f)','N/A','Determine if unauthorized exchanges of control plan traffic with external networks are prevented.'),
('004870','draft','2022-03-07','DISA','policy','Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks.','SC-07(04)(g)','N/A','Determine if information is published to enable remote networks to detect unauthorized control plane traffic from internal networks.'),
('004871','draft','2022-03-07','DISA','policy','Filter unauthorized control plane traffic from external networks.','SC-07(04)(h)','N/A','Determine if unauthorized control plane traffic is filtered from external networks.'),
('004872','draft','2022-03-07','DISA','technical','Defines the systems that will deny network communications traffic by default and allow network communications traffic by exception.','SC-07(05)','N/A','Determine if: - network communications traffic is denied by default [SC-07(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {at managed interfaces; for [SC-07(05)_ODP[02]; systems for which network communications traffic is denied by default and network communications traffic is allowed by exception are defined (if selected)]}]. - network communications traffic is allowed by exception [SC-07(05)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {at managed interfaces; for [SC-07(05)_ODP[02]; systems for which network communications traffic is denied by default and network communications traffic is allowed by exception are defined (if selected)]}].'),
('004873','draft','2022-03-07','DISA','technical','Defines the safeguards to prevent split tunneling for remote devices connecting to organizational systems.','SC-07(07)','N/A','Determine if split tunneling is prevented for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using [SC-07(07)_ODP; safeguards to securely provision split tunneling are defined].'),
('004874','draft','2022-03-07','DISA','policy','Conduct exfiltration tests at an organization-defined frequency.','SC-07(10)(b)','N/A','Determine if exfiltration tests are conducted [SC-07(10)_ODP; the frequency for conducting exfiltration tests is defined].'),
('004875','draft','2022-03-07','DISA','policy','Defines the frequency to conduct exfiltration tests.','SC-07(10)(b)','N/A','Determine if exfiltration tests are conducted [SC-07(10)_ODP; the frequency for conducting exfiltration tests is defined].'),
('004876','draft','2022-03-07','DISA','policy','For systems that process personally identifiable information, apply organization-defined processing rules to data elements of personally identifiable information.','SC-07(24)(a)','N/A','Determine if [SC-07(24)_ODP; processing rules for systems that process personally identifiable information are defined] are applied to data elements of personally identifiable information on systems that process personally identifiable information.'),
('004877','draft','2022-03-07','DISA','policy','Defines processing rules to be applied to data elements of personally identifiable information.','SC-07(24)(a)','N/A','Determine if [SC-07(24)_ODP; processing rules for systems that process personally identifiable information are defined] are applied to data elements of personally identifiable information on systems that process personally identifiable information.'),
('004878','draft','2022-03-07','DISA','policy','For systems that process personally identifiable information, monitor for permitted processing at the external boundary of the system and at key internal boundaries within the system.','SC-07(24)(b)','N/A','Determine if: - permitted processing is monitored at the external interfaces to the systems that process personally identifiable information. - permitted processing is monitored at key internal boundaries within the systems that process personally identifiable information.'),
('004879','draft','2022-03-07','DISA','policy','For systems that process personally identifiable information, document each processing exception.','SC-07(24)(c)','N/A','Determine if each processing exception is documented for systems that process personally identifiable information.'),
('004880','draft','2022-03-07','DISA','policy','For systems that process personally identifiable information, review and remove exceptions that are no longer supported.','SC-07(24)(d)','N/A','Determine if: - exceptions for systems that process personally identifiable information are reviewed. - exceptions for systems that process personally identifiable information that are no longer supported are removed.'),
('004881','draft','2022-03-07','DISA','policy','Prohibit the direct connection of organization-defined unclassified national security system to an external network without the use of organization-defined boundary protection device.','SC-07(25)','N/A','Determine if the direct connection of [SC-07(25)_ODP[01]; the unclassified national security system prohibited from directly connecting to an external network is defined] to an external network without the use of [SC-07(25)_ODP[02]; the boundary protection device required for a direct connection to an external network is defined] is prohibited.'),
('004882','draft','2022-03-07','DISA','policy','Defines the unclassified national security system that is prohibited from connecting to an external network without the use of organization-defined boundary protection device.','SC-07(25)','N/A','Determine if the direct connection of [SC-07(25)_ODP[01]; the unclassified national security system prohibited from directly connecting to an external network is defined] to an external network without the use of [SC-07(25)_ODP[02]; the boundary protection device required for a direct connection to an external network is defined] is prohibited.'),
('004883','draft','2022-03-07','DISA','policy','Defines the boundary protection device that prohibits the direct connection of organization-defined unclassified national security system to an external system.','SC-07(25)','N/A','Determine if the direct connection of [SC-07(25)_ODP[01]; the unclassified national security system prohibited from directly connecting to an external network is defined] to an external network without the use of [SC-07(25)_ODP[02]; the boundary protection device required for a direct connection to an external network is defined] is prohibited.'),
('004884','draft','2022-03-07','DISA','policy','Prohibit the direct connection of a classified national security system to an external network without the use of organization-defined boundary protection device.','SC-07(26)','N/A','Determine if the direct connection of classified national security system to an external network without the use of a [SC-07(26)_ODP; the boundary protection device required for a direct connection to an external network is defined] is prohibited.'),
('004885','draft','2022-03-07','DISA','policy','Defines the boundary protection device that prohibits the direct connection of a classified national security system to an external system.','SC-07(26)','N/A','Determine if the direct connection of classified national security system to an external network without the use of a [SC-07(26)_ODP; the boundary protection device required for a direct connection to an external network is defined] is prohibited.'),
('004886','draft','2022-03-07','DISA','policy','Prohibit the direct connection of organization-defined unclassified non-national security system to an external network without the use of organization-defined boundary protection device.','SC-07(27)','N/A','Determine if the direct connection of [SC-07(27)_ODP[01]; the unclassified, non-national security system prohibited from directly connecting to an external network is defined] to an external network without the use of a [SC-07(27)_ODP[02]; the boundary protection device required for a direct connection of unclassified, non-national security system to an external network is defined] is prohibited.'),
('004887','draft','2022-03-07','DISA','policy','Defines the unclassified non-national security system that is prohibited from connecting to an external network without the use of organization-defined boundary protection device.','SC-07(27)','N/A','Determine if the direct connection of [SC-07(27)_ODP[01]; the unclassified, non-national security system prohibited from directly connecting to an external network is defined] to an external network without the use of a [SC-07(27)_ODP[02]; the boundary protection device required for a direct connection of unclassified, non-national security system to an external network is defined] is prohibited.'),
('004888','draft','2022-03-07','DISA','policy','Defines the boundary protection device that prohibits the direct connection of organization-defined unclassified non-national security system to an external system.','SC-07(27)','N/A','Determine if the direct connection of [SC-07(27)_ODP[01]; the unclassified, non-national security system prohibited from directly connecting to an external network is defined] to an external network without the use of a [SC-07(27)_ODP[02]; the boundary protection device required for a direct connection of unclassified, non-national security system to an external network is defined] is prohibited.'),
('004889','draft','2022-03-07','DISA','policy','Prohibit the direct connection of organization-defined system to a public network.','SC-07(28)','N/A','Determine if the direct connection of the [SC-07(28)_ODP; the system that is prohibited from directly connecting to a public network is defined] to a public network is prohibited.'),
('004890','draft','2022-03-07','DISA','policy','Defines the system that prohibits the direct connection to a public network.','SC-07(28)','N/A','Determine if the direct connection of the [SC-07(28)_ODP; the system that is prohibited from directly connecting to a public network is defined] to a public network is prohibited.'),
('004891','draft','2022-03-07','DISA','technical','Implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions.','SC-07(29)','N/A','Determine if subnetworks are separated [SC-07(29)_ODP[01]; one of the following PARAMETER VALUES is selected: {physically; logically}] to isolate [SC-07(29)_ODP[02]; critical system components and functions to be isolated are defined].'),
('004892','draft','2022-03-07','DISA','technical','Defines the critical system components to implement physically or logically separate subnetworks.','SC-07(29)','N/A','Determine if subnetworks are separated [SC-07(29)_ODP[01]; one of the following PARAMETER VALUES is selected: {physically; logically}] to isolate [SC-07(29)_ODP[02]; critical system components and functions to be isolated are defined].'),
('004893','draft','2022-03-07','DISA','technical','Implement organization-defined protection distribution system to prevent unauthorized disclosure of information, and/or detect changes to information during transmission.','SC-08(05)','N/A','Determine if the [SC-08(05)_ODP[01]; the protected distribution system is defined] is implemented to [SC-08(05)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {prevent unauthorized disclosure of information; detect changes to information}] during transmission.'),
('004894','draft','2022-03-07','DISA','technical','Defines the protected distribution system for preventing unauthorized disclosure of information, and/or detect changes to information during transmission.','SC-08(05)','N/A','Determine if the [SC-08(05)_ODP[01]; the protected distribution system is defined] is implemented to [SC-08(05)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {prevent unauthorized disclosure of information; detect changes to information}] during transmission.'),
('004895','draft','2022-03-07','DISA','technical','Permit users to invoke the trusted communications path for communications between the user and the organization-defined security functions, including at a minimum, authentication and re-authentication.','SC-11b.','N/A','Determine if users are permitted to invoke the trusted communication path for communications between the user and the [SC-11_ODP[02]; security functions of the system are defined] of the system, including authentication and re-authentication, at a minimum.'),
('004896','draft','2022-03-07','DISA','technical','Initiates the trusted communications path for communications between the organization-defined security functions of the system and the user.','SC-11(01)(b)','N/A','Determine if the trusted communication path for communications between the [SC-11(01)_ODP; security functions of the system are defined] of the system and the user is initiated.'),
('004897','draft','2022-03-07','DISA','technical','Defines the security functions to be initiated between the system and the user for trusted communications path for communications.','SC-11(01)(b)','N/A','Determine if the trusted communication path for communications between the [SC-11(01)_ODP; security functions of the system are defined] of the system and the user is initiated.'),
('004898','draft','2022-03-07','DISA','policy','Defines requirements for certificates that are issued for producing, controlling, and distributing asymmetric cryptographic keys.','SC-12(03)','N/A','Determine if: - asymmetric cryptographic keys are produced using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are controlled using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}]. - asymmetric cryptographic keys are distributed using [SC-12(03)_ODP; one of the following PARAMETER VALUES is selected: {NSA-approved key management technology and processes; prepositioned keying material; DoD-approved or DoD-issued Medium Assurance PKI certificates; DoD-approved or DoD-issued Medium Hardware Assurance PKI certificates and hardware security tokens that protect the user''s private key; certificates issued in accordance with organization-defined requirements}].'),
('004899','draft','2022-03-07','DISA','policy','Maintain physical control of cryptographic keys when store information is encrypted by external service providers.','SC-12(06)','N/A','Determine if physical control of cryptographic keys is maintained when stored information is encrypted by external service providers.'),
('004900','draft','2022-03-07','DISA','technical','Determine the organization-defined cryptographic uses.','SC-13b.','N/A','Determine if [SC-13_ODP[02]; types of cryptography for each specified cryptographic use are defined] for each specified cryptographic use (defined in SC-13_ODP[01]) are implemented.'),
('004901','draft','2022-03-07','DISA','technical','Associate organization-defined privacy attributes with information exchanged between systems.','SC-16','N/A','Determine if: - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between system components. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between system components.'),
('004902','draft','2022-03-07','DISA','technical','Associate organization-defined privacy attributes with information exchanged between system components.','SC-16','N/A','Determine if: - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between system components. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between system components.'),
('004903','draft','2022-03-07','DISA','policy','Defines the privacy attributes to associate with the information being exchanged between systems and between system components.','SC-16','N/A','Determine if: - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[01]; security attributes to be associated with information exchanged are defined] are associated with information exchanged between system components. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between systems. - [SC-16_ODP[02]; privacy attributes to be associated with information exchanged are defined] are associated with information exchanged between system components.'),
('004904','draft','2022-03-07','DISA','technical','Verify the integrity of transmitted privacy attributes.','SC-16(01)','N/A','Determine if: - the integrity of transmitted security attributes is verified. - the integrity of transmitted privacy attributes is verified.'),
('004905','draft','2022-03-07','DISA','technical','Implement anti-spoofing mechanisms to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.','SC-16(02)','N/A','Determine if anti-spoofing mechanisms are implemented to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.'),
('004906','draft','2022-03-07','DISA','technical','Implement organization-defined mechanisms or techniques to bind security attributes to transmitted information.','SC-16(03)','N/A','Determine if [SC-16(03)_ODP; mechanisms or techniques to bind security and privacy attributes to transmitted information are defined] are implemented to bind security and privacy attributes to transmitted information.'),
('004907','draft','2022-03-07','DISA','technical','Implement organization-defined mechanisms or techniques to bind privacy attributes to transmitted information.','SC-16(03)','N/A','Determine if [SC-16(03)_ODP; mechanisms or techniques to bind security and privacy attributes to transmitted information are defined] are implemented to bind security and privacy attributes to transmitted information.'),
('004908','draft','2022-03-07','DISA','technical','Defines the mechanisms or techniques for binding security and privacy attributes to transmitted information.','SC-16(03)','N/A','Determine if [SC-16(03)_ODP; mechanisms or techniques to bind security and privacy attributes to transmitted information are defined] are implemented to bind security and privacy attributes to transmitted information.'),
('004909','draft','2022-03-07','DISA','policy','Include only approved trust anchors in trust stores or certificate stores managed by the organization.','SC-17b.','N/A','Determine if only approved trust anchors are included in trust stores or certificate stores managed by the organization.'),
('004910','draft','2022-03-07','DISA','policy','Provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store.','SC-28(03)','N/A','Determine if protected storage for cryptographic keys is provided using [SC-28(03)_ODP[01]; one of the following PARAMETER VALUES is selected: {[SC-28(03)_ODP[02]; safeguards for protecting the storage of cryptographic keys are defined (if selected)]; hardware-protected key store}].'),
('004911','draft','2022-03-07','DISA','policy','Defines the safeguards for providing protected storage for cryptographic keys.','SC-28(03)','N/A','Determine if protected storage for cryptographic keys is provided using [SC-28(03)_ODP[01]; one of the following PARAMETER VALUES is selected: {[SC-28(03)_ODP[02]; safeguards for protecting the storage of cryptographic keys are defined (if selected)]; hardware-protected key store}].'),
('004912','draft','2022-03-07','DISA','policy','Partition privileged functions into separate physical domains.','SC-32(01)','N/A','Determine if privileged functions are partitioned into separate physical domains.'),
('004913','draft','2022-03-07','DISA','policy','Takes organization-defined actions in response to identified faults, errors, or compromises.','SC-36(01)(b)','N/A','Determine if [SC-36(01)_ODP[02]; actions to be taken in response to identified faults, errors, or compromise are defined] are taken in response to identified faults, errors, or compromise.'),
('004914','draft','2022-03-07','DISA','policy','Defines actions to take in response to identified faults, errors, or compromises.','SC-36(01)(b)','N/A','Determine if [SC-36(01)_ODP[02]; actions to be taken in response to identified faults, errors, or compromise are defined] are taken in response to identified faults, errors, or compromise.'),
('004915','draft','2022-03-07','DISA','policy','Synchronize the organization-defined duplicate systems or system components.','SC-36(02)','N/A','Determine if [SC-36(02)_ODP; duplicate systems or system components to be synchronized are defined] are synchronized.'),
('004916','draft','2022-03-07','DISA','policy','Defines the duplicate systems or system components to be synchronized.','SC-36(02)','N/A','Determine if [SC-36(02)_ODP; duplicate systems or system components to be synchronized are defined] are synchronized.'),
('004917','draft','2022-03-07','DISA','policy','Defines sensors to facilitate an individual''s awareness that personally identifiable information is being collected.','SC-42(04)','N/A','Determine if [SC-42(04)_ODP[01]; measures to facilitate an individual''s awareness that personally identifiable information is being collected are defined] are employed to facilitate an individual''s awareness that personally identifiable information is being collected by [SC-42(04)_ODP[02]; sensors that collect personally identifiable information are defined].'),
('004918','draft','2022-03-07','DISA','policy','Defines measures to facility an individual''s awareness that personally identifiable information is being collected.','SC-42(04)','N/A','Determine if [SC-42(04)_ODP[01]; measures to facilitate an individual''s awareness that personally identifiable information is being collected are defined] are employed to facilitate an individual''s awareness that personally identifiable information is being collected by [SC-42(04)_ODP[02]; sensors that collect personally identifiable information are defined].'),
('004919','draft','2022-03-07','DISA','policy','Employ organization-defined measures to facilitate an individual''s awareness that personally identifiable information is being collected by organization-defined sensors.','SC-42(04)','N/A','Determine if [SC-42(04)_ODP[01]; measures to facilitate an individual''s awareness that personally identifiable information is being collected are defined] are employed to facilitate an individual''s awareness that personally identifiable information is being collected by [SC-42(04)_ODP[02]; sensors that collect personally identifiable information are defined].'),
('004920','draft','2022-03-07','DISA','policy','Defines sensors that are configured to minimize the collection of information about individuals that is not needed.','SC-42(05)','N/A','Determine if the [SC-42(05)_ODP; the sensors that are configured to minimize the collection of unneeded information about individuals are defined] configured to minimize the collection of information about individuals that is not needed are employed.'),
('004921','draft','2022-03-07','DISA','policy','Employ organization-defined sensors that are configured to minimize the collection of information about individuals that is not needed.','SC-42(05)','N/A','Determine if the [SC-42(05)_ODP; the sensors that are configured to minimize the collection of unneeded information about individuals are defined] configured to minimize the collection of information about individuals that is not needed are employed.'),
('004922','draft','2022-03-07','DISA','technical','Synchronize system clocks within and between systems or system components.','SC-45','N/A','Determine if system clocks are synchronized within and between systems and system components.'),
('004923','draft','2022-03-07','DISA','technical','Compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.','SC-45(01)(a)','N/A','Determine if the internal system clocks are compared [SC-45(01)_ODP[01]; the frequency at which to compare the internal system clocks with the authoritative time source is defined] with [SC-45(01)_ODP[02]; the authoritative time source to which internal system clocks are to be compared is defined].'),
('004924','draft','2022-03-07','DISA','technical','Defines the frequency for comparing the internal system clocks with organization-defined authoritative time source.','SC-45(01)(a)','N/A','Determine if the internal system clocks are compared [SC-45(01)_ODP[01]; the frequency at which to compare the internal system clocks with the authoritative time source is defined] with [SC-45(01)_ODP[02]; the authoritative time source to which internal system clocks are to be compared is defined].'),
('004925','draft','2022-03-07','DISA','technical','Defines the time source used for comparing the internal system clocks.','SC-45(01)(a)','N/A','Determine if the internal system clocks are compared [SC-45(01)_ODP[01]; the frequency at which to compare the internal system clocks with the authoritative time source is defined] with [SC-45(01)_ODP[02]; the authoritative time source to which internal system clocks are to be compared is defined].'),
('004926','draft','2022-03-07','DISA','technical','Synchronize the internal system clocks to the authoritative time source when the time difference is greater than organization-defined time period.','SC-45(01)(b)','N/A','Determine if the internal system clocks are synchronized with the authoritative time source when the time difference is greater than [SC-45(01)_ODP[03]; the time period to compare the internal system clocks with the authoritative time source is defined].'),
('004927','draft','2022-03-07','DISA','technical','Defines the time period for synchronizing the internal system clocks to the authoritative time source.','SC-45(01)(b)','N/A','Determine if the internal system clocks are synchronized with the authoritative time source when the time difference is greater than [SC-45(01)_ODP[03]; the time period to compare the internal system clocks with the authoritative time source is defined].'),
('004928','draft','2022-03-07','DISA','technical','Identify a secondary authoritative time source that is in a different geographic region than the primary authoritative time source.','SC-45(02)(a)','N/A','Determine if a secondary authoritative time source is identified that is in a different geographic region than the primary authoritative time source.'),
('004929','draft','2022-03-07','DISA','technical','Synchronize the internal system clocks to the secondary authoritative time source if the primary authoritative time source is unavailable.','SC-45(02)(b)','N/A','Determine if the internal system clocks are synchronized to the secondary authoritative time source if the primary authoritative time source is unavailable.'),
('004930','draft','2022-03-07','DISA','technical','Implement a policy enforcement mechanism physically or logically between the physical and/or network interfaces for the connecting security domains.','SC-46','N/A','Determine if a policy enforcement mechanism is [SC-46_ODP; one of the following PARAMETER VALUES is selected: {physically; logically}] implemented between the physical and/or network interfaces for the connecting security domains.'),
('004931','draft','2022-03-07','DISA','policy','Establish organization-defined alternate communications paths for system operations organizational command and control.','SC-47','N/A','Determine if [SC-47_ODP; alternate communication paths for system operations and operational command and control are defined] are established for system operations and operational command and control.'),
('004932','draft','2022-03-07','DISA','policy','Relocate organization-defined sensors and monitoring capabilities to organization-defined locations under organization-defined conditions or circumstances.','SC-48','N/A','Determine if [SC-48_ODP[01]; sensors and monitoring capabilities to be relocated are defined] are relocated to [SC-48_ODP[02]; locations to where sensors and monitoring capabilities are to be relocated are defined] under [SC-48_ODP[03]; conditions or circumstances for relocating sensors and monitoring capabilities are defined].'),
('004933','draft','2022-03-07','DISA','policy','Defines the sensors and monitoring capabilities to be relocated to organization-defined locations.','SC-48','N/A','Determine if [SC-48_ODP[01]; sensors and monitoring capabilities to be relocated are defined] are relocated to [SC-48_ODP[02]; locations to where sensors and monitoring capabilities are to be relocated are defined] under [SC-48_ODP[03]; conditions or circumstances for relocating sensors and monitoring capabilities are defined].'),
('004934','draft','2022-03-07','DISA','policy','Defines the locations of which the organization-defined sensors and monitoring capabilities will be relocated.','SC-48','N/A','Determine if [SC-48_ODP[01]; sensors and monitoring capabilities to be relocated are defined] are relocated to [SC-48_ODP[02]; locations to where sensors and monitoring capabilities are to be relocated are defined] under [SC-48_ODP[03]; conditions or circumstances for relocating sensors and monitoring capabilities are defined].'),
('004935','draft','2022-03-07','DISA','policy','Defines the conditions or circumstances of which the organization-defined sensors and monitoring capabilities are relocated.','SC-48','N/A','Determine if [SC-48_ODP[01]; sensors and monitoring capabilities to be relocated are defined] are relocated to [SC-48_ODP[02]; locations to where sensors and monitoring capabilities are to be relocated are defined] under [SC-48_ODP[03]; conditions or circumstances for relocating sensors and monitoring capabilities are defined].'),
('004936','draft','2022-03-07','DISA','policy','Dynamically relocate organization-defined sensors and monitoring capabilities to organization-defined locations under organization-defined conditions or circumstances.','SC-48(01)','N/A','Determine if [SC-48(01)_ODP[01]; sensors and monitoring capabilities to be dynamically relocated are defined] are dynamically relocated to [SC-48(01)_ODP[02]; locations to where sensors and monitoring capabilities are to be dynamically relocated are defined] under [SC-48(01)_ODP[03]; conditions or circumstances for dynamically relocating sensors and monitoring capabilities are defined].'),
('004937','draft','2022-03-07','DISA','policy','Defines the sensors and monitoring capabilities to be dynamically relocated to organization-defined locations.','SC-48(01)','N/A','Determine if [SC-48(01)_ODP[01]; sensors and monitoring capabilities to be dynamically relocated are defined] are dynamically relocated to [SC-48(01)_ODP[02]; locations to where sensors and monitoring capabilities are to be dynamically relocated are defined] under [SC-48(01)_ODP[03]; conditions or circumstances for dynamically relocating sensors and monitoring capabilities are defined].'),
('004938','draft','2022-03-07','DISA','policy','Defines the locations of which the organization-defined sensors and monitoring capabilities will be dynamically relocated.','SC-48(01)','N/A','Determine if [SC-48(01)_ODP[01]; sensors and monitoring capabilities to be dynamically relocated are defined] are dynamically relocated to [SC-48(01)_ODP[02]; locations to where sensors and monitoring capabilities are to be dynamically relocated are defined] under [SC-48(01)_ODP[03]; conditions or circumstances for dynamically relocating sensors and monitoring capabilities are defined].'),
('004939','draft','2022-03-07','DISA','policy','Defines the conditions or circumstances of which the organization-defined sensors and monitoring capabilities are dynamically relocated.','SC-48(01)','N/A','Determine if [SC-48(01)_ODP[01]; sensors and monitoring capabilities to be dynamically relocated are defined] are dynamically relocated to [SC-48(01)_ODP[02]; locations to where sensors and monitoring capabilities are to be dynamically relocated are defined] under [SC-48(01)_ODP[03]; conditions or circumstances for dynamically relocating sensors and monitoring capabilities are defined].'),
('004940','draft','2022-03-07','DISA','policy','Implement hardware-enforced separation and policy enforcement mechanisms between organization-defined security domains.','SC-49','N/A','Determine if hardware-enforced separation and policy enforcement mechanisms are implemented between [SC-49_ODP; security domains requiring hardware-enforced separation and policy enforcement mechanisms are defined].'),
('004941','draft','2022-03-07','DISA','policy','Defines the security domains for implementing hardware-enforced separation and policy enforcement mechanisms.','SC-49','N/A','Determine if hardware-enforced separation and policy enforcement mechanisms are implemented between [SC-49_ODP; security domains requiring hardware-enforced separation and policy enforcement mechanisms are defined].'),
('004942','draft','2022-03-07','DISA','policy','Implement software-enforced separation and policy enforcement mechanisms between organization-defined security domains.','SC-50','N/A','Determine if software-enforced separation and policy enforcement mechanisms are implemented between [SC-50_ODP; security domains requiring software-enforced separation and policy enforcement mechanisms are defined].'),
('004943','draft','2022-03-07','DISA','policy','Defines the security domains for implementing software-enforced separation and policy enforcement mechanisms.','SC-50','N/A','Determine if software-enforced separation and policy enforcement mechanisms are implemented between [SC-50_ODP; security domains requiring software-enforced separation and policy enforcement mechanisms are defined].'),
('004944','draft','2022-03-07','DISA','policy','Develop and document an organization-level; mission/business process-level; and/or system level system and information integrity policy that is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.','SI-01a.01(b)','N/A','Determine if the [SI-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] system and information integrity policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('004945','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the development and documentation of the system and information integrity policy.','SI-01b.','N/A','Determine if the [SI-01_ODP[04]; an official to manage the system and information integrity policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures.'),
('004946','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the dissemination of the system and information integrity policy.','SI-01b.','N/A','Determine if the [SI-01_ODP[04]; an official to manage the system and information integrity policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures.'),
('004947','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the development and documentation of the system and information integrity procedures.','SI-01b.','N/A','Determine if the [SI-01_ODP[04]; an official to manage the system and information integrity policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures.'),
('004948','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the dissemination of the system and information integrity procedures.','SI-01b.','N/A','Determine if the [SI-01_ODP[04]; an official to manage the system and information integrity policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures.'),
('004949','draft','2022-03-07','DISA','policy','Defines the official designated for managing the development, documentation, and dissemination of the system and information integrity policy.','SI-01b.','N/A','Determine if the [SI-01_ODP[04]; an official to manage the system and information integrity policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures.'),
('004950','draft','2022-03-07','DISA','policy','Defines the official designated for managing the development, documentation, and dissemination of the system and information integrity procedures.','SI-01b.','N/A','Determine if the [SI-01_ODP[04]; an official to manage the system and information integrity policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures.'),
('004951','draft','2022-03-07','DISA','policy','Review and update the current system and information integrity policy following organization-defined events.','SI-01c.01','N/A','Determine if: - the current system and information integrity policy is reviewed and updated [SI-01_ODP[05]; the frequency at which the current system and information integrity policy is reviewed and updated is defined]. - the current system and information integrity policy is reviewed and updated following [SI-01_ODP[06]; events that would require the current system and information integrity policy to be reviewed and updated are defined].'),
('004952','draft','2022-03-07','DISA','policy','Defines the events following reviewing and updating the current system and information integrity policy.','SI-01c.01','N/A','Determine if: - the current system and information integrity policy is reviewed and updated [SI-01_ODP[05]; the frequency at which the current system and information integrity policy is reviewed and updated is defined]. - the current system and information integrity policy is reviewed and updated following [SI-01_ODP[06]; events that would require the current system and information integrity policy to be reviewed and updated are defined].'),
('004953','draft','2022-03-07','DISA','policy','Review and update the current system and information integrity procedures following organization-defined events.','SI-01c.02','N/A','Determine if: - the current system and information integrity procedures are reviewed and updated [SI-01_ODP[07]; the frequency at which the current system and information integrity procedures are reviewed and updated is defined]. - the current system and information integrity procedures are reviewed and updated following [SI-01_ODP[08]; events that would require the system and information integrity procedures to be reviewed and updated are defined].'),
('004954','draft','2022-03-07','DISA','policy','Defines the events following reviewing and updating the current system and information integrity procedures.','SI-01c.02','N/A','Determine if: - the current system and information integrity procedures are reviewed and updated [SI-01_ODP[07]; the frequency at which the current system and information integrity procedures are reviewed and updated is defined]. - the current system and information integrity procedures are reviewed and updated following [SI-01_ODP[08]; events that would require the system and information integrity procedures to be reviewed and updated are defined].'),
('004955','draft','2022-03-07','DISA','policy','Determine if system components have applicable security-related software updates installed using organization-defined mechanisms on an organization-defined frequency.','SI-02(02)','N/A','Determine if system components have applicable security-relevant software and firmware updates installed [SI-02(02)_ODP[02]; the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined] using [SI-02(02)_ODP[01]; automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined].'),
('004956','draft','2022-03-07','DISA','policy','Determine if system components have applicable security-related firmware updates installed using organization-defined mechanisms on an organization-defined frequency.','SI-02(02)','N/A','Determine if system components have applicable security-relevant software and firmware updates installed [SI-02(02)_ODP[02]; the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined] using [SI-02(02)_ODP[01]; automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined].'),
('004957','draft','2022-03-07','DISA','policy','Defines a frequency for installing security-relevant software updates using organization-defined automated mechanisms.','SI-02(02)','N/A','Determine if system components have applicable security-relevant software and firmware updates installed [SI-02(02)_ODP[02]; the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined] using [SI-02(02)_ODP[01]; automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined].'),
('004958','draft','2022-03-07','DISA','policy','Defines a frequency for installing security-relevant firmware updates using organization-defined automated mechanisms.','SI-02(02)','N/A','Determine if system components have applicable security-relevant software and firmware updates installed [SI-02(02)_ODP[02]; the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined] using [SI-02(02)_ODP[01]; automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined].'),
('004959','draft','2022-03-07','DISA','policy','Defines the automated mechanisms for determining if system components have applicable security-related software updates installed.','SI-02(02)','N/A','Determine if system components have applicable security-relevant software and firmware updates installed [SI-02(02)_ODP[02]; the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined] using [SI-02(02)_ODP[01]; automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined].'),
('004960','draft','2022-03-07','DISA','policy','Defines the automated mechanisms for determining if system components have applicable security-related firmware updates installed.','SI-02(02)','N/A','Determine if system components have applicable security-relevant software and firmware updates installed [SI-02(02)_ODP[02]; the frequency at which to determine if applicable security-relevant software and firmware updates are installed on system components is defined] using [SI-02(02)_ODP[01]; automated mechanisms to determine if applicable security-relevant software and firmware updates are installed on system components are defined].'),
('004961','draft','2022-03-07','DISA','policy','Employ automated patch management tools to facilitate flaw remediation to the organization-defined system components.','SI-02(04)','N/A','Determine if automated patch management tools are employed to facilitate flaw remediation to [SI-02(04)_ODP; the system components requiring automated patch management tools to facilitate flaw remediation are defined].'),
('004962','draft','2022-03-07','DISA','policy','Defines the system components on which patch management tools to facilitate flaw remediation are employed.','SI-02(04)','N/A','Determine if automated patch management tools are employed to facilitate flaw remediation to [SI-02(04)_ODP; the system components requiring automated patch management tools to facilitate flaw remediation are defined].'),
('004963','draft','2022-03-07','DISA','policy','Implement signature based and/or non-signature based malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code.','SI-03a.','N/A','Determine if: - [SI-03_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {signature-based; non-signature-based}] malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code. - [SI-03_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {signature-based; non-signature-based}] malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code.'),
('004964','draft','2022-03-07','DISA','policy','Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy.','SI-03b.','N/A','Determine if malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures.'),
('004965','draft','2022-03-07','DISA','policy','Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management procedures.','SI-03b.','N/A','Determine if malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures.'),
('004966','draft','2022-03-07','DISA','policy','Configure malicious code protection mechanisms to send alerts to organization-defined personnel in response to malicious code detection.','SI-03c.02','N/A','Determine if: - malicious code protection mechanisms are configured to [SI-03_ODP[04]; one or more of the following PARAMETER VALUES is/are selected: {block malicious code; quarantine malicious code; take [SI-03_ODP[05]; action to be taken in response to malicious code detection are defined (if selected)}] in response to malicious code detection. - malicious code protection mechanisms are configured to send alerts to [SI-03_ODP[06]; personnel or roles to be alerted when malicious code is detected is/are defined] in response to malicious code detection.'),
('004967','draft','2022-03-07','DISA','policy','Analyze detected events and anomalies.','SI-04d.','N/A','Determine if: - detected events are analyzed. - detected anomalies are analyzed.'),
('004968','draft','2022-03-07','DISA','technical','Employ automated mechanisms to support near real-time analysis of events.','SI-04(02)','N/A','Determine if automated tools and mechanisms are employed to support a near real-time analysis of events.'),
('004969','draft','2022-03-07','DISA','technical','Employ automated mechanisms to integrate intrusion detection mechanisms into access control mechanisms.','SI-04(03)','N/A','Determine if: - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into access control mechanisms. - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into flow control mechanisms.'),
('004970','draft','2022-03-07','DISA','technical','Employ automated mechanisms to integrate intrusion detection mechanisms into flow control mechanisms.','SI-04(03)','N/A','Determine if: - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into access control mechanisms. - automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into flow control mechanisms.'),
('004971','draft','2022-03-07','DISA','technical','Determine criteria for unusual or unauthorized activities or conditions for inbound communications traffic.','SI-04(04)(a)','N/A','Determine if: - criteria for unusual or unauthorized activities or conditions for inbound communications traffic are defined. - criteria for unusual or unauthorized activities or conditions for outbound communications traffic are defined.'),
('004972','draft','2022-03-07','DISA','technical','Determine criteria for unusual or unauthorized activities or conditions for outbound communications traffic.','SI-04(04)(a)','N/A','Determine if: - criteria for unusual or unauthorized activities or conditions for inbound communications traffic are defined. - criteria for unusual or unauthorized activities or conditions for outbound communications traffic are defined.'),
('004973','draft','2022-03-07','DISA','technical','Defines the unusual or unauthorized activities or conditions that will be monitored for inbound communications traffic.','SI-04(04)(b)','N/A','Determine if: - inbound communications traffic is monitored [SI-04(04)_ODP[01]; the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[02]; unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined]. - outbound communications traffic is monitored [SI-04(04)_ODP[03]; the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[04]; unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined].'),
('004974','draft','2022-03-07','DISA','technical','Defines the unusual or unauthorized activities or conditions that will be monitored for outbound communications traffic.','SI-04(04)(b)','N/A','Determine if: - inbound communications traffic is monitored [SI-04(04)_ODP[01]; the frequency at which to monitor inbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[02]; unusual or unauthorized activities or conditions that are to be monitored in inbound communications traffic are defined]. - outbound communications traffic is monitored [SI-04(04)_ODP[03]; the frequency at which to monitor outbound communications traffic for unusual or unauthorized activities or conditions is defined] for [SI-04(04)_ODP[04]; unusual or unauthorized activities or conditions that are to be monitored in outbound communications traffic are defined].'),
('004975','draft','2022-03-07','DISA','policy','Test intrusion monitoring mechanisms at an organization-defined frequency.','SI-04(09)','N/A','Determine if intrusion-monitoring tools and mechanisms are tested [SI-04(09)_ODP; a frequency at which to test intrusion-monitoring tools and mechanisms is defined].'),
('004976','draft','2022-03-07','DISA','policy','Defines the frequency for testing intrusion monitoring mechanisms.','SI-04(09)','N/A','Determine if intrusion-monitoring tools and mechanisms are tested [SI-04(09)_ODP; a frequency at which to test intrusion-monitoring tools and mechanisms is defined].'),
('004977','draft','2022-03-07','DISA','policy','Defines the encrypted communications traffic that is to be visible to organization-defined system monitoring mechanisms.','SI-04(10)','N/A','Determine if provisions are made so that [SI-04(10)_ODP[01]; encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined] is visible to [SI-04(10)_ODP[02]; system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined].'),
('004978','draft','2022-03-07','DISA','policy','Defines the system monitoring mechanisms that will have visibility into organization-defined encrypted communications traffic.','SI-04(10)','N/A','Determine if provisions are made so that [SI-04(10)_ODP[01]; encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined] is visible to [SI-04(10)_ODP[02]; system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined].'),
('004979','draft','2022-03-07','DISA','policy','Make provisions so that organization-defined encrypted communications traffic is visible to organization-defined system monitoring mechanisms.','SI-04(10)','N/A','Determine if provisions are made so that [SI-04(10)_ODP[01]; encrypted communications traffic to be made visible to system monitoring tools and mechanisms is defined] is visible to [SI-04(10)_ODP[02]; system monitoring tools and mechanisms to be provided access to encrypted communications traffic are defined].'),
('004980','draft','2022-03-07','DISA','policy','Defines the personnel or roles to receive alerts when indications of inappropriate or unusual activities with security or privacy occur.','SI-04(12)','N/A','Determine if [SI-04(12)_ODP[01]; personnel or roles to be alerted when indications of inappropriate or unusual activity with security or privacy implications occur is/are defined] is/are alerted using [SI-04(12)_ODP[02]; automated mechanisms used to alert personnel or roles are defined] when [SI-04(12)_ODP[03]; activities that trigger alerts to personnel or are defined] indicate inappropriate or unusual activities with security or privacy implications.'),
('004981','draft','2022-03-07','DISA','policy','Correlate information from monitoring mechanisms employed throughout the system.','SI-04(16)','N/A','Determine if information from monitoring tools and mechanisms employed throughout the system is correlated.'),
('004982','draft','2022-03-07','DISA','technical','Provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.','SI-04(25)','N/A','Determine if: - visibility into network traffic at external system interfaces is provided to optimize the effectiveness of monitoring devices. - visibility into network traffic at key internal system interfaces is provided to optimize the effectiveness of monitoring devices.'),
('004983','draft','2022-03-07','DISA','policy','Defines the automated mechanisms for broadcasting security alert and advisory information.','SI-05(01)','N/A','Determine if [SI-05(01)_ODP; automated mechanisms used to broadcast security alert and advisory information throughout the organization are defined] are used to broadcast security alert and advisory information throughout the organization.'),
('004984','draft','2022-03-07','DISA','policy','Defines the privacy functions that require verification of correct operation.','SI-06a.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified to be operating correctly. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified to be operating correctly.'),
('004985','draft','2022-03-07','DISA','technical','Verify correct operation of organization-defined privacy functions.','SI-06a.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified to be operating correctly. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified to be operating correctly.'),
('004986','draft','2022-03-07','DISA','policy','Defines the frequency at which it will verify correct operation of organization-defined privacy functions.','SI-06b.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}]. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}].'),
('004987','draft','2022-03-07','DISA','policy','Defines the system transitional states when the system will verify correct operation of organization-defined privacy functions.','SI-06b.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}]. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}].'),
('004988','draft','2022-03-07','DISA','technical','Perform verification of the correct operation of organization-defined privacy functions: when the system is in an organization-defined transitional state; upon command by a user with appropriate privileges; and/or on an organization-defined frequency.','SI-06b.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}]. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}].'),
('004989','draft','2022-03-07','DISA','technical','Alert organization-defined personnel or roles of failed privacy verification tests.','SI-06b.','N/A','Determine if: - [SI-06_ODP[01]; security functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}]. - [SI-06_ODP[02]; privacy functions to be verified for correct operation are defined] are verified [SI-06_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {[SI-06_ODP[04]; system transitional states requiring the verification of security and privacy functions are defined; (if selected]; upon command by user with appropriate privilege; [SI-06_ODP[05]; frequency at which to verify the correct operation of security and privacy functions is defined; (if selected]}].'),
('004990','draft','2022-03-07','DISA','policy','Defines the personnel or roles to be notified when privacy verification tests fail.','SI-06c.','N/A','Determine if: - [SI-06_ODP[06]; personnel or roles to be alerted of failed security and privacy verification tests is/are defined] is/are alerted to failed security verification tests. - [SI-06_ODP[06]; personnel or roles to be alerted of failed security and privacy verification tests is/are defined] is/are alerted to failed privacy verification tests.'),
('004991','draft','2022-03-07','DISA','policy','Defines alternative action(s) to be taken when anomalies in the operation of organization-defined privacy functions are discovered.','SI-06d.','N/A','Determine if [SI-06_ODP[07]; one or more of the following PARAMETER VALUES is/are selected: {shut the system down; restart the system; [SI-06_ODP[08]; alternative action(s) to be performed when anomalies are discovered are defined (if selected)]}] is/are initiated when anomalies are discovered.'),
('004992','draft','2022-03-07','DISA','technical','Shut the system down, restart the system, and/or initiate organization-defined alternative action(s) when anomalies in the operation of the organization-defined privacy functions are discovered.','SI-06d.','N/A','Determine if [SI-06_ODP[07]; one or more of the following PARAMETER VALUES is/are selected: {shut the system down; restart the system; [SI-06_ODP[08]; alternative action(s) to be performed when anomalies are discovered are defined (if selected)]}] is/are initiated when anomalies are discovered.'),
('004993','draft','2022-03-07','DISA','technical','Implement automated mechanisms to support the management of distributed privacy function testing.','SI-06(02)','N/A','Determine if: - automated mechanisms are implemented to support the management of distributed security function testing. - automated mechanisms are implemented to support the management of distributed privacy function testing.'),
('004994','draft','2022-03-07','DISA','policy','Report the results of privacy function verification to organization-defined personnel or roles.','SI-06(03)','N/A','Determine if: - the results of security function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined]. - the results of privacy function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined].'),
('004995','draft','2022-03-07','DISA','policy','Defines the personnel or roles that are to receive reports on the results of privacy function verification.','SI-06(03)','N/A','Determine if: - the results of security function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined]. - the results of privacy function verification are reported to [SI-06(03)_ODP; personnel or roles designated to receive the results of security and privacy function verification is/are defined].'),
('004996','draft','2022-03-07','DISA','policy','Take organization-defined actions when unauthorized changes to the software, firmware, and information are detected.','SI-07b.','N/A','Determine if: - [SI-07_ODP[04]; actions to be taken when unauthorized changes to software are detected are defined] are taken when unauthorized changes to the software are detected. - [SI-07_ODP[05]; actions to be taken when unauthorized changes to firmware are detected are defined] are taken when unauthorized changes to the firmware are detected. - [SI-07_ODP[06]; actions to be taken when unauthorized changes to information are detected are defined] are taken when unauthorized changes to the information are detected.'),
('004997','draft','2022-03-07','DISA','policy','Defines the actions to be taken when unauthorized changes to the software, firmware, and information are detected.','SI-07b.','N/A','Determine if: - [SI-07_ODP[04]; actions to be taken when unauthorized changes to software are detected are defined] are taken when unauthorized changes to the software are detected. - [SI-07_ODP[05]; actions to be taken when unauthorized changes to firmware are detected are defined] are taken when unauthorized changes to the firmware are detected. - [SI-07_ODP[06]; actions to be taken when unauthorized changes to information are detected are defined] are taken when unauthorized changes to the information are detected.'),
('004998','draft','2022-03-07','DISA','technical','Implement organization-defined controls for application self-protection at runtime.','SI-07(17)','N/A','Determine if [SI-07(17)_ODP; controls to be implemented for application self-protection at runtime are defined] are implemented for application self-protection at runtime.'),
('004999','draft','2022-03-07','DISA','policy','Defines the controls to be implemented for runtime application self-protection.','SI-07(17)','N/A','Determine if [SI-07(17)_ODP; controls to be implemented for application self-protection at runtime are defined] are implemented for application self-protection at runtime.'),
('005000','draft','2022-03-07','DISA','policy','Update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy.','SI-08b.','N/A','Determine if spam protection mechanisms are updated when new releases are available in accordance with organizational configuration management policies and procedures.'),
('005001','draft','2022-03-07','DISA','policy','Update spam protection mechanisms when new releases are available in accordance with organizational configuration management procedures.','SI-08b.','N/A','Determine if spam protection mechanisms are updated when new releases are available in accordance with organizational configuration management policies and procedures.'),
('005002','draft','2022-03-07','DISA','policy','Defines the frequency for updating spam protection mechanisms.','SI-08(02)','N/A','Determine if spam protection mechanisms are automatically updated [SI-08(02)_ODP; the frequency at which to automatically update spam protection mechanisms is defined].'),
('005003','draft','2022-03-07','DISA','technical','Prevent untrusted data injections.','SI-10(06)','N/A','Determine if untrusted data injections are prevented.'),
('005004','draft','2022-03-07','DISA','policy','Limit personally identifiable information being processed in the information life cycle to the organization-defined elements of personally identifiable information.','SI-12(01)','N/A','Determine if personally identifiable information being processed in the information life cycle is limited to [SI-12(01)_ODP; elements of personally identifiable information being processed in the information life cycle are defined].'),
('005005','draft','2022-03-07','DISA','policy','Defines the elements of personally identifiable information being processed in the information life cycle.','SI-12(01)','N/A','Determine if personally identifiable information being processed in the information life cycle is limited to [SI-12(01)_ODP; elements of personally identifiable information being processed in the information life cycle are defined].'),
('005006','draft','2022-03-07','DISA','policy','Use organization-defined techniques to minimize the use of personally identifiable information for research, testing, or training, in accordance with the privacy risk assessment.','SI-12(02)','N/A','Determine if: - [SI-12(02)_ODP[01]; techniques used to minimize the use of personally identifiable information for research are defined] are used to minimize the use of personally identifiable information for research. - [SI-12(02)_ODP[02]; techniques used to minimize the use of personally identifiable information for testing are defined] are used to minimize the use of personally identifiable information for testing. - [SI-12(02)_ODP[03]; techniques used to minimize the use of personally identifiable information for training are defined] are used to minimize the use of personally identifiable information for training.'),
('005007','draft','2022-03-07','DISA','policy','Defines the techniques for minimizing the use of personally identifiable information for research, testing, or training.','SI-12(02)','N/A','Determine if: - [SI-12(02)_ODP[01]; techniques used to minimize the use of personally identifiable information for research are defined] are used to minimize the use of personally identifiable information for research. - [SI-12(02)_ODP[02]; techniques used to minimize the use of personally identifiable information for testing are defined] are used to minimize the use of personally identifiable information for testing. - [SI-12(02)_ODP[03]; techniques used to minimize the use of personally identifiable information for training are defined] are used to minimize the use of personally identifiable information for training.'),
('005008','draft','2022-03-07','DISA','policy','Use organization-defined techniques to dispose of, destroy, or erase information following the retention period.','SI-12(03)','N/A','Determine if: - [SI-12(03)_ODP[01]; techniques used to dispose of information following the retention period are defined] are used to dispose of information following the retention period. - [SI-12(03)_ODP[02]; techniques used to destroy information following the retention period are defined] are used to destroy information following the retention period. - [SI-12(03)_ODP[03]; techniques used to erase information following the retention period are defined] are used to erase information following the retention period. '),
('005009','draft','2022-03-07','DISA','policy','Defines the percentage of the mean time to failure used to manually initiate transfer between active and standby system components.','SI-13(03)','N/A','Determine if transfers are initiated manually between active and standby system components when the use of the active component reaches [SI-13(03)_ODP; the percentage of the mean time to failure for transfers to be manually initiated is defined] of the mean time to failure.'),
('005010','draft','2022-03-07','DISA','policy','Defines the action to be taken when system failures are detected.','SI-13(04)(b)','N/A','Determine if [SI-13(04)_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {activate [SI-13(04)_ODP[03]; alarm to be activated when system component failures are detected is defined (if selected)]; automatically shut down the system; [SI-13(04)_ODP[04]; action to be taken when system component failures are detected is defined (if selected)]}] are performed if system component failures are detected.'),
('005011','draft','2022-03-07','DISA','policy','Refresh organization-defined information on an organization-defined frequency, or generate organization-defined information on demand.','SI-14(02)(a)','N/A','Determine if [SI-14(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {refresh [SI-14(02)_ODP[02]; the information to be refreshed is defined (if selected)] [SI-14(02)_ODP[03]; the frequency at which to refresh information is defined (if selected)]; generate [SI-14(02)_ODP[04]; the information to be generated is defined (if selected)] on demand}] is performed.'),
('005012','draft','2022-03-07','DISA','policy','Defines the information to be refreshed on an organization-defined frequency.','SI-14(02)(a)','N/A','Determine if [SI-14(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {refresh [SI-14(02)_ODP[02]; the information to be refreshed is defined (if selected)] [SI-14(02)_ODP[03]; the frequency at which to refresh information is defined (if selected)]; generate [SI-14(02)_ODP[04]; the information to be generated is defined (if selected)] on demand}] is performed.'),
('005013','draft','2022-03-07','DISA','policy','Defines the frequency at which to refresh organization-defined information.','SI-14(02)(a)','N/A','Determine if [SI-14(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {refresh [SI-14(02)_ODP[02]; the information to be refreshed is defined (if selected)] [SI-14(02)_ODP[03]; the frequency at which to refresh information is defined (if selected)]; generate [SI-14(02)_ODP[04]; the information to be generated is defined (if selected)] on demand}] is performed.'),
('005014','draft','2022-03-07','DISA','policy','Defines the information to be generated on demand.','SI-14(02)(a)','N/A','Determine if [SI-14(02)_ODP[01]; one of the following PARAMETER VALUES is selected: {refresh [SI-14(02)_ODP[02]; the information to be refreshed is defined (if selected)] [SI-14(02)_ODP[03]; the frequency at which to refresh information is defined (if selected)]; generate [SI-14(02)_ODP[04]; the information to be generated is defined (if selected)] on demand}] is performed.'),
('005015','draft','2022-03-07','DISA','policy','Delete information when no longer needed.','SI-14(02)(b)','N/A','Determine if information is deleted when no longer needed.'),
('005016','draft','2022-03-07','DISA','policy','Refresh connections to the system on demand.','SI-14(03)','N/A','Determine if: - connections to the system are established on demand. - connections to the system are terminated after [SI-14(03)_ODP; one of the following PARAMETER VALUES is selected: {completion of a request; a period of non-use}].'),
('005017','draft','2022-03-07','DISA','policy','Terminate connections after completion of a request, or a period of non-use.','SI-14(03)','N/A','Determine if: - connections to the system are established on demand. - connections to the system are terminated after [SI-14(03)_ODP; one of the following PARAMETER VALUES is selected: {completion of a request; a period of non-use}].'),
('005018','draft','2022-03-07','DISA','policy','Check the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle, on an organization-defined frequency.','SI-18a.','N/A','Determine if: - the accuracy of personally identifiable information across the information life cycle is checked [SI-18_ODP[01]; the frequency at which to check the accuracy of personally identifiable information across the information life cycle is defined]. - the relevance of personally identifiable information across the information life cycle is checked [SI-18_ODP[02]; the frequency at which to check the relevance of personally identifiable information across the information life cycle is defined]. - the timeliness of personally identifiable information across the information life cycle is checked [SI-18_ODP[03]; the frequency at which to check the timeliness of personally identifiable information across the information life cycle is defined]. - the completeness of personally identifiable information across the information life cycle is checked [SI-18_ODP[04]; the frequency at which to check the completeness of personally identifiable information across the information life cycle is defined].'),
('005019','draft','2022-03-07','DISA','policy','Defines the frequency for checking the accuracy, relevance, timeliness, and completeness of personally identifiable information.','SI-18a.','N/A','Determine if: - the accuracy of personally identifiable information across the information life cycle is checked [SI-18_ODP[01]; the frequency at which to check the accuracy of personally identifiable information across the information life cycle is defined]. - the relevance of personally identifiable information across the information life cycle is checked [SI-18_ODP[02]; the frequency at which to check the relevance of personally identifiable information across the information life cycle is defined]. - the timeliness of personally identifiable information across the information life cycle is checked [SI-18_ODP[03]; the frequency at which to check the timeliness of personally identifiable information across the information life cycle is defined]. - the completeness of personally identifiable information across the information life cycle is checked [SI-18_ODP[04]; the frequency at which to check the completeness of personally identifiable information across the information life cycle is defined].'),
('005020','draft','2022-03-07','DISA','policy','Correct or delete inaccurate or outdated personally identifiable information.','SI-18b.','N/A','Determine if inaccurate or outdated personally identifiable information is corrected or deleted.'),
('005021','draft','2022-03-07','DISA','policy','Correct or delete personally identifiable information that is inaccurate or outdated, incorrectly determined regarding impact, or incorrectly de-identified using organization-defined mechanisms.','SI-18(01)','N/A','Determine if [SI-18(01)_ODP; automated mechanisms used to correct or delete personally identifiable information that is inaccurate, outdated, incorrectly determined regarding impact, or incorrectly de-identified are defined] are used to correct or delete personally identifiable information that is inaccurate, outdated, incorrectly determined regarding impact, or incorrectly de-identified.'),
('005022','draft','2022-03-07','DISA','policy','Defines the automated mechanisms for identifying inaccurate or outdated, incorrectly determined regarding impact, or incorrectly de-identified personally identifiable information.','SI-18(01)','N/A','Determine if [SI-18(01)_ODP; automated mechanisms used to correct or delete personally identifiable information that is inaccurate, outdated, incorrectly determined regarding impact, or incorrectly de-identified are defined] are used to correct or delete personally identifiable information that is inaccurate, outdated, incorrectly determined regarding impact, or incorrectly de-identified.'),
('005023','draft','2022-03-07','DISA','policy','Employ data tags to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.','SI-18(02)','N/A','Determine if data tags are employed to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.'),
('005024','draft','2022-03-07','DISA','policy','Collect personally identifiable information directly from the individual.','SI-18(03)','N/A','Determine if personally identifiable information is collected directly from the individual.'),
('005025','draft','2022-03-07','DISA','policy','Correct or delete personally identifiable information upon request by individuals or their designated representatives.','SI-18(04)','N/A','Determine if personally identifiable information is corrected or deleted upon request by individuals or their designated representatives.'),
('005026','draft','2022-03-07','DISA','policy','Notify organization-defined recipients of personally identifiable information that the personally identifiable information has been corrected or deleted.','SI-18(05)','N/A','Determine if [SI-18(05)_ODP; recipients of personally identifiable information to be notified when the personally identifiable information has been corrected or deleted are defined] and individuals are notified when the personally identifiable information has been corrected or deleted.'),
('005027','draft','2022-03-07','DISA','policy','Defines the recipients of personally identifiable information who are to be notified when the personally identifiable information is corrected or deleted.','SI-18(05)','N/A','Determine if [SI-18(05)_ODP; recipients of personally identifiable information to be notified when the personally identifiable information has been corrected or deleted are defined] and individuals are notified when the personally identifiable information has been corrected or deleted.'),
('005028','draft','2022-03-07','DISA','policy','Notify individuals that the personally identifiable information has been corrected or deleted.','SI-18(05)','N/A','Determine if [SI-18(05)_ODP; recipients of personally identifiable information to be notified when the personally identifiable information has been corrected or deleted are defined] and individuals are notified when the personally identifiable information has been corrected or deleted.'),
('005029','draft','2022-03-07','DISA','policy','Remove the following elements of personally identifiable information from datasets.','SI-19a.','N/A','Determine if [SI-19_ODP[01]; elements of personally identifiable information to be removed from datasets are defined] are removed from datasets.'),
('005030','draft','2022-03-07','DISA','policy','Defines the elements of personally identifiable information to be removed from datasets.','SI-19a.','N/A','Determine if [SI-19_ODP[01]; elements of personally identifiable information to be removed from datasets are defined] are removed from datasets.'),
('005031','draft','2022-03-07','DISA','policy','Evaluate organization-defined frequency for effectiveness of de-identification.','SI-19b.','N/A','Determine if the effectiveness of de-identification is evaluated [SI-19_ODP[02]; the frequency at which to evaluate the effectiveness of de-identification is defined].'),
('005032','draft','2022-03-07','DISA','policy','Defines the frequency for evaluating for effectiveness of de-identification.','SI-19b.','N/A','Determine if the effectiveness of de-identification is evaluated [SI-19_ODP[02]; the frequency at which to evaluate the effectiveness of de-identification is defined].'),
('005033','draft','2022-03-07','DISA','policy','De-identify the dataset upon collection by not collecting personally identifiable information.','SI-19(01)','N/A','Determine if the dataset is de-identified upon collection by not collecting personally identifiable information.'),
('005034','draft','2022-03-07','DISA','policy','Prohibit archiving personally identifiable information elements if those elements in a dataset will not be needed after the dataset is archived.','SI-19(02)','N/A','Determine if the archiving of personally identifiable information elements is prohibited if those elements in a dataset will not be needed after the dataset is archived.'),
('005035','draft','2022-03-07','DISA','policy','Remove personally identifiable information elements from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.','SI-19(03)','N/A','Determine if personally identifiable information elements are removed from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.'),
('005036','draft','2022-03-07','DISA','technical','Remove, mask, encrypt, hash, or replace direct identifiers in a dataset.','SI-19(04)','N/A','Determine if direct identifiers in a dataset are removed, masked, encrypted, hashed, or replaced.'),
('005037','draft','2022-03-07','DISA','policy','Manipulate numerical data, contingency tables, and statistical findings so that no individual or organization is identifiable in the results of the analysis.','SI-19(05)','N/A','Determine if: - numerical data is manipulated so that no individual or organization is identifiable in the results of the analysis. - contingency tables are manipulated so that no individual or organization is identifiable in the results of the analysis. - statistical findings are manipulated so that no individual or organization is identifiable in the results of the analysis.'),
('005038','draft','2022-03-07','DISA','policy','Prevent disclosure of personally identifiable information by adding non-deterministic noise to the results of mathematical operations before the results are reported.','SI-19(06)','N/A','Determine if the disclosure of personally identifiable information is prevented by adding non-deterministic noise to the results of mathematical operations before the results are reported.'),
('005039','draft','2022-03-07','DISA','policy','Perform de-identification using validated algorithms and software that is validated to implement the algorithms.','SI-19(07)','N/A','Determine if: - de-identification is performed using validated algorithms. - de-identification is performed using software that is validated to implement the algorithms.'),
('005040','draft','2022-03-07','DISA','policy','Perform a motivated intruder test on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.','SI-19(08)','N/A','Determine if a motivated intruder test is performed on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.'),
('005041','draft','2022-03-07','DISA','policy','Embed data or capabilities in the following systems or system components to determine if organizational data has been exfiltrated or improperly removed from the organization.','SI-20','N/A','Determine if data or capabilities are embedded in [SI-20_ODP; the systems or system components with data or capabilities to be embedded are defined] to determine if organizational data has been exfiltrated or improperly removed from the organization.'),
('005042','draft','2022-03-07','DISA','policy','Defines the systems or system components used to determine if organizational data has been exfiltrated or improperly removed from the organization.','SI-20','N/A','Determine if data or capabilities are embedded in [SI-20_ODP; the systems or system components with data or capabilities to be embedded are defined] to determine if organizational data has been exfiltrated or improperly removed from the organization.'),
('005043','draft','2022-03-07','DISA','policy','Refresh organization-defined information at organization-defined frequencies or generate the information on demand and delete the information when no longer needed.','SI-21','N/A','Determine if the [SI-21_ODP[01]; the information to be refreshed is defined] is refreshed [SI-21_ODP[02]; the frequencies at which to refresh information are defined] or is generated on demand and deleted when no longer needed.'),
('005044','draft','2022-03-07','DISA','policy','Defines the information to be refreshed at organization-defined frequencies or generate the information on demand and delete the information when no longer needed.','SI-21','N/A','Determine if the [SI-21_ODP[01]; the information to be refreshed is defined] is refreshed [SI-21_ODP[02]; the frequencies at which to refresh information are defined] or is generated on demand and deleted when no longer needed.'),
('005045','draft','2022-03-07','DISA','policy','Defines the frequencies for refreshing organization-defined information.','SI-21','N/A','Determine if the [SI-21_ODP[01]; the information to be refreshed is defined] is refreshed [SI-21_ODP[02]; the frequencies at which to refresh information are defined] or is generated on demand and deleted when no longer needed.'),
('005046','draft','2022-03-07','DISA','policy','Identify the following alternate sources of information for organization-defined essential functions and services.','SI-22a.','N/A','Determine if [SI-22_ODP[01]; alternative information sources for essential functions and services are defined] for [SI-22_ODP[02]; essential functions and services that require alternative sources of information are defined] are identified.'),
('005047','draft','2022-03-07','DISA','policy','Defines the alternative information sources for identifying organization-defined essential functions and services.','SI-22a.','N/A','Determine if [SI-22_ODP[01]; alternative information sources for essential functions and services are defined] for [SI-22_ODP[02]; essential functions and services that require alternative sources of information are defined] are identified.'),
('005048','draft','2022-03-07','DISA','policy','Use an alternate information source for the execution of essential functions or services on organization-defined systems or system components when the primary source of information is corrupted or unavailable.','SI-22b.','N/A','Determine if an alternative information source is used for the execution of essential functions or services on [SI-22_ODP[03]; systems or system components that require an alternative information source for the execution of essential functions or services are defined] when the primary source of information is corrupted or unavailable.'),
('005049','draft','2022-03-07','DISA','policy','Defines the systems or system components used as an alternate information source for the execution of essential functions or services when the primary source of information is corrupted or unavailable.','SI-22b.','N/A','Determine if an alternative information source is used for the execution of essential functions or services on [SI-22_ODP[03]; systems or system components that require an alternative information source for the execution of essential functions or services are defined] when the primary source of information is corrupted or unavailable.'),
('005050','draft','2022-03-07','DISA','policy','Based on organization-defined circumstances, fragment the following information.','SI-23a.','N/A','Determine if under [SI-23_ODP[01]; circumstances that require information fragmentation are defined], [SI-23_ODP[02]; the information to be fragmented is defined] is fragmented.'),
('005051','draft','2022-03-07','DISA','policy','Defines the information for fragmentation.','SI-23a.','N/A','Determine if under [SI-23_ODP[01]; circumstances that require information fragmentation are defined], [SI-23_ODP[02]; the information to be fragmented is defined] is fragmented.'),
('005052','draft','2022-03-07','DISA','policy','Defines the circumstances for fragmenting organization-defined information.','SI-23a.','N/A','Determine if under [SI-23_ODP[01]; circumstances that require information fragmentation are defined], [SI-23_ODP[02]; the information to be fragmented is defined] is fragmented.'),
('005053','draft','2022-03-07','DISA','policy','Based on organization-defined circumstances, distribute the fragmented information across the following systems or system components.','SI-23b.','N/A','Determine if under [SI-23_ODP[01]; circumstances that require information fragmentation are defined], the fragmented information is distributed across [SI-23_ODP[03]; systems or system components across which the fragmented information is to be distributed are defined].'),
('005054','draft','2022-03-07','DISA','policy','Defines the systems or system components used to distribute fragmented information.','SI-23b.','N/A','Determine if under [SI-23_ODP[01]; circumstances that require information fragmentation are defined], the fragmented information is distributed across [SI-23_ODP[03]; systems or system components across which the fragmented information is to be distributed are defined].'),
('005055','draft','2022-03-07','DISA','policy','Defines the circumstances for distributing fragmented information across organization-defined systems or system components.','SI-23b.','N/A','Determine if under [SI-23_ODP[01]; circumstances that require information fragmentation are defined], the fragmented information is distributed across [SI-23_ODP[03]; systems or system components across which the fragmented information is to be distributed are defined].'),
('005056','draft','2022-03-07','DISA','policy','Disseminate an organization-level, mission/business process-level, and/or system-level supply chain risk management policy to organization-defined personnel or roles.','SR-01a.','N/A','Determine if: - a supply chain risk management policy is developed and documented. - the supply chain risk management policy is disseminated to [SR-01_ODP[01]; personnel or roles to whom supply chain risk management policy is to be disseminated to is/are defined].'),
('005057','draft','2022-03-07','DISA','policy','Develop and document an organization-level, mission/business process-level, and/or system-level supply chain risk management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.','SR-01a.01(a)','N/A','Determine if: - the [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses purpose. - the [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses scope. - [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses roles. - the [SR-01_ODP[03];one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses responsibilities. - the [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses management commitment. - the [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses coordination among organizational entities. - the [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy addresses compliance.'),
('005058','draft','2022-03-07','DISA','policy','Develop and document organization-level, mission/business process-level, and/or system-level supply chain risk management policy that is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.','SR-01a.01(b)','N/A','Determine if the [SR-01_ODP[03]; one or more of the following PARAMETER VALUES is/are selected: {organization-level; mission/business process-level; system-level}] supply chain risk management policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines.'),
('005059','draft','2022-03-07','DISA','policy','Develop and document procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls.','SR-01a.02','N/A','Determine if: - supply chain risk management procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls are developed and documented. - the supply chain risk management procedures are disseminated to [SR-01_ODP[02]; personnel or roles to whom supply chain risk management procedures are disseminated to is/are defined].'),
('005060','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the development and documentation of the supply chain risk management policy.','SR-01b.','N/A','Determine if the [SR-01_ODP[04]; an official to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures.'),
('005061','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the development and documentation of the supply chain risk management procedures.','SR-01b.','N/A','Determine if the [SR-01_ODP[04]; an official to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures.'),
('005062','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the dissemination of the supply chain risk management policy.','SR-01b.','N/A','Determine if the [SR-01_ODP[04]; an official to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures.'),
('005063','draft','2022-03-07','DISA','policy','Designate an organization-defined official to manage the dissemination of the supply chain risk management procedures.','SR-01b.','N/A','Determine if the [SR-01_ODP[04]; an official to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures is defined] is designated to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures.'),
('005064','draft','2022-03-07','DISA','policy','Review and update the current supply chain risk management policy on an organization-defined frequency.','SR-01c.01','N/A','Determine if: - the current supply chain risk management policy is reviewed and updated [SR-01_ODP[05]; the frequency at which the current supply chain risk management policy is reviewed and updated is defined]. - the current supply chain risk management policy is reviewed and updated following [SR-01_ODP[06]; events that require the current supply chain risk management policy to be reviewed and updated are defined].'),
('005065','draft','2022-03-07','DISA','policy','Defines the frequency for reviewing and updating the current supply chain risk management policy.','SR-01c.01','N/A','Determine if: - the current supply chain risk management policy is reviewed and updated [SR-01_ODP[05]; the frequency at which the current supply chain risk management policy is reviewed and updated is defined]. - the current supply chain risk management policy is reviewed and updated following [SR-01_ODP[06]; events that require the current supply chain risk management policy to be reviewed and updated are defined].'),
('005066','draft','2022-03-07','DISA','policy','Review and update the current supply chain risk management policy following organization-defined events.','SR-01c.01','N/A','Determine if: - the current supply chain risk management policy is reviewed and updated [SR-01_ODP[05]; the frequency at which the current supply chain risk management policy is reviewed and updated is defined]. - the current supply chain risk management policy is reviewed and updated following [SR-01_ODP[06]; events that require the current supply chain risk management policy to be reviewed and updated are defined].'),
('005067','draft','2022-03-07','DISA','policy','Defines the events following reviewing and updating the current supply chain risk management policy.','SR-01c.01','N/A','Determine if: - the current supply chain risk management policy is reviewed and updated [SR-01_ODP[05]; the frequency at which the current supply chain risk management policy is reviewed and updated is defined]. - the current supply chain risk management policy is reviewed and updated following [SR-01_ODP[06]; events that require the current supply chain risk management policy to be reviewed and updated are defined].'),
('005068','draft','2022-03-07','DISA','policy','Review and update the current supply chain risk management procedures on an organization-defined frequency.','SR-01c.02','N/A','Determine if: - the current supply chain risk management procedures are reviewed and updated [SR-01_ODP[07]; the frequency at which the current supply chain risk management procedure is reviewed and updated is defined]. - the current supply chain risk management procedures are reviewed and updated following [SR-01_ODP[08]; events that require the supply chain risk management procedures to be reviewed and updated are defined].'),
('005069','draft','2022-03-07','DISA','policy','Defines the frequency for reviewing and updating the current supply chain risk management procedures.','SR-01c.02','N/A','Determine if: - the current supply chain risk management procedures are reviewed and updated [SR-01_ODP[07]; the frequency at which the current supply chain risk management procedure is reviewed and updated is defined]. - the current supply chain risk management procedures are reviewed and updated following [SR-01_ODP[08]; events that require the supply chain risk management procedures to be reviewed and updated are defined].'),
('005070','draft','2022-03-07','DISA','policy','Review and update the current supply chain risk management procedures following organization-defined events.','SR-01c.02','N/A','Determine if: - the current supply chain risk management procedures are reviewed and updated [SR-01_ODP[07]; the frequency at which the current supply chain risk management procedure is reviewed and updated is defined]. - the current supply chain risk management procedures are reviewed and updated following [SR-01_ODP[08]; events that require the supply chain risk management procedures to be reviewed and updated are defined].'),
('005071','draft','2022-03-07','DISA','policy','Defines the events following reviewing and updating the current supply chain risk management procedures.','SR-01c.02','N/A','Determine if: - the current supply chain risk management procedures are reviewed and updated [SR-01_ODP[07]; the frequency at which the current supply chain risk management procedure is reviewed and updated is defined]. - the current supply chain risk management procedures are reviewed and updated following [SR-01_ODP[08]; events that require the supply chain risk management procedures to be reviewed and updated are defined].'),
('005072','draft','2022-03-07','DISA','policy','Develop a plan for managing supply chain risks associated with the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of the following systems, system components, or system services.','SR-02a.','N/A','Determine if: - a plan for managing supply chain risks is developed. - the supply chain risk management plan addresses risks associated with the research and development of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the design of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the manufacturing of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the acquisition of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the delivery of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the integration of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the operation and maintenance of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the disposal of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined].'),
('005073','draft','2022-03-07','DISA','policy','Defines the systems, system components, or system services that a plan for managing supply chain risks are developed.','SR-02a.','N/A','Determine if: - a plan for managing supply chain risks is developed. - the supply chain risk management plan addresses risks associated with the research and development of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the design of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the manufacturing of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the acquisition of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the delivery of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the integration of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the operation and maintenance of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined]. - the supply chain risk management plan addresses risks associated with the disposal of [SR-02_ODP[01]; systems, system components, or system services for which a supply chain risk management plan is developed are defined].'),
('005074','draft','2022-03-07','DISA','policy','Review and update the supply chain risk management plan on an organization-defined frequency, or as required, to address threat, organizational or environmental changes.','SR-02b.','N/A','Determine if the supply chain risk management plan is reviewed and updated [SR-02_ODP[02]; the frequency at which to review and update the supply chain risk management plan is defined] or as required to address threat, organizational, or environmental changes.'),
('005075','draft','2022-03-07','DISA','policy','Defines the frequency for reviewing and updating the supply chain risk management plan.','SR-02b.','N/A','Determine if the supply chain risk management plan is reviewed and updated [SR-02_ODP[02]; the frequency at which to review and update the supply chain risk management plan is defined] or as required to address threat, organizational, or environmental changes.'),
('005076','draft','2022-03-07','DISA','policy','Protect the supply chain risk management plan from unauthorized disclosure and modification.','SR-02c.','N/A','Determine if: - the supply chain risk management plan is protected from unauthorized disclosure. - the supply chain risk management plan is protected from unauthorized modification.'),
('005077','draft','2022-03-07','DISA','policy','Establish a supply chain risk management team consisting of organization-defined personnel, roles, and responsibilities to lead and support the following SCRM activities.','SR-02(01)','N/A','Determine if a supply chain risk management team consisting of [SR-02(01)_ODP[01]; the personnel, roles, and responsibilities of the supply chain risk management team are defined] is established to lead and support [SR-02(01)_ODP[02]; supply chain risk management activities are defined].'),
('005078','draft','2022-03-07','DISA','policy','Defines the supply chain risk management activities that will be led by a supply chain risk management team consisting of organization-defined personnel, roles, and responsibilities.','SR-02(01)','N/A','Determine if a supply chain risk management team consisting of [SR-02(01)_ODP[01]; the personnel, roles, and responsibilities of the supply chain risk management team are defined] is established to lead and support [SR-02(01)_ODP[02]; supply chain risk management activities are defined].'),
('005079','draft','2022-03-07','DISA','policy','Defines the personnel, roles, and responsibilities who lead and support organization-defined supply chain risk management activities.','SR-02(01)','N/A','Determine if a supply chain risk management team consisting of [SR-02(01)_ODP[01]; the personnel, roles, and responsibilities of the supply chain risk management team are defined] is established to lead and support [SR-02(01)_ODP[02]; supply chain risk management activities are defined].'),
('005080','draft','2022-03-07','DISA','policy','Establish a process of processes to identify and address weaknesses or deficiencies in the supply chain elements of organization-defined system or system components in coordination with organization-defined supply chain personnel.','SR-03a.','N/A','Determine if: - a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined]. - the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined] is/are coordinated with [SR-03_ODP[02]; supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined].'),
('005081','draft','2022-03-07','DISA','policy','Defines the system or system processes which establish a process or processes for identifying and addressing weaknesses or deficiencies in the supply chain elements.','SR-03a.','N/A','Determine if: - a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined]. - the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined] is/are coordinated with [SR-03_ODP[02]; supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined].'),
('005082','draft','2022-03-07','DISA','policy','Defines the supply chain personnel who, in coordination, establish a process or processes for identifying and addressing weaknesses or deficiencies in the supply chain elements.','SR-03a.','N/A','Determine if: - a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined]. - the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined] is/are coordinated with [SR-03_ODP[02]; supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined].'),
('005083','draft','2022-03-07','DISA','policy','Establish a process of processes to identify and address weaknesses or deficiencies in the processes of organization-defined system or system components in coordination with organization-defined supply chain personnel.','SR-03a.','N/A','Determine if: - a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined]. - the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined] is/are coordinated with [SR-03_ODP[02]; supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined].'),
('005084','draft','2022-03-07','DISA','policy','Defines the system or system processes which establish a process or processes for identifying and addressing weaknesses or deficiencies in the supply chain processes.','SR-03a.','N/A','Determine if: - a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined]. - the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined] is/are coordinated with [SR-03_ODP[02]; supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined].'),
('005085','draft','2022-03-07','DISA','policy','Defines the supply chain personnel who, in coordination, establish a process or processes for identifying and addressing weaknesses or deficiencies in the supply chain processes.','SR-03a.','N/A','Determine if: - a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined]. - the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [SR-03_ODP[01]; the system or system component requiring a process or processes to identify and address weaknesses or deficiencies is defined] is/are coordinated with [SR-03_ODP[02]; supply chain personnel with whom to coordinate the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes is/are defined].'),
('005086','draft','2022-03-07','DISA','policy','Employ the following controls to protect against supply chain risks to the system, system component, or system service.','SR-03b.','N/A','Determine if [SR-03_ODP[03]; supply chain controls employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events are defined] are employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events.'),
('005087','draft','2022-03-07','DISA','policy','Limit the harm or consequences from supply chain-related events.','SR-03b.','N/A','Determine if [SR-03_ODP[03]; supply chain controls employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events are defined] are employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events.'),
('005088','draft','2022-03-07','DISA','policy','Defines the supply chain controls employed for protecting against supply chain risks to the system, system component, or system service.','SR-03b.','N/A','Determine if [SR-03_ODP[03]; supply chain controls employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events are defined] are employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events.'),
('005089','draft','2022-03-07','DISA','policy','Document the selected and implemented supply chain processes and controls in security and privacy plans, supply chain risk management plan, or organization-defined document.','SR-03c.','N/A','Determine if the selected and implemented supply chain processes and controls are documented in [SR-03_ODP[04]; one or more of the following PARAMETER VALUES is/are selected: {security and privacy plans; supply chain risk management plan; [SR-03_ODP[05]; the document identifying the selected and implemented supply chain processes and controls is defined (if selected)]}].'),
('005090','draft','2022-03-07','DISA','policy','Defines the document which contains supply chain processes and controls.','SR-03c.','N/A','Determine if the selected and implemented supply chain processes and controls are documented in [SR-03_ODP[04]; one or more of the following PARAMETER VALUES is/are selected: {security and privacy plans; supply chain risk management plan; [SR-03_ODP[05]; the document identifying the selected and implemented supply chain processes and controls is defined (if selected)]}].'),
('005091','draft','2022-03-07','DISA','policy','Employ a diverse set of sources for the following system components and services.','SR-03(01)','N/A','Determine if: - a diverse set of sources is employed for [SR-03(01)_ODP[01]; system components with a diverse set of sources are defined]. - a diverse set of sources is employed for [SR-03(01)_ODP[02]; services with a diverse set of sources are defined].'),
('005092','draft','2022-03-07','DISA','policy','Defines the system or system components and services which employ a diverse set of sources.','SR-03(01)','N/A','Determine if: - a diverse set of sources is employed for [SR-03(01)_ODP[01]; system components with a diverse set of sources are defined]. - a diverse set of sources is employed for [SR-03(01)_ODP[02]; services with a diverse set of sources are defined].'),
('005093','draft','2022-03-07','DISA','policy','Employ the following controls to limit harm from potential adversaries identifying and targeting the organizational supply chain.','SR-03(02)','N/A','Determine if [SR-03(02)_ODP; controls to limit harm from potential supply chain adversaries are defined] are employed to limit harm from potential adversaries identifying and targeting the organizational supply chain.'),
('005094','draft','2022-03-07','DISA','policy','Defines the controls to be employed to limit harm from potential adversaries identifying and targeting the organizational supply chain.','SR-03(02)','N/A','Determine if [SR-03(02)_ODP; controls to limit harm from potential supply chain adversaries are defined] are employed to limit harm from potential adversaries identifying and targeting the organizational supply chain.'),
('005095','draft','2022-03-07','DISA','policy','Ensure that the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.','SR-03(03)','N/A','Determine if the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.'),
('005096','draft','2022-03-07','DISA','policy','Document valid provenance of the following systems, system components, and associated data.','SR-04','N/A','Determine if: - valid provenance is documented for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is monitored for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is maintained for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined].'),
('005097','draft','2022-03-07','DISA','policy','Monitor valid provenance of the following systems, system components, and associated data.','SR-04','N/A','Determine if: - valid provenance is documented for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is monitored for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is maintained for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined].'),
('005098','draft','2022-03-07','DISA','policy','Maintain valid provenance of the following systems, system components, and associated data.','SR-04','N/A','Determine if: - valid provenance is documented for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is monitored for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is maintained for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined].'),
('005099','draft','2022-03-07','DISA','policy','Defines the systems, system components, and associated data for documenting, monitoring, and maintaining valid provenance.','SR-04','N/A','Determine if: - valid provenance is documented for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is monitored for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined]. - valid provenance is maintained for [SR-04_ODP; systems, system components, and associated data that require valid provenance are defined].'),
('005100','draft','2022-03-07','DISA','policy','Establish and maintain unique identification of the following supply chain elements, processes, and personnel associated with the identified system and critical system components.','SR-04(01)','N/A','Determine if: - unique identification of [SR-04(01)_ODP; supply chain elements, processes, and personnel associated with systems and critical system components that require unique identification are defined] is established. - unique identification of [SR-04(01)_ODP; supply chain elements, processes, and personnel associated with systems and critical system components that require unique identification are defined] is maintained.'),
('005101','draft','2022-03-07','DISA','policy','Defines the supply chain elements, processes, and personnel associated with organization-defined systems and critical system components for establishing and maintaining unique identification.','SR-04(01)','N/A','Determine if: - unique identification of [SR-04(01)_ODP; supply chain elements, processes, and personnel associated with systems and critical system components that require unique identification are defined] is established. - unique identification of [SR-04(01)_ODP; supply chain elements, processes, and personnel associated with systems and critical system components that require unique identification are defined] is maintained.'),
('005102','draft','2022-03-07','DISA','policy','Establish and maintain unique identification of the following systems and critical components for tracking through the supply chain.','SR-04(02)','N/A','Determine if: - the unique identification of [SR-04(02)_ODP; systems and critical system components that require unique identification for tracking through the supply chain are defined] is established for tracking through the supply chain. - the unique identification of [SR-04(02)_ODP; systems and critical system components that require unique identification for tracking through the supply chain are defined] is maintained for tracking through the supply chain.'),
('005103','draft','2022-03-07','DISA','policy','Defines the systems and critical system components for tracking through the supply chain.','SR-04(02)','N/A','Determine if: - the unique identification of [SR-04(02)_ODP; systems and critical system components that require unique identification for tracking through the supply chain are defined] is established for tracking through the supply chain. - the unique identification of [SR-04(02)_ODP; systems and critical system components that require unique identification for tracking through the supply chain are defined] is maintained for tracking through the supply chain.'),
('005104','draft','2022-03-07','DISA','policy','Employ the following controls to validate that the system or system component received is genuine.','SR-04(03)','N/A','Determine if: - [SR-04(03)_ODP[01]; controls to validate that the system or system component received is genuine are defined] are employed to validate that the system or system component received is genuine. - [SR-04(03)_ODP[02]; controls to validate that the system or system component received has not been altered are defined] are employed to validate that the system or system component received has not been altered.'),
('005105','draft','2022-03-07','DISA','policy','Employ the following controls to validate that the system or system component received has not been altered.','SR-04(03)','N/A','Determine if: - [SR-04(03)_ODP[01]; controls to validate that the system or system component received is genuine are defined] are employed to validate that the system or system component received is genuine. - [SR-04(03)_ODP[02]; controls to validate that the system or system component received has not been altered are defined] are employed to validate that the system or system component received has not been altered.'),
('005106','draft','2022-03-07','DISA','policy','Defines the controls for validating that the system or system component received is genuine.','SR-04(03)','N/A','Determine if: - [SR-04(03)_ODP[01]; controls to validate that the system or system component received is genuine are defined] are employed to validate that the system or system component received is genuine. - [SR-04(03)_ODP[02]; controls to validate that the system or system component received has not been altered are defined] are employed to validate that the system or system component received has not been altered.'),
('005107','draft','2022-03-07','DISA','policy','Defines the controls for validating that the system or system component received has not been altered.','SR-04(03)','N/A','Determine if: - [SR-04(03)_ODP[01]; controls to validate that the system or system component received is genuine are defined] are employed to validate that the system or system component received is genuine. - [SR-04(03)_ODP[02]; controls to validate that the system or system component received has not been altered are defined] are employed to validate that the system or system component received has not been altered.'),
('005108','draft','2022-03-07','DISA','policy','Employ organization-defined controls to ensure the integrity of the system and system components by validating the internal composition and provenance of critical or mission essential technologies, products, and services.','SR-04(04)','N/A','Determine if: - [SR-04(04)_ODP[01]; controls employed to ensure that the integrity of the system and system component are defined] are employed to ensure the integrity of the system and system components. - [SR-04(04)_ODP[02]; an analysis method to be conducted to validate the internal composition and provenance of critical or mission-essential technologies, products, and services to ensure the integrity of the system and system component is defined] is conducted to ensure the integrity of the system and system components.'),
('005109','draft','2022-03-07','DISA','policy','Defines the controls for ensuring the integrity of the system and system components.','SR-04(04)','N/A','Determine if: - [SR-04(04)_ODP[01]; controls employed to ensure that the integrity of the system and system component are defined] are employed to ensure the integrity of the system and system components. - [SR-04(04)_ODP[02]; an analysis method to be conducted to validate the internal composition and provenance of critical or mission-essential technologies, products, and services to ensure the integrity of the system and system component is defined] is conducted to ensure the integrity of the system and system components.'),
('005110','draft','2022-03-07','DISA','policy','Conduct organization-defined analysis to ensure the integrity of the system and system components by validating the internal composition and provenance of critical or mission essential technologies, products, and services.','SR-04(04)','N/A','Determine if: - [SR-04(04)_ODP[01]; controls employed to ensure that the integrity of the system and system component are defined] are employed to ensure the integrity of the system and system components. - [SR-04(04)_ODP[02]; an analysis method to be conducted to validate the internal composition and provenance of critical or mission-essential technologies, products, and services to ensure the integrity of the system and system component is defined] is conducted to ensure the integrity of the system and system components.'),
('005111','draft','2022-03-07','DISA','policy','Defines the analysis for ensuring the integrity of the system and system components.','SR-04(04)','N/A','Determine if: - [SR-04(04)_ODP[01]; controls employed to ensure that the integrity of the system and system component are defined] are employed to ensure the integrity of the system and system components. - [SR-04(04)_ODP[02]; an analysis method to be conducted to validate the internal composition and provenance of critical or mission-essential technologies, products, and services to ensure the integrity of the system and system component is defined] is conducted to ensure the integrity of the system and system components.'),
('005112','draft','2022-03-07','DISA','policy','Employ the following acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks.','SR-05','N/A','Determine if: - [SR-05_ODP; acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined] are employed to protect against supply chain risks. - [SR-05_ODP; acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined] are employed to identify supply chain risks. - [SR-05_ODP; acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined] are employed to mitigate supply chain risks.'),
('005113','draft','2022-03-07','DISA','policy','Defines the acquisition strategies, contract tools, and procurement methods for protecting against, identifying, and mitigating supply chain risks.','SR-05','N/A','Determine if: - [SR-05_ODP; acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined] are employed to protect against supply chain risks. - [SR-05_ODP; acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined] are employed to identify supply chain risks. - [SR-05_ODP; acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined] are employed to mitigate supply chain risks.'),
('005114','draft','2022-03-07','DISA','policy','Employ the following controls to ensure an adequate supply of organization-defined critical system components.','SR-05(01)','N/A','Determine if [SR-05(01)_ODP[01]; controls to ensure an adequate supply of critical system components are defined] are employed to ensure an adequate supply of [SR-05(01)_ODP[02]; critical system components of which an adequate supply is required are defined].'),
('005115','draft','2022-03-07','DISA','policy','Defines the controls for ensuring an adequate supply of organization-defined critical system components.','SR-05(01)','N/A','Determine if [SR-05(01)_ODP[01]; controls to ensure an adequate supply of critical system components are defined] are employed to ensure an adequate supply of [SR-05(01)_ODP[02]; critical system components of which an adequate supply is required are defined].'),
('005116','draft','2022-03-07','DISA','policy','Defines the critical system components that the organization-defined controls ensure an adequate supply of.','SR-05(01)','N/A','Determine if [SR-05(01)_ODP[01]; controls to ensure an adequate supply of critical system components are defined] are employed to ensure an adequate supply of [SR-05(01)_ODP[02]; critical system components of which an adequate supply is required are defined].'),
('005117','draft','2022-03-07','DISA','policy','Access the system, system component, or system service prior to selection, acceptance, modification, or update.','SR-05(02)','N/A','Determine if: - the system, system component, or system service is assessed prior to selection. - the system, system component, or system service is assessed prior to acceptance. - the system, system component, or system service is assessed prior to modification. - the system, system component, or system service is assessed prior to update.'),
('005118','draft','2022-03-07','DISA','policy','Access and review the supply chain-related risks associated with suppliers or contractors and the system, system component, or system service they provide on an organization-defined frequency.','SR-06','N/A','Determine if the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide are assessed and reviewed [SR-06_ODP; the frequency at which to assess and review the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide is defined].'),
('005119','draft','2022-03-07','DISA','policy','Defines the frequency for assessing and reviewing the supply chain risks.','SR-06','N/A','Determine if the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide are assessed and reviewed [SR-06_ODP; the frequency at which to assess and review the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide is defined].'),
('005120','draft','2022-03-07','DISA','policy','Employ organizational analysis, independent third-party analysis, organizational testing, and/or independent third-party testing of the following supply chain elements, processes, and actors associated with the system, system component, or system service.','SR-06(01)','N/A','Determine if [SR-06(01)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {organizational analysis; independent third-party analysis; organizational testing; independent third-party testing}] is/are employed on [SR-06(01)_ODP[02]; supply chain elements, processes, and actors to be analyzed and tested are defined] associated with the system, system component, or system service.'),
('005121','draft','2022-03-07','DISA','policy','Defines the supply chain elements, processes, and actors for employing organizational analysis, independent third-party analysis, organizational testing, and/or independent third-party testing.','SR-06(01)','N/A','Determine if [SR-06(01)_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {organizational analysis; independent third-party analysis; organizational testing; independent third-party testing}] is/are employed on [SR-06(01)_ODP[02]; supply chain elements, processes, and actors to be analyzed and tested are defined] associated with the system, system component, or system service.'),
('005122','draft','2022-03-07','DISA','policy','Employ the following Operations Security (OPSEC) controls to protect supply chain-related information for the system, system component, or system service.','SR-07','N/A','Determine if [SR-07_ODP; Operations Security (OPSEC) controls to protect supply chain-related information for the system, system component, or system service are defined] are employed to protect supply chain-related information for the system, system component, or system service.'),
('005123','draft','2022-03-07','DISA','policy','Defines the Operations Security (OPSEC) controls that protect supply chain-related information for the system, system component, or system service.','SR-07','N/A','Determine if [SR-07_ODP; Operations Security (OPSEC) controls to protect supply chain-related information for the system, system component, or system service are defined] are employed to protect supply chain-related information for the system, system component, or system service.'),
('005124','draft','2022-03-07','DISA','policy','Establish agreements and procedures with entities involved in the supply chain for the system, system component, or system service for the notification of supply chain compromises, results of assessments or audits, and/or organization-defined information.','SR-08','N/A','Determine if agreements and procedures are established with entities involved in the supply chain for the system, system components, or system service for [SR-08_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {notification of supply chain compromises; [SR-08_ODP[02]; information for which agreements and procedures are to be established are defined (if selected)]}].'),
('005125','draft','2022-03-07','DISA','policy','Defines the information for establishing agreements and procedures with entities involved in the supply chain for the system, system component, or system service.','SR-08','N/A','Determine if agreements and procedures are established with entities involved in the supply chain for the system, system components, or system service for [SR-08_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {notification of supply chain compromises; [SR-08_ODP[02]; information for which agreements and procedures are to be established are defined (if selected)]}].'),
('005126','draft','2022-03-07','DISA','policy','Implement a tamper protection program for the system, system component, or system service.','SR-09','N/A','Determine if a tamper protection program is implemented for the system, system component, or system service.'),
('005127','draft','2022-03-07','DISA','policy','Employ anti-tamper technologies, tool, and techniques throughout the system development life cycle.','SR-09(01)','N/A','Determine if anti-tamper technologies, tools, and techniques are employed throughout the system development life cycle.'),
('005128','draft','2022-03-07','DISA','policy','Inspect the following systems or system components at random, at organization-defined frequency, and/or upon organization-defined indications of need for inspection to detect tampering.','SR-10','N/A','Determine if [SR-10_ODP[01]; systems or system components that require inspection are defined] are inspected [SR-10_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at random; at [SR-10_ODP[03]; frequency at which to inspect systems or system components is defined (if selected)]; upon [SR-10_ODP[04]; indications of the need for an inspection of systems or system components are defined (if selected)]}] to detect tampering.'),
('005129','draft','2022-03-07','DISA','policy','Defines the frequency for inspecting systems or system components.','SR-10','N/A','Determine if [SR-10_ODP[01]; systems or system components that require inspection are defined] are inspected [SR-10_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at random; at [SR-10_ODP[03]; frequency at which to inspect systems or system components is defined (if selected)]; upon [SR-10_ODP[04]; indications of the need for an inspection of systems or system components are defined (if selected)]}] to detect tampering.'),
('005130','draft','2022-03-07','DISA','policy','Defines the indications of need for inspection for detecting tampering.','SR-10','N/A','Determine if [SR-10_ODP[01]; systems or system components that require inspection are defined] are inspected [SR-10_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at random; at [SR-10_ODP[03]; frequency at which to inspect systems or system components is defined (if selected)]; upon [SR-10_ODP[04]; indications of the need for an inspection of systems or system components are defined (if selected)]}] to detect tampering.'),
('005131','draft','2022-03-07','DISA','policy','Defines the system or system components which will be inspected at random, at organization-defined frequency, and/or upon organization-defined indications of need for inspection to detect tampering.','SR-10','N/A','Determine if [SR-10_ODP[01]; systems or system components that require inspection are defined] are inspected [SR-10_ODP[02]; one or more of the following PARAMETER VALUES is/are selected: {at random; at [SR-10_ODP[03]; frequency at which to inspect systems or system components is defined (if selected)]; upon [SR-10_ODP[04]; indications of the need for an inspection of systems or system components are defined (if selected)]}] to detect tampering.'),
('005132','draft','2022-03-07','DISA','policy','Develop and document anti-counterfeit policy that include the means to detect and prevent counterfeit components from entering the system.','SR-11a.','N/A','Determine if: - an anti-counterfeit policy is developed and implemented. - anti-counterfeit procedures are developed and implemented. - the anti-counterfeit procedures include the means to detect counterfeit components entering the system. - the anti-counterfeit procedures include the means to prevent counterfeit components from entering the system.'),
('005133','draft','2022-03-07','DISA','policy','Develop and document anti-counterfeit procedures that include the means to detect and prevent counterfeit components from entering the system.','SR-11a.','N/A','Determine if: - an anti-counterfeit policy is developed and implemented. - anti-counterfeit procedures are developed and implemented. - the anti-counterfeit procedures include the means to detect counterfeit components entering the system. - the anti-counterfeit procedures include the means to prevent counterfeit components from entering the system.'),
('005134','draft','2022-03-07','DISA','policy','Report counterfeit system components to source of counterfeit component, organization-defined external reporting organizations, and/or organization-defined personnel or roles.','SR-11b.','N/A','Determine if counterfeit system components are reported to [SR-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {source of counterfeit component; [SR-11_ODP[02]; external reporting organizations to whom counterfeit system components are to be reported is/are defined (if selected)]; [SR-11_ODP[03]; personnel or roles to whom counterfeit system components are to be reported is/are defined (if selected)]}].'),
('005135','draft','2022-03-07','DISA','policy','Defines the external reporting organizations who report counterfeit system components.','SR-11b.','N/A','Determine if counterfeit system components are reported to [SR-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {source of counterfeit component; [SR-11_ODP[02]; external reporting organizations to whom counterfeit system components are to be reported is/are defined (if selected)]; [SR-11_ODP[03]; personnel or roles to whom counterfeit system components are to be reported is/are defined (if selected)]}].'),
('005136','draft','2022-03-07','DISA','policy','Defines the personnel or roles who report counterfeit system components.','SR-11b.','N/A','Determine if counterfeit system components are reported to [SR-11_ODP[01]; one or more of the following PARAMETER VALUES is/are selected: {source of counterfeit component; [SR-11_ODP[02]; external reporting organizations to whom counterfeit system components are to be reported is/are defined (if selected)]; [SR-11_ODP[03]; personnel or roles to whom counterfeit system components are to be reported is/are defined (if selected)]}].'),
('005137','draft','2022-03-07','DISA','policy','Train organization-defined personnel or roles to detect counterfeit system components including hardware, software, and firmware.','SR-11(01)','N/A','Determine if [SR-11(01)_ODP; personnel or roles requiring training to detect counterfeit system components (including hardware, software, and firmware) is/are defined] are trained to detect counterfeit system components (including hardware, software, and firmware).'),
('005138','draft','2022-03-07','DISA','policy','Defines the personnel or roles who are trained to detect counterfeit system components (including hardware, software, and firmware).','SR-11(01)','N/A','Determine if [SR-11(01)_ODP; personnel or roles requiring training to detect counterfeit system components (including hardware, software, and firmware) is/are defined] are trained to detect counterfeit system components (including hardware, software, and firmware).'),
('005139','draft','2022-03-07','DISA','policy','Maintain configuration control over the following system components awaiting service or repair.','SR-11(02)','N/A','Determine if: - configuration control over [SR-11(02)_ODP; system components requiring configuration control are defined] awaiting service or repair is maintained. - configuration control over serviced or repaired [SR-11(02)_ODP; system components requiring configuration control are defined] awaiting return to service is maintained.'),
('005140','draft','2022-03-07','DISA','policy','Maintain configuration control over serviced or repaired components awaiting return to service.','SR-11(02)','N/A','Determine if: - configuration control over [SR-11(02)_ODP; system components requiring configuration control are defined] awaiting service or repair is maintained. - configuration control over serviced or repaired [SR-11(02)_ODP; system components requiring configuration control are defined] awaiting return to service is maintained.'),
('005141','draft','2022-03-07','DISA','policy','Defines the system components awaiting service or repair.','SR-11(02)','N/A','Determine if: - configuration control over [SR-11(02)_ODP; system components requiring configuration control are defined] awaiting service or repair is maintained. - configuration control over serviced or repaired [SR-11(02)_ODP; system components requiring configuration control are defined] awaiting return to service is maintained.'),
('005142','draft','2022-03-07','DISA','policy','Scan for counterfeit system components on an organization-defined frequency.','SR-11(03)','N/A','Determine if scanning for counterfeit system components is conducted [SR-11(03)_ODP; the frequency at which to scan for counterfeit system components is defined].'),
('005143','draft','2022-03-07','DISA','policy','Defines the frequency for which the counterfeit system components are scanned.','SR-11(03)','N/A','Determine if scanning for counterfeit system components is conducted [SR-11(03)_ODP; the frequency at which to scan for counterfeit system components is defined].'),
('005144','draft','2022-03-07','DISA','policy','Dispose of organization-defined data, documentation, tools, or system components using the following techniques and methods.','SR-12','N/A','Determine if [SR-12_ODP[01]; data, documentation, tools, or system components to be disposed of are defined] are disposed of using [SR-12_ODP[02]; techniques and methods for disposing of data, documentation, tools, or system components are defined].'),
('005145','draft','2022-03-07','DISA','policy','Defines the data, documentation, tools, or system components which are to be disposed of using organization-defined techniques and methods.','SR-12','N/A','Determine if [SR-12_ODP[01]; data, documentation, tools, or system components to be disposed of are defined] are disposed of using [SR-12_ODP[02]; techniques and methods for disposing of data, documentation, tools, or system components are defined].'),
('005146','draft','2022-03-07','DISA','policy','Defines the techniques or methods used to dispose of organization-defined data, documentation, tools, or system components.','SR-12','N/A','Determine if [SR-12_ODP[01]; data, documentation, tools, or system components to be disposed of are defined] are disposed of using [SR-12_ODP[02]; techniques and methods for disposing of data, documentation, tools, or system components are defined].'),
('005147','draft','2022-03-08','DISA','policy','Provide basic privacy literacy training to system users (including managers, senior executives, and contractors) as part of initial training for new users.','AT-02a.01','N/A','Determine if: - security literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users. - privacy literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users. - security literacy training is provided to system users (including managers, senior executives, and contractors) [AT-02_ODP[01]; the frequency at which to provide security literacy training to system users (including managers, senior executives, and contractors) after initial training is defined] thereafter. - privacy literacy training is provided to system users (including managers, senior executives, and contractors) [AT-02_ODP[02]; the frequency at which to provide privacy literacy training to system users (including managers, senior executives, and contractors) after initial training is defined] thereafter.'),
('005149','draft','2023-07-17','DISA FSO','policy','Implement organization-defined measures to disassociate individuals from audit information transmitted across organizational boundaries.',NULL,'N/A',NULL),
('005150','draft','2023-07-17','DISA FSO','policy','Identify, prioritize, and assess suppliers of critical or mission-essential technologies, products, and services.',NULL,'N/A',NULL),
('005151','draft','2024-11-18','DISA','policy','Review and update incident response training content at an organization-defined frequency and following organization-defined events.',NULL,'N/A',NULL),
('005152','draft','2024-11-18','DISA','policy','Defines the frequency to review and update incident response training content.',NULL,'N/A',NULL),
('005153','draft','2024-11-18','DISA','policy','Defines events that require the review and update of incident response training content.',NULL,'N/A',NULL),
('005154','draft','2024-11-18','DISA','policy','Increase the availability of incident response information and support using organization-defined automated mechanisms.',NULL,'N/A',NULL),
('005155','draft','2025-01-23','DISA','policy','Employ identity providers and authorization servers to manage user, device, and non-person entity (NPE) identities, attributes, and access rights supporting authentication and authorization decisions in accordance with organization-defined identification and authentication policy using organization-defined mechanisms.',NULL,'N/A',NULL),
('005156','draft','2025-01-23','DISA','policy','Cryptographic keys that protect access tokens are generated, managed, and protected from disclosure and misuse.',NULL,'N/A',NULL),
('005157','draft','2025-01-23','DISA','policy','The private keys used to sign assertions and tokens are protected commensurate with the impact of the system and information resources that can be accessed.',NULL,'N/A',NULL),
('005158','draft','2025-01-23','DISA','technical','Assertions are generated in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005159','draft','2025-01-23','DISA','technical','Assertions are issued in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005160','draft','2025-01-23','DISA','technical','Assertions are refreshed in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005161','draft','2025-01-23','DISA','technical','Assertions are revoked in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005162','draft','2025-01-23','DISA','technical','Assertions are time-restricted in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005163','draft','2025-01-23','DISA','technical','Assertions are audience-restricted in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005164','draft','2025-01-23','DISA','technical','Access tokens are generated in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005165','draft','2025-01-23','DISA','technical','Access tokens are issued in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005166','draft','2025-01-23','DISA','technical','Access tokens are refreshed in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005167','draft','2025-01-23','DISA','technical','Access tokens are revoked in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005168','draft','2025-01-23','DISA','technical','Access tokens are time-restricted in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL),
('005169','draft','2025-01-23','DISA','technical','Access tokens are audience-restricted in accordance with organization-defined identification and authentication policy.',NULL,'N/A',NULL);
/*!40000 ALTER TABLE `cci` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Data for table `cci_reference_map`
--
LOCK TABLES `cci_reference_map` WRITE;
/*!40000 ALTER TABLE `cci_reference_map` DISABLE KEYS */;
INSERT INTO `cci_reference_map` (`cci`, `creator`, `title`, `version`, `location`, `indexDisa`, `textRefNist`, `parentControl`) VALUES ('000002','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1 (a)','AC-1a1(a)','AC-1'),
('000003','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 1','AC-1c1','AC-1'),
('000005','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 2','AC-1a2','AC-1'),
('000006','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 2','AC-1c2','AC-1'),
('000010','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 e','AC-2e','AC-2'),
('000011','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('000012','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 j','AC-2j','AC-2'),
('000015','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (1)','AC-2(1)','AC-2'),
('000016','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2(2)','AC-2'),
('000017','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3) (d)','AC-2(3)(d)','AC-2'),
('000018','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2(4)','AC-2'),
('000019','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (5)','AC-2(5)','AC-2'),
('000021','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (2)','AC-3(2)','AC-3'),
('000024','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (5)','AC-3(5)','AC-3'),
('000026','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (2)','AC-4(2)','AC-4'),
('000027','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (3)','AC-4(3)','AC-4'),
('000028','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (4)','AC-4(4)','AC-4'),
('000029','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (5)','AC-4(5)','AC-4'),
('000030','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (6)','AC-4(6)','AC-4'),
('000031','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (7)','AC-4(7)','AC-4'),
('000032','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8) (a)','AC-4(8)(a)','AC-4'),
('000034','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (10)','AC-4(10)','AC-4'),
('000035','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (11)','AC-4(11)','AC-4'),
('000039','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (2)','AC-6(2)','AC-6'),
('000041','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6(3)','AC-6'),
('000042','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6(3)','AC-6'),
('000043','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 a','AC-7a','AC-7'),
('000044','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 a','AC-7a','AC-7'),
('000048','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a','AC-8a','AC-8'),
('000050','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 b','AC-8b','AC-8'),
('000052','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9','AC-9','AC-9'),
('000053','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (1)','AC-9(1)','AC-9'),
('000054','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
('000055','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
('000056','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 b','AC-11b','AC-11'),
('000057','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 a','AC-11a','AC-11'),
('000059','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 a','AC-11a','AC-11'),
('000060','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-11 (1)','AC-11(1)','AC-11'),
('000061','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-14 a','AC-14a','AC-14'),
('000065','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 b','AC-17b','AC-17'),
('000067','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (1)','AC-17(1)','AC-17'),
('000068','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (2)','AC-17(2)','AC-17'),
('000069','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (3)','AC-17(3)','AC-17'),
('000070','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17(4)(a)','AC-17'),
('000072','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (6)','AC-17(6)','AC-17'),
('000073','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 1','PM-1a1','PM-1'),
('000074','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 4','PM-1a4','PM-1'),
('000075','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 b','PM-1b','PM-1'),
('000076','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 b','PM-1b','PM-1'),
('000078','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-2','PM-2','PM-2'),
('000080','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 a','PM-3a','PM-3'),
('000083','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a','AC-19'),
('000084','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 b','AC-19b','AC-19'),
('000093','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a 1','AC-20a1','AC-20'),
('000097','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (2)','AC-20(2)','AC-20'),
('000098','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 a','AC-21a','AC-21'),
('000099','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 (1)','AC-21(1)','AC-21'),
('000100','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1 (a)','AT-1a1(a)','AT-1'),
('000101','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1 (a)','AT-1a1(a)','AT-1'),
('000102','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 c 1','AT-1c1','AT-1'),
('000103','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 2','AT-1a2','AT-1'),
('000104','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 2','AT-1a2','AT-1'),
('000105','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 c 2','AT-1c2','AT-1'),
('000106','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 a 1','AT-2a1','AT-2'),
('000107','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (1)','AT-2(1)','AT-2'),
('000108','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 a 1','AT-3a1','AT-3'),
('000109','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 a 2','AT-3a2','AT-3'),
('000112','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 a 2','AT-2a2','AT-2'),
('000113','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 a','AT-4a','AT-4'),
('000114','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 a','AT-4a','AT-4'),
('000117','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1 (a)','AU-1a1(a)','AU-1'),
('000119','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 1','AU-1c1','AU-1'),
('000120','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a2','AU-1'),
('000122','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 2','AU-1c2','AU-1'),
('000123','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 a','AU-2a','AU-2'),
('000124','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 b','AU-2b','AU-2'),
('000125','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 d','AU-2d','AU-2'),
('000126','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 c','AU-2c','AU-2'),
('000130','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 a','AU-3a','AU-3'),
('000131','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 b','AU-3b','AU-3'),
('000132','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 c','AU-3c','AU-3'),
('000133','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 d','AU-3d','AU-3'),
('000134','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 e','AU-3e','AU-3'),
('000135','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (1)','AU-3(1)','AU-3'),
('000139','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 a','AU-5a','AU-5'),
('000140','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 b','AU-5b','AU-5'),
('000141','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 c','PM-3c','PM-3'),
('000142','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a1','PM-4'),
('000145','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (3)','AU-5(3)','AU-5'),
('000147','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5(2)','AU-5'),
('000148','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a','AU-6'),
('000149','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 b','AU-6b','AU-6'),
('000151','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a','AU-6'),
('000153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (3)','AU-6(3)','AU-6'),
('000154','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (4)','AU-6(4)','AU-6'),
('000158','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (1)','AU-7(1)','AU-7'),
('000159','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 a','AU-8a','AU-8'),
('000162','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 a','AU-9a','AU-9'),
('000163','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 a','AU-9a','AU-9'),
('000164','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 a','AU-9a','AU-9'),
('000165','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (1)','AU-9(1)','AU-9'),
('000166','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10','AU-10','AU-10'),
('000167','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-11','AU-11','AU-11'),
('000168','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-11','AU-11','AU-11'),
('000169','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 a','AU-12a','AU-12'),
('000170','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 2','PM-4a2','PM-4'),
('000171','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 b','AU-12b','AU-12'),
('000172','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 c','AU-12c','AU-12'),
('000173','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12(1)','AU-12'),
('000174','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12(1)','AU-12'),
('000176','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 b','IA-5b','IA-5'),
('000182','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 f','IA-5f','IA-5'),
('000183','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 g','IA-5g','IA-5'),
('000184','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 h','IA-5h','IA-5'),
('000185','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (b) (1)','IA-5(2)(b)(1)','IA-5'),
('000186','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (a) (1)','IA-5(2)(a)(1)','IA-5'),
('000187','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (a) (2)','IA-5(2)(a)(2)','IA-5'),
('000197','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (c)','IA-5(1)(c)','IA-5'),
('000201','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (6)','IA-5(6)','IA-5'),
('000204','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (8)','IA-5(8)','IA-5'),
('000206','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-6','IA-6','IA-6'),
('000209','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
('000210','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
('000211','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
('000212','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-7','PM-7','PM-7'),
('000213','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3','AC-3','AC-3'),
('000216','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-8','PM-8','PM-8'),
('000217','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3)','AC-2(3)','AC-2'),
('000219','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (13)','AC-4(13)','AC-4'),
('000225','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6','AC-6','AC-6'),
('000227','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 a 1','PM-9a1','PM-9'),
('000228','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 b','PM-9b','PM-9'),
('000232','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-14 b','AC-14b','AC-14'),
('000233','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 b','PM-10b','PM-10'),
('000234','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 c','PM-10c','PM-10'),
('000235','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 a','PM-11a','PM-11'),
('000236','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 b','PM-11b','PM-11'),
('000238','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 1','CA-1c1','CA-1'),
('000239','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1 (a)','CA-1a1(a)','CA-1'),
('000240','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1 (a)','CA-1a1(a)','CA-1'),
('000241','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 1','CA-1c1','CA-1'),
('000242','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a2','CA-1'),
('000243','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a2','CA-1'),
('000244','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 2','CA-1c2','CA-1'),
('000246','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 b 1','CA-2b1','CA-2'),
('000247','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 b 2','CA-2b2','CA-2'),
('000248','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 b 3','CA-2b3','CA-2'),
('000251','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 d','CA-2d','CA-2'),
('000252','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 d','CA-2d','CA-2'),
('000253','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 e','CA-2e','CA-2'),
('000254','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 f','CA-2f','CA-2'),
('000255','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (1)','CA-2(1)','CA-2'),
('000256','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2(2)','CA-2'),
('000258','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 b','CA-3b','CA-3'),
('000259','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 b','CA-3b','CA-3'),
('000264','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 a','CA-5a','CA-5'),
('000265','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 b','CA-5b','CA-5'),
('000266','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 b','CA-5b','CA-5'),
('000267','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5(1)','CA-5'),
('000268','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5(1)','CA-5'),
('000269','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5(1)','CA-5'),
('000270','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 a','CA-6a','CA-6'),
('000271','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 c 2','CA-6c2','CA-6'),
('000272','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 e','CA-6e','CA-6'),
('000273','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 e','CA-6e','CA-6'),
('000274','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7','CA-7','CA-7'),
('000279','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 c','CA-7c','CA-7'),
('000280','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g','CA-7'),
('000281','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g','CA-7'),
('000282','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (1)','CA-7(1)','CA-7'),
('000286','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 1','CM-1c1','CM-1'),
('000287','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1 (a)','CM-1a1(a)','CM-1'),
('000289','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 1','CM-1c1','CM-1'),
('000290','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a2','CM-1'),
('000292','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a2','CM-1'),
('000295','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 a','CM-2a','CM-2'),
('000296','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 b 1','CM-2b1','CM-2'),
('000297','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 b 2','CM-2b2','CM-2'),
('000300','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2(2)','CM-2'),
('000301','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2(2)','CM-2'),
('000302','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2(2)','CM-2'),
('000303','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2(2)','CM-2'),
('000304','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (3)','CM-2(3)','CM-2'),
('000311','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (6)','CM-2(6)','CM-2'),
('000312','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (6)','CM-2(6)','CM-2'),
('000313','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 a','CM-3a','CM-3'),
('000314','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 b','CM-3b','CM-3'),
('000316','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 e','CM-3e','CM-3'),
('000318','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 f','CM-3f','CM-3'),
('000319','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g','CM-3'),
('000320','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g','CM-3'),
('000321','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g','CM-3'),
('000322','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (a)','CM-3(1)(a)','CM-3'),
('000323','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (b)','CM-3(1)(b)','CM-3'),
('000324','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (c)','CM-3(1)(c)','CM-3'),
('000325','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (d)','CM-3(1)(d)','CM-3'),
('000326','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (e)','CM-3(1)(e)','CM-3'),
('000327','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (2)','CM-3(2)','CM-3'),
('000328','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (2)','CM-3(2)','CM-3'),
('000329','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (2)','CM-3(2)','CM-3'),
('000330','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (3)','CM-3(3)','CM-3'),
('000331','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (3)','CM-3(3)','CM-3'),
('000332','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3(4)','CM-3'),
('000333','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4','CM-4','CM-4'),
('000335','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4(2)','CM-4'),
('000336','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4(2)','CM-4'),
('000337','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4(2)','CM-4'),
('000340','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
('000341','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
('000344','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
('000345','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
('000353','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5(4)','CM-5'),
('000354','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5(4)','CM-5'),
('000366','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 b','CM-6b','CM-6'),
('000367','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c','CM-6'),
('000368','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c','CM-6'),
('000369','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c','CM-6'),
('000370','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6(1)','CM-6'),
('000371','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6(1)','CM-6'),
('000372','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6(1)','CM-6'),
('000380','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 b','CM-7b','CM-7'),
('000381','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 a','CM-7a','CM-7'),
('000382','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 b','CM-7b','CM-7'),
('000384','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (a)','CM-7(1)(a)','CM-7'),
('000387','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (3)','CM-7(3)','CM-7'),
('000388','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (3)','CM-7(3)','CM-7'),
('000398','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 5','CM-8a5','CM-8'),
('000408','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (1)','CM-8(1)','CM-8'),
('000409','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (1)','CM-8(1)','CM-8'),
('000410','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (1)','CM-8(1)','CM-8'),
('000411','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8(2)','CM-8'),
('000412','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8(2)','CM-8'),
('000413','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8(2)','CM-8'),
('000414','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8(2)','CM-8'),
('000415','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (a)','CM-8(3)(a)','CM-8'),
('000416','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (a)','CM-8(3)(a)','CM-8'),
('000418','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (4)','CM-8(4)','CM-8'),
('000420','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (6)','CM-8(6)','CM-8'),
('000423','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 a','CM-9a','CM-9'),
('000426','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c','CM-9'),
('000436','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 (1)','CM-9(1)','CM-9'),
('000437','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 1','CP-1c1','CP-1'),
('000438','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1 (a)','CP-1a1(a)','CP-1'),
('000439','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1 (a)','CP-1a1(a)','CP-1'),
('000440','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 1','CP-1c1','CP-1'),
('000441','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 2','CP-1a2','CP-1'),
('000443','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 1','CP-2a1','CP-2'),
('000444','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 1','CP-2a1','CP-2'),
('000445','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 1','CP-2a1','CP-2'),
('000446','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 2','CP-2a2','CP-2'),
('000447','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 2','CP-2a2','CP-2'),
('000448','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 2','CP-2a2','CP-2'),
('000449','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 3','CP-2a3','CP-2'),
('000456','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 5','CP-2a5','CP-2'),
('000457','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 7','CP-2a7','CP-2'),
('000458','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 b','CP-2b','CP-2'),
('000459','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 b','CP-2b','CP-2'),
('000460','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 c','CP-2c','CP-2'),
('000461','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 d','CP-2d','CP-2'),
('000462','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 d','CP-2d','CP-2'),
('000463','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e','CP-2'),
('000464','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e','CP-2'),
('000465','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e','CP-2'),
('000466','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 e','CP-2e','CP-2'),
('000468','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 f','CP-2f','CP-2'),
('000469','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (1)','CP-2(1)','CP-2'),
('000470','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (2)','CP-2(2)','CP-2'),
('000471','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (2)','CP-2(2)','CP-2'),
('000472','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (2)','CP-2(2)','CP-2'),
('000473','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2(3)','CP-2'),
('000474','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2(3)','CP-2'),
('000475','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2(3)','CP-2'),
('000476','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (3)','CP-2(3)','CP-2'),
('000481','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2(5)','CP-2'),
('000482','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2(5)','CP-2'),
('000483','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2(6)','CP-2'),
('000484','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2(6)','CP-2'),
('000485','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a 3','CP-3a3','CP-3'),
('000486','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a 1','CP-3a1','CP-3'),
('000487','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a 3','CP-3a3','CP-3'),
('000488','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 (1)','CP-3(1)','CP-3'),
('000489','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 (2)','CP-3(2)','CP-3'),
('000490','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 a','CP-4a','CP-4'),
('000492','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 a','CP-4a','CP-4'),
('000494','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 a','CP-4a','CP-4'),
('000496','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 b','CP-4b','CP-4'),
('000497','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 c','CP-4c','CP-4'),
('000498','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (1)','CP-4(1)','CP-4'),
('000500','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (2) (a)','CP-4(2)(a)','CP-4'),
('000502','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (3)','CP-4(3)','CP-4'),
('000504','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (4)','CP-4(4)','CP-4'),
('000505','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 a','CP-6a','CP-6'),
('000507','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (1)','CP-6(1)','CP-6'),
('000508','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (2)','CP-6(2)','CP-6'),
('000509','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (3)','CP-6(3)','CP-6'),
('000510','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a','CP-7'),
('000513','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a','CP-7'),
('000514','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a','CP-7'),
('000515','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 b','CP-7b','CP-7'),
('000516','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (1)','CP-7(1)','CP-7'),
('000517','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (2)','CP-7(2)','CP-7'),
('000518','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (3)','CP-7(3)','CP-7'),
('000519','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (4)','CP-7(4)','CP-7'),
('000520','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (4)','CP-7(4)','CP-7'),
('000521','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 c','CP-7c','CP-7'),
('000522','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
('000523','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
('000524','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
('000525','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
('000526','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (a)','CP-8(1)(a)','CP-8'),
('000527','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (a)','CP-8(1)(a)','CP-8'),
('000530','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (2)','CP-8(2)','CP-8'),
('000531','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (3)','CP-8(3)','CP-8'),
('000532','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (a)','CP-8(4)(a)','CP-8'),
('000533','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (a)','CP-8(4)(a)','CP-8'),
('000534','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (a)','CP-9(a)','CP-9'),
('000535','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (a)','CP-9(a)','CP-9'),
('000536','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (b)','CP-9(b)','CP-9'),
('000537','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (b)','CP-9(b)','CP-9'),
('000538','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (c)','CP-9(c)','CP-9'),
('000539','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (c)','CP-9(c)','CP-9'),
('000541','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (1)','CP-9(1)','CP-9'),
('000542','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (1)','CP-9(1)','CP-9'),
('000543','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (2)','CP-9(2)','CP-9'),
('000547','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (5)','CP-9(5)','CP-9'),
('000548','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (5)','CP-9(5)','CP-9'),
('000549','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (6)','CP-9(6)','CP-9'),
('000553','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (2)','CP-10(2)','CP-10'),
('000556','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (4)','CP-10(4)','CP-10'),
('000557','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (4)','CP-10(4)','CP-10'),
('000558','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (5)','SI-13(5)','SI-13'),
('000559','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (5)','SI-13(5)','SI-13'),
('000563','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1 (a)','PL-1a1(a)','PL-1'),
('000564','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1 (a)','PL-1a1(a)','PL-1'),
('000566','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 2','PL-1a2','PL-1'),
('000567','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 2','PL-1a2','PL-1'),
('000568','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 c 2','PL-1c2','PL-1'),
('000571','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 15','PL-2a15','PL-2'),
('000572','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 c','PL-2c','PL-2'),
('000573','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 c','PL-2c','PL-2'),
('000574','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 d','PL-2d','PL-2'),
('000577','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 b','PL-7b','PL-7'),
('000578','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 b','PL-7b','PL-7'),
('000592','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a','PL-4'),
('000593','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 b','PL-4b','PL-4'),
('000594','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 (1) (a)','PL-4(1)(a)','PL-4'),
('000595','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 (1) (b)','PL-4(1)(b)','PL-4'),
('000601','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 1','SA-1c1','SA-1'),
('000602','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1 (a)','SA-1a1(a)','SA-1'),
('000603','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1','SA-1a1','SA-1'),
('000604','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 1','SA-1c1','SA-1'),
('000605','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 2','SA-1a2','SA-1'),
('000606','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 2','SA-1a2','SA-1'),
('000607','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 2','SA-1c2','SA-1'),
('000610','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 b','SA-2b','SA-2'),
('000611','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 b','SA-2b','SA-2'),
('000612','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 b','SA-2b','SA-2'),
('000613','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 c','SA-2c','SA-2'),
('000614','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 c','SA-2c','SA-2'),
('000615','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('000616','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 b','SA-3b','SA-3'),
('000618','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 c','SA-3c','SA-3'),
('000623','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (1)','SA-4(1)','SA-4'),
('000631','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (6) (a)','SA-4(6)(a)','SA-4'),
('000633','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (6) (b)','SA-4(6)(b)','SA-4'),
('000634','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (7) (a)','SA-4(7)(a)','SA-4'),
('000635','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (7) (b)','SA-4(7)(b)','SA-4'),
('000642','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 c','SA-5c','SA-5'),
('000664','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('000665','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('000666','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('000667','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('000668','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('000669','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9','SA-9','SA-9'),
('000692','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 c','SA-10c','SA-10'),
('000694','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 d','SA-10d','SA-10'),
('000698','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (1)','SA-10(1)','SA-10'),
('000700','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (2)','SA-10(2)','SA-10'),
('000757','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1 (a)','IA-1a1(a)','IA-1'),
('000758','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 1','IA-1c1','IA-1'),
('000759','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 1','IA-1c1','IA-1'),
('000762','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 2','IA-1c2','IA-1'),
('000763','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 2','IA-1c2','IA-1'),
('000764','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2','IA-2','IA-2'),
('000765','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (1)','IA-2(1)','IA-2'),
('000766','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (2)','IA-2(2)','IA-2'),
('000777','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3','IA-3','IA-3'),
('000778','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3','IA-3','IA-3'),
('000783','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (b)','IA-3(3)(b)','IA-3'),
('000796','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (1)','IA-4(1)','IA-4'),
('000800','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (4)','IA-4(4)','IA-4'),
('000801','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (4)','IA-4(4)','IA-4'),
('000803','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-7','IA-7','IA-7'),
('000804','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8','IA-8','IA-8'),
('000805','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1 (a)','IR-1a1(a)','IR-1'),
('000806','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1 (a)','IR-1a1(a)','IR-1'),
('000807','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 1','IR-1c1','IR-1'),
('000808','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 1','IR-1c1','IR-1'),
('000809','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 2','IR-1a2','IR-1'),
('000810','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 2','IR-1a2','IR-1'),
('000811','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 2','IR-1c2','IR-1'),
('000812','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 2','IR-1c2','IR-1'),
('000813','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a 1','IR-2a1','IR-2'),
('000814','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a 3','IR-2a3','IR-2'),
('000815','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a 3','IR-2a3','IR-2'),
('000816','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 (1)','IR-2(1)','IR-2'),
('000817','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 (2)','IR-2(2)','IR-2'),
('000818','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
('000819','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
('000820','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3','IR-3','IR-3'),
('000821','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (1)','IR-3(1)','IR-3'),
('000822','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 a','IR-4a','IR-4'),
('000823','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 b','IR-4b','IR-4'),
('000825','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (1)','IR-4(1)','IR-4'),
('000826','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (2)','IR-4(2)','IR-4'),
('000827','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (3)','IR-4(3)','IR-4'),
('000828','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (3)','IR-4(3)','IR-4'),
('000829','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (4)','IR-4(4)','IR-4'),
('000830','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (5)','IR-4(5)','IR-4'),
('000831','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (5)','IR-4(5)','IR-4'),
('000832','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-5','IR-5','IR-5'),
('000834','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 a','IR-6a','IR-6'),
('000835','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 a','IR-6a','IR-6'),
('000836','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 b','IR-6b','IR-6'),
('000837','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (1)','IR-6(1)','IR-6'),
('000838','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (2)','IR-6(2)','IR-6'),
('000839','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-7','IR-7','IR-7'),
('000841','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-7 (2) (a)','IR-7(2)(a)','IR-7'),
('000842','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-7 (2) (b)','IR-7(2)(b)','IR-7'),
('000844','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 9','IR-8a9','IR-8'),
('000845','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 b','IR-8b','IR-8'),
('000846','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 b','IR-8b','IR-8'),
('000849','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 c','IR-8c','IR-8'),
('000850','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 d','IR-8d','IR-8'),
('000851','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 1','MA-1c1','MA-1'),
('000852','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1 (a)','MA-1a1(a)','MA-1'),
('000853','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1','MA-1a1','MA-1'),
('000854','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 1','MA-1c1','MA-1'),
('000855','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 2','MA-1a2','MA-1'),
('000856','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 2','MA-1a2','MA-1'),
('000857','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 2','MA-1c2','MA-1'),
('000860','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 c','MA-2c','MA-2'),
('000861','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 d','MA-2d','MA-2'),
('000862','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 e','MA-2e','MA-2'),
('000865','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 a','MA-3a','MA-3'),
('000866','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 a','MA-3a','MA-3'),
('000867','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 a','MA-3a','MA-3'),
('000869','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (1)','MA-3(1)','MA-3'),
('000870','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (2)','MA-3(2)','MA-3'),
('000871','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3)','MA-3(3)','MA-3'),
('000873','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 a','MA-4a','MA-4'),
('000874','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 a','MA-4a','MA-4'),
('000876','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 b','MA-4b','MA-4'),
('000877','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 c','MA-4c','MA-4'),
('000878','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 d','MA-4d','MA-4'),
('000882','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (3) (a)','MA-4(3)(a)','MA-4'),
('000883','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (3) (b)','MA-4(3)(b)','MA-4'),
('000884','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (a)','MA-4(4)(a)','MA-4'),
('000886','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (b)','MA-4(5)(b)','MA-4'),
('000887','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (a)','MA-4(5)(a)','MA-4'),
('000890','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 a','MA-5a','MA-5'),
('000891','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 a','MA-5a','MA-5'),
('000893','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (a)','MA-5(1)(a)','MA-5'),
('000894','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (a) (1)','MA-5(1)(a)(1)','MA-5'),
('000895','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (a) (2)','MA-5(1)(a)(2)','MA-5'),
('000897','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (2)','MA-5(2)','MA-5'),
('000898','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (3)','MA-5(3)','MA-5'),
('000899','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (4) (a)','MA-5(4)(a)','MA-5'),
('000900','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (4) (b)','MA-5(4)(b)','MA-5'),
('000903','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6','MA-6','MA-6'),
('000904','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1 (a)','PE-1a1(a)','PE-1'),
('000905','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1','PE-1a1','PE-1'),
('000906','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 1','PE-1c1','PE-1'),
('000907','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 1','PE-1c1','PE-1'),
('000908','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 2','PE-1a2','PE-1'),
('000909','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 2','PE-1a2','PE-1'),
('000910','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 2','PE-1c2','PE-1'),
('000911','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 2','PE-1c2','PE-1'),
('000912','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 a','PE-2a','PE-2'),
('000913','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 b','PE-2b','PE-2'),
('000914','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 c','PE-2c','PE-2'),
('000915','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 c','PE-2c','PE-2'),
('000916','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (1)','PE-2(1)','PE-2'),
('000917','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (2)','PE-2(2)','PE-2'),
('000920','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 1','PE-3a1','PE-3'),
('000923','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 e','PE-3e','PE-3'),
('000924','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 f','PE-3f','PE-3'),
('000925','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 f','PE-3f','PE-3'),
('000926','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 g','PE-3g','PE-3'),
('000927','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 g','PE-3g','PE-3'),
('000928','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (1)','PE-3(1)','PE-3'),
('000929','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (2)','PE-3(2)','PE-3'),
('000930','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (3)','PE-3(3)','PE-3'),
('000931','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (4)','PE-3(4)','PE-3'),
('000932','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (4)','PE-3(4)','PE-3'),
('000933','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (5)','PE-3(5)','PE-3'),
('000936','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-4','PE-4','PE-4'),
('000937','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-5','PE-5','PE-5'),
('000939','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b','PE-6'),
('000940','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b','PE-6'),
('000941','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 c','PE-6c','PE-6'),
('000942','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (1)','PE-6(1)','PE-6'),
('000947','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 a','PE-8a','PE-8'),
('000948','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 b','PE-8b','PE-8'),
('000949','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 b','PE-8b','PE-8'),
('000950','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 (1)','PE-8(1)','PE-8'),
('000952','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-9','PE-9','PE-9'),
('000954','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (2)','PE-9(2)','PE-9'),
('000955','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (2)','PE-9(2)','PE-9'),
('000956','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 a','PE-10a','PE-10'),
('000957','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 b','PE-10b','PE-10'),
('000958','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 b','PE-10b','PE-10'),
('000959','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 c','PE-10c','PE-10'),
('000961','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (1)','PE-11(1)','PE-11'),
('000963','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-12','PE-12','PE-12'),
('000965','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13','PE-13','PE-13'),
('000968','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2) (b)','PE-13(2)(b)','PE-13'),
('000971','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 a','PE-14a','PE-14'),
('000972','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 a','PE-14a','PE-14'),
('000973','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 b','PE-14b','PE-14'),
('000974','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 b','PE-14b','PE-14'),
('000975','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 (1)','PE-14(1)','PE-14'),
('000976','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 (2)','PE-14(2)','PE-14'),
('000977','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15','PE-15','PE-15'),
('000978','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15','PE-15','PE-15'),
('000979','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15','PE-15','PE-15'),
('000981','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-16 a','PE-16a','PE-16'),
('000983','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-16 a','PE-16a','PE-16'),
('000984','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-16 b','PE-16b','PE-16'),
('000985','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 b','PE-17b','PE-17'),
('000987','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 c','PE-17c','PE-17'),
('000988','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 d','PE-17d','PE-17'),
('000989','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-18','PE-18','PE-18'),
('000991','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-18','PE-18','PE-18'),
('000993','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-19','PE-19','PE-19'),
('000995','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1 (a)','MP-1a1(a)','MP-1'),
('000996','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1','MP-1a1','MP-1'),
('000997','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 1','MP-1c1','MP-1'),
('000998','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 1','MP-1c1','MP-1'),
('000999','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 2','MP-1a2','MP-1'),
('001000','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 2','MP-1a2','MP-1'),
('001001','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 2','MP-1c2','MP-1'),
('001002','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 2','MP-1c2','MP-1'),
('001003','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-2','MP-2','MP-2'),
('001004','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-2','MP-2','MP-2'),
('001005','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-2','MP-2','MP-2'),
('001007','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 (2)','MP-4(2)','MP-4'),
('001008','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 (2)','MP-4(2)','MP-4'),
('001010','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 a','MP-3a','MP-3'),
('001011','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 b','MP-3b','MP-3'),
('001012','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 b','MP-3b','MP-3'),
('001013','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-3 b','MP-3b','MP-3'),
('001015','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a','MP-4'),
('001016','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a','MP-4'),
('001021','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a','MP-5'),
('001022','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a','MP-5'),
('001023','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 b','MP-5b','MP-5'),
('001024','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 d','MP-5d','MP-5'),
('001025','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 c','MP-5c','MP-5'),
('001026','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 (3)','MP-5(3)','MP-5'),
('001028','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 a','MP-6a','MP-6'),
('001031','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (2)','MP-6(2)','MP-6'),
('001032','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (3)','MP-6(3)','MP-6'),
('001033','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (3)','MP-6(3)','MP-6'),
('001037','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1 (a)','RA-1a1(a)','RA-1'),
('001038','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1 (a)','RA-1a1(a)','RA-1'),
('001039','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 1','RA-1c1','RA-1'),
('001040','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 1','RA-1c1','RA-1'),
('001041','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 2','RA-1a2','RA-1'),
('001042','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 2','RA-1a2','RA-1'),
('001043','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 2','RA-1c2','RA-1'),
('001044','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 2','RA-1c2','RA-1'),
('001046','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 b','RA-2b','RA-2'),
('001047','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 c','RA-2c','RA-2'),
('001048','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 a 2','RA-3a2','RA-3'),
('001049','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 c','RA-3c','RA-3'),
('001050','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 d','RA-3d','RA-3'),
('001051','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 d','RA-3d','RA-3'),
('001052','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 f','RA-3f','RA-3'),
('001053','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 f','RA-3f','RA-3'),
('001054','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a','RA-5'),
('001055','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a','RA-5'),
('001056','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a','RA-5'),
('001057','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 b 1','RA-5b1','RA-5'),
('001058','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 c','RA-5c','RA-5'),
('001059','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 d','RA-5d','RA-5'),
('001060','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 d','RA-5d','RA-5'),
('001061','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 e','RA-5e','RA-5'),
('001063','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (2)','RA-5(2)','RA-5'),
('001064','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (2)','RA-5(2)','RA-5'),
('001066','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (4)','RA-5(4)','RA-5'),
('001067','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (5)','RA-5(5)','RA-5'),
('001068','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (6)','RA-5(6)','RA-5'),
('001071','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (8)','RA-5(8)','RA-5'),
('001075','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1','SC-1a1','SC-1'),
('001076','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 1','SC-1c1','SC-1'),
('001077','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 1','SC-1c1','SC-1'),
('001079','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a2','SC-1'),
('001080','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 2','SC-1c2','SC-1'),
('001081','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 2','SC-1c2','SC-1'),
('001082','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-2','SC-2','SC-2'),
('001083','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-2 (1)','SC-2(1)','SC-2'),
('001084','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-3','SC-3','SC-3'),
('001085','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (1)','SC-3(1)','SC-3'),
('001086','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (2)','SC-3(2)','SC-3'),
('001089','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (5)','SC-3(5)','SC-3'),
('001090','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-4','SC-4','SC-4'),
('001093','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 a','SC-5a','SC-5'),
('001094','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (1)','SC-5(1)','SC-5'),
('001095','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (2)','SC-5(2)','SC-5'),
('001097','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 a','SC-7a','SC-7'),
('001098','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 c','SC-7c','SC-7'),
('001101','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (3)','SC-7(3)','SC-7'),
('001102','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (a)','SC-7(4)(a)','SC-7'),
('001103','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (b)','SC-7(4)(b)','SC-7'),
('001105','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (d)','SC-7(4)(d)','SC-7'),
('001106','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (e)','SC-7(4)(e)','SC-7'),
('001107','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (e)','SC-7(4)(e)','SC-7'),
('001108','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (e)','SC-7(4)(e)','SC-7'),
('001109','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (5)','SC-7(5)','SC-7'),
('001112','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (8)','SC-7(8)','SC-7'),
('001113','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (8)','SC-7(8)','SC-7'),
('001114','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (8)','SC-7(8)','SC-7'),
('001116','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (10) (a)','SC-7(10)(a)','SC-7'),
('001119','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (13)','SC-7(13)','SC-7'),
('001120','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (13)','SC-7(13)','SC-7'),
('001121','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (14)','SC-7(14)','SC-7'),
('001123','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (15)','SC-7(15)','SC-7'),
('001124','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (16)','SC-7(16)','SC-7'),
('001125','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (17)','SC-7(17)','SC-7'),
('001126','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (18)','SC-7(18)','SC-7'),
('001133','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-10','SC-10','SC-10'),
('001134','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-10','SC-10','SC-10'),
('001135','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 a','SC-11a','SC-11'),
('001139','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (1)','SC-12(1)','SC-12'),
('001150','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 a','SC-15a','SC-15'),
('001151','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 a','SC-15a','SC-15'),
('001152','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 b','SC-15b','SC-15'),
('001153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (1)','SC-15(1)','SC-15'),
('001155','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (3)','SC-15(3)','SC-15'),
('001156','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (3)','SC-15(3)','SC-15'),
('001157','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
('001158','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (1)','SC-16(1)','SC-16'),
('001159','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-17 a','SC-17a','SC-17'),
('001160','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 a','SC-18a','SC-18'),
('001163','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 b','SC-18b','SC-18'),
('001164','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 b','SC-18b','SC-18'),
('001165','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 b','SC-18b','SC-18'),
('001166','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18(1)','SC-18'),
('001167','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18(2)','SC-18'),
('001168','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18(2)','SC-18'),
('001169','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (3)','SC-18(3)','SC-18'),
('001170','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18(4)','SC-18'),
('001171','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18(4)','SC-18'),
('001172','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18(4)','SC-18'),
('001178','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 a','SC-20a','SC-20'),
('001179','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 b','SC-20b','SC-20'),
('001182','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-22','SC-22','SC-22'),
('001183','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-22','SC-22','SC-22'),
('001184','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23','SC-23','SC-23'),
('001185','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (1)','SC-23(1)','SC-23'),
('001188','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (3)','SC-23(3)','SC-23'),
('001189','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (3)','SC-23(3)','SC-23'),
('001190','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
('001191','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
('001192','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
('001193','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
('001194','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-25','SC-25','SC-25'),
('001195','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-26','SC-26','SC-26'),
('001196','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-35','SC-35','SC-35'),
('001197','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-27','SC-27','SC-27'),
('001198','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-27','SC-27','SC-27'),
('001199','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28','SC-28','SC-28'),
('001201','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-29','SC-29','SC-29'),
('001203','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-29 (1)','SC-29(1)','SC-29'),
('001204','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-29 (1)','SC-29(1)','SC-29'),
('001207','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (1)','SC-31(1)','SC-31'),
('001210','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 a','SC-34a','SC-34'),
('001211','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 b','SC-34b','SC-34'),
('001212','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34','SC-34','SC-34'),
('001213','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 b','SC-34b','SC-34'),
('001214','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (1)','SC-34(1)','SC-34'),
('001215','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (1)','SC-34(1)','SC-34'),
('001216','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (2)','SC-34(2)','SC-34'),
('001217','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 1 (a)','SI-1a1(a)','SI-1'),
('001218','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 1','SI-1a1','SI-1'),
('001219','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 1','SI-1c1','SI-1'),
('001220','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 2','SI-1a2','SI-1'),
('001221','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 2','SI-1a2','SI-1'),
('001222','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 2','SI-1c2','SI-1'),
('001223','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 1','SI-1c1','SI-1'),
('001224','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 2','SI-1c2','SI-1'),
('001225','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 a','SI-2a','SI-2'),
('001226','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 a','SI-2a','SI-2'),
('001227','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 a','SI-2a','SI-2'),
('001228','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b','SI-2'),
('001229','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b','SI-2'),
('001230','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 d','SI-2d','SI-2'),
('001235','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (3) (a)','SI-2(3)(a)','SI-2'),
('001236','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (3) (b)','SI-2(3)(b)','SI-2'),
('001241','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c1','SI-3'),
('001243','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 2','SI-3c2','SI-3'),
('001244','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 2','SI-3c2','SI-3'),
('001245','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 d','SI-3d','SI-3'),
('001249','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (4)','SI-3(4)','SI-3'),
('001251','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (a)','SI-3(6)(a)','SI-3'),
('001253','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 1','SI-4a1','SI-4'),
('001255','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 c 1','SI-4c1','SI-4'),
('001256','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 c 2','SI-4c2','SI-4'),
('001257','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 e','SI-4e','SI-4'),
('001258','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 f','SI-4f','SI-4'),
('001260','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (2)','SI-4(2)','SI-4'),
('001264','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (5)','SI-4(5)','SI-4'),
('001266','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7) (a)','SI-4(7)(a)','SI-4'),
('001267','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7) (a)','SI-4(7)(a)','SI-4'),
('001268','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7) (b)','SI-4(7)(b)','SI-4'),
('001270','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (9)','SI-4(9)','SI-4'),
('001271','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (9)','SI-4(9)','SI-4'),
('001273','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (11)','SI-4(11)','SI-4'),
('001274','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (12)','SI-4(12)','SI-4'),
('001275','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (12)','SI-4(12)','SI-4'),
('001276','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (13) (a)','SI-4(13)(a)','SI-4'),
('001277','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (13) (b)','SI-4(13)(b)','SI-4'),
('001282','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (15)','SI-4(15)','SI-4'),
('001283','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (16)','SI-4(16)','SI-4'),
('001284','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (17)','SI-4(17)','SI-4'),
('001285','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 a','SI-5a','SI-5'),
('001286','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 b','SI-5b','SI-5'),
('001287','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c','SI-5'),
('001288','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c','SI-5'),
('001289','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 d','SI-5d','SI-5'),
('001290','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 (1)','SI-5(1)','SI-5'),
('001294','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 c','SI-6c','SI-6'),
('001295','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (2)','SI-6(2)','SI-6'),
('001296','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (3)','SI-6(3)','SI-6'),
('001300','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (2)','SI-7(2)','SI-7'),
('001301','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (3)','SI-7(3)','SI-7'),
('001308','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 (2)','SI-8(2)','SI-8'),
('001310','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10','SI-10','SI-10'),
('001312','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-11 a','SI-11a','SI-11'),
('001314','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-11 b','SI-11b','SI-11'),
('001315','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12','SI-12','SI-12'),
('001318','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 b','SI-13b','SI-13'),
('001319','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (1)','SI-13(1)','SI-13'),
('001320','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (1)','SI-13(1)','SI-13'),
('001321','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (16)','SI-7(16)','SI-7'),
('001322','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (16)','SI-7(16)','SI-7'),
('001323','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (3)','SI-13(3)','SI-13'),
('001326','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (a)','SI-13(4)(a)','SI-13'),
('001327','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (a)','SI-13(4)(a)','SI-13'),
('001328','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (b)','SI-13(4)(b)','SI-13'),
('001329','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (b)','SI-13(4)(b)','SI-13'),
('001330','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (a)','AC-19(4)(a)','AC-19'),
('001331','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (1)','AC-19(4)(b)(1)','AC-19'),
('001332','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (2)','AC-19(4)(b)(2)','AC-19'),
('001333','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (3)','AC-19(4)(b)(3)','AC-19'),
('001334','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (4)','AC-19(4)(b)(4)','AC-19'),
('001335','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (4)','AC-19(4)(b)(4)','AC-19'),
('001336','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 b','AT-4b','AT-4'),
('001337','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 b','AT-4b','AT-4'),
('001340','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (3)','AU-10(3)','AU-10'),
('001341','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (a)','AU-10(4)(a)','AU-10'),
('001348','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (2)','AU-9(2)','AU-9'),
('001349','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (2)','AU-9(2)','AU-9'),
('001350','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (3)','AU-9(3)','AU-9'),
('001351','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (4)','AU-9(4)','AU-9'),
('001353','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (2)','AU-12(2)','AU-12'),
('001358','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (a)','AC-2(7)(a)','AC-2'),
('001360','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (b)','AC-2(7)(b)','AC-2'),
('001361','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2(2)','AC-2'),
('001365','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2(2)','AC-2'),
('001368','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
('001371','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (14)','AC-4(14)','AC-4'),
('001372','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (14)','AC-4(14)','AC-4'),
('001373','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4(15)','AC-4'),
('001374','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4(15)','AC-4'),
('001384','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 1','AC-8c1','AC-8'),
('001385','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 2','AC-8c2','AC-8'),
('001386','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 2','AC-8c2','AC-8'),
('001387','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 2','AC-8c2','AC-8'),
('001388','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 3','AC-8c3','AC-8'),
('001389','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9(2)','AC-9'),
('001390','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9(2)','AC-9'),
('001391','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9(2)','AC-9'),
('001392','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (2)','AC-9(2)','AC-9'),
('001393','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (3)','AC-9(3)','AC-9'),
('001394','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (3)','AC-9(3)','AC-9'),
('001395','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (3)','AC-9(3)','AC-9'),
('001403','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2(4)','AC-2'),
('001404','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2(4)','AC-2'),
('001405','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2(4)','AC-2'),
('001406','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (5)','AC-2(5)','AC-2'),
('001407','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (a)','AC-2(7)(a)','AC-2'),
('001408','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (2)','AC-3(2)','AC-3'),
('001411','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (5)','AC-3(5)','AC-3'),
('001414','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
('001415','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (5)','AC-4(5)','AC-4'),
('001417','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8) (a)','AC-4(8)(a)','AC-4'),
('001419','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (2)','AC-6(2)','AC-6'),
('001420','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6(3)','AC-6'),
('001422','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (6)','AC-6(6)','AC-6'),
('001423','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 a','AC-7a','AC-7'),
('001424','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('001425','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16(2)','AC-16'),
('001428','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16(5)','AC-16'),
('001429','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16(5)','AC-16'),
('001430','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16(5)','AC-16'),
('001439','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 a','AC-18a','AC-18'),
('001441','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 b','AC-18b','AC-18'),
('001443','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (1)','AC-18(1)','AC-18'),
('001444','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (1)','AC-18(1)','AC-18'),
('001449','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (3)','AC-18(3)','AC-18'),
('001451','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (5)','AC-18(5)','AC-18'),
('001453','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (2)','AC-17(2)','AC-17'),
('001458','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (b) (4)','AC-19(4)(b)(4)','AC-19'),
('001459','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 a','AU-12a','AU-12'),
('001460','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 a','AU-13a','AU-13'),
('001461','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 a','AU-13a','AU-13'),
('001464','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 (1)','AU-14(1)','AU-14'),
('001470','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 a','AC-21a','AC-21'),
('001471','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 b','AC-21b','AC-21'),
('001472','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 b','AC-21b','AC-21'),
('001473','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 a','AC-22a','AC-22'),
('001474','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 b','AC-22b','AC-22'),
('001475','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 c','AC-22c','AC-22'),
('001476','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 d','AC-22d','AC-22'),
('001477','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 d','AC-22d','AC-22'),
('001478','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-22 d','AC-22d','AC-22'),
('001481','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3(1)','AT-3'),
('001482','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3(1)','AT-3'),
('001483','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3(1)','AT-3'),
('001484','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 c','AU-2c','AU-2'),
('001485','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 c','AU-2c','AU-2'),
('001487','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 f','AU-3f','AU-3'),
('001488','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (1)','AU-3(1)','AU-3'),
('001490','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 b','AU-5b','AU-5'),
('001491','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (6)','AU-6(6)','AU-6'),
('001493','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 a','AU-9a','AU-9'),
('001494','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 a','AU-9a','AU-9'),
('001495','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 a','AU-9a','AU-9'),
('001496','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (3)','AU-9(3)','AU-9'),
('001497','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 b 1','CM-2b1','CM-2'),
('001498','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (c)','CM-3(1)(c)','CM-3'),
('001499','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (6)','CM-5(6)','CM-5'),
('001504','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1 (a)','PS-1a1(a)','PS-1'),
('001505','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1','PS-1a1','PS-1'),
('001506','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 1','PS-1c1','PS-1'),
('001507','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 1','PS-1c1','PS-1'),
('001508','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 2','PS-1c2','PS-1'),
('001509','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 2','PS-1a2','PS-1'),
('001510','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 2','PS-1a2','PS-1'),
('001511','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 2','PS-1c2','PS-1'),
('001512','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 a','PS-2a','PS-2'),
('001513','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 b','PS-2b','PS-2'),
('001514','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 c','PS-2c','PS-2'),
('001515','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-2 c','PS-2c','PS-2'),
('001516','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 a','PS-3a','PS-3'),
('001517','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 b','PS-3b','PS-3'),
('001518','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 b','PS-3b','PS-3'),
('001519','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 b','PS-3b','PS-3'),
('001520','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (1)','PS-3(1)','PS-3'),
('001521','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (2)','PS-3(2)','PS-3'),
('001522','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 a','PS-4a','PS-4'),
('001523','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 c','PS-4c','PS-4'),
('001524','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 d','PS-4d','PS-4'),
('001525','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 e','PS-4e','PS-4'),
('001526','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 e','PS-4e','PS-4'),
('001527','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 a','PS-5a','PS-5'),
('001528','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 b','PS-5b','PS-5'),
('001529','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 b','PS-5b','PS-5'),
('001530','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 b','PS-5b','PS-5'),
('001532','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 b','PS-6b','PS-6'),
('001533','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 b','PS-6b','PS-6'),
('001536','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (2) (a)','PS-6(2)(a)','PS-6'),
('001537','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (2) (b)','PS-6(2)(b)','PS-6'),
('001538','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (2) (c)','PS-6(2)(c)','PS-6'),
('001539','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 a','PS-7a','PS-7'),
('001540','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 c','PS-7c','PS-7'),
('001541','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 e','PS-7e','PS-7'),
('001544','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 c','IA-5c','IA-5'),
('001545','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 1','AC-1c1','AC-1'),
('001546','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 2','AC-1c2','AC-1'),
('001547','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 j','AC-2j','AC-2'),
('001548','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
('001549','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4','AC-4','AC-4'),
('001553','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (10)','AC-4(10)','AC-4'),
('001554','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (11)','AC-4(11)','AC-4'),
('001558','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1) (a)','AC-6(1)(a)','AC-6'),
('001564','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 c 1','AT-1c1','AT-1'),
('001565','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 c 2','AT-1c2','AT-1'),
('001566','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3(2)','AT-3'),
('001567','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3(2)','AT-3'),
('001568','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3(2)','AT-3'),
('001569','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 1','AU-1c1','AU-1'),
('001570','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 2','AU-1c2','AU-1'),
('001571','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 a','AU-2a','AU-2'),
('001572','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 a','AU-5a','AU-5'),
('001573','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (3)','AU-5(3)','AU-5'),
('001577','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (1)','AU-12(1)','AU-12'),
('001578','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 2','CA-1c2','CA-1'),
('001582','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2(2)','CA-2'),
('001584','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 2','CM-1c2','CM-1'),
('001585','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 b 2','CM-2b2','CM-2'),
('001586','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 g','CM-3g','CM-3'),
('001592','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (2)','CM-7(2)','CM-7'),
('001596','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 2','CP-1c2','CP-1'),
('001597','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 2','CP-1a2','CP-1'),
('001598','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 2','CP-1c2','CP-1'),
('001599','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2(5)','CP-2'),
('001600','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (5)','CP-2(5)','CP-2'),
('001601','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2(6)','CP-2'),
('001602','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (6)','CP-2(6)','CP-2'),
('001604','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 (3)','CP-6(3)','CP-6'),
('001606','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (2)','CP-7(2)','CP-7'),
('001609','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (6)','CP-9(6)','CP-9'),
('001610','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 f','IA-5f','IA-5'),
('001621','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (8)','IA-5(8)','IA-5'),
('001625','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 c','IR-4c','IR-4'),
('001628','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 2','MA-1c2','MA-1'),
('001631','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (3) (b)','MA-4(3)(b)','MA-4'),
('001632','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (b) (1)','MA-4(4)(b)(1)','MA-4'),
('001635','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 d','PE-2d','PE-2'),
('001636','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 c 1','PL-1c1','PL-1'),
('001637','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 c 1','PL-1c1','PL-1'),
('001638','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 c 2','PL-1c2','PL-1'),
('001640','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-8','PM-8','PM-8'),
('001641','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a','RA-5'),
('001642','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 c','RA-3c','RA-3'),
('001643','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 a','RA-5a','RA-5'),
('001645','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (5)','RA-5(5)','RA-5'),
('001646','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 2','SA-1c2','SA-1'),
('001661','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 b','SC-11b','SC-11'),
('001662','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18(1)','SC-18'),
('001663','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 b','SC-20b','SC-20'),
('001664','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (3)','SC-23(3)','SC-23'),
('001665','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-24','SC-24','SC-24'),
('001669','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (a)','SI-3(6)(a)','SI-3'),
('001670','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (7) (b)','SI-4(7)(b)','SI-4'),
('001671','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (11)','SI-4(11)','SI-4'),
('001673','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (14)','SI-4(14)','SI-4'),
('001675','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (3)','SI-6(3)','SI-6'),
('001678','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12','SI-12','SI-12'),
('001680','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 2','PM-1a2','PM-1'),
('001682','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (2)','AC-2(2)','AC-2'),
('001687','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18(2)','SC-18'),
('001688','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (2)','SC-18(2)','SC-18'),
('001695','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (3)','SC-18(3)','SC-18'),
('001726','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a','CM-10'),
('001727','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a','CM-10'),
('001728','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a','CM-10'),
('001729','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 a','CM-10a','CM-10'),
('001730','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b','CM-10'),
('001731','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b','CM-10'),
('001732','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 c','CM-10c','CM-10'),
('001733','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 c','CM-10c','CM-10'),
('001734','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 (1)','CM-10(1)','CM-10'),
('001735','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 (1)','CM-10(1)','CM-10'),
('001736','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (3)','CM-2(3)','CM-2'),
('001737','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (a)','CM-2(7)(a)','CM-2'),
('001738','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (a)','CM-2(7)(a)','CM-2'),
('001739','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (a)','CM-2(7)(a)','CM-2'),
('001740','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 b','CM-3b','CM-3'),
('001741','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 c','CM-3c','CM-3'),
('001742','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (b)','CM-3(1)(b)','CM-3'),
('001743','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (5)','CM-3(5)','CM-3'),
('001744','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (5)','CM-3(5)','CM-3'),
('001745','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (6)','CM-3(6)','CM-3'),
('001746','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (6)','CM-3(6)','CM-3'),
('001751','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5(4)','CM-5'),
('001752','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (4)','CM-5(4)','CM-5'),
('001753','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (a)','CM-5(5)(a)','CM-5'),
('001754','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (a)','CM-5(5)(a)','CM-5'),
('001755','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c','CM-6'),
('001756','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 c','CM-6c','CM-6'),
('001757','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (2)','CM-6(2)','CM-6'),
('001758','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (2)','CM-6(2)','CM-6'),
('001759','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (2)','CM-6(2)','CM-6'),
('001760','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (a)','CM-7(1)(a)','CM-7'),
('001761','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (b)','CM-7(1)(b)','CM-7'),
('001762','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (1) (b)','CM-7(1)(b)','CM-7'),
('001763','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (2)','CM-7(2)','CM-7'),
('001764','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (2)','CM-7(2)','CM-7'),
('001765','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (a)','CM-7(4)(a)','CM-7'),
('001766','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (a)','CM-7(4)(a)','CM-7'),
('001767','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (b)','CM-7(4)(b)','CM-7'),
('001768','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (c)','CM-7(4)(c)','CM-7'),
('001770','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (4) (c)','CM-7(4)(c)','CM-7'),
('001772','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (a)','CM-7(5)(a)','CM-7'),
('001773','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (a)','CM-7(5)(a)','CM-7'),
('001774','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (b)','CM-7(5)(b)','CM-7'),
('001775','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (c)','CM-7(5)(c)','CM-7'),
('001777','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (5) (c)','CM-7(5)(c)','CM-7'),
('001779','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 b','CM-8b','CM-8'),
('001780','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 b','CM-8b','CM-8'),
('001783','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (b)','CM-8(3)(b)','CM-8'),
('001784','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (b)','CM-8(3)(b)','CM-8'),
('001785','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (7)','CM-8(7)','CM-8'),
('001786','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (8)','CM-8(8)','CM-8'),
('001788','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (9) (a)','CM-8(9)(a)','CM-8'),
('001789','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (9) (b)','CM-8(9)(b)','CM-8'),
('001792','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b','CM-9'),
('001795','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b','CM-9'),
('001798','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c','CM-9'),
('001799','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 e','CM-9e','CM-9'),
('001801','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 e','CM-9e','CM-9'),
('001802','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b','CM-10'),
('001803','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-10 b','CM-10b','CM-10'),
('001804','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 a','CM-11a','CM-11'),
('001805','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 a','CM-11a','CM-11'),
('001806','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 b','CM-11b','CM-11'),
('001807','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 b','CM-11b','CM-11'),
('001808','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 c','CM-11c','CM-11'),
('001809','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 c','CM-11c','CM-11'),
('001813','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (1) (a)','CM-5(1)(a)','CM-5'),
('001815','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (b)','CM-2(7)(b)','CM-2'),
('001816','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (7) (b)','CM-2(7)(b)','CM-2'),
('001817','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (1)','CM-4(1)','CM-4'),
('001818','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (1)','CM-4(1)','CM-4'),
('001819','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 d','CM-3d','CM-3'),
('001821','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1 (a)','CM-1a1(a)','CM-1'),
('001822','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1 (a)','CM-1a1(a)','CM-1'),
('001824','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a2','CM-1'),
('001825','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 2','CM-1a2','CM-1'),
('001832','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1 (a)','AU-1a1(a)','AU-1'),
('001834','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a2','AU-1'),
('001848','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-4','AU-4','AU-4'),
('001849','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-4','AU-4','AU-4'),
('001850','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-4 (1)','AU-4(1)','AU-4'),
('001851','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-4 (1)','AU-4(1)','AU-4'),
('001852','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5(1)','AU-5'),
('001853','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5(1)','AU-5'),
('001854','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5(1)','AU-5'),
('001855','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (1)','AU-5(1)','AU-5'),
('001856','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5(2)','AU-5'),
('001857','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5(2)','AU-5'),
('001858','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (2)','AU-5(2)','AU-5'),
('001859','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (3)','AU-5(3)','AU-5'),
('001860','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (4)','AU-5(4)','AU-5'),
('001861','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (4)','AU-5(4)','AU-5'),
('001862','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a','AU-6'),
('001863','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 b','AU-6b','AU-6'),
('001864','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (1)','AU-6(1)','AU-6'),
('001865','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (1)','AU-6(1)','AU-6'),
('001866','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (5)','AU-6(5)','AU-6'),
('001867','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (5)','AU-6(5)','AU-6'),
('001868','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (7)','AU-6(7)','AU-6'),
('001869','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (7)','AU-6(7)','AU-6'),
('001870','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (8)','AU-6(8)','AU-6'),
('001871','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (9)','AU-6(9)','AU-6'),
('001875','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('001876','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('001877','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('001878','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('001879','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('001880','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('001881','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 b','AU-7b','AU-7'),
('001882','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 b','AU-7b','AU-7'),
('001883','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (1)','AU-7(1)','AU-7'),
('001888','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 b','AU-8b','AU-8'),
('001889','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 b','AU-8b','AU-8'),
('001890','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-8 b','AU-8b','AU-8'),
('001894','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (4)','AU-9(4)','AU-9'),
('001895','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (5)','AU-9(5)','AU-9'),
('001896','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (5)','AU-9(5)','AU-9'),
('001897','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (6)','AU-9(6)','AU-9'),
('001898','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (6)','AU-9(6)','AU-9'),
('001899','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10','AU-10','AU-10'),
('001900','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (1) (a)','AU-10(1)(a)','AU-10'),
('001901','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (1) (a)','AU-10(1)(a)','AU-10'),
('001902','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (1) (b)','AU-10(1)(b)','AU-10'),
('001903','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (a)','AU-10(2)(a)','AU-10'),
('001904','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (a)','AU-10(2)(a)','AU-10'),
('001905','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (b)','AU-10(2)(b)','AU-10'),
('001906','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (2) (b)','AU-10(2)(b)','AU-10'),
('001907','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (a)','AU-10(4)(a)','AU-10'),
('001908','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (b)','AU-10(4)(b)','AU-10'),
('001909','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-10 (4) (b)','AU-10(4)(b)','AU-10'),
('001910','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 b','AU-12b','AU-12'),
('001911','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12(3)','AU-12'),
('001912','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12(3)','AU-12'),
('001913','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12(3)','AU-12'),
('001914','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12(3)','AU-12'),
('001915','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 a','AU-13a','AU-13'),
('001917','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (2)','AU-13(2)','AU-13'),
('001918','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (2)','AU-13(2)','AU-13'),
('001919','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 a','AU-14a','AU-14'),
('001920','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 (3)','AU-14(3)','AU-14'),
('001923','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16','AU-16','AU-16'),
('001924','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16','AU-16','AU-16'),
('001925','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16','AU-16','AU-16'),
('001926','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (1)','AU-16(1)','AU-16'),
('001927','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (2)','AU-16(2)','AU-16'),
('001928','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (2)','AU-16(2)','AU-16'),
('001929','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (2)','AU-16(2)','AU-16'),
('001930','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1','AU-1a1','AU-1'),
('001931','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 2','AU-1a2','AU-1'),
('001941','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (8)','IA-2(8)','IA-2'),
('001943','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2(10)','IA-2'),
('001944','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2(10)','IA-2'),
('001945','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2(10)','IA-2'),
('001946','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (10)','IA-2(10)','IA-2'),
('001953','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (12)','IA-2(12)','IA-2'),
('001954','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (12)','IA-2(12)','IA-2'),
('001955','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (13)','IA-2(13)','IA-2'),
('001956','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (13)','IA-2(13)','IA-2'),
('001957','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (13)','IA-2(13)','IA-2'),
('001958','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3','IA-3','IA-3'),
('001959','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (1)','IA-3(1)','IA-3'),
('001960','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3(3)(a)','IA-3'),
('001961','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3(3)(a)','IA-3'),
('001962','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3(3)(a)','IA-3'),
('001963','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (3) (a)','IA-3(3)(a)','IA-3'),
('001965','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3(4)','IA-3'),
('001966','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3(4)','IA-3'),
('001967','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (1)','IA-3(1)','IA-3'),
('001968','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3(4)','IA-3'),
('001969','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-3 (4)','IA-3(4)','IA-3'),
('001970','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 a','IA-4a','IA-4'),
('001971','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 a','IA-4a','IA-4'),
('001972','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 b','IA-4b','IA-4'),
('001973','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 c','IA-4c','IA-4'),
('001974','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 d','IA-4d','IA-4'),
('001975','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 d','IA-4d','IA-4'),
('001976','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (5)','IA-4(5)','IA-4'),
('001977','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (6)','IA-4(6)','IA-4'),
('001978','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (6)','IA-4(6)','IA-4'),
('001980','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 a','IA-5a','IA-5'),
('001981','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d','IA-5'),
('001984','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d','IA-5'),
('001985','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d','IA-5'),
('001988','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d','IA-5'),
('001990','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 i','IA-5i','IA-5'),
('001998','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (5)','IA-5(5)','IA-5'),
('002001','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (10)','IA-5(10)','IA-5'),
('002004','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (12)','IA-5(12)','IA-5'),
('002005','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (12)','IA-5(12)','IA-5'),
('002006','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (13)','IA-5(13)','IA-5'),
('002007','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (13)','IA-5(13)','IA-5'),
('002008','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (14)','IA-5(14)','IA-5'),
('002009','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (1)','IA-8(1)','IA-8'),
('002010','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (1)','IA-8(1)','IA-8'),
('002015','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (5)','IA-8(5)','IA-8'),
('002016','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (5)','IA-8(5)','IA-8'),
('002018','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
('002021','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
('002022','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-9','IA-9','IA-9'),
('002033','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-10','IA-10','IA-10'),
('002034','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-10','IA-10','IA-10'),
('002035','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-10','IA-10','IA-10'),
('002036','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-11','IA-11','IA-11'),
('002038','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-11','IA-11','IA-11'),
('002042','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 g','IA-5g','IA-5'),
('002044','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-11 (1)','AU-11(1)','AU-11'),
('002045','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-11 (1)','AU-11(1)','AU-11'),
('002047','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12(3)','AU-12'),
('002048','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1 (a)','AT-1a1(a)','AT-1'),
('002049','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 2','AT-1a2','AT-1'),
('002050','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (1)','AT-3(1)','AT-3'),
('002051','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (2)','AT-3(2)','AT-3'),
('002052','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (3)','AT-3(3)','AT-3'),
('002055','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (2)','AT-2(2)','AT-2'),
('002056','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 e','CM-3e','CM-3'),
('002057','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (f)','CM-3(1)(f)','CM-3'),
('002058','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (f)','CM-3(1)(f)','CM-3'),
('002059','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6(1)','CM-6'),
('002061','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1 (a)','CA-1a1(a)','CA-1'),
('002062','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a2','CA-1'),
('002065','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (2)','CA-2(2)','CA-2'),
('002066','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2(3)','CA-2'),
('002067','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2(3)','CA-2'),
('002068','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2(3)','CA-2'),
('002069','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 (3)','CA-2(3)','CA-2'),
('002070','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 b 3','CA-2b3','CA-2'),
('002071','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 f','CA-2f','CA-2'),
('002083','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 c','CA-3c','CA-3'),
('002084','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 c','CA-3c','CA-3'),
('002086','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (3)','CA-7(3)','CA-7'),
('002087','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 a','CA-7a','CA-7'),
('002088','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 b','CA-7b','CA-7'),
('002090','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 d','CA-7d','CA-7'),
('002091','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 e','CA-7e','CA-7'),
('002092','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 f','CA-7f','CA-7'),
('002093','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8','CA-8','CA-8'),
('002094','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8','CA-8','CA-8'),
('002095','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8','CA-8','CA-8'),
('002096','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (1)','CA-8(1)','CA-8'),
('002097','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (2)','CA-8(2)','CA-8'),
('002099','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (2)','CA-8(2)','CA-8'),
('002100','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (1)','CA-9(1)','CA-9'),
('002101','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (a)','CA-9(a)','CA-9'),
('002102','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (a)','CA-9(a)','CA-9'),
('002103','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
('002104','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
('002105','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
('002107','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1 (a)','AC-1a1(a)','AC-1'),
('002108','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 2','AC-1a2','AC-1'),
('002112','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 b','AC-2b','AC-2'),
('002115','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d 1','AC-2d1','AC-2'),
('002116','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d 2','AC-2d2','AC-2'),
('002117','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d 2','AC-2d2','AC-2'),
('002118','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d 3','AC-2d3','AC-2'),
('002119','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d 3','AC-2d3','AC-2'),
('002120','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 e','AC-2e','AC-2'),
('002121','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('002122','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 g','AC-2g','AC-2'),
('002123','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h 1','AC-2h1','AC-2'),
('002124','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h 2','AC-2h2','AC-2'),
('002125','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h 3','AC-2h3','AC-2'),
('002126','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 1','AC-2i1','AC-2'),
('002127','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 2','AC-2i2','AC-2'),
('002128','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 3','AC-2i3','AC-2'),
('002129','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 k','AC-2k','AC-2'),
('002130','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (4)','AC-2(4)','AC-2'),
('002133','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (5)','AC-2(5)','AC-2'),
('002134','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (6)','AC-2(6)','AC-2'),
('002135','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (6)','AC-2(6)','AC-2'),
('002137','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (d)','AC-2(7)(d)','AC-2'),
('002138','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('002139','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('002140','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (9)','AC-2(9)','AC-2'),
('002141','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (9)','AC-2(9)','AC-2'),
('002143','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (11)','AC-2(11)','AC-2'),
('002144','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (11)','AC-2(11)','AC-2'),
('002145','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (11)','AC-2(11)','AC-2'),
('002146','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (a)','AC-2(12)(a)','AC-2'),
('002147','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (a)','AC-2(12)(a)','AC-2'),
('002148','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (b)','AC-2(12)(b)','AC-2'),
('002149','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (12) (b)','AC-2(12)(b)','AC-2'),
('002150','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (13)','AC-2(13)','AC-2'),
('002151','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (13)','AC-2(13)','AC-2'),
('002152','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (2)','AC-3(2)','AC-3'),
('002153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3)','AC-3(3)','AC-3'),
('002153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (15) (a)','AC-3(15)(a)','AC-3'),
('002154','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (a)','AC-3(3)(a)','AC-3'),
('002155','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (1)','AC-3(3)(b)(1)','AC-3'),
('002156','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (2)','AC-3(3)(b)(2)','AC-3'),
('002157','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (3)','AC-3(3)(b)(3)','AC-3'),
('002158','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (4)','AC-3(3)(b)(4)','AC-3'),
('002159','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (4)','AC-3(3)(b)(4)','AC-3'),
('002160','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (b) (5)','AC-3(3)(b)(5)','AC-3'),
('002161','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (c)','AC-3(3)(c)','AC-3'),
('002162','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (c)','AC-3(3)(c)','AC-3'),
('002163','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4)','AC-3(4)','AC-3'),
('002164','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4)','AC-3(4)','AC-3'),
('002165','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4)','AC-3(4)','AC-3'),
('002166','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3(7)','AC-3'),
('002169','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3(7)','AC-3'),
('002170','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3(7)','AC-3'),
('002173','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3(7)','AC-3'),
('002174','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (7)','AC-3(7)','AC-3'),
('002177','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (8)','AC-3(8)','AC-3'),
('002178','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (8)','AC-3(8)','AC-3'),
('002179','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (8)','AC-3(8)','AC-3'),
('002180','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (a)','AC-3(9)(a)','AC-3'),
('002181','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (a)','AC-3(9)(a)','AC-3'),
('002182','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (a)','AC-3(9)(a)','AC-3'),
('002183','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (b)','AC-3(9)(b)','AC-3'),
('002184','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (9) (b)','AC-3(9)(b)','AC-3'),
('002185','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (10)','AC-3(10)','AC-3'),
('002186','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (10)','AC-3(10)','AC-3'),
('002187','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4(1)','AC-4'),
('002188','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4(1)','AC-4'),
('002189','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4(1)','AC-4'),
('002190','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4(1)','AC-4'),
('002191','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (2)','AC-4(2)','AC-4'),
('002192','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (3)','AC-4(3)','AC-4'),
('002193','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (4)','AC-4(4)','AC-4'),
('002194','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (6)','AC-4(6)','AC-4'),
('002195','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8) (a)','AC-4(8)(a)','AC-4'),
('002196','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (9)','AC-4(9)','AC-4'),
('002197','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (9)','AC-4(9)','AC-4'),
('002198','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (9)','AC-4(9)','AC-4'),
('002199','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (10)','AC-4(10)','AC-4'),
('002200','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (12)','AC-4(12)','AC-4'),
('002201','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (12)','AC-4(12)','AC-4'),
('002202','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (13)','AC-4(13)','AC-4'),
('002203','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4(15)','AC-4'),
('002204','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (15)','AC-4(15)','AC-4'),
('002205','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (17)','AC-4(17)','AC-4'),
('002207','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (17)','AC-4(17)','AC-4'),
('002211','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (19)','AC-4(19)','AC-4'),
('002212','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (20)','AC-4(20)','AC-4'),
('002213','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (20)','AC-4(20)','AC-4'),
('002214','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (20)','AC-4(20)','AC-4'),
('002215','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (21)','AC-4(21)','AC-4'),
('002216','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (21)','AC-4(21)','AC-4'),
('002217','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (21)','AC-4(21)','AC-4'),
('002218','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (22)','AC-4(22)','AC-4'),
('002219','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 a','AC-5a','AC-5'),
('002220','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 b','AC-5b','AC-5'),
('002221','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1) (b)','AC-6(1)(b)','AC-6'),
('002222','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1) (a)','AC-6(1)(a)','AC-6'),
('002223','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1) (b)','AC-6(1)(b)','AC-6'),
('002224','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (3)','AC-6(3)','AC-6'),
('002225','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (4)','AC-6(4)','AC-6'),
('002226','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (5)','AC-6(5)','AC-6'),
('002227','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (5)','AC-6(5)','AC-6'),
('002228','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (a)','AC-6(7)(a)','AC-6'),
('002229','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (a)','AC-6(7)(a)','AC-6'),
('002230','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (a)','AC-6(7)(a)','AC-6'),
('002231','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (7) (b)','AC-6(7)(b)','AC-6'),
('002232','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (8)','AC-6(8)','AC-6'),
('002233','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (8)','AC-6(8)','AC-6'),
('002234','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (9)','AC-6(9)','AC-6'),
('002235','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (10)','AC-6(10)','AC-6'),
('002236','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 b','AC-7b','AC-7'),
('002237','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 b','AC-7b','AC-7'),
('002238','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 b','AC-7b','AC-7'),
('002239','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7(2)','AC-7'),
('002240','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7(2)','AC-7'),
('002241','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7(2)','AC-7'),
('002242','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (2)','AC-7(2)','AC-7'),
('002243','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 1','AC-8a1','AC-8'),
('002244','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 2','AC-8a2','AC-8'),
('002245','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 3','AC-8a3','AC-8'),
('002246','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a 4','AC-8a4','AC-8'),
('002247','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 a','AC-8a','AC-8'),
('002248','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-8 c 1','AC-8c1','AC-8'),
('002249','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (4)','AC-9(4)','AC-9'),
('002250','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-9 (4)','AC-9(4)','AC-9'),
('002252','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-10','AC-10','AC-10'),
('002256','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002257','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002258','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002259','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002260','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002261','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002262','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002263','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002264','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('002265','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 b','AC-16b','AC-16'),
('002266','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 b','AC-16b','AC-16'),
('002267','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c','AC-16'),
('002268','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c','AC-16'),
('002269','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c','AC-16'),
('002270','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 d','AC-16d','AC-16'),
('002271','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 d','AC-16d','AC-16'),
('002272','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('002273','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('002274','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('002275','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('002277','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16(2)','AC-16'),
('002278','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002279','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002280','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002281','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002282','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002283','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002284','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('002286','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('002287','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('002288','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('002289','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('002290','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('002291','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002292','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002293','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002294','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002295','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002296','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002297','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002298','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('002299','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (7)','AC-16(7)','AC-16'),
('002300','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16(8)','AC-16'),
('002301','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16(8)','AC-16'),
('002302','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16(8)','AC-16'),
('002303','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (9)','AC-16(9)','AC-16'),
('002304','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (9)','AC-16(9)','AC-16'),
('002306','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('002307','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('002308','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('002309','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('002310','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a','AC-17'),
('002311','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a','AC-17'),
('002312','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 a','AC-17a','AC-17'),
('002314','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (1)','AC-17(1)','AC-17'),
('002316','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17(4)(a)','AC-17'),
('002317','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17(4)(a)','AC-17'),
('002318','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (a)','AC-17(4)(a)','AC-17'),
('002319','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (b)','AC-17(4)(b)','AC-17'),
('002320','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (4) (b)','AC-17(4)(b)','AC-17'),
('002321','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (9)','AC-17(9)','AC-17'),
('002322','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (9)','AC-17(9)','AC-17'),
('002323','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 a','AC-18a','AC-18'),
('002324','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-18 (4)','AC-18(4)','AC-18'),
('002325','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a','AC-19'),
('002326','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 a','AC-19a','AC-19'),
('002327','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (c)','AC-19(4)(c)','AC-19'),
('002328','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (4) (c)','AC-19(4)(c)','AC-19'),
('002329','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (5)','AC-19(5)','AC-19'),
('002330','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (5)','AC-19(5)','AC-19'),
('002331','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-19 (5)','AC-19(5)','AC-19'),
('002332','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a 2','AC-20a2','AC-20'),
('002337','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (b)','AC-20(1)(b)','AC-20'),
('002338','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (3)','AC-20(3)','AC-20'),
('002339','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (4)','AC-20(4)','AC-20'),
('002340','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (4)','AC-20(4)','AC-20'),
('002341','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 (2)','AC-21(2)','AC-21'),
('002342','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-21 (2)','AC-21(2)','AC-21'),
('002343','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
('002344','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
('002345','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
('002346','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
('002347','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-23','AC-23','AC-23'),
('002348','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24','AC-24','AC-24'),
('002349','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24','AC-24','AC-24'),
('002350','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24(1)','AC-24'),
('002351','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24(1)','AC-24'),
('002352','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24(1)','AC-24'),
('002353','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (1)','AC-24(1)','AC-24'),
('002354','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (2)','AC-24(2)','AC-24'),
('002355','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (2)','AC-24(2)','AC-24'),
('002356','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
('002357','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
('002358','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
('002359','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-25','AC-25','AC-25'),
('002360','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12','AC-12','AC-12'),
('002361','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12','AC-12','AC-12'),
('002362','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (1)','AC-12(1)','AC-12'),
('002363','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (1)','AC-12(1)','AC-12'),
('002364','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (2)','AC-12(2)','AC-12'),
('002368','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1 (a)','RA-1a1(a)','RA-1'),
('002369','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 2','RA-1a2','RA-1'),
('002370','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 e','RA-3e','RA-3'),
('002371','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 e','RA-3e','RA-3'),
('002372','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (10)','RA-5(10)','RA-5'),
('002373','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (3)','RA-5(3)','RA-5'),
('002374','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (4)','RA-5(4)','RA-5'),
('002375','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (4)','RA-5(4)','RA-5'),
('002376','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 e','RA-5e','RA-5'),
('002378','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1','SC-1a1','SC-1'),
('002380','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a2','SC-1'),
('002381','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (3)','SC-3(3)','SC-3'),
('002382','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-3 (4)','SC-3(4)','SC-3'),
('002383','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-4 (2)','SC-4(2)','SC-4'),
('002384','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-4 (2)','SC-4(2)','SC-4'),
('002385','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 a','SC-5a','SC-5'),
('002387','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (1)','SC-5(1)','SC-5'),
('002388','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (a)','SC-5(3)(a)','SC-5'),
('002389','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (a)','SC-5(3)(a)','SC-5'),
('002390','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (b)','SC-5(3)(b)','SC-5'),
('002391','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 (3) (b)','SC-5(3)(b)','SC-5'),
('002392','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-6','SC-6','SC-6'),
('002393','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-6','SC-6','SC-6'),
('002394','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-6','SC-6','SC-6'),
('002395','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 b','SC-7b','SC-7'),
('002396','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (c)','SC-7(4)(c)','SC-7'),
('002397','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (7)','SC-7(7)','SC-7'),
('002398','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (9) (a)','SC-7(9)(a)','SC-7'),
('002399','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (9) (a)','SC-7(9)(a)','SC-7'),
('002400','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (9) (b)','SC-7(9)(b)','SC-7'),
('002401','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (11)','SC-7(11)','SC-7'),
('002402','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (11)','SC-7(11)','SC-7'),
('002403','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (11)','SC-7(11)','SC-7'),
('002404','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (12)','SC-7(12)','SC-7'),
('002405','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (12)','SC-7(12)','SC-7'),
('002406','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (12)','SC-7(12)','SC-7'),
('002407','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (14)','SC-7(14)','SC-7'),
('002408','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (19)','SC-7(19)','SC-7'),
('002409','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (19)','SC-7(19)','SC-7'),
('002410','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (20)','SC-7(20)','SC-7'),
('002411','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (20)','SC-7(20)','SC-7'),
('002413','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7(21)','SC-7'),
('002414','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7(21)','SC-7'),
('002415','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (21)','SC-7(21)','SC-7'),
('002416','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (22)','SC-7(22)','SC-7'),
('002417','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (23)','SC-7(23)','SC-7'),
('002418','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8','SC-8','SC-8'),
('002420','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (2)','SC-8(2)','SC-8'),
('002421','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (1)','SC-8(1)','SC-8'),
('002422','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (2)','SC-8(2)','SC-8'),
('002423','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (3)','SC-8(3)','SC-8'),
('002424','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (4)','SC-8(4)','SC-8'),
('002425','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (4)','SC-8(4)','SC-8'),
('002426','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 (1) (a)','SC-11(1)(a)','SC-11'),
('002427','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (3)','SC-8(3)','SC-8'),
('002428','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002429','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002430','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002431','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002432','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002433','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002434','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002435','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002436','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002437','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002438','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002439','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002440','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002441','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002442','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12','SC-12','SC-12'),
('002443','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (2)','SC-12(2)','SC-12'),
('002444','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (2)','SC-12(2)','SC-12'),
('002445','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (2)','SC-12(2)','SC-12'),
('002446','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12(3)','SC-12'),
('002447','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12(3)','SC-12'),
('002448','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12(3)','SC-12'),
('002449','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-13','SC-13','SC-13'),
('002450','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-13 b','SC-13b','SC-13'),
('002451','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (3)','SC-15(3)','SC-15'),
('002452','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (4)','SC-15(4)','SC-15'),
('002453','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-15 (4)','SC-15(4)','SC-15'),
('002454','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
('002455','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
('002456','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-17 a','SC-17a','SC-17'),
('002457','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18(1)','SC-18'),
('002458','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (1)','SC-18(1)','SC-18'),
('002459','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (3)','SC-18(3)','SC-18'),
('002460','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (4)','SC-18(4)','SC-18'),
('002461','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-18 (5)','SC-18(5)','SC-18'),
('002462','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 a','SC-20a','SC-20'),
('002463','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 (2)','SC-20(2)','SC-20'),
('002464','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-20 (2)','SC-20(2)','SC-20'),
('002465','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
('002466','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
('002467','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
('002468','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-21','SC-21','SC-21'),
('002469','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (5)','SC-23(5)','SC-23'),
('002470','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-23 (5)','SC-23(5)','SC-23'),
('002471','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-25','SC-25','SC-25'),
('002472','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28','SC-28','SC-28'),
('002473','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28(1)','SC-28'),
('002474','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28(1)','SC-28'),
('002475','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28(1)','SC-28'),
('002476','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (1)','SC-28(1)','SC-28'),
('002477','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (2)','SC-28(2)','SC-28'),
('002478','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (2)','SC-28(2)','SC-28'),
('002479','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (2)','SC-28(2)','SC-28'),
('002480','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-29','SC-29','SC-29'),
('002481','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-29 (1)','SC-29(1)','SC-29'),
('002482','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
('002483','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
('002484','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
('002485','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30','SC-30','SC-30'),
('002486','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (2)','SC-30(2)','SC-30'),
('002487','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (2)','SC-30(2)','SC-30'),
('002488','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (2)','SC-30(2)','SC-30'),
('002489','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30(3)','SC-30'),
('002490','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30(3)','SC-30'),
('002492','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (3)','SC-30(3)','SC-30'),
('002493','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (4)','SC-30(4)','SC-30'),
('002494','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (4)','SC-30(4)','SC-30'),
('002495','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (5)','SC-30(5)','SC-30'),
('002496','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (5)','SC-30(5)','SC-30'),
('002497','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-30 (5)','SC-30(5)','SC-30'),
('002498','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 a','SC-31a','SC-31'),
('002499','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 b','SC-31b','SC-31'),
('002500','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (2)','SC-31(2)','SC-31'),
('002501','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (2)','SC-31(2)','SC-31'),
('002502','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (3)','SC-31(3)','SC-31'),
('002503','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-31 (3)','SC-31(3)','SC-31'),
('002504','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-32','SC-32','SC-32'),
('002505','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-32','SC-32','SC-32'),
('002506','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-32','SC-32','SC-32'),
('002507','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-34 (2)','SC-34(2)','SC-34'),
('002508','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-51 a','SC-51a','SC-51'),
('002509','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-51 a','SC-51a','SC-51'),
('002510','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-51 b','SC-51b','SC-51'),
('002511','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-51 b','SC-51b','SC-51'),
('002512','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-51 b','SC-51b','SC-51'),
('002513','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
('002514','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
('002515','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
('002516','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36','SC-36','SC-36'),
('002517','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1) (a)','SC-36(1)(a)','SC-36'),
('002518','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1) (a)','SC-36(1)(a)','SC-36'),
('002519','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1) (a)','SC-36(1)(a)','SC-36'),
('002520','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1) (a)','SC-36(1)(a)','SC-36'),
('002521','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
('002522','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
('002523','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37(1)','SC-37'),
('002523','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
('002524','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37','SC-37','SC-37'),
('002525','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37(1)','SC-37'),
('002526','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37(1)','SC-37'),
('002527','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-37 (1)','SC-37(1)','SC-37'),
('002528','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-38','SC-38','SC-38'),
('002529','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-38','SC-38','SC-38'),
('002530','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-39','SC-39','SC-39'),
('002531','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-39 (1)','SC-39(1)','SC-39'),
('002532','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-39 (2)','SC-39(2)','SC-39'),
('002533','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-39 (2)','SC-39(2)','SC-39'),
('002534','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40','SC-40','SC-40'),
('002535','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40','SC-40','SC-40'),
('002536','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40','SC-40','SC-40'),
('002537','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (1)','SC-40(1)','SC-40'),
('002538','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (1)','SC-40(1)','SC-40'),
('002539','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (2)','SC-40(2)','SC-40'),
('002540','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (2)','SC-40(2)','SC-40'),
('002541','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (3)','SC-40(3)','SC-40'),
('002542','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (4)','SC-40(4)','SC-40'),
('002543','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-40 (4)','SC-40(4)','SC-40'),
('002544','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-41','SC-41','SC-41'),
('002545','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-41','SC-41','SC-41'),
('002546','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-41','SC-41','SC-41'),
('002547','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 a','SC-42a','SC-42'),
('002548','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 a','SC-42a','SC-42'),
('002549','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 b','SC-42b','SC-42'),
('002550','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 b','SC-42b','SC-42'),
('002551','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (1)','SC-42(1)','SC-42'),
('002552','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (1)','SC-42(1)','SC-42'),
('002553','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (2)','SC-42(2)','SC-42'),
('002554','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (2)','SC-42(2)','SC-42'),
('002555','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (2)','SC-42(2)','SC-42'),
('002556','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 a','SC-42a','SC-42'),
('002557','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 a','SC-42a','SC-42'),
('002559','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 a','SC-43a','SC-43'),
('002560','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 a','SC-43a','SC-43'),
('002561','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 b','SC-43b','SC-43'),
('002562','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 b','SC-43b','SC-43'),
('002563','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-43 b','SC-43b','SC-43'),
('002564','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-44','SC-44','SC-44'),
('002565','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-44','SC-44','SC-44'),
('002566','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1','MP-1a1','MP-1'),
('002567','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6(1)','MP-6'),
('002568','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6(1)','MP-6'),
('002569','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6(1)','MP-6'),
('002570','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6(1)','MP-6'),
('002571','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6(1)','MP-6'),
('002572','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (1)','MP-6(1)','MP-6'),
('002573','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (7)','MP-6(7)','MP-6'),
('002574','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (7)','MP-6(7)','MP-6'),
('002575','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (8)','MP-6(8)','MP-6'),
('002576','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (8)','MP-6(8)','MP-6'),
('002577','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (8)','MP-6(8)','MP-6'),
('002578','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 a','MP-6a','MP-6'),
('002579','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 a','MP-6a','MP-6'),
('002580','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 b','MP-6b','MP-6'),
('002581','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (a)','MP-7(a)','MP-7'),
('002582','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (a)','MP-7(a)','MP-7'),
('002583','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (a)','MP-7(a)','MP-7'),
('002584','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (a)','MP-7(a)','MP-7'),
('002585','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (b)','MP-7(b)','MP-7'),
('002586','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-7 (2)','MP-7(2)','MP-7'),
('002587','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (1)','MP-8(1)','MP-8'),
('002591','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8(2)','MP-8'),
('002593','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (3)','MP-8(3)','MP-8'),
('002594','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (4)','MP-8(4)','MP-8'),
('002600','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 d','MP-8d','MP-8'),
('002601','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a','SI-1a','SI-1'),
('002602','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b','SI-2'),
('002603','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 b','SI-2b','SI-2'),
('002604','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c','SI-2'),
('002605','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c','SI-2'),
('002606','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c','SI-2'),
('002607','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 c','SI-2c','SI-2'),
('002608','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (3) (b)','SI-2(3)(b)','SI-2'),
('002609','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2(5)','SI-2'),
('002610','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2(5)','SI-2'),
('002611','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2(5)','SI-2'),
('002612','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2(5)','SI-2'),
('002613','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2(5)','SI-2'),
('002614','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (5)','SI-2(5)','SI-2'),
('002615','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2(6)','SI-2'),
('002616','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2(6)','SI-2'),
('002617','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2(6)','SI-2'),
('002618','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (6)','SI-2(6)','SI-2'),
('002623','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c1','SI-3'),
('002624','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 1','SI-3c1','SI-3'),
('002625','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (b)','SI-3(6)(b)','SI-3'),
('002626','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (6) (b)','SI-3(6)(b)','SI-3'),
('002628','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8) (a)','SI-3(8)(a)','SI-3'),
('002629','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8) (a)','SI-3(8)(a)','SI-3'),
('002630','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8) (a)','SI-3(8)(a)','SI-3'),
('002631','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (8) (b)','SI-3(8)(b)','SI-3'),
('002634','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3(10)(a)','SI-3'),
('002635','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3(10)(a)','SI-3'),
('002636','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3(10)(a)','SI-3'),
('002638','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (a)','SI-3(10)(a)','SI-3'),
('002639','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (b)','SI-3(10)(b)','SI-3'),
('002640','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 (10) (b)','SI-3(10)(b)','SI-3'),
('002641','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 1','SI-4a1','SI-4'),
('002642','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 2','SI-4a2','SI-4'),
('002643','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 2','SI-4a2','SI-4'),
('002644','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 a 2','SI-4a2','SI-4'),
('002645','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 b','SI-4b','SI-4'),
('002646','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 b','SI-4b','SI-4'),
('002650','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g','SI-4'),
('002651','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g','SI-4'),
('002652','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g','SI-4'),
('002654','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 g','SI-4g','SI-4'),
('002655','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (1)','SI-4(1)','SI-4'),
('002656','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (1)','SI-4(1)','SI-4'),
('002657','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (3)','SI-4(3)','SI-4'),
('002658','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (3)','SI-4(3)','SI-4'),
('002659','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (b)','SI-4(4)(b)','SI-4'),
('002660','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (b)','SI-4(4)(b)','SI-4'),
('002661','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (b)','SI-4(4)(b)','SI-4'),
('002662','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (b)','SI-4(4)(b)','SI-4'),
('002663','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (5)','SI-4(5)','SI-4'),
('002664','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (5)','SI-4(5)','SI-4'),
('002665','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4(10)','SI-4'),
('002666','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4(10)','SI-4'),
('002667','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4(10)','SI-4'),
('002668','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (11)','SI-4(11)','SI-4'),
('002669','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (13) (c)','SI-4(13)(c)','SI-4'),
('002670','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (18)','SI-4(18)','SI-4'),
('002671','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (18)','SI-4(18)','SI-4'),
('002672','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (18)','SI-4(18)','SI-4'),
('002673','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (19)','SI-4(19)','SI-4'),
('002674','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (19)','SI-4(19)','SI-4'),
('002675','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (19)','SI-4(19)','SI-4'),
('002676','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (20)','SI-4(20)','SI-4'),
('002677','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (20)','SI-4(20)','SI-4'),
('002678','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (21)','SI-4(21)','SI-4'),
('002679','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (21)','SI-4(21)','SI-4'),
('002680','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (21)','SI-4(21)','SI-4'),
('002681','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22) (a)','SI-4(22)(a)','SI-4'),
('002682','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22) (a)','SI-4(22)(a)','SI-4'),
('002683','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22) (a)','SI-4(22)(a)','SI-4'),
('002684','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (22) (b)','SI-4(22)(b)','SI-4'),
('002685','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (23)','SI-4(23)','SI-4'),
('002686','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (23)','SI-4(23)','SI-4'),
('002687','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (23)','SI-4(23)','SI-4'),
('002688','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4(24)','SI-4'),
('002689','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4(24)','SI-4'),
('002690','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (24)','SI-4(24)','SI-4'),
('002692','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 a','SI-5a','SI-5'),
('002693','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c','SI-5'),
('002694','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 c','SI-5c','SI-5'),
('002695','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 a','SI-6a','SI-6'),
('002696','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 a','SI-6a','SI-6'),
('002697','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b','SI-6'),
('002698','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b','SI-6'),
('002699','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b','SI-6'),
('002700','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 c','SI-6c','SI-6'),
('002701','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 d','SI-6d','SI-6'),
('002702','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 d','SI-6d','SI-6'),
('002703','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7','SI-7','SI-7'),
('002704','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 a','SI-7a','SI-7'),
('002705','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002706','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002707','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002708','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002709','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002710','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002711','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002712','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (1)','SI-7(1)','SI-7'),
('002713','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (2)','SI-7(2)','SI-7'),
('002714','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (5)','SI-7(5)','SI-7'),
('002715','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (5)','SI-7(5)','SI-7'),
('002716','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (6)','SI-7(6)','SI-7'),
('002717','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (6)','SI-7(6)','SI-7'),
('002718','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (6)','SI-7(6)','SI-7'),
('002719','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (7)','SI-7(7)','SI-7'),
('002720','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (7)','SI-7(7)','SI-7'),
('002721','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7(8)','SI-7'),
('002722','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7(8)','SI-7'),
('002723','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7(8)','SI-7'),
('002724','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (8)','SI-7(8)','SI-7'),
('002725','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (9)','SI-7(9)','SI-7'),
('002726','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (9)','SI-7(9)','SI-7'),
('002727','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (10)','SI-7(10)','SI-7'),
('002728','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (10)','SI-7(10)','SI-7'),
('002729','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (10)','SI-7(10)','SI-7'),
('002732','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (12)','SI-7(12)','SI-7'),
('002733','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (12)','SI-7(12)','SI-7'),
('002739','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (15)','SI-7(15)','SI-7'),
('002740','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (15)','SI-7(15)','SI-7'),
('002741','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 a','SI-8a','SI-8'),
('002742','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 a','SI-8a','SI-8'),
('002743','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 (3)','SI-8(3)','SI-8'),
('002744','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10','SI-10','SI-10'),
('002745','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (a)','SI-10(1)(a)','SI-10'),
('002746','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (a)','SI-10(1)(a)','SI-10'),
('002747','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (b)','SI-10(1)(b)','SI-10'),
('002748','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (b)','SI-10(1)(b)','SI-10'),
('002749','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (1) (c)','SI-10(1)(c)','SI-10'),
('002750','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10(2)','SI-10'),
('002751','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10(2)','SI-10'),
('002752','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10(2)','SI-10'),
('002753','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (2)','SI-10(2)','SI-10'),
('002754','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (3)','SI-10(3)','SI-10'),
('002755','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (4)','SI-10(4)','SI-10'),
('002756','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (5)','SI-10(5)','SI-10'),
('002757','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (5)','SI-10(5)','SI-10'),
('002758','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (5)','SI-10(5)','SI-10'),
('002759','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-11 b','SI-11b','SI-11'),
('002760','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 a','SI-13a','SI-13'),
('002761','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 a','SI-13a','SI-13'),
('002762','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 b','SI-13b','SI-13'),
('002763','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 b','SI-13b','SI-13'),
('002764','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
('002765','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
('002766','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
('002767','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14','SI-14','SI-14'),
('002768','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (1)','SI-14(1)','SI-14'),
('002769','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (1)','SI-14(1)','SI-14'),
('002770','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-15','SI-15','SI-15'),
('002771','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-15','SI-15','SI-15'),
('002773','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-17','SI-17','SI-17'),
('002774','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-17','SI-17','SI-17'),
('002775','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-17','SI-17','SI-17'),
('002776','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1 (a)','IR-1a1(a)','IR-1'),
('002777','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 2','IR-1a2','IR-1'),
('002778','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a 1','IR-2a1','IR-2'),
('002779','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 a 2','IR-2a2','IR-2'),
('002780','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (2)','IR-3(2)','IR-3'),
('002781','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (2)','IR-4(2)','IR-4'),
('002782','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (6)','IR-4(6)','IR-4'),
('002785','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (8)','IR-4(8)','IR-4'),
('002786','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (8)','IR-4(8)','IR-4'),
('002787','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (8)','IR-4(8)','IR-4'),
('002788','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (9)','IR-4(9)','IR-4'),
('002789','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (9)','IR-4(9)','IR-4'),
('002790','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (10)','IR-4(10)','IR-4'),
('002791','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 b','IR-6b','IR-6'),
('002792','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (2)','IR-6(2)','IR-6'),
('002793','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (3)','IR-6(3)','IR-6'),
('002794','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a','IR-8a','IR-8'),
('002795','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 1','IR-8a1','IR-8'),
('002796','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 2','IR-8a2','IR-8'),
('002797','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 3','IR-8a3','IR-8'),
('002798','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 4','IR-8a4','IR-8'),
('002799','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 5','IR-8a5','IR-8'),
('002800','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 6','IR-8a6','IR-8'),
('002801','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 7','IR-8a7','IR-8'),
('002802','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 9','IR-8a9','IR-8'),
('002803','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 d','IR-8d','IR-8'),
('002804','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 e','IR-8e','IR-8'),
('002805','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 b','IR-9b','IR-9'),
('002806','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 c','IR-9c','IR-9'),
('002807','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 c','IR-9c','IR-9'),
('002808','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 d','IR-9d','IR-9'),
('002809','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 e','IR-9e','IR-9'),
('002810','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 f','IR-9f','IR-9'),
('002811','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 g','IR-9g','IR-9'),
('002812','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 g','IR-9g','IR-9'),
('002816','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (2)','IR-9(2)','IR-9'),
('002817','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (2)','IR-9(2)','IR-9'),
('002818','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (3)','IR-9(3)','IR-9'),
('002819','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (3)','IR-9(3)','IR-9'),
('002820','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (4)','IR-9(4)','IR-9'),
('002821','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 (4)','IR-9(4)','IR-9'),
('002823','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-16','SI-16','SI-16'),
('002824','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-16','SI-16','SI-16'),
('002825','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1 (a)','CP-1a1(a)','CP-1'),
('002826','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 2','CP-1a2','CP-1'),
('002827','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (7)','CP-2(7)','CP-2'),
('002828','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (8)','CP-2(8)','CP-2'),
('002829','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 (8)','CP-2(8)','CP-2'),
('002830','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 7','CP-2a7','CP-2'),
('002831','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 f','CP-2f','CP-2'),
('002832','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 h','CP-2h','CP-2'),
('002833','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a 1','CP-3a1','CP-3'),
('002834','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 a 2','CP-3a2','CP-3'),
('002835','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (2) (b)','CP-4(2)(b)','CP-4'),
('002836','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 b','CP-6b','CP-6'),
('002837','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (6)','CP-7(6)','CP-7'),
('002838','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 (6)','CP-7(6)','CP-7'),
('002839','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-7 a','CP-7a','CP-7'),
('002840','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
('002841','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8','CP-8','CP-8'),
('002842','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (b)','CP-8(4)(b)','CP-8'),
('002843','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c)','CP-8(4)(c)','CP-8'),
('002844','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c)','CP-8(4)(c)','CP-8'),
('002845','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c)','CP-8(4)(c)','CP-8'),
('002846','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (4) (c)','CP-8(4)(c)','CP-8'),
('002847','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (5)','CP-8(5)','CP-8'),
('002848','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (5)','CP-8(5)','CP-8'),
('002849','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (3)','CP-9(3)','CP-9'),
('002850','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (3)','CP-9(3)','CP-9'),
('002851','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (7)','CP-9(7)','CP-9'),
('002852','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (7)','CP-9(7)','CP-9'),
('002853','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-11','CP-11','CP-11'),
('002854','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-11','CP-11','CP-11'),
('002855','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-12','CP-12','CP-12'),
('002856','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-12','CP-12','CP-12'),
('002857','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-12','CP-12','CP-12'),
('002858','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-13','CP-13','CP-13'),
('002859','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-13','CP-13','CP-13'),
('002860','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-13','CP-13','CP-13'),
('002861','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1 (a)','MA-1a1(a)','MA-1'),
('002862','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 2','MA-1a2','MA-1'),
('002864','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (b)','MA-2(2)(b)','MA-2'),
('002865','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (b)','MA-2(2)(b)','MA-2'),
('002866','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('002868','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('002869','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('002870','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('002872','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('002873','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('002874','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 c','MA-2c','MA-2'),
('002875','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 f','MA-2f','MA-2'),
('002876','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 f','MA-2f','MA-2'),
('002882','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (3) (d)','MA-3(3)(d)','MA-3'),
('002883','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (4)','MA-3(4)','MA-3'),
('002884','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (1) (a)','MA-4(1)(a)','MA-4'),
('002885','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (1) (a)','MA-4(1)(a)','MA-4'),
('002886','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (1) (b)','MA-4(1)(b)','MA-4'),
('002887','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (a)','MA-4(4)(a)','MA-4'),
('002888','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (a)','MA-4(5)(a)','MA-4'),
('002889','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (5) (b)','MA-4(5)(b)','MA-4'),
('002890','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (6)','MA-4(6)','MA-4'),
('002891','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (7)','MA-4(7)','MA-4'),
('002893','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (5)','MA-5(5)','MA-5'),
('002894','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 b','MA-5b','MA-5'),
('002895','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 c','MA-5c','MA-5'),
('002896','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6','MA-6','MA-6'),
('002897','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6','MA-6','MA-6'),
('002898','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (1)','MA-6(1)','MA-6'),
('002899','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (1)','MA-6(1)','MA-6'),
('002900','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (1)','MA-6(1)','MA-6'),
('002901','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (2)','MA-6(2)','MA-6'),
('002902','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (2)','MA-6(2)','MA-6'),
('002903','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (2)','MA-6(2)','MA-6'),
('002904','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (3)','MA-6(3)','MA-6'),
('002906','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (5)','RA-5(5)','RA-5'),
('002907','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (4)','AU-5(4)','AU-5'),
('002908','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1','PE-1a1','PE-1'),
('002909','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 2','PE-1a2','PE-1'),
('002910','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 a','PE-2a','PE-2'),
('002911','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 a','PE-2a','PE-2'),
('002912','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (2)','PE-2(2)','PE-2'),
('002913','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (3)','PE-2(3)','PE-2'),
('002914','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-2 (3)','PE-2(3)','PE-2'),
('002915','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a','PE-3a','PE-3'),
('002916','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 2','PE-3a2','PE-3'),
('002917','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 b','PE-3b','PE-3'),
('002918','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 b','PE-3b','PE-3'),
('002919','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 c','PE-3c','PE-3'),
('002920','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 c','PE-3c','PE-3'),
('002921','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d','PE-3'),
('002922','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d','PE-3'),
('002923','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d','PE-3'),
('002924','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 d','PE-3d','PE-3'),
('002925','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 f','PE-3f','PE-3'),
('002926','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (1)','PE-3(1)','PE-3'),
('002927','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (2)','PE-3(2)','PE-3'),
('002928','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (5)','PE-3(5)','PE-3'),
('002929','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (5)','PE-3(5)','PE-3'),
('002930','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-4','PE-4','PE-4'),
('002931','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-4','PE-4','PE-4'),
('002939','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 a','PE-6a','PE-6'),
('002940','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b','PE-6'),
('002941','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 b','PE-6b','PE-6'),
('002942','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6(2)','PE-6'),
('002943','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6(2)','PE-6'),
('002944','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6(2)','PE-6'),
('002945','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6(2)','PE-6'),
('002946','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3) (a)','PE-6(3)(a)','PE-6'),
('002947','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3) (a)','PE-6(3)(a)','PE-6'),
('002948','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3) (c)','PE-6(3)(c)','PE-6'),
('002949','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3) (c)','PE-6(3)(c)','PE-6'),
('002950','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (4)','PE-6(4)','PE-6'),
('002951','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (4)','PE-6(4)','PE-6'),
('002952','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 a','PE-8a','PE-8'),
('002953','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (1)','PE-9(1)','PE-9'),
('002954','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-9 (1)','PE-9(1)','PE-9'),
('002955','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-11','PE-11','PE-11'),
('002956','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (2) (a)','PE-11(2)(a)','PE-11'),
('002957','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (2) (b)','PE-11(2)(b)','PE-11'),
('002958','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-11 (2) (c)','PE-11(2)(c)','PE-11'),
('002959','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-12 (1)','PE-12(1)','PE-12'),
('002960','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-12 (1)','PE-12(1)','PE-12'),
('002961','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13(1)','PE-13'),
('002962','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13(1)','PE-13'),
('002963','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13(1)','PE-13'),
('002964','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (1)','PE-13(1)','PE-13'),
('002965','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2) (a)','PE-13(2)(a)','PE-13'),
('002966','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2) (a)','PE-13(2)(a)','PE-13'),
('002967','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (2) (a)','PE-13(2)(a)','PE-13'),
('002968','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13(4)','PE-13'),
('002969','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13(4)','PE-13'),
('002970','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13(4)','PE-13'),
('002971','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-13 (4)','PE-13(4)','PE-13'),
('002973','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15 (1)','PE-15(1)','PE-15'),
('002974','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-16 a','PE-16a','PE-16'),
('002975','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 b','PE-17b','PE-17'),
('002976','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-18','PE-18','PE-18'),
('002979','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-20','PE-20','PE-20'),
('002980','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-20','PE-20','PE-20'),
('002981','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-20','PE-20','PE-20'),
('002982','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-20','PE-20','PE-20'),
('002984','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 3','PM-1a3','PM-1'),
('002985','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 1','PM-1a1','PM-1'),
('002986','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 2','PM-1a2','PM-1'),
('002987','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 3','PM-1a3','PM-1'),
('002988','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 a 4','PM-1a4','PM-1'),
('002989','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 c','PM-1c','PM-1'),
('002990','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 c','PM-1c','PM-1'),
('002991','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a1','PM-4'),
('002993','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 b','PM-4b','PM-4'),
('002994','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 c','PM-9c','PM-9'),
('002995','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 c','PM-9c','PM-9'),
('002996','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-12','PM-12','PM-12'),
('002997','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-13','PM-13','PM-13'),
('002998','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('002999','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('003000','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('003001','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('003002','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('003003','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('003004','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a2','PM-14'),
('003005','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a2','PM-14'),
('003006','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a2','PM-14'),
('003007','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 b','PM-14b','PM-14'),
('003008','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 b','PM-14b','PM-14'),
('003009','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 b','PM-14b','PM-14'),
('003010','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 a','PM-15a','PM-15'),
('003011','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 b','PM-15b','PM-15'),
('003012','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 c','PM-15c','PM-15'),
('003013','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-16','PM-16','PM-16'),
('003014','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3)','AC-3(3)','AC-3'),
('003015','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (3) (c)','AC-3(3)(c)','AC-3'),
('003017','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1','PS-1a1','PS-1'),
('003018','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 2','PS-1a2','PS-1'),
('003019','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (3) (a)','PS-3(3)(a)','PS-3'),
('003020','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (3) (b)','PS-3(3)(b)','PS-3'),
('003021','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (3) (b)','PS-3(3)(b)','PS-3'),
('003022','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 a','PS-4a','PS-4'),
('003023','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 b','PS-4b','PS-4'),
('003024','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 c','PS-4c','PS-4'),
('003027','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (1) (a)','PS-4(1)(a)','PS-4'),
('003028','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (1) (b)','PS-4(1)(b)','PS-4'),
('003029','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (2)','PS-4(2)','PS-4'),
('003030','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (2)','PS-4(2)','PS-4'),
('003031','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 c','PS-5c','PS-5'),
('003032','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 d','PS-5d','PS-5'),
('003033','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 d','PS-5d','PS-5'),
('003034','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-5 d','PS-5d','PS-5'),
('003035','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 a','PS-6a','PS-6'),
('003038','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (3) (a)','PS-6(3)(a)','PS-6'),
('003039','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 (3) (b)','PS-6(3)(b)','PS-6'),
('003041','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 d','PS-7d','PS-7'),
('003042','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 d','PS-7d','PS-7'),
('003043','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 d','PS-7d','PS-7'),
('003044','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 b','PS-8b','PS-8'),
('003045','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 b','PS-8b','PS-8'),
('003046','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 b','PS-8b','PS-8'),
('003047','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1 (a)','PL-1a1(a)','PL-1'),
('003048','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 2','PL-1a2','PL-1'),
('003049','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a','PL-2a','PL-2'),
('003050','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 1','PL-2a1','PL-2'),
('003051','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 2','PL-2a2','PL-2'),
('003052','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 3','PL-2a3','PL-2'),
('003053','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 6','PL-2a6','PL-2'),
('003054','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 9','PL-2a9','PL-2'),
('003055','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 10','PL-2a10','PL-2'),
('003056','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 11','PL-2a11','PL-2'),
('003057','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 12','PL-2a12','PL-2'),
('003059','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b','PL-2'),
('003060','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b','PL-2'),
('003061','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b','PL-2'),
('003062','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 b','PL-2b','PL-2'),
('003063','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 e','PL-2e','PL-2'),
('003064','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 e','PL-2e','PL-2'),
('003068','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 c','PL-4c','PL-4'),
('003069','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 c','PL-4c','PL-4'),
('003070','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 d','PL-4d','PL-4'),
('003071','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 a','PL-7a','PL-7'),
('003072','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a','PL-8a','PL-8'),
('003073','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 1','PL-8a1','PL-8'),
('003074','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 3','PL-8a3','PL-8'),
('003075','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 4','PL-8a4','PL-8'),
('003076','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 b','PL-8b','PL-8'),
('003077','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 b','PL-8b','PL-8'),
('003078','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c','PL-8'),
('003079','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c','PL-8'),
('003080','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c','PL-8'),
('003081','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('003082','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('003083','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('003084','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('003085','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('003086','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('003087','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (b)','PL-8(1)(b)','PL-8'),
('003088','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (2)','PL-8(2)','PL-8'),
('003089','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1 (a)','SA-1a1(a)','SA-1'),
('003090','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 2','SA-1a2','SA-1'),
('003091','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 a','SA-2a','SA-2'),
('003092','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('003093','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 d','SA-3d','SA-3'),
('003094','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 a','SA-4a','SA-4'),
('003095','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 b','SA-4b','SA-4'),
('003096','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 c','SA-4c','SA-4'),
('003097','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 e','SA-4e','SA-4'),
('003098','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 f','SA-4f','SA-4'),
('003099','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 g','SA-4g','SA-4'),
('003100','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 i','SA-4i','SA-4'),
('003101','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4(2)','SA-4'),
('003102','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4(2)','SA-4'),
('003103','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4(2)','SA-4'),
('003104','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4(2)','SA-4'),
('003105','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4(2)','SA-4'),
('003106','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (2)','SA-4(2)','SA-4'),
('003109','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (5) (a)','SA-4(5)(a)','SA-4'),
('003110','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (5) (a)','SA-4(5)(a)','SA-4'),
('003111','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (5) (b)','SA-4(5)(b)','SA-4'),
('003112','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (8)','SA-4(8)','SA-4'),
('003114','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (9)','SA-4(9)','SA-4'),
('003116','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (10)','SA-4(10)','SA-4'),
('003117','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-9','PL-9','PL-9'),
('003118','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-9','PL-9','PL-9'),
('003119','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
('003120','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
('003121','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
('003122','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-6','RA-6','RA-6'),
('003123','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (6)','MA-4(6)','MA-4'),
('003124','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 1','SA-5a1','SA-5'),
('003125','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 1','SA-5a1','SA-5'),
('003126','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 1','SA-5a1','SA-5'),
('003127','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 2','SA-5a2','SA-5'),
('003128','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 3','SA-5a3','SA-5'),
('003129','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 1','SA-5b1','SA-5'),
('003130','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 2','SA-5b2','SA-5'),
('003131','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 3','SA-5b3','SA-5'),
('003132','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 c','SA-5c','SA-5'),
('003133','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 c','SA-5c','SA-5'),
('003135','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 d','SA-5d','SA-5'),
('003136','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 d','SA-5d','SA-5'),
('003138','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 c','SA-9c','SA-9'),
('003139','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 c','SA-9c','SA-9'),
('003140','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (1) (a)','SA-9(1)(a)','SA-9'),
('003141','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (1) (b)','SA-9(1)(b)','SA-9'),
('003142','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (1) (b)','SA-9(1)(b)','SA-9'),
('003143','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (2)','SA-9(2)','SA-9'),
('003144','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (2)','SA-9(2)','SA-9'),
('003145','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('003146','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('003147','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('003148','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('003149','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (4)','SA-9(4)','SA-9'),
('003150','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (4)','SA-9(4)','SA-9'),
('003151','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (4)','SA-9(4)','SA-9'),
('003152','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (5)','SA-9(5)','SA-9'),
('003153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (5)','SA-9(5)','SA-9'),
('003154','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (5)','SA-9(5)','SA-9'),
('003155','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 a','SA-10a','SA-10'),
('003156','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b','SA-10'),
('003157','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b','SA-10'),
('003158','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b','SA-10'),
('003159','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 b','SA-10b','SA-10'),
('003160','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 d','SA-10d','SA-10'),
('003161','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e','SA-10'),
('003162','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e','SA-10'),
('003163','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e','SA-10'),
('003164','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 e','SA-10e','SA-10'),
('003165','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (3)','SA-10(3)','SA-10'),
('003166','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (4)','SA-10(4)','SA-10'),
('003167','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (4)','SA-10(4)','SA-10'),
('003168','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (4)','SA-10(4)','SA-10'),
('003169','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (5)','SA-10(5)','SA-10'),
('003170','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (6)','SA-10(6)','SA-10'),
('003171','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 a','SA-11a','SA-11'),
('003172','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 a','SA-11a','SA-11'),
('003173','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 b','SA-11b','SA-11'),
('003174','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 b','SA-11b','SA-11'),
('003175','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 c','SA-11c','SA-11'),
('003176','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 c','SA-11c','SA-11'),
('003177','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 d','SA-11d','SA-11'),
('003178','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 e','SA-11e','SA-11'),
('003179','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (1)','SA-11(1)','SA-11'),
('003180','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (1)','SA-11(1)','SA-11'),
('003181','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2)','SA-11(2)','SA-11'),
('003182','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2)','SA-11(2)','SA-11'),
('003183','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11(3)(a)','SA-11'),
('003184','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11(3)(a)','SA-11'),
('003185','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11(3)(a)','SA-11'),
('003186','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (b)','SA-11(3)(b)','SA-11'),
('003187','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (4)','SA-11(4)','SA-11'),
('003188','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (4)','SA-11(4)','SA-11'),
('003189','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (4)','SA-11(4)','SA-11'),
('003191','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5) (a)','SA-11(5)(a)','SA-11'),
('003192','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5) (b)','SA-11(5)(b)','SA-11'),
('003193','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (6)','SA-11(6)','SA-11'),
('003194','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (7)','SA-11(7)','SA-11'),
('003195','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (7)','SA-11(7)','SA-11'),
('003196','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (8)','SA-11(8)','SA-11'),
('003197','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (8)','SA-11(8)','SA-11'),
('003233','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a','SA-15a','SA-15'),
('003234','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 1','SA-15a1','SA-15'),
('003235','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 2','SA-15a2','SA-15'),
('003236','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 2','SA-15a2','SA-15'),
('003237','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 3','SA-15a3','SA-15'),
('003238','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 4','SA-15a4','SA-15'),
('003239','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 4','SA-15a4','SA-15'),
('003240','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 4','SA-15a4','SA-15'),
('003241','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('003242','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('003243','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('003244','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('003245','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('003246','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('003247','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (a)','SA-15(1)(a)','SA-15'),
('003248','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (b)','SA-15(1)(b)','SA-15'),
('003249','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (b)','SA-15(1)(b)','SA-15'),
('003250','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (1) (b)','SA-15(1)(b)','SA-15'),
('003251','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (2)','SA-15(2)','SA-15'),
('003252','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (2)','SA-15(2)','SA-15'),
('003254','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3) (b)','SA-15(3)(b)','SA-15'),
('003255','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3) (a)','SA-15(3)(a)','SA-15'),
('003272','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (5)','SA-15(5)','SA-15'),
('003273','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (5)','SA-15(5)','SA-15'),
('003274','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (6)','SA-15(6)','SA-15'),
('003275','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (a)','SA-15(7)(a)','SA-15'),
('003276','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (a)','SA-15(7)(a)','SA-15'),
('003277','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (b)','SA-15(7)(b)','SA-15'),
('003278','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (c)','SA-15(7)(c)','SA-15'),
('003279','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (d)','SA-15(7)(d)','SA-15'),
('003280','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (d)','SA-15(7)(d)','SA-15'),
('003281','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (8)','SA-15(8)','SA-15'),
('003282','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (8)','SA-15(8)','SA-15'),
('003289','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (10)','SA-15(10)','SA-15'),
('003290','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (11)','SA-15(11)','SA-15'),
('003291','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-16','SA-16','SA-16'),
('003292','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-16','SA-16','SA-16'),
('003293','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17','SA-17','SA-17'),
('003294','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 a','SA-17a','SA-17'),
('003295','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 b','SA-17b','SA-17'),
('003296','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 b','SA-17b','SA-17'),
('003297','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 c','SA-17c','SA-17'),
('003298','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (a)','SA-17(1)(a)','SA-17'),
('003299','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (a)','SA-17(1)(a)','SA-17'),
('003300','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (b)','SA-17(1)(b)','SA-17'),
('003301','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17(2)(a)','SA-17'),
('003303','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17(2)(a)','SA-17'),
('003304','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (a)','SA-17(2)(a)','SA-17'),
('003305','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (b)','SA-17(2)(b)','SA-17'),
('003306','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (b)','SA-17(2)(b)','SA-17'),
('003307','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (2) (b)','SA-17(2)(b)','SA-17'),
('003308','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (a)','SA-17(3)(a)','SA-17'),
('003309','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (a)','SA-17(3)(a)','SA-17'),
('003310','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (a)','SA-17(3)(a)','SA-17'),
('003311','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (b)','SA-17(3)(b)','SA-17'),
('003312','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (c)','SA-17(3)(c)','SA-17'),
('003313','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (c)','SA-17(3)(c)','SA-17'),
('003314','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (c)','SA-17(3)(c)','SA-17'),
('003315','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (d)','SA-17(3)(d)','SA-17'),
('003316','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (d)','SA-17(3)(d)','SA-17'),
('003317','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (d)','SA-17(3)(d)','SA-17'),
('003318','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (e)','SA-17(3)(e)','SA-17'),
('003319','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (e)','SA-17(3)(e)','SA-17'),
('003320','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (3) (e)','SA-17(3)(e)','SA-17'),
('003321','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (a)','SA-17(4)(a)','SA-17'),
('003322','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (a)','SA-17(4)(a)','SA-17'),
('003323','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (a)','SA-17(4)(a)','SA-17'),
('003324','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (b)','SA-17(4)(b)','SA-17'),
('003325','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (c)','SA-17(4)(c)','SA-17'),
('003326','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (c)','SA-17(4)(c)','SA-17'),
('003327','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (c)','SA-17(4)(c)','SA-17'),
('003328','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (d)','SA-17(4)(d)','SA-17'),
('003329','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (d)','SA-17(4)(d)','SA-17'),
('003330','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (d)','SA-17(4)(d)','SA-17'),
('003331','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (e)','SA-17(4)(e)','SA-17'),
('003332','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (e)','SA-17(4)(e)','SA-17'),
('003333','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (4) (e)','SA-17(4)(e)','SA-17'),
('003334','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (a)','SA-17(5)(a)','SA-17'),
('003335','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (a)','SA-17(5)(a)','SA-17'),
('003336','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (a)','SA-17(5)(a)','SA-17'),
('003337','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (b)','SA-17(5)(b)','SA-17'),
('003338','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (b)','SA-17(5)(b)','SA-17'),
('003339','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (5) (b)','SA-17(5)(b)','SA-17'),
('003340','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (6)','SA-17(6)','SA-17'),
('003341','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (6)','SA-17(6)','SA-17'),
('003342','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (6)','SA-17(6)','SA-17'),
('003343','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (7)','SA-17(7)','SA-17'),
('003344','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (7)','SA-17(7)','SA-17'),
('003345','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (7)','SA-17(7)','SA-17'),
('003372','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 b','SA-22b','SA-22'),
('003373','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 b','SA-22b','SA-22'),
('003376','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-22 a','SA-22a','SA-22'),
('003381','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 b','SA-21b','SA-21'),
('003382','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 b','SA-21b','SA-21'),
('003383','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 a','SA-21a','SA-21'),
('003384','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-21','SA-21','SA-21'),
('003385','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-21 a','SA-21a','SA-21'),
('003386','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-20','SA-20','SA-20'),
('003387','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-20','SA-20','SA-20'),
('003601','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1 (b)','AC-1a1(b)','AC-1'),
('003602','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1 (a)','AC-1a1(a)','AC-1'),
('003603','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 1 (b)','AC-1a1(b)','AC-1'),
('003604','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 a 2','AC-1a2','AC-1'),
('003605','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b','AC-1b','AC-1'),
('003606','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b','AC-1b','AC-1'),
('003607','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 b','AC-1b','AC-1'),
('003608','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 1','AC-1c1','AC-1'),
('003609','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 1','AC-1c1','AC-1'),
('003610','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 2','AC-1c2','AC-1'),
('003611','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-1 c 2','AC-1c2','AC-1'),
('003612','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 a','AC-2a','AC-2'),
('003613','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 c','AC-2c','AC-2'),
('003614','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 c','AC-2c','AC-2'),
('003615','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 c','AC-2c','AC-2'),
('003616','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 d 3','AC-2d3','AC-2'),
('003617','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('003618','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('003619','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('003620','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('003621','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('003622','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 f','AC-2f','AC-2'),
('003623','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h','AC-2h','AC-2'),
('003624','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 h','AC-2h','AC-2'),
('003625','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 i 3','AC-2i3','AC-2'),
('003626','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 l','AC-2l','AC-2'),
('003627','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3) (a)','AC-2(3)(a)','AC-2'),
('003628','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3) (b)','AC-2(3)(b)','AC-2'),
('003629','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (3) (c)','AC-2(3)(c)','AC-2'),
('003630','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (7) (c)','AC-2(7)(c)','AC-2'),
('003631','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('003632','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('003633','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('003634','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('003635','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('003636','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (8)','AC-2(8)','AC-2'),
('003637','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-2 (13)','AC-2(13)','AC-2'),
('003638','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4) (a)','AC-3(4)(a)','AC-3'),
('003639','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4) (b)','AC-3(4)(b)','AC-3'),
('003640','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4) (c)','AC-3(4)(c)','AC-3'),
('003641','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4) (d)','AC-3(4)(d)','AC-3'),
('003642','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (4) (e)','AC-3(4)(e)','AC-3'),
('003643','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (10)','AC-3(10)','AC-3'),
('003644','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (11)','AC-3(11)','AC-3'),
('003645','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (11)','AC-3(11)','AC-3'),
('003646','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (12) (a)','AC-3(12)(a)','AC-3'),
('003647','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (12) (a)','AC-3(12)(a)','AC-3'),
('003648','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (12) (b)','AC-3(12)(b)','AC-3'),
('003649','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (12) (c)','AC-3(12)(c)','AC-3'),
('003650','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (13)','AC-3(13)','AC-3'),
('003651','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (13)','AC-3(13)','AC-3'),
('003652','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (13)','AC-3(13)','AC-3'),
('003653','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (13)','AC-3(13)','AC-3'),
('003654','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (14)','AC-3(14)','AC-3'),
('003655','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (14)','AC-3(14)','AC-3'),
('003656','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (14)','AC-3(14)','AC-3'),
('003657','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (15) (a)','AC-3(15)(a)','AC-3'),
('003658','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (15) (a)','AC-3(15)(a)','AC-3'),
('003659','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (15) (b)','AC-3(15)(b)','AC-3'),
('003660','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-3 (15) (b)','AC-3(15)(b)','AC-3'),
('003661','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (1)','AC-4(1)','AC-4'),
('003662','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (4)','AC-4(4)','AC-4'),
('003663','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8) (a)','AC-4(8)(a)','AC-4'),
('003664','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8) (b)','AC-4(8)(b)','AC-4'),
('003665','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (8) (b)','AC-4(8)(b)','AC-4'),
('003666','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (19)','AC-4(19)','AC-4'),
('003667','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (23)','AC-4(23)','AC-4'),
('003668','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (23)','AC-4(23)','AC-4'),
('003669','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (24)','AC-4(24)','AC-4'),
('003670','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (24)','AC-4(24)','AC-4'),
('003671','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (25)','AC-4(25)','AC-4'),
('003672','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (25)','AC-4(25)','AC-4'),
('003673','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (26)','AC-4(26)','AC-4'),
('003674','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (27)','AC-4(27)','AC-4'),
('003675','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (28)','AC-4(28)','AC-4'),
('003676','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (29) (a)','AC-4(29)(a)','AC-4'),
('003677','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (29) (b)','AC-4(29)(b)','AC-4'),
('003678','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (30)','AC-4(30)','AC-4'),
('003679','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (31)','AC-4(31)','AC-4'),
('003680','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (32) (a)','AC-4(32)(a)','AC-4'),
('003681','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (32) (b)','AC-4(32)(b)','AC-4'),
('003682','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (32) (c)','AC-4(32)(c)','AC-4'),
('003683','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-4 (32) (d)','AC-4(32)(d)','AC-4'),
('003684','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-5 a','AC-5a','AC-5'),
('003685','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1) (a)','AC-6(1)(a)','AC-6'),
('003686','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-6 (1) (b)','AC-6(1)(b)','AC-6'),
('003687','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (3)','AC-7(3)','AC-7'),
('003688','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (3)','AC-7(3)','AC-7'),
('003689','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (4) (a)','AC-7(4)(a)','AC-7'),
('003690','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (4) (a)','AC-7(4)(a)','AC-7'),
('003691','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (4) (b)','AC-7(4)(b)','AC-7'),
('003692','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-7 (4) (b)','AC-7(4)(b)','AC-7'),
('003693','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (3)','AC-12(3)','AC-12'),
('003694','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-12 (3)','AC-12(3)','AC-12'),
('003695','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-14 a','AC-14a','AC-14'),
('003696','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('003697','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('003698','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('003699','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('003700','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('003701','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 a','AC-16a','AC-16'),
('003702','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 b','AC-16b','AC-16'),
('003703','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 b','AC-16b','AC-16'),
('003704','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c','AC-16'),
('003705','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 c','AC-16c','AC-16'),
('003706','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 d','AC-16d','AC-16'),
('003707','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 e','AC-16e','AC-16'),
('003708','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 f','AC-16f','AC-16'),
('003709','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 f','AC-16f','AC-16'),
('003710','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 f','AC-16f','AC-16'),
('003711','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 f','AC-16f','AC-16'),
('003712','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('003713','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('003714','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (1)','AC-16(1)','AC-16'),
('003715','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16(2)','AC-16'),
('003716','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (2)','AC-16(2)','AC-16'),
('003717','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('003718','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('003719','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('003720','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('003721','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (3)','AC-16(3)','AC-16'),
('003722','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('003723','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('003724','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('003725','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('003726','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (4)','AC-16(4)','AC-16'),
('003727','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16(5)','AC-16'),
('003728','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16(5)','AC-16'),
('003729','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (5)','AC-16(5)','AC-16'),
('003730','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003731','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003732','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003733','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003734','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003735','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003736','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003737','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (6)','AC-16(6)','AC-16'),
('003738','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (7)','AC-16(7)','AC-16'),
('003739','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16(8)','AC-16'),
('003740','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16(8)','AC-16'),
('003741','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (8)','AC-16(8)','AC-16'),
('003742','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (9)','AC-16(9)','AC-16'),
('003743','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('003744','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('003745','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('003746','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-16 (10)','AC-16(10)','AC-16'),
('003747','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (10)','AC-17(10)','AC-17'),
('003748','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (10)','AC-17(10)','AC-17'),
('003749','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-17 (10)','AC-17(10)','AC-17'),
('003750','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a 1','AC-20a1','AC-20'),
('003751','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a 1','AC-20a1','AC-20'),
('003752','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a 2','AC-20a2','AC-20'),
('003753','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 a 2','AC-20a2','AC-20'),
('003754','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 b','AC-20b','AC-20'),
('003755','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 b','AC-20b','AC-20'),
('003756','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (a)','AC-20(1)(a)','AC-20'),
('003757','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (1) (a)','AC-20(1)(a)','AC-20'),
('003758','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (2)','AC-20(2)','AC-20'),
('003759','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-20 (5)','AC-20(5)','AC-20'),
('003760','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AC-24 (2)','AC-24(2)','AC-24'),
('003761','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 a 1 (b)','AT-1a1(b)','AT-1'),
('003762','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b','AT-1b','AT-1'),
('003763','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b','AT-1b','AT-1'),
('003764','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b','AT-1b','AT-1'),
('003765','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-1 b','AT-1b','AT-1'),
('003766','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 a 2','AT-2a2','AT-2'),
('003767','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 b','AT-2b','AT-2'),
('003768','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 b','AT-2b','AT-2'),
('003769','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 b','AT-2b','AT-2'),
('003770','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 c','AT-2c','AT-2'),
('003771','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 c','AT-2c','AT-2'),
('003772','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 c','AT-2c','AT-2'),
('003773','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 c','AT-2c','AT-2'),
('003774','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 d','AT-2d','AT-2'),
('003775','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (3)','AT-2(3)','AT-2'),
('003776','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (3)','AT-2(3)','AT-2'),
('003777','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (4)','AT-2(4)','AT-2'),
('003778','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (4)','AT-2(4)','AT-2'),
('003779','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (5)','AT-2(5)','AT-2'),
('003780','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (6) (a)','AT-2(6)(a)','AT-2'),
('003781','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 (6) (b)','AT-2(6)(b)','AT-2'),
('003782','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 a','AT-3a','AT-3'),
('003783','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 a 1','AT-3a1','AT-3'),
('003784','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 a 2','AT-3a2','AT-3'),
('003785','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 b','AT-3b','AT-3'),
('003786','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 b','AT-3b','AT-3'),
('003787','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 b','AT-3b','AT-3'),
('003788','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 b','AT-3b','AT-3'),
('003789','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 c','AT-3c','AT-3'),
('003790','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (3)','AT-3(3)','AT-3'),
('003791','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (5)','AT-3(5)','AT-3'),
('003792','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (5)','AT-3(5)','AT-3'),
('003793','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-3 (5)','AT-3(5)','AT-3'),
('003794','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 a','AT-4a','AT-4'),
('003795','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-4 a','AT-4a','AT-4'),
('003796','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-6','AT-6','AT-6'),
('003797','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-6','AT-6','AT-6'),
('003798','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-6','AT-6','AT-6'),
('003799','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 a 1 (b)','AU-1a1(b)','AU-1'),
('003800','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b','AU-1b','AU-1'),
('003801','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b','AU-1b','AU-1'),
('003802','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b','AU-1b','AU-1'),
('003803','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b','AU-1b','AU-1'),
('003804','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b','AU-1b','AU-1'),
('003805','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 b','AU-1b','AU-1'),
('003806','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 1','AU-1c1','AU-1'),
('003807','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 1','AU-1c1','AU-1'),
('003808','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 2','AU-1c2','AU-1'),
('003809','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-1 c 2','AU-1c2','AU-1'),
('003810','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 e','AU-2e','AU-2'),
('003811','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-2 e','AU-2e','AU-2'),
('003812','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (3)','AU-3(3)','AU-3'),
('003813','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-3 (3)','AU-3(3)','AU-3'),
('003814','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 a','AU-5a','AU-5'),
('003815','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (5)','AU-5(5)','AU-5'),
('003816','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-5 (5)','AU-5(5)','AU-5'),
('003817','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 a','AU-6a','AU-6'),
('003818','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 c','AU-6c','AU-6'),
('003819','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 c','AU-6c','AU-6'),
('003820','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (1)','AU-6(1)','AU-6'),
('003821','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-6 (4)','AU-6(4)','AU-6'),
('003822','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('003823','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('003824','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('003825','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('003826','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('003827','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 a','AU-7a','AU-7'),
('003828','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 b','AU-7b','AU-7'),
('003829','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 b','AU-7b','AU-7'),
('003830','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-7 (1)','AU-7(1)','AU-7'),
('003831','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 b','AU-9b','AU-9'),
('003832','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 b','AU-9b','AU-9'),
('003833','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-9 (7)','AU-9(7)','AU-9'),
('003834','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (3)','AU-12(3)','AU-12'),
('003835','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (4)','AU-12(4)','AU-12'),
('003836','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-12 (4)','AU-12(4)','AU-12'),
('003837','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 b 1','AU-13b1','AU-13'),
('003838','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 b 1','AU-13b1','AU-13'),
('003839','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 b 2','AU-13b2','AU-13'),
('003840','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 b 2','AU-13b2','AU-13'),
('003841','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (1)','AU-13(1)','AU-13'),
('003842','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (1)','AU-13(1)','AU-13'),
('003843','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-13 (3)','AU-13(3)','AU-13'),
('003844','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 a','AU-14a','AU-14'),
('003845','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 a','AU-14a','AU-14'),
('003846','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 a','AU-14a','AU-14'),
('003847','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 b','AU-14b','AU-14'),
('003848','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-14 (3)','AU-14(3)','AU-14'),
('003849','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 1 (b)','CA-1a1(b)','CA-1'),
('003850','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 a 2','CA-1a2','CA-1'),
('003851','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b','CA-1b','CA-1'),
('003852','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b','CA-1b','CA-1'),
('003853','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b','CA-1b','CA-1'),
('003854','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 b','CA-1b','CA-1'),
('003855','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 1','CA-1c1','CA-1'),
('003856','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 1','CA-1c1','CA-1'),
('003857','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 2','CA-1c2','CA-1'),
('003858','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-1 c 2','CA-1c2','CA-1'),
('003859','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 a','CA-2a','CA-2'),
('003860','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 c','CA-2c','CA-2'),
('003861','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-2 d','CA-2d','CA-2'),
('003862','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 a','CA-3a','CA-3'),
('003863','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 b','CA-3b','CA-3'),
('003864','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (6)','CA-3(6)','CA-3'),
('003865','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (7) (a)','CA-3(7)(a)','CA-3'),
('003866','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-3 (7) (b)','CA-3(7)(b)','CA-3'),
('003867','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-5 (1)','CA-5(1)','CA-5'),
('003868','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 b','CA-6b','CA-6'),
('003869','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 c 1','CA-6c1','CA-6'),
('003870','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 d','CA-6d','CA-6'),
('003871','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 (1)','CA-6(1)','CA-6'),
('003872','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-6 (2)','CA-6(2)','CA-6'),
('003873','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7','CA-7','CA-7'),
('003874','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 a','CA-7a','CA-7'),
('003875','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 b','CA-7b','CA-7'),
('003876','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 b','CA-7b','CA-7'),
('003877','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 b','CA-7b','CA-7'),
('003878','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 c','CA-7c','CA-7'),
('003879','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g','CA-7'),
('003880','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 g','CA-7g','CA-7'),
('003881','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (4) (a)','CA-7(4)(a)','CA-7'),
('003882','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (4) (b)','CA-7(4)(b)','CA-7'),
('003883','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (4) (c)','CA-7(4)(c)','CA-7'),
('003884','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (5)','CA-7(5)','CA-7'),
('003885','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (5)','CA-7(5)','CA-7'),
('003886','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (5)','CA-7(5)','CA-7'),
('003887','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (6)','CA-7(6)','CA-7'),
('003888','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-7 (6)','CA-7(6)','CA-7'),
('003889','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (3)','CA-8(3)','CA-8'),
('003890','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-8 (3)','CA-8(3)','CA-8'),
('003891','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (b)','CA-9(b)','CA-9'),
('003892','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (c)','CA-9(c)','CA-9'),
('003893','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (c)','CA-9(c)','CA-9'),
('003894','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (d)','CA-9(d)','CA-9'),
('003895','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (d)','CA-9(d)','CA-9'),
('003896','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CA-9 (1)','CA-9(1)','CA-9'),
('003897','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 a 1 (b)','CM-1a1(b)','CM-1'),
('003898','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b','CM-1b','CM-1'),
('003899','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b','CM-1b','CM-1'),
('003900','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b','CM-1b','CM-1'),
('003901','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b','CM-1b','CM-1'),
('003902','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b','CM-1b','CM-1'),
('003903','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 b','CM-1b','CM-1'),
('003904','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 1','CM-1c1','CM-1'),
('003905','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 1','CM-1c1','CM-1'),
('003906','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 2','CM-1c2','CM-1'),
('003907','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 2','CM-1c2','CM-1'),
('003908','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-1 c 2','CM-1c2','CM-1'),
('003909','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 a','CM-2a','CM-2'),
('003910','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 b 3','CM-2b3','CM-2'),
('003911','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-2 (2)','CM-2(2)','CM-2'),
('003912','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 b','CM-3b','CM-3'),
('003913','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (a)','CM-3(1)(a)','CM-3'),
('003914','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (b)','CM-3(1)(b)','CM-3'),
('003915','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (c)','CM-3(1)(c)','CM-3'),
('003916','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (d)','CM-3(1)(d)','CM-3'),
('003917','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (e)','CM-3(1)(e)','CM-3'),
('003918','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (1) (f)','CM-3(1)(f)','CM-3'),
('003919','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (3)','CM-3(3)','CM-3'),
('003920','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (3)','CM-3(3)','CM-3'),
('003921','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3(4)','CM-3'),
('003922','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3(4)','CM-3'),
('003923','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3(4)','CM-3'),
('003924','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (4)','CM-3(4)','CM-3'),
('003925','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (7)','CM-3(7)','CM-3'),
('003926','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (7)','CM-3(7)','CM-3'),
('003927','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (7)','CM-3(7)','CM-3'),
('003928','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (8)','CM-3(8)','CM-3'),
('003929','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-3 (8)','CM-3(8)','CM-3'),
('003930','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4','CM-4','CM-4'),
('003931','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (1)','CM-4(1)','CM-4'),
('003932','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4(2)','CM-4'),
('003933','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4(2)','CM-4'),
('003934','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-4 (2)','CM-4(2)','CM-4'),
('003935','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
('003936','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5','CM-5','CM-5'),
('003937','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (1) (a)','CM-5(1)(a)','CM-5'),
('003938','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (1) (b)','CM-5(1)(b)','CM-5'),
('003939','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (b)','CM-5(5)(b)','CM-5'),
('003940','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-5 (5) (b)','CM-5(5)(b)','CM-5'),
('003941','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 a','CM-6a','CM-6'),
('003942','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 a','CM-6a','CM-6'),
('003943','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 d','CM-6d','CM-6'),
('003944','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 d','CM-6d','CM-6'),
('003945','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 d','CM-6d','CM-6'),
('003946','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 d','CM-6d','CM-6'),
('003947','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-6 (1)','CM-6(1)','CM-6'),
('003948','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 a','CM-7a','CM-7'),
('003949','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (6)','CM-7(6)','CM-7'),
('003950','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (6)','CM-7(6)','CM-7'),
('003951','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (7) (a)','CM-7(7)(a)','CM-7'),
('003952','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (7) (a)','CM-7(7)(a)','CM-7'),
('003953','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (7) (b)','CM-7(7)(b)','CM-7'),
('003954','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (7) (b)','CM-7(7)(b)','CM-7'),
('003955','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (8) (a)','CM-7(8)(a)','CM-7'),
('003956','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (8) (b)','CM-7(8)(b)','CM-7'),
('003957','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (9) (a)','CM-7(9)(a)','CM-7'),
('003958','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (9) (a)','CM-7(9)(a)','CM-7'),
('003959','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (9) (b)','CM-7(9)(b)','CM-7'),
('003960','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (9) (c)','CM-7(9)(c)','CM-7'),
('003961','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-7 (9) (c)','CM-7(9)(c)','CM-7'),
('003962','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 1','CM-8a1','CM-8'),
('003963','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 2','CM-8a2','CM-8'),
('003964','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 3','CM-8a3','CM-8'),
('003965','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 4','CM-8a4','CM-8'),
('003966','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 4','CM-8a4','CM-8'),
('003967','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 a 5','CM-8a5','CM-8'),
('003968','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (2)','CM-8(2)','CM-8'),
('003969','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (3) (a)','CM-8(3)(a)','CM-8'),
('003970','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-8 (8)','CM-8(8)','CM-8'),
('003971','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 a','CM-9a','CM-9'),
('003972','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 a','CM-9a','CM-9'),
('003973','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b','CM-9'),
('003974','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 b','CM-9b','CM-9'),
('003975','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c','CM-9'),
('003976','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 c','CM-9c','CM-9'),
('003977','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 d','CM-9d','CM-9'),
('003978','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 d','CM-9d','CM-9'),
('003979','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-9 d','CM-9d','CM-9'),
('003980','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 (2)','CM-11(2)','CM-11'),
('003981','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-11 (3)','CM-11(3)','CM-11'),
('003982','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 a','CM-12a','CM-12'),
('003983','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 a','CM-12a','CM-12'),
('003984','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 a','CM-12a','CM-12'),
('003985','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 b','CM-12b','CM-12'),
('003986','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 b','CM-12b','CM-12'),
('003987','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 c','CM-12c','CM-12'),
('003988','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 (1)','CM-12(1)','CM-12'),
('003989','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 (1)','CM-12(1)','CM-12'),
('003990','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-12 (1)','CM-12(1)','CM-12'),
('003991','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-13','CM-13','CM-13'),
('003992','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-14','CM-14','CM-14'),
('003993','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CM-14','CM-14','CM-14'),
('003994','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1 (b)','CP-1a1(b)','CP-1'),
('003995','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 a 1 (b)','CP-1a1(b)','CP-1'),
('003996','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b','CP-1b','CP-1'),
('003997','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b','CP-1b','CP-1'),
('003998','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b','CP-1b','CP-1'),
('003999','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b','CP-1b','CP-1'),
('004000','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b','CP-1b','CP-1'),
('004001','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 b','CP-1b','CP-1'),
('004002','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 1','CP-1c1','CP-1'),
('004003','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 1','CP-1c1','CP-1'),
('004004','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 2','CP-1c2','CP-1'),
('004005','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-1 c 2','CP-1c2','CP-1'),
('004006','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a4','CP-2'),
('004007','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 4','CP-2a4','CP-2'),
('004008','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 a 6','CP-2a6','CP-2'),
('004009','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-2 g','CP-2g','CP-2'),
('004010','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 b','CP-3b','CP-3'),
('004011','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 b','CP-3b','CP-3'),
('004012','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 b','CP-3b','CP-3'),
('004013','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-3 b','CP-3b','CP-3'),
('004014','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (3)','CP-4(3)','CP-4'),
('004015','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (5)','CP-4(5)','CP-4'),
('004016','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (5)','CP-4(5)','CP-4'),
('004017','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-4 (5)','CP-4(5)','CP-4'),
('004018','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-6 a','CP-6a','CP-6'),
('004019','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-8 (1) (b)','CP-8(1)(b)','CP-8'),
('004020','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (a)','CP-9(a)','CP-9'),
('004021','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (c)','CP-9(c)','CP-9'),
('004022','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (d)','CP-9(d)','CP-9'),
('004023','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (d)','CP-9(d)','CP-9'),
('004024','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (d)','CP-9(d)','CP-9'),
('004025','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (8)','CP-9(8)','CP-9'),
('004026','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (8)','CP-9(8)','CP-9'),
('004027','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-9 (8)','CP-9(8)','CP-9'),
('004028','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-10','CP-10','CP-10'),
('004029','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-10','CP-10','CP-10'),
('004030','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','CP-10 (6)','CP-10(6)','CP-10'),
('004031','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1','IA-1a1','IA-1'),
('004032','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1 (a)','IA-1a1(a)','IA-1'),
('004033','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 1 (b)','IA-1a1(b)','IA-1'),
('004034','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 a 2','IA-1a2','IA-1'),
('004035','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b','IA-1b','IA-1'),
('004036','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b','IA-1b','IA-1'),
('004037','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b','IA-1b','IA-1'),
('004038','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b','IA-1b','IA-1'),
('004039','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b','IA-1b','IA-1'),
('004040','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 b','IA-1b','IA-1'),
('004041','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 1','IA-1c1','IA-1'),
('004042','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 1','IA-1c1','IA-1'),
('004043','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 2','IA-1c2','IA-1'),
('004044','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-1 c 2','IA-1c2','IA-1'),
('004045','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (5)','IA-2(5)','IA-2'),
('004046','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (6) (a)','IA-2(6)(a)','IA-2'),
('004047','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (6) (b)','IA-2(6)(b)','IA-2'),
('004048','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-2 (6) (b)','IA-2(6)(b)','IA-2'),
('004049','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (5)','IA-4(5)','IA-4'),
('004050','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (8)','IA-4(8)','IA-4'),
('004051','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (9)','IA-4(9)','IA-4'),
('004052','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-4 (9)','IA-4(9)','IA-4'),
('004053','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d','IA-5'),
('004054','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 d','IA-5d','IA-5'),
('004055','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 e','IA-5e','IA-5'),
('004056','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 f','IA-5f','IA-5'),
('004057','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5(1)(a)','IA-5'),
('004058','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5(1)(a)','IA-5'),
('004059','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5(1)(a)','IA-5'),
('004060','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (a)','IA-5(1)(a)','IA-5'),
('004061','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (b)','IA-5(1)(b)','IA-5'),
('004062','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (d)','IA-5(1)(d)','IA-5'),
('004063','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (e)','IA-5(1)(e)','IA-5'),
('004064','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (f)','IA-5(1)(f)','IA-5'),
('004065','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (g)','IA-5(1)(g)','IA-5'),
('004066','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (h)','IA-5(1)(h)','IA-5'),
('004067','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (1) (h)','IA-5(1)(h)','IA-5'),
('004068','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (2) (b) (2)','IA-5(2)(b)(2)','IA-5'),
('004069','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (7)','IA-5(7)','IA-5'),
('004070','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (9)','IA-5(9)','IA-5'),
('004071','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (9)','IA-5(9)','IA-5'),
('004072','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (10)','IA-5(10)','IA-5'),
('004073','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (15)','IA-5(15)','IA-5'),
('004074','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (16)','IA-5(16)','IA-5'),
('004075','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (16)','IA-5(16)','IA-5'),
('004076','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (16)','IA-5(16)','IA-5'),
('004077','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (16)','IA-5(16)','IA-5'),
('004078','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (17)','IA-5(17)','IA-5'),
('004079','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (18) (a)','IA-5(18)(a)','IA-5'),
('004080','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (18) (a)','IA-5(18)(a)','IA-5'),
('004081','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (18) (b)','IA-5(18)(b)','IA-5'),
('004082','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-5 (18) (b)','IA-5(18)(b)','IA-5'),
('004083','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (2) (a)','IA-8(2)(a)','IA-8'),
('004084','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (2) (b)','IA-8(2)(b)','IA-8'),
('004085','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (4)','IA-8(4)','IA-8'),
('004086','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (4)','IA-8(4)','IA-8'),
('004087','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (5)','IA-8(5)','IA-8'),
('004088','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (6)','IA-8(6)','IA-8'),
('004089','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (6)','IA-8(6)','IA-8'),
('004090','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (6)','IA-8(6)','IA-8'),
('004091','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-8 (6)','IA-8(6)','IA-8'),
('004092','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 a','IA-12a','IA-12'),
('004093','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 a','IA-12a','IA-12'),
('004094','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 b','IA-12b','IA-12'),
('004095','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 c','IA-12c','IA-12'),
('004096','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 c','IA-12c','IA-12'),
('004097','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 c','IA-12c','IA-12'),
('004098','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (1)','IA-12(1)','IA-12'),
('004099','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (2)','IA-12(2)','IA-12'),
('004100','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (3)','IA-12(3)','IA-12'),
('004101','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (3)','IA-12(3)','IA-12'),
('004102','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (3)','IA-12(3)','IA-12'),
('004103','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (3)','IA-12(3)','IA-12'),
('004104','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (4)','IA-12(4)','IA-12'),
('004105','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (4)','IA-12(4)','IA-12'),
('004106','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (5)','IA-12(5)','IA-12'),
('004107','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (6)','IA-12(6)','IA-12'),
('004108','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-12 (6)','IA-12(6)','IA-12'),
('004109','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 a 1 (b)','IR-1a1(b)','IR-1'),
('004110','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b','IR-1b','IR-1'),
('004111','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b','IR-1b','IR-1'),
('004112','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 b','IR-1b','IR-1'),
('004113','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 1','IR-1c1','IR-1'),
('004114','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 1','IR-1c1','IR-1'),
('004115','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 2','IR-1c2','IR-1'),
('004116','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-1 c 2','IR-1c2','IR-1'),
('004117','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 (2)','IR-2(2)','IR-2'),
('004118','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 (3)','IR-2(3)','IR-2'),
('004119','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (1)','IR-3(1)','IR-3'),
('004120','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (a)','IR-3(3)(a)','IR-3'),
('004121','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (a)','IR-3(3)(a)','IR-3'),
('004122','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (b)','IR-3(3)(b)','IR-3'),
('004123','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (b)','IR-3(3)(b)','IR-3'),
('004124','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (c)','IR-3(3)(c)','IR-3'),
('004125','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (c)','IR-3(3)(c)','IR-3'),
('004126','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (c)','IR-3(3)(c)','IR-3'),
('004127','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (c)','IR-3(3)(c)','IR-3'),
('004128','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (c)','IR-3(3)(c)','IR-3'),
('004129','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-3 (3) (c)','IR-3(3)(c)','IR-3'),
('004130','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 c','IR-4c','IR-4'),
('004131','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 c','IR-4c','IR-4'),
('004132','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 c','IR-4c','IR-4'),
('004133','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 d','IR-4d','IR-4'),
('004134','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 d','IR-4d','IR-4'),
('004135','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 d','IR-4d','IR-4'),
('004136','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 d','IR-4d','IR-4'),
('004137','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (1)','IR-4(1)','IR-4'),
('004138','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (2)','IR-4(2)','IR-4'),
('004139','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (3)','IR-4(3)','IR-4'),
('004140','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (3)','IR-4(3)','IR-4'),
('004141','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (7)','IR-4(7)','IR-4'),
('004142','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (7)','IR-4(7)','IR-4'),
('004143','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (11)','IR-4(11)','IR-4'),
('004144','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (11)','IR-4(11)','IR-4'),
('004145','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (12)','IR-4(12)','IR-4'),
('004146','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (13)','IR-4(13)','IR-4'),
('004147','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (13)','IR-4(13)','IR-4'),
('004148','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (14)','IR-4(14)','IR-4'),
('004149','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (15) (a)','IR-4(15)(a)','IR-4'),
('004150','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-4 (15) (b)','IR-4(15)(b)','IR-4'),
('004151','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5(1)','IR-5'),
('004152','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5(1)','IR-5'),
('004153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5(1)','IR-5'),
('004154','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-5 (1)','IR-5(1)','IR-5'),
('004155','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (1)','IR-6(1)','IR-6'),
('004156','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-6 (3)','IR-6(3)','IR-6'),
('004157','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 8','IR-8a8','IR-8'),
('004158','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 9','IR-8a9','IR-8'),
('004159','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 a 10','IR-8a10','IR-8'),
('004160','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 (1) (a)','IR-8(1)(a)','IR-8'),
('004161','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 (1) (b)','IR-8(1)(b)','IR-8'),
('004162','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-8 (1) (c)','IR-8(1)(c)','IR-8'),
('004163','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 a','IR-9a','IR-9'),
('004164','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-9 a','IR-9a','IR-9'),
('004165','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 a 1 (b)','MA-1a1(b)','MA-1'),
('004166','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b','MA-1b','MA-1'),
('004167','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b','MA-1b','MA-1'),
('004168','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b','MA-1b','MA-1'),
('004169','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 b','MA-1b','MA-1'),
('004170','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 1','MA-1c1','MA-1'),
('004171','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 1','MA-1c1','MA-1'),
('004172','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 2','MA-1c2','MA-1'),
('004173','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-1 c 2','MA-1c2','MA-1'),
('004174','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('004175','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('004176','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 a','MA-2a','MA-2'),
('004177','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 b','MA-2b','MA-2'),
('004178','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 b','MA-2b','MA-2'),
('004179','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 b','MA-2b','MA-2'),
('004180','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 b','MA-2b','MA-2'),
('004181','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 d','MA-2d','MA-2'),
('004182','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (a)','MA-2(2)(a)','MA-2'),
('004183','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (a)','MA-2(2)(a)','MA-2'),
('004184','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (a)','MA-2(2)(a)','MA-2'),
('004185','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-2 (2) (b)','MA-2(2)(b)','MA-2'),
('004186','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 b','MA-3b','MA-3'),
('004187','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 b','MA-3b','MA-3'),
('004188','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (5)','MA-3(5)','MA-3'),
('004189','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-3 (6)','MA-3(6)','MA-3'),
('004190','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 e','MA-4e','MA-4'),
('004191','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 e','MA-4e','MA-4'),
('004192','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (4) (b) (2)','MA-4(4)(b)(2)','MA-4'),
('004193','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-4 (6)','MA-4(6)','MA-4'),
('004194','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (b)','MA-5(1)(b)','MA-5'),
('004195','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (b)','MA-5(1)(b)','MA-5'),
('004196','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-5 (1) (b)','MA-5(1)(b)','MA-5'),
('004197','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-6 (3)','MA-6(3)','MA-6'),
('004198','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-7','MA-7','MA-7'),
('004199','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-7','MA-7','MA-7'),
('004200','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MA-7','MA-7','MA-7'),
('004201','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 a 1 (b)','MP-1a1(b)','MP-1'),
('004202','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b','MP-1b','MP-1'),
('004203','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b','MP-1b','MP-1'),
('004204','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b','MP-1b','MP-1'),
('004205','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b','MP-1b','MP-1'),
('004206','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 b','MP-1b','MP-1'),
('004207','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 1','MP-1c1','MP-1'),
('004208','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 1','MP-1c1','MP-1'),
('004209','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 2','MP-1c2','MP-1'),
('004210','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-1 c 2','MP-1c2','MP-1'),
('004211','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a','MP-4'),
('004212','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 a','MP-4a','MP-4'),
('004213','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 b','MP-4b','MP-4'),
('004214','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 b','MP-4b','MP-4'),
('004215','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 b','MP-4b','MP-4'),
('004216','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-4 (2)','MP-4(2)','MP-4'),
('004217','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a','MP-5'),
('004218','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-5 a','MP-5a','MP-5'),
('004219','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (2)','MP-6(2)','MP-6'),
('004220','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-6 (2)','MP-6(2)','MP-6'),
('004221','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 a','MP-8a','MP-8'),
('004222','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 a','MP-8a','MP-8'),
('004223','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 b','MP-8b','MP-8'),
('004224','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 b','MP-8b','MP-8'),
('004225','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 c','MP-8c','MP-8'),
('004226','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 c','MP-8c','MP-8'),
('004227','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8(2)','MP-8'),
('004228','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','MP-8 (2)','MP-8(2)','MP-8'),
('004229','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 a 1 (b)','PE-1a1(b)','PE-1'),
('004230','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b','PE-1b','PE-1'),
('004231','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b','PE-1b','PE-1'),
('004232','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b','PE-1b','PE-1'),
('004233','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b','PE-1b','PE-1'),
('004234','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b','PE-1b','PE-1'),
('004235','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 b','PE-1b','PE-1'),
('004236','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 1','PE-1c1','PE-1'),
('004237','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 1','PE-1c1','PE-1'),
('004238','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 2','PE-1c2','PE-1'),
('004239','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-1 c 2','PE-1c2','PE-1'),
('004240','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a','PE-3a','PE-3'),
('004241','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a','PE-3a','PE-3'),
('004242','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 2','PE-3a2','PE-3'),
('004243','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 a 2','PE-3a2','PE-3'),
('004244','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (7)','PE-3(7)','PE-3'),
('004245','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (8)','PE-3(8)','PE-3'),
('004246','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-3 (8)','PE-3(8)','PE-3'),
('004247','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-5 (2)','PE-5(2)','PE-5'),
('004248','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (2)','PE-6(2)','PE-6'),
('004249','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3) (b)','PE-6(3)(b)','PE-6'),
('004250','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-6 (3) (b)','PE-6(3)(b)','PE-6'),
('004251','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 c','PE-8c','PE-8'),
('004252','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 c','PE-8c','PE-8'),
('004253','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 (1)','PE-8(1)','PE-8'),
('004254','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 (3)','PE-8(3)','PE-8'),
('004255','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-8 (3)','PE-8(3)','PE-8'),
('004256','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-10 a','PE-10a','PE-10'),
('004257','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 (1)','PE-14(1)','PE-14'),
('004258','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-14 (2)','PE-14(2)','PE-14'),
('004259','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15 (1)','PE-15(1)','PE-15'),
('004260','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15 (1)','PE-15(1)','PE-15'),
('004261','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-15 (1)','PE-15(1)','PE-15'),
('004262','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 a','PE-17a','PE-17'),
('004263','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-17 d','PE-17d','PE-17'),
('004264','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-19 (1)','PE-19(1)','PE-19'),
('004265','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-19 (1)','PE-19(1)','PE-19'),
('004266','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-21','PE-21','PE-21'),
('004267','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-21','PE-21','PE-21'),
('004268','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-21','PE-21','PE-21'),
('004269','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-22','PE-22','PE-22'),
('004270','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-22','PE-22','PE-22'),
('004271','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-23 a','PE-23a','PE-23'),
('004272','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PE-23 b','PE-23b','PE-23'),
('004273','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 a 1 (b)','PL-1a1(b)','PL-1'),
('004274','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 b','PL-1b','PL-1'),
('004275','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 b','PL-1b','PL-1'),
('004276','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 c 1','PL-1c1','PL-1'),
('004277','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-1 c 2','PL-1c2','PL-1'),
('004278','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 4','PL-2a4','PL-2'),
('004279','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 5','PL-2a5','PL-2'),
('004280','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 7','PL-2a7','PL-2'),
('004281','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 8','PL-2a8','PL-2'),
('004282','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 13','PL-2a13','PL-2'),
('004283','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-2 a 14','PL-2a14','PL-2'),
('004284','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a','PL-4'),
('004285','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a','PL-4'),
('004286','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a','PL-4'),
('004287','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a','PL-4'),
('004288','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 a','PL-4a','PL-4'),
('004289','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 d','PL-4d','PL-4'),
('004290','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-4 (1) (c)','PL-4(1)(c)','PL-4'),
('004291','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-7 a','PL-7a','PL-7'),
('004292','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a','PL-8a','PL-8'),
('004293','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 1','PL-8a1','PL-8'),
('004294','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 2','PL-8a2','PL-8'),
('004295','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 2','PL-8a2','PL-8'),
('004296','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 3','PL-8a3','PL-8'),
('004297','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 a 4','PL-8a4','PL-8'),
('004298','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c','PL-8'),
('004299','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c','PL-8'),
('004300','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 c','PL-8c','PL-8'),
('004301','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('004302','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('004303','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('004304','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('004305','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('004306','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (a)','PL-8(1)(a)','PL-8'),
('004307','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (1) (b)','PL-8(1)(b)','PL-8'),
('004308','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (2)','PL-8(2)','PL-8'),
('004309','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-8 (2)','PL-8(2)','PL-8'),
('004310','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-10','PL-10','PL-10'),
('004311','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PL-11','PL-11','PL-11'),
('004312','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 b','PM-1b','PM-1'),
('004313','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-1 b','PM-1b','PM-1'),
('004314','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 a','PM-3a','PM-3'),
('004315','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 a','PM-3a','PM-3'),
('004316','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 b','PM-3b','PM-3'),
('004317','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 b','PM-3b','PM-3'),
('004318','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-3 c','PM-3c','PM-3'),
('004319','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a1','PM-4'),
('004320','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a1','PM-4'),
('004321','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a1','PM-4'),
('004322','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 1','PM-4a1','PM-4'),
('004323','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 2','PM-4a2','PM-4'),
('004324','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 2','PM-4a2','PM-4'),
('004325','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 3','PM-4a3','PM-4'),
('004326','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 3','PM-4a3','PM-4'),
('004327','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-4 a 3','PM-4a3','PM-4'),
('004328','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5','PM-5','PM-5'),
('004329','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5','PM-5','PM-5'),
('004330','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5','PM-5','PM-5'),
('004331','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5 (1)','PM-5(1)','PM-5'),
('004332','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5 (1)','PM-5(1)','PM-5'),
('004333','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5 (1)','PM-5(1)','PM-5'),
('004334','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-5 (1)','PM-5(1)','PM-5'),
('004335','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
('004336','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
('004337','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-6','PM-6','PM-6'),
('004338','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-7','PM-7','PM-7'),
('004339','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-7','PM-7','PM-7'),
('004340','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-7','PM-7','PM-7'),
('004341','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-7 (1)','PM-7(1)','PM-7'),
('004342','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-7 (1)','PM-7(1)','PM-7'),
('004343','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-8','PM-8','PM-8'),
('004344','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-8','PM-8','PM-8'),
('004345','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-9 a 2','PM-9a2','PM-9'),
('004346','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 a','PM-10a','PM-10'),
('004347','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-10 a','PM-10a','PM-10'),
('004348','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 a','PM-11a','PM-11'),
('004349','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 b','PM-11b','PM-11'),
('004350','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 c','PM-11c','PM-11'),
('004351','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-11 c','PM-11c','PM-11'),
('004352','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-13','PM-13','PM-13'),
('004353','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('004354','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('004355','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('004356','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('004357','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('004358','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 1','PM-14a1','PM-14'),
('004359','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a2','PM-14'),
('004360','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a2','PM-14'),
('004361','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-14 a 2','PM-14a2','PM-14'),
('004362','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 a','PM-15a','PM-15'),
('004363','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 b','PM-15b','PM-15'),
('004364','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-15 c','PM-15c','PM-15'),
('004365','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-16 (1)','PM-16(1)','PM-16'),
('004366','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-17 a','PM-17a','PM-17'),
('004367','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-17 a','PM-17a','PM-17'),
('004368','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-17 b','PM-17b','PM-17'),
('004369','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-17 b','PM-17b','PM-17'),
('004370','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-17 b','PM-17b','PM-17'),
('004371','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-17 b','PM-17b','PM-17'),
('004372','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a','PM-18a','PM-18'),
('004373','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a','PM-18a','PM-18'),
('004374','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 1','PM-18a1','PM-18'),
('004375','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 1','PM-18a1','PM-18'),
('004376','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 2','PM-18a2','PM-18'),
('004377','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 2','PM-18a2','PM-18'),
('004378','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 2','PM-18a2','PM-18'),
('004379','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 2','PM-18a2','PM-18'),
('004380','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 3','PM-18a3','PM-18'),
('004381','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 3','PM-18a3','PM-18'),
('004382','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 4','PM-18a4','PM-18'),
('004383','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 4','PM-18a4','PM-18'),
('004384','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 5','PM-18a5','PM-18'),
('004385','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 5','PM-18a5','PM-18'),
('004386','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 6','PM-18a6','PM-18'),
('004387','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 6','PM-18a6','PM-18'),
('004388','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 a 6','PM-18a6','PM-18'),
('004389','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-18 b','PM-18b','PM-18'),
('004390','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-19','PM-19','PM-19'),
('004391','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-19','PM-19','PM-19'),
('004392','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-19','PM-19','PM-19'),
('004393','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-19','PM-19','PM-19'),
('004394','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20','PM-20','PM-20'),
('004395','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 a','PM-20a','PM-20'),
('004396','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 a','PM-20a','PM-20'),
('004397','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 b','PM-20b','PM-20'),
('004398','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 c','PM-20c','PM-20'),
('004399','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 (1) (a)','PM-20(1)(a)','PM-20'),
('004400','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 (1) (a)','PM-20(1)(a)','PM-20'),
('004401','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 (1) (b)','PM-20(1)(b)','PM-20'),
('004402','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 (1) (c)','PM-20(1)(c)','PM-20'),
('004403','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-20 (1) (c)','PM-20(1)(c)','PM-20'),
('004404','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 a','PM-21a','PM-21'),
('004405','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 a','PM-21a','PM-21'),
('004406','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 a 1','PM-21a1','PM-21'),
('004407','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 a 1','PM-21a1','PM-21'),
('004408','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 a 2','PM-21a2','PM-21'),
('004409','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 a 2','PM-21a2','PM-21'),
('004410','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 b','PM-21b','PM-21'),
('004411','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-21 c','PM-21c','PM-21'),
('004412','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 a','PM-22a','PM-22'),
('004413','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 a','PM-22a','PM-22'),
('004414','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 b','PM-22b','PM-22'),
('004415','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 b','PM-22b','PM-22'),
('004416','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 c','PM-22c','PM-22'),
('004417','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 c','PM-22c','PM-22'),
('004418','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 d','PM-22d','PM-22'),
('004419','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-22 d','PM-22d','PM-22'),
('004420','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-23','PM-23','PM-23'),
('004421','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-23','PM-23','PM-23'),
('004422','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-23','PM-23','PM-23'),
('004423','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-24 a','PM-24a','PM-24'),
('004424','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-24 b','PM-24b','PM-24'),
('004425','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 a','PM-25a','PM-25'),
('004426','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 a','PM-25a','PM-25'),
('004427','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 a','PM-25a','PM-25'),
('004428','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 a','PM-25a','PM-25'),
('004429','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 b','PM-25b','PM-25'),
('004430','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 c','PM-25c','PM-25'),
('004431','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 d','PM-25d','PM-25'),
('004432','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 d','PM-25d','PM-25'),
('004433','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 d','PM-25d','PM-25'),
('004434','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-25 d','PM-25d','PM-25'),
('004435','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26','PM-26','PM-26'),
('004436','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26','PM-26','PM-26'),
('004437','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 a','PM-26a','PM-26'),
('004438','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 a','PM-26a','PM-26'),
('004439','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 b','PM-26b','PM-26'),
('004440','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 c','PM-26c','PM-26'),
('004441','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 c','PM-26c','PM-26'),
('004442','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 d','PM-26d','PM-26'),
('004443','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 d','PM-26d','PM-26'),
('004444','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 e','PM-26e','PM-26'),
('004445','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-26 e','PM-26e','PM-26'),
('004446','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27','PM-27','PM-27'),
('004447','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27','PM-27','PM-27'),
('004448','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27 a 1','PM-27a1','PM-27'),
('004449','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27 a 2','PM-27a2','PM-27'),
('004450','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27 a 2','PM-27a2','PM-27'),
('004451','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27 a 2','PM-27a2','PM-27'),
('004452','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27 b','PM-27b','PM-27'),
('004453','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-27 b','PM-27b','PM-27'),
('004454','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 a 1','PM-28a1','PM-28'),
('004455','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 a 2','PM-28a2','PM-28'),
('004456','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 a 3','PM-28a3','PM-28'),
('004457','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 a 4','PM-28a4','PM-28'),
('004458','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 b','PM-28b','PM-28'),
('004459','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 b','PM-28b','PM-28'),
('004460','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 c','PM-28c','PM-28'),
('004461','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-28 c','PM-28c','PM-28'),
('004462','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-29 a','PM-29a','PM-29'),
('004463','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-29 a','PM-29a','PM-29'),
('004464','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-29 b','PM-29b','PM-29'),
('004465','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-29 b','PM-29b','PM-29'),
('004466','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 a','PM-30a','PM-30'),
('004467','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 a','PM-30a','PM-30'),
('004468','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 a','PM-30a','PM-30'),
('004469','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 a','PM-30a','PM-30'),
('004470','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 b','PM-30b','PM-30'),
('004471','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 c','PM-30c','PM-30'),
('004472','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 c','PM-30c','PM-30'),
('004473','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 a','PM-31a','PM-31'),
('004474','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 a','PM-31a','PM-31'),
('004475','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 a','PM-31a','PM-31'),
('004476','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 b','PM-31b','PM-31'),
('004477','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 b','PM-31b','PM-31'),
('004478','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 b','PM-31b','PM-31'),
('004479','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 b','PM-31b','PM-31'),
('004480','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 b','PM-31b','PM-31'),
('004481','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 b','PM-31b','PM-31'),
('004482','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 c','PM-31c','PM-31'),
('004483','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 c','PM-31c','PM-31'),
('004484','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 d','PM-31d','PM-31'),
('004485','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 d','PM-31d','PM-31'),
('004486','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 e','PM-31e','PM-31'),
('004487','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 e','PM-31e','PM-31'),
('004488','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004489','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004490','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004491','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004492','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004493','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004494','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004495','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-31 f','PM-31f','PM-31'),
('004496','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-32','PM-32','PM-32'),
('004497','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-32','PM-32','PM-32'),
('004498','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 a 1 (b)','PS-1a1(b)','PS-1'),
('004499','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b','PS-1b','PS-1'),
('004500','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b','PS-1b','PS-1'),
('004501','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b','PS-1b','PS-1'),
('004502','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b','PS-1b','PS-1'),
('004503','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b','PS-1b','PS-1'),
('004504','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 b','PS-1b','PS-1'),
('004505','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 1','PS-1c1','PS-1'),
('004506','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 1','PS-1c1','PS-1'),
('004507','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 2','PS-1c2','PS-1'),
('004508','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-1 c 2','PS-1c2','PS-1'),
('004509','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (4)','PS-3(4)','PS-3'),
('004510','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (4)','PS-3(4)','PS-3'),
('004511','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-3 (4)','PS-3(4)','PS-3'),
('004512','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-4 (2)','PS-4(2)','PS-4'),
('004513','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 1','PS-6c1','PS-6'),
('004514','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 1','PS-6c1','PS-6'),
('004515','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 2','PS-6c2','PS-6'),
('004516','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 2','PS-6c2','PS-6'),
('004517','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 2','PS-6c2','PS-6'),
('004518','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-6 c 2','PS-6c2','PS-6'),
('004519','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 b','PS-7b','PS-7'),
('004520','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-7 b','PS-7b','PS-7'),
('004521','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 a','PS-8a','PS-8'),
('004522','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-8 a','PS-8a','PS-8'),
('004523','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-9','PS-9','PS-9'),
('004524','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PS-9','PS-9','PS-9'),
('004525','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 a 1 (a)','PT-1a1(a)','PT-1'),
('004526','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 a','PT-1a','PT-1'),
('004527','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 a','PT-1a','PT-1'),
('004528','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 a 1 (b)','PT-1a1(b)','PT-1'),
('004529','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 a 2','PT-1a2','PT-1'),
('004530','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 b','PT-1b','PT-1'),
('004531','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 b','PT-1b','PT-1'),
('004532','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 b','PT-1b','PT-1'),
('004533','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 c 1','PT-1c1','PT-1'),
('004534','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 c 1','PT-1c1','PT-1'),
('004535','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 c 1','PT-1c1','PT-1'),
('004536','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 c 2','PT-1c2','PT-1'),
('004537','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 c 2','PT-1c2','PT-1'),
('004538','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-1 c 2','PT-1c2','PT-1'),
('004539','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 a','PT-2a','PT-2'),
('004540','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 a','PT-2a','PT-2'),
('004541','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 a','PT-2a','PT-2'),
('004542','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 b','PT-2b','PT-2'),
('004543','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 b','PT-2b','PT-2'),
('004544','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 (1)','PT-2(1)','PT-2'),
('004545','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 (1)','PT-2(1)','PT-2'),
('004546','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 (1)','PT-2(1)','PT-2'),
('004547','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 (2)','PT-2(2)','PT-2'),
('004548','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-2 (2)','PT-2(2)','PT-2'),
('004549','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 a','PT-3a','PT-3'),
('004550','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 a','PT-3a','PT-3'),
('004551','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 b','PT-3b','PT-3'),
('004552','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 c','PT-3c','PT-3'),
('004553','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 c','PT-3c','PT-3'),
('004554','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 d','PT-3d','PT-3'),
('004555','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 d','PT-3d','PT-3'),
('004556','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 d','PT-3d','PT-3'),
('004557','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 d','PT-3d','PT-3'),
('004558','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 (1)','PT-3(1)','PT-3'),
('004559','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 (1)','PT-3(1)','PT-3'),
('004560','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-3 (2)','PT-3(2)','PT-3'),
('004561','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4','PT-4','PT-4'),
('004562','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4','PT-4','PT-4'),
('004563','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (1)','PT-4(1)','PT-4'),
('004564','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (1)','PT-4(1)','PT-4'),
('004565','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (2)','PT-4(2)','PT-4'),
('004566','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (2)','PT-4(2)','PT-4'),
('004567','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (2)','PT-4(2)','PT-4'),
('004568','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (2)','PT-4(2)','PT-4'),
('004569','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (3)','PT-4(3)','PT-4'),
('004570','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-4 (3)','PT-4(3)','PT-4'),
('004571','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 a','PT-5a','PT-5'),
('004572','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 a','PT-5a','PT-5'),
('004573','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 b','PT-5b','PT-5'),
('004574','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 c','PT-5c','PT-5'),
('004575','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 d','PT-5d','PT-5'),
('004576','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 e','PT-5e','PT-5'),
('004577','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 e','PT-5e','PT-5'),
('004578','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 (1)','PT-5(1)','PT-5'),
('004579','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 (1)','PT-5(1)','PT-5'),
('004580','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-5 (2)','PT-5(2)','PT-5'),
('004581','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 a','PT-6a','PT-6'),
('004582','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 a','PT-6a','PT-6'),
('004583','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 b','PT-6b','PT-6'),
('004584','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 c','PT-6c','PT-6'),
('004585','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (1)','PT-6(1)','PT-6'),
('004586','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (1)','PT-6(1)','PT-6'),
('004587','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (1)','PT-6(1)','PT-6'),
('004588','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (2)','PT-6(2)','PT-6'),
('004589','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (2)','PT-6(2)','PT-6'),
('004590','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (2)','PT-6(2)','PT-6'),
('004591','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-6 (2)','PT-6(2)','PT-6'),
('004592','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-7','PT-7','PT-7'),
('004593','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-7','PT-7','PT-7'),
('004594','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-7 (1) (a)','PT-7(1)(a)','PT-7'),
('004595','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-7 (1) (b)','PT-7(1)(b)','PT-7'),
('004596','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-7 (1) (c)','PT-7(1)(c)','PT-7'),
('004597','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-7 (2)','PT-7(2)','PT-7'),
('004598','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-8 a','PT-8a','PT-8'),
('004599','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-8 b','PT-8b','PT-8'),
('004600','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-8 c','PT-8c','PT-8'),
('004601','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-8 d','PT-8d','PT-8'),
('004602','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PT-8 e','PT-8e','PT-8'),
('004603','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1 (b)','RA-1a1(b)','RA-1'),
('004604','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 a 1 (b)','RA-1a1(b)','RA-1'),
('004605','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b','RA-1b','RA-1'),
('004606','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b','RA-1b','RA-1'),
('004607','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b','RA-1b','RA-1'),
('004608','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b','RA-1b','RA-1'),
('004609','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 b','RA-1b','RA-1'),
('004610','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 1','RA-1c1','RA-1'),
('004611','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 1','RA-1c1','RA-1'),
('004612','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 2','RA-1c2','RA-1'),
('004613','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-1 c 2','RA-1c2','RA-1'),
('004614','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 a','RA-2a','RA-2'),
('004615','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 a','RA-2a','RA-2'),
('004616','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 a','RA-2a','RA-2'),
('004617','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-2 (1)','RA-2(1)','RA-2'),
('004618','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 a 1','RA-3a1','RA-3'),
('004619','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 a 1','RA-3a1','RA-3'),
('004620','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 a 3','RA-3a3','RA-3'),
('004621','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 b','RA-3b','RA-3'),
('004622','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 b','RA-3b','RA-3'),
('004623','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 b','RA-3b','RA-3'),
('004624','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (1) (a)','RA-3(1)(a)','RA-3'),
('004625','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (1) (a)','RA-3(1)(a)','RA-3'),
('004626','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (1) (b)','RA-3(1)(b)','RA-3'),
('004627','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (1) (b)','RA-3(1)(b)','RA-3'),
('004628','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (2)','RA-3(2)','RA-3'),
('004629','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (3)','RA-3(3)','RA-3'),
('004630','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (3)','RA-3(3)','RA-3'),
('004631','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (4)','RA-3(4)','RA-3'),
('004632','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (4)','RA-3(4)','RA-3'),
('004633','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-3 (4)','RA-3(4)','RA-3'),
('004634','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 b 2','RA-5b2','RA-5'),
('004635','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 b 3','RA-5b3','RA-5'),
('004636','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 f','RA-5f','RA-5'),
('004637','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (6)','RA-5(6)','RA-5'),
('004638','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (8)','RA-5(8)','RA-5'),
('004639','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (8)','RA-5(8)','RA-5'),
('004640','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-5 (11)','RA-5(11)','RA-5'),
('004641','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-7','RA-7','RA-7'),
('004642','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-7','RA-7','RA-7'),
('004643','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-7','RA-7','RA-7'),
('004644','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-7','RA-7','RA-7'),
('004645','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-8 a','RA-8a','RA-8'),
('004646','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-8 b 1','RA-8b1','RA-8'),
('004647','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-8 b 2','RA-8b2','RA-8'),
('004648','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-9','RA-9','RA-9'),
('004649','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-9','RA-9','RA-9'),
('004650','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-9','RA-9','RA-9'),
('004651','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-10 a 1','RA-10a1','RA-10'),
('004652','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-10 a 2','RA-10a2','RA-10'),
('004653','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-10 b','RA-10b','RA-10'),
('004654','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','RA-10 b','RA-10b','RA-10'),
('004655','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 a 1 (b)','SA-1a1(b)','SA-1'),
('004656','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b','SA-1b','SA-1'),
('004657','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b','SA-1b','SA-1'),
('004658','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b','SA-1b','SA-1'),
('004659','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b','SA-1b','SA-1'),
('004660','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b','SA-1b','SA-1'),
('004661','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 b','SA-1b','SA-1'),
('004662','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 1','SA-1c1','SA-1'),
('004663','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 1','SA-1c1','SA-1'),
('004664','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 2','SA-1c2','SA-1'),
('004665','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-1 c 2','SA-1c2','SA-1'),
('004666','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 a','SA-2a','SA-2'),
('004667','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 c','SA-2c','SA-2'),
('004668','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-2 c','SA-2c','SA-2'),
('004669','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004670','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004671','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004672','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004673','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004674','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004675','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 a','SA-3a','SA-3'),
('004676','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 b','SA-3b','SA-3'),
('004677','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 c','SA-3c','SA-3'),
('004678','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 d','SA-3d','SA-3'),
('004679','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (1)','SA-3(1)','SA-3'),
('004680','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (2) (a)','SA-3(2)(a)','SA-3'),
('004681','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (2) (a)','SA-3(2)(a)','SA-3'),
('004682','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (2) (a)','SA-3(2)(a)','SA-3'),
('004683','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (2) (b)','SA-3(2)(b)','SA-3'),
('004684','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (3)','SA-3(3)','SA-3'),
('004685','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-3 (3)','SA-3(3)','SA-3'),
('004686','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4','SA-4','SA-4'),
('004687','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 a','SA-4a','SA-4'),
('004688','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 c','SA-4c','SA-4'),
('004689','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 d','SA-4d','SA-4'),
('004690','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 d','SA-4d','SA-4'),
('004691','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 e','SA-4e','SA-4'),
('004692','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 f','SA-4f','SA-4'),
('004693','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 f','SA-4f','SA-4'),
('004694','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 h','SA-4h','SA-4'),
('004695','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 h','SA-4h','SA-4'),
('004696','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 h','SA-4h','SA-4'),
('004697','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3) (a)','SA-4(3)(a)','SA-4'),
('004698','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3) (a)','SA-4(3)(a)','SA-4'),
('004699','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3) (b)','SA-4(3)(b)','SA-4'),
('004700','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3) (b)','SA-4(3)(b)','SA-4'),
('004701','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3) (c)','SA-4(3)(c)','SA-4'),
('004702','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (3) (c)','SA-4(3)(c)','SA-4'),
('004703','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (11)','SA-4(11)','SA-4'),
('004704','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (11)','SA-4(11)','SA-4'),
('004705','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (12) (a)','SA-4(12)(a)','SA-4'),
('004706','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (12) (b)','SA-4(12)(b)','SA-4'),
('004707','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-4 (12) (b)','SA-4(12)(b)','SA-4'),
('004708','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 a 2','SA-5a2','SA-5'),
('004709','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 1','SA-5b1','SA-5'),
('004710','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 2','SA-5b2','SA-5'),
('004711','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-5 b 3','SA-5b3','SA-5'),
('004712','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('004713','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('004714','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('004715','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('004716','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8','SA-8','SA-8'),
('004717','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (1)','SA-8(1)','SA-8'),
('004718','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (2)','SA-8(2)','SA-8'),
('004719','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (2)','SA-8(2)','SA-8'),
('004720','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (3)','SA-8(3)','SA-8'),
('004721','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (3)','SA-8(3)','SA-8'),
('004722','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (4)','SA-8(4)','SA-8'),
('004723','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (4)','SA-8(4)','SA-8'),
('004724','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (5)','SA-8(5)','SA-8'),
('004725','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (5)','SA-8(5)','SA-8'),
('004726','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (6)','SA-8(6)','SA-8'),
('004727','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (6)','SA-8(6)','SA-8'),
('004728','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (7)','SA-8(7)','SA-8'),
('004729','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (7)','SA-8(7)','SA-8'),
('004730','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (8)','SA-8(8)','SA-8'),
('004731','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (8)','SA-8(8)','SA-8'),
('004732','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (9)','SA-8(9)','SA-8'),
('004733','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (9)','SA-8(9)','SA-8'),
('004734','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (10)','SA-8(10)','SA-8'),
('004735','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (10)','SA-8(10)','SA-8'),
('004736','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (11)','SA-8(11)','SA-8'),
('004737','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (11)','SA-8(11)','SA-8'),
('004738','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (12)','SA-8(12)','SA-8'),
('004739','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (12)','SA-8(12)','SA-8'),
('004740','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (13)','SA-8(13)','SA-8'),
('004741','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (13)','SA-8(13)','SA-8'),
('004742','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (14)','SA-8(14)','SA-8'),
('004743','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (14)','SA-8(14)','SA-8'),
('004744','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (15)','SA-8(15)','SA-8'),
('004745','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (15)','SA-8(15)','SA-8'),
('004746','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (16)','SA-8(16)','SA-8'),
('004747','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (16)','SA-8(16)','SA-8'),
('004748','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (17)','SA-8(17)','SA-8'),
('004749','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (17)','SA-8(17)','SA-8'),
('004750','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (18)','SA-8(18)','SA-8'),
('004751','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (18)','SA-8(18)','SA-8'),
('004752','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (19)','SA-8(19)','SA-8'),
('004753','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (19)','SA-8(19)','SA-8'),
('004754','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (20)','SA-8(20)','SA-8'),
('004755','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (20)','SA-8(20)','SA-8'),
('004756','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (21)','SA-8(21)','SA-8'),
('004757','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (21)','SA-8(21)','SA-8'),
('004758','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (22)','SA-8(22)','SA-8'),
('004759','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (22)','SA-8(22)','SA-8'),
('004760','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (23)','SA-8(23)','SA-8'),
('004761','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (23)','SA-8(23)','SA-8'),
('004762','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (24)','SA-8(24)','SA-8'),
('004763','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (24)','SA-8(24)','SA-8'),
('004764','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (25)','SA-8(25)','SA-8'),
('004765','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (25)','SA-8(25)','SA-8'),
('004766','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (26)','SA-8(26)','SA-8'),
('004767','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (26)','SA-8(26)','SA-8'),
('004768','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (27)','SA-8(27)','SA-8'),
('004769','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (27)','SA-8(27)','SA-8'),
('004770','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (28)','SA-8(28)','SA-8'),
('004771','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (28)','SA-8(28)','SA-8'),
('004772','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (29)','SA-8(29)','SA-8'),
('004773','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (29)','SA-8(29)','SA-8'),
('004774','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (30)','SA-8(30)','SA-8'),
('004775','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (30)','SA-8(30)','SA-8'),
('004776','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (31)','SA-8(31)','SA-8'),
('004777','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (31)','SA-8(31)','SA-8'),
('004778','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (32)','SA-8(32)','SA-8'),
('004779','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (32)','SA-8(32)','SA-8'),
('004780','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (33)','SA-8(33)','SA-8'),
('004781','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-8 (33)','SA-8(33)','SA-8'),
('004782','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 a','SA-9a','SA-9'),
('004783','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 a','SA-9a','SA-9'),
('004784','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 a','SA-9a','SA-9'),
('004785','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 b','SA-9b','SA-9'),
('004786','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 b','SA-9b','SA-9'),
('004787','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('004788','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('004789','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('004790','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (3)','SA-9(3)','SA-9'),
('004791','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (6)','SA-9(6)','SA-9'),
('004792','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (7)','SA-9(7)','SA-9'),
('004793','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-9 (8)','SA-9(8)','SA-9'),
('004794','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 d','SA-10d','SA-10'),
('004795','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (7)','SA-10(7)','SA-10'),
('004796','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (7)','SA-10(7)','SA-10'),
('004797','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-10 (7)','SA-10(7)','SA-10'),
('004798','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 a','SA-11a','SA-11'),
('004799','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 a','SA-11a','SA-11'),
('004800','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 b','SA-11b','SA-11'),
('004801','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (a)','SA-11(2)(a)','SA-11'),
('004802','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (a)','SA-11(2)(a)','SA-11'),
('004803','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (b)','SA-11(2)(b)','SA-11'),
('004804','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (b)','SA-11(2)(b)','SA-11'),
('004805','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (c)','SA-11(2)(c)','SA-11'),
('004806','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (c)','SA-11(2)(c)','SA-11'),
('004807','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (d)','SA-11(2)(d)','SA-11'),
('004808','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (2) (d)','SA-11(2)(d)','SA-11'),
('004809','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11(3)(a)','SA-11'),
('004810','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11(3)(a)','SA-11'),
('004811','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (3) (a)','SA-11(3)(a)','SA-11'),
('004812','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5) (a)','SA-11(5)(a)','SA-11'),
('004813','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (5) (b)','SA-11(5)(b)','SA-11'),
('004814','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (9)','SA-11(9)','SA-11'),
('004815','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-11 (9)','SA-11(9)','SA-11'),
('004816','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 a 1','SA-15a1','SA-15'),
('004817','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('004818','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('004819','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('004820','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('004821','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('004822','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 b','SA-15b','SA-15'),
('004823','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (2)','SA-15(2)','SA-15'),
('004824','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (2)','SA-15(2)','SA-15'),
('004825','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3) (a)','SA-15(3)(a)','SA-15'),
('004826','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (3) (b)','SA-15(3)(b)','SA-15'),
('004827','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (a)','SA-15(7)(a)','SA-15'),
('004828','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (b)','SA-15(7)(b)','SA-15'),
('004829','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (c)','SA-15(7)(c)','SA-15'),
('004830','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (7) (d)','SA-15(7)(d)','SA-15'),
('004831','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (10)','SA-15(10)','SA-15'),
('004832','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (10)','SA-15(10)','SA-15'),
('004833','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (11)','SA-15(11)','SA-15'),
('004834','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-15 (12)','SA-15(12)','SA-15'),
('004835','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-16','SA-16','SA-16'),
('004836','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-16','SA-16','SA-16'),
('004837','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17','SA-17','SA-17'),
('004838','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 a','SA-17a','SA-17'),
('004839','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 b','SA-17b','SA-17'),
('004840','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 b','SA-17b','SA-17'),
('004841','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 c','SA-17c','SA-17'),
('004842','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (a)','SA-17(1)(a)','SA-17'),
('004843','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (a)','SA-17(1)(a)','SA-17'),
('004844','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (1) (b)','SA-17(1)(b)','SA-17'),
('004845','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (8)','SA-17(8)','SA-17'),
('004846','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (8)','SA-17(8)','SA-17'),
('004847','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (8)','SA-17(8)','SA-17'),
('004848','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (9)','SA-17(9)','SA-17'),
('004849','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-17 (9)','SA-17(9)','SA-17'),
('004850','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-23','SA-23','SA-23'),
('004851','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SA-23','SA-23','SA-23'),
('004852','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1 (a)','SC-1a1(a)','SC-1'),
('004853','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 1 (b)','SC-1a1(b)','SC-1'),
('004854','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 a 2','SC-1a2','SC-1'),
('004855','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b','SC-1b','SC-1'),
('004856','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b','SC-1b','SC-1'),
('004857','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b','SC-1b','SC-1'),
('004858','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b','SC-1b','SC-1'),
('004859','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b','SC-1b','SC-1'),
('004860','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 b','SC-1b','SC-1'),
('004861','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 1','SC-1c1','SC-1'),
('004862','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 1','SC-1c1','SC-1'),
('004863','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 2','SC-1c2','SC-1'),
('004864','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-1 c 2','SC-1c2','SC-1'),
('004865','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-2 (2)','SC-2(2)','SC-2'),
('004866','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 b','SC-5b','SC-5'),
('004867','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-5 b','SC-5b','SC-5'),
('004868','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 c','SC-7c','SC-7'),
('004869','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (f)','SC-7(4)(f)','SC-7'),
('004870','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (g)','SC-7(4)(g)','SC-7'),
('004871','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (4) (h)','SC-7(4)(h)','SC-7'),
('004872','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (5)','SC-7(5)','SC-7'),
('004873','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (7)','SC-7(7)','SC-7'),
('004874','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (10) (b)','SC-7(10)(b)','SC-7'),
('004875','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (10) (b)','SC-7(10)(b)','SC-7'),
('004876','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (24) (a)','SC-7(24)(a)','SC-7'),
('004877','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (24) (a)','SC-7(24)(a)','SC-7'),
('004878','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (24) (b)','SC-7(24)(b)','SC-7'),
('004879','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (24) (c)','SC-7(24)(c)','SC-7'),
('004880','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (24) (d)','SC-7(24)(d)','SC-7'),
('004881','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (25)','SC-7(25)','SC-7'),
('004882','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (25)','SC-7(25)','SC-7'),
('004883','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (25)','SC-7(25)','SC-7'),
('004884','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (26)','SC-7(26)','SC-7'),
('004885','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (26)','SC-7(26)','SC-7'),
('004886','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (27)','SC-7(27)','SC-7'),
('004887','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (27)','SC-7(27)','SC-7'),
('004888','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (27)','SC-7(27)','SC-7'),
('004889','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (28)','SC-7(28)','SC-7'),
('004890','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (28)','SC-7(28)','SC-7'),
('004891','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (29)','SC-7(29)','SC-7'),
('004892','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-7 (29)','SC-7(29)','SC-7'),
('004893','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (5)','SC-8(5)','SC-8'),
('004894','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-8 (5)','SC-8(5)','SC-8'),
('004895','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 b','SC-11b','SC-11'),
('004896','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 (1) (b)','SC-11(1)(b)','SC-11'),
('004897','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-11 (1) (b)','SC-11(1)(b)','SC-11'),
('004898','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (3)','SC-12(3)','SC-12'),
('004899','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-12 (6)','SC-12(6)','SC-12'),
('004900','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-13 a','SC-13a','SC-13'),
('004901','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
('004902','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
('004903','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16','SC-16','SC-16'),
('004904','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (1)','SC-16(1)','SC-16'),
('004905','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (2)','SC-16(2)','SC-16'),
('004906','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (3)','SC-16(3)','SC-16'),
('004907','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (3)','SC-16(3)','SC-16'),
('004908','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-16 (3)','SC-16(3)','SC-16'),
('004909','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-17 b','SC-17b','SC-17'),
('004910','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (3)','SC-28(3)','SC-28'),
('004911','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-28 (3)','SC-28(3)','SC-28'),
('004912','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-32 (1)','SC-32(1)','SC-32'),
('004913','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1) (b)','SC-36(1)(b)','SC-36'),
('004914','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (1) (b)','SC-36(1)(b)','SC-36'),
('004915','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (2)','SC-36(2)','SC-36'),
('004916','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-36 (2)','SC-36(2)','SC-36'),
('004917','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (4)','SC-42(4)','SC-42'),
('004918','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (4)','SC-42(4)','SC-42'),
('004919','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (4)','SC-42(4)','SC-42'),
('004920','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (5)','SC-42(5)','SC-42'),
('004921','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-42 (5)','SC-42(5)','SC-42'),
('004922','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45','SC-45','SC-45'),
('004923','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (1) (a)','SC-45(1)(a)','SC-45'),
('004924','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (1) (a)','SC-45(1)(a)','SC-45'),
('004925','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (1) (a)','SC-45(1)(a)','SC-45'),
('004926','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (1) (b)','SC-45(1)(b)','SC-45'),
('004927','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (1) (b)','SC-45(1)(b)','SC-45'),
('004928','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (2) (a)','SC-45(2)(a)','SC-45'),
('004929','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-45 (2) (b)','SC-45(2)(b)','SC-45'),
('004930','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-46','SC-46','SC-46'),
('004931','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-47','SC-47','SC-47'),
('004932','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48','SC-48','SC-48'),
('004933','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48','SC-48','SC-48'),
('004934','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48','SC-48','SC-48'),
('004935','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48','SC-48','SC-48'),
('004936','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48 (1)','SC-48(1)','SC-48'),
('004937','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48 (1)','SC-48(1)','SC-48'),
('004938','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48 (1)','SC-48(1)','SC-48'),
('004939','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-48 (1)','SC-48(1)','SC-48'),
('004940','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-49','SC-49','SC-49'),
('004941','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-49','SC-49','SC-49'),
('004942','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-50','SC-50','SC-50'),
('004943','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SC-50','SC-50','SC-50'),
('004944','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 a 1 (b)','SI-1a1(b)','SI-1'),
('004945','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b','SI-1b','SI-1'),
('004946','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b','SI-1b','SI-1'),
('004947','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b','SI-1b','SI-1'),
('004948','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b','SI-1b','SI-1'),
('004949','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b','SI-1b','SI-1'),
('004950','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 b','SI-1b','SI-1'),
('004951','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 1','SI-1c1','SI-1'),
('004952','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 1','SI-1c1','SI-1'),
('004953','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 2','SI-1c2','SI-1'),
('004954','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-1 c 2','SI-1c2','SI-1'),
('004955','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2(2)','SI-2'),
('004956','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2(2)','SI-2'),
('004957','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2(2)','SI-2'),
('004958','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2(2)','SI-2'),
('004959','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2(2)','SI-2'),
('004960','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (2)','SI-2(2)','SI-2'),
('004961','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (4)','SI-2(4)','SI-2'),
('004962','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-2 (4)','SI-2(4)','SI-2'),
('004963','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 a','SI-3a','SI-3'),
('004964','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 b','SI-3b','SI-3'),
('004965','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 b','SI-3b','SI-3'),
('004966','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-3 c 2','SI-3c2','SI-3'),
('004967','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 d','SI-4d','SI-4'),
('004968','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (2)','SI-4(2)','SI-4'),
('004969','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (3)','SI-4(3)','SI-4'),
('004970','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (3)','SI-4(3)','SI-4'),
('004971','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (a)','SI-4(4)(a)','SI-4'),
('004972','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (a)','SI-4(4)(a)','SI-4'),
('004973','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (b)','SI-4(4)(b)','SI-4'),
('004974','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (4) (b)','SI-4(4)(b)','SI-4'),
('004975','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (9)','SI-4(9)','SI-4'),
('004976','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (9)','SI-4(9)','SI-4'),
('004977','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4(10)','SI-4'),
('004978','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4(10)','SI-4'),
('004979','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (10)','SI-4(10)','SI-4'),
('004980','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (12)','SI-4(12)','SI-4'),
('004981','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (16)','SI-4(16)','SI-4'),
('004982','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-4 (25)','SI-4(25)','SI-4'),
('004983','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-5 (1)','SI-5(1)','SI-5'),
('004984','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 a','SI-6a','SI-6'),
('004985','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 a','SI-6a','SI-6'),
('004986','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b','SI-6'),
('004987','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b','SI-6'),
('004988','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 b','SI-6b','SI-6'),
('004989','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 c','SI-6c','SI-6'),
('004990','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 c','SI-6c','SI-6'),
('004991','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 d','SI-6d','SI-6'),
('004992','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 d','SI-6d','SI-6'),
('004993','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (2)','SI-6(2)','SI-6'),
('004994','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (3)','SI-6(3)','SI-6'),
('004995','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-6 (3)','SI-6(3)','SI-6'),
('004996','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 b','SI-7b','SI-7'),
('004997','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 b','SI-7b','SI-7'),
('004998','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (17)','SI-7(17)','SI-7'),
('004999','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-7 (17)','SI-7(17)','SI-7'),
('005000','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 b','SI-8b','SI-8'),
('005001','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 b','SI-8b','SI-8'),
('005002','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-8 (2)','SI-8(2)','SI-8'),
('005003','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-10 (6)','SI-10(6)','SI-10'),
('005004','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12 (1)','SI-12(1)','SI-12'),
('005005','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12 (1)','SI-12(1)','SI-12'),
('005006','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12 (2)','SI-12(2)','SI-12'),
('005007','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12 (2)','SI-12(2)','SI-12'),
('005008','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-12 (3)','SI-12(3)','SI-12'),
('005009','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (3)','SI-13(3)','SI-13'),
('005010','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-13 (4) (b)','SI-13(4)(b)','SI-13'),
('005011','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (2) (a)','SI-14(2)(a)','SI-14'),
('005012','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (2) (a)','SI-14(2)(a)','SI-14'),
('005013','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (2) (a)','SI-14(2)(a)','SI-14'),
('005014','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (2) (a)','SI-14(2)(a)','SI-14'),
('005015','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (2) (b)','SI-14(2)(b)','SI-14'),
('005016','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (3)','SI-14(3)','SI-14'),
('005017','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-14 (3)','SI-14(3)','SI-14'),
('005018','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 a','SI-18a','SI-18'),
('005019','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 a','SI-18a','SI-18'),
('005020','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 b 1','SI-18b1','SI-18'),
('005021','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (1)','SI-18(1)','SI-18'),
('005022','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (1)','SI-18(1)','SI-18'),
('005023','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (2)','SI-18(2)','SI-18'),
('005024','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (3)','SI-18(3)','SI-18'),
('005025','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (4)','SI-18(4)','SI-18'),
('005026','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (5)','SI-18(5)','SI-18'),
('005027','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (5)','SI-18(5)','SI-18'),
('005028','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-18 (5)','SI-18(5)','SI-18'),
('005029','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 a','SI-19a','SI-19'),
('005030','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 a','SI-19a','SI-19'),
('005031','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 b','SI-19b','SI-19'),
('005032','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 b','SI-19b','SI-19'),
('005033','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (1)','SI-19(1)','SI-19'),
('005034','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (2)','SI-19(2)','SI-19'),
('005035','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (3)','SI-19(3)','SI-19'),
('005036','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (4)','SI-19(4)','SI-19'),
('005037','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (5)','SI-19(5)','SI-19'),
('005038','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (6)','SI-19(6)','SI-19'),
('005039','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (7)','SI-19(7)','SI-19'),
('005040','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-19 (8)','SI-19(8)','SI-19'),
('005041','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-20','SI-20','SI-20'),
('005042','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-20','SI-20','SI-20'),
('005043','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-21','SI-21','SI-21'),
('005044','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-21','SI-21','SI-21'),
('005045','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-21','SI-21','SI-21'),
('005046','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-22 a','SI-22a','SI-22'),
('005047','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-22 a','SI-22a','SI-22'),
('005048','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-22 b','SI-22b','SI-22'),
('005049','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-22 b','SI-22b','SI-22'),
('005050','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-23 a','SI-23a','SI-23'),
('005051','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-23 a','SI-23a','SI-23'),
('005052','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-23 a','SI-23a','SI-23'),
('005053','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-23 b','SI-23b','SI-23'),
('005054','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-23 b','SI-23b','SI-23'),
('005055','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SI-23 b','SI-23b','SI-23'),
('005056','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 a 1','SR-1a1','SR-1'),
('005057','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 a 1 (a)','SR-1a1(a)','SR-1'),
('005058','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 a 1 (b)','SR-1a1(b)','SR-1'),
('005059','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 a 2','SR-1a2','SR-1'),
('005060','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 b','SR-1b','SR-1'),
('005061','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 b','SR-1b','SR-1'),
('005062','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 b','SR-1b','SR-1'),
('005063','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 b','SR-1b','SR-1'),
('005064','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 1','SR-1c1','SR-1'),
('005065','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 1','SR-1c1','SR-1'),
('005066','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 1','SR-1c1','SR-1'),
('005067','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 1','SR-1c1','SR-1'),
('005068','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 2','SR-1c2','SR-1'),
('005069','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 2','SR-1c2','SR-1'),
('005070','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 2','SR-1c2','SR-1'),
('005071','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-1 c 2','SR-1c2','SR-1'),
('005072','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 a','SR-2a','SR-2'),
('005073','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 a','SR-2a','SR-2'),
('005074','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 b','SR-2b','SR-2'),
('005075','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 b','SR-2b','SR-2'),
('005076','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 c','SR-2c','SR-2'),
('005077','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 (1)','SR-2(1)','SR-2'),
('005078','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 (1)','SR-2(1)','SR-2'),
('005079','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-2 (1)','SR-2(1)','SR-2'),
('005080','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 a','SR-3a','SR-3'),
('005081','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 a','SR-3a','SR-3'),
('005082','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 a','SR-3a','SR-3'),
('005083','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 a','SR-3a','SR-3'),
('005084','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 a','SR-3a','SR-3'),
('005085','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 a','SR-3a','SR-3'),
('005086','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 b','SR-3b','SR-3'),
('005087','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 b','SR-3b','SR-3'),
('005088','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 b','SR-3b','SR-3'),
('005089','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 c','SR-3c','SR-3'),
('005090','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 c','SR-3c','SR-3'),
('005091','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 (1)','SR-3(1)','SR-3'),
('005092','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 (1)','SR-3(1)','SR-3'),
('005093','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 (2)','SR-3(2)','SR-3'),
('005094','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 (2)','SR-3(2)','SR-3'),
('005095','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-3 (3)','SR-3(3)','SR-3'),
('005096','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4','SR-4','SR-4'),
('005097','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4','SR-4','SR-4'),
('005098','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4','SR-4','SR-4'),
('005099','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4','SR-4','SR-4'),
('005100','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (1)','SR-4(1)','SR-4'),
('005101','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (1)','SR-4(1)','SR-4'),
('005102','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (2)','SR-4(2)','SR-4'),
('005103','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (2)','SR-4(2)','SR-4'),
('005104','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (3)','SR-4(3)','SR-4'),
('005105','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (3)','SR-4(3)','SR-4'),
('005106','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (3)','SR-4(3)','SR-4'),
('005107','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (3)','SR-4(3)','SR-4'),
('005108','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (4)','SR-4(4)','SR-4'),
('005109','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (4)','SR-4(4)','SR-4'),
('005110','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (4)','SR-4(4)','SR-4'),
('005111','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-4 (4)','SR-4(4)','SR-4'),
('005112','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-5','SR-5','SR-5'),
('005113','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-5','SR-5','SR-5'),
('005114','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-5 (1)','SR-5(1)','SR-5'),
('005115','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-5 (1)','SR-5(1)','SR-5'),
('005116','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-5 (1)','SR-5(1)','SR-5'),
('005117','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-5 (2)','SR-5(2)','SR-5'),
('005118','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-6','SR-6','SR-6'),
('005119','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-6','SR-6','SR-6'),
('005120','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-6 (1)','SR-6(1)','SR-6'),
('005121','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-6 (1)','SR-6(1)','SR-6'),
('005122','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-7','SR-7','SR-7'),
('005123','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-7','SR-7','SR-7'),
('005124','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-8','SR-8','SR-8'),
('005125','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-8','SR-8','SR-8'),
('005126','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-9','SR-9','SR-9'),
('005127','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-9 (1)','SR-9(1)','SR-9'),
('005128','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-10','SR-10','SR-10'),
('005129','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-10','SR-10','SR-10'),
('005130','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-10','SR-10','SR-10'),
('005131','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-10','SR-10','SR-10'),
('005132','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 a','SR-11a','SR-11'),
('005133','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 a','SR-11a','SR-11'),
('005134','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 b','SR-11b','SR-11'),
('005135','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 b','SR-11b','SR-11'),
('005136','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 b','SR-11b','SR-11'),
('005137','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (1)','SR-11(1)','SR-11'),
('005138','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (1)','SR-11(1)','SR-11'),
('005139','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (2)','SR-11(2)','SR-11'),
('005140','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (2)','SR-11(2)','SR-11'),
('005141','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (2)','SR-11(2)','SR-11'),
('005142','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (3)','SR-11(3)','SR-11'),
('005143','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-11 (3)','SR-11(3)','SR-11'),
('005144','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-12','SR-12','SR-12'),
('005145','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-12','SR-12','SR-12'),
('005146','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','SR-12','SR-12','SR-12'),
('005147','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AT-2 a 1','AT-2a1','AT-2'),
('005149','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','AU-16 (3)','AU-16(3)','AU-16'),
('005150','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','PM-30 (1)','PM-30(1)','PM-30'),
('005151','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 b','IR-2b','IR-2'),
('005152','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 b','IR-2b','IR-2'),
('005153','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-2 b','IR-2b','IR-2'),
('005154','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IR-7 (1)','IR-7(1)','IR-7'),
('005155','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13','IA-13','IA-13'),
('005156','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (01)','IA-13(01)','IA-13'),
('005157','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (02)','IA-13(02)','IA-13'),
('005158','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (a)','IA-13(03)(a)','IA-13'),
('005159','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (b)','IA-13(03)(b)','IA-13'),
('005160','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (c)','IA-13(03)(c)','IA-13'),
('005161','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (d)','IA-13(03)(d)','IA-13'),
('005162','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (e)','IA-13(03)(e)','IA-13'),
('005163','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (f)','IA-13(03)(f)','IA-13'),
('005164','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (a)','IA-13(03)(a)','IA-13'),
('005165','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (b)','IA-13(03)(b)','IA-13'),
('005166','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (c)','IA-13(03)(c)','IA-13'),
('005167','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (d)','IA-13(03)(d)','IA-13'),
('005168','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (e)','IA-13(03)(e)','IA-13'),
('005169','NIST','NIST SP 800-53 Revision 5','5','http://csrc.nist.gov/publications/PubsSPs.html','IA-13 (03) (f)','IA-13(03)(f)','IA-13');
/*!40000 ALTER TABLE `cci_reference_map` ENABLE KEYS */;
UNLOCK TABLES;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
================================================
FILE: api/source/service/migrations/sql/generateSchema.sh
================================================
#!/bin/bash
# Use this script to generate the current schema and static data for the 'stigman' database.
# It will produce two SQL scripts which will be used in the stig manager application to recreate a new database schema in its most recent state.
#NEEDS: mysqldump
#How to use:
# 1. Ensure that the MySQL server is running and that the 'stigman' database is accessible and in its most recent state.
# 2. Run this script from the command line.
# 3. When stig-manager is started, it will automatically run the SQL scripts to create the database schema and insert the static data.
#List of table names for static data.
static_data_tables="result status _migrations task job job_task_map"
# Export the schema of all tables in the 'stigman' database into a SQL file,
# removing any AUTO_INCREMENT attribute values to prevent conflicts with existing data when imported
# and removing statements that trigger a mysql2 bug when changing client character set
# The '--no-data' flag means no table row data will be dumped, only the schema.
# The '--no-create-db' flag prevents the inclusion of CREATE DATABASE statements in the dump.
mysqldump -h 127.0.0.1 -P 3306 -u root -prootpw --routines --events --no-data --no-create-db stigman |
sed --expression='s/ AUTO_INCREMENT=[0-9]\+//' \
--expression='s/DEFINER=`stigman`@`%` *//' \
--expression '/SQL SECURITY DEFINER/d' \
--expression='s/;;/$/g' |
awk 'tolower($0) !~ /character_set|set names/' > 10-stigman-tables.sql
# Export only the data from specific tables listed in $static_data_tables into a separate SQL file.
# '--no-create-info' flag ensures that table creation statements are not included, just the row insertions.
mysqldump -h 127.0.0.1 -P 3306 -u root -prootpw --no-create-info stigman $static_data_tables |
awk 'tolower($0) !~ /character_set|set names/' > 20-stigman-static.sql
echo "ALTER TABLE job AUTO_INCREMENT=100;" >> 20-stigman-static.sql
echo "ALTER TABLE job_task_map AUTO_INCREMENT=1000;" >> 20-stigman-static.sql
================================================
FILE: api/source/service/utils.js
================================================
const mysql = require('mysql2/promise')
const config = require('../utils/config')
const logger = require('../utils/logger')
const retry = require('async-retry')
const Umzug = require('umzug')
const path = require('path')
const fs = require("fs")
const semverGte = require('semver/functions/gte')
const semverCoerce = require('semver/functions/coerce')
const Importer = require('./migrations/lib/mysql-import.js')
const state = require('../utils/state')
const minMySqlVersion = '8.0.24'
let _this = this
let initAttempt = 0
let NetKeepAlive
if (!process.pkg) {
// pkg does not support the dynamic loading used by net-keepalive.
// Therefore, support for TCP_USER_TIMEOUT is excluded from binaries built with pkg.
NetKeepAlive = require('net-keepalive')
}
const PoolMonitor = require('../utils/PoolMonitor.js')
/**
* Performs a preflight connection check by getting and releasing a connection from the pool.
*/
async function preflightConnection () {
logger.writeDebug('mysql', 'preflight', { attempt: ++initAttempt })
const connection = await _this.pool.getConnection()
await connection.release()
}
/**
* Retrieves the MySQL version from the database.
* @returns {Promise} The MySQL version.
*/
async function getMySqlVersion () {
let [result] = await _this.pool.query('SELECT VERSION() as version')
return result[0].version
}
/**
* Retrieves the count of tables in the database.
* @returns {Promise} The number of tables.
*/
async function getTableCount () {
let [tables] = await _this.pool.query('SHOW TABLES')
return tables.length
}
/**
* Checks if the provided MySQL version is acceptable.
* @param {string} version - The MySQL version to check.
* @returns {boolean} True if the version is acceptable, false otherwise.
*/
function isOkVersion(version) {
return semverGte(semverCoerce(version), semverCoerce(minMySqlVersion))
}
/**
* Performs database migrations using Umzug.
* @returns {Promise} The list of executed migrations.
*/
async function doMigrations() {
// Perform migrations
const umzug = new Umzug({
migrations: {
path: path.join(__dirname, './migrations'),
params: [_this.pool]
},
storage: path.join(__dirname, './migrations/lib/umzug-mysql-storage'),
storageOptions: {
pool: _this.pool
}
})
if (config.database.revert) {
const migrations = await umzug.executed()
if (migrations.length) {
logger.writeInfo('mysql', 'migration', { message: 'MySQL schema will revert the last migration and terminate' })
await umzug.down()
} else {
logger.writeInfo('mysql', 'migration', { message: 'MySQL schema has no migrations to revert' })
}
logger.writeInfo('mysql', 'migration', { message: 'MySQL revert migration has completed' })
state.setState('stop')
}
const migrations = await umzug.pending()
if (migrations.length > 0) {
logger.writeInfo('mysql', 'migration', { message: `MySQL schema requires ${migrations.length} update${migrations.length > 1 ? 's' : ''}` })
await umzug.up()
logger.writeInfo('mysql', 'migration', { message: `All migrations performed successfully` })
}
else {
logger.writeInfo('mysql', 'migration', { message: `MySQL schema is up to date` })
}
return umzug.executed()
}
/**
* Sets up the initial database schema by importing SQL files.
*/
async function setupInitialSchema(){
logger.writeInfo('mysql', 'schema', { message: 'setting up new schema.' })
const importer = new Importer(_this.pool)
const dir = path.join(__dirname, 'migrations', 'sql', 'current')
const files = await fs.promises.readdir(dir)
try {
for (const file of files) {
logger.writeInfo('mysql', 'schema', {status: 'running', name: file })
await importer.import(path.join(dir, file))
}
}
catch (e) {
logger.writeError('mysql', 'schema', {status: 'error', files, message: e.message })
throw new Error(`failed to setup initial schema, ${e.message}`)
}
logger.writeInfo('mysql', 'schema', { message: 'schema setup complete.' })
}
/**
* Sets up the database schema by checking the number of tables and performing migrations if necessary.
*/
async function setupSchema() {
try {
// Check the number of tables in the database
const numTables = await getTableCount()
if (numTables === 0) {
await setupInitialSchema()
}
const migrated = await doMigrations()
config.lastMigration = parseInt(migrated[migrated.length -1].file.substring(0,4))
}
catch (error) {
logger.writeError('mysql', 'initalization', { message: error.message })
throw new Error('Failed during database initialization or migration.')
}
}
/**
* Resolves a database TLS certificate path.
* Detects if the path is absolute or relative and returns the appropriate resolved path.
* Relative paths are resolved relative to the /tls directory for backward compatibility.
*
* @param {string} certPath - The certificate path from configuration
* @returns {string} The resolved absolute path
*/
function resolveDbCertPath(certPath) {
if (path.isAbsolute(certPath)) {
// Path is already absolute, use it directly
return certPath
} else {
// Path is relative, resolve it relative to the /tls directory (legacy behavior)
return path.join(__dirname, '..', 'tls', certPath)
}
}
/**
* Generates the pool configuration object based on the application configuration.
* @returns {Object} The pool configuration object.
*/
function getPoolConfig() {
const poolConfig = {
connectionLimit : config.database.maxConnections,
timezone: 'Z',
host: config.database.host,
port: config.database.port,
user: config.database.username,
database: config.database.schema,
decimalNumbers: true,
charset: 'utf8mb4_0900_ai_ci',
keepAliveInitialDelay: 10000,
connectAttributes: {
program_name: 'stig-manager'
},
typeCast: function (field, next) {
if ((field.type === "BIT") && (field.length === 1)) {
let bytes = field.buffer() || [0]
return( bytes[ 0 ] === 1 )
}
return next()
}
}
if (config.database.password) {
poolConfig.password = config.database.password
}
if (config.database.tls.ca_file || config.database.tls.cert_file || config.database.tls.key_file) {
const sslConfig = {}
if (config.database.tls.ca_file) {
sslConfig.ca = fs.readFileSync(resolveDbCertPath(config.database.tls.ca_file))
}
if (config.database.tls.cert_file) {
sslConfig.cert = fs.readFileSync(resolveDbCertPath(config.database.tls.cert_file))
}
if (config.database.tls.key_file) {
sslConfig.key = fs.readFileSync(resolveDbCertPath(config.database.tls.key_file))
}
poolConfig.ssl = sslConfig
}
return poolConfig
}
/**
* Patches the pool to emit a 'remove' event when a connection is removed.
* @param {Object} promisePool - The mysql2 PromisePool object.
*/
function patchRemoveConnection(promisePool) {
const originalRemoveConnection = promisePool.pool._removeConnection
promisePool.pool._removeConnection = function (connection) {
originalRemoveConnection.call(promisePool.pool, connection)
promisePool.emit('remove', connection)
}
}
/**
* Retry function for the pool monitor to attempt to restore pool connections.
*/
async function poolMonitorRetryFn () {
try {
logger.writeInfo('mysql', 'restore', { message: 'attempting to restore pool connection' })
await preflightConnection()
logger.writeInfo('mysql', 'restore', { message: `connection suceeded` })
const version = await getMySqlVersion()
if (!isOkVersion(version)) {
const connection = await _this.pool.getConnection()
connection.connection.destroy()
throw new Error(`MySQL release ${version} is too old. Update to release ${minMySqlVersion} or later.`)
}
else {
await setupSchema()
logger.writeInfo('mysql', 'restore', { success: true, version, message: 'pool connection restored' })
}
}
catch (e) {
logger.writeError('mysql', 'restore', { success: false, message: e.message })
throw e
}
}
/**
* Retry function for bootstrapping the database connection.
* @param {Function} fn - The function to retry.
* @returns {Promise} The result of the retried function.
*/
async function bootstrapRetryFn (fn) {
return retry(fn, {
retries: config.settings.dependencyRetries,
factor: 1,
minTimeout: 5 * 1000,
maxTimeout: 5 * 1000,
onRetry: (error) => {
logger.writeError('mysql', 'preflight', { success: false, message: error.message })
}
})
}
/**
* Formats a Node.js socket object into a string representation.
*
* @param {net.Socket} socket - The Node.js socket object.
* @returns {string|undefined} A string representation of the socket's local and remote addresses and ports, or undefined if the socket is not connected.
*/
function formatSocket(socket) {
return socket.localAddress ? `${socket.localAddress}:${socket.localPort} -> ${socket.remoteAddress}:${socket.remotePort}` : undefined
}
/**
* Attaches event handlers to the pool for connection and removal events.
* @param {Object} pool - The mysql2 PromisePool object.
*/
function attachPoolEventHandlers(pool) {
pool.on('connection', function (connection) {
const socket = formatSocket(connection.stream)
connection.on('error', function (error) {
logger.writeError('mysql', 'connectionEvent', { event: 'error', socket, message: error.message })
})
logger.writeInfo('mysql', 'poolEvent', { event: 'connection', socket })
NetKeepAlive?.setUserTimeout(connection.stream, 20000)
connection.query('SET SESSION group_concat_max_len=10000000')
})
pool.on('remove', function (connection) {
const socket = formatSocket(connection.stream)
logger.writeInfo('mysql', 'poolEvent', { event: 'remove', socket, remaining: pool.pool._allConnections.toArray().length, authorized: connection.authorized })
})
}
module.exports.initializeDatabase = async function () {
try {
// Create the connection pool
const poolConfig = getPoolConfig()
logger.writeDebug('mysql', 'poolConfig', { ...poolConfig })
_this.pool = mysql.createPool(poolConfig)
attachPoolEventHandlers(_this.pool)
new PoolMonitor({pool: _this.pool, state, retryInterval: 20000, retryFn: poolMonitorRetryFn})
state.dbPool = _this.pool
// Try to create a pool connection, will retry every 5 seconds
await bootstrapRetryFn(preflightConnection)
// Check the MySQL version
const version = await getMySqlVersion()
if (!isOkVersion(version)) {
logger.writeError('mysql', 'preflight', { success: false, message: `MySQL release ${version} is too old. Update to release ${minMySqlVersion} or later.` })
throw new Error('MySQL release is too old.')
}
else {
logger.writeInfo('mysql', 'preflight', {success: true, version })
}
// Patch the pool to emit a 'remove' event when a connection is removed
patchRemoveConnection(_this.pool)
// Setup the schema, will scaffold if necessary and run migrations
await setupSchema()
state.setDbStatus(true)
}
catch (err) {
state.setDbStatus(false)
throw err
}
}
module.exports.parseRevisionStr = function (revisionStr) {
const ro = {}
if (revisionStr !== 'latest') {
const results = /V(\d+)R(\d+(\.\d+)?)/.exec(revisionStr)
ro.version = results[1]
ro.release = results[2]
ro.table = 'revision'
ro.table_alias = 'r'
ro.predicates = ' and r.version = ? and r.release = ? '
}
else {
ro.version = null
ro.release = null
ro.table = 'current_rev'
ro.table_alias = 'cr'
ro.predicates = ''
}
return ro
}
module.exports.selectCollectionByAssetId = async function (assetId) {
const [rows] = await _this.pool.query(`SELECT c.* from enabled_asset a left join enabled_collection c using (collectionId) where a.assetId = ?`, [assetId])
return rows[0]
}
module.exports.getGrantByAssetId = async function (assetId, grants) {
const row = await _this.selectCollectionByAssetId(assetId)
return row ? grants[row.collectionId] : null
}
module.exports.getUserAssetStigAccess = async function ({assetId, benchmarkId, grants}) {
const grant = await _this.getGrantByAssetId(assetId, grants)
if (!grant) return 'none'
const binds = [assetId, benchmarkId]
const sql = `with ${_this.cteAclEffective({grantIds: grant.grantIds})} select
coalesce(ae.access, 'rw') as access
from
stig_asset_map sa
inner join enabled_asset a on sa.assetId = a.assetId
${grant.roleId === 1 ? 'inner' : 'left'} join cteAclEffective ae using (saId)
where
sa.assetId = ? and sa.benchmarkId = ?`
const [rows] = await _this.pool.query(sql, binds)
return rows[0]?.access ?? 'none'
}
/**
* updateStatsAssetStig
* @param {PoolConnection} connection
* @param {Object} param1
* @param {string} param1.collectionId
* @param {string} param1.assetId
* @param {string} param1.benchmarkId
* @param {string[]} param1.rules
*/
module.exports.updateStatsAssetStig = async function(connection, {
collectionId,
collectionIds,
assetId,
assetIds,
assetBenchmarkIds,
benchmarkId,
benchmarkIds,
rules,
saIds }) {
if (!connection) { throw new Error ('Connection required')}
// Handle optional predicates,
let predicates = ['sa.assetId IS NOT NULL AND sa.benchmarkId IS NOT NULL']
let binds = []
let whereClause = ''
if (rules && rules.length > 0) {
predicates.push(`sa.benchmarkId IN (SELECT DISTINCT benchmarkId from rev_group_rule_map left join revision using (revId) where ruleId IN ?)`)
binds.push( [rules] )
}
if (collectionId) {
predicates.push('a.collectionId = ?')
binds.push(collectionId)
}
if (collectionIds) {
predicates.push('a.collectionId IN ?')
binds.push([collectionIds])
}
if (assetId) {
predicates.push('a.assetId = ?')
binds.push(assetId)
}
if (assetIds) {
predicates.push('a.assetId IN ?')
binds.push([assetIds])
}
if (assetBenchmarkIds) {
predicates.push(`a.assetId IN (select assetId from stig_asset_map where benchmarkId in ?)`)
binds.push([assetBenchmarkIds])
}
if (benchmarkId) {
predicates.push('sa.benchmarkId = ?')
binds.push(benchmarkId)
}
if (benchmarkIds) {
predicates.push('sa.benchmarkId IN ?')
binds.push([benchmarkIds])
}
if (saIds) {
predicates.push('sa.saId IN ?')
binds.push([saIds])
}
if (predicates.length > 0) {
whereClause = `where ${predicates.join(' and ')}`
}
const sqlUpdate = `
with source as
( select
sa.assetId,
sa.benchmarkId,
min(review.ts) as minTs,
max(review.ts) as maxTs,
max(review.touchTs) as maxTouchTs,
sum(CASE WHEN review.statusId = 0 THEN 1 ELSE 0 END) as saved,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 0 THEN 1 ELSE 0 END) as savedResultEngine,
sum(CASE WHEN review.statusId = 1 THEN 1 ELSE 0 END) as submitted,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 1 THEN 1 ELSE 0 END) as submittedResultEngine,
sum(CASE WHEN review.statusId = 2 THEN 1 ELSE 0 END) as rejected,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 2 THEN 1 ELSE 0 END) as rejectedResultEngine,
sum(CASE WHEN review.statusId = 3 THEN 1 ELSE 0 END) as accepted,
sum(CASE WHEN review.resultEngine is not null and review.statusId = 3 THEN 1 ELSE 0 END) as acceptedResultEngine,
sum(CASE WHEN review.resultId=4 and rgr.severity='high' THEN 1 ELSE 0 END) as highCount,
sum(CASE WHEN review.resultId=4 and rgr.severity='medium' THEN 1 ELSE 0 END) as mediumCount,
sum(CASE WHEN review.resultId=4 and rgr.severity='low' THEN 1 ELSE 0 END) as lowCount,
sum(CASE WHEN (review.resultId in (2,3,4)) and rgr.severity='high' THEN 1 ELSE 0 END) as assessedHighCount,
sum(CASE WHEN (review.resultId in (2,3,4)) and rgr.severity='medium' THEN 1 ELSE 0 END) as assessedMediumCount,
sum(CASE WHEN (review.resultId in (2,3,4)) and rgr.severity='low' THEN 1 ELSE 0 END) as assessedLowCount,
sum(CASE WHEN review.resultId = 1 THEN 1 ELSE 0 END) as notchecked,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 1 THEN 1 ELSE 0 END) as notcheckedResultEngine,
sum(CASE WHEN review.resultId = 2 THEN 1 ELSE 0 END) as notapplicable,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 2 THEN 1 ELSE 0 END) as notapplicableResultEngine,
sum(CASE WHEN review.resultId = 3 THEN 1 ELSE 0 END) as pass,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 3 THEN 1 ELSE 0 END) as passResultEngine,
sum(CASE WHEN review.resultId = 4 THEN 1 ELSE 0 END) as fail,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 4 THEN 1 ELSE 0 END) as failResultEngine,
sum(CASE WHEN review.resultId = 5 THEN 1 ELSE 0 END) as unknown,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 5 THEN 1 ELSE 0 END) as unknownResultEngine,
sum(CASE WHEN review.resultId = 6 THEN 1 ELSE 0 END) as error,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 6 THEN 1 ELSE 0 END) as errorResultEngine,
sum(CASE WHEN review.resultId = 7 THEN 1 ELSE 0 END) as notselected,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 7 THEN 1 ELSE 0 END) as notselectedResultEngine,
sum(CASE WHEN review.resultId = 8 THEN 1 ELSE 0 END) as informational,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 8 THEN 1 ELSE 0 END) as informationalResultEngine,
sum(CASE WHEN review.resultId = 9 THEN 1 ELSE 0 END) as fixed,
sum(CASE WHEN review.resultEngine is not null and review.resultId = 9 THEN 1 ELSE 0 END) as fixedResultEngine
from
enabled_asset a
inner join enabled_collection ec on a.collectionId = ec.collectionId
left join stig_asset_map sa using (assetId)
left join default_rev dr on (sa.benchmarkId = dr.benchmarkId and a.collectionId = dr.collectionId)
left join rev_group_rule_map rgr on dr.revId = rgr.revId
left join rule_version_check_digest rvcd on rgr.ruleId = rvcd.ruleId
left join review on (rvcd.version=review.version and rvcd.checkDigest=review.checkDigest and review.assetId=sa.assetId)
${whereClause}
group by
sa.assetId,
sa.benchmarkId
)
update stig_asset_map sam
inner join source on sam.assetId = source.assetId and source.benchmarkId = sam.benchmarkId
set sam.minTs = source.minTs,
sam.maxTs = source.maxTs,
sam.maxTouchTs = source.maxTouchTs,
sam.saved = source.saved,
sam.savedResultEngine = source.savedResultEngine,
sam.submitted = source.submitted,
sam.submittedResultEngine = source.submittedResultEngine,
sam.rejected = source.rejected,
sam.rejectedResultEngine = source.rejectedResultEngine,
sam.accepted = source.accepted,
sam.acceptedResultEngine = source.acceptedResultEngine,
sam.highCount = source.highCount,
sam.mediumCount = source.mediumCount,
sam.lowCount = source.lowCount,
sam.assessedHighCount = source.assessedHighCount,
sam.assessedMediumCount = source.assessedMediumCount,
sam.assessedLowCount = source.assessedLowCount,
sam.notchecked = source.notchecked,
sam.notcheckedResultEngine = source.notcheckedResultEngine,
sam.notapplicable = source.notapplicable,
sam.notapplicableResultEngine = source.notapplicableResultEngine,
sam.pass = source.pass,
sam.passResultEngine = source.passResultEngine,
sam.fail = source.fail,
sam.failResultEngine = source.failResultEngine,
sam.unknown = source.unknown,
sam.unknownResultEngine = source.unknownResultEngine,
sam.error = source.error,
sam.errorResultEngine = source.errorResultEngine,
sam.notselected = source.notselected,
sam.notselectedResultEngine = source.notselectedResultEngine,
sam.informational = source.informational,
sam.informationalResultEngine = source.informationalResultEngine,
sam.fixed = source.fixed,
sam.fixedResultEngine = source.fixedResultEngine
`
let stats
[stats] = await connection.query(sqlUpdate, binds)
return stats
}
module.exports.uuidToSqlString = function (uuid) {
return {
toSqlString: function () {
return `UUID_TO_BIN(${mysql.escape(uuid)},1)`
}
}
}
module.exports.makeQueryString = function ({ctes = [], hints= [], columns, joins, predicates, groupBy, orderBy, format = false}) {
if (joins instanceof Set) joins = Array.from(joins)
if (groupBy instanceof Set) groupBy = Array.from(groupBy)
const query = `${ctes.length ? 'WITH ' + ctes.join(', \n') : ''}
SELECT ${hints.length ? '/*+ ' + hints.join(' ') + '*/' : ''}
${columns.join(',\n ')}
FROM
${joins.join('\n ')}
${predicates?.statements.length ? 'WHERE\n ' + predicates.statements.join(' and\n ') : ''}
${groupBy?.length ? 'GROUP BY\n ' + groupBy.join(',\n ') : ''}
${orderBy?.length ? 'ORDER BY\n ' + orderBy.join(',\n ') : ''}
`
return format? mysql.format(query, predicates.binds) : query
}
module.exports.CONTEXT_ALL = 'all'
module.exports.CONTEXT_DEPT = 'department'
module.exports.CONTEXT_USER = 'user'
module.exports.REVIEW_RESULT_API = {
'notchecked': 1,
'notapplicable': 2,
'pass': 3,
'fail': 4,
'unknown': 5,
'error': 6,
'notselected': 7,
'informational': 8,
'fixed': 9
}
module.exports.REVIEW_ACTION_API = {
'remediate': 1,
'mitigate': 2,
'exception': 3
}
module.exports.REVIEW_STATUS_API = {
'saved': 0,
'submitted': 1,
'rejected': 2,
'accepted': 3
}
module.exports.WRITE_ACTION = {
CREATE: 0,
REPLACE: 1,
UPDATE: 2
}
module.exports.retryOnDeadlock = async function (fn, statusObj = {}) {
const retryFunction = async function (bail) {
try {
return await fn()
}
catch (e) {
if (e.code === 'ER_LOCK_DEADLOCK') {
throw(e)
}
bail(e)
}
}
statusObj.retries = 0
return await retry(retryFunction, {
retries: 15,
factor: 1,
minTimeout: 200,
maxTimeout: 200,
onRetry: () => {
++statusObj.retries
}
})
}
module.exports.retryOnDeadlock2 = async function ({ transactionFn, statusObj = {}, beforeReleaseFn, afterRollbackFn}) {
const connection = await _this.pool.getConnection()
const retryFunction = async function (bail) {
try {
await connection.query('START TRANSACTION')
const transactionReturn = await transactionFn(connection)
await connection.commit()
await connection.release()
return transactionReturn
}
catch (e) {
if (e.code === 'ER_LOCK_DEADLOCK') {
throw(e)
}
await connection.rollback()
afterRollbackFn?.(connection)
beforeReleaseFn?.(connection)
await connection.release()
bail(e)
}
}
statusObj.retries = 0
return await retry(retryFunction, {
retries: 15,
factor: 1,
minTimeout: 200,
maxTimeout: 200,
onRetry: () => {
++statusObj.retries
}
})
// return returnValue
}
exports.createAssetValidation = async function({ assets, collectionId}) {
const assetJson = JSON.stringify(assets)
const validationQuery = `
WITH cteFails AS (
SELECT
jt.positionA,
jt.positionB,
jt.positionL,
jt.name,
jt.benchmarkId,
jt.labelName,
a.name AS matchedName,
s.benchmarkId AS matchedBenchmarkId,
cl.clId AS matchedClId
FROM
JSON_TABLE(?, '$[*]'
COLUMNS (
positionA FOR ORDINALITY,
name VARCHAR(255) PATH '$.name',
NESTED PATH '$.stigs[*]'
COLUMNS (positionB FOR ORDINALITY, benchmarkId VARCHAR(255) PATH '$'),
NESTED PATH '$.labelNames[*]'
COLUMNS (positionL FOR ORDINALITY, labelName VARCHAR(255) PATH '$')
)
) AS jt
LEFT JOIN enabled_asset a
ON jt.name = a.name
AND a.collectionId = ?
LEFT JOIN stig s
ON jt.benchmarkId COLLATE utf8mb4_0900_ai_ci = s.benchmarkId COLLATE utf8mb4_0900_ai_ci
LEFT JOIN collection_label cl
ON jt.labelName = cl.name
AND cl.collectionId = ?
)
SELECT
'name exists' AS failure,
JSON_OBJECT('assetIndex', positionA, 'name', name) AS detail
FROM cteFails
WHERE name IS NOT NULL AND matchedName IS NOT NULL
UNION
SELECT
'unknown benchmarkId',
JSON_OBJECT('assetIndex', positionA, 'name', name, 'benchmarkIdIndex', positionB, 'benchmarkId', benchmarkId)
FROM cteFails
WHERE benchmarkId IS NOT NULL AND matchedBenchmarkId IS NULL AND matchedName IS NULL
UNION
SELECT
'unknown labelName',
JSON_OBJECT('assetIndex', positionA, 'name', name, 'labelIndex', positionL, 'labelName', labelName)
FROM cteFails
WHERE labelName IS NOT NULL AND matchedClId IS NULL AND matchedName IS NULL
`
const [results] = await _this.pool.query(validationQuery, [assetJson, collectionId, collectionId])
return results
}
module.exports.pruneCollectionRevMap = async function (connection) {
const sql = `delete crm from collection_rev_map crm
left join( select distinct a.collectionId, sa.benchmarkId from stig_asset_map sa left join enabled_asset a using (assetId)) maps using (collectionId, benchmarkId)
where maps.collectionId is null`
await (connection ?? _this.pool).query(sql)
}
module.exports.updateDefaultRev = async function (connection, {collectionId, collectionIds, benchmarkId}) {
const predicates = []
const binds = []
let whereClause = ''
if (collectionId) {
predicates.push(`collectionId = ?`)
binds.push(collectionId)
}
if (collectionIds) {
predicates.push(`collectionId IN ?`)
binds.push([collectionIds])
}
if (benchmarkId) {
predicates.push(`benchmarkId = ?`)
binds.push(benchmarkId)
}
if (predicates.length > 0) {
whereClause = `where ${predicates.join(' and ')}`
}
const sqlDelete = `DELETE FROM default_rev ${whereClause}`
const sqlInsert = `INSERT INTO default_rev(collectionId, benchmarkId, revId, revisionPinned) SELECT collectionId, benchmarkId, revId, revisionPinned FROM v_default_rev ${whereClause}`
await (connection ?? _this.pool).query(sqlDelete, binds)
await (connection ?? _this.pool).query(sqlInsert, binds)
}
module.exports.jsonArrayAggDistinct = function (valueStr) {
return `cast(concat('[', group_concat(distinct ${valueStr}), ']') as json)`
}
module.exports.jsonArrayAgg = function ({value, orderBy = '', distinct = false}) {
return `cast(concat('[', group_concat(${distinct ? 'distinct ' : ''}${value} ${orderBy ? `order by ${orderBy}` : ''}), ']') as json)`
}
module.exports.sqlGrantees = function ({collectionId, collectionIds, userId, username, nameMatch, includeColumnCollectionId = true, returnCte = false}) {
const predicates = {
statements: [],
binds: []
}
if (collectionId) {
predicates.statements.push('cg.collectionId = ?')
predicates.binds.push(collectionId)
}
if (collectionIds) {
predicates.statements.push('cg.collectionId IN (?)')
predicates.binds.push(collectionIds)
}
if (userId) {
predicates.statements.push('ud.userId = ?')
predicates.binds.push(userId)
}
if (username) {
let matchStr = '= ?'
if ( nameMatch && nameMatch !== 'exact') {
matchStr = 'LIKE ?'
switch (nameMatch) {
case 'startsWith':
username = `${username}%`
break
case 'endsWith':
username = `%${username}`
break
case 'contains':
username = `%${username}%`
break
}
}
predicates.statements.push(`ud.username ${matchStr}`)
predicates.binds.push(username)
}
// final query will be a UNION of sqlDirectGrants and sqlGroupGrants
const sqlDirectGrants = `select
${includeColumnCollectionId ? 'cg.collectionId,' : ''}
cast(cg.userId as char) as userId,
cg.roleId,
json_array(json_object('userId', cast(ud.userId as char),'username', ud.username)) as grantees,
json_array(cg.grantId) as grantIds
from
collection_grant cg
inner join enabled_collection c on (cg.collectionId = c.collectionId)
left join user_data ud on cg.userId = ud.userId
where
cg.userId is not null
${predicates.statements.length ? `and ${predicates.statements.join(' and ')}` : ''}`
const sqlFormattedDirectGrants = mysql.format(sqlDirectGrants, predicates.binds)
const sqlGroupGrants = `select
${includeColumnCollectionId ? 'collectionId,' : ''}
userId,
roleId,
grantees,
grantIds
from
(select
ROW_NUMBER() OVER(PARTITION BY ugu.userId, cg.collectionId ORDER BY cg.roleId desc) as rn,
${includeColumnCollectionId ? 'cg.collectionId,' : ''}
cast(ugu.userId as char) as userId,
cg.roleId,
json_arrayagg(json_object('userGroupId', cast(cg.userGroupId as char),'name', ug.name)) OVER (PARTITION BY ugu.userId, cg.collectionId, cg.roleId) as grantees,
json_arrayagg(cg.grantId) OVER (PARTITION BY ugu.userId, cg.collectionId, cg.roleId) as grantIds
from
collection_grant cg
inner join enabled_collection c on cg.collectionId = c.collectionId
left join user_group_user_map ugu on cg.userGroupId = ugu.userGroupId
left join user_group ug on ugu.userGroupId = ug.userGroupId
left join user_data ud on ugu.userId = ud.userId
left join collection_grant cgDirect on (cg.collectionId = cgDirect.collectionId and ugu.userId = cgDirect.userId)
where
cg.userGroupId is not null
and cgDirect.userId is null
${predicates.statements.length ? `and ${predicates.statements.join(' and ')}` : ''}
) dt
where
dt.rn = 1`
const sqlFormattedGroupGrants = mysql.format(sqlGroupGrants, predicates.binds)
const sqlFormatted = `${sqlFormattedDirectGrants} union ${sqlFormattedGroupGrants}`
return returnCte ? `cteGrantees as (${sqlFormatted})` : sqlFormatted
}
module.exports.cteAclEffective = function ({grantIds = [], includeColumnCollectionId = true, inClauseTable = 'cteGrantees', inClauseColumn = 'grantIds', inClauseUserId = ''}) {
const inClause = grantIds.length ? '?' : `select jt.grantId from ${inClauseTable} left join json_table (${inClauseTable}.${inClauseColumn}, '$[*]' COLUMNS (grantId INT PATH '$')) jt on true${inClauseUserId ? ` where ${inClauseTable}.userId = ${inClauseUserId}` : ''}`
const sql = `cteAclRules as (select${includeColumnCollectionId ? ' a.collectionId,' : ''}
sa.saId,
cga.access,
case when cga.benchmarkId is not null then 1 else 0 end +
case when cga.assetId is not null then 1 else 0 end +
case when cga.assetId is not null and cga.benchmarkId is not null then 1 else 0 end +
case when cga.clId is not null then 1 else 0 end as specificity
from
collection_grant_acl cga
left join collection_grant cg on cga.grantId = cg.grantId
left join collection_label_asset_map cla on cga.clId = cla.clId
left join collection_label cl on cla.clId = cl.clId
inner join stig_asset_map sa on (
case when cga.assetId is not null
then cga.assetId = sa.assetId
else true
end and
case when cga.benchmarkId is not null
then cga.benchmarkId = sa.benchmarkId
else true
end and
case when cga.clId is not null
then cla.assetId = sa.assetId
else true
end)
inner join enabled_asset a on sa.assetId = a.assetId and cg.collectionId = a.collectionId
where
cga.grantId in (${inClause})
),
cteAclRulesRanked as (
select /*+ NO_MERGE() */ ${includeColumnCollectionId ? ' collectionId,' : ''}
saId,
access,
row_number() over (partition by saId order by specificity desc, access asc) as rn
from
cteAclRules),
cteAclEffective as (select${includeColumnCollectionId ? ' collectionId,' : ''} saId, access from cteAclRulesRanked where rn = 1 and access != 'none')`
const sqlFormatted = mysql.format(sql, [grantIds])
return sqlFormatted
}
module.exports.selectInvalidUserIds = async function (userIds) {
const sql = `select jt.inUserId as userId,ud.status from
JSON_TABLE(?,'$[*]' COLUMNS( inUserId INT PATH '$')) as jt
left join user_data ud on jt.inUserId = ud.userId
where ud.userId is null or ud.status='unavailable'`
const [results] = await _this.pool.query(sql, [JSON.stringify(userIds)])
return results
}
================================================
FILE: api/source/specification/log-socket.yaml
================================================
asyncapi: 3.0.0
info:
title: Log Stream WebSocket API
version: 1.0.0
description: |
WebSocket API for streaming log messages with token-based authentication.
Provides real-time log streaming after successful JWT token authorization.
Stream Control:
- Clients must send 'stream-start' command to begin receiving log messages
- Clients can send 'stream-stop' command to stop receiving log messages
- Only authorized clients can send stream control commands
contact:
name: STIG Manager Team
license:
name: MIT
servers:
development:
host: localhost:64001
protocol: ws
description: Development log stream server
pathname: /socket/log-socket
channels:
logStream:
address: /socket/log-socket
messages:
AuthorizeRequest:
$ref: '#/components/messages/AuthorizeRequest'
AuthorizeResponse:
$ref: '#/components/messages/AuthorizeResponse'
LogMessage:
$ref: '#/components/messages/LogMessage'
ErrorMessage:
$ref: '#/components/messages/ErrorMessage'
InfoMessage:
$ref: '#/components/messages/InfoMessage'
CloseMessage:
$ref: '#/components/messages/CloseMessage'
CommandMessage:
$ref: '#/components/messages/CommandMessage'
operations:
receiveAuthorizeResponse:
action: receive
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/AuthorizeResponse'
description: Server receives authorization tokens from clients
sendAuthorizeRequest:
action: send
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/AuthorizeRequest'
description: Server sends authorization prompts or token expiration notices
sendLog:
action: send
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/LogMessage'
description: Server sends log messages to authorized clients after receiving stream-start command
sendError:
action: send
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/ErrorMessage'
description: Server sends error messages
sendInfo:
action: send
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/InfoMessage'
description: Server sends informational messages
sendClose:
action: send
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/CloseMessage'
description: Server sends close notification before terminating connection
receiveCommand:
action: receive
channel:
$ref: '#/channels/logStream'
messages:
- $ref: '#/channels/logStream/messages/CommandMessage'
description: Server receives stream control commands from authorized clients (stream-start, stream-stop)
components:
messages:
AuthorizeRequest:
name: authorize
title: Authorization Request
summary: Server requests authorization or notifies of token expiration
payload:
$ref: '#/components/schemas/AuthorizeRequestPayload'
examples:
- name: initialRequest
payload:
type: authorize
data: null
- name: tokenExpired
payload:
type: authorize
data: "token expired"
LogMessage:
name: log
title: Log Message
summary: Server sends log data to authorized clients
payload:
$ref: '#/components/schemas/LogMessagePayload'
examples:
- name: transactionLog
payload:
type: log
data:
timestamp: "2025-09-03T10:30:00Z"
level: 3
component: "rest"
type: "transaction"
message: "API request processed"
ErrorMessage:
name: error
title: Error Message
summary: Server sends error information
payload:
$ref: '#/components/schemas/ErrorMessagePayload'
examples:
- name: authError
payload:
type: error
data: "Authorization failed: missing token"
- name: unexpectedMessage
payload:
type: error
data: "Unexpected message type"
InfoMessage:
name: info
title: Info Message
summary: Server sends informational messages
payload:
$ref: '#/components/schemas/InfoMessagePayload'
examples:
- name: authSuccess
payload:
type: info
data: "Authorization successful"
CloseMessage:
name: close
title: Close Message
summary: Server notifies client before closing connection
payload:
$ref: '#/components/schemas/CloseMessagePayload'
examples:
- name: closing
payload:
type: close
data: "Closing connection"
CommandMessage:
name: command
title: Command Message
summary: Client sends stream control commands to server
description: |
Clients can send the following commands to control log streaming:
- `stream-start`: Begin receiving log messages (requires authorization). Optionally include filters to limit which logs are streamed.
- `stream-stop`: Stop receiving log messages
payload:
$ref: '#/components/schemas/CommandMessagePayload'
examples:
- name: streamStart
summary: Start log streaming
payload:
type: command
data:
command: "stream-start"
- name: streamStartWithFilter
summary: Start log streaming with filters
payload:
type: command
data:
command: "stream-start"
filter:
logLevels: [1, 2]
components: ["rest"]
- name: streamStop
summary: Stop log streaming
payload:
type: command
data:
command: "stream-stop"
AuthorizeResponse:
name: authorize
title: Authorization Response
summary: Client sends JWT token for authorization
payload:
$ref: '#/components/schemas/AuthorizeResponsePayload'
examples:
- name: tokenAuth
payload:
type: authorize
data:
token: "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
schemas:
AuthorizeRequestPayload:
type: object
properties:
type:
const: authorize
data:
type: object
description: Authorization state notice
properties:
state:
type: string
enum: ["unauthorized", "authorized"]
reason:
type: string
description: Optional reason for unauthorized state (e.g., "token expired")
required:
- state
additionalProperties: false
AuthorizeResponsePayload:
type: object
properties:
type:
const: authorize
data:
type: object
required:
- token
properties:
token:
type: string
description: JWT token for authentication
additionalProperties: false
LogMessagePayload:
type: object
properties:
type:
const: log
data:
type: object
description: Log entry object with timestamp, level, component, etc.
additionalProperties: true
ErrorMessagePayload:
type: object
properties:
type:
const: error
data:
type: string
description: Error description
InfoMessagePayload:
type: object
properties:
type:
const: info
data:
type: object
description: Informational message
CloseMessagePayload:
type: object
properties:
type:
const: close
data:
type: string
description: Close reason
CommandMessagePayload:
type: object
properties:
type:
const: command
data:
oneOf:
- $ref: '#/components/schemas/StreamStartCommandData'
- $ref: '#/components/schemas/StreamStopCommandData'
StreamStartCommandData:
type: object
required:
- command
properties:
command:
const: "stream-start"
description: Instructs the server to begin sending log messages to this client. Client must be authorized.
filter:
type: object
description: Optional filter criteria. Only logs matching the filter will be sent.
properties:
level:
type: array
items:
type: integer
minimum: 1
maximum: 4
description: Array of log levels to include (e.g., [1, 2] for error and warn levels)
uniqueItems: true
component:
type: array
items:
type: string
description: Array of component names to include (e.g., ["rest", "auth"])
uniqueItems: true
additionalProperties: false
additionalProperties: false
StreamStopCommandData:
type: object
required:
- command
properties:
command:
const: "stream-stop"
description: Instructs the server to stop sending log messages to this client.
additionalProperties: false
================================================
FILE: api/source/specification/stig-manager.yaml
================================================
openapi: 3.0.1
info:
title: STIG Manager API
description: An API for managing evaluations of Security Technical Implementation Guide (STIG) assessments.
contact:
name: STIG Manager OSS Project
url: https://github.com/NUWCDIVNPT/stig-manager
version: 'v1'
servers:
- url: 'http://localhost:64001/api'
paths:
/assets:
get:
tags:
- Asset
summary: Return a list of Assets accessible to the requester
operationId: getAssets
parameters:
- $ref: '#/components/parameters/CollectionIdQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/NameQuery'
- $ref: '#/components/parameters/NameMatchQuery'
- $ref: '#/components/parameters/MetadataQuery'
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/AssetProjectionQuery'
responses:
'200':
description: AssetProjected array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Asset
summary: Create an Asset
operationId: createAsset
parameters:
- $ref: '#/components/parameters/AssetProjectionQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AssetCreateOrReplace'
responses:
'201':
description: AssetProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/AssetProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'422':
description: Unprocessable Entity
content:
application/json:
schema:
$ref: '#/components/schemas/ClientErrorBadAssetPost'
security:
- oauth:
- 'stig-manager:collection'
patch:
tags:
- Asset
summary: Delete one or more Assets
operationId: patchAssets
parameters:
- $ref: '#/components/parameters/CollectionIdQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AssetsPatchRequest'
responses:
'200':
description: AssetsPatch response
content:
application/json:
schema:
$ref: '#/components/schemas/AssetsPatchResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/AssetProjectionQuery'
get:
tags:
- Asset
summary: Return an Asset
operationId: getAsset
responses:
'200':
description: AssetProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/AssetProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Asset
summary: Merge provided properties with an Asset
operationId: updateAsset
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AssetUpdate'
responses:
'200':
description: AssetProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/AssetProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
put:
tags:
- Asset
summary: Set all properties of an Asset
operationId: replaceAsset
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AssetCreateOrReplace'
responses:
'200':
description: AssetProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/AssetProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Asset
summary: Delete an Asset
operationId: deleteAsset
responses:
'200':
description: AssetProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/AssetProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}/checklists':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- name: format
in: query
description: The format of the response.
schema:
type: string
default: ckl
enum:
- ckl
- cklb
get:
tags:
- Asset
summary: Return a multi-STIG CKL for an Asset and its mapped STIGs
operationId: getChecklistByAsset
responses:
'200':
description: Review response
content:
application/xml:
schema:
$ref: '#/components/schemas/ChecklistCkl'
application/json:
schema:
$ref: '#/components/schemas/ChecklistCklb'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}/checklists/{benchmarkId}/{revisionStr}':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/BenchmarkIdPath'
- $ref: '#/components/parameters/RevisionStrPath'
get:
tags:
- Asset
summary: Return JSON summary, or CKL(B) file, or XCCDF file for an Asset and STIG
operationId: getChecklistByAssetStig
parameters:
- name: format
in: query
description: The format of the response.
schema:
type: string
default: json
enum:
- json
- json-access
- ckl
- cklb
- xccdf
- name: projection
in: query
description: Additional fields to include in JSON checklist responses.
schema:
type: array
items:
type: string
enum:
- rule
- detail
- comment
style: form
explode: true
responses:
'200':
description: A JSON array of Checklist summary items or a CKL
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/ChecklistAssetStig'
- $ref: '#/components/schemas/ChecklistJsonAccess'
- $ref: '#/components/schemas/ChecklistCklb'
application/xml:
schema:
oneOf:
- $ref: '#/components/schemas/ChecklistCkl'
- $ref: '#/components/schemas/ChecklistXccdf'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}/metadata':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
get:
tags:
- Asset
summary: Return the metadata for Asset
operationId: getAssetMetadata
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Asset
summary: Merge the provided object to a Assetmetadata
operationId: patchAssetMetadata
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
put:
tags:
- Asset
summary: Set a Asset metadata to the provided object
operationId: putAssetMetadata
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}/metadata/keys':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
get:
tags:
- Asset
summary: Return the keys of the provided Asset's metadata
operationId: getAssetMetadataKeys
responses:
'200':
description: MetadataKeys response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetadataKey'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/assets/{assetId}/metadata/keys/{key}':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/MetadataKeyPath'
get:
tags:
- Asset
summary: Return the value of the provided Asset metadata key
operationId: getAssetMetadataValue
responses:
'200':
description: MetadataValue response
content:
application/json:
schema:
$ref: '#/components/schemas/MetadataValue'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Asset
summary: Set the value of the provided Asset metadata key to the provided string
operationId: putAssetMetadataValue
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/MetadataValue'
responses:
'204':
description: Empty to avoid large response after putting key with large value
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Asset
summary: Remove the provided Asset metadata key
operationId: deleteAssetMetadataKey
responses:
'204':
description: Empty to avoid large response after deleting key with large value
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}/stigs':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
get:
tags:
- Asset
summary: Return an Asset's STIG assignments
operationId: getStigsByAsset
responses:
'200':
description: STIG array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetStigResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
# put:
# tags:
# - Asset
# summary: UNIMPLEMENTED Set all the STIG assignments of an Asset
# operationId: attachStigsToAsset
# requestBody:
# required: true
# content:
# application/json:
# schema:
# type: array
# minItems: 1
# items:
# type: string
# responses:
# '200':
# description: Asset response
# content:
# application/json:
# schema:
# $ref: '#/components/schemas/Asset'
# default:
# description: unexpected error
# content:
# application/json:
# schema:
# $ref: '#/components/schemas/Error'
# security:
# - oauth:
# - 'stig-manager:collection'
delete:
tags:
- Asset
summary: Delete all STIG assignments to an Asset
operationId: removeStigsFromAsset
responses:
'200':
description: STIG array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/STIG'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/assets/{assetId}/stigs/{benchmarkId}':
parameters:
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/BenchmarkIdPath'
put:
tags:
- Asset
summary: Assign a STIG to an Asset
operationId: attachStigToAsset
responses:
'200':
description: STIG array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetStigResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Asset
summary: Delete a STIG assignment to an Asset
operationId: removeStigFromAsset
responses:
'200':
description: STIG array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetStigResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
/collections:
parameters:
- $ref: '#/components/parameters/ElevateQuery'
get:
tags:
- Collection
summary: Return a list of Collections accessible to the requester
description: ''
operationId: getCollections
parameters:
- $ref: '#/components/parameters/NameQuery'
- $ref: '#/components/parameters/NameMatchQuery'
- $ref: '#/components/parameters/MetadataQuery'
- $ref: '#/components/parameters/CollectionsProjectionQuery'
responses:
'200':
description: CollectionsProjected response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/CollectionsProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Collection
summary: Create a Collection
description: |
The `settings` property is optional and can be partially provided.
- If `settings` is not provided, the Collection will be created with the default settings.
The default settings are:
```
{
fields: {
detail: {
enabled: 'always',
required: 'always'
},
comment: {
enabled: 'findings',
required: 'findings'
}
},
status: {
canAccept: true,
resetCriteria: 'result',
minAcceptGrant: 3
},
history: {
maxReviews: 5
}
importOptions: {
autoStatus: 'saved',
unreviewed: 'commented',
unreviewedCommented: 'informational',
emptyDetail: 'replace',
emptyComment: 'ignore',
updateAssetProps: false,
allowCustom: true
}
```
operationId: createCollection
parameters:
- $ref: '#/components/parameters/CollectionProjectionQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionCreateOrReplace'
responses:
'201':
description: CollectionProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionProjected'
'400':
description: Client Error
content:
application/json:
schema:
$ref: '#/components/schemas/ClientErrorDuplicateCollection'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}':
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/CollectionProjectionQuery'
get:
tags:
- Collection
summary: Return a Collection
description: ''
operationId: getCollection
responses:
'200':
description: CollectionProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionProjected'
'204':
description: No Content
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Collection
summary: Merge provided properties with a Collection
operationId: updateCollection
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionUpdate'
responses:
'200':
description: CollectionProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
put:
tags:
- Collection
summary: Set all properties of a Collection
description: |
See the description of path `POST /collections` for notes about the `settings` property
operationId: replaceCollection
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionCreateOrReplace'
responses:
'200':
description: CollectionProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Collection
summary: Delete a Collection
operationId: deleteCollection
responses:
'200':
description: CollectionProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/archive/ckl':
post:
tags:
- Collection
summary: Return a ZIP archive containing CKL files for the supplied Assets and STIGs
operationId: postCklArchiveByCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/CklModeQuery'
requestBody:
required: true
description: An array of '#/components/schemas/AssetStigSelection'.
content:
application/json:
schema:
type: array
minItems: 1
uniqueItems: true
items:
$ref: '#/components/schemas/AssetStigSelection'
responses:
'200':
description: ZIP file stream
content:
application/zip:
schema:
type: string
format: binary
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/archive/cklb':
post:
tags:
- Collection
summary: Return a ZIP archive containing CKLB files for the supplied Assets and STIGs
operationId: postCklbArchiveByCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/CklModeQuery'
requestBody:
required: true
description: An array of '#/components/schemas/AssetStigSelection'.
content:
application/json:
schema:
type: array
minItems: 1
uniqueItems: true
items:
$ref: '#/components/schemas/AssetStigSelection'
responses:
'200':
description: ZIP file stream
content:
application/zip:
schema:
type: string
format: binary
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/assets':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
post:
tags:
- Asset
- Collection
summary: Create Multiple Assets
operationId: createAssets
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetProjectionQuery'
- $ref: '#/components/parameters/DryRunQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AssetCreateBatch'
responses:
'200':
description: Dry Run Failure
content:
application/json:
schema:
$ref: '#/components/schemas/ClientErrorBadAssetPost'
'201':
description: Array of AssetProjected responses
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetProjected'
'204':
description: Dry run successful. Validation passed, but no data was persisted.
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/archive/xccdf':
post:
tags:
- Collection
summary: Return a ZIP archive containing XCCDF results for the supplied Assets and STIGs
operationId: postXccdfArchiveByCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
requestBody:
required: true
description: An array of '#/components/schemas/AssetStigSelection'.
content:
application/json:
schema:
type: array
minItems: 1
items:
$ref: '#/components/schemas/AssetStigSelection'
responses:
'200':
description: ZIP file stream
content:
application/zip:
schema:
type: string
format: binary
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/checklists/{benchmarkId}/{revisionStr}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdPath'
- $ref: '#/components/parameters/RevisionStrPath'
get:
tags:
- Collection
summary: Return the Checklist for the supplied Collection and STIG
operationId: getChecklistByCollectionStig
responses:
'200':
description: ChecklistCollectionStig response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ChecklistCollectionStig'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/clone':
post:
tags:
- Collection
summary: Clone an existing Collection to a new Collection
description: |
Cloning large Collections can take several minutes! Users may see a performance impact when accessing the source Collection during this time. Making changes to the source Collection while it is being cloned may lead to inconsistent results in the cloned Collection.Before proceeding, it is recommended you warn Users that they refrain from modifying components of the source Collection while the cloning process is underway.
operationId: cloneCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/CollectionProjectionQuery'
requestBody:
required: true
description: CollectionClone request body
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionCloneRequest'
responses:
'200':
description: See the description for '#/components/schemas/CollectionCloneResponse'
content:
application/x-ndjson:
schema:
$ref: '#/components/schemas/CollectionCloneResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/export-to/{dstCollectionId}':
post:
tags:
- Collection
summary: Export reviews from a source Collection to a destination Collection
description: |
Exports reviews (result, detail and comment) from a `srcCollection` to a `dstCollection`, creating Assets in `dstCollection` if they do not exist. The `status` property of existing reviews in `dstCollection` are reset, if necessary, in accordance with the Collection settings.
operationId: exportToCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/DstCollectionIdPath'
requestBody:
required: true
description: An array of '#/components/schemas/AssetStigSelection'. The number of array items must conform to the minItems/maxItems properties
content:
application/json:
schema:
type: array
minItems: 1
maxItems: 100
uniqueItems: true
items:
$ref: '#/components/schemas/AssetStigSelection'
responses:
'200':
description: See the description for '#/components/schemas/CollectionExportToResponse'
content:
application/x-ndjson:
schema:
$ref: '#/components/schemas/CollectionExportToResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/findings':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/FindingAggregatorQuery'
- name: acceptedOnly
in: query
schema:
type: boolean
default: false
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/AssetIdQuery'
- $ref: '#/components/parameters/FindingProjectionQuery'
get:
tags:
- Collection
summary: Return the Findings for the specified Collection
operationId: getFindingsByCollection
responses:
'200':
description: CollectionFinding response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/FindingProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/grants':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/ElevateQuery'
get:
tags:
- Collection
summary: Return all collection grants
operationId: getGrantsByCollection
responses:
'200':
description: Collection Grant array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Grant'
'403':
$ref: '#/components/responses/Forbidden'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Collection
summary: Add Grants to a Collection
operationId: postGrantsByCollection
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/GrantPost'
responses:
'201':
description: Collection grant array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Grant'
'403':
$ref: '#/components/responses/Forbidden'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/grants/{grantId}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/GrantIdPath'
- $ref: '#/components/parameters/ElevateQuery'
get:
tags:
- Collection
summary: Return a collection grant by grantId
operationId: getGrantByCollectionGrant
responses:
'200':
description: Collection StigAssetBasic array response
content:
application/json:
schema:
$ref: '#/components/schemas/Grant'
'403':
$ref: '#/components/responses/Forbidden'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Collection
summary: Replace the properties of a Collection Grant by grantId.
operationId: putGrantByCollectionGrant
requestBody:
required: true
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/UserGrant'
- $ref: '#/components/schemas/UserGroupGrant'
responses:
'200':
description: Collection grant array response
content:
application/json:
schema:
$ref: '#/components/schemas/Grant'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Collection
operationId: deleteGrantByCollectionGrant
responses:
'200':
description: UserGrantEffective response
content:
application/json:
schema:
$ref: '#/components/schemas/Grant'
'403':
$ref: '#/components/responses/Forbidden'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/grants/{grantId}/acl':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/GrantIdPath'
get:
tags:
- Collection
summary: Return the Access Control List for the specified Collection Grant.
operationId: getAclRulesByCollectionGrant
responses:
'200':
description: Collection AclRuleAssetBasic array response
content:
application/json:
schema:
$ref: '#/components/schemas/AclForGrant'
'403':
$ref: '#/components/responses/Forbidden'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Collection
summary: Set the Access Control List for the specified Collection Grant.
operationId: putAclRulesByCollectionGrant
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AclRulePut'
responses:
'200':
description: AclRuleAssetBasic array response
content:
application/json:
schema:
$ref: '#/components/schemas/AclForGrant'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/reviews':
get:
tags:
- Review
summary: Return a list of Reviews accessible to the requester
description: ''
operationId: getReviewsByCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/ReviewRulesQuery'
- $ref: '#/components/parameters/ReviewResultQuery'
- $ref: '#/components/parameters/ReviewStatusQuery'
- $ref: '#/components/parameters/RuleIdQuery'
- $ref: '#/components/parameters/GroupIdQuery'
- $ref: '#/components/parameters/CciQuery'
- $ref: '#/components/parameters/UserIdQuery'
- $ref: '#/components/parameters/AssetIdQuery'
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/MetadataQuery'
- $ref: '#/components/parameters/ReviewsProjectionQuery'
responses:
'200':
description: Review response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ReviewRead'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Review
summary: Insert, update, or merge a complete or partial Review to multiple Assets and Rules
description: |
Applies a complete or partial Review to multiple target Asset/Rule pairs. Depending on the Review properties supplied, new Reviews may be created, existing Reviews may be updated, or both operations may occur (similar to an SQL merge).
## Caution
**It is possible to send a request which will place the database under considerable load and take many seconds (or minutes) to complete. To determine if a request affects a large set of Reviews, clients are strongly encouraged to send a "preflight" request with the `dryRun` option enabled.**
## Request Validation
The overall request is validated as follows:
- conformance with the OAS schema for `ReviewBatch`
- the requesting user has been granted access to the {collectionId}
## Request body
**source** *(required)*
The Review source is applied to the product of `assets` x `rules` (see below). It MUST contain at least one of the properties `result`, `detail`, `comment`, `resultEngine`, `metadata` or `status`.
- Multiple properties can be specified.
- a string value for the `status` property is normalized to `{ label: , text: null }`
**assets** *(required)*
The target Assets, which are specified as either:
- an array of `assetId`
- an array of `benchmarkId` where target Assets are calculated as the list of distinct Assets assigned at least one of the given STIGs, taking into account the requesting User's collection grant.
**rules** *(required)*
The target Rules, which are specified as either:
- an array of `ruleId`
- an array of `benchmarkId` where target Rules are calculated as the list of distinct Rules from all available revisions of the given STIGs.
**action** *(optional)*
Constrains the data action to be taken. If present, the value MUST be one of `insert`, `update`, or `merge`.
- `insert`: only create new Reviews, do not update existing Reviews
- `update`: only update existing Reviews, do not create new Reviews
- `merge`: create new Reviews and update existing Reviews
If not present, the default value is:
- `merge` if the source Review includes `result`
- `update` if the source Review does not include `result`
New Reviews cannot be created when `source` does not include `result`. In that case, specifying either the `insert` or `merge` value is an error.
**updateFilters** *(optional)*
Limits the Reviews to be updated, based on an array of filtering objects. If present, updates are applied to Reviews from the product `assets` x `rules` that pass each of the filters (filters are combined with logical AND). If not present, updates are applied to each Review from the product `assets` x `rules`.
Filtering objects specify a Review `field` , a `condition`, and a `value`. See the schema definition for further details.
**dryRun** *(optional)*
If present with a `true` value, performs all processing and validation logic without actually changing any data. Useful to verify what a given request would do and to reveal any validation errors. The default value is `false`.
## Review candidates
Candidate Reviews are created by cross joining the source Review with the product of `assets` x `rules` and applying the resulting rows to existing Reviews (if any) in accordance with the Collection settings.
**For updated Reviews**
In general, an absent source Review property will retain existing values except as below.
- an absent `status` property will either retain the existing value or update the `status` value to `{ label: "saved", text: "Review change triggered status update" }`, in accordance with the Collection `settings.status.resetCriteria`.
- an absent `resultEngine` property will either retain the existing value or update the `resultEngine` value to `null`. If applying the source Review changes an existing `result`, the `resultEngine` value will be set to `null`.
**For new Reviews**
- an absent `detail` or `comment` property will set the candidate value to the empty string.
- an absent `status` property will set the candidate value to `{ label: "saved", text: null }`.
- an absent `resultEngine` property will set the candidate value to `null`.
- an absent `metadata` property will set the candidate value to `{}`
## Candidate validation
Each candidate Review is permitted or rejected as follows:
- If the requesting user's collection grant is `restricted` AND the `ruleId` is not included in any version of any `benchmarkId` for which the requesting user been granted access, then **reject** the Review.
- If `status.label` has value `saved`, then permit the Review.
- If the Review would not be submittable according to the Collection settings, then **reject** the Review
- If the value of `status.label` is `submitted`, then **permit** the Review.
- If the value of `status.label` is `accepted` or `rejected` AND the Collection settings allow Reviews to be Accepted or Rejected, then **permit** the Review.
- If `status.label` has value `accepted` or `rejected` AND the Collection settings prohibit Reviews from being Accepted or Rejected, then **reject** the Review.
operationId: postReviewBatch
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewBatch'
responses:
'200':
description: ReviewBatchResponse response
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/ReviewBatchResponse'
- $ref: '#/components/schemas/ReviewBatchResponseDryRun'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/reviews/{assetId}':
get:
tags:
- Review
summary: Return a list of Reviews for an Asset
operationId: getReviewsByAsset
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/ReviewRulesQuery'
- $ref: '#/components/parameters/ReviewResultQuery'
- $ref: '#/components/parameters/ReviewStatusQuery'
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/MetadataQuery'
- $ref: '#/components/parameters/ReviewsProjectionQuery'
responses:
'200':
description: ReviewAssetProjected response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ReviewAsset'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Review
summary: Post one or more Reviews
description: |
The request body is an array that can contain both new and updated Reviews. All Reviews MUST contain the properties `ruleId`, `result`, `detail`, and `comment`. The overall request is validated as follows:
- conformance with the OAS schema for `ReviewAssetPost`
- the requesting user has been granted access to the {collectionId}
**For all Reviews**
- a string value for the `status` property will set the stored value to `{ label: , text: null }`
- an absent `resultEngine` property will set the stored value to `null`
**For updated Reviews**
- a `null` value for either `detail` or `comment` will retain the existing value.
- an absent `status` property will either retain the existing value or update the `status` value to `{ label: "saved", text: "Review change triggered status update" }`, in accordance with the Collection `settings.status.resetCriteria`.
**For new Reviews**
- a `null` value for either `detail` or `comment` will set the stored value to the empty string.
- an absent `status` property will set the stored value to `{ label: "saved", text: null }`.
**Each new or updated Review is permitted or rejected as follows:**
- If the requesting user's collection grant is `restricted` AND the `ruleId` is not included in any version of any `benchmarkId` for which the requesting user been granted access, then **reject** the Review
- If the optional property `status` is absent or `status.label` has value `saved`, then permit the Review
- If the new or updated Review would not be submittable according to the Collection settings, then **reject** the Review
- If the value of `status.label` is `submitted`, then **permit** the Review.
- If the value of `status.label` is `accepted` or `rejected` AND the Collection settings allow Reviews to be Accepted or Rejected, then **permit** the Review.
- If `status.label` has value `accepted` or `rejected` AND the Collection settings prohibit Reviews from being Accepted or Rejected, then **reject** the Review.
operationId: postReviewsByAsset
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdPath'
requestBody:
content:
application/json:
schema:
type: array
minItems: 1
items:
$ref: '#/components/schemas/ReviewAssetPost'
responses:
'200':
description: ReviewPostResponse response
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewPostResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/reviews/{assetId}/{ruleId}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/RuleIdPath'
- $ref: '#/components/parameters/ReviewProjectionQuery'
get:
tags:
- Review
summary: Return the Review for an Asset and Rule
operationId: getReviewByAssetRule
responses:
'200':
description: ReviewAssetRuleRead response
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewAssetRuleRead'
'204':
description: The requested resource has no content.
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Review
summary: Merge the provided properties with an existing Review
description: |
The request MUST target an existing Review and the request body MUST contain one or more Review properties. The overall request is validated as follows:
- the request body conforms with the OAS schema for `ReviewAssetRulePatch`
- a request body that includes `resultEngine` must also include `result`
- the requesting user has been granted access to the {collectionId}
- a Review already exists for the {assetId} and {ruleId}
A string value for the `status` property will set the stored value to `{ label: , text: null }`.
If the request includes a `result`, then the `resultEngine` value will be set to `null` unless the request includes an explicit `resultEngine` value.
An absent `status` property may still lead to the `status` value being updated to `{ label: "saved", text: "Review change triggered status update" }`, in accordance with the Collection `settings.status.resetCriteria`.
Unlike the corresponding PUT endpoint, the `detail` and `comment` properties do not support `null` as a value.
The request is permitted or rejected as follows:
- If the requesting user's collection grant is `restricted` AND the `assetId` is not included in any user grant, then **reject** the Review
- If the requesting user's collection grant is `restricted` AND the `ruleId` is not included in any version of any `benchmarkId` for which the user been granted access, then **reject** the Review
- If the new or updated Review would not be submittable according to the Collection settings, then **reject** the Review
- If the value of `status.label` is `submitted`, then **permit** the Review.
- If the value of `status.label` is `accepted` or `rejected` AND the Collection settings allow Reviews to be Accepted or Rejected, then **permit** the Review.
- If `status.label` has value `accepted` or `rejected` AND the Collection settings prohibit Reviews from being Accepted or Rejected, then **reject** the Review.
operationId: patchReviewByAssetRule
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewAssetRulePatch'
responses:
'200':
description: ReviewProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewAssetRuleRead'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
put:
tags:
- Review
summary: Set all properties of a Review
description: |
The request can target either a new or an existing Review. The request body MUST contain the Review properties `result`, `detail`, and `comment`. The overall request is validated as follows:
- conformance with the OAS schema for `ReviewAssetRulePut`
- the requesting user has been granted access to the {collectionId}
**For all Reviews**
- a string value for the `status` property will set the stored value to `{ label: , text: null }`
- an absent `resultEngine` property will set the stored value to `resultEngine: null`
**For updated Reviews**
- a `null` value for either `detail` or `comment` will retain the existing value.
- an absent `status` property will either retain or update the `status` value to `{ label: "saved", text: "Review change triggered status update" }`, in accordance with the Collection `settings.status.resetCriteria`.
**For new Reviews**
- a `null` value for either `detail` or `comment` will set the stored value to the empty string.
- an absent `status` property will set the stored value to `{ label: "saved", text: null }`.
The request is permitted or rejected as follows:
- If the requesting user's collection grant is `restricted` AND the `assetId` is not included in any user grant, then **reject** the Review
- If the requesting user's collection grant is `restricted` AND the `ruleId` is not included in any version of any `benchmarkId` for which the user been granted access, then **reject** the Review
- If the new or updated Review would not be submittable according to the Collection settings, then **reject** the Review
- If the value of `status.label` is `submitted`, then **permit** the Review.
- If the value of `status.label` is `accepted` or `rejected` AND the Collection settings allow Reviews to be Accepted or Rejected, then **permit** the Review.
- If `status.label` has value `accepted` or `rejected` AND the Collection settings prohibit Reviews from being Accepted or Rejected, then **reject** the Review.
operationId: putReviewByAssetRule
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewAssetRulePut'
responses:
'200':
description: ReviewProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewAssetRuleRead'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Review
summary: Delete a Review
operationId: deleteReviewByAssetRule
# parameters:
responses:
'200':
description: ReviewProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewAssetRuleRead'
'204':
description: No Content
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/reviews/{assetId}/{ruleId}/metadata':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/RuleIdPath'
get:
tags:
- Review
summary: Return the metadata for Review
operationId: getReviewMetadata
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Review
summary: Merge the provided object to a Review metadata
operationId: patchReviewMetadata
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
put:
tags:
- Review
summary: Set a Review metadata to the provided object
operationId: putReviewMetadata
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/reviews/{assetId}/{ruleId}/metadata/keys':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/RuleIdPath'
get:
tags:
- Review
summary: Return the keys of the provided Review's metadata
operationId: getReviewMetadataKeys
responses:
'200':
description: MetadataKeys response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetadataKey'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/reviews/{assetId}/{ruleId}/metadata/keys/{key}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdPath'
- $ref: '#/components/parameters/RuleIdPath'
- $ref: '#/components/parameters/MetadataKeyPath'
get:
tags:
- Review
summary: Return the value of the provided Review metadata key
operationId: getReviewMetadataValue
responses:
'200':
description: MetadataValue response
content:
application/json:
schema:
$ref: '#/components/schemas/MetadataValue'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Review
summary: Set the value of the provided Review metadata key to the provided string
operationId: putReviewMetadataValue
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/MetadataValue'
responses:
'204':
description: Empty to avoid large response after putting key with large value
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Review
summary: Remove the provided Review metadata key
operationId: deleteReviewMetadataKey
responses:
'204':
description: Empty to avoid large response after deleting key with large value
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/labels':
get:
tags:
- Collection
summary: Return labels of the specified Collection
operationId: getCollectionLabels
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
responses:
200:
description: Labels response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Label'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Collection
summary: Create a label in the specified Collection
operationId: createCollectionLabel
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/LabelCreate'
responses:
201:
description: Label response
content:
application/json:
schema:
$ref: '#/components/schemas/Label'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/labels/batch':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
post:
tags:
- Collection
summary: Create multiple labels in the specified Collection
operationId: createCollectionLabels
requestBody:
required: true
content:
application/json:
schema:
type: array
minItems: 1
items:
$ref: '#/components/schemas/LabelCreate'
responses:
201:
description: Labels response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Label'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/labels/{labelId}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/LabelIdPath'
get:
tags:
- Collection
summary: Return the specified Label of the specified Collection
operationId: getCollectionLabelById
responses:
200:
description: Labels response
content:
application/json:
schema:
$ref: '#/components/schemas/Label'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Collection
summary: Update an existing Label
operationId: patchCollectionLabelById
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/LabelUpdate'
responses:
'200':
description: Label response
content:
application/json:
schema:
$ref: '#/components/schemas/Label'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Collection
summary: Delete a Label
operationId: deleteCollectionLabelById
responses:
'204':
description: No Content
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/labels/{labelId}/assets':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/LabelIdPath'
get:
tags:
- Collection
- Asset
summary: Return the Assets mapped to the Label
operationId: getAssetsByCollectionLabelId
responses:
'200':
description: Asset response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetBasic'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Collection
- Asset
summary: Replace the Label's Asset mappings
operationId: putAssetsByCollectionLabelId
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/String255'
responses:
'200':
description: The Label's Asset mappings
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetBasic'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/metadata':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
get:
tags:
- Collection
summary: Return the metadata for Collection
operationId: getCollectionMetadata
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
patch:
tags:
- Collection
summary: Merge the provided object to a Collection metadata
operationId: patchCollectionMetadata
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
put:
tags:
- Collection
summary: Set a Collection metadata to the provided object
operationId: putCollectionMetadata
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
responses:
'200':
description: Metadata response
content:
application/json:
schema:
$ref: '#/components/schemas/Metadata'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/metadata/keys':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
get:
tags:
- Collection
summary: Return the keys of the provided Collection metadata
operationId: getCollectionMetadataKeys
responses:
'200':
description: MetadataKeys response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetadataKey'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metadata/keys/{key}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/MetadataKeyPath'
get:
tags:
- Collection
summary: Return the value of the provided Collection metadata key
operationId: getCollectionMetadataValue
responses:
'200':
description: MetadataValue response
content:
application/json:
schema:
$ref: '#/components/schemas/MetadataValue'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Collection
summary: Set the value of the provided Collection metadata key to the provided string
operationId: putCollectionMetadataValue
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/MetadataValue'
responses:
'204':
description: Empty to avoid large response after putting key with large value
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
delete:
tags:
- Collection
summary: Remove the provided Collection metadata key
operationId: deleteCollectionMetadataKey
responses:
'204':
description: Empty to avoid large response after deleting key with large value
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/metrics/detail':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return unaggregated Asset/STIG metrics for the specified Collection
operationId: getMetricsDetailByCollection
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsDetailUnagg'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/detail/asset':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return metrics for the specified Collection aggregated by Asset
operationId: getMetricsDetailByCollectionAggAsset
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsDetailAggAsset'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/detail/collection':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return aggregated metrics for the specified Collection
operationId: getMetricsDetailByCollectionAgg
responses:
'200':
description: Metrics response
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsDetailAggCollection'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/detail/label':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return metrics for the specified Collection aggregated by Label
operationId: getMetricsDetailByCollectionAggLabel
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsDetailAggLabel'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/detail/stig':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return metrics for the specified Collection aggregated by STIG
operationId: getMetricsDetailByCollectionAggStig
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsDetailAggStig'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/summary':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return unaggregated Asset/STIG metrics for the specified Collection
operationId: getMetricsSummaryByCollection
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsSummaryUnagg'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/summary/asset':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return metrics for the specified Collection aggregated by Asset
operationId: getMetricsSummaryByCollectionAggAsset
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsSummaryAggAsset'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/summary/collection':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return aggregated metrics for the specified Collection
operationId: getMetricsSummaryByCollectionAgg
responses:
'200':
description: Metrics response
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSummaryAggCollection'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/summary/label':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return metrics for the specified Collection aggregated by Label
operationId: getMetricsSummaryByCollectionAggLabel
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsSummaryAggLabel'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/metrics/summary/stig':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/AssetIdArrayQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return metrics for the specified Collection aggregated by STIG
operationId: getMetricsSummaryByCollectionAggStig
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsSummaryAggStig'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/poam':
get:
tags:
- Collection
summary: Return a POAM-like spreadsheet for the specified Collection aggregated by groupId
operationId: getPoamByCollection
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/PoamAggregatorQuery'
- name: acceptedOnly
in: query
schema:
type: boolean
default: false
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/AssetIdQuery'
- name: date
description: Value for columns Scheduled Completion Date, Milestone With Completion Dates, Milestone Changes
in: query
schema:
type: string
pattern: '^(0[1-9]|1[0-2])/(0[1-9]|[12][0-9]|3[01])/\d{4}$'
- name: office
description: Value for column Office/Org
in: query
schema:
type: string
maxLength: 255
allowReserved: true
- name: status
description: Value for column Status
in: query
schema:
type: string
maxLength: 255
allowReserved: true
- $ref: '#/components/parameters/PoamFormatQuery'
- name: mccastPackageId
description: Value for POAM MCCAST PackageId
in: query
schema:
type: string
maxLength: 255
allowReserved: true
- name: mccastAuthName
description: Value for POAM MCCAST Authorization Name
in: query
schema:
type: string
maxLength: 255
allowReserved: true
responses:
'200':
description: CollectionFinding response
content:
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet:
schema:
type: string
format: binary
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/review-history':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
get:
tags:
- Collection
summary: Return history records for the specified Collection that meet the specified criteria
operationId: getReviewHistoryByCollection
parameters:
- $ref: '#/components/parameters/StartDateQuery' # Lower bound (earliest date) of returned history entry timestamps
- $ref: '#/components/parameters/EndDateQuery' # Upper bound (latest date) of returned history entry timestamps
- $ref: '#/components/parameters/AssetIdQuery' # return review history entries for just the specified assetId, if provided.
- $ref: '#/components/parameters/RuleIdQuery' # return review history entries for just the specified RuleId, if provided.
- $ref: '#/components/parameters/ReviewStatusQuery' # return review history entries with the specified status
responses:
'200':
description: ReviewHistory response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ReviewHistoryAsset'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
delete:
tags:
- Collection
summary: Remove history records that meet specified criteria
operationId: deleteReviewHistoryByCollection
parameters:
- $ref: '#/components/parameters/RetentionDateQuery' # Review History Entries older than this date will be deleted.
- $ref: '#/components/parameters/AssetIdQuery' # Apply operation to just the specified assetId, if provided.
responses:
'200':
description: Number of history records deleted.
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewHistoryDeleted'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/review-history/stats':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
get:
tags:
- Collection
summary: Return history statistics for the specified Collection
operationId: getReviewHistoryStatsByCollection
parameters:
- $ref: '#/components/parameters/StartDateQuery' # Lower bound (earliest date) of returned history entry count
- $ref: '#/components/parameters/EndDateQuery' # Upper bound (latest date) of returned history entry count
- $ref: '#/components/parameters/AssetIdQuery' # return review history stats for just the specified assetId, if provided.
- $ref: '#/components/parameters/RuleIdQuery' # return review history stats for just the specified RuleId, if provided.
- $ref: '#/components/parameters/ReviewStatusQuery' # return review history stats with the specified status
- $ref: '#/components/parameters/ReviewHistoryStatsProjectionQuery'
responses:
'200':
description: ReviewHistoryStats response
content:
application/json:
schema:
$ref: '#/components/schemas/ReviewHistoryStats'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/stigs':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
- $ref: '#/components/parameters/CollectionStigProjectionQuery'
get:
tags:
- Collection
summary: Return the STIGs mapped in the specified Collection
operationId: getStigsByCollection
responses:
'200':
description: Collection STIGs array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/CollectionStigWithAssetCount'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/stigs/{benchmarkId}':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdPath'
- $ref: '#/components/parameters/CollectionStigProjectionQuery'
get:
tags:
- Collection
summary: Return the STIG mapped in the specified Collection
operationId: getStigByCollection
responses:
'200':
description: Collection STIGs array response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionStigWithAssetCount'
'204':
description: No content because STIG is not assigned
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
post:
tags:
- Collection
summary: Set the default Revision and/or the Asset list of a STIG in a Collection
description: |
Neither of the request body properties is required but at least one must be present. If the path parameter `{benchmarkId}` is not already mapped to at least one Asset in `{collectionId}`, then the `assetIds` property must be present.
operationId: writeStigPropsByCollectionStig
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
minProperties: 1
properties:
defaultRevisionStr:
$ref: '#/components/schemas/RevisionStr'
assetIds:
type: array
items:
$ref: '#/components/schemas/StringIntId'
responses:
'200':
description: Default Revision response
content:
application/json:
schema:
$ref: '#/components/schemas/CollectionStigWithAssetCount'
'204':
description: No content because STIG is not assigned
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/stigs/{benchmarkId}/assets':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/BenchmarkIdPath'
get:
tags:
- Asset
- Collection
summary: Get the Assets in a Collection attached to a STIG
description: ''
operationId: getAssetsByStig
parameters:
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/LabelMatchQuery'
responses:
'200':
description: AssetBasicProjected response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetBasicProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
put:
tags:
- Asset
- Collection
summary: Set the Assets mapped to a STIG
description: ''
operationId: attachAssetsToStig
requestBody:
required: true
description: A list of assetIds from the specified Collection
content:
application/json:
schema:
type: array
items:
type: string
responses:
'200':
description: AssetBasicProjected response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AssetBasicProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection'
'/collections/{collectionId}/unreviewed/assets':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/AssetIdQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/RuleSeverityQuery'
- $ref: '#/components/parameters/UnreviewedAssetsProjectionQuery'
get:
tags:
- Collection
summary: EXPERIMENTAL - Return the Assets in the specified Collection with unreviewed Rules
operationId: getUnreviewedAssetsByCollection
responses:
'200':
description: UnreviewedAsset response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/UnreviewedAsset'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/unreviewed/rules':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/RuleIdQuery'
- $ref: '#/components/parameters/LabelIdQuery'
- $ref: '#/components/parameters/LabelNameQuery'
- $ref: '#/components/parameters/BenchmarkIdQuery'
- $ref: '#/components/parameters/RuleSeverityQuery'
- $ref: '#/components/parameters/UnreviewedRulesProjectionQuery'
get:
tags:
- Collection
summary: EXPERIMENTAL - Return the Rules in the specified Collection with unreviewed Assets
operationId: getUnreviewedRulesByCollection
responses:
'200':
description: UnreviewedRules response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/UnreviewedRule'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/{collectionId}/users/{userId}/effective-acl':
parameters:
- $ref: '#/components/parameters/CollectionIdPath'
- $ref: '#/components/parameters/UserIdPath'
get:
tags:
- Collection
summary: Return a User's effective access rules for the specified Collection.
operationId: getEffectiveAclByCollectionUser
responses:
'200':
description: EffectiveAcl array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/EffectiveAcl'
'403':
$ref: '#/components/responses/Forbidden'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/meta/metrics/detail':
parameters:
- $ref: '#/components/parameters/CollectionIdArrayQuery'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return fully aggregated meta-metrics
operationId: getMetricsDetailByMeta
responses:
'200':
description: Metrics response
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsDetailAggMeta'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/meta/metrics/detail/collection':
parameters:
- $ref: '#/components/parameters/CollectionIdArrayQuery'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/RevisionIdArrayQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return meta-metrics aggregated by Collection
operationId: getMetricsDetailByMetaAggCollection
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsDetailAggCollection'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/meta/metrics/detail/stig':
parameters:
- $ref: '#/components/parameters/CollectionIdArrayQuery'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return meta-metrics aggregated by STIG
operationId: getMetricsDetailByMetaAggStig
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsDetailAggStig'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/meta/metrics/summary':
parameters:
- $ref: '#/components/parameters/CollectionIdArrayQuery'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return fully aggregated meta-metrics
operationId: getMetricsSummaryByMeta
responses:
'200':
description: Metrics response
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSummaryAggMeta'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/meta/metrics/summary/collection':
parameters:
- $ref: '#/components/parameters/CollectionIdArrayQuery'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/RevisionIdArrayQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return meta-metrics aggregated by Collection
operationId: getMetricsSummaryByMetaAggCollection
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsSummaryAggCollection'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
'/collections/meta/metrics/summary/stig':
parameters:
- $ref: '#/components/parameters/CollectionIdArrayQuery'
- $ref: '#/components/parameters/BenchmarkIdArrayQuery'
- $ref: '#/components/parameters/MetricsFormatQuery'
get:
tags:
- Metrics
summary: Return meta-metrics aggregated by STIG
operationId: getMetricsSummaryByMetaAggStig
responses:
'200':
description: Metrics response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/MetricsSummaryAggStig'
text/csv:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:collection:read'
/jobs:
get:
summary: List jobs
tags:
- Job
operationId: getJobs
parameters:
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: List of jobs
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Job'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
x-elevation-required: true
post:
summary: Create a new job
tags:
- Job
operationId: postJob
parameters:
- $ref: '#/components/parameters/ElevateQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/JobCreate'
responses:
'201':
description: Job created
content:
application/json:
schema:
$ref: '#/components/schemas/Job'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op
x-elevation-required: true
/jobs/{jobId}:
get:
summary: Get job by ID
tags:
- Job
operationId: getJob
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobIdPath'
responses:
'200':
description: Job details
content:
application/json:
schema:
$ref: '#/components/schemas/Job'
'default':
description: Job not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
x-elevation-required: true
delete:
summary: Delete job by ID
tags:
- Job
operationId: deleteJob
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobIdPath'
responses:
'204':
description: Job deleted
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op
x-elevation-required: true
patch:
summary: Update job by ID
tags:
- Job
operationId: patchJob
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobIdPath'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/JobUpdate'
responses:
'200':
description: Job updated
content:
application/json:
schema:
$ref: '#/components/schemas/Job'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op
x-elevation-required: true
/jobs/{jobId}/runs:
get:
summary: List the job runs
tags:
- Job
operationId: getRunsByJob
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobIdPath'
responses:
'200':
description: List of job runs
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/JobRun'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
x-elevation-required: true
post:
summary: Start an immediate job run
tags:
- Job
operationId: runImmediateJob
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobIdPath'
responses:
'201':
description: Job run created
content:
application/json:
schema:
$ref: '#/components/schemas/JobRunCreated'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op
x-elevation-required: true
/jobs/runs/{runId}:
get:
summary: Get a job run by ID
tags:
- Job
operationId: getRunById
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobRunIdPath'
responses:
'200':
description: Job run details
content:
application/json:
schema:
$ref: '#/components/schemas/JobRun'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
x-elevation-required: true
delete:
summary: Delete a job run by ID
tags:
- Job
operationId: deleteRunById
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobRunIdPath'
responses:
'204':
description: Job run deleted
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op
x-elevation-required: true
/jobs/runs/{runId}/output:
get:
summary: Get the output for a job run
tags:
- Job
operationId: getOutputByRun
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/JobRunIdPath'
- $ref: '#/components/parameters/RunSequenceQuery'
responses:
'200':
description: Job run output
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/JobRunOutput'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
x-elevation-required: true
/jobs/tasks:
get:
summary: List all tasks
tags:
- Job
operationId: getAllTasks
parameters:
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: List of tasks
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/JobTask'
'default':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
x-elevation-required: true
/op/appdata:
get:
tags:
- Operation
summary: Export application data
operationId: getAppData
parameters:
- $ref: '#/components/parameters/AppDataFormatQuery'
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: Exported data
content:
application/jsonl:
schema:
type: string
application/gzip:
schema:
type: string
format: binary
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
post:
tags:
- Operation
summary: Import and overwrite application data
operationId: replaceAppData
parameters:
- $ref: '#/components/parameters/ElevateQuery'
requestBody:
required: false
content:
application/gzip:
schema:
type: string
format: binary
application/x-gzip:
schema:
type: string
format: binary
application/jsonl:
schema:
type: string
format: binary
responses:
'200':
description: Import successful
content:
application/jsonl:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op
/op/appdata/tables:
get:
tags:
- Operation
summary: Get the name and data length of each table
operationId: getAppDataTables
parameters:
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: An array of table names and lengths
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AppDataTable'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- stig-manager:op:read
/op/appinfo:
get:
tags:
- Operation
summary: Return information about the application deployment
operationId: getAppInfo
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- name: includeRowCounts
in: query
description: Include exact row counts for each table (slower) or use estimated counts (faster)
schema:
type: boolean
default: false
responses:
'200':
description: AppInfo response
content:
application/json:
schema:
$ref: '#/components/schemas/AppInfo'
security:
- oauth:
- stig-manager:op:read
/op/configuration:
get:
tags:
- Operation
summary: Return API version and configuration information
operationId: getConfiguration
security: []
responses:
'200':
description: Configuration response
content:
application/json:
schema:
$ref: '#/components/schemas/ApiConfiguration'
/op/definition:
get:
tags:
- Operation
summary: Return the API definition
operationId: getDefinition
security: []
parameters:
- $ref: '#/components/parameters/JsonPathQuery'
responses:
'200':
description: Definition response
content:
application/json:
schema:
$ref: '#/components/schemas/ApiDefinition'
/op/details:
get:
tags:
- Operation
summary: "DEPRECATED: replaced by /op/appinfo"
operationId: getDetails
parameters:
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: Detail response
content:
application/json:
schema:
$ref: '#/components/schemas/Detail'
security:
- oauth:
- stig-manager:op:read
/op/state:
get:
tags:
- Operation
summary: Return information about the API state
operationId: getState
responses:
'200':
description: Detail response
content:
application/json:
schema:
$ref: '#/components/schemas/StateResponse'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/op/state/sse:
get:
tags:
- Operation
operationId: streamStateSse
summary: Stream Server-Sent Events (SSE) about changes to the current API state
description: >
Opens a one-way stream using SSE.
The response is a continuous stream of events in `text/event-stream` format.
responses:
'200':
description: Stream of events
content:
text/event-stream:
schema:
type: string
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/stigs:
get:
tags:
- STIG
summary: Return a list of available STIGs
operationId: getSTIGs
parameters:
- name: title
in: query
description: A string found anywhere in a STIG title
schema:
type: string
- $ref: '#/components/parameters/StigProjectionQuery'
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: STIG response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/STIG'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
post:
tags:
- STIG
summary: Import a STIG Benchmark
operationId: importBenchmark
parameters:
- name: clobber
in: query
description: Should existing Revision data be overwritten
schema:
type: boolean
default: false
- $ref: '#/components/parameters/ElevateQuery'
requestBody:
required: true
content:
multipart/form-data:
schema:
type: object
properties:
importFile:
type: string
format: binary
responses:
'200':
description: The added STIG
content:
application/json:
schema:
$ref: '#/components/schemas/RevisionPost'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig'
'/stigs/ccis/{cci}':
get:
tags:
- STIG
summary: Return data for the specified CCI
operationId: getCci
parameters:
- $ref: '#/components/parameters/CciProjectionQuery'
- name: cci
in: path
description: A path parameter that identifies a CCI
required: true
schema:
pattern: ^[0-9]{6}$
type: string
responses:
'200':
description: CCI response
content:
application/json:
schema:
$ref: '#/components/schemas/Cci'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/rules/{ruleId}':
get:
tags:
- STIG
summary: Return the definition and associated check and fix for the specified Rule
description: |
Note: A very small number of edge cases are known to exist where published STIGs have updated Rule Content without updating the associated RuleId. In these cases, it is possible this endpoint may return inconsistent Rule info. If you need specific Rule information for a given STIG Revision, use the `/stigs/{benchmarkId}/revisions/{revisionStr}/rules/{ruleId}` endpoint.
operationId: getRuleByRuleId
parameters:
- $ref: '#/components/parameters/RuleProjectionQuery'
- name: ruleId
in: path
description: A path parameter that identifies a Rule
required: true
schema:
type: string
responses:
'200':
description: Rule response
content:
application/json:
schema:
$ref: '#/components/schemas/RuleProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/scap-maps':
get:
tags:
- STIG
summary: Return a list of SCAP benchmarkIds mapped to Manual benchmarkIds
operationId: getScapMap
responses:
'200':
description: SCAP Map response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/SCAPMap'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/{benchmarkId}':
get:
tags:
- STIG
summary: Return properties of the specified STIG
operationId: getStigById
parameters:
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: STIG response
content:
application/json:
schema:
$ref: '#/components/schemas/STIG'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
delete:
tags:
- STIG
summary: Deletes a STIG (*** and all revisions ***)
operationId: deleteStigById
parameters:
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/ForceQuery'
responses:
'200':
description: The deleted STIG
content:
application/json:
schema:
$ref: '#/components/schemas/STIG'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig'
x-rbac:
- admin
'/stigs/{benchmarkId}/revisions':
get:
tags:
- STIG
summary: Return a list of revisions for the specified STIG
operationId: getRevisionsByBenchmarkId
parameters:
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: Revision response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Revision'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/{benchmarkId}/revisions/{revisionStr}':
get:
tags:
- STIG
summary: Return metadata for the specified revision of a STIG
operationId: getRevisionByString
parameters:
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?|latest)$
type: string
- $ref: '#/components/parameters/ElevateQuery'
responses:
'200':
description: Revision response
content:
application/json:
schema:
$ref: '#/components/schemas/Revision'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
delete:
tags:
- STIG
summary: Deletes the specified revision of a STIG
operationId: deleteRevisionByString
parameters:
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?)$
type: string
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/ForceQuery'
responses:
'200':
description: The deleted Revision
content:
application/json:
schema:
$ref: '#/components/schemas/Revision'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig'
x-rbac:
- admin
'/stigs/{benchmarkId}/revisions/{revisionStr}/ccis':
get:
tags:
- STIG
summary: Return a list of CCIs from a STIG revision
operationId: getCcisByRevision
parameters:
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?|latest)$
type: string
responses:
'200':
description: CCI response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/CciListItem'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/{benchmarkId}/revisions/{revisionStr}/groups':
get:
tags:
- STIG
summary: Return the list of groups for the specified revision of a STIG.
operationId: getGroupsByRevision
parameters:
- $ref: '#/components/parameters/GroupProjectionQuery'
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?|latest)$
type: string
responses:
'200':
description: GroupProjected response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/GroupProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/{benchmarkId}/revisions/{revisionStr}/groups/{groupId}':
get:
tags:
- STIG
summary: Return the rules, checks and fixes for a Group from a specified revision of a STIG.
description: None
operationId: getGroupByRevision
parameters:
- $ref: '#/components/parameters/GroupProjectionQuery'
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?|latest)$
type: string
- name: groupId
in: path
description: A path parameter that identifies a Group
required: true
schema:
type: string
responses:
'200':
description: Group response
content:
application/json:
schema:
$ref: '#/components/schemas/GroupProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/{benchmarkId}/revisions/{revisionStr}/rules':
get:
tags:
- STIG
summary: Return rule data for the specified revision of a STIG.
operationId: getRulesByRevision
parameters:
- $ref: '#/components/parameters/RuleProjectionQuery'
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?|latest)$
type: string
responses:
'200':
description: Rule response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/RuleProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
'/stigs/{benchmarkId}/revisions/{revisionStr}/rules/{ruleId}':
get:
tags:
- STIG
summary: Return rule data for the specified Rule in a revision of a STIG.
operationId: getRuleByRevision
parameters:
- $ref: '#/components/parameters/RuleProjectionQuery'
- name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
type: string
- name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
pattern: ^(V\d+R\d+(\.\d+)?|latest)$
type: string
- name: ruleId
in: path
description: A path parameter that identifies a Rule
required: true
schema:
type: string
responses:
'200':
description: RuleProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/RuleProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:stig:read'
/user:
parameters:
- $ref: '#/components/parameters/UserPreferenceQuery'
get:
tags:
- User
summary: Return the requester's user information
operationId: getUser
responses:
'200':
description: User response
content:
application/json:
schema:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user:read'
/user/web-preferences:
get:
tags:
- User
summary: Return the requester's web-preferences
operationId: getUserWebPreferences
responses:
'200':
description: User Web Preferences response
content:
application/json:
schema:
$ref: '#/components/schemas/WebPreferences'
security:
- oauth:
- 'stig-manager:user:read'
patch:
tags:
- User
summary: Merge the provided object to the requester's web-preferences
operationId: patchUserWebPreferences
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/WebPreferencesPatch'
responses:
'200':
description: User Web Preferences response
content:
application/json:
schema:
$ref: '#/components/schemas/WebPreferences'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
# not semantically correct but needed for backwards compatability
- 'stig-manager:user:read'
/users:
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserProjectionQuery'
get:
tags:
- User
summary: Return a list of Users accessible to the requester
operationId: getUsers
parameters:
- $ref: '#/components/parameters/UsernameQuery'
- $ref: '#/components/parameters/PrivilegeQuery'
- $ref: '#/components/parameters/UsernameMatchQuery'
- $ref: '#/components/parameters/UserStatusQuery'
responses:
'200':
description: UserProjected array response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user:read'
post:
tags:
- User
summary: Create a User
operationId: createUser
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserPost'
responses:
'201':
description: UserProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
'/users/{userId}':
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserProjectionQuery'
- $ref: '#/components/parameters/UserIdPath'
get:
tags:
- User
summary: Return a User
operationId: getUserByUserId
responses:
'200':
description: UserProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user:read'
patch:
tags:
- User
summary: Merge provided properties with a User
operationId: updateUser
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserPatch'
responses:
'200':
description: UserProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
put:
tags:
- User
summary: Set all properties of a User
operationId: replaceUser
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserPut'
responses:
'200':
description: UserProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
delete:
tags:
- User
summary: Delete a User that has never accessed the system.
operationId: deleteUser
responses:
'200':
description: UserProjected response
content:
application/json:
schema:
$ref: '#/components/schemas/UserProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
/user-groups:
post:
tags:
- User
summary: Create a User Group
operationId: createUserGroup
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserGroupProjectionQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupPostOrPut'
responses:
'201':
description: UserGroup response
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupProjected'
default:
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
get:
tags:
- User
summary: Get a list of User Groups accessible to the requester
operationId: getUserGroups
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserGroupProjectionQuery'
responses:
'200':
description: UserGroups response
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/UserGroupProjected'
security:
- oauth:
- 'stig-manager:user:read'
'/user-groups/{userGroupId}':
get:
tags:
- User
summary: Return a User Group
operationId: getUserGroup
parameters:
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserGroupIdPath'
- $ref: '#/components/parameters/UserGroupProjectionQuery'
responses:
'200':
description: UserGroup response
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupProjected'
'default':
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user:read'
patch:
tags:
- User
summary: Patch a User Group
operationId: patchUserGroup
parameters:
- $ref: '#/components/parameters/UserGroupIdPath'
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserGroupProjectionQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupPatch'
responses:
'200':
description: UserGroup response
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupProjected'
'default':
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
put:
tags:
- User
summary: Replace a User Group
operationId: putUserGroup
parameters:
- $ref: '#/components/parameters/UserGroupIdPath'
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserGroupProjectionQuery'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupPostOrPut'
responses:
'200':
description: UserGroup response
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupProjected'
'default':
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
delete:
tags:
- User
summary: Delete a User Group
operationId: deleteUserGroup
parameters:
- $ref: '#/components/parameters/UserGroupIdPath'
- $ref: '#/components/parameters/ElevateQuery'
- $ref: '#/components/parameters/UserGroupProjectionQuery'
responses:
'200':
description: UserGroup response
content:
application/json:
schema:
$ref: '#/components/schemas/UserGroupProjected'
'default':
description: unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- oauth:
- 'stig-manager:user'
components:
schemas:
RoleId:
maximum: 4
minimum: 1
type: integer
AclForGrant:
type: object
properties:
defaultAccess:
$ref: '#/components/schemas/AclRuleAccess'
acl:
type: array
items:
$ref: '#/components/schemas/AclRuleBasic'
AclRuleAccess:
type: string
enum:
- none
- r
- rw
default: rw
AclRuleAssetBasic:
additionalProperties: false
type: object
properties:
asset:
$ref: '#/components/schemas/AssetBasic'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
access:
$ref: '#/components/schemas/AclRuleAccess'
# required:
# - access
AclRuleAssetPut:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
access:
$ref: '#/components/schemas/AclRuleAccess'
required:
- access
AclRuleBasic:
anyOf:
- $ref: '#/components/schemas/AclRuleAssetBasic'
- $ref: '#/components/schemas/AclRuleLabel'
AclRuleLabel:
additionalProperties: false
type: object
properties:
label:
$ref: '#/components/schemas/LabelBasicWithColor'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
access:
$ref: '#/components/schemas/AclRuleAccess'
required:
- access
AclRuleLabelBasic:
additionalProperties: false
type: object
properties:
label:
$ref: '#/components/schemas/LabelBasic'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
access:
$ref: '#/components/schemas/AclRuleAccess'
required:
- access
AclRuleLabelPut:
additionalProperties: false
type: object
properties:
labelId:
$ref: '#/components/schemas/LabelId'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
access:
$ref: '#/components/schemas/AclRuleAccess'
required:
- access
AclRulePut:
anyOf:
- $ref: '#/components/schemas/AclRuleAssetPut'
- $ref: '#/components/schemas/AclRuleLabelPut'
AclSource:
type: object
properties:
grantee:
$ref: '#/components/schemas/Grantee'
aclRule:
anyOf:
- $ref: '#/components/schemas/AclRuleAssetBasic'
- $ref: '#/components/schemas/AclRuleLabelBasic'
ApAcronym:
$ref: '#/components/schemas/String20Nullable'
ApiClassification:
type: string
enum:
- NONE
- U
- FOUO
- CUI
- C
- S
- TS
- SCI
ApiConfiguration:
additionalProperties: false
type: object
properties:
classification:
$ref: '#/components/schemas/ApiClassification'
commit:
$ref: '#/components/schemas/CommitObject'
lastMigration:
$ref: '#/components/schemas/LastMigration'
version:
$ref: '#/components/schemas/ApiVersion'
ApiDefinition:
oneOf:
- type: object
- type: array
ApiVersion:
$ref: '#/components/schemas/Version'
AppDataFormat:
type: string
default: 'gzip'
enum:
- jsonl
- gzip
AppDataTable:
type: object
properties:
name:
$ref: '#/components/schemas/String255'
rows:
type: number
dataLength:
type: number
AppInfo:
type: object
properties:
date:
$ref: '#/components/schemas/StringDateTime'
schema:
$ref: '#/components/schemas/AppInfoSchemaVersion'
version:
$ref: '#/components/schemas/ApiVersion'
collections:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoCollection'
requests:
$ref: '#/components/schemas/AppInfoRequests'
users:
$ref: '#/components/schemas/AppInfoUsers'
groups:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoGroups'
mysql:
$ref: '#/components/schemas/AppInfoMySql'
nodejs:
$ref: '#/components/schemas/AppInfoNodejs'
required:
- date
- schema
- version
- collections
- requests
- users
- mysql
- nodejs
AppInfoGroups:
type: object
properties:
name:
$ref: '#/components/schemas/String255'
members:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
created:
$ref: '#/components/schemas/Created'
modifiedDate:
$ref: '#/components/schemas/StringDateTime'
roles:
$ref: '#/components/schemas/AppInfoGroupsRoles'
required:
- name
- members
- created
- modifiedDate
- roles
AppInfoGroupsRoles:
type: object
properties:
full:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
owner:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
manage:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
restricted:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- full
- owner
- manage
- restricted
AppInfoSchemaVersion:
type: string
pattern: "^[a-zA-Z0-9_-]+-appinfo-v[0-9]+\\.[0-9]+$"
AppInfoNodejs:
type: object
properties:
version:
$ref: '#/components/schemas/ApiVersion'
uptime:
type: number
format: double
os:
$ref: '#/components/schemas/AppInfoNodeOs'
environment:
additionalProperties:
type: string
memory:
$ref: '#/components/schemas/AppInfoNodeMemory'
cpus:
type: array
items:
$ref: '#/components/schemas/AppInfoNodeCpus'
required:
- version
- uptime
- os
- environment
- memory
- cpus
AppInfoNodeOs:
type: object
properties:
platform:
$ref: '#/components/schemas/String255'
arch:
$ref: '#/components/schemas/String255'
osMachine:
$ref: '#/components/schemas/String255'
osName:
$ref: '#/components/schemas/String255'
osRelease:
$ref: '#/components/schemas/String255'
loadAverage:
$ref: '#/components/schemas/String255'
required:
- platform
- arch
- osMachine
- osName
- osRelease
- loadAverage
AppInfoNodeCpus:
type: object
properties:
model:
$ref: '#/components/schemas/String255'
speed:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- model
- speed
AppInfoNodeMemory:
type: object
properties:
rss:
$ref: '#/components/schemas/Integer64MinimumZero'
heapTotal:
$ref: '#/components/schemas/Integer64MinimumZero'
heapUsed:
$ref: '#/components/schemas/Integer64MinimumZero'
external:
$ref: '#/components/schemas/Integer64MinimumZero'
arrayBuffers:
$ref: '#/components/schemas/Integer64MinimumZero'
maxRss:
$ref: '#/components/schemas/Integer64MinimumZero'
required:
- rss
- heapTotal
- heapUsed
- external
- arrayBuffers
- maxRss
AppInfoMySql:
type: object
properties:
version:
$ref: '#/components/schemas/ApiVersion'
tables:
$ref: '#/components/schemas/AppInfoMysqlTableStats'
variables:
$ref: '#/components/schemas/AppInfoMysqlVariables'
status:
$ref: '#/components/schemas/AppInfoMysqlStatus'
required:
- version
- tables
- variables
- status
AppInfoMysqlStatus:
type: object
properties:
# Network
Bytes_received:
$ref: '#/components/schemas/String255'
Bytes_sent:
$ref: '#/components/schemas/String255'
# Handler operations
Handler_commit:
$ref: '#/components/schemas/String255'
Handler_update:
$ref: '#/components/schemas/String255'
Handler_write:
$ref: '#/components/schemas/String255'
# Buffer pool health - critical for performance monitoring
Innodb_buffer_pool_bytes_data:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_pages_total:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_pages_free:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_pages_dirty:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_pages_flushed:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_read_requests:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_reads:
$ref: '#/components/schemas/String255'
Innodb_buffer_pool_wait_free:
$ref: '#/components/schemas/String255'
# Redo log / Checkpoint - detect checkpoint thrashing
Innodb_redo_log_current_lsn:
$ref: '#/components/schemas/String255'
Innodb_redo_log_checkpoint_lsn:
$ref: '#/components/schemas/String255'
Innodb_redo_log_flushed_to_disk_lsn:
$ref: '#/components/schemas/String255'
Innodb_log_waits:
$ref: '#/components/schemas/String255'
Innodb_log_writes:
$ref: '#/components/schemas/String255'
Innodb_os_log_fsyncs:
$ref: '#/components/schemas/String255'
# I/O operations
Innodb_data_reads:
$ref: '#/components/schemas/String255'
Innodb_data_writes:
$ref: '#/components/schemas/String255'
Innodb_data_fsyncs:
$ref: '#/components/schemas/String255'
Innodb_pages_read:
$ref: '#/components/schemas/String255'
Innodb_pages_written:
$ref: '#/components/schemas/String255'
Innodb_pages_created:
$ref: '#/components/schemas/String255'
# Row operations
Innodb_rows_read:
$ref: '#/components/schemas/String255'
Innodb_rows_updated:
$ref: '#/components/schemas/String255'
Innodb_rows_inserted:
$ref: '#/components/schemas/String255'
Innodb_rows_deleted:
$ref: '#/components/schemas/String255'
# Row locking
Innodb_row_lock_waits:
$ref: '#/components/schemas/String255'
Innodb_row_lock_current_waits:
$ref: '#/components/schemas/String255'
Innodb_row_lock_time:
$ref: '#/components/schemas/String255'
Innodb_row_lock_time_avg:
$ref: '#/components/schemas/String255'
Innodb_row_lock_time_max:
$ref: '#/components/schemas/String255'
# Temp tables
Created_tmp_tables:
$ref: '#/components/schemas/String255'
Created_tmp_disk_tables:
$ref: '#/components/schemas/String255'
Created_tmp_files:
$ref: '#/components/schemas/String255'
# Table cache
Open_tables:
$ref: '#/components/schemas/String255'
Opened_tables:
$ref: '#/components/schemas/String255'
Table_open_cache_hits:
$ref: '#/components/schemas/String255'
Table_open_cache_misses:
$ref: '#/components/schemas/String255'
Table_open_cache_overflows:
$ref: '#/components/schemas/String255'
# Connections/Threads
Connections:
$ref: '#/components/schemas/String255'
Max_used_connections:
$ref: '#/components/schemas/String255'
Threads_connected:
$ref: '#/components/schemas/String255'
Threads_running:
$ref: '#/components/schemas/String255'
Threads_created:
$ref: '#/components/schemas/String255'
Threads_cached:
$ref: '#/components/schemas/String255'
Aborted_connects:
$ref: '#/components/schemas/String255'
Aborted_clients:
$ref: '#/components/schemas/String255'
# Queries
Queries:
$ref: '#/components/schemas/String255'
Slow_queries:
$ref: '#/components/schemas/String255'
Select_scan:
$ref: '#/components/schemas/String255'
Select_full_join:
$ref: '#/components/schemas/String255'
Select_full_range_join:
$ref: '#/components/schemas/String255'
# Sorts
Sort_merge_passes:
$ref: '#/components/schemas/String255'
Sort_scan:
$ref: '#/components/schemas/String255'
Sort_range:
$ref: '#/components/schemas/String255'
Sort_rows:
$ref: '#/components/schemas/String255'
# Table locks
Table_locks_immediate:
$ref: '#/components/schemas/String255'
Table_locks_waited:
$ref: '#/components/schemas/String255'
# Server
Uptime:
$ref: '#/components/schemas/String255'
Uptime_since_flush_status:
$ref: '#/components/schemas/String255'
required:
# Network
- Bytes_received
- Bytes_sent
# Handler operations
- Handler_commit
- Handler_update
- Handler_write
# Buffer pool health
- Innodb_buffer_pool_bytes_data
- Innodb_buffer_pool_pages_total
- Innodb_buffer_pool_pages_free
- Innodb_buffer_pool_pages_dirty
- Innodb_buffer_pool_pages_flushed
- Innodb_buffer_pool_read_requests
- Innodb_buffer_pool_reads
- Innodb_buffer_pool_wait_free
# Redo log / Checkpoint
# - Innodb_redo_log_current_lsn (MySQL 8.0.30+ only)
# - Innodb_redo_log_checkpoint_lsn (MySQL 8.0.30+ only)
# - Innodb_redo_log_flushed_to_disk_lsn (MySQL 8.0.30+ only)
- Innodb_log_waits
- Innodb_log_writes
- Innodb_os_log_fsyncs
# I/O operations
- Innodb_data_reads
- Innodb_data_writes
- Innodb_data_fsyncs
- Innodb_pages_read
- Innodb_pages_written
- Innodb_pages_created
# Row operations
- Innodb_rows_read
- Innodb_rows_updated
- Innodb_rows_inserted
- Innodb_rows_deleted
# Row locking
- Innodb_row_lock_waits
- Innodb_row_lock_current_waits
- Innodb_row_lock_time
- Innodb_row_lock_time_avg
- Innodb_row_lock_time_max
# Temp tables
- Created_tmp_tables
- Created_tmp_disk_tables
- Created_tmp_files
# Table cache
- Open_tables
- Opened_tables
- Table_open_cache_hits
- Table_open_cache_misses
- Table_open_cache_overflows
# Connections/Threads
- Connections
- Max_used_connections
- Threads_connected
- Threads_running
- Threads_created
- Threads_cached
- Aborted_connects
- Aborted_clients
# Queries
- Queries
- Slow_queries
- Select_scan
- Select_full_join
- Select_full_range_join
# Sorts
- Sort_merge_passes
- Sort_scan
- Sort_range
- Sort_rows
# Table locks
- Table_locks_immediate
- Table_locks_waited
# Server
- Uptime
- Uptime_since_flush_status
AppInfoMysqlVariables:
type: object
properties:
# InnoDB Buffer Pool - critical for memory and caching
innodb_buffer_pool_size:
$ref: '#/components/schemas/String255'
innodb_buffer_pool_instances:
$ref: '#/components/schemas/String255'
# InnoDB Logging
innodb_log_buffer_size:
$ref: '#/components/schemas/String255'
innodb_log_file_size:
$ref: '#/components/schemas/String255'
innodb_redo_log_capacity:
$ref: '#/components/schemas/String255'
# InnoDB I/O and Flushing
innodb_io_capacity:
$ref: '#/components/schemas/String255'
innodb_io_capacity_max:
$ref: '#/components/schemas/String255'
innodb_flush_sync:
$ref: '#/components/schemas/String255'
innodb_flush_log_at_trx_commit:
$ref: '#/components/schemas/String255'
innodb_doublewrite:
$ref: '#/components/schemas/String255'
# InnoDB Locking and Buffering
innodb_lock_wait_timeout:
$ref: '#/components/schemas/String255'
innodb_change_buffering:
$ref: '#/components/schemas/String255'
# Temporary Tables
tmp_table_size:
$ref: '#/components/schemas/String255'
max_heap_table_size:
$ref: '#/components/schemas/String255'
temptable_max_mmap:
$ref: '#/components/schemas/String255'
temptable_max_ram:
$ref: '#/components/schemas/String255'
# Memory Buffers
key_buffer_size:
$ref: '#/components/schemas/String255'
sort_buffer_size:
$ref: '#/components/schemas/String255'
read_buffer_size:
$ref: '#/components/schemas/String255'
read_rnd_buffer_size:
$ref: '#/components/schemas/String255'
join_buffer_size:
$ref: '#/components/schemas/String255'
binlog_cache_size:
$ref: '#/components/schemas/String255'
# Connection and Table Cache
max_connections:
$ref: '#/components/schemas/String255'
max_allowed_packet:
$ref: '#/components/schemas/String255'
thread_cache_size:
$ref: '#/components/schemas/String255'
table_open_cache:
$ref: '#/components/schemas/String255'
table_definition_cache:
$ref: '#/components/schemas/String255'
# Server Version and Query Performance
version:
$ref: '#/components/schemas/Version'
version_compile_machine:
$ref: '#/components/schemas/String255'
version_compile_os:
$ref: '#/components/schemas/String255'
long_query_time:
$ref: '#/components/schemas/String255'
required:
# InnoDB Buffer Pool
- innodb_buffer_pool_size
- innodb_buffer_pool_instances
# InnoDB Logging
- innodb_log_buffer_size
- innodb_log_file_size
# - innodb_redo_log_capacity (8.0.30+ only)
# InnoDB I/O and Flushing
- innodb_io_capacity
- innodb_io_capacity_max
- innodb_flush_sync
- innodb_flush_log_at_trx_commit
- innodb_doublewrite
# InnoDB Locking and Buffering
- innodb_lock_wait_timeout
- innodb_change_buffering
# Temporary Tables
- tmp_table_size
- max_heap_table_size
- temptable_max_mmap
- temptable_max_ram
# Memory Buffers
- key_buffer_size
- sort_buffer_size
- read_buffer_size
- read_rnd_buffer_size
- join_buffer_size
- binlog_cache_size
# Connection and Table Cache
- max_connections
- max_allowed_packet
- thread_cache_size
- table_open_cache
- table_definition_cache
# Server Version and Query Performance
- version
- version_compile_machine
- version_compile_os
- long_query_time
AppInfoMysqlTableStats:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoTableInfo'
AppInfoTableInfo:
type: object
properties:
tableRows:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
tableCollation:
$ref: '#/components/schemas/String255'
avgRowLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
dataLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
indexLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
autoIncrement:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
createTime:
$ref: '#/components/schemas/Created'
updateTime:
$ref: '#/components/schemas/StringDateTimeNullable'
rowCount:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- tableRows
- tableCollation
- avgRowLength
- dataLength
- indexLength
- autoIncrement
- createTime
- rowCount
AppInfoUsers:
type: object
properties:
userInfo:
additionalProperties:
$ref: '#/components/schemas/AppInfoUserInfo'
userPrivilegeCounts:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoUserPrivilegeCounts'
required:
- userInfo
- userPrivilegeCounts
AppInfoUserPrivilegeCounts:
type: object
properties:
overall:
$ref: '#/components/schemas/AppInfoPrivilegeTimeSeriesCounts'
activeInLast30Days:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoPrivilegeTimeSeriesCounts'
activeInLast90Days:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoPrivilegeTimeSeriesCounts'
AppInfoPrivilegeTimeSeriesCounts:
type: object
additionalProperties:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
AppInfoUserInfo:
type: object
properties:
username:
$ref: '#/components/schemas/Username'
created:
$ref: '#/components/schemas/Created'
lastAccess:
$ref: '#/components/schemas/UserLastAccess'
privileges:
$ref: '#/components/schemas/AppInfoUserPrivileges'
roles:
$ref: '#/components/schemas/AppInfoUserRoles'
required:
- username
- created
- lastAccess
- privileges
- roles
AppInfoUserRoles:
type: object
properties:
full:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
owner:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
manage:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
restricted:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- full
- owner
- manage
- restricted
AppInfoUserPrivileges:
type: array
items:
$ref: '#/components/schemas/String255'
AppInfoRequests:
type: object
properties:
totalRequests:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
totalApiRequests:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
totalRequestDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
operationIds:
additionalProperties:
$ref: '#/components/schemas/AppInfoOperation'
required:
- totalRequests
- totalApiRequests
- totalRequestDuration
- operationIds
AppInfoOperation:
type: object
properties:
totalRequests:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
totalDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
elevatedRequests:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
minDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
maxDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
maxDurationUpdates:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
retried:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
averageRetries:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
totalResLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
minResLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
maxResLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
totalReqLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
minReqLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
maxReqLength:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
projections:
$ref: '#/components/schemas/AppInfoOperationIdProjections'
clients:
$ref: '#/components/schemas/AppInfoClients'
users:
$ref: '#/components/schemas/AppInfoUserRequests'
errors:
type: object
additionalProperties:
type: integer
format: int64
minimum: 0
required:
- totalRequests
- totalDuration
- elevatedRequests
- minDuration
- maxDuration
- maxDurationUpdates
- retried
- averageRetries
- totalResLength
- minResLength
- maxResLength
- clients
- users
- errors
AppInfoClients:
type: object
additionalProperties:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
AppInfoUserRequests:
type: object
additionalProperties:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
AppInfoOperationIdProjections:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoOperationIdProjection'
AppInfoOperationIdProjection:
type: object
properties:
statusStats:
type: object
properties:
totalRequests:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
minDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
maxDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
totalDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
retried:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
averageRetries:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
averageDuration:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- totalRequests
- minDuration
- maxDuration
- totalDuration
- retried
- averageRetries
- averageDuration
AppInfoCollection:
type: object
properties:
name:
$ref: '#/components/schemas/CollectionName'
state:
$ref: '#/components/schemas/AppInfoCollectionState'
settings:
$ref: '#/components/schemas/CollectionSettings'
assets:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
assetsDisabled:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
uniqueStigs:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
stigAssignments:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
rules:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
reviews:
$ref: '#/components/schemas/Integer64MinimumZeroNullable'
reviewsDisabled:
$ref: '#/components/schemas/Integer64MinimumZeroNullable'
assetStigRanges:
$ref: '#/components/schemas/AppInfoAssetStigRanges'
grants:
$ref: '#/components/schemas/AppInfoCollectionGrants'
roleCounts:
$ref: '#/components/schemas/AppInfoCollectionRoleCounts'
labelCounts:
$ref: '#/components/schemas/AppInfoLabelCounts'
required:
- name
- state
- settings
- assets
- assetsDisabled
- uniqueStigs
- stigAssignments
- rules
- reviews
- reviewsDisabled
- assetStigRanges
- grants
- roleCounts
- labelCounts
AppInfoCollectionRoleCounts:
type: object
properties:
restricted:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
full:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
manage:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
owner:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- restricted
- full
- manage
- owner
AppInfoCollectionGrants:
type: object
additionalProperties:
$ref: '#/components/schemas/AppInfoCollectionGrant'
AppInfoCollectionGrant:
type: object
properties:
role:
$ref: '#/components/schemas/Roles'
grantee:
$ref: '#/components/schemas/AppInfoGrantee'
ruleCounts:
$ref: '#/components/schemas/AppInfoRuleCounts'
uniqueStigs:
type: integer
format: int64
minimum: 0
uniqueAssets:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
uniqueStigsDisabled:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
uniqueAssetsDisabled:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- role
- grantee
- ruleCounts
- uniqueStigs
- uniqueAssets
- uniqueStigsDisabled
- uniqueAssetsDisabled
AppInfoGrantee:
type: object
properties:
userId:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
userGroupId:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- userId
- userGroupId
AppInfoRuleCounts:
type: object
properties:
r:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
rw:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
none:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- r
- rw
- none
AppInfoCollectionSettings:
type: object
additionalProperties: false
properties:
fields:
$ref: '#/components/schemas/CollectionFieldSettings'
status:
$ref: '#/components/schemas/CollectionStatusSettings'
history:
$ref: '#/components/schemas/CollectionHistorySettings'
importOptions:
$ref: '#/components/schemas/CollectionImportOptions'
AppInfoCollectionState:
type: string
enum:
- enabled
- disabled
AppInfoLabelCounts:
type: object
properties:
collectionLabels:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
labeledAssets:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
assetLabels:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- collectionLabels
- labeledAssets
- assetLabels
AppInfoGrantCounts:
type: object
properties:
role1:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
role2:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
role3:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
role4:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
AppInfoRestrictedUsers:
type: object
properties:
uniqueAssets:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
stigAsstCount:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
AppInfoAssetStigRanges:
type: object
properties:
range00:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
range01to05:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
range06to10:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
range11to15:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
range16plus:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
required:
- range00
- range01to05
- range06to10
- range11to15
- range16plus
Asset:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
collection:
$ref: '#/components/schemas/CollectionBasic'
description:
$ref: '#/components/schemas/AssetDescription'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
ip:
$ref: '#/components/schemas/AssetIp'
labelIds:
type: array
items:
$ref: '#/components/schemas/LabelId'
mac:
$ref: '#/components/schemas/AssetMac'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/AssetName'
noncomputing:
$ref: '#/components/schemas/AssetNoncomputing'
required:
- assetId
- name
- fqdn
- collection
- description
- ip
- mac
- noncomputing
AssetBasic:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
name:
$ref: '#/components/schemas/AssetName'
required:
- assetId
- name
AssetBasicProjected:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
assetLabelIds:
items:
$ref: '#/components/schemas/LabelId'
type: array
assetLabels:
type: array
items:
$ref: '#/components/schemas/LabelBasicWithColor'
collectionId:
$ref: '#/components/schemas/CollectionId'
name:
$ref: '#/components/schemas/AssetName'
access:
$ref: '#/components/schemas/AclRuleAccess'
required:
- assetId
- name
AssetCount:
minimum: 0
type: integer
AssetCreateBatch:
type: array
items:
$ref: '#/components/schemas/AssetBatchItem'
minItems: 1
AssetBatchItem:
additionalProperties: false
type: object
properties:
description:
$ref: '#/components/schemas/AssetDescription'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
ip:
$ref: '#/components/schemas/AssetIp'
labelNames:
items:
$ref: '#/components/schemas/LabelName'
type: array
mac:
$ref: '#/components/schemas/AssetMac'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/AssetName'
noncomputing:
$ref: '#/components/schemas/AssetNoncomputing'
stigs:
description: The benchmarkIds mapped to this Asset
items:
type: string
type: array
required:
- name
- description
- ip
- noncomputing
- metadata
- stigs
AssetCreateOrReplace:
additionalProperties: false
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
description:
$ref: '#/components/schemas/AssetDescription'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
ip:
$ref: '#/components/schemas/AssetIp'
labelNames:
items:
$ref: '#/components/schemas/LabelName'
type: array
mac:
$ref: '#/components/schemas/AssetMac'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/AssetName'
noncomputing:
$ref: '#/components/schemas/AssetNoncomputing'
stigs:
description: The benchmarkIds mapped to this Asset
items:
type: string
type: array
required:
- name
- collectionId
- description
- ip
- noncomputing
- metadata
- stigs
AssetDescription:
$ref: '#/components/schemas/String255Nullable'
AssetForCollection:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
name:
$ref: '#/components/schemas/AssetName'
AssetFqdn:
$ref: '#/components/schemas/String255Nullable'
AssetId:
$ref: '#/components/schemas/StringIntId'
AssetIp:
$ref: '#/components/schemas/String255Nullable'
AssetMac:
$ref: '#/components/schemas/String255Nullable'
AssetName:
$ref: '#/components/schemas/String255'
AssetNoncomputing:
type: boolean
AssetProjected:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
collection:
$ref: '#/components/schemas/CollectionBasic'
description:
$ref: '#/components/schemas/AssetDescription'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
ip:
$ref: '#/components/schemas/AssetIp'
labelIds:
type: array
items:
$ref: '#/components/schemas/LabelId'
labels:
type: array
items:
$ref: '#/components/schemas/LabelBasicWithColor'
mac:
$ref: '#/components/schemas/AssetMac'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/AssetName'
noncomputing:
$ref: '#/components/schemas/AssetNoncomputing'
statusStats:
additionalProperties: false
type: object
properties:
acceptedCount:
nullable: true
type: integer
maxTs:
$ref: '#/components/schemas/MaxTs'
minTs:
$ref: '#/components/schemas/MinTs'
rejectedCount:
nullable: true
type: integer
ruleCount:
$ref: '#/components/schemas/RuleCount'
savedCount:
nullable: true
type: integer
stigCount:
type: integer
submittedCount:
nullable: true
type: integer
stigs:
type: array
description: The benchmarkIds mapped to this Asset
items:
$ref: '#/components/schemas/CollectionStig'
required:
- assetId
- name
- fqdn
- collection
- description
- ip
- mac
- noncomputing
- labelIds
AssetStigResponse:
additionalProperties: false
type: object
properties:
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
revisionDate:
$ref: '#/components/schemas/RevisionDate'
revisionStr:
$ref: '#/components/schemas/RevisionStrRaw'
ruleCount:
$ref: '#/components/schemas/RuleCount'
required:
- benchmarkId
- revisionStr
- revisionDate
- ruleCount
AssetStigSelection:
additionalProperties: false
type: object
description: >
An array that specifies a list of Assets/STIG items.
Each array item is an object that MUST include the property `assetId`
and MAY include the property `stigs`.
If the `stigs` property is absent, the default value of the property is
used. The default value is an array of the default revisions of each
STIG to which the requesting User
has been granted access on the Asset.
If the `stigs` property is present, the value MUST be an array. Each
array member is EITHER:
- an object that identifies both a `benchmarkId` and a specific
`revisionStr`
- a string whose value is a `benchmarkId`. This is equivalent to
specifying the object {"benchmarkId": [provided benchmarkId],
"revisionStr": [default revisionStr for the provided benchmarkId]}
properties:
assetId:
$ref: '#/components/schemas/AssetId'
stigs:
maxItems: 30
minItems: 1
type: array
uniqueItems: true
items:
oneOf:
- $ref: '#/components/schemas/RevisionBasic'
- $ref: '#/components/schemas/String255'
required:
- assetId
AssetUpdate:
additionalProperties: false
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
description:
$ref: '#/components/schemas/AssetDescription'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
ip:
$ref: '#/components/schemas/AssetIp'
labelNames:
type: array
items:
$ref: '#/components/schemas/LabelName'
mac:
$ref: '#/components/schemas/AssetMac'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/AssetName'
noncomputing:
$ref: '#/components/schemas/AssetNoncomputing'
stigs:
description: The benchmarkIds mapped to this Asset
type: array
items:
$ref: '#/components/schemas/BenchmarkId'
AssetsPatchRequest:
additionalProperties: false
type: object
properties:
assetIds:
type: array
minItems: 1
items:
$ref: '#/components/schemas/AssetId'
operation:
type: string
enum:
- delete
required:
- assetIds
- operation
AssetsPatchResponse:
additionalProperties: false
type: object
properties:
assetIds:
type: array
items:
$ref: '#/components/schemas/AssetId'
operation:
type: string
enum:
- deleted
Attribution:
type: object
properties:
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
ts:
$ref: '#/components/schemas/StringDateTime'
Attributions:
type: object
properties:
created:
$ref: '#/components/schemas/Attribution'
modified:
$ref: '#/components/schemas/Attribution'
BenchmarkId:
$ref: '#/components/schemas/String255Nullable'
Cci:
additionalProperties: false
type: object
properties:
cci:
$ref: '#/components/schemas/CciString'
contributor:
type: string
definition:
$ref: '#/components/schemas/DefinitionString'
emassAp:
$ref: '#/components/schemas/EmassAp'
publishdate:
$ref: '#/components/schemas/StringDateTime'
references:
type: array
items:
$ref: '#/components/schemas/CciReferenceItem'
status:
$ref: '#/components/schemas/CciStatus'
stigs:
items:
$ref: '#/components/schemas/RevisionBasic'
type: array
type:
$ref: '#/components/schemas/CciType'
CciBasic:
additionalProperties: false
type: object
properties:
apAcronym:
$ref: '#/components/schemas/ApAcronym'
cci:
$ref: '#/components/schemas/CciString'
control:
nullable: true
type: string
definition:
$ref: '#/components/schemas/DefinitionString'
required:
- cci
- apAcronym
- definition
- control
CciListItem:
additionalProperties: false
type: object
properties:
cci:
$ref: '#/components/schemas/CciString'
references:
type: array
items:
$ref: '#/components/schemas/CciReferenceItem'
type:
$ref: '#/components/schemas/CciType'
CciLocation:
$ref: '#/components/schemas/String255'
CciReferenceItem:
additionalProperties: false
type: object
properties:
creator:
type: string
indexDisa:
$ref: '#/components/schemas/IndexDisa'
location:
$ref: '#/components/schemas/CciLocation'
parentControl:
$ref: '#/components/schemas/ParentControl'
textRefNist:
$ref: '#/components/schemas/TextRefNist'
title:
$ref: '#/components/schemas/CciString'
version:
$ref: '#/components/schemas/VersionString'
CciStatus:
$ref: '#/components/schemas/String20'
CciString:
$ref: '#/components/schemas/String255'
CciType:
$ref: '#/components/schemas/String20'
Check:
additionalProperties: false
type: object
properties:
content:
type: string
system:
type: string
ChecklistAssetStig:
type: array
items:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
autoResult:
type: boolean
comment:
$ref: '#/components/schemas/CommentaryStringNullable'
detail:
$ref: '#/components/schemas/CommentaryStringNullable'
groupId:
$ref: '#/components/schemas/GroupId'
groupTitle:
$ref: '#/components/schemas/GroupTitle'
result:
$ref: '#/components/schemas/ChecklistResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
rule:
$ref: '#/components/schemas/RuleProjected'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleTitle:
$ref: '#/components/schemas/RuleTitle'
severity:
$ref: '#/components/schemas/RuleSeverity'
status:
$ref: '#/components/schemas/ChecklistStatus'
statusTs:
$ref: '#/components/schemas/StringDateTimeNullable'
touchTs:
$ref: '#/components/schemas/StringDateTimeNullable'
ts:
$ref: '#/components/schemas/StringDateTimeNullable'
version:
$ref: '#/components/schemas/VersionString'
ChecklistCkl:
additionalProperties: false
description: The CKL format generated and read by DISA STIG Viewer
type: object
properties:
ASSET:
type: object
additionalProperties: false
properties:
ASSET_TYPE:
type: string
HOST_FQDN:
type: string
HOST_GUID:
type: string
HOST_IP:
type: string
HOST_MAC:
type: string
HOST_NAME:
type: string
TARGET_KEY:
type: string
TECH_AREA:
type: string
STIGS:
type: object
additionalProperties: false
properties:
iSTIG:
type: array
items:
type: object
properties:
STIG_INFO:
type: array
items:
type: object
properties:
SI_DATA:
type: object
properties:
SID_DATA:
type: string
SID_NAME:
type: string
VULN:
type: array
items:
type: object
additionalProperties: false
properties:
COMMENTS:
type: string
FINDING_DETAILS:
type: string
SEVERITY_JUSTIFICATION:
type: string
SEVERITY_OVERRIDE:
type: string
STATUS:
type: string
enum:
- Open
- NotAFinding
- Not_Applicable
- Not_Reviewed
STIG_DATA:
type: array
items:
type: object
properties:
ATTRIBUTE_DATA:
type: string
VULN_ATTRIBUTE:
type: string
xml:
name: CHECKLIST
ChecklistCklb:
additionalProperties: false
description: The CKLB format generated and read by DISA STIG VIewer 3
type: object
properties:
title:
type: string
id:
type: string
format: uuid
active:
type: boolean
mode:
type: integer
has_path:
type: boolean
target_data:
$ref: '#/components/schemas/TargetData'
stigs:
type: array
items:
$ref: '#/components/schemas/StigCklb'
ChecklistJsonAccess:
type: object
properties:
access:
$ref: '#/components/schemas/AclRuleAccess'
checklist:
$ref: '#/components/schemas/ChecklistAssetStig'
TargetData:
type: object
properties:
target_type:
type: string
host_name:
$ref: '#/components/schemas/AssetName'
ip_address:
$ref: '#/components/schemas/AssetIp'
mac_address:
$ref: '#/components/schemas/AssetMac'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
comments:
type: string
role:
type: string
is_web_database:
type: boolean
technology_area:
type: string
web_db_site:
type: string
web_db_instance:
type: string
StigCklb:
type: object
properties:
stig_name:
type: string
display_name:
type: string
stig_id:
type: string
version:
type: string
release_info:
type: string
uuid:
type: string
format: uuid
reference_identifier:
type: string
size:
type: integer
rules:
type: array
items:
$ref: '#/components/schemas/Rule'
Rule:
type: object
properties:
uuid:
type: string
format: uuid
stig_uuid:
type: string
format: uuid
target_key:
type: string
nullable: true
stig_ref:
type: string
nullable: true
group_id:
type: string
rule_id:
type: string
rule_id_src:
type: string
weight:
type: string
classification:
type: string
severity:
type: string
rule_version:
type: string
group_title:
type: string
rule_title:
type: string
fix_text:
type: string
false_positives:
type: string
nullable: true
false_negatives:
type: string
nullable: true
discussion:
type: string
check_content:
type: string
documentable:
type: string
mitigations:
type: string
nullable: true
potential_impacts:
type: string
nullable: true
third_party_tools:
type: string
nullable: true
mitigation_control:
type: string
nullable: true
responsibility:
type: string
nullable: true
security_override_guidance:
type: string
nullable: true
ia_controls:
type: string
nullable: true
check_content_ref:
type: object
properties:
href:
type: string
name:
type: string
legacy_ids:
type: array
items:
type: string
group_tree:
type: array
items:
$ref: '#/components/schemas/GroupTree'
createdAt:
type: string
format: date-time
updatedAt:
type: string
format: date-time
STIGUuid:
type: string
format: uuid
status:
type: string
overrides:
type: object
comments:
type: string
finding_details:
type: string
ccis:
type: array
items:
type: string
GroupTree:
type: object
properties:
id:
type: string
title:
type: string
description:
type: string
ChecklistCollectionCounts:
additionalProperties: false
type: object
properties:
results:
type: object
additionalProperties: false
properties:
fail:
type: integer
notapplicable:
type: integer
other:
type: integer
pass:
type: integer
statuses:
additionalProperties: false
type: object
properties:
accepted:
type: integer
rejected:
type: integer
saved:
type: integer
submitted:
type: integer
ChecklistCollectionStig:
additionalProperties: false
type: object
properties:
counts:
$ref: '#/components/schemas/ChecklistCollectionCounts'
groupId:
$ref: '#/components/schemas/GroupId'
groupTitle:
$ref: '#/components/schemas/GroupTitle'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleTitle:
$ref: '#/components/schemas/RuleTitle'
severity:
$ref: '#/components/schemas/RuleSeverity'
timestamps:
additionalProperties: false
type: object
properties:
statusTs:
$ref: '#/components/schemas/ChecklistCollectionStigTimestamps'
touchTs:
$ref: '#/components/schemas/ChecklistCollectionStigTimestamps'
ts:
$ref: '#/components/schemas/ChecklistCollectionStigTimestamps'
version:
$ref: '#/components/schemas/VersionString'
ChecklistCollectionStigTimestamp:
$ref: '#/components/schemas/StringDateTimeNullable'
ChecklistCollectionStigTimestamps:
additionalProperties: false
type: object
properties:
max:
$ref: '#/components/schemas/ChecklistCollectionStigTimestamp'
min:
$ref: '#/components/schemas/ChecklistCollectionStigTimestamp'
ChecklistResult:
description: The Review result
type: string
nullable: true
enum:
- fail
- pass
- notapplicable
- notchecked
- unknown
- error
- notselected
- informational
- fixed
- null
ChecklistResultUnreviewed:
description: The Review result
type: string
enum:
- notchecked
- unknown
- error
- notselected
- informational
- fixed
- null
nullable: true
ChecklistStatus:
type: string
nullable: true
enum:
- saved
- submitted
- accepted
- rejected
- null
ChecklistXccdf:
additionalProperties: true
type: object
description: >
An XCCDF document with TestResult. Note: OAS 3.x cannot represent the
actual XML schema
xml:
name: Benchmark
namespace: http://checklists.nist.gov/xccdf/1.2
ClientErrorBadAssetPost:
additionalProperties: false
type: object
properties:
code:
type: string
enum:
- "422"
nullable: true
error:
type: string
detail:
type: array
items:
type: object
properties:
failure:
type: string
detail:
type: object
properties:
name:
type: string
assetIndex:
type: integer
benchmarkId:
type: string
benchmarkIdIndex:
type: integer
labelName:
type: string
labelIndex:
type: integer
required:
- error
- detail
ClientErrorDuplicateCollection:
additionalProperties: false
type: object
properties:
code:
type: string
enum:
- "400"
data:
$ref: '#/components/schemas/Collection'
message:
type: string
enum:
- Duplicate name
Collection:
additionalProperties: false
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
created:
$ref: '#/components/schemas/Created'
description:
$ref: '#/components/schemas/CollectionDescription'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/CollectionName'
settings:
$ref: '#/components/schemas/CollectionSettings'
required:
- collectionId
- name
- description
- settings
- metadata
- created
CollectionBasic:
additionalProperties: false
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
name:
$ref: '#/components/schemas/CollectionName'
CollectionCloneOptions:
additionalProperties: false
type: object
properties:
assets:
type: boolean
default: true
description: >-
Clone the source Collection's Assets and their core properties. If
this option is not enabled then the stagMappings and pinRevisions
options are ignored.
grants:
default: true
type: boolean
description: >-
Clone the source Collection's users and their grants. Whether this
option is enabled or not, the creator of the cloned Collection (ie.
you) will be given an Owner grant in the clone.
labels:
type: boolean
default: true
description: >-
Clone the source Collection's available labels. You must enable this
option AND the assets option for labels to be mapped to Assets in
the clone.
pinRevisions:
default: matchSource
type: string
description: >
matchSource: STIGs in the source Collection that are pinned
to a specific Revision will be pinned to that Revision in the clone.
STIGs that track the latest Revision (unpinned) in the source will
be unpinned in the clone.sourceDefaults: All STIGs in
the clone will be pinned to a specific Revision. STIGs that are
pinned to a specific Revision in the source Collection will be
pinned to that Revision in the clone. STIGs that track the latest
Revision in the source will be pinned to the current latest Revision
in the clone.
enum:
- matchSource
- sourceDefaults
stigMappings:
default: withReviews
type: string
description: >
withReviews: Assets will be cloned with their current STIG
assignments and ALL stored Reviews. This will include Reviews that
are no longer associated with a current STIG assignment or are
associated with a non-default Revision of a
STIG.withoutReviews: Assets will be cloned with their
current STIG assignments but NO stored Reviews will be cloned. All
Metrics will be set to zero. none: Assets will be
cloned with only their core properties and no STIG assignments or
Reviews. The pinRevisions option will be ignored.
enum:
- none
- withReviews
- withoutReviews
CollectionCloneRequest:
additionalProperties: false
type: object
properties:
description:
$ref: '#/components/schemas/CollectionDescription'
name:
$ref: '#/components/schemas/CollectionName'
options:
$ref: '#/components/schemas/CollectionCloneOptions'
required:
- name
- description
CollectionCloneResponse:
description: >
The response body is a stream of newline-delimited JSON (NDJSON) objects
reporting the progress of the (possibly long running) cloning process.
Each object conforms to this schema, but not all objects will have every
property. The sequence of objects starts with multiple
{"stage": "collection"} objects, optionally followed by multiple
{"stage": "reviews"} objects if review cloning is requested, and
concludes with one {"stage": "result"} object whose "collection"
property value conforms to the CollectionProjected schema for the
created Collection. Success is indicated when the final
{"stage": "result"} message is sent. Errors that prevent cloning from
completing are reported with {"status": "error"} and the "result" stage
is not reported. Note that the endpoint will return HTTP status 200
immediately after the request is validated and the cloning process has
started, so you should not rely on status 200 for indication of cloning
success.
type: object
properties:
collection:
$ref: '#/components/schemas/CollectionProjected'
error:
type: object
message:
type: string
stack:
type: string
stage:
enum:
- collection
- reviews
- result
type: string
status:
enum:
- running
- finished
- error
type: string
step:
type: integer
stepCount:
type: integer
stepName:
type: string
CollectionCreateOrReplace:
additionalProperties: false
type: object
properties:
description:
$ref: '#/components/schemas/CollectionDescription'
grants:
type: array
items:
anyOf:
- $ref: '#/components/schemas/UserGrant'
- $ref: '#/components/schemas/UserGroupGrant'
labels:
type: array
items:
$ref: '#/components/schemas/LabelCreate'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/CollectionName'
settings:
$ref: '#/components/schemas/CollectionSettings'
required:
- name
- grants
CollectionDescription:
$ref: '#/components/schemas/String255Nullable'
CollectionExportToResponse:
description: >
The response body is a stream of newline-delimited JSON (NDJSON) objects
reporting the progress of the (possibly long running) export process.
Each object conforms to this schema, but not all objects will have every
property. The sequence of objects starts with multiple
{"stage": "prepare"} objects, followed by multiple {"stage": "assets"}
objects, multiple {"stage": "reviews"} objects, and multiple {"stage":
"metrics"} objects. The stream concludes with one {"stage": "commit"}
object and then one {"stage": "result"} object whose "counts" property
value conforms to the schema below. Success is indicated when
the final {"stage": "result"} message is sent. Errors that prevent
exporting from completing are reported with {"status": "error"} and the
"result" stage is not reported. Note that the endpoint will return HTTP
status 200 immediately after the request is validated and the export
process has started, so you should not rely on status 200 for indication
of export success.
type: object
properties:
counts:
additionalProperties: false
type: object
properties:
assetsCreated:
type: integer
reviewsInserted:
type: integer
reviewsUpdated:
type: integer
stigsMapped:
type: integer
error:
type: object
message:
type: string
stack:
type: string
stage:
enum:
- prepare
- assets
- reviews
- metrics
- result
type: string
status:
enum:
- running
- error
type: string
step:
type: integer
stepCount:
type: integer
stepName:
type: string
CollectionFieldEnabledAlways:
additionalProperties: false
type: object
properties:
enabled:
type: string
enum:
- always
required:
type: string
enum:
- always
- findings
- optional
required:
- enabled
- required
CollectionFieldEnabledFindings:
additionalProperties: false
type: object
properties:
enabled:
type: string
enum:
- findings
required:
type: string
enum:
- findings
- optional
required:
- enabled
- required
CollectionFieldSetting:
type: object
example:
enabled: always
required: findings
oneOf:
- $ref: '#/components/schemas/CollectionFieldEnabledAlways'
- $ref: '#/components/schemas/CollectionFieldEnabledFindings'
CollectionFieldSettings:
additionalProperties: false
type: object
properties:
comment:
$ref: '#/components/schemas/CollectionFieldSetting'
detail:
$ref: '#/components/schemas/CollectionFieldSetting'
required:
- detail
- comment
CollectionGrant:
additionalProperties: false
type: object
properties:
roleId:
$ref: '#/components/schemas/RoleId'
collectionId:
$ref: '#/components/schemas/CollectionId'
required:
- collectionId
- roleId
CollectionGrantProjected:
additionalProperties: false
type: object
properties:
roleId:
$ref: '#/components/schemas/RoleId'
collection:
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
name:
$ref: '#/components/schemas/CollectionName'
grantees:
$ref: '#/components/schemas/Grantees'
CollectionHistorySettings:
additionalProperties: false
type: object
properties:
maxReviews:
example: 5
maximum: 15
minimum: 0
type: integer
required:
- maxReviews
CollectionId:
$ref: '#/components/schemas/StringIntId'
CollectionImportOptions:
additionalProperties: false
type: object
properties:
autoStatus:
$ref: '#/components/schemas/CollectionImportAutoStatus'
unreviewed:
description: |
Controls how to handle unreviewed rules (those with result = 'notchecked').
- 'never': Don't import unreviewed rules
- 'commented': Import unreviewed rules that have comments, using the result specified in unreviewedCommented
- 'always': Import all unreviewed rules, using the result specified in unreviewedCommented for those with comments
type: string
enum:
- never
- commented
- always
unreviewedCommented:
description: |
The result to use for unreviewed rules that have comments, when unreviewed is set to 'commented' or 'always'.
type: string
enum:
- notchecked
- informational
emptyDetail:
description: |
Controls how to handle rules with empty finding details.
- 'ignore': Leave the detail field null
- 'import': Import the empty detail (as an empty string)
- 'replace': Replace with a default message
type: string
enum:
- ignore
- import
- replace
emptyComment:
description: |
Controls how to handle rules with empty comments.
- 'ignore': Leave the comment field null
- 'import': Import the empty comment (as an empty string)
- 'replace': Replace with a default message
type: string
enum:
- ignore
- import
- replace
updateAssetProps:
description: |
Flag indicating whether to update Asset information (IP, MAC, FQDN, noncomputing, and metadata including role and tech area) when Asset already exists in the Collection.
type: boolean
allowCustom:
description: |
Flag indicating whether Clients may POST reviews that do not conform to importOptions specified.
type: boolean
required:
- autoStatus
- unreviewed
- unreviewedCommented
- emptyDetail
- emptyComment
- allowCustom
CollectionImportAutoStatus:
type: object
additionalProperties: false
description: |
Determines how to set the status property of imported reviews for each evaluation result.
Each property must be one of:
- 'null': Don't set a status (Keep existing Review Status)
- 'saved': Always set status to 'saved'
- 'submitted': Set status to 'submitted' if the review is submittable per Collection settings
- 'accepted': Set status to 'accepted' if the review is submittable, and User has permission to accept, otherwise 'submitted'
properties:
fail:
$ref: '#/components/schemas/ReviewStatusOption'
notapplicable:
$ref: '#/components/schemas/ReviewStatusOption'
pass:
$ref: '#/components/schemas/ReviewStatusOption'
required:
- fail
- notapplicable
- pass
CollectionName:
$ref: '#/components/schemas/String45'
CollectionProjected:
additionalProperties: false
type: object
properties:
assets:
type: array
items:
$ref: '#/components/schemas/AssetForCollection'
collectionId:
$ref: '#/components/schemas/CollectionId'
description:
$ref: '#/components/schemas/CollectionDescription'
grants:
type: array
items:
anyOf:
- $ref: '#/components/schemas/UserGrantProjected'
- $ref: '#/components/schemas/UserGroupGrantProjected'
users:
type: array
items:
$ref: '#/components/schemas/GrantEffective'
labels:
type: array
items:
$ref: '#/components/schemas/Label'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/CollectionName'
owners:
type: array
items:
$ref: '#/components/schemas/Owner'
settings:
$ref: '#/components/schemas/CollectionSettings'
statistics:
$ref: '#/components/schemas/CollectionStatistics'
stigs:
type: array
items:
$ref: '#/components/schemas/CollectionStig'
required:
- collectionId
- name
- description
- settings
- metadata
CollectionSettings:
additionalProperties: false
type: object
properties:
fields:
$ref: '#/components/schemas/CollectionFieldSettings'
history:
$ref: '#/components/schemas/CollectionHistorySettings'
status:
$ref: '#/components/schemas/CollectionStatusSettings'
importOptions:
$ref: '#/components/schemas/CollectionImportOptions'
CollectionSettingsRequired:
additionalProperties: false
type: object
properties:
fields:
$ref: '#/components/schemas/CollectionFieldSettings'
history:
$ref: '#/components/schemas/CollectionHistorySettings'
status:
$ref: '#/components/schemas/CollectionStatusSettings'
importOptions:
$ref: '#/components/schemas/CollectionImportOptions'
required:
- fields
- history
- status
- importOptions
CollectionStatistics:
additionalProperties: false
type: object
properties:
assetCount:
$ref: '#/components/schemas/AssetCount'
checklistCount:
type: integer
created:
$ref: '#/components/schemas/Created'
userCount:
type: integer
required:
- created
- assetCount
- userCount
- checklistCount
CollectionStatusCount:
additionalProperties: false
type: object
properties:
resultEngine:
type: integer
total:
type: integer
required:
- total
- resultEngine
CollectionStatusSettings:
additionalProperties: false
type: object
properties:
canAccept:
type: boolean
minAcceptGrant:
type: integer
example: 2
maximum: 4
minimum: 2
resetCriteria:
type: string
example: result
enum:
- any
- result
required:
- canAccept
- minAcceptGrant
- resetCriteria
CollectionStig:
additionalProperties: false
type: object
properties:
benchmarkDate:
$ref: '#/components/schemas/StringDateNullable'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
revisionPinned:
type: boolean
revisionStr:
$ref: '#/components/schemas/RevisionStr'
ruleCount:
$ref: '#/components/schemas/RuleCount'
required:
- benchmarkId
- revisionStr
- benchmarkDate
- revisionPinned
- ruleCount
CollectionStigWithAssetCount:
additionalProperties: false
type: object
properties:
assetCount:
$ref: '#/components/schemas/AssetCount'
assets:
items:
$ref: '#/components/schemas/AssetForCollection'
type: array
benchmarkDate:
$ref: '#/components/schemas/StringDateNullable'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
revisionPinned:
type: boolean
revisionStr:
$ref: '#/components/schemas/RevisionStr'
ruleCount:
$ref: '#/components/schemas/RuleCount'
title:
$ref: '#/components/schemas/StatusText'
required:
- benchmarkId
- revisionStr
- benchmarkDate
- revisionPinned
- ruleCount
- assetCount
CollectionStigWithIsDefault:
additionalProperties: false
type: object
properties:
benchmarkDate:
$ref: '#/components/schemas/StringDateNullable'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
isDefault:
type: boolean
revisionPinned:
type: boolean
revisionStr:
$ref: '#/components/schemas/RevisionStr'
ruleCount:
$ref: '#/components/schemas/RuleCount'
required:
- benchmarkId
- revisionStr
- benchmarkDate
- revisionPinned
- ruleCount
- isDefault
CollectionUpdate:
type: object
additionalProperties: false
minProperties: 1
properties:
description:
$ref: '#/components/schemas/CollectionDescription'
grants:
type: array
items:
type: object
properties:
roleId:
$ref: '#/components/schemas/RoleId'
userId:
$ref: '#/components/schemas/UserId'
labels:
type: array
items:
$ref: '#/components/schemas/LabelCreate'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/CollectionName'
settings:
$ref: '#/components/schemas/CollectionSettingsRequired'
CollectionsProjected:
additionalProperties: false
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
description:
$ref: '#/components/schemas/CollectionDescription'
metadata:
$ref: '#/components/schemas/Metadata'
name:
$ref: '#/components/schemas/CollectionName'
owners:
type: array
items:
$ref: '#/components/schemas/Owner'
settings:
$ref: '#/components/schemas/CollectionSettings'
statistics:
$ref: '#/components/schemas/CollectionStatistics'
required:
- collectionId
- name
- description
- settings
- metadata
CommentaryString:
$ref: '#/components/schemas/String32767'
CommentaryStringNullable:
$ref: '#/components/schemas/String32767Nullable'
CommitBranch:
type: string
CommitDescribe:
type: string
CommitObject:
type: object
additionalProperties: false
properties:
branch:
$ref: '#/components/schemas/CommitBranch'
describe:
$ref: '#/components/schemas/CommitDescribe'
sha:
$ref: '#/components/schemas/CommitSha'
tag:
$ref: '#/components/schemas/CommitTag'
CommitSha:
type: string
CommitTag:
type: string
Created:
$ref: '#/components/schemas/StringDateTime'
DefinitionString:
nullable: true
type: string
Detail:
type: object
properties:
assetStig:
type: array
items:
$ref: '#/components/schemas/DetailAssetStig'
dbInfo:
$ref: '#/components/schemas/DetailMySqlInfo'
DetailAssetStig:
additionalProperties: false
type: object
properties:
assetCnt:
type: integer
collectionId:
$ref: '#/components/schemas/CollectionId'
range01to05:
type: integer
range06to10:
type: integer
range11to15:
type: integer
range16plus:
type: integer
DetailMySqlInfo:
type: object
properties:
tables:
type: object
additionalProperties:
$ref: '#/components/schemas/DetailMySqlTableInfo'
DetailMySqlTableInfo:
additionalProperties: false
type: object
properties:
autoIncrement:
nullable: true
type: integer
avgRowLength:
nullable: true
type: integer
createTime:
$ref: '#/components/schemas/StringDateTimeNullable'
dataLength:
nullable: true
type: integer
indexLength:
nullable: true
type: integer
maxDataLength:
nullable: true
type: integer
tableCollation:
nullable: true
type: string
tableName:
type: string
tableRows:
nullable: true
type: integer
updateTime:
$ref: '#/components/schemas/StringDateTimeNullable'
Dependencies:
type: object
properties:
db:
type: boolean
oidc:
type: boolean
DisplayName:
$ref: '#/components/schemas/String255Nullable'
EffectiveAcl:
additionalProperties: false
type: object
properties:
access:
$ref: '#/components/schemas/AclRuleAccess'
asset:
$ref: '#/components/schemas/AssetBasic'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
aclSources:
type: array
items:
$ref: '#/components/schemas/AclSource'
EmassAp:
additionalProperties: false
type: object
nullable: true
properties:
apAcronym:
$ref: '#/components/schemas/ApAcronym'
assessmentProcedure:
type: string
implementation:
type: string
Endpoints:
additionalProperties: false
type: object
properties:
ui:
type: string
Error:
type: object
properties:
detail:
type: string
error:
type: string
stack:
type: string
FindingProjected:
additionalProperties: false
type: object
properties:
apAcronym:
$ref: '#/components/schemas/ApAcronym'
assetCount:
$ref: '#/components/schemas/AssetCount'
assets:
type: array
items:
$ref: '#/components/schemas/AssetBasic'
cci:
nullable: true
type: string
ccis:
type: array
minItems: 0
items:
$ref: '#/components/schemas/CciBasic'
definition:
$ref: '#/components/schemas/DefinitionString'
groupId:
$ref: '#/components/schemas/GroupId'
groups:
type: array
items:
$ref: '#/components/schemas/GroupProjected'
ruleId:
$ref: '#/components/schemas/RuleId'
rules:
type: array
items:
$ref: '#/components/schemas/RuleAbbr'
severity:
$ref: '#/components/schemas/RuleSeverity'
stigs:
type: array
items:
$ref: '#/components/schemas/CollectionStig'
title:
$ref: '#/components/schemas/RuleTitle'
Fix:
additionalProperties: false
type: object
properties:
fixref:
type: string
text:
type: string
Grant:
oneOf:
- $ref: '#/components/schemas/UserGrantProjected'
- $ref: '#/components/schemas/UserGroupGrantProjected'
GrantPost:
oneOf:
- $ref: '#/components/schemas/UserGrant'
- $ref: '#/components/schemas/UserGroupGrant'
GrantEffective:
type: object
properties:
roleId:
$ref: '#/components/schemas/RoleId'
grantees:
$ref: '#/components/schemas/Grantees'
user:
$ref: '#/components/schemas/UserBasicWithDisplayName'
required:
- roleId
- grantees
- user
Grantee:
oneOf:
- $ref: '#/components/schemas/UserBasic'
- $ref: '#/components/schemas/UserGroupBasic'
Grantees:
type: array
items:
$ref: '#/components/schemas/Grantee'
GrantId:
$ref: '#/components/schemas/StringIntId'
GroupId:
$ref: '#/components/schemas/String255Nullable'
GroupProjected:
additionalProperties: false
type: object
properties:
groupId:
$ref: '#/components/schemas/GroupId'
rules:
type: array
items:
$ref: '#/components/schemas/RuleAbbr'
severity:
$ref: '#/components/schemas/RuleSeverity'
title:
$ref: '#/components/schemas/GroupTitle'
GroupTitle:
$ref: '#/components/schemas/String255Nullable'
IndexDisa:
$ref: '#/components/schemas/String255'
IntegerMinimumZeroNullable:
type: integer
minimum: 0
nullable: true
Integer64MinimumZero:
type: integer
format: int64
minimum: 0
Integer64MinimumZeroNullable:
type: integer
format: int64
minimum: 0
nullable: true
Job:
additionalProperties: false
type: object
properties:
jobId:
$ref: '#/components/schemas/JobId'
name:
$ref: "#/components/schemas/String45"
description:
$ref: "#/components/schemas/String255Nullable"
createdBy:
$ref: '#/components/schemas/UserBasicNullable'
created:
$ref: '#/components/schemas/StringDateTime'
updatedBy:
$ref: '#/components/schemas/UserBasicNullable'
updated:
$ref: '#/components/schemas/StringDateTimeNullable'
tasks:
$ref: '#/components/schemas/JobTaskList'
event:
$ref: '#/components/schemas/JobEvent'
runCount:
type: integer
lastRun:
$ref: '#/components/schemas/JobRun'
required: [jobId, name, tasks, created, createdBy]
JobCreate:
additionalProperties: false
type: object
properties:
name:
$ref: "#/components/schemas/String45"
description:
$ref: "#/components/schemas/String255Nullable"
tasks:
$ref: '#/components/schemas/JobTaskListCreate'
event:
$ref: '#/components/schemas/JobEventCreate'
required: [name, tasks]
JobEvent:
oneOf:
- type: integer
nullable: true
- $ref: '#/components/schemas/JobEventRecurring'
- $ref: '#/components/schemas/JobEventOnce'
JobEventCreate:
oneOf:
- $ref: '#/components/schemas/JobEventRecurringCreate'
- $ref: '#/components/schemas/JobEventOnceCreate'
- type: integer
nullable: true
JobEventOnce:
additionalProperties: false
type: object
properties:
eventId:
$ref: "#/components/schemas/String45"
type:
type: string
enum:
- once
starts:
$ref: '#/components/schemas/StringDateTime'
enabled:
type: boolean
default: true
required: [eventId, starts, type]
JobEventOnceCreate:
additionalProperties: false
type: object
properties:
type:
type: string
enum:
- once
starts:
$ref: '#/components/schemas/StringDateTime'
required: [starts, type]
JobEventRecurring:
additionalProperties: false
type: object
properties:
eventId:
$ref: "#/components/schemas/String45"
type:
type: string
enum:
- recurring
interval:
$ref: '#/components/schemas/JobInterval'
starts:
$ref: '#/components/schemas/StringDateTimeNullable'
ends:
$ref: '#/components/schemas/StringDateTimeNullable'
enabled:
type: boolean
default: true
required: [eventId, type, interval]
JobEventRecurringCreate:
additionalProperties: false
type: object
properties:
type:
type: string
enum:
- recurring
interval:
$ref: '#/components/schemas/JobInterval'
starts:
$ref: '#/components/schemas/StringDateTimeNullable'
ends:
$ref: '#/components/schemas/StringDateTimeNullable'
enabled:
type: boolean
default: true
required: [type, interval]
JobInterval:
additionalProperties: false
type: object
properties:
value:
type: string
field:
type: string
enum:
- minute
- hour
- day
- week
- month
required: [value, field]
JobId:
$ref: '#/components/schemas/StringIntId'
JobRun:
additionalProperties: false
nullable: true
type: object
properties:
runId:
$ref: '#/components/schemas/JobRunId'
created:
$ref: '#/components/schemas/StringDateTime'
updated:
$ref: '#/components/schemas/StringDateTimeNullable'
state:
$ref: '#/components/schemas/JobRunState'
jobId:
$ref: '#/components/schemas/JobId'
required: [runId, created, state]
JobRunCreated:
additionalProperties: false
type: object
properties:
runId:
$ref: '#/components/schemas/JobRunId'
required: [runId]
JobRunId:
$ref: '#/components/schemas/StringUuid'
JobRunOutput:
additionalProperties: false
type: object
properties:
type:
type: string
message:
type: string
task:
$ref: "#/components/schemas/String45"
taskId:
$ref: "#/components/schemas/JobTaskId"
ts:
$ref: '#/components/schemas/StringDateTime'
required: [message, type, task, ts]
JobRunState:
type: string
nullable: true
enum:
- running
- completed
- failed
JobTask:
type: object
additionalProperties: false
properties:
taskId:
$ref: '#/components/schemas/StringIntId'
name:
$ref: "#/components/schemas/String45"
description:
$ref: "#/components/schemas/String255Nullable"
command:
$ref: '#/components/schemas/String255'
required: [taskId, name]
JobTaskId:
$ref: '#/components/schemas/StringIntId'
JobTaskList:
type: array
minItems: 1
items:
$ref: '#/components/schemas/JobTask'
JobTaskListCreate:
type: array
minItems: 1
items:
$ref: '#/components/schemas/JobTaskId'
JobUpdate:
type: object
additionalProperties: false
minProperties: 1
properties:
name:
$ref: "#/components/schemas/String45"
description:
$ref: "#/components/schemas/String255Nullable"
tasks:
$ref: '#/components/schemas/JobTaskListCreate'
event:
$ref: '#/components/schemas/JobEventCreate'
Label:
additionalProperties: false
type: object
properties:
color:
$ref: '#/components/schemas/StringHexColor'
description:
$ref: '#/components/schemas/String255Nullable'
labelId:
$ref: '#/components/schemas/LabelId'
name:
$ref: '#/components/schemas/LabelName'
uses:
type: integer
required:
- name
- description
- color
- labelId
- uses
LabelBasic:
additionalProperties: false
type: object
properties:
labelId:
$ref: '#/components/schemas/LabelId'
name:
$ref: '#/components/schemas/LabelName'
required:
- name
- labelId
LabelBasicWithColor:
additionalProperties: false
type: object
properties:
color:
$ref: '#/components/schemas/StringHexColor'
labelId:
$ref: '#/components/schemas/LabelId'
name:
$ref: '#/components/schemas/LabelName'
required:
- name
- color
- labelId
LabelCreate:
additionalProperties: false
type: object
properties:
color:
$ref: '#/components/schemas/StringHexColor'
description:
$ref: '#/components/schemas/String255Nullable'
name:
$ref: '#/components/schemas/LabelName'
required:
- name
- description
- color
LabelId:
$ref: '#/components/schemas/StringUuid'
LabelIdNullable:
$ref: '#/components/schemas/StringUuidNullable'
LabelName:
maxLength: 16
minLength: 1
type: string
LabelUpdate:
additionalProperties: false
type: object
properties:
color:
$ref: '#/components/schemas/StringHexColor'
description:
$ref: '#/components/schemas/String255Nullable'
name:
$ref: '#/components/schemas/LabelName'
LastMigration:
type: integer
minimum: 0
LocationString:
type: string
MaxTs:
format: date-time
nullable: true
type: string
Metadata:
type: object
additionalProperties:
type: string
MetadataKey:
type: string
MetadataValue:
type: string
MetricsAggAsset:
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
benchmarkIds:
type: array
items:
$ref: '#/components/schemas/BenchmarkId'
fqdn:
$ref: '#/components/schemas/AssetFqdn'
ip:
$ref: '#/components/schemas/AssetIp'
labels:
type: array
items:
$ref: '#/components/schemas/LabelBasicWithColor'
mac:
$ref: '#/components/schemas/AssetMac'
name:
$ref: '#/components/schemas/AssetName'
noncomputing:
$ref: '#/components/schemas/AssetNoncomputing'
required:
- assetId
- name
- labels
- benchmarkIds
MetricsAggCollection:
type: object
properties:
assets:
type: integer
checklists:
type: integer
collectionId:
$ref: '#/components/schemas/CollectionId'
name:
$ref: '#/components/schemas/CollectionName'
stigs:
type: integer
required:
- collectionId
- name
- checklists
- assets
- stigs
MetricsAggLabel:
type: object
properties:
assets:
type: integer
labelId:
$ref: '#/components/schemas/LabelIdNullable'
name:
nullable: true
type: string
required:
- labelId
- name
- assets
MetricsAggMeta:
type: object
properties:
assets:
type: integer
checklists:
type: integer
collections:
type: integer
stigs:
type: integer
required:
- collections
- assets
- stigs
- checklists
MetricsAggStig:
type: object
properties:
assets:
type: integer
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
collections:
type: integer
marking:
$ref: '#/components/schemas/RevisionMarkingNullable'
revisionPinned:
type: boolean
revisionStr:
$ref: '#/components/schemas/RevisionStrRaw'
revisionDate:
$ref: "#/components/schemas/StringDateNullable"
ruleCount:
$ref: '#/components/schemas/RuleCount'
title:
$ref: '#/components/schemas/StigTitle'
required:
- benchmarkId
- marking
- title
- assets
- revisionStr
- revisionDate
- ruleCount
MetricsDetail:
properties:
metrics:
additionalProperties: false
type: object
properties:
assessed:
type: integer
assessedBySeverity:
additionalProperties: false
type: object
properties:
high:
type: integer
low:
type: integer
medium:
type: integer
required:
- low
- medium
- high
assessments:
type: integer
assessmentsBySeverity:
additionalProperties: false
type: object
properties:
high:
type: integer
low:
type: integer
medium:
type: integer
required:
- low
- medium
- high
findings:
additionalProperties: false
type: object
properties:
high:
type: integer
low:
type: integer
medium:
type: integer
required:
- low
- medium
- high
maxTouchTs:
$ref: '#/components/schemas/StringDateTimeNullable'
maxTs:
$ref: '#/components/schemas/MaxTs'
minTs:
$ref: '#/components/schemas/MinTs'
results:
additionalProperties: false
type: object
properties:
error:
$ref: '#/components/schemas/CollectionStatusCount'
fail:
$ref: '#/components/schemas/CollectionStatusCount'
fixed:
$ref: '#/components/schemas/CollectionStatusCount'
informational:
$ref: '#/components/schemas/CollectionStatusCount'
notapplicable:
$ref: '#/components/schemas/CollectionStatusCount'
notchecked:
$ref: '#/components/schemas/CollectionStatusCount'
notselected:
$ref: '#/components/schemas/CollectionStatusCount'
pass:
$ref: '#/components/schemas/CollectionStatusCount'
unknown:
$ref: '#/components/schemas/CollectionStatusCount'
required:
- notchecked
- notapplicable
- pass
- fail
- unknown
- error
- notselected
- informational
- fixed
statuses:
type: object
properties:
accepted:
$ref: '#/components/schemas/CollectionStatusCount'
rejected:
$ref: '#/components/schemas/CollectionStatusCount'
saved:
$ref: '#/components/schemas/CollectionStatusCount'
submitted:
$ref: '#/components/schemas/CollectionStatusCount'
required:
- assessed
- assessedBySeverity
- assessments
- assessmentsBySeverity
- findings
- minTs
- maxTs
- maxTouchTs
- results
- statuses
required:
- metrics
MetricsDetailAggAsset:
allOf:
- $ref: '#/components/schemas/MetricsAggAsset'
- $ref: '#/components/schemas/MetricsDetail'
MetricsDetailAggCollection:
allOf:
- $ref: '#/components/schemas/MetricsAggCollection'
- $ref: '#/components/schemas/MetricsDetail'
MetricsDetailAggLabel:
allOf:
- $ref: '#/components/schemas/MetricsAggLabel'
- $ref: '#/components/schemas/MetricsDetail'
MetricsDetailAggMeta:
allOf:
- $ref: '#/components/schemas/MetricsAggMeta'
- $ref: '#/components/schemas/MetricsDetail'
MetricsDetailAggStig:
allOf:
- $ref: '#/components/schemas/MetricsAggStig'
- $ref: '#/components/schemas/MetricsDetail'
MetricsDetailUnagg:
allOf:
- $ref: '#/components/schemas/MetricsUnagg'
- $ref: '#/components/schemas/MetricsDetail'
MetricsSummary:
properties:
metrics:
additionalProperties: false
type: object
properties:
assessed:
type: integer
assessedBySeverity:
additionalProperties: false
type: object
properties:
high:
type: integer
low:
type: integer
medium:
type: integer
required:
- low
- medium
- high
assessments:
type: integer
assessmentsBySeverity:
additionalProperties: false
type: object
properties:
high:
type: integer
low:
type: integer
medium:
type: integer
required:
- low
- medium
- high
findings:
additionalProperties: false
type: object
properties:
high:
type: integer
low:
type: integer
medium:
type: integer
required:
- low
- medium
- high
maxTouchTs:
$ref: '#/components/schemas/StringDateTimeNullable'
maxTs:
$ref: '#/components/schemas/MaxTs'
minTs:
$ref: '#/components/schemas/MinTs'
results:
additionalProperties: false
type: object
properties:
fail:
type: integer
notapplicable:
type: integer
other:
type: integer
pass:
type: integer
required:
- fail
- notapplicable
- other
- pass
statuses:
additionalProperties: false
type: object
properties:
accepted:
type: integer
rejected:
type: integer
saved:
type: integer
submitted:
type: integer
required:
- saved
- submitted
- accepted
- rejected
required:
- assessed
- assessedBySeverity
- assessments
- assessmentsBySeverity
- findings
- minTs
- maxTs
- maxTouchTs
- results
- statuses
required:
- metrics
MetricsSummaryAggAsset:
allOf:
- $ref: '#/components/schemas/MetricsAggAsset'
- $ref: '#/components/schemas/MetricsSummary'
MetricsSummaryAggCollection:
allOf:
- $ref: '#/components/schemas/MetricsAggCollection'
- $ref: '#/components/schemas/MetricsSummary'
MetricsSummaryAggLabel:
allOf:
- $ref: '#/components/schemas/MetricsAggLabel'
- $ref: '#/components/schemas/MetricsSummary'
MetricsSummaryAggMeta:
allOf:
- $ref: '#/components/schemas/MetricsAggMeta'
- $ref: '#/components/schemas/MetricsSummary'
MetricsSummaryAggStig:
allOf:
- $ref: '#/components/schemas/MetricsAggStig'
- $ref: '#/components/schemas/MetricsSummary'
MetricsSummaryUnagg:
allOf:
- $ref: '#/components/schemas/MetricsUnagg'
- $ref: '#/components/schemas/MetricsSummary'
MetricsUnagg:
type: object
properties:
assetId:
type: string
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
labels:
items:
$ref: '#/components/schemas/LabelBasicWithColor'
type: array
name:
type: string
revisionPinned:
type: boolean
revisionStr:
$ref: '#/components/schemas/RevisionStrRaw'
revisionDate:
$ref: "#/components/schemas/StringDateNullable"
title:
$ref: '#/components/schemas/StigTitle'
required:
- assetId
- name
- labels
- benchmarkId
- title
- revisionStr
- revisionDate
- revisionPinned
MinTs:
format: date-time
nullable: true
type: string
Owner:
oneOf:
- $ref: '#/components/schemas/UserBasicWithDisplayName'
- $ref: '#/components/schemas/UserGroup'
ParentControl:
$ref: '#/components/schemas/String255'
ResultEngine:
additionalProperties: false
type: object
nullable: true
properties:
checkContent:
$ref: '#/components/schemas/ResultEngineCheckContent'
overrides:
type: array
items:
$ref: '#/components/schemas/ResultEngineOverride'
minItems: 1
product:
$ref: '#/components/schemas/String255'
time:
$ref: '#/components/schemas/StringDateTime'
type:
$ref: '#/components/schemas/ResultEngineType'
version:
$ref: '#/components/schemas/VersionString'
required:
- product
- type
ResultEngineCheckContent:
additionalProperties: false
nullable: true
type: object
properties:
component:
$ref: '#/components/schemas/String255'
location:
$ref: '#/components/schemas/LocationString'
required:
- location
ResultEngineOverride:
additionalProperties: false
type: object
properties:
authority:
$ref: '#/components/schemas/String255'
newResult:
$ref: '#/components/schemas/ReviewResult'
oldResult:
$ref: '#/components/schemas/ReviewResult'
remark:
$ref: '#/components/schemas/String255'
time:
$ref: '#/components/schemas/StringDateTime'
required:
- authority
- oldResult
- newResult
ResultEngineType:
type: string
enum:
- scap
- script
- other
ReviewAsset:
type: object
properties:
autoResult:
type: boolean
comment:
$ref: '#/components/schemas/CommentaryString'
detail:
$ref: '#/components/schemas/CommentaryString'
history:
type: array
items:
$ref: '#/components/schemas/ReviewHistory'
metadata:
$ref: '#/components/schemas/Metadata'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
rule:
$ref: '#/components/schemas/RuleAbbr'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleIds:
type: array
items:
$ref: '#/components/schemas/RuleId'
status:
$ref: '#/components/schemas/ReviewStatusRead'
stigs:
type: array
items:
$ref: '#/components/schemas/CollectionStigWithIsDefault'
touchTs:
$ref: '#/components/schemas/StringDateTime'
ts:
$ref: '#/components/schemas/StringDateTime'
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
required:
- ruleId
- ruleIds
- result
- detail
- comment
- status
- userId
- username
- ts
- touchTs
ReviewAssetPost:
type: object
required:
- ruleId
- result
- detail
- comment
additionalProperties: false
properties:
ruleId:
$ref: '#/components/schemas/RuleId'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
detail:
$ref: '#/components/schemas/CommentaryStringNullable'
comment:
$ref: '#/components/schemas/CommentaryStringNullable'
autoResult:
type: boolean
metadata:
$ref: '#/components/schemas/Metadata'
status:
$ref: '#/components/schemas/ReviewStatusWrite'
ReviewAssetRulePatch:
additionalProperties: false
type: object
minProperties: 1
properties:
comment:
$ref: '#/components/schemas/CommentaryString'
detail:
$ref: '#/components/schemas/CommentaryString'
metadata:
$ref: '#/components/schemas/Metadata'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
status:
$ref: '#/components/schemas/ReviewStatusWrite'
ReviewAssetRulePut:
additionalProperties: false
type: object
properties:
autoResult:
type: boolean
comment:
$ref: '#/components/schemas/CommentaryStringNullable'
detail:
$ref: '#/components/schemas/CommentaryStringNullable'
metadata:
$ref: '#/components/schemas/Metadata'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
status:
$ref: '#/components/schemas/ReviewStatusWrite'
required:
- result
- detail
- comment
ReviewAssetRuleRead:
type: object
properties:
access:
$ref: '#/components/schemas/AclRuleAccess'
autoResult:
type: boolean
comment:
$ref: '#/components/schemas/CommentaryString'
detail:
$ref: '#/components/schemas/CommentaryString'
history:
type: array
items:
$ref: '#/components/schemas/ReviewHistory'
metadata:
$ref: '#/components/schemas/Metadata'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
rule:
$ref: '#/components/schemas/RuleAbbr'
ruleIds:
type: array
items:
$ref: '#/components/schemas/RuleId'
status:
$ref: '#/components/schemas/ReviewStatusRead'
stigs:
type: array
items:
$ref: '#/components/schemas/CollectionStigWithIsDefault'
touchTs:
$ref: '#/components/schemas/StringDateTime'
ts:
$ref: '#/components/schemas/StringDateTime'
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
required:
- access
- result
- detail
- comment
- userId
- username
- ts
- status
- touchTs
ReviewBatch:
additionalProperties: false
type: object
properties:
action:
$ref: '#/components/schemas/ReviewBatchAction'
assets:
$ref: '#/components/schemas/ReviewBatchAssetsCriteria'
dryRun:
default: false
type: boolean
rules:
$ref: '#/components/schemas/ReviewBatchRulesCriteria'
source:
$ref: '#/components/schemas/ReviewBatchSource'
updateFilters:
type: array
items:
$ref: '#/components/schemas/ReviewBatchFilter'
required:
- source
- assets
- rules
ReviewBatchAction:
type: string
enum:
- insert
- update
- merge
ReviewBatchAssetsCriteria:
oneOf:
- $ref: '#/components/schemas/ReviewBatchCriteria_AssetIds'
- $ref: '#/components/schemas/ReviewBatchCriteria_BenchmarkIds'
ReviewBatchCriteria_AssetIds:
additionalProperties: false
type: object
properties:
assetIds:
type: array
items:
$ref: '#/components/schemas/AssetId'
maxItems: 2500
minItems: 1
uniqueItems: true
required:
- assetIds
ReviewBatchCriteria_BenchmarkIds:
additionalProperties: false
type: object
properties:
benchmarkIds:
type: array
items:
$ref: '#/components/schemas/BenchmarkId'
maxItems: 50
minItems: 1
uniqueItems: true
required:
- benchmarkIds
ReviewBatchCriteria_RuleIds:
additionalProperties: false
type: object
properties:
ruleIds:
type: array
items:
$ref: '#/components/schemas/RuleId'
maxItems: 500
minItems: 1
uniqueItems: true
required:
- ruleIds
ReviewBatchFilter:
oneOf:
- $ref: '#/components/schemas/ReviewBatchFilter_String'
- $ref: '#/components/schemas/ReviewBatchFilter_Result'
- $ref: '#/components/schemas/ReviewBatchFilter_Status'
- $ref: '#/components/schemas/ReviewBatchFilter_Date'
- $ref: '#/components/schemas/ReviewBatchFilter_User'
ReviewBatchFilter_Date:
additionalProperties: false
type: object
properties:
condition:
default: equals
type: string
enum:
- equals
- lessThan
- greaterThan
field:
type: string
enum:
- ts
- statusTs
- touchTs
value:
$ref: '#/components/schemas/StringDateTime'
required:
- field
- value
ReviewBatchFilter_Result:
additionalProperties: false
type: object
properties:
condition:
default: equals
type: string
enum:
- equals
- notequal
field:
type: string
enum:
- result
value:
$ref: '#/components/schemas/ReviewResult'
required:
- field
- value
ReviewBatchFilter_Status:
additionalProperties: false
type: object
properties:
condition:
default: equals
type: string
enum:
- equals
- notequal
field:
type: string
enum:
- statusLabel
- status
value:
$ref: '#/components/schemas/ReviewStatusLabel'
required:
- field
- value
ReviewBatchFilter_String:
additionalProperties: false
type: object
properties:
condition:
default: equals
type: string
enum:
- equals
- contains
- beginsWith
- endsWith
field:
type: string
enum:
- detail
- comment
- statusText
value:
type: string
required:
- field
- value
ReviewBatchFilter_User:
additionalProperties: false
type: object
properties:
condition:
default: equals
type: string
enum:
- equals
- notequal
field:
type: string
enum:
- userId
- statusUserId
value:
$ref: '#/components/schemas/StringIntId'
required:
- field
- value
ReviewBatchResponse:
additionalProperties: false
type: object
properties:
failedValidation:
type: integer
inserted:
type: integer
updated:
type: integer
validationErrors:
type: array
items:
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
error:
$ref: '#/components/schemas/String255'
ruleId:
$ref: '#/components/schemas/RuleId'
required:
- inserted
- updated
- failedValidation
- validationErrors
ReviewBatchResponseDryRun:
additionalProperties: false
type: object
properties:
validationErrors:
type: array
items:
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
error:
$ref: '#/components/schemas/String255'
ruleId:
$ref: '#/components/schemas/RuleId'
willFailValidation:
type: integer
willInsert:
type: integer
willUpdate:
type: integer
required:
- willInsert
- willUpdate
- willFailValidation
- validationErrors
ReviewBatchRulesCriteria:
oneOf:
- $ref: '#/components/schemas/ReviewBatchCriteria_RuleIds'
- $ref: '#/components/schemas/ReviewBatchCriteria_BenchmarkIds'
ReviewBatchSource:
additionalProperties: false
type: object
properties:
review:
$ref: '#/components/schemas/ReviewAssetRulePatch'
required:
- review
ReviewHistory:
additionalProperties: false
type: object
properties:
autoResult:
type: boolean
comment:
$ref: '#/components/schemas/CommentaryString'
detail:
$ref: '#/components/schemas/CommentaryString'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
ruleId:
$ref: '#/components/schemas/RuleId'
status:
$ref: '#/components/schemas/ReviewStatusRead'
touchTs:
$ref: '#/components/schemas/StringDateTime'
ts:
$ref: '#/components/schemas/StringDateTime'
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
required:
- result
- detail
- comment
- status
- userId
- username
- ts
- touchTs
- ruleId
ReviewHistoryAsset:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/String255'
reviewHistories:
type: array
items:
$ref: '#/components/schemas/ReviewHistoryRule'
required:
- assetId
- reviewHistories
ReviewHistoryDeleted:
additionalProperties: false
type: object
properties:
HistoryEntriesDeleted:
type: integer
required:
- HistoryEntriesDeleted
ReviewHistoryRule:
additionalProperties: false
type: object
properties:
history:
type: array
items:
$ref: '#/components/schemas/ReviewHistory'
ruleId:
$ref: '#/components/schemas/RuleId'
required:
- ruleId
- history
ReviewHistoryStats:
additionalProperties: false
type: object
properties:
assetHistoryEntryCounts:
type: array
items:
$ref: '#/components/schemas/ReviewHistoryStatsAsset'
collectionHistoryEntryCount:
type: integer
oldestHistoryEntryDate:
$ref: '#/components/schemas/StringDateTime'
required:
- collectionHistoryEntryCount
- oldestHistoryEntryDate
ReviewHistoryStatsAsset:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/String255'
historyEntryCount:
type: integer
oldestHistoryEntry:
nullable: true
type: string
required:
- assetId
- historyEntryCount
- oldestHistoryEntry
ReviewPostResponse:
additionalProperties: false
type: object
properties:
affected:
type: object
properties:
inserted:
type: number
updated:
type: number
rejected:
type: array
items:
type: object
properties:
reason:
$ref: '#/components/schemas/String255'
ruleId:
$ref: '#/components/schemas/RuleId'
required:
- rejected
- affected
ReviewRead:
additionalProperties: false
type: object
properties:
access:
$ref: '#/components/schemas/AclRuleAccess'
assetId:
$ref: '#/components/schemas/StringIntId'
assetLabelIds:
type: array
items:
$ref: '#/components/schemas/LabelId'
assetLabels:
type: array
items:
$ref: '#/components/schemas/LabelBasicWithColor'
assetName:
$ref: '#/components/schemas/String255'
autoResult:
type: boolean
comment:
$ref: '#/components/schemas/CommentaryStringNullable'
detail:
$ref: '#/components/schemas/CommentaryStringNullable'
metadata:
$ref: '#/components/schemas/Metadata'
result:
$ref: '#/components/schemas/ReviewResult'
resultEngine:
$ref: '#/components/schemas/ResultEngine'
rule:
$ref: '#/components/schemas/RuleAbbr'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleIds:
type: array
items:
$ref: '#/components/schemas/RuleId'
status:
$ref: '#/components/schemas/ReviewStatusRead'
stigs:
type: array
items:
$ref: '#/components/schemas/CollectionStigWithIsDefault'
touchTs:
$ref: '#/components/schemas/StringDateTime'
ts:
$ref: '#/components/schemas/StringDateTime'
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
required:
- assetId
- assetName
- ruleId
- ruleIds
- result
- detail
- comment
- userId
- username
- ts
- touchTs
- status
ReviewResult:
enum:
- fail
- pass
- notapplicable
- notchecked
- unknown
- error
- notselected
- informational
- fixed
type: string
ReviewStatusLabel:
enum:
- saved
- submitted
- accepted
- rejected
type: string
ReviewStatusRead:
additionalProperties: false
type: object
properties:
label:
$ref: '#/components/schemas/ReviewStatusLabel'
text:
$ref: '#/components/schemas/StatusText'
ts:
$ref: '#/components/schemas/StringDateTime'
user:
$ref: '#/components/schemas/UserBasic'
required:
- label
- text
- user
- ts
ReviewStatusOption:
enum:
- "null"
- saved
- submitted
- accepted
type: string
ReviewStatusWrite:
oneOf:
- $ref: '#/components/schemas/ReviewStatusLabel'
- type: object
required:
- label
- text
additionalProperties: false
properties:
label:
$ref: '#/components/schemas/ReviewStatusLabel'
text:
$ref: '#/components/schemas/StatusText'
Revision:
additionalProperties: false
type: object
properties:
benchmarkDate:
$ref: '#/components/schemas/StringDateNullable'
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
collectionIds:
type: array
items:
$ref: '#/components/schemas/CollectionId'
marking:
$ref: '#/components/schemas/RevisionMarkingNullable'
release:
$ref: '#/components/schemas/RevisionRelease'
revisionStr:
$ref: '#/components/schemas/RevisionStr'
ruleCount:
$ref: '#/components/schemas/RuleCount'
status:
$ref: '#/components/schemas/RevisionStatus'
statusDate:
$ref: '#/components/schemas/StringDateNullable'
version:
$ref: '#/components/schemas/VersionString'
required:
- benchmarkId
- revisionStr
- version
- release
- benchmarkDate
- status
- statusDate
- ruleCount
- collectionIds
RevisionBasic:
additionalProperties: false
type: object
properties:
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
revisionStr:
$ref: '#/components/schemas/RevisionStr'
required:
- benchmarkId
- revisionStr
RevisionDate:
$ref: '#/components/schemas/StringDate'
RevisionMarkingNullable:
type: string
nullable: true
pattern: ^CUI|U|FOUO$
RevisionPost:
additionalProperties: false
type: object
properties:
action:
type: string
enum:
- inserted
- preserved
- replaced
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
revisionStr:
$ref: '#/components/schemas/RevisionStr'
marking:
$ref: '#/components/schemas/RevisionMarkingNullable'
required:
- benchmarkId
- revisionStr
- action
RevisionRelease:
$ref: '#/components/schemas/String45'
RevisionStatus:
$ref: '#/components/schemas/String45Nullable'
RevisionStr:
pattern: ^(V\d{1,3}R\d{1,3}(\.\d{1,3})?|latest)$
type: string
RevisionStrRaw:
pattern: ^(V\d{1,3}R\d{1,3}(\.\d{1,3})?)$
type: string
Roles:
type: string
enum: ["restricted", "full", "manage", "owner"]
RuleAbbr:
additionalProperties: false
type: object
properties:
ruleId:
$ref: '#/components/schemas/RuleId'
severity:
type: string
title:
$ref: '#/components/schemas/RuleTitle'
version:
$ref: '#/components/schemas/VersionString'
required:
- ruleId
- version
- title
- severity
RuleCount:
nullable: true
type: integer
RuleId:
$ref: '#/components/schemas/String45Nullable'
RuleProjected:
additionalProperties: false
type: object
properties:
ccis:
items:
$ref: '#/components/schemas/CciBasic'
type: array
check:
$ref: '#/components/schemas/Check'
detail:
additionalProperties: false
type: object
properties:
documentable:
nullable: true
type: string
falseNegatives:
nullable: true
type: string
falsePositives:
nullable: true
type: string
mitigationControl:
nullable: true
type: string
mitigations:
nullable: true
type: string
potentialImpacts:
nullable: true
type: string
responsibility:
nullable: true
type: string
severityOverrideGuidance:
nullable: true
type: string
thirdPartyTools:
nullable: true
type: string
vulnDiscussion:
nullable: true
type: string
weight:
nullable: true
type: string
fix:
$ref: '#/components/schemas/Fix'
groupId:
$ref: '#/components/schemas/GroupId'
groupTitle:
$ref: '#/components/schemas/GroupTitle'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleIds:
type: array
items:
$ref: '#/components/schemas/RuleId'
severity:
type: string
stigs:
type: array
items:
$ref: '#/components/schemas/RevisionBasic'
title:
$ref: '#/components/schemas/RuleTitle'
version:
$ref: '#/components/schemas/VersionString'
required:
- ruleId
- version
- title
- severity
- groupId
- groupTitle
RuleSeverity:
enum:
- high
- medium
- low
- null
type: string
nullable: true
RuleTitle:
$ref: '#/components/schemas/StringMax'
SCAPMap:
additionalProperties: false
type: object
properties:
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
scapBenchmarkId:
type: string
STIG:
additionalProperties: false
type: object
properties:
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
collectionIds:
type: array
items:
$ref: '#/components/schemas/CollectionId'
lastRevisionDate:
$ref: '#/components/schemas/StringDateNullable'
lastRevisionStr:
type: string
marking:
$ref: '#/components/schemas/RevisionMarkingNullable'
revisionStrs:
type: array
items:
$ref: '#/components/schemas/RevisionStrRaw'
revisions:
type: array
items:
$ref: '#/components/schemas/Revision'
ruleCount:
$ref: '#/components/schemas/RuleCount'
status:
$ref: '#/components/schemas/StatusText'
title:
$ref: '#/components/schemas/StigTitle'
required:
- benchmarkId
- title
- lastRevisionStr
- lastRevisionDate
- ruleCount
- collectionIds
State:
type: string
enum:
- starting
- available
- unavailable
- fail
- stop
StateResponse:
type: object
properties:
currentState:
$ref: '#/components/schemas/State'
since:
$ref: '#/components/schemas/StringDateTime'
dependencies:
$ref: '#/components/schemas/Dependencies'
endpoints:
$ref: '#/components/schemas/Endpoints'
StatusText:
$ref: '#/components/schemas/String511Nullable'
StigTitle:
$ref: '#/components/schemas/String255'
String20:
maxLength: 20
type: string
String20Nullable:
maxLength: 20
nullable: true
type: string
String255:
maxLength: 255
type: string
String255Nullable:
maxLength: 255
nullable: true
type: string
String32767:
maxLength: 32767
type: string
String32767Nullable:
maxLength: 32767
nullable: true
type: string
String45:
maxLength: 45
type: string
String45Nullable:
maxLength: 45
nullable: true
type: string
String511Nullable:
maxLength: 511
nullable: true
type: string
StringDate:
format: date
type: string
StringDateNullable:
format: date
nullable: true
type: string
StringDateTime:
format: date-time
type: string
StringDateTimeNullable:
format: date-time
nullable: true
type: string
StringHexColor:
example: aa33cc
pattern: ^[a-fA-F0-9]{6}$
type: string
StringIntId:
maxLength: 10
minLength: 1
pattern: ^[0-9]{1,10}$
type: string
StringIntIdNullable:
nullable: true
maxLength: 10
minLength: 1
pattern: ^[0-9]{1,10}$
type: string
StringMax:
maxLength: 16777215
type: string
StringUuid:
pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
type: string
StringUuidNullable:
nullable: true
pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
type: string
TextRefNist:
$ref: '#/components/schemas/String255'
UnreviewedAsset:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
labels:
type: array
items:
$ref: '#/components/schemas/LabelBasic'
name:
$ref: '#/components/schemas/AssetName'
unreviewed:
type: array
items:
$ref: '#/components/schemas/UnreviewedAssetItem'
required:
- assetId
- name
- labels
- unreviewed
UnreviewedAssetItem:
additionalProperties: false
type: object
properties:
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
groupId:
$ref: '#/components/schemas/GroupId'
groupTitle:
$ref: '#/components/schemas/GroupTitle'
result:
$ref: '#/components/schemas/ChecklistResultUnreviewed'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleTitle:
$ref: '#/components/schemas/RuleTitle'
severity:
$ref: '#/components/schemas/RuleSeverity'
required:
- result
- ruleId
- groupId
- benchmarkId
UnreviewedRule:
additionalProperties: false
type: object
properties:
benchmarkId:
$ref: '#/components/schemas/BenchmarkId'
groupId:
$ref: '#/components/schemas/GroupId'
groupTitle:
$ref: '#/components/schemas/GroupTitle'
ruleId:
$ref: '#/components/schemas/RuleId'
ruleTitle:
$ref: '#/components/schemas/RuleTitle'
severity:
$ref: '#/components/schemas/RuleSeverity'
unreviewed:
type: array
items:
$ref: '#/components/schemas/UnreviewedRuleItem'
required:
- ruleId
- groupId
- benchmarkId
- unreviewed
UnreviewedRuleItem:
additionalProperties: false
type: object
properties:
assetId:
$ref: '#/components/schemas/AssetId'
labels:
type: array
items:
$ref: '#/components/schemas/LabelBasic'
name:
$ref: '#/components/schemas/AssetName'
result:
$ref: '#/components/schemas/ChecklistResultUnreviewed'
required:
- result
- assetId
- name
- labels
UserBasic:
additionalProperties: false
type: object
properties:
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
roleId:
$ref: '#/components/schemas/RoleId'
required:
- userId
- username
UserBasicNullable:
nullable: true
additionalProperties: false
type: object
properties:
userId:
$ref: '#/components/schemas/UserIdNullable'
username:
$ref: '#/components/schemas/UsernameNullable'
required:
- userId
- username
UserBasicWithDisplayName:
additionalProperties: false
type: object
properties:
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
displayName:
$ref: '#/components/schemas/DisplayName'
required:
- userId
- username
- displayName
UserCreateOrReplace:
additionalProperties: false
type: object
properties:
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrant'
uniqueItems: true
userGroups:
type: array
items:
$ref: '#/components/schemas/UserGroupId'
uniqueItems: true
default: []
username:
$ref: '#/components/schemas/Username'
status:
$ref: '#/components/schemas/UserStatus'
required:
- username
- collectionGrants
UserGrant:
type: object
required:
- userId
- roleId
properties:
userId:
$ref: '#/components/schemas/UserId'
roleId:
$ref: '#/components/schemas/RoleId'
UserGrantProjected:
additionalProperties: false
type: object
properties:
grantId:
$ref: '#/components/schemas/GrantId'
roleId:
$ref: '#/components/schemas/RoleId'
user:
$ref: '#/components/schemas/UserBasicWithDisplayName'
required:
- user
- roleId
UserGroup:
type: object
additionalProperties: false
required:
- userGroupId
- name
- description
properties:
userGroupId:
$ref: '#/components/schemas/UserGroupId'
name:
$ref: '#/components/schemas/String255'
description:
$ref: '#/components/schemas/String255Nullable'
UserGroupBasic:
type: object
additionalProperties: false
required:
- userGroupId
- name
properties:
userGroupId:
$ref: '#/components/schemas/UserGroupId'
name:
$ref: '#/components/schemas/String255'
roleId:
$ref: '#/components/schemas/RoleId'
UserGroupCollectionGrant:
additionalProperties: false
type: object
properties:
roleId:
$ref: '#/components/schemas/RoleId'
collection:
type: object
properties:
collectionId:
$ref: '#/components/schemas/CollectionId'
name:
$ref: '#/components/schemas/CollectionName'
UserGroupGrant:
type: object
required:
- userGroupId
- roleId
additionalProperties: false
properties:
userGroupId:
$ref: '#/components/schemas/UserGroupId'
roleId:
type: integer
minimum: 1
maximum: 4
UserGroupGrantProjected:
type: object
required:
- userGroup
- roleId
additionalProperties: false
properties:
grantId:
$ref: '#/components/schemas/GrantId'
userGroup:
$ref: '#/components/schemas/UserGroup'
roleId:
$ref: '#/components/schemas/RoleId'
UserGroupId:
$ref: '#/components/schemas/StringIntId'
UserGroupPatch:
type: object
additionalProperties: false
minProperties: 1
properties:
name:
$ref: '#/components/schemas/String255'
description:
$ref: '#/components/schemas/String255Nullable'
userIds:
type: array
items:
$ref: '#/components/schemas/UserId'
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrant'
uniqueItems: true
UserGroupProjected:
type: object
additionalProperties: false
required:
- userGroupId
- name
- description
properties:
userGroupId:
$ref: '#/components/schemas/UserGroupId'
name:
$ref: '#/components/schemas/String255'
description:
$ref: '#/components/schemas/String255Nullable'
users:
type: array
items:
$ref: '#/components/schemas/UserBasicWithDisplayName'
collectionGrants:
type: array
items:
$ref: '#/components/schemas/UserGroupCollectionGrant'
attributions:
$ref: '#/components/schemas/Attributions'
UserGroupPostOrPut:
type: object
additionalProperties: false
required:
- name
properties:
name:
$ref: '#/components/schemas/String255'
description:
$ref: '#/components/schemas/String255Nullable'
userIds:
type: array
uniqueItems: true
items:
$ref: '#/components/schemas/UserId'
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrant'
uniqueItems: true
UserId:
$ref: '#/components/schemas/StringIntId'
UserIdNullable:
$ref: '#/components/schemas/StringIntIdNullable'
UserLastAccess:
$ref: '#/components/schemas/IntegerMinimumZeroNullable'
UserPatch:
additionalProperties: false
minProperties: 1
type: object
properties:
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrant'
uniqueItems: true
userGroups:
type: array
items:
$ref: '#/components/schemas/UserGroupId'
uniqueItems: true
username:
$ref: '#/components/schemas/Username'
status:
$ref: '#/components/schemas/UserStatus'
UserPost:
additionalProperties: false
type: object
properties:
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrant'
uniqueItems: true
userGroups:
type: array
items:
$ref: '#/components/schemas/UserGroupId'
uniqueItems: true
username:
$ref: '#/components/schemas/Username'
required:
- collectionGrants
- username
UserPut:
additionalProperties: false
type: object
properties:
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrant'
uniqueItems: true
userGroups:
type: array
items:
$ref: '#/components/schemas/UserGroupId'
uniqueItems: true
username:
$ref: '#/components/schemas/Username'
status:
$ref: '#/components/schemas/UserStatus'
required:
- collectionGrants
- username
UserPrivileges:
type: object
additionalProperties: false
properties:
admin:
type: boolean
create_collection:
type: boolean
UserProjected:
additionalProperties: false
type: object
properties:
collectionGrants:
type: array
items:
$ref: '#/components/schemas/CollectionGrantProjected'
displayName:
$ref: '#/components/schemas/DisplayName'
email:
nullable: true
type: string
lastAccess:
$ref: '#/components/schemas/UserLastAccess'
privileges:
$ref: '#/components/schemas/UserPrivileges'
statistics:
$ref: '#/components/schemas/UserStatistics'
status:
$ref: '#/components/schemas/UserStatus'
statusDate:
$ref: '#/components/schemas/UserStatusDate'
statusUser:
$ref: '#/components/schemas/UserStatusUser'
userGroups:
type: array
items:
$ref: '#/components/schemas/UserGroupBasic'
userId:
$ref: '#/components/schemas/UserId'
username:
$ref: '#/components/schemas/Username'
webPreferences:
$ref: '#/components/schemas/WebPreferences'
required:
- userId
- username
- displayName
- email
- lastAccess
UserStatus:
type: string
enum:
- available
- unavailable
UserStatusDate:
$ref: '#/components/schemas/StringDateTime'
UserStatusUser:
$ref: '#/components/schemas/StringIntIdNullable'
UserStatistics:
additionalProperties: false
type: object
properties:
collectionGrantCount:
type: integer
created:
$ref: '#/components/schemas/Created'
lastClaims:
type: object
required:
- created
- collectionGrantCount
- lastClaims
Username:
$ref: '#/components/schemas/String255'
UsernameNullable:
$ref: '#/components/schemas/String255Nullable'
WebPreferences:
type: object
properties:
darkMode:
type: boolean
lastWhatsNew:
type: string
format: date
additionalProperties: false
required:
- darkMode
- lastWhatsNew
WebPreferencesPatch:
type: object
properties:
darkMode:
type: boolean
lastWhatsNew:
type: string
format: date
additionalProperties: false
minProperties: 1
Version:
description: |
Semver as defined by the BNF at semver.org
pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-([0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?(?:\+([0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?$
type: string
VersionString:
$ref: '#/components/schemas/String255'
parameters:
AppDataFormatQuery:
name: format
in: query
description: The format of the appdata
schema:
$ref: '#/components/schemas/AppDataFormat'
AssetIdArrayQuery:
name: assetId
in: query
description: A query parameter that identifies a list of Assets
schema:
type: array
uniqueItems: true
minItems: 1
items:
$ref: '#/components/schemas/AssetId'
AssetIdPath:
name: assetId
in: path
description: A path parameter that identifies an Asset
required: true
schema:
$ref: '#/components/schemas/AssetId'
AssetIdQuery:
name: assetId
in: query
description: A query parameter that identifies an Asset
schema:
$ref: '#/components/schemas/AssetId'
AssetProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- statusStats
- stigs
BenchmarkIdArrayQuery:
name: benchmarkId
in: query
description: Filter by one or more benchmarkIds
schema:
type: array
uniqueItems: true
minItems: 1
items:
$ref: '#/components/schemas/BenchmarkId'
BenchmarkIdPath:
name: benchmarkId
in: path
description: A path parameter that identifies a STIG
required: true
schema:
$ref: '#/components/schemas/BenchmarkId'
BenchmarkIdQuery:
name: benchmarkId
in: query
description: A query parameter that identifies a STIG
schema:
$ref: '#/components/schemas/BenchmarkId'
CciProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- emassAp
- stigs
- references
CciQuery:
name: cci
in: query
description: A query parameter that identifies a CCI
schema:
$ref: '#/components/schemas/CciString'
CklModeQuery:
name: mode
in: query
description: A query parameter that describes the CKL mode
schema:
type: string
default: mono
enum:
- multi
- mono
CollectionIdPath:
name: collectionId
in: path
description: A path parameter that identifies a Collection
required: true
schema:
$ref: '#/components/schemas/CollectionId'
CollectionIdQuery:
name: collectionId
required: true
in: query
description: A query parameter that identifies a Collection
schema:
$ref: '#/components/schemas/CollectionId'
CollectionIdArrayQuery:
name: collectionId
required: false
in: query
description: Filter by one or more collectionIds
schema:
type: array
uniqueItems: true
minItems: 1
items:
$ref: '#/components/schemas/CollectionId'
CollectionProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- assets
- grants
- users
- owners
- statistics
- stigs
- labels
CollectionsProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- owners
- statistics
CollectionStigProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- assets
DryRunQuery:
name: dryRun
in: query
description: If set to `true`, performs validation without persisting data.
required: false
schema:
type: boolean
DstCollectionIdPath:
name: dstCollectionId
in: path
description: A path parameter that identifies a Collection
required: true
schema:
$ref: '#/components/schemas/CollectionId'
EndDateQuery:
name: endDate
in: query
description: History entries with a timestamp after the specified end date.
schema:
$ref: '#/components/schemas/StringDate'
ElevateQuery:
name: elevate
in: query
description: Elevate the user context for this request if user is permitted (canAdmin)
schema:
type: boolean
default: false
FindingAggregatorQuery:
name: aggregator
required: true
in: query
description: Aggregate the findings on this property
schema:
type: string
minLength: 1
enum:
- ruleId
- groupId
- cci
FindingProjectionQuery:
name: projection
in: query
description: Optional properties to return
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- assets
- groups
- rules
- stigs
- ccis
ForceQuery:
name: force
in: query
description: Force an action, such as a delete, that would otherwise not be permitted
schema:
type: boolean
default: false
GrantIdPath:
name: grantId
in: path
description: A path parameter that identifies a Grant
required: true
schema:
$ref: '#/components/schemas/GrantId'
GroupIdQuery:
name: groupId
in: query
description: A query parameter that identifies a Group
schema:
$ref: '#/components/schemas/GroupId'
GroupProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- rules
JobIdPath:
name: jobId
in: path
description: A path parameter that identifies a Job
required: true
schema:
$ref: '#/components/schemas/JobId'
JobRunIdPath:
name: runId
in: path
description: A path parameter that identifies a Job Run
required: true
schema:
$ref: '#/components/schemas/JobRunId'
JsonPathQuery:
name: jsonpath
in: query
description: A JSONPath expression
schema:
$ref: '#/components/schemas/String255'
LabelIdPath:
name: labelId
in: path
required: true
description: A path parameter that specifies a Label
schema:
$ref: '#/components/schemas/LabelId'
LabelIdQuery:
name: labelId
in: query
description: Selects Assets by labelId
schema:
type: array
uniqueItems: true
minItems: 1
items:
$ref: '#/components/schemas/LabelId'
LabelMatchQuery:
name: labelMatch
in: query
description: Selectes Assets without labels
schema:
type: string
enum:
- 'null'
LabelNameQuery:
name: labelName
in: query
description: Selectes Assets by label name
schema:
type: array
uniqueItems: true
minItems: 1
items:
$ref: '#/components/schemas/LabelName'
MetadataKeyPath:
name: key
in: path
required: true
description: A path parameter that specifies a metadata key
schema:
pattern: '^([\w\.]+)$'
type: string
MetadataQuery:
name: metadata
in: query
description: A query parameter that specifies metadata key:value pairs to select matching Objects
schema:
type: array
uniqueItems: true
minItems: 1
items:
pattern: '^([\w\.]+:.*?)$'
type: string
MetricsFormatQuery:
name: format
in: query
description: The format of the response body
schema:
type: string
default: 'json'
enum:
- json
- csv
NameQuery:
name: name
in: query
description: Matches against the name according to the `name-match` parameter
schema:
type: string
NameMatchQuery:
name: name-match
in: query
description: How to match against the `name` parameter
schema:
type: string
default: exact
enum:
- exact
- startsWith
- endsWith
- contains
PoamAggregatorQuery:
name: aggregator
required: true
in: query
description: Aggregate the findings on this property
schema:
type: string
enum:
- ruleId
- groupId
PoamFormatQuery:
name: format
in: query
description: Value for POAM format (ie. EMASS, MCCAST)
schema:
type: string
enum:
- EMASS
- MCCAST
default: EMASS
PrivilegeQuery:
name: privilege
in: query
description: Selects Users with the specified privilege
schema:
type: string
enum:
- admin
- create_collection
RetentionDateQuery:
name: retentionDate
in: query
description: Delete history entries with a timestamp earlier than the specified retention date.
required: true
schema:
$ref: '#/components/schemas/StringDate'
ReviewProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- metadata
- rule
- stigs
- history
ReviewHistoryStatsProjectionQuery:
name: projection
in: query
description: Return review history statistics with the specified level of granularity.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- asset
ReviewsProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- metadata
- rule
- stigs
ReviewResultQuery:
name: result
in: query
schema:
$ref: '#/components/schemas/ReviewResult'
ReviewRulesQuery:
name: rules
in: query
description:
default - rules from the default revision of a STIG in the Collection. mapped - rules from any version of a STIG assigned to the Asset
schema:
type: string
default: default-mapped
enum:
- all
- default
- default-mapped
- mapped
- not-default
- not-default-mapped
- not-mapped
ReviewStatusQuery:
name: status
in: query
schema:
$ref: '#/components/schemas/ReviewStatusLabel'
RevisionIdArrayQuery:
name: revisionId
in: query
description: Filter by one or more revisionIds (benchmarkId-version-release) If Revision specified is not the default rev for at least one Collection, response will be empty.
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
RevisionStrPath:
name: revisionStr
in: path
description: A path parameter that identifies a STIG revision [V{version_num}R{release_num} | 'latest' ]
required: true
schema:
$ref: '#/components/schemas/RevisionStr'
RuleIdPath:
name: ruleId
in: path
description: A path parameter that identifies a Rule
required: true
schema:
$ref: '#/components/schemas/RuleId'
RuleIdQuery:
name: ruleId
in: query
description: Selects Reviews of a Rule
schema:
$ref: '#/components/schemas/RuleId'
RuleProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- detail
- ccis
- check
- fix
- ruleIds
- stigs
RuleSeverityQuery:
name: severity
in: query
description: Selects Rules with the specified severity
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
maxItems: 2
items:
$ref: '#/components/schemas/RuleSeverity'
RunSequenceQuery:
name: after-seq
in: query
description: The starting sequence number of the run output to retrieve. If not specified, all run output is returned.
schema:
type: integer
minimum: 0
StartDateQuery:
name: startDate
in: query
description: History entries with a timestamp before the specified start date.
schema:
$ref: '#/components/schemas/StringDate'
StigProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
items:
type: string
enum:
- revisions
UnreviewedAssetsProjectionQuery:
name: projection
in: query
description: Additional properties to include in the `unreviewed` objects.
style: form
explode: true
schema:
type: array
items:
type: string
enum:
- ruleTitle
- groupTitle
UnreviewedRulesProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
items:
type: string
enum:
- ruleTitle
- groupTitle
UserGroupIdPath:
name: userGroupId
in: path
description: A path parameter that identifies a User Group
required: true
schema:
$ref: '#/components/schemas/UserGroupId'
UserGroupProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
items:
type: string
enum:
- users
- collections
- collectionGrants
- attributions
UserIdPath:
name: userId
in: path
description: A path parameter that identifies a User
required: true
schema:
$ref: '#/components/schemas/UserId'
UserIdQuery:
name: userId
in: query
description: A query parameter that identifies a User
schema:
$ref: '#/components/schemas/UserId'
UsernameQuery:
name: username
in: query
description: Matches against the username according to the `username-match` parameter
schema:
$ref: '#/components/schemas/Username'
UsernameMatchQuery:
name: username-match
in: query
description: How to match against the `username` parameter
schema:
type: string
default: exact
enum:
- exact
- startsWith
- endsWith
- contains
UserStatusQuery:
name: status
in: query
description: A query parameter that identifies a UserStatus
schema:
$ref: '#/components/schemas/UserStatus'
UserPreferenceQuery:
name: projection
in: query
description: A query parameter that identifies a UserPreference
schema:
type: string
enum:
- webPreferences
UserProjectionQuery:
name: projection
in: query
description: Additional properties to include in the response.
style: form
explode: true
schema:
type: array
uniqueItems: true
minItems: 1
items:
type: string
enum:
- collectionGrants
- statistics
- userGroups
- webPreferences
responses:
Forbidden:
description: The requesting User does not have access rights to the content
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
securitySchemes:
oauth:
type: openIdConnect
openIdConnectUrl: http://localhost:8080/realms/stigman/.well-known/openid-configuration
# supported oauth scopes:
# - stig-manager
# - 'stig-manager:op'
# - 'stig-manager:op:read'
# - 'stig-manager:stig'
# - 'stig-manager:stig:read'
# - 'stig-manager:collection'
# - 'stig-manager:collection:read'
# - 'stig-manager:user'
# - 'stig-manager:user:read'
================================================
FILE: api/source/tls/README.md
================================================
Optional: Place your TLS/SSL certificates and keys here
================================================
FILE: api/source/utils/PoolMonitor.js
================================================
/**
* Class representing a PoolMonitor.
* Monitors the database connection status and determines if the API should enter an Unavailable state.
*/
class PoolMonitor {
/**
* Creates an instance of PoolMonitor.
* @param {Object} options - Constructor options.
* @param {Object} options.pool - The mysql2 PromisePool object.
* @param {Object} options.state - The API state object.
* @param {number} [options.retryInterval=40000] - The interval at which to execute the retryFn (in milliseconds).
* @param {Function} [options.retryFn=async ()=>{})] - The retry function.
* @throws {Error} Throws an error if pool or state is not provided.
*/
constructor({ pool, state, retryInterval = 40000, retryFn = async () => {} }) {
if (!pool || !state) {
throw new Error('PoolMonitor requires a pool and state object.')
}
this.pool = pool
this.state = state
this.retryInterval = retryInterval
this.retryFn = retryFn
this.retries = 0
this.pool.on('remove', this.onRemove.bind(this))
}
/**
* Handler for the pool's remove event.
* Sets the database status based on the pool's connection status.
*/
onRemove() {
const poolIsEmpty = this.pool.pool._allConnections.length === 0
if (poolIsEmpty && this.state.dependencyStatus.db) {
this.state.setDbStatus(false)
this.retries = 0
this.timeoutId = setTimeout(this.callRetryFn.bind(this), this.retryInterval)
}
}
/**
* Calls the instance's retry function.
* If successful, sets the database status to true and clears the retry interval.
* If unsuccessful, increments the retry count and schedules the next retry.
*/
async callRetryFn() {
try {
await this.retryFn()
this.state.setDbStatus(true)
}
catch (error) {
this.retries++
this.timeoutId = setTimeout(this.callRetryFn.bind(this), this.retryInterval)
}
}
}
module.exports = PoolMonitor
================================================
FILE: api/source/utils/asyncApiValidator.js
================================================
/**
* Lightweight AsyncAPI 3.0 message validator.
*
* Builds AJV-compiled validators from an AsyncAPI 3.0 YAML spec file.
* Provides a validate(key, payload, channel, operation) method for runtime
* message validation on any channel defined in the spec.
*
* Parser limitations (not AsyncAPI requirements — these are constraints of this
* module's simplified parsing approach):
* - Only handles AsyncAPI 3.0 (not 2.x, which has a different structure)
* - Spec must be a single YAML file (no external file $ref references)
* - Circular $ref references will throw an error (detected via visited set)
* - $ref pointers are only resolved within components/schemas
* - Each message must have a `name` field (AsyncAPI makes this optional; we
* use it as the validation lookup key, same role as asyncapi-validator's
* msgIdentifier option)
* - Message payloads must use a $ref to components/schemas (inline schemas
* are not supported)
* - Operations must include a `messages` array (AsyncAPI makes this optional,
* defaulting to all channel messages; we require it to be explicit)
*
* Background:
* Replaces the asyncapi-validator npm package, which was removed because its
* dependency chain (asyncapi-validator -> @asyncapi/parser -> @stoplight/spectral-core
* -> minimatch@3.1.2) included a version of minimatch vulnerable to CVE-2026-27904
* (catastrophic regex backtracking). The asyncapi-validator package was not receiving
* regular updates, and all alternative AsyncAPI message validation packages
* (e.g., asyncapi-validation) also depend on @asyncapi/parser, so they would
* introduce the same vulnerability.
*
* Why js-yaml instead of @asyncapi/parser:
* @asyncapi/parser is a full-featured AsyncAPI spec parser that validates the spec
* itself, resolves multi-file $ref chains, handles protocol bindings, and produces
* a rich document model. Our specs are single self-contained files with only
* intra-file $ref references and simple JSON schemas. js-yaml gives us the parsed
* YAML object, and we resolve the $ref chains ourselves in ~15 lines. This
* eliminates the entire @asyncapi/parser dependency tree (~160 packages) while
* preserving identical validation behavior.
*
* Spec validation:
* This module does not validate that the YAML file is a valid AsyncAPI document.
* It trusts the spec structure. To validate a spec against the AsyncAPI schema,
* use the AsyncAPI CLI (also enforced in CI via api-spec-validation.yml):
* npx @asyncapi/cli validate api/source/specification/log-socket.yaml
*/
const Ajv = require('ajv')
const addFormats = require('ajv-formats')
const fs = require('node:fs')
const jsYaml = require('js-yaml')
class AsyncApiValidator {
constructor(channels, ajv) {
this._channels = channels
this._ajv = ajv
}
/**
* Validate a message payload against the schema defined in the AsyncAPI spec.
* @param {string} key - Message name as defined in the spec (e.g., 'authorize', 'log')
* @param {object} payload - The message object to validate
* @param {string} channel - Channel name (e.g., 'logStream')
* @param {string} operation - 'send' or 'receive'
* @throws {Error} if validation fails or the key/channel/operation is not found
*/
validate(key, payload, channel, operation) {
const channelDef = this._channels[channel]
if (!channelDef) {
throw new Error(`channel "${channel}" not found`)
}
const operationDef = channelDef[operation]
if (!operationDef) {
throw new Error(`operation "${operation}" not found on channel "${channel}"`)
}
const validateFn = operationDef[key]
if (!validateFn) {
throw new Error(`message "${key}" on channel "${channel}" operation "${operation}" not found`)
}
const valid = validateFn(payload)
if (!valid) {
throw new Error(this._ajv.errorsText(validateFn.errors))
}
return true
}
}
/**
* Recursively resolve $ref pointers within a JSON Schema object.
* Only handles intra-file references to components/schemas.
* Tracks visited refs to detect circular references.
*/
function resolveRefs(node, schemas, visited = new Set()) {
if (!node || typeof node !== 'object') return node
if (node.$ref) {
const refName = node.$ref.split('/').pop()
if (visited.has(refName)) {
throw new Error(`Circular $ref detected: ${refName}`)
}
if (!schemas[refName]) {
throw new Error(`Dangling $ref: "${node.$ref}" not found in components/schemas`)
}
return resolveRefs(schemas[refName], schemas, new Set(visited).add(refName))
}
if (Array.isArray(node)) {
return node.map(item => resolveRefs(item, schemas, visited))
}
const resolved = {}
for (const [key, value] of Object.entries(node)) {
resolved[key] = resolveRefs(value, schemas, visited)
}
return resolved
}
/**
* Build an AsyncApiValidator from an AsyncAPI 3.0 YAML spec file.
* Parses the spec, resolves $ref chains, and pre-compiles AJV validators
* for each message type grouped by channel and operation (send/receive).
*
* Messages are keyed by their `name` field in the spec. See the module-level
* JSDoc for full spec requirements.
*
* @param {string} schemaPath - Absolute path to the AsyncAPI YAML file
* @returns {AsyncApiValidator}
*/
function fromSource(schemaPath) {
const yamlContent = fs.readFileSync(schemaPath, 'utf8')
const spec = jsYaml.load(yamlContent)
const ajv = new Ajv({ allErrors: true, strict: false, unicodeRegExp: false })
addFormats(ajv)
const schemas = spec.components.schemas
const messages = spec.components.messages
const channels = {}
for (const operation of Object.values(spec.operations)) {
const channelName = operation.channel.$ref.split('/').pop()
const action = operation.action
for (const msgRefObj of operation.messages) {
// Resolve through channels to components/messages
const refParts = msgRefObj.$ref.split('/')
// e.g., '#/channels/logStream/messages/AuthorizeResponse'
const channelMsgEntry = spec.channels[refParts[2]].messages[refParts[4]]
const componentMsgName = channelMsgEntry.$ref.split('/').pop()
const message = messages[componentMsgName]
const msgKey = message.name
const schemaName = message.payload.$ref.split('/').pop()
const payloadSchema = resolveRefs(schemas[schemaName], schemas)
const validateFn = ajv.compile(payloadSchema)
channels[channelName] ??= {}
channels[channelName][action] ??= {}
channels[channelName][action][msgKey] = validateFn
}
}
return new AsyncApiValidator(channels, ajv)
}
module.exports = { fromSource }
================================================
FILE: api/source/utils/auth.js
================================================
const config = require('./config')
const logger = require('./logger')
const jwt = require('jsonwebtoken')
const retry = require('async-retry')
const UserService = require(`../service/UserService`)
const SmError = require('./error')
const state = require('./state')
const JWKSCache = require('./jwksCache')
const { Agent, fetch } = require('undici');
const fs = require('node:fs');
const path = require('node:path')
let jwksCache
let initAttempt = 0
// Helper function to safely traverse object properties using dot notation
function getClaimByPath(obj, path = config.oauth.claims.privilegesRaw) {
if (!obj || !path) return [];
try {
// Split the path by dots and traverse the object
const keys = path.split('.');
let value = obj;
for (const key of keys) {
if (value == null) return [];
value = value[key];
}
return value || [];
} catch {
return [];
}
}
// Helper function to decode and validate the JWT structure
function decodeToken(tokenJWT) {
const tokenObj = jwt.decode(tokenJWT, { complete: true })
if (!tokenObj) {
throw new SmError.AuthorizeError("Token is not valid JWT")
}
return tokenObj
}
// Helper function to check for insecure kids
function checkInsecureKid(tokenObj) {
if (!config.oauth.allowInsecureTokens && config.oauth.insecureKids.includes(tokenObj.header.kid)) {
throw new SmError.InsecureTokenError(`Insecure kid found: ${tokenObj.header.kid}`)
}
}
// Helper function to retrieve the signing key
async function getSigningKey(tokenObj) {
let signingKey = jwksCache.getKey(tokenObj.header.kid)
if (signingKey === null) {
const result = await jwksCache.refreshCache(false) // Will not retry on failure
if (result) {
signingKey = jwksCache.getKey(tokenObj.header.kid)
}
if (!result || !signingKey) {
signingKey = 'unknown'
jwksCache.setKey(tokenObj.header.kid, signingKey)
logger.writeWarn('auth', 'unknownKid', { kid: tokenObj.header.kid })
}
}
if (signingKey === 'unknown') {
throw new SmError.SigningKeyNotFoundError(`Signing key unknown for kid: ${tokenObj.header.kid}`)
}
return signingKey
}
// Helper function to verify the token
function verifyToken(tokenJWT, signingKey) {
const options = config.oauth.audienceValue ? {audience: config.oauth.audienceValue} : undefined
try {
jwt.verify(tokenJWT, signingKey, options)
} catch (e) {
throw new SmError.AuthorizeError(e.message)
}
}
// express middleware to validate token
const validateToken = async function (req, res, next) {
try {
const tokenJWT = getBearerToken(req)
if (tokenJWT) {
const tokenObj = decodeToken(tokenJWT)
checkInsecureKid(tokenObj)
const signingKey = await getSigningKey(tokenObj)
verifyToken(tokenJWT, signingKey)
req.access_token = tokenObj.payload
req.bearer = tokenJWT
}
next()
} catch (e) {
next(e)
}
}
// express middleware to setup user object, expects to be called after validateToken()
const setupUser = async function (req, res, next) {
try {
if (req.access_token) {
// Get decoded JWT payload from request
const tokenPayload = req.access_token
// Get username from configured claims in token, or fall back through precedence list.
const usernamePrecedence = [config.oauth.claims.username, "preferred_username", config.oauth.claims.servicename, "azp", "client_id", "clientId"]
const username = tokenPayload[usernamePrecedence.find(element => !!tokenPayload[element])]
// If no username found, throw Privilege error
if (username === undefined) {
throw new SmError.AuthorizeError("No token claim mappable to username found")
}
const userObject = await UserService.getUserObject(username) ?? {username}
if (userObject.status === 'unavailable') {
throw new SmError.UserUnavailableError()
}
const refreshFields = {}
let now = new Date().toUTCString()
now = new Date(now).getTime()
now = now / 1000 | 0 //https://stackoverflow.com/questions/7487977/using-bitwise-or-0-to-floor-a-number
if (!userObject?.lastAccess || now - userObject?.lastAccess >= config.settings.lastAccessResolution) {
refreshFields.lastAccess = now
}
if (!userObject?.lastClaims || tokenPayload[config.oauth.claims.assertion] !== userObject?.lastClaims?.[config.oauth.claims.assertion]) {
refreshFields.lastClaims = JSON.stringify(tokenPayload)
}
if (refreshFields.lastAccess || refreshFields.lastClaims) {
const userId = await UserService.setUserData(userObject, refreshFields)
if (userId != userObject.userId) {
userObject.userId = userId.toString()
}
}
// Get privileges and check elevate param
userObject.privileges = {
create_collection: getClaimByPath(tokenPayload).includes('create_collection'),
admin: getClaimByPath(tokenPayload).includes('admin')
}
if ('elevate' in req.query && (req.query.elevate === 'true' && !userObject.privileges.admin)) {
throw new SmError.InvalidElevationError()
}
req.userObject = userObject
}
next()
}
catch (e) {
next(e)
}
}
// express-openapi-validator security handler
const validateOauthSecurity = function (req, requiredScopes) {
if (!req.access_token) {
throw new SmError.NoTokenError()
}
// Get decoded JWT payload from request
const tokenPayload = req.access_token
// Check scopes
const grantedScopes = typeof tokenPayload[config.oauth.claims.scope] === 'string' ?
tokenPayload[config.oauth.claims.scope].split(' ') :
tokenPayload[config.oauth.claims.scope]
const commonScopes = grantedScopes.filter(gs =>
requiredScopes.some(rs => {
if (gs === rs) return true
const gsTokens = gs.split(':').filter(i => i.length)
const rsTokens = rs.split(':').filter(i => i.length)
return gsTokens.length > 0 && gsTokens.every((t, i) => rsTokens[i] === t)
})
)
if (commonScopes.length == 0) {
throw new SmError.OutOfScopeError()
}
return true
}
// utility to extract bearer token from request
const getBearerToken = req => {
if (!req.headers.authorization) return
const headerParts = req.headers.authorization.split(' ')
if (headerParts[0].toLowerCase() === 'bearer') return headerParts[1]
}
// Check if JWKS contains any insecure key IDs
const containsInsecureKids = (kids) => {
return kids.some(kid => config.oauth.insecureKids.includes(kid))
}
// setup the JWKS key handling client
const setupJwks = async function (jwksUri, caCerts) {
jwksCache = new JWKSCache({
jwksUri,
caCerts,
cacheMaxAge: config.oauth.cacheMaxAge * 60 * 1000, // convert minutes to milliseconds
})
jwksCache.on('cacheUpdate', (cache) => {
logger.writeDebug('auth', 'jwksCacheEvent', { event: 'cacheUpdate', kids: jwksCache.getKidTypes() })
})
jwksCache.on('cacheStale', (cache) => {
logger.writeDebug('auth', 'jwksCacheEvent', { event: 'cacheStale', message: cache })
state.setOidcStatus(false)
jwksCache.once('cacheUpdate', (cache) => {
state.setOidcStatus(true)
})
})
// refresh cache of signing keys
const cacheResult = await jwksCache.refreshCache(false) // will not retry on failure
if (!cacheResult) throw new Error('refresh jwks cache failed')
const kids = jwksCache.getKids()
if (!config.oauth.allowInsecureTokens && containsInsecureKids(kids)) {
throw new Error('insecure_kid - JWKS contains insecure key IDs and STIGMAN_DEV_ALLOW_INSECURE_TOKENS is false')
}
logger.writeDebug('auth', 'discovery', { jwksUri, kids: jwksCache.getKidTypes() })
}
const getCaCerts = () => {
if (config.oauth.caCerts) {
try {
return fs.readFileSync(config.oauth.caCerts);
} catch (e) {
logger.writeError('auth', 'getCaCerts', { message: `Failed to read CA certificates from path: ${config.oauth.caCerts}`, error: e.message })
throw new Error(`Failed to read CA certificates from path: ${config.oauth.caCerts}`)
}
}
}
async function initializeAuth() {
const retries = config.settings.dependencyRetries
const metadataUri = `${config.oauth.authority}/.well-known/openid-configuration`
let jwksUri
let dispatcher
let caCerts = null
if (config.oauth.caCerts) {
caCerts = getCaCerts()
dispatcher = new Agent({ connect: { ca: caCerts } })
logger.writeInfo('auth', 'initializeAuth', { message: 'Using custom CA certificates to validate OIDC provider connections' })
}
async function getJwks(bail) {
logger.writeDebug('auth', 'discovery', { metadataUri, attempt: ++initAttempt })
const response = await fetch(metadataUri, { method: 'GET', dispatcher })
const openidConfig = await response.json()
logger.writeDebug('auth', 'discovery', { metadataUri, metadata: openidConfig})
if (!openidConfig.jwks_uri) {
const message = "No jwks_uri property found in oidcConfig"
logger.writeError('auth', 'discovery', { success: false, metadataUri, message })
bail(new Error(message)) // Bail if jwks_uri is not found
return // return after bail
}
jwksUri = openidConfig.jwks_uri
try {
await setupJwks(jwksUri, caCerts)
} catch (error) {
// If the error is from insecure kids detection, bail immediately
if (error.message.startsWith('insecure_kid -')) {
logger.writeError('auth', 'discovery', { success: false, metadataUri, message: error.message })
bail(error) // This will immediately stop retrying
return // Make sure to return after bail
}
throw error // Other errors will be retried
}
}
await retry(getJwks, {
retries,
factor: 1,
minTimeout: 5 * 1000,
maxTimeout: 5 * 1000,
onRetry: (error) => {
state.setOidcStatus(false)
logger.writeError('auth', 'discovery', { success: false, metadataUri, message: error.message })
}
})
logger.writeInfo('auth', 'discovery', { success: true, metadataUri, jwksUri })
state.setOidcStatus(true)
}
module.exports = {
validateToken,
setupUser,
validateOauthSecurity,
initializeAuth,
getClaimByPath,
checkInsecureKid,
decodeToken,
getSigningKey,
verifyToken
}
================================================
FILE: api/source/utils/buffer-json.js
================================================
function stringify (value, space) {
return JSON.stringify(value, replacer, space)
}
function parse (text) {
return JSON.parse(text, reviver)
}
function replacer (key, value) {
if (isBufferLike(value)) {
if (isArray(value.data)) {
if (value.data.length > 0) {
value.data = 'base64:' + Buffer.from(value.data).toString('base64')
} else {
value.data = ''
}
}
}
return value
}
function reviver (key, value) {
if (isBufferLike(value)) {
if (isArray(value.data)) {
return Buffer.from(value.data)
} else if (isString(value.data)) {
if (value.data.startsWith('base64:')) {
return Buffer.from(value.data.slice('base64:'.length), 'base64')
}
// Assume that the string is UTF-8 encoded (or empty).
return Buffer.from(value.data)
}
}
return value
}
function isBufferLike (x) {
return (
isObject(x) && x.type === 'Buffer' && (isArray(x.data) || isString(x.data))
)
}
function isArray (x) {
return Array.isArray(x)
}
function isString (x) {
return typeof x === 'string'
}
function isObject (x) {
return typeof x === 'object' && x !== null
}
module.exports = {
stringify,
parse,
replacer,
reviver
}
================================================
FILE: api/source/utils/config.js
================================================
const ourPackage = require("../package.json")
// Array of known insecure kid values
const insecureKids = ['FJ86GcF3jTbNLOco4NvZkUCIUmfYCqoqtOQeMfbhNlE']
const config = {
version: `${process.env.COMMIT_DESCRIBE ? process.env.COMMIT_DESCRIBE.replace(/-g[0-9a-f]+$/, "").replace(/-/g, "+") : ourPackage.version}`,
commit: {
branch: process.env.COMMIT_BRANCH || 'na',
sha: process.env.COMMIT_SHA || 'na',
tag: process.env.COMMIT_TAG || 'na',
describe: process.env.COMMIT_DESCRIBE || 'na'
},
settings: {
setClassification: process.env.STIGMAN_CLASSIFICATION ?? "NONE",
lastAccessResolution: 60,
// Supported STIGMAN_DEV_RESPONSE_VALIDATION values:
// "logOnly" (logs failing response, but still sends them)
// "none"(no validation performed)
responseValidation: process.env.STIGMAN_DEV_RESPONSE_VALIDATION || "none",
dependencyRetries: process.env.STIGMAN_DEPENDENCY_RETRIES || 24
},
client: {
clientId: process.env.STIGMAN_CLIENT_ID || "stig-manager",
consoleMode: process.env.STIGMAN_CLIENT_CONSOLE_MODE || "production",
displayAppManagers: process.env.STIGMAN_CLIENT_DISPLAY_APPMANAGERS || "true",
idleTimeoutUser: (() => {
const val = parseInt(process.env.STIGMAN_CLIENT_USER_TIMEOUT)
if (isNaN(val) || val < 0) return 0
return val
})(),
idleTimeoutAdmin: (() => {
const val = parseInt(process.env.STIGMAN_CLIENT_ADMIN_TIMEOUT)
if (isNaN(val) || val < 0) return 0
return val
})(),
authority: process.env.STIGMAN_CLIENT_OIDC_PROVIDER || process.env.STIGMAN_OIDC_PROVIDER || "http://localhost:8080/realms/stigman",
apiBase: process.env.STIGMAN_CLIENT_API_BASE || "api",
disabled: process.env.STIGMAN_CLIENT_DISABLED === "true",
directory: process.env.STIGMAN_CLIENT_DIRECTORY || '../../client/dist',
extraScopes: process.env.STIGMAN_CLIENT_EXTRA_SCOPES,
scopePrefix: process.env.STIGMAN_CLIENT_SCOPE_PREFIX,
responseMode: process.env.STIGMAN_CLIENT_RESPONSE_MODE || "fragment",
reauthAction: process.env.STIGMAN_CLIENT_REAUTH_ACTION || "popup",
strictPkce: process.env.STIGMAN_CLIENT_STRICT_PKCE !== 'false',
stateEvents: process.env.STIGMAN_CLIENT_STATE_EVENTS !== 'false',
welcome: {
image: process.env.STIGMAN_CLIENT_WELCOME_IMAGE || "",
message: process.env.STIGMAN_CLIENT_WELCOME_MESSAGE || "",
title: process.env.STIGMAN_CLIENT_WELCOME_TITLE || "",
link: process.env.STIGMAN_CLIENT_WELCOME_LINK || ""
}
},
docs: {
disabled: process.env.STIGMAN_DOCS_DISABLED === "true",
docsDirectory: process.env.STIGMAN_DOCS_DIRECTORY || '../../docs/_build/html',
},
http: {
address: process.env.STIGMAN_API_ADDRESS || "0.0.0.0",
port: process.env.STIGMAN_API_PORT || 54000,
maxJsonBody: process.env.STIGMAN_API_MAX_JSON_BODY || "31457280",
maxUpload: process.env.STIGMAN_API_MAX_UPLOAD || "1073741824",
tls: {
key_file: process.env.STIGMAN_API_TLS_KEY_FILE,
key_passphrase: process.env.STIGMAN_API_TLS_KEY_PASSPHRASE,
cert_file: process.env.STIGMAN_API_TLS_CERT_FILE
}
},
database: {
host: process.env.STIGMAN_DB_HOST || "localhost",
port: process.env.STIGMAN_DB_PORT || 3306,
schema: process.env.STIGMAN_DB_SCHEMA || "stigman",
username: process.env.STIGMAN_DB_USER || "stigman",
password: process.env.STIGMAN_DB_PASSWORD,
maxConnections: process.env.STIGMAN_DB_MAX_CONNECTIONS || 25,
tls: {
ca_file: process.env.STIGMAN_DB_TLS_CA_FILE,
cert_file: process.env.STIGMAN_DB_TLS_CERT_FILE,
key_file: process.env.STIGMAN_DB_TLS_KEY_FILE
},
revert: process.env.STIGMAN_DB_REVERT === "true",
toJSON: function () {
let {password, ...props} = this
props.password = !!password
return props
}
},
swaggerUi: {
enabled: process.env.STIGMAN_SWAGGER_ENABLED === "true",
authority: process.env.STIGMAN_SWAGGER_OIDC_PROVIDER || process.env.STIGMAN_SWAGGER_AUTHORITY || process.env.STIGMAN_OIDC_PROVIDER || "http://localhost:8080/auth/realms/stigman",
server: process.env.STIGMAN_SWAGGER_SERVER || "http://localhost:54000/api",
oauth2RedirectUrl: process.env.STIGMAN_SWAGGER_REDIRECT || "http://localhost:54000/api-docs/oauth2-redirect.html"
},
oauth: {
authority: process.env.STIGMAN_OIDC_PROVIDER || process.env.STIGMAN_API_AUTHORITY || "http://localhost:8080/realms/stigman",
audienceValue: process.env.STIGMAN_JWT_AUD_VALUE,
allowInsecureTokens: process.env.STIGMAN_DEV_ALLOW_INSECURE_TOKENS === "true",
caCerts: process.env.STIGMAN_OIDC_CA_CERTS,
insecureKids,
cacheMaxAge: Math.min(Math.max(process.env.STIGMAN_JWKS_CACHE_MAX_AGE, 1) || 10, 35791),
claims: {
scope: process.env.STIGMAN_JWT_SCOPE_CLAIM || "scope",
username: process.env.STIGMAN_JWT_USERNAME_CLAIM || "preferred_username",
servicename: process.env.STIGMAN_JWT_SERVICENAME_CLAIM,
name: process.env.STIGMAN_JWT_NAME_CLAIM || process.env.STIGMAN_JWT_USERNAME_CLAIM || "name",
privileges: formatMySqlJsonPath(process.env.STIGMAN_JWT_PRIVILEGES_CLAIM || "realm_access.roles"),
privilegesChain: formatJsChain(process.env.STIGMAN_JWT_PRIVILEGES_CLAIM || "realm_access.roles"),
privilegesRaw: process.env.STIGMAN_JWT_PRIVILEGES_CLAIM || "realm_access.roles",
email: process.env.STIGMAN_JWT_EMAIL_CLAIM || "email",
assertion: process.env.STIGMAN_JWT_ASSERTION_CLAIM || "jti"
}
},
log: {
level: parseInt(process.env.STIGMAN_LOG_LEVEL) || 3,
mode: process.env.STIGMAN_LOG_MODE || 'combined',
optStats: process.env.STIGMAN_DEV_LOG_OPT_STATS === "true"
},
experimental: {
appData: process.env.STIGMAN_EXPERIMENTAL_APPDATA === "true",
logStream: process.env.STIGMAN_EXPERIMENTAL_LOGSTREAM !== "false"
}
}
function formatJsChain(path) {
const components = path?.split('.')
if (components?.length === 1) return path
for (let x=0; x < components.length; x++) {
components[x] = `['${components[x]}']`
}
return components.join('?.')
}
function formatMySqlJsonPath(path) {
return path?.split('.').map(p => `"${p}"`).join('.')
}
module.exports = config
================================================
FILE: api/source/utils/error.js
================================================
class SmError extends Error {
constructor(message) {
super(message)
// Ensure the name of this error is the same as the class name
this.name = this.constructor.name
// This clips the constructor invocation from the stack trace.
// It's not absolutely essential, but it does make the stack trace a little nicer.
// @see Node.js reference (bottom)
Error.captureStackTrace(this, this.constructor)
this.toJSON = () => ({ error: this.message })
}
}
class ClientError extends SmError {
constructor(detail) {
super('Incorrect request.')
this.status = 400
this.detail = detail
}
}
class AuthorizeError extends SmError {
constructor(detail) {
super('Request not authorized.')
this.status = 401
this.detail = detail
}
}
class PrivilegeError extends SmError {
constructor(detail) {
super('User has insufficient privilege to complete this request.')
this.status = 403
this.detail = detail
}
}
class NotFoundError extends SmError {
constructor(detail) {
super('Resource not found.')
this.status = 404
this.detail = detail
}
}
class UnprocessableError extends SmError {
constructor(detail) {
super('Unprocessable Entity.')
this.status = 422
this.detail = detail
}
}
class InternalError extends SmError {
constructor(error) {
super(error.message)
this.status = 500
this.detail = { error }
}
}
class OIDCProviderError extends SmError {
constructor(detail) {
super('OIDC Provider is unreachable, unable to validate token.')
this.status = 503
this.detail = detail
}
}
class SigningKeyNotFoundError extends SmError {
constructor(detail) {
super('Unknown signing key, unable to validate token.')
this.status = 401
this.detail = detail
}
}
class InsecureTokenError extends SmError {
constructor(detail) {
super('Insecure token presented and STIGMAN_DEV_ALLOW_INSECURE_TOKENS is false.')
this.status = 401
this.detail = detail
}
}
class NoTokenError extends SmError {
constructor(detail) {
super('Request requires an access token.')
this.status = 401
this.detail = detail
}
}
class OutOfScopeError extends SmError {
constructor(detail) {
super('Required scopes were not found in token.')
this.status = 403
this.detail = detail
}
}
class ElevationError extends SmError {
constructor(detail) {
super('Request requires parameter elevate=true.')
this.status = 403
this.detail = detail
}
}
class InvalidElevationError extends SmError {
constructor(detail) {
super('Invalid use of parameter elevate=true.')
this.status = 403
this.detail = detail
}
}
class UserUnavailableError extends SmError {
constructor(detail) {
super('User status is "unavailable".')
this.status = 403
this.detail = detail
}
}
class UserInconsistentError extends SmError {
constructor(detail) {
super('Setting collectionGrants or userGroups is inconsistent with status "unavailable".')
this.status = 422
this.detail = detail
}
}
class EndpointUnavailableError extends SmError {
constructor(detail) {
super('Endpoint is unavailable.')
this.status = 409
this.detail = detail
}
}
class ModeLockedError extends SmError {
constructor(detail) {
super('API mode is locked.')
this.status = 409
this.detail = detail
}
}
module.exports = {
SmError,
AuthorizeError,
PrivilegeError,
NotFoundError,
ClientError,
UnprocessableError,
OIDCProviderError,
SigningKeyNotFoundError,
NoTokenError,
OutOfScopeError,
ElevationError,
InvalidElevationError,
InternalError,
InsecureTokenError,
UserUnavailableError,
UserInconsistentError,
EndpointUnavailableError,
ModeLockedError
}
================================================
FILE: api/source/utils/escape.js
================================================
/**
* Escapes XML reserved characters with named entity references.
* @param {string} value - The string to escape.
* @returns {string} The escaped string.
*/
module.exports.escapeForXml = function (name, value) {
/**
* Regex matches characters that need to be escaped in XML.
* @type {RegExp}
*/
const regexEscapeXml = /["&'<>]/g
/**
* Map of characters to their corresponding named XML entities.
* @type {Object.}
*/
const escapeMapXml = {
'"': '"',
'&': '&',
'\'': ''',
'<': '<',
'>': '>'
}
return value.toString().replace(regexEscapeXml, function ($0) {
return escapeMapXml[$0]
})
}
/**
* Escapes filesystem reserved characters with named entity references.
* @param {string} value - The string to escape.
* @returns {string} The escaped string.
*/
module.exports.escapeFilename = function (value) {
/**
* Regexes match characters that need to be escaped in filenames.
* @type {RegExp}
*/
const osReserved = /[/\\:*"?<>|]/g
const controlChars = /[\x00-\x1f]/g
/**
* Map of characters to their corresponding named HTML entities.
* @type {Object.}
*/
const osReserveReplace = {
'/': '/',
'\\': '\',
':': ':',
'*': '*',
'"': '"',
'?': '?',
'<': '<',
'>': '>',
'|': '|',
}
return value.toString()
.replace(osReserved, (match) => osReserveReplace[match])
.replace(controlChars, (match) => `${match.charCodeAt(0).toString().padStart(2,'0')};`)
.substring(0, 255)
}
module.exports.filenameComponentFromDate = function (dateObject = new Date()) {
return dateObject.toISOString().replace(/:|\d{2}\.\d{3}/g,'')
}
================================================
FILE: api/source/utils/jwksCache.js
================================================
const EventEmitter = require('node:events')
const crypto = require('node:crypto')
const http = require('node:http')
const https = require('node:https')
const logger = require('./logger')
class JWKSCache extends EventEmitter {
constructor({ jwksUri, caCerts, cacheMaxAge = 60000 }) {
super()
this.cache = new Map()
this.jwksUri = jwksUri
this.caCerts = caCerts
this.cacheMaxAge = Math.min(cacheMaxAge, 2 ** 31 - 1)
this.cacheRefreshAge = this.cacheMaxAge / 2
this.staleTimeoutId = null
this.refreshTimeoutId = null
this.isCacheUpdating = false
}
getKey(kid) {
if (this.cache.has(kid)) {
return this.cache.get(kid)
}
return null
}
getKids() {
return Array.from(this.cache.keys())
}
getKidTypes() {
const keys = {}
for (const [kid, key] of this.cache.entries()) {
keys[kid] = key.type
}
return keys
}
setKey(kid, key) {
this.cache.set(kid, key)
this.emit('keyAdded', kid, key)
}
async refreshCache(retryOnFailure = true) {
logger.writeInfo('jwksCache', 'refreshing cache', { uri: this.jwksUri })
clearTimeout(this.refreshTimeoutId)
const result = await this.updateCache()
if (result) {
this.refreshTimeoutId = setTimeout(this.refreshCache.bind(this), this.cacheRefreshAge)
}
else {
logger.writeError('jwksCache', 'refresh error', { message: 'updateCache returned false' })
if (retryOnFailure) this.refreshTimeoutId = setTimeout(this.refreshCache.bind(this), 10000)
}
return result
}
clearAllCache() {
this.cache.clear()
}
clearCacheKeepUnknown() {
for (const [kid, key] of this.cache.entries()) {
if (key !== 'unknown') {
this.cache.delete(kid)
}
}
}
onCacheStale() {
this.clearCacheKeepUnknown()
this.emit('cacheStale', this.cache)
}
request(url, options) {
return new Promise((resolve, reject) => {
const socketInfo = {
localAddress: undefined,
localPort: undefined,
remoteAddress: undefined,
remotePort: undefined
}
const requestOptions = {
timeout: 10000,
...options
}
if (this.caCerts) {
requestOptions.ca = this.caCerts
}
const httpRequestLib = url.protocol === 'https:' ? https : http;
const httpRequest = httpRequestLib.request(url, requestOptions
, (res) => {
const socket = res.socket
socketInfo.localAddress = socket.localAddress
socketInfo.localPort = socket.localPort
socketInfo.remoteAddress = socket.remoteAddress
socketInfo.remotePort = socket.remotePort
let rawData = ''
res.setEncoding('utf8')
res.on('data', (chunk) => rawData += chunk)
res.on('end', () => {
if (res.statusCode < 200 || res.statusCode >= 300) {
const errorMsg = res.body && (res.body.message || res.body) || res.statusMessage || `Http Error ${res.statusCode}`
reject({ errorMsg })
}
else {
try {
logger.writeInfo('jwksCache','response', {socket: formatSocket(socketInfo)})
resolve(rawData && JSON.parse(rawData))
}
catch (error) {
reject(error)
}
}
})
}
)
/**
* Formats a Node.js socket object into a string representation.
*
* @param {net.Socket} socket - The Node.js socket object.
* @returns {string|undefined} A string representation of the socket's local and remote addresses and ports, or undefined if the socket is not connected.
*/
function formatSocket(socket) {
return socket.localAddress || socket.remoteAddress ? `${socket.localAddress}:${socket.localPort} -> ${socket.remoteAddress}:${socket.remotePort}` : undefined
}
function onSocket(socket) {
socketInfo.localAddress = socket.localAddress
socketInfo.localPort = socket.localPort
socketInfo.remoteAddress = socket.remoteAddress
socketInfo.remotePort = socket.remotePort
socketInfo.socket = socket
logger.writeDebug('jwksCache', 'requestEvent', {event: 'socket', socket: formatSocket(socketInfo)})
socket.on('error', (error) => {
const err = error.errors ? error.errors[0] : error
socketInfo.remoteAddress = err.address
socketInfo.remotePort = err.port
logger.writeError('jwksCache', 'socketEvent', {event: 'error', socket: formatSocket(socketInfo), message: err.message})
})
socket.on('connectionAttempt', (ip, port, family) => {
socketInfo.remoteAddress = ip
socketInfo.remotePort = port
logger.writeDebug('jwksCache', 'socketEvent', {event: 'connectionAttempt', ip, port, family})
})
socket.on('connectionAttemptFailed', (ip, port, family, error) => {
socketInfo.remoteAddress = ip
socketInfo.remotePort = port
logger.writeDebug('jwksCache', 'socketEvent', {event: 'connectionAttemptFailed', ip, port, family, message: error.message})
})
socket.on('lookup', (error, address, family, host) => {
socketInfo.remoteAddress = address
logger.writeDebug('jwksCache', 'socketEvent', {event: 'lookup', address, family, host, message: error?.message })
})
}
function onTimeout() {
logger.writeError('jwksCache', 'requestTimeout', { socket: formatSocket(socketInfo) })
httpRequest.destroy()
}
httpRequest
.on('socket', onSocket)
.on('timeout', onTimeout)
.on('error', reject)
.end()
})
}
extractKeysFromJwks(jwks) {
const results = []
jwks = jwks
.filter(({ use }) => use === 'sig' || use === undefined)
.filter(({ kty }) => kty === 'RSA' || kty === 'EC' || kty === 'OKP')
for (const jwk of jwks) {
try {
if (!jwk.kid) throw new Error('Missing kid')
const publicKey = crypto.createPublicKey({ format: 'jwk', key: jwk })
results.push({
publicKey,
publicKeyPem: publicKey.export({ format: 'pem', type: 'spki' }),
kid: jwk.kid,
alg: jwk.alg
})
}
catch {
continue
}
}
return results
}
updateCache() {
return new Promise((resolve) => {
if (!this.isCacheUpdating) {
this.isCacheUpdating = true
this.request(new URL(this.jwksUri), { method: 'GET' })
.then(jwks => {
clearTimeout(this.staleTimeoutId)
this.staleTimeoutId = setTimeout(this.onCacheStale.bind(this), this.cacheMaxAge)
this.clearCacheKeepUnknown()
const keys = this.extractKeysFromJwks(jwks.keys)
for (const key of keys) {
this.setKey(key.kid, key.publicKey)
}
this.isCacheUpdating = false
this.emit('cacheUpdate', this.cache)
resolve(true)
})
.catch(error => {
this.isCacheUpdating = false
this.emit('cacheError', error)
resolve(false)
})
}
else { // an update is already in progress
logger.writeDebug('jwksCache', 'updateCache', { message: 'update already in progress' })
this.once('cacheUpdate', () => {
logger.writeDebug('jwksCache', 'cacheUpdate', { message: 'concurrent update event' })
resolve(true)
})
this.once('cacheError', () => {
logger.writeDebug('jwksCache', 'cacheError', { message: 'concurrent update event' })
resolve(false)
})
}
})
}
}
module.exports = JWKSCache
================================================
FILE: api/source/utils/klona.js
================================================
module.exports = function klona(val) {
// MIT License
// Copyright (c) Luke Edwards (lukeed.com)
// https://github.com/lukeed/klona
let k, out, tmp
if (Array.isArray(val)) {
out = Array(k = val.length)
while (k--) out[k] = (tmp = val[k]) && typeof tmp === 'object' ? klona(tmp) : tmp
return out
}
if (Object.prototype.toString.call(val) === '[object Object]') {
out = {} // null
for (k in val) {
if (k === '__proto__') {
Object.defineProperty(out, k, {
value: klona(val[k]),
configurable: true,
enumerable: true,
writable: true,
})
} else {
out[k] = (tmp = val[k]) && typeof tmp === 'object' ? klona(tmp) : tmp
}
}
return out
}
return val
}
================================================
FILE: api/source/utils/log-schema.json
================================================
{
"$schema": "https://json-schema.org/draft-07/schema",
"$id": "http://yourdomain.com/schemas/myschema.json",
"type": "object",
"properties": {
"date": {
"type": "string",
"format": "date-time"
},
"level": {
"type": "integer",
"minimum": 1,
"maximum": 4
},
"component": {
"type": "string"
},
"type": {
"type": "string"
},
"data": {
"type": "object"
}
},
"required": [
"date",
"level",
"component",
"type",
"data"
],
"additionalProperties": false,
"oneOf": [
{
"$ref": "#/$defs/componentIndex"
},
{
"$ref": "#/$defs/componentOidc"
}
],
"$defs": {
"componentIndex": {
"properties": {
"component": {
"type": "string",
"const": "index"
}
},
"oneOf": [
{
"$ref": "#/$defs/typeStarting"
},
{
"$ref": "#/$defs/typeConfiguration"
},
{
"$ref": "#/$defs/typeStarted"
}
]
},
"typeStarting": {
"properties": {
"type": {
"type": "string",
"const": "starting"
},
"data": {
"type": "object",
"properties": {
"version": {
"type": "string"
}
},
"additionalProperties": false
}
}
},
"typeConfiguration": {
"properties": {
"type": {
"type": "string",
"const": "configuration"
},
"data": {
"type": "object",
"properties": {
"version": {
"type": "string"
},
"commit": {
"type": "object",
"required": [],
"properties": {
"branch": {
"type": "string"
},
"sha": {
"type": "string"
},
"tag": {
"type": "string"
},
"describe": {
"type": "string"
}
},
"additionalProperties": false
},
"settings": {
"type": "object",
"required": [],
"properties": {
"setClassification": {
"type": "string"
},
"lastAccessResolution": {
"type": "integer"
},
"responseValidation": {
"type": "string"
}
},
"additionalProperties": false
},
"client": {
"type": "object",
"required": [],
"properties": {
"clientId": {
"type": "string"
},
"displayAppManagers": {
"type": "boolean"
},
"authority": {
"type": "string"
},
"apiBase": {
"type": "string"
},
"disabled": {
"type": "boolean"
},
"directory": {
"type": "string"
},
"refreshToken": {
"type": "object",
"required": [],
"properties": {
"disabled": {
"type": "boolean"
}
},
"additionalProperties": false
},
"welcome": {
"type": "object",
"required": [],
"properties": {
"image": {
"type": "string"
},
"message": {
"type": "string"
},
"title": {
"type": "string"
},
"link": {
"type": "string"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"docs": {
"type": "object",
"required": [],
"properties": {
"disabled": {
"type": "boolean"
},
"docsDirectory": {
"type": "string"
}
},
"additionalProperties": false
},
"http": {
"type": "object",
"required": [],
"properties": {
"address": {
"type": "string"
},
"port": {
"type": "string"
},
"maxJsonBody": {
"type": "string"
},
"maxUpload": {
"type": "string"
}
},
"additionalProperties": false
},
"database": {
"type": "object",
"required": [],
"properties": {
"type": {
"type": "string"
},
"host": {
"type": "string"
},
"port": {
"type": "string"
},
"schema": {
"type": "string"
},
"username": {
"type": "string"
},
"maxConnections": {
"type": "string"
},
"tls": {
"type": "object",
"required": [],
"additionalProperties": false
},
"revert": {
"type": "boolean"
},
"password": {
"type": "boolean"
}
},
"additionalProperties": false
},
"init": {
"type": "object",
"required": [],
"properties": {
"importStigs": {
"type": "boolean"
},
"importScap": {
"type": "boolean"
}
},
"additionalProperties": false
},
"swaggerUi": {
"type": "object",
"required": [],
"properties": {
"enabled": {
"type": "boolean"
},
"authority": {
"type": "string"
},
"server": {
"type": "string"
},
"oauth2RedirectUrl": {
"type": "string"
}
},
"additionalProperties": false
},
"oauth": {
"type": "object",
"required": [],
"properties": {
"authority": {
"type": "string"
},
"claims": {
"type": "object",
"required": [],
"properties": {
"scope": {
"type": "string"
},
"scopeFormat": {
"type": "string"
},
"username": {
"type": "string"
},
"servicename": {
"type": "string"
},
"name": {
"type": "string"
},
"privileges": {
"type": "string"
},
"email": {
"type": "string"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"log": {
"type": "object",
"required": [],
"properties": {
"level": {
"type": "integer"
},
"mode": {
"type": "string"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
}
},
"typeStarted": {
"properties": {
"type": {
"type": "string",
"const": "started"
},
"data": {
"type": "object",
"properties": {
"durationS": {
"type": "number"
},
"port": {
"type": "string"
},
"api": {
"type": "string"
},
"client": {
"type": "string"
},
"documentation": {
"type": "string"
},
"swagger": {
"type": "string"
}
},
"additionalProperties": false
}
}
},
"componentOidc": {
"properties": {
"component": {
"type": "string",
"const": "oidc"
}
},
"oneOf": [
{
"$ref": "#/$defs/typeDiscovery"
}
]
},
"typeDiscovery": {
"properties": {
"type": {
"type": "string",
"const": "discovery"
},
"data": {
"type": "object",
"properties": {
"success": {
"type": "boolean"
},
"url": {
"type": "string"
}
}
},
"additionalProperties": false
}
}
}
}
================================================
FILE: api/source/utils/logSocket.js
================================================
const { randomUUID } = require('node:crypto')
const logger = require('./logger')
const WebSocket = require('ws')
const component = 'logSocket'
const auth = require('./auth')
const SmError = require('./error')
const asyncApiValidator = require('./asyncApiValidator')
const socketPath = '/socket/log-socket'
class LogSession {
constructor(ws, validator) {
this.ws = ws;
this.validator = validator;
this.authorized = false;
this.tokenExp = null;
this.logForwarding = false;
this.sessionId = randomUUID();
this.filter = null;
this.pingIntervalId = null
this.unauthorizedTimerId = null
this.unauthorizedTimeoutMs = 10000
this.pingIntervalMs = 30000
}
start = () => {
logger.writeInfo(component, 'session-start', { sessionId: this.sessionId, message: 'Session started' });
this.ws.on('message', this.onSocketMessage);
this.ws.on('close', this.stop);
this.ws.on('pong', this.onSocketPong);
this.startHeartbeat();
this.sendUnauthorized();
}
stop = () => {
this.sendClose('Session ending');
this.disableLogForwarding();
this.stopHeartbeat();
this.ws.off('message', this.onSocketMessage);
this.ws.off('close', this.stop);
this.ws.off('pong', this.onSocketPong);
if (this.tokenTimer) clearTimeout(this.tokenTimer);
if (this.unauthorizedTimerId) {
clearTimeout(this.unauthorizedTimerId);
this.unauthorizedTimerId = null;
}
this.ws.close();
logger.writeInfo(component, 'session-stop', { sessionId: this.sessionId, message: 'Session stopped' });
}
enableLogForwarding = () => {
if (!this.logForwarding) {
logger.loggerEvents.on('log', this.loggerEventHandler);
this.logForwarding = true;
}
}
disableLogForwarding = () => {
if (this.logForwarding) {
logger.loggerEvents.off('log', this.loggerEventHandler);
this.logForwarding = false;
}
}
includeLogRecord = (logObj) => {
if (!this.filter) return true;
return Object.entries(this.filter).every(([key, value]) => {
return logObj[key] && value.includes(logObj[key]);
});
}
loggerEventHandler = (logObj) => {
if (this.authorized && this.includeLogRecord(logObj)) {
this.sendLog(logObj);
}
}
startHeartbeat = () => {
this.stopHeartbeat();
this.pingIntervalId = setInterval(this.sendPing, this.pingIntervalMs);
}
stopHeartbeat = () => {
if (this.pingIntervalId) {
clearInterval(this.pingIntervalId);
this.pingIntervalId = null;
}
}
sendPing = () => {
try {
this.ws.ping();
logger.writeInfo(component, 'ping-sent', { sessionId: this.sessionId });
} catch {
// Ignore ping errors
}
}
onSocketPong = () => {
// Pong received, connection is alive
logger.writeInfo(component, 'pong-received', { sessionId: this.sessionId });
}
onSocketMessage = (message) => {
let msgObj;
try {
msgObj = JSON.parse(message);
} catch {
this.sendError('Invalid JSON message');
return;
}
try {
this.validator.validate(msgObj.type, msgObj, 'logStream', 'receive');
}
catch (e) {
this.sendError('Message validation failed: ' + e.message);
return;
}
if (msgObj.type === 'authorize' && (typeof msgObj.data?.token === 'string')) {
const loggedMessage = this.deepClone(msgObj);
loggedMessage.data.token = this.decodeToken(msgObj.data.token) || loggedMessage.data.token;
logger.writeInfo(component, 'message-receive', { sessionId: this.sessionId, ...loggedMessage });
} else {
logger.writeInfo(component, 'message-receive', { sessionId: this.sessionId, ...msgObj });
}
switch (msgObj.type) {
case 'authorize':
this.onAuthorize(msgObj.data);
break;
case 'command':
if (this.authorized) {
this.onCommand(msgObj.data);
}
break;
default:
this.sendError('Unexpected message type');
}
}
deepClone = (msg) => {
return JSON.parse(JSON.stringify(msg));
}
onCommand = (commandData) => {
switch (commandData.command) {
case 'stream-start':
this.filter = commandData.filter;
this.enableLogForwarding();
break;
case 'stream-stop':
this.disableLogForwarding();
break;
default:
this.sendError('Unknown command');
}
this.sendInfo({ success: true, command: commandData });
}
onAuthorize = async (authData) => {
// Validate token (format and expiration)
try {
// Accept JWTs: decode and check exp
const decoded = auth.decodeToken(authData.token);
// Mock a bad token for testing
// decoded.header.kid = 'xxx-bad-kid-xxx';
auth.checkInsecureKid(decoded);
const signingKey = await auth.getSigningKey(decoded);
auth.verifyToken(authData.token, signingKey);
const privileges = auth.getClaimByPath(decoded.payload);
if (!privileges.includes('admin')) {
throw new SmError.PrivilegeError();
}
// successful authorization
clearTimeout(this.unauthorizedTimerId);
this.unauthorizedTimerId = null;
this.tokenExp = decoded.payload.exp;
this.startTokenTimer();
this.authorized = true;
this.sendAuthorized();
} catch (e) {
this.authorized = false;
this.disableLogForwarding();
logger.writeWarn(component, 'authorize-failed', { sessionId: this.sessionId, message: e.message });
this.sendUnauthorized('Authorization failed: ' + e.detail || e.message);
return;
}
}
startTokenTimer = () => {
if (this.tokenTimer) clearTimeout(this.tokenTimer);
if (!this.tokenExp) return;
const now = Math.floor(Date.now() / 1000);
const ms = Math.max(0, (this.tokenExp - now) * 1000);
this.tokenTimer = setTimeout(() => {
this.authorized = false;
this.disableLogForwarding();
this.sendUnauthorized('jwt expired');
}, ms);
}
decodeToken = (token) => {
try {
const parts = token.split('.');
if (parts.length !== 3) throw new Error('Invalid JWT format');
const decoded = JSON.parse(Buffer.from(parts[1], 'base64').toString('utf8'));
return decoded;
}
catch {
return null;
}
}
sendUnauthorized = (reason) => {
this.send({ type: 'authorize', data: { state: 'unauthorized', reason } });
if (!this.unauthorizedTimerId) {
this.unauthorizedTimerId = setTimeout(() => {
this.stop();
}, this.unauthorizedTimeoutMs); // Set a maximum time to be unauthorized
}
}
sendAuthorized = () => {
this.send({ type: 'authorize', data: { state: 'authorized' } });
}
sendClose = (message = 'Closing connection') => {
this.send({ type: 'close', data: message});
}
sendInfo = (info) => {
this.send({ type: 'info', data: info });
}
sendError = (error) => {
this.send({ type: 'error', data: error });
}
sendLog = (logObj) => {
this.send({ type: 'log', data: logObj });
}
send = (msg) => {
try {
this.validator.validate(msg.type, msg, 'logStream', 'send');
} catch (e) {
logger.writeError(component, 'message-validation-failed', { sessionId: this.sessionId, message: msg, error: e.message });
}
this.ws.send(JSON.stringify(msg));
if (msg.type !== 'log') {
const loggerFn = msg.type === 'error' ? logger.writeError : logger.writeInfo;
loggerFn(component, 'message-send', { sessionId: this.sessionId, ...msg });
}
}
}
async function setupLogSocket (server, schemaPath) {
const validator = asyncApiValidator.fromSource(schemaPath)
const wss = new WebSocket.Server({ server, path: socketPath })
wss.on('connection', (ws) => onConnection(ws, validator))
}
function onConnection (ws, validator) {
const clientAddr = `${ws._socket.remoteAddress}:${ws._socket.remotePort}`;
const logSession = new LogSession(ws, validator);
logger.writeInfo(component, 'connection', {source: clientAddr, sessionId: logSession.sessionId, message: 'New log socket connection'});
logSession.start();
}
module.exports = { setupLogSocket }
================================================
FILE: api/source/utils/logger.js
================================================
const { randomUUID } = require('node:crypto')
const onFinished = require('on-finished')
const onHeaders = require('on-headers')
const config = require('./config')
const EventEmitter = require('node:events')
const loggerEvents = new EventEmitter()
// Ensure no other code will write to the console
const _log = console.log
for (const method of ['log', 'error', 'warn', 'trace', 'debug']) {
console[method] = function () {
writeError('logger', 'consoleIntercept', { method, arguments })
}
}
// Setup noops for logger methods > config.log.level
const writeDebug = config.log.level == 4 ? function writeDebug () {
write(4, ...arguments)
} : () => {}
const writeInfo = config.log.level >= 3 ? function writeInfo () {
write(3, ...arguments)
} : () => {}
const writeWarn = config.log.level >= 2 ? function writeWarn () {
write(2, ...arguments)
} : () => {}
const writeError = config.log.level >= 1 ? function writeError () {
write(1, ...arguments)
} : () => {}
// Stats for all requests
const requestStats = {
totalRequests: 0,
totalApiRequests: 0,
totalRequestDuration: 0,
operationIds: {}
}
// All messages to STDOUT are handled here
async function write (level, component, type, data) {
try {
const date = new Date().toISOString()
const logObj = {date, level, component, type, data}
_log(JSON.stringify(logObj))
loggerEvents.emit('log', logObj)
}
catch (e) {
const date = new Date().toISOString()
const errorObj = {date, level:1, component:'logger', type:'error', data: { message: e.message, stack: e.stack}}
_log(JSON.stringify(errorObj))
loggerEvents.emit('log', errorObj)
}
}
// Base64 decoding
const atob = (data) => Buffer.from(data, 'base64').toString('ascii')
function sanitizeHeaders () {
let {authorization, ...headers} = this
if (authorization !== undefined) {
headers.authorization = true
if (config.log.mode !== 'combined') {
const payload = authorization.match(/^Bearer [[A-Za-z0-9-_=]+\.([[A-Za-z0-9-_=]+?)\./)?.[1]
if (payload) {
headers.accessToken = JSON.parse(atob(payload))
}
}
}
else {
headers.authorization = false
}
return headers
}
function serializeRequest (req) {
req.headers.toJSON = sanitizeHeaders
if (config.log.mode === 'combined') {
req.headers.accessToken = req.access_token
}
return {
requestId: req.requestId,
date: req._startTime,
source: req.ip,
// claims: req.userObject ? serializeUserObject(req.userObject) : undefined,
method: req.method,
url: req.originalUrl,
headers: req.headers,
body: req.query.elevate === true || req.query.elevate === 'true' || config.log.level === 4 ? req.body : undefined
}
}
function recordStartTime () {
this._startTime = new Date()
}
function requestLogger (req, res, next) {
req._startAt = undefined
req._startTime = undefined
res._startAt = undefined
res._startTime = undefined
res.svcStatus = {}
req.requestId = randomUUID()
// Response body length for appinfo and content for privileged requests
let responseBody
responseBody = ''
if (req.query.elevate) {
const originalSend = res.send
res.send = function (chunk) {
if (chunk !== undefined) {
responseBody += chunk
}
originalSend.apply(res, arguments)
}
}
// record request start
recordStartTime.call(req)
function logRequest () {
if (req.originalUrl.startsWith('/api')) {
req.component = 'rest'
} else {
req.component = 'static'
}
writeInfo(req.component, 'request', serializeRequest(req))
}
function logResponse () {
res._startTime = res._startTime ?? new Date()
requestStats.totalRequests += 1
const durationMs = Number(res._startTime - req._startTime)
requestStats.totalRequestDuration += durationMs
const operationId = res.req.openapi?.schema.operationId
let operationStats = {
operationId,
retries: res.svcStatus?.retries,
durationMs
}
//if operationId is defined, this is an api endpoint response so we can track some stats
if (operationId ) {
trackOperationStats(operationId, durationMs, res)
// If including stats in log entries, add to operationStats object
if (config.log.optStats) {
operationStats = {
...operationStats,
...requestStats.operationIds[operationId]
}
}
}
if (config.log.mode === 'combined') {
writeInfo(req.component || 'rest', 'transaction', {
request: serializeRequest(res.req),
response: {
date: res._startTime,
status: res.finished ? res.statusCode : undefined,
clientTerminated: res.destroyed ? true : undefined,
headers: res.finished ? res.getHeaders() : undefined,
errorBody: res.errorBody,
responseBody,
},
operationStats
})
}
else {
writeInfo(req.component || 'rest', 'response', {
requestId: res.req.requestId,
status: res.statusCode,
headers: res.getHeaders(),
errorBody: res.errorBody,
responseBody,
operationStats
})
}
}
if (config.log.mode !== 'combined') {
logRequest()
}
onHeaders(res, recordStartTime)
onFinished(res, logResponse)
next()
}
function serializeEnvironment () {
let env = {}
for (const [key, value] of Object.entries(process.env)) {
if (/^(NODE|STIGMAN)_/.test(key)) {
env[key] = key === 'STIGMAN_DB_PASSWORD' ? '*' : value
}
}
return env
}
function trackOperationStats(operationId, durationMs, res) {
const acceptsRequestBody = (res.req.method === 'POST' || res.req.method === 'PUT' || res.req.method === 'PATCH')
//increment total api requests
requestStats.totalApiRequests++
// Ensure the operationIds object exists for the operationId
if (!requestStats.operationIds[operationId]) {
requestStats.operationIds[operationId] = {
totalRequests: 0,
totalDuration: 0,
elevatedRequests: 0,
minDuration: Infinity,
maxDuration: 0,
maxDurationUpdates: 0,
retried: 0,
averageRetries: 0,
totalResLength: 0,
minResLength: Infinity,
maxResLength: 0,
clients: {},
users: {},
errors: {}
}
if (acceptsRequestBody) {
requestStats.operationIds[operationId].totalReqLength = 0
requestStats.operationIds[operationId].minReqLength = Infinity
requestStats.operationIds[operationId].maxReqLength = 0
}
}
// Get the stats object for this operationId
const stats = requestStats.operationIds[operationId]
// errors
if (res.statusCode >= 500) {
const code = res.errorBody?.code || 'nocode'
stats.errors[code] = (stats.errors[code] || 0) + 1
}
// Update max duration
stats.minDuration = Math.min(stats.minDuration, durationMs)
if (durationMs > stats.maxDuration) {
stats.maxDuration = durationMs
stats.maxDurationUpdates++
}
// Increment total requests and total duration for this operationId
stats.totalRequests++
stats.totalDuration += durationMs
const responseLength = parseInt(res.getHeader('content-length')) || 0
stats.totalResLength += responseLength
stats.minResLength = Math.min(stats.minResLength, responseLength)
stats.maxResLength = Math.max(stats.maxResLength, responseLength)
if (acceptsRequestBody) {
const requestLength = parseInt(res.req.headers['content-length']) || 0
stats.totalReqLength += requestLength
stats.minReqLength = Math.min(stats.minReqLength, requestLength)
stats.maxReqLength = Math.max(stats.maxReqLength, requestLength)
}
// Update retries
if (res.svcStatus?.retries) {
stats.retried++
stats.averageRetries = runningAverage({
currentAvg: stats.averageRetries,
counter: stats.retried,
newValue: res.svcStatus.retries
})
}
// Check token for userid
let userId = res.req.userObject?.userId || 'unknown'
// Increment user count for this operationId
stats.users[userId] = (stats.users[userId] || 0) + 1
// Check token for client id
let client = res.req.access_token?.azp || 'unknown'
// Increment client count for this operationId
stats.clients[client] = (stats.clients[client] || 0) + 1
// Increment elevated request count if elevate query param is true
if (res.req.query?.elevate === true) {
stats.elevatedRequests = (stats.elevatedRequests || 0) + 1
}
// If projections are defined, track stats for each projection
if (res.req.query?.projection?.length > 0) {
stats.projections = stats.projections || {}
for (const projection of res.req.query.projection) {
// Ensure the projection stats object exists
stats.projections[projection] = stats.projections[projection] || {
totalRequests: 0,
minDuration: Infinity,
maxDuration: 0,
totalDuration: 0,
retried: 0,
averageRetries: 0,
get averageDuration() {
return this.totalRequests ? Math.round(this.totalDuration / this.totalRequests) : 0
}
}
const projStats = stats.projections[projection]
// Increment projection count and update duration stats
projStats.totalRequests++
projStats.minDuration = Math.min(projStats.minDuration, durationMs)
projStats.maxDuration = Math.max(projStats.maxDuration, durationMs)
projStats.totalDuration += durationMs
// Update retries
if (res.svcStatus?.retries) {
projStats.retried++
projStats.averageRetries = projStats.averageRetries + (res.svcStatus.retries - projStats.averageRetries) / projStats.retried
}
}
}
function runningAverage({currentAvg, counter, newValue}) {
return currentAvg + (newValue - currentAvg) / counter
}
}
module.exports = {
requestLogger,
sanitizeHeaders,
serializeRequest,
serializeEnvironment,
writeError,
writeWarn,
writeInfo,
writeDebug,
requestStats,
loggerEvents,
}
================================================
FILE: api/source/utils/parsers.js
================================================
const {XMLParser} = require('fast-xml-parser')
const he = require('he')
module.exports.benchmarkFromXccdf = function (xccdfData) {
try {
const parser = new XMLParser({
allowBooleanAttributes: false,
attributeNamePrefix: "",
textNodeName: "_",
ignoreAttributes: false,
removeNSPrefix: true,
parseTagValue: false,
parseAttributeValue: false,
trimValues: true,
processEntities: { enabled: true, maxTotalExpansions: 200000 },
isArray: (name, jpath, isLeafNode, isAttribute) => !isAttribute,
alwaysCreateTextNode: true,
tagValueProcessor: (name, value) => he.decode(value)
})
const j = parser.parse(xccdfData.toString())
let bIn, isScap=false
if (j['data-stream-collection']?.[0]) {
// SCAP
const components = j['data-stream-collection'][0].component
const candidate = components?.find(component => 'Benchmark' in component)
if (candidate?.Benchmark?.[0]) {
bIn = candidate.Benchmark[0]
isScap = true
}
else {
throw new Error("Cannot parse as a DISA SCAP benchmark. No Benchmark element found.")
}
}
else if (j.Benchmark?.[0]) {
// Manual STIG
bIn = j.Benchmark[0]
}
else {
throw new Error("Cannot parse XML document as STIG or SCAP.")
}
const groups = bIn.Group.map(group => {
const rules = group.Rule.map(rule => {
const checks = rule.check ? rule.check.map(check => ({
system: check.system,
content: isScap? check['check-content-ref']?.[0]?._ : check['check-content']?.[0]?._
})) : []
const fixes = rule.fixtext ? rule.fixtext.map(fix => ({
fixref: fix.fixref,
text: fix._
})) : []
const idents = rule.ident ? rule.ident.map(ident => ({
ident: ident._,
system: ident.system
})) : []
// The description element's value is often not well-formed XML, so we fallback on extracting content between expected tags
function parseRuleDescription (d) {
const parsed = {}
const propMap = {
vulnDiscussion: 'VulnDiscussion',
falsePositives: 'FalsePositives',
falseNegatives: 'FalseNegatives',
documentable: 'Documentable',
mitigations: 'Mitigations',
severityOverrideGuidance: 'SeverityOverrideGuidance',
potentialImpacts: 'PotentialImpacts',
thirdPartyTools: 'ThirdPartyTools',
mitigationControl: 'MitigationControl',
responsibility: 'Responsibility',
iacontrols: 'IAControls'
}
for (const prop in propMap) {
const re = new RegExp(`<${propMap[prop]}>([\\s\\S]*)${propMap[prop]}>`)
const result = re.exec(d)
parsed[propMap[prop]] = result && result.length > 1 ? result[1] : null
}
if (parsed.Responsibility) {
parsed.Responsibility = parsed.Responsibility.replace(/<\/Responsibility>/g, ', ')
}
return parsed
}
const desc = parseRuleDescription(rule.description?.[0]?._)
return {
ruleId: rule.id,
version: rule.version?.[0]._ || null,
title: rule.title?.[0]._ || null,
severity: rule.severity || null,
weight: rule.weight || null,
vulnDiscussion: desc.VulnDiscussion || null,
falsePositives: desc.FalsePositives || null,
falseNegatives: desc.FalseNegatives || null,
documentable: desc.Documentable || null,
mitigations: desc.Mitigations || null,
severityOverrideGuidance: desc.SeverityOverrideGuidance || null,
potentialImpacts: desc.PotentialImpacts || null,
thirdPartyTools: desc.ThirdPartyTools || null,
mitigationControl: desc.MitigationControl || null,
responsibility: desc.Responsibility || null,
iacontrols: desc.IAControls || null,
checks,
fixes,
idents
}
})
return {
groupId: group.id,
title: group.title[0]._ || null,
rules: rules
}
})
const [releaseInfo, release, benchmarkDate] = /Release:\s+(\S+)\s+Benchmark Date:\s+(.*)/g.exec(bIn['plain-text'][0]._)
return {
benchmarkId: bIn.id,
title: bIn.title?.[0]._,
scap: isScap,
revision: {
revisionStr: `V${bIn.version?.[0]._}R${release}`,
version: bIn.version?.[0]._,
release,
releaseInfo,
benchmarkDate,
benchmarkDate8601: benchmarkDateTo8601(benchmarkDate),
status: bIn.status?.[0]._ || null,
statusDate: bIn.status?.[0].date || null,
description: bIn.description?.[0]._ || null,
groups
}
}
}
catch (e) {
throw (e)
}
function benchmarkDateTo8601(benchmarkDate) {
const monthToNum = {
'Jan': '01',
'January': '01',
'Feb': '02',
'February': '02',
'Mar': '03',
'March': '03',
'Apr': '04',
'April': '04',
'May': '05',
'Jun': '06',
'June': '06',
'Jul': '07',
'July': '07',
'Aug': '08',
'August': '08',
'Sep': '09',
'Sept': '09',
'September': '09',
'Oct': '10',
'October': '10',
'Nov': '11',
'November': '11',
'Dec': '12',
'December': '12'
};
let [day, monStr, year] = benchmarkDate.split(/\s+/);
return `${year}-${monthToNum[monStr]}-${day}`
}
}
================================================
FILE: api/source/utils/roles.js
================================================
module.exports.ROLES = {
'Restricted': 1,
'Full': 2,
'Manage': 3,
'Owner': 4
}
================================================
FILE: api/source/utils/serializeError.js
================================================
// MIT License
// Copyright (c) Sindre Sorhus (https://sindresorhus.com)
// Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
// The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
'use strict';
class NonError extends Error {
constructor(message) {
super(NonError._prepareSuperMessage(message));
Object.defineProperty(this, 'name', {
value: 'NonError',
configurable: true,
writable: true
});
if (Error.captureStackTrace) {
Error.captureStackTrace(this, NonError);
}
}
static _prepareSuperMessage(message) {
try {
return JSON.stringify(message);
} catch {
return String(message);
}
}
}
const commonProperties = [
{property: 'name', enumerable: false},
{property: 'message', enumerable: false},
{property: 'stack', enumerable: false},
{property: 'code', enumerable: true}
];
const isCalled = Symbol('.toJSON called');
const toJSON = from => {
from[isCalled] = true;
const json = from.toJSON();
delete from[isCalled];
return json;
};
const destroyCircular = ({
from,
seen,
to_,
forceEnumerable,
maxDepth,
depth
}) => {
const to = to_ || (Array.isArray(from) ? [] : {});
seen.push(from);
if (depth >= maxDepth) {
return to;
}
if (typeof from.toJSON === 'function' && from[isCalled] !== true) {
return toJSON(from);
}
for (const [key, value] of Object.entries(from)) {
if (typeof Buffer === 'function' && Buffer.isBuffer(value)) {
to[key] = '[object Buffer]';
continue;
}
if (typeof value === 'function') {
continue;
}
if (!value || typeof value !== 'object') {
to[key] = value;
continue;
}
if (!seen.includes(from[key])) {
depth++;
to[key] = destroyCircular({
from: from[key],
seen: seen.slice(),
forceEnumerable,
maxDepth,
depth
});
continue;
}
to[key] = '[Circular]';
}
for (const {property, enumerable} of commonProperties) {
if (typeof from[property] === 'string') {
Object.defineProperty(to, property, {
value: from[property],
enumerable: forceEnumerable ? true : enumerable,
configurable: true,
writable: true
});
}
}
return to;
};
const serializeError = (value, options = {}) => {
const {maxDepth = Number.POSITIVE_INFINITY} = options;
if (typeof value === 'object' && value !== null) {
return destroyCircular({
from: value,
seen: [],
forceEnumerable: true,
maxDepth,
depth: 0
});
}
// People sometimes throw things besides Error objects…
if (typeof value === 'function') {
// `JSON.stringify()` discards functions. We do too, unless a function is thrown directly.
return `[Function: ${(value.name || 'anonymous')}]`;
}
return value;
};
const deserializeError = (value, options = {}) => {
const {maxDepth = Number.POSITIVE_INFINITY} = options;
if (value instanceof Error) {
return value;
}
if (typeof value === 'object' && value !== null && !Array.isArray(value)) {
const newError = new Error(); // eslint-disable-line unicorn/error-message
destroyCircular({
from: value,
seen: [],
to_: newError,
maxDepth,
depth: 0
});
return newError;
}
return new NonError(value);
};
module.exports = {
serializeError,
deserializeError
};
================================================
FILE: api/source/utils/serializers.js
================================================
const {promises: fs} = require('fs')
const path = require('path')
const XlsxTemplate = require('xlsx-template')
module.exports.mccastPoamObjectFromFindings = function (findings, defaults = {}) {
const vuln = findings.map( finding => ({
authPackage: defaults.mccastAuthName,
name: finding.rules[0].title,
dateId: finding.stigs[0].ruleCount === 0 ? finding.stigs[0].benchmarkDate : '',
stigInfo: 'STIG Finding',
status: defaults.status,
packageId: defaults.mccastPackageId,
date: defaults.date,
startDate: '',
endDate: '',
securityChecks: finding.rules[0].ruleId || finding.groupId,
control: finding.ccis.map( cci => `DoD RMF-${defaults.mccastPackageId}-${cci.apAcronym?.replace(/\./g,' ')}-CNSSI 1253`).join('\n'),
resultingRisk: finding.severity === 'medium' ? 'Moderate' : `${finding.severity.charAt(0).toUpperCase()}${finding.severity.slice(1)}`,
weakness: finding.rules[0].vulnDiscussion,
mitigations: '',
comments: finding.stigs[0].ruleCount === 0 ? '' : finding.ccis.map( cci => `CCI-${cci.cci}`).join('\n'),
assets: finding.assets.map( asset => asset.name ).join('\n'),
mav: '',
mac: '',
mpr: '',
mui: '',
ms: '',
mi: '',
ma: ''
}))
return {vuln}
}
module.exports.poamObjectFromFindings = function (findings, defaults = {}) {
const vuln = findings.map( finding => ({
desc: `Title:\n${finding.rules[0].title}\n\nDescription:\n${finding.rules[0].vulnDiscussion}`,
control: finding.ccis.map( cci => cci.apAcronym).join('\n'),
office: defaults.office,
securityChecks: finding.ruleId || finding.groupId,
resourcesRequired: '',
date: defaults.date,
milestone: `Resolve this finding. ${defaults.date}`,
milestoneChanges: `Resolve this finding. ${defaults.date}`,
stigInfo: finding.stigs.map( stig =>
`${stig.benchmarkId}\n${stig.revisionStr}\nBenchmark Date: ${stig.benchmarkDate}` ).join('\n\n'),
status: defaults.status,
comments: finding.ccis.map( cci => `CCI-${cci.cci}`).join('\n'),
rawSeverity: finding.severity === 'medium' ? 'II' : finding.severity === 'low' ? 'III' : finding.severity === 'high' ? 'I' : 'Mixed',
assets: finding.assets.map( asset => asset.name ).join('\n'),
mitigations: '',
predisposingConditions: '',
severity: finding.severity === 'medium' ? 'Moderate' : `${finding.severity.charAt(0).toUpperCase()}${finding.severity.slice(1)}`, // uppercase first letter
threatRelevance: '',
threatDescription: '',
likelihood: '',
impact: '',
impactDescription: '',
residualRiskLevel: finding.severity === 'medium' ? 'Moderate' : `${finding.severity.charAt(0).toUpperCase()}${finding.severity.slice(1)}`,
recommendations: '',
resultingRisk: finding.severity === 'medium' ? 'Moderate' : `${finding.severity.charAt(0).toUpperCase()}${finding.severity.slice(1)}`,
}))
return {vuln}
}
module.exports.xlsxFromPoamObject = async function (substitutions, format) {
const templateFiles = {
EMASS: 'poam-template.xlsx',
MCCAST: 'poam-template-mccast.xlsx'
}
const templateData = await fs.readFile(path.join(__dirname, templateFiles[format]))
const template = new XlsxTemplate()
await template.loadTemplate(templateData)
await template.substitute(1, substitutions)
return await template.generate({type: 'nodebuffer'})
}
================================================
FILE: api/source/utils/state.js
================================================
const EventEmitter = require('events')
const logger = require('./logger')
/**
* Represents the state of the API.
* @typedef {'starting' | 'fail' | 'available' | 'unavailable' | 'stop'} StateString
*/
/**
* @typedef {Object} DependencyStatus
* @property {boolean} db - The status of the database dependency.
* @property {boolean} oidc - The status of the OIDC dependency.
*/
/**
* Class representing the state of the API.
* @extends EventEmitter
*/
class State extends EventEmitter {
/** @type {StateString} */
#currentState
/** @type {StateString} */
#previousState
/** @type {Date} */
#stateDate
/** @type {DependencyStatus} */
#dependencyStatus
/** @type {Object} */
#dbPool
/** @type {Object} */
#endpoints
/** @type {Number} */
#changeTimeoutId
/**
* Creates an instance of State.
* @param {Object} options - Options for initializing the state.
* @param {StateString} [options.initialState='starting'] - The initial state of the API.
*/
constructor({
initialState = 'starting',
endpoints = {
ui: {
current: '/',
next: ''
}
}
} = {}) {
super()
this.#currentState = initialState
this.#stateDate = new Date()
this.#dependencyStatus = {
db: false,
oidc: false
}
this.#endpoints = endpoints
}
/**
* Emits 'state-changed', passing the previous and current state and dependency status.
* @private
*/
#emitStateChangedEvent() {
this.emit('state-changed', this.#currentState, this.#previousState, this.#dependencyStatus)
}
#emitDependencyChangeEvent() {
this.emit('dependency-changed', this.#dependencyStatus)
}
/**
* Sets the state based on the dependency status.
* @private
*/
#setStateFromDependencyStatus() {
if (this.#dependencyStatus.db && this.#dependencyStatus.oidc) {
this.setState('available')
}
else {
this.setState(this.#currentState === 'starting' ? 'starting' : 'unavailable')
}
}
/**
* Sets the state to the provided state and emits state-changed event.
* @param {StateString} state - The new state.
*/
setState(state) {
if (this.#currentState === state) return
this.#previousState = this.#currentState
this.#currentState = state
this.#stateDate = new Date()
this.#emitStateChangedEvent()
}
/**
* Sets the status of the database dependency.
* @param {boolean} status - The new status of the database dependency.
*/
setDbStatus(status) {
if (this.#dependencyStatus.db === status) return
this.#dependencyStatus.db = status
this.#emitDependencyChangeEvent()
this.#setStateFromDependencyStatus()
}
/**
* Sets the status of the OIDC dependency.
* @param {boolean} status - The new status of the OIDC dependency.
*/
setOidcStatus(status) {
if (this.#dependencyStatus.oidc === status) return
this.#dependencyStatus.oidc = status
this.#emitDependencyChangeEvent()
this.#setStateFromDependencyStatus()
}
/**
* Gets the current state.
* @type {StateString}
* @readonly
*/
get currentState() {
return this.#currentState
}
/**
* Gets the dependency status.
* @type {DependencyStatus}
* @readonly
*/
get dependencyStatus() {
return {...this.#dependencyStatus}
}
/**
* Sets the database pool.
* @param {Object} pool - The new database pool.
*/
set dbPool(pool) {
this.#dbPool = pool
}
/**
* Gets the database pool.
* @type {Object}
* @readonly
*/
get dbPool() {
return this.#dbPool
}
/**
* Gets the API state.
* @type {Object}
* @readonly
*/
get apiState() {
return {
currentState: this.#currentState,
since: this.#stateDate,
dependencies: this.#dependencyStatus,
endpoints: this.#endpoints,
}
}
}
const state = new State()
state.on('state-changed', async (currentState, previousState, dependencyStatus) => {
logger.writeInfo('state','state-changed', {currentState, previousState, dependencyStatus})
let exitCode = 0
switch (currentState) {
case 'fail':
exitCode = 1
logger.writeError('state','fail', {message:'Application failed', exitCode})
process.exit(exitCode)
break
case 'stop':
try {
await state.dbPool?.end()
}
catch (err) {
logger.writeError('state','stop', {message:'Error closing database pool', error: serializeError(err)})
}
logger.writeInfo('state','stop', {message:'Application stopped', exitCode})
process.exit(exitCode)
break
}
})
module.exports = state
================================================
FILE: api/source/utils/writer.js
================================================
const escape = require ('./escape.js')
let ResponsePayload = function(code, payload) {
this.code = code;
this.payload = payload;
}
exports.respondWithCode = function(code, payload) {
return new ResponsePayload(code, payload);
}
let writeJson = exports.writeJson = function(response, arg1, arg2) {
let code;
let payload;
if(arg1 && arg1 instanceof ResponsePayload) {
writeJson(response, arg1.payload, arg1.code);
return;
}
if(arg2 && Number.isInteger(arg2)) {
code = arg2;
}
else {
if(arg1 && Number.isInteger(arg1)) {
code = arg1;
}
}
if(code && arg1) {
payload = arg1;
}
else if(arg1) {
payload = arg1;
}
if(!code) {
// if no response code given, we default to 200
code = 200;
}
if (typeof payload == 'undefined') {
code = 204
}
if (payload instanceof Error) {
payload = JSON.stringify(payload, Object.getOwnPropertyNames(payload), 2);
code = 500
}
else {
payload = JSON.stringify(payload);
}
response.writeHead(code, {
'Content-Type': 'application/json',
'Cache-control': 'no-store'
});
response.end(payload);
}
exports.writeInlineFile = function(response, payload, filename, contentType) {
response.writeHead(200, {
'Content-Type': contentType,
'Content-Disposition': `inline; filename="${escape.escapeFilename(filename)}"`,
'Access-Control-Expose-Headers': 'Content-Disposition'
})
response.write(payload)
response.end()
}
exports.writeWithContentType = function(response, {payload, status = "200", contentType = "application/json"}) {
response.writeHead(status, {
'Content-Type': contentType
})
response.end(payload)
}
exports.writeNoContent = function (response) {
response.writeHead(204)
response.end()
}
================================================
FILE: api/source/utils/xlsx-template-js-zip-upgrade/LICENSE
================================================
Copyright (c) 2013-2018 Martin Aspeli, 2018-2020 Andrii Kurdiumov
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
================================================
FILE: api/source/utils/xlsx-template-js-zip-upgrade/README.md
================================================
# XLSX Template
[](http://travis-ci.org/optilude/xlsx-template)
This module provides a means of generating "real" Excel reports (i.e. not CSV
files) in NodeJS applications.
The basic principle is this: You create a template in Excel. This can be
formatted as you wish, contain formulae etc. In this file, you put placeholders
using a specific syntax (see below). In code, you build a map of placeholders
to values and then load the template, substitute the placeholders for the
relevant values, and generate a new .xlsx file that you can then serve to the
user.
## Placeholders
Placeholders are inserted in cells in a spreadsheet. It does not matter how
those cells are formatted, so e.g. it is OK to insert a placeholder (which is
text content) into a cell formatted as a number or currecy or date, if you
expect the placeholder to resolve to a number or currency or date.
### Scalars
Simple placholders take the format `${name}`. Here, `name` is the name of a
key in the placeholders map. The value of this placholder here should be a
scalar, i.e. not an array or object. The placeholder may appear on its own in a
cell, or as part of a text string. For example:
| Extracted on: | ${extractDate} |
might result in (depending on date formatting in the second cell):
| Extracted on: | Jun-01-2013 |
Here, `extractDate` may be a date and the second cell may be formatted as a
number.
Inside scalars there possibility to use array indexers.
For example:
Given data
var template = { extractDates: ["Jun-01-2113", "Jun-01-2013" ]}
which will be applied to following template
| Extracted on: | ${extractDates[0]} |
will results in the
| Extracted on: | Jun-01-2113 |
### Columns
You can use arrays as placeholder values to indicate that the placeholder cell
is to be replicated across columns. In this case, the placeholder cannot appear
inside a text string - it must be the only thing in its cell. For example,
if the placehodler value `dates` is an array of dates:
| ${dates} |
might result in:
| Jun-01-2013 | Jun-02-2013 | Jun-03-2013 |
### Tables
Finally, you can build tables made up of multiple rows. In this case, each
placeholder should be prefixed by `table:` and contain both the name of the
placeholder variable (a list of objects) and a key (in each object in the list).
For example:
| Name | Age |
| ${table:people.name} | ${table:people.age} |
If the replacement value under `people` is an array of objects, and each of
those objects have keys `name` and `age`, you may end up with something like:
| Name | Age |
| John Smith | 20 |
| Bob Johnson | 22 |
If a particular value is an array, then it will be repeated across columns as
above.
## Generating reports
To make this magic happen, you need some code like this:
```
var XlsxTemplate = require('xlsx-template');
// Load an XLSX file into memory
fs.readFile(path.join(__dirname, 'templates', 'template1.xlsx'), async function(err, data) {
// Create a template
var template = new XlsxTemplate();
await template.loadTemplate(data);
// Replacements take place on first sheet
var sheetNumber = 1;
// Set up some placeholder values matching the placeholders in the template
var values = {
extractDate: new Date(),
dates: [ new Date("2013-06-01"), new Date("2013-06-02"), new Date("2013-06-03") ],
people: [
{name: "John Smith", age: 20},
{name: "Bob Johnson", age: 22}
]
};
// Perform substitution
await template.substitute(sheetNumber, values);
// Get binary data
var data = await template.generate();
// ...
});
```
At this stage, `data` is a string blob representing the compressed archive that
is the `.xlsx` file (that's right, a `.xlsx` file is a zip file of XML files,
if you didn't know). You can send this back to a client, store it to disk,
attach it to an email or do whatever you want with it.
You can pass options to `generate()` to set a different return type. use
`{type: 'uint8array'}` to generate a `Uint8Array`, `arraybuffer`, `blob`,
`nodebuffer` to generate an `ArrayBuffer`, `Blob` or `nodebuffer`, or
`base64` to generate a base64-encoded string.
## Caveats
* The spreadsheet must be saved in `.xlsx` format. `.xls`, `.xlsb` or `.xlsm`
won't work.
* Column (array) and table (array-of-objects) insertions cause rows and cells to
be inserted or removed. When this happens, only a limited number of
adjustments are made:
* Merged cells and named cells/ranges to the right of cells where insertions
or deletions are made are moved right or left, appropriately. This may
not work well if cells are merged across rows, unless all rows have the
same number of insertions.
* Merged cells, named tables or named cells/ranges below rows where further
rows are inserted are moved down.
Formulae are not adjusted.
* As a corollary to this, it is not always easy to build formulae that refer
to cells in a table (e.g. summing all rows) where the exact number of rows
or columns is not known in advance. There are two strategies for dealing
with this:
* Put the table as the last (or only) thing on a particular sheet, and
use a formula that includes a large number of rows or columns in the
hope that the actual table will be smaller than this number.
* Use named tables. When a placeholder in a named table causes columns or
rows to be added, the table definition (i.e. the cells included in the
table) will be updated accordingly. You can then use things like
`TableName[ColumnName]` in your formula to refer to all values in a given
column in the table as a logical range.
* Placeholders only work in simple cells and tables, pivot tables or
other such things.
## Changelog
### Version 0.2.0
* Add ability copy and delete sheets.
### Version 0.0.7
* Fix bug with calculating when adding columns
### Version 0.0.6
* You can now pass `options` to `generate()`, which are passed to JSZip
* Fix setting of sheet when growing the sheet
* Fix corruption of sheet when writing dates
* Fix corruption of sheet when calculating calcChain
### Version 0.0.5
* Mysterious
### Version 0.0.4
Merged pending pull requests
* Deletion of the sheets.
### Version 0.0.3
Merged a number of overdue pull requests, including:
* Windows support
* Support for table footers
* Documentation improvements
### Version 0.0.2
* Fix a potential issue with the typing of string indices that could cause the
first string to not render correctly if it contained a substitution.
### Version 0.0.1
* Initial release
================================================
FILE: api/source/utils/xlsx-template-js-zip-upgrade/lib/index.d.ts
================================================
import * as etree from "elementtree";
import * as JSZip from "jszip";
export interface TemplatePlaceholder{
type: string;
string?: string;
full: boolean;
name: string;
key: string;
placeholder?: string
}
export interface NamedTable{
filename: string;
root: etree.Element;
}
export default class Workbook
{
protected readonly sharedStrings: string[];
protected readonly workbook: etree.ElementTree;
protected readonly archive: JSZip;
protected readonly workbookPath: string;
protected readonly calcChainPath?: string;
constructor(data? : Buffer);
public deleteSheet(sheetName : string) : this;
public copySheet(sheetName : string, copyName : string) : this;
public loadTemplate(data : Buffer) : void;
public substitute(sheetName : string | number, substitutions : Object) : void;
public generate(options? : GenerateOptions) : T;
// need typing properly
protected _rebuild() : void;
protected writeSharedStrings() : void;
protected addSharedString(s : any) : any; // I think s is a string? Not sure what its return "idx" is though, I think it's a number? Is "idx" short for "index"?
protected stringIndex(s : any) : any; // returns idx
protected replaceString(oldString : string, newString : string) : any; // returns idx
protected loadSheets(prefix : any, workbook : etree.ElementTree, workbookRels : any) : any[];
protected loadSheet(sheet : any) : { filename : any, name : any, id : any, root : any }; // this could definitely return a "Sheet" interface/class
protected loadTables(sheet : any, sheetFilename : any) : any;
protected writeTables(tables : any) : void;
protected substituteHyperlinks(sheetFilename : any, substitutions : any) : void;
protected substituteTableColumnHeaders(tables : any, substitutions : any) : void;
protected extractPlaceholders(string : any) : any[];
protected splitRef(ref : any) : { table : any, colAbsolute : any, col : any, rowAbsolute : any, row : any }
protected joinRef(ref : any) : string;
protected nextCol(ref : any) : string;
protected nextRow(ref : any) : string
protected charToNum(str : string) : number;
protected numToChar(num : number) : string;
protected isRange(ref : any) : boolean;
protected isWithin(ref : any, startRef : any, endRef : any) : boolean;
protected stringify(value : any) : string;
protected insertCellValue(cell : any, substitution : any) : string;
protected substituteScalar(cell : any, string: string, placeholder: TemplatePlaceholder, substitution: any);
protected substituteArray(cells : any[], cell : any, substitution : any);
protected substituteTable(row : any, newTableRows : any, cells : any[], cell : any, namedTables : any, substitution : any, key : any) : any;
protected cloneElement(element : any, deep? : any) : any;
protected replaceChildren(parent : any, children : any) : void;
protected getCurrentRow(row : any, rowsInserted : any) : number;
protected getCurrentCell(cell : any, currentRow : any, cellsInserted : any) : string;
protected updateRowSpan(row : any, cellsInserted : any) : any;
protected splitRange(range : string) : any;
protected joinRange(range : any) : string
protected pushRight(workbook : etree.ElementTree, sheet : any, currentCell : any, numCols : any) : any;
protected pushDown(workbook : etree.ElementTree, sheets : any, tables : any, currentRow : any, numRows : any) : any;
}
export interface GenerateOptions
{
type : "uint8array" | "arraybuffer" | "blob" | "nodebuffer" | "base64";
}
================================================
FILE: api/source/utils/xlsx-template-js-zip-upgrade/lib/index.js
================================================
/*jshint globalstrict:true, devel:true */
/*eslint no-var:0 */
/*global require, module, Buffer */
"use strict";
var path = require('path'),
JSZip = require('jszip'),
etree = require('elementtree');
module.exports = (function() {
var DOCUMENT_RELATIONSHIP = "http://schemas.openxmlformats.org/officeDocument/2006/relationships/officeDocument",
CALC_CHAIN_RELATIONSHIP = "http://schemas.openxmlformats.org/officeDocument/2006/relationships/calcChain",
SHARED_STRINGS_RELATIONSHIP = "http://schemas.openxmlformats.org/officeDocument/2006/relationships/sharedStrings",
HYPERLINK_RELATIONSHIP = "http://schemas.openxmlformats.org/officeDocument/2006/relationships/hyperlink";
/**
* Create a new workbook. and call `loadTemplate` later.
*/
var Workbook = function() {
var self = this;
self.archive = null;
self.sharedStrings = [];
self.sharedStringsLookup = {};
};
var _get_simple = function (obj, desc) {
if (desc.indexOf("[") >=0 ) {
var specification = desc.split(/[[[\]]/);
var property = specification[0];
var index = specification[1];
return obj[property][index];
}
return obj[desc];
}
/**
* Based on http://stackoverflow.com/questions/8051975
* Mimic https://lodash.com/docs#get
*/
var _get = function(obj, desc, defaultValue) {
var arr = desc.split('.');
try {
while (arr.length) {
obj = _get_simple(obj, arr.shift());
}
} catch(ex) {
/* invalid chain */
obj = undefined;
}
return obj === undefined ? defaultValue : obj;
}
/**
* Delete unused sheets if needed
*/
Workbook.prototype.deleteSheet = function(sheetName){
var self = this;
var sheet = self.loadSheet(sheetName);
var sh = self.workbook.find("sheets/sheet[@sheetId='" + sheet.id + "']");
self.workbook.find("sheets").remove(sh);
var rel = self.workbookRels.find("Relationship[@Id='" + sh.attrib['r:id'] + "']");
self.workbookRels.remove(rel);
self._rebuild();
return self
};
/**
* Clone sheets in current workbook template
*/
Workbook.prototype.copySheet = function(sheetName, copyName){
var self = this;
var sheet = self.loadSheet(sheetName); //filename, name , id, root
var newSheetIndex = (self.workbook.findall("sheets/sheet").length+1).toString();
var fileName = 'worksheets' + '/' + 'sheet' + newSheetIndex + '.xml';
var arcName = self.prefix + '/' + fileName;
self.archive.file(arcName, etree.tostring(sheet.root) );
self.archive.files[arcName].options.binary = true;
var newSheet = etree.SubElement( self.workbook.find('sheets'), 'sheet' );
newSheet.attrib.name = copyName || 'Sheet' + newSheetIndex;
newSheet.attrib.sheetId = newSheetIndex;
newSheet.attrib['r:id'] = 'rId' + newSheetIndex;
var newRel = etree.SubElement(self.workbookRels, 'Relationship');
newRel.attrib.Type = 'http://schemas.openxmlformats.org/officeDocument/2006/relationships/worksheet';
newRel.attrib.Target = fileName;
self._rebuild();
// TODO: work with "definedNames"
// var defn = etree.SubElement(self.workbook.find('definedNames'), 'definedName');
//
return self
};
/**
* Partially rebuild after copy/delete sheets
*/
Workbook.prototype._rebuild = function(){
//each 'r:id' attribute in '\xl\workbook.xml'
//must point to correct 'Id' in xl\_rels\workbook.xml.rels
var self = this;
var order = ['worksheet', 'theme', 'styles','sharedStrings'];
self.workbookRels.findall("*")
.sort(function(rel1, rel2){ //using order
var index1 = order.indexOf( path.basename(rel1.attrib.Type) );
var index2 = order.indexOf( path.basename(rel2.attrib.Type) );
if ((index1 + index2) == 0) {
if(rel1.attrib.Id && rel2.attrib.Id) return rel1.attrib.Id.substring(3) - rel2.attrib.Id.substring(3);
return rel1._id - rel2._id;
}
return index1 - index2
})
.forEach(function(item, index) {
item.attrib.Id = 'rId' + (index+1);
})
self.workbook.findall("sheets/sheet").forEach(function(item, index) {
item.attrib['r:id'] = 'rId' + (index+1);
item.attrib.sheetId = (index+1).toString();
})
self.archive.file(self.prefix + '/' + '_rels' + '/' + path.basename(self.workbookPath) + '.rels', etree.tostring(self.workbookRels));
self.archive.file(self.workbookPath, etree.tostring(self.workbook));
self.sheets = self.loadSheets(self.prefix, self.workbook, self.workbookRels);
}
/**
* Load a .xlsx file from a byte array.
*/
Workbook.prototype.loadTemplate = async function(data) {
var self = this;
if(Buffer.isBuffer(data)) {
data = data.toString('binary');
}
self.archive = await new JSZip.loadAsync(data, {base64: false, checkCRC32: true});
// Load relationships
var rels = etree.parse(await self.archive.file("_rels/.rels").async("string")).getroot(),
workbookPath = rels.find("Relationship[@Type='" + DOCUMENT_RELATIONSHIP + "']").attrib.Target;
self.workbookPath = workbookPath;
self.prefix = path.dirname(workbookPath);
self.workbook = etree.parse(await self.archive.file(workbookPath).async("string")).getroot();
self.workbookRels = etree.parse(await self.archive.file(self.prefix + "/" + '_rels' + "/" + path.basename(workbookPath) + '.rels').async("string")).getroot();
self.sheets = self.loadSheets(self.prefix, self.workbook, self.workbookRels);
self.calChainRel = self.workbookRels.find("Relationship[@Type='" + CALC_CHAIN_RELATIONSHIP + "']")
if (self.calChainRel) {
self.calcChainPath = self.prefix + "/" + self.calChainRel.attrib.Target;
}
self.sharedStringsPath = self.prefix + "/" + self.workbookRels.find("Relationship[@Type='" + SHARED_STRINGS_RELATIONSHIP + "']").attrib.Target;
self.sharedStrings = [];
etree.parse(await self.archive.file(self.sharedStringsPath).async("string")).getroot().findall('si').forEach(function(si) {
var t = {text:''};
si.findall('t').forEach(function(tmp){
t.text += tmp.text;
});
si.findall('r/t').forEach(function(tmp){
t.text += tmp.text;
});
self.sharedStrings.push(t.text);
self.sharedStringsLookup[t.text] = self.sharedStrings.length - 1;
});
};
/**
* Interpolate values for the sheet with the given number (1-based) or
* name (if a string) using the given substitutions (an object).
*/
Workbook.prototype.substitute = async function(sheetName, substitutions) {
var self = this;
var sheet = await self.loadSheet(sheetName);
var dimension = sheet.root.find("dimension"),
sheetData = sheet.root.find("sheetData"),
currentRow = null,
totalRowsInserted = 0,
totalColumnsInserted = 0,
namedTables = await self.loadTables(sheet.root, sheet.filename),
rows = [];
sheetData.findall("row").forEach(function(row) {
row.attrib.r = currentRow = self.getCurrentRow(row, totalRowsInserted);
rows.push(row);
var cells = [],
cellsInserted = 0,
newTableRows = [];
row.findall("c").forEach(function(cell) {
var appendCell = true;
cell.attrib.r = self.getCurrentCell(cell, currentRow, cellsInserted);
// If c[@t="s"] (string column), look up /c/v@text as integer in
// `this.sharedStrings`
if(cell.attrib.t === "s") {
// Look for a shared string that may contain placeholders
var cellValue = cell.find("v"),
stringIndex = parseInt(cellValue.text, 10),
string = self.sharedStrings[stringIndex];
if(string === undefined) {
return;
}
// Loop over placeholders
self.extractPlaceholders(string).forEach(function(placeholder) {
// Only substitute things for which we have a substitution
var substitution = _get(substitutions, placeholder.name, ''),
newCellsInserted = 0;
if(placeholder.full && placeholder.type === "table" && substitution instanceof Array) {
newCellsInserted = self.substituteTable(
row, newTableRows,
cells, cell,
namedTables, substitution, placeholder.key
);
// don't double-insert cells
// this applies to arrays only, incorrectly applies to object arrays when there a single row, thus not rendering single row
if (newCellsInserted !== 0 || substitution.length) {
if (substitution.length === 1) {
appendCell = true;
}
if (substitution[0][placeholder.key] instanceof Array) {
appendCell = false;
}
}
// Did we insert new columns (array values)?
if(newCellsInserted !== 0) {
cellsInserted += newCellsInserted;
self.pushRight(self.workbook, sheet.root, cell.attrib.r, newCellsInserted);
}
} else if(placeholder.full && placeholder.type === "normal" && substitution instanceof Array) {
appendCell = false; // don't double-insert cells
newCellsInserted = self.substituteArray(
cells, cell, substitution
);
if(newCellsInserted !== 0) {
cellsInserted += newCellsInserted;
self.pushRight(self.workbook, sheet.root, cell.attrib.r, newCellsInserted);
}
} else {
if (placeholder.key) {
substitution = _get(substitutions, placeholder.name + '.' + placeholder.key);
}
string = self.substituteScalar(cell, string, placeholder, substitution);
}
});
}
// if we are inserting columns, we may not want to keep the original cell anymore
if(appendCell) {
cells.push(cell);
}
}); // cells loop
// We may have inserted columns, so re-build the children of the row
self.replaceChildren(row, cells);
// Update row spans attribute
if(cellsInserted !== 0) {
self.updateRowSpan(row, cellsInserted);
if(cellsInserted > totalColumnsInserted) {
totalColumnsInserted = cellsInserted;
}
}
// Add newly inserted rows
if(newTableRows.length > 0) {
newTableRows.forEach(function(row) {
rows.push(row);
++totalRowsInserted;
});
self.pushDown(self.workbook, sheet.root, namedTables, currentRow, newTableRows.length);
}
}); // rows loop
// We may have inserted rows, so re-build the children of the sheetData
self.replaceChildren(sheetData, rows);
// Update placeholders in table column headers
self.substituteTableColumnHeaders(namedTables, substitutions);
// Update placeholders in hyperlinks
await self.substituteHyperlinks(sheet.filename, substitutions);
// Update if we added rows or columns
if(dimension) {
if(totalRowsInserted > 0 || totalColumnsInserted > 0) {
var dimensionRange = self.splitRange(dimension.attrib.ref),
dimensionEndRef = self.splitRef(dimensionRange.end);
dimensionEndRef.row += totalRowsInserted;
dimensionEndRef.col = self.numToChar(self.charToNum(dimensionEndRef.col) + totalColumnsInserted);
dimensionRange.end = self.joinRef(dimensionEndRef);
dimension.attrib.ref = self.joinRange(dimensionRange);
}
}
//Here we are forcing the values in formulas to be recalculated
// existing as well as just substituted
sheetData.findall("row").forEach(function(row) {
row.findall("c").forEach(function(cell) {
var formulas = cell.findall('f');
if (formulas && formulas.length > 0) {
cell.findall('v').forEach(function(v){
cell.remove(v);
});
}
})
})
// Write back the modified XML trees
self.archive.file(sheet.filename, etree.tostring(sheet.root));
self.archive.file(self.workbookPath, etree.tostring(self.workbook));
// Remove calc chain - Excel will re-build, and we may have moved some formulae
if(self.calcChainPath && self.archive.file(self.calcChainPath)) {
self.archive.remove(self.calcChainPath);
}
await self.writeSharedStrings();
self.writeTables(namedTables);
};
/**
* Generate a new binary .xlsx file
*/
Workbook.prototype.generate = async function(options) {
var self = this;
if(!options) {
options = {
type: "binarystring"
}
}
return await self.archive.generateAsync(options);
};
// Helpers
// Write back the new shared strings list
Workbook.prototype.writeSharedStrings = async function() {
var self = this;
var root = etree.parse(await self.archive.file(self.sharedStringsPath).async("string")).getroot(),
children = root.getchildren();
root.delSlice(0, children.length);
self.sharedStrings.forEach(function(string) {
var si = new etree.Element("si"),
t = new etree.Element("t");
t.text = string;
si.append(t);
root.append(si);
});
root.attrib.count = self.sharedStrings.length;
root.attrib.uniqueCount = self.sharedStrings.length;
self.archive.file(self.sharedStringsPath, etree.tostring(root));
};
// Add a new shared string
Workbook.prototype.addSharedString = function(s) {
var self = this;
var idx = self.sharedStrings.length;
self.sharedStrings.push(s);
self.sharedStringsLookup[s] = idx;
return idx;
};
// Get the number of a shared string, adding a new one if necessary.
Workbook.prototype.stringIndex = function(s) {
var self = this;
var idx = self.sharedStringsLookup[s];
if(idx === undefined) {
idx = self.addSharedString(s);
}
return idx;
};
// Replace a shared string with a new one at the same index. Return the
// index.
Workbook.prototype.replaceString = function(oldString, newString) {
var self = this;
var idx = self.sharedStringsLookup[oldString];
if(idx === undefined) {
idx = self.addSharedString(newString);
} else {
self.sharedStrings[idx] = newString;
delete self.sharedStringsLookup[oldString];
self.sharedStringsLookup[newString] = idx;
}
return idx;
};
// Get a list of sheet ids, names and filenames
Workbook.prototype.loadSheets = function(prefix, workbook, workbookRels) {
var sheets = [];
workbook.findall("sheets/sheet").forEach(function(sheet) {
var sheetId = sheet.attrib.sheetId,
relId = sheet.attrib['r:id'],
relationship = workbookRels.find("Relationship[@Id='" + relId + "']"),
filename = prefix + "/" + relationship.attrib.Target;
sheets.push({
id: parseInt(sheetId, 10),
name: sheet.attrib.name,
filename: filename
});
});
return sheets;
};
// Get sheet a sheet, including filename and name
Workbook.prototype.loadSheet = async function(sheet) {
var self = this;
var info = null;
for(var i = 0; i < self.sheets.length; ++i) {
if((typeof(sheet) === "number" && self.sheets[i].id === sheet) || (self.sheets[i].name === sheet)) {
info = self.sheets[i];
break;
}
}
if(info === null && (typeof(sheet) === "number")){
//Get the sheet that corresponds to the 0 based index if the id does not work
info = self.sheets[sheet - 1];
}
if(info === null) {
throw new Error("Sheet " + sheet + " not found");
}
return {
filename: info.filename,
name: info.name,
id: info.id,
root: etree.parse(await self.archive.file(info.filename).async("string")).getroot()
};
};
// Load tables for a given sheet
Workbook.prototype.loadTables = async function(sheet, sheetFilename) {
var self = this;
var sheetDirectory = path.dirname(sheetFilename),
sheetName = path.basename(sheetFilename),
relsFilename = sheetDirectory + "/" + '_rels' + "/" + sheetName + '.rels',
relsFile = self.archive.file(relsFilename),
tables = []; // [{filename: ..., root: ....}]
if(relsFile === null) {
return tables;
}
var rels = etree.parse(await relsFile.async("string")).getroot();
for(let tablePart of sheet.findall("tableParts/tablePart")) {
var relationshipId = tablePart.attrib['r:id'],
target = rels.find("Relationship[@Id='" + relationshipId + "']").attrib.Target,
tableFilename = target.replace('..', self.prefix),
tableTree = etree.parse(await self.archive.file(tableFilename).async("string"));
tables.push({
filename: tableFilename,
root: tableTree.getroot()
});
}
return tables;
};
// Write back possibly-modified tables
Workbook.prototype.writeTables = function(tables) {
var self = this;
tables.forEach(function(namedTable) {
self.archive.file(namedTable.filename, etree.tostring(namedTable.root));
});
};
//Perform substitution in hyperlinks
Workbook.prototype.substituteHyperlinks = async function(sheetFilename, substitutions) {
let self = this;
const sheetDirectory = path.dirname(sheetFilename),
sheetName = path.basename(sheetFilename),
relsFilename = sheetDirectory + "/" + '_rels' + "/" + sheetName + '.rels',
relsFile = self.archive.file(relsFilename);
etree.parse(await self.archive.file(self.sharedStringsPath).async("string")).getroot();
if(relsFile === null) {
return;
}
const rels = etree.parse(await relsFile.async("string")).getroot();
const relationships = rels._children;
const newRelationships = [];
relationships.forEach(function(relationship){
newRelationships.push(relationship);
if(relationship.attrib.Type === HYPERLINK_RELATIONSHIP) {
let target = relationship.attrib.Target;
//Double-decode due to excel double encoding url placeholders
target = decodeURI(decodeURI(target));
self.extractPlaceholders(target).forEach(function (placeholder) {
const substitution = substitutions[placeholder.name];
if (substitution === undefined) {
return;
}
target = target.replace(placeholder.placeholder, self.stringify(substitution));
relationship.attrib.Target = encodeURI(target);
}
);
}
});
self.replaceChildren(rels, newRelationships);
self.archive.file(relsFilename, etree.tostring(rels));
};
// Perform substitution in table headers
Workbook.prototype.substituteTableColumnHeaders = function(tables, substitutions) {
var self = this;
tables.forEach(function(table) {
var root = table.root,
columns = root.find("tableColumns"),
autoFilter = root.find("autoFilter"),
tableRange = self.splitRange(root.attrib.ref),
idx = 0,
inserted = 0,
newColumns = [];
columns.findall("tableColumn").forEach(function(col) {
++idx;
col.attrib.id = Number(idx).toString();
newColumns.push(col);
var name = col.attrib.name;
self.extractPlaceholders(name).forEach(function(placeholder) {
var substitution = substitutions[placeholder.name];
if(substitution === undefined) {
return;
}
// Array -> new columns
if(placeholder.full && placeholder.type === "normal" && substitution instanceof Array) {
substitution.forEach(function(element, i) {
var newCol = col;
if(i > 0) {
newCol = self.cloneElement(newCol);
newCol.attrib.id = Number(++idx).toString();
newColumns.push(newCol);
++inserted;
tableRange.end = self.nextCol(tableRange.end);
}
newCol.attrib.name = self.stringify(element);
});
// Normal placeholder
} else {
name = name.replace(placeholder.placeholder, self.stringify(substitution));
col.attrib.name = name;
}
});
});
self.replaceChildren(columns, newColumns);
// Update range if we inserted columns
if(inserted > 0) {
columns.attrib.count = Number(idx).toString();
root.attrib.ref = self.joinRange(tableRange);
if(autoFilter !== null) {
// XXX: This is a simplification that may stomp on some configurations
autoFilter.attrib.ref = self.joinRange(tableRange);
}
}
//update ranges for totalsRowCount
var tableRoot = table.root,
tableRange = self.splitRange(tableRoot.attrib.ref),
tableStart = self.splitRef(tableRange.start),
tableEnd = self.splitRef(tableRange.end);
if (tableRoot.attrib.totalsRowCount) {
var autoFilter = tableRoot.find("autoFilter");
if(autoFilter !== null) {
autoFilter.attrib.ref = self.joinRange({
start: self.joinRef(tableStart),
end: self.joinRef(tableEnd),
});
}
++tableEnd.row;
tableRoot.attrib.ref = self.joinRange({
start: self.joinRef(tableStart),
end: self.joinRef(tableEnd),
});
}
});
};
// Return a list of tokens that may exist in the string.
// Keys are: `placeholder` (the full placeholder, including the `${}`
// delineators), `name` (the name part of the token), `key` (the object key
// for `table` tokens), `full` (boolean indicating whether this placeholder
// is the entirety of the string) and `type` (one of `table` or `cell`)
Workbook.prototype.extractPlaceholders = function(string) {
// Yes, that's right. It's a bunch of brackets and question marks and stuff.
var re = /\${(?:(.+?):)?(.+?)(?:\.(.+?))?}/g;
var match = null, matches = [];
while((match = re.exec(string)) !== null) {
matches.push({
placeholder: match[0],
type: match[1] || 'normal',
name: match[2],
key: match[3],
full: match[0].length === string.length
});
}
return matches;
};
// Split a reference into an object with keys `row` and `col` and,
// optionally, `table`, `rowAbsolute` and `colAbsolute`.
Workbook.prototype.splitRef = function(ref) {
var match = ref.match(/(?:(.+)!)?(\$)?([A-Z]+)(\$)?([0-9]+)/);
return {
table: match && match[1] || null,
colAbsolute: Boolean(match && match[2]),
col: match && match[3],
rowAbsolute: Boolean(match && match[4]),
row: parseInt(match && match[5], 10)
};
};
// Join an object with keys `row` and `col` into a single reference string
Workbook.prototype.joinRef = function(ref) {
return (ref.table? ref.table + "!" : "") +
(ref.colAbsolute? "$" : "") +
ref.col.toUpperCase() +
(ref.rowAbsolute? "$" : "" )+
Number(ref.row).toString();
};
// Get the next column's cell reference given a reference like "B2".
Workbook.prototype.nextCol = function(ref) {
var self = this;
ref = ref.toUpperCase();
return ref.replace(/[A-Z]+/, function(match) {
return self.numToChar(self.charToNum(match) + 1);
});
};
// Get the next row's cell reference given a reference like "B2".
Workbook.prototype.nextRow = function(ref) {
ref = ref.toUpperCase();
return ref.replace(/[0-9]+/, function(match) {
return (parseInt(match, 10) + 1).toString();
});
};
// Turn a reference like "AA" into a number like 27
Workbook.prototype.charToNum = function(str) {
var num = 0;
for(var idx = str.length - 1, iteration = 0; idx >= 0; --idx, ++iteration) {
var thisChar = str.charCodeAt(idx) - 64, // A -> 1; B -> 2; ... Z->26
multiplier = Math.pow(26, iteration);
num += multiplier * thisChar;
}
return num;
};
// Turn a number like 27 into a reference like "AA"
Workbook.prototype.numToChar = function(num) {
var str = "";
for(var i = 0; num > 0; ++i) {
var remainder = num % 26,
charCode = remainder + 64;
num = (num - remainder) / 26;
// Compensate for the fact that we don't represent zero, e.g. A = 1, Z = 26, but AA = 27
if(remainder === 0) { // 26 -> Z
charCode = 90;
--num;
}
str = String.fromCharCode(charCode) + str;
}
return str;
};
// Is ref a range?
Workbook.prototype.isRange = function(ref) {
return ref.indexOf(':') !== -1;
};
// Is ref inside the table defined by startRef and endRef?
Workbook.prototype.isWithin = function(ref, startRef, endRef) {
var self = this;
var start = self.splitRef(startRef),
end = self.splitRef(endRef),
target = self.splitRef(ref);
start.col = self.charToNum(start.col);
end.col = self.charToNum(end.col);
target.col = self.charToNum(target.col);
return (
start.row <= target.row && target.row <= end.row &&
start.col <= target.col && target.col <= end.col
);
};
// Turn a value of any type into a string
Workbook.prototype.stringify = function (value) {
if(value instanceof Date) {
//In Excel date is a number of days since 01/01/1900
// timestamp in ms to days + number of days from 1900 to 1970
return Number( (value.getTime()/(1000*60*60*24)) + 25569);
} else if(typeof(value) === "number" || typeof(value) === "boolean") {
return Number(value).toString();
} else if(typeof(value) === "string") {
return String(value).toString();
}
return "";
};
// Insert a substitution value into a cell (c tag)
Workbook.prototype.insertCellValue = function(cell, substitution) {
var self = this;
var cellValue = cell.find("v"),
stringified = self.stringify(substitution);
if (typeof substitution ==='string' && substitution[0] === '='){
//substitution, started with '=' is a formula substitution
var formula = new etree.Element("f");
formula.text = substitution.substr(1);
cell.insert(1, formula);
delete cell.attrib.t; //cellValue will be deleted later
return formula.text
}
if(typeof(substitution) === "number" || substitution instanceof Date) {
delete cell.attrib.t;
cellValue.text = stringified;
} else if(typeof(substitution) === "boolean" ) {
cell.attrib.t = "b";
cellValue.text = stringified;
} else {
cell.attrib.t = "s";
cellValue.text = Number(self.stringIndex(stringified)).toString();
}
return stringified;
};
// Perform substitution of a single value
Workbook.prototype.substituteScalar = function(cell, string, placeholder, substitution) {
var self = this;
if(placeholder.full) {
return self.insertCellValue(cell, substitution);
} else {
var newString = string.replace(placeholder.placeholder, self.stringify(substitution));
cell.attrib.t = "s";
return self.insertCellValue(cell, newString)
}
};
// Perform a columns substitution from an array
Workbook.prototype.substituteArray = function(cells, cell, substitution) {
var self = this;
var newCellsInserted = -1, // we technically delete one before we start adding back
currentCell = cell.attrib.r;
// add a cell for each element in the list
substitution.forEach(function(element) {
++newCellsInserted;
if(newCellsInserted > 0) {
currentCell = self.nextCol(currentCell);
}
var newCell = self.cloneElement(cell);
self.insertCellValue(newCell, element);
newCell.attrib.r = currentCell;
cells.push(newCell);
});
return newCellsInserted;
};
// Perform a table substitution. May update `newTableRows` and `cells` and change `cell`.
// Returns total number of new cells inserted on the original row.
Workbook.prototype.substituteTable = function(row, newTableRows, cells, cell, namedTables, substitution, key) {
var self = this,
newCellsInserted = 0; // on the original row
// if no elements, blank the cell, but don't delete it
if(substitution.length === 0) {
delete cell.attrib.t;
self.replaceChildren(cell, []);
} else {
var parentTables = namedTables.filter(function(namedTable) {
var range = self.splitRange(namedTable.root.attrib.ref);
return self.isWithin(cell.attrib.r, range.start, range.end);
});
substitution.forEach(function(element, idx) {
var newRow, newCell,
newCellsInsertedOnNewRow = 0,
newCells = [],
value = _get(element, key, '');
if(idx === 0) { // insert in the row where the placeholders are
if(value instanceof Array) {
newCellsInserted = self.substituteArray(cells, cell, value);
} else {
self.insertCellValue(cell, value);
}
} else { // insert new rows (or reuse rows just inserted)
// Do we have an existing row to use? If not, create one.
if((idx - 1) < newTableRows.length) {
newRow = newTableRows[idx - 1];
} else {
newRow = self.cloneElement(row, false);
newRow.attrib.r = self.getCurrentRow(row, newTableRows.length + 1);
newTableRows.push(newRow);
}
// Create a new cell
newCell = self.cloneElement(cell);
newCell.attrib.r = self.joinRef({
row: newRow.attrib.r,
col: self.splitRef(newCell.attrib.r).col
});
if(value instanceof Array) {
newCellsInsertedOnNewRow = self.substituteArray(newCells, newCell, value);
// Add each of the new cells created by substituteArray()
newCells.forEach(function(newCell) {
newRow.append(newCell);
});
self.updateRowSpan(newRow, newCellsInsertedOnNewRow);
} else {
self.insertCellValue(newCell, value);
// Add the cell that previously held the placeholder
newRow.append(newCell);
}
// expand named table range if necessary
parentTables.forEach(function(namedTable) {
var tableRoot = namedTable.root,
autoFilter = tableRoot.find("autoFilter"),
range = self.splitRange(tableRoot.attrib.ref);
if(!self.isWithin(newCell.attrib.r, range.start, range.end)) {
range.end = self.nextRow(range.end);
tableRoot.attrib.ref = self.joinRange(range);
if(autoFilter !== null) {
// XXX: This is a simplification that may stomp on some configurations
autoFilter.attrib.ref = tableRoot.attrib.ref;
}
}
});
}
});
}
return newCellsInserted;
};
// Clone an element. If `deep` is true, recursively clone children
Workbook.prototype.cloneElement = function(element, deep) {
var self = this;
var newElement = etree.Element(element.tag, element.attrib);
newElement.text = element.text;
newElement.tail = element.tail;
if(deep !== false) {
element.getchildren().forEach(function(child) {
newElement.append(self.cloneElement(child, deep));
});
}
return newElement;
};
// Replace all children of `parent` with the nodes in the list `children`
Workbook.prototype.replaceChildren = function(parent, children) {
parent.delSlice(0, parent.len());
children.forEach(function(child) {
parent.append(child);
});
};
// Calculate the current row based on a source row and a number of new rows
// that have been inserted above
Workbook.prototype.getCurrentRow = function(row, rowsInserted) {
return parseInt(row.attrib.r, 10) + rowsInserted;
};
// Calculate the current cell based on asource cell, the current row index,
// and a number of new cells that have been inserted so far
Workbook.prototype.getCurrentCell = function(cell, currentRow, cellsInserted) {
var self = this;
var colRef = self.splitRef(cell.attrib.r).col,
colNum = self.charToNum(colRef);
return self.joinRef({
row: currentRow,
col: self.numToChar(colNum + cellsInserted)
});
};
// Adjust the row `spans` attribute by `cellsInserted`
Workbook.prototype.updateRowSpan = function(row, cellsInserted) {
if(cellsInserted !== 0 && row.attrib.spans) {
var rowSpan = row.attrib.spans.split(':').map(function(f) { return parseInt(f, 10); });
rowSpan[1] += cellsInserted;
row.attrib.spans = rowSpan.join(":");
}
};
// Split a range like "A1:B1" into {start: "A1", end: "B1"}
Workbook.prototype.splitRange = function(range) {
var split = range.split(":");
return {
start: split[0],
end: split[1]
};
};
// Join into a a range like "A1:B1" an object like {start: "A1", end: "B1"}
Workbook.prototype.joinRange = function(range) {
return range.start + ":" + range.end;
};
// Look for any merged cell or named range definitions to the right of
// `currentCell` and push right by `numCols`.
Workbook.prototype.pushRight = function(workbook, sheet, currentCell, numCols) {
var self = this;
var cellRef = self.splitRef(currentCell),
currentRow = cellRef.row,
currentCol = self.charToNum(cellRef.col);
// Update merged cells on the same row, at a higher column
sheet.findall("mergeCells/mergeCell").forEach(function(mergeCell) {
var mergeRange = self.splitRange(mergeCell.attrib.ref),
mergeStart = self.splitRef(mergeRange.start),
mergeStartCol = self.charToNum(mergeStart.col),
mergeEnd = self.splitRef(mergeRange.end),
mergeEndCol = self.charToNum(mergeEnd.col);
if(mergeStart.row === currentRow && currentCol < mergeStartCol) {
mergeStart.col = self.numToChar(mergeStartCol + numCols);
mergeEnd.col = self.numToChar(mergeEndCol + numCols);
mergeCell.attrib.ref = self.joinRange({
start: self.joinRef(mergeStart),
end: self.joinRef(mergeEnd),
});
}
});
// Named cells/ranges
workbook.findall("definedNames/definedName").forEach(function(name) {
var ref = name.text;
if(self.isRange(ref)) {
var namedRange = self.splitRange(ref),
namedStart = self.splitRef(namedRange.start),
namedStartCol = self.charToNum(namedStart.col),
namedEnd = self.splitRef(namedRange.end),
namedEndCol = self.charToNum(namedEnd.col);
if(namedStart.row === currentRow && currentCol < namedStartCol) {
namedStart.col = self.numToChar(namedStartCol + numCols);
namedEnd.col = self.numToChar(namedEndCol + numCols);
name.text = self.joinRange({
start: self.joinRef(namedStart),
end: self.joinRef(namedEnd),
});
}
} else {
var namedRef = self.splitRef(ref),
namedCol = self.charToNum(namedRef.col);
if(namedRef.row === currentRow && currentCol < namedCol) {
namedRef.col = self.numToChar(namedCol + numCols);
name.text = self.joinRef(namedRef);
}
}
});
};
// Look for any merged cell, named table or named range definitions below
// `currentRow` and push down by `numRows` (used when rows are inserted).
Workbook.prototype.pushDown = function(workbook, sheet, tables, currentRow, numRows) {
var self = this;
var mergeCells = sheet.find("mergeCells");
// Update merged cells below this row
sheet.findall("mergeCells/mergeCell").forEach(function(mergeCell) {
var mergeRange = self.splitRange(mergeCell.attrib.ref),
mergeStart = self.splitRef(mergeRange.start),
mergeEnd = self.splitRef(mergeRange.end);
if(mergeStart.row > currentRow) {
mergeStart.row += numRows;
mergeEnd.row += numRows;
mergeCell.attrib.ref = self.joinRange({
start: self.joinRef(mergeStart),
end: self.joinRef(mergeEnd),
});
}
//add new merge cell
if (mergeStart.row == currentRow) {
for (var i = 1; i <= numRows; i++) {
var newMergeCell = self.cloneElement(mergeCell);
mergeStart.row += 1;
mergeEnd.row += 1;
newMergeCell.attrib.ref = self.joinRange({
start: self.joinRef(mergeStart),
end: self.joinRef(mergeEnd)
});
mergeCells.attrib.count += 1;
mergeCells._children.push(newMergeCell);
}
}
});
// Update named tables below this row
tables.forEach(function(table) {
var tableRoot = table.root,
tableRange = self.splitRange(tableRoot.attrib.ref),
tableStart = self.splitRef(tableRange.start),
tableEnd = self.splitRef(tableRange.end);
if(tableStart.row > currentRow) {
tableStart.row += numRows;
tableEnd.row += numRows;
tableRoot.attrib.ref = self.joinRange({
start: self.joinRef(tableStart),
end: self.joinRef(tableEnd),
});
var autoFilter = tableRoot.find("autoFilter");
if(autoFilter !== null) {
// XXX: This is a simplification that may stomp on some configurations
autoFilter.attrib.ref = tableRoot.attrib.ref;
}
}
});
// Named cells/ranges
workbook.findall("definedNames/definedName").forEach(function(name) {
var ref = name.text;
if(self.isRange(ref)) {
var namedRange = self.splitRange(ref),
namedStart = self.splitRef(namedRange.start),
namedEnd = self.splitRef(namedRange.end);
if(namedStart){
if(namedStart.row > currentRow) {
namedStart.row += numRows;
namedEnd.row += numRows;
name.text = self.joinRange({
start: self.joinRef(namedStart),
end: self.joinRef(namedEnd),
});
}
}
} else {
var namedRef = self.splitRef(ref);
if(namedRef.row > currentRow) {
namedRef.row += numRows;
name.text = self.joinRef(namedRef);
}
}
});
};
return Workbook;
})();
================================================
FILE: api/source/utils/xlsx-template-js-zip-upgrade/package.json
================================================
{
"name": "xlsx-template",
"version": "1.2.0",
"description": "Generate .xlsx (Excel) files from templates built in Excel",
"main": "./lib/index",
"files": [
"lib"
],
"author": {
"name": "Martin Aspeli"
},
"contributors": [
{
"name": "Martin Aspeli",
"email": "optilude@gmail.com"
},
{
"name": "Andrii Kurdiumov",
"email": "kant2002@gmail.com"
}
],
"license": "MIT",
"repository": {
"type": "git",
"url": "http://github.com/optilude/xlsx-template.git"
},
"bugs": {
"url": "http://github.com/optilude/xlsx-template/issues"
},
"licenses": [
{
"type": "MIT",
"url": "http://github.com/optilude/xlsx-template/raw/master/LICENSE"
}
],
"dependencies": {
"elementtree": "0.1.6",
"jszip": "^3.5.0"
}
}
================================================
FILE: client/README.md
================================================
# STIG Manager Web App
### Running the STIG Manager API and Web App from source
You must build the web app prior to starting the API. Assuming your shell is at the root of this repository:
```
$ cd client
$ ./build.sh
$ cd ../api/source
$ npm ci
$ node index.js
```
### If you wish to develop or modify the web app code
You must install the required modules. Assuming your shell is at the root of this repository:
```
$ cd client/src/js/modules
$ npm ci
```
and invoke the API with the envar `STIGMAN_CLIENT_DIRECTORY` set to `../../client/src`
```
$ cd ../api/source
$ npm ci
$ STIGMAN_CLIENT_DIRECTORY=../../client/src node index.js
```
================================================
FILE: client/build.sh
================================================
#!/bin/bash
# STIG Manager client distribution build script
#
# Requires nodejs and npm to install uglify-js
# npm install -g uglify-js
#
# Build artifacts will created in ./dist
set -e
echo "Client build starting"
# Change to this script directory
ScriptDir=$(dirname "$(realpath "$0")")
cd $ScriptDir
echo "Changed to $ScriptDir"
SrcDir=src
DistDir=dist
# Clean dist directory
echo "Cleaning $DistDir"
rm -rf $DistDir/*
# ExtJS
echo "Preparing ExtJS resources"
ExtResources="ext/adapter/ext/ext-base.js
ext/ext-all.js
ext/ux/GroupSummary.js
ext/resources/css/ext-all.css
ext/resources/css/xtheme-gray.css
ext/resources/images/default/shadow-c.png
ext/resources/images/default/shadow-lr.png
ext/resources/images/default/shadow.png
ext/resources/images/default/button/arrow.gif
ext/resources/images/default/dd/drop-no.gif
ext/resources/images/default/grid/loading.gif
ext/resources/images/default/grid/hmenu-asc.gif
ext/resources/images/default/grid/hmenu-desc.gif
ext/resources/images/default/grid/columns.gif
ext/resources/images/default/grid/grid-split.gif
ext/resources/images/default/grid/grid3-special-col-bg.gif
ext/resources/images/default/menu/menu.gif
ext/resources/images/default/tree/loading.gif
ext/resources/images/gray/button/btn.gif
ext/resources/images/gray/button/group-cs.gif
ext/resources/images/gray/button/group-tb.gif
ext/resources/images/gray/button/group-lr.gif
ext/resources/images/gray/form/trigger.gif
ext/resources/images/gray/form/clear-trigger.gif
ext/resources/images/gray/grid/col-move-bottom.gif
ext/resources/images/gray/grid/col-move-top.gif
ext/resources/images/gray/grid/grid3-special-col-sel-bg.gif
ext/resources/images/gray/grid/sort_asc.gif
ext/resources/images/gray/grid/sort_desc.gif
ext/resources/images/gray/menu/group-checked.gif
ext/resources/images/gray/menu/item-over.gif
ext/resources/images/gray/menu/item-over-disabled.gif
ext/resources/images/gray/menu/menu-parent.gif
ext/resources/images/gray/panel/tool-sprites.gif
ext/resources/images/gray/panel/white-top-bottom.gif
ext/resources/images/gray/qtip/tip-anchor-sprite.gif
ext/resources/images/gray/qtip/tip-sprite.gif
ext/resources/images/gray/tabs/tab-close.gif
ext/resources/images/gray/tabs/scroll-left.gif
ext/resources/images/gray/tabs/scroll-right.gif
ext/resources/images/gray/window/icon-question.gif
ext/ux/css/LockingGridView.css
ext/ux/fileuploadfield/css/fileuploadfield.css"
tar cf - -C $SrcDir --files-from <(echo "${ExtResources}") | tar xf - -C $DistDir
# CSS
echo "Preparing CSS resources"
cp -r $SrcDir/css $DistDir
# Fonts
echo "Preparing font resources"
cp -r $SrcDir/fonts $DistDir
# Images
echo "Preparing image resources"
cp -r $SrcDir/img $DistDir
# HTML
echo "Preparing HTML resources"
cp $SrcDir/index.html $DistDir/index.html
cp $SrcDir/reauth.html $DistDir/reauth.html
# Workers
echo "Preparing Worker resources"
mkdir -p $DistDir/js
mkdir -p $DistDir/js/workers
cp $SrcDir/js/workers/service-worker.js $DistDir/js/workers/service-worker.js
cp $SrcDir/js/workers/oidc-worker.js $DistDir/js/workers/oidc-worker.js
cp $SrcDir/js/workers/state-worker.js $DistDir/js/workers/state-worker.js
# npm
echo "Preparing npm resources"
cd $SrcDir/js/modules
npm install
cd $ScriptDir
# JS
echo "Preparing JavaScript resources"
cp $SrcDir/js/resources-dist.js $DistDir/js/resources.js
cp $SrcDir/js/init.js $DistDir/js/init.js
cp $SrcDir/js/Env.js.example $DistDir/js
cp -r $SrcDir/js/modules $DistDir/js/modules
cd $SrcDir/js
uglifyjs \
'diff.js' \
'diff2html.min.js' \
'stigmanUtils.js' \
'SM/Global.js' \
'SM/StackTrace.js' \
'SM/Error.js' \
'SM/ActivityHandler.js' \
'SM/FlexboxLayout.js' \
'BufferView.js' \
'SM/EventDispatcher.js' \
'SM/Cache.js' \
'SM/ServiceWorker.js' \
'SM/State.js' \
'SM/TipContent.js' \
'SM/Ajax.js' \
'SM/Classification.js' \
'SM/MainPanel.js' \
'SM/WhatsNew.js' \
'FileUploadField.js' \
'MessageBox.js' \
'overrides.js' \
'RowEditor.js' \
'RowExpander.js' \
'SM/SelectingGridToolbar.js' \
'SM/NavTree.js' \
'SM/RowEditorToolbar.js' \
'SM/BatchReview.js' \
'SM/CollectionClone.js' \
'SM/Grant.js' \
'SM/Manage.js' \
'SM/CollectionPanel.js' \
'SM/MetaPanel.js' \
'LockingGridView.js' \
'SM/ColumnFilters.js' \
'SM/FindingsPanel.js' \
'SM/Acl.js' \
'SM/Attachments.js' \
'SM/Exports.js' \
'SM/Review.js' \
'SM/ReviewsImport.js' \
'SM/TransferAssets.js' \
'SM/Library.js' \
'SM/StigRevision.js' \
'SM/Inventory.js' \
'SM/AssetSelection.js' \
'SM/User.js' \
'SM/UserGroup.js' \
'SM/AppInfo.js' \
'SM/AppData.js' \
'SM/Job.js' \
'library.js' \
'collectionAdmin.js' \
'collectionManager.js' \
'stigAdmin.js' \
'completionStatus.js' \
'findingsSummary.js' \
'review.js' \
'collectionReview.js' \
'ExportButton.js' \
'jszip.min.js' \
'FileSaver.js' \
'jsonview.bundle.js' \
'SM/LogStream.js' \
'SM/ApiState.js' \
'stigman.js' -o ../../$DistDir/js/stig-manager.min.js -m -c --source-map "root='src',url='stig-manager.min.js.map'"
echo "Copying files for sourcemap debugging"
cp -r . ../../$DistDir/js/src
echo "Client build finished"
================================================
FILE: client/dist/.gitignore
================================================
## Directory for the STIG Manager client distribution
# Content can be written here by executing:
# $ ../build.sh
#
# This file hopes to prevent commits to this directory
# Ignore everything in this directory
*
# Except this file
!.gitignore
================================================
FILE: client/src/css/ColumnHeaderGroup.css
================================================
/*!
* Ext JS Library 3.2.1
* Copyright(c) 2006-2010 Ext JS, Inc.
* licensing@extjs.com
* http://www.extjs.com/license
*/
td.ux-grid-hd-group-cell {
background: url(/ext/resources/images/default/grid/grid3-hrow.gif) repeat-x bottom;
}
================================================
FILE: client/src/css/RowEditor.css
================================================
/*
This file is part of Ext JS 3.4
Copyright (c) 2011-2013 Sencha Inc
Contact: http://www.sencha.com/contact
GNU General Public License Usage
This file may be used under the terms of the GNU General Public License version 3.0 as
published by the Free Software Foundation and appearing in the file LICENSE included in the
packaging of this file.
Please review the following information to ensure the GNU General Public License version 3.0
requirements will be met: http://www.gnu.org/copyleft/gpl.html.
If you are unsure which license is appropriate for your use, please contact the sales department
at http://www.sencha.com/contact.
Build date: 2013-04-03 15:07:25
*/
.ext-ie .x-row-editor .x-form-text {
margin:0 !important;
}
.x-row-editor-header {
height:2px;
overflow:hidden;
background: transparent url(../img/row-editor-bg-grey.gif) repeat-x 0 0;
}
.x-row-editor-footer {
height:2px;
overflow:hidden;
background: transparent url(../img/row-editor-bg-grey.gif) repeat-x 0 -2px;
}
.ext-ie .x-row-editor-footer {
margin-top:-1px;
}
.x-row-editor-body {
overflow:hidden;
zoom:1;
background: #e8e8e8;
padding-top:2px;
}
.x-row-editor .x-btns {
position:absolute;
top:28px;
left:20px;
padding-left:5px;
background: transparent url(../img/row-editor-btns-grey.gif) no-repeat 0 0;
}
.x-row-editor .x-btns .x-plain-bwrap {
padding-right:5px;
background: transparent url(../img/row-editor-btns-grey.gif) no-repeat right -31px;
}
.x-row-editor .x-btns .x-plain-body {
background: transparent url(../img/row-editor-btns-grey.gif) repeat-x 0 -62px;
height:31px;
}
.x-row-editor .x-btns .x-table-layout-cell {
padding:3px;
}
/* Fixes for IE6/7 trigger fields */
.ext-ie6 .x-row-editor .x-form-field-wrap .x-form-trigger, .ext-ie7 .x-row-editor .x-form-field-wrap .x-form-trigger {
top: 1px;
}
.ext-ie6 .x-row-editor .x-form-field-trigger-wrap, .ext-ie7 .x-row-editor .x-form-field-trigger-wrap {
margin-top: -1px;
}
.errorTip .x-tip-body ul{
list-style-type:disc;
margin-left:15px;
}
.x-row-editor.x-small-editor {
border-right: #c4c4c4 solid 1px;
}
================================================
FILE: client/src/css/dark-mode.css
================================================
/*! Portions were generated by Dark Reader | Licensed under MIT https://github.com/darkreader/darkreader/blob/master/LICENSE */
:root {
--color-severity-high:rgb(196 130 130);
--color-severity-medium:rgb(200 149 60);
--color-severity-low:rgb(169 177 219);
--color-risk-moderate: rgb(230 210 0);
--color-risk-very-low:rgb(100 167 90);
--color-scrollbar-idle: #333333;
--color-scrollbar-hover:#505050;
--color-http-status-200: #006017;
--color-http-status-300: #003761;
--color-http-status-400: #984a00;
--color-http-status-500: #980000;
--color-job-run-state-completed: hsl(121 84% 19% / 1);
--color-job-run-state-running: hsl(222, 84%, 19%);
--color-job-run-state-failed: hsl(1, 84%, 19%);
--color-job-run-state-missing: hsl(0deg 0% 32.91%);
}
html {
background-color: #181a1b!important
}
body, button, html, input, select, textarea {
background-color: #181a1b;
border-color: #736b5e;
color: hsl(0 0% 85% / 1);
}
a {
color: #3391ff
}
table {
border-color: #545b5e
}
::placeholder {
color: #b2aba1;
opacity: .5!important
}
input:-webkit-autofill, select:-webkit-autofill, textarea:-webkit-autofill {
background-color: #555b00!important;
color: #e8e6e3!important
}
::selection {
background-color: #004daa!important;
color: #e8e6e3!important
}
::-moz-selection {
background-color: #004daa!important;
color: #e8e6e3!important
}
:root {
color-scheme: dark
}
.x-grid3-row-over .sm-grid-cell-with-toolbar .sm-static-width {
filter: grayscale(100%) brightness(75%);
}
.x-grid3-row-over .sm-grid-cell-with-toolbar-2 .sm-static-width .sm-grid-cell-tool img {
filter: grayscale(100%) brightness(75%);
}
/* .x-grid3-row-over .sm-grid-cell-with-toolbar-2 .sm-static-width .sm-grid-cell-tool:hover img {
cursor: pointer;
scale: 150%;
filter: brightness(100%);
}
*/
.sm-metrics-status-table .sm-metrics-label {
border: 1px solid #444
}
.sm-metrics-status-table .sm-metrics-total td {
border-top: 1px solid #444
}
.sm-metrics-status-table .sm-metrics-assessed {
background-color: var(--metrics-status-chart-assessed-dark)
}
.sm-metrics-status-table .sm-metrics-submitted {
background-color: var(--metrics-status-chart-submitted-dark)
}
.sm-metrics-status-table .sm-metrics-accepted {
background-color: var(--metrics-status-chart-accepted-dark);
}
.sm-metrics-status-table .sm-metrics-unassessed {
background-color: var(--metrics-status-chart-unassessed-dark)
}
.sm-metrics-status-table .sm-metrics-unsaved {
background-color: var(--metrics-status-chart-unsaved-dark)
}
.sm-metrics-status-table .sm-metrics-rejected {
background-color: var(--metrics-status-chart-rejected-dark)
}
.sm-metrics-count-child {
border: 1px solid #444;
}
.sm-metric-agg-panel .x-layout-split {
background-color: #1f1f1f
}
.sm-metrics-inventory-box {
background-color: hsl(21 30% 60% / 1)
}
.sm-metrics-overview-panel .x-panel-body {
background-color: hsl(0 0% 12% / 1)
}
.sm-round-panel .sm-round-inner-panel .x-panel-body {
background-color: #1a1d1e
}
.sm-round-panel .x-panel-body, .sm-round-panel.x-window {
background-color: #1a1d1e;
}
.sm-round-panel.sm-offline-modal {
background-color: hsl(4 71% 29% / 1)
}
.sm-round-panel.sm-unavailable-modal {
background-color: hsl(24 71% 12% / 1);
}
.sm-round-panel.x-window-dlg {
background-color: #1a1d1e;
}
.x-grid3-row-expanded .x-grid3-row-body {
background-color: hsl(37deg 10% 23%)
}
.sm-truncated-action {
color: #5a94b9
}
.sm-review-sprite {
background-color: hsl(0 0% 14% / 1);
border-color: hsl(0 0% 25% / 1);
color: hsl(0deg 0% 80%)
}
.sm-label-sprite {
filter: brightness(.9);
}
body, html, img {
border-color: initial
}
ol, ul {
list-style-image: initial
}
.x-hide-nosize, .x-hide-nosize * {
border-color: initial!important
}
.x-repaint {
background-color: transparent;
outline-color: initial
}
.x-color-palette a {
text-decoration-color: initial;
outline-color: initial
}
.x-color-palette a.x-color-palette-sel, .x-color-palette a:hover, .x-color-palette em, .x-shadow * {
border-color: initial
}
.x-shadow .xsmc {
background-color: transparent
}
.x-shadow .xsbc, .x-shadow .xsbl, .x-shadow .xsbr, .x-shadow .xsml, .x-shadow .xsmr, .x-shadow .xstc, .x-shadow .xstl, .x-shadow .xstr {
background-image: initial;
background-color: transparent
}
.loading-indicator {
background-color: initial
}
.x-drag-overlay {
background-image: url("../ext/resources/images/default/s.gif")
}
ul.x-tab-strip-bottom {
border-bottom-color: initial
}
.x-tab-panel-header-plain, .x-tab-panel-header-plain .x-tab-strip-top {
background-image: initial!important;
background-color: transparent!important
}
.x-tab-panel-footer-plain, .x-tab-panel-footer-plain .x-tab-strip-bottom {
background-image: initial!important;
background-color: transparent!important
}
ul.x-tab-strip li.x-tab-edge {
border-color: initial!important;
background-image: initial!important;
background-color: transparent!important
}
.x-tab-strip a {
outline-color: initial;
text-decoration-color: initial!important
}
.x-tab-strip-bottom .x-tab-left, .x-tab-strip-bottom .x-tab-right, .x-tab-strip-bottom .x-tab-strip-active .x-tab-left, .x-tab-strip-bottom .x-tab-strip-active .x-tab-right {
background-color: initial
}
.x-tab-scroller-left, .x-tab-scroller-right {
background-color: transparent
}
.ext-webkit :focus {
outline-color: initial!important
}
.x-form-field-wrap .x-form-trigger {
border-color: initial;
background-color: #1a1d1e;
}
.x-form-grow-sizer p {
border-color: initial!important
}
.x-form-invalid-msg {
background-color: transparent
}
.x-form .x-form-btns-ct .x-form-btns td {
border-color: initial
}
.x-form-invalid-icon {
background-color: transparent
}
fieldset.x-panel-collapsed {
border-left-color: transparent;
border-right-color: transparent
}
.x-fieldset-noborder {
border-color: transparent
}
.ext-gecko .x-form-item, .ext-gecko .x-window-body .x-form-item {
outline-color: initial
}
.x-btn button {
border-color: initial;
background-color: transparent;
outline-color: initial
}
.x-btn button.sm-error-icon {
background-color: #602020
}
.x-btn-bc, .x-btn-bl, .x-btn-br, .x-btn-mc, .x-btn-ml, .x-btn-mr, .x-btn-tc, .x-btn-tl, .x-btn-tr {
background-color: initial
}
.x-btn-mc em.x-btn-arrow, .x-btn-mc em.x-btn-arrow-bottom, .x-btn-mc em.x-btn-split, .x-btn-mc em.x-btn-split-bottom {
background-color: transparent
}
.x-btn-as-arrow .x-btn-mc em {
background-color: transparent
}
.x-btn-group-bc, .x-btn-group-bl, .x-btn-group-br, .x-btn-group-tc, .x-btn-group-tl, .x-btn-group-tr {
background-color: transparent
}
.x-btn-group-mc {
border-color: initial
}
.x-btn-group-mc .x-btn-group-body {
background-color: transparent;
border-color: initial
}
.x-btn-group-ml, .x-btn-group-mr, .x-btn-group-notitle .x-btn-group-tc {
background-color: transparent
}
.x-toolbar .xtb-sep {
background-image: none;
background-color: #505050;
width: 1px;
margin: 0 3px 0 3px;
}
.x-toolbar-more em.x-btn-arrow {
background-color: transparent
}
.x-toolbar-more .x-btn-mc em.x-btn-arrow {
background-image: none
}
div.x-toolbar-no-items {
color: #988f81!important
}
.x-grid3-hd-row td, .x-grid3-row td, .x-grid3-summary-row td {
outline-color: initial
}
.x-grid3-body-cell {
outline-color: initial
}
.x-grid3-resize-marker, .x-grid3-resize-proxy {
border-color: initial
}
.x-grid3-focus {
outline-color: initial
}
.x-grid3-header-pop-inner {
background-color: transparent
}
.col-move-bottom, .col-move-top {
background-color: transparent
}
.x-grid3-locked .x-grid3-row-selected td.x-grid3-row-marker, .x-grid3-locked td.x-grid3-row-marker {
border-bottom-color: initial!important
}
.x-grid3-dirty-cell {
background-color: transparent
}
.x-grid3-topbar .x-toolbar {
border-right-color: initial
}
.x-grid3-bottombar .x-toolbar {
border-right-color: initial;
border-bottom-color: initial
}
.x-props-grid .x-grid3-td-name .x-grid3-cell-inner {
background-color: transparent!important
}
.x-props-grid .x-grid3-body .x-grid3-td-name {
border-color: initial
}
.x-grid3-col-dd {
border-color: initial;
background-color: transparent
}
.x-grid3-body .x-grid3-td-expander {
background-image: initial;
background-color: transparent
}
.x-grid3-row-expander {
background-color: transparent
}
.x-grid3-body .x-grid3-td-checker {
background-image: initial;
background-color: transparent
}
.x-grid3-hd-checker, .x-grid3-row-checker {
background-color: transparent
}
.x-grid3-body .x-grid3-row-selected .x-grid3-td-checker, .x-grid3-body .x-grid3-row-selected .x-grid3-td-expander, .x-grid3-body .x-grid3-row-selected .x-grid3-td-numberer, .x-grid3-body .x-grid3-td-numberer, .x-grid3-body .x-grid3-td-row-icon {
background-image: initial;
background-color: transparent
}
.x-grid3-check-col, .x-grid3-check-col-on {
background-color: transparent
}
.x-grid-group-hd div.x-grid-group-title {
background-color: transparent
}
.x-dd-drag-repair .x-dd-drag-ghost {
border-color: initial;
background-color: transparent
}
.x-dd-drop-icon {
background-color: transparent
}
.x-tree-ec-icon, .x-tree-elbow, .x-tree-elbow-end, .x-tree-elbow-end-minus, .x-tree-elbow-end-plus, .x-tree-elbow-line, .x-tree-elbow-minus, .x-tree-elbow-plus, .x-tree-icon, .x-tree-node-collapsed .x-tree-node-icon, .x-tree-node-expanded .x-tree-node-icon, .x-tree-node-leaf .x-tree-node-icon, .x-view-selector {
border-color: initial
}
.x-tree-arrows .x-tree-elbow, .x-tree-no-lines .x-tree-elbow, .x-tree-no-lines .x-tree-elbow-end, .x-tree-no-lines .x-tree-elbow-line {
background-color: transparent
}
.x-tree-arrows .x-tree-elbow-minus, .x-tree-arrows .x-tree-elbow-plus {
background-color: transparent
}
.x-tree-arrows .x-tree-elbow-end {
background-color: transparent
}
.x-tree-arrows .x-tree-elbow-end-minus, .x-tree-arrows .x-tree-elbow-end-plus {
background-color: transparent
}
.x-tree-arrows .x-tree-elbow-line {
background-color: transparent
}
.x-dd-drag-ghost a, .x-tree-node a {
text-decoration-color: initial;
outline-color: initial
}
.x-tree-node .x-tree-node-inline-icon {
background-color: transparent
}
.x-dd-drag-ghost a:hover, .x-tree-node a:hover {
text-decoration-color: initial
}
.x-tree-dd-underline .x-tree-node div.x-tree-drag-insert-below {
border-bottom-color: initial
}
.x-tree-dd-underline .x-tree-node div.x-tree-drag-insert-above {
border-top-color: initial
}
.x-date-picker a {
outline-color: initial
}
.x-date-left, .x-date-middle, .x-date-right {
background-color: initial
}
.x-date-middle .x-btn-bc, .x-date-middle .x-btn-bl, .x-date-middle .x-btn-br, .x-date-middle .x-btn-mc, .x-date-middle .x-btn-ml, .x-date-middle .x-btn-mr, .x-date-middle .x-btn-tc, .x-date-middle .x-btn-tl, .x-date-middle .x-btn-tr {
background-image: initial!important;
background-color: transparent!important
}
.x-date-middle .x-btn-mc em.x-btn-arrow {
background-color: transparent
}
.x-date-left a, .x-date-right a {
text-decoration-color: initial!important
}
.x-date-inner a {
text-decoration-color: initial
}
.x-date-inner .x-date-nextday a, .x-date-inner .x-date-prevday a {
text-decoration-color: initial!important
}
.x-date-inner .x-date-disabled a:hover, .x-date-inner a:hover {
text-decoration-color: initial!important
}
.x-item-disabled .x-date-inner a:hover {
background-image: initial;
background-color: initial
}
td.x-date-mp-month, td.x-date-mp-ybtn, td.x-date-mp-year {
border-color: initial
}
.x-date-mp-btns button {
text-decoration-color: initial!important
}
td.x-date-mp-month a, td.x-date-mp-month a:hover, td.x-date-mp-year a, td.x-date-mp-year a:hover {
text-decoration-color: initial
}
.x-date-mp-ybtn a {
background-color: transparent
}
.x-tip {
border-color: initial
}
.x-tip .x-tip-bc, .x-tip .x-tip-bl, .x-tip .x-tip-br, .x-tip .x-tip-tc, .x-tip .x-tip-tl, .x-tip .x-tip-tr {
background-image: initial
}
.x-tip .x-tip-mc {
border-color: initial
}
.x-tip .x-tip-ml {
background-image: initial
}
.x-tip .x-tip-mr {
background-image: initial
}
.x-form-invalid-tip .x-tip-bc, .x-form-invalid-tip .x-tip-bl, .x-form-invalid-tip .x-tip-br, .x-form-invalid-tip .x-tip-tc {
background-color: initial
}
.x-form-invalid-tip .x-tip-body, .x-tip-anchor {
background-color: transparent
}
.x-menu {
background-image: initial
}
.x-menu a {
text-decoration-color: initial!important
}
.x-menu-list {
background-color: transparent;
border-color: initial
}
.x-menu-item-arrow {
background-color: transparent
}
.x-menu-focus {
outline-color: initial
}
.x-menu-item-icon {
border-color: initial
}
.x-menu-check-item .x-menu-item-icon {
background-color: transparent
}
.x-menu-group-item .x-menu-item-icon {
background-color: transparent
}
.x-menu-item-checked .x-menu-group-item .x-menu-item-icon {
background-color: transparent
}
.x-menu .x-date-picker, .x-menu-plain .x-color-palette, .x-menu-plain .x-date-picker {
border-color: initial
}
.x-box-ml, .x-box-tc, .x-box-tl, .x-box-tr {
background-color: transparent
}
.x-box-bc, .x-box-bl, .x-box-br, .x-box-mr {
background-color: transparent
}
.x-combo-list .x-toolbar {
border-bottom-color: initial
}
.x-panel-header {
background-color: transparent
}
.x-panel-mc .x-panel-tbar .x-toolbar, .x-panel-tbar-noheader .x-toolbar {
border-bottom-color: initial
}
.x-panel-tl .x-panel-header {
border-color: initial;
background-image: initial;
background-color: transparent
}
.x-panel-tc {
background-color: transparent
}
.x-panel-tl {
background-color: transparent
}
.x-panel-bc, .x-panel-bl, .x-panel-br, .x-panel-tr {
background-color: transparent
}
.x-panel-mc {
border-color: initial
}
.x-panel-mc .x-panel-body {
background-color: transparent;
border-color: initial
}
.x-panel-mr, .x-tool {
background-color: transparent
}
.x-panel-reset .x-panel-body del, .x-panel-reset .x-panel-body s, .x-panel-reset .x-panel-body strike {
text-decoration-color: initial
}
.x-panel-reset .x-panel-body hr {
border-color: initial
}
.x-panel-reset .x-panel-body :link, .x-panel-reset .x-panel-body :visited, .x-panel-reset .x-panel-body ins, .x-panel-reset .x-panel-body u {
text-decoration-color: initial
}
.x-window-bc, .x-window-bl, .x-window-br, .x-window-tc, .x-window-tl, .x-window-tr {
background-color: transparent
}
.x-window-ml, .x-window-mr {
background-color: transparent
}
.x-window-bbar .x-toolbar, .x-window-maximized .x-window-mc, .x-window-tbar .x-toolbar {
border-left-color: initial;
border-right-color: initial
}
.x-window-bbar .x-toolbar {
border-bottom-color: initial
}
.x-window-body {
background-color: transparent
}
.x-window-sizing-ghost ul {
border-color: initial!important
}
.x-dlg-focus {
outline-color: initial
}
.x-html-editor-tb .x-btn-text {
background-color: transparent
}
.x-html-editor-tb .x-edit-backcolor, .x-html-editor-tb .x-edit-bold, .x-html-editor-tb .x-edit-createlink, .x-html-editor-tb .x-edit-decreasefontsize, .x-html-editor-tb .x-edit-forecolor, .x-html-editor-tb .x-edit-increasefontsize, .x-html-editor-tb .x-edit-insertorderedlist, .x-html-editor-tb .x-edit-insertunorderedlist, .x-html-editor-tb .x-edit-italic, .x-html-editor-tb .x-edit-justifycenter, .x-html-editor-tb .x-edit-justifyleft, .x-html-editor-tb .x-edit-justifyright, .x-html-editor-tb .x-edit-sourceedit, .x-html-editor-tb .x-edit-underline, .x-menu-item img.x-edit-backcolor, .x-menu-item img.x-edit-bold, .x-menu-item img.x-edit-createlink, .x-menu-item img.x-edit-decreasefontsize, .x-menu-item img.x-edit-forecolor, .x-menu-item img.x-edit-increasefontsize, .x-menu-item img.x-edit-insertorderedlist, .x-menu-item img.x-edit-insertunorderedlist, .x-menu-item img.x-edit-italic, .x-menu-item img.x-edit-justifycenter, .x-menu-item img.x-edit-justifyleft, .x-menu-item img.x-edit-justifyright, .x-menu-item img.x-edit-sourceedit, .x-menu-item img.x-edit-underline {
background-image: url("../ext/resources/images/default/editor/tb-sprite.gif")
}
.x-accordion-hd {
border-top-color: initial;
background-color: transparent
}
.x-layout-split {
background-color: transparent;
transition-property: background-color;
transition-duration: 100ms;
transition-delay: 0s;
}
.x-layout-split:hover {
background-color: #243385;
transition-duration: 100ms;
transition-delay: 0s;
}
.ext-strict .ext-ie6 .x-layout-split {
background-color: #181a1b!important
}
.x-layout-split-h, .x-layout-split-v {
background-image: url("../ext/resources/images/default/s.gif")
}
.x-layout-cmini-east, .x-layout-cmini-north, .x-layout-cmini-south, .x-layout-cmini-west {
border-color: initial;
background-color: transparent
}
.x-progress-wrap, .x-viewport, .x-viewport body {
border-color: initial
}
.x-list-header-inner em.sort-asc, .x-list-header-inner em.sort-desc {
background-color: transparent
}
.x-slider-focus {
outline-color: initial
}
.x-slider-horz, .x-slider-horz .x-slider-end, .x-slider-horz .x-slider-inner, .x-slider-horz .x-slider-thumb, .x-slider-vert, .x-slider-vert .x-slider-end, .x-slider-vert .x-slider-inner, .x-slider-vert .x-slider-thumb {
background-color: transparent
}
.x-window-dlg .x-window-body, .x-window-dlg .x-window-mc {
border-color: initial!important
}
.x-window-dlg .ext-mb-error, .x-window-dlg .ext-mb-info, .x-window-dlg .ext-mb-question, .x-window-dlg .ext-mb-warning, .x-window-dlg .x-msg-box-wait {
background-color: transparent
}
.x-form-field-wrap .x-form-trigger {
border-bottom-color: #42484a
}
.x-form-invalid.x-form-composite {
border-color: initial;
background-image: none
}
.x-form-invalid.x-form-composite .x-form-invalid {
background-color: #181a1b;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIzIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMjQ5IC0wLjYxNCAtMC42NzIgMC4wMDAgMS4wMzUgLTAuNjQ2IDAuMjg4IC0wLjY2NCAwLjAwMCAxLjAyMCAtMC42MzYgLTAuNjA5IDAuMjUwIDAuMDAwIDAuOTk0IDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMyIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBREFJY0FBQUQvQVA4QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBRUFBQUFBTEFBQUFBQUVBQU1BQUFnTUFBTUFHQWhBb01DQ0FBSUNBRHM9IiAvPjwvc3ZnPg==");
border-color: #c23000
}
td.grid-hd-group-cell {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMiIgaGVpZ2h0PSIyNCI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyIiBoZWlnaHQ9IjI0IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBZ0FZQUljQUFORFEwT3ZzN3V6dDcrM3U4Tzd2OGUvdzh2RHg4L0h5OVBuNStRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQ0FCZ0FBQWdoQUJFSUhFaXdZTUVEQ0E4WVdNaXdnTU1DQkFnTW1EaEFnSUFBR0FNQUFCQVFBRHM9IiAvPjwvc3ZnPg==");
background-color: initial
}
.x-menu-plain {
background-image: none
}
.x-color-menu, .x-date-menu {
background-color: #181a1b!important
}
.x-panel-mc .x-panel-tbar .x-toolbar, .x-panel-tbar-noheader .x-toolbar {
border-top-color: #1a4072
}
.x-item-disabled {
color: #988f81
}
.x-item-disabled * {
color: #988f81!important
}
.x-splitbar-proxy {
background-color: #484e51
}
.x-color-palette a {
border-color: #303436
}
.x-color-palette a.x-color-palette-sel, .x-color-palette a:hover {
border-color: #3e4345;
background-color: #242728
}
.x-color-palette em {
border-color: #4a5053
}
.x-ie-shadow {
background-color: #5a6165
}
.loading-indicator {
background-image: url("../ext/resources/images/default/grid/loading.gif")
}
.x-spotlight {
background-color: #35393b
}
.x-tab-panel-footer, .x-tab-panel-header {
background-color: transparent;
border-color: #3d4245
}
ul.x-tab-strip-bottom {
background-color: #2c3032;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIyNiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjI2IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUFhQUljQUFBQUFBQUVCQVFJQ0FnTURBd1FFQkFVRkJRWUdCZ2NIQndnSUNBa0pDUW9LQ2dzTEN3d01EQTBORFE0T0RnOFBEeEFRRUJFUkVSSVNFaE1URXhRVUZCVVZGUllXRmhjWEZ4Z1lHQmtaR1JvYUdoc2JHeHdjSEIwZEhSNGVIaDhmSHlBZ0lDRWhJU0lpSWlNakl5UWtKQ1VsSlNZbUppY25KeWdvS0NrcEtTb3FLaXNyS3l3c0xDMHRMUzR1TGk4dkx6QXdNREV4TVRJeU1qTXpNelEwTkRVMU5UWTJOamMzTnpnNE9EazVPVG82T2pzN096dzhQRDA5UFQ0K1BqOC9QMEJBUUVGQlFVSkNRa05EUTBSRVJFVkZSVVpHUmtkSFIwaElTRWxKU1VwS1NrdExTMHhNVEUxTlRVNU9UazlQVDFCUVVGRlJVVkpTVWxOVFUxUlVWRlZWVlZaV1ZsZFhWMWhZV0ZsWldWcGFXbHRiVzF4Y1hGMWRYVjVlWGw5ZlgyQmdZR0ZoWVdKaVltTmpZMlJrWkdWbFpXWm1abWRuWjJob2FHbHBhV3BxYW10cmEyeHNiRzF0Ylc1dWJtOXZiM0J3Y0hGeGNYSnljbk56YzNSMGRIVjFkWFoyZG5kM2QzaDRlSGw1ZVhwNmVudDdlM3g4ZkgxOWZYNStmbjkvZjRDQWdJR0JnWUtDZ29PRGc0U0VoSVdGaFlhR2hvZUhoNGlJaUltSmlZcUtpb3VMaTR5TWpJMk5qWTZPam8rUGo1Q1FrSkdSa1pLU2twT1RrNVNVbEpXVmxaYVdscGVYbDVpWW1KbVptWnFhbXB1Ym01eWNuSjJkblo2ZW5wK2ZuNkNnb0tHaG9hS2lvcU9qbzZTa3BLV2xwYWFtcHFlbnA2aW9xS21wcWFxcXFxdXJxNnlzcksydHJhNnVycSt2cjdDd3NMR3hzYkt5c3JPenM3UzB0TFcxdGJhMnRyZTN0N2k0dUxtNXVicTZ1cnU3dTd5OHZMMjl2YjYrdnIrL3Y4REF3TUhCd2NMQ3dzUER3OFRFeE1YRnhjYkd4c2ZIeDhqSXlNbkp5Y3JLeXN2THk4ek16TTNOemM3T3pzL1B6OURRME5IUjBkTFMwdFBUMDlUVTFOWFYxZGJXMXRmWDE5alkyTm5aMmRyYTJ0dmIyOXpjM04zZDNkN2UzdC9mMytEZzRPSGg0ZUxpNHVQajQrVGs1T1hsNWVibTV1Zm41K2pvNk9ucDZlcnE2dXZyNit6czdPM3Q3ZTd1N3UvdjcvRHc4UEh4OGZMeTh2UHo4L1QwOVBYMTlmYjI5dmYzOS9qNCtQbjUrZnI2K3Z2NysvejgvUDM5L2Y3Ky92Ly8veUg1QkFBQUFQOEFMQUFBQUFBQkFCb0FBQWdYQUpzMXc5Yk5HN2h3NDhpWlE1ZHVIYnVIRUNOQ0RBZ0FPdz09IiAvPjwvc3ZnPg==");
border-top-color: #3d4245
}
.x-tab-panel-footer-plain .x-tab-strip-spacer, .x-tab-panel-header-plain .x-tab-strip-spacer {
border-color: #3d4245;
background-color: #242728
}
.x-tab-strip span.x-tab-strip-text {
color: #c8c3bc
}
.x-tab-strip-over span.x-tab-strip-text {
color: #dddad6
}
.x-tab-strip-active span.x-tab-strip-text {
color: #c8c3bc
}
.x-tab-strip-disabled .x-tabs-text {
color: #b2aca2
}
.x-tab-strip-bottom .x-tab-right {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMzAwIiBoZWlnaHQ9IjUwIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjMwMCIgaGVpZ2h0PSI1MCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoTEFFeUFJY0FBQUFBQUFFQkFRSUNBZ01EQXdRRUJBVUZCUVlHQmdjSEJ3Z0lDQWtKQ1FvS0Nnc0xDd3dNREEwTkRRNE9EZzhQRHhBUUVCRVJFUklTRWhNVEV4UVVGQlVWRlJZV0ZoY1hGeGdZR0JrWkdSb2FHaHNiR3h3Y0hCMGRIUjRlSGg4Zkh5QWdJQ0VoSVNJaUlpTWpJeVFrSkNVbEpTWW1KaWNuSnlnb0tDa3BLU29xS2lzckt5d3NMQzB0TFM0dUxpOHZMekF3TURFeE1USXlNak16TXpRME5EVTFOVFkyTmpjM056ZzRPRGs1T1RvNk9qczdPenc4UEQwOVBUNCtQajgvUDBCQVFFRkJRVUpDUWtORFEwUkVSRVZGUlVaR1JrZEhSMGhJU0VsSlNVcEtTa3RMUzB4TVRFMU5UVTVPVGs5UFQxQlFVRkZSVVZKU1VsTlRVMVJVVkZWVlZWWldWbGRYVjFoWVdGbFpXVnBhV2x0YlcxeGNYRjFkWFY1ZVhsOWZYMkJnWUdGaFlXSmlZbU5qWTJSa1pHVmxaV1ptWm1kbloyaG9hR2xwYVdwcWFtdHJhMnhzYkcxdGJXNXVibTl2YjNCd2NIRnhjWEp5Y25OemMzUjBkSFYxZFhaMmRuZDNkM2g0ZUhsNWVYcDZlbnQ3ZTN4OGZIMTlmWDUrZm45L2Y0Q0FnSUdCZ1lLQ2dvT0RnNFNFaElXRmhZYUdob2VIaDRpSWlJbUppWXFLaW91TGk0eU1qSTJOalk2T2pvK1BqNUNRa0pHUmtaS1NrcE9UazVTVWxKV1ZsWmFXbHBlWGw1aVltSm1abVpxYW1wdWJtNXljbkoyZG5aNmVucCtmbjZDZ29LR2hvYUtpb3FPam82U2twS1dscGFhbXBxZW5wNmlvcUttcHFhcXFxcXVycTZ5c3JLMnRyYTZ1cnErdnI3Q3dzTEd4c2JLeXNyT3pzN1MwdExXMXRiYTJ0cmUzdDdpNHVMbTV1YnE2dXJ1N3U3eTh2TDI5dmI2K3ZyKy92OERBd01IQndjTEN3c1BEdzhURXhNWEZ4Y2JHeHNmSHg4akl5TW5KeWNyS3lzdkx5OHpNek0zTnpjN096cy9QejlEUTBOSFIwZExTMHRQVDA5VFUxTlhWMWRiVzF0ZlgxOWpZMk5uWjJkcmEydHZiMjl6YzNOM2QzZDdlM3QvZjMrRGc0T0hoNGVMaTR1UGo0K1RrNU9YbDVlYm01dWZuNStqbzZPbnA2ZXJxNnV2cjYrenM3TzN0N2U3dTd1L3Y3L0R3OFBIeDhmTHk4dlB6OC9UMDlQWDE5ZmIyOXZmMzkvajQrUG41K2ZyNit2djcrL3o4L1AzOS9mNysvdi8vL3lINUJBQUFBUDhBTEFBQUFBQXNBVElBQUFqL0FOVUpIRWl3b01HRENCTXFYTWl3b2NPSEVDTktuRWl4b3NXTEZ2KzV3c2l4bzhlUElFT0tIRW15SVRoY0pWT3FYTW15cGN1V0oxL0tuRW16cHMyVk1XL3EzTW16cDgrY1BvTUtIVXEwSTlDaVNKTXFYWHAwcWRPblVHazJqVXExcWxXUFU2OXEzY3BWWWRhdVlNTmUvU3Eyck5ta1pNK3FYYnN6TGR1M2NHR2lqRXUzcmx5N2VQT0tkS3UzcjkrRmZQOEtIcXd1TU9IRGVRMGpYaHhYTWVQSGFoMURuaHhXTXVYTFdpMWozaHhWTStmUFNqMkRIajFVTk9uVFBFMmpYbDFUTmV2WExsM0RucDFTTnUzYkljbk54YzE3SjdyZHZZUFRaQWRjdVBHVzc0b2ZYMTVTbm5MbTBFSE9leDY5T3NicDFyTjd4SzY5dTBYdTNzTkQvMHhYRDllNTgralRxMS9QdnIzNzkvRGp5NTlQdjc3OSsvano2OS9QZjMvNWNnQUdLT0NBQkJabzRJRUlKcWpnZ2d3MjZPQ0RFRVlvNFlRVVZramhkT1JrcU9HR0hIYm80WWNnaGlqaWlDU1dhT0tKS0thbzRvb3N0dWhpaTlPSkkrT01OTlpvNDQwNDVxampqanoyNk9PUFFBWXA1SkJFRm1ua2tVYkdnMHM0VERicDVKTlFSaW5sbEZSV2FlV1ZXR2FwNVpaY2R1bmxsMkNHQ2FZOHVYeGo1cGxvcHFubW1teTI2ZWFiY01ZcDU1eDAxbW5ublhqbXFlZWVlcnFqaXplQUJpcm9vSVFXYXVpaGlDYXE2S0tNTnVyb281QkdLdW1rbEZaS3FUcStjS1BwcHB4MjZ1bW5vSVlxNnFpa2xtcnFxYWltcXVxcXJMYnE2cXV1L2tSRHpEKzAxbXJycmJqbXF1dXV2UGJxNjYvQUJpdnNzTVFXYSt5eHlDYUxMRExrdU9Mc3M5QkdLKzIwMUZacjdiWFlacXZ0dHR4MjYrMjM0SVlyN3JqaWtzTk9RQUE3IiAvPjwvc3ZnPg==")
}
.x-tab-strip-bottom .x-tab-left {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMyIgaGVpZ2h0PSI0OSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIzIiBoZWlnaHQ9IjQ5IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBd0F4QUljQUFBQUFBQUVCQVFJQ0FnTURBd1FFQkFVRkJRWUdCZ2NIQndnSUNBa0pDUW9LQ2dzTEN3d01EQTBORFE0T0RnOFBEeEFRRUJFUkVSSVNFaE1URXhRVUZCVVZGUllXRmhjWEZ4Z1lHQmtaR1JvYUdoc2JHeHdjSEIwZEhSNGVIaDhmSHlBZ0lDRWhJU0lpSWlNakl5UWtKQ1VsSlNZbUppY25KeWdvS0NrcEtTb3FLaXNyS3l3c0xDMHRMUzR1TGk4dkx6QXdNREV4TVRJeU1qTXpNelEwTkRVMU5UWTJOamMzTnpnNE9EazVPVG82T2pzN096dzhQRDA5UFQ0K1BqOC9QMEJBUUVGQlFVSkNRa05EUTBSRVJFVkZSVVpHUmtkSFIwaElTRWxKU1VwS1NrdExTMHhNVEUxTlRVNU9UazlQVDFCUVVGRlJVVkpTVWxOVFUxUlVWRlZWVlZaV1ZsZFhWMWhZV0ZsWldWcGFXbHRiVzF4Y1hGMWRYVjVlWGw5ZlgyQmdZR0ZoWVdKaVltTmpZMlJrWkdWbFpXWm1abWRuWjJob2FHbHBhV3BxYW10cmEyeHNiRzF0Ylc1dWJtOXZiM0J3Y0hGeGNYSnljbk56YzNSMGRIVjFkWFoyZG5kM2QzaDRlSGw1ZVhwNmVudDdlM3g4ZkgxOWZYNStmbjkvZjRDQWdJR0JnWUtDZ29PRGc0U0VoSVdGaFlhR2hvZUhoNGlJaUltSmlZcUtpb3VMaTR5TWpJMk5qWTZPam8rUGo1Q1FrSkdSa1pLU2twT1RrNVNVbEpXVmxaYVdscGVYbDVpWW1KbVptWnFhbXB1Ym01eWNuSjJkblo2ZW5wK2ZuNkNnb0tHaG9hS2lvcU9qbzZTa3BLV2xwYWFtcHFlbnA2aW9xS21wcWFxcXFxdXJxNnlzcksydHJhNnVycSt2cjdDd3NMR3hzYkt5c3JPenM3UzB0TFcxdGJhMnRyZTN0N2k0dUxtNXVicTZ1cnU3dTd5OHZMMjl2YjYrdnIrL3Y4REF3TUhCd2NMQ3dzUER3OFRFeE1YRnhjYkd4c2ZIeDhqSXlNbkp5Y3JLeXN2THk4ek16TTNOemM3T3pzL1B6OURRME5IUjBkTFMwdFBUMDlUVTFOWFYxZGJXMXRmWDE5alkyTm5aMmRyYTJ0dmIyOXpjM04zZDNkN2UzdC9mMytEZzRPSGg0ZUxpNHVQajQrVGs1T1hsNWVibTV1Zm41K2pvNk9ucDZlcnE2dXZyNit6czdPM3Q3ZTd1N3UvdjcvRHc4UEh4OGZMeTh2UHo4L1QwOVBYMTlmYjI5dmYzOS9qNCtQbjUrZnI2K3Z2NysvejgvUDM5L2Y3Ky92Ly8veUg1QkFBQUFQOEFMQUFBQUFBREFERUFBQWhPQUhHQlV5ZVE0TUNDQ0E4cU5NZ3dZY09GRGlOQ25QaXdJa0p5Qk5FUlpFZndIVUY1Qk9lRkhJbExKSzU2NlU2ZUsxbXVKRGxjOGNUbGtoZE9sN3R2dnRSNUkvYVBHemxrLzlpUmN4VVFBRHM9IiAvPjwvc3ZnPg==")
}
.x-tab-strip-bottom .x-tab-strip-over .x-tab-left {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMyIgaGVpZ2h0PSI0OSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIzIiBoZWlnaHQ9IjQ5IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBd0F4QU1RQUFMYTJ0dkx5OHVmbjUvcjYrdm41K2ZEdzhPUGo0Ly8vLyt6czdPdnI2L3Y3Ky9Qejg3Mjl2YmUzdC9iMjl1cnE2cmk0dUx1N3U2eXNyTzN0N2NMQ3d2WDE5ZVhsNWZqNCtPL3Y3K2pvNkFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBQUFBQUFBTEFBQUFBQURBREVBQUFVNklDQUVJam1XNkttYWJOcXViZ3pQYjQwaVpFRXVwRU1TUDlKQVNBUW9Da1lNWURBQkVCQ0FTNkpCZUVBcUdVWkFRRGxZREpGRHdpQUpBUUE3IiAvPjwvc3ZnPg==")
}
.x-tab-strip-bottom .x-tab-strip-over .x-tab-right {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMzAwIiBoZWlnaHQ9IjUwIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjMwMCIgaGVpZ2h0PSI1MCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoTEFFeUFNUUFBUEx5OHV2cjYrM3Q3ZWpvNk9ycTZ1L3Y3Ly8vLytmbjU3dTd1K1hsNWV6czdLeXNyTjdlM3ZQejgrUGo0L1gxOWZIeDhlN3U3dG5aMlFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQUFBQUxBQUFBQUFzQVRJQUFBWC9JQ0NPWkdtZWFLcXViT3UrY0N6UGRHM2ZOclBnZk8vL3dLQndTR3pwaXNpa2NzbHNNby9PcUhSS3JTYWgxcXgyeStWaXUrQ3dlTXo3a3Mvb2ROcXNicnZmVWpaOFRxLzM1UGE4ZnAvQzgvK0FkWDZCaElWbmc0YUppbG1JaTQ2UFM0MlFrNVEva3BXWW1US1htcDJlS0p5Zm9wK2hvNmFZcGFlcWo2bXJyb2F0cjdKL3NiTzJkclczdW0rNXU3NW92Yi9DWWNIRHhsckZ4OHBUeWN2T1R6dlAwbXZSMDlaaUR0WFgyMXNEMnR6Z1ZBSGY0ZVZORWVUbTZrZ1E2ZXZ2UXU3dzh6d044dlQ0TlBiNS9QWDMvUUJYUEZoUW9LREJnd2dUS2x6SXNLSERoeEFqU3B4SXNhTEZpeGd6YXN3NFVJREhqeUJEaWh4SnNxVEpreWhUK0twY3liS2x5NWN3WThxY0tkT2VncHM0YytyY3liT256NTlBZ3dvZFNyU28wYU5Ja3lwZHluUXBnQVVCb2txZFNyV3ExYXRZczJyZHlyV3IxNjlndzRvZFM3YXMyYkx0Q0toZHk3YXQyN2R3NDhxZFM3ZXUzYnQ0OCtyZHk3ZXYzNzkrbnc0WVRMaXc0Y09JRXl0ZXpMaXg0OGVRSTB1ZVRMbXk1Y3VZTHd0WWNLQ3o1OCtnUTRzZVRicTA2ZE9vVTZ0ZXpicTE2OWV3WTh1T1RXQkJndHU0Yyt2ZXpidTM3OS9BZ3dzZlRyeTQ4ZVBJa3l0ZnpueTVoQVVHb2t1ZlRyMjY5ZXZZczJ2ZnpyMjc5Ky9ndzRzZlQ3NjgrZklMSENCWXo3NjkrL2Z3NDh1ZlQ3KysvZnY0OCt2Zno3Ky8vLzhBL3VkQUFDRUFBRHM9IiAvPjwvc3ZnPg==")
}
.x-tab-strip-bottom .x-tab-strip-active .x-tab-right {
background-image: url("../ext/resources/images/gray/tabs/tab-btm-right-bg.gif")
}
.x-tab-strip-bottom .x-tab-strip-active .x-tab-left {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMzAwIiBoZWlnaHQ9IjUwIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjMwMCIgaGVpZ2h0PSI1MCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoTEFFeUFJY0FBQUFBQUFFQkFRSUNBZ01EQXdRRUJBVUZCUVlHQmdjSEJ3Z0lDQWtKQ1FvS0Nnc0xDd3dNREEwTkRRNE9EZzhQRHhBUUVCRVJFUklTRWhNVEV4UVVGQlVWRlJZV0ZoY1hGeGdZR0JrWkdSb2FHaHNiR3h3Y0hCMGRIUjRlSGg4Zkh5QWdJQ0VoSVNJaUlpTWpJeVFrSkNVbEpTWW1KaWNuSnlnb0tDa3BLU29xS2lzckt5d3NMQzB0TFM0dUxpOHZMekF3TURFeE1USXlNak16TXpRME5EVTFOVFkyTmpjM056ZzRPRGs1T1RvNk9qczdPenc4UEQwOVBUNCtQajgvUDBCQVFFRkJRVUpDUWtORFEwUkVSRVZGUlVaR1JrZEhSMGhJU0VsSlNVcEtTa3RMUzB4TVRFMU5UVTVPVGs5UFQxQlFVRkZSVVZKU1VsTlRVMVJVVkZWVlZWWldWbGRYVjFoWVdGbFpXVnBhV2x0YlcxeGNYRjFkWFY1ZVhsOWZYMkJnWUdGaFlXSmlZbU5qWTJSa1pHVmxaV1ptWm1kbloyaG9hR2xwYVdwcWFtdHJhMnhzYkcxdGJXNXVibTl2YjNCd2NIRnhjWEp5Y25OemMzUjBkSFYxZFhaMmRuZDNkM2g0ZUhsNWVYcDZlbnQ3ZTN4OGZIMTlmWDUrZm45L2Y0Q0FnSUdCZ1lLQ2dvT0RnNFNFaElXRmhZYUdob2VIaDRpSWlJbUppWXFLaW91TGk0eU1qSTJOalk2T2pvK1BqNUNRa0pHUmtaS1NrcE9UazVTVWxKV1ZsWmFXbHBlWGw1aVltSm1abVpxYW1wdWJtNXljbkoyZG5aNmVucCtmbjZDZ29LR2hvYUtpb3FPam82U2twS1dscGFhbXBxZW5wNmlvcUttcHFhcXFxcXVycTZ5c3JLMnRyYTZ1cnErdnI3Q3dzTEd4c2JLeXNyT3pzN1MwdExXMXRiYTJ0cmUzdDdpNHVMbTV1YnE2dXJ1N3U3eTh2TDI5dmI2K3ZyKy92OERBd01IQndjTEN3c1BEdzhURXhNWEZ4Y2JHeHNmSHg4akl5TW5KeWNyS3lzdkx5OHpNek0zTnpjN096cy9QejlEUTBOSFIwZExTMHRQVDA5VFUxTlhWMWRiVzF0ZlgxOWpZMk5uWjJkcmEydHZiMjl6YzNOM2QzZDdlM3QvZjMrRGc0T0hoNGVMaTR1UGo0K1RrNU9YbDVlYm01dWZuNStqbzZPbnA2ZXJxNnV2cjYrenM3TzN0N2U3dTd1L3Y3L0R3OFBIeDhmTHk4dlB6OC9UMDlQWDE5ZmIyOXZmMzkvajQrUG41K2ZyNit2djcrL3o4L1AzOS9mNysvdi8vL3lINUJBQUFBUDhBTEFBQUFBQXNBVElBQUFqL0FGMzlVMGV3b01HRENCTXFYTWl3b2NPSEVDTktuRWl4b3NXTEdETmlGS2l4bzhlUElFT0tIRW15NUVPT0psT3FYTW15cFV1V0tGL0tuRW16cHMyVU1XL3EzTW16SjgrY1BvTUtIVXBVSTlDaVNKTXFUWHAwcWRPblVHVTJqVXExcXRXT1U2OXEzY3BWWWRhdVlNTlcvU3Eyck5taVpNK3FYWHN6TGR1M2NGZTZqVXUzN3NlNWR2UHFuWWgzcjkrL0Nmc0NIdnhYTU9IRGRnMGpYdnhXTWVQSFpoMURudHhWTXVYTFZpMWozdnhVTStmUFNEMkRIaDFVTk9uVE9rMmpYajFUTmV2WE1BZkNucTNVTmUzYklXM2ozbTFVTnUvZmJYMERIeTVWT1BIamNvMGpYMDVTTi9QbkJaMURmeTR3bnZYcjJMTnIzODY5dS9mdjRNT0wveDlQdnJ6NTgralRxMSt2WHFDODkvRGp5NTlQdjc3OSsvano2OS9QdjcvLy93QUdLT0NBQkE0b0VEMElKcWpnZ2d3MjZPQ0RFRVlvNFlRVVZtamhoUmhtcU9HR0hIYklvVUQyaENqaWlDU1dhT0tKS0thbzRvb3N0dWppaXpER0tPT01OTlpvWTQwQzRhUGpqanoyNk9PUFFBWXA1SkJFRm1ua2tVZ21xZVNTVERicDVKTk9DcFRQbEZSV2FlV1ZXR2FwNVpaY2R1bmxsMkNHS2VhWVpKWnA1cGxvbmluUVBteTI2ZWFiY01ZcDU1eDAxbW5ublhqbXFlZWVmUGJwNTUrQUJncW9RUHdVYXVpaGlDYXE2S0tNTnVyb281QkdLdW1rbEZacTZhV1lacXBwcGdMNTQrbW5vSVlxNnFpa2xtcnFxYWltcXVxcXJMYnE2cXV3eGxjcTY2eXl1c0xOUDdqbXF1dXV2UGJxNjYvQUJpdnNzTVFXYSt5eHlDYXI3TExNTnNzc09iWTZLKzIwMUZacjdiWFlacXV0c094QTY4cTM0SVlyN3Jqa2xtdnV1ZWltcSs2NjdMYnI3cnZ3eGl2dnZQVEtHeEFBT3c9PSIgLz48L3N2Zz4=")
}
.x-tab-strip .x-tab-strip-closable a.x-tab-strip-close {
background-image: url('../img/tab-close-dark.gif')
}
.x-tab-strip .x-tab-strip-closable a.x-tab-strip-close:hover {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTEiIGhlaWdodD0iMTEiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTEiIGhlaWdodD0iMTEiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEN3QUxBSWNBQUhkM2QzMTlmVUQvUUlPRGc0aUlpSTZPanE2dXJyaTR1Tm5aMmVIaDRlVGs1T2ZuNS9EdzhQVDA5UGo0K1BuNStmejgvUDM5L2YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQU1BQUFJQUxBQUFBQUFMQUFzQUFBaGRBQVVJT0VDdzRBR0JBeVVvWENqaDRBRUpEQkE0bUlpQVFjTURFUkFVS09CZ0k0SUlCQ0UwSUVDU1pBTUlCQjh3WURDZzVjb0hCQmtrQ0VDVFpnSUdNUTBBQUtCZ3B3R2NCeGdzTUxDZ0tGR2NBMWNxWFhsUW9NR0NBZ01DQURzPSIgLz48L3N2Zz4=")
}
.x-tab-panel-body-top {
border-top-color: initial
}
.x-tab-panel-body-bottom {
border-bottom-color: initial
}
.x-tab-scroller-left {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMzYiIGhlaWdodD0iNDMiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMzYiIGhlaWdodD0iNDMiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEpBQXJBSWNBQUc5dmIzbDVlVUQvUUlxS2lwU1VsSzZ1cnRiVzF0ZlgxOWpZMk5uWjJkcmEydHZiMjl6YzNOM2QzZDdlM3QvZjMrRGc0T0hoNGVMaTR1UGo0K1RrNU9YbDVlYm01dWZuNStqbzZPbnA2ZXJxNnV2cjYrenM3TzN0N2U3dTd1L3Y3L0R3OFBIeDhmUHo4L2IyOXZyNitnQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUVBQUFJQUxBQUFBQUFrQUNzQUFBai9BQVVJSEVpd29NR0RDQXNvWE1pd29jT0hFRWxJbkVpeG9zUUNGak5TTENDaW84ZVBJRVdRS0pDaHBNbVRLRE9NRE1HeXBjdVhJVVplbUVtenBzMExJMEhvM01teko0aVJGb0lLSFVyVXdzZ1BTSk1xWGZwQlJJRUtVS05LblZyQnFZZXJXRDJNMkpyMXFsTUtZTU9LSFV2QmFZZXphTGNTMklyMnJOTUpjT1BDSFNBM3JsTU9lUEZ1RFJCZ3ExKzhUaVVJSGl3QkFBRENnNTF1V0x4aEwxKy9XeGM3alVDNXNtRUFsVE03MWNEWk1kL1BmVGs3aFVDYTlPWFRBRW83TGVrWjlPT1NUaC9JZm9ENjlHeW5HSEszQmowaXQxTUh3SUhYTmh6Y2FVM1BrRWZNZE5xZ3VmUEx6cU03SmVvNGVWQ25ETEpyWjJCNHUzYW5WTlZ1eVozcWRJSDU4K1lIb0QvL2xheGZzazRWeUo5UHY3NkN0M1h6eTNXYW9MLy8vd0FtRUJoaUJCTG1GQUlJSnFqZ2dnaE1sdG1ERURwMXdJUVVWbWpoQWFPVnB1R0dxaFZnd0ljZ2hpaWlBUmx5YUNJRVRvMm9Jb2dsbnJoaGlpdXEyS0tMSGNZb1l3RTBjZ2lqalNIT21PT09QSDdvSTQxQUJqbWtpMFh5ZU9TSlNkcTRwSWxOeHZpa2poNEd5U0tPT1dvWTVZcFR2bGlsbFNSaW1TVnBXOTQ0Wm8xZ2hua21tVjlhMmFXV2JSb3A1cGhsanZnbW1tRGV5V2FhYXE1WnA0aDZvaGlua2dVRUJBQTciIC8+PC9zdmc+");
border-bottom-color: #3d4245
}
.x-tab-scroller-right {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMzYiIGhlaWdodD0iNDMiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMzYiIGhlaWdodD0iNDMiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEpBQXJBSWNBQUc5dmIzbDVlVUQvUUlxS2lwU1VsSzZ1cnRiVzF0ZlgxOWpZMk5uWjJkcmEydHZiMjl6YzNOM2QzZDdlM3QvZjMrRGc0T0hoNGVMaTR1UGo0K1RrNU9YbDVlYm01dWZuNStqbzZPbnA2ZXJxNnV2cjYrenM3TzN0N2U3dTd1L3Y3L0R3OFBIeDhmUHo4L2IyOXZyNitnQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUVBQUFJQUxBQUFBQUFrQUNzQUFBai9BQVVJSEVpd29NR0RDQXNvWE1pd29jT0hFQXVRbUVpeG9zV0pFaTlxcENneGc4ZVBJRU5ta0NpaXBNbVRLRVZJdk1DeXBjdVhGeVNHbUVtenBzMFFFaTNvM01tenB3V0pJSUlLSFVvVVJBRVJGWklxWGNxMHd0RVBVS05LbmZyaEtJV3JXTE5xcFhEVWc5ZXZJOEorSFh0MGd0bXpFd2FnUlh1MGcxdTNZUW1FZmZ2MnFJUzdlQ1VBQUpBWDcxRU9ITUlLRGhBZ0xPRERSeU1vWGh4aEx3REdpbzl1MkNBNExPSENJeVpQUGdxaHMrUFBBRHFMUHFwQnc0akxxREdYMW5EMGdXdlFuMTI3UHVyeGRPckxZVDBlZGNBYjlsN2V3STlpd0dEN2R0amhHSTQyV002OGdlUG15NCt5ckZ3OHJNdWpETEpyWjdCM3UvYWpPcWtUMGc3YjgraUM4K2dYREVpZi9palR1R0diSGxWQXY3Nzkrd3FzYWhXOGxhdUlCQUFHS09DQUNaUzExb0ZzaVlEQWdndzI2Q0FDZHZVbFlWNUhIV0RoaFJobWVFQmlrSFhJMkZFR2hDamlpQ1Fhd0psb0tLWTRtZ2dsdGlqaWlTckdDQUdJTHJZSW80d3AwbGdqaVRmaXVPS09KZmJvNDR3c0FqbWlrRDdxYUtTSklneVpZNUZMTXVra2lrb2FpU1NPVlFKNXBZeFo3cmhsakYzVytLV0tZYm80NXBOUmhuZ21sVkF1dWVhUGFiN1pXWmsyTmpubG5HMWFhZWVkZEFhNTU1Ujk4dmluazRFZU9laVFoYjU0cUk4QkFRQTciIC8+PC9zdmc+");
border-bottom-color: #3d4245
}
.x-tab-panel-bbar .x-toolbar, .x-tab-panel-tbar .x-toolbar {
border-color: #3d4245
}
.x-form-text, textarea.x-form-field {
background-color: #181a1b;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIxOCI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjE4IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUFTQUljQUFON2o1dkR6OC9QMTlmWDM5L2Y1K2ZuNysvejgvZjMrL3YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQkFCSUFBQWdRQUFFRUVEQ0FRQUVEQnhBb1hNZ3dJQUE3IiAvPjwvc3ZnPg==");
border-color: #42474a
}
.x-form-select-one {
background-color: #181a1b;
border-color: #42474a
}
.x-form-check-group-label {
border-bottom-color: #3d4245;
color: #c8c3bc
}
.x-editor .x-form-check-wrap {
background-color: #181a1b
}
.x-form-field-wrap .x-form-trigger {
background-image: url("../img/dark/trigger-flat-dark.svg");
border: solid rgb(45 69 83);
border-width: 1px 1px 1px 0;
height: 20px;
width: 16px
}
x-trigger-wrap-focus .x-form-field-wrap .x-form-trigger {
border: solid rgb(83 72 45);
border-width: 1px 1px 1px 0;
height: 20px;
width: 16px
}
.x-small-editor .x-form-field-wrap .x-form-trigger {
height: 18px;
}
.x-form-field-wrap .x-form-date-trigger {
/* background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAyIiBoZWlnaHQ9IjI0Ij48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjEwMiIgaGVpZ2h0PSIyNCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoWmdBWUFOVW9BSTZPanQ3ZTNzek16UC8vLzhuSnlhU2twT0RnNE5mWDE5SFIwY2pJeU83dTdpZ29LUHo4L1BiMjlybTV1Zkh4OGYzOS9kTFMwdFBUMDkzZDNjTEN3dHJhMnR2YjI5bloyZS92NzhyS3lzZkh4OFhGeGR6YzNQRHc4Ti9mMzh2THkvdjcrL1gxOWRiVzF0VFUxT3pzN1BQejgrM3Q3ZnI2K3YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBRUFBQ2dBTEFBQUFBQm1BQmdBQUFiL1FJZHdTQ3c2VUlXa2Nza3NJSnZRNURQYW5GS1gxcXNVd3UxNnZ4Y0hZMHd1bXorRmczck5icVBOOFBJN0hrZTM3MnowWTgvdjk3a09Cb0tEaElRUUEybDRpZ1dGallPSEJRMlNrNVNVQTRpS2kzNmJmU0dCam82WW1YZU1vSTJJbGFtV2lhTnNCUjBkRkFDenRMVVVIU0FPSGg2eXRiNFVIcUt0YXdXN3ZiNjB3SWdoSWNmSUFCUWh3c01IQlJnWXo3NFl1UUVCMmJVQm9zN0lGR29GM2QrMDRRVWxKZW16SmVMcDVkVUtDZ0RkK1FQaCt3QUt1Uk1tNE1zWGpwKzNDYUxlQVRBWGNLQStnd0FRRnRqanNOdStTOTRlSkh4bnpsN0ZmQXNXZVB2bmdBT0hqOTFDZXVPUWtHQkJqQXVybVVRWlFDVUFscTg2MExUWm9TWEIvNHY5ekprd0FRQm91QVdYRmdBd2tjdUNoYUlHQnlDVkNzQ0NUNWMyelRtRmlsRnEwcXFJcm5HOU9GVXBocXNFczFZalFXTHMwYThrVGppb1VNR3RWNm9WRWhxOXE5UWNYYnRsQWVRdDRIRnZZQVY2b3dabUtOQmxTcEVSR3pqWXNHRW41QTBLQ2lSSUFQanI1Z0tVTFh2RFhPRENCZEVBTG1UZTNKbnE1Nzk3SVZhUXJFR0RYWWdhVm5OMlhCUHk1OXEzWWVZdXNEVTJUQXU2VVg4MkhiemZCY2taTWpUM2xpRzU4WDZmbzA4SFVMMUF3K3NIclVlRitGa056WHdMSlFzUWNCNmRBUEZkeVNjb3NMNjl0L2VsN0FNd0FQK2kvQUlpaUxDZENPcXhCeDRBK0xIR0czcWYxWGNnZm9Kc3g1OW11eTNveldjampLRFFDQVVxbEw0Z1p3YzJ5TjQ3RUJxZzBJU3NoVGlmQkN5MjZPS0xCYTRuNDR3ekp2ZU9pRFRtdUY1bXBqUmlZenFmUlNEa2tFUVdHYU9PTkdaR3dKSk1OdW5rZkVqcXlHT1BoQ2pwNUpWTXpvZkFsbHgyNmVXUlVlNVlBSlprUWhsbWphVlFLWWlWWkQ1WmdKZHdkZ2xtbUd5Mm1TVjlaOG80cFpvVDJ1bG1uSURPR1dXZGZwcVpaNGw4RW1xbmxvRENLU2lTaXJacGFKNTdxaGxwbVc4MitxVURoNHJwWjVPVG5sa3BsWmRpeWFpbVhENHE1WmlmTGhrcW5XbGF5bXFyOHdVQkFEcz0iIC8+PC9zdmc+"); */
}
.x-form-field-wrap .x-form-clear-trigger {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAyIiBoZWlnaHQ9IjI0Ij48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjEwMiIgaGVpZ2h0PSIyNCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoWmdBWUFPWUFBTXpNek9EZzROZlgxOG5KeWFTa3BNakl5TkhSMGZIeDhmejgvTnZiMjk3ZTNybTV1ZmIyOXMzTnpmRHc4Ti9mMys3dTd0M2QzWFoyZHRyYTJ1Ym01cFNVbFBYMTllL3Y3K1RrNU9ycTZ1M3Q3Zkx5OHVMaTR2MzkvZFBUMDYrdnI5TFMwdFRVMU1yS3l2UHo4OXpjM0xHeHNhYW1wcCtmbjJscGFaQ1FrTmJXMXBpWW1IZDNkMjl2YjluWjJlenM3T1BqNDhmSHg4WEZ4WnFhbXJDd3NPWGw1Yy9QejlYVjFlSGg0WnVibTZXbHBkalkyTWJHeHV2cjYram82T2ZuNStucDZmVDA5QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQUFBQUxBQUFBQUJtQUJnQUFBZi9nQXVDZzRTRmdnU0lpWXFMakkyT2o1Q1JrbzBkbFphWG1CMExDSnlkbnA4SUJBS2pwS1dtQWdTZ3FwMnBxNnFpcDdHakJBZTF0cmU0QndzQnZMMit2d0d3c3FjRXdNYTlCQXpLeTh6TkRNTERwYlM1MUxXN3g4YlEwYlBZMmM3Znk5cmJCQTdsRHJYbTZPWU9Ddy91RHh3YzcvSHY3dUxSQlBYMDd2dnZCQllBTFNnTE9EQ2doWHZEQ0Z4WXVNSENoZzBYSGpwY3VIQ0Jnb3NZSUdKNGdDRWlob3NYb1NWSVFHcWtLUUlnTTE3WTJISERSNUFFUnNnRU9NSkN6Wm8yWlk0UVNYS1VTV2tRSURnSXNxTEVnUkVIU3F3STRpQW9oQVVSSWdRNFVCUUNCUWhLRHdTSUdrR1lBZ2NhRk94UW9NR0JBbWxScDFhOW1uVnIxR2sxLzRzMjNLRFVwaTJ2WU1XU05RdFVLQVFhTFdqOERldzM2QUlTSkI3MCtORGlnd2JHSDNvOFFFd0NWZ0lIUlRWdzBLRFVRVTlVaUJWRGZ0eFlNbVZ5RGpZTXBuRUJzT0FONWl4akxxR1o4d3JQcEFobzJPMGdnd2tVT2xDWXlBQjJ0NFlGSXhQZ29QQTd1QWtLT0pJbnNKd0I4Z3ZJR1Q0VFNMNjh1WERvMGhVeTlBMWNlQWFJRktsYng2NzloZnNYQnlpY2tIQ0N3b0gzN2hkTTJKOEFCb2I1SjJBQVF3TDc3ZWNWYytVOWQxWnVCZmIzSDMwQ0VsZ2dBVTVCc0lGODlGR2dXb1VIZXFjZ1dsSEJBRVFPRXN3Z1FRNUF3TUJWQkF2SUlBTVBOdFJnNG93MTJNQ0RpeklRVU1DT0lnakFBWUFjQ0NEQ2pqc1M0Q0tNTXBaWVl2K05ON3BJZ0F0UUJ1QURpU2JtNEVNQVVFS3BJNDgrQWlra2tRVVFzRjhFR1ZRZ1FRVVJtRmxCQmhFVXVFQU1NVFJBZ1pvVHFFbEJBM0RHc0dVQkJ0UkE1WWsxR0FBbUFYREtTYWVkZU1LNVhRSUtsSGttQ1dwbW9FQnllL2I1Wnc2QkRnb2xDUnF3a0FJT0txYkFnZ1lrWkxtQUNDTFlrSUduWWlVZ2FnWTJvQ3JDbG9hZW1RQ2lSQktBcXFxczd1QXFDN0RLU2tCVU9FRGdLUWMvS0NBcUJEaHdSZXVjdHVKYUpDa0svQkNBWGdFa1c4b0NBQURRd0EwZjNmQ3RBaGlJMnkwQXRLNmF3bGtUdk5wQXJ0MStHKzY0NVRad2JqRzhVT0FEQjlCUndJRVBGUGlTTHFzQ3RBdnN1MFdxb0xBSyt5M2M4TUlxY0J1dkFRYlkyd0R1eGZiZVM2UUJHRVJnd0FBR1JJQ0JvUEJPWExHM0dKK0xyaTh3d05CTHk3OVUydkhISVk4OGFBZzQ1Nnp6emlGSXJQTFBQKzlaUUFNSUQxMTBrVUFuZlc4M3dBaE5OSkZQRCtyQjFGUlhiYlVIUGlzZE5KaGNkeDJtMWtuanl6UXlYcGNkSmdob3A2MzIyaUJrRFhhM0JBd2c5OXgwMS8zMTJ5cUxQWFl3ZGZkTmQ1Z1VCeTc0NEJTNy9YYmNmdnQ5Tjk1dzc0MU00b29UUVBqa2dSc09OdUtRLzAwQTQwczd6bmZtbWxOT3VlVmFZdzc2QUlzenJ2Zllwb01PdU9pRWs2NTA2NW1uanZmcVROTU8rZXV3Q3k1NzJLZlBiZnZobm44ZVBPKzlGODQ1M01ITFBmemx4ZXVlZUppQkFBQTciIC8+PC9zdmc+")
}
.x-form-field-wrap .x-form-search-trigger {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAyIiBoZWlnaHQ9IjI0Ij48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjEwMiIgaGVpZ2h0PSIyNCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoWmdBWUFQZUhBTXpNek1uSnlhU2twT0RnNE5mWDE5SFIwY2pJeU83dTd2ejgvTTNOemJtNXVkcmEydmIyOXRqWTJOUFQwK0hoNGQ3ZTN0M2QzZGJXMXR2YjI5L2YzLy8vLzg3T3p2SHg4ZWZuNStUazVPUGo0LzM5L2VqbzZQTHk4dUxpNG10cmEvRHc4TXJLeXVycTZ1Ym01dW5wNmR6YzNOTFMwdVhsNWMvUHoyaG9hS2FtcG1GaFlXSmlZbkJ3Y0lDQWdORFEwSXFLaXZYMTljdkx5OW5aMldscGFYcDZldFRVMUxTMHRKZVhsNUdSa2ZUMDlOWFYxV05qWThYRnhicTZ1c2ZIeDhIQndheXNyR2RuWi9qNCtPL3Y3MzE5ZmIyOXZhT2pvOGJHeG50N2UyUmtaSnVibSszdDdVMU5UWEZ4Y2Z2NyszSnljbXBxYXZQejgwVkZSV3hzYk96czdMS3lzb0tDZ3JHeHNYVjFkYlcxdFdWbFpXOXZiNGlJaUZsWldaQ1FrSFIwZElHQmdjREF3S3FxcXZuNStjVEV4SDUrZm5OemM3aTR1RzV1Ym54OGZKYVdsb09EZzNoNGVGcGFXbjkvZjdlM3Q2bXBxYTZ1cnErdnIyMXRiYUdob2JPenMzZDNkNktpb291TGkrdnI2NG1KaVVaR1J2cjYrb1NFaEx1N3UvZjM5MDVPVHBxYW1xZW5wMGRIUjdDd3NKbVptZi8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBRUFBSWNBTEFBQUFBQm1BQmdBQUFqL0FCVUlIRWl3b0lKREFoSXFYTWhRQU1LR0VCTStqTmh3SXNXRkZpOUszTUN4bzhlUE14UWdHRW15cEVrWkFnaW9YTW15SlVxVE1FdStqQmtUWmN1YkxGRmUyTW16ZzQ0WU1YUjAyTWxSd1lDalJ4OW93TUNCQXdZTlJ6ZFVTSG16Z2RVR0xRVWdUYnEwNmRPb1V4bUlIY3RnaU5raFl5dE14WGtWSzBzQlBDLzRaQkFCZ0lVQkRJWmVpR0VVNmRJcUJINkVXQ0FDNm9DMUxCdE1vUERnQVlVRmI3ZitEVHk0OE5Hd1pJZVFvWkFBaFFZeWFhbXVWTXpZTWVTVkFrQ28zc3RCeFpVa1NkakFpWEVCeEJNRkZISjdJT0VCajRzYU5hNVlFZUhoc0dnQ0N3YU1jRkFHaVlRTUUxRG5wckM3OSsvZ3c0dFBCUXAwaUloQmJHRDcvMUdBTmdaaWxjbVhOMzhlWGFVQUl2QTdnRENVSlVjUElERE13TkZoV3dFRUNCU2NRQUlPOWQwSGd4cFlrUERBZVF0a0FFRWQxNFV4QjNUdS9SZmdnQVhpaDZDQ1UwbmhJVzJDWkppSEdXZ0FvZ09ERGtJSW5JUVVFaURBQVRCMjhJSVRNSFFRQVFRZy9KYkJCYmRGY09NSU1yUlE0NDA1dGdGQkJvZzFRTUVJYTRCaEgzNUp5SkVCWkFMNENBR1FRdHFJb3d0R0lnbVhYREVVUUtPV09kWXd3b2xVS2Nta2t3WkdPYVdMTUI3UWdRSWZHREdCQlo0RlFRVUFIZHhXUWdrUm5LQkZuWGZtK2NFUEp5VDVRQUJaRXVuQ0hTVlEwSUFBZndZNnFKMTRhaERFb1ltbXBwb09kR0thSnhVSm9LbFNBNHMydWlXa2tnckF4S3NkK1ArUXdnMFF2TEFEQmtmUVlFR2ZDa3d3UVFtQ0NrR3JyYmltWUlDWHB6NWdCNkdaYm9yRUE1UDZDcXdXd3RaNjZ4SEdlZ2tmRVZMNFVDMnh1Vm9naGFMTGlxcnBCODlPV2tVVlRGd2d3Ull0T0NVQ0JSK2NRUUlJZlNpd3dBSVRaRkFBdlBKU0VJVVRIaXlZNWdNM2ZIdHRDajlBSzhDKy9mNGJMd2J6RGx6d1ZIRjI4TzdFRlo4aHdnV0tKanpzd2cxUDZ1TUFJalJBd3dvMExJRkRDbWtBd1FGZUN2U0FCQUFsT0pBQ3l5NEw4WUVDRFlSd2dBQUdHQkJDQXdBb3diSEFYRXpnUUFBQzJJeXp6anpqNERQUVFnc3d3d3dSY0VEQXlpMi9USWNZSjVRd2RORkhKNzEwRkUwLy9YQUVJeEFBeGdwRjhNQ0RFazZJTVVJRUN6RC9vSUFCQ1N4UUFCUjBzOEFDRHkzb200QUJad2RnUVFSVWg1M0NCejRzc0RqUmdROWUrT0dKVzg2NEFCTkFnRUVEYzlkOU54UmlZQURCQkkwL0hybkxrMWQrT2JBNzBPRkdEa3g0QU1BTEo1d1F3ZForV3pEQkMxUjQ4UVVKRUJnQUFBVVRvQ0JEMWdGa1RuZ1JodlBBaGV3QkdDQ0E4TVFiajd6eXpEdWY5UUFrU0pERzdRZG9rRUFCSXlnSVFRUkRSeS80OU5WZmIzbjJBbERnZ0JKTjdPR1VCd1Y3ekVvWTRBTUpvSUFGVGVqQ0NRYXdyeGxJb0FBSkFBQUFoaFk0Rkh6QWV4SDRnUXdnY0wraXFjQ0FDRlFnQXhmZ1FBaEs4QUFxaUpzU0FnRURQVENCQkUwWlFYR09Rc0VGV0JDREd1UmdBcktudlFFRWdROWh3TUNiLzFZaWdTSktnQUYvbU1FWXB1Q0NERVRBQkJhSVlnSWllRUlWT0NBQklkUkFCQWhReEN2eTBBQXFVQ0lUblFoRktWSnhnaXJnUUNFSWNRVVJGS1l4amRrS0NxK1l4UzEyY1lkRjAxNEpJSENEREhpZ0FUdXdnU0FIS1VnQ1NtQUJWbmhBQkV3b3dVWldVUUp4bU1JYlBMQUFDNFFnQUpqTW93Y1BtY2hGbnRHUmFCeEJCdEJBQXN0c1JZNGZqT1FrSzNuSlRHcFNBQklJWFFrSVlBTUgyUEtXdC9UYkN5UlF3aytDY280TndBSUQ4YWpKVis2eWw2QjA1TkE4TUFJT3lQQ1Vwd1NtTUR0WXpEd0t3QVMzTklFMnQ4bE5FL2h0aWhhWVlqS1ZLUUFBT0VBQ1hzU2tPdGVwUFhDS2M1d24xQW9jb1JuTmNwNHpuZXRrcHdBS3dJblBmdnJ6bjM2RDV6ampGNEtDNXZPZzJoTm9Nb2RHejRZUzFLQUgxZWMvSityUGdDcVVuQkhOYUVJdjJraUdOaFNhOGNzb1F2ZEpVWXBhbEtNVEZJQklSNHJTZUg0VXBDcGRxVVJMT3RHVGNqU2tNczFrT1Z2cTBaY2lCYWM1MVI1TmE2cUFscVkwcCtyY0tFcDc2dE1CQUZXbVFoMXFSWXZLMDVnaVZhazMxVXBUYVdqVm9Bb2dJQUE3IiAvPjwvc3ZnPg==")
}
.x-item-disabled .x-form-trigger-click, .x-item-disabled .x-form-trigger-over {
border-bottom-color: #42484a
}
.x-form-focus, textarea.x-form-focus {
border-color: #655e53
}
.x-form-invalid, textarea.x-form-invalid {
background-color: #181a1b;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIzIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMjQ5IC0wLjYxNCAtMC42NzIgMC4wMDAgMS4wMzUgLTAuNjQ2IDAuMjg4IC0wLjY2NCAwLjAwMCAxLjAyMCAtMC42MzYgLTAuNjA5IDAuMjUwIDAuMDAwIDAuOTk0IDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMyIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBREFJY0FBQUQvQVA4QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBRUFBQUFBTEFBQUFBQUVBQU1BQUFnTUFBTUFHQWhBb01DQ0FBSUNBRHM9IiAvPjwvc3ZnPg==");
border-color: #c23000
}
.ext-webkit .x-form-invalid {
background-color: #3d0000;
border-color: #910800
}
.x-form-inner-invalid, textarea.x-form-inner-invalid {
background-color: #181a1b;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIzIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMjQ5IC0wLjYxNCAtMC42NzIgMC4wMDAgMS4wMzUgLTAuNjQ2IDAuMjg4IC0wLjY2NCAwLjAwMCAxLjAyMCAtMC42MzYgLTAuNjA5IDAuMjUwIDAuMDAwIDAuOTk0IDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMyIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBREFJY0FBQUQvQVA4QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBRUFBQUFBTEFBQUFBQUVBQU1BQUFnTUFBTUFHQWhBb01DQ0FBSUNBRHM9IiAvPjwvc3ZnPg==")
}
.x-form-invalid-msg {
color: #db4e52;
background-image: url("../ext/resources/images/default/shared/warning.gif")
}
.x-form-empty-field {
color: #988f81
}
.x-form-invalid-icon {
background-image: url("../ext/resources/images/default/form/exclamation.gif")
}
.x-fieldset {
border-color: #3e4446
}
.x-fieldset legend {
color: hsl(0deg 0% 57%)
}
.x-btn button {
color: #c8c3bc
}
.x-btn-bc, .x-btn-bl, .x-btn-br, .x-btn-mc, .x-btn-ml, .x-btn-mr, .x-btn-tc, .x-btn-tl, .x-btn-tr {
background-image: none;
}
.x-btn-click .x-btn-text, .x-btn-menu-active .x-btn-text, .x-btn-pressed .x-btn-text {
color: #e8e6e3
}
.x-btn-disabled * {
color: #988f81!important
}
.x-btn-mc em.x-btn-arrow {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaENnQUtBSWNBQUFBQUFQLy8vd0FBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUVBQUFFQUxBQUFBQUFLQUFvQUFBZ1pBQU1JSEVpd29NR0RDQTBDV0xoUVljT0RBQkpLbkZnd0lBQTciIC8+PC9zdmc+")
}
.x-btn-mc em.x-btn-split {
background-image: url("../ext/resources/images/default/button/s-arrow.gif")
}
.x-btn-mc em.x-btn-arrow-bottom {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMjAwIiBoZWlnaHQ9IjE0Ij48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMjQ5IC0wLjYxNCAtMC42NzIgMC4wMDAgMS4wMzUgLTAuNjQ2IDAuMjg4IC0wLjY2NCAwLjAwMCAxLjAyMCAtMC42MzYgLTAuNjA5IDAuMjUwIDAuMDAwIDAuOTk0IDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjIwMCIgaGVpZ2h0PSIxNCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoeUFBT0FJY0FBQUFBQU1URXhNTGE5di8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBTUFBQUlBTEFBQUFBRElBQTRBQUFoZkFBVUlIRWl3b01HRENCTXFYTWl3b2NPSEVDTktuRWl4b3NXTEdETnEzTWl4bzhlUElFT0tIRW15cE1tVEtGT3FYTW15cGN1WE1HUEtuRW16cGsyR0FITG12TW16SjBlZFBvTUtyUWhncU5HalNKTXFYY3EwcWRPblVLTjJEQWdBT3c9PSIgLz48L3N2Zz4=")
}
.x-btn-mc em.x-btn-split-bottom {
background-image: url("../ext/resources/images/default/button/s-arrow-b.gif")
}
.x-btn-click .x-btn-mc em.x-btn-split-bottom, .x-btn-menu-active .x-btn-mc em.x-btn-split-bottom, .x-btn-over .x-btn-mc em.x-btn-split-bottom, .x-btn-pressed .x-btn-mc em.x-btn-split-bottom {
background-image: url("../ext/resources/images/gray/button/s-arrow-bo.gif")
}
.x-btn-group-header {
color: #a8a095
}
.x-btn-group-tc {
background-image: url("../ext/resources/images/gray/button/group-tb.gif")
}
.x-btn-group-tl, .x-btn-group-tr {
background-image: url("../ext/resources/images/gray/button/group-cs.gif")
}
.x-btn-group-bc {
background-image: url("../ext/resources/images/gray/button/group-tb.gif")
}
.x-btn-group-bl, .x-btn-group-br {
background-image: url("../ext/resources/images/gray/button/group-cs.gif")
}
.x-btn-group-ml, .x-btn-group-mr {
background-image: url("../ext/resources/images/gray/button/group-lr.gif")
}
.x-btn-group-notitle .x-btn-group-tc {
background-image: url("../ext/resources/images/gray/button/group-tb.gif")
}
.x-toolbar .x-item-disabled, .x-toolbar .x-item-disabled * {
color: #988f81
}
.x-toolbar .x-btn-mc em.x-btn-split {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTQiIGhlaWdodD0iNzIiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTQiIGhlaWdodD0iNzIiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaERnQklBSWNBQUFBQUFNbkp5Y0xhOXZYMTlRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQU1BQUFJQUxBQUFBQUFPQUVnQUFBZzhBQVVJSEVpd29NR0RDQk1xWE1pd29jT0hFQ05LbkVpeG9zV0xHRE5xM01peG84ZVBBRUtHVkNpU0lZQ1BLRk9xWE1teXBjdVhNR1BLbkJrUUFEcz0iIC8+PC9zdmc+");
}
.x-toolbar .x-btn-click .x-btn-mc em.x-btn-split, .x-toolbar .x-btn-menu-active .x-btn-mc em.x-btn-split, .x-toolbar .x-btn-over .x-btn-mc em.x-btn-split, .x-toolbar .x-btn-pressed .x-btn-mc em.x-btn-split {
background-image: url("../img/dark/s-arrow-o.gif");
}
.x-toolbar .x-btn-mc em.x-btn-split-bottom {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMjAwIiBoZWlnaHQ9IjE0Ij48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMjQ5IC0wLjYxNCAtMC42NzIgMC4wMDAgMS4wMzUgLTAuNjQ2IDAuMjg4IC0wLjY2NCAwLjAwMCAxLjAyMCAtMC42MzYgLTAuNjA5IDAuMjUwIDAuMDAwIDAuOTk0IDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjIwMCIgaGVpZ2h0PSIxNCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoeUFBT0FJY0FBQUFBQU1URXhNTGE5di8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBTUFBQUlBTEFBQUFBRElBQTRBQUFoZkFBVUlIRWl3b01HRENCTXFYTWl3b2NPSEVDTktuRWl4b3NXTEdETnEzTWl4bzhlUElFT0tIRW15cE1tVEtGT3FYTW15cGN1WE1HUEtuRW16cGsyR0FITG12TW16SjBlZFBvTUtyUWhncU5HalNKTXFYY3EwcWRPblVLTjJEQWdBT3c9PSIgLz48L3N2Zz4=")
}
.x-toolbar .x-btn-click .x-btn-mc em.x-btn-split-bottom, .x-toolbar .x-btn-menu-active .x-btn-mc em.x-btn-split-bottom, .x-toolbar .x-btn-over .x-btn-mc em.x-btn-split-bottom, .x-toolbar .x-btn-pressed .x-btn-mc em.x-btn-split-bottom {
background-image: url("../ext/resources/images/gray/button/s-arrow-bo.gif")
}
.x-tbar-page-first {
background-image: url("../ext/resources/images/gray/grid/page-first.gif")!important
}
.x-tbar-loading {
background-image: url("../ext/resources/images/gray/grid/refresh.gif")!important
}
.x-tbar-page-last {
background-image: url("../ext/resources/images/gray/grid/page-last.gif")!important
}
.x-tbar-page-next {
background-image: url("../ext/resources/images/gray/grid/page-next.gif")!important
}
.x-tbar-page-prev {
background-image: url("../ext/resources/images/gray/grid/page-prev.gif")!important
}
.x-item-disabled .x-tbar-loading {
background-image: url("../ext/resources/images/default/grid/loading.gif")!important
}
.x-item-disabled .x-tbar-page-first {
background-image: url("../ext/resources/images/default/grid/page-first-disabled.gif")!important
}
.x-item-disabled .x-tbar-page-last {
background-image: url("../ext/resources/images/default/grid/page-last-disabled.gif")!important
}
.x-item-disabled .x-tbar-page-next {
background-image: url("../ext/resources/images/default/grid/page-next-disabled.gif")!important
}
.x-item-disabled .x-tbar-page-prev {
background-image: url("../ext/resources/images/default/grid/page-prev-disabled.gif")!important
}
.x-paging-info {
color: #bdb7af
}
.x-toolbar-more-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTIiIGhlaWdodD0iMTYiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTIiIGhlaWdodD0iMTYiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaERBQVFBSUFBQUdOalkyTmpZeUg1QkFFQUFBRUFMQUFBQUFBTUFCQUFBQUlhakkrcHkrMEpvb2tBeWtCdHhmZGt2b0ZUOTMzaSthVHFXZ0FBT3c9PSIgLz48L3N2Zz4=")!important
}
.x-resizable-handle {
background-color: #181a1b
}
.x-resizable-over .x-resizable-handle-east, .x-resizable-over .x-resizable-handle-west, .x-resizable-pinned .x-resizable-handle-east, .x-resizable-pinned .x-resizable-handle-west {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMjAwMCI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxMCIgaGVpZ2h0PSIyMDAwIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhDZ0RRQjZJQUFOZlgxK25wNmVYbDVkdmIyK0RnNEtPam8vLy8vd0FBQUNINUJBQUFBQUFBTEFBQUFBQUtBTkFIQUFQL0dFSUQvb285dU5vRTBjNThjZTNjRlc2ZldKS1NtYUlhdGJxdE04TGdTYXV4OThvMnYrdTVtUy9ZQTlaK1FpUHVTRVFXazlDbjFFbHRXcG5ZcFphVjVXNXYzakI0UE95U2xlTHlWNTFHbjZOVk0vczl2YTdkOHp4K0Q3ZTMrM0o4ZFlHQWQ0Vi9nNGFKaUhHS2pZeCtkSStTa1hxSGxJU0xtSTZWZ3BPV21xQ2ZucDJYb3FXaHBKbWpwcXFjcTZpc3FhMjBzN2F5dUxHNnNMeXZ2cEM5d0wrYndzWEV4NmZCeUs3R3ljUE96Y3pMdGJuSzBOTzN1OC9TMTkzYzM5VGEwZUhXNE5ubDVOdnA0K2ZxN2V6Vjd2SHc0dGp6OXZYZTYvam83L3p5K2N6ZDArZVA0RUNCQWZjWlRGZ1FZYitEQ2gwQ2ZNZ1FZc09JR0M5cXRNaXgvNkpIaWlBbmlxUVhrdVRJZnlaVG9seTVzQ1JMaVNwYm5wUVpFK2JMakIxZDByeTU4ZU5NbXp1REFoMkswMmZOb2pxSjlreUs5R2ZUbzB1ZFJvV2FVMnBWcWtaNVh0V2FWZWhUcmt5bmdyWGFWZWxXcjJMUm5qVmI5cXZhdG1uWmhsM3JWaTdadVhEcHhxM0xkNjlmdllEekNzWkwrSzVocklVUkh4NnJ1REhqeDI4VFE3YnJPUEppeTVVcFQrNGJXRExtelg4SFg5Yjh1VFRwMDV4RlowN3RHWFhvMXF4SHgxNzlXbmJ0b3dVS0JNbHRvSWFCM29aeTd5NEFuTVJ2RUIwZ0NBZkIyM2R4Q01sbExCZlIzTVJ4MjUyeHF3YWRuWFozN3R0Tnp3WVArelo1N2VXL2l6ZS9YcjFyOStQYmgzOC9Qejc5OVBYWjMwZlAzM3QrK0xiNjJTZGdnQVFDYU9CL0NPS25ZSC9uK2JlZ2d3eks5MkNERkVvWTRYNFFabGdoaGhzT2VPQ0VGbW9ZWW9jRkpuaWhoeWFLeU9HSUxLN29Jb29ndmxoaWpEQ2VPS09OSCtLWUlvazVxbGlqanpjQzJTT1BPN2I0STVFMEJvbWtqa2tPYWFTU1R6b3BvNVJIUmxua2xGZFdpV1dUV1VLNUpaTmdDdGtsbFY1cWFXYVphSktwNXBoc2N1bG1tRXVLK2FhY2NGbzVaNXg0MmxubmwzVDJtU2VmZjU2NTVwMTYrbGxvb0dtMnVhZWdpaG9LcUdrSkFBQTciIC8+PC9zdmc+")
}
.x-resizable-over .x-resizable-handle-north, .x-resizable-over .x-resizable-handle-south, .x-resizable-pinned .x-resizable-handle-north, .x-resizable-pinned .x-resizable-handle-south {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMjAwMCIgaGVpZ2h0PSIxMCI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyMDAwIiBoZWlnaHQ9IjEwIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGgwQWNLQUtJQUFOZlgxK25wNmVYbDVkdmIyK0RnNEtPam8vLy8vd0FBQUNINUJBQUFBQUFBTEFBQUFBRFFCd29BQUFQL0dMcmMvakRLU2F1OU9Pdk51LzlnS0k1a2FaNW9xcTVzNjc1d0xNOTBiZDk0cnU5ODcvL0FvSEJJTEJwdmdxUnl5V3c2bjlDb2RFcXRXcS9ZckhiTDdYcS80TEI0VEM2YnoraTBlczF1dTkvd3VIeXVMQlNTZHZ4ZGtLZjcvNENCZ29PRWhZYUhpSW1LaTR5TmptUUVrWktUbEpXV2w1aVptcHVjblo2Zm9LR2lvNlNscHFlb3FhcXJySzJ1cjdDeHNyTzB0YmEzdUxtNnU1SjJCZ1Mrd0FXL3diekd4OGpKeXN2TXpjN1AwTkhTMDlUVjFxc0QyZHJiM04zZTMrRGg0dVBrNWVibjZPbnE2K3p0N3UvdzhmTHo5UFgyOS9qNSt2djgvZjcvQUFNS0hMak5nSUZzQmhFZUhKQ1FvTU9IRUNOS25FaXhvc1dMR0ROcTNNaXhzNlBIZVFCQ2loeEpzcVRKa3loVHFsekpzcVhMbHpCanlweEpzNmJObXpoejZ0ekpzNmZQbjBDRENoMUt0S2pSbzBpVEtsM0t0S25UcDFDalNwMUt0YXJWcTFpemF0M0t0YXZYcjJERGloMUx0cXpaczJqVHFsM0x0cTNidDNEanlwMUx0NjdkdTNqejZ0M0x0Ni9mdjRBREN4NU11TERodzRnVEsxN011TEhqeDVBalM1NU11YkxseTVnemE5N011YlBuejZCRGl4NU51clRwMDZoVHExN051clhyMTdCank1NU51N2J0MjdoemcwMEFBRHM9IiAvPjwvc3ZnPg==")
}
.x-resizable-over .x-resizable-handle-southeast, .x-resizable-pinned .x-resizable-handle-southeast {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaENnQUtBTE1BQU5mWDE2T2pvLy8vLytEZzRPbnA2ZWJtNXRyYTJ1WGw1ZWZuNStMaTRnQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQUFBQUxBQUFBQUFLQUFvQUFBUWZrSkFTd2dBWUVIU3F5RUJ4SklQd1pkVlFHYURuZ2FWZ21HQnQzM2hlUndBNyIgLz48L3N2Zz4=")
}
.x-resizable-over .x-resizable-handle-northwest, .x-resizable-pinned .x-resizable-handle-northwest {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaENnQUtBTE1BQU5mWDE2T2pvLy8vLytEZzRPbnA2ZWJtNXRyYTJ1WGw1ZWZuNStMaTRnQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQUFBQUxBQUFBQUFLQUFvQUFBUWZFTWhKcTcwWUMySDJvRUlRaEFGbGlJTUlDa055RktCNElBU1ZCZ1ZCUkFBNyIgLz48L3N2Zz4=")
}
.x-resizable-over .x-resizable-handle-northeast, .x-resizable-pinned .x-resizable-handle-northeast {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaENnQUtBT01DQU5mWDE2T2pvLy8vLytEZzRPbnA2ZWJtNXRyYTJ1WGw1ZWZuNStMaTR2Ly8vLy8vLy8vLy8vLy8vLy8vLy8vLy95SCtFVU55WldGMFpXUWdkMmwwYUNCSFNVMVFBQ3dBQUFBQUNnQUtBQUFFSUJESVNhdTltQTRoREtkQklJUUNHQXloUVJWSHNwVVRnUndrUlJCRk9GQVJBRHM9IiAvPjwvc3ZnPg==")
}
.x-resizable-over .x-resizable-handle-southwest, .x-resizable-pinned .x-resizable-handle-southwest {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaENnQUtBTE1BQU5mWDE2T2pvLy8vLytEZzRPbnA2ZWJtNXRyYTJ1WGw1ZWZuNStMaTRnQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQUFBQUxBQUFBQUFLQUFvQUFBUWhFRWd3UWlpRVRDRHNRZG9rQ0VOeUZKdGhWY0hXQmE4ckdPT3czWGl1NzBBRUFEcz0iIC8+PC9zdmc+")
}
.x-resizable-proxy {
border-color: #70685c
}
.x-resizable-overlay {
background-color: #181a1b
}
.x-grid3 {
background-color: hsl(200deg 6% 11%)
}
.x-grid-panel .x-panel-mc .x-panel-body {
border-color: #3d4245
}
.x-grid3-hd-row td {
border-left-color: #35393b;
border-right-color: #3d4245
}
.x-grid-row-loading {
background-color: #181a1b;
background-image: url("../ext/resources/images/default/shared/loading-balls.gif")
}
.x-grid3-row {
border-color: #303436 #353a3c #353a3c
}
.x-grid3-row-alt {
background-color: hsl(200deg 5% 13%)
}
.x-grid3-resize-marker, .x-grid3-resize-proxy {
background-color: #5a6165
}
.x-grid3-header-pop {
border-left-color: #3d4245
}
.x-grid3-header-pop-inner {
border-left-color: #35393b;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iOSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjI0OSAtMC42MTQgLTAuNjcyIDAuMDAwIDEuMDM1IC0wLjY0NiAwLjI4OCAtMC42NjQgMC4wMDAgMS4wMjAgLTAuNjM2IC0wLjYwOSAwLjI1MCAwLjAwMCAwLjk5NCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxMCIgaGVpZ2h0PSI5IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhDZ0FKQUljQUFHRmhZVUQvUUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFNQUFBRUFMQUFBQUFBS0FBa0FBQWdrQUFFSUhEZ3dBSUFBQ0E4bU5FaVFvRUdFRHhjcWpQaHdJa1NJRmhzNlpHanhvc0tBQURzPSIgLz48L3N2Zz4=")
}
td.sort-asc .x-grid3-hd-inner, td.sort-desc .x-grid3-hd-inner, td.x-grid3-hd-menu-open .x-grid3-hd-inner, td.x-grid3-hd-over .x-grid3-hd-inner {
background-color: #1b1e1f;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMiIgaGVpZ2h0PSIyMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyIiBoZWlnaHQ9IjIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBZ0FXQUxNQUFOcmEydWJtNXVYbDVlTGk0dDNkM2R2YjI5N2UzdC9mMzd5OHZPSGg0ZVRrNU9QajQrRGc0TnpjM0FBQUFBQUFBQ0g1QkFBQUFBQUFMQUFBQUFBQ0FCWUFBQVFZTU1ncHFsQnFyY0ZIU2d4empFWkpuRVJUckVEcklrZ0VBRHM9IiAvPjwvc3ZnPg==")
}
.x-grid3-cell-text, .x-grid3-hd-text {
color: #e8e6e3
}
.x-grid3-split {
background-image: url("../ext/resources/images/default/grid/grid-split.gif")
}
.x-grid3-hd-text {
color: #c8c3bc
}
.x-dd-drag-proxy .x-grid3-hd-inner {
background-color: #1b1e1f;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMiIgaGVpZ2h0PSIyMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyIiBoZWlnaHQ9IjIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBZ0FXQUxNQUFOcmEydWJtNXVYbDVlTGk0dDNkM2R2YjI5N2UzdC9mMzd5OHZPSGg0ZVRrNU9QajQrRGc0TnpjM0FBQUFBQUFBQ0g1QkFBQUFBQUFMQUFBQUFBQ0FCWUFBQVFZTU1ncHFsQnFyY0ZIU2d4empFWkpuRVJUckVEcklrZ0VBRHM9IiAvPjwvc3ZnPg==");
border-color: #474d50
}
.col-move-top {
background-image: url("../ext/resources/images/gray/grid/col-move-top.gif")
}
.col-move-bottom {
background-image: url("../ext/resources/images/gray/grid/col-move-bottom.gif")
}
.x-grid3-row-selected {
background-image: none;
border-color: #474d50;
background-color: #35393b!important
}
.x-grid3-cell-selected {
color: #e8e6e3;
background-color: #353a3c!important
}
.x-grid3-cell-selected span {
color: #e8e6e3!important
}
.x-grid3-cell-selected .x-grid3-cell-text {
color: #e8e6e3
}
.x-grid3-locked .x-grid3-row-selected td.x-grid3-row-marker, .x-grid3-locked td.x-grid3-row-marker {
color: #e8e6e3;
border-top-color: #303436;
background-color: #36351e!important;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMiIgaGVpZ2h0PSIyMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyIiBoZWlnaHQ9IjIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBZ0FXQUljQUFHK2czOWZYMTkzZDNkN2UzdC9mMytEZzRPSGg0ZUxpNHVQajQrVGs1T1hsNWVibTV1Zm41K2pvNk9ucDZlcnE2dXZyNit6czdPM3Q3ZTd1N3UvdjcvRHc4QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQ0FCWUFBQWcwQUFVSUdEQ0FBSUVDQlF3WU9IQUFBWUlFQ1JRb1dMQ0FBWU1HRFJ3NGVQQUFBb1FJRVNSSW1EQ0JBb1VLRlFJRUFBQWdJQUE3IiAvPjwvc3ZnPg==")!important;
border-right-color: #1c477f!important
}
.x-grid3-locked .x-grid3-row-selected td.x-grid3-row-marker div, .x-grid3-locked td.x-grid3-row-marker div {
color: #c8c3bc!important
}
.x-grid3-dirty-cell {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaENnQUtBSWNBQU1BQUFQLy8vd0FBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQU1BQUFFQUxBQUFBQUFLQUFvQUFBZ2RBQUVJRkJpZ1lNR0JBQXdhSEtod1ljS0dCeUZLbkVpeG9zV0pBUUVBT3c9PSIgLz48L3N2Zz4=")
}
.x-grid3-bottombar .x-toolbar {
border-top-color: #30485d
}
.x-props-grid .x-grid3-td-name .x-grid3-cell-inner {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMjQiIGhlaWdodD0iMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyNCIgaGVpZ2h0PSIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhHQUFDQUljQUFORFEwT3ZzN3V6dDcrM3U4Tzd2OGUvdzh2RHg4L0h5OVBuNStRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBWUFBSUFBQWdpQUJFSUhFand3QUVEQ0FzVUlEQmdnSUFBQVFBUW5JakFJRUlEQ2hrNmhBZ2dJQUE3IiAvPjwvc3ZnPg==")!important;
color: #e8e6e3!important
}
.x-props-grid .x-grid3-body .x-grid3-td-name {
border-right-color: #35393b;
background-color: #181a1b!important
}
.xg-hmenu-lock .x-menu-item-icon {
background-image: url("../ext/resources/images/default/grid/hmenu-lock.gif")
}
.xg-hmenu-unlock .x-menu-item-icon {
background-image: url("../ext/resources/images/default/grid/hmenu-unlock.gif")
}
.x-grid3-row-expander {
background-image: url("../ext/resources/images/gray/grid/row-expand-sprite.gif")
}
.x-grid3-hd-checker, .x-grid3-row-checker {
background-image: url(../img/checkboxes-dark.svg)
}
.x-grid3-body .x-grid3-td-numberer {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMjQiIGhlaWdodD0iMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyNCIgaGVpZ2h0PSIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhHQUFDQUljQUFORFEwT3ZzN3V6dDcrM3U4Tzd2OGUvdzh2RHg4L0h5OVBuNStRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBWUFBSUFBQWdpQUJFSUhFand3QUVEQ0FzVUlEQmdnSUFBQVFBUW5JakFJRUlEQ2hrNmhBZ2dJQUE3IiAvPjwvc3ZnPg==")
}
.x-grid3-body .x-grid3-td-numberer .x-grid3-cell-inner {
color: #bdb7af
}
.x-grid3-body .x-grid3-td-row-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMjQiIGhlaWdodD0iMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyNCIgaGVpZ2h0PSIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhHQUFDQUljQUFORFEwT3ZzN3V6dDcrM3U4Tzd2OGUvdzh2RHg4L0h5OVBuNStRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBWUFBSUFBQWdpQUJFSUhFand3QUVEQ0FzVUlEQmdnSUFBQVFBUW5JakFJRUlEQ2hrNmhBZ2dJQUE3IiAvPjwvc3ZnPg==")
}
.x-grid3-check-col {
background-image: url("../ext/resources/images/default/menu/unchecked.gif")
}
.x-grid3-check-col-on {
background-image: url("../ext/resources/images/default/menu/checked.gif")
}
.x-grid-group-hd {
border-bottom-color: #3d4245
}
.x-grid-group-hd div.x-grid-group-title {
color: #aca59a
}
.x-group-by-icon {
background-image: url("../ext/resources/images/default/grid/group-by.gif")
}
.x-show-groups-icon {
background-image: url("../ext/resources/images/default/grid/group-by.gif")
}
.x-grid-empty {
color: #988f81
}
.x-grid-with-col-lines .x-grid3-row td.x-grid3-cell {
border-right-color: #353a3c
}
.x-grid-with-col-lines .x-grid3-row {
border-top-color: #353a3c
}
.x-grid-with-col-lines .x-grid3-row-selected {
border-top-color: #44494c
}
.x-pivotgrid .x-grid3-header-offset table td {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMiIgaGVpZ2h0PSIyMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyIiBoZWlnaHQ9IjIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBZ0FXQUxNQUFPYm01dkx5OHZIeDhlN3U3dW5wNmVycTZ1Zm41K3ZyNit6czdPL3Y3L0R3OE8zdDdjYkd4dWpvNkFBQUFBQUFBQ0g1QkFBQUFBQUFMQUFBQUFBQ0FCWUFBQVFZTU1ncHFsQXFwY0hIV2doeWpFVkpuRVJqckVEck1rd0VBRHM9IiAvPjwvc3ZnPg==");
background-color: initial;
border-left-color: #3d4245;
border-right-color: #3d4245
}
.x-pivotgrid .x-grid3-row-headers {
background-color: #1b1e1f
}
.x-pivotgrid .x-grid3-row-headers table td {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIxIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjEiIGhlaWdodD0iMSIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQVFBQkFJQUFBUC8vL3dBQUFDSDVCQUFBQUFBQUxBQUFBQUFCQUFFQUFBSUNSQUVBT3c9PSIgLz48L3N2Zz4=");
background-color: #222426;
border-left-color: #35393b;
border-right-color: #3d4245;
border-bottom-color: #3d4245
}
.x-dd-drag-ghost {
color: #e8e6e3;
border-color: #3a3e41 #43494c #43494c #3a3e41;
background-color: #181a1b
}
.x-view-selector {
background-color: #2f3335;
border-color: #52585c
}
.x-tree-node-expanded .x-tree-node-icon {
background-image: url("../ext/resources/images/default/tree/folder-open.gif")
}
.x-tree-node-leaf .x-tree-node-icon {
background-image: url("../ext/resources/images/default/tree/leaf.gif")
}
.x-tree-node-collapsed .x-tree-node-icon {
background-image: url("../ext/resources/images/default/tree/folder.gif")
}
.x-tree-node-loading .x-tree-node-icon {
background-image: url("../ext/resources/images/default/tree/loading.gif")!important
}
.x-tree-node .x-tree-node-inline-icon {
background-image: none
}
.x-tree-node-loading a span {
color: #bdb7af
}
.x-tree-no-lines .x-tree-elbow-plus {
background-image: url("../ext/resources/images/default/tree/elbow-plus-nl.gif")
}
.x-tree-no-lines .x-tree-elbow-minus {
background-image: url("../ext/resources/images/default/tree/elbow-minus-nl.gif")
}
.x-tree-no-lines .x-tree-elbow-end-plus {
background-image: url("../ext/resources/images/gray/tree/elbow-end-plus-nl.gif")
}
.x-tree-no-lines .x-tree-elbow-end-minus {
background-image: url("../ext/resources/images/gray/tree/elbow-end-minus-nl.gif")
}
.x-tree-arrows .x-tree-elbow-end-minus, .x-tree-arrows .x-tree-elbow-end-plus, .x-tree-arrows .x-tree-elbow-minus, .x-tree-arrows .x-tree-elbow-plus {
background-image: url("../ext/resources/images/gray/tree/arrows.gif")
}
.x-dd-drag-ghost a, .x-tree-node, .x-tree-node a {
color: #e8e6e3
}
.x-dd-drag-ghost a span, .x-tree-node a span {
text-decoration-color: initial;
color: hsl(36deg 10% 85%)
}
.x-tree-node .x-tree-node-disabled a span {
color: #988f81!important
}
.x-tree-node div.x-tree-drag-insert-below {
border-bottom-color: #24478f
}
.x-tree-node div.x-tree-drag-insert-above {
border-top-color: #24478f
}
.x-tree-dd-underline .x-tree-node div.x-tree-drag-insert-below a {
border-bottom-color: #24478f
}
.x-tree-dd-underline .x-tree-node div.x-tree-drag-insert-above a {
border-top-color: #24478f
}
.x-tree-node .x-tree-drag-append a span {
background-color: #2b2f31;
border-color: #545b5e
}
.x-tree-node .x-tree-node-over {
background-color: #222426
}
.x-tree-node .x-tree-selected {
background-color: #2b2f31
}
.x-tree-drop-ok-append .x-dd-drop-icon {
background-image: url("../ext/resources/images/default/tree/drop-add.gif")
}
.x-tree-drop-ok-above .x-dd-drop-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTYiIGhlaWdodD0iMTYiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEVBQVFBSWNBQURWSlkwWTNLMGc1TEZKQk0xWkVOU0JJb0dkNmxXdCttWFNGbjN5TnBvOStZSnlNYXFHUWJxMmRkN0dnZU5mRllPUFViTy9pZUtpa243MnRncSt2cjcrL3Y1dXB3TUd3aE0vUHo5L2YzLy8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQVA4QUxBQUFBQUFRQUJBQUFBaHNBRFVJSERnUVF3R0NDQWthUEVqUVFrSU5CU0pLcFBCUVlJV0lBak1jZFBqdzRrQ0dEUzFJRUlqaG93YU9BaDBDcUVqd2dnTUdDeFE4ZE9od1FnUUlEd2hvU0lEZ2dJR0VEUVlNRUJCZ0pzdWpKMFZXUkhsU3cwcWtMbUhLVEVoVGcwMmNPbm42QkNxVTZNT0FBRHM9IiAvPjwvc3ZnPg==")
}
.x-tree-drop-ok-below .x-dd-drop-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTYiIGhlaWdodD0iMTYiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEVBQVFBSWNBQURWSlkwWTNLMGc1TEZKQk0xWkVOU0JJb0dkNmxXdCttWFNGbjN5TnBvOStZSnlNYXFHUWJxMmRkN0dnZU5mRllPUFViTy9pZUtpa243MnRncSt2cjcrL3Y1dXB3TUd3aE0vUHo5L2YzLy8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQVA4QUxBQUFBQUFRQUJBQUFBaHNBRFVJRkdqQmdvU0JDRFZZUUxnUVFNS0hHaTQ0WUxCQWdZWUVDQTRZSUtoUXc0UUlFQjRRZ0lpd3dZQUJBZ0pBWEVpeUpVR0RKRmx5ZE9neTRzU0tGek51N0xqd1k4aVJMazJpVklsaFlJR09FQ3NjRmJnMGFZR2xHWTR1bE1uMHFWVUtMVEU4clRsUWE4S0FBRHM9IiAvPjwvc3ZnPg==")
}
.x-tree-drop-ok-between .x-dd-drop-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTYiIGhlaWdodD0iMTYiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEVBQVFBSWNBQURWSlkwWTNLMGc1TEZKQk0xWkVOU0JJb0dkNmxXdCttWFNGbjN5TnBvOStZSnlNYXFHUWJxMmRkN0dnZU5mRllPUFViTy9pZUtpa243MnRncisvdjV1cHdNR3doTS9Qei8vLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUFBQVA4QUxBQUFBQUFRQUJBQUFBaG9BREVJRkZpaGdvU0JDREZVUUxnUVFNS0hHQ3c0WUxCQUFZWUVDQTRZSUtnUXc0UUlFQjRRZ0lpd3dZQUJBZ0lJdk1DUUpBWUtCVndpaEJsejRNS0ZDUXZvM0NuemdzNldKSDI2TEhod0pWQ09EbVZHbkZqeFlzYU5IUmQrRERsU3BrbVVLcFVxRFFnQU93PT0iIC8+PC9zdmc+")
}
.x-date-picker {
border-color: #6f675b;
background-color: #181a1b
}
.x-date-left, .x-date-middle, .x-date-right {
background-image: none;
color: #e8e6e3
}
.x-date-middle .x-btn .x-btn-text {
color: #e8e6e3
}
.x-date-middle .x-btn-mc em.x-btn-arrow {
background-image: url("../ext/resources/images/gray/toolbar/btn-arrow-light.gif")
}
.x-date-right a {
background-image: url("../ext/resources/images/gray/shared/right-btn.gif")
}
.x-date-left a {
background-image: url("../ext/resources/images/gray/shared/left-btn.gif")
}
.x-date-inner th {
background-color: #2e3234;
background-image: none;
border-bottom-color: #474c4f;
color: #b0a99f
}
.x-date-inner td {
border-color: #303436
}
.x-date-inner .x-date-active, .x-date-inner a {
color: #e8e6e3
}
.x-date-inner .x-date-selected a {
background-image: none;
background-color: #2e3234;
border-color: #3a3f41
}
.x-date-inner .x-date-today a {
border-color: #d50000
}
.x-date-inner .x-date-nextday a, .x-date-inner .x-date-prevday a {
color: #b2aca2
}
.x-date-bottom {
border-top-color: #474c4f;
background-image: none;
background-color: #2e3234
}
.x-date-inner .x-date-disabled a:hover, .x-date-inner a:hover {
color: #e8e6e3;
background-color: #2e3234
}
.x-date-inner .x-date-disabled a {
background-color: #222426;
color: #bdb7af
}
.x-date-mmenu {
background-color: #222426!important
}
.x-date-mmenu .x-menu-item {
color: #e8e6e3
}
.x-date-mp {
background-color: #181a1b
}
.x-date-mp-btns button {
background-color: #414749;
color: #e8e6e3;
border-color: #42474a #766e61 #766e61 #42474a;
}
.x-date-mp-btns {
background-image: none;
background-color: #2e3234
}
.x-date-mp-btns td {
border-top-color: #474c4f
}
td.x-date-mp-month a, td.x-date-mp-year a {
color: #c8c3bc
}
td.x-date-mp-month a:hover, td.x-date-mp-year a:hover {
color: #c8c3bc;
background-color: #191b1c
}
td.x-date-mp-sel a {
background-image: none;
background-color: #2e3234;
border-color: #3a3f41
}
.x-date-mp-ybtn a.x-date-mp-prev {
background-image: url(../img/collapse-left.svg);
background-position: unset;
}
.x-date-mp-ybtn a.x-date-mp-next {
background-image: url(../img/collapse-right.svg);
background-position: unset;
}
.x-date-mp-ybtn a.x-date-mp-next:hover, .x-date-mp-ybtn a.x-date-mp-prev:hover {
background-position: unset;
opacity: 0.5;
}
td.x-date-mp-sep {
border-right-color: #3b4043
}
.x-tip .x-tip-close {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTUiIGhlaWdodD0iMTUiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTUiIGhlaWdodD0iMTUiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaER3QVBBSWNBQUdWbFpVRC9RSXVMaTQrUGo1T1RrNWVYbDV5Y25LQ2dvS1NrcEx5OHZMMjl2YjYrdnIrL3Y4REF3TUhCd2NMQ3dzWEZ4Y2ZIeDlIUjBkTFMwdDNkM2VqbzZPL3Y3L0h4OGZQejgvVDA5UFgxOWZiMjl2ZjM5L2o0K1BuNStmcjYrdnY3Ky96OC9QMzkvZjcrL3YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQU1BQUFFQUxBQUFBQUFQQUE4QUFBaXBBQU5NR0Vpd0lNRUFFaWlRV01pd0lRa0tFaHFBK0FBQ1JJaUxHRU5ZZk1BQWhJZUtHVEZXZE5EUkE0Q1RHRThDR01uZ3cwY0JBZ0NJQUFCVFJNVUdEVnhXSERBQUFFOFJOa0U0V0pBaFE0Y09Id2dvbmZpaHd3YVNSWTkrS0VDVnFkTUhSREZ3NEdDZ2ExY1BIamhzYU1BZ2c5WURhRDJnUFJEMnFZSU1GeERJOWREQmcxd0VHalEwSUhxaDZOYWpIYmJtZFFDaEFnaWdJMFk0SkhFaFFvQUVrQ05Mamh3Z0lBQTciIC8+PC9zdmc+")
}
.x-tip .x-tip-bc, .x-tip .x-tip-bl, .x-tip .x-tip-br, .x-tip .x-tip-ml, .x-tip .x-tip-mr, .x-tip .x-tip-tc, .x-tip .x-tip-tl, .x-tip .x-tip-tr {
background-color: hsl(25deg 20% 15%)
}
.x-tip .x-tip-body, .x-tip .x-tip-header-text {
color: #bdb7af
}
.x-form-invalid-tip .x-tip-bc, .x-form-invalid-tip .x-tip-bl, .x-form-invalid-tip .x-tip-br, .x-form-invalid-tip .x-tip-ml, .x-form-invalid-tip .x-tip-mr, .x-form-invalid-tip .x-tip-tc, .x-form-invalid-tip .x-tip-tl, .x-form-invalid-tip .x-tip-tr {
background-image: url("data:image/svg+xml;base64,<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="500" height="824"><defs><filter id="darkreader-image-filter"><feColorMatrix type="matrix" values="0.333 -0.667 -0.667 0.000 1.000 -0.667 0.333 -0.667 0.000 1.000 -0.667 -0.667 0.333 0.000 1.000 0.000 0.000 0.000 1.000 0.000" /></filter></defs><image width="500" height="824" filter="url(#darkreader-image-filter)" xlink:href="data:image/gif;base64,R0lGODlh9AE4A4cAAED/QKExH9RWRthxZt2Lhd3d3e7u7v///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAMAAAAALAAAAAD0ATgDAAj/AAEIBEBAwMCDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEN2FEBAoYAAAUSqXMmypcuXMGPKnEmzpkKUBg+eHHDAps+fQIMKHUq0qNGBBwYEyAlg5wEDR6NKnUq1qtWrHw0kXUowAE8DBbCKHUu2rNmzKwtoVVowwNMCPdHKnUu3rl2qB9QeWHrybdy7gAMLHkwYY16tSwl4fVu4sePHkOvqZdt0MdTImDNr3gx0LVeBTjmLHk26tMatTEGjNM26tevWOBUWfE27tu3GJA+i3M27t+/fwIMLH068uPHjyJMrX868ufPn0KNLn069uvXrvQdo3869u/fv4MOL/x9Pvrz58+jTq1/Pvr379/Djy59Pv779+9wN6N/Pv7///wAGKOCABBZo4IEIJqjgggw26OCDEEYo4YQUVmjhhfwVoOGGHHbo4YcghijiiCSWaOKJKKao4oostujiizDGKOOMNNZo440cYqjjjjz26OOPQAYp5JBEFunfAUgmqeSSTDbp5JNQRinllFRWaeWVWGap5ZZcdunll2CGKeaYZJZp5plopqnmmmy26eabcMYpJ5RG1mnnnXjmqeeefPbZH46ABirooIQWauihiCaq6KIe+unoo5BGKumklGKI36WYZqrpppx26umnoIYqqnfYlWrqqaimquqqrLbq6quw/v82AFhz1mrrrbjmquuuvOqqllJe0drrsMQWa+yxyCZb5q8ozQqXstBGK+201FarJrPBPmvtttx26+23yWLrLLjklmvuueiGKa6w6bbr7rvwgruutvHWa++9+OI6b7789uvvv+oaAOy4ABds8MEIHzYwuwk37PDD5+4L8cQUVyytxBZnrPHGt2LM8ccgh7yswM0yLPLJKKdMpccqt+xyyyy/LPPMG8dM8804N2xzzjz3zO/OPgctdLtAD2300d0WjfTSTCurdNNQR73r01JXbTWcVF+t9dZmZs3112Bz6XXYZJct5dhmp602kmiv7XbYbb8tt9Zxz2131HXfrTfSee//7XfQff8tOM6BD274y4UfrjjKiS/u+MeNPy65xZFPbvnDlV+u+cGZb+65v51/Lvq9oY9u+ruln656xCRnu/rrFKcO++zbyk777Re3TjDuvPdre+/AE/t78MT7qrvJxSdv7vDKN4/18fQ6Lz23zE9v/ZnVX6+9mNlv732X3X8vPpbhj2/+lOWfr76T6a/vfpLtv+9+/PKrT3/95t+Pv/j67+99//7THgADaL0BElB6Bjxg8xKowOQxsIHEeyAEgSfBCfKugha8HQYzOLsNcvB1Hvyg6kIoQtORsISiOyEKPafCFWquhS60HAxjKLkZ0tBxNryh4nKoQ8PxsIeC+yEQ//0mxCHqrYhGtBsSkyi3JTLRbU58otqiKEWzUbGKZLsiFsGmxS1yrYtepBv0whhAMJKxamY8I97GqMb6pbGNTHsjHPnGxjmuT452HBoe8wi4OvJxfHv8I88CKUjC+bGQ2yMkImemyEUi7pCOnF4jI6mySVKScZC8pPIsqcmQcbKTkMskKIP3yVFqrJSmpJwoU4k7VLJyYq58JeZWKUvYxbKWCbslLjlHy12eTpe+BBgwgwm6XhLzc8M8Zr6SqUzSGbOZl2MmNOMlzWmi7pnWfFw1s5mubXKTdQuL3jdfiM1x+rCc5gwiOtNJxHWy84jufKcS4ynPJtKznlC8Jz6nqP/PfVqxn/7MIkADysWBEvSLBj2oGMOp0MN5s6FOSyhEpfbQiR6rohYtFkYzOqyNcpRXHv2o8Rgq0nmStKT2PClK86nSlfKzpS79J0xjKtCZ0rSgNr0pQnOq04WWTJw93elPg1q2kBKVTUY96rUkqlSZJbWp2GMqVGEm1amm7KlWHRNWsxownnLVaFv9qpfCKlaxVbWsHCMrWrOk1rVeqa1urRJc44q+s9I1dna9K8Tmqtcn8bWvTforYJck2MHCL6+G5aVXE1tJxDJWmI59bDEXK1mRFTaxlzVsZge7WcB2tq+f1Wto7zpaupY2rqd1a2rXulq0trasrxVrbL86W67/1jart7Vqbqe6W6j2tqm/VWpwjzpcohY3qMftaXJ1utybNpemz41pdF063ZVWF6XXLWl2Rbrdj3aXo9/NaHgtOt6Jlhei521oehW63oO2l6DvDWh8/TnffdYXn/etZ37lud939ped/01ngM054HEW+JsH5maCs7lgazZ4mg+GZoSbOWFlVviYFyZmhoO5YV92eJcfxmWIazliWZb4lSdmZYpTuWJTtniULwZljDs5Y03W+JI3pmSOI7ljR/Z4kT9GZJALOWRBFvmPR+ZjkvO4ZDs2eY5PhmOU2zhlNVb5jFcmY5bDuGUvdnmLX8ZimKs4ZimW+YlnZmKak7hmI7Z5/4hvBmKcezhnHdb5hnemYZ5juGcX9nmFf0ZhoEs4aBEW+oOH5mCiM7hoCzZ6go+GYKQbOGkFVvqAlyZgpssY2cous9OediZlQ51WUJOamqY+9TVHrWpVsrrVeH01rPea6lmDc6i2Ptmm/bfr/fUaf792Y61zTa5gy8/Y70P2/IZN7G8p+47MbnbSoi3t2lG72tV6tv2uje1paft8384ft7sdrXADctzkjqis0+07dLP7ou5+t0bjLe+O0rveIL03vkeK633rTN/+7hjAA14rc/Nv4ASXk8G/t/D/ITzhz1s3xLv58Im3qeGJrLjF14RxAWp842nq+PVEXsCPgzyqEv8/ubxMrnIykVySLG8592IuczC9HIE0r/lYc65zs6a859nmOdDZKvShv7XoRpcr0pNe158zXd39fvqtXSd1dN3ceVdf4NKrzr6tc51JWd+k17+upLA7cOxkZxva02724rU9gmsn+9tJGfevz52Cdef63Xu39wvmvep9b+XfpR54DQ7+6YWnXeI7eHimL96WjU/640EYeaNPfnWXH2Hlh575X24e6J034ed7HvrRlT6Fo9f56ZGZ+pqvnoWtl/nrNzd7cjo97b2qfTRj33Ldy5D3Kvf95IRfQ+CfnPjaND7IkY9D5W+c+YuD/g6db3HpO5T6E7f+OW+P+6lhH+LaH1z/+NXJ/e7navx/Q387y29+gbO//QX/fsLVvzf6w/P98Fe4/Alu/7v136RRl3/etn8B939zY4ApFYACWG4E6G8I+DYPyFIKuIBQR3UUmDv4d4FI1YD7FoFr44EvNYEaaCwgmDYlKFMiOILCw4H4doJFxYL15oI1lYIqmHswKG8yCDc3+G45iFM0WIPel4FA2DU7yG49+DVHKFQWOITzJoRMqFVFmG5JuDVT6FNL+IQ26IRYaHNRSG5VeDVfaDVhiEZd2G1jSFFliG1nuEZauIU714Zu6HM/GIdxsoZQY4dNg4dxlIbVpodL44d0BId0SHSCOIhHV4iGqHSImIhNN4eM/8hxfChtgHg0kwhWkdhslahHl0hsmSg0ndhHi/iIUPKJPkOKPWOKg7SJuYaKOcOKhhSKoth1sBiLYKeKtuaKN4OLNKOLjGSLs8aLTuWLsAaMjzSLtFh2wthqxOgyy0hVxniMaveM0NiMjSWNx0iNV5WMqoaNmGSNtMiNuqaNpwaOliWOpEaOnmSOoYaOIMOOoeSNseiOpQaPoiiPNaOOnmaPp4SPlaWPGeOPruaI0Ohy/ChZAFkxBxlrAjmQM0ePj5iQsFSQjwWRtOaQjEiRs2SRiYiRDsOR/6aRhuiRuSSRjCWSCGOSirWQDMmFIDmIKGkwL1kwMQlZLUmHM/kvN/85WSq5km+4kzwph1f4kyjnk0JJiERZlId4lEipiEq5lI0YlE7ZVU0ZlaNIkphllZqFlZyllZ7FlaDllaIFlqQllqZFlqhllqqFlqyllq7FlrDllrIFl7Qll7ZFl7hll7qFl7yll77Fl8Dll8IFmMQlmMZFmMhlmMqFmMylmM7FmNDlmNIFmdQlmdZFmdhlmdqFmdylmd7FmeDlmeIFmuQlmuZFmuhlmuqFmuylmu7FmvDlmvIFm/Qlm/ZFm/hlm/qFm/ylm/7FmwDmmwIGnAQmnAZGnAhmnAqGnAymnA7GnBDmnBIGnRQmnRZGnRhmnRqGnRymnR7GnSDmnSIGniT/Jp4mRp4oZp4qhp4spp4uxp4w5p4yBp80Jp82Rp84Zp86hp88pp8+xp9A5p9CBqBEJqBGRqBIZqBKhqBMpqBOxqBQ5qBSBqFUJqFWRqFYZqFahqFcpqFexqFg5qFiBqJkJqJmRqJoZqJqhqJspqJuxqJw5qJyBqN0JqN2RqN4ZqN6hqN8pqN+xqOA5qOCBqSEJqSGRqSIZqSKhqSMpqSOxqSQ5qSSBqWUJqWWRqWYZqWahqWcVpNxmJPtxqVu6KU/o6W8Rqa+ZqbAhqbCBqZbKKafxqZY6Kb4IqeiNpVUKYt2eqe1CKdPSKf24qf1AqioxqdMKKjwYqirlqd6ioyENDqEiOouj0o0anpsk5pslbpsjQqEkUpxmVqDm2p1lwptnaqCnzp1u7OoX1KqyxOq26YUAQEAOw==" /></svg>")
}
.x-form-invalid-tip .x-tip-body {
background-image: url("../ext/resources/images/default/form/exclamation.gif")
}
.x-tip-anchor {
background-image: url("../ext/resources/images/gray/qtip/tip-anchor-sprite.gif")
}
.x-menu {
background-color: #202325
}
.x-menu-floating {
border-color: hsl(200 6% 20% / 1);
border-width: 2px;
border-radius: 6px;
box-shadow: 5px 5px 10px rgba(0, 0, 0, 0.5);
}
.x-menu-nosep {
background-image: none
}
.x-menu-item-arrow {
background-image: url("../ext/resources/images/gray/menu/menu-parent.gif")
}
.x-menu-sep {
background-color: #2a2d2f;
border-bottom-color: #303436
}
a.x-menu-item {
text-decoration-color: initial;
color: #d3cfc9
}
.x-menu-item-active {
background: unset;
border: unset;
margin: unset;
padding: 1px;
background-color: #2f3537;
border-color: #474d50;
/* border: 1px solid red; */
}
.x-menu-item-active a.x-menu-item {
border: unset;
margin: unset;
border-color: #474d50
}
.x-menu-check-item .x-menu-item-icon, .x-menu-item-checked .x-menu-item-icon {
background-image: url(../img/checkboxes-dark.svg)
}
.x-menu-item-checked .x-menu-group-item .x-menu-item-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTYiIGhlaWdodD0iMTYiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEVBQVFBTlVpQURrNU9UMDlQVFUxTlZCUVVEYzNOM0J3Y0RBd01FQkFRRU5EUTJSa1pFOVBUenM3T3pvNk9qWTJOajQrUGxkWFZ5NHVManc4UEMwdExTOHZMMDVPVG1ob2FFbEpTV1ZsWldCZ1lHRmhZVjlmWHl3c0xEZzRPR0ppWWtSRVJISnlja1ZGUldscGFRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDSDVCQUVBQUNJQUxBQUFBQUFRQUJBQUFBWkVRSkZ3U0N3YWo4aWtja2tzQkFDaDVXZWdRREFTeWNMZ1FVRUVCTmlqZzJvNUxBZ1RKQURrT1R3RkVHUmxFWWdBR29aTThrTGdDQXdhU3gwU0d4aE1oNGlKaWtFQU93PT0iIC8+PC9zdmc+")
}
.x-menu-group-item .x-menu-item-icon {
background-image: none
}
.x-menu-plain {
background-color: #181a1b!important
}
.x-menu .x-date-picker {
border-color: #474c4f
}
.x-cycle-menu .x-menu-item-checked {
background-color: #202324;
border-color: #44494c!important
}
.x-menu-scroller-top {
background-image: url("../ext/resources/images/default/layout/mini-top.gif")
}
.x-menu-scroller-bottom {
background-image: url("../ext/resources/images/default/layout/mini-bottom.gif")
}
.x-box-tl {
background-image: url("../ext/resources/images/default/box/corners.gif")
}
.x-box-tc {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIzMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjMyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUFnQUljQUFNSEJ3Y2pJeU52YjIrVGs1T3pzN083dTd1L3Y3L0R3OFBIeDhmUHo4L1QwOVBYMTlmYjI5dmYzOS9qNCtQbjUrZnI2K3Z6OC9QMzkvZjcrL3YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQkFDQUFBQWdrQUJrTUNDQ0Jna0VLQlJJV1lBQkFBQUVLRXlSRWdQREFRUU1HQ3hRa1FIREFRSUdBQURzPSIgLz48L3N2Zz4=")
}
.x-box-tr {
background-image: url("../ext/resources/images/default/box/corners.gif")
}
.x-box-ml {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIxIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMSIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBQkFJY0FBTUhCd2R6YzNPenM3UDcrL2dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBQUFBUDhBTEFBQUFBQUVBQUVBQUFnSEFBVUVBREFnSUFBNyIgLz48L3N2Zz4=")
}
.x-box-mc {
background-color: #222426;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIzMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjMyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUFnQUljQUFNSEJ3Y2pJeU52YjIrVGs1T3pzN083dTd1L3Y3L0R3OFBIeDhmUHo4L1QwOVBYMTlmYjI5dmYzOS9qNCtQbjUrZnI2K3Z6OC9QMzkvZjcrL3YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQkFDQUFBQWdrQUJrTUNDQ0Jna0VLQlJJV1lBQkFBQUVLRXlSRWdQREFRUU1HQ3hRa1FIREFRSUdBQURzPSIgLz48L3N2Zz4=");
color: #c4bfb7
}
.x-box-mr {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIxIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMSIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBQkFJY0FBTUhCd2R6YzNPenM3UC8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBQUFBUDhBTEFBQUFBQUVBQUVBQUFnSEFBY0FDQ0FnSUFBNyIgLz48L3N2Zz4=")
}
.x-box-bl {
background-image: url("../ext/resources/images/default/box/corners.gif")
}
.x-box-bc {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIzMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjMyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUFnQUljQUFNSEJ3Y2pJeU52YjIrVGs1T3pzN083dTd1L3Y3L0R3OFBIeDhmUHo4L1QwOVBYMTlmYjI5dmYzOS9qNCtQbjUrZnI2K3Z6OC9QMzkvZjcrL3YvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQkFDQUFBQWdrQUJrTUNDQ0Jna0VLQlJJV1lBQkFBQUVLRXlSRWdQREFRUU1HQ3hRa1FIREFRSUdBQURzPSIgLz48L3N2Zz4=")
}
.x-box-br {
background-image: url("../ext/resources/images/default/box/corners.gif")
}
.x-box-blue .x-box-bl, .x-box-blue .x-box-br, .x-box-blue .x-box-tl, .x-box-blue .x-box-tr {
background-image: url("../ext/resources/images/default/box/corners-blue.gif")
}
.x-box-blue .x-box-bc, .x-box-blue .x-box-mc, .x-box-blue .x-box-tc {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSI0MiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjQyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUFxQUljQUFLTEc5S1RIOUtmSjlhbks5YXZNOWE3TjlyRFA5ckxROXJYUjk3ZlQ5N3JVK0x6VytMN1grTnZiMjhIWitjWGIrY2pkK2N6ZytzL2krdExrK3RibSt0cnArOS9zKytUazVPenM3T1B2L09qeS9QYjI5djM5L1FBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQkFDb0FBQWd3QURkY0FNQkJnMEVORGhJNjJBQ2dBUVlOR1N4VW9FQmhnb1FJRUI0NEFCQkF3QUFDQlF3Y1FKQkF3UUlHRGdJQ0FEcz0iIC8+PC9zdmc+")
}
.x-box-blue .x-box-mc {
background-color: #2b2e30
}
.x-box-blue .x-box-mc h3 {
color: #a0c7e7
}
.x-box-blue .x-box-ml {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIxIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMSIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBQkFJY0FBS0xHOU56YzNPenM3UDcrL2dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBQUFBUDhBTEFBQUFBQUVBQUVBQUFnSEFBVUVBREFnSUFBNyIgLz48L3N2Zz4=")
}
.x-box-blue .x-box-mr {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNCIgaGVpZ2h0PSIxIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjQiIGhlaWdodD0iMSIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoQkFBQkFJY0FBS0xHOU56YzNPenM3UC8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBQUFBUDhBTEFBQUFBQUVBQUVBQUFnSEFBY0FDQ0FnSUFBNyIgLz48L3N2Zz4=")
}
.x-combo-list {
border-color: #3e4446;
background-color: #2b2f31;
box-shadow: 0 0 5px 3px #2c2ab0;
}
.x-combo-list-inner {
background-color: #212121;
}
.x-combo-list-hd {
color: #c8c3bc;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSI5OCI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9Ijk4IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUJpQUljQUFNbmUrc3pmK3MvaCt0SGordFRsKzlmbSs5cm8rOTNxL09Ecy9PUHQvT1h2L09qeC9ldnovZTcxL1FBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ0g1QkFBQUFQOEFMQUFBQUFBQkFHSUFBQWdnQUJzd1dLQWdBWUlEQmdvUUdDQWdBSUNIRUNOS25FaXhvc1dMR0ROU0RBZ0FPdz09IiAvPjwvc3ZnPg==");
border-bottom-color: #43484b
}
.x-resizable-pinned .x-combo-list-inner {
border-bottom-color: #42484b
}
.x-combo-list-item {
border-color: #303436
}
.x-combo-list .x-combo-selected {
background-color: #494949;
border-color: #655e53!important
}
.x-combo-list .x-toolbar {
border-top-color: #43484b
}
.x-panel {
border-color: #3d4245
}
.x-panel-header {
border-color: #3d4245;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIzMDAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMSIgaGVpZ2h0PSIzMDAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEFRQXNBZmNBQU5mWDE5alkyTnJhMnR2YjI5emMzTjdlM3VEZzRPTGk0dVBqNCtYbDVlZm41K2pvNk9ucDZldnI2K3pzN08zdDdlN3U3dkR3OFAvLy93QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFDd0FBQUFBQVFBc0FRQUlRUUFGU0lnQTRZR0RCZ3dXS0VpQUFNRUJBd1VLRUJnZ0lBQ0FpeGd6YXR6SXNhUEhqeUJEaWh4SjBxT0VreWhUcWx6SnNxWExsekJqeXB4SnM2Wk1BUUVCQURzPSIgLz48L3N2Zz4=")
}
.x-panel-body {
border-color: #3d4245;
background-color: transparent;
}
.x-panel-bbar .x-toolbar, .x-panel-tbar .x-toolbar {
border-color: #3d4245
}
.x-panel-body-noheader, .x-panel-mc .x-panel-body, .x-panel-mc .x-panel-tbar .x-toolbar, .x-panel-tbar-noheader .x-toolbar {
border-top-color: #3d4245
}
.x-panel-tl .x-panel-header {
color: #c8c3bc
}
.x-panel-tc {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIzMDAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMSIgaGVpZ2h0PSIzMDAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEFRQXNBWWNBQU03T3p0ZlgxOWpZMk5yYTJ0dmIyOXpjM04zZDNkN2UzdURnNE9IaDRlTGk0dVBqNCtYbDVlYm01dWZuNStqbzZPbnA2ZXZyNit6czdPM3Q3ZTd1N3ZEdzhQSHg4ZlgxOWYvLy8vLy8vd29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0NpSDVCQUFBQVA4QUxBQUFBQUFCQUN3QkFBaEVBQWRncUVCaGdvUUlFQjQ0WUxCZ2dRSUVCdzRVSURCQVFJQ0xHRE5xM01peG84ZVBJRU9LSEVuU280V1RLRk9xWE1teXBjdVhNR1BLbkVtenBzc0xPRE1NQ0FnQU93PT0iIC8+PC9zdmc+")
}
.x-panel-bl, .x-panel-br, .x-panel-tl, .x-panel-tr {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTIiIGhlaWdodD0iMzAwIj48ZGVmcz48ZmlsdGVyIGlkPSJkYXJrcmVhZGVyLWltYWdlLWZpbHRlciI+PGZlQ29sb3JNYXRyaXggdHlwZT0ibWF0cml4IiB2YWx1ZXM9IjAuMzMzIC0wLjY2NyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IDAuMzMzIC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgLTAuNjY3IDAuMzMzIDAuMDAwIDEuMDAwIDAuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDAuMDAwIiAvPjwvZmlsdGVyPjwvZGVmcz48aW1hZ2Ugd2lkdGg9IjEyIiBoZWlnaHQ9IjMwMCIgZmlsdGVyPSJ1cmwoI2RhcmtyZWFkZXItaW1hZ2UtZmlsdGVyKSIgeGxpbms6aHJlZj0iZGF0YTppbWFnZS9naWY7YmFzZTY0LFIwbEdPRGxoREFBc0FZY0FBRXIvU3RmWDE5alkyTnJhMnR2YjI5emMzTjdlM3VEZzRPSGg0ZUxpNHVQajQrVGs1T1hsNWVibTV1Zm41K2pvNk9ucDZlcnE2dXZyNit6czdPM3Q3ZTd1N3UvdjcvRHc4UEh4OGZMeTh2UHo4L1gxOWZiMjl2ZjM5L2o0K1ByNit2djcrLy8vL3dBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUNINUJBRUFBQUFBTEFBQUFBQU1BQ3dCQUFqL0FBRU1HRWl3b01BQklSSXFURWp3dzRXSEVCOStHT2loZ3NXTEZqME03RUNobzhlT0hRWnltRUN5SkVrT0F6ZElXTWx5NVlhQkdpREluQ2xUdzhBTUQzTHF6SmxoSUFZSFFJTUN4VERRQW9PalNJOWFHRWhCZ2RPblRpa3doUXBWNm9BSkNiSnF6VHBoWUlRRFlNT0NqVER3Z1lHemFNOCtLSnMyN2RvQkRRckluU3Uzd1VBR0JQTHF6Y3RnNElLQ0JmOE9TQ0Nnc09IQ0NRWWlDTUM0TVdNRWloMDdoanhnc2VUSGtTOEhvR3o1TW1mTm16TjdGaTM1czJiVG95dURSbDJhOUdUWGpWbS9WbjBhTm1iYXFUdTN4cjFiOTJ6ZnNXMkg1djE3dFhEWndZa25CMzZiK1hEbnlKc2JWeTY5TnZYbjA2RWYzMzQ5T25icjJydHovdzlQUHJ0NThPZHpwKys5dmpqNjkrcmhzNWZ2UHI3OStmZnI0OSt2di8veTl2L1JGMkIrQS9KWG9IL1ZFWmlnZ1FzaStKMkNEeklZb1lQZVZUZ2VnQTBlcUdHR0hFNjRvWWNkV2lqZWlPVUpHT0tGSm9Lb29vZ2xRc2dpaHNPQmdNR01OTTRJd2tBeTFrampqUVBrcUNNR1BQcW9ZNUEvMm9oamtVQWVXU1NSU3lyNUk1TlBPam1rbERWQ09XV1BTRnBaSlpVN2Nta2tsazJDR2FXWVZ3cTVKWmxubXRrbG1tdXErYVdiU2JMNVpwWmV4Z21ubG0zU0thZWRldDVaSjU1emh1bm5ub0R5S1dpZmlCNnE2SmlETnBvb280K1dHV21haythNXFLU1hVcHFwcFpCdUdtaW5vR0lhcXFhamNpcnFxYVNpYW1xcXJLN3E2cWVxd2xmYXFxeXZHbG9xcmJqYUdxdXVzL0phYTZIQS9pa3NvY002NnFtdnVRWkw3TExHM29yc3M4bzJ1MnUwbFNaYmJMWFFYbnNzdGR0cTZ5eTMzM283TFk0YmxHdHV1VUdlZTI2NjZxSkwwRUlMRFhRUVlBUUJFQkFBT3c9PSIgLz48L3N2Zz4=");
border-bottom-color: #3d4245
}
.x-panel-bc {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSIzMDAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4zMzMgLTAuNjY3IC0wLjY2NyAwLjAwMCAxLjAwMCAtMC42NjcgMC4zMzMgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAtMC42NjcgMC4zMzMgMC4wMDAgMS4wMDAgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMSIgaGVpZ2h0PSIzMDAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvZ2lmO2Jhc2U2NCxSMGxHT0RsaEFRQXNBWWNBQU03T3p0ZlgxOWpZMk5yYTJ0dmIyOXpjM04zZDNkN2UzdURnNE9IaDRlTGk0dVBqNCtYbDVlYm01dWZuNStqbzZPbnA2ZXZyNit6czdPM3Q3ZTd1N3ZEdzhQSHg4ZlgxOWYvLy8vLy8vd29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0NpSDVCQUFBQVA4QUxBQUFBQUFCQUN3QkFBaEVBQWRncUVCaGdvUUlFQjQ0WUxCZ2dRSUVCdzRVSURCQVFJQ0xHRE5xM01peG84ZVBJRU9LSEVuU280V1RLRk9xWE1teXBjdVhNR1BLbkVtenBzc0xPRE1NQ0FnQU93PT0iIC8+PC9zdmc+")
}
.x-panel-mc {
background-color: #202324
}
.x-panel-ml {
background-color: #181a1b;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTIiIGhlaWdodD0iMSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxMiIgaGVpZ2h0PSIxIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhEQUFCQUljQUFOcmEydkh4OGYvLy93b0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDaUg1QkFBQUFQOEFMQUFBQUFBTUFBRUFBQWdNQUFFSUNFQ3dJRUVCQUFJQ0FEcz0iIC8+PC9zdmc+")
}
.x-panel-mr {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTIiIGhlaWdodD0iMSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxMiIgaGVpZ2h0PSIxIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhEQUFCQUljQUFOcmEydkh4OGYvLy93b0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDZ29LQ2dvS0Nnb0tDaUg1QkFBQUFQOEFMQUFBQUFBTUFBRUFBQWdNQUFFSUNFQ3dJRUVCQUFJQ0FEcz0iIC8+PC9zdmc+")
}
.x-tool {
background-image: url('../img/tool-sprites-dark.gif')
}
.x-panel-ghost {
background-color: #1f2223
}
.x-panel-dd-spacer, .x-panel-ghost ul {
border-color: #3d4245
}
.x-window-proxy {
background-color: #1a1c1d;
border-color: #3d4245
}
.x-window-tl .x-window-header {
color: #b2aca2
}
.x-window-mc {
border-color: #3d4245;
background-color: #25282a
}
.x-window-ml, .x-window-mr {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTIiIGhlaWdodD0iNSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxMiIgaGVpZ2h0PSI1IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL3BuZztiYXNlNjQsaVZCT1J3MEtHZ29BQUFBTlNVaEVVZ0FBQUF3QUFBQUZDQU1BQUFCR3BQMGRBQUFBR1hSRldIUlRiMlowZDJGeVpRQkJaRzlpWlNCSmJXRm5aVkpsWVdSNWNjbGxQQUFBQUFsUVRGUkY5UFQwNit2cnU3dTdFeG1vSEFBQUFCVkpSRUZVZU5waVlHSmtnQUpHSmdZeU9BQUJCZ0FFRUFBZldSTWVEZ0FBQUFCSlJVNUVya0pnZ2c9PSIgLz48L3N2Zz4=")
}
.x-window-maximized .x-window-tc {
background-color: #181a1b
}
.x-window-bbar .x-toolbar {
border-top-color: #3d4245
}
.x-panel-collapsed .x-window-tl, .x-panel-ghost .x-window-tl {
border-bottom-color: #3d4245
}
.x-dlg-mask {
background-color: #35393b
}
.x-window-plain .x-window-mc {
background-color: #25282a
}
.x-html-editor-wrap {
border-color: #43484b;
background-color: #181a1b
}
.x-html-editor-tb .x-btn-text {
background-image: url("../ext/resources/images/default/editor/tb-sprite.gif")
}
.x-panel-noborder .x-panel-header-noborder, .x-panel-noborder .x-panel-tbar-noborder .x-toolbar {
border-bottom-color: #3d4245
}
.x-panel-noborder .x-panel-bbar-noborder .x-toolbar, .x-tab-panel-bbar-noborder .x-toolbar {
border-top-color: #3d4245
}
.x-tab-panel-tbar-noborder .x-toolbar {
border-bottom-color: #3d4245
}
.x-accordion-hd {
color: #d3cfc9;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMSIgaGVpZ2h0PSI0NiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxIiBoZWlnaHQ9IjQ2IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBUUF1QUljQUFBQUFBQUVCQVFJQ0FnTURBd1FFQkFVRkJRWUdCZ2NIQndnSUNBa0pDUW9LQ2dzTEN3d01EQTBORFE0T0RnOFBEeEFRRUJFUkVSSVNFaE1URXhRVUZCVVZGUllXRmhjWEZ4Z1lHQmtaR1JvYUdoc2JHeHdjSEIwZEhSNGVIaDhmSHlBZ0lDRWhJU0lpSWlNakl5UWtKQ1VsSlNZbUppY25KeWdvS0NrcEtTb3FLaXNyS3l3c0xDMHRMUzR1TGk4dkx6QXdNREV4TVRJeU1qTXpNelEwTkRVMU5UWTJOamMzTnpnNE9EazVPVG82T2pzN096dzhQRDA5UFQ0K1BqOC9QMEJBUUVGQlFVSkNRa05EUTBSRVJFVkZSVVpHUmtkSFIwaElTRWxKU1VwS1NrdExTMHhNVEUxTlRVNU9UazlQVDFCUVVGRlJVVkpTVWxOVFUxUlVWRlZWVlZaV1ZsZFhWMWhZV0ZsWldWcGFXbHRiVzF4Y1hGMWRYVjVlWGw5ZlgyQmdZR0ZoWVdKaVltTmpZMlJrWkdWbFpXWm1abWRuWjJob2FHbHBhV3BxYW10cmEyeHNiRzF0Ylc1dWJtOXZiM0J3Y0hGeGNYSnljbk56YzNSMGRIVjFkWFoyZG5kM2QzaDRlSGw1ZVhwNmVudDdlM3g4ZkgxOWZYNStmbjkvZjRDQWdJR0JnWUtDZ29PRGc0U0VoSVdGaFlhR2hvZUhoNGlJaUltSmlZcUtpb3VMaTR5TWpJMk5qWTZPam8rUGo1Q1FrSkdSa1pLU2twT1RrNVNVbEpXVmxaYVdscGVYbDVpWW1KbVptWnFhbXB1Ym01eWNuSjJkblo2ZW5wK2ZuNkNnb0tHaG9hS2lvcU9qbzZTa3BLV2xwYWFtcHFlbnA2aW9xS21wcWFxcXFxdXJxNnlzcksydHJhNnVycSt2cjdDd3NMR3hzYkt5c3JPenM3UzB0TFcxdGJhMnRyZTN0N2k0dUxtNXVicTZ1cnU3dTd5OHZMMjl2YjYrdnIrL3Y4REF3TUhCd2NMQ3dzUER3OFRFeE1YRnhjYkd4c2ZIeDhqSXlNbkp5Y3JLeXN2THk4ek16TTNOemM3T3pzL1B6OURRME5IUjBkTFMwdFBUMDlUVTFOWFYxZGJXMXRmWDE5alkyTm5aMmRyYTJ0dmIyOXpjM04zZDNkN2UzdC9mMytEZzRPSGg0ZUxpNHVQajQrVGs1T1hsNWVibTV1Zm41K2pvNk9ucDZlcnE2dXZyNit6czdPM3Q3ZTd1N3UvdjcvRHc4UEh4OGZMeTh2UHo4L1QwOVBYMTlmYjI5dmYzOS9qNCtQbjUrZnI2K3Z2NysvejgvUDM5L2Y3Ky92Ly8veUg1QkFBQUFQOEFMQUFBQUFBQkFDNEFBQWdZQVBYcHkzZlBIcjE1OGQ2MVkxZXVvY09IRUNOS2xCZ1FBRHM9IiAvPjwvc3ZnPg==")
}
.x-layout-collapsed {
background-color: #2a2e2f;
border-color: #3d4245
}
.x-layout-collapsed-over {
background-color: #26292a
}
.x-layout-split-west .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-left.gif")
}
.x-layout-split-east .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-right.gif")
}
.x-layout-split-north .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-top.gif")
}
.x-layout-split-south .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-bottom.gif")
}
.x-layout-cmini-west .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-right.gif")
}
.x-layout-cmini-east .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-left.gif")
}
.x-layout-cmini-north .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-bottom.gif")
}
.x-layout-cmini-south .x-layout-mini {
background-image: url("../ext/resources/images/default/layout/mini-top.gif")
}
.x-progress-wrap {
border-color: #50575a
}
.x-progress-text-back {
color: #aca59a
}
.x-list-header {
background-color: #1b1e1f;
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMiIgaGVpZ2h0PSIyMiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIyIiBoZWlnaHQ9IjIyIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhBZ0FXQUxNQUFPYm01dkx5OHZIeDhlN3U3dW5wNmVycTZ1Zm41K3ZyNit6czdPL3Y3L0R3OE8zdDdjYkd4dWpvNkFBQUFBQUFBQ0g1QkFBQUFBQUFMQUFBQUFBQ0FCWUFBQVFZTU1ncHFsQXFwY0hIV2doeWpFVkpuRVJqckVEck1rd0VBRHM9IiAvPjwvc3ZnPg==")
}
.x-list-header-inner div em {
border-left-color: #3a3e41
}
.x-list-over {
background-color: #222426
}
.x-list-selected {
background-color: #202325
}
.x-list-resizer {
border-left-color: #70685c;
border-right-color: #70685c
}
.x-list-header-inner em.sort-asc, .x-list-header-inner em.sort-desc {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTIwMCIgaGVpZ2h0PSI0NiI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjMzMyAtMC42NjcgLTAuNjY3IDAuMDAwIDEuMDAwIC0wLjY2NyAwLjMzMyAtMC42NjcgMC4wMDAgMS4wMDAgLTAuNjY3IC0wLjY2NyAwLjMzMyAwLjAwMCAxLjAwMCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSIxMjAwIiBoZWlnaHQ9IjQ2IiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL2dpZjtiYXNlNjQsUjBsR09EbGhzQVF1QUxNQUFOcmEydWJtNXQzZDNlTGk0dVhsNWQvZjM5dmIyOTdlM3ZuNStlRGc0T0hoNGVQajQ3eTh2T1RrNU56YzNJbUppU0gvQzFoTlVDQkVZWFJoV0UxUVBEOTRjR0ZqYTJWMElHSmxaMmx1UFNMdnU3OGlJR2xrUFNKWE5VMHdUWEJEWldocFNIcHlaVk42VGxSamVtdGpPV1FpUHo0Z1BIZzZlRzF3YldWMFlTQjRiV3h1Y3pwNFBTSmhaRzlpWlRwdWN6cHRaWFJoTHlJZ2VEcDRiWEIwYXowaVFXUnZZbVVnV0UxUUlFTnZjbVVnTlM0d0xXTXdOakFnTmpFdU1UTTBOemMzTENBeU1ERXdMekF5THpFeUxURTNPak15T2pBd0lDQWdJQ0FnSUNBaVBpQThjbVJtT2xKRVJpQjRiV3h1Y3pweVpHWTlJbWgwZEhBNkx5OTNkM2N1ZHpNdWIzSm5MekU1T1Rrdk1ESXZNakl0Y21SbUxYTjViblJoZUMxdWN5TWlQaUE4Y21SbU9rUmxjMk55YVhCMGFXOXVJSEprWmpwaFltOTFkRDBpSWlCNGJXeHVjenA0YlhCTlRUMGlhSFIwY0RvdkwyNXpMbUZrYjJKbExtTnZiUzk0WVhBdk1TNHdMMjF0THlJZ2VHMXNibk02YzNSU1pXWTlJbWgwZEhBNkx5OXVjeTVoWkc5aVpTNWpiMjB2ZUdGd0x6RXVNQzl6Vkhsd1pTOVNaWE52ZFhKalpWSmxaaU1pSUhodGJHNXpPbmh0Y0QwaWFIUjBjRG92TDI1ekxtRmtiMkpsTG1OdmJTOTRZWEF2TVM0d0x5SWdlRzF3VFUwNlQzSnBaMmx1WVd4RWIyTjFiV1Z1ZEVsRVBTSjRiWEF1Wkdsa09rRXdOalExTXpBMU1qTXlNRFk0TVRGQ1FUQkZPRFJFTTBZME1rUkVOVFpESWlCNGJYQk5UVHBFYjJOMWJXVnVkRWxFUFNKNGJYQXVaR2xrT2tVeU5UZzNRa0U1UkVaRFJERXhSRVpDUWtZeVFUaERNVEU0TURaQ1FqWTBJaUI0YlhCTlRUcEpibk4wWVc1alpVbEVQU0o0YlhBdWFXbGtPa1V5TlRnM1FrRTRSRVpEUkRFeFJFWkNRa1l5UVRoRE1URTRNRFpDUWpZMElpQjRiWEE2UTNKbFlYUnZjbFJ2YjJ3OUlrRmtiMkpsSUZCb2IzUnZjMmh2Y0NCRFV6VWdUV0ZqYVc1MGIzTm9JajRnUEhodGNFMU5Pa1JsY21sMlpXUkdjbTl0SUhOMFVtVm1PbWx1YzNSaGJtTmxTVVE5SW5odGNDNXBhV1E2UVRFMk5EVXpNRFV5TXpJd05qZ3hNVUpCTUVVNE5FUXpSalF5UkVRMU5rTWlJSE4wVW1WbU9tUnZZM1Z0Wlc1MFNVUTlJbmh0Y0M1a2FXUTZRVEEyTkRVek1EVXlNekl3TmpneE1VSkJNRVU0TkVRelJqUXlSRVExTmtNaUx6NGdQQzl5WkdZNlJHVnpZM0pwY0hScGIyNCtJRHd2Y21SbU9sSkVSajRnUEM5NE9uaHRjRzFsZEdFK0lEdy9lSEJoWTJ0bGRDQmxibVE5SW5JaVB6NEIvLzc5L1B2NitmajM5dlgwOC9MeDhPL3U3ZXpyNnVubzUrYmw1T1BpNGVEZjN0M2MyOXJaMk5mVzFkVFQwdEhRejg3TnpNdkt5Y2pIeHNYRXc4TEJ3TCsrdmJ5N3VybTR0N2ExdExPeXNiQ3ZycTJzcTZxcHFLZW1wYVNqb3FHZ241NmRuSnVhbVppWGxwV1VrNUtSa0krT2pZeUxpb21JaDRhRmhJT0NnWUIvZm4xOGUzcDVlSGQyZFhSemNuRndiMjV0Ykd0cWFXaG5abVZrWTJKaFlGOWVYVnhiV2xsWVYxWlZWRk5TVVZCUFRrMU1TMHBKU0VkR1JVUkRRa0ZBUHo0OVBEczZPVGczTmpVME16SXhNQzh1TFN3cktpa29KeVlsSkNNaUlTQWZIaDBjR3hvWkdCY1dGUlFURWhFUUR3NE5EQXNLQ1FnSEJnVUVBd0lCQUFBaCtRUUFBQUFBQUN3QUFBQUFzQVF1QUFBRS94REpTYXU5T092TnUvOWdLSTVrYVo1b3FxNXM2NzV3TE05MGJkOTRydTk4Ny85QVZHQklMQnFQeUtSeXlXdzZuOUNvZEVxdFdxL1lySGJMN1hxLzRMQjRiSHlReitpMGVzMXV1OS93dUh4T3I5dnYrTHgreisvN3NRK0JmNE9FaFlhSGlJbUtpNHlOam8rUWtaSnJnWldUbDVpWm1wdWNhQVNmb0tHaW82U2xwcWVvcWFxcnJLMnVyN0N4c3JPMHRiYTN1TG02dTd5OXZyK2ZsY0xBeE1YR3g4akp5c3ZNemM3UDBOSFMwOVRWMXRmWTJkcmIzTjNlMytEaDR1UGt6UTNuNk9ucTYrenQ3dS93OGZMejlQWDI5L2o1K3Z2OC9mNy9BQU1LSEVpd29NR0RDQk1xWE1pd29jT0hFQ05LbkVpeFlyOEZHRE5xM01peG84ZVBJUDlEaWh4SnNxVEpreWhUcWx6SnNxWExsekJqeXB4SnM2Yk5temh6NnR6SnM2ZlBuMENEQ2gxS3RLaFJsd09TS2wzS3RLblRwMUNqU3AxS3RhclZxMWl6YXQzS3RhdlhyMkREaWgxTHRxelpzMmpUcWwzTHRxM2J0M0RqeXAxTHQ2N2R1M2p6NnQzTHQ2L2Z2NEFEQ3g1TXVMRGh3NGdUSzE3Y1Y0SGp4NUFqUzU1TXViTGx5NWd6YTk3TXViUG56NkJEaXg1TnVyVHAwNmhUcTE3TnVyWHIxN0JqeTU1TnU3YnQyN2h6Njk3Tm0zU0MzOENEQ3g5T3ZMang0OGlUSzEvT3ZMbno1OUNqUzU5T3ZicjE2OWl6YTkvT3ZidjM3K0REaXg5UHZyejU4K2pUcTEvUHZuMzFBdkRqeTU5UHY3NzkrL2p6NjkvUHY3Ly8vd0FHS09EL2dBUVdhT0NCQ0NhbzRJSU1OdWpnZ3hCR0tPR0VGRlpvNFlVWVpxamhoaHgyNk9HSElJWW80b2drbG1qaWlTaW02T0FCTExibzRvc3d4aWpqakRUV2FPT05PT2FvNDQ0ODl1ampqMEFHS2VTUVJCWnA1SkZJSnFua2trdzI2ZVNUVUVZcDVaUlVWbW5sbFZobXFlV1dYSGJwNVpkZ2hpbm1tR1NXYWFRQWFLYXA1cHBzdHVubW0zREdLZWVjZE5acDU1MTQ1cW5ubm56MjZlZWZnQVlxNktDRUZtcm9vWWdtcXVpaWpEYnE2S09RUmlycHBKUldhdW1sbUdhcTZhYWNkdXJwcDZDR0t1cW9wSlpxNnFtb3Bxb3FwdzYwNnVxcnNNWXE2NnkwMW1ycnJiam1xdXV1dlBicTY2L0FCaXZzc01RV2EreXh5Q2FyN0xMTU5pdXIvd0hRUml2dHROUldhKzIxMkdhcjdiYmNkdXZ0dCtDR0srNjQ1SlpyN3Jub3BxdnV1dXkyNis2NzhNWXI3N3owMW12dnZmam1xKysrL1Bicjc3OEFCeXp3d0FRWGJQREJDQ2VzTGdBTU4rend3eEJITFBIRUZGZHM4Y1VZWjZ6eHhoeDM3UEhISUljczhzZ2tsMnp5eVNpbnJQTEtMTGZzOHNzd3h5enp6RFRYYlBQTk9PZXM4ODQ4OSt6enowQUhMZlRRUkJkdDlORklKNjMwMGt3MzdmVFRVRWN0OWRSVVYyMzExVmhucmZYV1hIZnROY29NaEMzMjJHU1hiZmJaYUtldDl0cHN0KzMyMjNESExmZmNkTmR0OTkxNDU2MzMzbnozN2ZmZmdBY3UrT0NFRjI3NDRZZ25ydmppakRmdStPTjNCeUg1NUpSWGJ2bmxtR2V1K2YvbW5IZnUrZWVnaHk3NjZLUzcwTW5wcUtldSt1cVhDR01KNjdESEx2dnN0TmR1KysyNDU2NjdISzd2N3Z2dndBY3YvUERFRjIvODhWUzhqdnp5ekRmdnZCWGxSQy85OU5SWGIvMzFzVHlBL2ZiY2QrLzk5K0NITC83NDVKZHYvdm5vcDYvKyt1eTNYNDVGOE1jdi8vejAxMi8vL2ZqbnIvLysvUGZ2Ly84QURLQUFCM0tVQWhyd2dBaE1vQUlYeU1BR092Q0JFSXlnQkNkSXdRcGE4SUkwWVl3R044akJEbnJ3Z3lBTW9RaEhTTUlTbXZDRUtFeWhDbGZJd2hhNjhJVXdqS0VNWjBoREYvYm1oampNb1E1M3lNTWUrdkNIUUF5aUVJZEl4Q0lhOFloSVRLSnEzTVBFSmpyeGlWQ01vaFNuU01VcVd2R0tXTXlpRnJmSXhTNzRlbkU3S2dxakdNZEl4akthOFl4b1RLTWExOGpHTnJyeGpYQ01veHpuU01jNjJ2R09lSVNQbWZiSXh6NzY4WStBREtRZ0IwbklRaHJ5a0loTXBDSVh5Y2hHT3ZLUmtJd2tKRmRGeVVwYThwS1l6S1FtTjhuSlRucnlrNkFNcFNoSFNjcFNtdktVcUV5bEtsZkp5bGE2RXBYT2lxVXNaMG5MV3RyeWxyak1wUzUzeWN0ZUFrdGh3QXltTUlkSnpHSWE4NWpJVEtZeWw4bk1aanJ6bWRDTXBqU25TYzFxV3JPYVg4dW1OcmZKelc1Njg1dmdES2M0eDBuT2NwcnpuT2hNcHpyWHljNTJ1dk9kOEl5blBPZEp6M3JhODU3NHpLYyt3UWE1ZnZyem53QU5xRUFIU3RDQ0d2U2dDRTJvUWhmSzBJWTY5S0Y4aXdBQU93PT0iIC8+PC9zdmc+");
border-color: #3d4245
}
.x-slider {
filter: invert(100%) contrast(90%)
}
.x-slider-horz, .x-slider-horz .x-slider-end, .x-slider-horz .x-slider-inner {
background-image: url("../ext/resources/images/default/slider/slider-bg.png")
}
.x-slider-horz .x-slider-thumb {
background-image: url("../ext/resources/images/gray/slider/slider-thumb.png")
}
.x-slider-vert, .x-slider-vert .x-slider-end, .x-slider-vert .x-slider-inner {
background-image: url("../ext/resources/images/default/slider/slider-v-bg.png")
}
.x-slider-vert .x-slider-thumb {
background-image: url("../ext/resources/images/gray/slider/slider-v-thumb.png")
}
.x-window-dlg .x-msg-box-wait {
background-image: url("../ext/resources/images/default/grid/loading.gif")
}
.x-window-dlg .ext-mb-info {
background-image: url("../ext/resources/images/gray/window/icon-info.gif")
}
.x-window-dlg .ext-mb-warning {
background-image: url("../ext/resources/images/gray/window/icon-warning.gif")
}
.x-window-dlg .ext-mb-question {
background-image: url("../img/question-circle.svg");
background-size: 32px;
}
.x-window-dlg .ext-mb-error {
background-image: url("../ext/resources/images/gray/window/icon-error.gif")
}
.sm-text-highlight {
background-color: #684006
}
.sm-menuitem-filter-label {
background-color: #46515d;
color: #d0ccc6!important
}
.sm-menuitem-filter-icon {
background-image: url("../img/bars-filter-d9.svg");
background-size: 12px
}
.sm-grid3-col-filterable .x-grid3-hd-btn, .sm-grid3-col-filterable .x-grid3-hd-btn:hover {
background-image: url("../img/bars-filter-d9.svg");
background-position: 2px 3px;
opacity: 0.5;
}
.sm-grid3-col-filtered .x-grid3-hd-btn {
background-color: hsl(107 57% 24% / 1);
opacity: 1;
}
.x-grid3-hd-btn {
background-color: transparent;
background-image: none
}
.sm-collection-manage-layout .x-border-layout-ct, .sm-collection-manage-layout .x-panel-body, .sm-dialog-window.sm-round-panel {
background-color: hsl(200deg 6% 11%)
}
.sm-collection-manage-layout .x-layout-split {
color: #b0a99f;
background-color: transparent
}
.x-form-search:focus, .x-form-text:focus, .x-form-textarea:focus {
border-color: #945619;
box-shadow: rgba(166,96,28,.2) 0 0 1px 1px inset
}
.sm-review-auto-sprite {
background-color: #2952a3;
color: #e6e4e1!important
}
.x-form-cb-label .sm-question-circle,
.x-form-item-label .sm-question-circle,
.x-grid3-hd .sm-question-circle,
.x-panel-header .sm-question-circle {
color: grey
}
.x-form-field-wrap.x-form-field-trigger-wrap .x-form-field.sm-review-combo-input[disabled] {
color: gray;
background-color: transparent
}
.x-progress-inner {
background-image: none;
background-color: #1f2223
}
.x-progress-bar {
background-image: none;
background-color: #425722;
border-color: initial
}
.sm-pb-error .x-progress-bar {
background-color: #602020
}
.x-progress-text {
color: transparent
}
.x-progress-text.x-progress-text-back {
color: #b3aca2
}
.sm-cell-thermometer-bg {
background-color: #1e2021;
outline: solid 1px #4d4d4d;
}
.sm-cell-mercury-low {
background-color: #425722
}
.sm-cell-mercury-medium {
background-color: hsl(209deg 48% 26%)
}
.sm-cell-mercury-high {
background-color: hsl(5deg 56% 21%)
}
.sm-dialog-panel-content, .sm-dialog-panel-text {
color: #e8e6e3
}
.sm-dialog-panel-callout {
background-color: #26292b;
color: #e8e6e3
}
.sm-export-sprite-high, .sm-export-sprite-medium {
background-color: #2b2f31
}
.sm-export-sprite-low {
background-color: #425722
}
.x-grid-group-collapsed .x-grid-group-hd div.x-grid-group-title {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2Uvc3ZnK3htbDtiYXNlNjQsUEQ5NGJXd2dkbVZ5YzJsdmJqMGlNUzR3SWlCbGJtTnZaR2x1WnowaVZWUkdMVGdpSUhOMFlXNWtZV3h2Ym1VOUltNXZJajgrQ2p4emRtY0tJQ0FnZUcxc2JuTTZaR005SW1oMGRIQTZMeTl3ZFhKc0xtOXlaeTlrWXk5bGJHVnRaVzUwY3k4eExqRXZJZ29nSUNCNGJXeHVjenBqWXowaWFIUjBjRG92TDJOeVpXRjBhWFpsWTI5dGJXOXVjeTV2Y21jdmJuTWpJZ29nSUNCNGJXeHVjenB5WkdZOUltaDBkSEE2THk5M2QzY3Vkek11YjNKbkx6RTVPVGt2TURJdk1qSXRjbVJtTFhONWJuUmhlQzF1Y3lNaUNpQWdJSGh0Ykc1ek9uTjJaejBpYUhSMGNEb3ZMM2QzZHk1M015NXZjbWN2TWpBd01DOXpkbWNpQ2lBZ0lIaHRiRzV6UFNKb2RIUndPaTh2ZDNkM0xuY3pMbTl5Wnk4eU1EQXdMM04yWnlJS0lDQWdlRzFzYm5NNmMyOWthWEJ2WkdrOUltaDBkSEE2THk5emIyUnBjRzlrYVM1emIzVnlZMlZtYjNKblpTNXVaWFF2UkZSRUwzTnZaR2x3YjJScExUQXVaSFJrSWdvZ0lDQjRiV3h1Y3pwcGJtdHpZMkZ3WlQwaWFIUjBjRG92TDNkM2R5NXBibXR6WTJGd1pTNXZjbWN2Ym1GdFpYTndZV05sY3k5cGJtdHpZMkZ3WlNJS0lDQWdkMmxrZEdnOUlqRXdJZ29nSUNCb1pXbG5hSFE5SWpFd0lnb2dJQ0IyYVdWM1FtOTRQU0l3SURBZ01pNDJORFU0TXpNeUlESXVOalExT0RNek5DSUtJQ0FnZG1WeWMybHZiajBpTVM0eElnb2dJQ0JwWkQwaWMzWm5PRFUySWdvZ0lDQnBibXR6WTJGd1pUcDJaWEp6YVc5dVBTSXhMakF1TVNBb01TNHdMakVyY2pjektTSUtJQ0FnYzI5a2FYQnZaR2s2Wkc5amJtRnRaVDBpZEhKbFpTMWxiR0p2ZHkxamJHOXpaV1F1YzNabklqNEtJQ0E4WkdWbWN3b2dJQ0FnSUdsa1BTSmtaV1p6T0RVd0lpQXZQZ29nSUR4emIyUnBjRzlrYVRwdVlXMWxaSFpwWlhjS0lDQWdJQ0JwWkQwaVltRnpaU0lLSUNBZ0lDQndZV2RsWTI5c2IzSTlJaU5tWm1abVptWWlDaUFnSUNBZ1ltOXlaR1Z5WTI5c2IzSTlJaU0yTmpZMk5qWWlDaUFnSUNBZ1ltOXlaR1Z5YjNCaFkybDBlVDBpTVM0d0lnb2dJQ0FnSUdsdWEzTmpZWEJsT25CaFoyVnZjR0ZqYVhSNVBTSXdMakFpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZjR0ZuWlhOb1lXUnZkejBpTWlJS0lDQWdJQ0JwYm10elkyRndaVHA2YjI5dFBTSTBOUzR5TlRRNE16UWlDaUFnSUNBZ2FXNXJjMk5oY0dVNlkzZzlJakV1TVRRM01UVXlOaUlLSUNBZ0lDQnBibXR6WTJGd1pUcGplVDBpTkM0Mk5qYzBNakUzSWdvZ0lDQWdJR2x1YTNOallYQmxPbVJ2WTNWdFpXNTBMWFZ1YVhSelBTSndlQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcGpkWEp5Wlc1MExXeGhlV1Z5UFNKc1lYbGxjakVpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZaRzlqZFcxbGJuUXRjbTkwWVhScGIyNDlJakFpQ2lBZ0lDQWdjMmh2ZDJkeWFXUTlJbVpoYkhObElnb2dJQ0FnSUhWdWFYUnpQU0p3ZUNJS0lDQWdJQ0JwYm10elkyRndaVHAzYVc1a2IzY3RkMmxrZEdnOUlqRTFNVFlpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZkMmx1Wkc5M0xXaGxhV2RvZEQwaU1UQXhOU0lLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGVEMGlNQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGVUMGlNQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGJXRjRhVzFwZW1Wa1BTSXdJaUF2UGdvZ0lEeHRaWFJoWkdGMFlRb2dJQ0FnSUdsa1BTSnRaWFJoWkdGMFlUZzFNeUkrQ2lBZ0lDQThjbVJtT2xKRVJqNEtJQ0FnSUNBZ1BHTmpPbGR2Y21zS0lDQWdJQ0FnSUNBZ2NtUm1PbUZpYjNWMFBTSWlQZ29nSUNBZ0lDQWdJRHhrWXpwbWIzSnRZWFErYVcxaFoyVXZjM1puSzNodGJEd3ZaR002Wm05eWJXRjBQZ29nSUNBZ0lDQWdJRHhrWXpwMGVYQmxDaUFnSUNBZ0lDQWdJQ0FnY21SbU9uSmxjMjkxY21ObFBTSm9kSFJ3T2k4dmNIVnliQzV2Y21jdlpHTXZaR050YVhSNWNHVXZVM1JwYkd4SmJXRm5aU0lnTHo0S0lDQWdJQ0FnSUNBOFpHTTZkR2wwYkdVK1BDOWtZenAwYVhSc1pUNEtJQ0FnSUNBZ1BDOWpZenBYYjNKclBnb2dJQ0FnUEM5eVpHWTZVa1JHUGdvZ0lEd3ZiV1YwWVdSaGRHRStDaUFnUEdjS0lDQWdJQ0JwYm10elkyRndaVHBzWVdKbGJEMGlUR0Y1WlhJZ01TSUtJQ0FnSUNCcGJtdHpZMkZ3WlRwbmNtOTFjRzF2WkdVOUlteGhlV1Z5SWdvZ0lDQWdJR2xrUFNKc1lYbGxjakVpUGdvZ0lDQWdQSEJoZEdnS0lDQWdJQ0FnSUhOMGVXeGxQU0ptYVd4c09pTTFPRFU0TlRnN1ptbHNiQzF2Y0dGamFYUjVPakU3YzNSeWIydGxPaU0xT0RVNE5UZzdjM1J5YjJ0bExYZHBaSFJvT2pBdU1qUTJOak00Y0hnN2MzUnliMnRsTFd4cGJtVmpZWEE2WW5WMGREdHpkSEp2YTJVdGJHbHVaV3B2YVc0NmJXbDBaWEk3YzNSeWIydGxMVzl3WVdOcGRIazZNU0lLSUNBZ0lDQWdJR1E5SWswZ01DNDFOekE0TlRFMU15d3lMak0xTkRRNU9UVWdWaUF3TGpJM09USXpOVFUwSUV3Z01TNDVPRGt6T0RJekxERXVNamN6TVRFeU1pQmFJZ29nSUNBZ0lDQWdhV1E5SW5CaGRHZ3hORGs1SWlBdlBnb2dJRHd2Wno0S1BDOXpkbWMrQ2c9PSIgLz48L3N2Zz4=")
}
.x-grid-group-hd div.x-grid-group-title {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2Uvc3ZnK3htbDtiYXNlNjQsUEQ5NGJXd2dkbVZ5YzJsdmJqMGlNUzR3SWlCbGJtTnZaR2x1WnowaVZWUkdMVGdpSUhOMFlXNWtZV3h2Ym1VOUltNXZJajgrQ2p4emRtY0tJQ0FnZUcxc2JuTTZaR005SW1oMGRIQTZMeTl3ZFhKc0xtOXlaeTlrWXk5bGJHVnRaVzUwY3k4eExqRXZJZ29nSUNCNGJXeHVjenBqWXowaWFIUjBjRG92TDJOeVpXRjBhWFpsWTI5dGJXOXVjeTV2Y21jdmJuTWpJZ29nSUNCNGJXeHVjenB5WkdZOUltaDBkSEE2THk5M2QzY3Vkek11YjNKbkx6RTVPVGt2TURJdk1qSXRjbVJtTFhONWJuUmhlQzF1Y3lNaUNpQWdJSGh0Ykc1ek9uTjJaejBpYUhSMGNEb3ZMM2QzZHk1M015NXZjbWN2TWpBd01DOXpkbWNpQ2lBZ0lIaHRiRzV6UFNKb2RIUndPaTh2ZDNkM0xuY3pMbTl5Wnk4eU1EQXdMM04yWnlJS0lDQWdlRzFzYm5NNmMyOWthWEJ2WkdrOUltaDBkSEE2THk5emIyUnBjRzlrYVM1emIzVnlZMlZtYjNKblpTNXVaWFF2UkZSRUwzTnZaR2x3YjJScExUQXVaSFJrSWdvZ0lDQjRiV3h1Y3pwcGJtdHpZMkZ3WlQwaWFIUjBjRG92TDNkM2R5NXBibXR6WTJGd1pTNXZjbWN2Ym1GdFpYTndZV05sY3k5cGJtdHpZMkZ3WlNJS0lDQWdkMmxrZEdnOUlqRXdJZ29nSUNCb1pXbG5hSFE5SWpFd0lnb2dJQ0IyYVdWM1FtOTRQU0l3SURBZ01pNDJORFU0TXpNeUlESXVOalExT0RNek5DSUtJQ0FnZG1WeWMybHZiajBpTVM0eElnb2dJQ0JwWkQwaWMzWm5PRFUySWdvZ0lDQnBibXR6WTJGd1pUcDJaWEp6YVc5dVBTSXhMakF1TVNBb01TNHdMakVyY2pjektTSUtJQ0FnYzI5a2FYQnZaR2s2Wkc5amJtRnRaVDBpZEhKbFpTMWxiR0p2ZHkxdGFXNTFjeTV6ZG1jaVBnb2dJRHhrWldaekNpQWdJQ0FnYVdROUltUmxabk00TlRBaUlDOCtDaUFnUEhOdlpHbHdiMlJwT201aGJXVmtkbWxsZHdvZ0lDQWdJR2xrUFNKaVlYTmxJZ29nSUNBZ0lIQmhaMlZqYjJ4dmNqMGlJMlptWm1abVppSUtJQ0FnSUNCaWIzSmtaWEpqYjJ4dmNqMGlJelkyTmpZMk5pSUtJQ0FnSUNCaWIzSmtaWEp2Y0dGamFYUjVQU0l4TGpBaUNpQWdJQ0FnYVc1cmMyTmhjR1U2Y0dGblpXOXdZV05wZEhrOUlqQXVNQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcHdZV2RsYzJoaFpHOTNQU0l5SWdvZ0lDQWdJR2x1YTNOallYQmxPbnB2YjIwOUlqRTFMamd6T1RFNU1pSUtJQ0FnSUNCcGJtdHpZMkZ3WlRwamVEMGlNalF1T0RBNU56WXhJZ29nSUNBZ0lHbHVhM05qWVhCbE9tTjVQU0l5TUM0ek1Ua3dNeklpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZaRzlqZFcxbGJuUXRkVzVwZEhNOUluQjRJZ29nSUNBZ0lHbHVhM05qWVhCbE9tTjFjbkpsYm5RdGJHRjVaWEk5SW14aGVXVnlNU0lLSUNBZ0lDQnBibXR6WTJGd1pUcGtiMk4xYldWdWRDMXliM1JoZEdsdmJqMGlNQ0lLSUNBZ0lDQnphRzkzWjNKcFpEMGlabUZzYzJVaUNpQWdJQ0FnZFc1cGRITTlJbkI0SWdvZ0lDQWdJR2x1YTNOallYQmxPbmRwYm1SdmR5MTNhV1IwYUQwaU1UVXhOaUlLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGFHVnBaMmgwUFNJeE1ERTFJZ29nSUNBZ0lHbHVhM05qWVhCbE9uZHBibVJ2ZHkxNFBTSXdJZ29nSUNBZ0lHbHVhM05qWVhCbE9uZHBibVJ2ZHkxNVBTSXdJZ29nSUNBZ0lHbHVhM05qWVhCbE9uZHBibVJ2ZHkxdFlYaHBiV2w2WldROUlqQWlJQzgrQ2lBZ1BHMWxkR0ZrWVhSaENpQWdJQ0FnYVdROUltMWxkR0ZrWVhSaE9EVXpJajRLSUNBZ0lEeHlaR1k2VWtSR1Bnb2dJQ0FnSUNBOFkyTTZWMjl5YXdvZ0lDQWdJQ0FnSUNCeVpHWTZZV0p2ZFhROUlpSStDaUFnSUNBZ0lDQWdQR1JqT21admNtMWhkRDVwYldGblpTOXpkbWNyZUcxc1BDOWtZenBtYjNKdFlYUStDaUFnSUNBZ0lDQWdQR1JqT25SNWNHVUtJQ0FnSUNBZ0lDQWdJQ0J5WkdZNmNtVnpiM1Z5WTJVOUltaDBkSEE2THk5d2RYSnNMbTl5Wnk5a1l5OWtZMjFwZEhsd1pTOVRkR2xzYkVsdFlXZGxJaUF2UGdvZ0lDQWdJQ0FnSUR4a1l6cDBhWFJzWlQ0OEwyUmpPblJwZEd4bFBnb2dJQ0FnSUNBOEwyTmpPbGR2Y21zK0NpQWdJQ0E4TDNKa1pqcFNSRVkrQ2lBZ1BDOXRaWFJoWkdGMFlUNEtJQ0E4WndvZ0lDQWdJR2x1YTNOallYQmxPbXhoWW1Wc1BTSk1ZWGxsY2lBeElnb2dJQ0FnSUdsdWEzTmpZWEJsT21keWIzVndiVzlrWlQwaWJHRjVaWElpQ2lBZ0lDQWdhV1E5SW14aGVXVnlNU0krQ2lBZ0lDQThjR0YwYUFvZ0lDQWdJQ0FnYzNSNWJHVTlJbVpwYkd3Nkl6VTROVGcxT0R0bWFXeHNMVzl3WVdOcGRIazZNVHR6ZEhKdmEyVTZJelU0TlRnMU9EdHpkSEp2YTJVdGQybGtkR2c2TUM0eU5EWTJNemh3ZUR0emRISnZhMlV0YkdsdVpXTmhjRHBpZFhSME8zTjBjbTlyWlMxc2FXNWxhbTlwYmpwdGFYUmxjanR6ZEhKdmEyVXRiM0JoWTJsMGVUb3hJZ29nSUNBZ0lDQWdaRDBpVFNBd0xqSTROak0zT1RrNExEQXVOamd6TWpjNE16UWdTQ0F5TGpNMk1UWTBNemtnVENBeExqTTJOemMyTnpNc01pNHhNREU0TURreElGb2lDaUFnSUNBZ0lDQnBaRDBpY0dGMGFERTBPVGtpSUM4K0NpQWdQQzluUGdvOEwzTjJaejRLIiAvPjwvc3ZnPg==")
}
.x-grid3-row-collapsed .x-grid3-row-expander {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2Uvc3ZnK3htbDtiYXNlNjQsUEQ5NGJXd2dkbVZ5YzJsdmJqMGlNUzR3SWlCbGJtTnZaR2x1WnowaVZWUkdMVGdpSUhOMFlXNWtZV3h2Ym1VOUltNXZJajgrQ2p4emRtY0tJQ0FnZUcxc2JuTTZaR005SW1oMGRIQTZMeTl3ZFhKc0xtOXlaeTlrWXk5bGJHVnRaVzUwY3k4eExqRXZJZ29nSUNCNGJXeHVjenBqWXowaWFIUjBjRG92TDJOeVpXRjBhWFpsWTI5dGJXOXVjeTV2Y21jdmJuTWpJZ29nSUNCNGJXeHVjenB5WkdZOUltaDBkSEE2THk5M2QzY3Vkek11YjNKbkx6RTVPVGt2TURJdk1qSXRjbVJtTFhONWJuUmhlQzF1Y3lNaUNpQWdJSGh0Ykc1ek9uTjJaejBpYUhSMGNEb3ZMM2QzZHk1M015NXZjbWN2TWpBd01DOXpkbWNpQ2lBZ0lIaHRiRzV6UFNKb2RIUndPaTh2ZDNkM0xuY3pMbTl5Wnk4eU1EQXdMM04yWnlJS0lDQWdlRzFzYm5NNmMyOWthWEJ2WkdrOUltaDBkSEE2THk5emIyUnBjRzlrYVM1emIzVnlZMlZtYjNKblpTNXVaWFF2UkZSRUwzTnZaR2x3YjJScExUQXVaSFJrSWdvZ0lDQjRiV3h1Y3pwcGJtdHpZMkZ3WlQwaWFIUjBjRG92TDNkM2R5NXBibXR6WTJGd1pTNXZjbWN2Ym1GdFpYTndZV05sY3k5cGJtdHpZMkZ3WlNJS0lDQWdkMmxrZEdnOUlqRXdJZ29nSUNCb1pXbG5hSFE5SWpFd0lnb2dJQ0IyYVdWM1FtOTRQU0l3SURBZ01pNDJORFU0TXpNeUlESXVOalExT0RNek5DSUtJQ0FnZG1WeWMybHZiajBpTVM0eElnb2dJQ0JwWkQwaWMzWm5PRFUySWdvZ0lDQnBibXR6WTJGd1pUcDJaWEp6YVc5dVBTSXhMakF1TVNBb01TNHdMakVyY2pjektTSUtJQ0FnYzI5a2FYQnZaR2s2Wkc5amJtRnRaVDBpZEhKbFpTMWxiR0p2ZHkxamJHOXpaV1F1YzNabklqNEtJQ0E4WkdWbWN3b2dJQ0FnSUdsa1BTSmtaV1p6T0RVd0lpQXZQZ29nSUR4emIyUnBjRzlrYVRwdVlXMWxaSFpwWlhjS0lDQWdJQ0JwWkQwaVltRnpaU0lLSUNBZ0lDQndZV2RsWTI5c2IzSTlJaU5tWm1abVptWWlDaUFnSUNBZ1ltOXlaR1Z5WTI5c2IzSTlJaU0yTmpZMk5qWWlDaUFnSUNBZ1ltOXlaR1Z5YjNCaFkybDBlVDBpTVM0d0lnb2dJQ0FnSUdsdWEzTmpZWEJsT25CaFoyVnZjR0ZqYVhSNVBTSXdMakFpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZjR0ZuWlhOb1lXUnZkejBpTWlJS0lDQWdJQ0JwYm10elkyRndaVHA2YjI5dFBTSTBOUzR5TlRRNE16UWlDaUFnSUNBZ2FXNXJjMk5oY0dVNlkzZzlJakV1TVRRM01UVXlOaUlLSUNBZ0lDQnBibXR6WTJGd1pUcGplVDBpTkM0Mk5qYzBNakUzSWdvZ0lDQWdJR2x1YTNOallYQmxPbVJ2WTNWdFpXNTBMWFZ1YVhSelBTSndlQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcGpkWEp5Wlc1MExXeGhlV1Z5UFNKc1lYbGxjakVpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZaRzlqZFcxbGJuUXRjbTkwWVhScGIyNDlJakFpQ2lBZ0lDQWdjMmh2ZDJkeWFXUTlJbVpoYkhObElnb2dJQ0FnSUhWdWFYUnpQU0p3ZUNJS0lDQWdJQ0JwYm10elkyRndaVHAzYVc1a2IzY3RkMmxrZEdnOUlqRTFNVFlpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZkMmx1Wkc5M0xXaGxhV2RvZEQwaU1UQXhOU0lLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGVEMGlNQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGVUMGlNQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGJXRjRhVzFwZW1Wa1BTSXdJaUF2UGdvZ0lEeHRaWFJoWkdGMFlRb2dJQ0FnSUdsa1BTSnRaWFJoWkdGMFlUZzFNeUkrQ2lBZ0lDQThjbVJtT2xKRVJqNEtJQ0FnSUNBZ1BHTmpPbGR2Y21zS0lDQWdJQ0FnSUNBZ2NtUm1PbUZpYjNWMFBTSWlQZ29nSUNBZ0lDQWdJRHhrWXpwbWIzSnRZWFErYVcxaFoyVXZjM1puSzNodGJEd3ZaR002Wm05eWJXRjBQZ29nSUNBZ0lDQWdJRHhrWXpwMGVYQmxDaUFnSUNBZ0lDQWdJQ0FnY21SbU9uSmxjMjkxY21ObFBTSm9kSFJ3T2k4dmNIVnliQzV2Y21jdlpHTXZaR050YVhSNWNHVXZVM1JwYkd4SmJXRm5aU0lnTHo0S0lDQWdJQ0FnSUNBOFpHTTZkR2wwYkdVK1BDOWtZenAwYVhSc1pUNEtJQ0FnSUNBZ1BDOWpZenBYYjNKclBnb2dJQ0FnUEM5eVpHWTZVa1JHUGdvZ0lEd3ZiV1YwWVdSaGRHRStDaUFnUEdjS0lDQWdJQ0JwYm10elkyRndaVHBzWVdKbGJEMGlUR0Y1WlhJZ01TSUtJQ0FnSUNCcGJtdHpZMkZ3WlRwbmNtOTFjRzF2WkdVOUlteGhlV1Z5SWdvZ0lDQWdJR2xrUFNKc1lYbGxjakVpUGdvZ0lDQWdQSEJoZEdnS0lDQWdJQ0FnSUhOMGVXeGxQU0ptYVd4c09pTTFPRFU0TlRnN1ptbHNiQzF2Y0dGamFYUjVPakU3YzNSeWIydGxPaU0xT0RVNE5UZzdjM1J5YjJ0bExYZHBaSFJvT2pBdU1qUTJOak00Y0hnN2MzUnliMnRsTFd4cGJtVmpZWEE2WW5WMGREdHpkSEp2YTJVdGJHbHVaV3B2YVc0NmJXbDBaWEk3YzNSeWIydGxMVzl3WVdOcGRIazZNU0lLSUNBZ0lDQWdJR1E5SWswZ01DNDFOekE0TlRFMU15d3lMak0xTkRRNU9UVWdWaUF3TGpJM09USXpOVFUwSUV3Z01TNDVPRGt6T0RJekxERXVNamN6TVRFeU1pQmFJZ29nSUNBZ0lDQWdhV1E5SW5CaGRHZ3hORGs1SWlBdlBnb2dJRHd2Wno0S1BDOXpkbWMrQ2c9PSIgLz48L3N2Zz4=")
}
.x-grid3-row-expanded .x-grid3-row-expander {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAiIGhlaWdodD0iMTAiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTAiIGhlaWdodD0iMTAiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2Uvc3ZnK3htbDtiYXNlNjQsUEQ5NGJXd2dkbVZ5YzJsdmJqMGlNUzR3SWlCbGJtTnZaR2x1WnowaVZWUkdMVGdpSUhOMFlXNWtZV3h2Ym1VOUltNXZJajgrQ2p4emRtY0tJQ0FnZUcxc2JuTTZaR005SW1oMGRIQTZMeTl3ZFhKc0xtOXlaeTlrWXk5bGJHVnRaVzUwY3k4eExqRXZJZ29nSUNCNGJXeHVjenBqWXowaWFIUjBjRG92TDJOeVpXRjBhWFpsWTI5dGJXOXVjeTV2Y21jdmJuTWpJZ29nSUNCNGJXeHVjenB5WkdZOUltaDBkSEE2THk5M2QzY3Vkek11YjNKbkx6RTVPVGt2TURJdk1qSXRjbVJtTFhONWJuUmhlQzF1Y3lNaUNpQWdJSGh0Ykc1ek9uTjJaejBpYUhSMGNEb3ZMM2QzZHk1M015NXZjbWN2TWpBd01DOXpkbWNpQ2lBZ0lIaHRiRzV6UFNKb2RIUndPaTh2ZDNkM0xuY3pMbTl5Wnk4eU1EQXdMM04yWnlJS0lDQWdlRzFzYm5NNmMyOWthWEJ2WkdrOUltaDBkSEE2THk5emIyUnBjRzlrYVM1emIzVnlZMlZtYjNKblpTNXVaWFF2UkZSRUwzTnZaR2x3YjJScExUQXVaSFJrSWdvZ0lDQjRiV3h1Y3pwcGJtdHpZMkZ3WlQwaWFIUjBjRG92TDNkM2R5NXBibXR6WTJGd1pTNXZjbWN2Ym1GdFpYTndZV05sY3k5cGJtdHpZMkZ3WlNJS0lDQWdkMmxrZEdnOUlqRXdJZ29nSUNCb1pXbG5hSFE5SWpFd0lnb2dJQ0IyYVdWM1FtOTRQU0l3SURBZ01pNDJORFU0TXpNeUlESXVOalExT0RNek5DSUtJQ0FnZG1WeWMybHZiajBpTVM0eElnb2dJQ0JwWkQwaWMzWm5PRFUySWdvZ0lDQnBibXR6WTJGd1pUcDJaWEp6YVc5dVBTSXhMakF1TVNBb01TNHdMakVyY2pjektTSUtJQ0FnYzI5a2FYQnZaR2s2Wkc5amJtRnRaVDBpZEhKbFpTMWxiR0p2ZHkxdGFXNTFjeTV6ZG1jaVBnb2dJRHhrWldaekNpQWdJQ0FnYVdROUltUmxabk00TlRBaUlDOCtDaUFnUEhOdlpHbHdiMlJwT201aGJXVmtkbWxsZHdvZ0lDQWdJR2xrUFNKaVlYTmxJZ29nSUNBZ0lIQmhaMlZqYjJ4dmNqMGlJMlptWm1abVppSUtJQ0FnSUNCaWIzSmtaWEpqYjJ4dmNqMGlJelkyTmpZMk5pSUtJQ0FnSUNCaWIzSmtaWEp2Y0dGamFYUjVQU0l4TGpBaUNpQWdJQ0FnYVc1cmMyTmhjR1U2Y0dGblpXOXdZV05wZEhrOUlqQXVNQ0lLSUNBZ0lDQnBibXR6WTJGd1pUcHdZV2RsYzJoaFpHOTNQU0l5SWdvZ0lDQWdJR2x1YTNOallYQmxPbnB2YjIwOUlqRTFMamd6T1RFNU1pSUtJQ0FnSUNCcGJtdHpZMkZ3WlRwamVEMGlNalF1T0RBNU56WXhJZ29nSUNBZ0lHbHVhM05qWVhCbE9tTjVQU0l5TUM0ek1Ua3dNeklpQ2lBZ0lDQWdhVzVyYzJOaGNHVTZaRzlqZFcxbGJuUXRkVzVwZEhNOUluQjRJZ29nSUNBZ0lHbHVhM05qWVhCbE9tTjFjbkpsYm5RdGJHRjVaWEk5SW14aGVXVnlNU0lLSUNBZ0lDQnBibXR6WTJGd1pUcGtiMk4xYldWdWRDMXliM1JoZEdsdmJqMGlNQ0lLSUNBZ0lDQnphRzkzWjNKcFpEMGlabUZzYzJVaUNpQWdJQ0FnZFc1cGRITTlJbkI0SWdvZ0lDQWdJR2x1YTNOallYQmxPbmRwYm1SdmR5MTNhV1IwYUQwaU1UVXhOaUlLSUNBZ0lDQnBibXR6WTJGd1pUcDNhVzVrYjNjdGFHVnBaMmgwUFNJeE1ERTFJZ29nSUNBZ0lHbHVhM05qWVhCbE9uZHBibVJ2ZHkxNFBTSXdJZ29nSUNBZ0lHbHVhM05qWVhCbE9uZHBibVJ2ZHkxNVBTSXdJZ29nSUNBZ0lHbHVhM05qWVhCbE9uZHBibVJ2ZHkxdFlYaHBiV2w2WldROUlqQWlJQzgrQ2lBZ1BHMWxkR0ZrWVhSaENpQWdJQ0FnYVdROUltMWxkR0ZrWVhSaE9EVXpJajRLSUNBZ0lEeHlaR1k2VWtSR1Bnb2dJQ0FnSUNBOFkyTTZWMjl5YXdvZ0lDQWdJQ0FnSUNCeVpHWTZZV0p2ZFhROUlpSStDaUFnSUNBZ0lDQWdQR1JqT21admNtMWhkRDVwYldGblpTOXpkbWNyZUcxc1BDOWtZenBtYjNKdFlYUStDaUFnSUNBZ0lDQWdQR1JqT25SNWNHVUtJQ0FnSUNBZ0lDQWdJQ0J5WkdZNmNtVnpiM1Z5WTJVOUltaDBkSEE2THk5d2RYSnNMbTl5Wnk5a1l5OWtZMjFwZEhsd1pTOVRkR2xzYkVsdFlXZGxJaUF2UGdvZ0lDQWdJQ0FnSUR4a1l6cDBhWFJzWlQ0OEwyUmpPblJwZEd4bFBnb2dJQ0FnSUNBOEwyTmpPbGR2Y21zK0NpQWdJQ0E4TDNKa1pqcFNSRVkrQ2lBZ1BDOXRaWFJoWkdGMFlUNEtJQ0E4WndvZ0lDQWdJR2x1YTNOallYQmxPbXhoWW1Wc1BTSk1ZWGxsY2lBeElnb2dJQ0FnSUdsdWEzTmpZWEJsT21keWIzVndiVzlrWlQwaWJHRjVaWElpQ2lBZ0lDQWdhV1E5SW14aGVXVnlNU0krQ2lBZ0lDQThjR0YwYUFvZ0lDQWdJQ0FnYzNSNWJHVTlJbVpwYkd3Nkl6VTROVGcxT0R0bWFXeHNMVzl3WVdOcGRIazZNVHR6ZEhKdmEyVTZJelU0TlRnMU9EdHpkSEp2YTJVdGQybGtkR2c2TUM0eU5EWTJNemh3ZUR0emRISnZhMlV0YkdsdVpXTmhjRHBpZFhSME8zTjBjbTlyWlMxc2FXNWxhbTlwYmpwdGFYUmxjanR6ZEhKdmEyVXRiM0JoWTJsMGVUb3hJZ29nSUNBZ0lDQWdaRDBpVFNBd0xqSTROak0zT1RrNExEQXVOamd6TWpjNE16UWdTQ0F5TGpNMk1UWTBNemtnVENBeExqTTJOemMyTnpNc01pNHhNREU0TURreElGb2lDaUFnSUNBZ0lDQnBaRDBpY0dGMGFERTBPVGtpSUM4K0NpQWdQQzluUGdvOEwzTjJaejRLIiAvPjwvc3ZnPg==")
}
.sm-toolbar-legend-box {
border-color: #414749
}
.x-tree-lines .x-tree-elbow, .x-tree-lines .x-tree-elbow-end, .x-tree-lines .x-tree-elbow-line {
background-image: none
}
.sm-drop {
border-color: #43494c;
color: #bdb7af
}
.sm-grid-result-sprite {
background-color: #1e2021;
border-color: #414749
}
.sm-result-pass {
color: hsl(120 84% 42% / 1);
}
.sm-result-fail {
color: hsl(19 100% 40% / 1);
}
.sm-result-na {
color: #767676
}
.sm-result-nr {
color: #c0bab2
}
.sm-grid-sprite {
background-color: #181a1b;
border-color: #414749
}
.sm-content-sprite {
color: #e6e4e1;
background-color: #20407f;
border-color: #414749
}
.sm-navtree-sprite {
background-color: #20407f;
color: #e6e4e1!important
}
.sm-severity-high {
color: hsl(0deg 50% 50%);
background-color: #1e2021
}
.sm-severity-medium {
color: #5c98d6;
background-color: transparent
}
.sm-severity-low {
color: hsl(120deg 54% 46%);
background-color: #1e2021
}
.sm-home-widget-text {
color: hsl(36deg 10% 85%)
}
.sm-home-widget-text a {
color: hsl(36deg 23% 55%)
}
.sm-home-widget-header-1 {
color: #e8e6e3
}
.sm-empty-cell {
color: #bdb7af
}
.sm-bare-button .x-btn-bc, .sm-bare-button .x-btn-bl, .sm-bare-button .x-btn-br, .sm-bare-button .x-btn-mc, .sm-bare-button .x-btn-ml, .sm-bare-button .x-btn-mr, .sm-bare-button .x-btn-tc, .sm-bare-button .x-btn-tl, .sm-bare-button .x-btn-tr {
background-image: none
}
.sm-round-panel .x-window-header {
color: #dddad6;
background-color: #35393b;
background-image: none
}
.x-window-plain .x-window-mc {
border-color: initial
}
.x-window-plain .x-window-body {
border-color: initial;
background-image: initial!important;
background-color: transparent!important
}
.x-window-bc, .x-window-bl, .x-window-br, .x-window-mc, .x-window-ml, .x-window-mr, .x-window-tc, .x-window-tl, .x-window-tr {
background-image: none
}
.sm-review-footer, .sm-review-form {
background-color: #1d1f20
}
.x-panel-header {
color: #dddad6
}
.x-tab-panel-body {
border-color: #3d4245;
background-color: transparent
}
.x-tab-strip .x-tab-strip-active span.x-tab-strip-text {
color: #dddad6
}
.x-tab-strip-top .x-tab-strip-over .x-tab-left, .x-tab-strip-top .x-tab-strip-over .x-tab-right, .x-tab-strip-top .x-tab-strip-over .x-tab-strip-inner {
background-color: #2b2f31
}
.x-tab-strip-top .x-tab-strip-active .x-tab-left, .x-tab-strip-top .x-tab-strip-active .x-tab-right, .x-tab-strip-top .x-tab-strip-active .x-tab-strip-inner {
background-color: hsl(200deg 5% 25%)
}
.x-tab-strip-top .x-tab-left, .x-tab-strip-top .x-tab-right, .x-tab-strip-top .x-tab-strip-inner {
background-image: none;
background-color: #25282a
}
.x-form-search, .x-form-text, textarea.x-form-field {
background-color: #181a1b;
background-image: none;
border-color: hsl(202deg 30% 25%)
}
.x-form-search:read-only, .x-form-text:read-only, textarea.x-form-field:read-only {
/* background-color: transparent; */
border-color: hsl(202 0% 25% / 1);
color: gray;
}
.x-form-text:read-only.x-trigger-noedit {
color: #d9d9d9
}
.sm-home-title {
background-image: url("../img/shield-green-check.svg");
color: #c8c3bc;
filter: saturate(.75)
}
#sm-home-oss-sprite {
color: #e6e4e1;
background-color: #20407f
}
#sm-home-version-sprite {
color: #e6e4e1;
background-color: #457a67
}
ul.x-tab-strip-top {
background-color: transparent;
background-image: none;
border-bottom-color: #3e4446
}
body.x-body-masked .x-window-plain .x-window-mc {
background-color: #1b1e1f
}
td.sort-asc, td.sort-desc, td.x-grid3-hd-menu-open, td.x-grid3-hd-over {
border-left-color: #35393b;
border-right-color: #3d4245
}
.x-grid3-header, td.sort-asc .x-grid3-hd-inner, td.sort-desc .x-grid3-hd-inner, td.x-grid3-hd-menu-open .x-grid3-hd-inner, td.x-grid3-hd-over .x-grid3-hd-inner {
background-color: #202325;
background-image: none
}
.x-toolbar {
border-color: #3d4245;
background-color: #272a2c;
background-image: none
}
.sm-border-layout-ct {
background-color: #1a1c1d
}
.x-border-layout-ct {
background-color: hsl(0 0% 8% / 1);
}
/* .sm-round-panel {
background-color: #276d90;
}
*/
.sm-round-panel .x-panel-header {
background-color: #35393b;
background-image: none
}
.sm-round-inner-panel .x-panel-header {
background-color: hsl(200 5% 17% / 1)
}
.sm-round-panel .sm-home-widget-body {
background-color: #2b2e30
}
.sm-user-list {
background-color: #2b2e30;
}
.sm-home-widget-header {
background-color: #313537
}
.sm-dialog-panel-title, .sm-home-widget-collectionName, .sm-home-widget-subtitle, .sm-home-widget-title {
color: #5c98d6
}
.sm-banner-unclassified {
background-color: #006229;
color: #e8e6e3
}
.sm-banner-cui {
background-color: #40226a;
color: #e8e6e3
}
.sm-banner-confidential {
background-color: #002980;
color: #e8e6e3
}
.sm-banner-secret {
background-color: #a00d25;
color: #e8e6e3
}
.sm-banner-topsecret {
background-color: #b93c00;
color: #e8e6e3
}
.sm-banner-sci {
background-color: #9f9307;
color: #e8e6e3
}
.hbss-control .x-grid3-hd-checker, .hbss-control .x-grid3-row-checker {
background-image: url("../img/hbss-check-sprite.gif")
}
.assignment-grid-item-selected {
background-color: #6c0000
}
.icon-department {
background-image: url("../img/department-16.png")!important;
background-color: initial!important
}
.icon-refresh {
background-image: url("../img/reload.svg");
background-color: initial
}
.icon-add {
background-image: url("../img/add.svg");
background-color: initial
}
.icon-edit {
background-image: url("../img/edit.svg")!important;
background-color: initial!important
}
.icon-save {
background-image: url("../img/save.gif")!important;
background-color: initial!important
}
.icon-new-window {
background-image: url("../img/new_window.gif")!important;
background-color: initial!important
}
.icon-new-tab {
background-image: url("../img/new_tab.gif")!important;
background-color: initial!important
}
.icon-icon-all {
background-image: url("../img/icon-all.gif")!important;
background-color: initial!important
}
.icon-excel {
background-image: url("../img/excel-16.gif")!important;
background-color: initial!important
}
.cs-section-five-o-eight {
text-decoration-color: initial
}
.sm-rule-body {
background-color: hsl(210deg 6% 16%);
}
.sm-rule-body-title {
color: #5c98d6
}
.sm-rule-body-text {
color: hsl(36deg 10% 85%)
}
.sm-reviews-home-body-title {
color: #5c98d6
}
.sm-reviews-home-body-text {
color: #e8e6e3
}
.sm-reviews-home-tasks {
background-color: #930000
}
.sm-reviews-home-no-tasks {
background-color: #2c501c
}
.sm-feedback-panel-active {
background-color: #930000
}
.sm-feedback-panel-inactive {
background-color: #181a1b
}
.sm-feedback-body-title {
color: #5c98d6
}
.sm-feedback-body-text {
color: #e8e6e3
}
.deferral-approval-trigger {
background-image: url("../img/trigger2.png")!important
}
.sm-manual-grid-item {
background-color: #181a1b
}
.sm-manual-grid-item.x-grid3-row-over {
background-color: #212425
}
.sm-grid3-row-red {
background-color: #6c0000
}
.sm-grid3-row-grey {
background-color: #2b2f31
}
.sm-grid3-row-orange {
background-color: #703800
}
.sm-grid3-row-green {
background-color: #2c501c
}
.sm-grid3-row-black td {
background-color: #0b0c0d;
color: #e8e6e3!important
}
.sm-grid3-row-error td, .sm-grid3-row-italic td {
background-color: #ff4b4b33 !important;
}
.x-grid3-row-over {
border-color: #3a3e41;
background-color: #212425;
background-image: none
}
.sm-add-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTYiIGhlaWdodD0iMTYiPjxkZWZzPjxmaWx0ZXIgaWQ9ImRhcmtyZWFkZXItaW1hZ2UtZmlsdGVyIj48ZmVDb2xvck1hdHJpeCB0eXBlPSJtYXRyaXgiIHZhbHVlcz0iMC4yNDkgLTAuNjE0IC0wLjY3MiAwLjAwMCAxLjAzNSAtMC42NDYgMC4yODggLTAuNjY0IDAuMDAwIDEuMDIwIC0wLjYzNiAtMC42MDkgMC4yNTAgMC4wMDAgMC45OTQgMC4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMC4wMDAiIC8+PC9maWx0ZXI+PC9kZWZzPjxpbWFnZSB3aWR0aD0iMTYiIGhlaWdodD0iMTYiIGZpbHRlcj0idXJsKCNkYXJrcmVhZGVyLWltYWdlLWZpbHRlcikiIHhsaW5rOmhyZWY9ImRhdGE6aW1hZ2UvcG5nO2Jhc2U2NCxpVkJPUncwS0dnb0FBQUFOU1VoRVVnQUFBQkFBQUFBUUNBWUFBQUFmOC85aEFBQUFCbUpMUjBRQS93RC9BUCtndmFlVEFBQUEzRWxFUVZRNGpjWFNUVTZDTVJTRjRVY0RPZ0dtT0ZEMlljQUY2RDdVdUIxQ3dncFVWa0NNUTlmQmp3a3kwZ1hJU0FlOVh5Sk5QM0JpZkpPbWYvZWUzdmFVUCtBQ0U2eXh3UnNlMGQrWDJNQVljMXpqRk0zb2I3REFLT0tLakRGRnEyYS9oYWNRS1pZOTI1RmMwY1pTNFRxVEtEdm5xN0IyaTRkOGNTM2Q5VGNDUGVsaHQ5amdLRXZNVzhVeFBxdkpZZlFmNlA0SU9vaVdqK0VFNzduQUN5NEw1WmE0aXZndEJwTC83VDNKSGJ6aXZMUTVrbnl1RStuZ0djTTY5VWFJTENXcnpxU0g3ZUV1VGg3YThSTXIrcExQSzhtZEZlN3J5djUvdmdGRWtpd3ltOVR5bUFBQUFBQkpSVTVFcmtKZ2dnPT0iIC8+PC9zdmc+")!important
}
.sm-disc-drive {
background-image: url("../img/disc_drive.png")!important
}
.sm-internet-search {
background-image: url("../img/internet_search.png")!important
}
.sm-search-icon {
background-image: url("../img/search.png")!important
}
.sm-filter-icon {
background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iNjgxIiBoZWlnaHQ9IjY4MSI+PGRlZnM+PGZpbHRlciBpZD0iZGFya3JlYWRlci1pbWFnZS1maWx0ZXIiPjxmZUNvbG9yTWF0cml4IHR5cGU9Im1hdHJpeCIgdmFsdWVzPSIwLjI0OSAtMC42MTQgLTAuNjcyIDAuMDAwIDEuMDM1IC0wLjY0NiAwLjI4OCAtMC42NjQgMC4wMDAgMS4wMjAgLTAuNjM2IC0wLjYwOSAwLjI1MCAwLjAwMCAwLjk5NCAwLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAwLjAwMCIgLz48L2ZpbHRlcj48L2RlZnM+PGltYWdlIHdpZHRoPSI2ODEiIGhlaWdodD0iNjgxIiBmaWx0ZXI9InVybCgjZGFya3JlYWRlci1pbWFnZS1maWx0ZXIpIiB4bGluazpocmVmPSJkYXRhOmltYWdlL3N2Zyt4bWw7YmFzZTY0LFBITjJaeUJvWldsbmFIUTlJalV4TVhCMElpQjJhV1YzUW05NFBTSXdJREFnTlRFeElEVXhNUzQ1T1RrNE1pSWdkMmxrZEdnOUlqVXhNWEIwSWlCNGJXeHVjejBpYUhSMGNEb3ZMM2QzZHk1M015NXZjbWN2TWpBd01DOXpkbWNpUGp4d1lYUm9JR1E5SW0wME9USXVORGMyTlRZeUlEQm9MVFEzTVM0NU56WTFOakpqTFRFeExqQTBOamczTlNBd0xUSXdJRGd1T1RVek1USTFMVEl3SURJd0lEQWdOVFV1TmprMU16RXlJREl6TGpnM05TQXhNRGd1T0RZM01UZzRJRFkxTGpVd016a3dOaUF4TkRVdU9EY3hNRGswYkRnM0xqVTRPVGcwTkNBM055NDROVEUxTmpKak1UVXVNVGczTlNBeE15NDFJREl6TGpnNU9EUXpPQ0F6TWk0NE9UZzBNemdnTWpNdU9EazRORE00SURVekxqSXlNalkxTm5ZeE9UVXVNRE14TWpWak1DQXhOUzQ1TXpjMUlERTNMamd4TWpVZ01qVXVORGt5TVRnNElETXhMakE0T1RnME15QXhOaTQyTXpZM01UbHNNVEUzTGprNU5qQTVOQzAzT0M0Mk5qQXhOVFpqTlM0MU5qSTFMVE11TnpFd09UTTNJRGd1T1RBMk1qVXRPUzQ1TlRNeE1qVWdPQzQ1TURZeU5TMHhOaTQyTkRBMk1qVjJMVEV4Tmk0ek5qY3hPRGhqTUMweU1DNHpNalF5TVRnZ09DNDNNVEE1TXpjdE16a3VOekl5TmpVMklESXpMamc1T0RRek55MDFNeTR5TWpJMk5UWnNPRGN1TlRnMU9UTTRMVGMzTGpnMU1UVTJNbU0wTVM0Mk1qZzVNRFl0TXpjdU1EQXpPVEEySURZMUxqVXdNemt3TmkwNU1DNHhOelUzT0RJZ05qVXVOVEF6T1RBMkxURTBOUzQ0TnpFd09UUWdNQzB4TVM0d05EWTROelV0T0M0NU5UTXhNalV0TWpBdE1Ua3VPVGsyTURrMExUSXdlbTB0TnpJdU1EZ3lNRE14SURFek5TNDVOekkyTlRZdE9EY3VOVGcxT1RNM0lEYzNMamcxTlRRMk9XTXRNak11TnpFNE56VWdNakV1TURnMU9UTTNMVE0zTGpNeU5ESXhPU0ExTVM0ek56ZzVNRFl0TXpjdU16STBNakU1SURnekxqRXhNekk0TVhZeE1EVXVOalkzT1RZNWJDMDNOeTQ1T1RZd09UUWdOVEV1T1RrMk1EazBkaTB4TlRjdU5qWXdNVFUzWXpBdE16RXVOek00TWpneExURXpMall3TlRRMk9TMDJNaTR3TXpFeU5TMHpOeTR6TWpReU1Ua3RPRE11TVRFM01UZzNiQzA0Tnk0MU9EVTVNemN0TnpjdU9EVXhOVFl6WXkweU9DNHdOekF6TVRNdE1qUXVPVFUzTURNeExUUTFMams0T0RJNE1TMDFPUzR4TlRJek5ETXROVEF1TnpnMU1UVTJMVGsxTGprNE1EUTJPR2cwTWprdU16ZzJOekU1WXkwMExqYzVOamczTmlBek5pNDRNamd4TWpVdE1qSXVOekV3T1RNNElEY3hMakF5TXpRek55MDFNQzQzT0RVeE5UY2dPVFV1T1RjMk5UWXllbTB3SURBaUx6NDhMM04yWno0PSIgLz48L3N2Zz4=")
}
.sm-control-panel {
background-image: url("../img/control_panel.png")!important
}
.sm-checklist-icon {
background-image: url("../img/shield-green-check.svg")!important;
filter: saturate(.75)
}
.sm-checklist-tab-icon {
background-image: url("../img/shield-green-check.svg")!important
}
.sm-setting-icon {
background-image: url("../img/gear.svg")!important
}
.sm-export-icon {
background-image: url("../img/download.svg")
}
.sm-import-icon {
background-image: url("../img/upload.svg")
}
.sm-asset-icon {
background-image: url("../img/target.svg")!important
}
.sm-template-icon {
background-image: url("../img/template.png")!important
}
.sm-library-icon {
background-image: url("../img/library.svg")!important
}
.sm-folder-icon {
background-image: url("../img/folder.svg")!important
}
.sm-collection-icon, .sm-collection-tab-icon {
background-image: url("../img/collection.svg")!important
}
.sm-department-icon {
background-image: url("../img/department-16.png")!important
}
.sm-stig-icon {
background-image: url("../img/shield-green-check.svg")!important;
filter: saturate(.75)
}
.sm-report-icon {
background-image: url("../img/grid.svg")!important
}
.sm-chat-icon {
background-image: url("../img/chat-16.png")!important
}
.sm-ackchat-icon, .sm-newchat-icon, .sm-unackchat-icon {
background-image: url("../img/message_edit.png")!important
}
.sm-feedback-icon {
background-image: url("../img/feedback-16.gif")!important
}
.sm-feedback-ack-icon {
background-image: url("../img/feedback-ack-16.gif")!important
}
.sm-feedback-unack-icon {
background-image: url("../img/feedback-unack-16.gif")!important
}
.sm-artifact-icon {
background-image: url("../img/page_white_text.png")!important
}
.sm-note-icon {
background-image: url("../img/note-16.png")!important
}
.sm-star-icon, .sm-star-icon-16 {
background-image: url("../img/star.svg")!important
}
.sm-assign-icon {
background-image: url("../img/right-arrow-16.png")!important
}
.sm-unlock-icon {
background-image: url("../img/unlock-16.png")!important
}
.sm-ready-icon {
background-image: url("../img/ready-16.png")!important
}
.sm-ready-flip-icon {
background-image: url("../img/ready-flip-16.png")!important
}
.x-btn-pressed.sm-star-icon {
background-image: url("../img/star.svg")!important
}
.sm-save-icon {
background-image: url("../img/save-16.png")!important
}
.sm-disk-icon {
background-image: url("../img/save-icon.svg")!important
}
.sm-database-save-icon {
background-image: url("../img/database.svg")!important
}
.sm-table-icon {
background-image: url("../img/table.png")!important
}
.sm-page-edit-icon {
background-image: url("../img/page_edit.png")!important
}
.sm-page-white-get-icon {
background-image: url("../img/page_white_get.png")!important
}
.sm-page-white-put-icon {
background-image: url("../img/page_white_put.png")!important
}
.sm-hbss-disabled-icon, .sm-hbss-enabled-icon {
background-image: url("../img/hbss-check-sprite.gif")
}
.sm-application-go-icon {
background-image: url("../img/application_go.png")!important
}
.sm-list-remove-16-icon {
background-image: url("../img/list-remove-16.png")
}
.sm-scan-assign-icon {
background-image: url("../img/greencheckt.gif")
}
.x-item-disabled .sm-scan-assign-icon {
background-image: url("../img/greycheckt.gif")
}
.sm-scan-unassign-icon {
background-image: url("../img/greydash.gif")
}
.sm-scan-toggleAssign-icon {
background-image: url("../img/icon-all.gif")
}
.sm-zip-icon {
background-image: url("../img/compress.png")
}
.sm-scap-grid-item {
background-color: #1e3516
}
.sm-scap-grid-item.x-grid3-row-over {
background-color: #24361e
}
.sm-scap-grid-item.x-grid3-row-selected {
background-color: #2d3c28!important
}
.sm-cell-red {
background-color: #6c0000;
border-right-color: #303436;
border-left-color: #303436
}
.x-grid3-row-over .sm-cell-red {
background-color: #4e0b0b!important
}
.sm-cell-orange {
background-color: #703800;
border-right-color: #303436;
border-left-color: #303436
}
.x-grid3-row-over .sm-cell-orange {
background-color: #502e0b!important
}
.sm-cell-green {
background-color: #2c501c;
border-right-color: #303436;
border-left-color: #303436
}
.x-grid3-row-over .sm-cell-green {
background-color: #253d1c!important
}
.sm-cell-grey {
background-color: #2b2f31;
border-right-color: #303436;
border-left-color: #303436
}
.sm-cell-purple {
background-color: #5f225f;
border-right-color: #303436;
border-left-color: #303436
}
.x-grid3-row-over .sm-cell-purple {
background-color: #441f44!important
}
.sm-cell-peach {
background-color: #6c5a04
}
.sm-cell-status {
background-color: hsl(192deg 55% 16%);
border-left-color: #303436
}
.x-grid3-row-over .sm-cell-status {
border-left-color: #303436;
background-color: #242728!important
}
.sm-cell-checklist {
background-image: url("../img/security_firewall_on.png")
}
.sm-cell-asset {
background-image: url("../img/target.svg")
}
.sm-cell-template {
background-image: url("../img/template.png")
}
.custom-stig-users .x-grid3-row-selected .x-grid3-cell-last {
background-image: url("../img/User-Group-icon.png")
}
.sm-artifact-download-icon {
background-image: url("../img/download.svg")
}
.sm-artifact-edit-icon {
background-image: url("../img/edit-16.png")
}
.x-grid3-row-over .artifact-download {
background-image: url("../img/download.svg")
}
.x-grid3-row-over .artifact-view {
background-image: url("../img/eye.svg")
}
.x-grid3-row-over .artifact-edit {
background-image: url("../img/edit-16.png")
}
.x-grid3-row-over .artifact-delete {
background-image: url("../img/delete.png")
}
.x-grid3-row-over .artifact-download :active, .x-grid3-row-over .artifact-download:active {
background-image: url("../img/download.svg")
}
.sm-reviews-home-background {
background-color: #181a1b
}
.sm-background-blue {
background-color: #222426!important
}
.x-grid3-summary-row {
border-left-color: #303436;
border-right-color: #303436;
color: #c8c3bc;
background-image: initial;
background-color: #1f2223
}
.sm-review-action-textarea[disabled], .sm-review-result-textarea[disabled] {
color: #e8e6e3;
background-image: none;
background-color: initial
}
.sm-combo-loading {
background-image: url("../img/loading.gif")
}
.sm-context-menu {
background-image: none
}
.sm-context-menu-header {
background-color: #272a2c;
border-color: #1a4072
}
.fa-border {
border-color: #35393b
}
.fa-inverse {
color: #e8e6e3
}
.sr-only {
border-color: initial
}
.x-form-file-wrap .x-form-file-text {
color: #9d9488
}
.x-row-editor-footer, .x-row-editor-header {
background-image: url(../img/row-editor-bg-dark.gif);
background-color: transparent
}
.x-row-editor-body {
background-image: initial;
background-color: #25282a
}
.x-row-editor .x-btns, .x-row-editor .x-btns .x-plain-body, .x-row-editor .x-btns .x-plain-bwrap {
background-image: url("../img/row-editor-btns-dark.gif");
background-color: transparent
}
.x-row-editor.x-small-editor {
border-right: 1px solid #c4c4c4
}
.json-container {
background-color: #181a1b;
color: #988f81
}
.json-container .json-key {
color: #bdb7af
}
.json-container .json-number {
color: #ff941a
}
.json-container .json-object {
color: #6b91d8
}
.json-container .json-boolean {
color: #ec6168
}
.json-container .json-string {
color: #b0f76d
}
.json-container .sm-caret-down {
border-color: #545b5e transparent
}
.json-container .sm-caret-right {
border-color: transparent transparent transparent #545b5e
}
.vimvixen-hint {
background-color: #7b5300!important;
border-color: #d8b013!important;
color: #f3e8c8!important
}
a[href="https://coinmarketcap.com/"] > svg[width="94"][height="16"] > path {
fill: var(--darkreader-neutral-text)!important
}
#edge-translate-panel-body {
color: var(--darkreader-neutral-text)!important
}
gr-main-header {
background-color: #0f3a48!important
}
embed[type="application/pdf"] {
filter: invert(100%) contrast(90%)
}
.ext-el-mask-msg span {
border: 3px solid #bbb;
border-bottom-color: transparent
}
.ext-el-mask-msg div {
background-color: #565656;
color: #eee
}
.ext-el-mask-modal {
background-color: rgb(0 0 0 / 65%)
}
.x-tool:hover {
filter: brightness(150%)
}
.sm-line-height-up {
background-image: url(../img/line-height-up-dark.svg);
background-size: 16px 16px;
}
.sm-line-height-down {
background-image: url(../img/line-height-down-dark.svg);
background-size: 16px 16px;
}
.d2h-file-wrapper {
border-color: #444;
}
.d2h-file-header {
border-bottom-color: #444;
background-color: hsl(204deg 6% 16%);
}
.d2h-info {
background-color: hsl(216deg 56% 60%);
border-color: hsl(216deg 56% 55%);
}
.d2h-file-name-wrapper {
color: #999
}
.d2h-code-line del, .d2h-code-side-line del {
background-color: hsl(0 63% 31% / 1);
}
.d2h-file-diff .d2h-del.d2h-change {
background-color: hsl(0 60% 17% / 1);
}
.d2h-file-diff .d2h-ins.d2h-change {
background-color: hsl(110deg 22% 22%);
}
.d2h-code-line ins, .d2h-code-side-line ins {
background-color: hsl(110deg 35% 30%);
}
.d2h-code-linenumber {
background-color: transparent;
color: hsl(0deg 0% 50%);
border-right-color: hsl(0 0% 20%);
}
.d2h-del {
background-color: hsl(0 60% 17% / 1);
border-right-color: hsl(0 59% 20%);
}
.d2h-file-diff {
background-color: hsl(195deg 7% 11%);
}
.d2h-ins {
background-color: hsl(110deg 22% 22%);
border-right-color: hsl(120 33% 20%);
}
.sm-diff-ins {
background-color: hsl(78deg 35% 26%);
}
.sm-diff-del {
background-color: hsl(0deg 71% 25%)
}
.sm-round-panel .x-panel-header.sm-selections-panel-header {
background-color: var(--metrics-status-chart-submitted-dark);
}
.sm-grabbing *, .sm-grabbing .sm-grid3-draggable .x-grid3-row-selected *, .sm-grabbing .sm-grid3-draggable .x-grid3-row-selected {
cursor: url("../img/drag-drop-dark.svg"), grabbing;
}
.sm-appinfo-message {
background-color: #2d2d2d;
color: #999999;
}
.sm-render-zero {
color: #444444
}
.sm-whats-new img {
border: 1px solid hsl(0 0% 20% / 1)
}
.sm-feedback-box {
background-color: #2d3e4a;
border: 1px solid #3a4d5c;
}
.sm-feedback-box-title {
color: #7ab3e8;
}
.sm-feedback-box-content {
color: hsl(36deg 10% 85%);
}
.sm-feedback-box-content a {
color: #7ab3e8;
}
.x-btn {
background-color: #424242;
border-radius: 6px;
}
.x-btn:hover {
background-color: var(--metrics-status-chart-submitted-dark);
}
.x-toolbar .x-btn {
background-color: transparent;
}
.x-toolbar .x-btn:hover {
background-color: var(--metrics-status-chart-submitted-dark);
}
.x-toolbar .x-btn-pressed.x-btn {
background-color: var(--metrics-status-chart-submitted-dark);
}
.sm-label-sprite.sm-sprite-read, .sm-label-sprite.sm-sprite-readwrite {
color: #000000;
}
.x-form-field-wrap:hover .x-form-file-btn {
background-color: var(--metrics-status-chart-submitted-dark);
border-radius: 5px;
}
.sm-cora-box-right {
border: 1px solid #444;
}
.sm-cora-cat {
border: 1px solid #444;
}
.sm-metrics-age-box {
background-color: #aaa
}
.x-btn-pressed {
box-shadow: inset 0px 0px 0px 1px hsl(0 0% 50% / 1);
}
.sm-log-line[data-component="logSocket"] {
color: #c48eff;
}
.sm-log-line[data-component="jwksCache"] {
color: #e7a15e;
}
.sm-log-line[data-component="static"] {
color: #808080;
}
.sm-log-line[data-component="rest"] {
color: #5ee75e;
}
.sm-log-line[data-level="1"] {
color: red;
}
.sm-log-line[data-level="2"] {
color: orange;
}
================================================
FILE: client/src/css/init.css
================================================
#loading-mask {
position: absolute;
left: 0;
top: 0;
width: 100%;
height: 100%;
z-index: 20000;
display: flex;
align-items: start;
justify-content: center;
background-color: #2a3037;
color: #d0cec5;
}
#loading {
position: absolute;
top: 100px;
display: flex;
flex-direction: column;
align-items: center;
justify-content: flex-start;
gap: 16px; /* space between items */
}
#loading .loading-indicator {
background: url("../img/loading.svg") no-repeat;
background-position: center top;
background-size: 50px;
color: #d0cec5;
font: bold 42px helvetica, sans-serif;
padding: 50px 0px;
margin: 0;
text-align: center;
height: auto;
}
#loading-text {
font: bold 12px helvetica, sans-serif;
padding-top: 8px;
}
#loading-text a {
color: #d0cec5;
background: url("../img/external-link.svg") no-repeat 100% 0;
background-size: 12px 12px;
padding-right: 16px;
}
================================================
FILE: client/src/css/jsonview.bundle.css
================================================
.json-container {
font-family: 'Open Sans';
font-size: 11px;
background-color: transparent;
color: #808080;
box-sizing: border-box;
}
.json-container .line {
margin: 2px 0;
display: flex;
justify-content: flex-start;
}
.json-container .caret-icon {
width: 18px;
text-align: center;
cursor: pointer; }
.json-container .empty-icon {
margin-left: 18px; }
.json-container .json-type {
margin-right: 4px;
margin-left: 4px; }
.json-container .empty-icon ~ .json-key {
font-weight: unset; }
.json-container .json-key {
color: #444;
font-weight: 600;
margin-right: 4px;
margin-left: 4px; }
.json-container .json-index {
margin-right: 4px;
margin-left: 4px; }
.json-container .json-value {
margin-left: 8px; }
.json-container .json-number {
color: #ff8800;
}
.json-container .json-object {
color: #6b65d7;
}
.json-container .json-boolean {
color: #ec5f66; }
.json-container .json-string {
color: hsl(91 89% 29% / 1);
}
.json-container .json-size {
margin-right: 4px;
margin-left: 4px; }
.json-container .hide {
display: none; }
.json-container .sms {
display: inline-block;
width: 0;
height: 0;
border-style: solid;
}
.json-container .sm-caret-down {
border-width: 6px 5px 0 5px;
border-color: #585858 transparent;
}
.json-container .sm-caret-right {
border-width: 5px 0 5px 6px;
border-color: transparent transparent transparent #585858;
}
================================================
FILE: client/src/css/stigman.css
================================================
:root {
--metrics-status-chart-assessed-light: hsl(230deg 41% 86%);
--metrics-status-chart-submitted-light: hsl(92deg 44% 77%);
--metrics-status-chart-accepted-light: hsl(146deg 60% 69%);
--metrics-status-chart-unassessed-light: hsl(0deg 0% 93%);
--metrics-status-chart-unsaved-light: hsl(0deg 0% 93%);
--metrics-status-chart-rejected-light: hsl(13deg 69% 75%);
--metrics-status-chart-assessed-dark: hsl(204deg 91% 25%);
--metrics-status-chart-submitted-dark: hsl(87deg 41% 25%);
--metrics-status-chart-accepted-dark: hsl(146deg 90% 25%);
--metrics-status-chart-unassessed-dark: hsl(0 0% 18% / 1);
--metrics-status-chart-unsaved-dark: hsl(0deg 0% 18%);
--metrics-status-chart-rejected-dark: hsl(5deg 90% 25%);
--color-severity-high: hsl(13deg 68% 75%);
--color-severity-medium: hsl(38 100% 78% / 1);
--color-severity-low: hsl(230deg 41% 86%);
--color-risk-very-high: var(--color-severity-high);
--color-risk-very-high-text: rgb(88, 12, 21);
--color-risk-high: var(--color-severity-medium);
--color-risk-high-text: rgb(146, 50, 18);
--color-risk-moderate: hsl(60 100% 80% / 1);
--color-risk-moderate-text: #805500;
--color-risk-low: var(--color-severity-low);
--color-risk-low-text: rgb(14, 90, 161);
--color-risk-very-low: #c3deab;
--color-risk-very-low-text: rgb(0, 100, 0);
--color-scrollbar-idle: #d0d0d0;
--color-scrollbar-hover: #b0b0b0;
--color-marking-unclassified: #007a33;
--color-marking-cui: #502b85;
--color-marking-confidential: #0033a0;
--color-marking-fouo: #502b85;
--color-marking-secret: #c8102e;
--color-marking-topsecret: #ff671f;
--color-marking-sci: #f7ea48;
--color-http-status-200: #7dd491;
--color-http-status-300: #99c2ff;
--color-http-status-400: #ffc099;
--color-http-status-500: #ff9999;
--color-job-run-state-completed: hsl(121 84% 50% / 1);
--color-job-run-state-running: hsl(222, 84%, 50%);
--color-job-run-state-failed: hsl(1deg 74.55% 52.35%);
--color-job-run-state-missing: hsl(0 0% 73% / 1);
}
.x-tree-node-collapsed .x-tree-node-icon,
.x-tree-node-expanded .x-tree-node-icon,
.x-tree-node-leaf .x-tree-node-icon {
width: 22px;
}
.sm-grid-cell-with-toolbar {
position: relative;
}
.sm-grid-cell-with-toolbar .sm-dynamic-width {
margin-right: 0px;
}
.sm-grid-cell-with-toolbar .sm-info {
text-overflow: ellipsis;
overflow: hidden;
white-space: nowrap;
}
.sm-grid-cell-with-toolbar .sm-static-width {
position: absolute;
visibility: hidden;
top: 0;
right: 0;
}
.x-grid3-row-over .sm-grid-cell-with-toolbar .sm-dynamic-width {
margin-right: 28px;
}
.x-grid3-row-over .sm-grid-cell-with-toolbar .sm-static-width {
visibility: visible;
filter: grayscale(100%) brightness(125%);
}
.x-grid3-row-over .sm-grid-cell-with-toolbar .sm-static-width:hover {
scale: 110%;
filter: brightness(100%);
}
.sm-grid-cell-with-toolbar-2 {
position: relative;
}
.sm-grid-cell-with-toolbar-2 .sm-dynamic-width {
margin-right: 0px;
}
.sm-grid-cell-with-toolbar-2 .sm-info {
text-overflow: ellipsis;
overflow: hidden;
white-space: nowrap;
}
.sm-grid-cell-with-toolbar-2 .sm-static-width {
position: absolute;
visibility: hidden;
top: 0;
right: 0;
}
.x-grid3-row-over .sm-grid-cell-with-toolbar-2 .sm-dynamic-width {
margin-right: 58px;
}
.x-grid3-row-over .sm-grid-cell-with-toolbar-2 .sm-static-width .sm-grid-cell-tool img {
visibility: visible;
filter: grayscale(100%) brightness(125%);
}
.x-grid3-row-over .sm-grid-cell-with-toolbar-2 .sm-static-width .sm-grid-cell-tool:hover img {
cursor: pointer;
scale: 125%;
filter: brightness(100%);
}
.sm-metrics-no-assessments-body {
color: #bbb;
display: flex;
justify-content: center;
align-items: center;
height: inherit;
width: inherit
}
.sm-metrics-progress-parent {
text-align: center
}
.sm-metrics-progress-child {
display: inline-block;
width: 73px;
border-radius: 5px;
margin: 0 9px;
vertical-align: middle
}
.sm-metrics-progress-label {
font-weight: 600;
padding-bottom: 4px
}
.sm-metrics-progress-child .sm-metrics-progress-thermometer-wrap {
height: 20px;
line-height: 20px;
font-weight: 600
}
.sm-metrics-progress-child .sm-cell-mercury-high,
.sm-metrics-progress-child .sm-cell-mercury-low,
.sm-metrics-progress-child .sm-cell-mercury-medium,
.sm-metrics-progress-child .sm-cell-thermometer-bg {
height: 100%
}
.sm-metrics-status-table {
padding-top: 10px
}
.sm-metrics-status-pct {
text-align: center;
font-size: large;
font-weight: 600
}
.sm-metrics-status-table .sm-metrics-total {
font-weight: 600
}
.sm-metrics-status-table .sm-metrics-total td {
font-weight: 600;
border-top: 1px solid #bbb
}
.sm-metrics-status-table tr {
height: 19px
}
.sm-metrics-status-table td {
padding-left: 4px;
padding-right: 4px
}
.sm-metrics-status-table .sm-metrics-value {
text-align: right;
padding-left: 10px
}
.sm-metrics-status-table .sm-metrics-label {
border: 1px solid #bbb;
border-radius: 3px
}
.sm-metrics-status-table .sm-metrics-assessed {
background-color: var(--metrics-status-chart-assessed-light)
}
.sm-metrics-status-table .sm-metrics-submitted {
background-color: var(--metrics-status-chart-submitted-light);
}
.sm-metrics-status-table .sm-metrics-accepted {
background-color: var(--metrics-status-chart-accepted-light)
}
.sm-metrics-status-table .sm-metrics-unassessed {
background-color: var(--metrics-status-chart-unassessed-light)
}
.sm-metrics-status-table .sm-metrics-unsaved {
background-color: var(--metrics-status-chart-unsaved-light)
}
.sm-metrics-status-table .sm-metrics-rejected {
background-color: var(--metrics-status-chart-rejected-light)
}
.sm-metrics-refresh-parent {
padding-right: 20px;
text-align: right;
font-style: italic
}
.sm-metrics-count-parent {
text-align: center;
color: #111
}
.sm-metrics-count-child {
display: inline-block;
cursor: default;
width: 61px;
height: 36px;
border-radius: 5px;
background-color: #eee;
border: 1px solid #bbb;
padding: 4px 12px;
margin: 0 12px;
vertical-align: middle;
line-height: 18px
}
.sm-metrics-count-label {
font-weight: 600;
font-size: larger
}
.sm-metrics-count-value {
font-weight: 800;
font-size: large
}
.sm-cora-column,
.sm-metrics-findings-count-cell {
border-radius: 5px;
outline: #bbb solid 1px;
outline-offset: -1px;
width: 35px;
font-weight: 600;
color: #111;
margin: 0 auto
}
.sm-cora-tooltip-label {
border-radius: 5px;
outline: #bbb solid 1px;
outline-offset: -1px;
width: auto;
/* Allow width to fit content */
min-width: 80px;
/* Ensure minimum width for consistency */
font-weight: 500;
/* Lighter weight */
color: #111;
margin: 2px auto;
padding: 2px 6px;
/* Add padding for better text spacing */
display: inline-block;
text-align: center;
}
.sm-metrics-high-box {
background-color: var(--color-severity-high)
}
.sm-metrics-medium-box {
background-color: var(--color-severity-medium)
}
.sm-metrics-low-box {
background-color: var(--color-severity-low)
}
.sm-metrics-inventory-box {
background-color: hsl(21deg 41% 86%)
}
.sm-metrics-overview-panel .x-panel-body {
background-color: hsl(0 0% 95% / 1)
}
.sm-round-inner-panel {
border-radius: 6px;
overflow: hidden;
margin: 12px;
}
.sm-round-panel .sm-round-inner-panel .x-panel-body {
background-color: #fff;
border-bottom-left-radius: 6px;
border-bottom-right-radius: 6px
}
.sm-metric-agg-panel .x-layout-split {
background-color: #eee
}
.sm-combo-list-icon {
border-width: 0px;
padding-left: 20px;
background-position: left
}
.sm-col-wrap .x-grid3-cell-inner,
.x-grid3-row-body {
white-space: pre-wrap;
overflow-wrap: break-word
}
.x-grid3-row-expanded .x-grid3-row-body {
max-width: 600px;
background-color: #faebd7
}
.sm-truncated-action {
color: #36c;
font-style: italic;
text-decoration: underline;
cursor: pointer
}
.sm-whats-new p {
margin-top: 10px;
margin-bottom: 10px
}
.sm-whats-new img {
border: 1px solid hsl(0deg 0% 65%)
}
.sm-whats-new-no-border img {
border: 0px
}
.sm-whats-new-feedback-panel {
padding: 10px 20px 20px 20px;
}
.sm-feedback-box {
background-color: #e8f4f8;
border: 1px solid #b8d4e8;
border-radius: 4px;
padding: 8px 16px;
margin: 0;
}
.sm-feedback-box-title {
font-weight: bold;
font-size: 14px;
margin-bottom: 8px;
color: #2c5f7c;
}
.sm-feedback-box-content {
font-size: 13px;
color: #333;
}
.sm-feedback-box-content a {
color: #2c5f7c;
text-decoration: underline;
}
.sm-whats-new-title {
padding-top: 10px;
}
.x-tree-node-leaf .x-tree-node-icon.sm-whats-new-icon {
background-image: url(../img/clock.svg);
background-size: 16px 16px
}
.sm-dark-mode-icon {
background-image: url(../img/dark-mode.svg) !important;
background-size: 16px 16px
}
.x-grid3-cell-inner {
padding-left: 4px
}
.sm-engine-result-icon {
background-image: url(../img/bot2.svg);
background-repeat: no-repeat;
width: 12px;
}
.sm-engine-override-icon {
background-image: url(../img/override2.svg);
background-repeat: no-repeat
}
.sm-engine-manual-icon {
background-image: url(../img/user.svg);
background-repeat: no-repeat
}
.x-grid3-cell.x-grid3-hd .sm-engine-result-icon {
background-size: 12px 12px;
width: 12px;
height: 12px
}
.x-grid3-cell :is(.sm-engine-result-icon, .sm-engine-override-icon, .sm-engine-manual-icon) {
background-size: 14px 14px;
height: 14px;
width: 14px
}
.x-menu-item-text .sm-engine-result-icon,
.x-menu-item-text .sm-history-icon {
background-size: 12px 12px;
height: 12px
}
.x-grid3-cell.x-grid3-hd .sm-history-icon {
background-size: 12px 12px;
background-position: center;
height: 12px
}
.x-menu-check-item .x-menu-item-icon {
background-image: url(../img/checkboxes.svg);
background-position: 1px 0;
background-repeat: no-repeat;
background-color: transparent
}
.x-menu-item-checked .x-menu-item-icon {
background-position: -24px 0
}
.x-menu-group-item .x-menu-item-icon {
background-image: none
}
.x-tree-node {
margin-bottom: 2px;
font-size: 11px
}
.x-grid3-row td,
.x-grid3-summary-row td {
line-height: 15px
}
.sm-label-edit-color {
position: absolute;
top: 5px;
right: 2px;
cursor: pointer
}
.x-tree-node-el.x-unselectable {
cursor: default
}
.sm-tree-toolbar {
display: none
}
/* Always show Meta Dashboard button (grid icon) */
.sm-tree-toolbar.sm-tree-toolbar-persistent {
display: inline;
position: absolute;
right: 10px;
margin-top: 2px;
cursor: pointer;
opacity: .5
}
.x-tree-node-el:hover .sm-tree-toolbar,
.x-tree-selected .sm-tree-toolbar {
display: inline;
position: absolute;
right: 10px;
margin-top: 2px;
cursor: pointer;
opacity: .5
}
.x-tree-node-el:hover .sm-tree-toolbar:hover,
.x-tree-selected .sm-tree-toolbar:hover {
opacity: 1;
scale: 125%
}
.x-color-palette {
height: unset;
width: 108px
}
.x-color-palette em {
border: 0
}
.x-color-palette em span {
width: 12px;
height: 12px
}
.sm-label-icon {
background-image: url(../img/label.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-pin-icon {
background-image: url(../img/pin.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-label-sprite {
font: 600 10px/14px Open Sans, helvetica, sans-serif;
top: 0;
padding: 0 5px;
border-radius: 3px;
margin-left: 3px;
white-space: nowrap
}
.sm-jumbo-sprite {
font-size: 12px;
}
.sm-diff-sprite {
background-color: hsl(207deg 100% 84%);
color: #000;
}
.sm-diff-sprite-check {
background-color: #F5A3A3;
color: #000;
}
.x-tip .x-tip-bc,
.x-tip .x-tip-bl,
.x-tip .x-tip-br,
.x-tip .x-tip-ml,
.x-tip .x-tip-mr,
.x-tip .x-tip-tc,
.x-tip .x-tip-tl,
.x-tip .x-tip-tr {
background-color: #feeecc;
background-image: unset
}
.x-grid3-row-selected {
background-color: hsl(212deg 14% 85%) !important;
background-image: none;
border-color: #acacac
}
.x-grid3-hd-checker,
.x-grid3-row-checker {
background-image: url(../img/checkboxes.svg);
width: 100%;
height: 18px;
background-position: 1px 2px;
background-repeat: no-repeat;
background-color: transparent
}
.x-grid3-body .x-grid3-td-checker {
background: unset
}
.x-grid3-body .x-grid3-row-selected .x-grid3-td-checker {
background-image: unset
}
.x-grid3-row .x-grid3-row-checker {
background-position: 1px 2px
}
.x-grid3-hd-checker-on .x-grid3-hd-checker,
.x-grid3-row-checked .x-grid3-row-checker,
.x-grid3-row-selected .x-grid3-row-checker {
background-position: -24px 2px;
}
.x-grid3-hd-checker {
background-position: 1px 1px
}
.ext-border-box .x-grid3-hd-checker {
background-position: 1px 3px
}
.x-grid3-hd-checker-on .x-grid3-hd-checker {
background-position: -24px 1px
}
.x-grid3-hd-checker-ind .x-grid3-hd-checker {
background-position: -50px 1px
}
.x-grid3-row-selected-checkonly .x-grid3-row-checker {
background-position: -24px 2px
}
input.x-tree-node-cb {
margin-right: 2px
}
.sm-text-highlight {
background-color: #fad6a2
}
.sm-menuitem-filter-label {
background-color: #d3d8de;
font-weight: 700;
font-size: 9px;
color: hsl(0 0% 50% / 1) !important;
height: 10px;
line-height: 10px !important
}
.sm-menuitem-filter-icon {
background-image: url(../img/bars-filter.svg);
background-size: 16px;
background-position: center;
background-repeat: no-repeat;
top: 0
}
.sm-menuitem-status-icon {
width: 12px;
height: 12px;
padding-right: 3px;
vertical-align: -2px
}
.sm-menuitem-div-icon {
padding-left: 18px;
background-size: 14px 14px;
background-position: 0 1px
}
.sm-grid3-col-filterable .x-grid3-hd-btn {
background-image: url(../img/bars-filter.svg);
background-size: 10px 14px;
background-position: center;
display: block;
margin-top: 1px;
height: 22px;
margin-right: 0
}
.sm-grid3-col-filtered .x-grid3-hd-btn {
background-color: var(--metrics-status-chart-submitted-light);
}
.x-grid3-hd-btn {
background-color: transparent;
background-image: none;
display: block;
cursor: default
}
.sm-cb .x-form-cb-label {
top: 3px
}
.sm-collection-manage-layout .x-border-layout-ct,
.sm-collection-manage-layout .x-panel-body,
.sm-dialog-window.sm-round-panel {
background-color: #fdfdfd
}
.sm-collection-manage-layout .x-layout-split {
position: absolute;
height: 5px;
width: 5px;
text-align: center;
line-height: 5px;
font-size: 10px;
color: hsl(0deg 0% 65%);
background-color: transparent
}
.sm-collection-manage-layout .x-layout-split:after {
content: "===="
}
.x-form-search:focus,
.x-form-text:focus,
.x-form-textarea:focus {
border: 1px solid #dc8633;
box-shadow: inset rgb(220 134 51 / 20%) 0 0 1px 1px
}
.sm-result-engine-span.x-column {
overflow: unset
}
.sm-result-engine-sprite {
color: #fcfcfc !important;
font: bold 10px Open Sans, helvetica, sans-serif;
position: relative;
top: -1px;
background-color: hsl(220deg 60% 50%);
padding: 1px 4px 2px !important;
border-radius: 3px;
margin-left: 4px;
user-select: none
}
.sm-result-override-sprite {
color: #fcfcfc !important;
font: bold 10px Open Sans, helvetica, sans-serif;
position: relative;
top: -1px;
background-color: #cc5e33;
padding: 1px 4px 2px !important;
border-radius: 3px;
margin-left: 4px;
user-select: none
}
.x-form-cb-label .sm-question-circle,
.x-form-item-label .sm-question-circle,
.x-grid3-hd .sm-question-circle,
.x-panel-header .sm-question-circle {
color: hsl(0deg 0% 60%);
margin-left: 3px;
font-size: 13px
}
.x-form-trigger+.sm-question-circle {
margin-left: 22px;
color: hsl(0deg 0% 60%);
font-size: 14px;
position: absolute;
top: 3px
}
.x-form-trigger[style*="display: none;"]+.sm-question-circle {
margin-left: 5px
}
.x-form-field-wrap.x-form-field-trigger-wrap .x-form-field.sm-review-combo-input[disabled] {
color: gray;
background-color: transparent;
cursor: auto
}
.sm-home-widget-bwrap {
overflow: auto;
height: 338px;
margin-right: 0
}
.x-progress-inner {
background-image: none;
background-color: hsl(0deg 0% 95%)
}
.x-progress-bar {
background-image: none;
background-color: #bdd0e5;
border: none
}
.sm-pb-error .x-progress-bar {
background-color: #ebadad
}
.x-progress-text {
color: transparent
}
.x-progress-text.x-progress-text-back {
color: hsl(0deg 0% 33%)
}
.sm-cell-thermometer-bg {
background-color: #eee;
border-radius: 3px;
outline: #bbb solid 1px;
outline-offset: 0px
}
.sm-cell-thermometer-text {
float: left;
margin-left: 4px;
font-style: italic;
font-weight: 600
}
.sm-cell-mercury-low {
background-color: #c3deab
}
.sm-cell-mercury-medium {
background-color: hsl(230deg 40% 86%)
}
.sm-cell-mercury-high {
background-color: #eba795;
height: 15px
}
.x-panel-btns td.x-toolbar-cell {
padding: 0 18px 10px 0
}
.sm-dialog-panel-text {
padding-bottom: 10px;
font: 10px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-dialog-panel-content {
padding-bottom: 10px;
font: 11px/13px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-dialog-panel-callout {
margin-top: 20px;
padding: 10px;
font: 11px/13px Open Sans, helvetica, sans-serif;
background-color: #e6e6e6;
color: #000;
word-wrap: break-word
}
.sm-dialog-panel-content ul {
list-style-type: square;
display: list-item;
margin-left: 2em
}
.ext-gecko .x-btn button,
.ext-webkit .x-btn button,
.x-btn button {
font-weight: 600;
padding: 0 3px 3px 3px
}
.x-btn button.sm-error-icon {
background-color: #ebadad;
background-image: url("../img/remove.svg")
}
.sm-export-sprite {
font: 10px Open Sans, helvetica, sans-serif;
position: relative;
top: -1px;
border-radius: 12px;
padding: 0 5px 1px !important;
user-select: none
}
.sm-export-sprite-high,
.sm-export-sprite-medium {
background-color: #ddd
}
.sm-export-sprite-low {
background-color: #c3deab
}
.x-form-display-field {
padding-top: 3px
}
.ext-webkit .x-small-editor .x-form-field {
font: 10px Open Sans, helvetica, sans-serif
}
.x-grid-group-collapsed .x-grid-group-hd div.x-grid-group-title {
background-image: url(../img/tree-elbow-closed.svg);
background-position: 3px 7px
}
.x-grid-group-hd div.x-grid-group-title {
background-image: url(../img/tree-elbow-minus.svg);
background-position: 3px 7px
}
.x-grid3-row-collapsed .x-grid3-row-expander {
background-image: url(../img/tree-elbow-closed.svg);
background-position: 3px 4px
}
.x-grid3-row-expanded .x-grid3-row-expander {
background-image: url(../img/tree-elbow-minus.svg);
background-position: 3px 4px
}
.sm-toolbar-legend-box {
width: 20px;
height: 10px;
border: 1px solid #c2c2c2
}
.x-tree-lines .x-tree-elbow,
.x-tree-lines .x-tree-elbow-end,
.x-tree-lines .x-tree-elbow-line {
background-image: none
}
.x-tree-lines .x-tree-elbow-end-minus,
.x-tree-lines .x-tree-elbow-minus {
background-image: url(../img/tree-elbow-minus.svg);
background-position: 3px 4px
}
.x-tree-lines .x-tree-elbow-end-plus,
.x-tree-lines .x-tree-elbow-plus {
background-image: url(../img/tree-elbow-closed.svg);
background-position: 3px 4px
}
.sm-drop {
border: 2px dashed #bbb;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
padding: 25px;
text-align: center;
font: 20pt bold;
color: #bbb
}
body {
font: 11px Open Sans, verdana, helvetica, sans-serif
}
.sm-grid-result-sprite {
font: bold 11px/13px Open Sans, helvetica, sans-serif;
position: relative;
top: 0;
background-color: #f5f3f3;
border: 1px solid #c1c1c1;
border-radius: 3px;
user-select: none;
max-width: 20px;
margin: 0 auto
}
.sm-tooltip-result-sprite {
font: bold 11px/13px Open Sans, helvetica, sans-serif;
position: relative;
top: 0;
background-color: #f5f3f3;
border: 1px solid #c1c1c1;
border-radius: 3px;
user-select: none
}
.sm-result-pass {
color: green;
text-align: center
}
.sm-result-fail {
color: #d74400;
text-align: center
}
.sm-result-na {
color: #909090;
text-align: center
}
.sm-result-nr {
color: #404040;
text-align: center
}
.sm-grid-sprite {
font: bold 10px/13px Open Sans, helvetica, sans-serif;
position: relative;
top: 1px;
background-color: #fff;
border: 1px solid #c1c1c1;
border-radius: 3px;
margin-left: 0;
user-select: none
}
.sm-content-sprite {
color: #fcfcfc;
font: bold 14px Open Sans, helvetica, sans-serif;
position: relative;
top: 5px;
background-color: #6f93db;
padding: 1px 4px;
border: 1px solid #c1c1c1;
border-radius: 3px;
user-select: none;
float: right;
}
.sm-navtree-sprite {
color: #fcfcfc !important;
font: bold 9px Open Sans, helvetica, sans-serif;
position: relative;
top: -1px;
background-color: #6f93db;
padding: 1px 4px 2px;
border-radius: 3px;
margin-left: 11px;
user-select: none
}
.sm-severity-high {
color: #d74400;
background-color: #f5f3f3;
padding: 0 2px
}
.sm-severity-medium {
color: #36c;
background-color: #f5f3f3;
padding: 0 2px
}
.sm-severity-low {
color: green;
background-color: #f5f3f3;
padding: 0 2px
}
.sm-home-widget-image-text-wrap {
float: left;
margin-right: 15px;
width: 125px;
height: 125px;
display: flex;
justify-content: center;
align-items: center
}
.sm-home-widget-text {
padding: 10px 20px;
font: 12px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-home-widget-text a {
color: #000
}
.sm-home-widget-text ul {
list-style-type: square;
margin-left: 20px;
margin-top: 4px;
margin-bottom: 4px
}
.sm-home-widget-text b {
font-weight: 600
}
.sm-home-widget-header-1 {
padding: 10px 20px;
font: 11px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-empty-cell {
font-style: italic;
color: #bbb
}
.sm-empty-cell::after {
content: "No value"
}
.sm-round-panel .ext-mb-content {
font-family: Open Sans, verdana, sans-serif
}
.sm-bare-button .x-btn-bc,
.sm-bare-button .x-btn-bl,
.sm-bare-button .x-btn-br,
.sm-bare-button .x-btn-mc,
.sm-bare-button .x-btn-ml,
.sm-bare-button .x-btn-mr,
.sm-bare-button .x-btn-tc,
.sm-bare-button .x-btn-tl,
.sm-bare-button .x-btn-tr {
background-image: none
}
.x-fieldset {
border-radius: 3px
}
.ext-el-mask {
background-color: rgb(0 0 0 / 0%);
backdrop-filter: blur(3px) grayscale();
animation: fadein 0.25s;
animation-fill-mode: forwards;
}
@keyframes fadein {
from {
opacity: 0;
}
to {
opacity: 1;
}
}
.ext-el-mask-modal {
background-color: rgb(0 0 0 / 50%);
backdrop-filter: blur(1px) grayscale();
animation: fadein 0.25s;
animation-fill-mode: forwards;
position: absolute;
top: 0;
left: 0;
}
.ext-el-mask-msg {
background-image: none;
background-color: unset;
border: none;
top: 50%;
left: 50%;
text-align: center;
transform: translate(-50%, -50%);
}
.ext-el-mask-msg div {
background-color: #dedede;
border: none;
color: #010101;
font-weight: 600;
border-radius: 6px;
margin-bottom: 10px;
}
.ext-el-mask-msg span {
width: 32px;
height: 32px;
border: 3px solid #888;
border-bottom-color: transparent;
border-radius: 50%;
display: inline-block;
box-sizing: border-box;
animation: rotation 1s linear infinite;
}
@keyframes rotation {
0% {
transform: rotate(0deg);
}
100% {
transform: rotate(360deg);
}
}
.sm-round-panel .x-window-header {
color: #111;
font-weight: 700;
font-size: 11px;
font-family: Open Sans, verdana, sans-serif;
background-color: #ccc;
background-image: none;
padding: 6px 8px 5px
}
.x-window-plain .x-window-mc {
border: 0 solid
}
.x-window-plain .x-window-body {
border: 0 solid;
background: 0 0 !important
}
.x-window-bc,
.x-window-bl,
.x-window-br,
.x-window-mc,
.x-window-ml,
.x-window-mr,
.x-window-tc,
.x-window-tl,
.x-window-tr {
background-image: none
}
.sm-review-footer,
.sm-review-form {
background-color: #f7f7f7
}
.x-panel-header {
color: #111
}
.x-tab-panel-body {
border-color: #d0d0d0;
background-color: transparent
}
.x-tab-panel-noborder .x-tab-panel-header-noborder {
border-width: 0
}
.x-tab-strip .x-tab-strip-over span.x-tab-strip-text {
opacity: 1
}
.x-tab-strip .x-tab-with-icon span.x-tab-strip-text {
opacity: .75;
background-position: 0 4px
}
.x-tab-strip .x-tab-strip-active span.x-tab-strip-text {
opacity: 1;
color: #111;
background-position: 0 4px
}
.x-tab-strip-top .x-tab-strip-over .x-tab-left,
.x-tab-strip-top .x-tab-strip-over .x-tab-right,
.x-tab-strip-top .x-tab-strip-over .x-tab-strip-inner {
background-color: #ddd
}
.x-tab-strip-top .x-tab-strip-active .x-tab-left,
.x-tab-strip-top .x-tab-strip-active .x-tab-right,
.x-tab-strip-top .x-tab-strip-active .x-tab-strip-inner {
background-color: hsl(0deg 0% 91%)
}
.x-tab-strip-top .x-tab-left,
.x-tab-strip-top .x-tab-right,
.x-tab-strip-top .x-tab-strip-inner {
background-image: none;
background-color: #ccc;
border-top-left-radius: 6px;
border-top-right-radius: 6px
}
.x-form-search,
.x-form-text,
textarea.x-form-field {
background-color: #fff;
background-image: none;
border: 1px solid #c1c1c1
}
.x-form-search:read-only,
.x-form-text:read-only,
textarea.x-form-field:read-only {
border-color: hsl(0deg 0% 80.31%);
color: gray;
}
.x-form-text:read-only.x-trigger-noedit {
color: #000000
}
.x-tab-panel-footer,
.x-tab-panel-header {
background-color: transparent
}
.sm-home-title {
background-image: url(../img/shield-green-check.svg);
background-size: 48px 48px;
background-position: 18px 12px;
background-repeat: no-repeat;
font: bold 36px Open Sans, helvetica, sans-serif;
color: #333;
padding-bottom: 30px;
padding-left: 74px;
padding-top: 12px
}
#sm-home-oss-sprite {
color: #fcfcfc;
font: bold 10px Open Sans, helvetica, sans-serif;
position: relative;
top: -14px;
background-color: #6f93db;
padding: 1px 4px 2px;
border-radius: 3px;
margin-left: 11px;
user-select: none
}
#sm-home-version-sprite {
color: #fcfcfc;
font: bold 10px Open Sans, helvetica, sans-serif;
position: relative;
top: -14px;
background-color: #569981;
padding: 1px 4px 2px;
border-radius: 3px;
margin-left: 5px;
user-select: none
}
.sm-main-tab-panels-common {
border-radius: 6px
}
ul.x-tab-strip-top {
background-color: transparent;
background-image: none;
border-bottom-color: #ccc;
border-bottom-width: 3px
}
body.x-body-masked .x-window-plain .x-window-mc {
background-color: #f9f9f9
}
td.sort-asc,
td.sort-desc,
td.x-grid3-hd-menu-open,
td.x-grid3-hd-over {
border-left-color: #eee;
border-right-color: #d0d0d0
}
.x-grid3-header,
td.sort-asc .x-grid3-hd-inner,
td.sort-desc .x-grid3-hd-inner,
td.x-grid3-hd-menu-open .x-grid3-hd-inner,
td.x-grid3-hd-over .x-grid3-hd-inner {
background-color: #f0f0f0;
background-image: none
}
.x-toolbar {
border-color: #d0d0d0;
background-color: #e5e5e5;
background-image: none
}
.sm-border-layout-ct {
background-color: #fcfcfc
}
.x-border-layout-ct {
background-color: hsl(220 8% 50% / 1);
}
.sm-round-panel {
border-radius: 6px;
overflow: hidden
}
.sm-round-panel.x-window-dlg {
background-color: hsl(0 0% 95% / 1);
}
.sm-round-panel .x-panel-body,
.sm-round-panel.x-window {
background-color: hsl(0 0% 95% / 1);
}
.sm-round-panel .x-panel-header {
background-color: #ccc;
background-image: none;
padding: 5px 3px 4px 8px
}
.sm-round-inner-panel .x-panel-header {
background-color: hsl(0deg 0% 90%);
background-image: none;
overflow: hidden;
border-radius: 6px 6px 0 0;
padding: 5px 8px 4px 8px;
}
.sm-round-panel .sm-home-widget-body {
background-color: #dedede;
border-radius: 25px;
border: none;
margin: 10px;
height: 400px;
width: 380px;
}
.sm-scroll-home-widget-body {
max-height: 340px;
overflow: auto;
scrollbar-width: thin;
margin-right: 8px;
margin-top: 5px;
}
.sm-user-list {
list-style: none;
max-height: 340px;
padding: 0;
margin-left: 0;
}
.sm-user-item {
padding: 3px;
display: flex;
align-items: left;
}
.sm-user-item::before {
content: "• ";
font-size: 16px;
color: #dedede;
margin-right: 3px;
}
.sm-user-details {
display: flex;
flex-direction: column;
font-size: 13px;
}
.sm-user-name {
font-size: 13px;
font-weight: bold;
}
.sm-user-email {
font-size: 11px;
font-style: italic;
}
.sm-home-widget-header {
background-color: #d3d3d3
}
.sm-home-widget-title {
padding: 10px 20px;
font: bold 18px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-dialog-panel-title {
padding-top: 10px;
padding-right: 20px;
padding-bottom: 10px;
font: bold 18px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-home-widget-subtitle {
padding-top: 5px;
padding-bottom: 5px;
font: bold 14px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-home-widget-collectionName {
font: bold 13px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-banner-unclassified {
background-color: var(--color-marking-unclassified);
color: #fff;
height: 20px
}
.sm-banner-cui {
background-color: var(--color-marking-cui);
color: #fff;
height: 20px
}
.sm-banner-confidential {
background-color: var(--color-marking-confidential);
color: #fff;
height: 20px
}
.sm-banner-secret {
background-color: var(--color-marking-secret);
color: #fff;
height: 20px
}
.sm-banner-topsecret {
background-color: var(--color-marking-topsecret);
color: #fff;
height: 20px
}
.sm-banner-sci {
background-color: var(--color-marking-sci);
color: #000;
height: 20px
}
.sm-banner-body-text {
text-align: center;
font: bold 12px Open Sans, helvetica, sans-serif;
padding-top: 1px
}
.sm-tree-node-collection-review,
.sm-tree-node-create {
font-style: italic
}
.x-grid3-row.x-stigman-cross-department {
opacity: .4
}
::-ms-clear {
display: none
}
.hbss-control .x-grid3-hd-checker,
.hbss-control .x-grid3-row-checker {
background-image: url(../img/hbss-check-sprite.gif)
}
.assignment-grid-item-selected {
font-weight: 700;
background-color: #ffa0a0
}
.icon-department {
background: url(../img/department-16.png) 0 no-repeat !important
}
.icon-refresh {
background: url(../img/reload.svg) 0 0/16px 16px
}
.icon-loading {
background: url(../img/loading.gif);
background-size: 16px 16px;
background-repeat: no-repeat;
}
.icon-add {
background: url(../img/add.svg) 0 0/16px 16px
}
.icon-edit {
background: url(../img/edit.svg) 0 no-repeat !important
}
.icon-del {
background: url(../img/trash.svg) 0 0/16px 16px
}
.icon-remove {
background: url(../img/remove.svg);
}
.icon-save {
background: url(../img/save.gif) 0 no-repeat !important
}
.icon-new-window {
background: url(../img/new_window.gif) 0 no-repeat !important
}
.icon-new-tab {
background: url(../img/new_tab.gif) 0 no-repeat !important
}
.icon-icon-all {
background: url(../img/icon-all.gif) 0 no-repeat !important
}
.icon-excel {
background: url(../img/excel-16.gif) 0 no-repeat !important
}
.sm-rule-header-top,
.sm-rule-content-header-top {
font: bold 22px Open Sans, helvetica, sans-serif
}
.cs-section-five-o-eight {
font: 9px Open Sans, helvetica, sans-serif;
text-decoration: underline;
cursor: pointer
}
.sm-rule-version {
padding: 10px;
font: 10px Open Sans, helvetica, sans-serif
}
.sm-rule-header-sub {
padding: 20px;
font: bold 14px Open Sans, helvetica, sans-serif
}
.sm-rule-body {
padding: 10px 20px;
background-color: #ddd;
border-radius: 6px;
margin-bottom: 6px;
}
.sm-rule-body-title {
font: bold 14px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-rule-body-text {
padding: 10px 20px;
font: 11px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-rule-body-text pre {
white-space: pre-wrap;
font: 11px Open Sans, helvetica, sans-serif
}
.sm-rule-body-table {
width: 100%;
border-collapse: collapse
}
.sm-rule-body-table td {
padding: 2px
}
.sm-reviews-home-body-title {
padding: 10px 20px;
font: bold 14px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-reviews-home-body-text {
padding: 10px 20px;
font: 11px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-reviews-home-tasks {
background-color: #ff5f5f
}
.sm-reviews-home-no-tasks {
background-color: #bbe6b8
}
.sm-rule-body-text li {
margin-top: 5px
}
.sm-feedback-panel-active {
background-color: #ff5f5f
}
.sm-feedback-panel-inactive {
background-color: #fff
}
.sm-feedback-body-title {
padding: 10px 20px;
font: bold 14px Open Sans, helvetica, sans-serif;
color: #36c
}
.sm-feedback-body-text {
padding: 10px 20px;
font: 11px Open Sans, helvetica, sans-serif;
color: #000;
word-wrap: break-word
}
.sm-feedback-body-text li {
margin-top: 5px
}
.deferral-approval-trigger {
background-image: url(../img/trigger2.png) !important
}
.x-form-field,
.x-form-item {
font: 11px Open Sans, helvetica, sans-serif
}
.sm-manual-grid-item {
background-color: #fff
}
.sm-manual-grid-item.x-grid3-row-over {
background-color: #efefef
}
.sm-grid3-row-red {
background-color: #ffa0a0
}
.sm-grid3-row-grey {
background-color: #ddd
}
.sm-grid3-row-orange {
background-color: #fc9
}
.sm-grid3-row-green {
background-color: #bbe6b8
}
.sm-grid3-row-black td {
background-color: #0f0f0f;
color: #fff !important
}
.sm-grid3-row-error td,
.sm-grid3-row-italic td {
background-color: #ffdede !important;
}
.x-grid3-row-over {
border-color: #ddd;
background-color: #efefef;
background-image: none
}
.sm-add-icon {
background-image: url(../img/icons8-add-16.png) !important
}
.sm-copy-icon {
background-image: url(../img/copy.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-clone-icon {
background-image: url(../img/clone.svg) !important;
background-size: 16px 16px
}
.sm-disc-drive {
background-image: url(../img/disc_drive.png) !important
}
.sm-internet-search {
background-image: url(../img/internet_search.png) !important
}
.sm-search-icon {
background-image: url(../img/search.png) !important
}
.sm-filter-icon {
background-image: url(../img/filter.svg);
background-size: 12px 12px
}
.sm-control-panel {
background-image: url(../img/control_panel.png) !important
}
.sm-checklist-icon,
.sm-checklist-tab-icon {
background-image: url(../img/shield-green-check.svg) !important
}
.sm-setting-icon {
background-image: url(../img/gear.svg) !important;
background-size: 16px 16px
}
.sm-export-icon {
background-image: url(../img/download.svg);
background-size: 16px 16px
}
.sm-wrap-lines-icon {
background-image: url(../img/wrap-lines.svg);
background-size: 16px 16px
}
.sm-clear-icon {
background-image: url(../img/clear.svg);
background-size: 16px 16px
}
.sm-stream-icon {
background-image: url(../img/stream.svg);
background-size: 16px 16px
}
.sm-stream-stopped-icon {
background-image: url(../img/stream-stopped.svg);
background-size: 16px 16px
}
.sm-recording-icon {
background-image: url(../img/recording.svg);
background-size: 16px 16px
}
.sm-recording-stopped-icon {
background-image: url(../img/recording-stopped.svg);
background-size: 16px 16px
}
.sm-alert-icon {
background-image: url("data:image/svg+xml,%3C%3Fxml version='1.0' encoding='UTF-8'%3F%3E%3Csvg width='16px' height='16px' fill='%23000000' version='1.1' viewBox='0 0 310.81 310.81' xml:space='preserve' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath d='m305.1 229.1-119.04-186.52c-6.713-10.52-18.172-16.801-30.652-16.801-12.481 0-23.94 6.281-30.651 16.801l-119.04 186.52c-7.145 11.197-7.619 25.39-1.233 37.042 6.386 11.647 18.604 18.883 31.886 18.883h238.08c13.282 0 25.5-7.235 31.888-18.886 6.383-11.649 5.909-25.841-1.236-37.038zm-149.69 24.527c-10.947 0-19.82-8.874-19.82-19.82 0-10.947 8.874-19.821 19.82-19.821 10.947 0 19.82 8.874 19.82 19.821 0 10.946-8.874 19.82-19.82 19.82zm27.472-137.73-9.762 65.727c-1.437 9.675-10.445 16.353-20.119 14.916-7.816-1.161-13.676-7.289-14.881-14.692l-10.601-65.597c-2.468-15.273 7.912-29.655 23.185-32.123s29.655 7.912 32.123 23.185c0.464 2.876 0.448 5.845 0.055 8.584z' fill='%23f38c00'/%3E%3C/svg%3E%0A");
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-import-icon {
background-image: url(../img/upload.svg);
background-size: 16px 16px
}
.sm-asset-icon {
background-image: url(../img/target.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-template-icon {
background-image: url(../img/template.png) !important
}
.sm-library-icon {
background-image: url(../img/library.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-folder-icon {
background-image: url(../img/folder.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-collection-color-icon {
background-image: url(../img/collection-color.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px;
}
.sm-collection-icon,
.sm-collection-tab-icon {
background-image: url(../img/collection.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-department-icon {
background-image: url(../img/department-16.png) !important
}
.sm-user-icon {
background-image: url(../img/user.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-user-unavailable-icon {
background-image: url(../img/user-unavailable.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-users-icon {
background-image: url(../img/users.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-stig-icon {
background-image: url(../img/shield-green-check.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-history-icon {
background-image: url(../img/clock.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-report-icon {
background-image: url(../img/grid.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-trash-icon {
background-image: url(../img/trash.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-chat-icon {
background-image: url(../img/chat-16.png) !important
}
.sm-ackchat-icon,
.sm-newchat-icon,
.sm-unackchat-icon {
background-image: url(../img/message_edit.png) !important
}
.sm-feedback-icon {
background-image: url(../img/feedback-16.gif) !important
}
.sm-feedback-ack-icon {
background-image: url(../img/feedback-ack-16.gif) !important
}
.sm-feedback-unack-icon {
background-image: url(../img/feedback-unack-16.gif) !important
}
.sm-artifact-icon {
background-image: url(../img/page_white_text.png) !important
}
.sm-note-icon {
background-image: url(../img/note-16.png) !important
}
.sm-star-icon {
background-image: url(../img/star.svg) !important
}
.sm-star-icon-16 {
background-image: url(../img/star.svg) !important;
background-size: 16px
}
.sm-assign-icon {
background-image: url(../img/right-arrow-16.png) !important
}
.sm-unlock-icon {
background-image: url(../img/unlock-16.png) !important
}
.sm-lock-icon {
background-image: url(../img/lock.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-ready-icon {
background-image: url(../img/ready-16.png) !important
}
.sm-ready-flip-icon {
background-image: url(../img/ready-flip-16.png) !important
}
.sm-rejected-icon {
background-image: url(../img/rejected-16.png) !important
}
.x-btn-pressed.sm-star-icon {
background-image: url(../img/star.svg) !important
}
.sm-save-icon {
background-image: url(../img/save-16.png) !important
}
.sm-disk-icon {
background-image: url(../img/save-icon.svg) !important;
background-size: 12px
}
.sm-database-save-icon {
background-image: url(../img/database.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-database-icon {
background-image: url(../img/database.svg) !important
}
.sm-table-icon {
background-image: url(../img/table.png) !important
}
.sm-page-edit-icon {
background-image: url(../img/page_edit.png) !important
}
.sm-page-white-get-icon {
background-image: url(../img/page_white_get.png) !important
}
.sm-page-white-put-icon {
background-image: url(../img/page_white_put.png) !important
}
.sm-hbss-disabled-icon {
background-image: url(../img/hbss-check-sprite.gif);
background-position: -23px 0;
background-repeat: no-repeat
}
.sm-hbss-enabled-icon {
background-image: url(../img/hbss-check-sprite.gif);
background-position: 2px 0;
background-repeat: no-repeat
}
.sm-application-go-icon {
background-image: url(../img/application_go.png) !important
}
.sm-list-remove-16-icon {
background-image: url(../img/list-remove-16.png)
}
.sm-scan-assign-icon {
background-image: url(../img/greencheckt.gif)
}
.x-item-disabled .sm-scan-assign-icon {
background-image: url(../img/greycheckt.gif)
}
.sm-scan-unassign-icon {
background-image: url(../img/greydash.gif)
}
.sm-scan-toggleAssign-icon {
background-image: url(../img/icon-all.gif)
}
.sm-zip-icon {
background-image: url(../img/compress.png)
}
.sm-scap-grid-item {
background-color: #e2f2e2
}
.sm-scap-grid-item.x-grid3-row-over {
background-color: #daebda
}
.sm-scap-grid-item.x-grid3-row-selected {
background-color: #cedece !important
}
.sm-cell-red {
background-color: #ffa0a0;
border-right: 1px solid #fff;
border-left: 1px solid #fff
}
.x-grid3-row-selected .sm-cell-red {
filter: brightness(85%)
}
.x-grid3-row-over .sm-cell-red {
background-color: #f7c8c8 !important
}
.x-grid3-row-selected.sm-grid3-row-error .sm-cell-red {
filter: brightness(85%)
}
.sm-cell-orange {
background-color: #fc9;
border-right: 1px solid #fff;
border-left: 1px solid #fff
}
.x-grid3-row-selected .sm-cell-orange {
filter: brightness(85%)
}
.x-grid3-row-over .sm-cell-orange {
background-color: #f7dec4 !important
}
.x-grid3-row-selected.sm-grid3-row-error .sm-cell-orange {
filter: brightness(85%)
}
.sm-cell-green {
background-color: #bbe6b8;
border-right: 1px solid #fff;
border-left: 1px solid #fff
}
.x-grid3-row-selected .sm-cell-green {
filter: brightness(85%)
}
.x-grid3-row-over .sm-cell-green {
background-color: #d5ebd4 !important
}
.x-grid3-row-selected.sm-grid3-row-error .sm-cell-green {
filter: brightness(85%)
}
.sm-cell-grey {
background-color: #ddd;
border-right: 1px solid #fff;
border-left: 1px solid #fff
}
.x-grid3-row-selected .sm-cell-grey {
filter: brightness(85%)
}
.sm-cell-purple {
background-color: plum;
border-right: 1px solid #fff;
border-left: 1px solid #fff
}
.x-grid3-row-selected .sm-cell-purple {
filter: brightness(85%)
}
.x-grid3-row-over .sm-cell-purple {
background-color: #e6c8e6 !important
}
.x-grid3-row-selected.sm-grid3-row-error .sm-cell-purple {
filter: brightness(85%)
}
.sm-cell-peach {
background-color: #fbeb9d
}
.sm-cell-status {
background-color: #ccf;
border-left: 1px solid #fff
}
.x-grid3-row-selected .sm-cell-status {
filter: brightness(85%)
}
.x-grid3-row-over .sm-cell-status {
background-color: #dedef7 !important;
border-left: 1px solid #fff
}
.sm-cell-checklist {
background-image: url(../img/security_firewall_on.png);
background-repeat: no-repeat;
padding-left: 14px !important
}
.sm-cell-pinned {
background-image: url(../img/pin.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
}
.sm-cell-asset {
background-image: url(../img/target.svg);
background-repeat: no-repeat;
background-position: 0 2px;
padding-left: 14px !important
}
.sm-cell-template {
background-image: url(../img/template.png);
background-repeat: no-repeat;
padding-left: 14px !important
}
.custom-stig-users .x-grid3-row-selected .x-grid3-cell-last {
background-image: url(../img/User-Group-icon.png);
background-position: left;
background-repeat: no-repeat
}
.sm-artifact-download-icon {
background-image: url(../img/download.svg)
}
.sm-artifact-edit-icon {
background-image: url(../img/edit-16.png)
}
.x-grid3-row-over .artifact-download {
background-image: url(../img/download.svg);
background-size: 14px 14px;
background-position: 2px 5px;
background-repeat: no-repeat
}
.x-grid3-row-over .artifact-view {
background-image: url(../img/eye.svg);
background-size: 14px 14px;
background-position: 2px 5px;
background-repeat: no-repeat
}
.x-grid3-row-over .artifact-edit {
background-image: url(../img/edit-16.png);
background-size: 14px 14px;
background-position: 2px 5px;
background-repeat: no-repeat
}
.x-grid3-row-over .artifact-delete {
background-image: url(../img/delete.png);
background-size: 14px 14px;
background-position: 2px 5px;
background-repeat: no-repeat
}
.x-grid3-row-over .artifact-download :active,
.x-grid3-row-over .artifact-download:active {
background-image: url(../img/download.svg);
background-size: 14px 14px;
background-position: 4px 10px;
background-repeat: no-repeat
}
.sm-reviews-home-background {
background-color: #fff
}
#artifact-admin .x-grid3-row td,
.artifact-grid .x-grid3-row td {
line-height: 25px
}
.sm-background-blue {
background-color: #eee !important
}
.sm-artifact-file-icon {
position: relative;
top: 3px;
margin-right: 5px
}
.x-grid3-summary-row {
border-left: 1px solid #fff;
border-right: 1px solid #fff;
color: #333;
background: #f1f2f4
}
.x-grid3-summary-row .x-grid3-cell-inner {
font-weight: 700;
padding-bottom: 4px
}
.x-grid-hide-summary .x-grid3-summary-row {
display: none
}
.x-grid3-summary-msg {
padding: 4px 16px;
font-weight: 700
}
.sm-review-action-textarea[disabled],
.sm-review-result-textarea[disabled] {
color: #000;
opacity: 1;
background: 0 0
}
.sm-progress-textarea {
font-size: 8pt;
font-family: Consolas, Courier, monospace
}
.sm-combo-loading {
background-image: url(../img/loading.gif);
background-repeat: no-repeat;
background-position: 2px 1px;
text-indent: 20px
}
.sm-context-menu {
background-image: none
}
.sm-context-menu .x-menu li.x-menu-sep-li {
padding: 0
}
.sm-context-menu-header {
background-color: #d5e4f5;
border: 1px solid #99bbe8;
padding-left: 8px;
font-style: italic;
font-weight: 700
}
.x-toolbar-cell .x-form-checkbox,
.x-toolbar-cell .x-form-radio {
margin-top: 0
}
.ext-chrome .x-toolbar-cell .x-form-checkbox,
.x-toolbar-cell .x-form-radio {
margin-top: 3px
}
.ext-chrome .x-toolbar-cell .x-form-cb-label {
vertical-align: bottom;
top: 1px;
}
.ext-strict .x-small-editor .x-form-text {
line-height: 18px
}
.sm-review-sprite {
color: #161128;
font: 600 10px Open Sans, helvetica, sans-serif;
position: relative;
top: 0px;
background-color: #f2f2f2;
padding: 1px 4px 2px 17px;
border-radius: 3px;
user-select: none;
background-size: 12px 12px;
background-repeat: no-repeat;
background-position: 2px 2px;
border: 1px solid #ccc;
display: inline-block;
margin-left: 0px;
}
.sm-review-sprite-user {
background-image: url(../img/user-60.svg);
width: auto
}
.sm-review-sprite-date {
background-image: url(../img/clock.svg);
width: auto
}
.sm-review-sprite-modified {
background-image: url(../img/shield-green-check.svg)
}
.sm-review-sprite-modified::after {
content: "Modified"
}
.sm-review-sprite-saved {
background-image: url(../img/save-icon-60.svg)
}
.sm-review-sprite-submitted {
background-image: url(../img/ready-16.png)
}
.sm-review-sprite-rejected {
background-image: url(../img/rejected-16.png)
}
.sm-review-sprite-accepted {
background-image: url(../img/star.svg)
}
.sm-review-sprite-saved::after {
content: "Saved"
}
.sm-review-sprite-submitted::after {
content: "Submitted"
}
.sm-review-sprite-rejected::after {
content: "Rejected"
}
.sm-review-sprite-accepted::after {
content: "Accepted"
}
.sm-review-sprite-rule {
background-image: url(../img/shield-green-check.svg)
}
.sm-assessment-icon {
background-image: url(../img/assessment.svg);
}
.sm-review-sprite-asset {
background-image: url(../img/target.svg)
}
.sm-review-sprite-stat-saved {
background-image: url(../img/save-icon-60.svg)
}
.sm-review-sprite-stat-submitted {
background-image: url(../img/ready-16.png)
}
.sm-review-sprite-stat-rejected {
background-image: url(../img/rejected-16.png)
}
.sm-review-sprite-stat-accepted {
background-image: url(../img/star.svg)
}
.sm-review-sprite-stat-result {
padding: 1px 4px 2px 4px;
}
.xtb-text .sm-xtb-sep {
display: inline-block;
position: relative;
top: 2px;
height: 13px;
width: 2px;
margin: 0 5px 0 5px;
background-image: url(../ext/resources/images/default/grid/grid-split.gif);
background-position: center;
background-repeat: no-repeat;
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 300;
src: local('Open Sans Light'), local('OpenSans-Light'), url('../fonts/open-sans-v15-latin-300.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-300.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: italic;
font-weight: 300;
src: local('Open Sans Light Italic'), local('OpenSans-LightItalic'), url('../fonts/open-sans-v15-latin-300italic.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-300italic.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 400;
src: local('Open Sans Regular'), local('OpenSans-Regular'), url('../fonts/open-sans-v15-latin-regular.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-regular.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: italic;
font-weight: 400;
src: local('Open Sans Italic'), local('OpenSans-Italic'), url('../fonts/open-sans-v15-latin-italic.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-italic.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 600;
src: local('Open Sans SemiBold'), local('OpenSans-SemiBold'), url('../fonts/open-sans-v15-latin-600.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-600.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: italic;
font-weight: 600;
src: local('Open Sans SemiBold Italic'), local('OpenSans-SemiBoldItalic'), url('../fonts/open-sans-v15-latin-600italic.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-600italic.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 700;
src: local('Open Sans Bold'), local('OpenSans-Bold'), url('../fonts/open-sans-v15-latin-700.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-700.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: italic;
font-weight: 700;
src: local('Open Sans Bold Italic'), local('OpenSans-BoldItalic'), url('../fonts/open-sans-v15-latin-700italic.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-700italic.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 800;
src: local('Open Sans ExtraBold'), local('OpenSans-ExtraBold'), url('../fonts/open-sans-v15-latin-800.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-800.woff') format('woff')
}
@font-face {
font-family: 'Open Sans';
font-style: italic;
font-weight: 800;
src: local('Open Sans ExtraBold Italic'), local('OpenSans-ExtraBoldItalic'), url('../fonts/open-sans-v15-latin-800italic.woff2') format('woff2'), url('../fonts/open-sans-v15-latin-800italic.woff') format('woff')
}
@font-face {
font-family: 'Ubuntu Mono';
font-style: normal;
font-weight: 400;
src: local(''),
url('../fonts/ubuntu-mono-v15-latin-regular.woff2') format('woff2'),
/* Chrome 26+, Opera 23+, Firefox 39+ */
}
.x-tool.x-tool-import {
background-image: url(../img/upload.svg);
background-repeat: no-repeat;
background-size: 12px 16px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-label {
background-image: url(../img/label.svg);
background-repeat: no-repeat;
background-size: 12px 16px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-collection {
background-image: url(../img/collection.svg);
background-repeat: no-repeat;
background-size: 12px 16px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-manage {
background-image: url(../img/gear.svg);
background-repeat: no-repeat;
background-size: 12px 16px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-download {
background-image: url(../img/download.svg);
background-repeat: no-repeat;
background-size: 16px 20px;
background-position: left;
color: grey;
width: auto;
padding-left: 20px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-report {
background-image: url(../img/grid.svg);
background-repeat: no-repeat;
background-size: 12px 16px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-trash {
background-image: url(../img/trash.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-clone {
background-image: url(../img/clone.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
color: grey;
width: auto;
padding-left: 15px;
font-size: 10px;
line-height: 16px;
}
.x-tool.x-tool-spacer {
width: 10px;
background-image: unset;
}
.x-tool.x-tool-logout {
background-image: url(../img/logout.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
}
.x-tool.x-tool-expand-grid {
background-image: url(../img/expand.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
padding-right: 3px;
}
.x-tool.x-tool-collapse-grids {
background-image: url(../img/collapse.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
padding-right: 3px;
}
.x-tool.x-tool-toggle.x-tool-collapse-west {
background-image: url(../img/collapse-left.svg);
background-repeat: no-repeat;
background-size: 10px 10px;
background-position: 2px 3px;
}
.x-tool.x-tool-expand-west {
background-image: url(../img/collapse-right.svg);
background-repeat: no-repeat;
background-size: 10px 10px;
background-position: 4px 4px;
}
.x-tool.x-tool-toggle.x-tool-collapse-east {
background-image: url(../img/collapse-right.svg);
background-repeat: no-repeat;
background-size: 10px 10px;
background-position: 2px 3px;
}
.x-tool.x-tool-expand-east {
background-image: url(../img/collapse-left.svg);
background-repeat: no-repeat;
background-size: 10px 10px;
background-position: 4px 4px;
}
.x-tool:hover {
filter: brightness(50%)
}
.sm-line-clamp-wrap .x-grid3-cell-inner {
overflow: hidden;
display: -webkit-box;
line-clamp: 1;
-webkit-line-clamp: 1;
-webkit-box-orient: vertical;
white-space: normal;
overflow-wrap: break-word;
}
.sm-line-height-up {
background-image: url(../img/line-height-up.svg);
background-size: 16px 16px;
}
.sm-line-height-down {
background-image: url(../img/line-height-down.svg);
background-size: 16px 16px;
}
.sm-content-stigid {
font-size: 10px;
font-weight: normal;
color: #808080;
}
.sm-direction-rtl {
direction: rtl;
}
.sm-diff-icon {
background-image: url(../img/diff.svg) !important;
background-repeat: no-repeat;
background-size: 16px 16px;
}
.sm-diff-ins {
background-color: hsl(110 62% 90% / 1);
}
.sm-diff-del {
background-color: hsl(0deg 60% 85%);
}
.sm-diff-rule-ins {
background-color: red
}
.sm-diff-rule-del {
background-color: green
}
.sm-toolbar-diff .x-toolbar-ct {
height: 100%;
margin-left: 3px;
}
.sm-toolbar-diff .xtb-spacer {
width: 12px;
}
.x-menu-item-active {
background-image: none;
background-color: #e5e5e5
}
.x-btn-text-icon .x-btn-icon-small-left .x-btn-text {
background-size: 14px 14px;
background-position: 0px 1px;
}
.sm-hover-icon {
opacity: 0.75;
filter: grayscale(50%)
}
.sm-hover-icon:hover {
opacity: 1;
scale: 110%;
filter: grayscale(0%)
}
.sm-warning-header {
background-image: url(../img/red-flag.svg);
background-size: 32px 32px;
background-repeat: no-repeat;
font-weight: 600;
font-size: 20px;
padding-left: 36px;
}
.x-panel-inline-icon {
vertical-align: bottom;
margin-top: 0px;
margin-bottom: 0px;
}
.sm-add-assignment-icon {
background-image: url(../img/add-assignment.svg);
background-size: 18px;
background-repeat: no-repeat;
}
.sm-remove-assignment-icon {
background-image: url(../img/remove-assignment.svg);
background-size: 18px;
background-repeat: no-repeat;
}
.x-dd-drop-nodrop .x-dd-drop-icon {
background-image: url("../img/remove.svg");
background-size: 16px 16px;
}
.x-dd-drop-ok .x-dd-drop-icon {
background-image: url("../img/add.svg");
background-size: 16px 16px;
}
.x-dd-drop-ok-add .x-dd-drop-icon {
background-image: url("../img/add.svg");
background-size: 16px 16px;
}
.sm-round-panel .x-panel-header.sm-selections-panel-header {
background-color: #c3deab;
}
.sm-fieldset-title-with-icon {
background-repeat: no-repeat;
background-size: 14px 14px;
padding-left: 20px;
}
.sm-stig-information-title {
background-image: url(../img/shield-green-check.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
padding-left: 20px;
}
.sm-asset-assignments-title {
background-image: url(../img/target.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
padding-left: 20px;
}
.sm-label-title {
background-image: url(../img/label.svg);
background-repeat: no-repeat;
background-size: 14px 14px;
padding-left: 20px;
}
.sm-grid3-draggable .x-grid3-row-selected .x-grid3-td-checker * {
cursor: default;
}
.sm-grid3-draggable .x-grid3-row-selected *,
.sm-grid3-draggable .x-grid3-row-selected {
cursor: grab;
}
.sm-grabbing *,
.sm-grabbing .sm-grid3-draggable .x-grid3-row-selected *,
.sm-grabbing .sm-grid3-draggable .x-grid3-row-selected {
cursor: url("../img/drag-drop-light.svg"), grabbing;
}
.x-item-disabled {
filter: saturate(0.25)
}
.sm-column-with-icon {
padding-left: 20px;
}
.sm-cell-with-icon {
padding-left: 20px;
line-height: 18px;
}
.sm-match-case-icon {
background-image: url(../img/match-case.svg);
background-size: contain;
}
.sm-match-word-icon {
background-image: url(../img/match-word.svg);
background-size: contain;
}
.sm-browser-icon {
background-image: url(../img/browser.svg);
background-size: 16px;
}
.sm-nodejs-icon {
background-image: url(../img/jsIconGreen.svg);
background-size: 16px;
}
.sm-mysql-icon {
background-image: url(../img/mysql.svg);
background-size: 16px;
}
.sm-json-icon {
background-image: url(../img/json.svg);
background-size: 16px;
}
.sm-login-icon {
background-image: url(../img/login.svg);
background-size: 16px;
}
.x-layout-split {
background-color: transparent;
transition-property: background-color;
transition-duration: 0.25s;
transition-delay: 0s;
}
.x-layout-split:hover {
background-color: hsl(0 0% 66% / 1);
transition-duration: 0.25s;
transition-delay: 0s;
}
.sm-row-disabled {
color: #a15e5e
}
.sm-share-icon {
background-image: url(../img/share.svg);
background-size: 16px;
}
.xg-hmenu-sort-asc .x-menu-item-icon {
background-image: url("../img/up.svg");
background-size: 16px 16px;
}
.xg-hmenu-sort-desc .x-menu-item-icon {
background-image: url("../img/down.svg");
background-size: 16px 16px;
}
.x-cols-icon {
background-image: url("../img/columns.svg");
background-size: 16px 16px;
}
.sort-asc .x-grid3-sort-icon {
background-image: url("../img/up.svg");
background-size: 10px;
background-position: center
}
.sort-desc .x-grid3-sort-icon {
background-image: url("../img/down.svg");
background-size: 10px;
background-position: center
}
.sm-circle-icon {
background-image: url("../img/circle.svg");
background-size: 7px 7px;
background-position: top 5px left 5px;
}
.x-menu {
background-image: none
}
.sm-appinfo-message {
background-color: #e0e0e0;
width: 330px;
height: 60px;
color: #484848;
padding: 7px;
}
.sm-info-circle-icon {
background-image: url(../img/info-circle.svg) !important;
background-size: 16px 16px;
}
.sm-render-zero {
color: #cccccc
}
.sm-appinfo-message a:link {
text-decoration: none
}
.sm-appinfo-message .sm-share-icon {
padding-left: 14px;
background-size: 12px 12px;
background-repeat: no-repeat;
background-position: left;
font-weight: 600;
}
.sm-appinfo-message .sm-email {
font-weight: 600;
color: cadetblue;
}
.sm-grid-cell-role {
height: 28px;
line-height: 28px;
}
.x-grid3-row-over .sm-grid-cell-with-menu {
background-image: url("../img/tree-elbow-minus.svg");
background-repeat: no-repeat;
background-size: 12px 12px;
background-position: right 3px center;
}
.sm-vbox-disabled .x-box-inner {
filter: opacity(0.25)
}
.sm-label-sprite.sm-sprite-read {
float: right;
background-color: #757c8a;
color: #eee;
}
.sm-label-sprite.sm-sprite-readwrite {
float: right;
background-color: #976a6e;
color: #eee;
}
.sm-row-readonly-icon {
background-size: 14px;
background-repeat: no-repeat;
background-image: url(../img/read-only.svg);
background-position: 0px 2px;
height: 18px;
}
.sm-read-only-icon {
background-size: 16px 16px;
background-image: url(../img/read-only.svg);
}
.sm-checklist-read,
.sm-checklist-read-write {
float: right;
color: #f2f2f2;
}
.sm-checklist-read-write {
background-color: hsl(145.08deg 100% 23.92%);
}
.sm-checklist-read {
background-color: hsl(330 55% 24% / 1);
}
.sm-sprite-U {
background-color: var(--color-marking-unclassified);
border-radius: 6px;
}
.sm-sprite-U::before {
content: "U";
font-weight: 800;
margin: 2px;
}
.sm-sprite-CUI {
background-color: var(--color-marking-cui);
border-radius: 6px;
}
.sm-sprite-CUI::before {
content: "CUI";
font-weight: 800;
margin: 2px;
}
.sm-sprite-FOUO::before {
content: "FOUO";
font-weight: 800;
margin: 2px;
}
.sm-sprite-FOUO {
background-color: var(--color-marking-unclassified);
border-radius: 6px;
}
.sm-flexbox-layout-ct {
display: flex;
flex-wrap: wrap;
overflow: auto;
scrollbar-width: none;
align-content: flex-start;
}
.sm-flexbox-layout-ct:hover {
scrollbar-width: auto;
}
.sm-status-csv {
color: #eee;
padding: 4px;
border-radius: 10px;
font-weight: bold;
font-size: 12px;
}
.sm-error-icon {
background-image: url(../img/x-red-svg.svg);
}
.sm-cora-container {
display: flex;
flex-direction: row;
justify-content: space-evenly;
}
.sm-cora-box-left {
display: flex;
flex-direction: column;
justify-content: space-between;
border-radius: 10px;
width: fit-content;
}
.sm-cora-box-title {
text-align: center;
font-weight: 600;
}
.sm-cora-cat {
color: #111;
border-radius: 5px;
border: 1px solid #bbb;
font-weight: 700;
text-align: right;
padding: 0px 6px;
margin: 0px 12px;
}
.sm-cat1 {
background-color: var(--color-severity-high);
}
.sm-cat2 {
background-color: var(--color-severity-medium);
}
.sm-cat3 {
background-color: var(--color-severity-low);
}
.sm-cat1::before {
content: "CAT 1";
float: left;
font-weight: 600
}
.sm-cat2::before {
content: "CAT 2";
float: left;
font-weight: 600
}
.sm-cat3::before {
content: "CAT 3";
float: left;
font-weight: 600
}
.sm-cora-box-right {
padding: 6px;
border-radius: 10px;
border: 1px solid #bbb;
text-align: center;
width: 110px;
}
.sm-cora-score-header {
font-weight: 600;
font-size: larger;
color: #111;
}
.sm-cora-score-risk-level {
font-size: 11px;
font-weight: 800;
}
.sm-risk-indicator {
margin: auto;
font-weight: 800;
font-size: 18px;
color: #111;
}
.sm-cora-risk-very-high {
background-color: var(--color-risk-very-high);
}
.sm-cora-risk-very-high .sm-cora-score-risk-level {
color: var(--color-risk-very-high-text);
}
.sm-cora-risk-high {
background-color: var(--color-risk-high);
}
.sm-cora-risk-high .sm-cora-score-risk-level {
color: var(--color-risk-high-text);
}
.sm-cora-risk-moderate {
background-color: var(--color-risk-moderate);
}
.sm-cora-risk-moderate .sm-cora-score-risk-level {
color: var(--color-risk-moderate-text);
}
.sm-cora-risk-low {
background-color: var(--color-risk-low);
}
.sm-cora-risk-low .sm-cora-score-risk-level {
color: var(--color-risk-low-text);
}
.sm-cora-risk-very-low {
background-color: var(--color-risk-very-low);
}
.sm-cora-risk-very-low .sm-cora-score-risk-level {
color: var(--color-risk-very-low-text);
}
.x-grid3-scroller {
overflow-x: auto;
scrollbar-color: var(--color-scrollbar-idle) transparent;
transition: scrollbar-color 0.125s;
}
.x-grid3-scroller:hover {
overflow-x: auto;
scrollbar-color: var(--color-scrollbar-hover) transparent;
}
.sm-round-panel .x-panel-body {
scrollbar-color: var(--color-scrollbar-idle) transparent;
transition: scrollbar-color 0.125s;
}
.sm-round-panel .x-panel-body:hover {
scrollbar-color: var(--color-scrollbar-hover) transparent;
}
.sm-multi-value-grid .x-grid3-row-selected {
background-color: transparent !important;
}
.x-menu-list-item:has(> .x-hide-display) {
padding: 0
}
.sm-logs-icon {
background-image: url(../img/logs.svg) !important;
background-size: 16px 16px
}
.sm-log-line {
width: 100%;
padding: 0.2em 0;
border-bottom: 1px solid #4b4b4b;
font-family: monospace;
font-size: 10px;
}
.sm-log-line:hover {
background-color: color-mix(in srgb, currentColor 10%, transparent);
}
.sm-log-line.selected {
background-color: color-mix(in srgb, currentColor 20%, transparent);
}
.sm-log-line[data-component="logSocket"] {
color: #8b1fff;
}
.sm-log-line[data-component="jwksCache"] {
color: #ad611a;
}
.sm-log-line[data-component="static"] {
color: #808080;
}
.sm-log-line[data-component="rest"] {
color: #00a900;
}
.sm-log-line[data-level="1"] {
color: red;
}
.sm-log-line[data-level="2"] {
color: orange;
}
.sm-log-panel-body {
cursor: pointer;
overflow: auto;
text-wrap-mode: nowrap;
}
.sm-log-wrapper {
padding: 0 0.2em;
display: table;
}
.sm-http-status-sprite {
font: 600 10px/14px Open Sans, helvetica, sans-serif;
top: 0;
padding: 0 5px;
border-radius: 3px;
margin-left: 3px;
white-space: nowrap
}
.sm-http-status-200 {
background-color: var(--color-http-status-200);
}
.sm-http-status-300 {
background-color: var(--color-http-status-300);
}
.sm-http-status-400 {
background-color: var(--color-http-status-400);
}
.sm-http-status-500 {
background-color: var(--color-http-status-500);
}
.x-toolbar-cell .x-form-check-wrap {
margin-bottom: 4px;
margin-right: 4px;
}
.sm-log-panel .x-toolbar-ct {
padding: 0
}
.sm-job-icon {
background-image: url(../img/job.svg)!important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-job-run-icon {
background-image: url(../img/job-run.svg)!important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-job-task-icon {
background-image: url(../img/job-task.svg)!important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-run-output-icon {
background-image: url(../img/logs.svg)!important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-job-event-icon {
background-image: url(../img/clock.svg)!important;
background-repeat: no-repeat;
background-size: 16px 16px
}
.sm-move-up-icon {
background-image: url(../img/move-up.svg)!important;
background-repeat: no-repeat;
background-size: 18px
}
.sm-move-down-icon {
background-image: url(../img/move-down.svg)!important;
background-repeat: no-repeat;
background-size: 18px
}
.sm-task-description {
font-size: smaller;
font-style: italic;
color: #808080;
line-height: 12px;
padding-left: 6px;
}
.sm-job-sprite {
font: 600 10px/14px Open Sans,helvetica,sans-serif;
top: 0;
padding: 0 5px;
border-radius: 3px;
margin-left: 3px;
white-space: nowrap;
line-height: 16px;
}
.sm-job-sprite.sm-job-scheduled {
background-color: var(--color-job-scheduled)
}
.sm-job-sprite.sm-job-unscheduled {
background-color: var(--color-job-unscheduled)
}
.sm-job-sprite.sm-job-run-state-completed {
background-color: var(--color-job-run-state-completed);
}
.sm-job-sprite.sm-job-run-state-running {
background-color: var(--color-job-run-state-running);
}
.sm-job-sprite.sm-job-run-state-failed {
background-color: var(--color-job-run-state-failed);
}
.sm-job-sprite.sm-job-run-state-missing {
background-color: var(--color-job-run-state-missing);
}
.sm-job-sprite.sm-job-run-state-shutdown {
background-color: var(--color-job-run-state-failed);
}
.sm-round-panel.sm-offline-modal {
background-color: hsl(0 61% 64% / 1);
}
.sm-round-panel.sm-unavailable-modal {
background-color: hsl(26.39deg 62.3% 64.31%);
}
.sm-icon-column {
padding-left: 20px;
background-size: 14px;
}
.sm-job-event-disabled {
opacity: 50%;
}
================================================
FILE: client/src/ext/INCLUDE_ORDER.txt
================================================
All adapter related files below are located in
/adapters// of this zip file.
Your include order should be:
Ext Stand-alone
-------------------------------------------------------------------
ext-base.js
ext-all.js (or your choice of files)
Yahoo! UI (.12+)
-------------------------------------------------------------------
yui-utilities.js
ext-yui-adapter.js
ext-all.js (or your choice of files)
jQuery (1.1+)
-------------------------------------------------------------------
jquery.js
ext-jquery-adapter.js
ext-all.js (or your choice of files)
Prototype (1.5+) / Scriptaculous (1.7+)
-------------------------------------------------------------------
prototype.js
scriptaculous.js?load=effects (or whatever you want to load)
ext-prototype-adapter.js
ext-all.js (or your choice of files)
See the examples folders for more examples.
================================================
FILE: client/src/ext/adapter/ext/ext-base-debug.js
================================================
/*
This file is part of Ext JS 3.4
Copyright (c) 2011-2013 Sencha Inc
Contact: http://www.sencha.com/contact
GNU General Public License Usage
This file may be used under the terms of the GNU General Public License version 3.0 as
published by the Free Software Foundation and appearing in the file LICENSE included in the
packaging of this file.
Please review the following information to ensure the GNU General Public License version 3.0
requirements will be met: http://www.gnu.org/copyleft/gpl.html.
If you are unsure which license is appropriate for your use, please contact the sales department
at http://www.sencha.com/contact.
Build date: 2013-04-03 15:07:25
*/
// for old browsers
window.undefined = window.undefined;
/**
* @class Ext
* Ext core utilities and functions.
* @singleton
*/
Ext = {
/**
* The version of the framework
* @type String
*/
version : '3.4.1.1',
versionDetail : {
major : 3,
minor : 4,
patch : 1.1
}
};
/**
* Copies all the properties of config to obj.
* @param {Object} obj The receiver of the properties
* @param {Object} config The source of the properties
* @param {Object} defaults A different object that will also be applied for default values
* @return {Object} returns obj
* @member Ext apply
*/
Ext.apply = function(o, c, defaults){
// no "this" reference for friendly out of scope calls
if(defaults){
Ext.apply(o, defaults);
}
if(o && c && typeof c == 'object'){
for(var p in c){
o[p] = c[p];
}
}
return o;
};
(function(){
var idSeed = 0,
toString = Object.prototype.toString,
ua = navigator.userAgent.toLowerCase(),
check = function(r){
return r.test(ua);
},
DOC = document,
docMode = DOC.documentMode,
isStrict = DOC.compatMode == "CSS1Compat",
isOpera = check(/opera/),
isChrome = check(/\bchrome\b/),
isWebKit = check(/webkit/),
isSafari = !isChrome && check(/safari/),
isSafari2 = isSafari && check(/applewebkit\/4/), // unique to Safari 2
isSafari3 = isSafari && check(/version\/3/),
isSafari4 = isSafari && check(/version\/4/),
isIE = !isOpera && check(/msie/),
isIE7 = isIE && ((check(/msie 7/) && docMode != 8 && docMode != 9 && docMode != 10) || docMode == 7),
isIE8 = isIE && ((check(/msie 8/) && docMode != 7 && docMode != 9 && docMode != 10) || docMode == 8),
isIE9 = isIE && ((check(/msie 9/) && docMode != 7 && docMode != 8 && docMode != 10) || docMode == 9),
isIE10 = isIE && ((check(/msie 10/) && docMode != 7 && docMode != 8 && docMode != 9) || docMode == 10),
isIE6 = isIE && check(/msie 6/),
isIE9m = isIE && (isIE6 || isIE7 || isIE8 || isIE9),
isGecko = !isWebKit && check(/gecko/),
isGecko2 = isGecko && check(/rv:1\.8/),
isGecko3 = isGecko && check(/rv:1\.9/),
isBorderBox = isIE9m && !isStrict,
isWindows = check(/windows|win32/),
isMac = check(/macintosh|mac os x/),
isAir = check(/adobeair/),
isLinux = check(/linux/),
isSecure = /^https/i.test(window.location.protocol),
noArgs = [],
nonEnumerables = [],
emptyFn = Ext.emptyFn,
t = Ext.apply({}, {
constructor: emptyFn,
toString: emptyFn,
valueOf: emptyFn
}),
callOverrideParent = function () {
var method = callOverrideParent.caller.caller; // skip callParent (our caller)
return method.$owner.prototype[method.$name].apply(this, arguments);
};
if (t.constructor !== emptyFn) {
nonEnumerables.push('constructor');
}
if (t.toString !== emptyFn) {
nonEnumerables.push('toString');
}
if (t.valueOf !== emptyFn) {
nonEnumerables.push('valueOf');
}
if (!nonEnumerables.length) {
nonEnumerables = null;
}
// Create the abstract Base class to provide an empty constructor and callParent implementations
function Base () {
//
}
Ext.apply(Base, {
$isClass: true,
callParent: function (args) {
var method;
// This code is intentionally inlined for the least number of debugger stepping
return (method = this.callParent.caller) && (method.$previous ||
((method = method.$owner ? method : method.caller) &&
method.$owner.superclass.self[method.$name])).apply(this, args || noArgs);
}
});
Base.prototype = {
constructor: function() {
},
callParent: function(args) {
// NOTE: this code is deliberately as few expressions (and no function calls)
// as possible so that a debugger can skip over this noise with the minimum number
// of steps. Basically, just hit Step Into until you are where you really wanted
// to be.
var method,
superMethod = (method = this.callParent.caller) && (method.$previous ||
((method = method.$owner ? method : method.caller) &&
method.$owner.superclass[method.$name]));
return superMethod.apply(this, args || noArgs);
}
};
// remove css image flicker
if(isIE6){
try{
DOC.execCommand("BackgroundImageCache", false, true);
}catch(e){}
}
Ext.apply(Ext, {
/**
* URL to a blank file used by Ext when in secure mode for iframe src and onReady src to prevent
* the IE insecure content warning ('about:blank' , except for IE in secure mode, which is 'javascript:""' ).
* @type String
*/
SSL_SECURE_URL : isSecure && isIE ? 'javascript:""' : 'about:blank',
/**
* True if the browser is in strict (standards-compliant) mode, as opposed to quirks mode
* @type Boolean
*/
isStrict : isStrict,
/**
* True if the page is running over SSL
* @type Boolean
*/
isSecure : isSecure,
/**
* True when the document is fully initialized and ready for action
* @type Boolean
*/
isReady : false,
/**
* True if the {@link Ext.Fx} Class is available
* @type Boolean
* @property enableFx
*/
/**
* HIGHLY EXPERIMENTAL
* True to force css based border-box model override and turning off javascript based adjustments. This is a
* runtime configuration and must be set before onReady.
* @type Boolean
*/
enableForcedBoxModel : false,
/**
* True to automatically uncache orphaned Ext.Elements periodically (defaults to true)
* @type Boolean
*/
enableGarbageCollector : true,
/**
* True to automatically purge event listeners during garbageCollection (defaults to false).
* @type Boolean
*/
enableListenerCollection : false,
/**
* EXPERIMENTAL - True to cascade listener removal to child elements when an element is removed.
* Currently not optimized for performance.
* @type Boolean
*/
enableNestedListenerRemoval : false,
/**
* Indicates whether to use native browser parsing for JSON methods.
* This option is ignored if the browser does not support native JSON methods.
* Note: Native JSON methods will not work with objects that have functions.
* Also, property names must be quoted, otherwise the data will not parse. (Defaults to false)
* @type Boolean
*/
USE_NATIVE_JSON : false,
/**
* Copies all the properties of config to obj if they don't already exist.
* @param {Object} obj The receiver of the properties
* @param {Object} config The source of the properties
* @return {Object} returns obj
*/
applyIf : function(o, c){
if(o){
for(var p in c){
if(!Ext.isDefined(o[p])){
o[p] = c[p];
}
}
}
return o;
},
/**
* Generates unique ids. If the element already has an id, it is unchanged
* @param {Mixed} el (optional) The element to generate an id for
* @param {String} prefix (optional) Id prefix (defaults "ext-gen")
* @return {String} The generated Id.
*/
id : function(el, prefix){
el = Ext.getDom(el, true) || {};
if (!el.id) {
el.id = (prefix || "ext-gen") + (++idSeed);
}
return el.id;
},
/**
* Extends one class to create a subclass and optionally overrides members with the passed literal. This method
* also adds the function "override()" to the subclass that can be used to override members of the class.
* For example, to create a subclass of Ext GridPanel:
*
MyGridPanel = Ext.extend(Ext.grid.GridPanel, {
constructor: function(config) {
// Create configuration for this Grid.
var store = new Ext.data.Store({...});
var colModel = new Ext.grid.ColumnModel({...});
// Create a new config object containing our computed properties
// *plus* whatever was in the config parameter.
config = Ext.apply({
store: store,
colModel: colModel
}, config);
MyGridPanel.superclass.constructor.call(this, config);
// Your postprocessing here
},
yourMethod: function() {
// etc.
}
});
*
* This function also supports a 3-argument call in which the subclass's constructor is
* passed as an argument. In this form, the parameters are as follows:
*
* subclass : Function The subclass constructor.
* superclass : Function The constructor of class being extended
* overrides : Object A literal with members which are copied into the subclass's
* prototype, and are therefore shared among all instances of the new class.
*
*
* @param {Function} superclass The constructor of class being extended.
* @param {Object} overrides A literal with members which are copied into the subclass's
* prototype, and are therefore shared between all instances of the new class.
* This may contain a special member named constructor . This is used
* to define the constructor of the new class, and is returned. If this property is
* not specified, a constructor is generated and returned which just calls the
* superclass's constructor passing on its parameters.
* It is essential that you call the superclass constructor in any provided constructor. See example code.
* @return {Function} The subclass constructor from the overrides parameter, or a generated one if not provided.
*/
extend : function(){
// inline overrides
var io = function(o){
for(var m in o){
this[m] = o[m];
}
};
var oc = Object.prototype.constructor;
return function(sb, sp, overrides){
if(typeof sp == 'object'){
overrides = sp;
sp = sb;
sb = overrides.constructor != oc ? overrides.constructor : function(){sp.apply(this, arguments);};
}
var F = function(){},
sbp,
spp = sp.prototype;
F.prototype = spp;
sbp = sb.prototype = new F();
sbp.constructor=sb;
sb.superclass=spp;
if(spp.constructor == oc){
spp.constructor=sp;
}
sb.override = function(o){
Ext.override(sb, o);
};
sbp.superclass = sbp.supr = (function(){
return spp;
});
sbp.override = io;
Ext.override(sb, overrides);
sb.extend = function(o){return Ext.extend(sb, o);};
return sb;
};
}(),
global: (function () {
return this;
})(),
Base: Base,
namespaceCache: {},
createNamespace: function (namespaceOrClass, isClass) {
var cache = Ext.namespaceCache,
namespace = isClass ? namespaceOrClass.substring(0, namespaceOrClass.lastIndexOf('.'))
: namespaceOrClass,
ns = cache[namespace],
i, n, part, parts, partials;
if (!ns) {
ns = Ext.global;
if (namespace) {
partials = [];
parts = namespace.split('.');
for (i = 0, n = parts.length; i < n; ++i) {
part = parts[i];
ns = ns[part] || (ns[part] = {});
partials.push(part);
cache[partials.join('.')] = ns; // build up prefixes as we go
}
}
}
return ns;
},
getClassByName: function (className) {
var parts = className.split('.'),
cls = Ext.global,
n = parts.length,
i;
for (i = 0; cls && i < n; ++i) {
cls = cls[parts[i]];
}
return cls || null;
},
addMembers: function (cls, target, members, handleNonEnumerables) {
var i, name, member;
for (name in members) {
if (members.hasOwnProperty(name)) {
member = members[name];
if (typeof member == 'function') {
member.$owner = cls;
member.$name = name;
}
target[name] = member;
}
}
if (handleNonEnumerables && nonEnumerables) {
for (i = nonEnumerables.length; i-- > 0; ) {
name = nonEnumerables[i];
if (members.hasOwnProperty(name)) {
member = members[name];
if (typeof member == 'function') {
member.$owner = cls;
member.$name = name;
}
target[name] = member;
}
}
}
},
/**
* @method
* Defines a class or override. A basic class is defined like this:
*
* Ext.define('My.awesome.Class', {
* someProperty: 'something',
*
* someMethod: function(s) {
* alert(s + this.someProperty);
* }
*
* ...
* });
*
* var obj = new My.awesome.Class();
*
* obj.someMethod('Say '); // alerts 'Say something'
*
* To create an anonymous class, pass `null` for the `className`:
*
* Ext.define(null, {
* constructor: function () {
* // ...
* }
* });
*
* In some cases, it is helpful to create a nested scope to contain some private
* properties. The best way to do this is to pass a function instead of an object
* as the second parameter. This function will be called to produce the class
* body:
*
* Ext.define('MyApp.foo.Bar', function () {
* var id = 0;
*
* return {
* nextId: function () {
* return ++id;
* }
* };
* });
*
* When using this form of `Ext.define`, the function is passed a reference to its
* class. This can be used as an efficient way to access any static properties you
* may have:
*
* Ext.define('MyApp.foo.Bar', function (Bar) {
* return {
* statics: {
* staticMethod: function () {
* // ...
* }
* },
*
* method: function () {
* return Bar.staticMethod();
* }
* };
* });
*
* To define an override, include the `override` property. The content of an
* override is aggregated with the specified class in order to extend or modify
* that class. This can be as simple as setting default property values or it can
* extend and/or replace methods. This can also extend the statics of the class.
*
* One use for an override is to break a large class into manageable pieces.
*
* // File: /src/app/Panel.js
*
* Ext.define('My.app.Panel', {
* extend: 'Ext.panel.Panel',
*
* constructor: function (config) {
* this.callParent(arguments); // calls Ext.panel.Panel's constructor
* //...
* },
*
* statics: {
* method: function () {
* return 'abc';
* }
* }
* });
*
* // File: /src/app/PanelPart2.js
* Ext.define('My.app.PanelPart2', {
* override: 'My.app.Panel',
*
* constructor: function (config) {
* this.callParent(arguments); // calls My.app.Panel's constructor
* //...
* }
* });
*
* Another use of overrides is to provide optional parts of classes that can be
* independently required. In this case, the class may even be unaware of the
* override altogether.
*
* Ext.define('My.ux.CoolTip', {
* override: 'Ext.tip.ToolTip',
*
* constructor: function (config) {
* this.callParent(arguments); // calls Ext.tip.ToolTip's constructor
* //...
* }
* });
*
* Overrides can also contain statics:
*
* Ext.define('My.app.BarMod', {
* override: 'Ext.foo.Bar',
*
* statics: {
* method: function (x) {
* return this.callParent([x * 2]); // call Ext.foo.Bar.method
* }
* }
* });
*
* @param {String} className The class name to create in string dot-namespaced format, for example:
* 'My.very.awesome.Class', 'FeedViewer.plugin.CoolPager'
* It is highly recommended to follow this simple convention:
* - The root and the class name are 'CamelCased'
* - Everything else is lower-cased
* Pass `null` to create an anonymous class.
* @param {Object} data The key - value pairs of properties to apply to this class. Property names can be of any valid
* strings, except those in the reserved listed below:
* - `mixins`
* - `statics`
* - `config`
* - `alias`
* - `self`
* - `singleton`
* - `alternateClassName`
* - `override`
*
* @param {Function} createdFn Optional callback to execute after the class is created, the execution scope of which
* (`this`) will be the newly created class itself.
* @return {Ext.Base}
* @markdown
* @member Ext
* @method define
*/
define: function (className, body, createdFn) {
var override = body.override,
cls, extend, name, namespace;
if (override) {
delete body.override;
cls = Ext.getClassByName(override);
Ext.override(cls, body);
} else {
if (className) {
namespace = Ext.createNamespace(className, true);
name = className.substring(className.lastIndexOf('.')+1);
}
cls = function ctor () {
this.constructor.apply(this, arguments);
}
if (className) {
cls.displayName = className;
}
cls.$isClass = true;
cls.callParent = Ext.Base.callParent;
if (typeof body == 'function') {
body = body(cls);
}
extend = body.extend;
if (extend) {
delete body.extend;
if (typeof extend == 'string') {
extend = Ext.getClassByName(extend);
}
} else {
extend = Base;
}
Ext.extend(cls, extend, body);
if (cls.prototype.constructor === cls) {
delete cls.prototype.constructor;
}
// Not extending a class which derives from Base...
if (!cls.prototype.$isClass) {
Ext.applyIf(cls.prototype, Base.prototype);
}
cls.prototype.self = cls;
if (body.xtype) {
Ext.reg(body.xtype, cls);
}
cls = body.singleton ? new cls() : cls;
if (className) {
namespace[name] = cls;
}
}
if (createdFn) {
createdFn.call(cls);
}
return cls;
},
/**
* Overrides members of the specified `target` with the given values.
*
* If the `target` is a function, it is assumed to be a constructor and the contents
* of `overrides` are applied to its `prototype` using {@link Ext#apply Ext.apply}.
*
* If the `target` is an instance of a class created using {@link #define},
* the `overrides` are applied to only that instance. In this case, methods are
* specially processed to allow them to use {@link Ext.Base#callParent}.
*
* var panel = new Ext.Panel({ ... });
*
* Ext.override(panel, {
* initComponent: function () {
* // extra processing...
*
* this.callParent();
* }
* });
*
* If the `target` is none of these, the `overrides` are applied to the `target`
* using {@link Ext#apply Ext.apply}.
*
* Please refer to {@link Ext#define Ext.define} for further details.
*
* @param {Object} target The target to override.
* @param {Object} overrides The properties to add or replace on `target`.
* @method override
*/
override: function (target, overrides) {
var proto, statics;
if (overrides) {
if (target.$isClass) {
statics = overrides.statics;
if (statics) {
delete overrides.statics;
}
Ext.addMembers(target, target.prototype, overrides, true);
if (statics) {
Ext.addMembers(target, target, statics);
}
} else if (typeof target == 'function') {
proto = target.prototype;
Ext.apply(proto, overrides);
if(Ext.isIE && overrides.hasOwnProperty('toString')){
proto.toString = overrides.toString;
}
} else {
var owner = target.self,
name, value;
if (owner && owner.$isClass) {
for (name in overrides) {
if (overrides.hasOwnProperty(name)) {
value = overrides[name];
if (typeof value == 'function') {
//
if (owner.$className) {
value.displayName = owner.$className + '#' + name;
}
//
value.$name = name;
value.$owner = owner;
value.$previous = target.hasOwnProperty(name)
? target[name] // already hooked, so call previous hook
: callOverrideParent; // calls by name on prototype
}
target[name] = value;
}
}
} else {
Ext.apply(target, overrides);
if (!target.constructor.$isClass) {
target.constructor.prototype.callParent = Base.prototype.callParent;
target.constructor.callParent = Base.callParent;
}
}
}
}
},
/**
* Creates namespaces to be used for scoping variables and classes so that they are not global.
* Specifying the last node of a namespace implicitly creates all other nodes. Usage:
*
Ext.namespace('Company', 'Company.data');
Ext.namespace('Company.data'); // equivalent and preferable to above syntax
Company.Widget = function() { ... }
Company.data.CustomStore = function(config) { ... }
* @param {String} namespace1
* @param {String} namespace2
* @param {String} etc
* @return {Object} The namespace object. (If multiple arguments are passed, this will be the last namespace created)
* @method namespace
*/
namespace : function(){
var len1 = arguments.length,
i = 0,
len2,
j,
main,
ns,
sub,
current;
for(; i < len1; ++i) {
main = arguments[i];
ns = arguments[i].split('.');
current = window[ns[0]];
if (current === undefined) {
current = window[ns[0]] = {};
}
sub = ns.slice(1);
len2 = sub.length;
for(j = 0; j < len2; ++j) {
current = current[sub[j]] = current[sub[j]] || {};
}
}
return current;
},
/**
* Takes an object and converts it to an encoded URL. e.g. Ext.urlEncode({foo: 1, bar: 2}); would return "foo=1&bar=2". Optionally, property values can be arrays, instead of keys and the resulting string that's returned will contain a name/value pair for each array value.
* @param {Object} o
* @param {String} pre (optional) A prefix to add to the url encoded string
* @return {String}
*/
urlEncode : function(o, pre){
var empty,
buf = [],
e = encodeURIComponent;
Ext.iterate(o, function(key, item){
empty = Ext.isEmpty(item);
Ext.each(empty ? key : item, function(val){
buf.push('&', e(key), '=', (!Ext.isEmpty(val) && (val != key || !empty)) ? (Ext.isDate(val) ? Ext.encode(val).replace(/"/g, '') : e(val)) : '');
});
});
if(!pre){
buf.shift();
pre = '';
}
return pre + buf.join('');
},
/**
* Takes an encoded URL and and converts it to an object. Example:
Ext.urlDecode("foo=1&bar=2"); // returns {foo: "1", bar: "2"}
Ext.urlDecode("foo=1&bar=2&bar=3&bar=4", false); // returns {foo: "1", bar: ["2", "3", "4"]}
* @param {String} string
* @param {Boolean} overwrite (optional) Items of the same name will overwrite previous values instead of creating an an array (Defaults to false).
* @return {Object} A literal with members
*/
urlDecode : function(string, overwrite){
if(Ext.isEmpty(string)){
return {};
}
var obj = {},
pairs = string.split('&'),
d = decodeURIComponent,
name,
value;
Ext.each(pairs, function(pair) {
pair = pair.split('=');
name = d(pair[0]);
value = d(pair[1]);
obj[name] = overwrite || !obj[name] ? value :
[].concat(obj[name]).concat(value);
});
return obj;
},
/**
* Appends content to the query string of a URL, handling logic for whether to place
* a question mark or ampersand.
* @param {String} url The URL to append to.
* @param {String} s The content to append to the URL.
* @return (String) The resulting URL
*/
urlAppend : function(url, s){
if(!Ext.isEmpty(s)){
return url + (url.indexOf('?') === -1 ? '?' : '&') + s;
}
return url;
},
/**
* Converts any iterable (numeric indices and a length property) into a true array
* Don't use this on strings. IE doesn't support "abc"[0] which this implementation depends on.
* For strings, use this instead: "abc".match(/./g) => [a,b,c];
* @param {Iterable} the iterable object to be turned into a true Array.
* @return (Array) array
*/
toArray : function(){
return isIE ?
function(a, i, j, res){
res = [];
for(var x = 0, len = a.length; x < len; x++) {
res.push(a[x]);
}
return res.slice(i || 0, j || res.length);
} :
function(a, i, j){
return Array.prototype.slice.call(a, i || 0, j || a.length);
};
}(),
isIterable : function(v){
//check for array or arguments
if(Ext.isArray(v) || v.callee){
return true;
}
//check for node list type
if(/NodeList|HTMLCollection/.test(toString.call(v))){
return true;
}
//NodeList has an item and length property
//IXMLDOMNodeList has nextNode method, needs to be checked first.
return ((typeof v.nextNode != 'undefined' || v.item) && Ext.isNumber(v.length));
},
/**
* Iterates an array calling the supplied function.
* @param {Array/NodeList/Mixed} array The array to be iterated. If this
* argument is not really an array, the supplied function is called once.
* @param {Function} fn The function to be called with each item. If the
* supplied function returns false, iteration stops and this method returns
* the current index. This function is called with
* the following arguments:
*
* item : Mixed
* The item at the current index
* in the passed array
* index : Number
* The current index within the array
* allItems : Array
* The array passed as the first
* argument to Ext.each.
*
* @param {Object} scope The scope (this reference) in which the specified function is executed.
* Defaults to the item at the current index
* within the passed array.
* @return See description for the fn parameter.
*/
each : function(array, fn, scope){
if(Ext.isEmpty(array, true)){
return;
}
if(!Ext.isIterable(array) || Ext.isPrimitive(array)){
array = [array];
}
for(var i = 0, len = array.length; i < len; i++){
if(fn.call(scope || array[i], array[i], i, array) === false){
return i;
};
}
},
/**
* Iterates either the elements in an array, or each of the properties in an object.
* Note : If you are only iterating arrays, it is better to call {@link #each}.
* @param {Object/Array} object The object or array to be iterated
* @param {Function} fn The function to be called for each iteration.
* The iteration will stop if the supplied function returns false, or
* all array elements / object properties have been covered. The signature
* varies depending on the type of object being interated:
*
* Arrays : (Object item, Number index, Array allItems)
*
* When iterating an array, the supplied function is called with each item.
* Objects : (String key, Object value, Object)
*
* When iterating an object, the supplied function is called with each key-value pair in
* the object, and the iterated object
*
* @param {Object} scope The scope (this reference) in which the specified function is executed. Defaults to
* the object being iterated.
*/
iterate : function(obj, fn, scope){
if(Ext.isEmpty(obj)){
return;
}
if(Ext.isIterable(obj)){
Ext.each(obj, fn, scope);
return;
}else if(typeof obj == 'object'){
for(var prop in obj){
if(obj.hasOwnProperty(prop)){
if(fn.call(scope || obj, prop, obj[prop], obj) === false){
return;
};
}
}
}
},
/**
* Return the dom node for the passed String (id), dom node, or Ext.Element.
* Optional 'strict' flag is needed for IE since it can return 'name' and
* 'id' elements by using getElementById.
* Here are some examples:
*
// gets dom node based on id
var elDom = Ext.getDom('elId');
// gets dom node based on the dom node
var elDom1 = Ext.getDom(elDom);
// If we don't know if we are working with an
// Ext.Element or a dom node use Ext.getDom
function(el){
var dom = Ext.getDom(el);
// do something with the dom node
}
*
* Note : the dom node to be found actually needs to exist (be rendered, etc)
* when this method is called to be successful.
* @param {Mixed} el
* @return HTMLElement
*/
getDom : function(el, strict){
if(!el || !DOC){
return null;
}
if (el.dom){
return el.dom;
} else {
if (typeof el == 'string') {
var e = DOC.getElementById(el);
// IE returns elements with the 'name' and 'id' attribute.
// we do a strict check to return the element with only the id attribute
if (e && isIE && strict) {
if (el == e.getAttribute('id')) {
return e;
} else {
return null;
}
}
return e;
} else {
return el;
}
}
},
/**
* Returns the current document body as an {@link Ext.Element}.
* @return Ext.Element The document body
*/
getBody : function(){
return Ext.get(DOC.body || DOC.documentElement);
},
/**
* Returns the current document body as an {@link Ext.Element}.
* @return Ext.Element The document body
* @method
*/
getHead : function() {
var head;
return function() {
if (head == undefined) {
head = Ext.get(DOC.getElementsByTagName("head")[0]);
}
return head;
};
}(),
/**
* Removes this element from the document, removes all DOM event listeners, and deletes the cache reference.
* All DOM event listeners are removed from this element. If {@link Ext#enableNestedListenerRemoval} is
* true, then DOM event listeners are also removed from all child nodes. The body node
* will be ignored if passed in.
* @param {HTMLElement} node The node to remove
* @method
*/
removeNode : isIE && !isIE8 ? function(){
var d;
return function(n){
if(n && n.tagName != 'BODY'){
(Ext.enableNestedListenerRemoval) ? Ext.EventManager.purgeElement(n, true) : Ext.EventManager.removeAll(n);
d = d || DOC.createElement('div');
d.appendChild(n);
d.innerHTML = '';
delete Ext.elCache[n.id];
}
};
}() : function(n){
if(n && n.parentNode && n.tagName != 'BODY'){
(Ext.enableNestedListenerRemoval) ? Ext.EventManager.purgeElement(n, true) : Ext.EventManager.removeAll(n);
n.parentNode.removeChild(n);
delete Ext.elCache[n.id];
}
},
/**
* Returns true if the passed value is empty.
* The value is deemed to be empty if it is
* null
* undefined
* an empty array
* a zero length string (Unless the allowBlank parameter is true )
*
* @param {Mixed} value The value to test
* @param {Boolean} allowBlank (optional) true to allow empty strings (defaults to false)
* @return {Boolean}
*/
isEmpty : function(v, allowBlank){
return v === null || v === undefined || ((Ext.isArray(v) && !v.length)) || (!allowBlank ? v === '' : false);
},
/**
* Returns true if the passed value is a JavaScript array, otherwise false.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isArray : function(v){
return toString.apply(v) === '[object Array]';
},
/**
* Returns true if the passed object is a JavaScript date object, otherwise false.
* @param {Object} object The object to test
* @return {Boolean}
*/
isDate : function(v){
return toString.apply(v) === '[object Date]';
},
/**
* Returns true if the passed value is a JavaScript Object, otherwise false.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isObject : function(v){
return !!v && Object.prototype.toString.call(v) === '[object Object]';
},
/**
* Returns true if the passed value is a JavaScript 'primitive', a string, number or boolean.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isPrimitive : function(v){
return Ext.isString(v) || Ext.isNumber(v) || Ext.isBoolean(v);
},
/**
* Returns true if the passed value is a JavaScript Function, otherwise false.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isFunction : function(v){
return toString.apply(v) === '[object Function]';
},
/**
* Returns true if the passed value is a number. Returns false for non-finite numbers.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isNumber : function(v){
return typeof v === 'number' && isFinite(v);
},
/**
* Returns true if the passed value is a string.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isString : function(v){
return typeof v === 'string';
},
/**
* Returns true if the passed value is a boolean.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isBoolean : function(v){
return typeof v === 'boolean';
},
/**
* Returns true if the passed value is an HTMLElement
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isElement : function(v) {
return v ? !!v.tagName : false;
},
/**
* Returns true if the passed value is not undefined.
* @param {Mixed} value The value to test
* @return {Boolean}
*/
isDefined : function(v){
return typeof v !== 'undefined';
},
/**
* True if the detected browser is Opera.
* @type Boolean
*/
isOpera : isOpera,
/**
* True if the detected browser uses WebKit.
* @type Boolean
*/
isWebKit : isWebKit,
/**
* True if the detected browser is Chrome.
* @type Boolean
*/
isChrome : isChrome,
/**
* True if the detected browser is Safari.
* @type Boolean
*/
isSafari : isSafari,
/**
* True if the detected browser is Safari 3.x.
* @type Boolean
*/
isSafari3 : isSafari3,
/**
* True if the detected browser is Safari 4.x.
* @type Boolean
*/
isSafari4 : isSafari4,
/**
* True if the detected browser is Safari 2.x.
* @type Boolean
*/
isSafari2 : isSafari2,
/**
* True if the detected browser is Internet Explorer.
* @type Boolean
*/
isIE : isIE,
/**
* True if the detected browser is Internet Explorer 6.x.
* @type Boolean
*/
isIE6 : isIE6,
/**
* True if the detected browser is Internet Explorer 7.x.
* @type Boolean
*/
isIE7 : isIE7,
/**
* True if the detected browser is Internet Explorer 8.x.
* @type Boolean
*/
isIE8 : isIE8,
/**
* True if the detected browser is Internet Explorer 9.x.
* @type Boolean
*/
isIE9 : isIE9,
/**
* True if the detected browser is Internet Explorer 10.x
* @type Boolean
*/
isIE10 : isIE10,
/**
* True if the detected browser is Internet Explorer 9.x or lower
* @type Boolean
*/
isIE9m : isIE9m,
/**
* True if the detected browser is Internet Explorer 10.x or higher
* @type Boolean
*/
isIE10p : isIE && !(isIE6 || isIE7 || isIE8 || isIE9),
// IE10 quirks behaves like Gecko/WebKit quirks, so don't include it here
// Used internally
isIEQuirks: isIE && (!isStrict && (isIE6 || isIE7 || isIE8 || isIE9)),
/**
* True if the detected browser uses the Gecko layout engine (e.g. Mozilla, Firefox).
* @type Boolean
*/
isGecko : isGecko,
/**
* True if the detected browser uses a pre-Gecko 1.9 layout engine (e.g. Firefox 2.x).
* @type Boolean
*/
isGecko2 : isGecko2,
/**
* True if the detected browser uses a Gecko 1.9+ layout engine (e.g. Firefox 3.x).
* @type Boolean
*/
isGecko3 : isGecko3,
/**
* True if the detected browser is Internet Explorer running in non-strict mode.
* @type Boolean
*/
isBorderBox : isBorderBox,
/**
* True if the detected platform is Linux.
* @type Boolean
*/
isLinux : isLinux,
/**
* True if the detected platform is Windows.
* @type Boolean
*/
isWindows : isWindows,
/**
* True if the detected platform is Mac OS.
* @type Boolean
*/
isMac : isMac,
/**
* True if the detected platform is Adobe Air.
* @type Boolean
*/
isAir : isAir
});
/**
* Creates namespaces to be used for scoping variables and classes so that they are not global.
* Specifying the last node of a namespace implicitly creates all other nodes. Usage:
*
Ext.namespace('Company', 'Company.data');
Ext.namespace('Company.data'); // equivalent and preferable to above syntax
Company.Widget = function() { ... }
Company.data.CustomStore = function(config) { ... }
* @param {String} namespace1
* @param {String} namespace2
* @param {String} etc
* @return {Object} The namespace object. (If multiple arguments are passed, this will be the last namespace created)
* @method ns
*/
Ext.ns = Ext.namespace;
})();
Ext.ns('Ext.util', 'Ext.lib', 'Ext.data', 'Ext.supports');
Ext.elCache = {};
/**
* @class Function
* These functions are available on every Function object (any JavaScript function).
*/
Ext.apply(Function.prototype, {
/**
* Creates an interceptor function. The passed function is called before the original one. If it returns false,
* the original one is not called. The resulting function returns the results of the original function.
* The passed function is called with the parameters of the original function. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
sayHi('Fred'); // alerts "Hi, Fred"
// create a new function that validates input without
// directly modifying the original function:
var sayHiToFriend = sayHi.createInterceptor(function(name){
return name == 'Brian';
});
sayHiToFriend('Fred'); // no alert
sayHiToFriend('Brian'); // alerts "Hi, Brian"
* @param {Function} fcn The function to call before the original
* @param {Object} scope (optional) The scope (this reference) in which the passed function is executed.
* If omitted, defaults to the scope in which the original function is called or the browser window.
* @return {Function} The new function
*/
createInterceptor : function(fcn, scope){
var method = this;
return !Ext.isFunction(fcn) ?
this :
function() {
var me = this,
args = arguments;
fcn.target = me;
fcn.method = method;
return (fcn.apply(scope || me || window, args) !== false) ?
method.apply(me || window, args) :
null;
};
},
/**
* Creates a callback that passes arguments[0], arguments[1], arguments[2], ...
* Call directly on any function. Example: myFunction.createCallback(arg1, arg2)
* Will create a function that is bound to those 2 args. If a specific scope is required in the
* callback, use {@link #createDelegate} instead. The function returned by createCallback always
* executes in the window scope.
* This method is required when you want to pass arguments to a callback function. If no arguments
* are needed, you can simply pass a reference to the function as a callback (e.g., callback: myFn).
* However, if you tried to pass a function with arguments (e.g., callback: myFn(arg1, arg2)) the function
* would simply execute immediately when the code is parsed. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
// clicking the button alerts "Hi, Fred"
new Ext.Button({
text: 'Say Hi',
renderTo: Ext.getBody(),
handler: sayHi.createCallback('Fred')
});
* @return {Function} The new function
*/
createCallback : function(/*args...*/){
// make args available, in function below
var args = arguments,
method = this;
return function() {
return method.apply(window, args);
};
},
/**
* Creates a delegate (callback) that sets the scope to obj.
* Call directly on any function. Example: this.myFunction.createDelegate(this, [arg1, arg2])
* Will create a function that is automatically scoped to obj so that the this variable inside the
* callback points to obj. Example usage:
*
var sayHi = function(name){
// Note this use of "this.text" here. This function expects to
// execute within a scope that contains a text property. In this
// example, the "this" variable is pointing to the btn object that
// was passed in createDelegate below.
alert('Hi, ' + name + '. You clicked the "' + this.text + '" button.');
}
var btn = new Ext.Button({
text: 'Say Hi',
renderTo: Ext.getBody()
});
// This callback will execute in the scope of the
// button instance. Clicking the button alerts
// "Hi, Fred. You clicked the "Say Hi" button."
btn.on('click', sayHi.createDelegate(btn, ['Fred']));
* @param {Object} scope (optional) The scope (this reference) in which the function is executed.
* If omitted, defaults to the browser window.
* @param {Array} args (optional) Overrides arguments for the call. (Defaults to the arguments passed by the caller)
* @param {Boolean/Number} appendArgs (optional) if True args are appended to call args instead of overriding,
* if a number the args are inserted at the specified position
* @return {Function} The new function
*/
createDelegate : function(obj, args, appendArgs){
var method = this;
return function() {
var callArgs = args || arguments;
if (appendArgs === true){
callArgs = Array.prototype.slice.call(arguments, 0);
callArgs = callArgs.concat(args);
}else if (Ext.isNumber(appendArgs)){
callArgs = Array.prototype.slice.call(arguments, 0); // copy arguments first
var applyArgs = [appendArgs, 0].concat(args); // create method call params
Array.prototype.splice.apply(callArgs, applyArgs); // splice them in
}
return method.apply(obj || window, callArgs);
};
},
/**
* Calls this function after the number of millseconds specified, optionally in a specific scope. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
// executes immediately:
sayHi('Fred');
// executes after 2 seconds:
sayHi.defer(2000, this, ['Fred']);
// this syntax is sometimes useful for deferring
// execution of an anonymous function:
(function(){
alert('Anonymous');
}).defer(100);
* @param {Number} millis The number of milliseconds for the setTimeout call (if less than or equal to 0 the function is executed immediately)
* @param {Object} scope (optional) The scope (this reference) in which the function is executed.
* If omitted, defaults to the browser window.
* @param {Array} args (optional) Overrides arguments for the call. (Defaults to the arguments passed by the caller)
* @param {Boolean/Number} appendArgs (optional) if True args are appended to call args instead of overriding,
* if a number the args are inserted at the specified position
* @return {Number} The timeout id that can be used with clearTimeout
*/
defer : function(millis, obj, args, appendArgs){
var fn = this.createDelegate(obj, args, appendArgs);
if(millis > 0){
return setTimeout(fn, millis);
}
fn();
return 0;
}
});
/**
* @class String
* These functions are available on every String object.
*/
Ext.applyIf(String, {
/**
* Allows you to define a tokenized string and pass an arbitrary number of arguments to replace the tokens. Each
* token must be unique, and must increment in the format {0}, {1}, etc. Example usage:
*
var cls = 'my-class', text = 'Some text';
var s = String.format('<div class="{0}">{1}</div>', cls, text);
// s now contains the string: '<div class="my-class">Some text</div>'
*
* @param {String} string The tokenized string to be formatted
* @param {String} value1 The value to replace token {0}
* @param {String} value2 Etc...
* @return {String} The formatted string
* @static
*/
format : function(format){
var args = Ext.toArray(arguments, 1);
return format.replace(/\{(\d+)\}/g, function(m, i){
return args[i];
});
}
});
/**
* @class Array
*/
Ext.applyIf(Array.prototype, {
/**
* Checks whether or not the specified object exists in the array.
* @param {Object} o The object to check for
* @param {Number} from (Optional) The index at which to begin the search
* @return {Number} The index of o in the array (or -1 if it is not found)
*/
indexOf : function(o, from){
var len = this.length;
from = from || 0;
from += (from < 0) ? len : 0;
for (; from < len; ++from){
if(this[from] === o){
return from;
}
}
return -1;
},
/**
* Removes the specified object from the array. If the object is not found nothing happens.
* @param {Object} o The object to remove
* @return {Array} this array
*/
remove : function(o){
var index = this.indexOf(o);
if(index != -1){
this.splice(index, 1);
}
return this;
}
});
/**
* @class Ext.util.TaskRunner
* Provides the ability to execute one or more arbitrary tasks in a multithreaded
* manner. Generally, you can use the singleton {@link Ext.TaskMgr} instead, but
* if needed, you can create separate instances of TaskRunner. Any number of
* separate tasks can be started at any time and will run independently of each
* other. Example usage:
*
// Start a simple clock task that updates a div once per second
var updateClock = function(){
Ext.fly('clock').update(new Date().format('g:i:s A'));
}
var task = {
run: updateClock,
interval: 1000 //1 second
}
var runner = new Ext.util.TaskRunner();
runner.start(task);
// equivalent using TaskMgr
Ext.TaskMgr.start({
run: updateClock,
interval: 1000
});
*
* See the {@link #start} method for details about how to configure a task object.
* Also see {@link Ext.util.DelayedTask}.
*
* @constructor
* @param {Number} interval (optional) The minimum precision in milliseconds supported by this TaskRunner instance
* (defaults to 10)
*/
Ext.util.TaskRunner = function(interval){
interval = interval || 10;
var tasks = [],
removeQueue = [],
id = 0,
running = false,
// private
stopThread = function(){
running = false;
clearInterval(id);
id = 0;
},
// private
startThread = function(){
if(!running){
running = true;
id = setInterval(runTasks, interval);
}
},
// private
removeTask = function(t){
removeQueue.push(t);
if(t.onStop){
t.onStop.apply(t.scope || t);
}
},
// private
runTasks = function(){
var rqLen = removeQueue.length,
now = new Date().getTime();
if(rqLen > 0){
for(var i = 0; i < rqLen; i++){
tasks.remove(removeQueue[i]);
}
removeQueue = [];
if(tasks.length < 1){
stopThread();
return;
}
}
for(var i = 0, t, itime, rt, len = tasks.length; i < len; ++i){
t = tasks[i];
itime = now - t.taskRunTime;
if(t.interval <= itime){
rt = t.run.apply(t.scope || t, t.args || [++t.taskRunCount]);
t.taskRunTime = now;
if(rt === false || t.taskRunCount === t.repeat){
removeTask(t);
return;
}
}
if(t.duration && t.duration <= (now - t.taskStartTime)){
removeTask(t);
}
}
};
/**
* Starts a new task.
* @method start
* @param {Object} task A config object that supports the following properties:
* run : FunctionThe function to execute each time the task is invoked. The
* function will be called at each interval and passed the args argument if specified, and the
* current invocation count if not.
*
If a particular scope (this reference) is required, be sure to specify it using the scope argument.
*
Return false from this function to terminate the task.
* interval : NumberThe frequency in milliseconds with which the task
* should be invoked.
* args : Array(optional) An array of arguments to be passed to the function
* specified by run. If not specified, the current invocation count is passed.
* scope : Object(optional) The scope (this reference) in which to execute the
* run function. Defaults to the task config object.
* duration : Number(optional) The length of time in milliseconds to invoke
* the task before stopping automatically (defaults to indefinite).
* repeat : Number(optional) The number of times to invoke the task before
* stopping automatically (defaults to indefinite).
*
* Before each invocation, Ext injects the property taskRunCount into the task object so
* that calculations based on the repeat count can be performed.
* @return {Object} The task
*/
this.start = function(task){
tasks.push(task);
task.taskStartTime = new Date().getTime();
task.taskRunTime = 0;
task.taskRunCount = 0;
startThread();
return task;
};
/**
* Stops an existing running task.
* @method stop
* @param {Object} task The task to stop
* @return {Object} The task
*/
this.stop = function(task){
removeTask(task);
return task;
};
/**
* Stops all tasks that are currently running.
* @method stopAll
*/
this.stopAll = function(){
stopThread();
for(var i = 0, len = tasks.length; i < len; i++){
if(tasks[i].onStop){
tasks[i].onStop();
}
}
tasks = [];
removeQueue = [];
};
};
/**
* @class Ext.TaskMgr
* @extends Ext.util.TaskRunner
* A static {@link Ext.util.TaskRunner} instance that can be used to start and stop arbitrary tasks. See
* {@link Ext.util.TaskRunner} for supported methods and task config properties.
*
// Start a simple clock task that updates a div once per second
var task = {
run: function(){
Ext.fly('clock').update(new Date().format('g:i:s A'));
},
interval: 1000 //1 second
}
Ext.TaskMgr.start(task);
* See the {@link #start} method for details about how to configure a task object.
* @singleton
*/
Ext.TaskMgr = new Ext.util.TaskRunner();(function(){
var libFlyweight;
function fly(el) {
if (!libFlyweight) {
libFlyweight = new Ext.Element.Flyweight();
}
libFlyweight.dom = el;
return libFlyweight;
}
(function(){
var doc = document,
isCSS1 = doc.compatMode == "CSS1Compat",
MAX = Math.max,
ROUND = Math.round,
PARSEINT = parseInt;
Ext.lib.Dom = {
isAncestor : function(p, c) {
var ret = false;
p = Ext.getDom(p);
c = Ext.getDom(c);
if (p && c) {
if (p.contains) {
return p.contains(c);
} else if (p.compareDocumentPosition) {
return !!(p.compareDocumentPosition(c) & 16);
} else {
while (c = c.parentNode) {
ret = c == p || ret;
}
}
}
return ret;
},
getViewWidth : function(full) {
return full ? this.getDocumentWidth() : this.getViewportWidth();
},
getViewHeight : function(full) {
return full ? this.getDocumentHeight() : this.getViewportHeight();
},
getDocumentHeight: function() {
return MAX(!isCSS1 ? doc.body.scrollHeight : doc.documentElement.scrollHeight, this.getViewportHeight());
},
getDocumentWidth: function() {
return MAX(!isCSS1 ? doc.body.scrollWidth : doc.documentElement.scrollWidth, this.getViewportWidth());
},
getViewportHeight: function(){
return Ext.isIE9m ?
(Ext.isStrict ? doc.documentElement.clientHeight : doc.body.clientHeight) :
self.innerHeight;
},
getViewportWidth : function() {
return !Ext.isStrict && !Ext.isOpera ? doc.body.clientWidth :
Ext.isIE9m ? doc.documentElement.clientWidth : self.innerWidth;
},
getY : function(el) {
return this.getXY(el)[1];
},
getX : function(el) {
return this.getXY(el)[0];
},
getXY : function(el) {
var p,
pe,
b,
bt,
bl,
dbd,
x = 0,
y = 0,
scroll,
hasAbsolute,
bd = (doc.body || doc.documentElement),
ret = [0,0];
el = Ext.getDom(el);
if(el != bd){
if (el.getBoundingClientRect) {
b = el.getBoundingClientRect();
scroll = fly(document).getScroll();
ret = [ROUND(b.left + scroll.left), ROUND(b.top + scroll.top)];
} else {
p = el;
hasAbsolute = fly(el).isStyle("position", "absolute");
while (p) {
pe = fly(p);
x += p.offsetLeft;
y += p.offsetTop;
hasAbsolute = hasAbsolute || pe.isStyle("position", "absolute");
if (Ext.isGecko) {
y += bt = PARSEINT(pe.getStyle("borderTopWidth"), 10) || 0;
x += bl = PARSEINT(pe.getStyle("borderLeftWidth"), 10) || 0;
if (p != el && !pe.isStyle('overflow','visible')) {
x += bl;
y += bt;
}
}
p = p.offsetParent;
}
if (Ext.isSafari && hasAbsolute) {
x -= bd.offsetLeft;
y -= bd.offsetTop;
}
if (Ext.isGecko && !hasAbsolute) {
dbd = fly(bd);
x += PARSEINT(dbd.getStyle("borderLeftWidth"), 10) || 0;
y += PARSEINT(dbd.getStyle("borderTopWidth"), 10) || 0;
}
p = el.parentNode;
while (p && p != bd) {
if (!Ext.isOpera || (p.tagName != 'TR' && !fly(p).isStyle("display", "inline"))) {
x -= p.scrollLeft;
y -= p.scrollTop;
}
p = p.parentNode;
}
ret = [x,y];
}
}
return ret;
},
setXY : function(el, xy) {
(el = Ext.fly(el, '_setXY')).position();
var pts = el.translatePoints(xy),
style = el.dom.style,
pos;
for (pos in pts) {
if (!isNaN(pts[pos])) {
style[pos] = pts[pos] + "px";
}
}
},
setX : function(el, x) {
this.setXY(el, [x, false]);
},
setY : function(el, y) {
this.setXY(el, [false, y]);
}
};
})();Ext.lib.Event = function() {
var loadComplete = false,
unloadListeners = {},
retryCount = 0,
onAvailStack = [],
_interval,
locked = false,
win = window,
doc = document,
// constants
POLL_RETRYS = 200,
POLL_INTERVAL = 20,
TYPE = 0,
FN = 1,
OBJ = 2,
ADJ_SCOPE = 3,
SCROLLLEFT = 'scrollLeft',
SCROLLTOP = 'scrollTop',
UNLOAD = 'unload',
MOUSEOVER = 'mouseover',
MOUSEOUT = 'mouseout',
// private
doAdd = function() {
var ret;
if (win.addEventListener) {
ret = function(el, eventName, fn, capture) {
if (eventName == 'mouseenter') {
fn = fn.createInterceptor(checkRelatedTarget);
el.addEventListener(MOUSEOVER, fn, (capture));
} else if (eventName == 'mouseleave') {
fn = fn.createInterceptor(checkRelatedTarget);
el.addEventListener(MOUSEOUT, fn, (capture));
} else {
el.addEventListener(eventName, fn, (capture));
}
return fn;
};
} else if (win.attachEvent) {
ret = function(el, eventName, fn, capture) {
el.attachEvent("on" + eventName, fn);
return fn;
};
} else {
ret = function(){};
}
return ret;
}(),
// private
doRemove = function(){
var ret;
if (win.removeEventListener) {
ret = function (el, eventName, fn, capture) {
if (eventName == 'mouseenter') {
eventName = MOUSEOVER;
} else if (eventName == 'mouseleave') {
eventName = MOUSEOUT;
}
el.removeEventListener(eventName, fn, (capture));
};
} else if (win.detachEvent) {
ret = function (el, eventName, fn) {
el.detachEvent("on" + eventName, fn);
};
} else {
ret = function(){};
}
return ret;
}();
function checkRelatedTarget(e) {
return !elContains(e.currentTarget, pub.getRelatedTarget(e));
}
function elContains(parent, child) {
if(parent && parent.firstChild){
while(child) {
if(child === parent) {
return true;
}
child = child.parentNode;
if(child && (child.nodeType != 1)) {
child = null;
}
}
}
return false;
}
// private
function _tryPreloadAttach() {
var ret = false,
notAvail = [],
element, i, v, override,
tryAgain = !loadComplete || (retryCount > 0);
if(!locked){
locked = true;
for(i = 0; i < onAvailStack.length; ++i){
v = onAvailStack[i];
if(v && (element = doc.getElementById(v.id))){
if(!v.checkReady || loadComplete || element.nextSibling || (doc && doc.body)) {
override = v.override;
element = override ? (override === true ? v.obj : override) : element;
v.fn.call(element, v.obj);
onAvailStack.remove(v);
--i;
}else{
notAvail.push(v);
}
}
}
retryCount = (notAvail.length === 0) ? 0 : retryCount - 1;
if (tryAgain) {
startInterval();
} else {
clearInterval(_interval);
_interval = null;
}
ret = !(locked = false);
}
return ret;
}
// private
function startInterval() {
if(!_interval){
var callback = function() {
_tryPreloadAttach();
};
_interval = setInterval(callback, POLL_INTERVAL);
}
}
// private
function getScroll() {
var dd = doc.documentElement,
db = doc.body;
if(dd && (dd[SCROLLTOP] || dd[SCROLLLEFT])){
return [dd[SCROLLLEFT], dd[SCROLLTOP]];
}else if(db){
return [db[SCROLLLEFT], db[SCROLLTOP]];
}else{
return [0, 0];
}
}
// private
function getPageCoord (ev, xy) {
ev = ev.browserEvent || ev;
var coord = ev['page' + xy];
if (!coord && coord !== 0) {
coord = ev['client' + xy] || 0;
if (Ext.isIE) {
coord += getScroll()[xy == "X" ? 0 : 1];
}
}
return coord;
}
var pub = {
extAdapter: true,
onAvailable : function(p_id, p_fn, p_obj, p_override) {
onAvailStack.push({
id: p_id,
fn: p_fn,
obj: p_obj,
override: p_override,
checkReady: false });
retryCount = POLL_RETRYS;
startInterval();
},
// This function should ALWAYS be called from Ext.EventManager
addListener: function(el, eventName, fn) {
el = Ext.getDom(el);
if (el && fn) {
if (eventName == UNLOAD) {
if (unloadListeners[el.id] === undefined) {
unloadListeners[el.id] = [];
}
unloadListeners[el.id].push([eventName, fn]);
return fn;
}
return doAdd(el, eventName, fn, false);
}
return false;
},
// This function should ALWAYS be called from Ext.EventManager
removeListener: function(el, eventName, fn) {
el = Ext.getDom(el);
var i, len, li, lis;
if (el && fn) {
if(eventName == UNLOAD){
if((lis = unloadListeners[el.id]) !== undefined){
for(i = 0, len = lis.length; i < len; i++){
if((li = lis[i]) && li[TYPE] == eventName && li[FN] == fn){
unloadListeners[el.id].splice(i, 1);
}
}
}
return;
}
doRemove(el, eventName, fn, false);
}
},
getTarget : function(ev) {
ev = ev.browserEvent || ev;
return this.resolveTextNode(ev.target || ev.srcElement);
},
resolveTextNode : Ext.isGecko ? function(node){
if(!node){
return;
}
// work around firefox bug, https://bugzilla.mozilla.org/show_bug.cgi?id=101197
var s = HTMLElement.prototype.toString.call(node);
if(s == '[xpconnect wrapped native prototype]' || s == '[object XULElement]'){
return;
}
return node.nodeType == 3 ? node.parentNode : node;
} : function(node){
return node && node.nodeType == 3 ? node.parentNode : node;
},
getRelatedTarget : function(ev) {
ev = ev.browserEvent || ev;
return this.resolveTextNode(ev.relatedTarget ||
(/(mouseout|mouseleave)/.test(ev.type) ? ev.toElement :
/(mouseover|mouseenter)/.test(ev.type) ? ev.fromElement : null));
},
getPageX : function(ev) {
return getPageCoord(ev, "X");
},
getPageY : function(ev) {
return getPageCoord(ev, "Y");
},
getXY : function(ev) {
return [this.getPageX(ev), this.getPageY(ev)];
},
stopEvent : function(ev) {
this.stopPropagation(ev);
this.preventDefault(ev);
},
stopPropagation : function(ev) {
ev = ev.browserEvent || ev;
if (ev.stopPropagation) {
ev.stopPropagation();
} else {
ev.cancelBubble = true;
}
},
preventDefault : function(ev) {
ev = ev.browserEvent || ev;
if (ev.preventDefault) {
ev.preventDefault();
} else {
if (ev.keyCode) {
ev.keyCode = 0;
}
ev.returnValue = false;
}
},
getEvent : function(e) {
e = e || win.event;
if (!e) {
var c = this.getEvent.caller;
while (c) {
e = c.arguments[0];
if (e && Event == e.constructor) {
break;
}
c = c.caller;
}
}
return e;
},
getCharCode : function(ev) {
ev = ev.browserEvent || ev;
return ev.charCode || ev.keyCode || 0;
},
//clearCache: function() {},
// deprecated, call from EventManager
getListeners : function(el, eventName) {
Ext.EventManager.getListeners(el, eventName);
},
// deprecated, call from EventManager
purgeElement : function(el, recurse, eventName) {
Ext.EventManager.purgeElement(el, recurse, eventName);
},
_load : function(e) {
loadComplete = true;
if (Ext.isIE9m && e !== true) {
// IE8 complains that _load is null or not an object
// so lets remove self via arguments.callee
doRemove(win, "load", arguments.callee);
}
},
_unload : function(e) {
var EU = Ext.lib.Event,
i, v, ul, id, len, scope;
for (id in unloadListeners) {
ul = unloadListeners[id];
for (i = 0, len = ul.length; i < len; i++) {
v = ul[i];
if (v) {
try{
scope = v[ADJ_SCOPE] ? (v[ADJ_SCOPE] === true ? v[OBJ] : v[ADJ_SCOPE]) : win;
v[FN].call(scope, EU.getEvent(e), v[OBJ]);
}catch(ex){}
}
}
};
Ext.EventManager._unload();
doRemove(win, UNLOAD, EU._unload);
}
};
// Initialize stuff.
pub.on = pub.addListener;
pub.un = pub.removeListener;
if (doc && doc.body) {
pub._load(true);
} else {
doAdd(win, "load", pub._load);
}
doAdd(win, UNLOAD, pub._unload);
_tryPreloadAttach();
return pub;
}();
/*
* Portions of this file are based on pieces of Yahoo User Interface Library
* Copyright (c) 2007, Yahoo! Inc. All rights reserved.
* YUI licensed under the BSD License:
* http://developer.yahoo.net/yui/license.txt
*/
Ext.lib.Ajax = function() {
var activeX = ['Msxml2.XMLHTTP.3.0',
'Msxml2.XMLHTTP'],
CONTENTTYPE = 'Content-Type';
// private
function setHeader(o) {
var conn = o.conn,
prop,
headers = {};
function setTheHeaders(conn, headers){
for (prop in headers) {
if (headers.hasOwnProperty(prop)) {
conn.setRequestHeader(prop, headers[prop]);
}
}
}
Ext.apply(headers, pub.headers, pub.defaultHeaders);
setTheHeaders(conn, headers);
delete pub.headers;
}
// private
function createExceptionObject(tId, callbackArg, isAbort, isTimeout) {
return {
tId : tId,
status : isAbort ? -1 : 0,
statusText : isAbort ? 'transaction aborted' : 'communication failure',
isAbort: isAbort,
isTimeout: isTimeout,
argument : callbackArg
};
}
// private
function initHeader(label, value) {
(pub.headers = pub.headers || {})[label] = value;
}
// private
function createResponseObject(o, callbackArg) {
var headerObj = {},
headerStr,
conn = o.conn,
t,
s,
// see: https://prototype.lighthouseapp.com/projects/8886/tickets/129-ie-mangles-http-response-status-code-204-to-1223
isBrokenStatus = conn.status == 1223;
try {
headerStr = o.conn.getAllResponseHeaders();
Ext.each(headerStr.replace(/\r\n/g, '\n').split('\n'), function(v){
t = v.indexOf(':');
if(t >= 0){
s = v.substr(0, t).toLowerCase();
if(v.charAt(t + 1) == ' '){
++t;
}
headerObj[s] = v.substr(t + 1);
}
});
} catch(e) {}
return {
tId : o.tId,
// Normalize the status and statusText when IE returns 1223, see the above link.
status : isBrokenStatus ? 204 : conn.status,
statusText : isBrokenStatus ? 'No Content' : conn.statusText,
getResponseHeader : function(header){return headerObj[header.toLowerCase()];},
getAllResponseHeaders : function(){return headerStr;},
responseText : conn.responseText,
responseXML : conn.responseXML,
argument : callbackArg
};
}
// private
function releaseObject(o) {
if (o.tId) {
pub.conn[o.tId] = null;
}
o.conn = null;
o = null;
}
// private
function handleTransactionResponse(o, callback, isAbort, isTimeout) {
if (!callback) {
releaseObject(o);
return;
}
var httpStatus, responseObject;
try {
if (o.conn.status !== undefined && o.conn.status != 0) {
httpStatus = o.conn.status;
}
else {
httpStatus = 13030;
}
}
catch(e) {
httpStatus = 13030;
}
if ((httpStatus >= 200 && httpStatus < 300) || (Ext.isIE && httpStatus == 1223)) {
responseObject = createResponseObject(o, callback.argument);
if (callback.success) {
if (!callback.scope) {
callback.success(responseObject);
}
else {
callback.success.apply(callback.scope, [responseObject]);
}
}
}
else {
switch (httpStatus) {
case 12002:
case 12029:
case 12030:
case 12031:
case 12152:
case 13030:
responseObject = createExceptionObject(o.tId, callback.argument, (isAbort ? isAbort : false), isTimeout);
if (callback.failure) {
if (!callback.scope) {
callback.failure(responseObject);
}
else {
callback.failure.apply(callback.scope, [responseObject]);
}
}
break;
default:
responseObject = createResponseObject(o, callback.argument);
if (callback.failure) {
if (!callback.scope) {
callback.failure(responseObject);
}
else {
callback.failure.apply(callback.scope, [responseObject]);
}
}
}
}
releaseObject(o);
responseObject = null;
}
function checkResponse(o, callback, conn, tId, poll, cbTimeout){
if (conn && conn.readyState == 4) {
clearInterval(poll[tId]);
poll[tId] = null;
if (cbTimeout) {
clearTimeout(pub.timeout[tId]);
pub.timeout[tId] = null;
}
handleTransactionResponse(o, callback);
}
}
function checkTimeout(o, callback){
pub.abort(o, callback, true);
}
// private
function handleReadyState(o, callback){
callback = callback || {};
var conn = o.conn,
tId = o.tId,
poll = pub.poll,
cbTimeout = callback.timeout || null;
if (cbTimeout) {
pub.conn[tId] = conn;
pub.timeout[tId] = setTimeout(checkTimeout.createCallback(o, callback), cbTimeout);
}
poll[tId] = setInterval(checkResponse.createCallback(o, callback, conn, tId, poll, cbTimeout), pub.pollInterval);
}
// private
function asyncRequest(method, uri, callback, postData) {
var o = getConnectionObject() || null;
if (o) {
o.conn.open(method, uri, true);
if (pub.useDefaultXhrHeader) {
initHeader('X-Requested-With', pub.defaultXhrHeader);
}
if(postData && pub.useDefaultHeader && (!pub.headers || !pub.headers[CONTENTTYPE])){
initHeader(CONTENTTYPE, pub.defaultPostHeader);
}
if (pub.defaultHeaders || pub.headers) {
setHeader(o);
}
handleReadyState(o, callback);
o.conn.send(postData || null);
}
return o;
}
// private
function getConnectionObject() {
var o;
try {
if (o = createXhrObject(pub.transactionId)) {
pub.transactionId++;
}
} catch(e) {
} finally {
return o;
}
}
// private
function createXhrObject(transactionId) {
var http;
try {
http = new XMLHttpRequest();
} catch(e) {
for (var i = Ext.isIE6 ? 1 : 0; i < activeX.length; ++i) {
try {
http = new ActiveXObject(activeX[i]);
break;
} catch(e) {}
}
} finally {
return {conn : http, tId : transactionId};
}
}
var pub = {
request : function(method, uri, cb, data, options) {
if(options){
var me = this,
xmlData = options.xmlData,
jsonData = options.jsonData,
hs;
Ext.applyIf(me, options);
if(xmlData || jsonData){
hs = me.headers;
if(!hs || !hs[CONTENTTYPE]){
initHeader(CONTENTTYPE, xmlData ? 'text/xml' : 'application/json');
}
data = xmlData || (!Ext.isPrimitive(jsonData) ? Ext.encode(jsonData) : jsonData);
}
}
return asyncRequest(method || options.method || "POST", uri, cb, data);
},
serializeForm : function(form) {
var fElements = form.elements || (document.forms[form] || Ext.getDom(form)).elements,
hasSubmit = false,
encoder = encodeURIComponent,
name,
data = '',
type,
hasValue;
Ext.each(fElements, function(element){
name = element.name;
type = element.type;
if (!element.disabled && name) {
if (/select-(one|multiple)/i.test(type)) {
Ext.each(element.options, function(opt){
if (opt.selected) {
hasValue = opt.hasAttribute ? opt.hasAttribute('value') : opt.getAttributeNode('value').specified;
data += String.format("{0}={1}&", encoder(name), encoder(hasValue ? opt.value : opt.text));
}
});
} else if (!(/file|undefined|reset|button/i.test(type))) {
if (!(/radio|checkbox/i.test(type) && !element.checked) && !(type == 'submit' && hasSubmit)) {
data += encoder(name) + '=' + encoder(element.value) + '&';
hasSubmit = /submit/i.test(type);
}
}
}
});
return data.substr(0, data.length - 1);
},
useDefaultHeader : true,
defaultPostHeader : 'application/x-www-form-urlencoded; charset=UTF-8',
useDefaultXhrHeader : true,
defaultXhrHeader : 'XMLHttpRequest',
poll : {},
timeout : {},
conn: {},
pollInterval : 50,
transactionId : 0,
// This is never called - Is it worth exposing this?
// setProgId : function(id) {
// activeX.unshift(id);
// },
// This is never called - Is it worth exposing this?
// setDefaultPostHeader : function(b) {
// this.useDefaultHeader = b;
// },
// This is never called - Is it worth exposing this?
// setDefaultXhrHeader : function(b) {
// this.useDefaultXhrHeader = b;
// },
// This is never called - Is it worth exposing this?
// setPollingInterval : function(i) {
// if (typeof i == 'number' && isFinite(i)) {
// this.pollInterval = i;
// }
// },
// This is never called - Is it worth exposing this?
// resetDefaultHeaders : function() {
// this.defaultHeaders = null;
// },
abort : function(o, callback, isTimeout) {
var me = this,
tId = o.tId,
isAbort = false;
if (me.isCallInProgress(o)) {
o.conn.abort();
clearInterval(me.poll[tId]);
me.poll[tId] = null;
clearTimeout(pub.timeout[tId]);
me.timeout[tId] = null;
handleTransactionResponse(o, callback, (isAbort = true), isTimeout);
}
return isAbort;
},
isCallInProgress : function(o) {
// if there is a connection and readyState is not 0 or 4
return o.conn && !{0:true,4:true}[o.conn.readyState];
}
};
return pub;
}();(function(){
var EXTLIB = Ext.lib,
noNegatives = /width|height|opacity|padding/i,
offsetAttribute = /^((width|height)|(top|left))$/,
defaultUnit = /width|height|top$|bottom$|left$|right$/i,
offsetUnit = /\d+(em|%|en|ex|pt|in|cm|mm|pc)$/i,
isset = function(v){
return typeof v !== 'undefined';
},
now = function(){
return new Date();
};
EXTLIB.Anim = {
motion : function(el, args, duration, easing, cb, scope) {
return this.run(el, args, duration, easing, cb, scope, Ext.lib.Motion);
},
run : function(el, args, duration, easing, cb, scope, type) {
type = type || Ext.lib.AnimBase;
if (typeof easing == "string") {
easing = Ext.lib.Easing[easing];
}
var anim = new type(el, args, duration, easing);
anim.animateX(function() {
if(Ext.isFunction(cb)){
cb.call(scope);
}
});
return anim;
}
};
EXTLIB.AnimBase = function(el, attributes, duration, method) {
if (el) {
this.init(el, attributes, duration, method);
}
};
EXTLIB.AnimBase.prototype = {
doMethod: function(attr, start, end) {
var me = this;
return me.method(me.curFrame, start, end - start, me.totalFrames);
},
setAttr: function(attr, val, unit) {
if (noNegatives.test(attr) && val < 0) {
val = 0;
}
Ext.fly(this.el, '_anim').setStyle(attr, val + unit);
},
getAttr: function(attr) {
var el = Ext.fly(this.el),
val = el.getStyle(attr),
a = offsetAttribute.exec(attr) || [];
if (val !== 'auto' && !offsetUnit.test(val)) {
return parseFloat(val);
}
return (!!(a[2]) || (el.getStyle('position') == 'absolute' && !!(a[3]))) ? el.dom['offset' + a[0].charAt(0).toUpperCase() + a[0].substr(1)] : 0;
},
getDefaultUnit: function(attr) {
return defaultUnit.test(attr) ? 'px' : '';
},
animateX : function(callback, scope) {
var me = this,
f = function() {
me.onComplete.removeListener(f);
if (Ext.isFunction(callback)) {
callback.call(scope || me, me);
}
};
me.onComplete.addListener(f, me);
me.animate();
},
setRunAttr: function(attr) {
var me = this,
a = this.attributes[attr],
to = a.to,
by = a.by,
from = a.from,
unit = a.unit,
ra = (this.runAttrs[attr] = {}),
end;
if (!isset(to) && !isset(by)){
return false;
}
var start = isset(from) ? from : me.getAttr(attr);
if (isset(to)) {
end = to;
}else if(isset(by)) {
if (Ext.isArray(start)){
end = [];
for(var i=0,len=start.length; i 0 && isFinite(tweak)){
if(tween.curFrame + tweak >= frames){
tweak = frames - (frame + 1);
}
tween.curFrame += tweak;
}
};
};
EXTLIB.Bezier = new function() {
this.getPosition = function(points, t) {
var n = points.length,
tmp = [],
c = 1 - t,
i,
j;
for (i = 0; i < n; ++i) {
tmp[i] = [points[i][0], points[i][1]];
}
for (j = 1; j < n; ++j) {
for (i = 0; i < n - j; ++i) {
tmp[i][0] = c * tmp[i][0] + t * tmp[parseInt(i + 1, 10)][0];
tmp[i][1] = c * tmp[i][1] + t * tmp[parseInt(i + 1, 10)][1];
}
}
return [ tmp[0][0], tmp[0][1] ];
};
};
EXTLIB.Easing = {
easeNone: function (t, b, c, d) {
return c * t / d + b;
},
easeIn: function (t, b, c, d) {
return c * (t /= d) * t + b;
},
easeOut: function (t, b, c, d) {
return -c * (t /= d) * (t - 2) + b;
}
};
(function() {
EXTLIB.Motion = function(el, attributes, duration, method) {
if (el) {
EXTLIB.Motion.superclass.constructor.call(this, el, attributes, duration, method);
}
};
Ext.extend(EXTLIB.Motion, Ext.lib.AnimBase);
var superclass = EXTLIB.Motion.superclass,
pointsRe = /^points$/i;
Ext.apply(EXTLIB.Motion.prototype, {
setAttr: function(attr, val, unit){
var me = this,
setAttr = superclass.setAttr;
if (pointsRe.test(attr)) {
unit = unit || 'px';
setAttr.call(me, 'left', val[0], unit);
setAttr.call(me, 'top', val[1], unit);
} else {
setAttr.call(me, attr, val, unit);
}
},
getAttr: function(attr){
var me = this,
getAttr = superclass.getAttr;
return pointsRe.test(attr) ? [getAttr.call(me, 'left'), getAttr.call(me, 'top')] : getAttr.call(me, attr);
},
doMethod: function(attr, start, end){
var me = this;
return pointsRe.test(attr)
? EXTLIB.Bezier.getPosition(me.runAttrs[attr], me.method(me.curFrame, 0, 100, me.totalFrames) / 100)
: superclass.doMethod.call(me, attr, start, end);
},
setRunAttr: function(attr){
if(pointsRe.test(attr)){
var me = this,
el = this.el,
points = this.attributes.points,
control = points.control || [],
from = points.from,
to = points.to,
by = points.by,
DOM = EXTLIB.Dom,
start,
i,
end,
len,
ra;
if(control.length > 0 && !Ext.isArray(control[0])){
control = [control];
}else{
/*
var tmp = [];
for (i = 0,len = control.length; i < len; ++i) {
tmp[i] = control[i];
}
control = tmp;
*/
}
Ext.fly(el, '_anim').position();
DOM.setXY(el, isset(from) ? from : DOM.getXY(el));
start = me.getAttr('points');
if(isset(to)){
end = translateValues.call(me, to, start);
for (i = 0,len = control.length; i < len; ++i) {
control[i] = translateValues.call(me, control[i], start);
}
} else if (isset(by)) {
end = [start[0] + by[0], start[1] + by[1]];
for (i = 0,len = control.length; i < len; ++i) {
control[i] = [ start[0] + control[i][0], start[1] + control[i][1] ];
}
}
ra = this.runAttrs[attr] = [start];
if (control.length > 0) {
ra = ra.concat(control);
}
ra[ra.length] = end;
}else{
superclass.setRunAttr.call(this, attr);
}
}
});
var translateValues = function(val, start) {
var pageXY = EXTLIB.Dom.getXY(this.el);
return [val[0] - pageXY[0] + start[0], val[1] - pageXY[1] + start[1]];
};
})();
})();// Easing functions
(function(){
// shortcuts to aid compression
var abs = Math.abs,
pi = Math.PI,
asin = Math.asin,
pow = Math.pow,
sin = Math.sin,
EXTLIB = Ext.lib;
Ext.apply(EXTLIB.Easing, {
easeBoth: function (t, b, c, d) {
return ((t /= d / 2) < 1) ? c / 2 * t * t + b : -c / 2 * ((--t) * (t - 2) - 1) + b;
},
easeInStrong: function (t, b, c, d) {
return c * (t /= d) * t * t * t + b;
},
easeOutStrong: function (t, b, c, d) {
return -c * ((t = t / d - 1) * t * t * t - 1) + b;
},
easeBothStrong: function (t, b, c, d) {
return ((t /= d / 2) < 1) ? c / 2 * t * t * t * t + b : -c / 2 * ((t -= 2) * t * t * t - 2) + b;
},
elasticIn: function (t, b, c, d, a, p) {
if (t == 0 || (t /= d) == 1) {
return t == 0 ? b : b + c;
}
p = p || (d * .3);
var s;
if (a >= abs(c)) {
s = p / (2 * pi) * asin(c / a);
} else {
a = c;
s = p / 4;
}
return -(a * pow(2, 10 * (t -= 1)) * sin((t * d - s) * (2 * pi) / p)) + b;
},
elasticOut: function (t, b, c, d, a, p) {
if (t == 0 || (t /= d) == 1) {
return t == 0 ? b : b + c;
}
p = p || (d * .3);
var s;
if (a >= abs(c)) {
s = p / (2 * pi) * asin(c / a);
} else {
a = c;
s = p / 4;
}
return a * pow(2, -10 * t) * sin((t * d - s) * (2 * pi) / p) + c + b;
},
elasticBoth: function (t, b, c, d, a, p) {
if (t == 0 || (t /= d / 2) == 2) {
return t == 0 ? b : b + c;
}
p = p || (d * (.3 * 1.5));
var s;
if (a >= abs(c)) {
s = p / (2 * pi) * asin(c / a);
} else {
a = c;
s = p / 4;
}
return t < 1 ?
-.5 * (a * pow(2, 10 * (t -= 1)) * sin((t * d - s) * (2 * pi) / p)) + b :
a * pow(2, -10 * (t -= 1)) * sin((t * d - s) * (2 * pi) / p) * .5 + c + b;
},
backIn: function (t, b, c, d, s) {
s = s || 1.70158;
return c * (t /= d) * t * ((s + 1) * t - s) + b;
},
backOut: function (t, b, c, d, s) {
if (!s) {
s = 1.70158;
}
return c * ((t = t / d - 1) * t * ((s + 1) * t + s) + 1) + b;
},
backBoth: function (t, b, c, d, s) {
s = s || 1.70158;
return ((t /= d / 2 ) < 1) ?
c / 2 * (t * t * (((s *= (1.525)) + 1) * t - s)) + b :
c / 2 * ((t -= 2) * t * (((s *= (1.525)) + 1) * t + s) + 2) + b;
},
bounceIn: function (t, b, c, d) {
return c - EXTLIB.Easing.bounceOut(d - t, 0, c, d) + b;
},
bounceOut: function (t, b, c, d) {
if ((t /= d) < (1 / 2.75)) {
return c * (7.5625 * t * t) + b;
} else if (t < (2 / 2.75)) {
return c * (7.5625 * (t -= (1.5 / 2.75)) * t + .75) + b;
} else if (t < (2.5 / 2.75)) {
return c * (7.5625 * (t -= (2.25 / 2.75)) * t + .9375) + b;
}
return c * (7.5625 * (t -= (2.625 / 2.75)) * t + .984375) + b;
},
bounceBoth: function (t, b, c, d) {
return (t < d / 2) ?
EXTLIB.Easing.bounceIn(t * 2, 0, c, d) * .5 + b :
EXTLIB.Easing.bounceOut(t * 2 - d, 0, c, d) * .5 + c * .5 + b;
}
});
})();
(function() {
var EXTLIB = Ext.lib;
// Color Animation
EXTLIB.Anim.color = function(el, args, duration, easing, cb, scope) {
return EXTLIB.Anim.run(el, args, duration, easing, cb, scope, EXTLIB.ColorAnim);
};
EXTLIB.ColorAnim = function(el, attributes, duration, method) {
EXTLIB.ColorAnim.superclass.constructor.call(this, el, attributes, duration, method);
};
Ext.extend(EXTLIB.ColorAnim, EXTLIB.AnimBase);
var superclass = EXTLIB.ColorAnim.superclass,
colorRE = /color$/i,
transparentRE = /^transparent|rgba\(0, 0, 0, 0\)$/,
rgbRE = /^rgb\(([0-9]+)\s*,\s*([0-9]+)\s*,\s*([0-9]+)\)$/i,
hexRE= /^#?([0-9A-F]{2})([0-9A-F]{2})([0-9A-F]{2})$/i,
hex3RE = /^#?([0-9A-F]{1})([0-9A-F]{1})([0-9A-F]{1})$/i,
isset = function(v){
return typeof v !== 'undefined';
};
// private
function parseColor(s) {
var pi = parseInt,
base,
out = null,
c;
if (s.length == 3) {
return s;
}
Ext.each([hexRE, rgbRE, hex3RE], function(re, idx){
base = (idx % 2 == 0) ? 16 : 10;
c = re.exec(s);
if(c && c.length == 4){
out = [pi(c[1], base), pi(c[2], base), pi(c[3], base)];
return false;
}
});
return out;
}
Ext.apply(EXTLIB.ColorAnim.prototype, {
getAttr : function(attr) {
var me = this,
el = me.el,
val;
if(colorRE.test(attr)){
while(el && transparentRE.test(val = Ext.fly(el).getStyle(attr))){
el = el.parentNode;
val = "fff";
}
}else{
val = superclass.getAttr.call(me, attr);
}
return val;
},
doMethod : function(attr, start, end) {
var me = this,
val,
floor = Math.floor,
i,
len,
v;
if(colorRE.test(attr)){
val = [];
end = end || [];
for(i = 0, len = start.length; i < len; i++) {
v = start[i];
val[i] = superclass.doMethod.call(me, attr, v, end[i]);
}
val = 'rgb(' + floor(val[0]) + ',' + floor(val[1]) + ',' + floor(val[2]) + ')';
}else{
val = superclass.doMethod.call(me, attr, start, end);
}
return val;
},
setRunAttr : function(attr) {
var me = this,
a = me.attributes[attr],
to = a.to,
by = a.by,
ra;
superclass.setRunAttr.call(me, attr);
ra = me.runAttrs[attr];
if(colorRE.test(attr)){
var start = parseColor(ra.start),
end = parseColor(ra.end);
if(!isset(to) && isset(by)){
end = parseColor(by);
for(var i=0,len=start.length; i0;){O=w[P];if(N.hasOwnProperty(O)){R=N[O];if(typeof R=="function"){R.$owner=t;R.$name=O}Q[O]=R}}}},define:function(R,P,N){var t=P.override,T,Q,e,O;if(t){delete P.override;T=Ext.getClassByName(t);Ext.override(T,P)}else{if(R){O=Ext.createNamespace(R,true);e=R.substring(R.lastIndexOf(".")+1)}T=function S(){this.constructor.apply(this,arguments)};if(R){T.displayName=R}T.$isClass=true;T.callParent=Ext.Base.callParent;if(typeof P=="function"){P=P(T)}Q=P.extend;if(Q){delete P.extend;if(typeof Q=="string"){Q=Ext.getClassByName(Q)}}else{Q=k}Ext.extend(T,Q,P);if(T.prototype.constructor===T){delete T.prototype.constructor}if(!T.prototype.$isClass){Ext.applyIf(T.prototype,k.prototype)}T.prototype.self=T;if(P.xtype){Ext.reg(P.xtype,T)}T=P.singleton?new T():T;if(R){O[e]=T}}if(N){N.call(T)}return T},override:function(P,R){var N,Q;if(R){if(P.$isClass){Q=R.statics;if(Q){delete R.statics}Ext.addMembers(P,P.prototype,R,true);if(Q){Ext.addMembers(P,P,Q)}}else{if(typeof P=="function"){N=P.prototype;Ext.apply(N,R);if(Ext.isIE&&R.hasOwnProperty("toString")){N.toString=R.toString}}else{var e=P.self,t,O;if(e&&e.$isClass){for(t in R){if(R.hasOwnProperty(t)){O=R[t];if(typeof O=="function"){if(e.$className){O.displayName=e.$className+"#"+t}O.$name=t;O.$owner=e;O.$previous=P.hasOwnProperty(t)?P[t]:l}P[t]=O}}}else{Ext.apply(P,R);if(!P.constructor.$isClass){P.constructor.prototype.callParent=k.prototype.callParent;P.constructor.callParent=k.callParent}}}}}},namespace:function(){var O=arguments.length,P=0,t,N,e,R,Q,S;for(;P0){return setTimeout(d,c)}d();return 0}});Ext.applyIf(String,{format:function(b){var a=Ext.toArray(arguments,1);return b.replace(/\{(\d+)\}/g,function(c,d){return a[d]})}});Ext.applyIf(Array.prototype,{indexOf:function(b,c){var a=this.length;c=c||0;c+=(c<0)?a:0;for(;c0){for(var p=0;p0);if(!A){A=true;for(I=0;I=0){B=s.substr(0,A).toLowerCase();if(s.charAt(A+1)==" "){++A}C[B]=s.substr(A+1)}})}catch(z){}return{tId:u.tId,status:v?204:w.status,statusText:v?"No Content":w.statusText,getResponseHeader:function(s){return C[s.toLowerCase()]},getAllResponseHeaders:function(){return x},responseText:w.responseText,responseXML:w.responseXML,argument:y}}function o(s){if(s.tId){k.conn[s.tId]=null}s.conn=null;s=null}function f(x,y,t,s){if(!y){o(x);return}var v,u;try{if(x.conn.status!==undefined&&x.conn.status!=0){v=x.conn.status}else{v=13030}}catch(w){v=13030}if((v>=200&&v<300)||(Ext.isIE&&v==1223)){u=p(x,y.argument);if(y.success){if(!y.scope){y.success(u)}else{y.success.apply(y.scope,[u])}}}else{switch(v){case 12002:case 12029:case 12030:case 12031:case 12152:case 13030:u=e(x.tId,y.argument,(t?t:false),s);if(y.failure){if(!y.scope){y.failure(u)}else{y.failure.apply(y.scope,[u])}}break;default:u=p(x,y.argument);if(y.failure){if(!y.scope){y.failure(u)}else{y.failure.apply(y.scope,[u])}}}}o(x);u=null}function m(u,x,s,w,t,v){if(s&&s.readyState==4){clearInterval(t[w]);t[w]=null;if(v){clearTimeout(k.timeout[w]);k.timeout[w]=null}f(u,x)}}function r(s,t){k.abort(s,t,true)}function n(u,x){x=x||{};var s=u.conn,w=u.tId,t=k.poll,v=x.timeout||null;if(v){k.conn[w]=s;k.timeout[w]=setTimeout(r.createCallback(u,x),v)}t[w]=setInterval(m.createCallback(u,x,s,w,t,v),k.pollInterval)}function i(w,t,v,s){var u=l()||null;if(u){u.conn.open(w,t,true);if(k.useDefaultXhrHeader){j("X-Requested-With",k.defaultXhrHeader)}if(s&&k.useDefaultHeader&&(!k.headers||!k.headers[d])){j(d,k.defaultPostHeader)}if(k.defaultHeaders||k.headers){h(u)}n(u,v);u.conn.send(s||null)}return u}function l(){var t;try{if(t=q(k.transactionId)){k.transactionId++}}catch(s){}finally{return t}}function q(v){var s;try{s=new XMLHttpRequest()}catch(u){for(var t=Ext.isIE6?1:0;t0&&isFinite(w)){if(r.curFrame+w>=v){w=v-(u+1)}r.curFrame+=w}}};g.Bezier=new function(){this.getPosition=function(p,o){var r=p.length,m=[],q=1-o,l,k;for(l=0;l0&&!Ext.isArray(s[0])){s=[s]}else{}Ext.fly(p,"_anim").position();A.setXY(p,j(x)?x:A.getXY(p));o=w.getAttr("points");if(j(y)){q=k.call(w,y,o);for(r=0,t=s.length;r0){n=n.concat(s)}n[n.length]=q}else{m.setRunAttr.call(this,u)}}});var k=function(n,p){var o=g.Dom.getXY(this.el);return[n[0]-o[0]+p[0],n[1]-o[1]+p[1]]}})()})();(function(){var d=Math.abs,i=Math.PI,h=Math.asin,g=Math.pow,e=Math.sin,f=Ext.lib;Ext.apply(f.Easing,{easeBoth:function(k,j,m,l){return((k/=l/2)<1)?m/2*k*k+j:-m/2*((--k)*(k-2)-1)+j},easeInStrong:function(k,j,m,l){return m*(k/=l)*k*k*k+j},easeOutStrong:function(k,j,m,l){return -m*((k=k/l-1)*k*k*k-1)+j},easeBothStrong:function(k,j,m,l){return((k/=l/2)<1)?m/2*k*k*k*k+j:-m/2*((k-=2)*k*k*k-2)+j},elasticIn:function(l,j,q,o,k,n){if(l==0||(l/=o)==1){return l==0?j:j+q}n=n||(o*0.3);var m;if(k>=d(q)){m=n/(2*i)*h(q/k)}else{k=q;m=n/4}return -(k*g(2,10*(l-=1))*e((l*o-m)*(2*i)/n))+j},elasticOut:function(l,j,q,o,k,n){if(l==0||(l/=o)==1){return l==0?j:j+q}n=n||(o*0.3);var m;if(k>=d(q)){m=n/(2*i)*h(q/k)}else{k=q;m=n/4}return k*g(2,-10*l)*e((l*o-m)*(2*i)/n)+q+j},elasticBoth:function(l,j,q,o,k,n){if(l==0||(l/=o/2)==2){return l==0?j:j+q}n=n||(o*(0.3*1.5));var m;if(k>=d(q)){m=n/(2*i)*h(q/k)}else{k=q;m=n/4}return l<1?-0.5*(k*g(2,10*(l-=1))*e((l*o-m)*(2*i)/n))+j:k*g(2,-10*(l-=1))*e((l*o-m)*(2*i)/n)*0.5+q+j},backIn:function(k,j,n,m,l){l=l||1.70158;return n*(k/=m)*k*((l+1)*k-l)+j},backOut:function(k,j,n,m,l){if(!l){l=1.70158}return n*((k=k/m-1)*k*((l+1)*k+l)+1)+j},backBoth:function(k,j,n,m,l){l=l||1.70158;return((k/=m/2)<1)?n/2*(k*k*(((l*=(1.525))+1)*k-l))+j:n/2*((k-=2)*k*(((l*=(1.525))+1)*k+l)+2)+j},bounceIn:function(k,j,m,l){return m-f.Easing.bounceOut(l-k,0,m,l)+j},bounceOut:function(k,j,m,l){if((k/=l)<(1/2.75)){return m*(7.5625*k*k)+j}else{if(k<(2/2.75)){return m*(7.5625*(k-=(1.5/2.75))*k+0.75)+j}else{if(k<(2.5/2.75)){return m*(7.5625*(k-=(2.25/2.75))*k+0.9375)+j}}}return m*(7.5625*(k-=(2.625/2.75))*k+0.984375)+j},bounceBoth:function(k,j,m,l){return(k
* For example:
*
Employee = Ext.extend(Ext.util.Observable, {
constructor: function(config){
this.name = config.name;
this.addEvents({
"fired" : true,
"quit" : true
});
// Copy configured listeners into *this* object so that the base class's
// constructor will add them.
this.listeners = config.listeners;
// Call our superclass constructor to complete construction process.
Employee.superclass.constructor.call(this, config)
}
});
* This could then be used like this:
var newEmployee = new Employee({
name: employeeName,
listeners: {
quit: function() {
// By default, "this" will be the object that fired the event.
alert(this.name + " has quit!");
}
}
});
*/
EXTUTIL.Observable = function(){
/**
* @cfg {Object} listeners (optional) A config object containing one or more event handlers to be added to this
* object during initialization. This should be a valid listeners config object as specified in the
* {@link #addListener} example for attaching multiple handlers at once.
* DOM events from ExtJs {@link Ext.Component Components}
* While some ExtJs Component classes export selected DOM events (e.g. "click", "mouseover" etc), this
* is usually only done when extra value can be added. For example the {@link Ext.DataView DataView}'s
* {@link Ext.DataView#click click} event passing the node clicked on. To access DOM
* events directly from a Component's HTMLElement, listeners must be added to the {@link Ext.Component#getEl Element} after the Component
* has been rendered. A plugin can simplify this step:
// Plugin is configured with a listeners config object.
// The Component is appended to the argument list of all handler functions.
Ext.DomObserver = Ext.extend(Object, {
constructor: function(config) {
this.listeners = config.listeners ? config.listeners : config;
},
// Component passes itself into plugin's init method
init: function(c) {
var p, l = this.listeners;
for (p in l) {
if (Ext.isFunction(l[p])) {
l[p] = this.createHandler(l[p], c);
} else {
l[p].fn = this.createHandler(l[p].fn, c);
}
}
// Add the listeners to the Element immediately following the render call
c.render = c.render.{@link Function#createSequence createSequence}(function() {
var e = c.getEl();
if (e) {
e.on(l);
}
});
},
createHandler: function(fn, c) {
return function(e) {
fn.call(this, e, c);
};
}
});
var combo = new Ext.form.ComboBox({
// Collapse combo when its element is clicked on
plugins: [ new Ext.DomObserver({
click: function(evt, comp) {
comp.collapse();
}
})],
store: myStore,
typeAhead: true,
mode: 'local',
triggerAction: 'all'
});
*
*/
var me = this, e = me.events;
if(me.listeners){
me.on(me.listeners);
delete me.listeners;
}
me.events = e || {};
};
EXTUTIL.Observable.prototype = {
// private
filterOptRe : /^(?:scope|delay|buffer|single)$/,
/**
* Fires the specified event with the passed parameters (minus the event name).
* An event may be set to bubble up an Observable parent hierarchy (See {@link Ext.Component#getBubbleTarget})
* by calling {@link #enableBubble}.
* @param {String} eventName The name of the event to fire.
* @param {Object...} args Variable number of parameters are passed to handlers.
* @return {Boolean} returns false if any of the handlers return false otherwise it returns true.
*/
fireEvent : function(){
var a = Array.prototype.slice.call(arguments, 0),
ename = a[0].toLowerCase(),
me = this,
ret = TRUE,
ce = me.events[ename],
cc,
q,
c;
if (me.eventsSuspended === TRUE) {
if (q = me.eventQueue) {
q.push(a);
}
}
else if(typeof ce == 'object') {
if (ce.bubble){
if(ce.fire.apply(ce, a.slice(1)) === FALSE) {
return FALSE;
}
c = me.getBubbleTarget && me.getBubbleTarget();
if(c && c.enableBubble) {
cc = c.events[ename];
if(!cc || typeof cc != 'object' || !cc.bubble) {
c.enableBubble(ename);
}
return c.fireEvent.apply(c, a);
}
}
else {
a.shift();
ret = ce.fire.apply(ce, a);
}
}
return ret;
},
/**
* Appends an event handler to this object.
* @param {String} eventName The name of the event to listen for.
* @param {Function} handler The method the event invokes.
* @param {Object} scope (optional) The scope (this reference) in which the handler function is executed.
* If omitted, defaults to the object which fired the event.
* @param {Object} options (optional) An object containing handler configuration.
* properties. This may contain any of the following properties:
* scope : ObjectThe scope (this reference) in which the handler function is executed.
* If omitted, defaults to the object which fired the event.
* delay : NumberThe number of milliseconds to delay the invocation of the handler after the event fires.
* single : BooleanTrue to add a handler to handle just the next firing of the event, and then remove itself.
* buffer : NumberCauses the handler to be scheduled to run in an {@link Ext.util.DelayedTask} delayed
* by the specified number of milliseconds. If the event fires again within that time, the original
* handler is not invoked, but the new handler is scheduled in its place.
* target : ObservableOnly call the handler if the event was fired on the target Observable, not
* if the event was bubbled up from a child Observable.
*
*
* Combining Options
* Using the options argument, it is possible to combine different types of listeners:
*
* A delayed, one-time listener.
*
myDataView.on('click', this.onClick, this, {
single: true,
delay: 100
});
*
* Attaching multiple handlers in 1 call
* The method also allows for a single argument to be passed which is a config object containing properties
* which specify multiple handlers.
*
*
myGridPanel.on({
'click' : {
fn: this.onClick,
scope: this,
delay: 100
},
'mouseover' : {
fn: this.onMouseOver,
scope: this
},
'mouseout' : {
fn: this.onMouseOut,
scope: this
}
});
*
* Or a shorthand syntax:
*
myGridPanel.on({
'click' : this.onClick,
'mouseover' : this.onMouseOver,
'mouseout' : this.onMouseOut,
scope: this
});
*/
addListener : function(eventName, fn, scope, o){
var me = this,
e,
oe,
ce;
if (typeof eventName == 'object') {
o = eventName;
for (e in o) {
oe = o[e];
if (!me.filterOptRe.test(e)) {
me.addListener(e, oe.fn || oe, oe.scope || o.scope, oe.fn ? oe : o);
}
}
} else {
eventName = eventName.toLowerCase();
ce = me.events[eventName] || TRUE;
if (typeof ce == 'boolean') {
me.events[eventName] = ce = new EXTUTIL.Event(me, eventName);
}
ce.addListener(fn, scope, typeof o == 'object' ? o : {});
}
},
/**
* Removes an event handler.
* @param {String} eventName The type of event the handler was associated with.
* @param {Function} handler The handler to remove. This must be a reference to the function passed into the {@link #addListener} call.
* @param {Object} scope (optional) The scope originally specified for the handler.
*/
removeListener : function(eventName, fn, scope){
var ce = this.events[eventName.toLowerCase()];
if (typeof ce == 'object') {
ce.removeListener(fn, scope);
}
},
/**
* Removes all listeners for this object
*/
purgeListeners : function(){
var events = this.events,
evt,
key;
for(key in events){
evt = events[key];
if(typeof evt == 'object'){
evt.clearListeners();
}
}
},
/**
* Adds the specified events to the list of events which this Observable may fire.
* @param {Object|String} o Either an object with event names as properties with a value of true
* or the first event name string if multiple event names are being passed as separate parameters.
* @param {string} Optional. Event name if multiple event names are being passed as separate parameters.
* Usage:
this.addEvents('storeloaded', 'storecleared');
*/
addEvents : function(o){
var me = this;
me.events = me.events || {};
if (typeof o == 'string') {
var a = arguments,
i = a.length;
while(i--) {
me.events[a[i]] = me.events[a[i]] || TRUE;
}
} else {
Ext.applyIf(me.events, o);
}
},
/**
* Checks to see if this object has any listeners for a specified event
* @param {String} eventName The name of the event to check for
* @return {Boolean} True if the event is being listened for, else false
*/
hasListener : function(eventName){
var e = this.events[eventName.toLowerCase()];
return typeof e == 'object' && e.listeners.length > 0;
},
/**
* Suspend the firing of all events. (see {@link #resumeEvents})
* @param {Boolean} queueSuspended Pass as true to queue up suspended events to be fired
* after the {@link #resumeEvents} call instead of discarding all suspended events;
*/
suspendEvents : function(queueSuspended){
this.eventsSuspended = TRUE;
if(queueSuspended && !this.eventQueue){
this.eventQueue = [];
}
},
/**
* Resume firing events. (see {@link #suspendEvents})
* If events were suspended using the queueSuspended parameter, then all
* events fired during event suspension will be sent to any listeners now.
*/
resumeEvents : function(){
var me = this,
queued = me.eventQueue || [];
me.eventsSuspended = FALSE;
delete me.eventQueue;
EACH(queued, function(e) {
me.fireEvent.apply(me, e);
});
}
};
var OBSERVABLE = EXTUTIL.Observable.prototype;
/**
* Appends an event handler to this object (shorthand for {@link #addListener}.)
* @param {String} eventName The type of event to listen for
* @param {Function} handler The method the event invokes
* @param {Object} scope (optional) The scope (this reference) in which the handler function is executed.
* If omitted, defaults to the object which fired the event.
* @param {Object} options (optional) An object containing handler configuration.
* @method
*/
OBSERVABLE.on = OBSERVABLE.addListener;
/**
* Removes an event handler (shorthand for {@link #removeListener}.)
* @param {String} eventName The type of event the handler was associated with.
* @param {Function} handler The handler to remove. This must be a reference to the function passed into the {@link #addListener} call.
* @param {Object} scope (optional) The scope originally specified for the handler.
* @method
*/
OBSERVABLE.un = OBSERVABLE.removeListener;
/**
* Removes all added captures from the Observable.
* @param {Observable} o The Observable to release
* @static
*/
EXTUTIL.Observable.releaseCapture = function(o){
o.fireEvent = OBSERVABLE.fireEvent;
};
function createTargeted(h, o, scope){
return function(){
if(o.target == arguments[0]){
h.apply(scope, Array.prototype.slice.call(arguments, 0));
}
};
};
function createBuffered(h, o, l, scope){
l.task = new EXTUTIL.DelayedTask();
return function(){
l.task.delay(o.buffer, h, scope, Array.prototype.slice.call(arguments, 0));
};
};
function createSingle(h, e, fn, scope){
return function(){
e.removeListener(fn, scope);
return h.apply(scope, arguments);
};
};
function createDelayed(h, o, l, scope){
return function(){
var task = new EXTUTIL.DelayedTask(),
args = Array.prototype.slice.call(arguments, 0);
if(!l.tasks) {
l.tasks = [];
}
l.tasks.push(task);
task.delay(o.delay || 10, function(){
l.tasks.remove(task);
h.apply(scope, args);
}, scope);
};
};
EXTUTIL.Event = function(obj, name){
this.name = name;
this.obj = obj;
this.listeners = [];
};
EXTUTIL.Event.prototype = {
addListener : function(fn, scope, options){
var me = this,
l;
scope = scope || me.obj;
if(!me.isListening(fn, scope)){
l = me.createListener(fn, scope, options);
if(me.firing){ // if we are currently firing this event, don't disturb the listener loop
me.listeners = me.listeners.slice(0);
}
me.listeners.push(l);
}
},
createListener: function(fn, scope, o){
o = o || {};
scope = scope || this.obj;
var l = {
fn: fn,
scope: scope,
options: o
}, h = fn;
if(o.target){
h = createTargeted(h, o, scope);
}
if(o.delay){
h = createDelayed(h, o, l, scope);
}
if(o.single){
h = createSingle(h, this, fn, scope);
}
if(o.buffer){
h = createBuffered(h, o, l, scope);
}
l.fireFn = h;
return l;
},
findListener : function(fn, scope){
var list = this.listeners,
i = list.length,
l;
scope = scope || this.obj;
while(i--){
l = list[i];
if(l){
if(l.fn == fn && l.scope == scope){
return i;
}
}
}
return -1;
},
isListening : function(fn, scope){
return this.findListener(fn, scope) != -1;
},
removeListener : function(fn, scope){
var index,
l,
k,
me = this,
ret = FALSE;
if((index = me.findListener(fn, scope)) != -1){
if (me.firing) {
me.listeners = me.listeners.slice(0);
}
l = me.listeners[index];
if(l.task) {
l.task.cancel();
delete l.task;
}
k = l.tasks && l.tasks.length;
if(k) {
while(k--) {
l.tasks[k].cancel();
}
delete l.tasks;
}
me.listeners.splice(index, 1);
ret = TRUE;
}
return ret;
},
// Iterate to stop any buffered/delayed events
clearListeners : function(){
var me = this,
l = me.listeners,
i = l.length;
while(i--) {
me.removeListener(l[i].fn, l[i].scope);
}
},
fire : function(){
var me = this,
listeners = me.listeners,
len = listeners.length,
i = 0,
l;
if(len > 0){
me.firing = TRUE;
var args = Array.prototype.slice.call(arguments, 0);
for (; i < len; i++) {
l = listeners[i];
if(l && l.fireFn.apply(l.scope || me.obj || window, args) === FALSE) {
return (me.firing = FALSE);
}
}
}
me.firing = FALSE;
return TRUE;
}
};
})();
/**
* @class Ext.DomHelper
* The DomHelper class provides a layer of abstraction from DOM and transparently supports creating
* elements via DOM or using HTML fragments. It also has the ability to create HTML fragment templates
* from your DOM building code.
*
* DomHelper element specification object
* A specification object is used when creating elements. Attributes of this object
* are assumed to be element attributes, except for 4 special attributes:
*
* tag : The tag name of the element
* children : or cn An array of the
* same kind of element definition objects to be created and appended. These can be nested
* as deep as you want.
* cls : The class attribute of the element.
* This will end up being either the "class" attribute on a HTML fragment or className
* for a DOM node, depending on whether DomHelper is using fragments or DOM.
* html : The innerHTML for the element
*
*
* Insertion methods
* Commonly used insertion methods:
*
* {@link #append} :
* {@link #insertBefore} :
* {@link #insertAfter} :
* {@link #overwrite} :
* {@link #createTemplate} :
* {@link #insertHtml} :
*
*
* Example
* This is an example, where an unordered list with 3 children items is appended to an existing
* element with id 'my-div' :
var dh = Ext.DomHelper; // create shorthand alias
// specification object
var spec = {
id: 'my-ul',
tag: 'ul',
cls: 'my-list',
// append children after creating
children: [ // may also specify 'cn' instead of 'children'
{tag: 'li', id: 'item0', html: 'List Item 0'},
{tag: 'li', id: 'item1', html: 'List Item 1'},
{tag: 'li', id: 'item2', html: 'List Item 2'}
]
};
var list = dh.append(
'my-div', // the context element 'my-div' can either be the id or the actual node
spec // the specification object
);
* Element creation specification parameters in this class may also be passed as an Array of
* specification objects. This can be used to insert multiple sibling nodes into an existing
* container very efficiently. For example, to add more list items to the example above:
dh.append('my-ul', [
{tag: 'li', id: 'item3', html: 'List Item 3'},
{tag: 'li', id: 'item4', html: 'List Item 4'}
]);
*
*
* Templating
* The real power is in the built-in templating. Instead of creating or appending any elements,
* {@link #createTemplate} returns a Template object which can be used over and over to
* insert new elements. Revisiting the example above, we could utilize templating this time:
*
// create the node
var list = dh.append('my-div', {tag: 'ul', cls: 'my-list'});
// get template
var tpl = dh.createTemplate({tag: 'li', id: 'item{0}', html: 'List Item {0}'});
for(var i = 0; i < 5, i++){
tpl.append(list, [i]); // use template to append to the actual node
}
*
* An example using a template:
var html = '{2} ';
var tpl = new Ext.DomHelper.createTemplate(html);
tpl.append('blog-roll', ['link1', 'http://www.jackslocum.com/', "Jack's Site"]);
tpl.append('blog-roll', ['link2', 'http://www.dustindiaz.com/', "Dustin's Site"]);
*
*
* The same example using named parameters:
var html = '{text} ';
var tpl = new Ext.DomHelper.createTemplate(html);
tpl.append('blog-roll', {
id: 'link1',
url: 'http://www.jackslocum.com/',
text: "Jack's Site"
});
tpl.append('blog-roll', {
id: 'link2',
url: 'http://www.dustindiaz.com/',
text: "Dustin's Site"
});
*
*
* Compiling Templates
* Templates are applied using regular expressions. The performance is great, but if
* you are adding a bunch of DOM elements using the same template, you can increase
* performance even further by {@link Ext.Template#compile "compiling"} the template.
* The way "{@link Ext.Template#compile compile()}" works is the template is parsed and
* broken up at the different variable points and a dynamic function is created and eval'ed.
* The generated function performs string concatenation of these parts and the passed
* variables instead of using regular expressions.
*
var html = '{text} ';
var tpl = new Ext.DomHelper.createTemplate(html);
tpl.compile();
//... use template like normal
*
*
* Performance Boost
* DomHelper will transparently create HTML fragments when it can. Using HTML fragments instead
* of DOM can significantly boost performance.
* Element creation specification parameters may also be strings. If {@link #useDom} is false ,
* then the string is used as innerHTML. If {@link #useDom} is true , a string specification
* results in the creation of a text node. Usage:
*
Ext.DomHelper.useDom = true; // force it to use DOM; reduces performance
*
* @singleton
*/
Ext.DomHelper = function(){
var tempTableEl = null,
emptyTags = /^(?:br|frame|hr|img|input|link|meta|range|spacer|wbr|area|param|col)$/i,
tableRe = /^table|tbody|tr|td$/i,
confRe = /tag|children|cn|html$/i,
tableElRe = /td|tr|tbody/i,
cssRe = /([a-z0-9-]+)\s*:\s*([^;\s]+(?:\s*[^;\s]+)*);?/gi,
endRe = /end/i,
pub,
// kill repeat to save bytes
afterbegin = 'afterbegin',
afterend = 'afterend',
beforebegin = 'beforebegin',
beforeend = 'beforeend',
ts = '',
tbs = ts+'',
tbe = ' '+te,
trs = tbs + '',
tre = ' '+tbe;
// private
function doInsert(el, o, returnElement, pos, sibling, append){
var newNode = pub.insertHtml(pos, Ext.getDom(el), createHtml(o));
return returnElement ? Ext.get(newNode, true) : newNode;
}
// build as innerHTML where available
function createHtml(o){
var b = '',
attr,
val,
key,
cn;
if(typeof o == "string"){
b = o;
} else if (Ext.isArray(o)) {
for (var i=0; i < o.length; i++) {
if(o[i]) {
b += createHtml(o[i]);
}
};
} else {
b += '<' + (o.tag = o.tag || 'div');
for (attr in o) {
val = o[attr];
if(!confRe.test(attr)){
if (typeof val == "object") {
b += ' ' + attr + '="';
for (key in val) {
b += key + ':' + val[key] + ';';
};
b += '"';
}else{
b += ' ' + ({cls : 'class', htmlFor : 'for'}[attr] || attr) + '="' + val + '"';
}
}
};
// Now either just close the tag or try to add children and close the tag.
if (emptyTags.test(o.tag)) {
b += '/>';
} else {
b += '>';
if ((cn = o.children || o.cn)) {
b += createHtml(cn);
} else if(o.html){
b += o.html;
}
b += '' + o.tag + '>';
}
}
return b;
}
function ieTable(depth, s, h, e){
tempTableEl.innerHTML = [s, h, e].join('');
var i = -1,
el = tempTableEl,
ns;
while(++i < depth){
el = el.firstChild;
}
// If the result is multiple siblings, then encapsulate them into one fragment.
if(ns = el.nextSibling){
var df = document.createDocumentFragment();
while(el){
ns = el.nextSibling;
df.appendChild(el);
el = ns;
}
el = df;
}
return el;
}
/**
* @ignore
* Nasty code for IE's broken table implementation
*/
function insertIntoTable(tag, where, el, html) {
var node,
before;
tempTableEl = tempTableEl || document.createElement('div');
if(tag == 'td' && (where == afterbegin || where == beforeend) ||
!tableElRe.test(tag) && (where == beforebegin || where == afterend)) {
return;
}
before = where == beforebegin ? el :
where == afterend ? el.nextSibling :
where == afterbegin ? el.firstChild : null;
if (where == beforebegin || where == afterend) {
el = el.parentNode;
}
if (tag == 'td' || (tag == 'tr' && (where == beforeend || where == afterbegin))) {
node = ieTable(4, trs, html, tre);
} else if ((tag == 'tbody' && (where == beforeend || where == afterbegin)) ||
(tag == 'tr' && (where == beforebegin || where == afterend))) {
node = ieTable(3, tbs, html, tbe);
} else {
node = ieTable(2, ts, html, te);
}
el.insertBefore(node, before);
return node;
}
/**
* @ignore
* Fix for IE9 createContextualFragment missing method
*/
function createContextualFragment(html){
var div = document.createElement("div"),
fragment = document.createDocumentFragment(),
i = 0,
length, childNodes;
div.innerHTML = html;
childNodes = div.childNodes;
length = childNodes.length;
for (; i < length; i++) {
fragment.appendChild(childNodes[i].cloneNode(true));
}
return fragment;
}
pub = {
/**
* Returns the markup for the passed Element(s) config.
* @param {Object} o The DOM object spec (and children)
* @return {String}
*/
markup : function(o){
return createHtml(o);
},
/**
* Applies a style specification to an element.
* @param {String/HTMLElement} el The element to apply styles to
* @param {String/Object/Function} styles A style specification string e.g. 'width:100px', or object in the form {width:'100px'}, or
* a function which returns such a specification.
*/
applyStyles : function(el, styles){
if (styles) {
var matches;
el = Ext.fly(el);
if (typeof styles == "function") {
styles = styles.call();
}
if (typeof styles == "string") {
/**
* Since we're using the g flag on the regex, we need to set the lastIndex.
* This automatically happens on some implementations, but not others, see:
* http://stackoverflow.com/questions/2645273/javascript-regular-expression-literal-persists-between-function-calls
* http://blog.stevenlevithan.com/archives/fixing-javascript-regexp
*/
cssRe.lastIndex = 0;
while ((matches = cssRe.exec(styles))) {
el.setStyle(matches[1], matches[2]);
}
} else if (typeof styles == "object") {
el.setStyle(styles);
}
}
},
/**
* Inserts an HTML fragment into the DOM.
* @param {String} where Where to insert the html in relation to el - beforeBegin, afterBegin, beforeEnd, afterEnd.
* @param {HTMLElement} el The context element
* @param {String} html The HTML fragment
* @return {HTMLElement} The new node
*/
insertHtml : function(where, el, html){
var hash = {},
hashVal,
range,
rangeEl,
setStart,
frag,
rs;
where = where.toLowerCase();
// add these here because they are used in both branches of the condition.
hash[beforebegin] = ['BeforeBegin', 'previousSibling'];
hash[afterend] = ['AfterEnd', 'nextSibling'];
if (el.insertAdjacentHTML) {
if(tableRe.test(el.tagName) && (rs = insertIntoTable(el.tagName.toLowerCase(), where, el, html))){
return rs;
}
// add these two to the hash.
hash[afterbegin] = ['AfterBegin', 'firstChild'];
hash[beforeend] = ['BeforeEnd', 'lastChild'];
if ((hashVal = hash[where])) {
el.insertAdjacentHTML(hashVal[0], html);
return el[hashVal[1]];
}
} else {
range = el.ownerDocument.createRange();
setStart = 'setStart' + (endRe.test(where) ? 'After' : 'Before');
if (hash[where]) {
range[setStart](el);
if (!range.createContextualFragment) {
frag = createContextualFragment(html);
}
else {
frag = range.createContextualFragment(html);
}
el.parentNode.insertBefore(frag, where == beforebegin ? el : el.nextSibling);
return el[(where == beforebegin ? 'previous' : 'next') + 'Sibling'];
} else {
rangeEl = (where == afterbegin ? 'first' : 'last') + 'Child';
if (el.firstChild) {
range[setStart](el[rangeEl]);
if (!range.createContextualFragment) {
frag = createContextualFragment(html);
}
else {
frag = range.createContextualFragment(html);
}
if(where == afterbegin){
el.insertBefore(frag, el.firstChild);
}else{
el.appendChild(frag);
}
} else {
el.innerHTML = html;
}
return el[rangeEl];
}
}
throw 'Illegal insertion point -> "' + where + '"';
},
/**
* Creates new DOM element(s) and inserts them before el.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
*/
insertBefore : function(el, o, returnElement){
return doInsert(el, o, returnElement, beforebegin);
},
/**
* Creates new DOM element(s) and inserts them after el.
* @param {Mixed} el The context element
* @param {Object} o The DOM object spec (and children)
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
*/
insertAfter : function(el, o, returnElement){
return doInsert(el, o, returnElement, afterend, 'nextSibling');
},
/**
* Creates new DOM element(s) and inserts them as the first child of el.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
*/
insertFirst : function(el, o, returnElement){
return doInsert(el, o, returnElement, afterbegin, 'firstChild');
},
/**
* Creates new DOM element(s) and appends them to el.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
*/
append : function(el, o, returnElement){
return doInsert(el, o, returnElement, beforeend, '', true);
},
/**
* Creates new DOM element(s) and overwrites the contents of el with them.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
*/
overwrite : function(el, o, returnElement){
el = Ext.getDom(el);
el.innerHTML = createHtml(o);
return returnElement ? Ext.get(el.firstChild) : el.firstChild;
},
createHtml : createHtml
};
return pub;
}();
/**
* @class Ext.Template
* Represents an HTML fragment template. Templates may be {@link #compile precompiled}
* for greater performance.
* For example usage {@link #Template see the constructor}.
*
* @constructor
* An instance of this class may be created by passing to the constructor either
* a single argument, or multiple arguments:
*
* single argument : String/Array
*
* The single argument may be either a String or an Array:
var t = new Ext.Template("<div>Hello {0}.</div>");
t.{@link #append}('some-element', ['foo']);
*
*
Array :
* An Array will be combined with
join('').
var t = new Ext.Template([
'<div name="{id}">',
'<span class="{cls}">{name:trim} {value:ellipsis(10)}</span>',
'</div>',
]);
t.{@link #compile}();
t.{@link #append}('some-element', {id: 'myid', cls: 'myclass', name: 'foo', value: 'bar'});
*
* multiple arguments : String, Object, Array, ...
*
* Multiple arguments will be combined with
join('').
*
var t = new Ext.Template(
'<div name="{id}">',
'<span class="{cls}">{name} {value}</span>',
'</div>',
// a configuration object:
{
compiled: true, // {@link #compile} immediately
disableFormats: true // See Notes below.
}
);
*
*
Notes :
*
* Formatting and disableFormats are not applicable for Ext Core.
* For a list of available format functions, see {@link Ext.util.Format}.
* disableFormats reduces {@link #apply} time
* when no formatting is required.
*
*
*
* @param {Mixed} config
*/
Ext.Template = function(html){
var me = this,
a = arguments,
buf = [],
v;
if (Ext.isArray(html)) {
html = html.join("");
} else if (a.length > 1) {
for(var i = 0, len = a.length; i < len; i++){
v = a[i];
if(typeof v == 'object'){
Ext.apply(me, v);
} else {
buf.push(v);
}
};
html = buf.join('');
}
/**@private*/
me.html = html;
/**
* @cfg {Boolean} compiled Specify true to compile the template
* immediately (see {@link #compile}).
* Defaults to false .
*/
if (me.compiled) {
me.compile();
}
};
Ext.Template.prototype = {
/**
* @cfg {RegExp} re The regular expression used to match template variables.
* Defaults to:
* re : /\{([\w\-]+)\}/g // for Ext Core
* re : /\{([\w\-]+)(?:\:([\w\.]*)(?:\((.*?)?\))?)?\}/g // for Ext JS
*
*/
re : /\{([\w\-]+)\}/g,
/**
* See {@link #re}.
* @type RegExp
* @property re
*/
/**
* Returns an HTML fragment of this template with the specified values applied.
* @param {Object/Array} values
* The template values. Can be an array if the params are numeric (i.e. {0})
* or an object (i.e. {foo: 'bar'}).
* @return {String} The HTML fragment
*/
applyTemplate : function(values){
var me = this;
return me.compiled ?
me.compiled(values) :
me.html.replace(me.re, function(m, name){
return values[name] !== undefined ? values[name] : "";
});
},
/**
* Sets the HTML used as the template and optionally compiles it.
* @param {String} html
* @param {Boolean} compile (optional) True to compile the template (defaults to undefined)
* @return {Ext.Template} this
*/
set : function(html, compile){
var me = this;
me.html = html;
me.compiled = null;
return compile ? me.compile() : me;
},
/**
* Compiles the template into an internal function, eliminating the RegEx overhead.
* @return {Ext.Template} this
*/
compile : function(){
var me = this,
sep = Ext.isGecko ? "+" : ",";
function fn(m, name){
name = "values['" + name + "']";
return "'"+ sep + '(' + name + " == undefined ? '' : " + name + ')' + sep + "'";
}
eval("this.compiled = function(values){ return " + (Ext.isGecko ? "'" : "['") +
me.html.replace(/\\/g, '\\\\').replace(/(\r\n|\n)/g, '\\n').replace(/'/g, "\\'").replace(this.re, fn) +
(Ext.isGecko ? "';};" : "'].join('');};"));
return me;
},
/**
* Applies the supplied values to the template and inserts the new node(s) as the first child of el.
* @param {Mixed} el The context element
* @param {Object/Array} values The template values. Can be an array if your params are numeric (i.e. {0}) or an object (i.e. {foo: 'bar'})
* @param {Boolean} returnElement (optional) true to return a Ext.Element (defaults to undefined)
* @return {HTMLElement/Ext.Element} The new node or Element
*/
insertFirst: function(el, values, returnElement){
return this.doInsert('afterBegin', el, values, returnElement);
},
/**
* Applies the supplied values to the template and inserts the new node(s) before el.
* @param {Mixed} el The context element
* @param {Object/Array} values The template values. Can be an array if your params are numeric (i.e. {0}) or an object (i.e. {foo: 'bar'})
* @param {Boolean} returnElement (optional) true to return a Ext.Element (defaults to undefined)
* @return {HTMLElement/Ext.Element} The new node or Element
*/
insertBefore: function(el, values, returnElement){
return this.doInsert('beforeBegin', el, values, returnElement);
},
/**
* Applies the supplied values to the template and inserts the new node(s) after el.
* @param {Mixed} el The context element
* @param {Object/Array} values The template values. Can be an array if your params are numeric (i.e. {0}) or an object (i.e. {foo: 'bar'})
* @param {Boolean} returnElement (optional) true to return a Ext.Element (defaults to undefined)
* @return {HTMLElement/Ext.Element} The new node or Element
*/
insertAfter : function(el, values, returnElement){
return this.doInsert('afterEnd', el, values, returnElement);
},
/**
* Applies the supplied values to the template and appends
* the new node(s) to the specified el.
* For example usage {@link #Template see the constructor}.
* @param {Mixed} el The context element
* @param {Object/Array} values
* The template values. Can be an array if the params are numeric (i.e. {0})
* or an object (i.e. {foo: 'bar'}).
* @param {Boolean} returnElement (optional) true to return an Ext.Element (defaults to undefined)
* @return {HTMLElement/Ext.Element} The new node or Element
*/
append : function(el, values, returnElement){
return this.doInsert('beforeEnd', el, values, returnElement);
},
doInsert : function(where, el, values, returnEl){
el = Ext.getDom(el);
var newNode = Ext.DomHelper.insertHtml(where, el, this.applyTemplate(values));
return returnEl ? Ext.get(newNode, true) : newNode;
},
/**
* Applies the supplied values to the template and overwrites the content of el with the new node(s).
* @param {Mixed} el The context element
* @param {Object/Array} values The template values. Can be an array if your params are numeric (i.e. {0}) or an object (i.e. {foo: 'bar'})
* @param {Boolean} returnElement (optional) true to return a Ext.Element (defaults to undefined)
* @return {HTMLElement/Ext.Element} The new node or Element
*/
overwrite : function(el, values, returnElement){
el = Ext.getDom(el);
el.innerHTML = this.applyTemplate(values);
return returnElement ? Ext.get(el.firstChild, true) : el.firstChild;
}
};
/**
* Alias for {@link #applyTemplate}
* Returns an HTML fragment of this template with the specified values applied.
* @param {Object/Array} values
* The template values. Can be an array if the params are numeric (i.e. {0})
* or an object (i.e. {foo: 'bar'}).
* @return {String} The HTML fragment
* @member Ext.Template
* @method apply
*/
Ext.Template.prototype.apply = Ext.Template.prototype.applyTemplate;
/**
* Creates a template from the passed element's value (display:none textarea, preferred) or innerHTML.
* @param {String/HTMLElement} el A DOM element or its id
* @param {Object} config A configuration object
* @return {Ext.Template} The created template
* @static
*/
Ext.Template.from = function(el, config){
el = Ext.getDom(el);
return new Ext.Template(el.value || el.innerHTML, config || '');
};
/*
* This is code is also distributed under MIT license for use
* with jQuery and prototype JavaScript libraries.
*/
/**
* @class Ext.DomQuery
Provides high performance selector/xpath processing by compiling queries into reusable functions. New pseudo classes and matchers can be plugged. It works on HTML and XML documents (if a content node is passed in).
DomQuery supports most of the CSS3 selectors spec , along with some custom selectors and basic XPath.
All selectors, attribute filters and pseudos below can be combined infinitely in any order. For example "div.foo:nth-child(odd)[@foo=bar].bar:first" would be a perfectly valid selector. Node filters are processed in the order in which they appear, which allows you to optimize your queries for your document structure.
Element Selectors:
* any element
E an element with the tag E
E F All descendent elements of E that have the tag F
E > F or E/F all direct children elements of E that have the tag F
E + F all elements with the tag F that are immediately preceded by an element with the tag E
E ~ F all elements with the tag F that are preceded by a sibling element with the tag E
Attribute Selectors:
The use of @ and quotes are optional. For example, div[@foo='bar'] is also a valid attribute selector.
E[foo] has an attribute "foo"
E[foo=bar] has an attribute "foo" that equals "bar"
E[foo^=bar] has an attribute "foo" that starts with "bar"
E[foo$=bar] has an attribute "foo" that ends with "bar"
E[foo*=bar] has an attribute "foo" that contains the substring "bar"
E[foo%=2] has an attribute "foo" that is evenly divisible by 2
E[foo!=bar] attribute "foo" does not equal "bar"
Pseudo Classes:
E:first-child E is the first child of its parent
E:last-child E is the last child of its parent
E:nth-child(n ) E is the n th child of its parent (1 based as per the spec)
E:nth-child(odd) E is an odd child of its parent
E:nth-child(even) E is an even child of its parent
E:only-child E is the only child of its parent
E:checked E is an element that is has a checked attribute that is true (e.g. a radio or checkbox)
E:first the first E in the resultset
E:last the last E in the resultset
E:nth(n ) the n th E in the resultset (1 based)
E:odd shortcut for :nth-child(odd)
E:even shortcut for :nth-child(even)
E:contains(foo) E's innerHTML contains the substring "foo"
E:nodeValue(foo) E contains a textNode with a nodeValue that equals "foo"
E:not(S) an E element that does not match simple selector S
E:has(S) an E element that has a descendent that matches simple selector S
E:next(S) an E element whose next sibling matches simple selector S
E:prev(S) an E element whose previous sibling matches simple selector S
E:any(S1|S2|S2) an E element which matches any of the simple selectors S1, S2 or S3//\\
CSS Value Selectors:
E{display=none} css value "display" that equals "none"
E{display^=none} css value "display" that starts with "none"
E{display$=none} css value "display" that ends with "none"
E{display*=none} css value "display" that contains the substring "none"
E{display%=2} css value "display" that is evenly divisible by 2
E{display!=none} css value "display" that does not equal "none"
* @singleton
*/
Ext.DomQuery = function(){
var cache = {},
simpleCache = {},
valueCache = {},
nonSpace = /\S/,
trimRe = /^\s+|\s+$/g,
tplRe = /\{(\d+)\}/g,
modeRe = /^(\s?[\/>+~]\s?|\s|$)/,
tagTokenRe = /^(#)?([\w\-\*]+)/,
nthRe = /(\d*)n\+?(\d*)/,
nthRe2 = /\D/,
// This is for IE MSXML which does not support expandos.
// IE runs the same speed using setAttribute, however FF slows way down
// and Safari completely fails so they need to continue to use expandos.
isIE = window.ActiveXObject ? true : false,
key = 30803;
// this eval is stop the compressor from
// renaming the variable to something shorter
eval("var batch = 30803;");
// Retrieve the child node from a particular
// parent at the specified index.
function child(parent, index){
var i = 0,
n = parent.firstChild;
while(n){
if(n.nodeType == 1){
if(++i == index){
return n;
}
}
n = n.nextSibling;
}
return null;
}
// retrieve the next element node
function next(n){
while((n = n.nextSibling) && n.nodeType != 1);
return n;
}
// retrieve the previous element node
function prev(n){
while((n = n.previousSibling) && n.nodeType != 1);
return n;
}
// Mark each child node with a nodeIndex skipping and
// removing empty text nodes.
function children(parent){
var n = parent.firstChild,
nodeIndex = -1,
nextNode;
while(n){
nextNode = n.nextSibling;
// clean worthless empty nodes.
if(n.nodeType == 3 && !nonSpace.test(n.nodeValue)){
parent.removeChild(n);
}else{
// add an expando nodeIndex
n.nodeIndex = ++nodeIndex;
}
n = nextNode;
}
return this;
}
// nodeSet - array of nodes
// cls - CSS Class
function byClassName(nodeSet, cls){
if(!cls){
return nodeSet;
}
var result = [], ri = -1;
for(var i = 0, ci; ci = nodeSet[i]; i++){
if((' '+ci.className+' ').indexOf(cls) != -1){
result[++ri] = ci;
}
}
return result;
};
function attrValue(n, attr){
// if its an array, use the first node.
if(!n.tagName && typeof n.length != "undefined"){
n = n[0];
}
if(!n){
return null;
}
if(attr == "for"){
return n.htmlFor;
}
if(attr == "class" || attr == "className"){
return n.className;
}
return n.getAttribute(attr) || n[attr];
};
// ns - nodes
// mode - false, /, >, +, ~
// tagName - defaults to "*"
function getNodes(ns, mode, tagName){
var result = [], ri = -1, cs;
if(!ns){
return result;
}
tagName = tagName || "*";
// convert to array
if(typeof ns.getElementsByTagName != "undefined"){
ns = [ns];
}
// no mode specified, grab all elements by tagName
// at any depth
if(!mode){
for(var i = 0, ni; ni = ns[i]; i++){
cs = ni.getElementsByTagName(tagName);
for(var j = 0, ci; ci = cs[j]; j++){
result[++ri] = ci;
}
}
// Direct Child mode (/ or >)
// E > F or E/F all direct children elements of E that have the tag
} else if(mode == "/" || mode == ">"){
var utag = tagName.toUpperCase();
for(var i = 0, ni, cn; ni = ns[i]; i++){
cn = ni.childNodes;
for(var j = 0, cj; cj = cn[j]; j++){
if(cj.nodeName == utag || cj.nodeName == tagName || tagName == '*'){
result[++ri] = cj;
}
}
}
// Immediately Preceding mode (+)
// E + F all elements with the tag F that are immediately preceded by an element with the tag E
}else if(mode == "+"){
var utag = tagName.toUpperCase();
for(var i = 0, n; n = ns[i]; i++){
while((n = n.nextSibling) && n.nodeType != 1);
if(n && (n.nodeName == utag || n.nodeName == tagName || tagName == '*')){
result[++ri] = n;
}
}
// Sibling mode (~)
// E ~ F all elements with the tag F that are preceded by a sibling element with the tag E
}else if(mode == "~"){
var utag = tagName.toUpperCase();
for(var i = 0, n; n = ns[i]; i++){
while((n = n.nextSibling)){
if (n.nodeName == utag || n.nodeName == tagName || tagName == '*'){
result[++ri] = n;
}
}
}
}
return result;
}
function concat(a, b){
if(b.slice){
return a.concat(b);
}
for(var i = 0, l = b.length; i < l; i++){
a[a.length] = b[i];
}
return a;
}
function byTag(cs, tagName){
if(cs.tagName || cs == document){
cs = [cs];
}
if(!tagName){
return cs;
}
var result = [], ri = -1;
tagName = tagName.toLowerCase();
for(var i = 0, ci; ci = cs[i]; i++){
if(ci.nodeType == 1 && ci.tagName.toLowerCase() == tagName){
result[++ri] = ci;
}
}
return result;
}
function byId(cs, id){
if(cs.tagName || cs == document){
cs = [cs];
}
if(!id){
return cs;
}
var result = [], ri = -1;
for(var i = 0, ci; ci = cs[i]; i++){
if(ci && ci.id == id){
result[++ri] = ci;
return result;
}
}
return result;
}
// operators are =, !=, ^=, $=, *=, %=, |= and ~=
// custom can be "{"
function byAttribute(cs, attr, value, op, custom){
var result = [],
ri = -1,
useGetStyle = custom == "{",
fn = Ext.DomQuery.operators[op],
a,
xml,
hasXml;
for(var i = 0, ci; ci = cs[i]; i++){
// skip non-element nodes.
if(ci.nodeType != 1){
continue;
}
// only need to do this for the first node
if(!hasXml){
xml = Ext.DomQuery.isXml(ci);
hasXml = true;
}
// we only need to change the property names if we're dealing with html nodes, not XML
if(!xml){
if(useGetStyle){
a = Ext.DomQuery.getStyle(ci, attr);
} else if (attr == "class" || attr == "className"){
a = ci.className;
} else if (attr == "for"){
a = ci.htmlFor;
} else if (attr == "href"){
// getAttribute href bug
// http://www.glennjones.net/Post/809/getAttributehrefbug.htm
a = ci.getAttribute("href", 2);
} else{
a = ci.getAttribute(attr);
}
}else{
a = ci.getAttribute(attr);
}
if((fn && fn(a, value)) || (!fn && a)){
result[++ri] = ci;
}
}
return result;
}
function byPseudo(cs, name, value){
return Ext.DomQuery.pseudos[name](cs, value);
}
function nodupIEXml(cs){
var d = ++key,
r;
cs[0].setAttribute("_nodup", d);
r = [cs[0]];
for(var i = 1, len = cs.length; i < len; i++){
var c = cs[i];
if(!c.getAttribute("_nodup") != d){
c.setAttribute("_nodup", d);
r[r.length] = c;
}
}
for(var i = 0, len = cs.length; i < len; i++){
cs[i].removeAttribute("_nodup");
}
return r;
}
function nodup(cs){
if(!cs){
return [];
}
var len = cs.length, c, i, r = cs, cj, ri = -1;
if(!len || typeof cs.nodeType != "undefined" || len == 1){
return cs;
}
if(isIE && typeof cs[0].selectSingleNode != "undefined"){
return nodupIEXml(cs);
}
var d = ++key;
cs[0]._nodup = d;
for(i = 1; c = cs[i]; i++){
if(c._nodup != d){
c._nodup = d;
}else{
r = [];
for(var j = 0; j < i; j++){
r[++ri] = cs[j];
}
for(j = i+1; cj = cs[j]; j++){
if(cj._nodup != d){
cj._nodup = d;
r[++ri] = cj;
}
}
return r;
}
}
return r;
}
function quickDiffIEXml(c1, c2){
var d = ++key,
r = [];
for(var i = 0, len = c1.length; i < len; i++){
c1[i].setAttribute("_qdiff", d);
}
for(var i = 0, len = c2.length; i < len; i++){
if(c2[i].getAttribute("_qdiff") != d){
r[r.length] = c2[i];
}
}
for(var i = 0, len = c1.length; i < len; i++){
c1[i].removeAttribute("_qdiff");
}
return r;
}
function quickDiff(c1, c2){
var len1 = c1.length,
d = ++key,
r = [];
if(!len1){
return c2;
}
if(isIE && typeof c1[0].selectSingleNode != "undefined"){
return quickDiffIEXml(c1, c2);
}
for(var i = 0; i < len1; i++){
c1[i]._qdiff = d;
}
for(var i = 0, len = c2.length; i < len; i++){
if(c2[i]._qdiff != d){
r[r.length] = c2[i];
}
}
return r;
}
function quickId(ns, mode, root, id){
if(ns == root){
var d = root.ownerDocument || root;
return d.getElementById(id);
}
ns = getNodes(ns, mode, "*");
return byId(ns, id);
}
return {
getStyle : function(el, name){
return Ext.fly(el).getStyle(name);
},
/**
* Compiles a selector/xpath query into a reusable function. The returned function
* takes one parameter "root" (optional), which is the context node from where the query should start.
* @param {String} selector The selector/xpath query
* @param {String} type (optional) Either "select" (the default) or "simple" for a simple selector match
* @return {Function}
*/
compile : function(path, type){
type = type || "select";
// setup fn preamble
var fn = ["var f = function(root){\n var mode; ++batch; var n = root || document;\n"],
mode,
lastPath,
matchers = Ext.DomQuery.matchers,
matchersLn = matchers.length,
modeMatch,
// accept leading mode switch
lmode = path.match(modeRe);
if(lmode && lmode[1]){
fn[fn.length] = 'mode="'+lmode[1].replace(trimRe, "")+'";';
path = path.replace(lmode[1], "");
}
// strip leading slashes
while(path.substr(0, 1)=="/"){
path = path.substr(1);
}
while(path && lastPath != path){
lastPath = path;
var tokenMatch = path.match(tagTokenRe);
if(type == "select"){
if(tokenMatch){
// ID Selector
if(tokenMatch[1] == "#"){
fn[fn.length] = 'n = quickId(n, mode, root, "'+tokenMatch[2]+'");';
}else{
fn[fn.length] = 'n = getNodes(n, mode, "'+tokenMatch[2]+'");';
}
path = path.replace(tokenMatch[0], "");
}else if(path.substr(0, 1) != '@'){
fn[fn.length] = 'n = getNodes(n, mode, "*");';
}
// type of "simple"
}else{
if(tokenMatch){
if(tokenMatch[1] == "#"){
fn[fn.length] = 'n = byId(n, "'+tokenMatch[2]+'");';
}else{
fn[fn.length] = 'n = byTag(n, "'+tokenMatch[2]+'");';
}
path = path.replace(tokenMatch[0], "");
}
}
while(!(modeMatch = path.match(modeRe))){
var matched = false;
for(var j = 0; j < matchersLn; j++){
var t = matchers[j];
var m = path.match(t.re);
if(m){
fn[fn.length] = t.select.replace(tplRe, function(x, i){
return m[i];
});
path = path.replace(m[0], "");
matched = true;
break;
}
}
// prevent infinite loop on bad selector
if(!matched){
throw 'Error parsing selector, parsing failed at "' + path + '"';
}
}
if(modeMatch[1]){
fn[fn.length] = 'mode="'+modeMatch[1].replace(trimRe, "")+'";';
path = path.replace(modeMatch[1], "");
}
}
// close fn out
fn[fn.length] = "return nodup(n);\n}";
// eval fn and return it
eval(fn.join(""));
return f;
},
/**
* Selects a group of elements.
* @param {String} selector The selector/xpath query (can be a comma separated list of selectors)
* @param {Node/String} root (optional) The start of the query (defaults to document).
* @return {Array} An Array of DOM elements which match the selector. If there are
* no matches, and empty Array is returned.
*/
jsSelect: function(path, root, type){
// set root to doc if not specified.
root = root || document;
if(typeof root == "string"){
root = document.getElementById(root);
}
var paths = path.split(","),
results = [];
// loop over each selector
for(var i = 0, len = paths.length; i < len; i++){
var subPath = paths[i].replace(trimRe, "");
// compile and place in cache
if(!cache[subPath]){
cache[subPath] = Ext.DomQuery.compile(subPath);
if(!cache[subPath]){
throw subPath + " is not a valid selector";
}
}
var result = cache[subPath](root);
if(result && result != document){
results = results.concat(result);
}
}
// if there were multiple selectors, make sure dups
// are eliminated
if(paths.length > 1){
return nodup(results);
}
return results;
},
isXml: function(el) {
var docEl = (el ? el.ownerDocument || el : 0).documentElement;
return docEl ? docEl.nodeName !== "HTML" : false;
},
select : document.querySelectorAll ? function(path, root, type) {
root = root || document;
if (!Ext.DomQuery.isXml(root)) {
try {
var cs = root.querySelectorAll(path);
return Ext.toArray(cs);
}
catch (ex) {}
}
return Ext.DomQuery.jsSelect.call(this, path, root, type);
} : function(path, root, type) {
return Ext.DomQuery.jsSelect.call(this, path, root, type);
},
/**
* Selects a single element.
* @param {String} selector The selector/xpath query
* @param {Node} root (optional) The start of the query (defaults to document).
* @return {Element} The DOM element which matched the selector.
*/
selectNode : function(path, root){
return Ext.DomQuery.select(path, root)[0];
},
/**
* Selects the value of a node, optionally replacing null with the defaultValue.
* @param {String} selector The selector/xpath query
* @param {Node} root (optional) The start of the query (defaults to document).
* @param {String} defaultValue (optional)
* @return {String}
*/
selectValue : function(path, root, defaultValue){
path = path.replace(trimRe, "");
if(!valueCache[path]){
valueCache[path] = Ext.DomQuery.compile(path, "select");
}
var n = valueCache[path](root), v;
n = n[0] ? n[0] : n;
// overcome a limitation of maximum textnode size
// Rumored to potentially crash IE6 but has not been confirmed.
// http://reference.sitepoint.com/javascript/Node/normalize
// https://developer.mozilla.org/En/DOM/Node.normalize
if (typeof n.normalize == 'function') n.normalize();
v = (n && n.firstChild ? n.firstChild.nodeValue : null);
return ((v === null||v === undefined||v==='') ? defaultValue : v);
},
/**
* Selects the value of a node, parsing integers and floats. Returns the defaultValue, or 0 if none is specified.
* @param {String} selector The selector/xpath query
* @param {Node} root (optional) The start of the query (defaults to document).
* @param {Number} defaultValue (optional)
* @return {Number}
*/
selectNumber : function(path, root, defaultValue){
var v = Ext.DomQuery.selectValue(path, root, defaultValue || 0);
return parseFloat(v);
},
/**
* Returns true if the passed element(s) match the passed simple selector (e.g. div.some-class or span:first-child)
* @param {String/HTMLElement/Array} el An element id, element or array of elements
* @param {String} selector The simple selector to test
* @return {Boolean}
*/
is : function(el, ss){
if(typeof el == "string"){
el = document.getElementById(el);
}
var isArray = Ext.isArray(el),
result = Ext.DomQuery.filter(isArray ? el : [el], ss);
return isArray ? (result.length == el.length) : (result.length > 0);
},
/**
* Filters an array of elements to only include matches of a simple selector (e.g. div.some-class or span:first-child)
* @param {Array} el An array of elements to filter
* @param {String} selector The simple selector to test
* @param {Boolean} nonMatches If true, it returns the elements that DON'T match
* the selector instead of the ones that match
* @return {Array} An Array of DOM elements which match the selector. If there are
* no matches, and empty Array is returned.
*/
filter : function(els, ss, nonMatches){
ss = ss.replace(trimRe, "");
if(!simpleCache[ss]){
simpleCache[ss] = Ext.DomQuery.compile(ss, "simple");
}
var result = simpleCache[ss](els);
return nonMatches ? quickDiff(result, els) : result;
},
/**
* Collection of matching regular expressions and code snippets.
* Each capture group within () will be replace the {} in the select
* statement as specified by their index.
*/
matchers : [{
re: /^\.([\w\-]+)/,
select: 'n = byClassName(n, " {1} ");'
}, {
re: /^\:([\w\-]+)(?:\(((?:[^\s>\/]*|.*?))\))?/,
select: 'n = byPseudo(n, "{1}", "{2}");'
},{
re: /^(?:([\[\{])(?:@)?([\w\-]+)\s?(?:(=|.=)\s?(["']?)(.*?)\4)?[\]\}])/,
select: 'n = byAttribute(n, "{2}", "{5}", "{3}", "{1}");'
}, {
re: /^#([\w\-]+)/,
select: 'n = byId(n, "{1}");'
},{
re: /^@([\w\-]+)/,
select: 'return {firstChild:{nodeValue:attrValue(n, "{1}")}};'
}
],
/**
* Collection of operator comparison functions. The default operators are =, !=, ^=, $=, *=, %=, |= and ~=.
* New operators can be added as long as the match the format c = where c is any character other than space, > <.
*/
operators : {
"=" : function(a, v){
return a == v;
},
"!=" : function(a, v){
return a != v;
},
"^=" : function(a, v){
return a && a.substr(0, v.length) == v;
},
"$=" : function(a, v){
return a && a.substr(a.length-v.length) == v;
},
"*=" : function(a, v){
return a && a.indexOf(v) !== -1;
},
"%=" : function(a, v){
return (a % v) == 0;
},
"|=" : function(a, v){
return a && (a == v || a.substr(0, v.length+1) == v+'-');
},
"~=" : function(a, v){
return a && (' '+a+' ').indexOf(' '+v+' ') != -1;
}
},
/**
* Object hash of "pseudo class" filter functions which are used when filtering selections. Each function is passed
* two parameters:
* A filter function returns an Array of DOM elements which conform to the pseudo class.
* In addition to the provided pseudo classes listed above such as first-child and nth-child,
* developers may add additional, custom psuedo class filters to select elements according to application-specific requirements.
* For example, to filter <a> elements to only return links to external resources:
*
Ext.DomQuery.pseudos.external = function(c, v){
var r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
// Include in result set only if it's a link to an external resource
if(ci.hostname != location.hostname){
r[++ri] = ci;
}
}
return r;
};
* Then external links could be gathered with the following statement:
var externalLinks = Ext.select("a:external");
*/
pseudos : {
"first-child" : function(c){
var r = [], ri = -1, n;
for(var i = 0, ci; ci = n = c[i]; i++){
while((n = n.previousSibling) && n.nodeType != 1);
if(!n){
r[++ri] = ci;
}
}
return r;
},
"last-child" : function(c){
var r = [], ri = -1, n;
for(var i = 0, ci; ci = n = c[i]; i++){
while((n = n.nextSibling) && n.nodeType != 1);
if(!n){
r[++ri] = ci;
}
}
return r;
},
"nth-child" : function(c, a) {
var r = [], ri = -1,
m = nthRe.exec(a == "even" && "2n" || a == "odd" && "2n+1" || !nthRe2.test(a) && "n+" + a || a),
f = (m[1] || 1) - 0, l = m[2] - 0;
for(var i = 0, n; n = c[i]; i++){
var pn = n.parentNode;
if (batch != pn._batch) {
var j = 0;
for(var cn = pn.firstChild; cn; cn = cn.nextSibling){
if(cn.nodeType == 1){
cn.nodeIndex = ++j;
}
}
pn._batch = batch;
}
if (f == 1) {
if (l == 0 || n.nodeIndex == l){
r[++ri] = n;
}
} else if ((n.nodeIndex + l) % f == 0){
r[++ri] = n;
}
}
return r;
},
"only-child" : function(c){
var r = [], ri = -1;;
for(var i = 0, ci; ci = c[i]; i++){
if(!prev(ci) && !next(ci)){
r[++ri] = ci;
}
}
return r;
},
"empty" : function(c){
var r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
var cns = ci.childNodes, j = 0, cn, empty = true;
while(cn = cns[j]){
++j;
if(cn.nodeType == 1 || cn.nodeType == 3){
empty = false;
break;
}
}
if(empty){
r[++ri] = ci;
}
}
return r;
},
"contains" : function(c, v){
var r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
if((ci.textContent||ci.innerText||'').indexOf(v) != -1){
r[++ri] = ci;
}
}
return r;
},
"nodeValue" : function(c, v){
var r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
if(ci.firstChild && ci.firstChild.nodeValue == v){
r[++ri] = ci;
}
}
return r;
},
"checked" : function(c){
var r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
if(ci.checked == true){
r[++ri] = ci;
}
}
return r;
},
"not" : function(c, ss){
return Ext.DomQuery.filter(c, ss, true);
},
"any" : function(c, selectors){
var ss = selectors.split('|'),
r = [], ri = -1, s;
for(var i = 0, ci; ci = c[i]; i++){
for(var j = 0; s = ss[j]; j++){
if(Ext.DomQuery.is(ci, s)){
r[++ri] = ci;
break;
}
}
}
return r;
},
"odd" : function(c){
return this["nth-child"](c, "odd");
},
"even" : function(c){
return this["nth-child"](c, "even");
},
"nth" : function(c, a){
return c[a-1] || [];
},
"first" : function(c){
return c[0] || [];
},
"last" : function(c){
return c[c.length-1] || [];
},
"has" : function(c, ss){
var s = Ext.DomQuery.select,
r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
if(s(ss, ci).length > 0){
r[++ri] = ci;
}
}
return r;
},
"next" : function(c, ss){
var is = Ext.DomQuery.is,
r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
var n = next(ci);
if(n && is(n, ss)){
r[++ri] = ci;
}
}
return r;
},
"prev" : function(c, ss){
var is = Ext.DomQuery.is,
r = [], ri = -1;
for(var i = 0, ci; ci = c[i]; i++){
var n = prev(ci);
if(n && is(n, ss)){
r[++ri] = ci;
}
}
return r;
}
}
};
}();
/**
* Selects an array of DOM nodes by CSS/XPath selector. Shorthand of {@link Ext.DomQuery#select}
* @param {String} path The selector/xpath query
* @param {Node} root (optional) The start of the query (defaults to document).
* @return {Array}
* @member Ext
* @method query
*/
Ext.query = Ext.DomQuery.select;
/**
* @class Ext.util.DelayedTask
* The DelayedTask class provides a convenient way to "buffer" the execution of a method,
* performing setTimeout where a new timeout cancels the old timeout. When called, the
* task will wait the specified time period before executing. If durng that time period,
* the task is called again, the original call will be cancelled. This continues so that
* the function is only called a single time for each iteration.
* This method is especially useful for things like detecting whether a user has finished
* typing in a text field. An example would be performing validation on a keypress. You can
* use this class to buffer the keypress events for a certain number of milliseconds, and
* perform only if they stop for that amount of time. Usage:
var task = new Ext.util.DelayedTask(function(){
alert(Ext.getDom('myInputField').value.length);
});
// Wait 500ms before calling our function. If the user presses another key
// during that 500ms, it will be cancelled and we'll wait another 500ms.
Ext.get('myInputField').on('keypress', function(){
task.{@link #delay}(500);
});
*
* Note that we are using a DelayedTask here to illustrate a point. The configuration
* option buffer for {@link Ext.util.Observable#addListener addListener/on} will
* also setup a delayed task for you to buffer events.
* @constructor The parameters to this constructor serve as defaults and are not required.
* @param {Function} fn (optional) The default function to call.
* @param {Object} scope (optional) The default scope (The this reference) in which the
* function is called. If not specified, this will refer to the browser window.
* @param {Array} args (optional) The default Array of arguments.
*/
Ext.util.DelayedTask = function(fn, scope, args){
var me = this,
id,
call = function(){
clearInterval(id);
id = null;
fn.apply(scope, args || []);
};
/**
* Cancels any pending timeout and queues a new one
* @param {Number} delay The milliseconds to delay
* @param {Function} newFn (optional) Overrides function passed to constructor
* @param {Object} newScope (optional) Overrides scope passed to constructor. Remember that if no scope
* is specified, this will refer to the browser window.
* @param {Array} newArgs (optional) Overrides args passed to constructor
*/
me.delay = function(delay, newFn, newScope, newArgs){
me.cancel();
fn = newFn || fn;
scope = newScope || scope;
args = newArgs || args;
id = setInterval(call, delay);
};
/**
* Cancel the last queued timeout
*/
me.cancel = function(){
if(id){
clearInterval(id);
id = null;
}
};
};/**
* @class Ext.Element
* Encapsulates a DOM element, adding simple DOM manipulation facilities, normalizing for browser differences.
* All instances of this class inherit the methods of {@link Ext.Fx} making visual effects easily available to all DOM elements.
* Note that the events documented in this class are not Ext events, they encapsulate browser events. To
* access the underlying browser event, see {@link Ext.EventObject#browserEvent}. Some older
* browsers may not support the full range of events. Which events are supported is beyond the control of ExtJs.
* Usage:
// by id
var el = Ext.get("my-div");
// by DOM element reference
var el = Ext.get(myDivElement);
* Animations
* When an element is manipulated, by default there is no animation.
*
var el = Ext.get("my-div");
// no animation
el.setWidth(100);
*
* Many of the functions for manipulating an element have an optional "animate" parameter. This
* parameter can be specified as boolean (true ) for default animation effects.
*
// default animation
el.setWidth(100, true);
*
*
* To configure the effects, an object literal with animation options to use as the Element animation
* configuration object can also be specified. Note that the supported Element animation configuration
* options are a subset of the {@link Ext.Fx} animation options specific to Fx effects. The supported
* Element animation configuration options are:
Option Default Description
--------- -------- ---------------------------------------------
{@link Ext.Fx#duration duration} .35 The duration of the animation in seconds
{@link Ext.Fx#easing easing} easeOut The easing method
{@link Ext.Fx#callback callback} none A function to execute when the anim completes
{@link Ext.Fx#scope scope} this The scope (this) of the callback function
*
*
// Element animation options object
var opt = {
{@link Ext.Fx#duration duration}: 1,
{@link Ext.Fx#easing easing}: 'elasticIn',
{@link Ext.Fx#callback callback}: this.foo,
{@link Ext.Fx#scope scope}: this
};
// animation with some options set
el.setWidth(100, opt);
*
* The Element animation object being used for the animation will be set on the options
* object as "anim", which allows you to stop or manipulate the animation. Here is an example:
*
// using the "anim" property to get the Anim object
if(opt.anim.isAnimated()){
opt.anim.stop();
}
*
* Also see the {@link #animate} method for another animation technique.
* Composite (Collections of) Elements
* For working with collections of Elements, see {@link Ext.CompositeElement}
* @constructor Create a new Element directly.
* @param {String/HTMLElement} element
* @param {Boolean} forceNew (optional) By default the constructor checks to see if there is already an instance of this element in the cache and if there is it returns the same instance. This will skip that check (useful for extending this class).
*/
(function(){
var DOC = document;
Ext.Element = function(element, forceNew){
var dom = typeof element == "string" ?
DOC.getElementById(element) : element,
id;
if(!dom) return null;
id = dom.id;
if(!forceNew && id && Ext.elCache[id]){ // element object already exists
return Ext.elCache[id].el;
}
/**
* The DOM element
* @type HTMLElement
*/
this.dom = dom;
/**
* The DOM element ID
* @type String
*/
this.id = id || Ext.id(dom);
};
var DH = Ext.DomHelper,
El = Ext.Element,
EC = Ext.elCache;
El.prototype = {
/**
* Sets the passed attributes as attributes of this element (a style attribute can be a string, object or function)
* @param {Object} o The object with the attributes
* @param {Boolean} useSet (optional) false to override the default setAttribute to use expandos.
* @return {Ext.Element} this
*/
set : function(o, useSet){
var el = this.dom,
attr,
val,
useSet = (useSet !== false) && !!el.setAttribute;
for (attr in o) {
if (o.hasOwnProperty(attr)) {
val = o[attr];
if (attr == 'style') {
DH.applyStyles(el, val);
} else if (attr == 'cls') {
el.className = val;
} else if (useSet) {
el.setAttribute(attr, val);
} else {
el[attr] = val;
}
}
}
return this;
},
// Mouse events
/**
* @event click
* Fires when a mouse click is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event contextmenu
* Fires when a right click is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event dblclick
* Fires when a mouse double click is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mousedown
* Fires when a mousedown is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mouseup
* Fires when a mouseup is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mouseover
* Fires when a mouseover is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mousemove
* Fires when a mousemove is detected with the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mouseout
* Fires when a mouseout is detected with the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mouseenter
* Fires when the mouse enters the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event mouseleave
* Fires when the mouse leaves the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
// Keyboard events
/**
* @event keypress
* Fires when a keypress is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event keydown
* Fires when a keydown is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event keyup
* Fires when a keyup is detected within the element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
// HTML frame/object events
/**
* @event load
* Fires when the user agent finishes loading all content within the element. Only supported by window, frames, objects and images.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event unload
* Fires when the user agent removes all content from a window or frame. For elements, it fires when the target element or any of its content has been removed.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event abort
* Fires when an object/image is stopped from loading before completely loaded.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event error
* Fires when an object/image/frame cannot be loaded properly.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event resize
* Fires when a document view is resized.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event scroll
* Fires when a document view is scrolled.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
// Form events
/**
* @event select
* Fires when a user selects some text in a text field, including input and textarea.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event change
* Fires when a control loses the input focus and its value has been modified since gaining focus.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event submit
* Fires when a form is submitted.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event reset
* Fires when a form is reset.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event focus
* Fires when an element receives focus either via the pointing device or by tab navigation.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event blur
* Fires when an element loses focus either via the pointing device or by tabbing navigation.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
// User Interface events
/**
* @event DOMFocusIn
* Where supported. Similar to HTML focus event, but can be applied to any focusable element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMFocusOut
* Where supported. Similar to HTML blur event, but can be applied to any focusable element.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMActivate
* Where supported. Fires when an element is activated, for instance, through a mouse click or a keypress.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
// DOM Mutation events
/**
* @event DOMSubtreeModified
* Where supported. Fires when the subtree is modified.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMNodeInserted
* Where supported. Fires when a node has been added as a child of another node.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMNodeRemoved
* Where supported. Fires when a descendant node of the element is removed.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMNodeRemovedFromDocument
* Where supported. Fires when a node is being removed from a document.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMNodeInsertedIntoDocument
* Where supported. Fires when a node is being inserted into a document.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMAttrModified
* Where supported. Fires when an attribute has been modified.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* @event DOMCharacterDataModified
* Where supported. Fires when the character data has been modified.
* @param {Ext.EventObject} e The {@link Ext.EventObject} encapsulating the DOM event.
* @param {HtmlElement} t The target of the event.
* @param {Object} o The options configuration passed to the {@link #addListener} call.
*/
/**
* The default unit to append to CSS values where a unit isn't provided (defaults to px).
* @type String
*/
defaultUnit : "px",
/**
* Returns true if this element matches the passed simple selector (e.g. div.some-class or span:first-child)
* @param {String} selector The simple selector to test
* @return {Boolean} True if this element matches the selector, else false
*/
is : function(simpleSelector){
return Ext.DomQuery.is(this.dom, simpleSelector);
},
/**
* Tries to focus the element. Any exceptions are caught and ignored.
* @param {Number} defer (optional) Milliseconds to defer the focus
* @return {Ext.Element} this
*/
focus : function(defer, /* private */ dom) {
var me = this,
dom = dom || me.dom;
try{
if(Number(defer)){
me.focus.defer(defer, null, [null, dom]);
}else{
dom.focus();
}
}catch(e){}
return me;
},
/**
* Tries to blur the element. Any exceptions are caught and ignored.
* @return {Ext.Element} this
*/
blur : function() {
try{
this.dom.blur();
}catch(e){}
return this;
},
/**
* Returns the value of the "value" attribute
* @param {Boolean} asNumber true to parse the value as a number
* @return {String/Number}
*/
getValue : function(asNumber){
var val = this.dom.value;
return asNumber ? parseInt(val, 10) : val;
},
/**
* Appends an event handler to this element. The shorthand version {@link #on} is equivalent.
* @param {String} eventName The name of event to handle.
* @param {Function} fn The handler function the event invokes. This function is passed
* the following parameters:
* evt : EventObjectThe {@link Ext.EventObject EventObject} describing the event.
* el : HtmlElementThe DOM element which was the target of the event.
* Note that this may be filtered by using the delegate option.
* o : ObjectThe options object from the addListener call.
*
* @param {Object} scope (optional) The scope (this reference) in which the handler function is executed.
* If omitted, defaults to this Element. .
* @param {Object} options (optional) An object containing handler configuration properties.
* This may contain any of the following properties:
* scope Object : The scope (this reference) in which the handler function is executed.
* If omitted, defaults to this Element.
* delegate String: A simple selector to filter the target or look for a descendant of the target. See below for additional details.
* stopEvent Boolean: True to stop the event. That is stop propagation, and prevent the default action.
* preventDefault Boolean: True to prevent the default action
* stopPropagation Boolean: True to prevent event propagation
* normalized Boolean: False to pass a browser event to the handler function instead of an Ext.EventObject
* target Ext.Element: Only call the handler if the event was fired on the target Element, not if the event was bubbled up from a child node.
* delay Number: The number of milliseconds to delay the invocation of the handler after the event fires.
* single Boolean: True to add a handler to handle just the next firing of the event, and then remove itself.
* buffer Number: Causes the handler to be scheduled to run in an {@link Ext.util.DelayedTask} delayed
* by the specified number of milliseconds. If the event fires again within that time, the original
* handler is not invoked, but the new handler is scheduled in its place.
*
*
* Combining Options
* In the following examples, the shorthand form {@link #on} is used rather than the more verbose
* addListener. The two are equivalent. Using the options argument, it is possible to combine different
* types of listeners:
*
* A delayed, one-time listener that auto stops the event and adds a custom argument (forumId) to the
* options object. The options object is available as the third parameter in the handler function.
* Code:
el.on('click', this.onClick, this, {
single: true,
delay: 100,
stopEvent : true,
forumId: 4
});
*
* Attaching multiple handlers in 1 call
* The method also allows for a single argument to be passed which is a config object containing properties
* which specify multiple handlers.
*
* Code:
el.on({
'click' : {
fn: this.onClick,
scope: this,
delay: 100
},
'mouseover' : {
fn: this.onMouseOver,
scope: this
},
'mouseout' : {
fn: this.onMouseOut,
scope: this
}
});
*
* Or a shorthand syntax:
* Code:
el.on({
'click' : this.onClick,
'mouseover' : this.onMouseOver,
'mouseout' : this.onMouseOut,
scope: this
});
*
*
delegate
*
This is a configuration option that you can pass along when registering a handler for
* an event to assist with event delegation. Event delegation is a technique that is used to
* reduce memory consumption and prevent exposure to memory-leaks. By registering an event
* for a container element as opposed to each element within a container. By setting this
* configuration option to a simple selector, the target element will be filtered to look for
* a descendant of the target.
* For example:
// using this markup:
<div id='elId'>
<p id='p1'>paragraph one</p>
<p id='p2' class='clickable'>paragraph two</p>
<p id='p3'>paragraph three</p>
</div>
// utilize event delegation to registering just one handler on the container element:
el = Ext.get('elId');
el.on(
'click',
function(e,t) {
// handle click
console.info(t.id); // 'p2'
},
this,
{
// filter the target element to be a descendant with the class 'clickable'
delegate: '.clickable'
}
);
*
* @return {Ext.Element} this
*/
addListener : function(eventName, fn, scope, options){
Ext.EventManager.on(this.dom, eventName, fn, scope || this, options);
return this;
},
/**
* Removes an event handler from this element. The shorthand version {@link #un} is equivalent.
*
Note : if a
scope was explicitly specified when {@link #addListener adding} the
* listener, the same scope must be specified here.
* Example:
*
el.removeListener('click', this.handlerFn);
// or
el.un('click', this.handlerFn);
* @param {String} eventName The name of the event from which to remove the handler.
* @param {Function} fn The handler function to remove.
This must be a reference to the function passed into the {@link #addListener} call.
* @param {Object} scope If a scope (
this reference) was specified when the listener was added,
* then this must refer to the same object.
* @return {Ext.Element} this
*/
removeListener : function(eventName, fn, scope){
Ext.EventManager.removeListener(this.dom, eventName, fn, scope || this);
return this;
},
/**
* Removes all previous added listeners from this element
* @return {Ext.Element} this
*/
removeAllListeners : function(){
Ext.EventManager.removeAll(this.dom);
return this;
},
/**
* Recursively removes all previous added listeners from this element and its children
* @return {Ext.Element} this
*/
purgeAllListeners : function() {
Ext.EventManager.purgeElement(this, true);
return this;
},
/**
* @private Test if size has a unit, otherwise appends the default
*/
addUnits : function(size){
if(size === "" || size == "auto" || size === undefined){
size = size || '';
} else if(!isNaN(size) || !unitPattern.test(size)){
size = size + (this.defaultUnit || 'px');
}
return size;
},
/**
*
Updates the innerHTML of this Element
* from a specified URL. Note that this is subject to the Same Origin Policy
*
Updating innerHTML of an element will not execute embedded <script> elements. This is a browser restriction.
* @param {Mixed} options. Either a sring containing the URL from which to load the HTML, or an {@link Ext.Ajax#request} options object specifying
* exactly how to request the HTML.
* @return {Ext.Element} this
*/
load : function(url, params, cb){
Ext.Ajax.request(Ext.apply({
params: params,
url: url.url || url,
callback: cb,
el: this.dom,
indicatorText: url.indicatorText || ''
}, Ext.isObject(url) ? url : {}));
return this;
},
/**
* Tests various css rules/browsers to determine if this element uses a border box
* @return {Boolean}
*/
isBorderBox : function(){
return Ext.isBorderBox || Ext.isForcedBorderBox || noBoxAdjust[(this.dom.tagName || "").toLowerCase()];
},
/**
*
Removes this element's dom reference. Note that event and cache removal is handled at {@link Ext#removeNode}
*/
remove : function(){
var me = this,
dom = me.dom;
if (dom) {
delete me.dom;
Ext.removeNode(dom);
}
},
/**
* Sets up event handlers to call the passed functions when the mouse is moved into and out of the Element.
* @param {Function} overFn The function to call when the mouse enters the Element.
* @param {Function} outFn The function to call when the mouse leaves the Element.
* @param {Object} scope (optional) The scope (
this reference) in which the functions are executed. Defaults to the Element's DOM element.
* @param {Object} options (optional) Options for the listener. See {@link Ext.util.Observable#addListener the
options parameter}.
* @return {Ext.Element} this
*/
hover : function(overFn, outFn, scope, options){
var me = this;
me.on('mouseenter', overFn, scope || me.dom, options);
me.on('mouseleave', outFn, scope || me.dom, options);
return me;
},
/**
* Returns true if this element is an ancestor of the passed element
* @param {HTMLElement/String} el The element to check
* @return {Boolean} True if this element is an ancestor of el, else false
*/
contains : function(el){
return !el ? false : Ext.lib.Dom.isAncestor(this.dom, el.dom ? el.dom : el);
},
/**
* Returns the value of a namespaced attribute from the element's underlying DOM node.
* @param {String} namespace The namespace in which to look for the attribute
* @param {String} name The attribute name
* @return {String} The attribute value
* @deprecated
*/
getAttributeNS : function(ns, name){
return this.getAttribute(name, ns);
},
/**
* Returns the value of an attribute from the element's underlying DOM node.
* @param {String} name The attribute name
* @param {String} namespace (optional) The namespace in which to look for the attribute
* @return {String} The attribute value
*/
getAttribute: (function(){
var test = document.createElement('table'),
isBrokenOnTable = false,
hasGetAttribute = 'getAttribute' in test,
unknownRe = /undefined|unknown/;
if (hasGetAttribute) {
try {
test.getAttribute('ext:qtip');
} catch (e) {
isBrokenOnTable = true;
}
return function(name, ns) {
var el = this.dom,
value;
if (el.getAttributeNS) {
value = el.getAttributeNS(ns, name) || null;
}
if (value == null) {
if (ns) {
if (isBrokenOnTable && el.tagName.toUpperCase() == 'TABLE') {
try {
value = el.getAttribute(ns + ':' + name);
} catch (e) {
value = '';
}
} else {
value = el.getAttribute(ns + ':' + name);
}
} else {
value = el.getAttribute(name) || el[name];
}
}
return value || '';
};
} else {
return function(name, ns) {
var el = this.om,
value,
attribute;
if (ns) {
attribute = el[ns + ':' + name];
value = unknownRe.test(typeof attribute) ? undefined : attribute;
} else {
value = el[name];
}
return value || '';
};
}
test = null;
})(),
/**
* Update the innerHTML of this element
* @param {String} html The new HTML
* @return {Ext.Element} this
*/
update : function(html) {
if (this.dom) {
this.dom.innerHTML = html;
}
return this;
}
};
var ep = El.prototype;
El.addMethods = function(o){
Ext.apply(ep, o);
};
/**
* Appends an event handler (shorthand for {@link #addListener}).
* @param {String} eventName The name of event to handle.
* @param {Function} fn The handler function the event invokes.
* @param {Object} scope (optional) The scope (
this reference) in which the handler function is executed.
* @param {Object} options (optional) An object containing standard {@link #addListener} options
* @member Ext.Element
* @method on
*/
ep.on = ep.addListener;
/**
* Removes an event handler from this element (see {@link #removeListener} for additional notes).
* @param {String} eventName The name of the event from which to remove the handler.
* @param {Function} fn The handler function to remove.
This must be a reference to the function passed into the {@link #addListener} call.
* @param {Object} scope If a scope (
this reference) was specified when the listener was added,
* then this must refer to the same object.
* @return {Ext.Element} this
* @member Ext.Element
* @method un
*/
ep.un = ep.removeListener;
/**
* true to automatically adjust width and height settings for box-model issues (default to true)
*/
ep.autoBoxAdjust = true;
// private
var unitPattern = /\d+(px|em|%|en|ex|pt|in|cm|mm|pc)$/i,
docEl;
/**
* Retrieves Ext.Element objects.
*
This method does not retrieve {@link Ext.Component Component}s. This method
* retrieves Ext.Element objects which encapsulate DOM elements. To retrieve a Component by
* its ID, use {@link Ext.ComponentMgr#get}.
*
Uses simple caching to consistently return the same object. Automatically fixes if an
* object was recreated with the same id via AJAX or DOM.
* @param {Mixed} el The id of the node, a DOM Node or an existing Element.
* @return {Element} The Element object (or null if no matching element was found)
* @static
* @member Ext.Element
* @method get
*/
El.get = function(el){
var ex,
elm,
id;
if(!el){ return null; }
if (typeof el == "string") { // element id
if (!(elm = DOC.getElementById(el))) {
return null;
}
if (EC[el] && EC[el].el) {
ex = EC[el].el;
ex.dom = elm;
} else {
ex = El.addToCache(new El(elm));
}
return ex;
} else if (el.tagName) { // dom element
if(!(id = el.id)){
id = Ext.id(el);
}
if (EC[id] && EC[id].el) {
ex = EC[id].el;
ex.dom = el;
} else {
ex = El.addToCache(new El(el));
}
return ex;
} else if (el instanceof El) {
if(el != docEl){
// refresh dom element in case no longer valid,
// catch case where it hasn't been appended
// If an el instance is passed, don't pass to getElementById without some kind of id
if (Ext.isIE && (el.id == undefined || el.id == '')) {
el.dom = el.dom;
} else {
el.dom = DOC.getElementById(el.id) || el.dom;
}
}
return el;
} else if(el.isComposite) {
return el;
} else if(Ext.isArray(el)) {
return El.select(el);
} else if(el == DOC) {
// create a bogus element object representing the document object
if(!docEl){
var f = function(){};
f.prototype = El.prototype;
docEl = new f();
docEl.dom = DOC;
}
return docEl;
}
return null;
};
El.addToCache = function(el, id){
id = id || el.id;
EC[id] = {
el: el,
data: {},
events: {}
};
return el;
};
// private method for getting and setting element data
El.data = function(el, key, value){
el = El.get(el);
if (!el) {
return null;
}
var c = EC[el.id].data;
if(arguments.length == 2){
return c[key];
}else{
return (c[key] = value);
}
};
// private
// Garbage collection - uncache elements/purge listeners on orphaned elements
// so we don't hold a reference and cause the browser to retain them
function garbageCollect(){
if(!Ext.enableGarbageCollector){
clearInterval(El.collectorThreadId);
} else {
var eid,
el,
d,
o;
for(eid in EC){
o = EC[eid];
if(o.skipGC){
Ext.EventManager.removeFromSpecialCache(o.el);
continue;
}
el = o.el;
d = el.dom;
// -------------------------------------------------------
// Determining what is garbage:
// -------------------------------------------------------
// !d
// dom node is null, definitely garbage
// -------------------------------------------------------
// !d.parentNode
// no parentNode == direct orphan, definitely garbage
// -------------------------------------------------------
// !d.offsetParent && !document.getElementById(eid)
// display none elements have no offsetParent so we will
// also try to look it up by it's id. However, check
// offsetParent first so we don't do unneeded lookups.
// This enables collection of elements that are not orphans
// directly, but somewhere up the line they have an orphan
// parent.
// -------------------------------------------------------
if(!d || !d.parentNode || (!d.offsetParent && !DOC.getElementById(eid))){
if(Ext.enableListenerCollection){
Ext.EventManager.removeAll(d);
}
delete EC[eid];
}
}
// Cleanup IE Object leaks
if (Ext.isIE) {
var t = {};
for (eid in EC) {
t[eid] = EC[eid];
}
EC = Ext.elCache = t;
}
}
}
El.collectorThreadId = setInterval(garbageCollect, 30000);
var flyFn = function(){};
flyFn.prototype = El.prototype;
// dom is optional
El.Flyweight = function(dom){
this.dom = dom;
};
El.Flyweight.prototype = new flyFn();
El.Flyweight.prototype.isFlyweight = true;
El._flyweights = {};
/**
*
Gets the globally shared flyweight Element, with the passed node as the active element. Do not store a reference to this element -
* the dom node can be overwritten by other code. Shorthand of {@link Ext.Element#fly}
*
Use this to make one-time references to DOM elements which are not going to be accessed again either by
* application code, or by Ext's classes. If accessing an element which will be processed regularly, then {@link Ext#get}
* will be more appropriate to take advantage of the caching provided by the Ext.Element class.
* @param {String/HTMLElement} el The dom node or id
* @param {String} named (optional) Allows for creation of named reusable flyweights to prevent conflicts
* (e.g. internally Ext uses "_global")
* @return {Element} The shared Element object (or null if no matching element was found)
* @member Ext.Element
* @method fly
*/
El.fly = function(el, named){
var ret = null;
named = named || '_global';
if (el = Ext.getDom(el)) {
(El._flyweights[named] = El._flyweights[named] || new El.Flyweight()).dom = el;
ret = El._flyweights[named];
}
return ret;
};
/**
* Retrieves Ext.Element objects.
*
This method does not retrieve {@link Ext.Component Component}s. This method
* retrieves Ext.Element objects which encapsulate DOM elements. To retrieve a Component by
* its ID, use {@link Ext.ComponentMgr#get}.
*
Uses simple caching to consistently return the same object. Automatically fixes if an
* object was recreated with the same id via AJAX or DOM.
* Shorthand of {@link Ext.Element#get}
* @param {Mixed} el The id of the node, a DOM Node or an existing Element.
* @return {Element} The Element object (or null if no matching element was found)
* @member Ext
* @method get
*/
Ext.get = El.get;
/**
*
Gets the globally shared flyweight Element, with the passed node as the active element. Do not store a reference to this element -
* the dom node can be overwritten by other code. Shorthand of {@link Ext.Element#fly}
*
Use this to make one-time references to DOM elements which are not going to be accessed again either by
* application code, or by Ext's classes. If accessing an element which will be processed regularly, then {@link Ext#get}
* will be more appropriate to take advantage of the caching provided by the Ext.Element class.
* @param {String/HTMLElement} el The dom node or id
* @param {String} named (optional) Allows for creation of named reusable flyweights to prevent conflicts
* (e.g. internally Ext uses "_global")
* @return {Element} The shared Element object (or null if no matching element was found)
* @member Ext
* @method fly
*/
Ext.fly = El.fly;
// speedy lookup for elements never to box adjust
var noBoxAdjust = Ext.isStrict ? {
select:1
} : {
input:1, select:1, textarea:1
};
if(Ext.isIE || Ext.isGecko){
noBoxAdjust['button'] = 1;
}
})();
/**
* @class Ext.Element
*/
Ext.Element.addMethods(function(){
var PARENTNODE = 'parentNode',
NEXTSIBLING = 'nextSibling',
PREVIOUSSIBLING = 'previousSibling',
DQ = Ext.DomQuery,
GET = Ext.get;
return {
/**
* Looks at this node and then at parent nodes for a match of the passed simple selector (e.g. div.some-class or span:first-child)
* @param {String} selector The simple selector to test
* @param {Number/Mixed} maxDepth (optional) The max depth to search as a number or element (defaults to 50 || document.body)
* @param {Boolean} returnEl (optional) True to return a Ext.Element object instead of DOM node
* @return {HTMLElement} The matching DOM node (or null if no match was found)
*/
findParent : function(simpleSelector, maxDepth, returnEl){
var p = this.dom,
b = document.body,
depth = 0,
stopEl;
if(Ext.isGecko && Object.prototype.toString.call(p) == '[object XULElement]') {
return null;
}
maxDepth = maxDepth || 50;
if (isNaN(maxDepth)) {
stopEl = Ext.getDom(maxDepth);
maxDepth = Number.MAX_VALUE;
}
while(p && p.nodeType == 1 && depth < maxDepth && p != b && p != stopEl){
if(DQ.is(p, simpleSelector)){
return returnEl ? GET(p) : p;
}
depth++;
p = p.parentNode;
}
return null;
},
/**
* Looks at parent nodes for a match of the passed simple selector (e.g. div.some-class or span:first-child)
* @param {String} selector The simple selector to test
* @param {Number/Mixed} maxDepth (optional) The max depth to
search as a number or element (defaults to 10 || document.body)
* @param {Boolean} returnEl (optional) True to return a Ext.Element object instead of DOM node
* @return {HTMLElement} The matching DOM node (or null if no match was found)
*/
findParentNode : function(simpleSelector, maxDepth, returnEl){
var p = Ext.fly(this.dom.parentNode, '_internal');
return p ? p.findParent(simpleSelector, maxDepth, returnEl) : null;
},
/**
* Walks up the dom looking for a parent node that matches the passed simple selector (e.g. div.some-class or span:first-child).
* This is a shortcut for findParentNode() that always returns an Ext.Element.
* @param {String} selector The simple selector to test
* @param {Number/Mixed} maxDepth (optional) The max depth to
search as a number or element (defaults to 10 || document.body)
* @return {Ext.Element} The matching DOM node (or null if no match was found)
*/
up : function(simpleSelector, maxDepth){
return this.findParentNode(simpleSelector, maxDepth, true);
},
/**
* Creates a {@link Ext.CompositeElement} for child nodes based on the passed CSS selector (the selector should not contain an id).
* @param {String} selector The CSS selector
* @return {CompositeElement/CompositeElementLite} The composite element
*/
select : function(selector){
return Ext.Element.select(selector, this.dom);
},
/**
* Selects child nodes based on the passed CSS selector (the selector should not contain an id).
* @param {String} selector The CSS selector
* @return {Array} An array of the matched nodes
*/
query : function(selector){
return DQ.select(selector, this.dom);
},
/**
* Selects a single child at any depth below this element based on the passed CSS selector (the selector should not contain an id).
* @param {String} selector The CSS selector
* @param {Boolean} returnDom (optional) True to return the DOM node instead of Ext.Element (defaults to false)
* @return {HTMLElement/Ext.Element} The child Ext.Element (or DOM node if returnDom = true)
*/
child : function(selector, returnDom){
var n = DQ.selectNode(selector, this.dom);
return returnDom ? n : GET(n);
},
/**
* Selects a single *direct* child based on the passed CSS selector (the selector should not contain an id).
* @param {String} selector The CSS selector
* @param {Boolean} returnDom (optional) True to return the DOM node instead of Ext.Element (defaults to false)
* @return {HTMLElement/Ext.Element} The child Ext.Element (or DOM node if returnDom = true)
*/
down : function(selector, returnDom){
var n = DQ.selectNode(" > " + selector, this.dom);
return returnDom ? n : GET(n);
},
/**
* Gets the parent node for this element, optionally chaining up trying to match a selector
* @param {String} selector (optional) Find a parent node that matches the passed simple selector
* @param {Boolean} returnDom (optional) True to return a raw dom node instead of an Ext.Element
* @return {Ext.Element/HTMLElement} The parent node or null
*/
parent : function(selector, returnDom){
return this.matchNode(PARENTNODE, PARENTNODE, selector, returnDom);
},
/**
* Gets the next sibling, skipping text nodes
* @param {String} selector (optional) Find the next sibling that matches the passed simple selector
* @param {Boolean} returnDom (optional) True to return a raw dom node instead of an Ext.Element
* @return {Ext.Element/HTMLElement} The next sibling or null
*/
next : function(selector, returnDom){
return this.matchNode(NEXTSIBLING, NEXTSIBLING, selector, returnDom);
},
/**
* Gets the previous sibling, skipping text nodes
* @param {String} selector (optional) Find the previous sibling that matches the passed simple selector
* @param {Boolean} returnDom (optional) True to return a raw dom node instead of an Ext.Element
* @return {Ext.Element/HTMLElement} The previous sibling or null
*/
prev : function(selector, returnDom){
return this.matchNode(PREVIOUSSIBLING, PREVIOUSSIBLING, selector, returnDom);
},
/**
* Gets the first child, skipping text nodes
* @param {String} selector (optional) Find the next sibling that matches the passed simple selector
* @param {Boolean} returnDom (optional) True to return a raw dom node instead of an Ext.Element
* @return {Ext.Element/HTMLElement} The first child or null
*/
first : function(selector, returnDom){
return this.matchNode(NEXTSIBLING, 'firstChild', selector, returnDom);
},
/**
* Gets the last child, skipping text nodes
* @param {String} selector (optional) Find the previous sibling that matches the passed simple selector
* @param {Boolean} returnDom (optional) True to return a raw dom node instead of an Ext.Element
* @return {Ext.Element/HTMLElement} The last child or null
*/
last : function(selector, returnDom){
return this.matchNode(PREVIOUSSIBLING, 'lastChild', selector, returnDom);
},
matchNode : function(dir, start, selector, returnDom){
var n = this.dom[start];
while(n){
if(n.nodeType == 1 && (!selector || DQ.is(n, selector))){
return !returnDom ? GET(n) : n;
}
n = n[dir];
}
return null;
}
};
}());/**
* @class Ext.Element
*/
Ext.Element.addMethods(
function() {
var GETDOM = Ext.getDom,
GET = Ext.get,
DH = Ext.DomHelper;
return {
/**
* Appends the passed element(s) to this element
* @param {String/HTMLElement/Array/Element/CompositeElement} el
* @return {Ext.Element} this
*/
appendChild: function(el){
return GET(el).appendTo(this);
},
/**
* Appends this element to the passed element
* @param {Mixed} el The new parent element
* @return {Ext.Element} this
*/
appendTo: function(el){
GETDOM(el).appendChild(this.dom);
return this;
},
/**
* Inserts this element before the passed element in the DOM
* @param {Mixed} el The element before which this element will be inserted
* @return {Ext.Element} this
*/
insertBefore: function(el){
(el = GETDOM(el)).parentNode.insertBefore(this.dom, el);
return this;
},
/**
* Inserts this element after the passed element in the DOM
* @param {Mixed} el The element to insert after
* @return {Ext.Element} this
*/
insertAfter: function(el){
(el = GETDOM(el)).parentNode.insertBefore(this.dom, el.nextSibling);
return this;
},
/**
* Inserts (or creates) an element (or DomHelper config) as the first child of this element
* @param {Mixed/Object} el The id or element to insert or a DomHelper config to create and insert
* @return {Ext.Element} The new child
*/
insertFirst: function(el, returnDom){
el = el || {};
if(el.nodeType || el.dom || typeof el == 'string'){ // element
el = GETDOM(el);
this.dom.insertBefore(el, this.dom.firstChild);
return !returnDom ? GET(el) : el;
}else{ // dh config
return this.createChild(el, this.dom.firstChild, returnDom);
}
},
/**
* Replaces the passed element with this element
* @param {Mixed} el The element to replace
* @return {Ext.Element} this
*/
replace: function(el){
el = GET(el);
this.insertBefore(el);
el.remove();
return this;
},
/**
* Replaces this element with the passed element
* @param {Mixed/Object} el The new element or a DomHelper config of an element to create
* @return {Ext.Element} this
*/
replaceWith: function(el){
var me = this;
if(el.nodeType || el.dom || typeof el == 'string'){
el = GETDOM(el);
me.dom.parentNode.insertBefore(el, me.dom);
}else{
el = DH.insertBefore(me.dom, el);
}
delete Ext.elCache[me.id];
Ext.removeNode(me.dom);
me.id = Ext.id(me.dom = el);
Ext.Element.addToCache(me.isFlyweight ? new Ext.Element(me.dom) : me);
return me;
},
/**
* Creates the passed DomHelper config and appends it to this element or optionally inserts it before the passed child element.
* @param {Object} config DomHelper element config object. If no tag is specified (e.g., {tag:'input'}) then a div will be
* automatically generated with the specified attributes.
* @param {HTMLElement} insertBefore (optional) a child element of this element
* @param {Boolean} returnDom (optional) true to return the dom node instead of creating an Element
* @return {Ext.Element} The new child element
*/
createChild: function(config, insertBefore, returnDom){
config = config || {tag:'div'};
return insertBefore ?
DH.insertBefore(insertBefore, config, returnDom !== true) :
DH[!this.dom.firstChild ? 'overwrite' : 'append'](this.dom, config, returnDom !== true);
},
/**
* Creates and wraps this element with another element
* @param {Object} config (optional) DomHelper element config object for the wrapper element or null for an empty div
* @param {Boolean} returnDom (optional) True to return the raw DOM element instead of Ext.Element
* @return {HTMLElement/Element} The newly created wrapper element
*/
wrap: function(config, returnDom){
var newEl = DH.insertBefore(this.dom, config || {tag: "div"}, !returnDom);
newEl.dom ? newEl.dom.appendChild(this.dom) : newEl.appendChild(this.dom);
return newEl;
},
/**
* Inserts an html fragment into this element
* @param {String} where Where to insert the html in relation to this element - beforeBegin, afterBegin, beforeEnd, afterEnd.
* @param {String} html The HTML fragment
* @param {Boolean} returnEl (optional) True to return an Ext.Element (defaults to false)
* @return {HTMLElement/Ext.Element} The inserted node (or nearest related if more than 1 inserted)
*/
insertHtml : function(where, html, returnEl){
var el = DH.insertHtml(where, this.dom, html);
return returnEl ? Ext.get(el) : el;
}
};
}());/**
* @class Ext.Element
*/
Ext.Element.addMethods(function(){
// local style camelizing for speed
var supports = Ext.supports,
propCache = {},
camelRe = /(-[a-z])/gi,
view = document.defaultView,
opacityRe = /alpha\(opacity=(.*)\)/i,
trimRe = /^\s+|\s+$/g,
EL = Ext.Element,
spacesRe = /\s+/,
wordsRe = /\w/g,
PADDING = "padding",
MARGIN = "margin",
BORDER = "border",
LEFT = "-left",
RIGHT = "-right",
TOP = "-top",
BOTTOM = "-bottom",
WIDTH = "-width",
MATH = Math,
HIDDEN = 'hidden',
ISCLIPPED = 'isClipped',
OVERFLOW = 'overflow',
OVERFLOWX = 'overflow-x',
OVERFLOWY = 'overflow-y',
ORIGINALCLIP = 'originalClip',
// special markup used throughout Ext when box wrapping elements
borders = {l: BORDER + LEFT + WIDTH, r: BORDER + RIGHT + WIDTH, t: BORDER + TOP + WIDTH, b: BORDER + BOTTOM + WIDTH},
paddings = {l: PADDING + LEFT, r: PADDING + RIGHT, t: PADDING + TOP, b: PADDING + BOTTOM},
margins = {l: MARGIN + LEFT, r: MARGIN + RIGHT, t: MARGIN + TOP, b: MARGIN + BOTTOM},
data = Ext.Element.data;
// private
function camelFn(m, a) {
return a.charAt(1).toUpperCase();
}
function chkCache(prop) {
return propCache[prop] || (propCache[prop] = prop == 'float' ? (supports.cssFloat ? 'cssFloat' : 'styleFloat') : prop.replace(camelRe, camelFn));
}
return {
// private ==> used by Fx
adjustWidth : function(width) {
var me = this;
var isNum = (typeof width == "number");
if(isNum && me.autoBoxAdjust && !me.isBorderBox()){
width -= (me.getBorderWidth("lr") + me.getPadding("lr"));
}
return (isNum && width < 0) ? 0 : width;
},
// private ==> used by Fx
adjustHeight : function(height) {
var me = this;
var isNum = (typeof height == "number");
if(isNum && me.autoBoxAdjust && !me.isBorderBox()){
height -= (me.getBorderWidth("tb") + me.getPadding("tb"));
}
return (isNum && height < 0) ? 0 : height;
},
/**
* Adds one or more CSS classes to the element. Duplicate classes are automatically filtered out.
* @param {String/Array} className The CSS class to add, or an array of classes
* @return {Ext.Element} this
*/
addClass : function(className){
var me = this,
i,
len,
v,
cls = [];
// Separate case is for speed
if (!Ext.isArray(className)) {
if (typeof className == 'string' && !this.hasClass(className)) {
me.dom.className += " " + className;
}
}
else {
for (i = 0, len = className.length; i < len; i++) {
v = className[i];
if (typeof v == 'string' && (' ' + me.dom.className + ' ').indexOf(' ' + v + ' ') == -1) {
cls.push(v);
}
}
if (cls.length) {
me.dom.className += " " + cls.join(" ");
}
}
return me;
},
/**
* Removes one or more CSS classes from the element.
* @param {String/Array} className The CSS class to remove, or an array of classes
* @return {Ext.Element} this
*/
removeClass : function(className){
var me = this,
i,
idx,
len,
cls,
elClasses;
if (!Ext.isArray(className)){
className = [className];
}
if (me.dom && me.dom.className) {
elClasses = me.dom.className.replace(trimRe, '').split(spacesRe);
for (i = 0, len = className.length; i < len; i++) {
cls = className[i];
if (typeof cls == 'string') {
cls = cls.replace(trimRe, '');
idx = elClasses.indexOf(cls);
if (idx != -1) {
elClasses.splice(idx, 1);
}
}
}
me.dom.className = elClasses.join(" ");
}
return me;
},
/**
* Adds one or more CSS classes to this element and removes the same class(es) from all siblings.
* @param {String/Array} className The CSS class to add, or an array of classes
* @return {Ext.Element} this
*/
radioClass : function(className){
var cn = this.dom.parentNode.childNodes,
v,
i,
len;
className = Ext.isArray(className) ? className : [className];
for (i = 0, len = cn.length; i < len; i++) {
v = cn[i];
if (v && v.nodeType == 1) {
Ext.fly(v, '_internal').removeClass(className);
}
};
return this.addClass(className);
},
/**
* Toggles the specified CSS class on this element (removes it if it already exists, otherwise adds it).
* @param {String} className The CSS class to toggle
* @return {Ext.Element} this
*/
toggleClass : function(className){
return this.hasClass(className) ? this.removeClass(className) : this.addClass(className);
},
/**
* Checks if the specified CSS class exists on this element's DOM node.
* @param {String} className The CSS class to check for
* @return {Boolean} True if the class exists, else false
*/
hasClass : function(className){
return className && (' '+this.dom.className+' ').indexOf(' '+className+' ') != -1;
},
/**
* Replaces a CSS class on the element with another. If the old name does not exist, the new name will simply be added.
* @param {String} oldClassName The CSS class to replace
* @param {String} newClassName The replacement CSS class
* @return {Ext.Element} this
*/
replaceClass : function(oldClassName, newClassName){
return this.removeClass(oldClassName).addClass(newClassName);
},
isStyle : function(style, val) {
return this.getStyle(style) == val;
},
/**
* Normalizes currentStyle and computedStyle.
* @param {String} property The style property whose value is returned.
* @return {String} The current value of the style property for this element.
*/
getStyle : function(){
return view && view.getComputedStyle ?
function(prop){
var el = this.dom,
v,
cs,
out,
display;
if(el == document){
return null;
}
prop = chkCache(prop);
out = (v = el.style[prop]) ? v :
(cs = view.getComputedStyle(el, "")) ? cs[prop] : null;
// Ignore cases when the margin is correctly reported as 0, the bug only shows
// numbers larger.
if(prop == 'marginRight' && out != '0px' && !supports.correctRightMargin){
display = el.style.display;
el.style.display = 'inline-block';
out = view.getComputedStyle(el, '').marginRight;
el.style.display = display;
}
if(prop == 'backgroundColor' && out == 'rgba(0, 0, 0, 0)' && !supports.correctTransparentColor){
out = 'transparent';
}
return out;
} :
function(prop){
var el = this.dom,
m,
cs;
if(el == document) return null;
if (prop == 'opacity') {
if (el.style.filter.match) {
if(m = el.style.filter.match(opacityRe)){
var fv = parseFloat(m[1]);
if(!isNaN(fv)){
return fv ? fv / 100 : 0;
}
}
}
return 1;
}
prop = chkCache(prop);
return el.style[prop] || ((cs = el.currentStyle) ? cs[prop] : null);
};
}(),
/**
* Return the CSS color for the specified CSS attribute. rgb, 3 digit (like #fff) and valid values
* are convert to standard 6 digit hex color.
* @param {String} attr The css attribute
* @param {String} defaultValue The default value to use when a valid color isn't found
* @param {String} prefix (optional) defaults to #. Use an empty string when working with
* color anims.
*/
getColor : function(attr, defaultValue, prefix){
var v = this.getStyle(attr),
color = (typeof prefix != 'undefined') ? prefix : '#',
h;
if(!v || (/transparent|inherit/.test(v))) {
return defaultValue;
}
if(/^r/.test(v)){
Ext.each(v.slice(4, v.length -1).split(','), function(s){
h = parseInt(s, 10);
color += (h < 16 ? '0' : '') + h.toString(16);
});
}else{
v = v.replace('#', '');
color += v.length == 3 ? v.replace(/^(\w)(\w)(\w)$/, '$1$1$2$2$3$3') : v;
}
return(color.length > 5 ? color.toLowerCase() : defaultValue);
},
/**
* Wrapper for setting style properties, also takes single object parameter of multiple styles.
* @param {String/Object} property The style property to be set, or an object of multiple styles.
* @param {String} value (optional) The value to apply to the given property, or null if an object was passed.
* @return {Ext.Element} this
*/
setStyle : function(prop, value){
var tmp, style;
if (typeof prop != 'object') {
tmp = {};
tmp[prop] = value;
prop = tmp;
}
for (style in prop) {
value = prop[style];
style == 'opacity' ?
this.setOpacity(value) :
this.dom.style[chkCache(style)] = value;
}
return this;
},
/**
* Set the opacity of the element
* @param {Float} opacity The new opacity. 0 = transparent, .5 = 50% visibile, 1 = fully visible, etc
* @param {Boolean/Object} animate (optional) a standard Element animation config object or
true for
* the default animation (
{duration: .35, easing: 'easeIn'} )
* @return {Ext.Element} this
*/
setOpacity : function(opacity, animate){
var me = this,
s = me.dom.style;
if(!animate || !me.anim){
if(Ext.isIE9m){
var opac = opacity < 1 ? 'alpha(opacity=' + opacity * 100 + ')' : '',
val = s.filter.replace(opacityRe, '').replace(trimRe, '');
s.zoom = 1;
s.filter = val + (val.length > 0 ? ' ' : '') + opac;
}else{
s.opacity = opacity;
}
}else{
me.anim({opacity: {to: opacity}}, me.preanim(arguments, 1), null, .35, 'easeIn');
}
return me;
},
/**
* Clears any opacity settings from this element. Required in some cases for IE.
* @return {Ext.Element} this
*/
clearOpacity : function(){
var style = this.dom.style;
if(Ext.isIE9m){
if(!Ext.isEmpty(style.filter)){
style.filter = style.filter.replace(opacityRe, '').replace(trimRe, '');
}
}else{
style.opacity = style['-moz-opacity'] = style['-khtml-opacity'] = '';
}
return this;
},
/**
* Returns the offset height of the element
* @param {Boolean} contentHeight (optional) true to get the height minus borders and padding
* @return {Number} The element's height
*/
getHeight : function(contentHeight){
var me = this,
dom = me.dom,
hidden = Ext.isIE9m && me.isStyle('display', 'none'),
h = MATH.max(dom.offsetHeight, hidden ? 0 : dom.clientHeight) || 0;
h = !contentHeight ? h : h - me.getBorderWidth("tb") - me.getPadding("tb");
return h < 0 ? 0 : h;
},
/**
* Returns the offset width of the element
* @param {Boolean} contentWidth (optional) true to get the width minus borders and padding
* @return {Number} The element's width
*/
getWidth : function(contentWidth){
var me = this,
dom = me.dom,
hidden = Ext.isIE9m && me.isStyle('display', 'none'),
w = MATH.max(dom.offsetWidth, hidden ? 0 : dom.clientWidth) || 0;
w = !contentWidth ? w : w - me.getBorderWidth("lr") - me.getPadding("lr");
return w < 0 ? 0 : w;
},
/**
* Set the width of this Element.
* @param {Mixed} width The new width. This may be one of:
* A Number specifying the new width in this Element's {@link #defaultUnit}s (by default, pixels).
* A String used to set the CSS width style. Animation may not be used.
*
* @param {Boolean/Object} animate (optional) true for the default animation or a standard Element animation config object
* @return {Ext.Element} this
*/
setWidth : function(width, animate){
var me = this;
width = me.adjustWidth(width);
!animate || !me.anim ?
me.dom.style.width = me.addUnits(width) :
me.anim({width : {to : width}}, me.preanim(arguments, 1));
return me;
},
/**
* Set the height of this Element.
*
// change the height to 200px and animate with default configuration
Ext.fly('elementId').setHeight(200, true);
// change the height to 150px and animate with a custom configuration
Ext.fly('elId').setHeight(150, {
duration : .5, // animation will have a duration of .5 seconds
// will change the content to "finished"
callback: function(){ this.{@link #update}("finished"); }
});
*
* @param {Mixed} height The new height. This may be one of:
* A Number specifying the new height in this Element's {@link #defaultUnit}s (by default, pixels.)
* A String used to set the CSS height style. Animation may not be used.
*
* @param {Boolean/Object} animate (optional) true for the default animation or a standard Element animation config object
* @return {Ext.Element} this
*/
setHeight : function(height, animate){
var me = this;
height = me.adjustHeight(height);
!animate || !me.anim ?
me.dom.style.height = me.addUnits(height) :
me.anim({height : {to : height}}, me.preanim(arguments, 1));
return me;
},
/**
* Gets the width of the border(s) for the specified side(s)
* @param {String} side Can be t, l, r, b or any combination of those to add multiple values. For example,
* passing
'lr' would get the border
l eft width + the border
r ight width.
* @return {Number} The width of the sides passed added together
*/
getBorderWidth : function(side){
return this.addStyles(side, borders);
},
/**
* Gets the width of the padding(s) for the specified side(s)
* @param {String} side Can be t, l, r, b or any combination of those to add multiple values. For example,
* passing
'lr' would get the padding
l eft + the padding
r ight.
* @return {Number} The padding of the sides passed added together
*/
getPadding : function(side){
return this.addStyles(side, paddings);
},
/**
* Store the current overflow setting and clip overflow on the element - use
{@link #unclip} to remove
* @return {Ext.Element} this
*/
clip : function(){
var me = this,
dom = me.dom;
if(!data(dom, ISCLIPPED)){
data(dom, ISCLIPPED, true);
data(dom, ORIGINALCLIP, {
o: me.getStyle(OVERFLOW),
x: me.getStyle(OVERFLOWX),
y: me.getStyle(OVERFLOWY)
});
me.setStyle(OVERFLOW, HIDDEN);
me.setStyle(OVERFLOWX, HIDDEN);
me.setStyle(OVERFLOWY, HIDDEN);
}
return me;
},
/**
* Return clipping (overflow) to original clipping before
{@link #clip} was called
* @return {Ext.Element} this
*/
unclip : function(){
var me = this,
dom = me.dom;
if(data(dom, ISCLIPPED)){
data(dom, ISCLIPPED, false);
var o = data(dom, ORIGINALCLIP);
if(o.o){
me.setStyle(OVERFLOW, o.o);
}
if(o.x){
me.setStyle(OVERFLOWX, o.x);
}
if(o.y){
me.setStyle(OVERFLOWY, o.y);
}
}
return me;
},
// private
addStyles : function(sides, styles){
var ttlSize = 0,
sidesArr = sides.match(wordsRe),
side,
size,
i,
len = sidesArr.length;
for (i = 0; i < len; i++) {
side = sidesArr[i];
size = side && parseInt(this.getStyle(styles[side]), 10);
if (size) {
ttlSize += MATH.abs(size);
}
}
return ttlSize;
},
margins : margins
};
}()
);
/**
* @class Ext.Element
*/
(function(){
var D = Ext.lib.Dom,
LEFT = "left",
RIGHT = "right",
TOP = "top",
BOTTOM = "bottom",
POSITION = "position",
STATIC = "static",
RELATIVE = "relative",
AUTO = "auto",
ZINDEX = "z-index";
Ext.Element.addMethods({
/**
* Gets the current X position of the element based on page coordinates. Element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @return {Number} The X position of the element
*/
getX : function(){
return D.getX(this.dom);
},
/**
* Gets the current Y position of the element based on page coordinates. Element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @return {Number} The Y position of the element
*/
getY : function(){
return D.getY(this.dom);
},
/**
* Gets the current position of the element based on page coordinates. Element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @return {Array} The XY position of the element
*/
getXY : function(){
return D.getXY(this.dom);
},
/**
* Returns the offsets of this element from the passed element. Both element must be part of the DOM tree and not have display:none to have page coordinates.
* @param {Mixed} element The element to get the offsets from.
* @return {Array} The XY page offsets (e.g. [100, -200])
*/
getOffsetsTo : function(el){
var o = this.getXY(),
e = Ext.fly(el, '_internal').getXY();
return [o[0]-e[0],o[1]-e[1]];
},
/**
* Sets the X position of the element based on page coordinates. Element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @param {Number} The X position of the element
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
setX : function(x, animate){
return this.setXY([x, this.getY()], this.animTest(arguments, animate, 1));
},
/**
* Sets the Y position of the element based on page coordinates. Element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @param {Number} The Y position of the element
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
setY : function(y, animate){
return this.setXY([this.getX(), y], this.animTest(arguments, animate, 1));
},
/**
* Sets the element's left position directly using CSS style (instead of {@link #setX}).
* @param {String} left The left CSS property value
* @return {Ext.Element} this
*/
setLeft : function(left){
this.setStyle(LEFT, this.addUnits(left));
return this;
},
/**
* Sets the element's top position directly using CSS style (instead of {@link #setY}).
* @param {String} top The top CSS property value
* @return {Ext.Element} this
*/
setTop : function(top){
this.setStyle(TOP, this.addUnits(top));
return this;
},
/**
* Sets the element's CSS right style.
* @param {String} right The right CSS property value
* @return {Ext.Element} this
*/
setRight : function(right){
this.setStyle(RIGHT, this.addUnits(right));
return this;
},
/**
* Sets the element's CSS bottom style.
* @param {String} bottom The bottom CSS property value
* @return {Ext.Element} this
*/
setBottom : function(bottom){
this.setStyle(BOTTOM, this.addUnits(bottom));
return this;
},
/**
* Sets the position of the element in page coordinates, regardless of how the element is positioned.
* The element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @param {Array} pos Contains X & Y [x, y] values for new position (coordinates are page-based)
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
setXY : function(pos, animate){
var me = this;
if(!animate || !me.anim){
D.setXY(me.dom, pos);
}else{
me.anim({points: {to: pos}}, me.preanim(arguments, 1), 'motion');
}
return me;
},
/**
* Sets the position of the element in page coordinates, regardless of how the element is positioned.
* The element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @param {Number} x X value for new position (coordinates are page-based)
* @param {Number} y Y value for new position (coordinates are page-based)
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
setLocation : function(x, y, animate){
return this.setXY([x, y], this.animTest(arguments, animate, 2));
},
/**
* Sets the position of the element in page coordinates, regardless of how the element is positioned.
* The element must be part of the DOM tree to have page coordinates (display:none or elements not appended return false).
* @param {Number} x X value for new position (coordinates are page-based)
* @param {Number} y Y value for new position (coordinates are page-based)
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
moveTo : function(x, y, animate){
return this.setXY([x, y], this.animTest(arguments, animate, 2));
},
/**
* Gets the left X coordinate
* @param {Boolean} local True to get the local css position instead of page coordinate
* @return {Number}
*/
getLeft : function(local){
return !local ? this.getX() : parseInt(this.getStyle(LEFT), 10) || 0;
},
/**
* Gets the right X coordinate of the element (element X position + element width)
* @param {Boolean} local True to get the local css position instead of page coordinate
* @return {Number}
*/
getRight : function(local){
var me = this;
return !local ? me.getX() + me.getWidth() : (me.getLeft(true) + me.getWidth()) || 0;
},
/**
* Gets the top Y coordinate
* @param {Boolean} local True to get the local css position instead of page coordinate
* @return {Number}
*/
getTop : function(local) {
return !local ? this.getY() : parseInt(this.getStyle(TOP), 10) || 0;
},
/**
* Gets the bottom Y coordinate of the element (element Y position + element height)
* @param {Boolean} local True to get the local css position instead of page coordinate
* @return {Number}
*/
getBottom : function(local){
var me = this;
return !local ? me.getY() + me.getHeight() : (me.getTop(true) + me.getHeight()) || 0;
},
/**
* Initializes positioning on this element. If a desired position is not passed, it will make the
* the element positioned relative IF it is not already positioned.
* @param {String} pos (optional) Positioning to use "relative", "absolute" or "fixed"
* @param {Number} zIndex (optional) The zIndex to apply
* @param {Number} x (optional) Set the page X position
* @param {Number} y (optional) Set the page Y position
*/
position : function(pos, zIndex, x, y){
var me = this;
if(!pos && me.isStyle(POSITION, STATIC)){
me.setStyle(POSITION, RELATIVE);
} else if(pos) {
me.setStyle(POSITION, pos);
}
if(zIndex){
me.setStyle(ZINDEX, zIndex);
}
if(x || y) me.setXY([x || false, y || false]);
},
/**
* Clear positioning back to the default when the document was loaded
* @param {String} value (optional) The value to use for the left,right,top,bottom, defaults to '' (empty string). You could use 'auto'.
* @return {Ext.Element} this
*/
clearPositioning : function(value){
value = value || '';
this.setStyle({
left : value,
right : value,
top : value,
bottom : value,
"z-index" : "",
position : STATIC
});
return this;
},
/**
* Gets an object with all CSS positioning properties. Useful along with setPostioning to get
* snapshot before performing an update and then restoring the element.
* @return {Object}
*/
getPositioning : function(){
var l = this.getStyle(LEFT);
var t = this.getStyle(TOP);
return {
"position" : this.getStyle(POSITION),
"left" : l,
"right" : l ? "" : this.getStyle(RIGHT),
"top" : t,
"bottom" : t ? "" : this.getStyle(BOTTOM),
"z-index" : this.getStyle(ZINDEX)
};
},
/**
* Set positioning with an object returned by getPositioning().
* @param {Object} posCfg
* @return {Ext.Element} this
*/
setPositioning : function(pc){
var me = this,
style = me.dom.style;
me.setStyle(pc);
if(pc.right == AUTO){
style.right = "";
}
if(pc.bottom == AUTO){
style.bottom = "";
}
return me;
},
/**
* Translates the passed page coordinates into left/top css values for this element
* @param {Number/Array} x The page x or an array containing [x, y]
* @param {Number} y (optional) The page y, required if x is not an array
* @return {Object} An object with left and top properties. e.g. {left: (value), top: (value)}
*/
translatePoints : function(x, y){
y = isNaN(x[1]) ? y : x[1];
x = isNaN(x[0]) ? x : x[0];
var me = this,
relative = me.isStyle(POSITION, RELATIVE),
o = me.getXY(),
l = parseInt(me.getStyle(LEFT), 10),
t = parseInt(me.getStyle(TOP), 10);
l = !isNaN(l) ? l : (relative ? 0 : me.dom.offsetLeft);
t = !isNaN(t) ? t : (relative ? 0 : me.dom.offsetTop);
return {left: (x - o[0] + l), top: (y - o[1] + t)};
},
animTest : function(args, animate, i) {
return !!animate && this.preanim ? this.preanim(args, i) : false;
}
});
})();/**
* @class Ext.Element
*/
Ext.Element.addMethods({
/**
* Returns true if this element is scrollable.
* @return {Boolean}
*/
isScrollable : function(){
var dom = this.dom;
return dom.scrollHeight > dom.clientHeight || dom.scrollWidth > dom.clientWidth;
},
/**
* Scrolls this element the specified scroll point. It does NOT do bounds checking so if you scroll to a weird value it will try to do it. For auto bounds checking, use scroll().
* @param {String} side Either "left" for scrollLeft values or "top" for scrollTop values.
* @param {Number} value The new scroll value.
* @return {Element} this
*/
scrollTo : function(side, value){
this.dom["scroll" + (/top/i.test(side) ? "Top" : "Left")] = value;
return this;
},
/**
* Returns the current scroll position of the element.
* @return {Object} An object containing the scroll position in the format {left: (scrollLeft), top: (scrollTop)}
*/
getScroll : function(){
var d = this.dom,
doc = document,
body = doc.body,
docElement = doc.documentElement,
l,
t,
ret;
if(d == doc || d == body){
if(Ext.isIE && Ext.isStrict){
l = docElement.scrollLeft;
t = docElement.scrollTop;
}else{
l = window.pageXOffset;
t = window.pageYOffset;
}
ret = {left: l || (body ? body.scrollLeft : 0), top: t || (body ? body.scrollTop : 0)};
}else{
ret = {left: d.scrollLeft, top: d.scrollTop};
}
return ret;
}
});/**
* @class Ext.Element
*/
/**
* Visibility mode constant for use with {@link #setVisibilityMode}. Use visibility to hide element
* @static
* @type Number
*/
Ext.Element.VISIBILITY = 1;
/**
* Visibility mode constant for use with {@link #setVisibilityMode}. Use display to hide element
* @static
* @type Number
*/
Ext.Element.DISPLAY = 2;
/**
* Visibility mode constant for use with {@link #setVisibilityMode}. Use offsets (x and y positioning offscreen)
* to hide element.
* @static
* @type Number
*/
Ext.Element.OFFSETS = 3;
Ext.Element.ASCLASS = 4;
/**
* Defaults to 'x-hide-nosize'
* @static
* @type String
*/
Ext.Element.visibilityCls = 'x-hide-nosize';
Ext.Element.addMethods(function(){
var El = Ext.Element,
OPACITY = "opacity",
VISIBILITY = "visibility",
DISPLAY = "display",
HIDDEN = "hidden",
OFFSETS = "offsets",
ASCLASS = "asclass",
NONE = "none",
NOSIZE = 'nosize',
ORIGINALDISPLAY = 'originalDisplay',
VISMODE = 'visibilityMode',
ISVISIBLE = 'isVisible',
data = El.data,
getDisplay = function(dom){
var d = data(dom, ORIGINALDISPLAY);
if(d === undefined){
data(dom, ORIGINALDISPLAY, d = '');
}
return d;
},
getVisMode = function(dom){
var m = data(dom, VISMODE);
if(m === undefined){
data(dom, VISMODE, m = 1);
}
return m;
};
return {
/**
* The element's default display mode (defaults to "")
* @type String
*/
originalDisplay : "",
visibilityMode : 1,
/**
* Sets the element's visibility mode. When setVisible() is called it
* will use this to determine whether to set the visibility or the display property.
* @param {Number} visMode Ext.Element.VISIBILITY or Ext.Element.DISPLAY
* @return {Ext.Element} this
*/
setVisibilityMode : function(visMode){
data(this.dom, VISMODE, visMode);
return this;
},
/**
* Perform custom animation on this element.
*
* Animation Properties
*
* The Animation Control Object enables gradual transitions for any member of an
* element's style object that takes a numeric value including but not limited to
* these properties:
* bottom, top, left, right
* height, width
* margin, padding
* borderWidth
* opacity
* fontSize
* lineHeight
*
*
*
* Animation Property Attributes
*
* Each Animation Property is a config object with optional properties:
*
*
* Animation Types
*
* The supported animation types:
* 'run' : Default
*
var el = Ext.get('complexEl');
el.animate(
// animation control object
{
borderWidth: {to: 3, from: 0},
opacity: {to: .3, from: 1},
height: {to: 50, from: el.getHeight()},
width: {to: 300, from: el.getWidth()},
top : {by: - 100, unit: 'px'},
},
0.35, // animation duration
null, // callback
'easeOut', // easing method
'run' // animation type ('run','color','motion','scroll')
);
*
*
* 'color'
* Animates transition of background, text, or border colors.
*
el.animate(
// animation control object
{
color: { to: '#06e' },
backgroundColor: { to: '#e06' }
},
0.35, // animation duration
null, // callback
'easeOut', // easing method
'color' // animation type ('run','color','motion','scroll')
);
*
*
*
* 'motion'
* Animates the motion of an element to/from specific points using optional bezier
* way points during transit.
*
el.animate(
// animation control object
{
borderWidth: {to: 3, from: 0},
opacity: {to: .3, from: 1},
height: {to: 50, from: el.getHeight()},
width: {to: 300, from: el.getWidth()},
top : {by: - 100, unit: 'px'},
points: {
to: [50, 100], // go to this point
control: [ // optional bezier way points
[ 600, 800],
[-100, 200]
]
}
},
3000, // animation duration (milliseconds!)
null, // callback
'easeOut', // easing method
'motion' // animation type ('run','color','motion','scroll')
);
*
*
* 'scroll'
* Animate horizontal or vertical scrolling of an overflowing page element.
*
el.animate(
// animation control object
{
scroll: {to: [400, 300]}
},
0.35, // animation duration
null, // callback
'easeOut', // easing method
'scroll' // animation type ('run','color','motion','scroll')
);
*
*
*
*
*
*
* @param {Object} args The animation control args
* @param {Float} duration (optional) How long the animation lasts in seconds (defaults to
.35 )
* @param {Function} onComplete (optional) Function to call when animation completes
* @param {String} easing (optional) {@link Ext.Fx#easing} method to use (defaults to
'easeOut' )
* @param {String} animType (optional)
'run' is the default. Can also be
'color' ,
*
'motion' , or
'scroll'
* @return {Ext.Element} this
*/
animate : function(args, duration, onComplete, easing, animType){
this.anim(args, {duration: duration, callback: onComplete, easing: easing}, animType);
return this;
},
/*
* @private Internal animation call
*/
anim : function(args, opt, animType, defaultDur, defaultEase, cb){
animType = animType || 'run';
opt = opt || {};
var me = this,
anim = Ext.lib.Anim[animType](
me.dom,
args,
(opt.duration || defaultDur) || .35,
(opt.easing || defaultEase) || 'easeOut',
function(){
if(cb) cb.call(me);
if(opt.callback) opt.callback.call(opt.scope || me, me, opt);
},
me
);
opt.anim = anim;
return anim;
},
// private legacy anim prep
preanim : function(a, i){
return !a[i] ? false : (typeof a[i] == 'object' ? a[i]: {duration: a[i+1], callback: a[i+2], easing: a[i+3]});
},
/**
* Checks whether the element is currently visible using both visibility and display properties.
* @return {Boolean} True if the element is currently visible, else false
*/
isVisible : function() {
var me = this,
dom = me.dom,
visible = data(dom, ISVISIBLE);
if(typeof visible == 'boolean'){ //return the cached value if registered
return visible;
}
//Determine the current state based on display states
visible = !me.isStyle(VISIBILITY, HIDDEN) &&
!me.isStyle(DISPLAY, NONE) &&
!((getVisMode(dom) == El.ASCLASS) && me.hasClass(me.visibilityCls || El.visibilityCls));
data(dom, ISVISIBLE, visible);
return visible;
},
/**
* Sets the visibility of the element (see details). If the visibilityMode is set to Element.DISPLAY, it will use
* the display property to hide the element, otherwise it uses visibility. The default is to hide and show using the visibility property.
* @param {Boolean} visible Whether the element is visible
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
setVisible : function(visible, animate){
var me = this, isDisplay, isVisibility, isOffsets, isNosize,
dom = me.dom,
visMode = getVisMode(dom);
// hideMode string override
if (typeof animate == 'string'){
switch (animate) {
case DISPLAY:
visMode = El.DISPLAY;
break;
case VISIBILITY:
visMode = El.VISIBILITY;
break;
case OFFSETS:
visMode = El.OFFSETS;
break;
case NOSIZE:
case ASCLASS:
visMode = El.ASCLASS;
break;
}
me.setVisibilityMode(visMode);
animate = false;
}
if (!animate || !me.anim) {
if(visMode == El.ASCLASS ){
me[visible?'removeClass':'addClass'](me.visibilityCls || El.visibilityCls);
} else if (visMode == El.DISPLAY){
return me.setDisplayed(visible);
} else if (visMode == El.OFFSETS){
if (!visible){
me.hideModeStyles = {
position: me.getStyle('position'),
top: me.getStyle('top'),
left: me.getStyle('left')
};
me.applyStyles({position: 'absolute', top: '-10000px', left: '-10000px'});
} else {
me.applyStyles(me.hideModeStyles || {position: '', top: '', left: ''});
delete me.hideModeStyles;
}
}else{
me.fixDisplay();
dom.style.visibility = visible ? "visible" : HIDDEN;
}
}else{
// closure for composites
if(visible){
me.setOpacity(.01);
me.setVisible(true);
}
me.anim({opacity: { to: (visible?1:0) }},
me.preanim(arguments, 1),
null,
.35,
'easeIn',
function(){
visible || me.setVisible(false).setOpacity(1);
});
}
data(dom, ISVISIBLE, visible); //set logical visibility state
return me;
},
/**
* @private
* Determine if the Element has a relevant height and width available based
* upon current logical visibility state
*/
hasMetrics : function(){
var dom = this.dom;
return this.isVisible() || (getVisMode(dom) == El.VISIBILITY);
},
/**
* Toggles the element's visibility or display, depending on visibility mode.
* @param {Boolean/Object} animate (optional) True for the default animation, or a standard Element animation config object
* @return {Ext.Element} this
*/
toggle : function(animate){
var me = this;
me.setVisible(!me.isVisible(), me.preanim(arguments, 0));
return me;
},
/**
* Sets the CSS display property. Uses originalDisplay if the specified value is a boolean true.
* @param {Mixed} value Boolean value to display the element using its default display, or a string to set the display directly.
* @return {Ext.Element} this
*/
setDisplayed : function(value) {
if(typeof value == "boolean"){
value = value ? getDisplay(this.dom) : NONE;
}
this.setStyle(DISPLAY, value);
return this;
},
// private
fixDisplay : function(){
var me = this;
if(me.isStyle(DISPLAY, NONE)){
me.setStyle(VISIBILITY, HIDDEN);
me.setStyle(DISPLAY, getDisplay(this.dom)); // first try reverting to default
if(me.isStyle(DISPLAY, NONE)){ // if that fails, default to block
me.setStyle(DISPLAY, "block");
}
}
},
/**
* Hide this element - Uses display mode to determine whether to use "display" or "visibility". See {@link #setVisible}.
* @param {Boolean/Object} animate (optional) true for the default animation or a standard Element animation config object
* @return {Ext.Element} this
*/
hide : function(animate){
// hideMode override
if (typeof animate == 'string'){
this.setVisible(false, animate);
return this;
}
this.setVisible(false, this.preanim(arguments, 0));
return this;
},
/**
* Show this element - Uses display mode to determine whether to use "display" or "visibility". See {@link #setVisible}.
* @param {Boolean/Object} animate (optional) true for the default animation or a standard Element animation config object
* @return {Ext.Element} this
*/
show : function(animate){
// hideMode override
if (typeof animate == 'string'){
this.setVisible(true, animate);
return this;
}
this.setVisible(true, this.preanim(arguments, 0));
return this;
}
};
}());(function(){
// contants
var NULL = null,
UNDEFINED = undefined,
TRUE = true,
FALSE = false,
SETX = "setX",
SETY = "setY",
SETXY = "setXY",
LEFT = "left",
BOTTOM = "bottom",
TOP = "top",
RIGHT = "right",
HEIGHT = "height",
WIDTH = "width",
POINTS = "points",
HIDDEN = "hidden",
ABSOLUTE = "absolute",
VISIBLE = "visible",
MOTION = "motion",
POSITION = "position",
EASEOUT = "easeOut",
/*
* Use a light flyweight here since we are using so many callbacks and are always assured a DOM element
*/
flyEl = new Ext.Element.Flyweight(),
queues = {},
getObject = function(o){
return o || {};
},
fly = function(dom){
flyEl.dom = dom;
flyEl.id = Ext.id(dom);
return flyEl;
},
/*
* Queueing now stored outside of the element due to closure issues
*/
getQueue = function(id){
if(!queues[id]){
queues[id] = [];
}
return queues[id];
},
setQueue = function(id, value){
queues[id] = value;
};
//Notifies Element that fx methods are available
Ext.enableFx = TRUE;
/**
* @class Ext.Fx
*
A class to provide basic animation and visual effects support. Note: This class is automatically applied
* to the {@link Ext.Element} interface when included, so all effects calls should be performed via {@link Ext.Element}.
* Conversely, since the effects are not actually defined in {@link Ext.Element}, Ext.Fx must be
* {@link Ext#enableFx included} in order for the Element effects to work.
*
*
Method Chaining
*
It is important to note that although the Fx methods and many non-Fx Element methods support "method chaining" in that
* they return the Element object itself as the method return value, it is not always possible to mix the two in a single
* method chain. The Fx methods use an internal effects queue so that each effect can be properly timed and sequenced.
* Non-Fx methods, on the other hand, have no such internal queueing and will always execute immediately. For this reason,
* while it may be possible to mix certain Fx and non-Fx method calls in a single chain, it may not always provide the
* expected results and should be done with care. Also see {@link #callback} .
*
*
Anchor Options for Motion Effects
*
Motion effects support 8-way anchoring, meaning that you can choose one of 8 different anchor points on the Element
* that will serve as either the start or end point of the animation. Following are all of the supported anchor positions:
Value Description
----- -----------------------------
tl The top left corner
t The center of the top edge
tr The top right corner
l The center of the left edge
r The center of the right edge
bl The bottom left corner
b The center of the bottom edge
br The bottom right corner
*
Note : some Fx methods accept specific custom config parameters. The options shown in the Config Options
* section below are common options that can be passed to any Fx method unless otherwise noted.
*
* @cfg {Function} callback A function called when the effect is finished. Note that effects are queued internally by the
* Fx class, so a callback is not required to specify another effect -- effects can simply be chained together
* and called in sequence (see note for
Method Chaining above), for example:
* el.slideIn().highlight();
*
* The callback is intended for any additional code that should run once a particular effect has completed. The Element
* being operated upon is passed as the first parameter.
*
* @cfg {Object} scope The scope (
this reference) in which the
{@link #callback} function is executed. Defaults to the browser window.
*
* @cfg {String} easing A valid Ext.lib.Easing value for the effect:
* backBoth
* backIn
* backOut
* bounceBoth
* bounceIn
* bounceOut
* easeBoth
* easeBothStrong
* easeIn
* easeInStrong
* easeNone
* easeOut
* easeOutStrong
* elasticBoth
* elasticIn
* elasticOut
*
*
* @cfg {String} afterCls A css class to apply after the effect
* @cfg {Number} duration The length of time (in seconds) that the effect should last
*
* @cfg {Number} endOpacity Only applicable for {@link #fadeIn} or {@link #fadeOut}, a number between
*
0 and
1 inclusive to configure the ending opacity value.
*
* @cfg {Boolean} remove Whether the Element should be removed from the DOM and destroyed after the effect finishes
* @cfg {Boolean} useDisplay Whether to use the
display CSS property instead of
visibility when hiding Elements (only applies to
* effects that end with the element being visually hidden, ignored otherwise)
* @cfg {String/Object/Function} afterStyle A style specification string, e.g.
"width:100px" , or an object
* in the form
{width:"100px"} , or a function which returns such a specification that will be applied to the
* Element after the effect finishes.
* @cfg {Boolean} block Whether the effect should block other effects from queueing while it runs
* @cfg {Boolean} concurrent Whether to allow subsequently-queued effects to run at the same time as the current effect, or to ensure that they run in sequence
* @cfg {Boolean} stopFx Whether preceding effects should be stopped and removed before running current effect (only applies to non blocking effects)
*/
Ext.Fx = {
// private - calls the function taking arguments from the argHash based on the key. Returns the return value of the function.
// this is useful for replacing switch statements (for example).
switchStatements : function(key, fn, argHash){
return fn.apply(this, argHash[key]);
},
/**
* Slides the element into view. An anchor point can be optionally passed to set the point of
* origin for the slide effect. This function automatically handles wrapping the element with
* a fixed-size container if needed. See the Fx class overview for valid anchor point options.
* Usage:
*
// default: slide the element in from the top
el.slideIn();
// custom: slide the element in from the right with a 2-second duration
el.slideIn('r', { duration: 2 });
// common config options shown with default values
el.slideIn('t', {
easing: 'easeOut',
duration: .5
});
* @param {String} anchor (optional) One of the valid Fx anchor positions (defaults to top: 't')
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
slideIn : function(anchor, o){
o = getObject(o);
var me = this,
dom = me.dom,
st = dom.style,
xy,
r,
b,
wrap,
after,
st,
args,
pt,
bw,
bh;
anchor = anchor || "t";
me.queueFx(o, function(){
xy = fly(dom).getXY();
// fix display to visibility
fly(dom).fixDisplay();
// restore values after effect
r = fly(dom).getFxRestore();
b = {x: xy[0], y: xy[1], 0: xy[0], 1: xy[1], width: dom.offsetWidth, height: dom.offsetHeight};
b.right = b.x + b.width;
b.bottom = b.y + b.height;
// fixed size for slide
fly(dom).setWidth(b.width).setHeight(b.height);
// wrap if needed
wrap = fly(dom).fxWrap(r.pos, o, HIDDEN);
st.visibility = VISIBLE;
st.position = ABSOLUTE;
// clear out temp styles after slide and unwrap
function after(){
fly(dom).fxUnwrap(wrap, r.pos, o);
st.width = r.width;
st.height = r.height;
fly(dom).afterFx(o);
}
// time to calculate the positions
pt = {to: [b.x, b.y]};
bw = {to: b.width};
bh = {to: b.height};
function argCalc(wrap, style, ww, wh, sXY, sXYval, s1, s2, w, h, p){
var ret = {};
fly(wrap).setWidth(ww).setHeight(wh);
if(fly(wrap)[sXY]){
fly(wrap)[sXY](sXYval);
}
style[s1] = style[s2] = "0";
if(w){
ret.width = w;
}
if(h){
ret.height = h;
}
if(p){
ret.points = p;
}
return ret;
};
args = fly(dom).switchStatements(anchor.toLowerCase(), argCalc, {
t : [wrap, st, b.width, 0, NULL, NULL, LEFT, BOTTOM, NULL, bh, NULL],
l : [wrap, st, 0, b.height, NULL, NULL, RIGHT, TOP, bw, NULL, NULL],
r : [wrap, st, b.width, b.height, SETX, b.right, LEFT, TOP, NULL, NULL, pt],
b : [wrap, st, b.width, b.height, SETY, b.bottom, LEFT, TOP, NULL, bh, pt],
tl : [wrap, st, 0, 0, NULL, NULL, RIGHT, BOTTOM, bw, bh, pt],
bl : [wrap, st, 0, 0, SETY, b.y + b.height, RIGHT, TOP, bw, bh, pt],
br : [wrap, st, 0, 0, SETXY, [b.right, b.bottom], LEFT, TOP, bw, bh, pt],
tr : [wrap, st, 0, 0, SETX, b.x + b.width, LEFT, BOTTOM, bw, bh, pt]
});
st.visibility = VISIBLE;
fly(wrap).show();
arguments.callee.anim = fly(wrap).fxanim(args,
o,
MOTION,
.5,
EASEOUT,
after);
});
return me;
},
/**
* Slides the element out of view. An anchor point can be optionally passed to set the end point
* for the slide effect. When the effect is completed, the element will be hidden (visibility =
* 'hidden') but block elements will still take up space in the document. The element must be removed
* from the DOM using the 'remove' config option if desired. This function automatically handles
* wrapping the element with a fixed-size container if needed. See the Fx class overview for valid anchor point options.
* Usage:
*
// default: slide the element out to the top
el.slideOut();
// custom: slide the element out to the right with a 2-second duration
el.slideOut('r', { duration: 2 });
// common config options shown with default values
el.slideOut('t', {
easing: 'easeOut',
duration: .5,
remove: false,
useDisplay: false
});
* @param {String} anchor (optional) One of the valid Fx anchor positions (defaults to top: 't')
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
slideOut : function(anchor, o){
o = getObject(o);
var me = this,
dom = me.dom,
st = dom.style,
xy = me.getXY(),
wrap,
r,
b,
a,
zero = {to: 0};
anchor = anchor || "t";
me.queueFx(o, function(){
// restore values after effect
r = fly(dom).getFxRestore();
b = {x: xy[0], y: xy[1], 0: xy[0], 1: xy[1], width: dom.offsetWidth, height: dom.offsetHeight};
b.right = b.x + b.width;
b.bottom = b.y + b.height;
// fixed size for slide
fly(dom).setWidth(b.width).setHeight(b.height);
// wrap if needed
wrap = fly(dom).fxWrap(r.pos, o, VISIBLE);
st.visibility = VISIBLE;
st.position = ABSOLUTE;
fly(wrap).setWidth(b.width).setHeight(b.height);
function after(){
o.useDisplay ? fly(dom).setDisplayed(FALSE) : fly(dom).hide();
fly(dom).fxUnwrap(wrap, r.pos, o);
st.width = r.width;
st.height = r.height;
fly(dom).afterFx(o);
}
function argCalc(style, s1, s2, p1, v1, p2, v2, p3, v3){
var ret = {};
style[s1] = style[s2] = "0";
ret[p1] = v1;
if(p2){
ret[p2] = v2;
}
if(p3){
ret[p3] = v3;
}
return ret;
};
a = fly(dom).switchStatements(anchor.toLowerCase(), argCalc, {
t : [st, LEFT, BOTTOM, HEIGHT, zero],
l : [st, RIGHT, TOP, WIDTH, zero],
r : [st, LEFT, TOP, WIDTH, zero, POINTS, {to : [b.right, b.y]}],
b : [st, LEFT, TOP, HEIGHT, zero, POINTS, {to : [b.x, b.bottom]}],
tl : [st, RIGHT, BOTTOM, WIDTH, zero, HEIGHT, zero],
bl : [st, RIGHT, TOP, WIDTH, zero, HEIGHT, zero, POINTS, {to : [b.x, b.bottom]}],
br : [st, LEFT, TOP, WIDTH, zero, HEIGHT, zero, POINTS, {to : [b.x + b.width, b.bottom]}],
tr : [st, LEFT, BOTTOM, WIDTH, zero, HEIGHT, zero, POINTS, {to : [b.right, b.y]}]
});
arguments.callee.anim = fly(wrap).fxanim(a,
o,
MOTION,
.5,
EASEOUT,
after);
});
return me;
},
/**
* Fades the element out while slowly expanding it in all directions. When the effect is completed, the
* element will be hidden (visibility = 'hidden') but block elements will still take up space in the document.
* The element must be removed from the DOM using the 'remove' config option if desired.
* Usage:
*
// default
el.puff();
// common config options shown with default values
el.puff({
easing: 'easeOut',
duration: .5,
remove: false,
useDisplay: false
});
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
puff : function(o){
o = getObject(o);
var me = this,
dom = me.dom,
st = dom.style,
width,
height,
r;
me.queueFx(o, function(){
width = fly(dom).getWidth();
height = fly(dom).getHeight();
fly(dom).clearOpacity();
fly(dom).show();
// restore values after effect
r = fly(dom).getFxRestore();
function after(){
o.useDisplay ? fly(dom).setDisplayed(FALSE) : fly(dom).hide();
fly(dom).clearOpacity();
fly(dom).setPositioning(r.pos);
st.width = r.width;
st.height = r.height;
st.fontSize = '';
fly(dom).afterFx(o);
}
arguments.callee.anim = fly(dom).fxanim({
width : {to : fly(dom).adjustWidth(width * 2)},
height : {to : fly(dom).adjustHeight(height * 2)},
points : {by : [-width * .5, -height * .5]},
opacity : {to : 0},
fontSize: {to : 200, unit: "%"}
},
o,
MOTION,
.5,
EASEOUT,
after);
});
return me;
},
/**
* Blinks the element as if it was clicked and then collapses on its center (similar to switching off a television).
* When the effect is completed, the element will be hidden (visibility = 'hidden') but block elements will still
* take up space in the document. The element must be removed from the DOM using the 'remove' config option if desired.
* Usage:
*
// default
el.switchOff();
// all config options shown with default values
el.switchOff({
easing: 'easeIn',
duration: .3,
remove: false,
useDisplay: false
});
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
switchOff : function(o){
o = getObject(o);
var me = this,
dom = me.dom,
st = dom.style,
r;
me.queueFx(o, function(){
fly(dom).clearOpacity();
fly(dom).clip();
// restore values after effect
r = fly(dom).getFxRestore();
function after(){
o.useDisplay ? fly(dom).setDisplayed(FALSE) : fly(dom).hide();
fly(dom).clearOpacity();
fly(dom).setPositioning(r.pos);
st.width = r.width;
st.height = r.height;
fly(dom).afterFx(o);
};
fly(dom).fxanim({opacity : {to : 0.3}},
NULL,
NULL,
.1,
NULL,
function(){
fly(dom).clearOpacity();
(function(){
fly(dom).fxanim({
height : {to : 1},
points : {by : [0, fly(dom).getHeight() * .5]}
},
o,
MOTION,
0.3,
'easeIn',
after);
}).defer(100);
});
});
return me;
},
/**
* Highlights the Element by setting a color (applies to the background-color by default, but can be
* changed using the "attr" config option) and then fading back to the original color. If no original
* color is available, you should provide the "endColor" config option which will be cleared after the animation.
* Usage:
// default: highlight background to yellow
el.highlight();
// custom: highlight foreground text to blue for 2 seconds
el.highlight("0000ff", { attr: 'color', duration: 2 });
// common config options shown with default values
el.highlight("ffff9c", {
attr: "background-color", //can be any valid CSS property (attribute) that supports a color value
endColor: (current color) or "ffffff",
easing: 'easeIn',
duration: 1
});
* @param {String} color (optional) The highlight color. Should be a 6 char hex color without the leading # (defaults to yellow: 'ffff9c')
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
highlight : function(color, o){
o = getObject(o);
var me = this,
dom = me.dom,
attr = o.attr || "backgroundColor",
a = {},
restore;
me.queueFx(o, function(){
fly(dom).clearOpacity();
fly(dom).show();
function after(){
dom.style[attr] = restore;
fly(dom).afterFx(o);
}
restore = dom.style[attr];
a[attr] = {from: color || "ffff9c", to: o.endColor || fly(dom).getColor(attr) || "ffffff"};
arguments.callee.anim = fly(dom).fxanim(a,
o,
'color',
1,
'easeIn',
after);
});
return me;
},
/**
* Shows a ripple of exploding, attenuating borders to draw attention to an Element.
* Usage:
// default: a single light blue ripple
el.frame();
// custom: 3 red ripples lasting 3 seconds total
el.frame("ff0000", 3, { duration: 3 });
// common config options shown with default values
el.frame("C3DAF9", 1, {
duration: 1 //duration of each individual ripple.
// Note: Easing is not configurable and will be ignored if included
});
* @param {String} color (optional) The color of the border. Should be a 6 char hex color without the leading # (defaults to light blue: 'C3DAF9').
* @param {Number} count (optional) The number of ripples to display (defaults to 1)
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
frame : function(color, count, o){
o = getObject(o);
var me = this,
dom = me.dom,
proxy,
active;
me.queueFx(o, function(){
color = color || '#C3DAF9';
if(color.length == 6){
color = '#' + color;
}
count = count || 1;
fly(dom).show();
var xy = fly(dom).getXY(),
b = {x: xy[0], y: xy[1], 0: xy[0], 1: xy[1], width: dom.offsetWidth, height: dom.offsetHeight},
queue = function(){
proxy = fly(document.body || document.documentElement).createChild({
style:{
position : ABSOLUTE,
'z-index': 35000, // yee haw
border : '0px solid ' + color
}
});
return proxy.queueFx({}, animFn);
};
arguments.callee.anim = {
isAnimated: true,
stop: function() {
count = 0;
proxy.stopFx();
}
};
function animFn(){
var scale = Ext.isBorderBox ? 2 : 1;
active = proxy.anim({
top : {from : b.y, to : b.y - 20},
left : {from : b.x, to : b.x - 20},
borderWidth : {from : 0, to : 10},
opacity : {from : 1, to : 0},
height : {from : b.height, to : b.height + 20 * scale},
width : {from : b.width, to : b.width + 20 * scale}
},{
duration: o.duration || 1,
callback: function() {
proxy.remove();
--count > 0 ? queue() : fly(dom).afterFx(o);
}
});
arguments.callee.anim = {
isAnimated: true,
stop: function(){
active.stop();
}
};
};
queue();
});
return me;
},
/**
* Creates a pause before any subsequent queued effects begin. If there are
* no effects queued after the pause it will have no effect.
* Usage:
el.pause(1);
* @param {Number} seconds The length of time to pause (in seconds)
* @return {Ext.Element} The Element
*/
pause : function(seconds){
var dom = this.dom,
t;
this.queueFx({}, function(){
t = setTimeout(function(){
fly(dom).afterFx({});
}, seconds * 1000);
arguments.callee.anim = {
isAnimated: true,
stop: function(){
clearTimeout(t);
fly(dom).afterFx({});
}
};
});
return this;
},
/**
* Fade an element in (from transparent to opaque). The ending opacity can be specified
* using the
{@link #endOpacity} config option.
* Usage:
// default: fade in from opacity 0 to 100%
el.fadeIn();
// custom: fade in from opacity 0 to 75% over 2 seconds
el.fadeIn({ endOpacity: .75, duration: 2});
// common config options shown with default values
el.fadeIn({
endOpacity: 1, //can be any value between 0 and 1 (e.g. .5)
easing: 'easeOut',
duration: .5
});
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
fadeIn : function(o){
o = getObject(o);
var me = this,
dom = me.dom,
to = o.endOpacity || 1;
me.queueFx(o, function(){
fly(dom).setOpacity(0);
fly(dom).fixDisplay();
dom.style.visibility = VISIBLE;
arguments.callee.anim = fly(dom).fxanim({opacity:{to:to}},
o, NULL, .5, EASEOUT, function(){
if(to == 1){
fly(dom).clearOpacity();
}
fly(dom).afterFx(o);
});
});
return me;
},
/**
* Fade an element out (from opaque to transparent). The ending opacity can be specified
* using the
{@link #endOpacity} config option. Note that IE may require
*
{@link #useDisplay}:true in order to redisplay correctly.
* Usage:
// default: fade out from the element's current opacity to 0
el.fadeOut();
// custom: fade out from the element's current opacity to 25% over 2 seconds
el.fadeOut({ endOpacity: .25, duration: 2});
// common config options shown with default values
el.fadeOut({
endOpacity: 0, //can be any value between 0 and 1 (e.g. .5)
easing: 'easeOut',
duration: .5,
remove: false,
useDisplay: false
});
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
fadeOut : function(o){
o = getObject(o);
var me = this,
dom = me.dom,
style = dom.style,
to = o.endOpacity || 0;
me.queueFx(o, function(){
arguments.callee.anim = fly(dom).fxanim({
opacity : {to : to}},
o,
NULL,
.5,
EASEOUT,
function(){
if(to == 0){
Ext.Element.data(dom, 'visibilityMode') == Ext.Element.DISPLAY || o.useDisplay ?
style.display = "none" :
style.visibility = HIDDEN;
fly(dom).clearOpacity();
}
fly(dom).afterFx(o);
});
});
return me;
},
/**
* Animates the transition of an element's dimensions from a starting height/width
* to an ending height/width. This method is a convenience implementation of {@link shift}.
* Usage:
// change height and width to 100x100 pixels
el.scale(100, 100);
// common config options shown with default values. The height and width will default to
// the element's existing values if passed as null.
el.scale(
[element's width],
[element's height], {
easing: 'easeOut',
duration: .35
}
);
* @param {Number} width The new width (pass undefined to keep the original width)
* @param {Number} height The new height (pass undefined to keep the original height)
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
scale : function(w, h, o){
this.shift(Ext.apply({}, o, {
width: w,
height: h
}));
return this;
},
/**
* Animates the transition of any combination of an element's dimensions, xy position and/or opacity.
* Any of these properties not specified in the config object will not be changed. This effect
* requires that at least one new dimension, position or opacity setting must be passed in on
* the config object in order for the function to have any effect.
* Usage:
// slide the element horizontally to x position 200 while changing the height and opacity
el.shift({ x: 200, height: 50, opacity: .8 });
// common config options shown with default values.
el.shift({
width: [element's width],
height: [element's height],
x: [element's x position],
y: [element's y position],
opacity: [element's opacity],
easing: 'easeOut',
duration: .35
});
* @param {Object} options Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
shift : function(o){
o = getObject(o);
var dom = this.dom,
a = {};
this.queueFx(o, function(){
for (var prop in o) {
if (o[prop] != UNDEFINED) {
a[prop] = {to : o[prop]};
}
}
a.width ? a.width.to = fly(dom).adjustWidth(o.width) : a;
a.height ? a.height.to = fly(dom).adjustWidth(o.height) : a;
if (a.x || a.y || a.xy) {
a.points = a.xy ||
{to : [ a.x ? a.x.to : fly(dom).getX(),
a.y ? a.y.to : fly(dom).getY()]};
}
arguments.callee.anim = fly(dom).fxanim(a,
o,
MOTION,
.35,
EASEOUT,
function(){
fly(dom).afterFx(o);
});
});
return this;
},
/**
* Slides the element while fading it out of view. An anchor point can be optionally passed to set the
* ending point of the effect.
* Usage:
*
// default: slide the element downward while fading out
el.ghost();
// custom: slide the element out to the right with a 2-second duration
el.ghost('r', { duration: 2 });
// common config options shown with default values
el.ghost('b', {
easing: 'easeOut',
duration: .5,
remove: false,
useDisplay: false
});
* @param {String} anchor (optional) One of the valid Fx anchor positions (defaults to bottom: 'b')
* @param {Object} options (optional) Object literal with any of the Fx config options
* @return {Ext.Element} The Element
*/
ghost : function(anchor, o){
o = getObject(o);
var me = this,
dom = me.dom,
st = dom.style,
a = {opacity: {to: 0}, points: {}},
pt = a.points,
r,
w,
h;
anchor = anchor || "b";
me.queueFx(o, function(){
// restore values after effect
r = fly(dom).getFxRestore();
w = fly(dom).getWidth();
h = fly(dom).getHeight();
function after(){
o.useDisplay ? fly(dom).setDisplayed(FALSE) : fly(dom).hide();
fly(dom).clearOpacity();
fly(dom).setPositioning(r.pos);
st.width = r.width;
st.height = r.height;
fly(dom).afterFx(o);
}
pt.by = fly(dom).switchStatements(anchor.toLowerCase(), function(v1,v2){ return [v1, v2];}, {
t : [0, -h],
l : [-w, 0],
r : [w, 0],
b : [0, h],
tl : [-w, -h],
bl : [-w, h],
br : [w, h],
tr : [w, -h]
});
arguments.callee.anim = fly(dom).fxanim(a,
o,
MOTION,
.5,
EASEOUT, after);
});
return me;
},
/**
* Ensures that all effects queued after syncFx is called on the element are
* run concurrently. This is the opposite of {@link #sequenceFx}.
* @return {Ext.Element} The Element
*/
syncFx : function(){
var me = this;
me.fxDefaults = Ext.apply(me.fxDefaults || {}, {
block : FALSE,
concurrent : TRUE,
stopFx : FALSE
});
return me;
},
/**
* Ensures that all effects queued after sequenceFx is called on the element are
* run in sequence. This is the opposite of {@link #syncFx}.
* @return {Ext.Element} The Element
*/
sequenceFx : function(){
var me = this;
me.fxDefaults = Ext.apply(me.fxDefaults || {}, {
block : FALSE,
concurrent : FALSE,
stopFx : FALSE
});
return me;
},
/* @private */
nextFx : function(){
var ef = getQueue(this.dom.id)[0];
if(ef){
ef.call(this);
}
},
/**
* Returns true if the element has any effects actively running or queued, else returns false.
* @return {Boolean} True if element has active effects, else false
*/
hasActiveFx : function(){
return getQueue(this.dom.id)[0];
},
/**
* Stops any running effects and clears the element's internal effects queue if it contains
* any additional effects that haven't started yet.
* @return {Ext.Element} The Element
*/
stopFx : function(finish){
var me = this,
id = me.dom.id;
if(me.hasActiveFx()){
var cur = getQueue(id)[0];
if(cur && cur.anim){
if(cur.anim.isAnimated){
setQueue(id, [cur]); //clear
cur.anim.stop(finish !== undefined ? finish : TRUE);
}else{
setQueue(id, []);
}
}
}
return me;
},
/* @private */
beforeFx : function(o){
if(this.hasActiveFx() && !o.concurrent){
if(o.stopFx){
this.stopFx();
return TRUE;
}
return FALSE;
}
return TRUE;
},
/**
* Returns true if the element is currently blocking so that no other effect can be queued
* until this effect is finished, else returns false if blocking is not set. This is commonly
* used to ensure that an effect initiated by a user action runs to completion prior to the
* same effect being restarted (e.g., firing only one effect even if the user clicks several times).
* @return {Boolean} True if blocking, else false
*/
hasFxBlock : function(){
var q = getQueue(this.dom.id);
return q && q[0] && q[0].block;
},
/* @private */
queueFx : function(o, fn){
var me = fly(this.dom);
if(!me.hasFxBlock()){
Ext.applyIf(o, me.fxDefaults);
if(!o.concurrent){
var run = me.beforeFx(o);
fn.block = o.block;
getQueue(me.dom.id).push(fn);
if(run){
me.nextFx();
}
}else{
fn.call(me);
}
}
return me;
},
/* @private */
fxWrap : function(pos, o, vis){
var dom = this.dom,
wrap,
wrapXY;
if(!o.wrap || !(wrap = Ext.getDom(o.wrap))){
if(o.fixPosition){
wrapXY = fly(dom).getXY();
}
var div = document.createElement("div");
div.style.visibility = vis;
wrap = dom.parentNode.insertBefore(div, dom);
fly(wrap).setPositioning(pos);
if(fly(wrap).isStyle(POSITION, "static")){
fly(wrap).position("relative");
}
fly(dom).clearPositioning('auto');
fly(wrap).clip();
wrap.appendChild(dom);
if(wrapXY){
fly(wrap).setXY(wrapXY);
}
}
return wrap;
},
/* @private */
fxUnwrap : function(wrap, pos, o){
var dom = this.dom;
fly(dom).clearPositioning();
fly(dom).setPositioning(pos);
if(!o.wrap){
var pn = fly(wrap).dom.parentNode;
pn.insertBefore(dom, wrap);
fly(wrap).remove();
}
},
/* @private */
getFxRestore : function(){
var st = this.dom.style;
return {pos: this.getPositioning(), width: st.width, height : st.height};
},
/* @private */
afterFx : function(o){
var dom = this.dom,
id = dom.id;
if(o.afterStyle){
fly(dom).setStyle(o.afterStyle);
}
if(o.afterCls){
fly(dom).addClass(o.afterCls);
}
if(o.remove == TRUE){
fly(dom).remove();
}
if(o.callback){
o.callback.call(o.scope, fly(dom));
}
if(!o.concurrent){
getQueue(id).shift();
fly(dom).nextFx();
}
},
/* @private */
fxanim : function(args, opt, animType, defaultDur, defaultEase, cb){
animType = animType || 'run';
opt = opt || {};
var anim = Ext.lib.Anim[animType](
this.dom,
args,
(opt.duration || defaultDur) || .35,
(opt.easing || defaultEase) || EASEOUT,
cb,
this
);
opt.anim = anim;
return anim;
}
};
// backwards compat
Ext.Fx.resize = Ext.Fx.scale;
//When included, Ext.Fx is automatically applied to Element so that all basic
//effects are available directly via the Element API
Ext.Element.addMethods(Ext.Fx);
})();
/**
* @class Ext.CompositeElementLite
*
This class encapsulates a collection of DOM elements, providing methods to filter
* members, or to perform collective actions upon the whole set.
*
Although they are not listed, this class supports all of the methods of {@link Ext.Element} and
* {@link Ext.Fx}. The methods from these classes will be performed on all the elements in this collection.
* Example:
var els = Ext.select("#some-el div.some-class");
// or select directly from an existing element
var el = Ext.get('some-el');
el.select('div.some-class');
els.setWidth(100); // all elements become 100 width
els.hide(true); // all elements fade out and hide
// or
els.setWidth(100).hide(true);
*/
Ext.CompositeElementLite = function(els, root){
/**
* The Array of DOM elements which this CompositeElement encapsulates. Read-only.
* This will not usually be accessed in developers' code, but developers wishing
* to augment the capabilities of the CompositeElementLite class may use it when adding
* methods to the class.
* For example to add the nextAll method to the class to add all
* following siblings of selected elements, the code would be
Ext.override(Ext.CompositeElementLite, {
nextAll: function() {
var els = this.elements, i, l = els.length, n, r = [], ri = -1;
// Loop through all elements in this Composite, accumulating
// an Array of all siblings.
for (i = 0; i < l; i++) {
for (n = els[i].nextSibling; n; n = n.nextSibling) {
r[++ri] = n;
}
}
// Add all found siblings to this Composite
return this.add(r);
}
});
* @type Array
* @property elements
*/
this.elements = [];
this.add(els, root);
this.el = new Ext.Element.Flyweight();
};
Ext.CompositeElementLite.prototype = {
isComposite: true,
// private
getElement : function(el){
// Set the shared flyweight dom property to the current element
var e = this.el;
e.dom = el;
e.id = el.id;
return e;
},
// private
transformElement : function(el){
return Ext.getDom(el);
},
/**
* Returns the number of elements in this Composite.
* @return Number
*/
getCount : function(){
return this.elements.length;
},
/**
* Adds elements to this Composite object.
* @param {Mixed} els Either an Array of DOM elements to add, or another Composite object who's elements should be added.
* @return {CompositeElement} This Composite object.
*/
add : function(els, root){
var me = this,
elements = me.elements;
if(!els){
return this;
}
if(typeof els == "string"){
els = Ext.Element.selectorFunction(els, root);
}else if(els.isComposite){
els = els.elements;
}else if(!Ext.isIterable(els)){
els = [els];
}
for(var i = 0, len = els.length; i < len; ++i){
elements.push(me.transformElement(els[i]));
}
return me;
},
invoke : function(fn, args){
var me = this,
els = me.elements,
len = els.length,
e,
i;
for(i = 0; i < len; i++) {
e = els[i];
if(e){
Ext.Element.prototype[fn].apply(me.getElement(e), args);
}
}
return me;
},
/**
* Returns a flyweight Element of the dom element object at the specified index
* @param {Number} index
* @return {Ext.Element}
*/
item : function(index){
var me = this,
el = me.elements[index],
out = null;
if(el){
out = me.getElement(el);
}
return out;
},
// fixes scope with flyweight
addListener : function(eventName, handler, scope, opt){
var els = this.elements,
len = els.length,
i, e;
for(i = 0; iCalls the passed function for each element in this composite.
* @param {Function} fn The function to call. The function is passed the following parameters:
* el : ElementThe current Element in the iteration.
* This is the flyweight (shared) Ext.Element instance, so if you require a
* a reference to the dom node, use el.dom.
* c : CompositeThis Composite object.
* idx : NumberThe zero-based index in the iteration.
*
* @param {Object} scope (optional) The scope (this reference) in which the function is executed. (defaults to the Element)
* @return {CompositeElement} this
*/
each : function(fn, scope){
var me = this,
els = me.elements,
len = els.length,
i, e;
for(i = 0; i
* el : Ext.ElementThe current DOM element.
* index : NumberThe current index within the collection.
*
* @return {CompositeElement} this
*/
filter : function(selector){
var els = [],
me = this,
fn = Ext.isFunction(selector) ? selector
: function(el){
return el.is(selector);
};
me.each(function(el, self, i) {
if (fn(el, i) !== false) {
els[els.length] = me.transformElement(el);
}
});
me.elements = els;
return me;
},
/**
* Find the index of the passed element within the composite collection.
* @param el {Mixed} The id of an element, or an Ext.Element, or an HtmlElement to find within the composite collection.
* @return Number The index of the passed Ext.Element in the composite collection, or -1 if not found.
*/
indexOf : function(el){
return this.elements.indexOf(this.transformElement(el));
},
/**
* Replaces the specified element with the passed element.
* @param {Mixed} el The id of an element, the Element itself, the index of the element in this composite
* to replace.
* @param {Mixed} replacement The id of an element or the Element itself.
* @param {Boolean} domReplace (Optional) True to remove and replace the element in the document too.
* @return {CompositeElement} this
*/
replaceElement : function(el, replacement, domReplace){
var index = !isNaN(el) ? el : this.indexOf(el),
d;
if(index > -1){
replacement = Ext.getDom(replacement);
if(domReplace){
d = this.elements[index];
d.parentNode.insertBefore(replacement, d);
Ext.removeNode(d);
}
this.elements.splice(index, 1, replacement);
}
return this;
},
/**
* Removes all elements.
*/
clear : function(){
this.elements = [];
}
};
Ext.CompositeElementLite.prototype.on = Ext.CompositeElementLite.prototype.addListener;
/**
* @private
* Copies all of the functions from Ext.Element's prototype onto CompositeElementLite's prototype.
* This is called twice - once immediately below, and once again after additional Ext.Element
* are added in Ext JS
*/
Ext.CompositeElementLite.importElementMethods = function() {
var fnName,
ElProto = Ext.Element.prototype,
CelProto = Ext.CompositeElementLite.prototype;
for (fnName in ElProto) {
if (typeof ElProto[fnName] == 'function'){
(function(fnName) {
CelProto[fnName] = CelProto[fnName] || function() {
return this.invoke(fnName, arguments);
};
}).call(CelProto, fnName);
}
}
};
Ext.CompositeElementLite.importElementMethods();
if(Ext.DomQuery){
Ext.Element.selectorFunction = Ext.DomQuery.select;
}
/**
* Selects elements based on the passed CSS selector to enable {@link Ext.Element Element} methods
* to be applied to many related elements in one statement through the returned {@link Ext.CompositeElement CompositeElement} or
* {@link Ext.CompositeElementLite CompositeElementLite} object.
* @param {String/Array} selector The CSS selector or an array of elements
* @param {HTMLElement/String} root (optional) The root element of the query or id of the root
* @return {CompositeElementLite/CompositeElement}
* @member Ext.Element
* @method select
* @static
*/
Ext.Element.select = function(selector, root){
var els;
if(typeof selector == "string"){
els = Ext.Element.selectorFunction(selector, root);
}else if(selector.length !== undefined){
els = selector;
}else{
throw "Invalid selector";
}
return new Ext.CompositeElementLite(els);
};
/**
* Selects elements based on the passed CSS selector to enable {@link Ext.Element Element} methods
* to be applied to many related elements in one statement through the returned {@link Ext.CompositeElement CompositeElement} or
* {@link Ext.CompositeElementLite CompositeElementLite} object.
* @param {String/Array} selector The CSS selector or an array of elements
* @param {HTMLElement/String} root (optional) The root element of the query or id of the root
* @return {CompositeElementLite/CompositeElement}
* @member Ext
* @method select
*/
Ext.select = Ext.Element.select;
(function(){
var BEFOREREQUEST = "beforerequest",
REQUESTCOMPLETE = "requestcomplete",
REQUESTEXCEPTION = "requestexception",
UNDEFINED = undefined,
LOAD = 'load',
POST = 'POST',
GET = 'GET',
WINDOW = window;
/**
* @class Ext.data.Connection
* @extends Ext.util.Observable
* The class encapsulates a connection to the page's originating domain, allowing requests to be made
* either to a configured URL, or to a URL specified at request time.
* Requests made by this class are asynchronous, and will return immediately. No data from
* the server will be available to the statement immediately following the {@link #request} call.
* To process returned data, use a
* success callback
* in the request options object,
* or an {@link #requestcomplete event listener}.
*
File Uploads File uploads are not performed using normal "Ajax" techniques, that
* is they are not performed using XMLHttpRequests. Instead the form is submitted in the standard
* manner with the DOM <form> element temporarily modified to have its
* target set to refer
* to a dynamically generated, hidden <iframe> which is inserted into the document
* but removed after the return data has been gathered.
* The server response is parsed by the browser to create the document for the IFRAME. If the
* server is using JSON to send the return object, then the
* Content-Type header
* must be set to "text/html" in order to tell the browser to insert the text unchanged into the document body.
* Characters which are significant to an HTML parser must be sent as HTML entities, so encode
* "<" as "<", "&" as "&" etc.
* The response text is retrieved from the document, and a fake XMLHttpRequest object
* is created containing a responseText property in order to conform to the
* requirements of event handlers and callbacks.
* Be aware that file upload packets are sent with the content type multipart/form
* and some server technologies (notably JEE) may require some custom processing in order to
* retrieve parameter names and parameter values from the packet content.
* Also note that it's not possible to check the response code of the hidden iframe, so the success handler will ALWAYS fire.
* @constructor
* @param {Object} config a configuration object.
*/
Ext.data.Connection = function(config){
Ext.apply(this, config);
this.addEvents(
/**
* @event beforerequest
* Fires before a network request is made to retrieve a data object.
* @param {Connection} conn This Connection object.
* @param {Object} options The options config object passed to the {@link #request} method.
*/
BEFOREREQUEST,
/**
* @event requestcomplete
* Fires if the request was successfully completed.
* @param {Connection} conn This Connection object.
* @param {Object} response The XHR object containing the response data.
* See The XMLHttpRequest Object
* for details.
* @param {Object} options The options config object passed to the {@link #request} method.
*/
REQUESTCOMPLETE,
/**
* @event requestexception
* Fires if an error HTTP status was returned from the server.
* See HTTP Status Code Definitions
* for details of HTTP status codes.
* @param {Connection} conn This Connection object.
* @param {Object} response The XHR object containing the response data.
* See The XMLHttpRequest Object
* for details.
* @param {Object} options The options config object passed to the {@link #request} method.
*/
REQUESTEXCEPTION
);
Ext.data.Connection.superclass.constructor.call(this);
};
Ext.extend(Ext.data.Connection, Ext.util.Observable, {
/**
* @cfg {String} url (Optional) The default URL to be used for requests to the server. Defaults to undefined.
* The url config may be a function which returns the URL to use for the Ajax request. The scope
* (this reference) of the function is the scope option passed to the {@link #request} method.
*/
/**
* @cfg {Object} extraParams (Optional) An object containing properties which are used as
* extra parameters to each request made by this object. (defaults to undefined)
*/
/**
* @cfg {Object} defaultHeaders (Optional) An object containing request headers which are added
* to each request made by this object. (defaults to undefined)
*/
/**
* @cfg {String} method (Optional) The default HTTP method to be used for requests.
* (defaults to undefined; if not set, but {@link #request} params are present, POST will be used;
* otherwise, GET will be used.)
*/
/**
* @cfg {Number} timeout (Optional) The timeout in milliseconds to be used for requests. (defaults to 30000)
*/
timeout : 30000,
/**
* @cfg {Boolean} autoAbort (Optional) Whether this request should abort any pending requests. (defaults to false)
* @type Boolean
*/
autoAbort:false,
/**
* @cfg {Boolean} disableCaching (Optional) True to add a unique cache-buster param to GET requests. (defaults to true)
* @type Boolean
*/
disableCaching: true,
/**
* @cfg {String} disableCachingParam (Optional) Change the parameter which is sent went disabling caching
* through a cache buster. Defaults to '_dc'
* @type String
*/
disableCachingParam: '_dc',
/**
* Sends an HTTP request to a remote server.
* Important: Ajax server requests are asynchronous, and this call will
* return before the response has been received. Process any returned data
* in a callback function.
*
Ext.Ajax.request({
url: 'ajax_demo/sample.json',
success: function(response, opts) {
var obj = Ext.decode(response.responseText);
console.dir(obj);
},
failure: function(response, opts) {
console.log('server-side failure with status code ' + response.status);
}
});
*
* To execute a callback function in the correct scope, use the scope option.
* @param {Object} options An object which may contain the following properties:
* url : String/Function (Optional)The URL to
* which to send the request, or a function to call which returns a URL string. The scope of the
* function is specified by the scope option. Defaults to the configured
* {@link #url} .
* params : Object/String/Function (Optional)
* An object containing properties which are used as parameters to the
* request, a url encoded string or a function to call to get either. The scope of the function
* is specified by the scope option.
* method : String (Optional)The HTTP method to use
* for the request. Defaults to the configured method, or if no method was configured,
* "GET" if no parameters are being sent, and "POST" if parameters are being sent. Note that
* the method name is case-sensitive and should be all caps.
* callback : Function (Optional)The
* function to be called upon receipt of the HTTP response. The callback is
* called regardless of success or failure and is passed the following
* parameters:
* success : Function (Optional)The function
* to be called upon success of the request. The callback is passed the following
* parameters:
* failure : Function (Optional)The function
* to be called upon failure of the request. The callback is passed the
* following parameters:
* scope : Object (Optional)The scope in
* which to execute the callbacks: The "this" object for the callback function. If the url , or params options were
* specified as functions from which to draw values, then this also serves as the scope for those function calls.
* Defaults to the browser window.
* timeout : Number (Optional)The timeout in milliseconds to be used for this request. Defaults to 30 seconds.
* form : Element/HTMLElement/String (Optional)The <form>
* Element or the id of the <form> to pull parameters from.
* isUpload : Boolean (Optional)Only meaningful when used
* with the form option .
*
True if the form object is a file upload (will be set automatically if the form was
* configured with enctype "multipart/form-data").
*
File uploads are not performed using normal "Ajax" techniques, that is they are not
* performed using XMLHttpRequests. Instead the form is submitted in the standard manner with the
* DOM <form> element temporarily modified to have its
* target set to refer
* to a dynamically generated, hidden <iframe> which is inserted into the document
* but removed after the return data has been gathered.
*
The server response is parsed by the browser to create the document for the IFRAME. If the
* server is using JSON to send the return object, then the
* Content-Type header
* must be set to "text/html" in order to tell the browser to insert the text unchanged into the document body.
*
The response text is retrieved from the document, and a fake XMLHttpRequest object
* is created containing a responseText property in order to conform to the
* requirements of event handlers and callbacks.
*
Be aware that file upload packets are sent with the content type multipart/form
* and some server technologies (notably JEE) may require some custom processing in order to
* retrieve parameter names and parameter values from the packet content.
*
* headers : Object (Optional)Request
* headers to set for the request.
* xmlData : Object (Optional)XML document
* to use for the post. Note: This will be used instead of params for the post
* data. Any params will be appended to the URL.
* jsonData : Object/String (Optional)JSON
* data to use as the post. Note: This will be used instead of params for the post
* data. Any params will be appended to the URL.
* disableCaching : Boolean (Optional)True
* to add a unique cache-buster param to GET requests.
*
* The options object may also contain any other property which might be needed to perform
* postprocessing in a callback because it is passed to callback functions.
* @return {Number} transactionId The id of the server transaction. This may be used
* to cancel the request.
*/
request : function(o){
var me = this;
if(me.fireEvent(BEFOREREQUEST, me, o)){
if (o.el) {
if(!Ext.isEmpty(o.indicatorText)){
me.indicatorText = ''+o.indicatorText+"
";
}
if(me.indicatorText) {
Ext.getDom(o.el).innerHTML = me.indicatorText;
}
o.success = (Ext.isFunction(o.success) ? o.success : function(){}).createInterceptor(function(response) {
Ext.getDom(o.el).innerHTML = response.responseText;
});
}
var p = o.params,
url = o.url || me.url,
method,
cb = {success: me.handleResponse,
failure: me.handleFailure,
scope: me,
argument: {options: o},
timeout : Ext.num(o.timeout, me.timeout)
},
form,
serForm;
if (Ext.isFunction(p)) {
p = p.call(o.scope||WINDOW, o);
}
p = Ext.urlEncode(me.extraParams, Ext.isObject(p) ? Ext.urlEncode(p) : p);
if (Ext.isFunction(url)) {
url = url.call(o.scope || WINDOW, o);
}
if((form = Ext.getDom(o.form))){
url = url || form.action;
if(o.isUpload || (/multipart\/form-data/i.test(form.getAttribute("enctype")))) {
return me.doFormUpload.call(me, o, p, url);
}
serForm = Ext.lib.Ajax.serializeForm(form);
p = p ? (p + '&' + serForm) : serForm;
}
method = o.method || me.method || ((p || o.xmlData || o.jsonData) ? POST : GET);
if(method === GET && (me.disableCaching && o.disableCaching !== false) || o.disableCaching === true){
var dcp = o.disableCachingParam || me.disableCachingParam;
url = Ext.urlAppend(url, dcp + '=' + (new Date().getTime()));
}
o.headers = Ext.applyIf(o.headers || {}, me.defaultHeaders || {});
if(o.autoAbort === true || me.autoAbort) {
me.abort();
}
if((method == GET || o.xmlData || o.jsonData) && p){
url = Ext.urlAppend(url, p);
p = '';
}
return (me.transId = Ext.lib.Ajax.request(method, url, cb, p, o));
}else{
return o.callback ? o.callback.apply(o.scope, [o,UNDEFINED,UNDEFINED]) : null;
}
},
/**
* Determine whether this object has a request outstanding.
* @param {Number} transactionId (Optional) defaults to the last transaction
* @return {Boolean} True if there is an outstanding request.
*/
isLoading : function(transId){
return transId ? Ext.lib.Ajax.isCallInProgress(transId) : !! this.transId;
},
/**
* Aborts any outstanding request.
* @param {Number} transactionId (Optional) defaults to the last transaction
*/
abort : function(transId){
if(transId || this.isLoading()){
Ext.lib.Ajax.abort(transId || this.transId);
}
},
// private
handleResponse : function(response){
this.transId = false;
var options = response.argument.options;
response.argument = options ? options.argument : null;
this.fireEvent(REQUESTCOMPLETE, this, response, options);
if(options.success){
options.success.call(options.scope, response, options);
}
if(options.callback){
options.callback.call(options.scope, options, true, response);
}
},
// private
handleFailure : function(response, e){
this.transId = false;
var options = response.argument.options;
response.argument = options ? options.argument : null;
this.fireEvent(REQUESTEXCEPTION, this, response, options, e);
if(options.failure){
options.failure.call(options.scope, response, options);
}
if(options.callback){
options.callback.call(options.scope, options, false, response);
}
},
// private
doFormUpload : function(o, ps, url){
var id = Ext.id(),
doc = document,
frame = doc.createElement('iframe'),
form = Ext.getDom(o.form),
hiddens = [],
hd,
encoding = 'multipart/form-data',
buf = {
target: form.target,
method: form.method,
encoding: form.encoding,
enctype: form.enctype,
action: form.action
};
/*
* Originally this behaviour was modified for Opera 10 to apply the secure URL after
* the frame had been added to the document. It seems this has since been corrected in
* Opera so the behaviour has been reverted, the URL will be set before being added.
*/
Ext.fly(frame).set({
id: id,
name: id,
cls: 'x-hidden',
src: Ext.SSL_SECURE_URL
});
doc.body.appendChild(frame);
// This is required so that IE doesn't pop the response up in a new window.
if(Ext.isIE){
document.frames[id].name = id;
}
Ext.fly(form).set({
target: id,
method: POST,
enctype: encoding,
encoding: encoding,
action: url || buf.action
});
// add dynamic params
Ext.iterate(Ext.urlDecode(ps, false), function(k, v){
hd = doc.createElement('input');
Ext.fly(hd).set({
type: 'hidden',
value: v,
name: k
});
form.appendChild(hd);
hiddens.push(hd);
});
function cb(){
var me = this,
// bogus response object
r = {responseText : '',
responseXML : null,
argument : o.argument},
doc,
firstChild;
try{
doc = frame.contentWindow.document || frame.contentDocument || WINDOW.frames[id].document;
if(doc){
if(doc.body){
if(/textarea/i.test((firstChild = doc.body.firstChild || {}).tagName)){ // json response wrapped in textarea
r.responseText = firstChild.value;
}else{
r.responseText = doc.body.innerHTML;
}
}
//in IE the document may still have a body even if returns XML.
r.responseXML = doc.XMLDocument || doc;
}
}
catch(e) {}
Ext.EventManager.removeListener(frame, LOAD, cb, me);
me.fireEvent(REQUESTCOMPLETE, me, r, o);
function runCallback(fn, scope, args){
if(Ext.isFunction(fn)){
fn.apply(scope, args);
}
}
runCallback(o.success, o.scope, [r, o]);
runCallback(o.callback, o.scope, [o, true, r]);
if(!me.debugUploads){
setTimeout(function(){Ext.removeNode(frame);}, 100);
}
}
Ext.EventManager.on(frame, LOAD, cb, this);
form.submit();
Ext.fly(form).set(buf);
Ext.each(hiddens, function(h) {
Ext.removeNode(h);
});
}
});
})();
/**
* @class Ext.Ajax
* @extends Ext.data.Connection
* The global Ajax request class that provides a simple way to make Ajax requests
* with maximum flexibility.
* Since Ext.Ajax is a singleton, you can set common properties/events for it once
* and override them at the request function level only if necessary.
* Common Properties you may want to set are:
* {@link #method}
* {@link #extraParams}
* {@link #url}
*
*
// Default headers to pass in every request
Ext.Ajax.defaultHeaders = {
'Powered-By': 'Ext'
};
*
*
* Common Events you may want to set are:
* {@link Ext.data.Connection#beforerequest beforerequest}
* {@link Ext.data.Connection#requestcomplete requestcomplete}
* {@link Ext.data.Connection#requestexception requestexception}
*
*
// Example: show a spinner during all Ajax requests
Ext.Ajax.on('beforerequest', this.showSpinner, this);
Ext.Ajax.on('requestcomplete', this.hideSpinner, this);
Ext.Ajax.on('requestexception', this.hideSpinner, this);
*
*
* An example request:
*
// Basic request
Ext.Ajax.{@link Ext.data.Connection#request request}({
url: 'foo.php',
success: someFn,
failure: otherFn,
headers: {
'my-header': 'foo'
},
params: { foo: 'bar' }
});
// Simple ajax form submission
Ext.Ajax.{@link Ext.data.Connection#request request}({
form: 'some-form',
params: 'foo=bar'
});
*
*
* @singleton
*/
Ext.Ajax = new Ext.data.Connection({
/**
* @cfg {String} url @hide
*/
/**
* @cfg {Object} extraParams @hide
*/
/**
* @cfg {Object} defaultHeaders @hide
*/
/**
* @cfg {String} method (Optional) @hide
*/
/**
* @cfg {Number} timeout (Optional) @hide
*/
/**
* @cfg {Boolean} autoAbort (Optional) @hide
*/
/**
* @cfg {Boolean} disableCaching (Optional) @hide
*/
/**
* @property disableCaching
* True to add a unique cache-buster param to GET requests. (defaults to true)
* @type Boolean
*/
/**
* @property url
* The default URL to be used for requests to the server. (defaults to undefined)
* If the server receives all requests through one URL, setting this once is easier than
* entering it on every request.
* @type String
*/
/**
* @property extraParams
* An object containing properties which are used as extra parameters to each request made
* by this object (defaults to undefined). Session information and other data that you need
* to pass with each request are commonly put here.
* @type Object
*/
/**
* @property defaultHeaders
* An object containing request headers which are added to each request made by this object
* (defaults to undefined).
* @type Object
*/
/**
* @property method
* The default HTTP method to be used for requests. Note that this is case-sensitive and
* should be all caps (defaults to undefined; if not set but params are present will use
* "POST" , otherwise will use "GET" .)
* @type String
*/
/**
* @property timeout
* The timeout in milliseconds to be used for requests. (defaults to 30000)
* @type Number
*/
/**
* @property autoAbort
* Whether a new request should abort any pending requests. (defaults to false)
* @type Boolean
*/
autoAbort : false,
/**
* Serialize the passed form into a url encoded string
* @param {String/HTMLElement} form
* @return {String}
*/
serializeForm : function(form){
return Ext.lib.Ajax.serializeForm(form);
}
});
/**
* @class Ext.util.JSON
* Modified version of Douglas Crockford"s json.js that doesn"t
* mess with the Object prototype
* http://www.json.org/js.html
* @singleton
*/
Ext.util.JSON = new (function(){
var useHasOwn = !!{}.hasOwnProperty,
isNative = function() {
var useNative = null;
return function() {
if (useNative === null) {
useNative = Ext.USE_NATIVE_JSON && window.JSON && JSON.toString() == '[object JSON]';
}
return useNative;
};
}(),
pad = function(n) {
return n < 10 ? "0" + n : n;
},
doDecode = function(json){
return json ? eval("(" + json + ")") : "";
},
doEncode = function(o){
if(!Ext.isDefined(o) || o === null){
return "null";
}else if(Ext.isArray(o)){
return encodeArray(o);
}else if(Ext.isDate(o)){
return Ext.util.JSON.encodeDate(o);
}else if(Ext.isString(o)){
return encodeString(o);
}else if(typeof o == "number"){
//don't use isNumber here, since finite checks happen inside isNumber
return isFinite(o) ? String(o) : "null";
}else if(Ext.isBoolean(o)){
return String(o);
}else {
var a = ["{"], b, i, v;
for (i in o) {
// don't encode DOM objects
if(!o.getElementsByTagName){
if(!useHasOwn || o.hasOwnProperty(i)) {
v = o[i];
switch (typeof v) {
case "undefined":
case "function":
case "unknown":
break;
default:
if(b){
a.push(',');
}
a.push(doEncode(i), ":",
v === null ? "null" : doEncode(v));
b = true;
}
}
}
}
a.push("}");
return a.join("");
}
},
m = {
"\b": '\\b',
"\t": '\\t',
"\n": '\\n',
"\f": '\\f',
"\r": '\\r',
'"' : '\\"',
"\\": '\\\\'
},
encodeString = function(s){
if (/["\\\x00-\x1f]/.test(s)) {
return '"' + s.replace(/([\x00-\x1f\\"])/g, function(a, b) {
var c = m[b];
if(c){
return c;
}
c = b.charCodeAt();
return "\\u00" +
Math.floor(c / 16).toString(16) +
(c % 16).toString(16);
}) + '"';
}
return '"' + s + '"';
},
encodeArray = function(o){
var a = ["["], b, i, l = o.length, v;
for (i = 0; i < l; i += 1) {
v = o[i];
switch (typeof v) {
case "undefined":
case "function":
case "unknown":
break;
default:
if (b) {
a.push(',');
}
a.push(v === null ? "null" : Ext.util.JSON.encode(v));
b = true;
}
}
a.push("]");
return a.join("");
};
/**
* Encodes a Date. This returns the actual string which is inserted into the JSON string as the literal expression.
* The returned value includes enclosing double quotation marks.
* The default return format is "yyyy-mm-ddThh:mm:ss".
* To override this:
Ext.util.JSON.encodeDate = function(d) {
return d.format('"Y-m-d"');
};
* @param {Date} d The Date to encode
* @return {String} The string literal to use in a JSON string.
*/
this.encodeDate = function(o){
return '"' + o.getFullYear() + "-" +
pad(o.getMonth() + 1) + "-" +
pad(o.getDate()) + "T" +
pad(o.getHours()) + ":" +
pad(o.getMinutes()) + ":" +
pad(o.getSeconds()) + '"';
};
/**
* Encodes an Object, Array or other value
* @param {Mixed} o The variable to encode
* @return {String} The JSON string
*/
this.encode = function() {
var ec;
return function(o) {
if (!ec) {
// setup encoding function on first access
ec = isNative() ? JSON.stringify : doEncode;
}
return ec(o);
};
}();
/**
* Decodes (parses) a JSON string to an object. If the JSON is invalid, this function throws a SyntaxError unless the safe option is set.
* @param {String} json The JSON string
* @return {Object} The resulting object
*/
this.decode = function() {
var dc;
return function(json) {
if (!dc) {
// setup decoding function on first access
dc = isNative() ? JSON.parse : doDecode;
}
return dc(json);
};
}();
})();
/**
* Shorthand for {@link Ext.util.JSON#encode}
* @param {Mixed} o The variable to encode
* @return {String} The JSON string
* @member Ext
* @method encode
*/
Ext.encode = Ext.util.JSON.encode;
/**
* Shorthand for {@link Ext.util.JSON#decode}
* @param {String} json The JSON string
* @param {Boolean} safe (optional) Whether to return null or throw an exception if the JSON is invalid.
* @return {Object} The resulting object
* @member Ext
* @method decode
*/
Ext.decode = Ext.util.JSON.decode;
/**
* @class Ext.EventManager
* Registers event handlers that want to receive a normalized EventObject instead of the standard browser event and provides
* several useful events directly.
* See {@link Ext.EventObject} for more details on normalized event objects.
* @singleton
*/
Ext.EventManager = function(){
var docReadyEvent,
docReadyProcId,
docReadyState = false,
DETECT_NATIVE = Ext.isGecko || Ext.isWebKit || Ext.isSafari || Ext.isIE10p,
E = Ext.lib.Event,
D = Ext.lib.Dom,
DOC = document,
WINDOW = window,
DOMCONTENTLOADED = "DOMContentLoaded",
COMPLETE = 'complete',
propRe = /^(?:scope|delay|buffer|single|stopEvent|preventDefault|stopPropagation|normalized|args|delegate)$/,
/*
* This cache is used to hold special js objects, the document and window, that don't have an id. We need to keep
* a reference to them so we can look them up at a later point.
*/
specialElCache = [];
function getId(el){
var id = false,
i = 0,
len = specialElCache.length,
skip = false,
o;
if (el) {
if (el.getElementById || el.navigator) {
// look up the id
for(; i < len; ++i){
o = specialElCache[i];
if(o.el === el){
id = o.id;
break;
}
}
if(!id){
// for browsers that support it, ensure that give the el the same id
id = Ext.id(el);
specialElCache.push({
id: id,
el: el
});
skip = true;
}
}else{
id = Ext.id(el);
}
if(!Ext.elCache[id]){
Ext.Element.addToCache(new Ext.Element(el), id);
if(skip){
Ext.elCache[id].skipGC = true;
}
}
}
return id;
}
/// There is some jquery work around stuff here that isn't needed in Ext Core.
function addListener(el, ename, fn, task, wrap, scope){
el = Ext.getDom(el);
var id = getId(el),
es = Ext.elCache[id].events,
wfn;
wfn = E.on(el, ename, wrap);
es[ename] = es[ename] || [];
/* 0 = Original Function,
1 = Event Manager Wrapped Function,
2 = Scope,
3 = Adapter Wrapped Function,
4 = Buffered Task
*/
es[ename].push([fn, wrap, scope, wfn, task]);
// this is a workaround for jQuery and should somehow be removed from Ext Core in the future
// without breaking ExtJS.
// workaround for jQuery
if(el.addEventListener && ename == "mousewheel"){
var args = ["DOMMouseScroll", wrap, false];
el.addEventListener.apply(el, args);
Ext.EventManager.addListener(WINDOW, 'unload', function(){
el.removeEventListener.apply(el, args);
});
}
// fix stopped mousedowns on the document
if(el == DOC && ename == "mousedown"){
Ext.EventManager.stoppedMouseDownEvent.addListener(wrap);
}
}
function doScrollChk(){
/* Notes:
'doScroll' will NOT work in a IFRAME/FRAMESET.
The method succeeds but, a DOM query done immediately after -- FAILS.
*/
if(window != top){
return false;
}
try{
DOC.documentElement.doScroll('left');
}catch(e){
return false;
}
fireDocReady();
return true;
}
/**
* @return {Boolean} True if the document is in a 'complete' state (or was determined to
* be true by other means). If false, the state is evaluated again until canceled.
*/
function checkReadyState(e){
if(Ext.isIE9m && doScrollChk()){
return true;
}
if(DOC.readyState == COMPLETE){
fireDocReady();
return true;
}
docReadyState || (docReadyProcId = setTimeout(arguments.callee, 2));
return false;
}
var styles;
function checkStyleSheets(e){
styles || (styles = Ext.query('style, link[rel=stylesheet]'));
if(styles.length == DOC.styleSheets.length){
fireDocReady();
return true;
}
docReadyState || (docReadyProcId = setTimeout(arguments.callee, 2));
return false;
}
function OperaDOMContentLoaded(e){
DOC.removeEventListener(DOMCONTENTLOADED, arguments.callee, false);
checkStyleSheets();
}
function fireDocReady(e){
if(!docReadyState){
docReadyState = true; //only attempt listener removal once
if(docReadyProcId){
clearTimeout(docReadyProcId);
}
if(DETECT_NATIVE) {
DOC.removeEventListener(DOMCONTENTLOADED, fireDocReady, false);
}
if(Ext.isIE9m && checkReadyState.bindIE){ //was this was actually set ??
DOC.detachEvent('onreadystatechange', checkReadyState);
}
E.un(WINDOW, "load", arguments.callee);
}
if(docReadyEvent && !Ext.isReady){
Ext.isReady = true;
docReadyEvent.fire();
docReadyEvent.listeners = [];
}
}
function initDocReady(){
docReadyEvent || (docReadyEvent = new Ext.util.Event());
if (DETECT_NATIVE) {
DOC.addEventListener(DOMCONTENTLOADED, fireDocReady, false);
}
/*
* Handle additional (exceptional) detection strategies here
*/
if (Ext.isIE9m){
//Use readystatechange as a backup AND primary detection mechanism for a FRAME/IFRAME
//See if page is already loaded
if(!checkReadyState()){
checkReadyState.bindIE = true;
DOC.attachEvent('onreadystatechange', checkReadyState);
}
}else if(Ext.isOpera ){
/* Notes:
Opera needs special treatment needed here because CSS rules are NOT QUITE
available after DOMContentLoaded is raised.
*/
//See if page is already loaded and all styleSheets are in place
(DOC.readyState == COMPLETE && checkStyleSheets()) ||
DOC.addEventListener(DOMCONTENTLOADED, OperaDOMContentLoaded, false);
}else if (Ext.isWebKit){
//Fallback for older Webkits without DOMCONTENTLOADED support
checkReadyState();
}
// no matter what, make sure it fires on load
E.on(WINDOW, "load", fireDocReady);
}
function createTargeted(h, o){
return function(){
var args = Ext.toArray(arguments);
if(o.target == Ext.EventObject.setEvent(args[0]).target){
h.apply(this, args);
}
};
}
function createBuffered(h, o, task){
return function(e){
// create new event object impl so new events don't wipe out properties
task.delay(o.buffer, h, null, [new Ext.EventObjectImpl(e)]);
};
}
function createSingle(h, el, ename, fn, scope){
return function(e){
Ext.EventManager.removeListener(el, ename, fn, scope);
h(e);
};
}
function createDelayed(h, o, fn){
return function(e){
var task = new Ext.util.DelayedTask(h);
if(!fn.tasks) {
fn.tasks = [];
}
fn.tasks.push(task);
task.delay(o.delay || 10, h, null, [new Ext.EventObjectImpl(e)]);
};
}
function listen(element, ename, opt, fn, scope){
var o = (!opt || typeof opt == "boolean") ? {} : opt,
el = Ext.getDom(element), task;
fn = fn || o.fn;
scope = scope || o.scope;
if(!el){
throw "Error listening for \"" + ename + '\". Element "' + element + '" doesn\'t exist.';
}
function h(e){
// prevent errors while unload occurring
if(!Ext){// !window[xname]){ ==> can't we do this?
return;
}
e = Ext.EventObject.setEvent(e);
var t;
if (o.delegate) {
if(!(t = e.getTarget(o.delegate, el))){
return;
}
} else {
t = e.target;
}
if (o.stopEvent) {
e.stopEvent();
}
if (o.preventDefault) {
e.preventDefault();
}
if (o.stopPropagation) {
e.stopPropagation();
}
if (o.normalized === false) {
e = e.browserEvent;
}
fn.call(scope || el, e, t, o);
}
if(o.target){
h = createTargeted(h, o);
}
if(o.delay){
h = createDelayed(h, o, fn);
}
if(o.single){
h = createSingle(h, el, ename, fn, scope);
}
if(o.buffer){
task = new Ext.util.DelayedTask(h);
h = createBuffered(h, o, task);
}
addListener(el, ename, fn, task, h, scope);
return h;
}
var pub = {
/**
* Appends an event handler to an element. The shorthand version {@link #on} is equivalent. Typically you will
* use {@link Ext.Element#addListener} directly on an Element in favor of calling this version.
* @param {String/HTMLElement} el The html element or id to assign the event handler to.
* @param {String} eventName The name of the event to listen for.
* @param {Function} handler The handler function the event invokes. This function is passed
* the following parameters:
* evt : EventObjectThe {@link Ext.EventObject EventObject} describing the event.
* t : ElementThe {@link Ext.Element Element} which was the target of the event.
* Note that this may be filtered by using the delegate option.
* o : ObjectThe options object from the addListener call.
*
* @param {Object} scope (optional) The scope (this reference) in which the handler function is executed. Defaults to the Element .
* @param {Object} options (optional) An object containing handler configuration properties.
* This may contain any of the following properties:
* scope : ObjectThe scope (this reference) in which the handler function is executed. Defaults to the Element .
* delegate : StringA simple selector to filter the target or look for a descendant of the target
* stopEvent : BooleanTrue to stop the event. That is stop propagation, and prevent the default action.
* preventDefault : BooleanTrue to prevent the default action
* stopPropagation : BooleanTrue to prevent event propagation
* normalized : BooleanFalse to pass a browser event to the handler function instead of an Ext.EventObject
* delay : NumberThe number of milliseconds to delay the invocation of the handler after te event fires.
* single : BooleanTrue to add a handler to handle just the next firing of the event, and then remove itself.
* buffer : NumberCauses the handler to be scheduled to run in an {@link Ext.util.DelayedTask} delayed
* by the specified number of milliseconds. If the event fires again within that time, the original
* handler is not invoked, but the new handler is scheduled in its place.
* target : ElementOnly call the handler if the event was fired on the target Element, not if the event was bubbled up from a child node.
*
* See {@link Ext.Element#addListener} for examples of how to use these options.
*/
addListener : function(element, eventName, fn, scope, options){
if(typeof eventName == 'object'){
var o = eventName, e, val;
for(e in o){
val = o[e];
if(!propRe.test(e)){
if(Ext.isFunction(val)){
// shared options
listen(element, e, o, val, o.scope);
}else{
// individual options
listen(element, e, val);
}
}
}
} else {
listen(element, eventName, options, fn, scope);
}
},
/**
* Removes an event handler from an element. The shorthand version {@link #un} is equivalent. Typically
* you will use {@link Ext.Element#removeListener} directly on an Element in favor of calling this version.
* @param {String/HTMLElement} el The id or html element from which to remove the listener.
* @param {String} eventName The name of the event.
* @param {Function} fn The handler function to remove. This must be a reference to the function passed into the {@link #addListener} call.
* @param {Object} scope If a scope (this reference) was specified when the listener was added,
* then this must refer to the same object.
*/
removeListener : function(el, eventName, fn, scope){
el = Ext.getDom(el);
var id = getId(el),
f = el && (Ext.elCache[id].events)[eventName] || [],
wrap, i, l, k, len, fnc;
for (i = 0, len = f.length; i < len; i++) {
/* 0 = Original Function,
1 = Event Manager Wrapped Function,
2 = Scope,
3 = Adapter Wrapped Function,
4 = Buffered Task
*/
if (Ext.isArray(fnc = f[i]) && fnc[0] == fn && (!scope || fnc[2] == scope)) {
if(fnc[4]) {
fnc[4].cancel();
}
k = fn.tasks && fn.tasks.length;
if(k) {
while(k--) {
fn.tasks[k].cancel();
}
delete fn.tasks;
}
wrap = fnc[1];
E.un(el, eventName, E.extAdapter ? fnc[3] : wrap);
// jQuery workaround that should be removed from Ext Core
if(wrap && el.addEventListener && eventName == "mousewheel"){
el.removeEventListener("DOMMouseScroll", wrap, false);
}
// fix stopped mousedowns on the document
if(wrap && el == DOC && eventName == "mousedown"){
Ext.EventManager.stoppedMouseDownEvent.removeListener(wrap);
}
f.splice(i, 1);
if (f.length === 0) {
delete Ext.elCache[id].events[eventName];
}
for (k in Ext.elCache[id].events) {
return false;
}
Ext.elCache[id].events = {};
return false;
}
}
},
/**
* Removes all event handers from an element. Typically you will use {@link Ext.Element#removeAllListeners}
* directly on an Element in favor of calling this version.
* @param {String/HTMLElement} el The id or html element from which to remove all event handlers.
*/
removeAll : function(el){
el = Ext.getDom(el);
var id = getId(el),
ec = Ext.elCache[id] || {},
es = ec.events || {},
f, i, len, ename, fn, k, wrap;
for(ename in es){
if(es.hasOwnProperty(ename)){
f = es[ename];
/* 0 = Original Function,
1 = Event Manager Wrapped Function,
2 = Scope,
3 = Adapter Wrapped Function,
4 = Buffered Task
*/
for (i = 0, len = f.length; i < len; i++) {
fn = f[i];
if(fn[4]) {
fn[4].cancel();
}
if(fn[0].tasks && (k = fn[0].tasks.length)) {
while(k--) {
fn[0].tasks[k].cancel();
}
delete fn.tasks;
}
wrap = fn[1];
E.un(el, ename, E.extAdapter ? fn[3] : wrap);
// jQuery workaround that should be removed from Ext Core
if(el.addEventListener && wrap && ename == "mousewheel"){
el.removeEventListener("DOMMouseScroll", wrap, false);
}
// fix stopped mousedowns on the document
if(wrap && el == DOC && ename == "mousedown"){
Ext.EventManager.stoppedMouseDownEvent.removeListener(wrap);
}
}
}
}
if (Ext.elCache[id]) {
Ext.elCache[id].events = {};
}
},
getListeners : function(el, eventName) {
el = Ext.getDom(el);
var id = getId(el),
ec = Ext.elCache[id] || {},
es = ec.events || {},
results = [];
if (es && es[eventName]) {
return es[eventName];
} else {
return null;
}
},
removeFromSpecialCache: function(o) {
var i = 0,
len = specialElCache.length;
for (; i < len; ++i) {
if (specialElCache[i].el == o) {
specialElCache.splice(i, 1);
}
}
},
purgeElement : function(el, recurse, eventName) {
el = Ext.getDom(el);
var id = getId(el),
ec = Ext.elCache[id] || {},
es = ec.events || {},
i, f, len;
if (eventName) {
if (es && es.hasOwnProperty(eventName)) {
f = es[eventName];
for (i = 0, len = f.length; i < len; i++) {
Ext.EventManager.removeListener(el, eventName, f[i][0]);
}
}
} else {
Ext.EventManager.removeAll(el);
}
if (recurse && el && el.childNodes) {
for (i = 0, len = el.childNodes.length; i < len; i++) {
Ext.EventManager.purgeElement(el.childNodes[i], recurse, eventName);
}
}
},
_unload : function() {
var el;
for (el in Ext.elCache) {
Ext.EventManager.removeAll(el);
}
delete Ext.elCache;
delete Ext.Element._flyweights;
// Abort any outstanding Ajax requests
var c,
conn,
tid,
ajax = Ext.lib.Ajax;
(typeof ajax.conn == 'object') ? conn = ajax.conn : conn = {};
for (tid in conn) {
c = conn[tid];
if (c) {
ajax.abort({conn: c, tId: tid});
}
}
},
/**
* Adds a listener to be notified when the document is ready (before onload and before images are loaded). Can be
* accessed shorthanded as Ext.onReady().
* @param {Function} fn The method the event invokes.
* @param {Object} scope (optional) The scope (this reference) in which the handler function executes. Defaults to the browser window.
* @param {boolean} options (optional) Options object as passed to {@link Ext.Element#addListener}. It is recommended that the options
* {single: true} be used so that the handler is removed on first invocation.
*/
onDocumentReady : function(fn, scope, options){
if (Ext.isReady) { // if it already fired or document.body is present
docReadyEvent || (docReadyEvent = new Ext.util.Event());
docReadyEvent.addListener(fn, scope, options);
docReadyEvent.fire();
docReadyEvent.listeners = [];
} else {
if (!docReadyEvent) {
initDocReady();
}
options = options || {};
options.delay = options.delay || 1;
docReadyEvent.addListener(fn, scope, options);
}
},
/**
* Forces a document ready state transition for the framework. Used when Ext is loaded
* into a DOM structure AFTER initial page load (Google API or other dynamic load scenario.
* Any pending 'onDocumentReady' handlers will be fired (if not already handled).
*/
fireDocReady : fireDocReady
};
/**
* Appends an event handler to an element. Shorthand for {@link #addListener}.
* @param {String/HTMLElement} el The html element or id to assign the event handler to
* @param {String} eventName The name of the event to listen for.
* @param {Function} handler The handler function the event invokes.
* @param {Object} scope (optional) (this reference) in which the handler function executes. Defaults to the Element .
* @param {Object} options (optional) An object containing standard {@link #addListener} options
* @member Ext.EventManager
* @method on
*/
pub.on = pub.addListener;
/**
* Removes an event handler from an element. Shorthand for {@link #removeListener}.
* @param {String/HTMLElement} el The id or html element from which to remove the listener.
* @param {String} eventName The name of the event.
* @param {Function} fn The handler function to remove. This must be a reference to the function passed into the {@link #on} call.
* @param {Object} scope If a scope (this reference) was specified when the listener was added,
* then this must refer to the same object.
* @member Ext.EventManager
* @method un
*/
pub.un = pub.removeListener;
pub.stoppedMouseDownEvent = new Ext.util.Event();
return pub;
}();
/**
* Adds a listener to be notified when the document is ready (before onload and before images are loaded). Shorthand of {@link Ext.EventManager#onDocumentReady}.
* @param {Function} fn The method the event invokes.
* @param {Object} scope (optional) The scope (this reference) in which the handler function executes. Defaults to the browser window.
* @param {boolean} options (optional) Options object as passed to {@link Ext.Element#addListener}. It is recommended that the options
* {single: true} be used so that the handler is removed on first invocation.
* @member Ext
* @method onReady
*/
Ext.onReady = Ext.EventManager.onDocumentReady;
//Initialize doc classes
(function(){
var initExtCss = function() {
// find the body element
var bd = document.body || document.getElementsByTagName('body')[0];
if (!bd) {
return false;
}
var cls = [];
if (Ext.isIE) {
// Only treat IE9 and less like IE in the css
if (!Ext.isIE10p) {
cls.push('ext-ie');
}
if (Ext.isIE6) {
cls.push('ext-ie6');
} else if (Ext.isIE7) {
cls.push('ext-ie7', 'ext-ie7m');
} else if (Ext.isIE8) {
cls.push('ext-ie8', 'ext-ie8m');
} else if (Ext.isIE9) {
cls.push('ext-ie9', 'ext-ie9m');
} else if (Ext.isIE10) {
cls.push('ext-ie10');
}
}
if (Ext.isGecko) {
if (Ext.isGecko2) {
cls.push('ext-gecko2');
} else {
cls.push('ext-gecko3');
}
}
if (Ext.isOpera) {
cls.push('ext-opera');
}
if (Ext.isWebKit) {
cls.push('ext-webkit');
}
if (Ext.isSafari) {
cls.push("ext-safari " + (Ext.isSafari2 ? 'ext-safari2' : (Ext.isSafari3 ? 'ext-safari3' : 'ext-safari4')));
} else if(Ext.isChrome) {
cls.push("ext-chrome");
}
if (Ext.isMac) {
cls.push("ext-mac");
}
if (Ext.isLinux) {
cls.push("ext-linux");
}
// add to the parent to allow for selectors like ".ext-strict .ext-ie"
if (Ext.isStrict || Ext.isBorderBox) {
var p = bd.parentNode;
if (p) {
if (!Ext.isStrict) {
Ext.fly(p, '_internal').addClass('x-quirks');
if (Ext.isIE9m && !Ext.isStrict) {
Ext.isIEQuirks = true;
}
}
Ext.fly(p, '_internal').addClass(((Ext.isStrict && Ext.isIE ) || (!Ext.enableForcedBoxModel && !Ext.isIE)) ? ' ext-strict' : ' ext-border-box');
}
}
// Forced border box model class applied to all elements. Bypassing javascript based box model adjustments
// in favor of css. This is for non-IE browsers.
if (Ext.enableForcedBoxModel && !Ext.isIE) {
Ext.isForcedBorderBox = true;
cls.push("ext-forced-border-box");
}
Ext.fly(bd, '_internal').addClass(cls);
return true;
};
if (!initExtCss()) {
Ext.onReady(initExtCss);
}
})();
// Code used to detect certain browser feature/quirks/bugs at startup.
(function(){
/**
* @class Ext.supports
* @ignore
*/
var supports = Ext.apply(Ext.supports, {
/**
* In Webkit, there is an issue with getting the margin right property, see
* https://bugs.webkit.org/show_bug.cgi?id=13343
*/
correctRightMargin: true,
/**
* Webkit browsers return rgba(0, 0, 0) when a transparent color is used
*/
correctTransparentColor: true,
/**
* IE uses styleFloat, not cssFloat for the float property.
*/
cssFloat: true
});
var supportTests = function(){
var div = document.createElement('div'),
doc = document,
view,
last;
div.innerHTML = '';
doc.body.appendChild(div);
last = div.lastChild;
if((view = doc.defaultView)){
if(view.getComputedStyle(div.firstChild.firstChild, null).marginRight != '0px'){
supports.correctRightMargin = false;
}
if(view.getComputedStyle(last, null).backgroundColor != 'transparent'){
supports.correctTransparentColor = false;
}
}
supports.cssFloat = !!last.style.cssFloat;
doc.body.removeChild(div);
};
if (Ext.isReady) {
supportTests();
} else {
Ext.onReady(supportTests);
}
})();
/**
* @class Ext.EventObject
* Just as {@link Ext.Element} wraps around a native DOM node, Ext.EventObject
* wraps the browser's native event-object normalizing cross-browser differences,
* such as which mouse button is clicked, keys pressed, mechanisms to stop
* event-propagation along with a method to prevent default actions from taking place.
*
For example:
*
function handleClick(e, t){ // e is not a standard event object, it is a Ext.EventObject
e.preventDefault();
var target = e.getTarget(); // same as t (the target HTMLElement)
...
}
var myDiv = {@link Ext#get Ext.get}("myDiv"); // get reference to an {@link Ext.Element}
myDiv.on( // 'on' is shorthand for addListener
"click", // perform an action on click of myDiv
handleClick // reference to the action handler
);
// other methods to do the same:
Ext.EventManager.on("myDiv", 'click', handleClick);
Ext.EventManager.addListener("myDiv", 'click', handleClick);
* @singleton
*/
Ext.EventObject = function(){
var E = Ext.lib.Event,
clickRe = /(dbl)?click/,
// safari keypress events for special keys return bad keycodes
safariKeys = {
3 : 13, // enter
63234 : 37, // left
63235 : 39, // right
63232 : 38, // up
63233 : 40, // down
63276 : 33, // page up
63277 : 34, // page down
63272 : 46, // delete
63273 : 36, // home
63275 : 35 // end
},
// normalize button clicks
btnMap = Ext.isIE ? {1:0,4:1,2:2} : {0:0,1:1,2:2};
Ext.EventObjectImpl = function(e){
if(e){
this.setEvent(e.browserEvent || e);
}
};
Ext.EventObjectImpl.prototype = {
/** @private */
setEvent : function(e){
var me = this;
if(e == me || (e && e.browserEvent)){ // already wrapped
return e;
}
me.browserEvent = e;
if(e){
// normalize buttons
me.button = e.button ? btnMap[e.button] : (e.which ? e.which - 1 : -1);
if(clickRe.test(e.type) && me.button == -1){
me.button = 0;
}
me.type = e.type;
me.shiftKey = e.shiftKey;
// mac metaKey behaves like ctrlKey
me.ctrlKey = e.ctrlKey || e.metaKey || false;
me.altKey = e.altKey;
// in getKey these will be normalized for the mac
me.keyCode = e.keyCode;
me.charCode = e.charCode;
// cache the target for the delayed and or buffered events
me.target = E.getTarget(e);
// same for XY
me.xy = E.getXY(e);
}else{
me.button = -1;
me.shiftKey = false;
me.ctrlKey = false;
me.altKey = false;
me.keyCode = 0;
me.charCode = 0;
me.target = null;
me.xy = [0, 0];
}
return me;
},
/**
* Stop the event (preventDefault and stopPropagation)
*/
stopEvent : function(){
var me = this;
if(me.browserEvent){
if(me.browserEvent.type == 'mousedown'){
Ext.EventManager.stoppedMouseDownEvent.fire(me);
}
E.stopEvent(me.browserEvent);
}
},
/**
* Prevents the browsers default handling of the event.
*/
preventDefault : function(){
if(this.browserEvent){
E.preventDefault(this.browserEvent);
}
},
/**
* Cancels bubbling of the event.
*/
stopPropagation : function(){
var me = this;
if(me.browserEvent){
if(me.browserEvent.type == 'mousedown'){
Ext.EventManager.stoppedMouseDownEvent.fire(me);
}
E.stopPropagation(me.browserEvent);
}
},
/**
* Gets the character code for the event.
* @return {Number}
*/
getCharCode : function(){
return this.charCode || this.keyCode;
},
/**
* Returns a normalized keyCode for the event.
* @return {Number} The key code
*/
getKey : function(){
return this.normalizeKey(this.keyCode || this.charCode);
},
// private
normalizeKey: function(k){
return Ext.isSafari ? (safariKeys[k] || k) : k;
},
/**
* Gets the x coordinate of the event.
* @return {Number}
*/
getPageX : function(){
return this.xy[0];
},
/**
* Gets the y coordinate of the event.
* @return {Number}
*/
getPageY : function(){
return this.xy[1];
},
/**
* Gets the page coordinates of the event.
* @return {Array} The xy values like [x, y]
*/
getXY : function(){
return this.xy;
},
/**
* Gets the target for the event.
* @param {String} selector (optional) A simple selector to filter the target or look for an ancestor of the target
* @param {Number/Mixed} maxDepth (optional) The max depth to
search as a number or element (defaults to 10 || document.body)
* @param {Boolean} returnEl (optional) True to return a Ext.Element object instead of DOM node
* @return {HTMLelement}
*/
getTarget : function(selector, maxDepth, returnEl){
return selector ? Ext.fly(this.target).findParent(selector, maxDepth, returnEl) : (returnEl ? Ext.get(this.target) : this.target);
},
/**
* Gets the related target.
* @return {HTMLElement}
*/
getRelatedTarget : function(){
return this.browserEvent ? E.getRelatedTarget(this.browserEvent) : null;
},
/**
* Normalizes mouse wheel delta across browsers
* @return {Number} The delta
*/
getWheelDelta : function(){
var e = this.browserEvent;
var delta = 0;
if(e.wheelDelta){ /* IE/Opera. */
delta = e.wheelDelta/120;
}else if(e.detail){ /* Mozilla case. */
delta = -e.detail/3;
}
return delta;
},
/**
* Returns true if the target of this event is a child of el. Unless the allowEl parameter is set, it will return false if if the target is el.
* Example usage:
// Handle click on any child of an element
Ext.getBody().on('click', function(e){
if(e.within('some-el')){
alert('Clicked on a child of some-el!');
}
});
// Handle click directly on an element, ignoring clicks on child nodes
Ext.getBody().on('click', function(e,t){
if((t.id == 'some-el') && !e.within(t, true)){
alert('Clicked directly on some-el!');
}
});
* @param {Mixed} el The id, DOM element or Ext.Element to check
* @param {Boolean} related (optional) true to test if the related target is within el instead of the target
* @param {Boolean} allowEl (optional) true to also check if the passed element is the target or related target
* @return {Boolean}
*/
within : function(el, related, allowEl){
if(el){
var t = this[related ? "getRelatedTarget" : "getTarget"]();
return t && ((allowEl ? (t == Ext.getDom(el)) : false) || Ext.fly(el).contains(t));
}
return false;
}
};
return new Ext.EventObjectImpl();
}();/**
* @class Ext.Loader
* @singleton
* Simple class to help load JavaScript files on demand
*/
Ext.Loader = Ext.apply({}, {
/**
* Loads a given set of .js files. Calls the callback function when all files have been loaded
* Set preserveOrder to true to ensure non-parallel loading of files if load order is important
* @param {Array} fileList Array of all files to load
* @param {Function} callback Callback to call after all files have been loaded
* @param {Object} scope The scope to call the callback in
* @param {Boolean} preserveOrder True to make files load in serial, one after the other (defaults to false)
*/
load: function(fileList, callback, scope, preserveOrder) {
var scope = scope || this,
head = document.getElementsByTagName("head")[0],
fragment = document.createDocumentFragment(),
numFiles = fileList.length,
loadedFiles = 0,
me = this;
/**
* Loads a particular file from the fileList by index. This is used when preserving order
*/
var loadFileIndex = function(index) {
head.appendChild(
me.buildScriptTag(fileList[index], onFileLoaded)
);
};
/**
* Callback function which is called after each file has been loaded. This calls the callback
* passed to load once the final file in the fileList has been loaded
*/
var onFileLoaded = function() {
loadedFiles ++;
//if this was the last file, call the callback, otherwise load the next file
if (numFiles == loadedFiles && typeof callback == 'function') {
callback.call(scope);
} else {
if (preserveOrder === true) {
loadFileIndex(loadedFiles);
}
}
};
if (preserveOrder === true) {
loadFileIndex.call(this, 0);
} else {
//load each file (most browsers will do this in parallel)
Ext.each(fileList, function(file, index) {
fragment.appendChild(
this.buildScriptTag(file, onFileLoaded)
);
}, this);
head.appendChild(fragment);
}
},
/**
* @private
* Creates and returns a script tag, but does not place it into the document. If a callback function
* is passed, this is called when the script has been loaded
* @param {String} filename The name of the file to create a script tag for
* @param {Function} callback Optional callback, which is called when the script has been loaded
* @return {Element} The new script ta
*/
buildScriptTag: function(filename, callback) {
var script = document.createElement('script');
script.type = "text/javascript";
script.src = filename;
//IE has a different way of handling <script> loads, so we need to check for it here
if (script.readyState) {
script.onreadystatechange = function() {
if (script.readyState == "loaded" || script.readyState == "complete") {
script.onreadystatechange = null;
callback();
}
};
} else {
script.onload = callback;
}
return script;
}
});
/**
* @class Ext
*/
Ext.ns("Ext.grid", "Ext.list", "Ext.dd", "Ext.tree", "Ext.form", "Ext.menu",
"Ext.state", "Ext.layout.boxOverflow", "Ext.app", "Ext.ux", "Ext.chart", "Ext.direct", "Ext.slider");
/**
* Namespace alloted for extensions to the framework.
* @property ux
* @type Object
*/
Ext.apply(Ext, function(){
var E = Ext,
idSeed = 0,
scrollWidth = null;
return {
/**
* A reusable empty function
* @property
* @type Function
*/
emptyFn : function(){},
/**
* URL to a 1x1 transparent gif image used by Ext to create inline icons with CSS background images.
* In older versions of IE, this defaults to "http://extjs.com/s.gif" and you should change this to a URL on your server.
* For other browsers it uses an inline data URL.
* @type String
*/
BLANK_IMAGE_URL : Ext.isIE6 || Ext.isIE7 || Ext.isAir ?
'http:/' + '/www.extjs.com/s.gif' :
'data:image/gif;base64,R0lGODlhAQABAID/AMDAwAAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==',
extendX : function(supr, fn){
return Ext.extend(supr, fn(supr.prototype));
},
/**
* Returns the current HTML document object as an {@link Ext.Element}.
* @return Ext.Element The document
*/
getDoc : function(){
return Ext.get(document);
},
/**
* Utility method for validating that a value is numeric, returning the specified default value if it is not.
* @param {Mixed} value Should be a number, but any type will be handled appropriately
* @param {Number} defaultValue The value to return if the original value is non-numeric
* @return {Number} Value, if numeric, else defaultValue
*/
num : function(v, defaultValue){
v = Number(Ext.isEmpty(v) || Ext.isArray(v) || typeof v == 'boolean' || (typeof v == 'string' && v.trim().length == 0) ? NaN : v);
return isNaN(v) ? defaultValue : v;
},
/**
*
Utility method for returning a default value if the passed value is empty.
*
The value is deemed to be empty if it is
* null
* undefined
* an empty array
* a zero length string (Unless the allowBlank parameter is true )
*
* @param {Mixed} value The value to test
* @param {Mixed} defaultValue The value to return if the original value is empty
* @param {Boolean} allowBlank (optional) true to allow zero length strings to qualify as non-empty (defaults to false)
* @return {Mixed} value, if non-empty, else defaultValue
*/
value : function(v, defaultValue, allowBlank){
return Ext.isEmpty(v, allowBlank) ? defaultValue : v;
},
/**
* Escapes the passed string for use in a regular expression
* @param {String} str
* @return {String}
*/
escapeRe : function(s) {
return s.replace(/([-.*+?^${}()|[\]\/\\])/g, "\\$1");
},
sequence : function(o, name, fn, scope){
o[name] = o[name].createSequence(fn, scope);
},
/**
* Applies event listeners to elements by selectors when the document is ready.
* The event name is specified with an
@ suffix.
*
Ext.addBehaviors({
// add a listener for click on all anchors in element with id foo
'#foo a@click' : function(e, t){
// do something
},
// add the same listener to multiple selectors (separated by comma BEFORE the @)
'#foo a, #bar span.some-class@mouseover' : function(){
// do something
}
});
*
* @param {Object} obj The list of behaviors to apply
*/
addBehaviors : function(o){
if(!Ext.isReady){
Ext.onReady(function(){
Ext.addBehaviors(o);
});
} else {
var cache = {}, // simple cache for applying multiple behaviors to same selector does query multiple times
parts,
b,
s;
for (b in o) {
if ((parts = b.split('@'))[1]) { // for Object prototype breakers
s = parts[0];
if(!cache[s]){
cache[s] = Ext.select(s);
}
cache[s].on(parts[1], o[b]);
}
}
cache = null;
}
},
/**
* Utility method for getting the width of the browser scrollbar. This can differ depending on
* operating system settings, such as the theme or font size.
* @param {Boolean} force (optional) true to force a recalculation of the value.
* @return {Number} The width of the scrollbar.
*/
getScrollBarWidth: function(force){
if(!Ext.isReady){
return 0;
}
if(force === true || scrollWidth === null){
// Append our div, do our calculation and then remove it
var div = Ext.getBody().createChild('
'),
child = div.child('div', true);
var w1 = child.offsetWidth;
div.setStyle('overflow', (Ext.isWebKit || Ext.isGecko) ? 'auto' : 'scroll');
var w2 = child.offsetWidth;
div.remove();
// Need to add 2 to ensure we leave enough space
scrollWidth = w1 - w2 + 2;
}
return scrollWidth;
},
// deprecated
combine : function(){
var as = arguments, l = as.length, r = [];
for(var i = 0; i < l; i++){
var a = as[i];
if(Ext.isArray(a)){
r = r.concat(a);
}else if(a.length !== undefined && !a.substr){
r = r.concat(Array.prototype.slice.call(a, 0));
}else{
r.push(a);
}
}
return r;
},
/**
* Copies a set of named properties fom the source object to the destination object.
*
example:
ImageComponent = Ext.extend(Ext.BoxComponent, {
initComponent: function() {
this.autoEl = { tag: 'img' };
MyComponent.superclass.initComponent.apply(this, arguments);
this.initialBox = Ext.copyTo({}, this.initialConfig, 'x,y,width,height');
}
});
*
* @param {Object} dest The destination object.
* @param {Object} source The source object.
* @param {Array/String} names Either an Array of property names, or a comma-delimited list
* of property names to copy.
* @return {Object} The modified object.
*/
copyTo : function(dest, source, names){
if(typeof names == 'string'){
names = names.split(/[,;\s]/);
}
Ext.each(names, function(name){
if(source.hasOwnProperty(name)){
dest[name] = source[name];
}
}, this);
return dest;
},
/**
* Attempts to destroy any objects passed to it by removing all event listeners, removing them from the
* DOM (if applicable) and calling their destroy functions (if available). This method is primarily
* intended for arguments of type {@link Ext.Element} and {@link Ext.Component}, but any subclass of
* {@link Ext.util.Observable} can be passed in. Any number of elements and/or components can be
* passed into this function in a single call as separate arguments.
* @param {Mixed...} args An {@link Ext.Element}, {@link Ext.Component}, or an Array of either of these to destroy
*/
destroy : function(){
Ext.each(arguments, function(arg){
if(arg){
if(Ext.isArray(arg)){
this.destroy.apply(this, arg);
}else if(typeof arg.destroy == 'function'){
arg.destroy();
}else if(arg.dom){
arg.remove();
}
}
}, this);
},
/**
* Attempts to destroy and then remove a set of named properties of the passed object.
* @param {Object} o The object (most likely a Component) who's properties you wish to destroy.
* @param {Mixed} arg1 The name of the property to destroy and remove from the object.
* @param {Mixed} etc... More property names to destroy and remove.
*/
destroyMembers : function(o, arg1, arg2, etc){
for(var i = 1, a = arguments, len = a.length; i < len; i++) {
Ext.destroy(o[a[i]]);
delete o[a[i]];
}
},
/**
* Creates a copy of the passed Array with falsy values removed.
* @param {Array/NodeList} arr The Array from which to remove falsy values.
* @return {Array} The new, compressed Array.
*/
clean : function(arr){
var ret = [];
Ext.each(arr, function(v){
if(!!v){
ret.push(v);
}
});
return ret;
},
/**
* Creates a copy of the passed Array, filtered to contain only unique values.
* @param {Array} arr The Array to filter
* @return {Array} The new Array containing unique values.
*/
unique : function(arr){
var ret = [],
collect = {};
Ext.each(arr, function(v) {
if(!collect[v]){
ret.push(v);
}
collect[v] = true;
});
return ret;
},
/**
* Recursively flattens into 1-d Array. Injects Arrays inline.
* @param {Array} arr The array to flatten
* @return {Array} The new, flattened array.
*/
flatten : function(arr){
var worker = [];
function rFlatten(a) {
Ext.each(a, function(v) {
if(Ext.isArray(v)){
rFlatten(v);
}else{
worker.push(v);
}
});
return worker;
}
return rFlatten(arr);
},
/**
* Returns the minimum value in the Array.
* @param {Array|NodeList} arr The Array from which to select the minimum value.
* @param {Function} comp (optional) a function to perform the comparision which determines minimization.
* If omitted the "<" operator will be used. Note: gt = 1; eq = 0; lt = -1
* @return {Object} The minimum value in the Array.
*/
min : function(arr, comp){
var ret = arr[0];
comp = comp || function(a,b){ return a < b ? -1 : 1; };
Ext.each(arr, function(v) {
ret = comp(ret, v) == -1 ? ret : v;
});
return ret;
},
/**
* Returns the maximum value in the Array
* @param {Array|NodeList} arr The Array from which to select the maximum value.
* @param {Function} comp (optional) a function to perform the comparision which determines maximization.
* If omitted the ">" operator will be used. Note: gt = 1; eq = 0; lt = -1
* @return {Object} The maximum value in the Array.
*/
max : function(arr, comp){
var ret = arr[0];
comp = comp || function(a,b){ return a > b ? 1 : -1; };
Ext.each(arr, function(v) {
ret = comp(ret, v) == 1 ? ret : v;
});
return ret;
},
/**
* Calculates the mean of the Array
* @param {Array} arr The Array to calculate the mean value of.
* @return {Number} The mean.
*/
mean : function(arr){
return arr.length > 0 ? Ext.sum(arr) / arr.length : undefined;
},
/**
* Calculates the sum of the Array
* @param {Array} arr The Array to calculate the sum value of.
* @return {Number} The sum.
*/
sum : function(arr){
var ret = 0;
Ext.each(arr, function(v) {
ret += v;
});
return ret;
},
/**
* Partitions the set into two sets: a true set and a false set.
* Example:
* Example2:
*
// Example 1:
Ext.partition([true, false, true, true, false]); // [[true, true, true], [false, false]]
// Example 2:
Ext.partition(
Ext.query("p"),
function(val){
return val.className == "class1"
}
);
// true are those paragraph elements with a className of "class1",
// false set are those that do not have that className.
*
* @param {Array|NodeList} arr The array to partition
* @param {Function} truth (optional) a function to determine truth. If this is omitted the element
* itself must be able to be evaluated for its truthfulness.
* @return {Array} [true
,false]
*/
partition : function(arr, truth){
var ret = [[],[]];
Ext.each(arr, function(v, i, a) {
ret[ (truth && truth(v, i, a)) || (!truth && v) ? 0 : 1].push(v);
});
return ret;
},
/**
* Invokes a method on each item in an Array.
*
// Example:
Ext.invoke(Ext.query("p"), "getAttribute", "id");
// [el1.getAttribute("id"), el2.getAttribute("id"), ..., elN.getAttribute("id")]
*
* @param {Array|NodeList} arr The Array of items to invoke the method on.
* @param {String} methodName The method name to invoke.
* @param {...*} args Arguments to send into the method invocation.
* @return {Array} The results of invoking the method on each item in the array.
*/
invoke : function(arr, methodName){
var ret = [],
args = Array.prototype.slice.call(arguments, 2);
Ext.each(arr, function(v,i) {
if (v && typeof v[methodName] == 'function') {
ret.push(v[methodName].apply(v, args));
} else {
ret.push(undefined);
}
});
return ret;
},
/**
* Plucks the value of a property from each item in the Array
*
// Example:
Ext.pluck(Ext.query("p"), "className"); // [el1.className, el2.className, ..., elN.className]
*
* @param {Array|NodeList} arr The Array of items to pluck the value from.
* @param {String} prop The property name to pluck from each element.
* @return {Array} The value from each item in the Array.
*/
pluck : function(arr, prop){
var ret = [];
Ext.each(arr, function(v) {
ret.push( v[prop] );
});
return ret;
},
/**
* Zips N sets together.
*
// Example 1:
Ext.zip([1,2,3],[4,5,6]); // [[1,4],[2,5],[3,6]]
// Example 2:
Ext.zip(
[ "+", "-", "+"],
[ 12, 10, 22],
[ 43, 15, 96],
function(a, b, c){
return "$" + a + "" + b + "." + c
}
); // ["$+12.43", "$-10.15", "$+22.96"]
*
* @param {Arrays|NodeLists} arr This argument may be repeated. Array(s) to contribute values.
* @param {Function} zipper (optional) The last item in the argument list. This will drive how the items are zipped together.
* @return {Array} The zipped set.
*/
zip : function(){
var parts = Ext.partition(arguments, function( val ){ return typeof val != 'function'; }),
arrs = parts[0],
fn = parts[1][0],
len = Ext.max(Ext.pluck(arrs, "length")),
ret = [];
for (var i = 0; i < len; i++) {
ret[i] = [];
if(fn){
ret[i] = fn.apply(fn, Ext.pluck(arrs, i));
}else{
for (var j = 0, aLen = arrs.length; j < aLen; j++){
ret[i].push( arrs[j][i] );
}
}
}
return ret;
},
/**
* This is shorthand reference to {@link Ext.ComponentMgr#get}.
* Looks up an existing {@link Ext.Component Component} by {@link Ext.Component#id id}
* @param {String} id The component {@link Ext.Component#id id}
* @return Ext.Component The Component, undefined if not found, or null if a
* Class was found.
*/
getCmp : function(id){
return Ext.ComponentMgr.get(id);
},
/**
* By default, Ext intelligently decides whether floating elements should be shimmed. If you are using flash,
* you may want to set this to true.
* @type Boolean
*/
useShims: E.isIE6 || (E.isMac && E.isGecko2),
// inpired by a similar function in mootools library
/**
* Returns the type of object that is passed in. If the object passed in is null or undefined it
* return false otherwise it returns one of the following values:
* string : If the object passed is a string
* number : If the object passed is a number
* boolean : If the object passed is a boolean value
* date : If the object passed is a Date object
* function : If the object passed is a function reference
* object : If the object passed is an object
* array : If the object passed is an array
* regexp : If the object passed is a regular expression
* element : If the object passed is a DOM Element
* nodelist : If the object passed is a DOM NodeList
* textnode : If the object passed is a DOM text node and contains something other than whitespace
* whitespace : If the object passed is a DOM text node and contains only whitespace
*
* @param {Mixed} object
* @return {String}
*/
type : function(o){
if(o === undefined || o === null){
return false;
}
if(o.htmlElement){
return 'element';
}
var t = typeof o;
if(t == 'object' && o.nodeName) {
switch(o.nodeType) {
case 1: return 'element';
case 3: return (/\S/).test(o.nodeValue) ? 'textnode' : 'whitespace';
}
}
if(t == 'object' || t == 'function') {
switch(o.constructor) {
case Array: return 'array';
case RegExp: return 'regexp';
case Date: return 'date';
}
if(typeof o.length == 'number' && typeof o.item == 'function') {
return 'nodelist';
}
}
return t;
},
intercept : function(o, name, fn, scope){
o[name] = o[name].createInterceptor(fn, scope);
},
// internal
callback : function(cb, scope, args, delay){
if(typeof cb == 'function'){
if(delay){
cb.defer(delay, scope, args || []);
}else{
cb.apply(scope, args || []);
}
}
}
};
}());
/**
* @class Function
* These functions are available on every Function object (any JavaScript function).
*/
Ext.apply(Function.prototype, {
/**
* Create a combined function call sequence of the original function + the passed function.
* The resulting function returns the results of the original function.
* The passed fcn is called with the parameters of the original function. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
sayHi('Fred'); // alerts "Hi, Fred"
var sayGoodbye = sayHi.createSequence(function(name){
alert('Bye, ' + name);
});
sayGoodbye('Fred'); // both alerts show
* @param {Function} fcn The function to sequence
* @param {Object} scope (optional) The scope (this reference) in which the passed function is executed.
* If omitted, defaults to the scope in which the original function is called or the browser window.
* @return {Function} The new function
*/
createSequence : function(fcn, scope){
var method = this;
return (typeof fcn != 'function') ?
this :
function(){
var retval = method.apply(this || window, arguments);
fcn.apply(scope || this || window, arguments);
return retval;
};
}
});
/**
* @class String
* These functions are available as static methods on the JavaScript String object.
*/
Ext.applyIf(String, {
/**
* Escapes the passed string for ' and \
* @param {String} string The string to escape
* @return {String} The escaped string
* @static
*/
escape : function(string) {
return string.replace(/('|\\)/g, "\\$1");
},
/**
* Pads the left side of a string with a specified character. This is especially useful
* for normalizing number and date strings. Example usage:
*
var s = String.leftPad('123', 5, '0');
// s now contains the string: '00123'
*
* @param {String} string The original string
* @param {Number} size The total length of the output string
* @param {String} char (optional) The character with which to pad the original string (defaults to empty string " ")
* @return {String} The padded string
* @static
*/
leftPad : function (val, size, ch) {
var result = String(val);
if(!ch) {
ch = " ";
}
while (result.length < size) {
result = ch + result;
}
return result;
}
});
/**
* Utility function that allows you to easily switch a string between two alternating values. The passed value
* is compared to the current string, and if they are equal, the other value that was passed in is returned. If
* they are already different, the first value passed in is returned. Note that this method returns the new value
* but does not change the current string.
*
// alternate sort directions
sort = sort.toggle('ASC', 'DESC');
// instead of conditional logic:
sort = (sort == 'ASC' ? 'DESC' : 'ASC');
* @param {String} value The value to compare to the current string
* @param {String} other The new value to use if the string already equals the first value passed in
* @return {String} The new value
*/
String.prototype.toggle = function(value, other){
return this == value ? other : value;
};
/**
* Trims whitespace from either end of a string, leaving spaces within the string intact. Example:
*
var s = ' foo bar ';
alert('-' + s + '-'); //alerts "- foo bar -"
alert('-' + s.trim() + '-'); //alerts "-foo bar-"
* @return {String} The trimmed string
*/
String.prototype.trim = function(){
var re = /^\s+|\s+$/g;
return function(){ return this.replace(re, ""); };
}();
// here to prevent dependency on Date.js
/**
Returns the number of milliseconds between this date and date
@param {Date} date (optional) Defaults to now
@return {Number} The diff in milliseconds
@member Date getElapsed
*/
Date.prototype.getElapsed = function(date) {
return Math.abs((date || new Date()).getTime()-this.getTime());
};
/**
* @class Number
*/
Ext.applyIf(Number.prototype, {
/**
* Checks whether or not the current number is within a desired range. If the number is already within the
* range it is returned, otherwise the min or max value is returned depending on which side of the range is
* exceeded. Note that this method returns the constrained value but does not change the current number.
* @param {Number} min The minimum number in the range
* @param {Number} max The maximum number in the range
* @return {Number} The constrained value if outside the range, otherwise the current value
*/
constrain : function(min, max){
return Math.min(Math.max(this, min), max);
}
});
Ext.lib.Dom.getRegion = function(el) {
return Ext.lib.Region.getRegion(el);
}; Ext.lib.Region = function(t, r, b, l) {
var me = this;
me.top = t;
me[1] = t;
me.right = r;
me.bottom = b;
me.left = l;
me[0] = l;
};
Ext.lib.Region.prototype = {
contains : function(region) {
var me = this;
return ( region.left >= me.left &&
region.right <= me.right &&
region.top >= me.top &&
region.bottom <= me.bottom );
},
getArea : function() {
var me = this;
return ( (me.bottom - me.top) * (me.right - me.left) );
},
intersect : function(region) {
var me = this,
t = Math.max(me.top, region.top),
r = Math.min(me.right, region.right),
b = Math.min(me.bottom, region.bottom),
l = Math.max(me.left, region.left);
if (b >= t && r >= l) {
return new Ext.lib.Region(t, r, b, l);
}
},
union : function(region) {
var me = this,
t = Math.min(me.top, region.top),
r = Math.max(me.right, region.right),
b = Math.max(me.bottom, region.bottom),
l = Math.min(me.left, region.left);
return new Ext.lib.Region(t, r, b, l);
},
constrainTo : function(r) {
var me = this;
me.top = me.top.constrain(r.top, r.bottom);
me.bottom = me.bottom.constrain(r.top, r.bottom);
me.left = me.left.constrain(r.left, r.right);
me.right = me.right.constrain(r.left, r.right);
return me;
},
adjust : function(t, l, b, r) {
var me = this;
me.top += t;
me.left += l;
me.right += r;
me.bottom += b;
return me;
}
};
Ext.lib.Region.getRegion = function(el) {
var p = Ext.lib.Dom.getXY(el),
t = p[1],
r = p[0] + el.offsetWidth,
b = p[1] + el.offsetHeight,
l = p[0];
return new Ext.lib.Region(t, r, b, l);
}; Ext.lib.Point = function(x, y) {
if (Ext.isArray(x)) {
y = x[1];
x = x[0];
}
var me = this;
me.x = me.right = me.left = me[0] = x;
me.y = me.top = me.bottom = me[1] = y;
};
Ext.lib.Point.prototype = new Ext.lib.Region();
/**
* @class Ext.DomHelper
*/
Ext.apply(Ext.DomHelper,
function(){
var pub,
afterbegin = 'afterbegin',
afterend = 'afterend',
beforebegin = 'beforebegin',
beforeend = 'beforeend',
confRe = /tag|children|cn|html$/i;
// private
function doInsert(el, o, returnElement, pos, sibling, append){
el = Ext.getDom(el);
var newNode;
if (pub.useDom) {
newNode = createDom(o, null);
if (append) {
el.appendChild(newNode);
} else {
(sibling == 'firstChild' ? el : el.parentNode).insertBefore(newNode, el[sibling] || el);
}
} else {
newNode = Ext.DomHelper.insertHtml(pos, el, Ext.DomHelper.createHtml(o));
}
return returnElement ? Ext.get(newNode, true) : newNode;
}
// build as dom
/** @ignore */
function createDom(o, parentNode){
var el,
doc = document,
useSet,
attr,
val,
cn;
if (Ext.isArray(o)) { // Allow Arrays of siblings to be inserted
el = doc.createDocumentFragment(); // in one shot using a DocumentFragment
for (var i = 0, l = o.length; i < l; i++) {
createDom(o[i], el);
}
} else if (typeof o == 'string') { // Allow a string as a child spec.
el = doc.createTextNode(o);
} else {
el = doc.createElement( o.tag || 'div' );
useSet = !!el.setAttribute; // In IE some elements don't have setAttribute
for (var attr in o) {
if(!confRe.test(attr)){
val = o[attr];
if(attr == 'cls'){
el.className = val;
}else{
if(useSet){
el.setAttribute(attr, val);
}else{
el[attr] = val;
}
}
}
}
Ext.DomHelper.applyStyles(el, o.style);
if ((cn = o.children || o.cn)) {
createDom(cn, el);
} else if (o.html) {
el.innerHTML = o.html;
}
}
if(parentNode){
parentNode.appendChild(el);
}
return el;
}
pub = {
/**
* Creates a new Ext.Template from the DOM object spec.
* @param {Object} o The DOM object spec (and children)
* @return {Ext.Template} The new template
*/
createTemplate : function(o){
var html = Ext.DomHelper.createHtml(o);
return new Ext.Template(html);
},
/** True to force the use of DOM instead of html fragments @type Boolean */
useDom : false,
/**
* Creates new DOM element(s) and inserts them before el.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
* @hide (repeat)
*/
insertBefore : function(el, o, returnElement){
return doInsert(el, o, returnElement, beforebegin);
},
/**
* Creates new DOM element(s) and inserts them after el.
* @param {Mixed} el The context element
* @param {Object} o The DOM object spec (and children)
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
* @hide (repeat)
*/
insertAfter : function(el, o, returnElement){
return doInsert(el, o, returnElement, afterend, 'nextSibling');
},
/**
* Creates new DOM element(s) and inserts them as the first child of el.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
* @hide (repeat)
*/
insertFirst : function(el, o, returnElement){
return doInsert(el, o, returnElement, afterbegin, 'firstChild');
},
/**
* Creates new DOM element(s) and appends them to el.
* @param {Mixed} el The context element
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @param {Boolean} returnElement (optional) true to return a Ext.Element
* @return {HTMLElement/Ext.Element} The new node
* @hide (repeat)
*/
append: function(el, o, returnElement){
return doInsert(el, o, returnElement, beforeend, '', true);
},
/**
* Creates new DOM element(s) without inserting them to the document.
* @param {Object/String} o The DOM object spec (and children) or raw HTML blob
* @return {HTMLElement} The new uninserted node
*/
createDom: createDom
};
return pub;
}());
/**
* @class Ext.Template
*/
Ext.apply(Ext.Template.prototype, {
/**
* @cfg {Boolean} disableFormats Specify true to disable format
* functions in the template. If the template does not contain
* {@link Ext.util.Format format functions}, setting disableFormats
* to true will reduce {@link #apply} time. Defaults to false .
*
var t = new Ext.Template(
'<div name="{id}">',
'<span class="{cls}">{name} {value}</span>',
'</div>',
{
compiled: true, // {@link #compile} immediately
disableFormats: true // reduce {@link #apply} time since no formatting
}
);
*
* For a list of available format functions, see {@link Ext.util.Format}.
*/
disableFormats : false,
/**
* See {@link #disableFormats}.
* @type Boolean
* @property disableFormats
*/
/**
* The regular expression used to match template variables
* @type RegExp
* @property
* @hide repeat doc
*/
re : /\{([\w\-]+)(?:\:([\w\.]*)(?:\((.*?)?\))?)?\}/g,
argsRe : /^\s*['"](.*)["']\s*$/,
compileARe : /\\/g,
compileBRe : /(\r\n|\n)/g,
compileCRe : /'/g,
/**
* Returns an HTML fragment of this template with the specified values applied.
* @param {Object/Array} values The template values. Can be an array if your params are numeric (i.e. {0}) or an object (i.e. {foo: 'bar'})
* @return {String} The HTML fragment
* @hide repeat doc
*/
applyTemplate : function(values){
var me = this,
useF = me.disableFormats !== true,
fm = Ext.util.Format,
tpl = me;
if(me.compiled){
return me.compiled(values);
}
function fn(m, name, format, args){
if (format && useF) {
if (format.substr(0, 5) == "this.") {
return tpl.call(format.substr(5), values[name], values);
} else {
if (args) {
// quoted values are required for strings in compiled templates,
// but for non compiled we need to strip them
// quoted reversed for jsmin
var re = me.argsRe;
args = args.split(',');
for(var i = 0, len = args.length; i < len; i++){
args[i] = args[i].replace(re, "$1");
}
args = [values[name]].concat(args);
} else {
args = [values[name]];
}
return fm[format].apply(fm, args);
}
} else {
return values[name] !== undefined ? values[name] : "";
}
}
return me.html.replace(me.re, fn);
},
/**
* Compiles the template into an internal function, eliminating the RegEx overhead.
* @return {Ext.Template} this
* @hide repeat doc
*/
compile : function(){
var me = this,
fm = Ext.util.Format,
useF = me.disableFormats !== true,
sep = Ext.isGecko ? "+" : ",",
body;
function fn(m, name, format, args){
if(format && useF){
args = args ? ',' + args : "";
if(format.substr(0, 5) != "this."){
format = "fm." + format + '(';
}else{
format = 'this.call("'+ format.substr(5) + '", ';
args = ", values";
}
}else{
args= ''; format = "(values['" + name + "'] == undefined ? '' : ";
}
return "'"+ sep + format + "values['" + name + "']" + args + ")"+sep+"'";
}
// branched to use + in gecko and [].join() in others
if(Ext.isGecko){
body = "this.compiled = function(values){ return '" +
me.html.replace(me.compileARe, '\\\\').replace(me.compileBRe, '\\n').replace(me.compileCRe, "\\'").replace(me.re, fn) +
"';};";
}else{
body = ["this.compiled = function(values){ return ['"];
body.push(me.html.replace(me.compileARe, '\\\\').replace(me.compileBRe, '\\n').replace(me.compileCRe, "\\'").replace(me.re, fn));
body.push("'].join('');};");
body = body.join('');
}
eval(body);
return me;
},
// private function used to call members
call : function(fnName, value, allValues){
return this[fnName](value, allValues);
}
});
Ext.Template.prototype.apply = Ext.Template.prototype.applyTemplate;
/**
* @class Ext.util.Functions
* @singleton
*/
Ext.util.Functions = {
/**
* Creates an interceptor function. The passed function is called before the original one. If it returns false,
* the original one is not called. The resulting function returns the results of the original function.
* The passed function is called with the parameters of the original function. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
sayHi('Fred'); // alerts "Hi, Fred"
// create a new function that validates input without
// directly modifying the original function:
var sayHiToFriend = Ext.createInterceptor(sayHi, function(name){
return name == 'Brian';
});
sayHiToFriend('Fred'); // no alert
sayHiToFriend('Brian'); // alerts "Hi, Brian"
* @param {Function} origFn The original function.
* @param {Function} newFn The function to call before the original
* @param {Object} scope (optional) The scope (this reference) in which the passed function is executed.
* If omitted, defaults to the scope in which the original function is called or the browser window.
* @return {Function} The new function
*/
createInterceptor: function(origFn, newFn, scope) {
var method = origFn;
if (!Ext.isFunction(newFn)) {
return origFn;
}
else {
return function() {
var me = this,
args = arguments;
newFn.target = me;
newFn.method = origFn;
return (newFn.apply(scope || me || window, args) !== false) ?
origFn.apply(me || window, args) :
null;
};
}
},
/**
* Creates a delegate (callback) that sets the scope to obj.
* Call directly on any function. Example: Ext.createDelegate(this.myFunction, this, [arg1, arg2])
* Will create a function that is automatically scoped to obj so that the this variable inside the
* callback points to obj. Example usage:
*
var sayHi = function(name){
// Note this use of "this.text" here. This function expects to
// execute within a scope that contains a text property. In this
// example, the "this" variable is pointing to the btn object that
// was passed in createDelegate below.
alert('Hi, ' + name + '. You clicked the "' + this.text + '" button.');
}
var btn = new Ext.Button({
text: 'Say Hi',
renderTo: Ext.getBody()
});
// This callback will execute in the scope of the
// button instance. Clicking the button alerts
// "Hi, Fred. You clicked the "Say Hi" button."
btn.on('click', Ext.createDelegate(sayHi, btn, ['Fred']));
* @param {Function} fn The function to delegate.
* @param {Object} scope (optional) The scope (this reference) in which the function is executed.
* If omitted, defaults to the browser window.
* @param {Array} args (optional) Overrides arguments for the call. (Defaults to the arguments passed by the caller)
* @param {Boolean/Number} appendArgs (optional) if True args are appended to call args instead of overriding,
* if a number the args are inserted at the specified position
* @return {Function} The new function
*/
createDelegate: function(fn, obj, args, appendArgs) {
if (!Ext.isFunction(fn)) {
return fn;
}
return function() {
var callArgs = args || arguments;
if (appendArgs === true) {
callArgs = Array.prototype.slice.call(arguments, 0);
callArgs = callArgs.concat(args);
}
else if (Ext.isNumber(appendArgs)) {
callArgs = Array.prototype.slice.call(arguments, 0);
// copy arguments first
var applyArgs = [appendArgs, 0].concat(args);
// create method call params
Array.prototype.splice.apply(callArgs, applyArgs);
// splice them in
}
return fn.apply(obj || window, callArgs);
};
},
/**
* Calls this function after the number of millseconds specified, optionally in a specific scope. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
// executes immediately:
sayHi('Fred');
// executes after 2 seconds:
Ext.defer(sayHi, 2000, this, ['Fred']);
// this syntax is sometimes useful for deferring
// execution of an anonymous function:
Ext.defer(function(){
alert('Anonymous');
}, 100);
* @param {Function} fn The function to defer.
* @param {Number} millis The number of milliseconds for the setTimeout call (if less than or equal to 0 the function is executed immediately)
* @param {Object} scope (optional) The scope (this reference) in which the function is executed.
* If omitted, defaults to the browser window.
* @param {Array} args (optional) Overrides arguments for the call. (Defaults to the arguments passed by the caller)
* @param {Boolean/Number} appendArgs (optional) if True args are appended to call args instead of overriding,
* if a number the args are inserted at the specified position
* @return {Number} The timeout id that can be used with clearTimeout
*/
defer: function(fn, millis, obj, args, appendArgs) {
fn = Ext.util.Functions.createDelegate(fn, obj, args, appendArgs);
if (millis > 0) {
return setTimeout(fn, millis);
}
fn();
return 0;
},
/**
* Create a combined function call sequence of the original function + the passed function.
* The resulting function returns the results of the original function.
* The passed fcn is called with the parameters of the original function. Example usage:
*
var sayHi = function(name){
alert('Hi, ' + name);
}
sayHi('Fred'); // alerts "Hi, Fred"
var sayGoodbye = Ext.createSequence(sayHi, function(name){
alert('Bye, ' + name);
});
sayGoodbye('Fred'); // both alerts show
* @param {Function} origFn The original function.
* @param {Function} newFn The function to sequence
* @param {Object} scope (optional) The scope (this reference) in which the passed function is executed.
* If omitted, defaults to the scope in which the original function is called or the browser window.
* @return {Function} The new function
*/
createSequence: function(origFn, newFn, scope) {
if (!Ext.isFunction(newFn)) {
return origFn;
}
else {
return function() {
var retval = origFn.apply(this || window, arguments);
newFn.apply(scope || this || window, arguments);
return retval;
};
}
}
};
/**
* Shorthand for {@link Ext.util.Functions#defer}
* @param {Function} fn The function to defer.
* @param {Number} millis The number of milliseconds for the setTimeout call (if less than or equal to 0 the function is executed immediately)
* @param {Object} scope (optional) The scope (this reference) in which the function is executed.
* If omitted, defaults to the browser window.
* @param {Array} args (optional) Overrides arguments for the call. (Defaults to the arguments passed by the caller)
* @param {Boolean/Number} appendArgs (optional) if True args are appended to call args instead of overriding,
* if a number the args are inserted at the specified position
* @return {Number} The timeout id that can be used with clearTimeout
* @member Ext
* @method defer
*/
Ext.defer = Ext.util.Functions.defer;
/**
* Shorthand for {@link Ext.util.Functions#createInterceptor}
* @param {Function} origFn The original function.
* @param {Function} newFn The function to call before the original
* @param {Object} scope (optional) The scope (this reference) in which the passed function is executed.
* If omitted, defaults to the scope in which the original function is called or the browser window.
* @return {Function} The new function
* @member Ext
* @method createInterceptor
*/
Ext.createInterceptor = Ext.util.Functions.createInterceptor;
/**
* Shorthand for {@link Ext.util.Functions#createSequence}
* @param {Function} origFn The original function.
* @param {Function} newFn The function to sequence
* @param {Object} scope (optional) The scope (this reference) in which the passed function is executed.
* If omitted, defaults to the scope in which the original function is called or the browser window.
* @return {Function} The new function
* @member Ext
* @method createSequence
*/
Ext.createSequence = Ext.util.Functions.createSequence;
/**
* Shorthand for {@link Ext.util.Functions#createDelegate}
* @param {Function} fn The function to delegate.
* @param {Object} scope (optional) The scope (this reference) in which the function is executed.
* If omitted, defaults to the browser window.
* @param {Array} args (optional) Overrides arguments for the call. (Defaults to the arguments passed by the caller)
* @param {Boolean/Number} appendArgs (optional) if True args are appended to call args instead of overriding,
* if a number the args are inserted at the specified position
* @return {Function} The new function
* @member Ext
* @method createDelegate
*/
Ext.createDelegate = Ext.util.Functions.createDelegate;
/**
* @class Ext.util.Observable
*/
Ext.apply(Ext.util.Observable.prototype, function(){
// this is considered experimental (along with beforeMethod, afterMethod, removeMethodListener?)
// allows for easier interceptor and sequences, including cancelling and overwriting the return value of the call
// private
function getMethodEvent(method){
var e = (this.methodEvents = this.methodEvents ||
{})[method], returnValue, v, cancel, obj = this;
if (!e) {
this.methodEvents[method] = e = {};
e.originalFn = this[method];
e.methodName = method;
e.before = [];
e.after = [];
var makeCall = function(fn, scope, args){
if((v = fn.apply(scope || obj, args)) !== undefined){
if (typeof v == 'object') {
if(v.returnValue !== undefined){
returnValue = v.returnValue;
}else{
returnValue = v;
}
cancel = !!v.cancel;
}
else
if (v === false) {
cancel = true;
}
else {
returnValue = v;
}
}
};
this[method] = function(){
var args = Array.prototype.slice.call(arguments, 0),
b;
returnValue = v = undefined;
cancel = false;
for(var i = 0, len = e.before.length; i < len; i++){
b = e.before[i];
makeCall(b.fn, b.scope, args);
if (cancel) {
return returnValue;
}
}
if((v = e.originalFn.apply(obj, args)) !== undefined){
returnValue = v;
}
for(var i = 0, len = e.after.length; i < len; i++){
b = e.after[i];
makeCall(b.fn, b.scope, args);
if (cancel) {
return returnValue;
}
}
return returnValue;
};
}
return e;
}
return {
// these are considered experimental
// allows for easier interceptor and sequences, including cancelling and overwriting the return value of the call
// adds an 'interceptor' called before the original method
beforeMethod : function(method, fn, scope){
getMethodEvent.call(this, method).before.push({
fn: fn,
scope: scope
});
},
// adds a 'sequence' called after the original method
afterMethod : function(method, fn, scope){
getMethodEvent.call(this, method).after.push({
fn: fn,
scope: scope
});
},
removeMethodListener: function(method, fn, scope){
var e = this.getMethodEvent(method);
for(var i = 0, len = e.before.length; i < len; i++){
if(e.before[i].fn == fn && e.before[i].scope == scope){
e.before.splice(i, 1);
return;
}
}
for(var i = 0, len = e.after.length; i < len; i++){
if(e.after[i].fn == fn && e.after[i].scope == scope){
e.after.splice(i, 1);
return;
}
}
},
/**
* Relays selected events from the specified Observable as if the events were fired by this .
* @param {Object} o The Observable whose events this object is to relay.
* @param {Array} events Array of event names to relay.
*/
relayEvents : function(o, events){
var me = this;
function createHandler(ename){
return function(){
return me.fireEvent.apply(me, [ename].concat(Array.prototype.slice.call(arguments, 0)));
};
}
for(var i = 0, len = events.length; i < len; i++){
var ename = events[i];
me.events[ename] = me.events[ename] || true;
o.on(ename, createHandler(ename), me);
}
},
/**
* Enables events fired by this Observable to bubble up an owner hierarchy by calling
* this.getBubbleTarget() if present. There is no implementation in the Observable base class.
* This is commonly used by Ext.Components to bubble events to owner Containers. See {@link Ext.Component.getBubbleTarget}. The default
* implementation in Ext.Component returns the Component's immediate owner. But if a known target is required, this can be overridden to
* access the required target more quickly.
* Example:
Ext.override(Ext.form.Field, {
// Add functionality to Field's initComponent to enable the change event to bubble
initComponent : Ext.form.Field.prototype.initComponent.createSequence(function() {
this.enableBubble('change');
}),
// We know that we want Field's events to bubble directly to the FormPanel.
getBubbleTarget : function() {
if (!this.formPanel) {
this.formPanel = this.findParentByType('form');
}
return this.formPanel;
}
});
var myForm = new Ext.formPanel({
title: 'User Details',
items: [{
...
}],
listeners: {
change: function() {
// Title goes red if form has been modified.
myForm.header.setStyle('color', 'red');
}
}
});
* @param {String/Array} events The event name to bubble, or an Array of event names.
*/
enableBubble : function(events){
var me = this;
if(!Ext.isEmpty(events)){
events = Ext.isArray(events) ? events : Array.prototype.slice.call(arguments, 0);
for(var i = 0, len = events.length; i < len; i++){
var ename = events[i];
ename = ename.toLowerCase();
var ce = me.events[ename] || true;
if (typeof ce == 'boolean') {
ce = new Ext.util.Event(me, ename);
me.events[ename] = ce;
}
ce.bubble = true;
}
}
}
};
}());
/**
* Starts capture on the specified Observable. All events will be passed
* to the supplied function with the event name + standard signature of the event
* before the event is fired. If the supplied function returns false,
* the event will not fire.
* @param {Observable} o The Observable to capture events from.
* @param {Function} fn The function to call when an event is fired.
* @param {Object} scope (optional) The scope (this reference) in which the function is executed. Defaults to the Observable firing the event.
* @static
*/
Ext.util.Observable.capture = function(o, fn, scope){
o.fireEvent = o.fireEvent.createInterceptor(fn, scope);
};
/**
* Sets observability on the passed class constructor.
*
This makes any event fired on any instance of the passed class also fire a single event through
* the class allowing for central handling of events on many instances at once.
* Usage:
Ext.util.Observable.observeClass(Ext.data.Connection);
Ext.data.Connection.on('beforerequest', function(con, options) {
console.log('Ajax request made to ' + options.url);
});
* @param {Function} c The class constructor to make observable.
* @param {Object} listeners An object containing a series of listeners to add. See {@link #addListener}.
* @static
*/
Ext.util.Observable.observeClass = function(c, listeners){
if(c){
if(!c.fireEvent){
Ext.apply(c, new Ext.util.Observable());
Ext.util.Observable.capture(c.prototype, c.fireEvent, c);
}
if(typeof listeners == 'object'){
c.on(listeners);
}
return c;
}
};
/**
* @class Ext.EventManager
*/
Ext.apply(Ext.EventManager, function(){
var resizeEvent,
resizeTask,
textEvent,
textSize,
D = Ext.lib.Dom,
propRe = /^(?:scope|delay|buffer|single|stopEvent|preventDefault|stopPropagation|normalized|args|delegate)$/,
unload = Ext.EventManager._unload,
curWidth = 0,
curHeight = 0,
// note 1: IE fires ONLY the keydown event on specialkey autorepeat
// note 2: Safari < 3.1, Gecko (Mac/Linux) & Opera fire only the keypress event on specialkey autorepeat
// (research done by @Jan Wolter at http://unixpapa.com/js/key.html)
useKeydown = Ext.isWebKit ?
Ext.num(navigator.userAgent.match(/AppleWebKit\/(\d+)/)[1]) >= 525 :
!((Ext.isGecko && !Ext.isWindows) || Ext.isOpera);
return {
_unload: function(){
Ext.EventManager.un(window, "resize", this.fireWindowResize, this);
unload.call(Ext.EventManager);
},
// private
doResizeEvent: function(){
var h = D.getViewHeight(),
w = D.getViewWidth();
//whacky problem in IE where the resize event will fire even though the w/h are the same.
if(curHeight != h || curWidth != w){
resizeEvent.fire(curWidth = w, curHeight = h);
}
},
/**
* Adds a listener to be notified when the browser window is resized and provides resize event buffering (100 milliseconds),
* passes new viewport width and height to handlers.
* @param {Function} fn The handler function the window resize event invokes.
* @param {Object} scope The scope (this reference) in which the handler function executes. Defaults to the browser window.
* @param {boolean} options Options object as passed to {@link Ext.Element#addListener}
*/
onWindowResize : function(fn, scope, options){
if(!resizeEvent){
resizeEvent = new Ext.util.Event();
resizeTask = new Ext.util.DelayedTask(this.doResizeEvent);
Ext.EventManager.on(window, "resize", this.fireWindowResize, this);
}
resizeEvent.addListener(fn, scope, options);
},
// exposed only to allow manual firing
fireWindowResize : function(){
if(resizeEvent){
resizeTask.delay(100);
}
},
/**
* Adds a listener to be notified when the user changes the active text size. Handler gets called with 2 params, the old size and the new size.
* @param {Function} fn The function the event invokes.
* @param {Object} scope The scope (this reference) in which the handler function executes. Defaults to the browser window.
* @param {boolean} options Options object as passed to {@link Ext.Element#addListener}
*/
onTextResize : function(fn, scope, options){
if(!textEvent){
textEvent = new Ext.util.Event();
var textEl = new Ext.Element(document.createElement('div'));
textEl.dom.className = 'x-text-resize';
textEl.dom.innerHTML = 'X';
textEl.appendTo(document.body);
textSize = textEl.dom.offsetHeight;
setInterval(function(){
if(textEl.dom.offsetHeight != textSize){
textEvent.fire(textSize, textSize = textEl.dom.offsetHeight);
}
}, this.textResizeInterval);
}
textEvent.addListener(fn, scope, options);
},
/**
* Removes the passed window resize listener.
* @param {Function} fn The method the event invokes
* @param {Object} scope The scope of handler
*/
removeResizeListener : function(fn, scope){
if(resizeEvent){
resizeEvent.removeListener(fn, scope);
}
},
// private
fireResize : function(){
if(resizeEvent){
resizeEvent.fire(D.getViewWidth(), D.getViewHeight());
}
},
/**
* The frequency, in milliseconds, to check for text resize events (defaults to 50)
*/
textResizeInterval : 50,
/**
* Url used for onDocumentReady with using SSL (defaults to Ext.SSL_SECURE_URL)
*/
ieDeferSrc : false,
// protected, short accessor for useKeydown
getKeyEvent : function(){
return useKeydown ? 'keydown' : 'keypress';
},
// protected for use inside the framework
// detects whether we should use keydown or keypress based on the browser.
useKeydown: useKeydown
};
}());
Ext.EventManager.on = Ext.EventManager.addListener;
Ext.apply(Ext.EventObjectImpl.prototype, {
/** Key constant @type Number */
BACKSPACE: 8,
/** Key constant @type Number */
TAB: 9,
/** Key constant @type Number */
NUM_CENTER: 12,
/** Key constant @type Number */
ENTER: 13,
/** Key constant @type Number */
RETURN: 13,
/** Key constant @type Number */
SHIFT: 16,
/** Key constant @type Number */
CTRL: 17,
CONTROL : 17, // legacy
/** Key constant @type Number */
ALT: 18,
/** Key constant @type Number */
PAUSE: 19,
/** Key constant @type Number */
CAPS_LOCK: 20,
/** Key constant @type Number */
ESC: 27,
/** Key constant @type Number */
SPACE: 32,
/** Key constant @type Number */
PAGE_UP: 33,
PAGEUP : 33, // legacy
/** Key constant @type Number */
PAGE_DOWN: 34,
PAGEDOWN : 34, // legacy
/** Key constant @type Number */
END: 35,
/** Key constant @type Number */
HOME: 36,
/** Key constant @type Number */
LEFT: 37,
/** Key constant @type Number */
UP: 38,
/** Key constant @type Number */
RIGHT: 39,
/** Key constant @type Number */
DOWN: 40,
/** Key constant @type Number */
PRINT_SCREEN: 44,
/** Key constant @type Number */
INSERT: 45,
/** Key constant @type Number */
DELETE: 46,
/** Key constant @type Number */
ZERO: 48,
/** Key constant @type Number */
ONE: 49,
/** Key constant @type Number */
TWO: 50,
/** Key constant @type Number */
THREE: 51,
/** Key constant @type Number */
FOUR: 52,
/** Key constant @type Number */
FIVE: 53,
/** Key constant @type Number */
SIX: 54,
/** Key constant @type Number */
SEVEN: 55,
/** Key constant @type Number */
EIGHT: 56,
/** Key constant @type Number */
NINE: 57,
/** Key constant @type Number */
A: 65,
/** Key constant @type Number */
B: 66,
/** Key constant @type Number */
C: 67,
/** Key constant @type Number */
D: 68,
/** Key constant @type Number */
E: 69,
/** Key constant @type Number */
F: 70,
/** Key constant @type Number */
G: 71,
/** Key constant @type Number */
H: 72,
/** Key constant @type Number */
I: 73,
/** Key constant @type Number */
J: 74,
/** Key constant @type Number */
K: 75,
/** Key constant @type Number */
L: 76,
/** Key constant @type Number */
M: 77,
/** Key constant @type Number */
N: 78,
/** Key constant @type Number */
O: 79,
/** Key constant @type Number */
P: 80,
/** Key constant @type Number */
Q: 81,
/** Key constant @type Number */
R: 82,
/** Key constant @type Number */
S: 83,
/** Key constant @type Number */
T: 84,
/** Key constant @type Number */
U: 85,
/** Key constant @type Number */
V: 86,
/** Key constant @type Number */
W: 87,
/** Key constant @type Number */
X: 88,
/** Key constant @type Number */
Y: 89,
/** Key constant @type Number */
Z: 90,
/** Key constant @type Number */
CONTEXT_MENU: 93,
/** Key constant @type Number */
NUM_ZERO: 96,
/** Key constant @type Number */
NUM_ONE: 97,
/** Key constant @type Number */
NUM_TWO: 98,
/** Key constant @type Number */
NUM_THREE: 99,
/** Key constant @type Number */
NUM_FOUR: 100,
/** Key constant @type Number */
NUM_FIVE: 101,
/** Key constant @type Number */
NUM_SIX: 102,
/** Key constant @type Number */
NUM_SEVEN: 103,
/** Key constant @type Number */
NUM_EIGHT: 104,
/** Key constant @type Number */
NUM_NINE: 105,
/** Key constant @type Number */
NUM_MULTIPLY: 106,
/** Key constant @type Number */
NUM_PLUS: 107,
/** Key constant @type Number */
NUM_MINUS: 109,
/** Key constant @type Number */
NUM_PERIOD: 110,
/** Key constant @type Number */
NUM_DIVISION: 111,
/** Key constant @type Number */
F1: 112,
/** Key constant @type Number */
F2: 113,
/** Key constant @type Number */
F3: 114,
/** Key constant @type Number */
F4: 115,
/** Key constant @type Number */
F5: 116,
/** Key constant @type Number */
F6: 117,
/** Key constant @type Number */
F7: 118,
/** Key constant @type Number */
F8: 119,
/** Key constant @type Number */
F9: 120,
/** Key constant @type Number */
F10: 121,
/** Key constant @type Number */
F11: 122,
/** Key constant @type Number */
F12: 123,
/** @private */
isNavKeyPress : function(){
var me = this,
k = this.normalizeKey(me.keyCode);
return (k >= 33 && k <= 40) || // Page Up/Down, End, Home, Left, Up, Right, Down
k == me.RETURN ||
k == me.TAB ||
k == me.ESC;
},
isSpecialKey : function(){
var k = this.normalizeKey(this.keyCode);
return (this.type == 'keypress' && this.ctrlKey) ||
this.isNavKeyPress() ||
(k == this.BACKSPACE) || // Backspace
(k >= 16 && k <= 20) || // Shift, Ctrl, Alt, Pause, Caps Lock
(k >= 44 && k <= 46); // Print Screen, Insert, Delete
},
getPoint : function(){
return new Ext.lib.Point(this.xy[0], this.xy[1]);
},
/**
* Returns true if the control, meta, shift or alt key was pressed during this event.
* @return {Boolean}
*/
hasModifier : function(){
return ((this.ctrlKey || this.altKey) || this.shiftKey);
}
});/**
* @class Ext.Element
*/
Ext.Element.addMethods({
/**
* Stops the specified event(s) from bubbling and optionally prevents the default action
* @param {String/Array} eventName an event / array of events to stop from bubbling
* @param {Boolean} preventDefault (optional) true to prevent the default action too
* @return {Ext.Element} this
*/
swallowEvent : function(eventName, preventDefault) {
var me = this;
function fn(e) {
e.stopPropagation();
if (preventDefault) {
e.preventDefault();
}
}
if (Ext.isArray(eventName)) {
Ext.each(eventName, function(e) {
me.on(e, fn);
});
return me;
}
me.on(eventName, fn);
return me;
},
/**
* Create an event handler on this element such that when the event fires and is handled by this element,
* it will be relayed to another object (i.e., fired again as if it originated from that object instead).
* @param {String} eventName The type of event to relay
* @param {Object} object Any object that extends {@link Ext.util.Observable} that will provide the context
* for firing the relayed event
*/
relayEvent : function(eventName, observable) {
this.on(eventName, function(e) {
observable.fireEvent(eventName, e);
});
},
/**
* Removes worthless text nodes
* @param {Boolean} forceReclean (optional) By default the element
* keeps track if it has been cleaned already so
* you can call this over and over. However, if you update the element and
* need to force a reclean, you can pass true.
*/
clean : function(forceReclean) {
var me = this,
dom = me.dom,
n = dom.firstChild,
ni = -1;
if (Ext.Element.data(dom, 'isCleaned') && forceReclean !== true) {
return me;
}
while (n) {
var nx = n.nextSibling;
if (n.nodeType == 3 && !(/\S/.test(n.nodeValue))) {
dom.removeChild(n);
} else {
n.nodeIndex = ++ni;
}
n = nx;
}
Ext.Element.data(dom, 'isCleaned', true);
return me;
},
/**
* Direct access to the Updater {@link Ext.Updater#update} method. The method takes the same object
* parameter as {@link Ext.Updater#update}
* @return {Ext.Element} this
*/
load : function() {
var updateManager = this.getUpdater();
updateManager.update.apply(updateManager, arguments);
return this;
},
/**
* Gets this element's {@link Ext.Updater Updater}
* @return {Ext.Updater} The Updater
*/
getUpdater : function() {
return this.updateManager || (this.updateManager = new Ext.Updater(this));
},
/**
* Update the innerHTML of this element, optionally searching for and processing scripts
* @param {String} html The new HTML
* @param {Boolean} loadScripts (optional) True to look for and process scripts (defaults to false)
* @param {Function} callback (optional) For async script loading you can be notified when the update completes
* @return {Ext.Element} this
*/
update : function(html, loadScripts, callback) {
if (!this.dom) {
return this;
}
html = html || "";
if (loadScripts !== true) {
this.dom.innerHTML = html;
if (typeof callback == 'function') {
callback();
}
return this;
}
var id = Ext.id(),
dom = this.dom;
html += ' ';
Ext.lib.Event.onAvailable(id, function() {
var DOC = document,
hd = DOC.getElementsByTagName("head")[0],
re = /(?: