- Intelligence Community
- Contact Us
This XML Data Encoding Specification for Enterprise Audit Exchange (AUDIT.XML) defines detailed specifications for using Extensible Markup Language (XML) to encode AUDIT.XML data in compliance with the Intelligence Community Abstract Data Definition (IC.ADD). This Data Encoding Specification (DES) defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing AUDIT.XML data concepts using XML.
This technical specification is linked to Intelligence Community Standard 500-27, Collection and Sharing of Audit Data for Intelligence Community (IC) Information Resources by IC Elements. The technical specification detailed herein is the codification of the payload of an audit record exchange as defined in 500-27. The architecture, interface specifications, design, and implementation of the enterprise audit collection and exchange services are outside the scope of this technical specification. This technical specification only applies to the payload of an audit record exchange.
Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.
This specification is maintained by the IC Chief Information Officer via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Data Encoding Specification Downloads
The successes of our intelligence, defense, homeland security, and law enforcement missions are critically dependent on information producers and consumers being able to share, manage, discover, retrieve, and access information across national and international boundaries.
To automate the enterprise, data, service, network, and information assurance architecture and engineering efforts must come together in response to defined mission and business requirements. The enterprise data specifications below are the result of IC collaboration and coordination in response to public law, executive orders, DNI policy and guidance, and change requests submitted by IC elements.
Data Encoding Specifications
The following data encoding specifications define agreed upon digital encodings or formats for information being shared or exchanged within the enterprise. These specifications are optimized for consistent and efficient processing within software, systems, or service applications.
These specifications should be viewed as component modules. Many of the specifications are tightly integrated and dependent on each other. They can be integrated into other data encoding specifications or profiled (i.e., configured or constrained) to achieve a particular mission or business objective. They may also serve in a standalone role as an encodings for exchange payloads within a web services environment.
Each version of an IC enterprise data encoding specification is individually registered in the IC Enterprise Standards Baseline (implemented via the IC Standards Registry (ICSR)). The registry citations address the prescriptive status and validity period for each new version. Data Encoding Specifications exist for the following types of data:
We are very interested in hearing your views on issues of importance to you. We encourage you to contact us with any questions, comments, and concerns of interest to the Intelligence Community Data Coordination Activity (Data Activity). Someone from the Data Activity staff will respond to your email.
As always, we thank you for your time and continued collaboration through the Data Activity.
Vision: An Integrated Intelligence Enterprise
Mission: We enable intelligence collection, analysis, and sharing through innovative, robust and secure capabilities.
In 2012, IC CIO embarked on the largest IT transformation in the history of the Intelligence Community. This transformation, guided by the IC Information Technology Enterprise (IC ITE) Strategy, focuses on enabling greater integration, information sharing, and information safeguarding through a common IC IT approach that substantially reduces costs.
Working with the IC under the IC ITE Strategy, IC CIO is facilitating the development of seamless and secure enterprise solutions that promote trusted collaboration – connecting people to people, people to data, and data to data. The strategy enhances the IC’s ability to securely discover, access and share information across agencies and ultimately enables greater mission success.
The IC ITE Strategy is based on achieving five strategic goals.
Goal 1: Fortify the Foundation
Define, implement and sustain a single, standards-based interoperable enterprise architecture and survivable infrastructure to accomplish mission objectives and drive efficiencies across the enterprise, encompassing all security domains.
Goal 2: Deliver User-Focused Capabilities
Provide seamless and secure enterprise solutions for trusted collaboration – people to people, people to data, and data to data, ensuring the protection of intelligence assets and information, and delivering a user experience that enhances mission accomplishment.
Goal 3: Enable Efficient Business Operations
Enhance support to mission with standardized, integrated, and where applicable, consolidated business processes and supporting technologies.
Goal 4: Establish Effective Governance and Oversight
Define and implement transparent and data driven governance and oversight processes to support mission.
Goal 5: Forge Strategic Partnerships
Develop and enhance trusted partnerships within the ODNI, the IC, across the US Government, with Allied partners, and industry, leveraging innovative capabilities to enhance and integrate the intelligence mission
The IC ITE Strategy directly supports the Administration’s "Cloud First" and Federal Cloud Computing Strategy as well as the Federal CIO’s 25 Point Implementation Plan to Reform Federal Information Technology Management.
Congress passed the Intelligence Reform and Terrorism Prevention Act December 17, 2004, establishing the position of the Director of National Intelligence and the supporting Office of the DNI. Six days later, Congress established the Intelligence Community Chief Information Officer through the Intelligence Authorization Act of 2005, empowering the position with Community-wide authority over enterprise architecture. The act established four areas of IC CIO responsibility above and beyond those accorded to other federal-level CIOs through legislation.
President Barack Obama appointed Mr. Al Tarasiuk to the position of IC CIO Feb. 17, 2011, reporting directly to the Director of National Intelligence.
IC CIO is comprised of three divisions: Mission Engagement, Strategic Programs and Data Management.
You have selected to open
If you would like to not see this alert again, please click the
"Do not show me this again" check box below