Information is data that has been processed, organized and linked to give it meaning; during disruption information can be rebuilt from data, but processing may take very long and the means may be missing, so the organization considers what its activities need in both information and data: if something an activity needs, prioritized or not, is lost for good, that activity may be unable to go on. Guidance: information and data essential to running the organization are protected and can be recovered within the impact analysis timescales, with regard to legal rules on storage and recovery; and whatever is needed for response and recovery has suitable confidentiality (for example when activities move), integrity (dependable and correct), availability (obtainable as fast as the activity requires, within its RTO, response information at once and other information later) and currency (as recent as the activity needs, per 8.2.2, though what the incident destroys may need rebuilding and data may need recovery). Copies can be electronic (disk, cloud, tape) or physical (microfiche, photocopies, duplicate copies made at production); ways of recovering information and data that have not yet been copied or backed up somewhere safe are written down; copies kept too near the original may be damaged or cut off by the same event while copies kept very far away can be slow to reach, so written instructions on balancing the two are sensible; and the information and data concerned can include contact details, supplier and party details, legal papers such as contracts, insurance policies and title deeds, service contracts and service levels, metadata, alerts and warnings issued in response, and the guidance and criteria for those allowed to invoke procedures.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.