NIAP Oversees Evaluations of Commercial IT Products for Use in National Security Systems

Short Name: pp_av_br_v1.1

Technology Type: AntiVirus

CC Version: 2.x

Date: 2006.04.04

Preceded By: pp_av_br_v1.0

Succeeded By: pp_av_br_v1.2

Sunset Date: 2008.03.21

Conformance Claim: Basic Robustness

Protection Profile 

Validation Report 

PP OVERVIEW

This PP specifies the minimum-security requirements for Anti-Virus Applications (i.e., the Target of Evaluation (TOE)) used on workstations in the US Government in Basic Robustness Environments. The Anti-Virus Application provides protection against viruses coming into the workstation from network connections and/or removable media, and is considered sufficient protection for environments where the likelihood of an attempted compromise is low. The target robustness level of "basic" is discussed in Section 3.0 of this PP. STs claiming compliance may consist of software only.

The PP defines the requirements for a general-purpose Anti-Virus Application that may be used in a variety of systems. Relative to these requirements the PP includes:

• Assumptions about the security aspects of the environment in which the TOE will be used;
• Threats that are to be addressed by the TOE;
• Security objectives of the TOE and its environment;
• Functional and assurance requirements to meet those security objectives; and
• Rationale demonstrating how the requirements meet the security objectives, and how the security objectives address the threats.

SECURITY EVALUATION SUMMARY

A Profile is intended to be generally applicable to products regardless of whether they are embedded, stand-alone, centralized, or distributed. However, based upon the results of numerous products trying to claim conformance to this PP, it was a security functional requirement did not support the stated applicability. The Errata Section identifies the area that has been identified as problematic for software vendors who are seeking conformance to this PP and clarifies the security function requirement in a manner that would allow a vendor to successfully achieve compliance. Software vendors who follow the guidance in this Errata Section will be able to successfully claim conformance to this PP, effective immediately.

ENVIRONMENTAL STRENGTHS

Because a PP is written to be implementation-independent, there may be some ambiguities that do not arise until a specific implementation is being evaluated against it. When this happens, a resolution is established through the Observation Decision (OD) process in the form of a Precedent Decision (PD), which is to be used consistently in subsequent evaluations involving the PP in question. The Precedent Decisions specifically associated with this PP are listed below:

• PD-0129: Deletion of the oldest audit events when audit storage space is exhausted
• PD-0130: Clarification of Alert requirement in Basic Robustness Anti-Virus PP

This U.S. Government Approved Protection Profile is not assigned to any Validated Products

This U.S. Government Approved Protection Profile does not have any related Technical Decisions