cti-cybox message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [cti-cybox] Network Connection Object Refactoring
- From: "Jason Keirstead" <Jason.Keirstead@ca.ibm.com>
- To: "Kirillov, Ivan A." <ikirillov@mitre.org>
- Date: Mon, 15 Feb 2016 19:55:06 -0400
There was a substantial amount of feedback on this proposal on Slack a few weeks ago... many of which aren't captured.
Can this be re-posted somewhere we can comment directly on it, such as Google Docs? It would greatly help the discussion.
I don't really want to re-hash all of my slack chat comments over email (or on the phone)... but I can do that if needed...
-
Jason Keirstead
STSM, Product Architect, Security Intelligence, IBM Security Systems
www.ibm.com/security | www.securityintelligence.com
Without data, all you are is just another person with an opinion - Unknown
"Kirillov, Ivan A." ---02/15/2016 05:35:27 PM---All, Here is a community contributed proposal around refactoring the Network Connection Object and r
From: "Kirillov, Ivan A." <ikirillov@mitre.org>
To: "cti-cybox@lists.oasis-open.org" <cti-cybox@lists.oasis-open.org>
Date: 02/15/2016 05:35 PM
Subject: [cti-cybox] Network Connection Object Refactoring
Sent by: <cti-cybox@lists.oasis-open.org>
All,
Here is a community contributed proposal around refactoring the Network Connection Object and related Objects: https://github.com/CybOXProject/schemas/wiki/CybOX-3.0:-Network-Connection-Object-Refactoring
The main points around this refactoring are:- The hierarchy around Network Objects would be replaced with an extension-based approach (as with the File Object) that revolves around the “base” Network Connection Object
- A base set of properties common to all network connections would be defined
- Existing layer 7 Objects (HTTP Session and DNS Query) would be become extensions
- The Network Flow Object would likely be split up into its components (e.g, YAF log, Netflow log, etc.), each of which would be an extension
- New extensions for common Network Connection properties, e.g., port, state and packet statistics, would be added
- Connections to destination/source IP addresses would be defined via relationships
- The existing Socket Address Object would be deprecated, as given the specification of IP addresses via relationships and the new port Network Connection Object extension it will no longer be necessary
We plan on discussing this (at least these high-level points) during tomorrow’s working session.
Regards,
Ivan
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]