TR NWT 000815 : ISSUE 2

1 Introduction
1.1 Background
1.2 Perspective
1.3 Scope
1.3.1 Requirements Applicability
1.3.2 Conformance
1.4 Sources
1.5 Terminology
1.5.1 Requirements
1.5.2 Other Significant Terms
1.6 Organization of Document
2 Rationale for NE/NS Security Measures
2.1 Network Element/Network System Threats
3 Security Feature Requirements
3.1 Overview
3.2 Identification
3.3 Authentication
3.4 System Access Control
3.5 Resource Access Control
3.6 Security Log (Audit)
3.6.1 Security Log Generation
3.6.2 Report Generation/Audit Trail
3.7 Data and System Integrity
3.7.1 Continuity of Service
3.8 Security Administration
4 Development Life Cycle Requirements
4.1 Security Policy
4.2 Requirement Analysis
4.3 System Design
4.4 Detailed System Design
4.5 Implementation
4.6 Development Environment
4.7 System Test
4.8 Packaging and Delivery
4.9 Documentation
4.10 Support
5 Risk Analysis Requirements for ASEs
5.1 Requirements Analysis and Determination
Appendix A: Resource Access Control Based on Privilege Code
References
Glossary

Provides Bellcore's view of its security strategy & the NE feature requirements to implement that strategy to protect NE databases from unauthorized actions (deliberate or inadvertent) by users such as customers, third party service providers, or employees of Bellcore Client Companies (BCCs). It takes into account the need to help ensure proper security against new threats that may ensure if technology & services allow customers & third party service providers to exercise increased control of networks & service features. The strategy is intended to be both flexible (can be tailored for a specific application) & streamlined (to minimize the incremental storage & computation requirements of the NE).