Re: [scap_interest] The Context Concept

[David Solin <[e-mail]>]

Isn't this exactly what CIM is for?  CIM makes it possible to organize 
assets across many dimensions, including customer-defined "service" 
dimensions, that could easily serve as references for targeting 
purposes.  I can imagine mapping services with profiles, or more 
generally, CIM graph queries with profiles.

I've never understood what purpose AI is supposed to serve when CIM has 
been around for much longer, is already fairly well-adopted by CMDB 
vendors, and addresses the asset management problem domain quite well.

Anyway, just my $.02.

Regards,
--David Solin

-- 

jOVAL.org: OVAL implemented in Java.
/Scan any machine from any machine. For free!/
Learn More <http://www.joval.org> | Features 
<http://www.joval.org/features/> | Download 
<http://www.joval.org/download/>



On 2/21/2012 12:46 PM, Waltermire, David A. wrote:
>
> There are a variety of use cases that can benefit from synthesizing 
> asset technical information (e.g., IPs, network address, default 
> gateways, machine accessable asset tags, configurations) with 
> organizational information (e.g., device role, criticality, etc).  For 
> example, if you can generate a network graph of devices and their 
> connections, and combine that with firewall rules and other topology 
> concerns to determine visibility between hosts, you can then perform 
> attack graph analysis to determine at what points a security related 
> change will provide the greatest security benefit.  This can be one 
> method used to prioritize the implementation of various security 
> controls.  As Karen Scarfone pointed out earlier, this is also needed 
> to support host-, network-, and system-oriented metrics starting with 
> things like CVSS and CCSS scores and utilizing the composition of 
> software on hosts and hosts on networks to support roll-up.
>
> This and similar use cases are supported by asset identification, but 
> require greater formalization around asset data management to enable 
> implementation neutral, interoperable approaches.
>
> Sincerely,
>
> David Waltermire
>
> *From:*[e-mail] 
> [mailto:[e-mail]] *On Behalf Of *Luis Nunez
> *Sent:* Tuesday, February 21, 2012 1:23 PM
> *To:* Chernin, Michael A.
> *Cc:* [e-mail]
> *Subject:* Re: [scap_interest] The Context Concept
>
> We also need to look at vulnerabilities as it applies an environment. 
>  An inherent vulnerability may have differing levels of exposure 
> depending on what, where and how the node is deployed.
>
> We maybe able to leverage Asset Identification (AI) to correlate what 
> role the node is playing in the environment (endpoint, Server, 
> Inter-networking Device,..) and determine level of exposure.  The 
> level of risk could also be applied depending on where the node is 
> situated.
>
> - Directly connected to internet.
>
> - DMZ controlled
>
> - Internal Network
>
> - Secure enclave
>
> -ln
>
> On Feb 21, 2012, at 9:47 AM, Chernin, Michael A. wrote:
>
>
>
> I agree that when dealing with "threats" that context matters. 
> However, vulnerabilities alone do not imply or guarantee there is an 
> associated threat or risk.
>
> In my perfect world there would be a threat indicator standard that 
> links to a structured threat standard that then could describe the 
> CVEs used. This would allow us to continue doing vulnerability 
> management by exposure (no threat context) or by specific threat 
> (which provides context).
>
> Aharon
>
> DTCC Non-Confidential (White)
> ---------------------------------------------------
> Michael "Aharon" Chernin
> Security Automation Program Manager
> Corporate Information Security -Depository Trust & Clearing Corporation
> O: 813-470-2173
>
> *From:*[e-mail] 
> <mailto:[e-mail]>[mailto:[e-mail]]*On 
> Behalf Of*Jerome Athias
> *Sent:*Saturday, February 18, 2012 2:03 PM
> *To:*[e-mail] <mailto:[e-mail]>
> *Subject:*[scap_interest] The Context Concept
>
> In a private discussion I had at ToorCon 9, with Matt Miller (skape);
> we came to the conclusion that a key (and unresolved) point of 
> automation is the (automatic) definition of the Context in which you 
> are where dealing with a vulnerability (threat).
> It was also identified (validated?), and introduced by Druid.
> And then, the Druid's work was related (validated?) at FRHACK 01 by 
> Rodrigo Branco (bsdaemon).
>
> /Situation awareness 
> (http://en.wikipedia.org/wiki/Situation_awareness) should be taken 
> into account.//
> /Maybe search for "military situational awareness"./
>
> /My 2 dirhams/
> //JA//
>
>
> _____________________________________________________________
> DTCC DISCLAIMER: This email and any files transmitted with it are 
> confidential and intended solely for the use of the individual or 
> entity to whom they are addressed. If you have received this email in 
> error, please notify us immediately and delete the email and any 
> attachments from your system. The recipient should check this email 
> and any attachments for the presence of viruses. The company accepts 
> no liability for any damage caused by any virus transmitted by this 
> email._______________________________________________
> scap_interest mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/scap_interest
>
>
>
> _______________________________________________
> scap_interest mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/scap_interest