Security Objectives for the Environment | Nortel Networks 7.11

Security Target, Version 3.9	March 18, 2008

4.2 Security Objectives for the Environment

4.2.1 IT Security Objectives

The following IT security objectives are to be satisfied by the environment:

OE.TIME

The environment must provide reliable timestamps for the time-stamping of audit events.

OE.CERTIFICATE The environment must provide the required certificate infrastructure so that the validity of certificates can be verified. The certificate infrastructure must be properly and securely maintained so that the status of certificates is accurately provided to the TOE.

OE.DOMSEP	The environment must maintain a security domain for the Nortel VPN Client software that
	protects it from interference and tampering by untrusted subjects.

4.2.2 Non-IT Security Objectives

The following non-IT environment security objectives are to be satisfied without imposing technical requirements on the TOE. That is, they will not require the implementation of functions in the TOE hardware and/or software. Thus, they will be satisfied largely through application of procedural or administrative measures.

OE.PHYS-SECThe TOE must be physically protected so that only TOE users who possess the appropriate privileges have access.

OE.TRAINED Those responsible for the TOE must train TOE users to establish and maintain sound security policies and practices.

OE.DELIVERY Those responsible for the TOE must ensure that it is delivered, installed, managed and operated in accordance with documented delivery and installation/setup procedures.

Nortel VPN Router v7.05 and Client Workstation v7.11	Page 19 of 67
© 2008 Nortel Networks

Image 19

Nortel Networks 7.11, 7.05 Security Objectives for the Environment, Non-IT Security Objectives, Oe.Time, Oe.Domsep

Contents

Nortel Networks Corsec Security, Inc Version Modification Date Modified By Description of Changes Revision History Table of Contents Rationale Table of FiguresTable of Tables Protection Profile Claims ST, TOE, and CC Identification and Conformance Security Target IntroductionPurpose Security Target, TOE and CC Identification and Conformance Terminology Conventions, Acronyms, and TerminologyConventions Terminology Primary Admin password Product Type TOE DescriptionProduct Description Branch Office Deployment Configuration of the TOE Physical Boundary TOE Boundaries and Scope TOE Environment Logical Boundary Enterprise World Cryptographic Support Security AuditUser Data Protection Trusted Path/Channels Identification and AuthenticationSecurity Management Protection of the TOE Security Functions Excluded TOE Functionality Assumptions TOE Security EnvironmentThreats to Security Threats Addressed by the TOE Environment Threats Addressed by the TOE Security Objectives for the TOE Security Objectives OE.TIME Security Objectives for the EnvironmentIT Security Objectives Non-IT Security Objectives ST Operation IT Security RequirementsTOE Security Functional Requirements TOE Security Functional Requirements Description ST Operation Auditable Events Class FAU Security AuditFAUGEN.1 Audit Data Generation FAUSAR.1 Audit review Dependencies FAUGEN.1 Audit data generation FCSCKM.4 Cryptographic key destruction Class FCS Cryptographic SupportFCSCKM.1a Cryptographic key generation Diffie-Hellman FCSCKM.1b Cryptographic key generation RSA FCSCOP.1d Cryptographic operation random number generation FCSCOP.1b Cryptographic operation authenticationFCSCOP.1e Cryptographic operation hashing Security Target, Version March 18 FDPIFC.2a Complete information flow control VPN FDPACC.2 Complete access controlFDPACF.1 Security attribute based access control Class FDP User Data Protection FDPIFF.1a Simple security attributes VPN FDPIFC.2b Complete information flow control Firewall FDPIFF.1b Simple security attributes Firewall FDPUIT.1.1 FDPUCT.1 Basic data exchange confidentialityFDPUIT.1 Data exchange integrity FDPUCT.1.1 FIAUID.2 User identification before any action Class FIA Identification and AuthenticationFIAUAU.1 Timing of authentication FIAUAU.5 Multiple authentication mechanisms Dependencies No dependencies FMTMSA.1a Management of security attributes Class FMT Security ManagementFMTMOF.1a Management of security functions behaviour FMTMOF.1b Management of security functions behaviour FMTMSA.2.1 FMTMSA.1c Management of security attributesFMTMSA.2 Secure security attributes FMTMSA.3a Static attribute initialisation FMTSMR.1 Security roles FMTSMF.1 Specification of Management FunctionsFMTMSA.3b Static attribute initialisation FMTMSA.3c Static attribute initialisation FMTSMR.1.2 FPTRPL.1 Replay detection FPTAMT.1 Abstract machine testingFPTTST.1 TSF testing Class FPT Protection of the TSF FTPTRP.1.2 Class FTP Trusted Path/ChannelsFTPTRP.1 Trusted path FTPTRP.1.1 FPTSTM.1 Reliable time stamps Security Functional Requirements on the IT EnvironmentFPTRVM.1 Non-bypassability of the TSP FPTSEP.1 TSF domain separation Security Target, Version 3.9March 18 Assurance Components Assurance RequirementsAssurance Requirements Description Function TOE Summary SpecificationTOE Security Functions TOE Security Security Log Configuration LogSecurity Audit Accounting Logs Event Log System Log Validation Modules Fips 140-2 Certificate # Cryptographic SupportFips Validated Modules FIPS-Validated Cryptographic Algorithms User Data Protection Security Management Identification and Authentication Protection of the TOE Security Functions Power-Up Self-TestsConditional Self-Tests Assurance Assurance Measure Component TOE Security Assurance MeasuresTrusted Path/Channels TOE Security Functional Requirements Satisfied FTPTRP.1 Augmentation to EAL 4+ assurance level Protection Profile Reference Protection Profile Claims TOE Objectives Environmental Objectives Non-IT RationaleSecurity Objectives Rationale Relationship of Security Threats to Objectives Hack Certificate OE.CERTIFICATE Security Functional Requirements Rationale Objectives Requirements Relationship of Security Requirements to Objectives Env Functions and data FMTMSA.3a,b,c Able to access such functionality Integrity Reject packets based on their attributes Functional Requirements Dependencies Security Assurance Requirements RationaleRationale for Strength of Function Dependency Rationale FCSCOP.1 TOE Summary Specification Rationale Secure Delivery and Operation Configuration ManagementDevelopment Life Cycle Support Documents Guidance DocumentationTests Vulnerability and TOE Strength of Function Analyses Strength of Function DoD AcronymsAcronyms Acronym Definition SHA