Re: [scap_interest] Checking language needs

<Kent_Landfield@McAfee.com> Tue, 14 February 2012 22:54 UTC

Return-Path: <Kent_Landfield@mcafee.com>
X-Original-To: scap_interest@ietfa.amsl.com
Delivered-To: scap_interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122F121F8617 for <scap_interest@ietfa.amsl.com>; Tue, 14 Feb 2012 14:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level:
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_25=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8GVpeOETvGs for <scap_interest@ietfa.amsl.com>; Tue, 14 Feb 2012 14:54:42 -0800 (PST)
Received: from dalsmrelay2.nai.com (dalsmrelay2.nai.com [205.227.136.216]) by ietfa.amsl.com (Postfix) with ESMTP id 622B321F85E1 for <scap_interest@ietf.org>; Tue, 14 Feb 2012 14:53:46 -0800 (PST)
Received: from (unknown [10.64.5.52]) by dalsmrelay2.nai.com with smtp id 023d_8a25_bb7637e4_575e_11e1_b9f8_00219b929abd; Tue, 14 Feb 2012 16:53:37 -0600
Received: from AMERDALEXMB1.corp.nai.org ([fe80::387d:3d79:ad3b:b517]) by DALEXHT2.corp.nai.org ([::1]) with mapi; Tue, 14 Feb 2012 16:52:41 -0600
From: <Kent_Landfield@McAfee.com>
To: <david.waltermire@nist.gov>, <amontville@tripwire.com>, <karen@scarfonecybersecurity.com>
Date: Tue, 14 Feb 2012 16:53:14 -0600
Thread-Topic: [scap_interest] Checking language needs
Thread-Index: Aczra1uHY2Ok2ew7Taevph/ZNryslg==
Message-ID: <CB6034F8.2C592%kent_landfield@mcafee.com>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C4930906AEA339@MBCLUSTER.xchange.nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CB6034F82C592kentlandfieldmcafeecom_"
MIME-Version: 1.0
Cc: scap_interest@ietf.org
Subject: Re: [scap_interest] Checking language needs
X-BeenThere: scap_interest@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion List for IETFers interested in the Security Content Automation Protocol \(SCAP\)." <scap_interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scap_interest>, <mailto:scap_interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scap_interest>
List-Post: <mailto:scap_interest@ietf.org>
List-Help: <mailto:scap_interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scap_interest>, <mailto:scap_interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2012 22:54:45 -0000

Dave,

What is your definition of checking clients and checking systems?  I want to make sure I understand. I think we are on the same page but wanted to make sureā€¦

Thanks.

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee | An Intel Company
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096
Mobile: +1.817.637.8026
Web: www.mcafee.com<http://www.mcafee.com/>

From: David Waltermire <david.waltermire@nist.gov<mailto:david.waltermire@nist.gov>>
Date: Tue, 14 Feb 2012 15:47:44 -0600
To: Adam Montville <amontville@tripwire.com<mailto:amontville@tripwire.com>>, Kent Landfield <kent_landfield@mcafee.com<mailto:kent_landfield@mcafee.com>>, "karen@scarfonecybersecurity.com<mailto:karen@scarfonecybersecurity.com>" <karen@scarfonecybersecurity.com<mailto:karen@scarfonecybersecurity.com>>
Cc: "scap_interest@ietf.org<mailto:scap_interest@ietf.org>" <scap_interest@ietf.org<mailto:scap_interest@ietf.org>>
Subject: RE: [scap_interest] Checking language needs

The issues we are discussing can be grouped into the following separate, but related functional areas.  Each should be treated as a separate concern.  Here are some ideas on how to parse out each area:

1) Defining a "checking design pattern" - This de facto pattern is used without a formal specification in many specifications including: XCCDF and the CPE 2.3 Applicability Language.  If we define the pattern properly, establishing a contract between checking clients and checking systems, we can stabilize our existing uses and provide a new foundation for additional checking uses cases.  This may also have the effect of stimulating novel checking solutions for mobile and network devices.  It may also make sense to look at breaking up the logical evaluation capabilities that share some commonality across XCCDF, OVAL and OCIL into a separate specification.  We have talked in the past about using the results of one check system to drive the behavior of another.  This type of approach might provide a mechanism to support that.

2) Enterprise targeting of assets - We currently have no standardized way to associate a checklist and/or a collection of checks with a set of assets that need to be interrogated to determine compliance.  This is definitely a problem for OCIL, but the approach is not formalized for OVAL checks either.  The closest thing we have is the applicability approach used in XCCDF which is not a targeting solution.  I would argue that applicability is something altogether different from targeting.  Applicability allows machine readable guidance to be pre-qualified as being purposed for scanning specific software.  What we desire from a targeting perspective is assignment of a checklist to a collection of assets that contain the applicable software.  Applicability can be used to determine what CAN be assigned, but it is not THE assignment.  It serves a separate purpose.  If we confound applicability and assignment, we risk creating checklists that are specific to an asset instead of being applicable to many assets.  This will hinder content reuse and exacerbate content management challenges.

Instead, it might be better to develop a new higher-level concept that enables definition of organizational digital policy that links rules in a checklist or checks to the appropriate assets that need to be assessed perhaps using ai:asset constructs.  For OCIL the asset in question could be the systems admin that is responsible for a set of hosts.  For OVAL the asset mapping might be to a domain server that provides group policy for a collection of hosts, or a directory server that provides authentication capabilities.  This policy can also indicate the frequency, conditions and timing of assessments, allowing automated tasks to be dispatched based on this information to enact the policy.

3) Tasking and scheduling - Based on the digital policy from the previous item, automated tasks can be created external to scanning applications to instruct them to perform a single scan, a recurring scan, establish a schedule based on a calendar or other conditions (e.g., CPU utilization, network load, etc).  By defining tasking as a separate concern from the assessment content, an organization will have the ability to orchestrate the assessment of a checklists or a collection of checks against many different sets of assets (e.g., people, systems, networks, devices) using independent tasks.  They can also use the same standardized approach to orchestrate different scanning solutions within their environments. This further promotes content reuse and avoids the need to customize content for a specific scanning task or solution.

My hope is that the MILE GRC Exchange specification can be shapped to support a high-level framework that allows detailed task messages to be exchanged using more specialized models (e.g., assessment, remdiation, etc.) as GRC message payloads.

Dave Waltermire


-----Original Message-----
From: scap_interest-bounces@ietf.org<mailto:scap_interest-bounces@ietf.org> [mailto:scap_interest-bounces@ietf.org] On Behalf Of Adam Montville
Sent: Tuesday, February 14, 2012 3:50 PM
To: Kent_Landfield@McAfee.com<mailto:Kent_Landfield@McAfee.com>; karen@scarfonecybersecurity.com<mailto:karen@scarfonecybersecurity.com>
Cc: scap_interest@ietf.org<mailto:scap_interest@ietf.org>
Subject: Re: [scap_interest] Checking language needs

Kent,

I think scheduling should be a separate concern, but can see targeting being embedded in the checking system, much as it is today in OVAL (in a way, the inventory definitions perform the targeting for technical checks).  If we were to leverage Asset Identification, the targeting could be handled in some cases with a simple ai:asset reference - a person is targeted as the owner of the given system.

Adam

From: kent_landfield <kent_landfield@mcafee.com<mailto:kent_landfield@mcafee.com><mailto:kent_landfield@mcafee.com>>
Date: Tue, 14 Feb 2012 14:30:27 -0600
To: <karen@scarfonecybersecurity.com<mailto:karen@scarfonecybersecurity.com><mailto:karen@scarfonecybersecurity.com>>
Cc: <scap_interest@ietf.org<mailto:scap_interest@ietf.org><mailto:scap_interest@ietf.org>>
Subject: Re: [scap_interest] Checking language needs

Thanks Karen!  I'll take you up on that!

>From the standpoint of what should be included beyond the actual integration issues, should this document, in addition to integration, discuss issues such as targeting and scheduling for interrogative checking systems like OCIL or would folks consider that a separate issue to be dealt with somewhere else?

Thoughts?

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee | An Intel Company
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096
Mobile: +1.817.637.8026
Web: www.mcafee.com<http://www.mcafee.com/>

From: Karen Scarfone <karen@scarfonecybersecurity.com<mailto:karen@scarfonecybersecurity.com><mailto:karen@scarfonecybersecurity.com>>
Date: Tue, 14 Feb 2012 14:11:21 -0600
To: Kent Landfield <kent_landfield@mcafee.com<mailto:kent_landfield@mcafee.com><mailto:kent_landfield@mcafee.com>>
Cc: "scap_interest@ietf.org<mailto:scap_interest@ietf.org><mailto:scap_interest@ietf.org>" <scap_interest@ietf.org<mailto:scap_interest@ietf.org><mailto:scap_interest@ietf.org>>
Subject: Re: [scap_interest] Checking language needs

Kent,

I'd be happy to help with the publication/editing side of specification development.


Karen

On Tue, Feb 14, 2012 at 3:02 PM, <Kent_Landfield@mcafee.com<mailto:Kent_Landfield@mcafee.com><mailto:Kent_Landfield@mcafee.com>> wrote:
All,

One of the missing pieces we have right now is a standardized approach to developing new checking languages.  Within fielded XCCDF-enabled products today there are multiple checking languages in use. One of them grew up with XCCDF (OVAL) and another (OCIL) was developed without much concern for how it might be called and used from XCCDF.  The later's adoption rate has been seriously impacted because of that.  Additionally, vendors have at times introduced their own checking mechanisms to support customer needs that could not be supported with the existing checking languages.  Scripting is also being done directly from XCCDF benchmarks by multiple vendor products.

As we are starting to expand security automation uses, it is important we enable innovative approaches to check execution. Not everything can be done using the existing model and existing means.  Continuous monitoring uses are going to require more flexibility by requiring different means to check certain areas than exist today.  Forcing implementers to have to dig thru the XCCDF specification to have to figure out how to properly integrate with it is an inhibitor. We need to foster alternative means so integrating into the the existing security automation architectures and products is not so daunting.  Even in areas where something as simple as scripting is used, I would be very surprised if two existing implementations could execute the same script content because of incompatible implementation approaches.  Yes, OVAL is interoperable today but we need to make sure additional checking languages have that same potential for interoperability.

>From my perspective, the key to the success in fielding a useful framework is assuring the right building blocks are in place.  We need to be able to leverage those building blocks to expand standards based security automation. It is important we document the proper way to develop new checking mechanisms if we are to have content and solutions that interoperate effectively.  By specifying the practices and items  new checking languages need to support, we can expand what is possible with security automation using already fielded tools and environments.

I am looking for interest here and for those that might want to help me in producing this draft specification.

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee | An Intel Company
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096
Mobile: +1.817.637.8026
Web: www.mcafee.com<http://www.mcafee.com/>

_______________________________________________
scap_interest mailing list
scap_interest@ietf.org<mailto:scap_interest@ietf.org><mailto:scap_interest@ietf.org>
https://www.ietf.org/mailman/listinfo/scap_interest




--
Karen Scarfone, Principal Consultant, Scarfone Cybersecurity
karen@scarfonecybersecurity.com<mailto:karen@scarfonecybersecurity.com><mailto:karen@scarfonecybersecurity.com>   (703)401-1018

_______________________________________________ scap_interest mailing list scap_interest@ietf.org<mailto:scap_interest@ietf.org><mailto:scap_interest@ietf.org> https://www.ietf.org/mailman/listinfo/scap_interest

_______________________________________________
scap_interest mailing list
scap_interest@ietf.org<mailto:scap_interest@ietf.org>
https://www.ietf.org/mailman/listinfo/scap_interest