The security plan and its annexes may be folded into operational plans, provided a cross-reference table shows that every requirement is covered, and may be divided by segment, including the measures partners have declared and how those declarations are checked. The plan should set out: the part of the chain it covers; what each member of security staff is responsible for; how security is managed and who the named security manager is; the internal and external emergency contacts for reporting security incidents; what skills and knowledge security staff need, the training provided and how people qualify; how the plan is exercised, with government drills counting; and how government requirements for contingencies or raised security levels will be met. It should include procedures that make sure: shipment information arrives before goods are accepted for onward carriage; goods for consolidation are checked against manifests, and outgoing units against orders; drivers and anyone else in the vehicle are positively identified before cargo is handed over or collected; and shortages, overages and other discrepancies are resolved or investigated, with law enforcement told of anything suspicious. It should also describe the countermeasures in place, the measures for recovering security, the measures applied when custody passes, how further shipment information is released to authorized people once the request has been checked, and the procedures for communicating with government under A.4.3.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.