NETCOM/9th SIGNAL COMMAND (ARMY) LANDWARNET NETOPS ARCHITECTURE (LNA) NETWORK ATTACHED STORAGE ELEMENT MANAGER COMPLIANCE CHECKLIST #1 Vendors Certification of Product Meeting LNA PRODUCT CHECKLIST TO BE COMPLETED BY Name: Requirements Title: Name: VENDOR Version: Signature: FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Analyze Events by Multiple Criteria The system shall enable administrators to analyze system events by This is essential to support root cause analyses, multiple criteria. It shall enable them to analyze events relating to two or troubleshooting, and in order to assess progress in improving more administrator designated criteria, to include (but not limited to) support/ services - all necessary to operate, maintain and specific times, assets (hardware, software, agents), Command, Control, defend the LandWarNet. It also reduces the amount of time Communications, Computers, and Information Management/Information administrators will spend in isolating the underpinning cause Technology (C4IM/IT) services, users,administrators, threat signatures, of an outage. 2 behavioral profiles, asset/ threat type, management system transactions/job, capacity/availability/performance data, business impact, data source, and/or configuration items. Assign Privileges to Administrative Groups The system shall provide the ability to assign privileges (read, write, This is needed for administrators to quickly and securely add execute, access to, restrictions from) to administrative groups. and remove access permissions to management platforms. 2 Administrative groups are composed of administrative accounts used to manage the platform. Collect Hardware Inventory and The system shall query managed platforms, agents, and devices/clients to Needed in order to manage the underlying components of the Configuration Data obtain information about their operational hardware inventory and LandWarNet. Could be used for metering for compliance. configuration. It automatically forwards designated Assets and 1 Configuration Items data, as directed/ configured by the administrator. Collect Software/ Firmware Inventory and The system shall query manage components, agents, or sensors and This is necessary in order to baseline, manage, and defend Configuration Data obtain information about the operational software/firmware inventory on the the underlying software existing within the LandWarNet. 1 managed asset(s). This information is stored in the Software Repository. Configure Communication Resources The system shall have configurable communication parameters. These This is needed to securely configure communication channels parameters can be set between component-to- management consoles, between agents and management platforms ensures secure manager-to-agent and manager-to-management consoles; client-to-server, transfer of data between the two elements. 1 client-to-client, Virtual Private Network (VPN) Device-to-remote user, and server-to-server components. This include configuring ports, Internet Protocol (IP) address. Configure Local Event Queues The system should accept user input of the data required to configure a N/A queue of events for a defined period of time for later collection by the 3 Manager. This includes enabling customers/users to define optimal times for non-disruptive data collection. Configure Operational Data Collection The system shall enable administrators to define the particulars of This is required to ensure that asset statuses and other operational data collection and storage. These shall include the intervals operational data are collected to operate and maintain the of data collection, the specific data to be collected (e.g., system operational LandWarNet. 2 status, user actions/activities being performed, etc.) and the methods of collection. Customize Diagnostic Routines The system should support local customization of the default diagnostic N/A 3 routines. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 1 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Customize Knowledge Base The system should enable administrators to customize its digital N/A documents knowledge bases for its managed clients/agents/applications, and supported customers, organizations, or services. This enables administrators to add Army specific documents (approval to operate, tailored standard operating procedure/Tactics, Techniques, and 3 Procedures, Army-refined Frequently Asked Questions (FAQs), Intrusion Prevention System (IPS) Policy/Behavior-Based Rule Implementation Instructions, Field Manuals (FM)/Behavior-Based Rules, etc.) to standard Enterprise documents and links within the knowledge base. Define Access Privileges The system shall enable designated administrators to define, and This is critical for securing LandWarNet resources and subsequently enforce access privileges for other administrators, users and preventing unauthorized users from making changes that assets to the management platform its data and any managed assets. could lead to false alarms, failure of vital system functions, 2 and corruption of data used to operate, manage and defend the LandWarNet. Define Performance Thresholds The system should define performance thresholds for the managed N/A agents/systems/clients/applications. Performance is primarily tied to availability, throughput and response time. (e.g., transaction time, storage 3 read write times, authentication processing time, update times, attacks blocked, attacks blocked by signature/ behavior rule, etc.) Detect and Report Login Credential The system shall identify when users/administrators have changed, or This is needed to track user activity and identify those types Changes attempted to change, their login credentials (user name, password, of activities that may indicate unauthorized changes to 2 domain) and report this change. accounts. Detect Hardware Changes The system shall identify hardware changes that have occurred within a This enables systems to prompt administrators to validate managed asset, based on the previous collection of hardware authorized infrastructure modifications and to identify and configuration and version data. respond to unauthorized modifications. This is key to 2 effectively defending and maintaining the LandWarNet. Detect Software/Firmware Changes The system shall identify software/firmware changes that have occurred This is needed to ensure authorized changes are effected within a device, agent, or sensor, based on the previous collection of and that unauthorized changes are identified. 2 software configuration and version data. Display Available Diagnostic Routines The system should present a list of available diagnostic routines that can N/A be executed on either the management platform or managed asset. 3 Display Change History The system shall display information regarding historical changes to the This is needed to enable administrators to verify authorized system and its managed objects or applications. changes and identify unauthorized changes to the 1 management system and any managed devices and applications. Display Events The system shall display dynamic near-real-time events based on alarm This is needed for the operation, maintenance, and defense severity, time, hierarchical importance, client groups, etc. The system shall of the Global Information Grid (GIG) and LandWarNet. 1 support drill down capabilities to display the underlying events behind larger alarms/incidents. Display Help The system should provide the ability to view help files specific to the N/A 3 application or management system. Display Knowledge Base Information The system should display requested information from a particular N/A knowledge base, in response to administrator queries. It should support information retrieval and display from authorized (administratively-linked) external knowledge bases (e.g., a vendor maintained knowledge base. 3 This facilitates rapid trouble-shooting and insightful decision making, particularly by less experienced administrators. Display Logging Information The system shall present logging information received from an asset or Enables administrators to view activity logs to identify 2 agent/sensor. unauthorized events per Army Regulation (AR) 25-2. Display Monitored Data The system shall drill down and display information about displayed This is essential for basic LandWarNet monitoring, devices and events. The information may include troubleshooting, and maintenance - particularly at Theater event/incidents/problems, operational activities, system transactions and/or Network Operation and Security Centers (TNOSC), where 1 capacity, availability, performance (CAP) data. remote access to fault sources will be critical for security and rapid repair/problem prevention. Display Results of Diagnostics The system shall present results of diagnostic routines executed on a This is needed to facilitate trouble shooting. 2 network device. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 2 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS IO I URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Distribute Configuration The system shall distribute configuration information to managed This is needed to set/change the configuration of an asset. components/assets. Also supports rollbacks to an authorized current baseline 2 following an unauthorized change/information attack. Distribute Current Software/Firmware The system shall distribute current baseline software releases from the This is needed to ensure current versions of software and Version Current Software Versions (i.e., management software, applications, patches can be installed. It also supports rapid rollbacks to an patches, etc.) area within the Software Repository. authorized current software/firmware baseline following an 2 unauthorized change/information attack. Distribute New Software/Firmware The system shall distribute new software releases (i.e., applications, This is needed to ensure that those systems will not be patches, etc.) from the New Software Versions staging area within the compromised. Remediation of systems on the LandWarNet Software Repository. Once installed and verified, the system changes the contributes to security in depth. Retaining prior baseline data 2 new release's status to current baseline status, and the previous current as described enables rollbacks in the event of a faulty baseline software to historical baseline status. update. Encrypt Data Exchanges The system shall provide secure (encrypted) data exchange between a Secures Network Operations management data used to manager and clients. Certain types of data being exchanged require control management platforms on the LandWarNet. encryption (e.g., logon credentials). The system shall provide the capability to encrypt data transferred between the system and assets using 1 Secure Socket Layer (SSL) and Transport Layer Security (TLS) that is Federal Information Processing Standards (FIPS) Publication 140-2 compliant. Manage Administrator Accounts The system shall provide the ability to manage (add, modify, verify, delete) This is needed to ensure that access to management accounts that are used to administrate the system. This also includes the systems is controlled and secure. 2 ability add and remove users from groups. Manage Component Grouping The system shall allow administrators to define groups of assets. Groups This is needed to enable the administrators to perform may be created using different characteristics, including hierarchical, common operations upon them (loading patches, signatures, organizational, geographical, or functional (e.g., Email Servers). Also, the profiles, access control list, etc.) - speeding implementation of 2 system shall enable administrators to assign specific assets/components to security measures during an attack, reducing the chances of defined groups. error, and reducing overall administrator workloads. Manage Configuration Profiles The system shall manage (create, modify, archive and delete) sets of This speeds asset configuration (during installation/updates), configuration profiles for specific classes of devices, agent/clients, and reduces administrator burdens, and reduces human error by applications. A configuration profile contains all the configuration establishing standard configuration sets to apply for specific information about a specific asset. It shall support both the current assets. It also provides a means to assess compliance to an configuration profile of a managed asset as well as a baseline approved Enterprise configuration standard for common 2 configuration profile. systems/devices (e.g., an Active Directory (AD) server should have specific agents, signatures and profiles loaded at any given time). Manage Data Movers (Heads) The system shall perform administration on redundant data movers or This is a core functionality of the Storage Area Network heads. Data movers provide a high speed low overhead method of moving (SAN) and is needed in order to prevent overwriting of data 2 files. being stored on the storage device. Manage Diagnostic Routines The system should enable administrators to create, copy, and delete N/A tailored/ unique diagnostic routines for the management system and any 3 managed devices, agents or applications. Manage Groups The system shall manage (create, modify, delete) User Groups, with user The system is critical to the operations and security of this roles and privileges. It shall support User Group creation, data entry/ Network Operations (NetOps) system and the LandWarNet. modification, and deletion by authorized system users. This includes the User accounts and their associated User Group(s) will be ability to remove multiple groups/super groups (groups that contain other used throughout the Enterprise to control privilege-based groups) within a single action. access to various resources/assets and services, track 1 trouble calls/service requests, provide alerts/notifications, and to maintain audit/transaction logs (In accordance with AR 25- 1 and AR 25-2). Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 3 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Manage Media Configuration Information The system shall manage configuration information for devices/media These features are essential to protect LandWarNet data assigned to specific Backup and Recovery Agents. It shall manage media from accidental overwrites, to account for all storage media overwrite settings (allowing or preventing media overwrite). It shall provide (to include classified drives procured for specific Title 50/other support of various methods of media labeling. It shall automatically uses) and to implement defense-in-depth access controls to recognize when destination storage devices/media have been swapped selected, sensitive media and their data (e.g., Hard Drives for 2 and reconfigure itself accordingly. It shall be able to reconfigure this new War Fighter systems/units or containing Privacy data). managed device media without interruption. It shall manage drive pool usage configuration, assigning specific uses for specific (real and virtual) drives in a storage pool. Manage Storage Gateway This system should define and manage a Network Attached Storage This is needed so that all other systems on the network can 2 gateway function. access data on the storage device. Manage Storage Performance Settings The system shall manage settings, rules, and options to control the This is essential to monitor the performance of critical storage performance of managed storage components. This includes: components within the manager and managed devices, and a) It shall define and provide baseline information used to manage storage to report related performance and configuration data to other performance. NetOps components monitoring/maintaining the health of b) It shall provide load testing capabilities. The information collected critical portions of the LandWarNet. during the execution of these load tests are then compared to the established performance baselines. c) It shall display performance data for storage components. This data will be stored in the Operational Data Repository. This performance data will include but not limited to disk throughputs, disk cache, and bandwidth 2 bottlenecks. d) Report System Performance. The system shall report performance issues like disk throughput, disk cache, and bandwidth bottlenecks. e) Display Performance Threshold Exceptions. The system shall display performance threshold exception data for storage components. This data is generated based on the performance thresholds configured for the network or components. These performance exceptions could be related to items such as disk throughputs, disk cache, and bandwidth bottlenecks. Perform Asset Maintenance Management The system shall perform maintenance activities on the system and its Provides the ability to keep critical systems functioning managed clients/assets, to include: cleaning out the cache file, deleting old through the remote execution of maintenance. logs, defragging hard drives, performing disk checks/optimization, compressing specific folders, and deleting files in a temp 2 directory/buffer/recycle bin. It also shall also enable administrators to remove assets/agents, de-install applications, delete individual folders/files, etc. Perform Local Authentication This is needed for the authentication of users to access and The system shall authenticate users, administrators, and assets from data stored locally within the management application or device. resources on the LandWarNet and is required by AR 25-1, 1 and AR 25-2. Perform Operations on Multiple Assets The system shall permit administrators to interact with multiple managed This is needed to save the administrators considerable time, assets on a single screen. It allows them to select and perform operations enable central management and maintenance of large on individual assets, and groups of assets (Hardware, Software, Agents), network - enhancing overall reliability and security. from administratively defined (pick) lists of available assets/asst groups 2 and operations. The system shall enable the administrator to define and save groups of assets for future pick list displays (to perform future operations upon). Perform Remote Authentication The system shall authenticate users, administrators, and assets from a This is the core function for the authentication of users to remote authentication service on the network. access and resources on the LandWarNet and is required by 1 AR 25-1, and AR 25-2. Process Requests for Capacity, Availability, The system shall process Requests For Data (polls) from the CAP This is needed to enable overarching NetOps management and Performance Monitoring Data Monitoring system. The system shall determine the required systems to function; it directly feeds the IT Metrics Program's information/data, retrieve/collect it and forward it to the CAP Monitoring data collection, which in turn provides required reports to 1 system. meet provisions within the Clinger-Cohen Act. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 4 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Provide Administrator Audit Log The system shall provide administrator audit log information, to include the This is required in accordance with Department of Defense administrator's identification, time stamp, the specific activity/transaction Instruction 8500.2, AR 25-1 and AR 25-2. performed, changes in permissions, and any other specified data of 2 interest related to administrator transactions on the system. Provide Alarm Trace Data Repository The system shall store Alarm/Event data collected and analyzed by the This is essential for retaining records of system failures and management system. Alarm data is generated based on predefined security events necessary for follow-up, in-depth analysis 2 criteria established and rules run against event/operational data received used to resolve problems and improve LandWarNet by the management platform. readiness and availability. Provide Capacity Data Repository The system should store capacity data collected and analyzed by the N/A management system. Capacity data may include used/remaining storage capacity (for disk drives, logical unit number, tape, drive pools, etc.), 3 processing/Central Processing Unit (CPU) capacity, the average/maximum number of files/applications/users and asset/service supports, transmission rate/bandwidth data, etc. Provide Capacity, Availability and The system should provide reports on CAP data. N/A 3 Performance Data Report Provide Capacity, Availability, and The system should integrate with the CAP Monitoring System. This is N/A Performance Monitoring System Integration needed in order for the CAP Monitoring system to receive data that it can 3 then analyze. Provide Command Line Interface The system shall use a command line interface for system or account This is needed to enable administrators to execute changes administration locally and remotely. on large groups of configuration items via a single command. 2 Provide Command Line Interface and The system should provide security mechanisms for Command Line N/A Application Program Interface Security Interface (CLI) and Application Program Interface access to the system. The system should enforce security for command line input that is functionally identical to graphical user interface access restrictions and 3 controls; security for Advanced Programming Interfaces that are functionally identical to graphical user interface access restrictions and controls. Provide Communication Ports Security The system shall provide the capability to designate a limited set of ports This is necessary to configure management platforms to for communication between management platforms and managed communicate across routers and switches (considering port 1 components. restrictions that may be applied to network devices) within the LandWarNet. Provide Configuration Change Reports The system should produce reports on a managed client’s configuration N/A 3 changes based on inventory scans. Provide Configuration Management Data This system shall integrate with an external Configuration Management This is required to provide critical Network Operations Base/Service Support Integration Data Base/Service Support (CMDB/SS) system; which includes inventory and configuration item data, health/welfare status components such as: Service Desk, Incident Management, Problem information/events, and other administrative information Management, Change Management, Configuration Management, Asset necessary to monitor and manage the health, welfare, and 1 Management, Project Management, etc. This includes enabling the user operational status of the LandWarNet. to access the manual workflow report (Trouble Ticket) features of the CMDB/SS. Provide Data File Security The system should enable administration of data file security. It should N/A provide user authentication and enable user authentication with user name 3 and password. Provide Data File Transfers The system should enable the administration of data files to retain file N/A 3 owner permissions, creation date, and other file attributes. Provide Data Sharing Administration The system should provide data sharing and gateway among disparate N/A 3 operating systems such as UNIX/LINUX. Provide Defineable Report Filters The system should provide filters that can be created and modified. Filters N/A provide a way to produce reports that provide data on a specific 3 attribute(s). Provide Device and Media Configuration The system shall store all configuration information about devices and This is needed to maintain and defend LandWarNet systems Information Repository media that is generated by the management system or its sub- via their configurations. It supports restoring and systems/agents, to include any unique communications/encryption reconstitution of vital assets and applications. 2 settings. This also includes new/staged, current, and multiple copies of historical configuration data. Provide Diagnostic Routines The system shall provide diagnostic routines. Diagnostic routines enable This is essential for the rapid trouble shooting and administrators to execute an action or set of actions intended to reveal maintenance of assets. 2 operational failures. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 5 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS IO I URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Provide Event Log Reports The system shall produce reports containing event and associated user This is needed to meet AR requirements for reporting on 2 activity logs. potential security breeches. Provide Failover Capabilities to Secondary The system should provide failover capabilities to a secondary site. This N/A Site encompasses the failover configuration and parameters for the secondary 3 site. This capability required secure data transmissions to the secondary site. Provide File Locking Administration The system should provide the ability to lock/unlock files residing on the N/A 3 storage device. Provide Frequently Asked Questions The system should support a FAQ capability, providing searchable, quick N/A Feature solutions for common problems for both administrators and 3 customers/users. Provide Graphical Diagrams The system shall provide a Graphical User Interface (GUI)/Web based This is required to monitor the health and security posture of diagram of disks or networks, along with physical and logical views of the the networked infrastructure. assets. Additionally, the system shall provide a network diagram of the 2 assets to include switches, tape libraries, or other managed assets. Provide Graphical Interface The system shall provide a GUI enabling users and/or administrators to This is needed to simplify the use of the management access and operate the system from their terminal or via a web-accessible system. Interface. The system functionality should be the same whether the 2 operator accesses the system via the terminal or at the server/system's native interface. Provide Hardware Inventory Repository The system shall store Hardware data collected and analyzed by the This is needed to rapidly and remotely detect unauthorized management system. The system shall be capable of storing staged, changes to hardware devices on the LandWarNet. Multiple current and multiple historical versions of hardware inventory information versions enable administrators to prepare for new systems for each managed asset. It shall support queries against this data. and archive inventory that is deployed/being repaired and will 1 return in the future; it also supports battle handovers of this data to the gaining TNOSC/signal unit and helps to centrally identify all assets belonging to an organization. Provide Help Feature The system should provide help functionality. This can be an on-line N/A functionality or provided locally on the platform. It should provide a search 3 and index capability. Provide Import Digital Documents For The system should import vendor supplied Digital Documentation N/A 3 Knowledge Bases Knowledge Base information. Provide Knowledge Base The system should provide a knowledge base. Knowledge bases are N/A searchable (via queries) repository of information about a specific topic or product. The knowledge base should contain at a minimum; frequently 3 asked questions, trouble-shooting wizards, Uniform Resource Locator's (URLs) for additional help/information. Provide Knowledge Base Repository The system should store NetOps Knowledge Base information. This This is essential for the basic operation of the NetOps includes all information stored in the Knowledge Base used primarily by Systems Knowledge Base management capabilities. 3 administrators in the operations and maintenance of systems and services. Provide Manual Component Registration The system shall accept manually entered asset and asset sub-component This supports management, situational awareness, and registration information. This information is entered by the administrator defense of critical LandWarNet assets and the about a specific asset(s) that is to be managed and is used to find and take implementation of urgent defensive measures and policies. 2 administrative control of the asset. The system shall enable administrators and designated users to add or remove assets as necessary. Provide Multiple Component Access The system shall control the administrator's ability to only perform This is needed to enable automated administrative access Controls operations to those assets/asset groups they are authorized to manage. controls - enhancing overall reliability and security. 2 Provide Operational Reports The system shall provide operational NetOps reports, to include those on This is needed to allow the element manager to combine and component and aggregated asset/system utilization (or usage); failed summarize device/storage information, Job Status, Job components/assets; configuration settings for all/designated Volume, Device Utilization, media verification, job failures, job 2 components/assets; and asset/device/storage information. schedules, report alerts. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 6 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Provide Performance Data Repository The system should store Performance data collected and analyzed by the N/A management system. Performance data may include average/max transaction times (e.g., raw/average/ maximum time required for network transmissions, storage read/writes, authentications, processing, etc.) security event metrics (number of attacks detected/prevented, number of 3 pre-emptive security-related work flow records, number of reactive security- related work flow records), customer satisfaction statistics, the mean time between service calls for a service, and accuracy metrics (e.g., Jitter, Bit- Error-Rates, Trouble Ticket re-openings, etc.). Provide Predefined Display Formats The system shall display predefined formats/displays to make the system This is needed for basic operation of the system out of the usable immediately after the initial installation. box, reducing configuration and implementation time. 2 Provide Predefined Reporting Filters The system should display filters to reduce displayed data based on N/A relevancy and provide predefined display filters to support analysis of 3 reported data. Provide Remote Administration The system shall provide secure, Internet protocol-based remote This is required to secure the LandWarNet and operate large 2 administration of the manager and its managed assets. networks. Provide Single Component Access The system shall enable administrators to interact with a single monitored This is needed to facilitate defensive actions, maintenance, asset or service on a single screen. This includes enabling them to view and operational management of core components and 2 and manipulate the asset/service's status, type, capacity, utilization, services underpinning the entire LandWarNet. allocation, and location. Provide Software Inventory Repository The system shall store software inventory data collected and analyzed by This is needed to support baseline determinations and data the management system. This includes historic, current, and staged restoral operations. 2 inventory data. Provide Software Repository The system shall provide a repository for storage of software or firmware, This repository is essential for the operation of the by version. It shall store the current version of profiles; and store multiple management system and in order to install, restore, and historical versions. It shall stage new versions within the repository for trouble-shoot faulty software/firmware versions. It also subsequent distribution/installation. Once a new version is deployed, it provides a baseline of authorized software that may be used 2 becomes the current version and the old current version becomes a during forensic analysis to identify unauthorized changes historical version. It shall enable administrators to control the number arising from a computer network attack. and/or age of historical versions retained. Provide Standard and Predefined Reports The system should predefined/standard reports and views. The system N/A should also provide graphics within text reports (e.g., Trending Reports may contain pie charts, bar charts, line charts and other standard graphics). The system should publish reports in Hyper Text Markup Language (HTML), eXtensible Markup Language (XML), Sequential Query 3 Language (SQL), American Standard Code for Information Interchange (ASCII), Joint Photographic Experts Group (JPEG) and other standard languages/formats; be able to print and email all generated reports. The system should be able to provide displays and reports on all on the following: a) audit reports that detail modifications and upgrades to the system b) identifying all major problems (per pre-defined service level agreement/service support program, per period) c) resolution time for incidents/problems d) closed incidents/problems e) problems that result in the highest percentage of resource utilization f) first contact to closure for incidents or problems g) first call closure for incidents or problems Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 7 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y h) open incidents or problems i) incidents or problems that violate service level agreement/service support program, Service Level Indicators j) closed incidents and problems k) resolved incidents and problems l) escalated incidents and problems m) based on each individual support staff for the number of incidents or problems that they turned over to other support staff during a shift change n) based on department/group for the number of incidents or problems that are turned over to other support staff during a shift change o) trends by agent/support staff for number of incidents and problems opened per day, week, and month p) trends by agent/support staff for number of incidents and problems resolved per day, week, and month q) trends by agent/support staff for number of incidents and problems escalated per day, week, and month r) trends by agent/support staff on the average time taken for incidents and problems to move from open to resolved status s) trends by agent/support staff on the average time spent talking to customers/ users regarding an incident or problem t) trends by agent/support staff on percent of first contact to resolution regarding incidents and problems u) trends (daily, weekly, monthly) by agent/support staff on percent of first call resolution regarding incidents and problems v) trends (daily, weekly, monthly) by agent/support staff on the average first contact to resolution regarding incidents and problems w) trends (daily, weekly, monthly) by agent/support staff on the average first call to resolution regarding incidents and problems x) trends by group/department for number of incidents and problems opened per day, week, and month y) trends by group/department for number of incidents and problems resolved per day, week, and month z) trends by group/department for number of incidents and problems escalated per day, week, and month aa) trends by group/department on the average time taken for incidents and problems to move from open to resolved status bb) trends by group/department on the average time spent talking to customers/ users regarding an incident or problem cc) trends by group/department on percent of first contact to resolution regarding incidents and problems dd) trends by group/department on percent of first call to resolution regarding incidents and problems Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 8 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS IO I URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y ee) trends by group/department on the average first contact to resolution regarding incidents and problems ff) trends (daily, weekly, monthly) by group on the average first call to resolution regarding incidents and problems gg) Incident/Problem rollups by LandWarNet C4IM/IT service or product hh) Users that access a specific asset ii) users that own a specific asset jj) operational assets which have exceeded their life-cycle (to identify equipment that needs to be replaced) kk) minimum, maximum, and averages for all time and numeric based reports ll) number of users that access a defined service mm) customers and their associated users nn) specify the concentration and distribution of vendors and their related products within the enterprise (allows the organization to more clearly understand the impact of issues related to specific products or vendors) oo) life-cycle plans (projections) for an asset pp) service or product defect status qq) service or product enhancement request/Request For Change reports. Provide System Documentation The system should support documentation for a specific technology/ N/A capabilities. This includes system design, implementation and user 3 guides. Provide User Account Repository The system shall store user and administrator account information for the This is needed to control access to the management system management system. and to support addressing for notification messages/alerts. 2 Provide User Activity Log The system shall create and manage the User Activity (Audit) Log, This is required per Army Regulatory requirements and recording all user transactions, and changes to permissions on the system provides a means to verify NetOps staff actions, conduct roll- 1 in accordance with AR 25-2. backs, and conduct post-mortems/after-action-reviews to improve NetOps procedures. Provide User Defined Display Filters The system shall enable administrators to define filtering criteria to view a This is needed to enable administrators to quickly view all subset of the available information. data based upon specific criteria, facilitating analyses, trouble- 2 shooting, work scheduling, etc. Provide User Defined Display Formats The system should allow users to create, add, modify, or delete display N/A 3 formats. Provide User Defined Report Format The system should allow for defined presentation formats to view available N/A information. It should enable the customization of the fields in a report template or system-provided default report. The system should provide report creation tools and support ability to customize reports. The system 3 should enable the user to define output report formats in XML,HTP, ASCII, SQL, and American JPEG. Provide User Log Data Repository The system shall store User Activity Log data collected for analyses by the This is needed to trace user logon activity and to meet AR 25- management system. 1 and AR 25-2 requirements (punitive requirement) 1 Provide Web Accessible Display The system shall interact with devices via a web based interface. The This is needed to support Army requirements to provide web functionality shall be equivalent to the capability provided by non-web accessible interface. 2 based user interfaces. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 9 1/11/2011 FUNCTIONAL REQUIREMENTS PRODUCT COMPLIANCE MET NOT-MET SUPPORTING DOCUMENTATION TO INCLUDE: PR FUNCTION SYSTEM DESCRIPTION JUSTIFICATION DESCRIPTION COMMENTS I IO URL, NAME OF SOURCE DOCUMENT AND RI √ √ PAGE NUMBER IT Y Y Receive Events in Standard Protocols The system shall receive events via industry standard protocols (Storage This is needed to reduce the amount of time spent integrating Management Initiative - Specifications, Simple Network Management products. 2 Protocol v2/3, common information model, XML, User Datagram Protocol, etc.). Report Inactive Administrator Accounts The system shall detect and report inactive administrator accounts. This is needed for enforcing secure access controls over the Inactive administrators are those who have not accessed a specific system NetOps systems used to secure, operate, and manage the for a predefined amount of time. Inactive administrators shall be flagged LandWarNet and its supported Army and Business systems. for administrative attention and possible action (i.e., account suspension, 2 deletion, etc.). The system shall provide alert and report mechanisms to system administrators to act on flagged files. Reset Administrator Account Parameters The system shall establish the capabilities expected from a Manager to This is to provide the ability to lock accounts and unlock reset Administrator Account/Group parameters of an application. A reset is administrative accounts allowing for the securing of the 2 the ability to lock or unlock, make active or disable, or change any of the LandWarNet. settings of an account. Schedule Asset Maintenance Tasks The system should provide for the scheduling of automated maintenance N/A tasks/jobs to be executed on managed assets. Examples of maintenance 3 tasks include: cleaning out the cache file, defragging hard drives, and deleting files in a temp directory/buffer. Schedule Hardware Inventory Data The system should enable an administrator to schedule for the collection of N/A Collection hardware inventory and configuration information from managed 3 components, directly or via an agent. Schedule Software/ Firmware Inventory The system should define a schedule for the collection of N/A Collection software/firmware inventory information from devices, agent, adapter, or 3 sensors. Schedule Software/ Firmware Distribution The system should allow an administrator to define a schedule for the N/A distribution of software (i.e., applications, patches, signatures, 3 remediations) to managed assets (e.g., sensors, agents, applications, devices, etc.). Schedule the Production of Reports The system should support the ability schedule the production of reports. N/A Scheduling will allow for monthly, daily, and hourly configuration such that 3 reports can be run automatically. Send Capacity, Availability, and The system should transmit capacity and availability data to the Capacity, N/A 3 Performance Data Availability, and Performance management system. Send Incident/Problem Data The system shall transmit Incident and Problem data. The system shall, This is necessary for ensuring that assets in the LandWarNet upon triggering of operational or security related problems, send or are operating optimally. 1 transmit the data (time of event, IP address, category of event, etc.) needed to create a Work Flow Record (WFR). Support Multiple Concurrent Administrators The system shall support multiple administrators performing management This is needed to support the ability for multiple operations concurrently. administrators to perform operations concurrently reducing 2 the total cost of ownership. Track Logon Attempts The system shall detect and log user logon attempts (successful or This is needed for enforcing AR 25-1 and AR 25-2 security otherwise). The system shall provide alerts/reports to system regulations and enforcing secure access controls over the administrators to act on multiple failed attempts. systems used to secure, operate, and manage the 1 LandWarNet and its supported Army and Business systems. It also supports post-mortems on IT outages/attacks. 11/032009 Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 10 1/11/2011 NETCOM/9TH SIGNAL COMMAND (ARMY) LANDWARNET NETOPS ARCHITECTURE (LNA) COMPLIANCE CHECKLIST #2 NETWORK ATTACHED STORAGE ELEMENT MANAGER PRODUCT COMPLIANCE INTERACTION WITH OTHER LNA CAPABILITIES TO BE COMPLETED BY VENDOR SUPPORTING DOCUMENTATION COMPLIANCE TO INCLUDE: URL, SOURCE DOCUMENT FROM TO DATA FLOW TEXT DESCRIPTION DATA ELEMENT DEFINITION YES/NO NAME AND PAGE NUMBERS DESCRIPTION COMMENTS Network Attached Storage Element Capacity, Availability, and Contains availabiity, capacity and performance data sent Availability Data: Data relative to which resources are ready for use. Manager Performance Monitoring System from the Network Attached Storage (NAS) Management system to the Capacity, Availability, and Performance (CAP) System Capacity Data: Data regarding the resource utilization, user data consumption, and allocation of resources. Performance Data: Provides graphical representations of current and historic performance information and trend analysis of the servers in the enterprise. Network Attached Storage Element Configuration Management Contains Configuration, Event, and Inventory data sent Address: Address that this protocol endpoint represents, for example, Manager Database/Service Support from the NAS Management system to the Configuration 184.108.40.206 or FE:ED:FE:ED:00:11. The address format, such as Internet Management Databas (CMDB). Protocol, internet packet exchange, or Ethernet, depends on the Protocol Type value. It can be further refined in subclasses. Alerting Managed Element: Name of the alerting computer as known by the management system. Configuration: Contains all the information on how an asset (configuration item) is presently configured (e.g., parameter settings, ports and protocols enabled, filters set, version of Internetwork Operating System/firmware, etc.) Description: Textual description of the instance. Event Time: Date and time of the event or occurrence within the LandWarNet. Host Name: Contains alphanumeric data reflecting the name of LandWarNet Asset. Inventory: Contains the full descriptive inventory of managed assets - to include all known/discoverable metadata about the asset. Primary Capability: Main function of the computer system. Possible values are defined in the Capability List attribute: Not Dedicated (default), Unknown, Other, Storage, Router, Switch, Layer 3 Switch, Central Office Switch, Hub, Access Server, Firewall , Print, Input/Output (I/O), Web Caching, Server, Management, Block Server, File Server, Mobile User Device, Repeater, Bridge/Extender, Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 11 1/11/2011 NETCOM/9TH SIGNAL COMMAND (ARMY) LANDWARNET NETOPS ARCHITECTURE (LNA) COMPLIANCE CHECKLIST #2 NETWORK ATTACHED STORAGE ELEMENT MANAGER PRODUCT COMPLIANCE INTERACTION WITH OTHER LNA CAPABILITIES TO BE COMPLETED BY VENDOR SUPPORTING DOCUMENTATION COMPLIANCE TO INCLUDE: URL, SOURCE DOCUMENT FROM TO DATA FLOW TEXT DESCRIPTION DATA ELEMENT DEFINITION YES/NO NAME AND PAGE NUMBERS DESCRIPTION COMMENTS Network Attached Storage Element Capacity, Availability, and Contains availabiity, capacity and performance data sent Gateway, Manager Performance Monitoring System from the Network Attached Storage (NAS) Management LoadBalancer, system to the Capacity, Availability, and Performance (CAP) System Mainframe, SANSwitch, SANHub, SANBridge, SANRouter, SANDirector, Redundant Array of Independent Disk (RAID) StorageDevice, TapeLibrary, JBOD. Typically, this attribute is set to the first item in Capability List. For example, a server that has some firewall capabilities could have Primary Capability set to Server and Capability List set to Server, Firewall. A switch device would have both Capability List and Primary Capability set to Switch. Primary Operating System: Computer system's primary operating system. Submitter: Unique account identifier of the user that created the instance. This attribute is automatically populated and can be an actual individual or a system that auto-generated instance. System Type: Type of computer system. If the computer is Windows- based, this attribute must have a value. Values are: X86-based Personal Computer (PC) (0), Millions of Instructions Per Second (MIPS) -based PC, Alpha-based PC, Power PC, SH-x PC, StrongARM PC, 64-bit Intel PC, 64-bit Alpha PC, Unknown (default), X86-Nec98 PC. Capacity, Availability and Network Attached Storage Element Contains a request for data sent from the CAP system to Request for Data: This is a generic request for data from one Network Performance Monitoring System Manager the NAS Management System. Operations system to another. The type, content, format, and frequency of the data requested and/or sent is dependant on the respective unique systems. Enterprise NetOps Planning Division ESTA-OSC I-ENPD 2133 Cushing St. Ft. Huachuca, AZ 85613-7070 Compliance.Team@conus.army.mil 12 1/11/2011 9th SIGNAL COMMAND (ARMY) LANDWARNET NETOPS ARCHITECTURE (LNA) NETWORK ATTACHED STORAGE ELEMENT MANAG TO BE COMPLETED BY ARMY REQUIRING ACTIVITY ARMY PROPONENT VENDOR PRODUCT COMPLIANCE CHECKLIST SUBMITTED TO NETCOM ORGANIZATION: COMPANY NAME: NAME: DATE: VERSION: POINT OF CONTACT: POINT OF CONTACT: INTENDED USE OF TH PHONE: PHONE: E-MAIL: E-MAIL: TARGETED ECHELON(S) FOR IMPLEMENTATION OF THIS PRODUCT (Please Check Army Area Processing Center (APC): Army CIO G-6: Army Global Network Operations and Security Center (Army-GNOSC) TOC: Army Operations Center - Pentagon: Army Strategic Command (ARSTRAT): Battalion (II) S-6: Battalion Command Assistance Team (BCAT): Brigade (X) Combat Team (BCT): Brigade (X) Signal Company: Communications-Electronics Research Development & Engineering Center (CERDEC): Corps (XXX) G-6: Corps (XXX) Signal Company: Division (XXX) G-6: Division (XX) Signal Company: Installation, Garrison, Post, Camp, Station NEC (formally DOIM): NETCOM / 9th Signal Command (Army): Regional Computer Emergency Response Team (RCERT): Regional Hub Node: Theater Network Operations (NetOps) Center (TNC) - DISA: Theater Network Operations (NetOps) Control Center (TNCC): Theater Tactical Signal Brigade (TTSB): U.S. Army National Guard NOSC: Other (Please Identify): NOTE: a) Completed LNA Compliance Checklists and supporting documentation are to be e-mailed to the NETCOM 9th Signal Command, LNA Compliance Team at the following: .- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - b) These LNA Checklists and supporting documentation will be utilized by the LNA Compliance Team in their assessment of this NetOps products compliance to the Army LNA, prior to a CoN being granted by NETCOM/9th Signal Command NAL COMMAND (ARMY) T NETOPS ARCHITECTURE (LNA) ED STORAGE ELEMENT MANAGER TED BY ARMY REQUIRING ACTIVITY COMPLIANCE CHECKLIST SUBMITTED TO NETCOM DOES THIS PRODUCT (VERSION ) HAVE A CERTIFICATE OF NETWORTHINESS (CoN) YES: CoN DATE: DATE: NO: DATE REQUEST SUBMITTED: INTENDED USE OF THIS PRODUCT LEMENTATION OF THIS PRODUCT (Please Check ( √ ) Army Computer Emergency Response Team (ACERT) Tactical Operations Center (TOC): Army Service Component Commands: Battalion (II) Signal Company: Brigade (X) S-6: Development & Engineering Center (CERDEC): Company Signal Support: Department of the Army (DA): Expeditionary Signal Battalion (ESB) BATCON: ): NSC Operations Center (OC): Signal Command (Theater) HQ and CIO: Control Center (TNCC): Theater Network Operations and Security Center (TNOSC): U.S. Strategic Command (STRATCOM): t the following: .- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - email@example.com e to the Army LNA, prior to a CoN being granted by NETCOM/9th Signal Command.
Pages to are hidden for
"Computer System Storage Management"Please download to view full document