Name of Your Organization:
McAfee, Inc.
Web Site:
Adopting Capability:
McAfee Network Access Control
Capability home page:
http://www.mcafee.com/us/products/network-access-control.aspx
Adoption Capabilities
If the functionality is available now, indicate "Yes." If it has been implemented but not released, indicate "Beta". If planned but not currently available, indicate "Planned". If there are no plans for a specific category, that section(s) is not included as part of the questionnaire below.
OVAL Definition Evaluator — Yes
Product Accessibility <AR_1.9>
Provide a short description of how and where your capability is made available to your customers and the public.
The product is available via a commercial license. Further information on purchasing McAfee Network Access Control is available online from http://www.mcafee.com/us/purchase.aspx.
Language Version Indication <AR_1.10>
Describe how and where the capability indicates the version of the OVAL Language used to validate, create, or update its content.
The product currently supports OVAL Versions 5.3, 5.4, 5.5, 5.6. Our upcoming version adds support up to 5.9.
Error Reporting <AR_2.1>
Indicate how a user who discovers an error in the capability’s use of OVAL can report the error.
Customers who feel they have discovered an error can utilize the Technical Support ServicePortal online at https://mysupport.mcafee.com/Eservice/Default.aspx to determine if the error encountered is a known error. A KnowledgeBase article may exist that describes the situation and the anticipated timeline to correction. If it appears this is a new error, customers can open a help desk ticket with McAfee Support.
Responding to Error Reports <AR_2.2>
Describe the approach to responding to the above error reports and how applicable fixes will be applied.
All reported potential errors are investigated by the technical support department. If a defect is confirmed, it is escalated to the appropriate SCAP content development team to be investigated and corrected. Once corrected, the updated content will be made available either via the normal content posting cycle or via an out-of-band release as appropriate.
Adoption Documentation <AR_3.1>
Provide a copy, or directions to the location, of where the documentation describes OVAL and OVAL Adoption for any customers.
This is described in the McAfee Network Access Control 3.2 Product and Installation Guide.
Language Support <AR_3.2>
List each supported component schema and specific OVAL Tests in those component schemas that are supported. (AR_3.2)
We support all tests in the following schemas, with the exception of the sql_test.
- aix-definitions-schema.xsd
- hpux-definitions-schema.xsd
- independent-definitions-schema.xsd
- linux-definitions-schema.xsd
- macos-definitions-schema.xsd
- solaris-definitions-schema.xsd
- unix-definitions-schema.xsd
- windows-definitions-schema.xsd
Because we are enterprise software, we do not and will not support the sql_test in its current form for security reasons.
OVAL Content Error Reporting <AR_3.3>
Provide a copy, or directions to the location, of where the documentation describes the procedure by which errors in OVAL content may be reported for any OVAL content that is produced by the product.
Customers who discover an error in the OVAL output content can open a McAfee Support Helpdesk ticket.
Syntax Error Detection and Reporting <AR_4.1> <AR_4.2> <AR_4.3> <AR_4.4>
Indicate how the product or repository detects and reports syntax errors in any OVAL content that is consumed by the product or repository.
The server product will report schema errors to the user when the user attempts to import an oval_definitions file which is not schema valid. The endpoint device engine will do the same.
Type-Specific Capability Questions
Content Transparency <AR_8.1> <AR_8.2>
Indicate how the product allows users to determine which OVAL Definitions are being evaluated and examine the details of those definitions.
The OVAL results file contains all of the components of all checks in the input OVAL definitions file. All definitions therein are evaluated and will appear in the OVAL results file with the appropriate status.
Content Import Process Explanation <AR_8.3>
If the capability does not support consuming OVAL content at runtime, explain the documented process by which users can submit OVAL content for interpretation by the capability, including how quickly submitted content is made available to the capability.
||Insert answer here.||
Content Evaluation <AR_8.4> <AR_8.5> <AR_8.6> <AR_8.7>
Indicate how users can review the detailed results of evaluating an OVAL Definition on a target system.
A standard OVAL results file is created, including both the input definitions (and their component parts, along with the system characteristics element, contain the data retrieved for each of the objects in the OVAL definitions file.
Full OVAL Results <AR_8.8>
Indicate how users can review the full OVAL Results of the evaluation of an OVAL Definition on a target system.
The OVAL results file will by default contain a full OVAL results file.
Adoption Signature
Statement of Adoption <AR_1.2>
"As an authorized representative of my organization I agree that we will abide by all of the mandatory adoption requirements as well as all of the additional mandatory adoption requirements that are appropriate for our specific type of capability."
NAME: Kent Landfield
TITLE: Director, Content Strategy, Architecture and Standards
Statement of Accuracy <AR_1.2>
"As an authorized representative of my organization and to the best of my knowledge, there are no errors in the correctness of our capability’s use of the OVAL Language and the interpretation of the logic."
NAME: Kent Landfield
TITLE: Director, Content Strategy, Architecture and Standards
Statement on Follow-On Correctness Testing Support <AR_1.7>
"As an authorized representative of my organization, we agree to support the Review Authority in follow-on correctness testing activities, where appropriate types of OVAL documents might need to be exchanged with other organizations attempting to prove the correctness of their capabilities."
NAME: Kent Landfield
TITLE: Director, Content Strategy, Architecture and Standards
Page Last Updated: May 04, 2011
