How federal information-security policy developed

The history of OMB Circular A-130, the laws that shaped it, and the technical standards agencies use to protect information.

1965–2026

Read the history Find a document →

How laws, agency policy, and technical standards fit together

Federal information security grew out of two related needs: managing government information well and protecting the computers that hold it. Congress gave agencies duties in both areas. The Office of Management and Budget (OMB), part of the Executive Office of the President, turns many of those duties into government-wide policy. Its Circular A-130 brings together rules for managing information, buying technology, protecting privacy, and securing systems. A circular is a set of instructions OMB issues to federal agencies.

The National Institute of Standards and Technology (NIST), within the Department of Commerce, develops the technical standards and guidance agencies use. Its predecessor, the National Bureau of Standards, was doing computer-security work before A-130 appeared in 1985. Congress has repeatedly assigned standards work directly to NIST. OMB and NIST also work together: OMB sets agency expectations, while NIST develops methods for meeting them. In some cases, NIST’s existing work helps shape OMB policy.

A-130’s central contribution is to make security part of everyday agency management. Officials must plan for it, fund it, assign responsibility, and decide whether a system’s risks are acceptable. Technical standards supply much of the detail. Federal Information Processing Standards (FIPS) establish standards for specified federal uses; NIST Special Publications (SP) explain methods and practices. A law, policy, standard, regulation, or contract determines when particular guidance is required.

Cloud services brought these responsibilities into a shared setting. Agencies increasingly relied on commercially operated systems, while remaining responsible for their information. The Federal Risk and Authorization Management Program (FedRAMP), established by OMB in 2011 and written into law in 2022, lets agencies reuse security assessments of cloud services. Its requirements combine A-130’s agency responsibilities with NIST standards and cloud-specific law and policy.1

CongressAssigns responsibilities in law
OMB & agenciesSet policy and manage systems
NIST & CommerceDevelop and issue standards

Laws, policies, and standards over time

Compare laws, OMB policies, and technical publications over time. Select an event to read about the document and open its sources.

PeriodLaws & presidential directivesOMB policyNIST and its predecessor, NBS
1965–1979
1980–1989
1990–1995
1996–2000
2001–2006
2007–2014
2015–2020
2021–2026

Select an event for its description and source links.

Before A-130: computers, personal records, and security

In the 1960s, federal computer policy focused on acquiring equipment, sharing expensive machines, and deciding who would manage them. In March 1965, the Bureau of the Budget, OMB’s predecessor, issued Circular A-71 to divide those responsibilities among agencies, the General Services Administration, and the Department of Commerce. The Brooks Act followed in October. It gave Commerce a statutory role in computer standards and technical services.

As agencies collected more personal information, Congress added safeguards. The Privacy Act of 1974 required agencies to protect records about individuals and assigned OMB responsibility for implementation guidance. The National Bureau of Standards developed technical guidance on physical security and risk analysis, as well as the Data Encryption Standard. These publications gave agencies practical tools for protecting information and computer facilities.

A 1978 addition to A-71 brought security of automated systems into OMB’s management instructions. Agencies were expected to plan for risks and disruptions. The National Bureau of Standards’ 1982 guide to contingency planning helped managers carry out those responsibilities, including preparing to continue essential work when computers were unavailable.

The Paperwork Reduction Act of 1980 gave OMB a broader information-management role, covering how agencies collected, used, maintained, and shared information. A-130 brought these strands together in 1985: information policy, technology management, privacy, records, and security.23

How A-130 changed

Six major editions show how A-130 changed as federal computing, public services, and security responsibilities developed.

1985 · Bringing information policy together

OMB issued A-130 in December 1985 to bring government information policy into one place. Agencies had previously worked under several circulars covering computers, records, privacy, and coordination with state and local governments. The new circular replaced four of them and carried forward the security responsibilities introduced under A-71. It took effect on December 12 and appeared in the Federal Register, the government’s official publication of rules and notices, on December 24.

“general policy framework for management of Federal information resources”

A-130: initial circular, 1985-12-124

The Paperwork Reduction Act of 1980 provided the main framework. Congress had assigned OMB responsibility for government-wide information management and required agencies to manage their information resources. A-130 connected those duties with the Privacy Act’s protections for personal records and the Brooks Act’s provisions for computer equipment and standards. It addressed both the public value of government information and the resources needed to collect, maintain, and use it.

Security was part of that larger management task. Appendix III required agencies to establish security programs, assess risks, review protections, and prepare for disruptions. Much of the policy reflected a period when agencies depended on centralized computer facilities. Managers needed to protect those facilities and ensure that essential work could continue after an equipment failure or other emergency.

Technical standards were already available. The National Bureau of Standards had published guidance on physical security and risk analysis, along with an encryption standard. A-130 connected this technical work to agency planning and accountability. Its lasting contribution was to put responsibility for security alongside decisions about budgets, equipment, staff, and information—not to leave protection solely to computer specialists. Later revisions would adapt that approach as agencies moved from large central computers to interconnected systems and commercial services.

Sources and edition notes 56

Official source · Download original · Read formatted text

1993 · Making government information easier to use

The 1993 revision focused on how agencies collected, managed, and shared information. Electronic records and new ways of distributing information were changing the relationship between government and the public. OMB asked agencies to plan for information throughout its life: from collection and use to public access, preservation, and disposal. The revision took effect on June 25 and was published on July 2.

Agencies were responsible for making information available in ways that supported their missions. They also needed to consider the needs of people using that information and consult with state and local governments. OMB folded its separate policies on government publications and audiovisual activities into A-130, making the circular a more complete guide to public information. Its definition of government information included information handled for the government, extending the management perspective beyond an agency’s own offices.

Several laws had changed since 1985. Amendments to the Paperwork Reduction Act affected information management. The Computer Security Act assigned security-planning and training duties to agencies and standards work to the National Bureau of Standards, renamed NIST in 1988. The Computer Matching and Privacy Protection Act and its amendments added protections when agencies compared personal records across systems. The revised circular also cited the Chief Financial Officers Act.

OMB updated its privacy appendix to reflect the matching requirements but left Appendix III, the security appendix, unchanged. Further work on technology management and security was still to come. Meanwhile, NIST continued developing security standards under its statutory responsibilities. The 1993 update therefore matters chiefly for its treatment of information as something agencies must manage from beginning to end, including the public’s ability to find and use it. That broader view would remain important as later revisions brought security more closely into agency planning.

Sources and edition notes 78

Official source · Download original · Extracted text

1994 · Connecting technology spending to public services

The 1994 revision asked agencies to judge technology by the work it helped them accomplish. OMB wanted better public services, lower administrative costs, and less burden on the public. Agencies needed to consider whether an investment would improve their operations before committing money to a system. The revision took effect on July 15 and was published on July 25.

This approach broadened the management of computers into the management of information and services. Agencies were expected to connect technology choices with their missions, examine work processes, and plan investments accordingly. A faster computer was useful only if the resulting system helped the agency do its job. Section 8b, which addressed information systems and technology, became an important part of that connection between spending and performance.

The Paperwork Reduction Act supplied OMB’s information-management responsibilities. The Computer Security Act remained part of the security framework, while the Government Performance and Results Act reflected a wider emphasis on agency goals and results. Together, this legal setting encouraged agencies to think about the purpose and performance of their systems as well as their equipment. Congress would strengthen technology-investment responsibilities further in the 1995 Paperwork Reduction Act and the 1996 Clinger–Cohen legislation.

NIST’s technical standards program continued alongside these management changes. FIPS 140-1, approved in January 1994, set security requirements for cryptographic modules—the hardware or software components that perform encryption and related functions. Its authority came from the federal standards and computer-security laws. OMB’s revision addressed the agency decisions surrounding technology; NIST and Commerce supplied standards for particular technical uses. The next major A-130 revision, in 1996, would turn directly to security management and replace the older security appendix.

Sources and edition notes 910

Official source · Download original · Extracted text

1996 · Making managers responsible for security risk

By 1996, federal computing had spread beyond central facilities into networks, desktop systems, and connected applications. OMB rewrote A-130’s security appendix for that environment. The revision, dated February 8 and published on February 20, placed responsibility on managers to understand their systems’ risks and provide appropriate protection.

The Computer Security Act and the Paperwork Reduction Act of 1995 were central to the update. OMB incorporated the security-planning instructions it had issued in Bulletins 88-16 and 90-08. Agencies still needed security plans, staff training, contingency arrangements, and reviews, but they no longer had to follow the same centralized process for submitting plans. The appendix distinguished shared computing environments, called general support systems, from major applications with their own particular risks.

Managers also had to authorize systems to operate. This meant accepting responsibility for the risks of using a system after considering its protections. Security plans and reviews supported that decision. OMB retained the duty to assess risk while allowing more flexibility in how agencies did so; a formal numerical risk analysis was no longer required for every system. Rules of behavior made employees’ responsibilities part of the security program.

“security commensurate with the risk and magnitude of the harm”

A-130: Transmittal 3, 1996-02-0811

NIST’s work helped shape this approach. OMB drew on the computer-security handbook’s discussion of policies for individual systems. NIST’s 1998 security-planning guide, SP 800-18, then gave agencies practical help with the circular’s planning requirements. Technical guidance and management policy developed together.

Clinger–Cohen became law on February 10, between the revision’s date and its publication. OMB’s accompanying explanation anticipated further technology-management guidance. The February revision’s main change was already clear: agency managers were responsible for choosing safeguards, preparing staff, reviewing security, and accepting the risks of operating their systems.

Sources and edition notes 1213

Official source · Download original · Extracted text

2000 · Building security into technology investment

The 2000 revision brought A-130 into line with the technology-management reforms of the late 1990s. Clinger–Cohen had strengthened agency responsibility for choosing and overseeing investments and established a larger role for chief information officers. OMB’s November 28 update connected those responsibilities with the circular’s existing policies for information and security. The final notice appeared on December 12.

Agencies were expected to plan their technology investments, compare choices, and monitor results. They also needed an enterprise architecture: a description of how their information, systems, and business processes fit together. These requirements aimed to make individual purchases serve the agency’s wider mission. Chief information officers helped connect technical decisions with budgets and management priorities.

Security became an explicit part of investment decisions. Earlier that year, memorandum M-00-07 had instructed agencies to include security planning and costs in information-system investments. OMB incorporated that guidance into A-130. Agencies therefore needed to account for protection when planning and funding a system, including the continuing costs of operating it securely. This gave security a place in the same decisions that determined a system’s purpose, design, and resources.

The Government Paperwork Elimination Act of 1998 added another task: expanding electronic transactions. OMB incorporated its implementation guidance as Appendix II, covering electronic records and signatures. Agencies had to consider the risks of a transaction when deciding how to handle it electronically.

The wider security framework continued to change while this edition remained in use. The Government Information Security Reform Act of 2000 introduced security-program and reporting duties. The Federal Information Security Management Act of 2002, known as FISMA, then assigned NIST work on risk categories and minimum security requirements. Agencies used the resulting standards alongside the 2000 circular until OMB comprehensively rewrote A-130 in 2016.

Sources and edition notes 1415

Official source · Download original · Read formatted text

2016 · Managing security and privacy throughout a system’s life

OMB comprehensively rewrote A-130 in July 2016 after sixteen years of changes in law, technology, and government services. Agencies were using interconnected systems and commercial services to deliver more of their work. The new circular brought security and privacy into decisions throughout a system’s life, from planning and purchasing to operation and retirement.

The revised title, Managing Information as a Strategic Resource, reflected this broader purpose. Information supported public services, accountability, and agency performance. Protecting it required coordination among leaders, technology staff, privacy officials, purchasing teams, and the people responsible for agency programs. Security and privacy needed attention while systems were being designed and acquired, as well as after they began operating.

“Federal information is both a strategic asset and a valuable national resource.”

A-130: Managing Information as a Strategic Resource, 2016-07-2816

The legal framework included the Paperwork Reduction Act, Clinger–Cohen, the E-Government Act, and FISMA. The 2014 Federal Information Security Modernization Act had updated the division of security responsibilities among OMB, the Department of Homeland Security, and agencies. The circular connected those responsibilities with NIST’s established standards and guidance for assessing risks, selecting safeguards, authorizing systems, and monitoring their operation.

OMB also reorganized the appendices. Appendix I covered protection and management of federal information resources; Appendix II covered personally identifiable information and agency privacy programs. Privacy received attention throughout the information life cycle, including the risks arising from how agencies collected and used information. Agency responsibilities extended to information handled on their behalf, and the circular expressly addressed cloud-based services.

NIST later updated its Risk Management Framework in SP 800-37 Revision 2 to integrate security and privacy more closely. OMB continued issuing memoranda on particular subjects, including identity, cloud services, software security, and zero trust—a security approach that checks access rather than assuming a user or device is trusted because it is inside a network.

Sources and edition notes 1718

Official source · Download original · Read formatted text

Who is responsible for each part of security?

Responsibility varies by subject. A-130 provides much of the management framework, while laws and presidential directives also assign work directly to NIST and other agencies.

Agency planning and accountability

OMB connects security with agency management.

A-130 brings security into budgets, investment decisions, staff responsibilities, and the planning and operation of systems. The Paperwork Reduction Act and FISMA give OMB and agency heads the underlying duties. NIST supplies technical methods that help agencies carry them out.19

Security categories and minimum safeguards

Congress assigned the technical work to NIST.

FISMA 2002 directed NIST to develop categories based on the harm a security failure could cause, along with minimum security requirements. FIPS 199 and FIPS 200 put those assignments into standards. Agencies use them with SP 800-53 to choose safeguards; A-130 incorporates their use into agency management.20

Deciding whether a system may operate

Agency officials accept risk; NIST provides a method.

The 1996 circular required management authorization and security reviews. NIST’s SP 800-37 later developed the Risk Management Framework, a process for selecting, assessing, and monitoring safeguards. The agency official responsible for authorization decides whether the remaining risk is acceptable.21

Encryption

NIST develops standards; OMB directs agency adoption.

Federal encryption standards began before A-130. NIST and Commerce continued that work under computer-security and standards legislation. More recently, the Quantum Computing Cybersecurity Preparedness Act assigned OMB migration duties linked to NIST standards designed to resist attacks using quantum computers.22

Identity and access

Presidential directives and OMB memoranda set specific tasks.

A 2004 presidential directive required a common identification standard for federal employees and contractors, leading to FIPS 201. Separately, OMB’s M-04-04 directed NIST to develop guidance for electronic authentication—checking that someone accessing an online service is who they claim to be.23

Contractors handling sensitive information

Requirements depend on the work and the agreement.

A-130 covers federal information handled on an agency’s behalf. A separate program governs controlled unclassified information, or CUI: information that needs safeguards under law or policy but is not classified. NIST’s SP 800-171 provides requirements for protecting CUI in nonfederal systems; applicable regulations and agreements determine a contractor’s obligations.24

Cloud services and FedRAMP

A shared assessment program supports agency decisions.

The 2011 FedRAMP memorandum established a common approach to assessing cloud services. Congress put the program into law in 2022, using A-130’s authorization terminology and NIST’s definition of cloud computing. OMB’s M-24-15 updated the program’s scope and responsibilities in 2024 and replaced the 2011 memorandum.25

National-security systems

A separate set of rules applies.

A-130’s 2016 scope provision excludes national-security systems from mandatory application of the circular. Agencies follow the statutes, executive orders, directives, and agency policies applicable to those systems. FISMA also gives these systems separate treatment.26

When technical guidance becomes a requirement

A NIST publication becomes a requirement for a particular use through the authority that adopts it. That may be a federal standard, an OMB policy, a regulation, or a contract. Agency officials remain responsible for carrying out the duties assigned to them by law and policy. This is why the technical standard and the agency instruction often need to be read together.27

How the technical standards developed

Early guidance: protecting facilities and keeping services running

Before A-130, the National Bureau of Standards published guidance on physical security and risk analysis in FIPS 31 and FIPS 65. Its 1982 contingency-planning guide helped managers prepare for computer disruptions and meet the responsibilities introduced under A-71. The Data Encryption Standard supplied a separate technical tool for protecting information.28

Turning security policy into practical plans

NIST’s computer-security handbook, SP 800-12, explained management and technical practices. OMB drew on it when revising the security appendix in 1996. SP 800-18 then explained how to write the security plans A-130 required. SP 800-30 developed guidance for assessing risk, helping agencies identify threats and choose protections.29

From the consequences of a failure to the choice of safeguards

FISMA gave NIST a sequence of technical tasks. FIPS 199, issued in 2004, classifies information and systems by the potential harm from a security failure. FIPS 200, issued in 2006, sets minimum requirements and directs agencies to choose controls—specific safeguards—from SP 800-53. The control catalog has expanded over time: Revision 4 added a privacy appendix, while Revision 5 integrated security and privacy controls. SP 800-53B supplies the baseline sets from which agencies begin selecting controls.30

Assessing risk throughout a system’s life

The first SP 800-37, published in 2004, described certification and accreditation: evaluating safeguards and approving a system’s operation. The 2010 revision placed those activities within a Risk Management Framework covering the system’s life cycle. The 2018 revision added organizational preparation and integrated privacy responsibilities. SP 800-137 supports the continuing monitoring needed to understand how risks and safeguards change after a system begins operating.31

Encryption and the move toward quantum-resistant standards

The 1977 Data Encryption Standard was an early federal encryption standard. Later publications addressed both encryption methods, such as the Advanced Encryption Standard in FIPS 197, and the security of cryptographic hardware and software through the FIPS 140 series. In 2024, NIST published FIPS 203, 204, and 205 for cryptography designed to withstand quantum-computing attacks. The 2022 quantum-preparedness law linked OMB’s migration instructions to NIST standards; M-26-15 set further migration policy in June 2026.32

Proving identity in person and online

Homeland Security Presidential Directive 12, issued in August 2004, called for a common identification standard for federal employees and contractors. FIPS 201 followed in 2005. OMB’s M-04-04 addressed a different need: assessing the identity checks required for electronic services. It directed NIST to develop technical guidance, which became SP 800-63. Later editions updated digital-identity practices, while M-19-17 revised agency identity and access policy in 2019.3334

Cloud services, contractor systems, and newer security practices

NIST’s 2011 cloud publications defined cloud computing and explained the security and privacy issues agencies faced when using public cloud services. SP 800-171 later addressed sensitive unclassified information in nonfederal systems. SP 800-207 described zero-trust architecture in 2020; subsequent presidential and OMB policy directed agencies to adopt that approach. SP 800-218 supplied a framework for secure software development, supporting the software-security work ordered in Executive Order 14028. OMB memoranda M-22-18 and M-23-16 applied that work to federal software purchases.35

How OMB policy changed between revisions

OMB updates agency instructions between major revisions of A-130 through memoranda. Some respond to new laws; others address a particular technology or management problem. Annual instructions tell agencies how to report on their security and privacy programs. Together, these documents explain how the broad responsibilities in the circular become specific agency tasks.

Some memoranda later became part of A-130 itself. M-95-22 explained the 1995 Paperwork Reduction Act’s public-information provisions, and OMB incorporated it into the 1996 explanatory appendix. M-00-07 required agencies to plan and fund security as part of technology investments; the 2000 revision incorporated that instruction. Other memoranda assigned technical work directly, as M-04-04 did when it asked NIST to develop electronic-authentication guidance.

Cloud policy followed a similar pattern. OMB established FedRAMP through a memorandum in December 2011. Congress enacted the FedRAMP Authorization Act in 2022, and OMB issued M-24-15 in 2024 to update the program. That memorandum replaced the 2011 instructions.

Policies also change through withdrawal or replacement. M-19-17 replaced several earlier identity instructions. M-17-26 withdrew some policies while modifying or pausing others. The library identifies these changes where the successor document records them.36

Source library

Find a document by title, subject, or phrase. Use the filters to narrow the list by date, document type, or relationship to A-130.

178 documents

1965-03-06Predecessor / bulletin

A-71: ADP management responsibilities

Later adopted in policy

Divided responsibility for federal computing among agencies, the Bureau of the Budget, the General Services Administration, and Commerce. It preceded the broader information-management framework in A-130.

Source details and edition

Historical edition

§4.6 reproduces original A-71

Date supplied by the source

Reproduced in FIPS 12, §4.6, PDF pages 34–37.

Reproduced in FIPS 12

Assigned by law

Gave Commerce responsibility for federal computer standards and technical services, establishing a statutory foundation for the standards program that later became NIST’s.

Source details and edition

Historical edition

§111, especially (f)

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 639408 bytes

SHA-256 checksum

a992b1d3d55cbe891c24e80543dc59470088e6d10e3e4d2f02af40832485351b

Guidance for implementation

Collected early federal computer standards and policies. Section 4.6 reproduces the 1965 A-71 circular and its division of agency responsibilities.

Terms found: related terminology
related terminology · PDF page 28

by Government con- tractors solely to process Government data at Government expense (e.g., Government- owned, contractor-operated facilities). These policies do not apply to ADP equipmert acquired by universities and similar institutions with financial assistance through grants- in-aid of Government funds. The policy provisions of this C

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§4.6: March 6, 1965 A-71 reproduction

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 3915472 bytes

SHA-256 checksum

6e67efbdc85e9bbdaebce936ace4196e0ae092f75f7517bc6c68c4d2ffcbeb5f

Guidance for implementation

Explained how agencies could protect computer facilities and manage physical risks, providing security guidance more than a decade before A-130.

Source details and edition

Withdrawn February 8, 2005; NIST historical withdrawal index.

Foreword; physical security guidance

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 7163308 bytes

SHA-256 checksum

683b51795e3ddc0c07bf50a5a151bcbc09729fde1561bf2a8e6f6254764c6346

Assigned by law

Required safeguards for federal records about individuals and assigned OMB implementation guidance. Its protections became a foundation for A-130’s privacy provisions.

Source details and edition

Historical edition

§3: 5 USC 552a(e)(10); §6 OMB guidance

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 2878782 bytes

SHA-256 checksum

e7ee29d2c9d09b077dc356a4583a4a008621dce40b0f23fd51e19b5368815d4a

Assigned by law

Established the Data Encryption Standard in 1977, an early example of the federal technical standards program. Its withdrawal history is recorded in the source details.

Source details and edition

Original edition withdrawn January 22, 1988; later DES edition FIPS 46-3 withdrawn May 19, 2005.

Authority and applicability

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1609953 bytes

SHA-256 checksum

a1c85b29aab88d505c33ab30988794a824e90be521fd535bbaefaac9b3935404

Later adopted in policy

Added security responsibilities for federal automated information systems to A-71. OMB later carried this work into A-130’s security appendix.

Source details and edition

Historical edition

Supplementary information: predecessor expressly identified

Date supplied by the source

A standalone copy is unavailable in this collection. The linked 1996 OMB preamble describes this document and its later incorporation into A-130.

Original unavailable in this collection

Guidance for implementation

Provided a method for analyzing the risks to automated data-processing systems, helping agencies assess potential losses and choose safeguards.

Source details and edition

Withdrawn August 25, 1995; NIST historical withdrawal index.

Introduction and authority

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 1945125 bytes

SHA-256 checksum

d417886c3c192560d908d77a86f5a435785d1947601689e541addbcab8e1cc8b

Assigned by law

Gave OMB government-wide information-management responsibilities. A-130 used this framework to connect information policy, technology, privacy, and records management.

Terms found: related terminology
related terminology · PDF page 2

f the territories and possessions of the United States, and their various subdivisions, or Government-owned contractor-operated facili­ ties including laboratories engaged in national defense research and production activities; "(2) the terms 'automatic data processing,' 'automatic data processing equipment,' and 'telecommunications

Extracted text; not checked against the page image.
Source details and edition

Historical edition

44 USC 3504, 3506 as enacted

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 2707905 bytes

SHA-256 checksum

5af687ae7085e87b72357c4ef3969bfa4388bddb179c76363ec7d49759036299

Guidance for implementation

Explained contingency planning for managers who depended on computer services. It helped agencies prepare for disruptions and comply with A-71’s security instructions.

Source details and edition

Historical edition

Abstract; A-71 compliance

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 602785 bytes

SHA-256 checksum

5f1783deca7749c79547cfee6f9339d8ed3996ebb2f68c3d119b80a791e25782

1985-12-12OMB circular

A-130: initial circular

Assigned by law

Combined information policy, computer management, privacy, records, and security in one circular. Appendix III assigned agencies responsibility for security programs, risk analysis, reviews, and contingency planning.

Terms found: related terminology
related terminology · PDF page 290

y statement 8a(2) reflects the existence of such conditions. Many also commented on the phrhse “or through commercial sources” in this statement. The revision qualifies this .phrase and Appendix IV provides further explanatory analysis of the policy. (3) through (6). Privacy Act and Freedom of Information Act. OMB revised sta

Extracted text; not checked against the page image.
Source details and edition

Amended by Transmittals 1–4.

50 FR 52730–52751; published December 24; effective December 12

Date supplied by the source

The PDF contains the full Federal Register issue. A-130 occupies PDF pages 288–309 (printed pages 52730–52751); the reading excerpt covers those pages only.

Text extracted from a scan; transcription errors are possible.

Downloaded 2026-10-10 · 54429790 bytes

SHA-256 checksum

c6c996a0a79cfbae6c9220153a4d019871ee22bf0930fd180c70055cffe7b784

Assigned by law

Assigned security standards and guidance work to the National Bureau of Standards and required agency security planning and training. OMB implemented these duties through bulletins and the 1996 security appendix.

Source details and edition

Historical edition

§§2–6; NBS functions, standards and agency plans

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1273575 bytes

SHA-256 checksum

2eb2c0cdd6d2bbf652b358266e98be07fdb2b52526554aded1f90bb0a5238fd0

1988-07-06Predecessor / bulletin

OMB Bulletin 88-16: submission of security plans

Later adopted in policy

Instructed agencies to submit security plans following the Computer Security Act. OMB incorporated and replaced it in the 1996 revision of A-130.

Source details and edition

Historical edition

Supplementary information: title, date and supersession

Date supplied by the source

A standalone copy is unavailable in this collection. The linked 1996 OMB preamble describes this document and its later incorporation into A-130.

Original unavailable in this collection

Later adopted in policy

Provided instructions for preparing security plans under the Computer Security Act. The 1996 A-130 revision incorporated and replaced this bulletin.

Source details and edition

Historical edition

Supplementary information: title, date and supersession

Date supplied by the source

A standalone copy is unavailable in this collection. The linked 1996 OMB preamble describes this document and its later incorporation into A-130.

Original unavailable in this collection

1993-06-25OMB circular

A-130: Transmittal 1

Assigned by law

Updated information collection, public access, records management, and privacy policy. It left the security appendix unchanged while OMB prepared further technology and security revisions.

Terms found: related terminology
related terminology · HTML body

to satisfy new information needs through interagency or intergovernmental sharing of information, or through commercial sources, where appropriate, before creating or collecting new information; (e) Integrate planning for information systems with plans for resource allocation and use, including budgeting, acquisition, and use of infor

Extracted text; not checked against the page image.
Source details and edition

Historical amendment; later editions contain further changes.

Sections 3, 8a; Appendix I; 58 FR 36068, July 2

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 143603 bytes

SHA-256 checksum

b394b7885e2a250a20af528c2c032bc8a749987bc7346c0f3bf385f00b05e270

Assigned by law

Established security requirements for cryptographic modules, the hardware and software that carry out encryption and related functions.

Source details and edition

Historical edition

Foreword; authority; superseded by 140-2

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 2204811 bytes

SHA-256 checksum

73a3af007191e3fb027993cfc9f93eddcc3295bb290ed55f8fe333711bf49e15

Assigned by law

Connected technology investments with agency missions, service quality, and performance. The revision focused on information systems and technology management in section 8b.

Terms found: related terminology
related terminology · HTML text

h those governments as appropriate; (d) Seek to satisfy new information needs through interagency or intergovernmental sharing of information, or through commercial sources, where appropriate, before creating or collecting new information; (e) Integrate planning for information systems with plans for resource allocation and use, including budgeting, acquisition, and use of information technology; (

Text-search result; not checked against the page image.
Source details and edition

Historical amendment; later editions contain further changes.

59 FR 37906–37928; July 25 publication

effective date; Federal Register publication July 25, 1994

Original notice supplied as HTML. The printed citation is 59 FR 37906–37928; the archive labels it “Page 0.”

Searchable text

Downloaded 2026-10-10 · 169523 bytes

SHA-256 checksum

846771a88c3cd134ed19a8ae2ecce7ad1067668e600909377b92cfaece6b9c9d

Assigned by law

Updated OMB and agency responsibilities for managing information, including public access and information resources. The 1996 A-130 revision reflected these changes.

Terms found: related terminology
related terminology · PDF page 3

e territories and possessions of the United States, and their various subdivisions; or ``(D) Government-owned contractor-operated facilities, including laboratories engaged in national defense research and production activities; ``(2) the term `burden' means time, effort, or financial resources expended by persons to generate, maintain,

Extracted text; not checked against the page image.
Source details and edition

Historical edition

44 USC 3504, 3506

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 216505 bytes

SHA-256 checksum

364b71f86413ba4424bba70125e51c983ea77d6c7d2d7aa7e62377520daddda9

Directed by OMB

Explained how agencies should implement the 1995 Paperwork Reduction Act’s public-information provisions. OMB later incorporated this guidance into A-130’s explanatory appendix.

Passage mentioning A-130

licies governing Federal agency dissemination of public information. Section 3506(d) of the PRA codifies the information policy provisions of OMB Circular No. A-130. The attached Memorandum from the Administrator of the Office of Information and Regulatory Affairs reviews some of the major information policy provisions of the PRA and provides guidance as to their implementation. Agencies should consider this guidance as they review their information dissemination practices for compliance with the PRA and Circular A-13

HTML body; first A-130 reference

Source details and edition

Current applicability not assessed

HTML body; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 22488 bytes

SHA-256 checksum

7eac80e1ad2cb37c686333d57ef159f346749a0b04d79ed4f1b71bc1ecf3eeb4

Later adopted in policy

Introduced computer-security management and technical practices. OMB drew on the handbook when explaining its 1996 security-policy changes.

Source details and edition

Withdrawn June 21, 2017, superseded by SP 800-12 Rev. 1; withdrawal recorded on the archived PDF cover.

Chapters 1–3; 1996 A-130 preamble cites earlier handbook

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 17862415 bytes

SHA-256 checksum

95e40613ce281a74e88e883fce52f89f74ca3bca1d86fee9a2cc310f14e4f825

1996-02-08OMB circular

A-130: Transmittal 3

Assigned by law

Rewrote the security appendix for interconnected systems. It emphasized management accountability, security plans, staff responsibilities, reviews, and authorization to operate.

Terms found: related terminology
related terminology · HTML body

to satisfy new information needs through interagency or intergovernmental sharing of information, or through commercial sources, where appropriate, before creating or collecting new information; (e) Integrate planning for information systems with plans for resource allocation and use, including budgeting, acquisition, and use of infor

Extracted text; not checked against the page image.
Source details and edition

Historical consolidated text; amended in 2000 and replaced in 2016.

Appendix III; February 20 publication, 61 FR 6428

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 211091 bytes

SHA-256 checksum

906a73bd9b77740b0ed2bfc6f2201ec33363e2a04def3f3108fc7aecc146c4b6

Assigned by law

Reformed federal technology investment and strengthened the role of chief information officers. These management responsibilities were central to the 2000 A-130 update.

Terms found: related terminology
related terminology · PDF page 471

, notwithstanding this section, such provision of law shall be applicable to contracts for the procurement of commercial off-the-shelf items. ``(c) D EFINITION.Ð(1) As used in this section, the term `commer- cially available off-the-shelf item' means, except as provided in paragraph (2), an item thatÐ ``(A) is a commercial item (as described

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Division E, §§5112–5113, 5125, 5131

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1832242 bytes

SHA-256 checksum

60ecc3db67b9a71474f8e11cb310d1d86f8246fc9df154b31f93801dbe786c7e

Assigned by law

Published the revised security appendix and OMB’s explanation of its decisions, including responses to public comments.

Terms found: related terminology
related terminology · PDF page 1

y different. It is characterized by open, widely distributed processing systems which frequently operate with commercial off-the-shelf software. While effective use of information technology often reduces risks to the Federal program being administered (e.g., risks from fraud or errors), the risk to and vulnerability of Federal information re

Extracted text; not checked against the page image.
Source details and edition

Historical edition

61 FR 6428

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 300014 bytes

SHA-256 checksum

86aae370d573c8d3e7aebddc8b629eda764043768bee8835f9bb8cccc4a5f0c5

Later adopted in policy

Explained why OMB changed its security policy in 1996, including more flexible risk analysis and the use of NIST guidance.

Terms found: related terminology
related terminology · HTML body

rent. It is characterized by open, widely distributed processing systems which frequently operate with commercial off-the-shelf software. While effective use of information technology often reduces risks to the Federal program being administered (e.g., risks from fraud or errors), the risk to and vulnerability of Federal

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Background; responses 5–6; supersession of Bulletins 88-16 and 90-08

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 27650 bytes

SHA-256 checksum

3403e89e6ce8d82f70158f2cda93db6ab9085ac068c069a005efd3d589ae64be

Directed by OMB

Gave agencies initial instructions for implementing the 1996 technology-management law, including the designation of chief information officers and changes to the General Services Administration’s role.

Passage mentioning A-130

his memorandum, OMB Circulars will be revised to provide further guidance to agencies. OMB will seek agency and public comment of draft revisions to Circul ar A130, "Management of Federal Information Resources," so that these revisions will be final by early August 1996. In addition, OMB Circular A-l l, "Preparation and Submission of Budget Estimates," will be revised as part of the annual update of that Circ ular. Agency Chief Information Officers Section 5125(a) of ITMRA amends Section 3506 of the Paperwork Re

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 55043 bytes

SHA-256 checksum

168235fff34cf582fa523ce0dbd2bb55c473b46e3a286e77827945b2c3364f43

Directed by OMB

Set criteria for evaluating major information-system investments in the federal budget, connecting proposed spending with agency plans and mission goals.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 43621 bytes

SHA-256 checksum

e3abd1f5b5e86ea53ed5eda1453c55660efe4b899e702abad08148be6ada4e1e

Directed by OMB

Established a way for agencies to jointly support interagency groups advising OMB on technology management under Clinger–Cohen.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 39328 bytes

SHA-256 checksum

f5c9c836f5ce5954f10f277d1ac716ebce6118ab85aaa8d96f2ef898cc221f24

Directed by OMB

Directed agencies to prepare plain-language guides explaining how the public could find and request government information. It connected those guides with A-130’s public-access policies.

Passage mentioning A-130

categories of information available. In preparing the document, each agency should review the dissemination policies and practices set out in OMB Circular No. A130, "Management of Federal Information Resources." The document should be in plain English and user-friendly. Where applicable, it should indicate that the public is encouraged to access information electronically via the agency's home page or to search in its reading room, and that the public may also submit a request to the agency under the Freedom of Inform

HTML body; first A-130 reference

Source details and edition

Current applicability not assessed

HTML body; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 4909 bytes

SHA-256 checksum

8f7d24961a677bb46f85c217b99dc3d0367a272c9d2d9eee25586302653ca661

Directed by OMB

Set policy for agencies acquiring and managing local telecommunications services under the 1996 technology-management law.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 50533 bytes

SHA-256 checksum

1586edb0436ac0cce0aec489d1586ddd358926e428af742c02cce5a634f0cc41

Directed by OMB

Explained how agencies should describe the relationships among their work, information, and technology. These architectures were intended to guide investments and improve information sharing.

Passage mentioning A-130

gement processes and information technology that ensure: • alignment of the requirements for agency-sponsored information systems (as defined in OMB Circular A- 130) with the processes that support the agency's missions and goals; • adequate interoperability, redundancy, and security of information systems; and, • the application and maintenance of a collection of standards by which the agency evaluates and acquires new systems. [PDF page 2] Agencies should be prepared to indicate the status of the development, im

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 105313 bytes

SHA-256 checksum

70ca5ee09546312fe78035529e631cc0de9ca6370dba4a83ff6785ae5d9e8156

Directed by OMB

Explained how the Government Information Locator Service could help people find federal information, supporting A-130’s public-access responsibilities.

Passage mentioning A-130

h aspects of the Federal Records Act (44 U.S.C. 3301) and the Freedom of Information Act as amended in 1996 (5 U.S.C. 552). Policies such as OMB Circular No. A-130, "Management of Federal Information Resources" (61 F.R. 6428, February 20, 1996) also describe agency responsibilities to help the public locate government information and to ensure management and accountability of agency programs. OMB Bulletin 95-1, "Establishment of Government Information Locator Service," which guided the initial startup of GILS, has

HTML body; first A-130 reference

Source details and edition

Current applicability not assessed

HTML body; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 3361 bytes

SHA-256 checksum

9a98bf1ccefeab8724dccfe13490ff3a06b2e69bf2a037b341189d7dfb32ee27

Guidance for implementation

Translated A-130’s security-planning responsibilities into practical guidance for documenting a system’s protections and management responsibilities.

Source details and edition

Historical edition

Introduction; A-130 Appendix III

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 5969905 bytes

SHA-256 checksum

a7c6fce03eba611fd29dc3825376e49f32ff7d29a14f16541daf96889ca7ea60

Directed by OMB

Applied existing security obligations to technology-investment decisions, including planning and funding. OMB incorporated this guidance into A-130 later in 2000.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 52960 bytes

SHA-256 checksum

1afe65004fc84798d544724049618088be403d536312d573d4f044d9242771cb

Related development

Proposed changes to technology investment, management, and electronic-transaction policy. OMB issued the final revision in November 2000.

Terms found: related terminology
related terminology · PDF page 5

ter match mission need with current technology and market conditions; (c) Acquire off-the-shelf software from commercial sources, unless the cost effectiveness of developing custom software is clear and has been documented through pilot projects or prototypes; and (d) Ensure accessibility of acquired information technology pursuant to t

Extracted text; not checked against the page image.
Source details and edition

Historical edition

65 FR 19933–19941

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 249152 bytes

SHA-256 checksum

11a9a1fe028a311f67ab14ddccf94cfd90cf110da83b88c3461b70e293595d5f

Later adopted in policy

Explained how agencies should implement electronic records and signatures under the Government Paperwork Elimination Act. OMB incorporated it as A-130 Appendix II in 2000.

Source details and edition

Historical edition

65 FR 25508–25521 (May 2, 2000); incorporated by Transmittal 4

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 102509 bytes

SHA-256 checksum

3187590255137edc831976321cbf1da05975962b6e351fb485e99fbeed092ca7

Assigned by law

Established a time-limited framework for agency security programs, evaluations, and reporting. OMB issued implementation and reporting instructions after its enactment.

Terms found: related terminology
related terminology · PDF page 20

pile stewardship and security. Sec.3196.Cooperative research and development agreements for government-owned, contractor-operated laboratories. Sec.3197.Office of Arctic Energy. TITLE XXXII— DEFENSE NUCLEAR FACILITIES SAFETY BOARD Sec.3201.Authorization. TITLE XXXIII— NATIONAL DEFENSE STOCKPILE Sec.3301.Authorized uses of stockpile funds

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Title X, Subtitle G, §§1061–1065

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1575303 bytes

SHA-256 checksum

931a74e24e0288af43250e5e5d32c5c456c119904c08a6da4d87cb2adc0e41f8

Assigned by law

Updated investment planning, technology architecture, chief information officer responsibilities, and electronic transactions. It brought security planning and costs into investment decisions.

Terms found: related terminology
related terminology · PDF page 7

to satisfy new information needs through interagency or intergovernmental sharing of information, or through commercial sources, where appropriate, before creating or collecting new information; (e) Integrate planning for information systems with plans for resource allocation and use, including budgeting, acquisition, and use of i

Extracted text; not checked against the page image.
Source details and edition

Replaced by 2016 A-130; PDF contains main circular, appendices listed separately.

Sections 3, 8b, 9; Appendices III–IV

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 330615 bytes

SHA-256 checksum

51408f42212316a9e92c2b4ed3bfe4299768afd150280322096ed97e8caccb82

2000-11-28OMB circular

A-130 (2000), Appendix I

Later adopted in policy

Set out agency responsibilities for records about individuals, linking A-130’s information-management policy with Privacy Act protections.

Source details and edition

Historical edition

Archived appendix text linked with Transmittal 4

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 41058 bytes

SHA-256 checksum

06be1352240778096615233a0878cdd5f23c9ff8b0278c816c950a576f874bd9

2000-11-28OMB circular

A-130 (2000), Appendix II

Later adopted in policy

Provided guidance on electronic records and signatures under the Government Paperwork Elimination Act.

Source details and edition

Historical edition

Archived appendix text linked with Transmittal 4

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 108301 bytes

SHA-256 checksum

fb19eaffb736eef46880b90ecdc6162b94ce0d678ec8a9a76ff40f77d2617e09

2000-11-28OMB circular

A-130 (2000), Appendix III

Later adopted in policy

Set out security responsibilities for federal automated information resources, including plans, training, reviews, and management authorization.

Source details and edition

Historical edition

Archived appendix text linked with Transmittal 4

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 59930 bytes

SHA-256 checksum

9b2406bfb6d36800fea1c38a361b17819c2adab4e45b5c4d14070ae512f29a74

2000-11-28OMB circular

A-130 (2000), Appendix IV

Later adopted in policy

Explained the reasoning behind key provisions of A-130 and their relationship to other information-management policies.

Source details and edition

Historical edition

Archived appendix text linked with Transmittal 4

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 83284 bytes

SHA-256 checksum

dec37813f1c79ee93e2cf259690af4243f274a6f4643bcdbe6b283d3692a5ca3

Assigned by law

Announced the final 2000 revision and explained OMB’s decisions after public comment, including its incorporation of earlier investment and security guidance.

Terms found: related terminology
related terminology · PDF page 8

ter match mission need with current technology and market conditions; (c) Acquire off-the-shelf software from commercial sources, unless the cost effectiveness of developing custom software is clear and has been documented through pilot projects or prototypes; and (d) Ensure accessibility of acquired information technology pursuant to t

Extracted text; not checked against the page image.
Source details and edition

Historical edition

65 FR 77677–77687

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 258362 bytes

SHA-256 checksum

88f92a0f399e62699c4f7693ea262c4a0d87cb32aff430e9d8fbc8993c5cd1f9

Directed by OMB

Explained the Government Information Security Reform Act’s new program, evaluation, and reporting duties and how they related to existing A-130 security requirements.

Passage mentioning A-130

the role of the agency Inspector General, and the annual reporting requirement, the Security Act essentially codifies the existing requirements of OMB Circular A-130, Appendix III, "Security of Federal Automated Information Resources." The Security Act also requires agencies to incorporate security into the life cycle of agency information systems. For guidance on meeting this requirement, see OMB Memorandum 00-07, "Incorporating and Funding Security in Information Systems Investments," now incorporated into Section 8

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 30010 bytes

SHA-256 checksum

5225f3328f1208b59e36d79908a78e02e64ae2139f98c4724eeb43bc1063569b

Assigned by law

Updated requirements for the security of cryptographic hardware and software modules, continuing the FIPS 140 standards series.

Source details and edition

Historical edition

Foreword; authority; superseded by 140-3

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1466246 bytes

SHA-256 checksum

0df0fdd676df643874adfbbf767b8508af3cc6520aff5cfef7d39428e1c63cd4

Directed by OMB

Set reporting instructions for agency security programs under the Government Information Security Reform Act for the 2001 reporting cycle.

Passage mentioning A-130

valuation aspects of the security of unclassified and national security systems. Generally, the Security Act codifies existing OMB security policies, Circular A-130, Appendix III, and reiterates security responsibilities outlined in the Computer Security Act of 1987, the PRA, and the Clinger-Cohen Act of 1996. In addition, the Security Act requires annual agency program reviews and annual independent evaluations for both unclassified and national security programs. On January 16, 2001, OMB issued memorandum 01-08, g

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 14034 bytes

SHA-256 checksum

e1c14b97e6bd8c7a4aaaa782d4d3e41574a5e31d88be06b1947c133ea10231f3

Directed by OMB

Explained how agencies should document security weaknesses, planned corrective actions, and milestones for completing the work.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 114958 bytes

SHA-256 checksum

b0a4390ecd6f863e283d35e0ec9795a070e5b824b11d3e42cd735867ae05e22c

Assigned by law

Specified the Advanced Encryption Standard, providing a federal standard for an encryption algorithm used to protect electronic data.

Source details and edition

Historical edition

Authority; algorithm specification

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 631927 bytes

SHA-256 checksum

251dfe0b5dc283abaf364adf586f7ec6dc4e495335d48dd5ee0fee6c5961da8a

Guidance for implementation

Provided a method for assessing and managing information-system risk, including identifying threats, vulnerabilities, and possible safeguards.

Source details and edition

Historical edition

§1.1; A-130 Appendix III

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 3181701 bytes

SHA-256 checksum

04456e1a4555e4ea3649a4f798af696a7eb91e80d2415a0b1e67a7f9e4b396ef

Directed by OMB

Set reporting instructions for agency security programs under the Government Information Security Reform Act for the 2002 reporting cycle.

Passage mentioning A-130

siness purpose for their use. 25 [PDF page 26] ATTACHMENT C Definitions of Key Words Referenced in OMB Guidance Adequate Security (defined in OMB Circular A-130, Appendix III, (A)(2)(a)) Security is commensurate with the risk and magnitude of the harm resulting from the loss, misuse, or unauthorized access to or modification of information. This includes assuring that systems and applications used by the agency operate effectively and provide appropriate confidentiality, integrity, and availability, through the

PDF page 26; first A-130 reference

Terms found: related terminology
related terminology · PDF page 21

up-to-date security plan and NIST guidance. Obtain written auth -- 12/15/01 Yes Ongoing 4 -- System is contractor operated and contract does not include FAR security and privacy clause nor are contractor practices evaluated by agency Program office, contracting officer, and agency CIO None 1/30/02 Identify specific securi

Extracted text; not checked against the page image.
Source details and edition

Rescinded by M-23-03, p. 1.

PDF page 26; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 304532 bytes

SHA-256 checksum

9377dd1250a9da761d4190a48dc8821b2f888df930d9a6af00e3350c0906d4f7

Assigned by law

Established agency information-security duties and directly assigned NIST the development of security categories and minimum requirements. These assignments led to FIPS 199 and FIPS 200.

Source details and edition

Historical edition

Title III; §303 NIST duties; §304 standards

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 311539 bytes

SHA-256 checksum

1eec72dc1f004c04be63c78eb850321592881cbf10bca889301f109dc5c9650e

Directed by OMB

Explained agency responsibilities under the E-Government Act, connecting electronic services and technology investments with existing OMB policies, including A-130.

Passage mentioning A-130

ide initiatives. This guidance also explains, throughout the document, how the E-Government Act fits within existing IT policy, such as OMB Circulars A-11 and A-130. Section I. New E-Gov Act Requirements A. Agency head responsibilities. Agencies are to use the provisions of the E-Government Act and this guidance to interact more successfully with citizens. For example, agencies should continue to use existing guidance, authorities, and procedures 2 to choose IT investments via the agency’s capital planning and in

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 196555 bytes

SHA-256 checksum

64a366b666c574a45e1f7b5e21e848ba2e072384ff52cc70f2ea70e46380995e

Directed by OMB

Set reporting instructions for agency information security programs for the 2003 reporting cycle.

Passage mentioning A-130

ing systems, i.e., Federal security requirements continue to apply and the agency is responsible for ensuring appropriate security controls (see OMB Circular A-130, Appendix III). Finally, because FISMA applies to Federal information (in addition to information systems), in certain limited circumstances its requirements also apply to a specific class of information technology to which Clinger-Cohen did not, i.e., “equipment that is acquired by a Federal contractor incidental to a Federal contract.” Therefore, w

PDF page 5; first A-130 reference

Terms found: related terminology
related terminology · PDF page 27

up-to-date security plan and NIST guidance. Obtain written auth -- 12/15/01 Yes Ongoing 4 -- System is contractor operated and contract does not include FAR security and privacy clause nor are contractor practices evaluated by agency Program office, contracting officer, and agency CIO None 1/30/02 Identify specific securi

Extracted text; not checked against the page image.
Source details and edition

Rescinded by M-17-26, Eliminated – Information Technology.

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 456943 bytes

SHA-256 checksum

5309251f1fd6afcdf11c9d183bc29c998ca86a0cfa0b84898db8369f7c8e9815

Directed by OMB

Explained the E-Government Act’s privacy requirements, including reviews of how new or changed information systems handle personal information.

Passage mentioning A-130

r reception of data or information. d. Major information system - embraces "large" and "sensitive" information systems and means, as defined in OMB Circular A-130 (Section 6.u.) and annually in OMB Circular A-11 (section 300-4 (2003)), a system or project that requires special management attention because of its: (i) importance to the agency mission, (ii) high development, operating and maintenance costs, (iii) high risk, (iv) high return, (v) significant role in the administration of an agency’s programs, finance

PDF page 3; first A-130 reference

Terms found: related terminology
related terminology · PDF page 4

ate, biometric) is newly applied to an electronic information system accessed by members of the public; 6. Commercial Sources - when agencies systematically incorporate into existing information systems databases of information in identifiable form purchased or obtained from commercial or public sources. (Merely querying such a sou

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 164785 bytes

SHA-256 checksum

528c67b7e34daa6093fc9ae947db919e2f06abbd6402ee3d77aeccfd795343c2

2003-12-16OMB memorandum

M-04-04, E-Authentication Guidance

Directed by OMB

Set policy for checking identity in online government services and directed NIST to develop supporting technical guidance. M-19-17 later rescinded it.

Passage mentioning A-130

step of the process influences the technology’s overall conformance to the desired assurance level. [PDF page 3] • This guidance supplements OMB Circular A-130, Management of Federal Information Resources, Appendix II, Implementation of the Government Paperwork Elimination Act (GPEA). • This guidance does not directly apply to authorization. Authorization focuses on the actions permitted of an identity after authentication has taken place. Decisions concerning authorization are and should remain the purview

PDF page 3; first A-130 reference

Source details and edition

Rescinded by M-19-17, rescissions section.

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 128618 bytes

SHA-256 checksum

1deb61aef7fee182c45a361a7a625209993eb5f26697e1dc203504fdc2131900

Assigned by law

Established categories based on the potential harm from a loss of confidentiality, integrity, or availability, carrying out a direct FISMA assignment to NIST.

Source details and edition

Historical edition

Foreword; §§1–3

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 80356 bytes

SHA-256 checksum

73d19f05f71e30f378050f178aa3943c38790bbae56c07f2b5708c5a1a90242f

Guidance for implementation

Explained certification and accreditation: assessing a system’s safeguards and making a management decision about whether it could operate.

Terms found: related terminology
related terminology · PDF page 64

YMS COMMON ABBREVIATIONS CIO Chief Information Officer CNSS Committee for National Security Systems COTS Commercial Off The Shelf DCID Director of Central Intelligence Directive FIPS Federal Information Processing Standard(s) FISMA Federal Information Security Management Act MOA Memorandum of Agreement MOU Memorandum of Understandin

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Authority; introduction

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 734902 bytes

SHA-256 checksum

97f1674500dab05be7fc48c0ef7d90eb44d32bc7c88212dfc9ec27af1add0522

2004-07-01OMB memorandum

M-04-16, Software Acquisition

Directed by OMB

Reminded agencies that software-acquisition decisions should follow technology- and vendor-neutral investment and purchasing policies, including A-130.

Passage mentioning A-130

ies of policies and procedures covering acquisition of software to support agency operations. The Office of Management and Budget (OMB) Circulars A -11 and A-130 and the Federal Acquisition Regulation (FAR), guide agency information technology (IT) investment decisions. These policies are intentionally technology and vendor neutral, and to the maximum extent practicable, agency implementation should be similarly neutral. As this guidance states , all agency IT investment decisions, including software, must be ma

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 38685 bytes

SHA-256 checksum

e4db1495cc05a12d1ba9dd88e25063e4be1d36ad71a8b1975d8ae0d4a41c8b64

Directed by OMB

Set reporting instructions for agency information security programs for fiscal year 2004.

Passage mentioning A-130

ystems. Therefore, Federal security requirements continue to apply and the agency is responsible for ensuring appropriate security controls (see OMB Circular A-130, Appendix III). Finally, because FISMA applies to Federal information (in addition to information systems), in certain limited circumstances its requirements also apply to a specific class of information technology to which Clinger-Cohen did not, i.e., “equipment that is acquired by a Federal contractor incidental to a Federal contract.” Therefore, w

PDF page 5; first A-130 reference

Terms found: related terminology
related terminology · PDF page 18

T guidance. Obtain written auth -- 12/15/04 Yes Ongoing, 1/30/05 4 – Significant Deficiency. System is contractor operated and contract does not include any security and privacy requirements nor are contractor practices evaluated by agency Program office, contracting officer, and agency CIO None 1/30/04 Identify specific

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 276422 bytes

SHA-256 checksum

6e89e7950cae63ee7ca425e55b60061f30f011f1850173681e06dbfd9a8a344b

2004-08-27Executive directive

HSPD-12: Common Identification Standard

Directed by the President

Directed Commerce to develop a common identification standard for federal employees and contractors. FIPS 201 implemented that assignment.

Source details and edition

Historical edition

¶¶2–4: Commerce standard and agency implementation

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 21890 bytes

SHA-256 checksum

a3f7fddc71931f21f7c33d89a82ed844efcdffacf1548a669b19e9a7843d621d

Directed by OMB

Addressed personal use of government computers and the security risks associated with file-sharing technology.

Passage mentioning A-130

training must train employees on agency personal use policies and the prohibited improper uses of file sharing. Training must be consistent with OMB Circular A-130, appendix III paragraph (3)(a)(b) which states agencies must "ensure that all individuals are appropriately trained in how to fulfill their security responsibilities […]. Such training shall assure that employees are versed in the rules of t he system, be consistent with guidance issued by NIST and OPM, and apprise them about available assistance and te

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 45252 bytes

SHA-256 checksum

647d912c809643ebb903ddd20b38887a7fac2ac04d0a564153b72f6cae61c5a2

Directed by OMB

Provided technical guidance for electronic authentication in response to OMB’s M-04-04. This copy is version 1.0.1, published in September 2004.

Source details and edition

Historical edition

§1; OMB M-04-04

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 263308 bytes

SHA-256 checksum

801ee73ff9c467a15516a421de08e14bb4583c75fee5cc92d115cb9636eca13d

Directed by OMB

Revised Circular A-127 to improve coordination among agency financial-system managers, software vendors, shared services, and Treasury.

Passage mentioning A-130

ed with the procurement vehicle being used to conduct the acquisition. OMB policy pertaining to using "off-the-shelf" software is contained in OMB Circular A-130 and must be followed when replacing financial management systems. 8d(2) Software Certification Testing. "Off-the-shelf" software will be tested to ensure that it meets core financial system requirements as defined in the Core Financial System Requirements document published by OFFM. The CFOC will coordinate the testing process and issue software certi

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 48117 bytes

SHA-256 checksum

90f76e6689ffed952368ed839bcb8326fb67318d94c5cab2ea0df02fcd86a6a3

Directed by OMB

Issued standards for peer review of important scientific information disseminated by federal agencies, extending the government’s information-quality policies.

Passage mentioning A-130

sclosed along with his/her comments or analysis, the agency must comply with the requirements of the Privacy Act, 5 U.S.C. 552a, as amended, and OMB Circular A-130, Appendix I, 61 Fed. Reg. 6428 (February 20, 1996) to establish appropriate routine uses in a published System of Records Notice. Furthermore, the peer review must be conducted in a manner that respects confidential business information as well as intellectual property. Section VIII also allows for a deferral or waiver of the requirements of the Bu

PDF page 31; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 31; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 268758 bytes

SHA-256 checksum

36e1612099787d8e377f82a3e31b8093ccd5eaf17b87c020dd80923537538a82

Directed by OMB

Set policies for federal public websites, applying information-management responsibilities to agencies’ online services.

Passage mentioning A-130

an agency function. Federal agency public websites are also information dissemination products as defined in Office of Management and Budget (OMB) Circular A-130, “Management of Federal Information Resources.” Agencies must manage Federal agency public websites as part of their information resource management program following guidance in OMB Circular A-130, OMB “Guidelines for Ensuring and Maximizing the Quality, Objectivity, Utility, and Integrity of Information Disseminated by Federal Agencies” (67 FR 5365),

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 49271 bytes

SHA-256 checksum

74e922b3ac01a0367b3d916ffc06e48297fd24b971b47dedc894c35d45972cc7

Assigned by law

Provided a catalog of recommended security controls for federal information systems, supporting implementation of FISMA.

Terms found: related terminology
related terminology · PDF page 38

de of Federal Regulations CIO Chief Information Officer CNSS Committee for National Security Systems COTS Commercial Off-The-Shelf DCID Director of Central Intelligence Directive FEA Federal Enterprise Architecture FIPS Federal Information Processing Standard(s) FISMA Federal Information Security Management Act GOTS Government Off-Th

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Authority; §1

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 1494246 bytes

SHA-256 checksum

5fd3ea2a25d0c85038583b465896738dd952a33f52698a01a07d456a1eb54e2b

Directed by the President

Established the common identification standard for federal employees and contractors required by Homeland Security Presidential Directive 12.

Source details and edition

Historical edition

Foreword; HSPD-12

Date supplied by the source

The original 2005 edition is unavailable in this collection. FIPS 201-3 records the publication history.

File unavailable in this collection

Directed by OMB

Directed agencies to implement the common identity credentials and related requirements established under Homeland Security Presidential Directive 12.

Passage mentioning A-130

ation for Federal Information and Information Systems, 2/04, http://www.csrc.nist.gov/publications/fips/fips199/FIPS- PUB-199-final.pdf. 10 See OMB Circular A-130 at http://www.whitehouse.gov/omb/circulars/a130/a130trans4.pdf. 7 [PDF page 8] B. Use of GSA Acquisition Services – GSA has been designated as the “executive agent for Government-wide acquisitions of information technology" under section 5112(e) of the Clinger-Cohen Act of 1996 (40 U.S.C. § 11302(e)) for the products and services required by the Direc

PDF page 7; first A-130 reference

Terms found: related terminology
related terminology · PDF page 3

the 10th floor of a commercial building, the Directive applies to the 10th floor only. • Government-owned contractor-operated facilities, including laboratories engaged in national defense research and production activities. • Facilities under a management and operating contract. Such as for the operation, maintenance, or support

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 7; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 143846 bytes

SHA-256 checksum

9735135d1a52e43b7b1f8bdc5d6ff2e7306040faec16fd4b39a43c6a5a4fa2cd

Directed by OMB

Connected public access to government information with shared descriptions of federal data, helping agencies organize information for use and reuse.

Passage mentioning A-130

y, academia, and specific interested members of the general public. Examples of significant information dissemination products are described in OMB Circular A-130 as those: a) required by law; b) involving expenditure of substantial funds; c) by reason of the nature of the information, are matters of continuing public interest, e.g., a key economic indicator; and d) by reason of the time value of the information, command public interest, e.g., monthly crop reports on the day of their release. 5 A "formal informat

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 65640 bytes

SHA-256 checksum

f30ff35aac93aacbae76dfdde029f3550f7aa31cd48f414f7c0f53e6b5982435

Guidance for implementation

Revised NIST’s security-planning guidance to help agencies document system protections, responsibilities, and compliance with federal requirements.

Source details and edition

Historical edition

§1; FISMA and A-130

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 375193 bytes

SHA-256 checksum

1635870f7cac9c0606cddbf42a7e4d0d8d01c5ab8709d3667821a4cdeaddd506

Assigned by law

Established minimum security requirements and directed agencies to select appropriate controls from SP 800-53, carrying out FISMA’s standards program.

Terms found: related terminology
related terminology · PDF page 12

e territories and possessions of the United States, and their various subdivisions; or (iv) government-owned contractor-operated facilities, including laboratories engaged in national defense research and production activities. [44 U.S.C., SEC. 3502] AUTHENTICATION: Verifying the identity of a user, process, or device, often as a pr

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Foreword; §§1–4

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 218892 bytes

SHA-256 checksum

107a9b9cdc8eccf37386aec28bbaf2dfaef5cfece17151ceabc3960423243a57

Directed by OMB

Directed agencies to designate a senior official for geographic information, assigning responsibility for coordinating that information across agency activities.

Passage mentioning A-130

nagement and Budget (OMB) has issued several policies relating to geospatial data, standards, and investments, including OMB Circulars A-11, A-16, A-119, and A-130. In addition, Executive Order 12906 and the E-Government Act of 2002, section 216 (Common Protocols for Geographic Information Systems), contain geospatial-related requirements. Some agencies have successfully implemented these policies by designating one agency official to be responsible and accountable for geospatial activities and investments. The

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 30227 bytes

SHA-256 checksum

f1324eb50f4f17224c58ba82927e37d789b512843d6d5eb6679ec66e91a52451

Directed by OMB

Called for safeguards for sensitive agency information, including protections for remote access and portable devices.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 120925 bytes

SHA-256 checksum

695616134b7b65886eab19adb4bb687009cbadc87892a29c3e3541c1563a66e7

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2006.

Passage mentioning A-130

tative assessment and the IGs a qualitative assessment of the C&A process. 11. Is certification and accreditation required for all systems? OMB Circular A-130 requires authorization to process only for general support systems and major applications. Yes, certification and accreditation is required for all systems. Section 3544(b)(3) of FISMA refers to “subordinate plans for providing adequate information security for networks, facilities, and systems or groups of information systems” and does not distingui

PDF page 6; first A-130 reference

Terms found: related terminology
related terminology · PDF page 12

late to securing systems and information: 1) service providers, 2) contractor support, 3) Government Owned, Contractor Operated facilities (GOCO), 4) laboratories and research centers, and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, telecomm

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 6; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 307948 bytes

SHA-256 checksum

d12077b85f8a1f476a54c7926f8a69cfbff1fe98563d930e8a43d12f3a10bd0a

Directed by OMB

Set reporting instructions for E-Government Act implementation for fiscal year 2006.

Passage mentioning A-130

7 Information from your agency’s IRM Strategic Plan addressing all information resources management at your agency (see section 8b1(a) of OMB Circular A-130 “Management of Federal Information Resources,” at: http://www.whitehouse.gov/omb/circulars/a130/a130trans4.pdf) can be copied or referenced in response to this question.

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 53726 bytes

SHA-256 checksum

b1bbf2b24863e37b1ecae7b6d9a4dd41ca475c181ae6866e03d50e4343416425

Directed by OMB

Addressed protection of personal information and agency preparation for responding when that information is breached.

Passage mentioning A-130

to publish notice of any subsequent substantive revisions to the use of information maintained in the system of records. 5 U.S.C. § 552a(e)(11). OMB Circular A-130 (“Management of Federal Information Resources”) offers additional guidance on this issue. OMB Circular A-130, App. I, sec. 4.c. 17 44 U.S.C. 3544(b). [PDF page 6] 6 ensure employees continue to understand their responsibilities.18 Additional or advanced training should also be provided commensurate with increased responsibilities or change

PDF page 5; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 232857 bytes

SHA-256 checksum

5bc7a03c093857d431fbed262f9adb488deea2cdaaea6b7f4ee40f839423cdfa

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2007.

Passage mentioning A-130

o present a quantitative assessment and the IGs a qualitative assessment of the C&A process. 24. Is C&A required for all information systems? OMB Circular A-130 requires authorization to process only for general support systems and major applications. Yes, C&A is required for all Federal information systems. Section 3544(b)(3) of FISMA refers to “subordinate plans for providing adequate information security for networks, facilities, and systems or groups of information systems” and does not distinguish betw

PDF page 13; first A-130 reference

Terms found: related terminology
related terminology · PDF page 18

elate to securing systems and information: 1) service providers, 2) contractor support, 3) Government Owned, Contractor Operated facilities (GOCO), 4) laboratories and research centers, and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, telecomm

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 13; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 256897 bytes

SHA-256 checksum

e29f4599c6266d2c20d67136ba75063a491492a75f3ad66924e58eea589f8ef0

Directed by OMB

Updated principles for assessing, managing, and communicating environmental, health, and safety risks, drawing on government-wide information policies.

Passage mentioning A-130

es should be reproducible. 59 For guidance on how to provide the public with timely access to government information, Agencies should refer to OMB’s Circular A-130, which addresses the management of Federal information resources, and OMB Memorandum 06-02, which addresses improving public access to Federal information.60 Principles for Priority Setting Using Risk Analysis 1. To inform priority setting, agencies should seek to compare risks, grouping them in broad categories of concern (e.g., high, moderate, and l

PDF page 13; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 13; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 159412 bytes

SHA-256 checksum

cff91b9806ee49b7104a643748cc734549479438045c0146b6b87b3daa34c794

Directed by OMB

Identified tools agencies could use to implement electronic-records management responsibilities.

Passage mentioning A-130

tly with the Federal community to 1 These requirements are in existing law and policy including OMB Circular A-130 and the Paperwork Reduction Act. OMB Circular A-130 can be found at: http://www.whitehouse.gov/omb/circulars/a130/a130trans4.html. The Paperwork Reduction Act can be found at: http://www.archives.gov/federal-register/laws/paperwork-reduction/. 2 This refers to the Meridio Enterprise Content Management SmartBUY agreement. This software possesses a valid

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 56018 bytes

SHA-256 checksum

83f7032914d72d026fe22b6e1f244d12cbb8717980cc16c809f345fd72948ca5

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2008.

Passage mentioning A-130

o present a quantitative assessment and the IGs a qualitative assessment of the C&A process. 24. Is C&A required for all information systems? OMB Circular A-130 requires authorization to process only for general support systems and major applications. Yes, C&A is required for all Federal information systems. Section 3544(b)(3) of FISMA refers to “subordinate plans for providing adequate information security for networks, facilities, and systems or groups of information systems” and does not distinguish betwe

PDF page 12; first A-130 reference

Terms found: related terminology
related terminology · PDF page 18

elate to securing systems and information: 1) service providers, 2) contractor support, 3) Government Owned, Contractor Operated facilities (GOCO), 4) laboratories and research centers, and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, telecommu

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 12; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 215351 bytes

SHA-256 checksum

e5b317184e742b02604685ef3def682ccf4c151466f5877f580f5460511bd6b2

Directed by OMB

Set out expectations for the management structure and oversight of agency technology, including the role of chief information officers.

Passage mentioning A-130

gency-Appointed CIO, and to advise the Director on matters regarding the authority, responsibilities and organizational resources of the CIO, per OMB Circular A-130 (published November 28, 2000), Section 9, Assignment of Responsibilities. Consultation with OMB on CIO appointments should be factored into your agency’s selection process, and OMB will ensure its input into such selections is expeditious. If you have questions regarding this requirement, please contact Karen Evans, Administrator of the Office of El

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 34660 bytes

SHA-256 checksum

5d8b52f455fa4365ddb35060c7560a98bfc51c886b964f3780bda28d1659accc

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2009.

Passage mentioning A-130

present a quantitative assessment and the IGs a qualitative assessment of the C&A process. 24. Is C&A required for all information systems? OMB Circular A-130 requires authorization to process only for general support systems and major applications. Yes, C&A is required for all Federal information systems. Section 3544(b)(3) of FISMA refers to “subordinate plans for providing adequate information security for networks, facilities, and systems or groups of information systems” and does not distinguish betwe

PDF page 11; first A-130 reference

Terms found: related terminology
related terminology · PDF page 17

late to securing systems and information: 1) service providers; 2) contractor support; 3) Government Owned, Contractor Operated facilities (GOCO); 4) laboratories and research centers; and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, teleco

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 11; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 181349 bytes

SHA-256 checksum

16a2bbf5ce9e9af74c0cc573199a23d5dc50546b22b945031fc8b24199b8ce6f

2009-12-08OMB memorandum

M-10-06, Open Government Directive

Directed by OMB

Directed agencies to make government more transparent and participatory, including expanding public access to information.

Passage mentioning A-130

hat webpage in a timely fashion. 2 The Federal Government has defined information in OMB Circular A-130, “Management of Federal Information Resources,” as any communication or representation of knowledge such as facts, data, or opinions presented in any medium or format. [PDF page 3] 3 f. Each Open Government Webpage shall incorporate a mechanism for the public to: i. Give feedback on and assessment of the quality of published information; ii.

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 82455 bytes

SHA-256 checksum

0af1c1140adeab559fed8bdd30f5528fa73ff3085fe7efe6a6fa4138ee16cc6d

Guidance for implementation

Organized system security around the Risk Management Framework, connecting selection and assessment of safeguards with authorization and continuing monitoring.

Terms found: cloud, related terminology
cloud · PDF page 31

nformation systems. In particular, net-centric architectures39 (e.g., service-oriented architectures [SOAs], cloud computing) introduce two important concepts: (i) dynamic subsystems; and (ii) external subsystems. While the concepts of dynamic subsystems and external subsystems (described in the following sections) are n

Extracted text; not checked against the page image.
related terminology · PDF page 32

iated with the subsystem. Appendix I further notes that the assurance or confidence that the risk from using external services is at an acceptable level depends on the trust that the organization places in the external service provider. In some cases, the level of trust is based on the amount of direct control the organization is ab

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§1.1; continuous monitoring

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 947930 bytes

SHA-256 checksum

d19a9f3447b0b769db361aaa14b3272d5f1d0816985e903140fe2531e0a7a647

Directed by OMB

Moved federal security reporting toward automated measurements and continuing monitoring as part of the fiscal year 2010 reporting instructions.

Passage mentioning A-130

the IGs a qualitative assessment of the security authorization process. 25. Is a security authorization required for all information systems? OMB Circular A-130 requires a security authorization to process only for general support systems and major applications. Yes, security authorizations are required for all Federal information systems. Section 3544(b)(3) of FISMA refers to “subordinate plans for providing adequate information security for networks, facilities, and systems or groups of information systems”

PDF page 13; first A-130 reference

Terms found: related terminology
related terminology · PDF page 18

elate to securing systems and information: 1) service providers, 2) contractor support, 3) Government Owned, Contractor Operated facilities (GOCO), 4) laboratories and research centers, and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, telecommu

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 13; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 281596 bytes

SHA-256 checksum

de73191abda2c3037a37d6ff60566a6dd72c9aacbeaa8f5337b1f7be467273d2

Directed by OMB

Explained agency responsibilities when using third-party websites and applications, including information management and privacy.

Passage mentioning A-130

y’s intended or expected use of PII; iv. with whom the agency will share PII; 10 OMB Circular A-130, available at http://www.whitehouse.gov/omb/Circulars_a130_a130trans4/ 11 OMB Memorandum M-03-22, OMB Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002 (Sept. 26, 2003), available at http://www.whitehouse.gov/omb/memoranda_m03-22/ [PDF page 5] 5 v. whether and how the agency will maintain PII, and for how long; vi.

PDF page 4; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 4; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 105750 bytes

SHA-256 checksum

85b9db09d186965513cc91591b039780fc21af2ffe878993cf27958dd68627bd

Directed by OMB

Set policy for managing the cost, schedule, and performance plans used to oversee technology investments.

Passage mentioning A-130

policy only addresses the establishment, management, and change to investment baselines. Agencies should reference other OMB requirements, including Circular A-130 and the Capital Programming Guide, to describe full lifecycle management of IT capital investments. 1 The term investment is generically used in this policy to include both major and non- major investments as defined by Circular A-11 unless the specific reference in the policy is to Major Investments.

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 79451 bytes

SHA-256 checksum

16de396fc61464f22b75cd976aca7cbc3edc07a9f1dd60952ff90b660fd3f610

Directed by OMB

Explained how agencies could share data while meeting privacy responsibilities, connecting information access with safeguards for individuals.

Passage mentioning A-130

Rights of Citizens (1973), available at http://aspe.hhs.gov/DATACNCL/1973privacy/tocprefacemembers.htm 4 OMB Circular A-130, Management of Federal Information Resources, available at http://www.whitehouse.gov/omb/circulars_a130_a130trans4/ [PDF page 3] 3 • Partnership Fund for Program Integrity Innovation: Our ability to identify, implement, and test methods to improve integrity, efficiency, and service in the delivery of State and Federal benefit programs will increase

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 70354 bytes

SHA-256 checksum

a82b8ec16fe91a53a48378a90dd1605a44866404de3dbbf314a1cacba91212e8

Directed by the President

Established the government-wide program for controlled unclassified information: information that needs protection under law or policy but is not classified.

Source details and edition

Historical edition

§§2–5; NARA executive agent

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 137663 bytes

SHA-256 checksum

84eafe59e43010d5aba14bd9c1f79ecc4ff817d3a9d8a1e92b34aa0916b2de8a

Directed by OMB

Directed continued implementation of common identity credentials under Homeland Security Presidential Directive 12. M-19-17 later rescinded it.

Source details and edition

Rescinded by M-19-17, p. 13.

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 209165 bytes

SHA-256 checksum

4ebd91e3539e7b63585135642c9374f3cbcae40d9278b110c1705bc0d64a75bb

Guidance for implementation

Explained how agencies could continuously monitor security controls and changing risks, supporting ongoing management of system security.

Terms found: related terminology
related terminology · PDF page 61

ttern Enumeration & Classification CIO Chief Information Officer CIRT Computer Incident Response Team COTS Commercial Off-The-Shelf CVSS Common Vulnerability Scoring System CVE Common Vulnerabilities and Exposures CWE Common Weakness Enumeration CWSS Common Weakness Scoring System DLP Data Loss Prevention FDCC Federal Desktop Core Co

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§1; FISMA; RMF

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 986916 bytes

SHA-256 checksum

2d1c0bf459f5e1bfd41ceb5eac83bf62e4c34bf08e2e7088b37cb73a11442b98

Guidance for implementation

Defined cloud computing and its service and deployment models. The FedRAMP Authorization Act later used this definition.

Terms found: cloud
cloud · PDF page 1

[PDF page 1] The NIST Definition of Cloud Computing Recommendations of the National Institute of Standards and Technology Peter Mell Timothy Grance Special Publication 800-145 [PDF page 2] NIST Special Publication 800-145 The NIST

Checked against extracted text; PDF page listed.
Source details and edition

Historical edition

§2

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 85781 bytes

SHA-256 checksum

7b0c1a9fdfc67218b8ba2098f448c100c27070db91736b3c87fed63bfa21d418

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2011.

Passage mentioning A-130

existing Federal requirements for data protection and remote access are applicabl e to mobile devices. For example , the security requirements in OMB Circular A-130 , NIST FIPS 140-2, Security Requirementsfor Cryptographic Modules, NIST FIPS 199, Standardsfor Security Categorization ofFederal Information and Information Systems, and NIST FIPS 200, Minimum Security ReqUirements for Federal Information and Information Systems, apply (including appropriate security controls specified in NIST Special Publication 800-53

PDF page 13; first A-130 reference

Terms found: related terminology
related terminology · PDF page 20

ate to securing systems and information : 1) service providers; 2) contractor support ; 3) Government Owned, Contractor Operated facilities (GOCO) ; 4) laboratories and research centers; and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations , telecommun

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 13; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 6008154 bytes

SHA-256 checksum

1da2650a71844d4556271a668e11821965ceda9a9a97868bee1c07cd09b4cb8d

Guidance for implementation

Explained security and privacy considerations for agencies moving information and services to public cloud environments.

Terms found: cloud, FedRAMP
cloud · PDF page 1

[PDF page 1] Guidelines on Security and Privacy in Public Cloud Computing Wayne Jansen Timothy Grance Special Publication 800-144 [PDF page 2] ii NIST Special Publication 800-144 Guidelines on Security and Privacy in Public Cloud Computing Wayne Jansen Timot

Checked against extracted text; PDF page listed.
FedRAMP · PDF page 50

rnment in cloud computing deployments for which the security risk model applies - http://www.cio.gov/modules/fedramp/demo.cfm. [PDF page 51] 41 negotiated service agreement s, which provide greater range and flexibility, necessitate careful scrutiny and prioritization of requirements that are incorporated into the terms

Checked against extracted text; PDF page listed.
Source details and edition

Historical edition

Executive summary; §§3–4

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 1105061 bytes

SHA-256 checksum

47f0fdf31f4f2b37fb2a8fa0bf77235aad0b3daa74a6397603a619a839500a42

Directed by OMB

Established FedRAMP’s shared approach to assessing and authorizing cloud services, allowing agencies to reuse security assessment work. M-24-15 replaced it in 2024.

Terms found: cloud, FedRAMP
cloud · PDF page 1

en VanRoekel Federal Chief Information Officer SUBJECT: Security Authorization of Information Systems in Cloud Computing Environments 1. Introduction Cloud computing offers a unique opportunity for the Federal Government to take advantage of cutting edge information technologies to dramatically reduce procurement a

Checked against extracted text; PDF page listed.
FedRAMP · PDF page 1

nmental organizations (NGOs), and academia to develop the Federal Risk and Authorization Management Program (FedRAMP). This program introduces an innovative policy approach to developing trusted relationships between Executive departments and agencies1 and cloud service providers (CSPs). FedRAMP will provide a cost-effec

Checked against extracted text; PDF page listed.
Source details and edition

Rescinded by M-24-15 (opening and concluding sections).

pp. 1–4; responsibilities; implementation

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 208300 bytes

SHA-256 checksum

1000dc126873b7d4831512434a5087d6991e7b02f73200a39d49e683ec068fbc

Directed by OMB

Directed agencies to improve government records management, including the transition to electronic records.

Passage mentioning A-130

y will identif y any existing use of cloud services or storage , and the date of implementation. 5 [PDF page 6] A4.2 By the next revision of OMB Circular A-130, OMB will update A-130 to explicitly require that agencies must incorporate records management requirements when moving to cloud-based services or storage solutions. AS Evaluate the feasibility for secure "data at rest" storage and management services for Federal agency-owned electronic records By December 31 ,2013, NARA will determine the feasibilit

PDF page 6; first A-130 reference

Terms found: cloud
cloud · PDF page 5

the development of open source records management solutions. A4 Embed records management requirements into cloud architectures and other Federal IT systems and commercially-available products A4.I By December 31 , 2013 , NARA will incorporate into existing reporting requirements an annual agency update on new cloud in

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 6; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 2742904 bytes

SHA-256 checksum

d82cd4015bc71bc5a4dbb22020628fda7fa64ca0993dc426d0da0e9d7523d934

Guidance for implementation

Updated NIST’s guidance for conducting risk assessments, helping agencies analyze threats, vulnerabilities, and potential consequences.

Terms found: cloud, related terminology
cloud · PDF page 27

nally or unintentionally); and (iv) the use of new information and computing technologies such as mobile and cloud and the potential effect on the ability of organizations to successfully carry out their missions/business operations while using those technologies. Organization-wide assessments of risk can be based solely

Extracted text; not checked against the page image.
related terminology · PDF page 73

performs critical functions for organizations. This is largely accomplished as supply chain attacks on both commercial off-the-shelf and custom information systems and components. Achieve results (i.e., cause adverse impacts, obtain information) Obtain sensitive information through network sniffing of external networks. Adversary with

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§1.1; supersedes 2002 guide

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 826897 bytes

SHA-256 checksum

f214087f0bdb35932a28c16eb93932a33c67a6edfb5e6f1638866bd201c98e04

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2012.

Passage mentioning A-130

l existing Federal requirements for data protection and remote access are applicable to mobile devices. For example, the security requirements in OMB Circular A-130, NIST FIPS 140-2, Security Requirementsfor Cryptographic Modules, NIST FIPS 199, Standardsfor Security Categorization ofFederal Information and Information Systems, and NIST FIPS 200, Minimum Security Requirements for Federal Information and Information Systems, apply (including appropriate security controls specified in NIST SP 800-53). Agencies should

PDF page 13; first A-130 reference

Terms found: cloud, FedRAMP, related terminology
cloud · PDF page 12

n Management Program (FedRAMp)l when conducting risk assessments and security authorizations for use of all cloud services. 24. How do agencies ensure FISMA compliance for connections to non-agency systems? Do Statement of Auditing Standards No. 70 (SAS 70) audits meet the requirements ofFISMA and implementing policies

Extracted text; not checked against the page image.
FedRAMP · PDF page 12

of December 8, 2011, all agencies are required to use the Federal Risk and Authorization Management Program (FedRAMp)l when conducting risk assessments and security authorizations for use of all cloud services. 24. How do agencies ensure FISMA compliance for connections to non-agency systems? Do Statement of Auditing Stan

Extracted text; not checked against the page image.
related terminology · PDF page 20

elate to securing systems and information: 1) service providers; 2) contractor support; 3) Government Owned, Contractor Operated facilities (GOCO); 4) laboratories and research centers; and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, telecommun

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 13; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 7080939 bytes

SHA-256 checksum

8a1918b812ae5778fbd6698b127f005a1fce92090ac55eb03be3aff80de48585

Directed by OMB

Encouraged shared services for federal financial systems, linking financial-management improvements with technology planning and investment.

Passage mentioning A-130

luding OMB's Memorandum M-10-26, Immediate Review ofFinancial Systems IT Projects, the Shared Services Strategy of May 2, 2012 ("Shared First"), and Circular A-130, Management ofFederal Information Resources, this memorandum: • directs all executive agencies to use, with limited exceptions, a shared service solution for future modernizations of core accounting or mixed systems; • describes the process through which OMB and the Department of the Treasury will conduct an assessment of the capabilities and gaps o

PDF page 1; first A-130 reference

Terms found: cloud
cloud · PDF page 3

so work with agencies to ensure that management and acquisition strategies promote the Federal Government's "Cloud First" policy 5 and the strategic sourcing principles outlined in OMB Memorandum M-13-02, Improving Acquisition through Strategic Sourcing. Laying the Groundwork (or Success(ul Shared Services Ensuring tha

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 293328 bytes

SHA-256 checksum

40f549d8a37401cc0280e877a68a2938a48965eb0e5a18b933eaad26a8b6ec1a

Directed by OMB

Set fiscal year 2013 instructions for reviewing agencies’ technology portfolios and improving management of their combined investments.

Passage mentioning A-130

s consolidating previously collected IT plans, reports and data calls into three primary collection channels: 1. IRM Strategic Plans. According to Circular A-130,8 "Information Resources Management (IRM) Strategic Plans9 should support the agency Strategic Plan required in OMB Circular A-11, 5 See the Federal Cloud Computing Strategy, http://www.whitehouse.gov/sites/default/files/omb/assets/egov docs/federal-cloud-computing-strategy.pdf. 6 See Fiscal Year 2012, Analytical Perspectives, Budget of the U.S. Governme

PDF page 3; first A-130 reference

Terms found: cloud, FedRAMP
cloud · PDF page 3

ve data centers, as a means of optimizing computing power for the enterprise. These agencies have found that cloud computing is a more scalable and transparent way to provision IT services, giving agencies a viable enterprise alternative to major and often stove-piped, capital IT investments. By procuring technology "as-

Extracted text; not checked against the page image.
FedRAMP · PDF page 5

Implementation of the following agency requirement under the Federal Risk Authorization Management Program (FedRAMP) will be reported through the Integrated Data Collection: 19 • Section 4.d.vii --Provide to the Federal CIO annually on April30, a certification in writing from the Executive department or agency CIO and C

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 629189 bytes

SHA-256 checksum

4a1e146b5188b0d18bff2e9b856a4a5dee6f1f27f6b613bf8d90ba2c7949b2ef

Guidance for implementation

Expanded the security-control catalog and added a privacy-control appendix, bringing privacy practices into the same reference used for system safeguards.

Terms found: cloud, commercial services, FedRAMP, related terminology
cloud · PDF page 17

ontrol enhancements have been developed and integrated into the catalog addressing such areas as: mobile and cloud computing; applications security; trustworthiness, assurance, and resiliency of information systems; insider threat; supply chain security; and the advanced persistent threat. In addition, Special Publicatio

Extracted text; not checked against the page image.
commercial services · PDF page 211

omated mechanisms can include, for example, automated scripts to monitor new posts on selected websites, and commercial services providing notifications and alerts to organizations. (2) MONITORING FOR INFORMATION DISCLOSURE | REVIEW OF MONITORED SITES The organization reviews the open source information sites being monitored [Assignm

Extracted text; not checked against the page image.
FedRAMP · PDF page 42

reements to obtain commodity 43 Organizations consult the Federal Risk and Authorization Management Program (FedRAMP) when acquiring cloud services from external providers. FedRAMP addresses required security controls and independent assessments for a variety of cloud services. Additional information is available at http:/

Extracted text; not checked against the page image.
related terminology · PDF page 41

ical space and control of assets, are being extended (both physically and logically) with the growing use of external services. In this context, external services can be provided by: (i) entities within the organization but outside of the security authorization boundaries established for organizational information systems; (ii) ent

Extracted text; not checked against the page image.
Source details and edition

Withdrawn September 23, 2021, superseded by Rev. 5; withdrawal recorded on the archived PDF cover.

Authority; Appendix J

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 5301858 bytes

SHA-256 checksum

e6f8a1aae41168f4ec9edc5b34aee0a21f2c888c78bf1de33e6ec63a0209db4e

Directed by OMB

Set policy for managing government information as an asset and making data available in reusable forms, subject to privacy and security protections.

Passage mentioning A-130

making it available online in open formats. OMB has also developed policies to help agencies incorporate sound information practices , including OMB Circular A-130 3 and OMB Memorandum M-06-02. 4 In addition, the Federal Government launched Data.gov, an online platform designed to increase access to Federal datasets. The publication of thousands of data assets through Data.gov has enabled the development of numerous products and services that benefit the public. To help build on these eff01ts, the President issued

PDF page 2; first A-130 reference

Source details and edition

Rescinded and replaced by M-25-05 (p. 2).

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 6126025 bytes

SHA-256 checksum

319d2098e2206645d8029779e9bc034d0e68e5ebfc4f9422b974b2acc2c3e9e0

Directed by OMB

Addressed privacy protections when agencies used the Do Not Pay initiative to identify and prevent improper payments.

Passage mentioning A-130

cy Sharing of Personal Data- Protecting Personal Privacy (Dec. 20, 2000), available at http://www.whitehouse.gov/omb/memoranda mOI-05/; see also OMB Circular A-130, Federal Agency Responsibilities for Maintaining Records About Individuals, available at http://www. whitehouse.gov/omb/circulars a 130 a 130trans4. 10 IPERIA applies only to executive agencies of the Federal Government, not to State or local governments or non­ executive Federal agencies. 2 [PDF page 3] defined in section 3 ofthis Memorandum. As requ

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 10433378 bytes

SHA-256 checksum

1df702fd01982fe2ceac9dbc10e33e914ccf7742ccf970a9c230fee8bbc49bba

Directed by OMB

Updated financial-system compliance guidance under Circular A-123, connecting financial-management requirements with existing technology policies.

Passage mentioning A-130

res contained in OMB Circular No. A-123, Management' s Responsibility for Internal Control (Circular A-123). C. The policies contained in OMB Circular No . A-130, Management ofF ederal information Resources (hereinafter Circular A-130), govern agency management of information systems and technology investments , including financial management systems. The policies contained in Circular A-130 apply to all agenc y information resources, including financial management systems as defmed in Appendix D. D. The finan

PDF page 4; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 4; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 4583434 bytes

SHA-256 checksum

46748dbd5ff783818b963b9b8081049dabceba4dc2bd6e26a7093c5b15866ce2

Directed by OMB

Directed agencies to improve continuous security monitoring and move toward ongoing authorization based on current information about risk.

Passage mentioning A-130

ommon controls inherited by organizational information systems. ISCM programs fulfill the three-year security reauthorization requirement required by Circular A-130 (dated November 2000), so a separate reauthorization process is not necessary. 6 [PDF page 7] Develop ISCM strategy (or February 28, 2014 All agencies strategies) Assess and Develop Staff and Resources Agencies shall ensure adequate staff and training are in place to meet the objectives of the ISCM program. To support agencies' implementations, DHS

PDF page 6; first A-130 reference

Terms found: cloud, FedRAMP
cloud · PDF page 3

ormation meet Federal information security requirements for ISCM. 14 This includes FedRAMP requirements for cloud computing; 15 and 8) Ensure adequate staff and training to meet the objectives of the ISCM program. In addition to the general agency responsibilities described above: 1) OMB will continue to oversee ag

Extracted text; not checked against the page image.
FedRAMP · PDF page 3

viders hosting Federal information meet Federal information security requirements for ISCM. 14 This includes FedRAMP requirements for cloud computing; 15 and 8) Ensure adequate staff and training to meet the objectives of the ISCM program. In addition to the general agency responsibilities described above: 1) OMB wil

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 6; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 889577 bytes

SHA-256 checksum

a48fae52553832b7ce8884cf77f273d47a7aac309878df87a220ee0a074e9761

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2013.

Passage mentioning A-130

l existing Federal requirements for data protection and remote access are applicable to mobile devices. For example, the security requirements in OMB Circular A-130, NIST FIPS 140-2, Security Requirements for Cryptographic Modules, NIST FIPS 199, Standards for Security Categorization ofFederal Information and Information Systems, and NIST FIPS 200, Minimum Security Requirements for Federal Information and Information Systems, apply (including appropriate security controls specified in NIST SP 800-53) to mobile devi

PDF page 14; first A-130 reference

Terms found: cloud, FedRAMP, related terminology
cloud · PDF page 13

gencies were required to follow Federal Risk and Authorization Management Program (FedRAMPt requirements for cloud computing. 4 See https://cio.gov/wp-content/uploads/20 12/09/fedrampmemo.pdf and http://www.fedramp.gov. 9 [PDF page 14] 27. How do agencies ensure FISMA compliance for connections to non-agency systems?

Extracted text; not checked against the page image.
FedRAMP · PDF page 13

ements for cloud computing. 4 See https://cio.gov/wp-content/uploads/20 12/09/fedrampmemo.pdf and http://www.fedramp.gov. 9 [PDF page 14] 27. How do agencies ensure FISMA compliance for connections to non-agency systems? Do Statement of Auditing Standards No. 70 (SAS 70) audits meet the requirements ofFISMA and impleme

Extracted text; not checked against the page image.
related terminology · PDF page 23

elate to securing systems and information: 1) service providers; 2) contractor support; 3) Government Owned, Contractor Operated facilities (GOCO); 4) laboratories and research centers; and 5) management and operating contracts. 1) Service providers -- this encompasses typical outsourcing of system or network operations, telecommunic

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 14; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1954339 bytes

SHA-256 checksum

05b6e2c84f3eaa5160f835f55c7e15816cbabadf3fd4f216802e57fc6dd1aad9

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2014-2015.

Passage mentioning A-130

existing Federal requirements for data protection and remote access are applicable to mobile devices. For example , the security requirements in OMB C ircular A-130, N IST FIPS 140-2, "Security R equirementsfor Cryptographic Modu les," IST FlPS 199, '"Standardsfor Security Ca tegorization ofFederal b?formarion and Information Systems," N IST FIPS 200, '"Minimum Security R equirementsfor Federal Information and Information System s," and N IST FIPS 201­ 2. ·'Personal Ident(fication Ver(fication ofFederal Emp loyees a

PDF page 15; first A-130 reference

Terms found: cloud, FedRAMP
cloud · PDF page 7

reporting of Federa l department and agency website and system vulnerabilities. Contracted third parties and cloud service providers , in accordance with agency and provider incident response plans (IRP) and FedRAMP requirements , should report vulnerabi lities to the relevant agencies who shou ld in turn report to DHS

Extracted text; not checked against the page image.
FedRAMP · PDF page 7

rties and cloud service providers , in accordance with agency and provider incident response plans (IRP) and FedRAMP requirements , should report vulnerabi lities to the relevant agencies who shou ld in turn report to DHS ; • Continue to deploy conso lidated intrusion detection and prevention capab ilitie s to protect

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 15; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 6782634 bytes

SHA-256 checksum

c12e6bde58f5462446a6957616fc2662baf3d594f01b7d34dccc807d9a6fa4f3

Directed by OMB

Called for department support of the responsibilities of federal statistical agencies and units, including the quality and integrity of official statistics.

Passage mentioning A-130

nsibilities (5 U.S.C. 552a; 40 FR 28948, Jul. 9, 1975); Section 208 of the £-Government Act of2002 (Pub. L. 107-347, 44 U.S.C. Ch 36, Dec. 17, 2002); Circular A-130 (revised Nov. 28, 2000); President's Memorandum on the Preservation and Promotion ofScientific Integrity; the Memorandum for the Heads of Executive Departments and Agencies; OMB's Implementation Guidance'for Title V ofthe £-Government Act, Confidential information Protection and Statistical Efficiency Act of2002; and Principles and Practices for a Federa

PDF page 4; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 4; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1282453 bytes

SHA-256 checksum

092f8cf98e6070346e33ce2ae640aa2cc7018e7e72bc2227282e1dadf3682380

Assigned by law

Updated OMB’s oversight, the Department of Homeland Security’s operational role, and agency security duties. It supplied a central part of the legal framework for A-130’s 2016 revision.

Source details and edition

Historical edition

§2: 44 USC 3553–3554, 3557

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 233997 bytes

SHA-256 checksum

96ab24c78d410963ebb0bcd519dbe4b95ee800400c49ea4448e6d3f39c3eb917

Guidance for implementation

Provided requirements for protecting controlled unclassified information in nonfederal systems, supporting the government-wide CUI program.

Terms found: cloud
cloud · PDF page 12

ervices; conducting background investigations for security clearances; processing healthcare data; providing cloud services; and developing communications, satellite, and weapons systems). Additionally, federal information is frequently provided to or shared with entities such as State and local governments, colleges an

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§1; EO 13556; contract applicability

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 901632 bytes

SHA-256 checksum

0cf9452bccca2eea7d5dd4283d3daf62f58b9663be35ceceb62c49aa3dd02f0d

Directed by OMB

Required secure connections for federal public websites and web services, using HTTPS to protect communications with the public.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 264619 bytes

SHA-256 checksum

99bf05ade627ab102c3f54bb7ba034d2dca15e6774093122a05a0a164ea9293f

Directed by OMB

Set instructions for agency technology management and oversight following federal IT acquisition reforms, including chief information officer responsibilities.

Passage mentioning A-130

achment A. R evising other IT management policies to reflect this scope To establish consistency across IT management and acquisition policies , OMB Circular A-130 , OMB Circular A-ll , and the Federal Acquisition Regulation (FAR) will be updated to reflect these definitions of "information technology resources " and "information technology ," as appropriate. Section B: Implementation of the Common Baseline 1. The "Common Baseline " (Attachment A) provides guidance on the CIO ' s and other Senior Agency Officia

PDF page 4; first A-130 reference

Terms found: cloud, FedRAMP
cloud · PDF page 4

f a computer, software , firmware and similar procedures , services (including provisioned services such as cloud computing and support services that support any point of the lifecycle of the equipment or service), and related resources. D. The term " information technology " does not include any equipment that is acq

Extracted text; not checked against the page image.
FedRAMP · PDF page 22

center activities and achieve overall IT objectives. This includes a discussion of how the agency is using FedRAMP services and ensuring cloud services meet applicable FISMA requirements.  Cybersecurity. In addition to the “Protect” metrics in Fiscal Year 2015 PortfolioStat Performance Metrics below, PortfolioStat di

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 4; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 7727764 bytes

SHA-256 checksum

d80236832182a0a944b766253d2d59f997f06917f0217a312176afbd82017e15

Directed by OMB

Set a cybersecurity strategy and implementation plan for civilian agencies, identifying actions to strengthen protection of federal information and systems.

Passage mentioning A-130

13-283) (FISMA); revisions to the Federal Government’s governing document establishing policies for the management of Federal information resources: Circular A-130, Managing Information as a Strategic Resource; new guidance on implementing cybersecurity contracting language; cyber incident response best practices for use by Federal civilian agencies; the issuance of a blanket purchase agreement for Identity Protection Services designed to give Federal agencies ready access to best-in-class solutions and reduce was

PDF page 5; first A-130 reference

Terms found: cloud
cloud · PDF page 14

ernet connections for consolidation and reduction. ii. Ensuring all possible traffic, including mobile and cloud, goes through a TIC. iii. Options for where TICs can be hosted to improve bandwidth coverage. iv. Additional tools that can be implemented at a TIC location. v. How external vendors who store, process, and

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 360506 bytes

SHA-256 checksum

722f46d5b73f218bf29e153acb5dfd3fbcae00a10b1f1e491f6341fd0f59f135

Directed by OMB

Directed agencies to improve how they acquire and manage software licenses, using coordinated purchasing and better information about existing software.

Passage mentioning A-130

elopment of new software. Agencies must develop processes and guidelines to manage software consistent with OMB policies and guidance, including OMB circular A-130 and the Federal Acquisition Regulation. The processes and guidelines must also include alternative analyses in a technology neutral manner that is merit-based, and considers such factors as performance, total cost of ownership, security, privacy, Section 508 compliance, interoperability, ability to share or re-use, and availability of quality support.

PDF page 6; first A-130 reference

Terms found: cloud
cloud · PDF page 3

purchased, deployed, and in use, as well as spending on subscription services (to include provisional (i.e. cloud) software as a service agreement (SaaS)). Agencies must better understand the true usage of certain types of software. • No later than September 30, 2016, covered agencies shall, to the extent practicable

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 6; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 183898 bytes

SHA-256 checksum

3d1e4032f8d326234dbb4567caa905f21428cdfc2176d1d9c0dc0492cf7c276b

Directed by OMB

Revised Circular A-123 to connect agency-wide risk management with internal controls, complementing A-130’s management of information risks.

Passage mentioning A-130

suant to OMB Circular No. A-123, Appendix A...................................................................... 37 D. Reporting Pursuant to OMB Circular No. A-130, Appendix I ....................................................................... 38 E. Reporting Pursuant to Section 2—31 U.S.C. 3512(d) (2) .............................................................................. 38 F. Reporting Pursuant to Section 4—31 U.S.C. 3512(d) (2) (B) ....................................................................

PDF page 7; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 7; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1630151 bytes

SHA-256 checksum

58592cd4f0650d061a16bc009fe98ebe73bd0b74f2e34fdcafdb197f56bcb8d2

Assigned by law

Reorganized information, security, and privacy policy around the full life of agency systems and information. It addressed commercial services and integrated established NIST standards and guidance.

Terms found: cloud
cloud · PDF page 14

and decommissioning of information systems, particularly Internet resources to include storage solutions and cloud-based services such as software as a service, platform as a service, and infrastructure as a service; and e) IT investments use an Earned Value Management System (EVMS) and Integrated Baseline Review, when

Checked against the original PDF page on October 10, 2026.
Source details and edition

2016 revision; later laws and memoranda also apply.

Sections 2, 3, 5, 6; Appendix I; Appendix II

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 550093 bytes

SHA-256 checksum

f1a2e73a1063eab7d83da2a3bfa810f3aaebc9a6ef8e9d264ffc57ccd02152e6

2016-07-28OMB circular

A-130 2016 final notice

Related development

Announced the 2016 revision of A-130 and its effective date, July 28, 2016.

Source details and edition

Historical edition

81 FR 49689

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 194514 bytes

SHA-256 checksum

d7d35c2d1635f604b9e68594a710258ff21568c8477c0fb627744e36bd358939

Directed by OMB

Defined the role and designation of senior agency privacy officials, supporting the privacy responsibilities in the revised A-130.

Passage mentioning A-130

1974; 8 the Paperwork Reduction Act of 1995;9 the E-Government Act of 2002;10 the Health Insurance Portability and Accountability Act of 1996;11 OMB Circular A-130;12 Privacy Act Implementation: Guidelines and Responsibilities;13 OMB Circular A-108;14 OMB’s Final Guidance Interpreting the Provisions of Public Law 100-503, the Computer Matching and Privacy Protection Act of 1988; 15 and OMB Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.16

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 294219 bytes

SHA-256 checksum

a9263143a2dd75478f08189d4eac7e9c15499293578697cdc8ed7a9f1e6f55e0

Directed by OMB

Provided DATA Act reporting instructions and requirements for the reliability of spending information submitted to USASpending.gov.

Passage mentioning A-130

eporting practices, personal identifiable information (PII) associated with awards to individuals should not be reported to USASpending.gov. OMB Circular No. A-130 defines PII as "information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual." Agencies currently report financial assistance records containing PII in summary groups of similar awards at the county level known as "aggregate records

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 5703568 bytes

SHA-256 checksum

5a3d10a48f41e7312df39f7f8b6bdcdc0874e85383da73de44d6bf9eaf555d3d

Directed by OMB

Updated policy for federal public websites and digital services, connecting public access, service delivery, and information management.

Passage mentioning A-130

y changes rapidly and agencies must have the flexibility to address known and emerging threats while making continuous improvements. FISMA and OMB Circular A-130 require each Federal Agency to develop, document, and implement an agency-wide information security program for the information and information systems that support the agency’s operations and assets, including those provided or managed by another agency, contractor, or other source.19 FISMA also provides for the development and maintenance of minimum c

PDF page 10; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 10; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1186881 bytes

SHA-256 checksum

0efc3e12ecc44293510730e9806cf7b3ed70585fe389e05311abf4702745985d

Directed by OMB

Set policy for identifying and protecting high-value assets: information and systems whose compromise could have especially serious consequences.

Passage mentioning A-130

ons of the agency and highlights IT as a component of the portfolio view of risk. • The overarching Federal information management policy, OMB Circular No. A-130, Managing Information as a Strategic Resource, requires agencies to manage Federal information throughout the information life cycle and directs agencies to provide protection for their information commensurate with the risk and potential harm resulting from its compromise. Additionally, OMB Circular A-130 states that agencies must identify IT assets a

PDF page 2; first A-130 reference

Terms found: related terminology
related terminology · PDF page 6

icious actor intent, capabilities, targeting, and trends based on government threat intelligence as well as commercial sources of threat intelligence. Such information includes cybersecurity threats to the agency by nation-state and criminal actors as well as current threat actor tactics, techniques, and procedures. • Throughout

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 9581328 bytes

SHA-256 checksum

468ed492ab556be64e653581d62cdf047e3af1b3370605af653d03cf7cdb738c

Directed by OMB

Set expectations for agency preparation and response when personally identifiable information is breached.

Passage mentioning A-130

r additional information becomes available - in any medium or from any source - that would make it possible to identify an individual. 28 25 OMB Circular No. A-130, Managing lriformation as a Strategic Resource (July 28, 2016), available at https://www.whitehouse.gov/sites/default/files/omb/assets/OMB/circulars/a130/a130revised.pdf. 26 When an agency acts as a service provider, the ultimate responsibility for compliance with applicable requirements is not shifted (to the service provider). Agencies shall describe t

PDF page 8; first A-130 reference

Terms found: cloud
cloud · PDF page 39

System (Intranet/Shared Drive) YIN Oral Disclosure YIN Email: I <<Provide email address and note the agency, cloud server, personal, private>> Other: I <<Provide a detailed description of the medium>> Reported to US-CERT_, Law Enforcement, or Con~s Reported to US-CERT YIN Ifyes, complete the following: Reported to Law

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 8; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 27851364 bytes

SHA-256 checksum

a81ee756459770808be552168627c2495a7a962c51bc4878686181d5c585dd9c

Directed by OMB

Withdrew, modified, or paused specified OMB policies to reduce agency workload. Each listed policy received the treatment described in its section.

Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 208192 bytes

SHA-256 checksum

a3bc0ce86c63a9d1dc7c8aa8f0f0d16159178a90a32f4109500be41333e007f7

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2017-2018.

Passage mentioning A-130

applicable privacy requirements and managing privacy risks, and any other information determined necessary by the agency’s privacy program. See OMB Circular A-130, Managing Information as a Strategic Resource, Appendix I § 4(c)(2), 4(e)(1) (July 28, 2016). Additionally, reporting by entities other than federal Executive Branch civilian agencies is voluntary. 7 Each agency is required to develop and implement a breach response plan. A breach response plan is a formal document that includes the agency's policies a

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 173864 bytes

SHA-256 checksum

049d496342e438d4f94419370fea378e2d1b3c5b2cbeb97b68b7a633f3f45904

Directed by OMB

Explained implementation of the Program Management Improvement Accountability Act, addressing agency program and project management.

Passage mentioning A-130

program/project management policy is consistent with: • OMB’s Capital Programming Guide, which establishes fundamental P/PM principles. • OMB Circular A-130, Managing Information as a Strategic Resource, which provides standards for information technology management and security. • FAR Part 34 (Major System Acquisition) which addresses acquisition strategy, full and open competition, and Earned Value Management. • FAR Part 39 (Acquisition of Information Technology) which addresses risk management and mod

PDF page 23; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 23; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1813508 bytes

SHA-256 checksum

7252800f6d5e0d904a54b0c073ef9ad52eb43204f56f5ba11cdda6749b4d1456

Directed by OMB

Updated Circular A-123’s requirements for preventing and addressing improper payments, including management and reporting responsibilities.

Passage mentioning A-130

54 Fed. Reg. 25818-29 (June 19, 1989), available at https://www.whitehouse.gov/sites/default/files/omb/inforeg/final_guidance_pl100 -503.pdf. 34 OMB Circular A-130, Federal Agency Responsibilities for Maintaining Records About Individuals, available at https://www.whitehouse.gov/sites/default/files/omb/assets/OMB/circulars/a130/a130revised.pdf . 35 OMB Circular A-108, Federal Agency Responsibilities for Review, Reporting, and Publication under the Privacy Act, available at https://www.whitehouse.gov/sites/whitehous

PDF page 59; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 59; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 2385777 bytes

SHA-256 checksum

f6506bec1a33cfeebaa61eec9b11c7f76e2e575096fcd313015fa75bf47c8685

Directed by OMB

Directed agencies to reduce low-value administrative work and redirect effort toward higher-priority activities, changing selected reporting and management requirements.

Passage mentioning A-130

3 Because two sections of M-00-07 (titled "Principles" and "Policy") provide potentially helpful guidance to agencies regarding implementation of portions of A-130, these sections will continue to be publicly available on whitehouse.gov as informal supplementary information accompanying A-130. Their availability is for informational purposes only, and they impose no requirements on agencies. 11 [PDF page 12] OMB is rescinding this memorandum to ensure that agencies continue to implement the most current guidan

PDF page 11; first A-130 reference

Terms found: cloud
cloud · PDF page 4

ith data collection, OGP has migrated an inefficient and outdated legacy information architecture onto a new cloud-based agile enterprise platform . With the migration, GSA realized significant cost savings through consolidation, reuse of shared services, and elimination of antiquated and redundant operations. Through th

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 11; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 13910399 bytes

SHA-256 checksum

02f0f9b0043a38fdffb0838af0edf7a3b465216365d01a582b109eb114bfc0c0

Directed by OMB

Requested agency feedback on the developing Federal Data Strategy, including how the government should manage and use its data.

Passage mentioning A-130

n update on the development of the Federal Data Strategy and to solicit substantive feedback from agencies that are subject to the provisions of OMB Circular A-130, Managing Federal Information as a Strategic Resource. Agencies should forward this information to all bureaus that create, collect, acquire, process, disseminate, use, and store data and solicit feedback from personnel to maximize the usefulness of comments that OMB receives to this important strategy. Agencies should use the Federal Data Strategy webs

PDF page 1; first A-130 reference

Terms found: cloud
cloud · PDF page 10

e through data platforms: Facilitate the collaborative use of federal data on 29 Conscious Design Use modern cloud computing platforms. Prevent Monopolization of Federal Data: Periodically evaluate and regularly monitor how 30 data are released to the public with an eye towards preventing monopolization, to ensure Ethic

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 251625 bytes

SHA-256 checksum

131f3db27535abb28f23554ac63537514807422ddbe070fdb478165d10cfd088

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2018-2019.

Passage mentioning A-130

applicable privacy requirements and managing privacy risks, and any other information determined necessary by the agency’s privacy program. See OMB Circular A-130, Managing Information as a Strategic Resource, Appendix I § 4(c)(2), 4(e)(1) (July 28, 2016). Additionally, reporting by entities other than Federal Executive Branch civilian agencies is voluntary. 5 Each agency is required to develop and implement a breach response plan. A breach response plan is a formal document that includes the agency's policies an

PDF page 2; first A-130 reference

Terms found: related terminology
related terminology · PDF page 9

standing of the potential impacts to their mission. CDM accomplishes this by working with agencies to deploy commercial off-the-shelf tools on agency networks that provide enterprise-wide visibility of what assets, users, and activities are on their networks. This actionable information allows agencies to effectively monitor, defend, and r

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 720374 bytes

SHA-256 checksum

78de98f7d8c7b077c5f62c714d01ab701ba9dea7d35ee14ba5d19a35b495d141

Guidance for implementation

Integrated security and privacy into the Risk Management Framework and added preparation at the organization and system levels.

Terms found: cloud, FedRAMP, related terminology
cloud · PDF page 9

consistent, and cost-effective security and privacy capability inheritance; - Maximize the use of shared or cloud-based systems, services, and applications to reduce the number of authorizations needed across the organization; - Employ organizationally-tailored control baselines to increase the speed of security and pr

Extracted text; not checked against the page image.
FedRAMP · PDF page 131

urity Systems Policy CUI Controlled Unclassified Information DoD Department of Defense EO Executive Order FedRAMP Federal Risk and Authorization Management Program FIPS Federal Information Processing Standards FISMA Federal Information Security Modernization Act FOCI Foreign Ownership, Control, or Influence GRC Govern

Extracted text; not checked against the page image.
related terminology · PDF page 41

2 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-37r2 services or commercial off-the-shelf products. The level of assurance can also be based on many other factors that convince the organization that the requisite controls have been implemented and that a credible determination of control effectiv

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Authority; §§1.1–1.3; Appendix D

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 2270327 bytes

SHA-256 checksum

4f75e1136bb905a654f1bcd9eefefb4108f47597276ee5eec0688f6d96f6a01d

Directed by OMB

Strengthened the program for protecting high-value federal information and systems, updating responsibilities for managing their risks.

Passage mentioning A-130

rdance with burden reduction guidance in 0MB memorandum M-17-26, Reducing Burden for Federal Agencies by Rescinding and Modifying 0MB Memorandum. 1 Circular A-130 defines a 'Trustworthy information system' as an information system that is believed to be capable of operating within defined levels ofrisk despite the environmental disruptions, human errors, structural failures, and purposeful attacks that are expected to occur in its environment of operation. [PDF page 2]

PDF page 1; first A-130 reference

Terms found: cloud, related terminology
cloud · PDF page 6

agreements (SLAs) that enable the execution of HVA assessments for Federal information systems, 17 including cloud-managed services and contractor-owned, contractor-operated systems. Remediation: Agencies are responsible for developing prioritized remediation plans to address HVA assessment findings. Agencies are encour

Extracted text; not checked against the page image.
related terminology · PDF page 6

HVA assessments for Federal information systems, 17 including cloud-managed services and contractor-owned, contractor-operated systems. Remediation: Agencies are responsible for developing prioritized remediation plans to address HVA assessment findings. Agencies are encouraged to coordinate these remediation plans with their CIO,

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 355599 bytes

SHA-256 checksum

0a9a5232558f41c4f772db4b6894bc9d47aea627faccd0bfa428637d6280ca32

Assigned by law

Updated the federal standard for cryptographic-module security, continuing the requirements for hardware and software that perform cryptographic functions.

Source details and edition

Historical edition

Authority; effective September 22, 2019

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 310627 bytes

SHA-256 checksum

942a4f929dfbd2b4af2e4e03df7f6e6377054346afd9bee346ed0ebac5db384b

Directed by OMB

Updated implementation of federal information-quality policy, including agency practices for reviewing and correcting disseminated information.

Passage mentioning A-130

rding privacy and confidentiality is vital in the context ofopen data. The Open, Public, Electronic, anq, Necessary Government Data Act; 13 0MB Circular No. A-130 Managing Information as a Strategic Resource;14 and 0MB Memorandum M-13-13: Open Data Policy-Managing Information as an Asset15 require agencies to collect and create information in a way that supports :public transparency as well as downstream, secondary information dissemination and processing by third pa1iies, thereby making government information ac

PDF page 5; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1014931 bytes

SHA-256 checksum

caf66ee7b3e3e00830b845eed3c15950853d02d82f7a1da9cff29da1fb31472e

Directed by OMB

Updated identity, credential, and access management policy and rescinded several earlier authentication and identity memoranda.

Passage mentioning A-130

on Act of2014), although 0MB encourages owners and operators ofNSS to utilize the requirements in this document where appropriate. 2 Pursuant to 0MB Circular A-130, "information system" means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. [PDF page 2] II. Managing Identities, Credentials, and Access in Modern Government Advances in technology have enabled more digital interactions and business transactions,

PDF page 1; first A-130 reference

Terms found: cloud
cloud · PDF page 2

focused on cybersecurity, procurement, and management of a workforce capable of operating modem, frequently cloud-based environments. To address the challenges that have emerged alongside this opportunity, embedded within these efforts is an intensified focus on risk management and the adoption of processes, policies, a

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1024193 bytes

SHA-256 checksum

751627782157ffa1ab36f9519ada643f90f1345cd6cb7d14fd4e9a8b719c2b5d

Directed by OMB

Established principles and practices for a Federal Data Strategy, connecting information management with the use of data across government.

Passage mentioning A-130

the Information Quality Act, the Federal Records Act, and the Foundations for Evidence-Based Policymaking Act of 2018, among others. 3 lncludin~ 0MB Circular A-130 Managing Information as a Strategic Resource, among others. [PDF page 2] The Strategy is comprised ofthree components to guide Federal data management and use: • Mission Statement: The mission statement articulates the intent and core purpose ofthe Strategy. • Principles: The principles serve as motivational guidelines in the areas of Ethical Governa

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 645418 bytes

SHA-256 checksum

3b96d5701cf2c6374fb2ea065a1d7272ae5793616ca86723849737feed32a448

Directed by OMB

Updated the Data Center Optimization Initiative, addressing agency management and improvement of data-center resources.

Passage mentioning A-130

s, and other similar systems. Finally, numerous data centers will continue to be required for legal or logistical reasons. 12 In accordance with 0MB Circular A-130, Managing Information as a Strategic Resource, CI Os should work with Senior Agency Officials for Privacy (SAOPs) to ensure compliance with applicable privacy requirements and to manage privacy risk when considering the consolidation of data .centers that process personally identifiable information. 13 M-16-19, at 9. Available at: . https:/ /www.whiteh

PDF page 5; first A-130 reference

Terms found: cloud
cloud · PDF page 1

st savings, have improved their understanding of energy efficiency technologies, and have begun implementing cloud-based and hybrid environments. After eight years of work in consolidating and closing Federal data centers, 0MB has seen diminishing returns from agency data center closures. The Government has picked off m

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 2168507 bytes

SHA-256 checksum

a33571d6213979384994f6f16368111aaa22f027c53f42971100bdb3468981fe

Directed by OMB

Explained initial implementation of the Evidence Act, including learning agendas, responsible officials, and planning for the use of evidence in agency decisions.

Passage mentioning A-130

.html (bipartisan report which provided the impetus for Pub . L. No . 115-435). 1° Cf Office ofMgm't & Budget, Exec. Office of the President, 0MB Circular No. A-130 , Managing Information as a Strategic Resource, available athttps://www.whitehouse .gov/sites/whitehouse.gov/files/omb /circulars/ A 130/al 30revised.pdf; Office of Mgm 't & Budget, Exec . Office of the President, Management of Federal Information Resources (Dec. 12, 2000) (revising 0MB Circular No . A-130), available athttps://www.whitehouse.gov /wp-con

PDF page 3; first A-130 reference

Terms found: cloud
cloud · PDF page 23

activities, and mission outcomes; and • Strong business acumen and familiarity with data science approaches, cloud computing, cyber security, privacy, confidentiality, data analytics, statistical methods, policy analysis, information quality standards set out in the Information Quality Act (IQA),35 record disclosure law

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 3604742 bytes

SHA-256 checksum

85885990110076098a185876fa8c162d0bfdefcb51a0812503886efbf7634301

Directed by OMB

Updated the Trusted Internet Connections initiative to accommodate newer technology architectures and services while protecting agency communications.

Terms found: cloud, FedRAMP
cloud · PDF page 1

y traffic to flow through a physical TIC access point, which has proven to be an obstacle to the adoption of cloud-based infrastructure. C. Removing Barriers to C loud and Modern Technology Adoption One of the Administration's top priorities is the modernization of Federal information technology (IT) and promoting polic

Extracted text; not checked against the page image.
FedRAMP · PDF page 4

ined Wide Area Network (SD-WAN) technologies. 4. Remote Users: This use case is an evolution of the original FedRAMP TIC Overlay (FTO) activities. This use case demonstrates how a remote user connects to the agency's traditional network, cloud, and the Internet using government furnished equipment (GFE). 4

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 336533 bytes

SHA-256 checksum

4defeeebb0a1a5a8ff65b594dea45d43996d270d8d00449ec879edab7cad44d7

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2019-2020.

Passage mentioning A-130

status of information security programs throughout the year. SAOP Reporting: Given the importance of privacy, as highlighted in policies such as 0MB Circular A-130, Managing Information as a Strategic Resource, and 0MB Memorandum M-17- 12, Preparing for and Responding to a Breach of Personally Identifiable Information, agencies · must take appropriate measures to comply with privacy requirements and manage privacy risks. SAOPs are required to report annually and must submit each of the following items as separate d

PDF page 2; first A-130 reference

Terms found: related terminology
related terminology · PDF page 8

standing of the potential impacts to their mission. CDM accomplishes this by working with agencies to deploy commercial off-the-shelf tools on agency networks that provide enterprise-wide visibility of what assets, users, and activities are on their networks. This actionable information enables agencies to effectively monitor, defend, and

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 770349 bytes

SHA-256 checksum

fa5d947d2fdfdb7ca73bf9e6748c4ff0f25067a3111451c1106c051a5d35f5a0

Directed by OMB

Set standards and practices for program evaluation under the Evidence Act, connecting the use of information with evaluation of government programs.

Passage mentioning A-130

quirements may result in legal liability for the agency or individual employees. 37 Office of Mgmt. & Budget, Exec. Office of the President, 0MB Circular No . A-130 , Managing Information as a Strategic Resource, app. I,§ 4(h)(l)---(2), (4)---(7) (July 28, 2016), available at https://www .whitehouse.gov/sites/whitehouse. gov /files/ omb / circulars/ A I 3 0/al 30revised. pdf. 38 Office of Mgmt. & Budget, E xec. Office of the President, 0MB M-19-23 Phase I Implementation of the Foundations for Evidence-Based Policym

PDF page 20; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 20; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 17539570 bytes

SHA-256 checksum

c3f59655a53d2e8e94c0e349b6448f52bb0fe90e640e5896cfb1c33646c818d0

Later adopted in policy

Explained zero-trust architecture, an approach that evaluates access to resources rather than assuming trust based on network location.

Terms found: cloud, related terminology
cloud · PDF page 4

rust is a response to enterprise network trends that include remote users, bring your own device (BYOD), and cloud-based assets that are not located within an enterprise- owned network boundary. Zero trust focuses on protecting resources (assets, services, workflows, network accounts, etc.), not network segments, as the n

Extracted text; not checked against the page image.
related terminology · PDF page 28

ice that may be suspect (such as queries for possible malware command and control nodes). These feeds can be external services or internal scans and discoveries and can include attack signatures and mitigations. This is the only component that will most likely be under the control of a service rather than the enterprise. The weigh

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Abstract; §§1–2

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 966908 bytes

SHA-256 checksum

0290d6ece24874287316f4bf430fef770aa4ec08a2227c8f2c1e5b2ff975e03d

Guidance for implementation

Integrated security and privacy controls in a revised catalog. Baseline sets of controls were published separately in SP 800-53B.

Terms found: cloud, commercial services, related terminology
cloud · PDF page 16

for all types of computing platforms, including general purpose computing systems, cyber-physical systems, cloud-based systems, mobile devices, Internet of Things (IoT) devices, weapons systems, space systems, communications systems, environmental control systems, super computers, and industrial control systems. Those

Extracted text; not checked against the page image.
commercial services · PDF page 106

es using [Assignment: organization- defined automated mechanisms]. Discussion: Automated mechanisms include commercial services that provide notifications and alerts to organizations and automated scripts to monitor new posts on websites. Related Controls: None. (2) MONITORING FOR INFORMATION DISCLOSURE | REVIEW OF MONITORED SITES

Extracted text; not checked against the page image.
related terminology · PDF page 56

ed in cross-domain products, such as high- assurance guards. Such capabilities are generally not available in commercial off-the-shelf products. Information flow enforcement also applies to control plane traffic (e.g., routing and DNS). Related Controls: AC-3, AC-6, AC-16, AC-17, AC-19, AC-21, AU-10, CA-3, CA-9, CM-7, PL-9, PM-24, SA-17,

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Authority; §1; separation of controls and baselines

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 6073678 bytes

SHA-256 checksum

fc63bcd61715d0181dd8e85998b1e6201ae3515fc6626102101cab1841e11ec6

Directed by OMB

Directed improvements in identifying, managing, and correcting vulnerabilities in federal systems.

Passage mentioning A-130

ho can then use the reports to address vulnerabilities of which they may not have been aware. Bug bounty programs differ from VDPs As defined by 0MB Circular A-130. 2 See International Organization for Standardization/International Electrotechnical Commission (!SOI/EC) 29147 and !SOI/EC 30111. 1 [PDF page 2] by offering compensation based on established parameters to security researchers who report the vulnerabilities. While several organizations in the Federal government have used bug bounty programs effective

PDF page 1; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 1; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 4577334 bytes

SHA-256 checksum

495a0bc601cdd55ca3495294560925a3719438ec2da3b8585a529e04eeff1893

Guidance for implementation

Provided security and privacy control baselines for use with SP 800-53 Revision 5, giving agencies starting sets of safeguards to tailor to their needs.

Terms found: cloud
cloud · PDF page 12

for all types of computing platforms, including general-purpose computing systems, cyber-physical systems, cloud-based systems, mobile devices, and industrial and process control systems. The control baselines provide a starting point for organizations in the security and privacy control selection process. Using the ta

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§§1–2; baselines and tailoring

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 1627293 bytes

SHA-256 checksum

8a9dae903c2e4924d7b67c246faa32757d15f9731abb85922fad63f9ea0e02fa

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2020-2021.

Passage mentioning A-130

status of information security programs throughout the year. SAOP Reporting: Given the importance of privacy, as highlighted in policies such as 0MB Circular A-130, Managing Information as a Strategic Resource, and 0MB Memorandum M-17- 12, Preparing for and Responding to a Breach of Personally Identifiable Information, agencies must take appropriate measures to comply with privacy requirements and manage privacy risks. SAOPs are required to report annually and must submit each of the following items as separate doc

PDF page 2; first A-130 reference

Terms found: related terminology
related terminology · PDF page 8

standing of the potential impacts to their mission. CDM accomplishes this by working with agencies to deploy commercial off-the-shelf tools on agency networks that provide enterprise-wide visibility of what assets, users, and activities are on their networks. This actionable information enables agencies to effectively monitor, defend, and

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 10489455 bytes

SHA-256 checksum

d158e7210f1ae941efffe14de95dfc01027838e2f088c0eaba10a352af40d0ea

Directed by OMB

Updated how individuals could access Privacy Act records and consent to their disclosure, including through electronic processes.

Passage mentioning A-130

nsent, and identify relevant records, they should apply the minimization principle, one of the Fair Information Practice Principles identified in 0MB Circular A-130, Managing Information as a Strategic Resource, 18 and ensure that they limit the collection of personally identifiable information (Pil)19 to the minimum that is directly relevant-and necessary for this purpose.20 In applying this principle, agencies may customize the PII required by their access and consent forms in accordance with applicable law and p

PDF page 3; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1883421 bytes

SHA-256 checksum

40bacbbf830c479593b245b8f160d6d83c6058dafa40011c84d13119a957bb1e

Directed by OMB

Provided principles for agency regulation of artificial-intelligence applications, including the role of access to government data.

Passage mentioning A-130

such access to government data must be done in a manner consistent with the Open, Public, Electronic, and Necessary Government Data Act; 11 0MB Circular No. A-130 "Managing 10 Office ofMgm't & Budget, Exec. Office of the President, 0MB Circular A-119, Federal Participation in the Development and Use of Voluntary Consensus Standards and in Conformity Assessment Activities (Jan. 27, 2016), available at https://www .whitehouse.gov/wp-content/uploads/2020 /07 /revised circular a-119 as of I 22.pdf. 11 Pub. L. No. 115

PDF page 8; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 8; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 14968653 bytes

SHA-256 checksum

fe1c2b15852e26bef95a1312db24823ff191a0504511d2a81d99433ded12c857

Directed by OMB

Directed agencies to complete the transition to Internet Protocol version 6, updating the technical basis for network communications.

Passage mentioning A-130

e) with feature and performance parity with existing IPv4 services. 10 Agencies are required to maintain an IRM Strategic Plan in accordance with 0MB Circular A-130, Managing Iriformation as a Strategic Resource. 11 Native IPv6 refers to direct support ofIPv6 in a system or service without requiring the use ofIPv4 for basic communications. 12 0MB guidance has required agencies to acquire and deploy IPv6 capabilities in some systems since 2010. It is recommended that agencies inform the development of their plan wi

PDF page 3; first A-130 reference

Terms found: cloud, related terminology
cloud · PDF page 5

ogies and those network capabilities necessary to support other Federal initiatives such as IoT, adoption of cloud-based shared services, advanced wireless communications, and software defined and virtualized networks. The USGv6 Test Program will continue to provide government-wide conformance and general interoperabili

Extracted text; not checked against the page image.
related terminology · PDF page 3

v6 on existing systems that are already capable of running IPv6 (e.g., focusing on commodity IT systems with commercial off the shelf operating systems that are already capable of running IPv6.) 3 [PDF page 4] 5. Work with external partners to identify systems that interface with networked Federal information systems and develop plans

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 5874880 bytes

SHA-256 checksum

08eb8b79a83f5719d790ea0b09f13b5838a754e67e1e6e16ee9b1fb73ace4f53

Directed by the President

Directed federal cybersecurity improvements, including zero trust, cloud services, incident investigation, and secure software development. It assigned specific work to agencies and NIST.

Terms found: cloud, FedRAMP
cloud · PDF page 1

he full scope of its authorities and resources to protect and secure its computer systems, whether they are cloud-based, on-premises, or hybrid. The scope of protection and security must include systems that process data (information technology (IT)) and those that run the vital machinery that ensures our safety (oper-

Extracted text; not checked against the page image.
FedRAMP · PDF page 4

he Administrator of General Services acting through the Federal Risk and Authorization Man- agement Program (FedRAMP) within the General Services Administration, shall develop security principles governing Cloud Service Providers (CSPs) for incorporation into agency modernization efforts. To facilitate this work: (i) With

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§§3–4; cloud, zero trust and software security

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 286859 bytes

SHA-256 checksum

250578b7bdd468cb67e4f64d332f6648694302257670ae966d37b21aa138a282

Directed by OMB

Set logging requirements to help agencies investigate and recover from cybersecurity incidents, implementing work directed by Executive Order 14028.

Terms found: cloud, related terminology
cloud · PDF page 1

Federal information systems1 (for both on-premises systems and connections hosted by third parties, such as cloud services providers (CSPs)) is invaluable in the detection, investigation, and remediation of cyber threats. Executive Order 14028, Improving the Nation's Cybersecurity,2 directs decisive action to improve t

Extracted text; not checked against the page image.
related terminology · PDF page 40

Application Level • Commercial Off the Shelf (COTS) and Custom Applications • User Authentication (Success/Failure) • User and Administrator Application Use: o File and Object Access o Audit Log Access (Success/Failure) o System Access (Failure

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1369040 bytes

SHA-256 checksum

eddb4ac590d5ba3411f84e714207b715644891f44478efd693f6f73298006b69

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2021-2022.

Passage mentioning A-130

ance or the mere presence or absence of controls. Section VI: SAOP Reporting Given the importance of privacy, as highlighted in policies such as OMB Circular A-130, Managing Information as a Strategic Resource, and OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information, agencies must take appropriate measures to comply with privacy requirements and manage privacy risks. SAOPs are required to report annually and must submit each of the following items as separate doc

PDF page 7; first A-130 reference

Terms found: cloud, related terminology
cloud · PDF page 2

d path to deploy protections that make use of thorough data categorization. Agencies are taking advantage of cloud security services to monitor access to their sensitive data, and have implemented enterprise-wide logging and information sharing. • Ground truth testing. Traditionally, we have relied heavily on self-attes

Extracted text; not checked against the page image.
related terminology · PDF page 3

lps agencies prioritize actions to mitigate or accept cybersecurity risks. CDM works with agencies to deploy commercial off-the-shelf tools that provide enterprise-wide visibility of assets, users, and activities. This enables agencies to more effectively monitor, defend, and respond to cyber incidents. CISA will perform a program review

Extracted text; not checked against the page image.
Source details and edition

Rescinded by M-23-03, p. 1.

PDF page 7; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 501723 bytes

SHA-256 checksum

c7703eab6e9757d516bfad25f4f520fcbf665194bcf1d6c3c638537b0e1397a7

Guidance for implementation

Updated the common federal identity-credential standard originally developed under Homeland Security Presidential Directive 12.

Terms found: related terminology
related terminology · PDF page 115

(PIV) CMVP Cryptographic Module Validation Program CMYK Cyan, Magenta, Yellow, and Key (or blacK) COTS Commercial Off-the-Shelf CRL Certificate Revocation List CSE Communications Security Establishment CTC Cardholder to Card CTE Cardholder to External System CVC Card Verifiable Certificate DHS Department of Homeland Securit

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Foreword; HSPD-12; supersedes 201-2

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 1399143 bytes

SHA-256 checksum

3d305e90719e373963d3753d7d07d648361e35099e95e551763962e26456e73e

Directed by OMB

Directed agencies to move toward zero-trust security, building on NIST’s architectural guidance and Executive Order 14028.

Terms found: cloud, FedRAMP
cloud · PDF page 1

ace, to migrate the Federal Government to a zero trust architecture, and to realize the security benefits of cloud-based infrastructure while mitigating associated risks. 1 As used in this memorandum, “agency” has the meaning given in 44 U.S.C. § 3502. 2 Exec. Order No. 14028, 86 Fed. Reg. 26633 (2021). https://www.fede

Extracted text; not checked against the page image.
FedRAMP · PDF page 3

curity and Infrastructure Security Agency (CISA) and the Federal Risk and Authorization Management Program (FedRAMP) will evaluate options for encrypting email in transit. Further, Federal applications cannot rely on network perimeter protections to guard against unauthorized access. Users should log into applications, r

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 934880 bytes

SHA-256 checksum

62566e9492063e046d8b27bf16a2a48aaaee0864c6ccaa94f2c6270056a412ed

Guidance for implementation

Provided a framework of secure software-development practices supporting the software-security work directed by Executive Order 14028.

Terms found: cloud, commercial services
cloud · PDF page 5

y helpful feedback from Amazon Web Services, Apiiro, Blackberry, BSA | The Software Alliance, the Enterprise Cloud Coalition, the General Services Administration (GSA), Google, IBM, Medical Imaging & Technology Alliance (MITA), Microsoft, Oracle, the Software Assurance Forum for Excellence in Code (SAFECode), Synopsis,

Extracted text; not checked against the page image.
commercial services · PDF page 22

n automatic detection of known vulnerabilities in software components. Example 3: Use existing results from commercial services for vetting the software modules and services. Example 4: Ensure that each software component is still actively maintained and has not reached end of life; this should include new vulnerabilities found in t

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§1; EO 14028

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 739891 bytes

SHA-256 checksum

617746e553a9e2da49bfbd4eef0dfc3094758a39b869314e4173ac36605cde22

Directed by OMB

Applied NIST’s secure software-development guidance to federal software purchases under Executive Order 14028.

Terms found: cloud, FedRAMP
cloud · PDF page 2

poses of this memorandum includes firmware, operating systems, applications, and application services (e.g., cloud-based software), as well as products containing software. 11 The following conditions apply to the requirements of this memorandum: • These requirements apply to agencies’ use of software developed after the

Extracted text; not checked against the page image.
FedRAMP · PDF page 4

t that is being acquired, as defined in M-21-30. d. A third-party assessment provided by either a certified FedRAMP Third Party Assessor Organization (3PAO) or one approved by the agency shall be acceptable in lieu of a software producer's self-attestation, including in the case of open source software or products incorp

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 406359 bytes

SHA-256 checksum

85b119f5b1e50a2a9bfb2ae19a9c0f52472e94a8e08fe474141849a1a4f6c6c2

Directed by OMB

Directed agencies to begin preparing for migration to quantum-resistant cryptography under National Security Memorandum 10.

Terms found: cloud, FedRAMP
cloud · PDF page 3

em or hosting information system(s) is/are hosted by: o The agency (on premise); o A commercially operated cloud service provider, in which case the name of the commercial provider must be supplied; 17 11 This criterion refers to data that if recorded now, and later decrypted by a CRQC in 2035, would still be consider

Extracted text; not checked against the page image.
FedRAMP · PDF page 3

16 For a list of CQRC-vulnerable algorithms, see Appendix B. 17 For cloud products or services accredited by FedRAMP, agencies should work with the FedRAMP PMO to obtain a cryptographic implementation inventory. 3 [PDF page 4] o A Government-operated cloud service provider, in which case the name of the agency p

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 255063 bytes

SHA-256 checksum

02e7a4ee3289e3dfcc81bdb43d2e21645b68e6f364a9889dda222b785ecfe6e6

2022-12-02OMB memorandum

M-23-03 FY23 FISMA Guidance

Directed by OMB

Set reporting instructions for agency information security programs for fiscal year 2023.

Passage mentioning A-130

ions to modernize the Federal Government’s investigative and remediation capabilities. If incidents are not properly reported—or updates are 3 OMB Circular A-130, Managing Information as a Strategic Resource, § 4(h) (July 28, 2016). 4 Id. 5 As defined in OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information, § III(C) (Jan. 3, 2017). This definition applies to “breach” throughout this memorandum. [PDF page 4] 4 improperly logged—the detection, investigation,

PDF page 3; first A-130 reference

Terms found: cloud, related terminology
cloud · PDF page 16

, CISA should initiate its vulnerability scanning service from multiple vantage points, including commercial cloud infrastructure, and from dynamically selected source addresses. To ensure CISA can perform this function effectively, each Federal civilian agency shall: • Ensure that CISA and agency security teams ha

Extracted text; not checked against the page image.
related terminology · PDF page 4

prioritize actions to mitigate or accept cybersecurity risks. The CDM Program works with agencies to deploy commercial off-the-shelf tools that provide enterprise-wide visibility of assets, users, and activities. This enables agencies to more effectively monitor, defend, and respond to cyber incidents. The CISA CDM Program Management

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 318969 bytes

SHA-256 checksum

3a0e679523207402606b2f3af7da3b32a8199e01bd13e1cce7f9b38c49900235

Assigned by law

Assigned OMB duties to guide agency migration to quantum-resistant cryptography, linked to the publication of NIST standards.

Source details and edition

Historical edition

§4: NIST standards and OMB migration guidance

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 207853 bytes

SHA-256 checksum

e02c4a7f703e17156fe92f8219ffea09715b3fcc4cff21065eaab093b6320d17

Assigned by law

Put FedRAMP into law. It used A-130’s authorization terminology and NIST’s cloud definition, assigning responsibilities for the federal cloud-security program.

Terms found: cloud, FedRAMP
cloud · PDF page 1055

orma- tion as a Strategic Resource’, or any successor document. ‘‘(4) C LOUD COMPUTING .—The term ‘cloud computing’ has the meaning given the term in Special Publication 800–145 of the National Institute of Standards and Technology, or any successor document. ‘‘(5) C LOUD SERVICE PROVIDER .—The term ‘cloud se

Checked against the original PDF page on October 10, 2026.
FedRAMP · PDF page 1055

[PDF page 1055] SEC. 5921. FEDRAMP AUTHORIZATION ACT. (a) SHORT TITLE.—This section may be cited as the ‘‘FedRAMP Authorization Act’’. (b) A MENDMENT.—Chapter 36 of title 44, United States Code, is amended by adding at the end the following

Checked against the original PDF page on October 10, 2026.
Source details and edition

Historical edition

Division E, Title LIX, Subtitle C, §5921; enacts 44 USC 3607–3616

Date supplied by the source

The PDF contains the full law. The reading excerpt and term flags cover the FedRAMP subtitle only.

Searchable text

Downloaded 2026-10-10 · 4646080 bytes

SHA-256 checksum

9e5d37dfa7d1282073c16f3dde21978078f62f58f9db36f4828e270e02de933f

Directed by OMB

Updated financial-system risk and compliance guidance, connecting financial-management requirements with agency technology and information policies.

Passage mentioning A-130

for Enterprise Risk Management and Internal Control, 4 Appendix A to Circular No. A-123, Management of Reporting and Data Integrity Risk,5 OMB Circular No. A-130, Managing Information as a Strategic Resource,6 Code of Federal Regulations (CFR) Title 48 Federal Acquisition Regulation, as well as associated financial management system guidance which includes but is not limited to relevant financial management memoranda and operational directives. • Use a risk-based approach to determine whether the Agency’s financ

PDF page 4; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 4; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 862507 bytes

SHA-256 checksum

c9be2ac193deb1d64445f69f00446e3646ad5cd022b9a1e233d073ee0779d838

Directed by OMB

Updated the implementation and deadlines of M-22-18’s requirements for software acquired by federal agencies.

Terms found: cloud
cloud · PDF page 2

s memorandum, “software” includes firmware, operating systems, applications, and application services (e.g., cloud-based software), as well as products containing software.3 This memorandum modifies the deadlines by which agencies must collect attestation letters. Agencies must collect attestations for critical software

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

Full text; A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 334237 bytes

SHA-256 checksum

f9f920e49032707f9a58a4ef32fdf44ef5253ed5c66f1bc8de3824fcedbcfa5b

Directed by OMB

Set expectations for designing and delivering federal websites and digital services under the 21st Century Integrated Digital Experience Act.

Passage mentioning A-130

cies, 67 Fed. Reg. 8452, and guidance from the National Archives and Records Administration for the management of electronic records. 18 See OMB Circular No. A-130, Managing Information as a Strategic Resource (2016); 44 U.S.C. § 3506(d). 19 For example, when a website or digital service is focused on improving a ccess for a unique and specific class of people within or across agencies. [PDF page 8] 8 they are being directed to appropriate content and tools when they seek to take advantage of an agency’s infor

PDF page 7; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 7; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 220396 bytes

SHA-256 checksum

fe840641ae1274d4162744c6d7244ac40a3885ccde4f40d15e1dc60f7d588088

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2024.

Passage mentioning A-130

es and CISA to monitor vulnerabilities and threats to their systems in near real-time and to more effectively respond to cyber incidents. This 3 OMB Circular A-130, Managing Information as a Strategic Resource, § 4(h) (July 28, 2016). 4 Id. 5 As defined in OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information, § III(C) (Jan. 3, 2017). This definition applies to “breach” throughout this memorandum. 3 [PDF page 4]

PDF page 3; first A-130 reference

Terms found: cloud, related terminology
cloud · PDF page 17

, CISA should initiate its vulnerability scanning service from multiple vantage points, including commercial cloud infrastructure, and from dynamically selected source addresses. To ensure CISA can perform this function effectively, each Federal agency, other than the Department of Defense and agencies in the Intelligen

Extracted text; not checked against the page image.
related terminology · PDF page 3

Mitigation Capabilities CISA’s Continuous Diagnostics and Mitigation (CDM) Program The CDM program deploys commercial off-the-shelf CDM security tools to agencies for an initial two-year period, allowing those agencies and CISA to monitor vulnerabilities and threats to their systems in near real-time and to more effectively respond to cy

Extracted text; not checked against the page image.
Source details and edition

Rescinded by M-25-04 (p. 1).

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 367173 bytes

SHA-256 checksum

d72205286cc287fc6d7cdc3d05d6f53ecb6fcfd4e2da390e6ebf22530ac3823c

Directed by OMB

Strengthened agency management of digital accessibility under Section 508, including testing and monitoring technology used to deliver services.

Passage mentioning A-130

st and evaluate interoperability, compatibility, and the functionality of ICT with common or frequently used assistive technology. As required by OMB Circular A-130, agencies must generally support and maximize interoperability when designing or developing information systems, where appropriate.22 • Agencies should continuously monitor accessibility of ICT solutions after deployment as part of ongoing maintenance and should validate any updates to ICT solutions to ensure they will not negatively impact accessibili

PDF page 6; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 6; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 270088 bytes

SHA-256 checksum

23dab5505b0b957354ff9d1201dc8a6bbfaba67f52d26eee21fe9a91b2222f29

Directed by OMB

Set requirements for agency use of artificial intelligence, including governance and management of risks to rights and safety. M-25-21 replaced it.

Passage mentioning A-130

Internal Control (July 15, 2016), https://www.whitehouse.gov/wp- content/uploads/legacy_drupal_files/omb/memoranda/2016/m-16-17.pdf. 16 See OMB Circular No. A-130, Managing Information as a Strategic Resource, Appx. I, sec. 5(b) (July 28, 2016), https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/circulars/A130/a130revised.pdf. 17 An example of a qualifying body includes agency Data Governance Bodies, established by OMB Memorandum M-19-23, Phase 1 Implementation of the Foundations for Evidence-B

PDF page 8; first A-130 reference

Terms found: cloud, related terminology
cloud · PDF page 25

s. Such steps may include promoting interoperability so that, for example, procured AI works across multiple cloud environments, and ensuring that vendors do not inappropriately favor their own products at the expense of competitors’ offerings. iv. Maximizing the Value of Data for AI. In contracts for AI products and

Extracted text; not checked against the page image.
related terminology · PDF page 3

of the territories and possessions of the United States, and their various subdivisions; or Government-owned contractor-operated facilities, including laboratories engaged in national defense research and production activities. 44 U.S.C. § 3502(1); see AI in Government Act of 2020 § 102(2) (defining “agency” by reference to § 3502); A

Extracted text; not checked against the page image.
Source details and edition

Rescinded and replaced by M-25-21 (p. 1).

PDF page 8; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 530549 bytes

SHA-256 checksum

89e548f806c3e2c6702ab9996f92344b5c05ec0f26e0d4874ddb402449c044fb

Guidance for implementation

Revised requirements for protecting controlled unclassified information in nonfederal systems, updating the technical safeguards used within that program.

Terms found: cloud, related terminology
cloud · PDF page 32

processes that are distributed across multiple organizations) and actions that occur in service-oriented or cloud- based architectures. Monitoring and auditing requirements can be balanced with other system needs. For example, organizations may determine that systems must have the capability to log every file access —

Extracted text; not checked against the page image.
related terminology · PDF page 74

or hidden files, or hidden in files using techniques such as steganography. Malicious code may be present in commercial off-the-shelf software and custom-built software and could include logic bombs, backdoors, and other types of attacks that could affect organizational mission and business functions. Periodic scans of the system and real

Extracted text; not checked against the page image.
Source details and edition

Historical edition

§1; authority and applicability

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 1593213 bytes

SHA-256 checksum

3e4631df8b5d61f40a6e542b52779ef30ddbbfff31e09214fa94ad6e6f5e6d08

Assigned by law

Updated FedRAMP following the 2022 Act, defining its scope and agency responsibilities. It replaced OMB’s 2011 cloud-authorization memorandum.

Terms found: cloud, FedRAMP, related terminology
cloud · PDF page 1

morandum from the Federal Chief Information Officer (CIO), “Security Authorization of Information Systems in Cloud Computing Environments,”1 to safely accelerate the adoption of cloud computing products and services by Federal agencies, and help those agencies avoid duplicating efforts by offering a consistent and reusab

Checked against the original PDF page on October 10, 2026.
FedRAMP · PDF page 1

M-24-15 MEMORANDUM FOR THE HEADS OF EXECUTIVE DEPARTMENTS AND AGENCIES FROM: SHALANDA D. YOUNG SUBJECT: (FedRAMP) The Federal Risk and Authorization Management Program, known as FedRAMP, was established by the Office of Management and Budget (OMB) through a December 8, 2011 memorandum from the Federal Chief Informatio

Checked against the original PDF page on October 10, 2026.
related terminology · PDF page 4

ure development that commercial cloud providers give to their core products to succeed in the marketplace. Commercial providers similarly are incentivized to integrate improved security practices that emerge from their engagement with FedRAMP into their core services, benefiting all customers. Structurally, FedRAMP consists of two p

Checked against extracted text; PDF page listed.
Source details and edition

Current applicability not assessed

Scope; agency responsibilities; rescission of 2011 memorandum

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 336948 bytes

SHA-256 checksum

07aabe7fd0baa34e3c77b7c9537204c6ac1caff473e04af8dc7e40743c30250a

Assigned by law

Standardized a mechanism for establishing shared encryption keys designed to resist attacks using quantum computers.

Source details and edition

Historical edition

Foreword; authority; implementation schedule

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1252341 bytes

SHA-256 checksum

fe1f12f32a7e44ec9fdebbf400cda843a40b506dee676725234dc6f7923b6cac

Assigned by law

Standardized a lattice-based digital-signature method designed to resist quantum-computing attacks.

Source details and edition

Historical edition

Foreword; authority; implementation schedule

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 3291746 bytes

SHA-256 checksum

57239b9f84c03227eda3ca0991204dc7764c79af9ce2e6824eda774918d46b6b

Assigned by law

Standardized a hash-based digital-signature method designed to resist quantum-computing attacks.

Source details and edition

Historical edition

Foreword; authority; implementation schedule

Date supplied by the source

Searchable text

Downloaded 2026-10-10 · 1055752 bytes

SHA-256 checksum

8ef34228276f3386d23cb0da8c14592b8cfb0db3358016bba64df7a004f8d13d

Directed by OMB

Set policy for acquiring artificial intelligence, including planning for risks and coordinating agency responsibilities. M-25-22 replaced it.

Passage mentioning A-130

This is a foundational principle of acquisition, including IT acquisition. See, e.g., FAR 7.104(a) and CAPITAL PROGRAMMING GUIDE – A-11, PART 7; OMB Circular A-130, Managing Information as a Strategic Resource, Appendix II. Additionally, such collaboration and consultation is necessary to implement certain requirements under the Federal Information Technology Acquisition Reform Act (FITARA), which prohibits agencies subject to the CFO Act, besides the Department of Defense, from “…enter[ing] into a contract or othe

PDF page 5; first A-130 reference

Terms found: cloud, commercial services, related terminology
cloud · PDF page 19

contract, such as for an operating system or for cloud computing services, when the elements of the definition above are met. The practices below35 will help agencies address the unique challenges of such contracts, including to protect the rights and safety of

Extracted text; not checked against the page image.
commercial services · PDF page 31

cases; viii. Explore authorities available to the agency in addition to those provided by the FAR, such as commercial services opening pilots and other transactions authorities, when they may be more suitable than the FAR in lowering barriers to entry; 56 Ali Crawford and Ido Wulkan, "Federal Prize Competitions" (Center for Security

Extracted text; not checked against the page image.
related terminology · PDF page 3

f the territories and possessions of the United States, and their various subdivisions; or Government -owned contractor-operated facilities, including laboratories engaged in national defense research and production activities. 44 U.S.C. § 3502(1); see AI in Government Act of 2020 § 102(2) (defining “agency” by reference to § 3502); A

Extracted text; not checked against the page image.
Source details and edition

Rescinded and replaced by M-25-22 (p. 1).

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 458682 bytes

SHA-256 checksum

eb9d3587e1556577737b9ce405053b1b18e0b664f73ce65c043898948a147e0a

Directed by OMB

Set reporting instructions for agency information security and privacy programs for fiscal year 2025.

Passage mentioning A-130

he General Services Administration (GSA), manages related contracts on behalf of the agencies, agencies are responsible for the state of their 3 OMB Circular A-130, Managing Information as a Strategic Resource, § 4(h) (July 28, 2016). 4 Id. 5 The term “breach” is defined in OMB Memorandum M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information, § III(C) (Jan. 3, 2017). This definition applies to the term “breach” throughout this memorandum. 6 The CFO Act agencies are defined in 31

PDF page 4; first A-130 reference

Terms found: cloud, FedRAMP, related terminology
cloud · PDF page 2

trategy’s call to modernize systems and continue to build our collective defense: Improving agency’s secure cloud adoption: As described in OMB Memorandum M-24-15, Modernizing the Federal Risk and Authorization Management Program (FedRAMP), the purpose of FedRAMP is to increase Federal agencies’ adoption and secure use

Extracted text; not checked against the page image.
FedRAMP · PDF page 2

: As described in OMB Memorandum M-24-15, Modernizing the Federal Risk and Authorization Management Program (FedRAMP), the purpose of FedRAMP is to increase Federal agencies’ adoption and secure use of the commercial cloud, by providing a standardized reusable approach to security assessments and authorizations for cloud

Extracted text; not checked against the page image.
related terminology · PDF page 4

prioritize actions to mitigate or accept cybersecurity risks. The CDM program works with agencies to deploy commercial off-the-shelf tools that provide enterprise-wide visibility of assets, users, and activities. This enables agencies to more effectively monitor, defend, and respond to cyber incidents. The CISA CDM Program Management Off

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 4; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 297627 bytes

SHA-256 checksum

de45d2e225c41cd9a7aa3d18bec7004c81829d0dbca211f116171cfdb8507f29

Directed by OMB

Explained open-data access and management requirements under the Evidence Act, including safeguards for privacy, confidentiality, and security.

Passage mentioning A-130

Managing Information as an Asset. Agencies should apply this guidance consistent with applicable laws5 and existing OMB guidance, including OMB Circular No. A-130.6 SCOPE AND APPLICABILITY This Memorandum provides guidance concerning the following requirements from the Act: • Open by default. Except as provided by this guidance, each agency is required to: o Maintain each agency data asset in an open format;7 and o Maintain each public data asset as an open Government data asset and under an open lice

PDF page 2; first A-130 reference

Terms found: related terminology
related terminology · PDF page 5

of the territories and possessions of the United States, and their various subdivisions; or Government-owned contractor-operated facilities, including laboratories engaged in national defense research and production activities.”24 Data means “recorded information, regardless of form or the media on which the data is recorded.”25

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 448618 bytes

SHA-256 checksum

1ccecff6ecfacf690df0263dafe4a0ed7da0d67a192309533351a060a2af42c1

Directed by OMB

Updated agency artificial-intelligence policy and replaced M-24-10. It kept acceptance of AI-use risks separate from authorization of information systems under A-130.

Passage mentioning A-130

accepting risk for AI use cases is separate from, and does not supersede, the authorization process for information systems, consistent with 0MB Circular No. A-130, Managing Information as a Strategic Resource, https:/ /bidenwhitehouse.archives.gov/wp- content/uploads/legacy drupal files/omb /circulars/ A 130/a 130revised.pdf. 23 Given the importance of context-specific guidance on AI, agencies are encouraged to continue implementing their agency's AI principles and guidelines, so long as they do not conflict with

PDF page 12; first A-130 reference

Terms found: related terminology
related terminology · PDF page 4

of the territories and possessions of the United States, and their various subdivisions; or Government-owned contractor-operated facilities, including laboratories engaged in national defense research and production activities. 44 U.S.C. § 3502(1); see AI in Government Act of2020 § 102(2) (defining "agency" by reference to§ 3502); Adv

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 12; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 2629748 bytes

SHA-256 checksum

0aab0aa4eaeac969ed93894d3940c5dc9d0b7377048171b164a439e8b9e49813

Directed by OMB

Updated policy for acquiring artificial intelligence and replaced M-24-18. It applied privacy requirements to acquired systems and relevant contractor uses.

Passage mentioning A-130

ta, legal, program evaluation, and other areas as necessary. 15 Executive Order 14179. 4 [PDF page 5] d. Protect Privacy. Consistent with 0MB Circular No. A-130, 16 agencies shall establish policies and processes, including contractual terms and conditions, that ensure compliance with privacy requirements in law and policy whenever agencies acquire an AI system or service, or an agency contractor uses an AI system or service, that will create, collect, use, process, store, maintain, disseminate, disclose, or di

PDF page 5; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 5; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 1399862 bytes

SHA-256 checksum

e157538371eb9665fabdacff748788fc6afc0575bb3661d15b146f3138084cd8

Guidance for implementation

Updated NIST’s digital-identity guidance for assessing identity risks and selecting appropriate identity-proofing, authentication, and federation practices.

Terms found: cloud, FedRAMP
cloud · PDF page 28

model in which the subscriber controls a device with software (i.e., a digital wallet) or an account with a cloud service provider (i.e., a hosted-wallet) that acts as the IdP . In the terminology of the “three-party model,” the CSP is the issuer, the IdP is the holder (i.e., the users device or agent operating on their

Extracted text; not checked against the page image.
FedRAMP · PDF page 67

S Domain Name System FACT Act Fair and Accurate Credit Transaction Act of 2003 FAL Federation Assurance Level FEDRAMP Federal Risk and Authorization Management Program 57 [PDF page 68] NIST SP 800-63-4 July 2025 Digital Identity Guidelines FIPS Federal Information Processing Standards FMR False Match Rate FNMR False Non-Matc

Extracted text; not checked against the page image.
Source details and edition

Historical edition

Authority; introduction

Only the month is known; the first day is used for sorting.

Searchable text

Downloaded 2026-10-10 · 858054 bytes

SHA-256 checksum

2f5b107de218a0fc3fe7f7e91b2ece5babb001eda5745b7c568a3cc876002f2d

Directed by OMB

Implemented procurement policy for unmanned aircraft systems and applied A-130 safeguards when those systems process federal information.

Passage mentioning A-130

icies and implementation of technical controls (e.g., methods of login for the ground control station) conform to applicable requirements in OMB Circular No. A-130, Managing Information as a Strategic Resource. 2 As defined in 49 U.S.C. § 44801. 3 Pub. L. No. 118-31, § 1829. 4 As defined in 44 U.S. Code § 3502. 5 Pub. L. No. 118-31, § 1829. 6 “Intelligence community” has the meaning given in 50 U.S.C. § 3003. 7 “Federal information” is “information created, collected, processed, maintained, disseminated, disclos

PDF page 2; first A-130 reference

Source details and edition

Current applicability not assessed

PDF page 2; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 376605 bytes

SHA-256 checksum

bba39cbd4cb783d2ecb58bfe2c73028e4d84e35507905b991fd8b2d412f4cffc

Directed by OMB

Directed accelerated migration to quantum-resistant cryptography under the 2022 preparedness law and June 2026 executive direction.

Passage mentioning A-130

lgorithms listed in Appendix A of this memorandum; or o Contain data expected to remain mission-sensitive in 2030. 3. System Modernization OMB Circular No. A-130 requires agencies to “consider information security . . . for all resource planning and management activities throughout the system development life cycle so that risks are appropriately managed.” Migration to PQC must be a primary information security consideration for agencies. Through their inventories, agencies have already identified legacy system

PDF page 3; first A-130 reference

Terms found: cloud, FedRAMP
cloud · PDF page 3

s for which migration would be too difficult or costly. Agencies must incorporate PQC upgrades into planned cloud migrations, software development lifecycles, and hardware- refresh schedules to maximize efficiency and minimize costs. Systems incapable of supporting PQC or hybrid cryptography must be identified and given

Extracted text; not checked against the page image.
FedRAMP · PDF page 4

for products used by the agency in those categories include PQC integration. Agencies should engage their FedRAMP-authorized cloud service providers to delineate PQC migration responsibilities within the shared responsibility model. CISA and the Department of War (DOW), in coordination with GSA, will lead PQC migration

Extracted text; not checked against the page image.
Source details and edition

Current applicability not assessed

PDF page 3; first A-130 reference

Date taken from the document heading

Searchable text

Downloaded 2026-10-10 · 283167 bytes

SHA-256 checksum

515af70472d3a4a2107c61a1bc5f8014523d99feab9b2cf92a95e4bcc790da2c

2016-12-15NIST archive index

NIST historical index of withdrawn FIPS

Related development

Recorded withdrawals of historical federal standards, helping identify when particular editions ceased to apply.

Source details and edition

Historical withdrawal list

Rows for FIPS 31, 46, 46-3, 65 and 140-1

Archive date; the listed withdrawals occurred earlier.

Searchable text

Downloaded 2026-10-10 · 110601 bytes

SHA-256 checksum

c476380eb9f411835eff191d4dd10dd9293fdeff8ea14da7f7a5aa0afb59c627

Notes and sources

  1. A-130: Managing Information as a Strategic Resource, §§3, 5, 6 and 9. Original. E-Government Act / FISMA 2002, Title III, §§303–304. Original. Federal Information Security Modernization Act, §2. Original. Security Authorization of Information Systems in Cloud Computing Environments, Introduction. Original. FedRAMP Authorization Act in P.L. 117-263, §5921. Original. Modernizing the Federal Risk and Authorization Management Program (FedRAMP), Scope and responsibilities. Original. ↩
  2. FIPS 12: Federal Information Processing Standards index (reproduces A-71), §4.6. Original. Brooks Act, P.L. 89-306, §111(f). Original. Privacy Act, P.L. 93-579, §3. Original. FIPS 31: Guidelines for ADP Physical Security, Foreword. Original. FIPS 46: Data Encryption Standard, Authority. Original. FIPS 65: Guideline for Automatic Data Processing Risk Analysis, Introduction. Original. Paperwork Reduction Act of 1980, 44 USC 3504–3506. Original. ↩
  3. The 1965 A-71 is reproduced in FIPS 12, §4.6. The collection lacks standalone copies of the 1978 transmittal and Bulletins 88-16 and 90-08; their role is documented in OMB’s 1996 preamble and, for contingency planning, NBS SP 500-85. FIPS 12: Federal Information Processing Standards index (reproduces A-71), §4.6. Original. Transmittal 3 explanatory preamble, Background and discussion of security plans. Original. NBS SP 500-85: Executive Guide to ADP Contingency Planning, Abstract and question 6. Original. ↩
  4. A-130: initial circular, 50 FR 52730, summary; PDF page 288. Original. ↩
  5. A-130: initial circular, 50 FR 52730–52751; purpose, authorities and Appendix III. Original. Paperwork Reduction Act of 1980, 44 USC 3504–3506 as enacted. Original. Brooks Act, P.L. 89-306, §111(f). Original. Privacy Act, P.L. 93-579, §3. Original. ↩
  6. Effective December 12, 1985; published December 24. The PDF is the full Federal Register issue; the reading excerpt contains only A-130, PDF pages 288–309 (printed pages 52730–52751). ↩
  7. A-130: Transmittal 1, 58 FR 36068; Background, Structure of this Revision, Summary of Revisions and Appendix I. Original. Computer Security Act of 1987, P.L. 100-235, §§2–6. Original. ↩
  8. Effective June 25, 1993; published July 2. Appendix III remained unchanged. ↩
  9. A-130 Transmittal 2: original Federal Register text, 59 FR 37906–37928; section 8b. Original. Transmittal 3 explanatory preamble, History of Transmittals 1 and 2. Original. FIPS 140-1: Security Requirements for Cryptographic Modules, Authority and applicability. Original. ↩
  10. Effective July 15, 1994; published July 25. The source link provides the original notice as HTML. Its printed citation is 59 FR 37906–37928; the archive’s “Page 0” label is a metadata error. ↩
  11. A-130: Transmittal 3, Appendix III, §2(a), definition of adequate security. Original. ↩
  12. A-130: Transmittal 3, Appendix III, parts A–B. Original. A-130 Transmittal 3: Federal Register final notice, 61 FR 6428–6431. Original. Computer Security Act of 1987, P.L. 100-235, §§3–6. Original. SP 800-18: Guide for Developing Security Plans, Introduction. Original. ↩
  13. Dated February 8, 1996; published February 20. Clinger–Cohen was enacted February 10. OMB discussed further implementation work in the preamble. A-130 Transmittal 3: Federal Register final notice, 61 FR 6428–6431. Original. ↩
  14. A-130: Transmittal 4 consolidated circular, Sections 3, 8b and 9. Original. Transmittal 4 final Federal Register notice, 65 FR 77677; incorporation of M-00-07 and M-00-10. Original. GPEA implementation guidance, later A-130 Appendix II, Implementation guidance. Original. Clinger–Cohen Act in P.L. 104-106, Division E. Original. GISRA in P.L. 106-398, Title X, Subtitle G. Original. E-Government Act / FISMA 2002, Title III. Original. ↩
  15. The April 13 Federal Register notice was the proposal. The final transmittal is dated November 28 and was published December 12. The main PDF and the four appendix texts are separate files in the library. A-130 proposed revision (not final), 65 FR 19933. Original. Transmittal 4 final Federal Register notice, 65 FR 77677. Original. ↩
  16. A-130: Managing Information as a Strategic Resource, §4, Basic Considerations; PDF page 3. Original. ↩
  17. A-130: Managing Information as a Strategic Resource, Sections 3, 5, 6 and 9; Appendices I–II. Original. A-130 2016 final notice, 81 FR 49689. Original. Federal Information Security Modernization Act, §2; 44 USC 3553–3554 and 3557. Original. SP 800-37 Rev. 2: Security and Privacy RMF, §§1–2. Original. ↩
  18. Effective July 28, 2016. This is the latest comprehensive revision identified in the official collections searched through October 10, 2026. Later laws and memoranda also affect agency responsibilities. A-130 2016 final notice, 81 FR 49689. Original. ↩
  19. A-130: Managing Information as a Strategic Resource, §5 and Appendix I. Original. ↩
  20. E-Government Act / FISMA 2002, Title III, §§303–304. Original. ↩
  21. SP 800-37 Rev. 2: Security and Privacy RMF, §2 and Appendix D. Original. ↩
  22. Quantum Computing Cybersecurity Preparedness Act, §4. Original. ↩
  23. HSPD-12: Common Identification Standard, ¶¶2–4; see also M-04-04 in the source library. Original. ↩
  24. SP 800-171 Rev. 3: Protecting CUI, §1, purpose and applicability. Original. ↩
  25. Modernizing the Federal Risk and Authorization Management Program (FedRAMP), Introduction, scope and responsibilities. Original. ↩
  26. A-130: Managing Information as a Strategic Resource, §3; see also FISMA 2014, 44 USC 3557. Original. ↩
  27. E-Government Act / FISMA 2002, Title III, §§301, 303–304. Original. Federal Information Security Modernization Act, §2. Original. A-130: Managing Information as a Strategic Resource, §§3, 6 and 9. Original. ↩
  28. FIPS 31: Guidelines for ADP Physical Security, Foreword and scope. Original. FIPS 65: Guideline for Automatic Data Processing Risk Analysis, Introduction. Original. NBS SP 500-85: Executive Guide to ADP Contingency Planning, Abstract and question 6. Original. FIPS 46: Data Encryption Standard, Authority. Original. ↩
  29. Transmittal 3 explanatory preamble, Responses 5–6. Original. SP 800-12: An Introduction to Computer Security, Introduction. Original. SP 800-18: Guide for Developing Security Plans, Introduction. Original. SP 800-18 Rev. 1: Security Plans, §1. Original. SP 800-30: Risk Management Guide, §1. Original. SP 800-30 Rev. 1: Risk Assessments, §1. Original. ↩
  30. E-Government Act / FISMA 2002, §303. Original. FIPS 199: Security Categorization, §3. Original. FIPS 200: Minimum Security Requirements, §§3–4. Original. SP 800-53: Recommended Security Controls, §1. Original. SP 800-53 Rev. 4: Security and Privacy Controls, Appendix J. Original. SP 800-53 Rev. 5: Security and Privacy Controls, §1. Original. SP 800-53B: Control Baselines, §2. Original. ↩
  31. SP 800-37: Certification and Accreditation, §1. Original. SP 800-37 Rev. 1: Risk Management Framework, §2. Original. SP 800-37 Rev. 2: Security and Privacy RMF, §§1–2. Original. SP 800-137: Continuous Monitoring, §1. Original. ↩
  32. FIPS 46: Data Encryption Standard, Authority. Original. FIPS 140-1: Security Requirements for Cryptographic Modules, Authority. Original. FIPS 140-2: Cryptographic Modules, Authority. Original. FIPS 140-3: Cryptographic Modules, Foreword. Original. FIPS 197: Advanced Encryption Standard, Authority. Original. FIPS 203: Post-quantum cryptography standard, Foreword. Original. FIPS 204: Post-quantum cryptography standard, Foreword. Original. FIPS 205: Post-quantum cryptography standard, Foreword. Original. Quantum Computing Cybersecurity Preparedness Act, §4. Original. M-26-15 Execution of the Migration to Post-Quantum Cryptography, Overview. Original. ↩
  33. HSPD-12: Common Identification Standard, ¶¶2–4. Original. FIPS 201-3: Personal Identity Verification, Foreword. Original. M-04-04, E-Authentication Guidance, NIST guidance assignment. Original. SP 800-63 Version 1.0.1: Electronic Authentication Guideline, §1. Original. SP 800-63-4: Digital Identity Guidelines, Introduction. Original. M-19-17, Enabling Mission Delivery through Improved Identity, Credential, and Access Management, p. 13. Original. ↩
  34. The original 2005 FIPS 201 file is unavailable in this collection; FIPS 201-3 provides its publication history. The older SP 800-63 copy is version 1.0.1, dated September 2004. FIPS 201-3: Personal Identity Verification, Foreword. Original. SP 800-63 Version 1.0.1: Electronic Authentication Guideline, Title page. Original. ↩
  35. SP 800-145: The NIST Definition of Cloud Computing, §2. Original. SP 800-144: Security and Privacy in Public Cloud Computing, Executive summary. Original. SP 800-171 Rev. 3: Protecting CUI, §1. Original. Executive Order 13556: Controlled Unclassified Information, §§2–5. Original. SP 800-207: Zero Trust Architecture, §1. Original. Executive Order 14028: Improving the Nation’s Cybersecurity, §§3–4. Original. SP 800-218: Secure Software Development Framework, §1. Original. M-22-09 Moving the U.S. Government Toward Zero Trust Cybersecurity Principles, Strategy. Original. M-22-18 Enhancing the Security of the Software Supply Chain through Secure Software Development Practices, Agency requirements. Original. M-23-16 Update to Memorandum M-22-18, Enhancing the Security of the Software Supply Chain through Secure Software Development Practices, Updated guidance. Original. ↩
  36. Transmittal 3 explanatory preamble, Appendix IV discussion. Original. Transmittal 4 final Federal Register notice, Incorporation of memoranda. Original. M-04-04, E-Authentication Guidance, NIST guidance assignment. Original. Security Authorization of Information Systems in Cloud Computing Environments, Introduction. Original. Modernizing the Federal Risk and Authorization Management Program (FedRAMP), Rescission. Original. M-19-17, Enabling Mission Delivery through Improved Identity, Credential, and Access Management, p. 13. Original. M-17-26, Reducing Burden for Federal Agencies by Rescinding and Modifying OMB Memoranda, Eliminated, modified and paused policies. Original. ↩

About the sources

This history covers developments through October 10, 2026. Sources include enacted laws, Federal Register notices, OMB and presidential archives, and NIST publications. The library contains 178 records and 173 downloaded documents, with selected major editions of NIST standards and guidance.

The memorandum search covered six official indexes, identifying 721 distinct numbered entries. Of 717 documents retrieved, 89 contained an A-130 reference in their extracted text. The library also includes selected related policies and the unnumbered 2011 FedRAMP memorandum. Missing archive links, unindexed documents, and imperfect text extraction limit coverage.

The source details record edition information, available files, and known gaps. Older scans can contain transcription errors. Term flags identify passages containing cloud, commercial services, FedRAMP, or related language; an occurrence may appear in a footnote or definition rather than a requirement. Historical policies and annual deadlines may have been replaced.

Downloaded documents and reading pages are available offline. Links to the publishing agency require an internet connection. Original files are retained with checksums so changes to their contents can be detected.

Source index (JSON) · Source index (CSV) · Collections searched · Memorandum search results