Re: Ability to withstand well known attacks

[Neal Ziring <nziring@thecouch.ncsc.mil>]

Florian, George,

  I think this discussion could use an
injection from George's "related work".

The Common Criteria does address this
issue to some extent, as a lifecycle
assurance requirement.  I've included
the relevant text below, but if you have a
copy of the CC, it's section 12.2 of Part 3.

Basically, we want vendors to fix bugs
as they come up, faithfully and in a
timely manner, so that by the time a
device is ready for operational use it
is proof against known flaws.

Perhaps we could adapt the wording from
the Common Criteria, or even use the CC
(ISO15408) as a normative reference?

...nz

--------------------------------------------------------------------------

*** 12.2 Flaw remediation (ALC_FLR)

ALC_FLR Flaw remediation
Objectives
Flaw remediation requires that discovered security flaws be tracked and corrected by the
developer. Although future compliance with flaw remediation procedures cannot be determined at
the time of the TOE evaluation, it is possible to evaluate the policies and procedures that a
developer has in place to track and correct flaws, and to distribute the flaw information and
corrections.

** ALC_FLR.1 Basic flaw remediation

ALC_FLR.1.1D The developer shall document the flaw remediation procedures.
Content and presentation of evidence elements:
ALC_FLR.1.1C The flaw remediation procedures documentation shall describe the procedures
used to track all reported security flaws in each release of the TOE.
ALC_FLR.1.2C The flaw remediation procedures shall require that a description of the nature
and effect of each security flaw be provided, as well as the status of finding a
correction to that flaw.
ALC_FLR.1.3C The flaw remediation procedures shall require that corrective actions be
identified for each of the security flaws.
ALC_FLR.1.4C The flaw remediation procedures documentation shall describe the methods
used to provide flaw information, corrections and guidance on corrective
actions to TOE users.

** ALC_FLR.2 Flaw reporting procedures

ALC_FLR.2.1D The developer shall document the flaw remediation procedures.
ALC_FLR.2.2D The developer shall establish a procedure for accepting and acting upon user
reports of security flaws and requests for corrections to those flaws.
Content and presentation of evidence elements:
ALC_FLR.2.1C The flaw remediation procedures documentation shall describe the procedures used
to track all reported security flaws in each release of the TOE.
ALC_FLR.2.2C The flaw remediation procedures shall require that a description of the nature and
effect of each security flaw be provided, as well as the status of finding a correction
to that flaw.
ALC_FLR.2.3C The flaw remediation procedures shall require that corrective actions be identified
for each of the security flaws.
ALC_FLR.2.4C The flaw remediation procedures documentation shall describe the methods used to
provide flaw information, corrections and guidance on corrective actions to TOE
users.
ALC_FLR.2.5C The procedures for processing reported security flaws shall ensure that any
reported flaws are corrected and the correction issued to TOE users.
ALC_FLR.2.6C The procedures for processing reported security flaws shall provide
safeguards that any corrections to these security flaws do not introduce any
new flaws.

** ALC_FLR.3 Systematic flaw remediation

ALC_FLR.3.1D The developer shall document the flaw remediation procedures.
ALC_FLR.3.2D The developer shall establish a procedure for accepting and acting upon user reports
of security flaws and requests for corrections to those flaws.
ALC_FLR.3.3D The developer shall designate one or more specific points of contact for user
reports and inquiries about security issues involving the TOE.
Content and presentation of evidence elements:
ALC_FLR.3.1C The flaw remediation procedures documentation shall describe the procedures used
to track all reported security flaws in each release of the TOE.
ALC_FLR.3.2C The flaw remediation procedures shall require that a description of the nature and
effect of each security flaw be provided, as well as the status of finding a correction
to that flaw.
ALC_FLR.3.3C The flaw remediation procedures shall require that corrective actions be identified
for each of the security flaws.
ALC_FLR.3.4C The flaw remediation procedures documentation shall describe the methods used to
provide flaw information, corrections and guidance on corrective actions to TOE
users.
ALC_FLR.3.5C The procedures for processing reported security flaws shall ensure that any reported
flaws are corrected and the correction issued to TOE users.
ALC_FLR.3.6C The procedures for processing reported security flaws shall provide safeguards that
any corrections to these security flaws do not introduce any new flaws.
ALC_FLR.3.7C The flaw remediation procedures shall include a procedure requiring timely
responses for the automatic distribution of security flaw reports and the
associated corrections to registered users who might be affected by the security
flaw.