MARITIME TACTICAL WIDE AREA NETWORKING (MTWAN ...

Uncontrolled copy when printedUNCLASSIFIEDACP 200(B) Vol 2c. Security Policy Establishment, Monitoring, & Enforcement;d. Firewall Management;e. Response Centre activities (route attack notifications to CERTs, co-ordinatefixes);f. Guard Management (―Guards‖ = devices connecting 2 or more networksrunning under different security policies and/or sensitivities, e.g., a guard whichconnects the US National networks with the MTWAN);g. Encryption Device Management (e.g. TACLANE/FASTLANE Management);andh. Administration which comprise the generation of reports, pertaining to:i. Robust Network Management under varying operational conditions (i.e.,EMCON);j. DNS Co-ordination;k. Interface with other non-MTWAN network management entities (e.g., nationalNOCs and their network management systems); andl. Provisioning requests up to national NOCs; responses down to MTWAN NOC;m. Critical fault alerts/alarms sent up to national NOCs; andn. Configuration and performance summary status/statistics sent up to nationalNOCs.REMOTE OR LOCAL MANAGEMENT312. Centralised, remote management of the MTWAN elements by a NOC will be moreefficient than co-ordinated local control. Remote management reduces the need for additionalskilled staff on each mobile unit, minimises the risk of errors in configuration, and permitsrapid reaction to events. However, the capability for remote management is limited at presentby national policy.313. National policies may prohibit remote control of network elements for safety orsystem integrity reasons. Monitoring may be acceptable, if specific equipment items can beconfigured to respond to remote requests for status information but ignore control messages.Network management procedures and protocols must be secure.3-3 OriginalUNCLASSIFIED