Back

[AD_PARENT_CATEGORY] > [AD_ORIGINATOR]

UCF AD List



AD ID

[AD_PADDED_ID]

AD STATUS

UCF AD List

ORIGINATOR

[AD_ORIGINATOR]

TYPE

[AD_DOC_TYPE]

AVAILABILITY

[AD_AVAILABILITY]

SYNONYMS

UCF AD List

UCF AD List

EFFECTIVE

[AD_EFFECTIVE_DATE]

ADDED

AD ID

[AD_PADDED_ID]

AD STATUS

ORIGINATOR

[AD_ORIGINATOR]

TYPE

[AD_DOC_TYPE]

AVAILABILITY

<[AD_AVAILABILITY]

SYNONYMS

UCF AD List

UCF AD List

EFFECTIVE

[AD_EFFECTIVE_DATE]

ADDED


Important Notice

This Authority Document In Depth Report is copyrighted - © 2020 - Network Frontiers LLC. All rights reserved. Copyright in the Authority Document analyzed herein is held by its authors. Network Frontiers makes no claims of copyright in this Authority Document.

This Authority Document In Depth Report is provided for informational purposes only and does not constitute, and should not be construed as, legal advice. The reader is encouraged to consult with an attorney experienced in these areas for further explanation and advice.

This Authority Document In Depth Report provides analysis and guidance for use and implementation of the Authority Document but it is not a substitute for the original authority document itself. Readers should refer to the original authority document as the definitive resource on obligations and compliance requirements.

The process we used to tag and map this document

This document has been mapped into the Unified Compliance Framework using a patented methodology and patented tools (you can research our patents HERE). The mapping team has taken every effort to ensure the quality of mapping is of the highest degree. To learn more about the process we use to map Authority Documents, or to become involved in that process, click HERE.

Controls and asociated Citations breakdown

When the UCF Mapping Teams tag Citations and their associated mandates within an Authority Document, those Citations and Mandates are tied to Common Controls. In addition, and by virtue of those Citations and mandates being tied to Common Controls, there are three sets of meta data that are associated with each Citation; Controls by Impact Zone, Controls by Type, and Controls by Classification.

The online version of the mapping analysis you see here is just a fraction of the work the UCF Mapping Team has done. The downloadable version of this document, available within the Common Controls Hub (available HERE) contains the following:

Document implementation analysis – statistics about the document’s alignment with Common Controls as compared to other Authority Documents and statistics on usage of key terms and non-standard terms.

Citation and Mandate Tagging and Mapping – A complete listing of each and every Citation we found within UCF AD List that have been tagged with their primary and secondary nouns and primary and secondary verbs in three column format. The first column shows the Citation (the marker within the Authority Document that points to where we found the guidance). The second column shows the Citation guidance per se, along with the tagging for the mandate we found within the Citation. The third column shows the Common Control ID that the mandate is linked to, and the final column gives us the Common Control itself.

Dictionary Terms – The dictionary terms listed for UCF AD List are based upon terms either found within the Authority Document’s defined terms section(which most legal documents have), its glossary, and for the most part, as tagged within each mandate. The terms with links are terms that are the standardized version of the term.



Common Controls and
mandates by Impact Zone
[MANDATED_CONTROLS_COUNT] Mandated Controls - bold    
[IMPLIED_CONTROLS_COUNT] Implied Controls - italic     0 Implementation

An Impact Zone is a hierarchical way of organizing our suite of Common Controls — it is a taxonomy. The top levels of the UCF hierarchy are called Impact Zones. Common Controls are mapped within the UCF’s Impact Zones and are maintained in a legal hierarchy within that Impact Zone. Each Impact Zone deals with a separate area of policies, standards, and procedures: technology acquisition, physical security, continuity, records management, etc.


The UCF created its taxonomy by looking at the corpus of standards and regulations through the lens of unification and a view toward how the controls impact the organization. Thus, we created a hierarchical structure for each impact zone that takes into account regulatory and standards bodies, doctrines, and language.

Number of Controls
0 Total
    Common Controls and
    mandates by Type
    [MANDATED_CONTROLS_COUNT] Mandated Controls - bold    
    [IMPLIED_CONTROLS_COUNT] Implied Controls - italic     0 Implementation

    Each Common Control is assigned a meta-data type to help you determine the objective of the Control and associated Authority Document mandates aligned with it. These types include behavioral controls, process controls, records management, technical security, configuration management, etc. They are provided as another tool to dissect the Authority Document’s mandates and assign them effectively within your organization.

    Number of Controls
    0 Total
      Common Controls and
      mandates by Classification
      [MANDATED_CONTROLS_COUNT] Mandated Controls - bold    
      [IMPLIED_CONTROLS_COUNT] Implied Controls - italic     0 Implementation

      There are three types of Common Control classifications; corrective, detective, and preventive. Common Controls at the top level have the default assignment of Impact Zone.

      Number of Controls
      0 Total